From: md@Linux.IT (Marco d'Itri)
To: linux-hotplug@vger.kernel.org
Subject: Re: Cold plug starting services too soon
Date: Tue, 17 Jan 2006 20:50:48 +0000 [thread overview]
Message-ID: <20060117205048.GB16165@wonderland.linux.it> (raw)
In-Reply-To: <20060117203244.GA3135@kroah.com>
[-- Attachment #1: Type: text/plain, Size: 914 bytes --]
On Jan 17, Greg KH <greg@kroah.com> wrote:
> Gentoo has run into the problem that if we load modules for some types
> of devices (like network devices for example), we can generate hotplug
> events that want to run things on disks that are not mounted yet, as we
> havn't even done mounting of the non-root filesystem yet (caused by udev
> doing the coldplug pretty much the first thing at boot time.)
>
> How has Debian and SuSE kept from having this issue? I think for SuSE
On Debian, packages which install RUN rules must either not care if
events happening before /usr is mounted are lost or if appropriate
use scripts which wait until whatever is needed is available (e.g. the
SUBSYSTEM=="net" agent waits for the lo interface to be up).
I am not sure if I want to replay failed events, because we don't know
why they failed and so far it's not clear if this is needed.
--
ciao,
Marco
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2006-01-17 20:50 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-17 20:32 Cold plug starting services too soon Greg KH
2006-01-17 20:34 ` Greg KH
2006-01-17 20:43 ` Kay Sievers
2006-01-17 20:50 ` Marco d'Itri [this message]
2006-01-18 0:27 ` Greg KH
2006-01-18 9:28 ` Roy Marples
2006-01-19 3:45 ` Greg KH
2006-01-19 17:54 ` Roy Marples
2006-01-19 18:04 ` Greg KH
2006-01-19 18:11 ` Roy Marples
2006-01-19 18:19 ` Greg KH
2006-01-19 18:35 ` Roy Marples
2006-01-20 0:09 ` 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=20060117205048.GB16165@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).