From: rich turner <rich@storix.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: determining udev running
Date: Wed, 15 Dec 2004 23:21:42 +0000 [thread overview]
Message-ID: <1103152901.4055.68.camel@rich> (raw)
In-Reply-To: <1103138473.4055.28.camel@rich>
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
2. there is a file /dev/.udev.tdb
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?
On Wed, 2004-12-15 at 14:50, rich turner wrote:
> On Wed, 2004-12-15 at 11:51, Marco d'Itri wrote:
> > On Dec 15, Kay Sievers <kay.sievers@vrfy.org> wrote:
> >
> > > You may check for a symlink to udevsend in /etc/hotplug.d/default/
> > This will not work if udev is not active (e.g. because the init script
> > detected a 2.4 kernel or was manually disabled).
>
> but i think this is what i need to know, if udev is active. or better
> yet, i only want to know whether a system booted with udev, or populated
> the /dev directory using udev.
>
> isnt there anything i can check to see that udev was used to populate
> /dev?
>
>
>
> -------------------------------------------------------
> 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
-------------------------------------------------------
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 23:21 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 [this message]
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=1103152901.4055.68.camel@rich \
--to=rich@storix.com \
--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).