From: Goswin von Brederlow <goswin-v-b@web.de>
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: Tue, 15 Jul 2008 07:22:36 +0200 [thread overview]
Message-ID: <873ambwwkj.fsf@frosties.localdomain> (raw)
In-Reply-To: <E1KITeX-0001PV-Pv@closure.thunk.org> (Theodore Ts'o's message of "Mon, 14 Jul 2008 15:24:05 -0400")
"Theodore Ts'o" <tytso@mit.edu> writes:
> 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.
Many thanks. Going through various pages I found the information to be
seriously out of date ranging from one to two years.
Some thoughts about missing bits from a first read through:
Getting Ext4 code:
- add ext4 and e2fsprogs git repositories
- Add Debian section
64 bit block support:
- limits without it
- state of it
- where to get patches
MfG
Goswin
prev parent reply other threads:[~2008-07-15 5:22 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
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 ` Goswin von Brederlow [this message]
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=873ambwwkj.fsf@frosties.localdomain \
--to=goswin-v-b@web.de \
--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