From: Wakko Warner <wakko@animx.eu.org>
To: Jes Sorensen <jes@linuxcare.com>
Cc: Daryll Strauss <daryll@valinux.com>,
David Feuer <David_Feuer@brown.edu>,
linux-kernel@vger.kernel.org
Subject: Re: [Fwd: NTFS repair tools]
Date: Mon, 11 Dec 2000 21:46:44 -0500 [thread overview]
Message-ID: <20001211214644.C29196@animx.eu.org> (raw)
In-Reply-To: <E144O4d-0003vd-00@the-village.bc.nu> <3A3066EC.3B657570@timpanogas.org> <E144O4d-0003vd-00@the-village.bc.nu> <20001209201238.A12452@zorro.pangea.ca> <4.3.2.7.2.20001209213353.00b8bef0@postoffice.brown.edu> <20001209184921.A8495@newbie> <d3aea2ml7r.fsf@lxplus015.cern.ch>
In-Reply-To: <d3aea2ml7r.fsf@lxplus015.cern.ch>; from Jes Sorensen on Tue, Dec 12, 2000 at 03:23:20AM +0100
> Daryll> On Sat, Dec 09, 2000 at 09:34:59PM -0500, David Feuer wrote:
> >> For what it's worth, I absolutely agree with this. I have the same
> >> impression when I just see the word "dangerous".
>
> Daryll> Why not call a spade a spade and label it BROKEN. I do think
> Daryll> that's stronger than DANGEROUS.
>
> I doubt it will make any difference whatever we write. I have seen
> several times how users enable every single option because 'they don't
> want to miss out on anything'. It's at the order of someone with a
> Macintosh enabling something labelled "Atari internal serial port
> support" (theoretical example, no offense).
How about reversed?
The option comes enabled by default, but the coding is change to fit this
below:
<M> NTFS support
[*] disable ntfs write support
But after reading other comments, having it be a forced mount r/w is better.
(just like I have to force other FS to be mounted r/o instead of default
r/w)
--
Lab tests show that use of micro$oft causes cancer in lab animals
-
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-12 3:08 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 [this message]
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
-- 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=20001211214644.C29196@animx.eu.org \
--to=wakko@animx.eu.org \
--cc=David_Feuer@brown.edu \
--cc=daryll@valinux.com \
--cc=jes@linuxcare.com \
--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