From: Juan Quintela <quintela@mandrakesoft.com>
To: Erik Mouw <J.A.K.Mouw@ITS.TUDelft.NL>
Cc: Hans Reiser <reiser@namesys.com>, Andi Kleen <ak@suse.de>,
Andreas Dilger <adilger@turbolinux.com>,
monkeyiq <monkeyiq@users.sourceforge.net>,
linux-kernel@vger.kernel.org, Nikita Danilov <god@namesys.com>
Subject: Re: Dying disk and filesystem choice.
Date: 25 May 2001 13:29:09 +0200 [thread overview]
Message-ID: <m2r8xdoeey.fsf@trasno.mitica> (raw)
In-Reply-To: <m3bsoj2zsw.fsf@kloof.cr.au> <200105240658.f4O6wEWq031945@webber.adilger.int> <20010524103145.A9521@gruyere.muc.suse.de> <3B0D3C99.255B5A24@namesys.com> <20010524214641.E10968@arthur.ubicom.tudelft.nl>
In-Reply-To: <20010524214641.E10968@arthur.ubicom.tudelft.nl>
>>>>> "erik" == Erik Mouw <J.A.K.Mouw@ITS.TUDelft.NL> writes:
erik> On Thu, May 24, 2001 at 09:53:45AM -0700, Hans Reiser wrote:
>> No, reiserfs does have badblock support!!!!
>>
>> You just have to get it as a separate patch from us because it was
>> written after code freeze.
erik> IMHO we are not that deep into code freeze anymore. Freevxfs got added
erik> in linux-2.4.5-pre*, so I think that a patch that adds a useful feature
erik> like badblock support would be OK.
A new filesystem don't touch anything if you don't use it. Some
reasoning for inclusion of new drivers. Big changes in a working
driver could make it not to work (very bad in the stable series).
Later, Juan.
--
In theory, practice and theory are the same, but in practice they
are different -- Larry McVoy
next prev parent reply other threads:[~2001-05-25 11:30 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-24 3:25 Dying disk and filesystem choice monkeyiq
2001-05-24 6:03 ` Hans Reiser
2001-05-24 6:58 ` Andreas Dilger
2001-05-24 8:31 ` Andi Kleen
2001-05-24 10:19 ` Jens Axboe
2001-05-24 12:08 ` monkeyiq
2001-05-24 15:46 ` Jonathan Lundell
2001-05-24 15:50 ` Jonathan Lundell
2001-05-24 15:56 ` Andi Kleen
2001-05-24 16:13 ` Jonathan Lundell
2001-05-24 16:53 ` Hans Reiser
2001-05-24 17:16 ` David Rees
2001-05-24 19:03 ` J Sloan
2001-05-24 20:54 ` Hans Reiser
2001-05-24 19:46 ` Erik Mouw
2001-05-24 21:24 ` Hans Reiser
2001-05-24 22:16 ` Alan Cox
2001-05-25 13:21 ` Chris Mason
2001-05-25 16:21 ` Hans Reiser
2001-05-25 16:58 ` Chris Mason
2001-05-25 17:42 ` Hans Reiser
2001-05-25 11:29 ` Juan Quintela [this message]
2001-05-24 21:35 ` monkeyiq
-- strict thread matches above, loose matches on Subject: below --
2001-05-24 17:30 Cress, Andrew R
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=m2r8xdoeey.fsf@trasno.mitica \
--to=quintela@mandrakesoft.com \
--cc=J.A.K.Mouw@ITS.TUDelft.NL \
--cc=adilger@turbolinux.com \
--cc=ak@suse.de \
--cc=god@namesys.com \
--cc=linux-kernel@vger.kernel.org \
--cc=monkeyiq@users.sourceforge.net \
--cc=reiser@namesys.com \
/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