Skip to Content.
Sympa Menu

baslinux - Re: [BL] More Busyboxen

baslinux AT lists.ibiblio.org

Subject: Baslinux mailing list

List archive

Chronological Thread  
  • From: sindi keesan <keesan AT sdf.lonestar.org>
  • To: baslinux AT lists.ibiblio.org
  • Subject: Re: [BL] More Busyboxen
  • Date: Tue, 20 Dec 2005 20:49:34 +0000 (UTC)

On Tue, 20 Dec 2005, David Moberg wrote:

sindi keesan wrote:

Will it hurt, if I operate only as /root, to leave everything where it is?

No.

I think your script requires the full tail and expr.

It should not.

Have you actually run it from BL3 or BL2?

Yes, but with Stephen's busybox (the first one).

David

I tried to copy that one to busybox while running BL2 and was told
Unable to open 'busybox': Text file busy.
I rebooted and used BL3 to
cp busybox-1.01 busybox

If I try to run your 1.sh using the current BL3 busybox:
expr: syntax error
Usage: tail [OPTION]... [FILE]...

I chrooted to BL2 to test this new busybox (and use it with 1.sh).
ls did not work. Function not implemented

Rebooted to BL2. ls still does not work, nor do some other things during boot (chmod?). Insmod is not working. The link to it is in /sbin not /bin/busybox. /sbin is on the path (type set).
cp: unable to stat '(filename)': Function not implemented.
top: scandir('/proc'): Function not implemented.
du: Function not implemented.
Many functions still work. find cd time tar

There was something about binary incompatibility - is this it?

I restored the BL3 busybox version and ls works again. Someone else please try 1.01 uclibc static in BL2 (or BL3) and if it works, explain the proper way to replace the current busybox with it.
My method worked to replace BL2 busybox with BL3 busybox.

Sindi




Archive powered by MHonArc 2.6.24.

Top of Page