From: "Alexander E. Patrakov" <patrakov@ums.usu.ru>
To: linux-kernel@vger.kernel.org
Cc: Joshua Hudson <joshudson@gmail.com>, "H. Peter Anvin" <hpa@zytor.com>
Subject: Re: [GIT PATCH] Remove devfs from 2.6.17
Date: Mon, 19 Jun 2006 13:14:36 +0600 [thread overview]
Message-ID: <44964EDC.3030104@ums.usu.ru> (raw)
In-Reply-To: <8e6f94720606182255u400964c2v1ea16221ffc5c94d@mail.gmail.com>
Will Dyson wrote:
> On 6/18/06, H. Peter Anvin <hpa@zytor.com> wrote:
>> Joshua Hudson wrote:
>> > With udev, you could mknod it yourself (in your application), then
>> open it.
>> > That would fire up the auto-module-load.
>>
>> Sure, but it would be even better if pointing udev to a set of modules
>> (or perhaps a file generated by depmod) and have it do it all
>> automatically.
>
> Providing the information about what devices a virtual driver will
> register when loaded seems like a good idea.
Why? This information is currently useless. What you want is that something
knows that you want this driver to be loaded. So, everything you need is one line:
MODULE_ALIAS("virtual_dev");
(add this to loop, nbd, ppp_generic, uinput, dm-mod and other "virtual" drivers
of your choice)
and the initscript that does a "modprobe virtual_dev" to catch them all.
--
Alexander E. Patrakov
next prev parent reply other threads:[~2006-06-19 7:14 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-18 22:13 [GIT PATCH] Remove devfs from 2.6.17 Greg KH
2006-06-18 22:45 ` Michal Piotrowski
2006-06-18 23:06 ` Greg KH
2006-06-18 23:00 ` Samuel Thibault
2006-06-18 23:12 ` Greg KH
2006-06-18 23:35 ` Samuel Thibault
2006-06-19 0:48 ` Nick Piggin
2006-06-19 3:22 ` Greg KH
2006-06-19 8:23 ` Samuel Thibault
2006-06-19 9:30 ` Marcel Holtmann
2006-06-19 9:39 ` Samuel Thibault
2006-06-19 10:22 ` Marcel Holtmann
2006-06-19 0:54 ` H. Peter Anvin
2006-06-19 1:17 ` Joshua Hudson
2006-06-19 1:35 ` H. Peter Anvin
2006-06-19 5:55 ` Will Dyson
2006-06-19 7:14 ` Alexander E. Patrakov [this message]
2006-06-19 22:14 ` Daniel Barkalow
2006-06-19 22:17 ` H. Peter Anvin
2006-06-19 3:15 ` Greg KH
2006-06-19 8:52 ` Samuel Thibault
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=44964EDC.3030104@ums.usu.ru \
--to=patrakov@ums.usu.ru \
--cc=hpa@zytor.com \
--cc=joshudson@gmail.com \
--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