From: Roy Marples <uberlord@gentoo.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: Cold plug starting services too soon
Date: Thu, 19 Jan 2006 18:11:55 +0000 [thread overview]
Message-ID: <200601191811.59494.uberlord@gentoo.org> (raw)
In-Reply-To: <20060117203244.GA3135@kroah.com>
[-- Attachment #1: Type: text/plain, Size: 992 bytes --]
On Thursday 19 January 2006 18:04, Greg KH wrote:
> On Thu, Jan 19, 2006 at 05:54:18PM +0000, Roy Marples wrote:
> > On Thursday 19 January 2006 03:45, Greg KH wrote:
> > > Hm, we might be able to mess around with this some, but why not just
> > > create a temporary file when we start udev, which the rc scripts can
> > > check? When the initial udev startup is done (or whenever you want
> > > it), the file can be removed. That should be a lot simpler, right?
> >
> > Yes it would, but all disks are mounted read only at this point - the
> > checking and mounting happens during sysinit. At this point we can create
> > temporary files, but udev is already active and doing its thing.
>
> In our ramfs/tmpfs? Why can't we use that, as we know we can write
> there :)
Is there any guarantee that user has ramfs/tmpfs compiled into kernel?
If so, where would we mount? /lib/rcscripts/sysinit ?
Thanks
--
Roy Marples <uberlord@gentoo.org>
Gentoo Linux Developer
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2006-01-19 18:11 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
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 [this message]
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=200601191811.59494.uberlord@gentoo.org \
--to=uberlord@gentoo.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).