I'll try strace Monday. I also built a static gcc-based busybox 1.6.1 and it failed with a different message. The busybox 1.6.1 also worked on a fully-booted box which makes me think that either something is missing (like a file in /dev), or a binary is missing.
The last time I used busybox, I could use gcc and link a program with it using the wrappers -- I guess a full environment is require now (I'll test on Monday). Thanks, -- Wade Hampton On 7/13/07, Denis Vlasenko <[EMAIL PROTECTED]> wrote: > On Friday 13 July 2007 16:52, Wade Hampton wrote: > > G'day, > > > > I am trying to use busybox in an initrd for system install/reinstall. > > The O/S is CentOS 5. My initrd is trying to mount a backup server > > using NFS, but fails with "No such device". > > Can you run it under strace? > > > O/S: CentOS 5.0 with updates, 2.6.18-8.1.1.el5 kernel > > Busybox: 1.2.0-3.el5 > > Same O/S for server and client. > > > > This works on a booted system: > > mkdir /mnt/tmp > > /sbin/busybox mount 10.1.2.3:/data -t nfs -o ro,hard,intr /mnt/tmp > > > > In the initrd this fails: > > mkdir -p /mnt/tmp > > mount 10.1.2.3:/data -t nfs -o ro,hard,intr /mnt/tmp > > > > Both have the exact same kernel and exact same busybox. I verified > > that the IP addresses are not an issue. I have tried adding > > rsize=1024,wsize=1024 and other mount options but still get the same > > error. > > > > Note, I tried making busybox 1.6.1 static but it fails with "static > > linking against glibc...". > > > > Should I make a static busybox 1.6.1 using uLibc and test that? If so, is > > there a simple way of doing this (the last time I did this was busybox 0.6 > > and lots have changed). Such instructions would be nice for the FAQ. > > I have uclibc cross compiler on my system: > > # ls /usr/bin/i486-linux-uclibc-* > /usr/bin/i486-linux-uclibc-addr2line /usr/bin/i486-linux-uclibc-gcc > /usr/bin/i486-linux-uclibc-objdump > /usr/bin/i486-linux-uclibc-ar /usr/bin/i486-linux-uclibc-gcc-4.1.1 > /usr/bin/i486-linux-uclibc-ranlib > /usr/bin/i486-linux-uclibc-as /usr/bin/i486-linux-uclibc-gccbug > /usr/bin/i486-linux-uclibc-readelf > /usr/bin/i486-linux-uclibc-c++ /usr/bin/i486-linux-uclibc-gcov > /usr/bin/i486-linux-uclibc-size > /usr/bin/i486-linux-uclibc-c++filt /usr/bin/i486-linux-uclibc-ld > /usr/bin/i486-linux-uclibc-strings > /usr/bin/i486-linux-uclibc-cpp /usr/bin/i486-linux-uclibc-nm > /usr/bin/i486-linux-uclibc-strip > /usr/bin/i486-linux-uclibc-g++ /usr/bin/i486-linux-uclibc-objcopy > > And building against uclibc is done simply like this: > > export ARCH=i386 > make CROSS_COMPILE=i486-linux-uclibc- > -- > vda > _______________________________________________ busybox mailing list [email protected] http://busybox.net/cgi-bin/mailman/listinfo/busybox
