Subject: Re: [QUESTION/PROPOSAL] udev (fwd)
From: Felipe Alfaro Solana <felipe_alfaro@linuxmail.org>
To: Grzegorz Kulewski <kangur@polcom.net>
Cc: linux-hotplug-devel@vger.kernel.org, greg@kroach.com,
       linux-kernel@vger.kernel.org
In-Reply-To: <Pine.LNX.4.58.0403032023090.1319@alpha.polcom.net>
References: <Pine.LNX.4.58.0403032023090.1319@alpha.polcom.net>
Content-Type: text/plain
Message-Id: <1078344278.1113.15.camel@teapot.felipe-alfaro.com>
Mime-Version: 1.0
Date: Wed, 03 Mar 2004 21:04:38 +0100
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1345
Lines: 30

On Wed, 2004-03-03 at 20:27, Grzegorz Kulewski wrote:

> If I understand well, currently, when kernel detects new device, it 
> creates all important files in /sys for it, excluding device file.
> 
> So, (sorry if it was asked 100000000 times...
> ... but) why when kernel detects new device or module is loaded, no device 
> file in sysfs is created? The device files in /dev would be only links to 
> these in /sys. 
> 
> This way we could stop care about major/minor numbers and leave it to sysfs...
> And it maybe could decrease the possible races related to udev because it 
> would only create or remove links to files in /sys.
> 
> Programs will be able to easily find, for what device and where located in 
> system (buses, etc.) the device file in /dev is - with readlink.
> 
> And it should make the entire process more clear.

This is more or less how Solaris works... In Solaris, /dev entries are
just symlinks to entries under the /devices tree which is much like
/sys: a tree-like structure which is composed of buses, devices et all.

This is a feature I've always liked from Solaris.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/