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 17:01:25 +0000 [thread overview]
Message-ID: <20040317100125.A21012@lnxi.com> (raw)
In-Reply-To: <200403122003.00557.patrakov@ums.usu.ru>
On Tue, Mar 16 2004 at 23:39,
Alexander E. Patrakov <patrakov@ums.usu.ru> wrote:
> Now I see where the confusion comes from. You misunderstood my proposal.
> Sorry for not making it clear enough.
>
> I don't propose to parse these files at all. I want to probe the modules
> corresponding to the *-major-* aliases unconditionally. Let's review the
> scenarios for the loop module.
>
> 1) It is in the kernel. Then the /sys/block/loop0/dev file will be
> present upon boot, the udev initscript as supplied with the current
> version of udev will notice it while walking the /sys/block hierarchy,
> and /dev/loop0 will be created from the initscript.
Cool, I didn't realize this.
> 2) It is a module. Then the modified initscript will notice that there
> is a block-major line in /lib/modules/<version>/modules.alias with the
> "loop" as its third field. You suggest to create /dev/loop0 based on
> this information. I suggest to just call "modprobe loop" instead. The
> kernel will send the hotplug event and the udev program as supplied in
> the current udev package will react upon that event by creating /dev/loop0.
I wasn't suggesting anything; merely pointed out that your solution was
dependent on modules. Ultimately udev will create /dev entries as it
walks sysfs (so it takes care of /dev/loopX, etc); but there are aspects
of the kernel that aren't sysfs-ified (e.g. tun). Not to mention if the
devices don't support hotplug udev will never get triggered.
So wouldn't a better option be to make the various devices that don't
support hotplug and/or sysfs support them? Then udev just needs some new
rules. Infering information from the module load (via modules.alias) is
fragile.
Are there devices that can't and/or shouldn't be hotplug/sysfs-ified?
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 17:01 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 [this message]
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=20040317100125.A21012@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.