From: Willy Tarreau <wtarreau@free.fr>
To: Mark Sutton <mes@capelazo.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [Fwd: NTFS repair tools]
Date: Sat, 09 Dec 2000 17:49:00 +0100 (MET) [thread overview]
Message-ID: <976380540.3a32627c184c3@imp.free.fr> (raw)
In-Reply-To: <Pine.GSO.4.10.10012082329290.27791-100000@lazo.capelazo.com>
In-Reply-To: <Pine.GSO.4.10.10012082329290.27791-100000@lazo.capelazo.com>
One problem with warnings at compile time is that in many cases, administrators
use kernels provided by friends or collegues that "know linux better than them".
If an admin uses a kernel in which write support has been activated to mount
an NTFS file system without providing any option, he will get it mount R/W
without any warning, then may destroy it at the first mistake or so.
perhaps we should add an option such as "force" to mount an NTFS r/w, and as
suggested by JBG, print a KERN_EMERG message when attempting to mount it r/w
without the "force" option.
we could also add a static counter which will make the first r/w mount always
fail, to ensure people will read the message, and which would prevent people
from mounting r/w from fstab.
just my $0.02.
BTW, I like the message about microsoft preventing from fixing the driver ;-)
Cheers,
Willy
-
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-09 17:20 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-09 8:00 [Fwd: NTFS repair tools] Mark Sutton
2000-12-09 16:49 ` Willy Tarreau [this message]
2000-12-09 20:14 ` Jeff V. Merkey
2000-12-09 22:51 ` Jeff V. Merkey
2000-12-11 13:52 ` Xavier Bestel
-- strict thread matches above, loose matches on Subject: below --
2000-12-10 1:38 willy tarreau
2000-12-10 2:40 ` Jeff V. Merkey
2000-12-08 3:27 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 7:50 ` 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=976380540.3a32627c184c3@imp.free.fr \
--to=wtarreau@free.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=mes@capelazo.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