From: Daryll Strauss <daryll@valinux.com>
To: David Feuer <David_Feuer@brown.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [Fwd: NTFS repair tools]
Date: Sat, 9 Dec 2000 18:49:22 -0800 [thread overview]
Message-ID: <20001209184921.A8495@newbie> (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>
In-Reply-To: <4.3.2.7.2.20001209213353.00b8bef0@postoffice.brown.edu>; from David_Feuer@brown.edu on Sat, Dec 09, 2000 at 09:34:59PM -0500
On Sat, Dec 09, 2000 at 09:34:59PM -0500, David Feuer wrote:
> At 08:12 PM 12/9/2000 -0600, Rene wrote:
> >I think part of the problem is that there are other things labeled
> >DANGEROUS that actually do work fairly reliably (offhand, I'm thinking
> >off the IDE config stuff..). Perhaps it needs to explicitely say
> >'This is broken and is gauranteed to destroy your data. Do not use it'
> >
> >The 'DANGEROUS' label seems to suggest that it -may- destroy data, which
> >leads to the 'it won't happen to me' mentality.
>
> For what it's worth, I absolutely agree with this. I have the same
> impression when I just see the word "dangerous".
Why not call a spade a spade and label it BROKEN. I do think that's
stronger than DANGEROUS.
- |Daryll
-
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-10 3:20 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 [this message]
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=20001209184921.A8495@newbie \
--to=daryll@valinux.com \
--cc=David_Feuer@brown.edu \
--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.