[BusyBox] Some problems with busybox-1.0.0-pre1

Erik Andersen andersen at codepoet.org
Sat Jul 26 09:27:11 UTC 2003


On Mon Jul 21, 2003 at 07:07:40PM +0200, Eric Spakman wrote:
> Hello all,
> 
> While working with busybox for some time, we found some bugs and 
> small glitches in 1.0.0-pre1. Below is a list:
> 
> -Some files still have libc5 hacks, while libc5 is no longer 
> supported: 
> Rules.mak, swaponoff.c, syslogd.c, isnmod.c, syscalls.c, setgroups.c, 
> interface.c, module_syscalls.c, libbb.h, logread.c, ping.c, 
> traceroute.c, wget.c, dutmp.c, busybox.h. 
> 
> For umount.c and cmdedit.c, the comments tell it's for libc5 but the 
> code defines < Glibc2.1 

fixed.

> -start-stop-daemon and run-parts only supports "short" options. The 
> Debian start-up scripts can't be used this way. 

I have redone the start-stop-daemon option parsing.

> -You can't choose busybox logger without also choosing at least 
> syslogd (it could with 0.60.5). In the "full blown" sources, logger 
> is part of "util-linux" not "sysklogd". Now it isn't possible to 
> choose an other, not busybox syslogd (f.i. syslog-ng) and use logger 
> from busybox.

You can now build logger w/o needing syslogd.

> -Running shell scripts containing more than a "few" lines on busybox 
> ash generates a segmentation fault: ash memory problems?

I run lots of comlex shell scripts w/o problems.  Perhaps you
should submit the script you are having problems with and/or
an strace or ltrace of this seg fault...

> -Message: "mknod: null: File exists" while creating /dev files (mknod 
> null c 1 3)

That is exactly what is supposed to happen when the /dev/null
already exists....

> -Message: "umount: bb_xasprintf: Read-only file system" while 
> halting/rebooting 

Sounds like you are using uClibc and have messed up the
permissions on /dev/null

> #su
> this applet requiere priviliged rights 

You did not make busybox setuid root, therefore the su
test was not able to work...

> -You can't choose ifupdown and iproute2 compatability, without also 
> choosing busybox iproute2. This way it's not possible to use the full 
> blown iproute2 programs with busybox ifupdown.

Fair enough.  Fixed.

 -Erik

--
Erik B. Andersen             http://codepoet-consulting.com/
--This message was written using 73% post-consumer electrons--



More information about the busybox mailing list