From: Aaron Lehmann <aaronl@vitelus.com>
To: Andrew Morton <akpm@zip.com.au>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux-2.4.10 + ext3
Date: Sun, 23 Sep 2001 21:45:08 -0700 [thread overview]
Message-ID: <20010923214507.A15014@vitelus.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0109231142060.1078-100000@penguin.transmeta.com> <1001280620.3540.33.camel@gromit.house> <9om4ed$1hv$1@penguin.transmeta.com>, <9om4ed$1hv$1@penguin.transmeta.com> <20010923193008.A13982@vitelus.com> <3BAEAC52.677C064C@zip.com.au>
In-Reply-To: <3BAEAC52.677C064C@zip.com.au>
On Sun, Sep 23, 2001 at 08:45:22PM -0700, Andrew Morton wrote:
> So yes, it would be nice if an ext3-only kernel could drive ext2
> filesystems, but not super-important.
Cool.
> As for the other part of your suggestion: make ext2 "obsolete":
> I don't think so. ext3 is wickedly complex, and ext2 is the
> reference filesystem for Linux. It could be argued (at length) that
> the VFS and block layers were designed for, and are almost part of
> ext2.
I didn't mean to imply this. I love ext2 and still use it more than
probably any other filesystem (judging by numbers of partitions).
I simply was hoping for insted of:
<*> EXT2 fs
<*> EXT3 fs
(which is required today for most ext3-using people who want to do ext2
mounts)
... there could be:
<*> EXT2 fs
<*> EXT3 journalling extensions
AFAIK this would eliminate a lot of duplicate kernel code for ext3
users.
But anyway, I'm not saying that ext2 should be made obsolete. I only
use ext3 on one machine and I would be much more annoyed if I had to
enable ext3 on the other machines than live with my current situation
of needing both ext2 and ext3 in the kernel on this particular one.
I think you understand ;-).
next prev parent reply other threads:[~2001-09-24 4:45 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-23 18:54 Linux-2.4.10 Linus Torvalds
2001-09-23 16:41 ` Linux-2.4.10 Rob Landley
2001-09-23 21:32 ` Linux-2.4.10 André Dahlqvist
2001-09-23 21:54 ` Linux-2.4.10 Alan Cox
2001-09-23 21:30 ` Linux-2.4.10 + ext3 Michael Rothwell
2001-09-23 22:18 ` Gergely Nagy
2001-09-24 2:06 ` Linus Torvalds
2001-09-24 2:30 ` Aaron Lehmann
2001-09-24 3:45 ` Andrew Morton
2001-09-24 4:35 ` Simon Fowler
2001-09-24 20:40 ` Stephen C. Tweedie
2001-09-24 4:45 ` Aaron Lehmann [this message]
2001-09-24 5:19 ` Andrew Morton
2001-09-24 19:49 ` Jamie Lokier
2001-09-24 20:22 ` Chris Meadors
2001-09-24 21:57 ` Jamie Lokier
2001-09-24 21:04 ` Andreas Dilger
2001-09-24 18:12 ` Linus Torvalds
2001-09-24 18:25 ` Alexander Viro
2001-09-26 16:49 ` Stephen C. Tweedie
2001-09-27 12:12 ` Jan Kara
2001-09-27 18:37 ` Stephen C. Tweedie
2001-09-23 21:54 ` Linux-2.4.10 Trond Myklebust
2001-09-23 22:34 ` Linux-2.4.10 David Woodhouse
2001-09-24 6:28 ` Linux-2.4.10 Erik Andersen
2001-09-24 6:48 ` Linux-2.4.10 David Woodhouse
2001-09-24 17:40 ` Linux-2.4.10 Erik Andersen
2001-09-24 17:41 ` Linux-2.4.10 David Woodhouse
2001-09-23 22:40 ` Linux-2.4.10 - necessary patches Eyal Lebedinsky
2001-09-24 0:04 ` Alan Cox
2001-09-24 14:42 ` Oliver Xymoron
2001-09-24 1:25 ` Linux-2.4.10 Matthias Andree
2001-09-24 2:26 ` Linux-2.4.10 Daniel T. Chen
2001-09-24 3:19 ` Linux-2.4.10 Matthias Andree
2001-09-24 2:57 ` Linux-2.4.10 Disconnect
2001-09-24 10:07 ` Linux-2.4.10 Matthias Andree
2001-09-27 12:17 ` Linux-2.4.10 Roeland Th. Jansen
2001-09-24 2:35 ` Linux-2.4.10 Naren Devaiah
2001-09-24 9:37 ` PATCH[2.4.9-pre14] Kill *writeonly* variable Martin Dalecki
2001-09-27 15:23 ` Linux-2.4.10 George R. Kasica
2001-09-27 15:27 ` Linux-2.4.10 Rik van Riel
2001-09-27 15:31 ` Linux-2.4.10 Bernd Petrovitsch
2001-09-27 15:49 ` Linux-2.4.10 John Jasen
2001-09-27 18:23 ` Linux-2.4.10 Petr Baudis
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=20010923214507.A15014@vitelus.com \
--to=aaronl@vitelus.com \
--cc=akpm@zip.com.au \
--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