From: David Weinehall <tao@acc.umu.se>
To: "Aneesh Kumar K.V" <aneesh.kumar@hp.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
opendlm-devel@lists.sourceforge.net,
opengfs-users@lists.sourceforge.net,
opengfs-devel@lists.sourceforge.net, linux-cluster@redhat.com
Subject: Re: [ANNOUNCE] OpenSSI 1.0.0 released!!
Date: Sat, 31 Jul 2004 18:35:58 +0200 [thread overview]
Message-ID: <20040731163558.GA10689@khan.acc.umu.se> (raw)
In-Reply-To: <410B80BC.4060100@hp.com>
On Sat, Jul 31, 2004 at 04:51:32PM +0530, Aneesh Kumar K.V wrote:
> Hi,
>
> Sorry for the cross post. I came across this on OpenSSI website. I guess
> others may also be interested.
>
> -aneesh
>
> The OpenSSI project leverages both HP's NonStop Clusters for Unixware
> technology and other open source technology to provide a full, highly
> available Single System Image environment for Linux.
I can already hear SCO's lawyers screaming "They are taking technology
from UnixWare and incorporating in Linux! Let's sue them!!!"...
That said, this looks really interesting.
Regards: David Weinehall
--
/) David Weinehall <tao@acc.umu.se> /) Northern lights wander (\
// Maintainer of the v2.0 kernel // Dance across the winter sky //
\) http://www.acc.umu.se/~tao/ (/ Full colour fire (/
next prev parent reply other threads:[~2004-07-31 16:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-31 11:21 [ANNOUNCE] OpenSSI 1.0.0 released!! Aneesh Kumar K.V
2004-07-31 14:40 ` Kevin P. Fleming
2004-08-02 19:29 ` Bill Davidsen
2004-07-31 16:35 ` David Weinehall [this message]
2004-08-01 17:23 ` Daniel Phillips
[not found] <2o0e0-6qx-5@gated-at.bofh.it>
[not found] ` <m37jsk42hw.fsf@averell.firstfloor.org>
2004-08-02 6:30 ` Aneesh Kumar K.V
-- strict thread matches above, loose matches on Subject: below --
2004-08-05 7:10 Clayton Weaver
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=20040731163558.GA10689@khan.acc.umu.se \
--to=tao@acc.umu.se \
--cc=aneesh.kumar@hp.com \
--cc=linux-cluster@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=opendlm-devel@lists.sourceforge.net \
--cc=opengfs-devel@lists.sourceforge.net \
--cc=opengfs-users@lists.sourceforge.net \
/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.