From: Lars Marowsky-Bree <lmb@suse.de>
To: Jonathan Stanton <jonathan@cnds.jhu.edu>,
sdake@mvista.com,
Discussion of clustering software components including GFS
<linux-cluster@redhat.com>
Cc: Chris Wright <chrisw@osdl.org>,
dcl_discussion@osdl.org, cgl_discussion@osdl.org,
linux-kernel@vger.kernel.org
Subject: Re: [Linux-cluster] Re: [cgl_discussion] Re: [dcl_discussion] Clustersummit materials
Date: Fri, 13 Aug 2004 22:30:29 +0200 [thread overview]
Message-ID: <20040813203029.GW4161@marowsky-bree.de> (raw)
In-Reply-To: <20040813155441.GA16662@cnds.jhu.edu>
On 2004-08-13T11:54:41,
Jonathan Stanton <jonathan@cnds.jhu.edu> said:
> If you havn't looked at it already, you might want to try out the Spread
> group communication system.
>
> http://www.spread.org/
The intel lawyers have identified the Spread license to be
GPL-incompatible.
Otherwise, I agree, Spread is very nice. If those issues could be
resolved, that may be an interesting option too.
(I think the advertising clause and something else clash with the
(L)GPL; I can put you in contact with the Intel folks if you wish to
resolve this.)
Sincerely,
Lars Marowsky-Brée <lmb@suse.de>
--
High Availability & Clustering \ This space /
SUSE Labs, Research and Development | intentionally |
SUSE LINUX AG - A Novell company \ left blank /
next prev parent reply other threads:[~2004-08-13 20:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3689AF909D816446BA505D21F1461AE4C75110@cacexc04.americas.cpqcorp.net>
2004-08-11 18:46 ` [Linux-cluster] Re: [cgl_discussion] Re: [dcl_discussion] Clustersummit materials Steven Dake
2004-08-12 9:57 ` Lars Marowsky-Bree
2004-08-12 17:42 ` Steven Dake
2004-08-12 20:37 ` Lars Marowsky-Bree
2004-08-12 22:59 ` Steven Dake
2004-08-13 9:40 ` Lars Marowsky-Bree
2004-08-13 15:54 ` Jonathan Stanton
2004-08-13 20:30 ` Lars Marowsky-Bree [this message]
2004-08-13 22:53 ` Jonathan Stanton
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=20040813203029.GW4161@marowsky-bree.de \
--to=lmb@suse.de \
--cc=cgl_discussion@osdl.org \
--cc=chrisw@osdl.org \
--cc=dcl_discussion@osdl.org \
--cc=jonathan@cnds.jhu.edu \
--cc=linux-cluster@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sdake@mvista.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.