From: Manish Singh <manish.singh@oracle.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [PATCH] ocfs2 support for blkid utility
Date: Tue Feb 3 23:36:22 2004 [thread overview]
Message-ID: <20040204053617.GA12219@ca-server1.us.oracle.com> (raw)
In-Reply-To: <200402040448.i144mMld031531@penguin.co.intel.com>
On Tue, Feb 03, 2004 at 08:48:22PM -0800, Rusty Lynch wrote:
> So... I downloaded the e2fsprog source tree and hacked the following
> patch that adds ocfs2 support.
>
> In the probe_ocfs() function, buf contains the first kbytes of data
> from the disk, and I just grab the label, suggested mount point, and
> UUID by indexing into buf.
>
> Some of the other probe functions define their super block structure
> in an e2fsprog header file, and then just cast buf to their own
> super block. Since ocfs2 structures are considerably more complex,
> I just went with the offset method.
It'd be cleaner to declare a couple structs in probe.h and use then in
probe.c, similar to what I did for mount in:
http://oss.oracle.com/projects/ocfs/src/trunk/patches/mountocfslabel.diff
Using offsets directly is rather cryptic.
> This code would totally break if ocfs2 changes the layout of the first
> kbyte on disk. Are there any plans to change this?
No changes are planned, since one goal is to maintain on-disk compatibility
with ocfs1 as much as possible.
> Would anyone have a problem with me submitting this to the e2fsprogs
> project?
Fine by me, if you take my suggestion above. ;)
-Manish
prev parent reply other threads:[~2004-02-03 23:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-03 22:48 [Ocfs2-devel] [PATCH] ocfs2 support for blkid utility Rusty Lynch
2004-02-03 22:52 ` Wim Coekaerts
2004-02-03 23:36 ` Manish Singh [this message]
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=20040204053617.GA12219@ca-server1.us.oracle.com \
--to=manish.singh@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.