From: Mark Fasheh <mark.fasheh@oracle.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [PATCH] Adding ocfs support to blkid
Date: Thu Feb 5 12:30:53 2004 [thread overview]
Message-ID: <20040205183046.GA26471@ca-server1.us.oracle.com> (raw)
In-Reply-To: <20040205001132.GA12919@penguin.co.intel.com>
Yeah, basically we haven't gotten around to it yet ;) Minor will still be
there - for ocfs2 it will be major=2, minor=0
--Mark
On Wed, Feb 04, 2004 at 04:11:32PM -0800, Rusty Lynch wrote:
> On Wed, Feb 04, 2004 at 03:31:49PM -0800, Manish Singh wrote:
> > On Wed, Feb 04, 2004 at 10:59:52AM -0800, Mark Fasheh wrote:
> > > Could we call it "ocfs" instead of "ocfs2" below? We will likely be bumping
> > > up the version number in the header for ocfs version 2 when it's released.
> >
> > Yeah, call it "ocfs" and set SEC_TYPE to "ocfs1", "ocfs2", and "ntocfs"
> > for version 1, version 2, and windows ocfs, respectively. For ocfs1 the
> > major version is 1, ocfs2 is 2, and ntocfs it's >= 9.
>
> The current ocfs2 code has major=1 and minor=2... is the increase of the
> major number just not done yet, or did you mean to switch off the minor?
>
> --rusty
--
Mark Fasheh
Software Developer, Oracle Corp
mark.fasheh@oracle.com
next prev parent reply other threads:[~2004-02-05 12:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-04 2:38 [Ocfs2-devel] [PATCH] Adding ocfs support to blkid Rusty Lynch
2004-02-04 12:59 ` Mark Fasheh
2004-02-04 17:32 ` Manish Singh
2004-02-05 1:59 ` Rusty Lynch
2004-02-05 12:30 ` Mark Fasheh [this message]
2004-02-05 4:58 ` Rusty Lynch
2004-02-05 15:49 ` Rusty Lynch
2004-02-13 16:10 ` [Ocfs2-devel] " Theodore Ts'o
2004-02-04 19:46 ` Rusty Lynch
2004-03-06 15:30 ` Theodore Ts'o
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=20040205183046.GA26471@ca-server1.us.oracle.com \
--to=mark.fasheh@oracle.com \
--cc=ocfs2-devel@oss.oracle.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.