From: Helge Hafting <helgehaf@aitel.hist.no>
To: Mike Bell <kernel@mikebell.org>, linux-kernel@vger.kernel.org
Subject: Re: devfs vs udev, thoughts from a devfs user
Date: Wed, 11 Feb 2004 10:44:10 +0100 [thread overview]
Message-ID: <4029F96A.6050105@aitel.hist.no> (raw)
In-Reply-To: <20040210160011.GJ4421@tinyvaio.nome.ca>
Mike Bell wrote:
> On Tue, Feb 10, 2004 at 02:20:19PM +0100, Helge Hafting wrote:
>
>>Non-devfs setups (with or without udev) support a similiar trigger
>>mechanism for module loading, that is simpler to set up and understand.
>>And that is a persistend device node. Plain, simple, and ls sees it too.
>>Open it and the device is loaded as needed. And at open time, not
>>at lookup time. Load at lookup time might not be necessary, after all.
>
>
> This doesn't work anymore if you move to dynamic device numbers, nor
Sure. Completely random device numbers will make this demand loading of
device drivers impossible. Either it won't happen (all numbers won't be
completely random, although they may get more dynamic than today) or
module loading based on device node opening will be deprecated.
This won't mean the end of dynamic loading, you will merely need to
load modules explicit before you get a device node.
> does it work cleanly if /dev is on tmpfs or something else that doesn't
> persist between reboots (that's one of the things I like about devfs,
> being able to use it with a RO root.)
Still possible. Boot script (possibly the udev startup script)
copies a handful of device nodes from the RO root into the tmpfs /dev.
Helge Hafting
next prev parent reply other threads:[~2004-02-11 9:31 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-10 11:34 devfs vs udev, thoughts from a devfs user Mike Bell
2004-02-10 13:20 ` Helge Hafting
2004-02-10 14:46 ` Mike Bell
2004-02-10 17:02 ` Mark Mielke
[not found] ` <20040210160011.GJ4421@tinyvaio.nome.ca>
2004-02-11 9:44 ` Helge Hafting [this message]
2004-02-11 20:05 ` Theodore Ts'o
2004-02-10 13:32 ` Ian Kent
2004-02-10 14:00 ` Mike Bell
2004-02-10 17:01 ` Greg KH
2004-02-10 17:13 ` Mike Bell
2004-02-10 17:25 ` Greg KH
2004-02-10 17:46 ` Mike Bell
2004-02-10 18:12 ` Greg KH
2004-02-10 18:29 ` Mike Bell
2004-02-10 22:19 ` Matthew Reppert
2004-02-11 1:10 ` Mike Bell
2004-02-11 10:05 ` Helge Hafting
2004-02-13 21:19 ` Greg KH
2004-02-14 8:51 ` Mike Bell
2004-02-14 9:13 ` Christian Borntraeger
2004-02-14 11:42 ` Helge Hafting
2004-02-14 16:54 ` Greg KH
2004-02-14 17:44 ` Alex Goddard
2004-02-15 8:16 ` Andrew Walrond
2004-02-19 9:47 ` Mike Bell
2004-02-19 19:43 ` Greg KH
2004-02-27 0:02 ` Mike Bell
2004-02-10 19:10 ` Shawn
2004-02-10 17:52 ` Chris Friesen
2004-02-10 19:24 ` Mike Bell
2004-02-10 19:46 ` Chris Friesen
2004-02-10 19:58 ` Tomasz Torcz
2004-02-10 20:11 ` Kevin P. Fleming
2004-02-10 20:39 ` Bill Rugolsky Jr.
2004-02-11 1:16 ` Greg KH
2004-02-11 1:41 ` Kevin P. Fleming
2004-02-11 9:36 ` Maneesh Soni
2004-02-11 7:50 ` viro
2004-02-11 12:33 ` Bill Rugolsky Jr.
2004-02-11 15:11 ` [PATCH] Fix /etc/mtab updating with mount --move [was Re: devfs vs udev, thoughts from a devfs user] Bill Rugolsky Jr.
2004-02-11 19:19 ` devfs vs udev, thoughts from a devfs user dleonard
2004-02-10 20:32 ` Diego Calleja García
2004-02-11 1:20 ` Mike Bell
2004-02-10 20:15 ` Timothy Miller
2004-02-10 22:24 ` Matthew Reppert
2004-02-11 1:35 ` Mike Bell
2004-02-10 20:44 ` Valdis.Kletnieks
2004-02-10 17:55 ` Mike Bell
2004-02-10 18:19 ` Greg KH
2004-02-10 18:43 ` Mike Bell
2004-02-10 20:11 ` Theodore Ts'o
2004-02-11 1:49 ` Mike Bell
2004-02-10 19:12 ` Mike Bell
2004-02-13 21:08 ` Greg KH
2004-02-10 18:35 ` Greg KH
2004-02-11 1:25 ` Ian Kent
-- strict thread matches above, loose matches on Subject: below --
2004-02-10 16:10 "Andrey Borzenkov"
[not found] <fa.i9mtr77.1pja9qf@ifi.uio.no>
[not found] ` <fa.de6p9mb.1ikipbl@ifi.uio.no>
2004-02-13 22:08 ` walt
2004-02-13 22:18 ` Greg KH
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=4029F96A.6050105@aitel.hist.no \
--to=helgehaf@aitel.hist.no \
--cc=kernel@mikebell.org \
--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