From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: the file system for /dev
Date: Sun, 31 Jul 2011 18:05:44 +0000 [thread overview]
Message-ID: <20110731180544.GA12063@kroah.com> (raw)
In-Reply-To: <20110731163116.GA24315@linux1>
On Sun, Jul 31, 2011 at 11:31:16AM -0500, William Hubbs wrote:
> All,
>
> The setup section of the udev README mentions that /dev should get the
> devtmpfs file system, but it also says that udev can be run on a blank
> tmpfs as long as you create /dev/{null,kmsg,console}. Also, the
> requirements section never mentions CONFIG_DEVTMPFS.
>
> So, I guess I'm attempting to figure out what is preferred. Is devtmpfs
> preferred for distros?
Yes.
> What are reasons that someone might not want to use devtmpfs with
> udev?
They don't want to use it? I don't know, why not ask the distros that
don't use it why they don't want it.
good luck,
greg k-h
next prev parent reply other threads:[~2011-07-31 18:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-31 16:31 the file system for /dev William Hubbs
2011-07-31 18:05 ` Greg KH [this message]
2011-07-31 21:47 ` 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=20110731180544.GA12063@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).