aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorBernhard Reutner-Fischer <rep.dot.nop@gmail.com>2008-05-16 11:36:32 +0000
committerBernhard Reutner-Fischer <rep.dot.nop@gmail.com>2008-05-16 11:36:32 +0000
commit9c3052aab6d14bc950a4f41af2d693f2d5d91c32 (patch)
tree7a7f4e0c463127b8890e793ff1ad42d8e091ce75
parent81e97a13801eb0cc3887d1696208629e5dda77b5 (diff)
downloadbusybox-w32-9c3052aab6d14bc950a4f41af2d693f2d5d91c32.tar.gz
busybox-w32-9c3052aab6d14bc950a4f41af2d693f2d5d91c32.tar.bz2
busybox-w32-9c3052aab6d14bc950a4f41af2d693f2d5d91c32.zip
- provide proc-less sample
- improve wording
-rw-r--r--docs/mdev.txt12
1 files changed, 9 insertions, 3 deletions
diff --git a/docs/mdev.txt b/docs/mdev.txt
index 38f1da964..1a97be4ce 100644
--- a/docs/mdev.txt
+++ b/docs/mdev.txt
@@ -15,13 +15,20 @@ require sysfs support in the kernel and have it mounted at /sys. For dynamic
15updates, you also need to have hotplugging enabled in your kernel. 15updates, you also need to have hotplugging enabled in your kernel.
16 16
17Here's a typical code snippet from the init script: 17Here's a typical code snippet from the init script:
18[0] mount -t proc proc /proc
18[1] mount -t sysfs sysfs /sys 19[1] mount -t sysfs sysfs /sys
19[2] echo /bin/mdev > /proc/sys/kernel/hotplug 20[2] echo /bin/mdev > /proc/sys/kernel/hotplug
20[3] mdev -s 21[3] mdev -s
21 22
23Alternatively, without procfs the above becomes:
24[1] mount -t sysfs sysfs /sys
25[2] sysctl -w kernel.hotplug=/bin/mdev
26[3] mdev -s
27
28
22Of course, a more "full" setup would entail executing this before the previous 29Of course, a more "full" setup would entail executing this before the previous
23code snippet: 30code snippet:
24[4] mount -t tmpfs mdev /dev 31[4] mount -t tmpfs -o size=64k,mode=0755 tmpfs /dev
25[5] mkdir /dev/pts 32[5] mkdir /dev/pts
26[6] mount -t devpts devpts /dev/pts 33[6] mount -t devpts devpts /dev/pts
27 34
@@ -87,5 +94,4 @@ properly initialize a device. Place all such firmware files into the
87/lib/firmware/ directory. At runtime, the kernel will invoke mdev with the 94/lib/firmware/ directory. At runtime, the kernel will invoke mdev with the
88filename of the firmware which mdev will load out of /lib/firmware/ and into 95filename of the firmware which mdev will load out of /lib/firmware/ and into
89the kernel via the sysfs interface. The exact filename is hardcoded in the 96the kernel via the sysfs interface. The exact filename is hardcoded in the
90kernel, so look there if you need to want to know what to name the file in 97kernel, so look there if you need to know how to name the file in userspace.
91userspace.