Menu
▾
▴
devil-linux-discuss
|
From: Martin G. <mar...@we...> - 2007-05-10 16:12:35
|
Hi, I had several Problems to use devil 1.2 on newer Hardware (connected to Intel ICH8, netcard and SATA drivers) Therefore I started to build 1.3.4. I had to configure only 2 Packages off, but make iso finally gives me an ISO, that is unable to find a config and the devil CD and stops. Can someone guide me, what I have to do, to get at least a running kernel+login. (I don't need much more for now). TIA Martin |
|
From: Martin G. <mar...@we...> - 2007-05-11 11:27:31
|
OK, I debugged the linuxrc coming when booting the 1.3.4 image. The problem seems to be, that ouputs of program calls in backticks `` are not working inside linuxrc. All variables assigned with backticks stay empty! (This are e.g. CONFIG_USER_ONLY and DEVICES_XXX.) If I bail out to /bin/sh and execute the commands (find /dev) manually, I get output.. the /bin/sh seems to behave differently when executing scripts or outside of it. What kind of sh is it? Martin |
|
From: Bruce S. <bw...@ar...> - 2007-05-11 12:11:06
|
> backticks `` are not working inside linuxrc. Can you try $(command) instead of backquotes? i.e. `ls` becomes: $(ls) - BS |
|
From: Martin G. <mar...@we...> - 2007-05-11 12:29:48
|
On May 11, 2007, at 2:11 PM, Bruce Smith wrote: > Can you try $(command) instead of backquotes? > > i.e. `ls` becomes: $(ls) Tried it on the find's for the devices: no change. Another test inside the booted initrd: / $ cat >bla.sh<<EOF #!/bin/sh bla=$(ls) echo $bla EOF / $ chmod 700 bla.sh / $ ./bla.sh / $ bla=$(ls) / $ echo $(bla) VERSION bin cd cdrom .... / $ Any idea? Martin |
|
From: Bruce S. <bw...@ar...> - 2007-05-11 12:34:57
|
> > Can you try $(command) instead of backquotes? > > > > i.e. `ls` becomes: $(ls) > > Tried it on the find's for the devices: no change. Is the first line: "#!/bin/sh" ? What is /bin/sh sym-linked to? Try changing the first line of the script to "#!/bin/bash" instead? - BS |
|
From: Heiko Z. <he...@zu...> - 2007-05-11 13:41:11
|
On Fri, May 11, 2007 07:34, Bruce Smith wrote: >>> Can you try $(command) instead of backquotes? >>> >>> >>> i.e. `ls` becomes: $(ls) >> >> Tried it on the find's for the devices: no change. >> > > Is the first line: "#!/bin/sh" ? > > > What is /bin/sh sym-linked to? > > > Try changing the first line of the script to "#!/bin/bash" instead? Won't work. Only busybox is available in the initrd. -- Regards Heiko Zuerker http://www.devil-linux.org |
|
From: Martin G. <mar...@we...> - 2007-05-11 12:39:50
|
Dear Bruce, Bruce Smith wrote: > > Is the first line: "#!/bin/sh" ? > > What is /bin/sh sym-linked to? > > Try changing the first line of the script to "#!/bin/bash" instead? First line is /bin/sh, which is linked to busybox, which seems to be the "shell and everything" (find, grep ...) inside the initrd. one static binary with 1M Inside Initrd there is no bash... Martin |
|
From: Bruce S. <bw...@ar...> - 2007-05-11 12:47:41
|
> > Is the first line: "#!/bin/sh" ? > > > > What is /bin/sh sym-linked to? > > > > Try changing the first line of the script to "#!/bin/bash" instead? > > First line is /bin/sh, which is linked to busybox, which seems to be > the "shell and everything" (find, grep ...) inside the initrd. > > one static binary with 1M > > Inside Initrd there is no bash... OK, maybe busybox is the wrong version (compare versions to DL 1.2), or maybe it was compiled with the wrong options (compare to 1.2)? - BS |
|
From: Heiko Z. <he...@zu...> - 2007-05-11 13:36:13
|
On Fri, May 11, 2007 06:27, Martin Ginkel wrote: > > OK, I debugged the linuxrc coming when booting the 1.3.4 image. > The problem seems to be, that ouputs of program calls in > backticks `` are not working inside linuxrc. All variables assigned with > backticks stay empty! (This are e.g. CONFIG_USER_ONLY and DEVICES_XXX.) > > > If I bail out to /bin/sh and execute the commands (find /dev) manually, > I get output.. > > > the /bin/sh seems to behave differently when executing scripts or outside > of it. > > What kind of sh is it? Busybox's ash implementation. It may just be a busybox problem. I also still got a few changes on my build machine, which I still have to check in to CVS (need to do some 1.2 stuff first). -- Regards Heiko Zuerker http://www.devil-linux.org |
|
From: Martin G. <mar...@we...> - 2007-05-11 14:31:21
|
Heiko Zuerker wrote: > Busybox's ash implementation. > It may just be a busybox problem. Strange, the first complete build worked properly. Now I wanted to recompile some packs (including the kernel) and found that 'uname -m' no longer returns i686 but only i Apparently it had been overwritten during build (m-time): is this normal? I unpacked the lfssystem into the directory again, now it works normally Martin |
|
From: Heiko Z. <he...@zu...> - 2007-05-11 14:54:00
|
On Fri, May 11, 2007 09:31, Martin Ginkel wrote: > Heiko Zuerker wrote: > >> Busybox's ash implementation. >> It may just be a busybox problem. >> > > Strange, > the first complete build worked properly. Now I wanted to recompile some > packs (including the kernel) and found that 'uname -m' no longer returns > i686 but only i > > Apparently it had been overwritten during build (m-time): > is this normal? > > I unpacked the lfssystem into the directory again, now it works normally yes we're messing with the uname in order to force the compile of the correct code. We rename uname to uname.old (so you can always copy it back) and create a bash script uname. It then calls uname.old and replaces the necessary strings to 'simulate' the correct CPU. This usually happens when you interrupt the build process in the wrong moment. If that happens, just copy the uname.old over to uname and it should work again. -- Regards Heiko Zuerker http://www.devil-linux.org |
|
From: Heiko Z. <he...@zu...> - 2007-05-12 14:54:13
|
On Thu, May 10, 2007 11:12, Martin Ginkel wrote: > Hi, > > > I had several Problems to use devil 1.2 on newer Hardware (connected to > Intel ICH8, netcard and SATA drivers) Therefore I started to > build 1.3.4. > > I had to configure only 2 Packages off, but make iso finally > gives me an ISO, that is unable to find a config and the devil CD and > stops. I can confirm this problem, the same system happens here. I'll do some tests. -- Regards Heiko Zuerker http://www.devil-linux.org |
|
From: Heiko Z. <he...@zu...> - 2007-05-14 00:19:03
|
On Sat, May 12, 2007 09:53, Heiko Zuerker wrote: > > On Thu, May 10, 2007 11:12, Martin Ginkel wrote: > >> Hi, >> >> >> >> I had several Problems to use devil 1.2 on newer Hardware (connected to >> Intel ICH8, netcard and SATA drivers) Therefore I started to >> build 1.3.4. >> >> I had to configure only 2 Packages off, but make iso finally >> gives me an ISO, that is unable to find a config and the devil CD and >> stops. > > I can confirm this problem, the same system happens here. > I'll do some tests. I'm a little confused... I did quite a few tests (even tried busybox 1.4.1 and 1.5.0) and it just doesn't work. For some reason it doesn't populate the variables with the device names. If I run the very same commands on the command line (by adding /bin/sh to linuxrc), they successfully execute. -- Regards Heiko Zuerker http://www.devil-linux.org |
|
From: Martin G. <mar...@we...> - 2007-05-14 07:38:01
|
Heiko Zuerker wrote: > I did quite a few tests (even tried busybox 1.4.1 and 1.5.0) and it just > doesn't work. For some reason it doesn't populate the variables with the > device names. If I run the very same commands on the command line (by > adding /bin/sh to linuxrc), they successfully execute. Yep, exactly my observation: The commands work in interactive mode only. Inside a script all backticks and similar ($(bla)) fail. Can there be a problem with file descriptors or something? Martin |
|
From: Serge L. <fi...@in...> - 2007-05-22 15:27:10
|
Hi Martin, Martin Ginkel wrote: > Yep, exactly my observation: The commands work in interactive mode only. > Inside a script all backticks and similar ($(bla)) fail. Can there be a > problem with file descriptors or something? > No, it's glibc bug. Please, sync now and try once again. -- Serge |
|
From: Serge L. <fi...@in...> - 2007-05-22 15:46:25
|
Serge Leschinsky wrote: > No, it's glibc bug. Please, sync now and try once again. Oops.. not glibc... My hands are before my minds. Sorry. On the other hands... it doesn't matter if glibc or gcc or bintools ;-) See http://sources.redhat.com/bugzilla/show_bug.cgi?id=3400 for details. -- Serge |
|
From: Heiko Z. <he...@zu...> - 2007-05-14 12:53:29
|
On Mon, May 14, 2007 02:37, Martin Ginkel wrote: > Heiko Zuerker wrote: > >> I did quite a few tests (even tried busybox 1.4.1 and 1.5.0) and it >> just doesn't work. For some reason it doesn't populate the variables >> with the device names. If I run the very same commands on the command >> line (by adding /bin/sh to linuxrc), they successfully execute. > > Yep, exactly my observation: The commands work in interactive mode only. > Inside a script all backticks and similar ($(bla)) fail. Can there be a > problem with file descriptors or something? Not sure. The other thing which changed recently (which could cause problems) is the kernel. I wanted to try the 2.6.21 anyway, maybe that resolves it. -- Regards Heiko Zuerker http://www.devil-linux.org |
|
From: Bruce S. <bw...@ar...> - 2007-05-14 13:18:43
|
> The other thing which changed recently (which could cause problems) is the
> kernel. I wanted to try the 2.6.21 anyway, maybe that resolves it.
I read that 2.6.22 is almost ready, .22-rc{something} was just released.
- BS
|
