From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: Assumptions in start_udev regarding the loop device
Date: Thu, 10 Feb 2005 08:03:17 +0000 [thread overview]
Message-ID: <1108022597.4867.5.camel@localhost.localdomain> (raw)
In-Reply-To: <1108016718.4753.86.camel@lh4.linush.net>
On Thu, 2005-02-10 at 01:25 -0500, C. Linus Hicks wrote:
> Okay, so as I was investigating the problem I am having and whether or
> not it might be fixed in the latest version of udev, I am faced with the
> fact that the issue I see is actually because of alterations Red Hat has
> made. The thing is, I would guess they made the specific change I have a
> problem with because of a perceived shortcoming of udev.
Why do we need to create these nodes with a script? Loop-devices are
in /sys/block/loop* and udevstart should create all of them.
If the modules is loaded later, the hotplug events should create all of
the nodes.
Kay
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_ide95&alloc_id\x14396&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:[~2005-02-10 8:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-10 6:25 Assumptions in start_udev regarding the loop device C. Linus Hicks
2005-02-10 8:03 ` Kay Sievers [this message]
2005-02-10 9:09 ` Marco d'Itri
2005-02-10 15:40 ` Harald Hoyer
2005-02-11 16:46 ` C. Linus Hicks
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=1108022597.4867.5.camel@localhost.localdomain \
--to=kay.sievers@vrfy.org \
--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).