From: Jan-Benedict Glaw <jbglaw@lug-owl.de>
To: linux-kernel@vger.kernel.org
Subject: Re: [Fwd: NTFS repair tools]
Date: Fri, 8 Dec 2000 15:34:09 +0100 [thread overview]
Message-ID: <20001208153408.A19802@lug-owl.de> (raw)
In-Reply-To: <3A30552D.A6BE248C@timpanogas.org> <20001207221347.R6567@cadcamlab.org> <3A3066EC.3B657570@timpanogas.org> <20001208005337.A26577@alcove.wittsend.com> <3A306994.63DB8208@timpanogas.org> <4.3.2.7.2.20001208081657.00b15220@mail.osagesoftware.com> <20001208144342.B25391@khan.acc.umu.se>
In-Reply-To: <20001208144342.B25391@khan.acc.umu.se>; from tao@acc.umu.se on Fri, Dec 08, 2000 at 02:43:42PM +0100
[-- Attachment #1: Type: text/plain, Size: 1360 bytes --]
On Fri, Dec 08, 2000 at 02:43:42PM +0100, David Weinehall wrote:
> On Fri, Dec 08, 2000 at 08:19:46AM -0500, David Relson wrote:
> > At 11:54 PM 12/7/00, Jeff V. Merkey wrote:
> No amount of warnings can prevent morons from f**king up. Unix gives
> you enough rope et al. I'm not arguing for removal of any warning, but
> seriously, if we have a loud (DANGEROUS) warning in the config-system
> aaaaaand a warning in the help-text that the write-support probably will
> mess up your fs, how much more can you do? I bet that if we remove the
Well, simply insert sth. like this into ./fs/ntfs/fs.c:parse_options()
printk(KERN_EMERG "You're likely to crash your NTFS if you do any "
"write attempts to it. NTFS write support is broken and for "
"developers *only*. Do only use this if you're debugging it, "
"never ever use this on data you'd like to see tomorrow "
"again!!! Please remount in read-only mode *now* or don't "
"complain afterwards!");
Maybe that can prevent pupils^H^H^H^H^Heople from shooting their
foots...
MfG, JBG
--
Fehler eingestehen, Größe zeigen: Nehmt die Rechtschreibreform zurück!!!
/* Jan-Benedict Glaw <jbglaw@lug-owl.de> -- +49-177-5601720 */
keyID=0x8399E1BB fingerprint=250D 3BCF 7127 0D8C A444 A961 1DBD 5E75 8399 E1BB
"insmod vi.o and there we go..." (Alexander Viro on linux-kernel)
[-- Attachment #2: Type: application/pgp-signature, Size: 240 bytes --]
next prev parent reply other threads:[~2000-12-08 15:05 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 [this message]
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
-- 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=20001208153408.A19802@lug-owl.de \
--to=jbglaw@lug-owl.de \
--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