From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: udev and depinit
Date: Fri, 05 May 2006 21:01:29 +0000 [thread overview]
Message-ID: <20060505210129.GA7198@kroah.com> (raw)
In-Reply-To: <ced5f0f60605051136h33dd73f2ve7284b24a764338e@mail.gmail.com>
On Fri, May 05, 2006 at 07:36:16PM +0100, Luke Kenneth Casson Leighton wrote:
>
> if there was a "pull" capability whereby a udev-command could
> be run "respond to all the networking hotplug events and tell
> me when you've done that including running all the net.agent
> scripts, please" then that would be ABSOLUTELY ideal.
You can do that today, look at how udevtrigger works. Just do that for
network devices and you are done.
In short, what you are wanting to do doesn't have much at all to do with
udev, but with how your distro handles the startup logic. All udev does
is act apon the events it gets. If you don't trigger events, it doesn't
act on them.
So just trigger the events that you care about and you will be fine.
good luck,
greg k-h
-------------------------------------------------------
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 prev parent reply other threads:[~2006-05-05 21:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-05 18:36 udev and depinit Luke Kenneth Casson Leighton
2006-05-05 21:01 ` Greg KH [this message]
2006-05-06 1:59 ` Luke Kenneth Casson Leighton
2006-05-06 10:26 ` Luke Kenneth Casson Leighton
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=20060505210129.GA7198@kroah.com \
--to=greg@kroah.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).