From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: Non-hardware devices like loop: another idea
Date: Thu, 18 Mar 2004 04:24:24 +0000 [thread overview]
Message-ID: <20040318042424.GA5517@kroah.com> (raw)
In-Reply-To: <200403122003.00557.patrakov@ums.usu.ru>
On Fri, Mar 12, 2004 at 08:03:00PM +0500, Alexander E. Patrakov wrote:
>
> I found my implementation rather clumsy and while implementing it I decided
> that it would be better to just mark such modules and modprobe tham all, and
> make the hotplug script modprobe other stuff. I decided to start implementing
> such mark... and found that it has already been done, so actually no patches
> are needed except for the udev initscript!
>
> I am talking about /lib/modules/<version>/modules.alias.
Take a look at a distro's modules.alias file. With your scheme you
would have them load every possible module. Not a good idea :)
Sorry,
greg k-h
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id\x1470&alloc_id638&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-03-18 4:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-12 15:03 Non-hardware devices like loop: another idea Alexander E. Patrakov
2004-03-17 1:47 ` Mike Snitzer
2004-03-17 4:13 ` Alexander E. Patrakov
2004-03-17 4:26 ` Mike Snitzer
2004-03-17 6:39 ` Alexander E. Patrakov
2004-03-17 17:01 ` Mike Snitzer
2004-03-18 3:56 ` Alexander E. Patrakov
2004-03-18 4:24 ` Greg KH [this message]
2004-03-18 4:55 ` Mike Snitzer
2004-03-18 9:55 ` Alexander E. Patrakov
2004-03-18 9:58 ` Alexander E. Patrakov
2004-03-18 10:23 ` Marco d'Itri
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=20040318042424.GA5517@kroah.com \
--to=greg@kroah.com \
--cc=linux-hotplug@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).