From: Lars Marowsky-Bree <lmb@suse.de>
To: "J. Ryan Earl" <ryan@dynaconnections.com>, miele@inwind.it
Cc: jakob <jakob@unthought.net>,
linux-raid <linux-raid@vger.kernel.org>,
mingo <mingo@chiara.csoma.elte.hu>, bueso <bueso@vives.org>
Subject: Re: Can you help me on Linux SW RAID?
Date: Thu, 28 Apr 2005 21:56:10 +0200 [thread overview]
Message-ID: <20050428195610.GO21645@marowsky-bree.de> (raw)
In-Reply-To: <OMEKLMBKKEOEENCKLEIDAEPDCIAA.ryan@dynaconnections.com>
On 2005-04-28T14:18:28, "J. Ryan Earl" <ryan@dynaconnections.com> wrote:
> OCFS2 isn't stable yet, I wouldn't suggest its use for production systems.
> Furthermore, where did the requirement for 2.6 (kernel I assume) come from?
> Sounds like he was using RHEL3 anyway...
That wasn't mentioned in the mail I replied to; anyone deploying a new
2.4 based system right now is a bit behind the times in my opinion, I
hope 2.4 goes away soon ;-)
OCFS2 is already included in SLES9 SP2 beta; we'll ship it for
production use with SLES9 SP2 general availability.
Sincerely,
Lars Marowsky-Brée <lmb@suse.de>
--
High Availability & Clustering
SUSE Labs, Research and Development
SUSE LINUX Products GmbH - A Novell Business
-
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2005-04-28 19:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-28 12:57 Can you help me on Linux SW RAID? miele
2005-04-28 13:06 ` Lars Marowsky-Bree
2005-04-28 19:18 ` J. Ryan Earl
2005-04-28 19:56 ` Lars Marowsky-Bree [this message]
2005-04-28 22:32 ` Can you help me on Linux SW RAID? [OT] J. Ryan Earl
-- strict thread matches above, loose matches on Subject: below --
2005-04-28 11:41 Can you help me on Linux SW RAID? miele
2005-04-28 11:49 ` Lars Marowsky-Bree
2005-04-28 10:27 miele
2005-04-28 10:11 miele
2005-04-28 11:29 ` Jakob Oestergaard
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=20050428195610.GO21645@marowsky-bree.de \
--to=lmb@suse.de \
--cc=bueso@vives.org \
--cc=jakob@unthought.net \
--cc=linux-raid@vger.kernel.org \
--cc=miele@inwind.it \
--cc=mingo@chiara.csoma.elte.hu \
--cc=ryan@dynaconnections.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;
as well as URLs for NNTP newsgroup(s).