linux-hotplug.vger.kernel.org archive mirror
 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: Sat, 02 Jul 2005 19:37:40 +0000	[thread overview]
Message-ID: <20050702193740.GC7277@vrfy.org> (raw)
In-Reply-To: <20050702012817.46255.qmail@web30214.mail.mud.yahoo.com>

On Sat, Jul 02, 2005 at 12:06:46PM -0700, Greg KH wrote:
> On Sat, Jul 02, 2005 at 08:55:42AM -0700, Greg KH wrote:
> > On Fri, Jul 01, 2005 at 07:46:48PM -0700, Greg KH wrote:
> > > On Fri, Jul 01, 2005 at 06:28:16PM -0700, Phil K wrote:
> > > > Gentoo here, udev-059 causes the
> > > > /etc/hotplug.d/default/default.hotplug script to
> > > > complain bitterly at boot on all references to the
> > > > /dev/null device.  I am using the hotplug 2004-09-23
> > > > script set.
> > > 
> > > This is a gentoo specific issue, stick with bugs.gentoo.org for now.
> > 
> > Hm, no, this might be a udev specific issue.  I'm also now seeing this,
> > and in fact, can't get 2.6.12 to work at all with the latest udev (059).
> > Will debug more tonight...
> 
> Kay, this seems to be caused by udevstart running the
> /etc/hotplug.d/defalt/default.hotplug link (points to the "load a
> module" hotplug stuff) before we've created anything in /dev.  This is
> because of the udev_run_hotplugd program rule.  But for udevstart, we
> don't want to run any hotplug stuff :(

Sure, that's wrong.

> Hm, any hints on how to fix this loop?

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.

Cheers,
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-02 19:37 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 [this message]
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
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=20050702193740.GC7277@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 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).