On Monday 17 March 2008 14:16, Thorsten Hirsch wrote:
> 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. :-)
This is a known administration problem in UNIX. Many utils delete incomplete
result file on error, but forget to check that it is a *file*. Now
imagine what can happen if e.g. wget deletes partially downloaded file
on Ctrl-C?
wget http://busybox.net/ -O /dev/null
If you ran this as root, BLAMMM and your /dev/null is gone.
There are too many programs to audit for this bug, so sometimes this happens.
I don't know how to fix it (make /dev/null undeletable even by root).
--
vda
_______________________________________________
busybox mailing list
[email protected]
http://busybox.net/cgi-bin/mailman/listinfo/busybox
