From: Mark Fasheh <mark.fasheh@oracle.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [RFC] to make files of ocfs2 under sysfs canonical
Date: Fri Dec 7 00:54:22 2007 [thread overview]
Message-ID: <20071207085416.GS28607@ca-server1.us.oracle.com> (raw)
In-Reply-To: <91b13c310712062321u7ffe7f9dqbe228d6995ce79e@mail.gmail.com>
On Fri, Dec 07, 2007 at 03:21:20PM +0800, rae l wrote:
> > The bigger problem is that there are tools expecting /sys/o2cb to be
> > there. We can't just drop it.
> Do you mean the ocfs2-tools? We could also change it. Or any other tools?
>
> The kernel community doesn't promise a stable kernel API, so does the sysfs,
> Except If it would break many userspace tools, we should consider with
> caution or keep the binary compatibility,
It would break ocfs2-tools, majorly. mount.ocfs2, fsck.ocfs2, tunefs.ocfs2,
mkfs.ocfs2, o2cb_ctl are just the programs which I can think of off the top
of my head which look for o2cb/interface_revision. Basically anything that
needs to interact with the cluster uses that file at least once.
So sorry, but shuffling it around would make many Ocfs2 users very, very
unhappy.
--Mark
--
Mark Fasheh
Senior Software Developer, Oracle
mark.fasheh@oracle.com
next prev parent reply other threads:[~2007-12-07 0:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-06 20:20 [Ocfs2-devel] [RFC] to make files of ocfs2 under sysfs canonical Denis Cheng
2007-12-06 21:12 ` Joel Becker
2007-12-06 23:21 ` rae l
2007-12-07 0:54 ` Mark Fasheh [this message]
2007-12-07 1:28 ` Joel Becker
2007-12-11 19:23 ` Greg KH
2007-12-11 17:02 ` rae l
2007-12-12 22:30 ` Greg KH
2007-12-12 14:54 ` Mark Fasheh
2007-12-13 0:07 ` Greg KH
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=20071207085416.GS28607@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.