Driver-Core: devtmpfs - remove EXPERIMENTAL and flush out the description

All major distros enable devtmpfs on recent systems, so remove
the EXPERIMENTAL flag, and make the description a bit more instructive.

Signed-off-by: Kay Sievers <kay.sievers@vrfy.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
This commit is contained in:
Kay Sievers 2010-01-14 22:47:57 +01:00 committed by Greg Kroah-Hartman
parent 5e31d76f28
commit 4237e5fd3e

View file

@ -9,29 +9,36 @@ config UEVENT_HELPER_PATH
every uevent. every uevent.
config DEVTMPFS config DEVTMPFS
bool "Create a kernel maintained /dev tmpfs (EXPERIMENTAL)" bool "Maintain a devtmpfs filesystem to mount at /dev"
depends on HOTPLUG && SHMEM && TMPFS depends on HOTPLUG && SHMEM && TMPFS
help help
This creates a tmpfs filesystem, and mounts it at bootup This creates a tmpfs filesystem instance early at bootup.
and mounts it at /dev. The kernel driver core creates device In this filesystem, the kernel driver core maintains device
nodes for all registered devices in that filesystem. All device nodes with their default names and permissions for all
nodes are owned by root and have the default mode of 0600. registered devices with an assigned major/minor number.
Userspace can add and delete the nodes as needed. This is Userspace can modify the filesystem content as needed, add
intended to simplify bootup, and make it possible to delay symlinks, and apply needed permissions.
the initial coldplug at bootup done by udev in userspace. It provides a fully functional /dev directory, where usually
It should also provide a simpler way for rescue systems udev runs on top, managing permissions and adding meaningful
to bring up a kernel with dynamic major/minor numbers. symlinks.
Meaningful symlinks, permissions and device ownership must In very limited environments, it may provide a sufficient
still be handled by userspace. functional /dev without any further help. It also allows simple
If unsure, say N here. rescue systems, and reliably handles dynamic major/minor numbers.
config DEVTMPFS_MOUNT config DEVTMPFS_MOUNT
bool "Automount devtmpfs at /dev" bool "Automount devtmpfs at /dev, after the kernel mounted the rootfs"
depends on DEVTMPFS depends on DEVTMPFS
help help
This will mount devtmpfs at /dev if the kernel mounts the root This will instruct the kernel to automatically mount the
filesystem. It will not affect initramfs based mounting. devtmpfs filesystem at /dev, directly after the kernel has
If unsure, say N here. mounted the root filesystem. The behavior can be overridden
with the commandline parameter: devtmpfs.mount=0|1.
This option does not affect initramfs based booting, here
the devtmpfs filesystem always needs to be mounted manually
after the roots is mounted.
With this option enabled, it allows to bring up a system in
rescue mode with init=/bin/sh, even when the /dev directory
on the rootfs is completely empty.
config STANDALONE config STANDALONE
bool "Select only drivers that don't need compile-time external firmware" if EXPERIMENTAL bool "Select only drivers that don't need compile-time external firmware" if EXPERIMENTAL