From: Pavel Machek <pavel@suse.cz>
To: Steven Whitehouse <swhiteho@redhat.com>
Cc: Andrew Morton <akpm@osdl.org>, linux-kernel@vger.kernel.org
Subject: Re: GFS2 Filesystem [13/16]
Date: Wed, 22 Feb 2006 18:50:59 +0000 [thread overview]
Message-ID: <20060222185059.GC2633@ucw.cz> (raw)
In-Reply-To: <1140793524.6400.734.camel@quoit.chygwyn.com>
Hi!
> Documentation/filesystems/gfs2.txt | 44 +++++++++++++++++++++++++++++++++++
> fs/Kconfig | 6 ++--
> fs/Makefile | 2 +
> fs/gfs2/Kconfig | 46 +++++++++++++++++++++++++++++++++++++
> fs/gfs2/Makefile | 42 +++++++++++++++++++++++++++++++++
> 5 files changed, 137 insertions(+), 3 deletions(-)
>
> --- a/fs/Kconfig
> +++ b/fs/Kconfig
> @@ -883,8 +884,6 @@ config CONFIGFS_FS
> Both sysfs and configfs can and should exist together on the
> same system. One is not a replacement for the other.
>
> - If unsure, say N.
> -
Why? Most users probably still want configfs_fs=N.
> @@ -1327,7 +1326,7 @@ config UFS_FS
>
> config UFS_FS_WRITE
> bool "UFS file system write support (DANGEROUS)"
> - depends on UFS_FS && EXPERIMENTAL
> + depends on UFS_FS && EXPERIMENTAL && BROKEN
> help
Well, maybe, but I thought this is gfs2 patch...
> +To use gfs as a local file system, no external clustering systems are
> +needed, simply:
> +
> + $ mkfs -t gfs2 -p lock_nolock -j 1 /dev/block_device
> + $ mount -t gfs2 /dev/block_device /dir
> +
> +GFS2 is not on-disk compatible with previous versions of GFS.
> +
> +The following man pages can be found at the URL above:
> + gfs2_mkfs to make a filesystem
I thought conventional name would be mkfs.gfs2 ... could you use that
variant?
Pavel
--
Thanks, Sharp!
next prev parent reply other threads:[~2006-02-24 22:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-24 15:05 GFS2 Filesystem [13/16] Steven Whitehouse
2006-02-22 18:50 ` Pavel Machek [this message]
2006-02-24 22:30 ` Joel Becker
2006-02-27 8:58 ` Steven Whitehouse
2006-02-27 8:46 ` Steven Whitehouse
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060222185059.GC2633@ucw.cz \
--to=pavel@suse.cz \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=swhiteho@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox