![]() | |||||||||||||
Messages in this thread |
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
-
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/
| ||||||||||||
| Last update: 2006-06-19 09:17 [from the cache] ©2003-2008 | |||||||||||||