From: Eric Sandeen <sandeen@redhat.com>
To: "Theodore Ts'o" <tytso@mit.edu>
Cc: linux-ext4@vger.kernel.org
Subject: Re: Making it easier for end users to use ext4
Date: Mon, 14 Jul 2008 14:35:07 -0500 [thread overview]
Message-ID: <487BAA6B.7030001@redhat.com> (raw)
In-Reply-To: <E1KITeX-0001PV-Pv@closure.thunk.org>
Theodore Ts'o wrote:
> So I got a comment on my recent blog posting about using ext4 that
> Googling ext4 results in a lot of ancient status reports and not a lot
> of good information about how to get started with ext4. The comment was
> fair, so I took a few minutes to update this web page:
>
> http://ext4.wiki.kernel.org/index.php/Ext4_Howto
>
> with some getting started information.
>
> Eric, when you have a chance, could you take a quick peek at the Fedora
> Core section of that page and update it appropriately.
Sure, first I'll remove "core" since that terminology doesn't exist
anymore ;)
> It would
> probably be a good idea to include the yum repository with the latest
> 1.41 e2fsprogs RPM's, etc. One other thought is if we start encouraging
> people to use ext4 on FC9, whether it might be a good idea to take all
> of the patches to ext4 since 2.6.25, add them to the patch queue, and
> then back port the resulting stack of patches to 2.6.25 so that FC9
> users who are interested in testing ext4 would get the benefit of the
> latest ext4 code, and also so any bug reports we get would also be
> against the latest code.
well, left to its own devices, F9 will see 2.6.26 at least as a testing
kernel pretty soon I think. Waiting for that seems reasonable vs. the
above patch gyrations....
> Alternatively, the repository could just
> simply include 2.6.26 plus the latest ext4 patch set, whichever would be
> easier.
I think very soon just saying "run the latest kernel + e2fsprogs from F9
updates-testing" will be a good start. It won't have delalloc yet,
though. Do we want to try to make that more widely available to people
who can't/don't build their own kernels? I'm slightly hesitant I guess
both for the extra work of maintaining the repo & complete kernel
builds, as well as providing too much rope to people who may not know
just how much rope they've got ...
For pre-built fedora stuff I'd rather those users just follow what gets
packaged from upstream unless someone really, really thinks we should do
otherwise.
-Eric
> If other ext4 developers have a chance, it would be a good idea to go
> through the http://ext4.wiki.kernel.org site, and do some grooming of
> the site. Some of the pages like the FAQ, which were originally
> targetted primarily at ext4 developers, may need to have some of the
> more developer-centric content moved to other pages now that we will
> start having more users coming to look at that site. And of course,
> there is some very badly out-of-date information on that site as well!
>
> - Ted
> --
> To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2008-07-14 19:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-14 19:24 Making it easier for end users to use ext4 Theodore Ts'o
2008-07-14 19:35 ` Eric Sandeen [this message]
2008-07-14 19:55 ` Theodore Tso
2008-07-14 21:27 ` Eric Sandeen
[not found] ` <1216172323.8292.23.camel@mingming-laptop>
[not found] ` <20080716023532.GO8185@mit.edu>
[not found] ` <1216227720.6424.7.camel@mingming-laptop>
2008-07-16 17:52 ` [PATCH, RFC] Add more intelligent handling of the mke2fs.conf installation process Theodore Tso
2008-07-16 18:24 ` Mingming Cao
2008-07-16 21:29 ` Andreas Dilger
2008-07-16 23:08 ` Theodore Tso
2008-07-15 5:22 ` Making it easier for end users to use ext4 Goswin von Brederlow
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=487BAA6B.7030001@redhat.com \
--to=sandeen@redhat.com \
--cc=linux-ext4@vger.kernel.org \
--cc=tytso@mit.edu \
/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