From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: determining udev running
Date: Wed, 15 Dec 2004 19:52:19 +0000 [thread overview]
Message-ID: <1103140340.14134.105.camel@localhost.localdomain> (raw)
In-Reply-To: <1103138473.4055.28.camel@rich>
On Wed, 2004-12-15 at 11:44 -0800, rich turner wrote:
> although that may be how udev was designed, it appears fc3 does not
> follow that standard. there is not a /dev/.udev file.
There is no such standard. You can specify the location in the udev.conf
file. But be aware that newer udev versions use that value to create a
directory and not a single file.
> # ls -la /dev/.udev*
> -rw-r--r-- 1 root root 163840 Dec 15 03:27 /dev/.udev.tdb
>
> would the best way be to determine if /dev is mounted on tmpfs?
> does anyone else use /dev on tmpfs?
Allmost all users of udev use tmpfs. If /dev is on tmpfs and you find a
db file/directory at the specified location, you can assume that udev
maintains the directory.
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
next prev parent reply other threads:[~2004-12-15 19:52 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 [this message]
2004-12-15 22:50 ` rich turner
2004-12-15 23:21 ` rich turner
2004-12-15 23:36 ` Kay Sievers
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=1103140340.14134.105.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).