linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Phillips <phillips@redhat.com>
To: linux-kernel <linux-kernel@vger.kernel.org>
Cc: linux-fsdevel@vger.kernel.org, dcl_discussion@lists.osdl.org,
	linux-ha@new.community.tummy.com, linux-cluster@redhat.com,
	ssic-linux-devel@lists.sourceforge.net
Subject: [ANNOUNCE] Linux Cluster Infrastructure BOF at Linux Kongress
Date: Wed, 1 Sep 2004 14:37:47 -0400	[thread overview]
Message-ID: <200409011437.48032.phillips@redhat.com> (raw)

There will be a Linux Cluster Infrastructure BOF at Linux Kongress in 
Erlangen, Germany, thursday 2004-09-09 or friday 2004-09-10.  The exact 
day, time and room number to be posted here:

    http://www.linux-kongress.org/2004/program.html

This will be round three of the Linux cluster infrastructure community 
effort.  Rounds one and two were at OLS and Minneapolis, respectively.  
A summary of the latter is available here:

    http://sources.redhat.com/cluster/events/summit2004/presentations.html

The story so far: We all agree that the time has come to establish a 
kernel infrastructure for cluster filesystems, which will also be 
useable by user space applications.  Or at least, most of us agree 
about that.  At Minneapolis we parted on the understanding that we 
would all read code and find out why (or why not) the GFS kernel 
support infrastructure can serve the needs of cluster systems beyond 
GFS, including other cluster filesystems, user space cluster 
applications, and the Single System Image project.

    http://sources.redhat.com/cluster/

Last time, Red Hat engineers outnumbered Suse engineers by roughly ten 
to one.  The Linux Kongress BOF therefore presents an opportunity to 
redress that imbalance.

Regards,

Daniel

--
Linux-cluster mailing list
Linux-cluster@redhat.com
http://www.redhat.com/mailman/listinfo/linux-cluster

                 reply	other threads:[~2004-09-01 18:37 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=200409011437.48032.phillips@redhat.com \
    --to=phillips@redhat.com \
    --cc=dcl_discussion@lists.osdl.org \
    --cc=linux-cluster@redhat.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-ha@new.community.tummy.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ssic-linux-devel@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 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).