[BusyBox] Some problems with busybox-1.0.0-pre1

[Eric Spakman]

Manuel,

> > > Hmm... I suppose that if you were using uClibc and if /dev/null didn't
> > > exist, then a /dev/null empty regular file could be created by
> > > asprintf().  Is /dev/null a regular file?
> > > 
> > I'm indeed using uClibc (0.9.20). /dev/null is created with "mknod 
> > null c 1 3" and "chmod 666 null". I wasn't complete in my previous 
> 
> Let's try again.  You said that it looked like /dev/null was generated
> automaticly by busybox.  I said that if /dev/null didn't exist, then
> it could be created by a uClibc call to asprintf (assuming perms).
> 
> In order to see if this was the case, I asked if the automaticly
> generated /dev/null was a regular file.  Is it?
> 
I'm sorry, yes it is:

brw-rw----    1 root     root      93,   4 Jul 28 17:42 nftla4
-rw-rw-rw-    1 root     root            0 Jul 28 17:42 null
crw-rw----    1 root     root      10, 144 Jul 28 17:42 nvram

> If so, then the fix is for me to finally redo uClibc's fopencookie()
> function so that it does not open /dev/null.
> 
> Manuel
> 

Eric