From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: netdev-dev.d? + udevsend-wait-for-udev?
Date: Sat, 27 Mar 2004 01:26:15 +0000 [thread overview]
Message-ID: <20040327012615.GC1425@vrfy.org> (raw)
In-Reply-To: <20040327005928.GA1425@vrfy.org>
On Fri, Mar 26, 2004 at 05:05:33PM -0800, Greg KH wrote:
> On Sat, Mar 27, 2004 at 01:59:28AM +0100, Kay Sievers wrote:
> > I need the net device names in the udev database, for managing the rules
> > with the gui. Before I send the patch, do we want to raise the dev.d/
> > events for net devices too?
>
> Sure, it makes sense to.
Fine, then we will have the netdev's in the selection list soon :)
> > I have a patch pending for udevsend which waits for the real udev to
> > come back and let udevsend exit with the return code of the real udev.
> > It is possible with it, to resubmit the event if we receive a recoverable
> > error from udev. Don't know if it's useful.
>
> I think I lost the last version you sent me of this. I still don't feel
> it's necessary, and possibly dangerous if we have a heavy system load,
> right?
It's not really dangerous and it doesn't take longer for hundreds of
debug disks.
udevsend will just wait a bit longer than udevs timout for a event and
then quit, also without the "ack message".
Hmm, it's nice style to let the caller know what happened, but are
there any cases you can think of, where we have a error and want to
retry? Hmm, ... :)
thanks,
Kay
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id\x1470&alloc_id638&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
next prev parent reply other threads:[~2004-03-27 1:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-27 0:59 netdev-dev.d? + udevsend-wait-for-udev? Kay Sievers
2004-03-27 1:05 ` Greg KH
2004-03-27 1:26 ` Kay Sievers [this message]
2004-03-27 1:33 ` Greg KH
2004-03-27 1:42 ` Kay Sievers
2004-03-27 8:58 ` Marco d'Itri
2004-03-27 11:12 ` Kay Sievers
2004-03-27 11:37 ` 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=20040327012615.GC1425@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).