From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: determining udev running
Date: Wed, 15 Dec 2004 23:36:53 +0000 [thread overview]
Message-ID: <1103153813.14134.119.camel@localhost.localdomain> (raw)
In-Reply-To: <1103138473.4055.28.camel@rich>
On Wed, 2004-12-15 at 15:21 -0800, rich turner wrote:
> can someone shoot any holes in my logic here. how about this:
>
> we used udev to populate /dev if:
> 1. /dev is a mounted filesystem as determined by /proc/mounts
No, udev will work perfectly on any filesystem, including the root filesystem.
> 2. there is a file /dev/.udev.tdb
You need to get the filename from /etc/udev/udev.conf. But if /dev is on
a persistent filesystem, yo can't know if its from the current system,
or an earlier run.
As said in the earlier mail: If /dev is on tmpfs and you find a udevdb
at the configured location, there is a high probability that udev is
manging the /dev directory.
> is there any importance for checking for udevd? doesnt it just listen
> for new devices detected by the kernel and create the nodes if they dont
> already exist?
udevd is just an event serializer. It collect events from the kernel and
forks the udev binary in the right order.
So, there in no distribution independent way to know if udev has created
the device nodes. There is no single state, where you can get that
information. What exact problem you need to address?
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-15 23:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-15 19:21 determining udev running rich turner
2004-12-15 19:23 ` Stefan Schweizer
2004-12-15 19:30 ` Marco d'Itri
2004-12-15 19:44 ` rich turner
2004-12-15 19:49 ` Kay Sievers
2004-12-15 19:50 ` Marco d'Itri
2004-12-15 19:51 ` Marco d'Itri
2004-12-15 19:52 ` Kay Sievers
2004-12-15 22:50 ` rich turner
2004-12-15 23:21 ` rich turner
2004-12-15 23:36 ` 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=1103153813.14134.119.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).