svn commit: trunk/busybox/docs

aldot at busybox.net aldot at busybox.net
Fri May 16 11:36:33 UTC 2008


Author: aldot
Date: 2008-05-16 04:36:32 -0700 (Fri, 16 May 2008)
New Revision: 21986

Log:
- provide proc-less sample
- improve wording


Modified:
   trunk/busybox/docs/mdev.txt


Changeset:
Modified: trunk/busybox/docs/mdev.txt
===================================================================
--- trunk/busybox/docs/mdev.txt	2008-05-15 22:43:48 UTC (rev 21985)
+++ trunk/busybox/docs/mdev.txt	2008-05-16 11:36:32 UTC (rev 21986)
@@ -15,13 +15,20 @@
 updates, you also need to have hotplugging enabled in your kernel.
 
 Here's a typical code snippet from the init script:
+[0] mount -t proc proc /proc
 [1] mount -t sysfs sysfs /sys
 [2] echo /bin/mdev > /proc/sys/kernel/hotplug
 [3] mdev -s
 
+Alternatively, without procfs the above becomes:
+[1] mount -t sysfs sysfs /sys
+[2] sysctl -w kernel.hotplug=/bin/mdev
+[3] mdev -s
+
+
 Of course, a more "full" setup would entail executing this before the previous
 code snippet:
-[4] mount -t tmpfs mdev /dev
+[4] mount -t tmpfs -o size=64k,mode=0755 tmpfs /dev
 [5] mkdir /dev/pts
 [6] mount -t devpts devpts /dev/pts
 
@@ -87,5 +94,4 @@
 /lib/firmware/ directory.  At runtime, the kernel will invoke mdev with the
 filename of the firmware which mdev will load out of /lib/firmware/ and into
 the kernel via the sysfs interface.  The exact filename is hardcoded in the
-kernel, so look there if you need to want to know what to name the file in
-userspace.
+kernel, so look there if you need to know how to name the file in userspace.




More information about the busybox-cvs mailing list