[BusyBox] [PATCH] devfsd

[Allen Chan]

Tito,

Thanks for spending the time to look at my patch.  You bring up some 
good points.  I went back and recreated the problem and looked more 
carefully to figure out exactly what is happening:

(1) I misreported that the error message showed up in dmesg.  The 
"devfsd: read config file: /etc/devfsd.conf: No such file or 
directory" line only shows on the console, not in dmesg, even though 
dmesg did show much of the boot process, including those that occur 
before /sbin/devsd was called.

(2) The "/sbin/devfsd /dev" was executed very early in the boot 
process, even before syslogd and klogd, so the device /dev/log was 
not created yet.  This explains why I was previously not able to 
reproduce this problem after the boot process was complete.  I can 
now reproduce this consistently by simply not starting syslogd and 
klogd at bootup.

(3) This is obviously a non-critical problem since nothing is really 
broken, just an error message displayed when there is no error, and 
only in a very specific situation that may not be very common.  
However, it would be nice if no one else wastes any time debugging 
this fake error message in the future.

On Thursday 18 November 2004 04:39 pm, Tito wrote:
> Hi Allen,
> after taking a look at the devsfd code (I've busyboxed some time
> ago) i'm wondering how it could be possible
> with this kind of error that the symlinks are created ...
>
> By a fast look at the man pages it seems to me that the only call 
> in msg_logger able to set errno to ENOENT is acces() in which case
> /dev/log would be not accessible so how is it possible that you
> have some output in dmesg?
>

-- 
Allen Chan
allen at developers.alyz.com
http://www.alyz.com