Hi, Now in the GFS2 -nmw git tree. Thanks,
Steve. On Tue, 2007-01-30 at 14:30 -0800, Randy Dunlap wrote: > From: Randy Dunlap <[EMAIL PROTECTED]> > > Indent help text as expected. > > Signed-off-by: Randy Dunlap <[EMAIL PROTECTED]> > --- > fs/dlm/Kconfig | 16 ++++++++-------- > fs/gfs2/Kconfig | 47 +++++++++++++++++++++++------------------------ > 2 files changed, 31 insertions(+), 32 deletions(-) > > --- linux-2620-rc6.orig/fs/dlm/Kconfig > +++ linux-2620-rc6/fs/dlm/Kconfig > @@ -7,17 +7,17 @@ config DLM > select CONFIGFS_FS > select IP_SCTP if DLM_SCTP > help > - A general purpose distributed lock manager for kernel or userspace > - applications. > + A general purpose distributed lock manager for kernel or userspace > + applications. > > choice > prompt "Select DLM communications protocol" > depends on DLM > default DLM_TCP > help > - The DLM Can use TCP or SCTP for it's network communications. > - SCTP supports multi-homed operations whereas TCP doesn't. > - However, SCTP seems to have stability problems at the moment. > + The DLM Can use TCP or SCTP for it's network communications. > + SCTP supports multi-homed operations whereas TCP doesn't. > + However, SCTP seems to have stability problems at the moment. > > config DLM_TCP > bool "TCP/IP" > @@ -31,8 +31,8 @@ config DLM_DEBUG > bool "DLM debugging" > depends on DLM > help > - Under the debugfs mount point, the name of each lockspace will > - appear as a file in the "dlm" directory. The output is the > - list of resource and locks the local node knows about. > + Under the debugfs mount point, the name of each lockspace will > + appear as a file in the "dlm" directory. The output is the > + list of resource and locks the local node knows about. > > endmenu > --- linux-2620-rc6.orig/fs/gfs2/Kconfig > +++ linux-2620-rc6/fs/gfs2/Kconfig > @@ -4,33 +4,33 @@ config GFS2_FS > select FS_POSIX_ACL > select CRC32 > help > - A cluster filesystem. > + 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 > - be found here: http://sources.redhat.com/cluster > + 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 > + be found here: http://sources.redhat.com/cluster > > config GFS2_FS_LOCKING_NOLOCK > tristate "GFS2 \"nolock\" locking module" > depends on GFS2_FS > help > - Single node locking module for GFS2. > + Single node locking module for GFS2. > > - Use this module if you want to use GFS2 on a single node without > - its clustering features. You can still take advantage of the > - large file support, and upgrade to running a full cluster later on > - if required. > + Use this module if you want to use GFS2 on a single node without > + its clustering features. You can still take advantage of the > + large file support, and upgrade to running a full cluster later on > + if required. > > - If you will only be using GFS2 in cluster mode, you do not need this > - module. > + If you will only be using GFS2 in cluster mode, you do not need this > + module. > > config GFS2_FS_LOCKING_DLM > tristate "GFS2 DLM locking module" > @@ -39,9 +39,8 @@ config GFS2_FS_LOCKING_DLM > select CONFIGFS_FS > select DLM > help > - Multiple node locking module for GFS2 > - > - Most users of GFS2 will require this module. It provides the locking > - interface between GFS2 and the DLM, which is required to use GFS2 > - in a cluster environment. > + Multiple node locking module for GFS2 > > + Most users of GFS2 will require this module. It provides the locking > + interface between GFS2 and the DLM, which is required to use GFS2 > + in a cluster environment. - To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
