Re: [ANNOUNCE] ndevfs - a "nano" devfs

From: Dmitry Torokhov <dtor_core@ameritech.net>
To: linux-kernel@vger.kernel.org
Cc: Mike Bell <kernel@mikebell.org>, Greg KH <greg@kroah.com>
Subject: Re: [ANNOUNCE] ndevfs - a "nano" devfs
Date: Mon, 27 Jun 2005 17:35:50 -0500	[thread overview]
Message-ID: <200506271735.50565.dtor_core@ameritech.net> (raw)
In-Reply-To: <20050627071907.GA5433@mikebell.org>

On Monday 27 June 2005 02:19, Mike Bell wrote:
> On Sat, Jun 25, 2005 at 04:43:05PM -0700, Greg KH wrote:
> > So no, I'm not going to be submitting this.  But what it is, is a nice
> > proof-of-concept for people who "just can't live without a in-kernel
> > devfs" to show that it can be done in less than 300 lines of code, and
> > only 6 hooks (2 functions in 3 different places) in the main kernel
> > tree.  That is managable outside of the main kernel for years, with
> > almost little to no effort.
> 
> Except that it isn't.
> 
> The "everything in the root" model just doesn't seem to work. It's been
> so long since I used linux without devfs I hadn't thought about how
> things like ALSA and the input subsystem have gone beyond supporting
> device nodes in a subdirectory to actually requiring device nodes to be
> in a subdirectory.

AFAIK there is no requirement in input subsystem that devices should be
created under /dev/input. When devfs is activated they are created there
by default, but that's it.

-- 
Dmitry