[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20090727090642.0e495919.randy.dunlap@oracle.com>
Date: Mon, 27 Jul 2009 09:06:42 -0700
From: Randy Dunlap <randy.dunlap@...cle.com>
To: lkml <linux-kernel@...r.kernel.org>
Cc: gregkh@...e.de, Lucian Adrian Grijincu <lgrijincu@...acom.com>
Subject: [PATCH] documentation: make it clear that sysfs is optional
From: Lucian Adrian Grijincu <lgrijincu@...acom.com>
Subject: [PATCH] documentation: make it clear that sysfs is optional
The original text suggested that sysfs is mandatory and always
compiled in the kernel.
Signed-off-by: Lucian Adrian Grijincu <lgrijincu@...acom.com>
Signed-off-by: Randy Dunlap <randy.dunlap@...cle.com>
---
Documentation/filesystems/sysfs.txt | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
--- linux-next-20090727.orig/Documentation/filesystems/sysfs.txt
+++ linux-next-20090727/Documentation/filesystems/sysfs.txt
@@ -23,7 +23,8 @@ interface.
Using sysfs
~~~~~~~~~~~
-sysfs is always compiled in. You can access it by doing:
+sysfs is always compiled in if CONFIG_SYSFS is defined. You can access
+it by doing:
mount -t sysfs sysfs /sys
---
~Randy
LPC 2009, Sept. 23-25, Portland, Oregon
http://linuxplumbersconf.org/2009/
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists