From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: udev sees everything
Date: Sat, 25 Dec 2004 03:21:59 +0000 [thread overview]
Message-ID: <1103944919.5805.14.camel@localhost.localdomain> (raw)
In-Reply-To: <41CCD4B6.8090709@snapafun.co.nz>
On Sat, 2004-12-25 at 15:47 +1300, SnapafunFrank wrote:
> I wish to make contact with the members here for two things.
>
> 1). To help me put things right
You may look here first:
http://www.kernel.org/pub/linux/utils/kernel/hotplug/udev.html
http://www.redhat.com/magazine/002dec04/features/udev/
> 2). To help me learn enough so as to put up a user friendly ( read raw
> newbie ) Howto
Maybe it's better to improve an existing one, than to create a new one.
You may look at:
http://www.reactivated.net/udevrules.php
http://webpages.charter.net/decibelshelp/LinuxHelp_UDEVPrimer.html
> If it is permitted here [ if not please point me in the correct
> direction ] then would someone help me understand why it is that upon a
> reboot - udev sees everything?
What do you mean with "sees everything"? That udev creates all the nodes
at reboot?
The kernel exports device informations to the sysfs mounted at /sys. If
a device is created, a hotplug event is generated, that may lead udev to
create a node.
> I have followed the instructions as per
> http://www.tldp.org/HOWTO/Flash-Memory-HOWTO/linux-2.6.html and things
> were doing as they ought when I issued # ls /udev but the reboot seems
> to have messed things up.
The userspace hotplug environment is not available directly at bootup,
so the hotplug events can not create some of the nodes. The udevstart
program covers that hole. You need to run it after every reboot and it
will create a node for every device the kernel makes the necessary
information available.
Good luck,
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://productguide.itmanagersjournal.com/
_______________________________________________
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
prev parent reply other threads:[~2004-12-25 3:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-25 2:47 udev sees everything SnapafunFrank
2004-12-25 3:21 ` Kay Sievers [this message]
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=1103944919.5805.14.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