From: Mike Snitzer <msnitzer@lnxi.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: Non-hardware devices like loop: another idea
Date: Wed, 17 Mar 2004 04:26:30 +0000 [thread overview]
Message-ID: <20040316212630.A15967@lnxi.com> (raw)
In-Reply-To: <200403122003.00557.patrakov@ums.usu.ru>
On Tue, Mar 16 2004 at 21:13,
Alexander E. Patrakov <patrakov@ums.usu.ru> wrote:
> On Wednesday 17 March 2004 06:47, Mike Snitzer wrote:
> > What if you configure this options into the kernel, e.g.:
> >
> > CONFIG_BLK_DEV_LOOP=y
> > CONFIG_TUN=y
> > ... etc ...
> >
> > rather than building all non-hardware backed devices as modules? Relying
> > on them being modules seems quite restrictive.
> >
> > Mike
>
> This will also work. If you do so, then the corresponding entries will not
> appear in the "modules.alias" file.
Right; they won't appear in modules.alias and therefore your solution
won't work.
> Also, I don't completely understand you when you say that something relies
> upon these options being modules. Can you explain it more clear?
You were suggesting that modules.alias and modules.conf be parsed to
determine which non-hardware backward devices should get created by udev.
By the nature of these module related files; it implies those options be
configured as modules, no?
So I suppose what you're suggesting _could_ work (if modules) but its not
a complete solution.
Mike
-------------------------------------------------------
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-17 4:26 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 [this message]
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
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=20040316212630.A15967@lnxi.com \
--to=msnitzer@lnxi.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.