From: md@Linux.IT (Marco d'Itri)
To: linux-hotplug@vger.kernel.org
Subject: Re: [PATCH] optical_gen
Date: Fri, 18 Aug 2006 17:22:32 +0000 [thread overview]
Message-ID: <20060818172231.GA23820@wonderland.linux.it> (raw)
In-Reply-To: <d5a13c80608141051w3b3e6dabwb6d58dd11b3ba7be@mail.gmail.com>
On Aug 18, Kay Sievers <kay.sievers@vrfy.org> wrote:
> > Scripts fork and wait in the background until they can continue.
> > I still do not like the idea of restarting all failed events without
> > knowing why they failed.
> Oh, but that works only for stuff that is trying to be directly executed
> by udev, but isn't there, right? A script or tool that fails cause it
> uses something that isn't reachable at that point, will never be tried
> again, right?
No, the few packages which need stuff in /usr have scripts which wait
for some event (tipically the presence of /dev/log) before continuing.
I provided a function to do this and so far it has worked well.
> > > The generic 'retrigger' to create the rules later, when /etc is writable
> > > sounds much easier than having a special boot script logic for that
> > > special case.
> > Looks simple enough to me: :-)
> Yeah, it's simple, especially in the case you don't handle failed events
> at all. :)
The idea is that events should not fail depending on when they are
received, so there retriggering failed events a few seconds later would
have no effect.
> Ah, that is also doing that for the network stuff?
Yes, and anything else we have not implemented yet (some people are
still waiting for persistent sound devices).
--
ciao,
Marco
-------------------------------------------------------------------------
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-08-18 17:22 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-14 17:51 [PATCH] optical_gen VMiklos
2006-08-14 22:58 ` Greg KH
2006-08-14 23:30 ` Kay Sievers
2006-08-15 18:12 ` VMiklos
2006-08-15 18:32 ` Marco d'Itri
2006-08-15 19:06 ` VMiklos
2006-08-15 19:08 ` Marco d'Itri
2006-08-15 19:22 ` VMiklos
2006-08-16 6:52 ` Olivier Blin
2006-08-16 8:50 ` Marco d'Itri
2006-08-16 15:49 ` Andrey Borzenkov
2006-08-17 12:43 ` VMiklos
2006-08-17 12:52 ` Alexander E. Patrakov
2006-08-17 13:25 ` Piter PUNK
2006-08-18 15:41 ` Kay Sievers
2006-08-18 17:02 ` Marco d'Itri
2006-08-18 17:13 ` Kay Sievers
2006-08-18 17:22 ` Marco d'Itri [this message]
2006-08-18 18:00 ` Kay Sievers
2006-08-18 18:37 ` Marco d'Itri
2006-08-18 23:04 ` Kay Sievers
2006-08-23 10:56 ` VMiklos
2006-08-23 11:40 ` Marco d'Itri
2006-09-01 18:17 ` VMiklos
2006-09-05 13:32 ` Kay Sievers
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=20060818172231.GA23820@wonderland.linux.it \
--to=md@linux.it \
--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).