> On Sat, Jun 19, 1999 at 06:44:11PM -0400, Horst von Brand wrote:
> > Nathan Hand <nathanh@chirp.com.au> said:
> > > On Thu, Jun 17, 1999 at 12:49:47PM -0400, Horst von Brand wrote:
> > > >
> > > > By whom/how are permissions handled? Even if it's symlinks, the original
> > > > files in /devfs have to carry them (you can't follow symplinks to files you
> > > > can't access directly!). And that means the kernel has to know how to set
> > > > up permissions for a new device when it appears, and remember the settings
> > > > from one boot to the next. Gross. And a kludged initscript that sets them
> > > > up on each boot is even worse. As bad as the much-maligned MAKEDEV, but run
> > > > _each_ boot, so much more critical.>> >
> > > I would like a devfs mounted on /dev which does nothing except report node
> > > accesses that ENODEV to devfsd.
> >
> > kmod + modprobe are doing fine, thanks.
>
> These tools do not (and can not) insert modules based on attempts to open
> non-existent device nodes, so I fail to see how they do fine. You've just
> thrown away one of the best features of the virtual /dev.
devfs + kmod + modprobe DO load modules for nonexistant device nodes,
read /usr/src/linux/Documentation/filesystems/devfs/*
especially /usr/src/linux/Documentation/filesystems/devfs/modules.conf
-- David Balazic , student E-mail : 1stein@writeme.com | living in sLOVEnija home page: http://surf.to/stein Computer: Amiga 1200 + Quantum LPS-340AT--- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/