From: "Peter J. Braam" <braam@clusterfilesystem.com>
To: <linux-kernel@vger.kernel.org>
Subject: Ext3 kernel RPMS (2.4.5 & 2.2.19)
Date: Fri, 8 Jun 2001 15:23:16 -0600 (MDT) [thread overview]
Message-ID: <Pine.LNX.4.33.0106081522340.1388-100000@lustre.clusterfilesystem.com> (raw)
Hi,
Mostly for my own use, I prepared two kernel RPM's with Ext3 in them.
They are totally basic: kernel + ext3 patch, config based on Red Hat
i386-smp config files. They include an RPM for e2fsprogs based on
Stephen's code.
I am running them (very) happily.
Versions:
2.2.19 + 0.0.7a
2.4.5 + 0.0.6
PLEASE USE THESE AT YOUR OWN RISK - THEY CONTAIN EXPERIMENTAL FILE SYSTEM
CODE.
The RPMS's can be found at:
ftp://ftp.clusterfilesystem.com/pub/ext3
Have a good day!
- Peter J. Braam -
http://www.clusterfilesystem.com
next reply other threads:[~2001-06-08 21:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-08 21:23 Peter J. Braam [this message]
2001-06-09 16:15 ` Ext3 kernel RPMS (2.4.5 & 2.2.19) P.A.M. van Dam
2001-06-09 16:24 ` Andrew Morton
2001-06-09 19:39 ` Peter J. Braam
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=Pine.LNX.4.33.0106081522340.1388-100000@lustre.clusterfilesystem.com \
--to=braam@clusterfilesystem.com \
--cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).