[BusyBox] Some problems with busybox-1.0.0-pre1

[Eric Spakman]

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 

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

-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.

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

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

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

-Su problem? While doing:
#adduser test
 ok
#su test
 ok
#whoami 
test
#su
this applet requiere priviliged rights 
 
-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.

Regards,
Eric Spakman