mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Anton Altaparmakov <aia21@cam.ac.uk>
To: Peter Samuelson <peter@cadcamlab.org>
Cc: "Jeff V. Merkey" <jmerkey@timpanogas.org>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] NTFS repair tools
Date: Fri, 08 Dec 2000 07:37:55 +0000	[thread overview]
Message-ID: <5.0.2.1.2.20001208072533.03fd97d0@pop.cus.cam.ac.uk> (raw)
In-Reply-To: <14896.31327.179696.632616@wire.cadcamlab.org>
In-Reply-To: <3A30552D.A6BE248C@timpanogas.org> <20001207221347.R6567@cadcamlab.org> <3A3066EC.3B657570@timpanogas.org> <20001208005337.A26577@alcove.wittsend.com> <20001207230407.S6567@cadcamlab.org> <3A306CE4.47B366B0@timpanogas.org>

Hearing how many people trash their partition I would agree to comment out 
the NTFS write option altogether. I will make a patch for both 2.4.0-testX 
and 2.2.18latest and send them off to Linus/Alan over the weekend if no one 
beats me to it.

Considering that people are blatantly ignoring all our warnings this might 
be the Right Thing(TM) as it is easy enough to activate the option if 
someone really wants/needs to use it. That should hopefully lower the 
amount of incidents with people trashing their partitions[1][2].

Anton

[1] On the other hand it might not help much as people might just uncomment 
it and go ahead using it, but there is a limit to how far we can go without 
taking out the write part of the driver altogether! Which might actually 
not be a Bad Thing(TM) were it not for the fact that having the write 
support can actually help in fixing a trashed partition when people know 
what they are doing...i.e. when they know what they can do safely and what 
not. - It's saved me from loosing 10Gb+ of non-backed up data in the past!

[2] My NTFS repair utility is under development albeit very slowly which 
should help a little bit once I have a stable release. - Initial release is 
yet TBA as there are some very strange bugs in it at the moment, which 
might actually turn out to be bugs in the compiler/libc/kernel as the 
program runs fine sometimes and sometimes corrupts the partitions slightly, 
operating on the _exact_ same partition with the _exact_ same data on it! - 
Anyway, I am not releasing this to the public before I have figured out WTH 
is going on...

At 06:06 08/12/2000, Peter Samuelson wrote:
>[Jeff Merkey]
> > Please consider the attached patch to make it a little bit harder for
> > folks to enable NTFS Write Support under Linux until it can get fixed
> > properly.
>
>Hey!  It was a joke!  A better way would be just to comment out the
>CONFIG_NTFS_RW line entirely.  Actually, I think that *would* be a good
>idea.  Anyone who has any business messing with NTFS_RW is more than
>capable of editing Config.in.
>
>Peter
>-
>To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
>the body of a message to majordomo@vger.kernel.org
>Please read the FAQ at http://www.tux.org/lkml/

-- 
      "Education is what remains after one has forgotten everything he 
learned in school." - Albert Einstein
-- 
Anton Altaparmakov  Voice: +44-(0)1223-333541(lab) / +44-(0)7712-632205(mobile)
Christ's College    eMail: AntonA@bigfoot.com / aia21@cam.ac.uk
Cambridge CB2 3BU    ICQ: 8561279
United Kingdom       WWW: http://www-stu.christs.cam.ac.uk/~aia21/

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  parent reply	other threads:[~2000-12-08  8:07 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-12-08  3:27 [Fwd: NTFS repair tools] Jeff V. Merkey
2000-12-08  4:13 ` Peter Samuelson
2000-12-08  4:43   ` Jeff V. Merkey
2000-12-08  5:53     ` Michael H. Warfield
2000-12-08  4:54       ` Jeff V. Merkey
2000-12-08  5:04       ` Peter Samuelson
2000-12-08  5:08         ` [PATCH] NTFS repair tools Jeff V. Merkey
2000-12-08  6:06           ` Peter Samuelson
2000-12-08  8:17             ` Jeff V. Merkey
2000-12-08 14:46             ` Jeff Garzik
2000-12-08  7:37           ` Anton Altaparmakov [this message]
2000-12-08 19:01             ` Jeff V. Merkey
2000-12-08  7:50         ` [Fwd: NTFS repair tools] Andrzej Krzysztofowicz
2000-12-08 13:19       ` David Relson
2000-12-08 13:43         ` David Weinehall
2000-12-08 14:34           ` Jan-Benedict Glaw
2000-12-08 17:02             ` Michael H. Warfield
2000-12-08 18:35             ` Jeff V. Merkey
2000-12-08 14:00     ` Alan Cox
2000-12-08 14:27       ` Rik van Riel
2000-12-08 14:44         ` Mohammad A. Haque
2000-12-08 15:08           ` David Woodhouse
2000-12-08 14:50         ` Richard B. Johnson
2000-12-08 18:33       ` Jeff V. Merkey
2000-12-08 17:42         ` Jeff Garzik
2000-12-08 18:50           ` Jeff V. Merkey
2000-12-09 22:03         ` Eric W. Biederman
2000-12-10  1:11           ` Jeff V. Merkey
2000-12-10  2:12       ` Ren Haddock
2000-12-10  5:26         ` Andre Hedrick
2000-12-10  2:34     ` David Feuer
2000-12-10  2:49       ` Daryll Strauss
2000-12-12  2:23         ` Jes Sorensen
2000-12-12  2:46           ` Wakko Warner
2000-12-10  5:00       ` John Alvord
2000-12-10 16:11         ` Horst von Brand
2000-12-08 13:55 ` Alan Cox
2000-12-08 18:31   ` Jeff V. Merkey

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=5.0.2.1.2.20001208072533.03fd97d0@pop.cus.cam.ac.uk \
    --to=aia21@cam.ac.uk \
    --cc=jmerkey@timpanogas.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peter@cadcamlab.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

all inboxes | Powered by JetHome®