can't get init to work

Craig craig5 at pobox.com
Thu Oct 25 04:49:54 UTC 2007


Yes, it appears to load the image. (My previous email had the boot 
output. Which said that the root filesystem was loaded.)

Sigh... I was missing a lib... I kept thinking the error would be 
something else for a missing lib.

Anyway, it seems to work. Now, I just need to get networking up. :)

Thanx for the quick response!

Craig

P.S. Just for reference. To figure out the missing lib:
$ ldd /usr/local/src/busybox-1.7.2/busybox
         libcrypt.so.1 => /lib/libcrypt.so.1 (0x00cce000)
         libm.so.6 => /lib/tls/libm.so.6 (0x002bb000)
         libc.so.6 => /lib/tls/libc.so.6 (0x0018d000)
         /lib/ld-linux.so.2 (0x0016f000)


Hamish Moffatt wrote:
> On Wed, Oct 24, 2007 at 09:15:47PM -0700, Craig wrote:
>> I am using busybox 1.7.2 on a CentOS 4.4 kernel (2.6.9). Everything 
>> seemed to compile fine. I am able to run the shell 
>> (/usr/local/src/busybox-1.7.2/busybox ash) and able to run some simple 
>> commands.
>>
>> But, when I try to build an initrd from it, things don't seem to work. I 
>> have tried PXE booting:
>>
>>          kernel os/test/vmlinuz
>>          append root=/dev/ram0 initrd=os/test/initrd.img.gz init=/linuxrc
> 
> Does it load the image and mount the root file system ok in this
> configuration?
> 
> With an unpacked version of your initrd image (or mount it via loop
> device), try to chroot into the directory and run /linuxrc. Does it run?
> 
> You might be missing libraries or something like that.
> 
> 
> Hamish



More information about the busybox mailing list