public inbox for gentoo-cluster@lists.gentoo.org
 help / color / mirror / Atom feed
From: "\"C. Bergström\"" <cbergstrom@netsyncro.com>
To: gentoo-cluster@lists.gentoo.org
Subject: [gentoo-cluster] Porting RH gfs-deploy-tool to Gentoo
Date: Mon, 26 Mar 2007 13:45:17 +0300	[thread overview]
Message-ID: <4607A43D.9000306@netsyncro.com> (raw)

I'm trying to really clean up my cluster deployment and while looking at 
GFS came across this.

http://people.redhat.com/rkenna/gfs-deploy-tool/html.doc/

My first thoughts are of course switching out the dependency to pull 
rpms from the rh network to PORTAGE_BINHOST.. I'm hoping to find the 
time within the next 30 days to port this to Gentoo.  If anyone is 
interested in contributing or the results let me know.  Also any 
feedback from those using GFS is most appreciated.

Cheers,

Christopher
-- 
gentoo-cluster@gentoo.org mailing list



             reply	other threads:[~2007-03-26 10:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-26 10:45 "C. Bergström" [this message]
2007-03-26 17:25 ` [gentoo-cluster] Porting RH gfs-deploy-tool to Gentoo Donnie Berkholz
2007-11-29 22:35 ` Anielkis Herrera Gonzalez

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=4607A43D.9000306@netsyncro.com \
    --to=cbergstrom@netsyncro.com \
    --cc=gentoo-cluster@lists.gentoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox