mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: David Weinehall <tao@acc.umu.se>
To: David Relson <relson@osagesoftware.com>
Cc: "Jeff V. Merkey" <jmerkey@timpanogas.org>,
	"Michael H. Warfield" <mhw@wittsend.com>,
	Peter Samuelson <peter@cadcamlab.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [Fwd: NTFS repair tools]
Date: Fri, 8 Dec 2000 14:43:42 +0100	[thread overview]
Message-ID: <20001208144342.B25391@khan.acc.umu.se> (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>
In-Reply-To: <4.3.2.7.2.20001208081657.00b15220@mail.osagesoftware.com>; from relson@osagesoftware.com on Fri, Dec 08, 2000 at 08:19:46AM -0500

On Fri, Dec 08, 2000 at 08:19:46AM -0500, David Relson wrote:
> At 11:54 PM 12/7/00, Jeff V. Merkey wrote:
> 
> 
> >Linux today monitors this list.  Some public education may be the best
> >route.  How do we post a security advisory warning people that will get
> >posted?  I'm sure folks see the DANGEROUS comments, but they don't seem
> >to stick in their heads.  Then they get themselves into trouble, and
> >fortunately for them, I'm around.  I am just concerned about the scope
> >of the black eye that will just keep getting bigger and bigger for Linux
> >NTFS.
> 
> 
> FWIW, Mandrake Linux includes a tool MandrakeUpdate which allows 
> downloading of "Normal Updates" or "Development Updates".  If you chose 
> Devel Upd, you get the following warning:
> 
>          Caution !  These packages are NOT well tested.
>          You really can screw up your system
>          by installing them.
> 
> Perhaps the configure tools could recognize a DANGEROUS status (or keyword 
> or ???) and would display such a message ...

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
config-option, people will still enable it manually, then go "Waaaaa,
your stupid kernel messed up my filesystem, Linux sucks!"

But I kind of liked the

Enable write support (DANGEROUS)
  Really enable write support (DANGEROUS)
    Are you f**king nuts?!

approach anyway. A strong candidate for Rik van Riel's patch-of-the-month
homepage.


/David
  _                                                                 _
 // David Weinehall <tao@acc.umu.se> /> Northern lights wander      \\
//  Project MCA Linux hacker        //  Dance across the winter sky //
\>  http://www.acc.umu.se/~tao/    </   Full colour fire           </
-
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/

  reply	other threads:[~2000-12-08 14:14 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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  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 [this message]
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
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=20001208144342.B25391@khan.acc.umu.se \
    --to=tao@acc.umu.se \
    --cc=jmerkey@timpanogas.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mhw@wittsend.com \
    --cc=peter@cadcamlab.org \
    --cc=relson@osagesoftware.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

all inboxes | Powered by JetHome®