Re: USB device allocation
H. Peter Anvin (hpa@transmeta.com)
Tue, 05 Oct 1999 16:11:55 -0700
David Weinehall wrote:
>
> On Tue, 5 Oct 1999, H. Peter Anvin wrote:
>
> > David Weinehall wrote:
> > >
> > > > That is one way of doing it; IMO a very good way because it lets you
> > > > have policy in user space.
> > >
> > > Oh? And what kind of image of how devfs does things do you have then?
> > >
> > > This is how devfs works. The kernel part of devfs informs devfsd of the
> > > changes (what devices need to be created/removed), and devfsd nicely
> > > carries out its chores. User-space policy and persistent access-rights are
> > > there for you.
> > >
> >
> > ... in which case you don't need devfs at all.
>
> And how will you inform the daemon that new devices need to be
> created/removed?
>
By a pipe or socket. Doing it via a filesystem is broken anyway, since
you need a message -- not a layout.
-hpa
--
<hpa@transmeta.com> at work, <hpa@zytor.com> in private!
-
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/