From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: Migrating from static /dev to udev
Date: Sat, 26 Sep 2009 15:41:22 +0000 [thread overview]
Message-ID: <20090926154122.GB4307@kroah.com> (raw)
In-Reply-To: <4ABD467F.7010901@broadcom.com>
On Sat, Sep 26, 2009 at 01:06:27AM +0200, Stephan Raue wrote:
> Hi,
>
> when you only need a automatically managed /dev (and not need udev) you can
> try the first snapshots of the new 2.6.32 kernel with enabled devtmpfs. i
> have tryed this yesterday (linux-2.6.31 +patch
> http://www.kernel.org/pub/linux/kernel/v2.6/next/patch-v2.6.31-next-20090925.bz2)
> and its works very good for me. you can mount /dev with "mount -t devtmpfs
> none /dev" and you have a complete /dev managed by kernel (when you need
> udev and it works, udev is very fast with this).
Or you can have the kernel mount it for you if you want to based on the
config option, making your userspace even simpler.
thanks,
greg k-h
next prev parent reply other threads:[~2009-09-26 15:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-25 22:38 Migrating from static /dev to udev Brendan Moran
2009-09-25 23:06 ` Stephan Raue
2009-09-26 9:22 ` Alan Jenkins
2009-09-26 15:41 ` Greg KH [this message]
2009-09-28 16:09 ` Brendan Moran
2009-09-28 21:02 ` Alan Jenkins
2009-09-29 17:41 ` Brendan Moran
2009-09-30 3:19 ` Bryan Kadzban
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=20090926154122.GB4307@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).