From: Rich Turner <rich@storix.com>
To: linux-hotplug@vger.kernel.org
Subject: udevstart v udevtrigger
Date: Thu, 13 Jul 2006 20:59:37 +0000 [thread overview]
Message-ID: <200607131359.39003.rich@storix.com> (raw)
i am doing some testing with SLES10_GMC and have noticed that there is no
longer a udevstart command. or i should say that SLES10 does not include the
udevstart command. it looks for the most part that where udevstart used to be
used udevtrigger is now being used.
i now see from the changelog that udev and udevstart programs are no longer
part of the base install.
what is the difference between udevstart and udevtrigger?
if i have the udev command and i run udevtrigger would i expect the same
results as running udevstart while having the udev command (assuming that
udevd is not running)?
is there any reason that i can not use the udevtrigger command everywhere i
used to use udevstart? my thoughts are that i will create a link
(udevstart->udevtrigger) if i have the udevtrigger command and not the
udevstart command.
-------------------------------------------------------------------------
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\x120709&bid&3057&dat\x121642
_______________________________________________
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 reply other threads:[~2006-07-13 20:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-13 20:59 Rich Turner [this message]
2006-07-13 21:29 ` udevstart v udevtrigger Greg KH
2006-07-13 22:06 ` Rich Turner
2006-07-13 22:21 ` Greg KH
2006-07-13 23:59 ` Kay Sievers
2006-07-14 16:49 ` Rich Turner
2006-07-14 17:09 ` Andrey Borzenkov
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=200607131359.39003.rich@storix.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.