From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: Cold plug starting services too soon
Date: Fri, 20 Jan 2006 00:09:08 +0000 [thread overview]
Message-ID: <20060120000908.GC29106@kroah.com> (raw)
In-Reply-To: <20060117203244.GA3135@kroah.com>
On Thu, Jan 19, 2006 at 06:35:53PM +0000, Roy Marples wrote:
> On Thursday 19 January 2006 18:19, Greg KH wrote:
> > No, I mean the ramfs/tmpfs that udev uses to hold it's /dev tree and
> > database. I can provide a function that the rc scripts can call to see
> > if udev is still initializing or not to keep them from having to worry
> > about the actual mechanics.
>
> So I could touch /dev/.rcsysinit and remove that after sysinit completes?
> That works for me :)
Yup.
> > And yes, ramfs is always compiled into the kernel these days.
>
> Really?
> I see CONFIG_RAMFS=y and CONFIG_TMPFS=y in my 2.6.15 kernel config so I was
> under the impression that they're optional.
Hm, I thought that the build system always forced ramfs on, due to boot
issues, but in looking at the Kconfig system, I can't see that
dependancy anymore. So you are right.
But udev on Gentoo will not work without that, so we don't really need
to worry about this :)
thanks,
greg k-h
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid\x103432&bid#0486&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
prev parent reply other threads:[~2006-01-20 0:09 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
2006-01-19 18:19 ` Greg KH
2006-01-19 18:35 ` Roy Marples
2006-01-20 0:09 ` Greg KH [this message]
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=20060120000908.GC29106@kroah.com \
--to=greg@kroah.com \
--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).