From: Bryan Kadzban <bryan@kadzban.is-a-geek.net>
To: linux-hotplug@vger.kernel.org
Subject: Re: What does 'udevtrigger' & 'udevsettle' stand for?!
Date: Wed, 09 Aug 2006 22:29:34 +0000 [thread overview]
Message-ID: <44DA61CE.806@kadzban.is-a-geek.net> (raw)
In-Reply-To: <dad91deb0608090804t2b201c8bsa1204578cd2fce28@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1368 bytes --]
Aaron Griffin wrote:
> Yeah, but there is a fine line there. I mean, why don't all unix
> tools read from stdin only, and force 'cat' usage to read files?
Because you would do this:
whatever-prog </path/to/file
or this:
</path/to/file whatever-prog
, not this:
cat /path/to/file | whatever-prog
, and the file-reading would be done by whatever-prog, not by both cat
and whatever-prog. (whatever-prog would still have to read() from stdin
if you used a pipe; the only difference is where stdin comes from.) ;-P
(See also the "useless use of cat" page [1].)
> Neither udevtrigger nor udevsettle have any use case outside of
> initializing udevd.
If you assume that udevd starts up every time the uevent files need to
be poked, that'd be true. But I don't believe that's the case: I've
poked all the uevent files many times, while doing testing of various
udev versions and rule packages. udevd was already running; restarting
it would be a pain. (Especially if I'm currently inside a chroot, though
that doesn't usually happen.)
I'd agree that most people don't find much use in having udevtrigger be
separate, but some do. And udevsettle is used in some cases without
udevtrigger but while udevd is up (for instance, after repartitioning,
to wait for the new hdXY or sdXY devices to show up).
[1] http://laku19.adsl.netsonic.fi/~era/unix/award.html
[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 258 bytes --]
[-- Attachment #2: Type: text/plain, Size: 373 bytes --]
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
[-- Attachment #3: Type: text/plain, Size: 226 bytes --]
_______________________________________________
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:[~2006-08-09 22:29 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-09 15:04 What does 'udevtrigger' & 'udevsettle' stand for?! - -
2006-08-09 16:18 ` xandrous
2006-08-09 17:53 ` Greg KH
2006-08-09 18:02 ` Aaron Griffin
2006-08-09 19:15 ` xandrous
2006-08-09 22:29 ` Bryan Kadzban [this message]
2006-08-09 22:35 ` VMiklos
2006-08-09 23:40 ` Marco d'Itri
2006-08-10 13:03 ` xandrous
2006-08-10 13:49 ` Kay Sievers
2006-08-10 14:42 ` Aaron Griffin
2006-08-10 14:47 ` Scott James Remnant
2006-08-10 16:20 ` Greg KH
2006-08-10 17:08 ` Aaron Griffin
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=44DA61CE.806@kadzban.is-a-geek.net \
--to=bryan@kadzban.is-a-geek.net \
--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).