aboutsummaryrefslogtreecommitdiffstats
path: root/fs/gfs2/Kconfig
diff options
context:
space:
mode:
authorSteven Whitehouse <swhiteho@redhat.com>2006-04-24 14:14:42 -0400
committerSteven Whitehouse <swhiteho@redhat.com>2006-04-24 14:14:42 -0400
commitb5ea3e1ef307548bdd40fff6aba5fc96b002f284 (patch)
tree9e6872147f473cea11086758e4a70f29655eb276 /fs/gfs2/Kconfig
parentb800a1cb3940f216c4e5c963007a1f72fca0f15f (diff)
downloadkernel_samsung_aries-b5ea3e1ef307548bdd40fff6aba5fc96b002f284.zip
kernel_samsung_aries-b5ea3e1ef307548bdd40fff6aba5fc96b002f284.tar.gz
kernel_samsung_aries-b5ea3e1ef307548bdd40fff6aba5fc96b002f284.tar.bz2
[GFS2] Tidy up Makefile & Kconfig
Remove select of SYSFS as requested by Greg KH. Change whitespace to tabs rather than spaces in places where it was incorrect and removed 'default m' as suggested by Adrian Bunk. Reorganised Makefile as suggested by Sam Ravnborg. Cc: Sam Ravnborg <sam@ravnborg.org> Cc: Adrian Bunk <bunk@stusta.de> Cc: Greg KH <greg@kroah.com> Signed-off-by: Steven Whitehouse <swhiteho@redhat.com>
Diffstat (limited to 'fs/gfs2/Kconfig')
-rw-r--r--fs/gfs2/Kconfig26
1 files changed, 12 insertions, 14 deletions
diff --git a/fs/gfs2/Kconfig b/fs/gfs2/Kconfig
index 17cb44b..115f30d 100644
--- a/fs/gfs2/Kconfig
+++ b/fs/gfs2/Kconfig
@@ -1,19 +1,17 @@
config GFS2_FS
- tristate "GFS2 file system support"
- default m
+ tristate "GFS2 file system support"
depends on EXPERIMENTAL
- select FS_POSIX_ACL
- select SYSFS
- help
- A cluster filesystem.
-
- Allows a cluster of computers to simultaneously use a block device
- that is shared between them (with FC, iSCSI, NBD, etc...). GFS reads
- and writes to the block device like a local filesystem, but also uses
- a lock module to allow the computers coordinate their I/O so
- filesystem consistency is maintained. One of the nifty features of
- GFS is perfect consistency -- changes made to the filesystem on one
- machine show up immediately on all other machines in the cluster.
+ select FS_POSIX_ACL
+ help
+ A cluster filesystem.
+
+ Allows a cluster of computers to simultaneously use a block device
+ that is shared between them (with FC, iSCSI, NBD, etc...). GFS reads
+ and writes to the block device like a local filesystem, but also uses
+ a lock module to allow the computers coordinate their I/O so
+ filesystem consistency is maintained. One of the nifty features of
+ GFS is perfect consistency -- changes made to the filesystem on one
+ machine show up immediately on all other machines in the cluster.
To use the GFS2 filesystem, you will need to enable one or more of
the below locking modules. Documentation and utilities for GFS2 can