[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Pine.LNX.4.61.0704012143120.16977@yvahk01.tjqt.qr>
Date: Sun, 1 Apr 2007 21:47:18 +0200 (MEST)
From: Jan Engelhardt <jengelh@...ux01.gwdg.de>
To: Kyle Moffett <mrmacman_g4@....com>
cc: Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Alan Cox <alan@...rguk.ukuu.org.uk>,
Sam Ravnborg <sam@...nborg.org>, Andrew Morton <akpm@...l.org>
Subject: Re: [PATCH]
On Apr 1 2007 15:42, Kyle Moffett wrote:
>Date: Sun, 1 Apr 2007 15:42:09 -0400
>From: Kyle Moffett <mrmacman_g4@....com>
>To: Jan Engelhardt <jengelh@...ux01.gwdg.de>
>Cc: Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
> Alan Cox <alan@...rguk.ukuu.org.uk>, Sam Ravnborg <sam@...nborg.org>,
> Andrew Morton <akpm@...l.org>
>Subject: [PATCH]
>
> Add a CONFIG_I_KNOW_WHAT_THE_HELL_I_AM_DOING variable with a really strong
> warning attached to it (and a shorter CONFIG_EXPERT variable for use in
> Kconfig files where it's a PITA to type out the full name)
Do it like Linus Torvalds and Marissa Mayer and get a better mailer :-D
Index: linux-2.6.20.1/init/Kconfig
===================================================================
--- linux-2.6.20.1.orig/init/Kconfig
+++ linux-2.6.20.1/init/Kconfig
@@ -40,6 +40,35 @@
you say Y here, you will be offered the choice of using features or
drivers that are currently considered to be in the alpha-test phase.
+config I_KNOW_WHAT_THE_HELL_I_AM_DOING
Let's just hope kconfig does not bust the stack.
Perhaps we could shorten that: I_KNOW_WTF_I_AM_DOING
+ bool "Prompt for config options which will break your computer"
s/will break (.*)/could break $1 if done wrong/;
+ ---help---
+ Some kernel developers sometimes need to tune kernel parameters
+ outside of their normal limits. Without complete knowledge of
+ exactly what you are doing you are likely to corrupt the laws of
+ physics and destroy the universe (well, not quite, but you'll
+ certainly corrupt your data and crash your box). If you really
+ know what you're doing and accept that if it breaks you get to
+ keep the pieces, then go ahead and enable this option.
+
+ NOTICE: Bug reports where this option is turned on in the kernel
+ config will be: (not necessarily in this order)
+ 1) Laughed at hysterically
+ 2) Made much fun of
+ 3) Ridiculed until we're red in the face
+ 4) Ignored
+
+ WARNING: If you are building a kernel for a distribution, DO NOT
+ TURN THIS OPTION ON!!! Instead you should submit a patch which
+ adds a new safe value to the list of possibilities for the config
+ option you're interested in. Otherwise your users might have a
+ hard time getting kernel support on the LKML.
+
+config EXPERT
+ bool
+ depends on I_KNOW_WHAT_THE_HELL_I_AM_DOING
+ default y
+
config BROKEN
bool
Given that, I hope the number of options dependent on CONFIG_EXPERT will
outnumber those depending on CONFIG_I_KNOW_WTF_I_AM_DOING.
If you want my answer: not-so-ACK, move the text to CONFIG_EXPERT and
let's stay sane for the next 366 days until next April 01.
Jan
--
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists