From: Brian J. Murrell <Brian.Murrell@Sun.COM>
To: lustre-devel@lists.lustre.org
Subject: [Lustre-devel] moving /proc to $MNT/.lustre
Date: Mon, 07 Jan 2008 13:10:36 -0500 [thread overview]
Message-ID: <1199729436.23325.65.camel@pc.ilinx> (raw)
In-Reply-To: <4782665E.1070406@sun.com>
On Mon, 2008-01-07 at 09:50 -0800, Nathan Rutman wrote:
> well, that's why I asked. As I said, Andreas and I are in agreement,
> and it certainly makes sense from a portability point of view, as well
> as consistency with future features (snapshots, audit logs, etc.), and
> the final elimination of our various /proc locking headaches. But yes,
> it would break user's scripts - that's a 1-time thing, and I think not
> too terrible.
Is it possible to support both for a release or two to give people time
to migrate and have an actual implementation to test against as they
work to port their scripts? The alternative is that given that we don't
provide public beta binaries or nightly snapshot binaries, we'd be
requiring people who want to port, test and release their ports on "flag
day" to build from CVS to test.
b.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
URL: <http://lists.lustre.org/pipermail/lustre-devel-lustre.org/attachments/20080107/c1d2062b/attachment.pgp>
next prev parent reply other threads:[~2008-01-07 18:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <47618E96.3080709@sun.com>
2008-01-07 4:04 ` [Lustre-devel] moving /proc to $MNT/.lustre Peter Bojanic
2008-01-07 17:50 ` Nathan Rutman
2008-01-07 18:10 ` Alex Zhuravlev
2008-01-07 18:10 ` Brian J. Murrell [this message]
2008-01-07 20:07 ` Andreas Dilger
2008-01-08 3:39 ` Oleg Drokin
2008-01-08 6:48 ` Andreas Dilger
2008-01-08 6:53 ` Alex Zhuravlev
2008-01-09 3:57 ` Nathan Rutman
2008-01-14 20:54 ` Alex Zhuravlev
2008-01-08 12:31 ` Nicholas Henke
2008-01-09 4:01 ` Nathan Rutman
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=1199729436.23325.65.camel@pc.ilinx \
--to=brian.murrell@sun.com \
--cc=lustre-devel@lists.lustre.org \
/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.