linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kay Sievers <kay.sievers@vrfy.org>
To: Greg KH <greg@kroah.com>
Cc: Martin Schlemmer <azarah@nosferatu.za.org>,
	linux-hotplug-devel@lists.sourceforge.net,
	Linux Kernel Mailing Lists <linux-kernel@vger.kernel.org>
Subject: Re: [ANNOUNCE] udev 016 release
Date: Wed, 04 Feb 2004 00:01:17 +0000	[thread overview]
Message-ID: <20040204000117.GA31071@vrfy.org> (raw)
In-Reply-To: <20040203231341.GA22058@kroah.com>

On Tue, Feb 03, 2004 at 03:13:41PM -0800, Greg KH wrote:
> On Wed, Feb 04, 2004 at 01:03:33AM +0200, Martin Schlemmer wrote:
> > On Tue, 2004-02-03 at 23:28, Martin Schlemmer wrote:
> > > On Tue, 2004-02-03 at 22:13, Greg KH wrote:
> > > 
> > > Except if I miss something major, udevsend and udevd still do not
> > > work:
> > > 
> > 
> > Skip that, it does work if SEQNUM is set :P
> > 
> > Anyhow, is it _really_ needed for SEQNUM to be set?  What about
> > the attached patch?
> 
> Yes it is necessary, as that is what the kernel spits out.  It's also
> the whole reason we need udevd :)
> 
> If you don't want to give a SEQNUM, just call udev directly.

Oh, never use this udevsend in any script. It expects the SEQNUM from
the kernel, not a random one from you! You will always get timeouts
everytime you use your own SEQNUM, like the timeout after the start of udevd.

If you really need udevsend, I can't imagine for what case, we need to
add some logic to it, to bypass the event ordering and waiting to put
the event straight to the exec_queue.


> > 2) events gets missing.  If you for example use udevsend in the
> > initscript that populate /dev (/udev), the amount of nodes/links
> > created is off with about 10-50 (once about 250) entries.

Your are calling udevsend with your script?

> Hm, that's not good.  I'll go test that and see what's happening.


thanks,
Kay


-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
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

  reply	other threads:[~2004-02-04  0:01 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-03 20:13 [ANNOUNCE] udev 016 release Greg KH
2004-02-03 21:30 ` Marco d'Itri
2004-02-03 22:23 ` Eric Sandall
2004-02-03 22:46 ` Greg KH
     [not found] ` <1075843712.7473.60.camel@nosferatu.lan>
     [not found]   ` <1075849413.11322.6.camel@nosferatu.lan>
2004-02-03 23:13     ` Greg KH
2004-02-04  0:01       ` Kay Sievers [this message]
     [not found] ` <1075841390.7473.57.camel@nosferatu.lan>
2004-02-03 23:14   ` Greg KH
2004-02-03 23:33 ` Eric Sandall
2004-02-03 23:53 ` Greg KH
2004-02-04  0:35 ` Eric Sandall
2004-02-04 22:31 ` Greg KH
     [not found] ` <1075844602.7473.75.camel@nosferatu.lan>
2004-02-11 22:13   ` Greg KH
     [not found]     ` <1076538429.22542.12.camel@nosferatu.lan>
2004-02-12  1:19       ` Greg KH

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=20040204000117.GA31071@vrfy.org \
    --to=kay.sievers@vrfy.org \
    --cc=azarah@nosferatu.za.org \
    --cc=greg@kroah.com \
    --cc=linux-hotplug-devel@lists.sourceforge.net \
    --cc=linux-kernel@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).