From: "Jeff V. Merkey" <jmerkey@vger.timpanogas.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: "Jeff V. Merkey" <jmerkey@timpanogas.org>, linux-kernel@vger.kernel.org
Subject: Re: [Fwd: NTFS repair tools]
Date: Fri, 8 Dec 2000 11:31:58 -0700 [thread overview]
Message-ID: <20001208113158.A4730@vger.timpanogas.org> (raw)
In-Reply-To: <3A30552D.A6BE248C@timpanogas.org> <E144O01-0003v7-00@the-village.bc.nu>
In-Reply-To: <E144O01-0003v7-00@the-village.bc.nu>; from alan@lxorguk.ukuu.org.uk on Fri, Dec 08, 2000 at 01:55:43PM +0000
On Fri, Dec 08, 2000 at 01:55:43PM +0000, Alan Cox wrote:
> > somewhere in the thousands. Is NTFS write stable enough now in 2.4 to
> > fix these problems, if so, can we DISABLE by REMOVING write code in the
>
> It says DANGEROUS in big letters on the configuration option. We are now
> down to the level of people who don't understand 'smoking kills you' in big
> letters on packaging, and people using very old trees that merely warned you
> that it was a very bad idea
I agree that if you give a mentally unbalanced person a firearm, they might
shoot themselves with it. I am suggesting we take away their firearm. Write
support for NTFS is useful for migrating from Linux to NT, R/O support is
useful for migrating NT to Linux. We won't be giving anything up. I think
just putting in a nastier warning message would suffice.
Jeff
>
> Alan
-
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/
next prev parent reply other threads:[~2000-12-08 18:07 UTC|newest]
Thread overview: 45+ 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
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 [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-12-09 8:00 Mark Sutton
2000-12-09 16:49 ` Willy Tarreau
2000-12-09 20:14 ` Jeff V. Merkey
2000-12-09 22:51 ` Jeff V. Merkey
2000-12-11 13:52 ` Xavier Bestel
2000-12-10 1:38 willy tarreau
2000-12-10 2:40 ` 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=20001208113158.A4730@vger.timpanogas.org \
--to=jmerkey@vger.timpanogas.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=jmerkey@timpanogas.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.