From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: [PATCH] optical_gen
Date: Fri, 18 Aug 2006 23:04:36 +0000 [thread overview]
Message-ID: <1155942276.3333.151.camel@pim.off.vrfy.org> (raw)
In-Reply-To: <d5a13c80608141051w3b3e6dabwb6d58dd11b3ba7be@mail.gmail.com>
On Fri, 2006-08-18 at 20:37 +0200, Marco d'Itri wrote:
> On Aug 18, Kay Sievers <kay.sievers@vrfy.org> wrote:
>
> > > 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.
> > Does it detach from the event process? Otherwise how do you manage that
> Yes.
Ok, fine.
> > Hmm, it's not 'a few seconds later' it's after localfs is done and all
> > system filesystem can expected to be available. That still sounds like a
> > sane approach and handles far more failure cases, cause of weird system
> > setups.
> This looks a bit like fixing the effects and not the causes of bugs.
Yeah, but the real bug is /usr not on the rootfs, or tools in udev rules
that use stuff in /usr. Unfortunately, people don't want me to fix this
'bug'. :)
Care to post an as much as possible stand-alone solution from the Debian
script for the cdrom rules, so we all can start to look at it for a
possible integration into the udev tree? If that works well, we can
continue with the network stuff ...
Thanks,
Kay
-------------------------------------------------------------------------
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 23:04 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
2006-08-18 18:00 ` Kay Sievers
2006-08-18 18:37 ` Marco d'Itri
2006-08-18 23:04 ` Kay Sievers [this message]
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=1155942276.3333.151.camel@pim.off.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.