enable wds sta interface splitting by default

[openwrt.git] / package / busybox / config / util-linux / Config.in

diff --git a/package/busybox/config/util-linux/Config.in b/package/busybox/config/util-linux/Config.in
index 0f219d7..a7e4467 100644 (file)
--- a/package/busybox/config/util-linux/Config.in
+++ b/package/busybox/config/util-linux/Config.in
@@ -127,7 +127,7 @@ config BUSYBOX_CONFIG_FEATURE_SGI_LABEL
 config BUSYBOX_CONFIG_FEATURE_SUN_LABEL
        bool "Support SUN disklabels"
        default n
-       depends on BUSYBOX_CONFIG_FDISK && BUSYBOX_CONFIG_FEATURE_FDISK_WRITABLE
+       depends on BUSYBOX_CONFIG_FDISK && BUSYBOX_CONFIG_FEATURE_FDISK_WRITABLE
        help
          Enabling this option allows you to create or change SUN disklabels.
          Most people can safely leave this option disabled.
@@ -181,7 +181,7 @@ config BUSYBOX_CONFIG_MKFS_MINIX
          this utility will do the job for you.
 
 comment "Minix filesystem support"
-    depends on BUSYBOX_CONFIG_FSCK_MINIX || BUSYBOX_CONFIG_MKFS_MINIX
+       depends on BUSYBOX_CONFIG_FSCK_MINIX || BUSYBOX_CONFIG_MKFS_MINIX
 
 config BUSYBOX_CONFIG_FEATURE_MINIX2
        bool "Support Minix fs v2 (fsck_minix/mkfs_minix)"
@@ -212,7 +212,7 @@ config BUSYBOX_CONFIG_HEXDUMP
 
 config BUSYBOX_CONFIG_HWCLOCK
        bool "hwclock"
-       default n
+       default y
        help
          The hwclock utility is used to read and set the hardware clock
          on a system.  This is primarily used to set the current time on
@@ -267,48 +267,43 @@ config BUSYBOX_CONFIG_LOSETUP
 
 config BUSYBOX_CONFIG_MDEV
        bool "mdev"
-       default y
+       default n
        help
-         mdev is a mini-udev implementation: call it with -s to populate
-         /dev from /sys, then "echo /sbin/mdev > /proc/sys/kernel/hotplug" to
-         have it handle hotplug events afterwards.  Device names are taken
-         from sysfs.
+         mdev is a mini-udev implementation for dynamically creating device
+         nodes in the /dev directory.
+
+         For more information, please see docs/mdev.txt
 
 config BUSYBOX_CONFIG_FEATURE_MDEV_CONF
        bool "Support /etc/mdev.conf"
-       default y
+       default n
        depends on BUSYBOX_CONFIG_MDEV
        help
-         The mdev config file contains lines that look like:
-
-           hd[a-z][0-9]* 0:3 660
+         Add support for the mdev config file to control ownership and
+         permissions of the device nodes.
 
-         That's device name (with regex match), uid:gid, and permissions.
-
-         Config file parsing stops on the first matching line.  If no config
-         entry is matched, devices are created with default 0:0 660.  (Make
-         the last line match .* to override this.)
+         For more information, please see docs/mdev.txt
 
 config BUSYBOX_CONFIG_FEATURE_MDEV_EXEC
        bool "Support command execution at device addition/removal"
        default n
        depends on BUSYBOX_CONFIG_FEATURE_MDEV_CONF
        help
-         This adds support for an optional field to /etc/mdev.conf, consisting
-         of a special character and a command line to run after creating the
-         corresponding device(s) and before removing, ala:
-
-           hdc root:cdrom 660  *ln -s $MDEV cdrom
+         This adds support for an optional field to /etc/mdev.conf for
+         executing commands when devices are created/removed.
 
-         The $MDEV environment variable is set to the name of the device.
+         For more information, please see docs/mdev.txt
 
-         The special characters and their meanings are:
-           @ Run after creating the device.
-           $ Run before removing the device.
-           * Run both after creating and before removing the device.
+config BUSYBOX_CONFIG_FEATURE_MDEV_LOAD_FIRMWARE
+       bool "Support loading of firmwares"
+       default n
+       depends on BUSYBOX_CONFIG_MDEV
+       help
+         Some devices need to load firmware before they can be usable.
 
-         Commands are executed via system() so you need /bin/sh, meaning you
-         probably want to select a default shell in the Shells menu.
+         These devices will request userspace look up the files in
+         /lib/firmware/ and if it exists, send it to the kernel for
+         loading into the hardware.
 
 config BUSYBOX_CONFIG_MKSWAP
        bool "mkswap"
@@ -365,11 +360,21 @@ config BUSYBOX_CONFIG_MOUNT
          NFS filesystems.  Most people using BusyBox will also want to enable
          the 'mount' utility.
 
+config BUSYBOX_CONFIG_FEATURE_MOUNT_HELPERS
+       bool "Support mount helpers"
+       default n
+       depends on BUSYBOX_CONFIG_MOUNT
+       help
+         Enable mounting of virtual file systems via external helpers.
+         E.g. mount obexfs#-b00.11.22.33.44.55 /mnt will in effect call
+         obexfs -b00.11.22.33.44.55 /mnt
+         The idea is to use such virtual filesystems in /etc/fstab
+
 config BUSYBOX_CONFIG_FEATURE_MOUNT_NFS
        bool "Support mounting NFS file systems"
        default y
        depends on BUSYBOX_CONFIG_MOUNT
-       depends on BUSYBOX_CONFIG_FEATURE_HAVE_RPC
+       select BUSYBOX_CONFIG_FEATURE_HAVE_RPC
        select BUSYBOX_CONFIG_FEATURE_SYSLOG
        help
          Enable mounting of NFS file systems.
@@ -495,7 +500,7 @@ config BUSYBOX_CONFIG_FEATURE_MOUNT_LOOP
          The umount command will also free that loopback device.
 
          You can still use the 'losetup' utility (to manually associate files
-          with loop devices) if you need to do something advanced, such as
+         with loop devices) if you need to do something advanced, such as
          specify an offset or cryptographic options to the loopback device.
          (If you don't want umount to free the loop device, use "umount -D".)