My problem is solved! Somehow /dev/null was no longer a device, but a file. It contained some binary and some text lines like "term signal received", "shutting down" and so on. So it seems as if it has been created when I did a "shutdown -r". The timestamp shows, that it has been created after I installed the new busybox binary. Maybe there's a problem when booting up with busybox 1.4.1, but shutting down with busybox 1.9.1....? But it might concern my nas device only, because shutdown is not a symlink to busybox, but a standalone binary.
Anyway, my nas device (a linkstation) is running busybox 1.9.1 w/o problems, after re-creating the null device. :-) Regards, Thorsten ---------- Forwarded message ---------- From: Thorsten Hirsch <[EMAIL PROTECTED]> Date: 13.03.2008 10:58 Subject: Re: [EMAIL PROTECTED] To: [email protected] Hervé, there is no new link in my root directory. Walter, uhm... I'm not sure, it's been about a year when I installed the old version on my nas device. IIRC it was a .tar.gz with the binaries, but it also might have been an ipkg. Anyway, I did not clear anything, I just unpacked the .tar.gz or installed the ipkg. And I also didn't clear my fs yesterday, when I installed the new version. So all the command symlinks in /bin and /usr/bin to busybox are the same as before ...so now that I replaced the new busybox binary with the old one, everything should be the same as before. A developer of my nas device's open firmware said, that he believes one or more commands that take place in the boot process don't behave anymore as they did in the old version. So the boot script(s) need to be modified. But that does not explain, why my old busybox binary does not work anymore. I guess you're right - there must be some dangling link since "make install" of the new version. But where? Regards, Thorsten
_______________________________________________ busybox mailing list [email protected] http://busybox.net/cgi-bin/mailman/listinfo/busybox
