On Tue, Apr 13, 2010 at 03:40:24PM +0300, Antti Kantee wrote:
> On Tue Apr 13 2010 at 12:32:38 +0000, Andrew Doran wrote:
> > So the kernel of the problem is namespace collisions, correct?
> 
> Mostly.  Though I still think it's not expected that opening a /dev
> node will load e.g. an exec package or secmodel even if that's what some
> programmer wants.
> 
> > Would you agree that's it's the kernel programmers responsibility
> > to avoid conflicts?
> > 
> > If so how about sprinkling a little process in order to make it harder to
> > screw up?
> 
> I'd say computers do conflict detection better.

So the result of our teeth-pulling so far is:

1. You are concerned about namespace conflicts.  I am too.
2. I would be happy to see these managed through documentation and
   a straightforward approval process for adding modules.
3. You suggest that it would be better for the computer to manage it.

Can you suggest an alternative mechanism that will (a) allow us to
autoload things that are not anointed device drivers and (b) satisfy
your concerns?

As an example of something that wants autoloading both as a file
system and a driver, see ZFS.

Reply via email to