All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: udev-059 and default.hotplug script
Date: Sun, 03 Jul 2005 10:53:17 +0000	[thread overview]
Message-ID: <20050703105317.GA29352@vrfy.org> (raw)
In-Reply-To: <20050702012817.46255.qmail@web30214.mail.mud.yahoo.com>

On Sun, Jul 03, 2005 at 12:22:42PM +0200, Marco d'Itri wrote:
> On Jul 02, Kay Sievers <kay.sievers@vrfy.org> wrote:
> 
> > I hope so:
> >   ENV{UDEVD_EVENT}="1", RUN+="/sbin/udev_run_hotplugd"
> > 
> > should prevent the hotplug stuff run, if it's not from the kernel.
> What about other RUN events? Should each one check for $UDEVD_EVENT?

There is no general rule. It depends on your setup and how you organize
things on bootup. SUSE does kernel event-replay from initramfs. udevstart
and coldplug are not used anymore.

udevstart did dev.d/ also with the old udev versions, so only the
hotplug.d/ replacement RUN rules you may disable with matching
$UDEVD_EVENT.

But it may also be possible to modify udevstart to replace coldplug.
Don't know, you may have a better view, if this is possible?

Btw:
The next major udev version will depend on kernel 2.6.12 and will support
fast node creation in the udev daemon itself. _Simple_ rules will be able to
handled by the daemon itself. That will hopefully make event-replay fast
and easy and be a better approach than udevstart and coldplug.

Thanks,
Kay



-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_idt77&alloc_id\x16492&op=click
_______________________________________________
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

  parent reply	other threads:[~2005-07-03 10:53 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-02  1:28 udev-059 and default.hotplug script Phil K
2005-07-02  2:46 ` Greg KH
2005-07-02  8:22 ` Marco d'Itri
2005-07-02 15:55 ` Greg KH
2005-07-02 15:58 ` Greg KH
2005-07-02 16:21 ` Marco d'Itri
2005-07-02 18:59 ` Stefan Schweizer
2005-07-02 19:06 ` Greg KH
2005-07-02 19:37 ` Kay Sievers
2005-07-03  7:17 ` Greg KH
2005-07-03  7:20 ` Greg KH
2005-07-03 10:22 ` Marco d'Itri
2005-07-03 10:53 ` Kay Sievers [this message]
2005-07-03 12:15 ` Marco d'Itri
2005-07-03 14:01 ` Kay Sievers
2005-07-03 16:26 ` Marco d'Itri
2005-07-03 19:46 ` Kay Sievers
2005-07-03 20:15 ` Marco d'Itri
2005-07-03 21:02 ` Kay Sievers
2005-07-05 10:28 ` Marco d'Itri
2005-07-05 11:45 ` Kay Sievers
2005-07-05 11:50 ` Marco d'Itri

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=20050703105317.GA29352@vrfy.org \
    --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 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.