Russell Coker writes:
> On Fri, 9 Nov 2001 23:15, Richard Gooch wrote:
> > Russell Coker writes:
> > > Currently on boot I see the following messages from devfsd:
> > > error lstat(2)ing: "stdin" No such file or directory
> > > error lstat(2)ing: "stdout" No such file or directory
> > > error lstat(2)ing: "stderr" No such file or directory
> > >
> > > Where are these links created? Why are they created in the early
> > > boot process? Why not just have devfsd create them (or one of the
> > > boot scripts)?
> >
> > Those links are created by devfsd (as is "fd") early in it's
> > initialisation phase. But the message is wrong, it's a call to stat(2)
> > that is failing, not lstat(2). I don't get these messages.
> >
> > Hm. Is /proc mounted at this time?
>
> No. On Debian devfs is started before the "checkroot" script (which
> mounts /proc).
>
> I'm looking into getting this changed.
Well, this shouldn't be necessary. I've already fixed the message to
reflect that it's stat(2) that's failing and not lstat(2). I'm
considering making the PERMISSIONS action ignore symlinks. Right now,
you can change permissions by going through a symlink. That would no
longer be possible. For example:
REGISTER discs/disc.*/disc PERMISSIONS 0.0 rw-r-----
would no longer change the permissions of all whole-disc
entries. However, you could get the same effect with:
REGISTER .*/disc PERMISSIONS 0.0 rw-r-----
since no non-disc driver should create a "disc" leaf node. Otherwise,
you'd need something like:
REGISTER scsi/.*/disc PERMISSIONS 0.0 rw-r-----
REGISTER ide/.*/disc PERMISSIONS 0.0 rw-r-----
Comments?
BTW: what config line do you have that wants to change the permissions
of "stdin", "stdout" and "stderr" anyway?
Regards,
Richard....
Permanent: rgooch@xxxxxxxxxxxxx
Current: rgooch@xxxxxxxxxxxxxxx
|