lkml.org 
[lkml]   [1999]   [Oct]   [6]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
Date
SubjectRe: USB device allocation
In <Pine.A41.4.10.9910060106240.22786-100000@pund.acc.umu.se> David Weinehall (tao@acc.umu.se) 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?

What's more: sometimes there are just NO infrastructure in place to inform
daemon. Except of human intervention. And since I need to access (say)
/dev/printer/0 to print sometihing anyway why it can not be a trigger ?
With devfs it IS a trigger. Without devfs it CAN NOT be a trigger.




-
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/

\
 
 \ /
  Last update: 2005-03-22 13:54    [W:0.109 / U:1.204 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site