mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrzej Krzysztofowicz <ankry@pg.gda.pl>
To: peter@cadcamlab.org (Peter Samuelson)
Cc: jmerkey@timpanogas.org (Jeff V. Merkey), linux-kernel@vger.kernel.org
Subject: Re: [Fwd: NTFS repair tools]
Date: Fri, 8 Dec 2000 08:50:47 +0100 (MET)	[thread overview]
Message-ID: <200012080750.IAA13825@sunrise.pg.gda.pl> (raw)
In-Reply-To: <20001207230407.S6567@cadcamlab.org> from "Peter Samuelson" at Dec 07, 2000 11:04:07 PM

"Peter Samuelson wrote:"
> [Michael Warfield]
> > This thing is not armed and dangerous due to an act of ommision.
> > It's live and active only through three acts of commision.
> 
> We could make it *four* acts of commission. (: (: (:
> 
> diff -urk~ fs/Config.in
> --- fs/Config.in~	Mon Nov 13 01:43:42 2000
> +++ fs/Config.in	Thu Dec  7 23:00:34 2000
> @@ -37,7 +37,8 @@
>  tristate 'Minix fs support' CONFIG_MINIX_FS
>  
>  tristate 'NTFS file system support (read only)' CONFIG_NTFS_FS
> -dep_mbool '  NTFS write support (DANGEROUS)' CONFIG_NTFS_RW $CONFIG_NTFS_FS $CONFIG_EXPERIMENTAL
> +dep_mbool '  NTFS write support (DANGEROUS)' CONFIG_MORON $CONFIG_NTFS_FS $CONFIG_EXPERIMENTAL
> +dep_bool  '    Are you sure?  I hope you dont care about your NTFS filesystems' CONFIG_NTFS_RW $CONFIG_MORON
>  
>  tristate 'OS/2 HPFS file system support' CONFIG_HPFS_FS

Of course, you know that it *WILL NOT* work as CONFIG_MORON is nowhere 
defined ... ?

Andrzej
--
=======================================================================
  Andrzej M. Krzysztofowicz               ankry@mif.pg.gda.pl
  phone (48)(58) 347 14 61
Faculty of Applied Phys. & Math.,   Technical University of Gdansk
-
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/

  parent reply	other threads:[~2000-12-08  8:22 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         ` Andrzej Krzysztofowicz [this message]
2000-12-08 13:19       ` [Fwd: NTFS repair tools] 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
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=200012080750.IAA13825@sunrise.pg.gda.pl \
    --to=ankry@pg.gda.pl \
    --cc=jmerkey@timpanogas.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peter@cadcamlab.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

all inboxes | Powered by JetHome®