From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: udev-076 and /lib/udev/devices
Date: Wed, 30 Nov 2005 12:54:41 +0000 [thread overview]
Message-ID: <20051130125441.GA1011@vrfy.org> (raw)
In-Reply-To: <438D9E40.8060505@linuxfromscratch.org>
On Wed, Nov 30, 2005 at 12:42:40PM +0000, Matthew Burgess wrote:
> Hi,
>
> In the RELEASE-NOTES for udev-076, it states:
>
> "Also /lib/udev/devices is recommended as a directory where packages or
> the user can place real device nodes, which get copied over to /dev at
> every boot."
>
> This suggests that udev does this copying itself. However, in README it
> states:
>
> "The content of /lib/udev/devices directory should be copied over to the
> tmpfs mounted /dev, to provide the required nodes to initialize udev."
>
> This suggests that it is the job of a bootscript to copy the devices
> across, and a quick test/grep of the source suggests that, indeed, udev
> won't do any such copying itself.
>
> Could someone confirm this for me please?
The boot script is expected to mount tmpfs on /dev, copy the initial and
static nodes from /lib/udev/devices and then start udevd.
Kay
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_idv37&alloc_id\x16865&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
prev parent reply other threads:[~2005-11-30 12:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-30 12:42 udev-076 and /lib/udev/devices Matthew Burgess
2005-11-30 12:54 ` 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=20051130125441.GA1011@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).