Fr > Mike Sensney wrote: > > > > For Eiger, busybox is called "ln" and is located in /bin > > Busybox is not "called" ln; it IS ln, cp, mv, rm, tar, gzip, gunzip, > swapon, swapoff, mknod, insmod, rmmod, lsmod, ...on my system, it has > about 70 applets.. > You are both right. but in the eigerstein image the busybox is renamed to ln and the other commands that are implemented by busybox are linked to ln. (It puzzled me also for some time ;) ) > > I had to make a copy to get it to ID itself: > > > > BusyBox v0.28 (19990719-2233) multi-call binary -- GPL2 > > Yow! Busybox v0.50 is about to be released - looks like this was > compiled June 19, 1999 - makes it coming up on two years old! I know > LRP 2.9.7 used busybox v0.48 or v0.49; there is your trouble right > there. > > It's time you upgraded. First of all, Eiger itself is also hopelessly > out of date; EigerStein2 Beta is the most recent in that lineage. > > To upgrade busybox there are some basic steps: > > 1. Compile or get a new version of busybox > * Compile busybox from CVS using Debian 2.1 or Red Hat 5.2 > * Get busybox from another source > > 2. Install the new busybox in your system > * Use these steps, if busybox (new) is in /tmp: > > # cd /tmp > # chmod 755 ./busybox > # type busybox > <find out where busybox is in your system> > # ./busybox cp ./busybox /bin/busybox > <using the right location at the end, if not /bin/busybox> > > 3. Save the changes > * This means updating root.lrp - and differs among systems. > Probably using lrpkg right? > Eric Wolzak _______________________________________________ Leaf-devel mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/leaf-devel
