From: Mike Waychison <Michael.Waychison@Sun.COM>
To: Jamie Lokier <jamie@shareable.org>
Cc: "Adam J. Richter" <adam@yggdrasil.com>,
hbryan@us.ibm.com, linux-fsdevel@vger.kernel.org
Subject: Re: DEVFS_FS
Date: Tue, 16 Nov 2004 14:48:34 -0500 [thread overview]
Message-ID: <419A5992.3000507@sun.com> (raw)
In-Reply-To: <20041116192647.GA19365@mail.shareable.org>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Jamie Lokier wrote:
> Mike Waychison wrote:
>>In fact, the opposite is true: userspace should not care at all about
>>major/minor. Userspace should care about the semantics of the available
>>device nodes available in /dev. With hardware, I want to _see_ the
>>device nodes created when I _add_ hardware. udev handles this semantic
>>very well. Where it fails is solely in the added devfs semantic of
>>modprobing on lookups of non-existing device nodes. _This_ is the case
>>where some form of trapping would help very much.
>
>
> I agree, this is desirable behaviour. But it isn't perfect.
>
> Better than trapping would be if /dev/net/tun0 and so forth did
> actually exist in /dev, to indicate the availability of those devices,
> but the modules were still autoloaded on first access.
That would be cool. :)
>
> It would also be nicer if the device nodes were created to indicate
> available/installed devices, without actually initialising the devices
> or loading the bulk of their driver until they're needed.
>
> In other words, if /dev were auto-generated based on all available
> hardware and all available non-hardware drivers for the current
> kernel, including modules not yet loaded.
>
> That would be better IMNSHO, to the extent that it's possible.
>
> Although it's necessary to load drivers for some devices (like ISA
> cards) to detect them, it isn't necessary to load PCI drivers to
> detect that they are present. A mapping directly from detected PCI
> ids to whatever udev needs could be extracted from the drivers at
> compile time. Such mappings nearly exist now, except that the mapping
> is from ids to drivers, instead of ids to dev info.
The problem is that you do need to load the drivers for devices to see
any attached hardware.
For instance, consider the case where you boot of ide, but have an
attached scsi card. There is no way for you to know what is behind that
scsi card until you load the drivers :(
- --
Mike Waychison
Sun Microsystems, Inc.
1 (650) 352-5299 voice
1 (416) 202-8336 voice
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
NOTICE: The opinions expressed in this email are held by me,
and may not represent the views of Sun Microsystems, Inc.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFBmlmSdQs4kOxk3/MRAsXfAJ4iUpCaZxw/3AwvwU/177PzMgZrCwCgkP67
Q/Arb34MO3Z7t0p67hD9v4I=
=lxp3
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2004-11-16 19:48 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-16 6:09 DEVFS_FS Adam J. Richter
2004-11-16 19:08 ` DEVFS_FS Mike Waychison
2004-11-16 19:26 ` DEVFS_FS Jamie Lokier
2004-11-16 19:42 ` DEVFS_FS Greg KH
2004-11-16 19:48 ` Mike Waychison [this message]
2004-11-17 18:19 ` DEVFS_FS Bryan Henderson
2004-11-17 18:28 ` DEVFS_FS Jamie Lokier
2004-11-16 19:47 ` DEVFS_FS Bryan Henderson
-- strict thread matches above, loose matches on Subject: below --
2004-11-13 16:29 DEVFS_FS Adam J. Richter
2004-11-15 19:35 ` DEVFS_FS Bryan Henderson
2004-11-11 19:53 DEVFS_FS Adam J. Richter
2004-11-11 23:00 ` DEVFS_FS Bryan Henderson
2004-11-12 5:55 ` DEVFS_FS Jamie Lokier
2004-11-12 18:50 ` DEVFS_FS Bryan Henderson
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=419A5992.3000507@sun.com \
--to=michael.waychison@sun.com \
--cc=adam@yggdrasil.com \
--cc=hbryan@us.ibm.com \
--cc=jamie@shareable.org \
--cc=linux-fsdevel@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).