From: Helge Hafting <helgehaf@aitel.hist.no>
To: Greg KH <greg@kroah.com>
Cc: linux-hotplug-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: udev and devfs - The final word
Date: Sat, 03 Jan 2004 15:22:41 +0000 [thread overview]
Message-ID: <20040103152241.GA5531@hh.idb.hist.no> (raw)
In-Reply-To: <20040103055938.GD5306@kroah.com>
On Fri, Jan 02, 2004 at 09:59:38PM -0800, Greg KH wrote:
> On Thu, Jan 01, 2004 at 02:18:55AM +0100, Helge Hafting wrote:
> > On Tue, Dec 30, 2003 at 04:29:42PM -0800, Greg KH wrote:
> > >
> > > 2) We are (well, were) running out of major and minor numbers for
> > > devices.
> >
> > devfs tried to fix this one by _getting rid_ of those numbers.
> > Seriously - what are they needed for?
>
> But devfs failed in this. The devfs kernel interface still requires a
> major/minor number to create device nodes.
>
Yes. The numbers went unused in the common case of opening a device by name though.
> Hopefully I can work on fixing this up in 2.7.
Interesting - how do you plan to do this?
There must be some connection from device node to driver. Devfs had
a pointer in the inode. The old way has numbers, and spend time on
a search.
Are you considering a sort of "minimal devfs" managed by udev?
Helge Hafting
-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills. Sign up for IBM's
Free Linux Tutorials. Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id\x1278&alloc_id371&op=click
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next prev parent reply other threads:[~2004-01-03 15:22 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-31 0:29 udev and devfs - The final word Greg KH
2003-12-31 0:46 ` Johannes Erdfelt
2003-12-31 0:53 ` Prakash K. Cheemplavam
2003-12-31 19:17 ` Greg KH
2004-01-02 16:45 ` Shawn
2004-01-01 1:18 ` Helge Hafting
2004-01-03 5:59 ` Greg KH
2004-01-03 15:22 ` Helge Hafting [this message]
2004-01-03 21:18 ` viro
2004-01-03 22:11 ` Greg KH
[not found] ` <20040103140140.3b848e9f.witukind@nsbm.kicks-ass.org>
2004-01-03 22:16 ` Greg KH
2004-01-03 22:33 ` Christoph Hellwig
2004-03-29 15:38 ` Shawn
2004-03-29 15:39 ` Greg KH
2004-03-29 15:40 ` Helge Hafting
2004-03-29 15:40 ` Greg KH
2004-03-29 15:40 ` Greg KH
2004-03-29 15:40 ` viro
2004-03-29 15:40 ` Christoph Hellwig
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20040103152241.GA5531@hh.idb.hist.no \
--to=helgehaf@aitel.hist.no \
--cc=greg@kroah.com \
--cc=linux-hotplug-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).