From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: udevstart vs udevsend vs /sbin/hotplug
Date: Thu, 15 Sep 2005 16:13:34 +0000 [thread overview]
Message-ID: <20050915161334.GA7562@vrfy.org> (raw)
In-Reply-To: <Pine.LNX.4.62.0509151112530.20775@www.mcquillansystems.com>
On Thu, Sep 15, 2005 at 11:42:53AM -0400, Jim McQuillan wrote:
> I'm still trying to wrap my brain around udev and all its friends.
>
> i've got an LTSP thin client booting, and i've got udev-069. As part of
> the startup process, I mount the /sys, /dev, /proc filesystems,
> and then I run /etc/start_udev, which populates my /dev tree.
>
> I've found the udev rules.d, and added some RUN commands, so I could
> watch what is happening. I've also seed udevmonitor, and it shows
> events, when I plug/unplug my USB memory stick.
>
> But, device nodes don't get created. If I then do this:
>
> modprobe sd_mod
> modprobe usb-storage
>
> Then, the device nodes are all created.
>
> So, I know that udev is doing its thing.
>
> What I can't figure out is where the hotplug scripts fit in.
>
> I read Greg's article on LWN (http://lwn.net/Articles/123932/).
> Great article btw. It helped me understand alot about the process of
> hotplugging. I really could have used that article last year, when we
> did our first hotplug system for LTSP.
>
> I was understanding just fine, until I got to the 2nd-to-last paragraph.
> It says to use '/sbin/udevstart' in /proc/sys/kernel/hotplug. BUT,
> udevstart looks like it should only be run once, at system startup.
Right. it's udevsend. Greg, can you fix the article?
> I'm thinking /sbin/udevsend it the correct thing to handle hotplug
> events, but I can't see how (or even if) it interfaces with the hotplug
> scripts.
Older udev versions handled /etc/hotplug.d/ internally, with newer versions
you need to plug it in as rules. Look at the distro rules in the udev tree for
MODALIAS and RUN keys with modprobe. If you want to stick with /etc/hotplug.d/,
look at the RELEASE-NOTES for udev 059.
Kay
-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server. Download
it for free - -and be entered to win a 42" plasma tv or your very own
Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php
_______________________________________________
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-09-15 16:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-15 15:42 udevstart vs udevsend vs /sbin/hotplug Jim McQuillan
2005-09-15 16:13 ` Kay Sievers [this message]
2005-09-15 16:48 ` Jim McQuillan
2005-09-15 17:52 ` Greg KH
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=20050915161334.GA7562@vrfy.org \
--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).