From: Ron Johnson <ron.l.johnson@cox.net>
To: linux-ext4@vger.kernel.org
Subject: Re: ext5
Date: Thu, 11 Feb 2010 22:47:15 -0600 [thread overview]
Message-ID: <4B74DD53.3080308@cox.net> (raw)
In-Reply-To: <874olnih62.fsf@frosties.localdomain>
On 2010-02-11 15:41, Goswin von Brederlow wrote:
> tytso@mit.edu writes:
>> The idea with read-only compressed files is that they are useful for
>> large executables or large static files, where compressing them means
>> that it takes less time to read them off of an HDD.
>
> Or when you only have so much flash.
Isn't that what squashfs is for?
--
"Hell hath no fury like the vast robot armies of a woman scorned."
Walt
next prev parent reply other threads:[~2010-02-12 4:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-09 23:40 ext5 Anonymous Remailer (austria)
2010-02-10 21:50 ` ext5 tytso
2010-02-11 3:38 ` ext5 Manish Katiyar
2010-02-11 4:30 ` ext5 tytso
2010-02-11 17:55 ` ext5 Jan Kara
2010-02-11 19:31 ` ext5 tytso
2010-02-11 5:18 ` ext5 Ron Johnson
2010-02-11 6:44 ` ext5 tytso
2010-02-11 16:49 ` ext5 Ron Johnson
2010-02-11 21:41 ` ext5 Goswin von Brederlow
2010-02-12 4:47 ` Ron Johnson [this message]
2010-02-12 16:02 ` ext5 tytso
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=4B74DD53.3080308@cox.net \
--to=ron.l.johnson@cox.net \
--cc=linux-ext4@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).