From: Matthias Juchem <lists@konfido.de>
To: linux-kernel@vger.kernel.org
Subject: [RFC] Hide dangerous configuration options
Date: Fri, 13 Dec 2002 01:10:04 +0100 [thread overview]
Message-ID: <E18MdP2-0002WU-00@gandalf.math.uni-mannheim.de> (raw)
Hi.
The patch below adds a configuration option 'DANGEROUS'.
Idea is to prevent people from enabling such options unintentionally.
Set to N, options which were labelled DANGEROUS are hidden,
set to Y, they are show.
DANGEROUS does not depend on EXPERIMENTAL, because there are options that are
dangerous but not experimental.
Patch is against 2.5.51.
Regards,
Matthias
diff -urN linux-2.5.51/arch/ppc/Kconfig linux-2.5.51-mj/arch/ppc/Kconfig
--- linux-2.5.51/arch/ppc/Kconfig Tue Dec 10 03:46:25 2002
+++ linux-2.5.51-mj/arch/ppc/Kconfig Fri Dec 13 00:19:17 2002
@@ -694,7 +694,7 @@
config TAU_INT
bool "Interrupt driven TAU driver (DANGEROUS)"
- depends on TAU
+ depends on TAU && DANGEROUS
---help---
The TAU supports an interrupt driven mode which causes an interrupt
whenever the temperature goes out of range. This is the fastest way
diff -urN linux-2.5.51/drivers/ide/Kconfig linux-2.5.51-mj/drivers/ide/Kconfig
--- linux-2.5.51/drivers/ide/Kconfig Tue Dec 10 03:45:56 2002
+++ linux-2.5.51-mj/drivers/ide/Kconfig Fri Dec 13 00:17:52 2002
@@ -424,7 +424,7 @@
config WDC_ALI15X3
bool "ALI M15x3 WDC support (DANGEROUS)"
- depends on BLK_DEV_ALI15X3
+ depends on BLK_DEV_ALI15X3 && DANGEROUS
---help---
This allows for UltraDMA support for WDC drives that ignore CRC
checking. You are a fool for enabling this option, but there have
diff -urN linux-2.5.51/fs/Kconfig linux-2.5.51-mj/fs/Kconfig
--- linux-2.5.51/fs/Kconfig Tue Dec 10 03:46:10 2002
+++ linux-2.5.51-mj/fs/Kconfig Fri Dec 13 00:18:55 2002
@@ -159,7 +159,7 @@
config ADFS_FS_RW
bool "ADFS write support (DANGEROUS)"
- depends on ADFS_FS
+ depends on ADFS_FS && DANGEROUS
help
If you say Y here, you will be able to write to ADFS partitions on
hard drives and ADFS-formatted floppy disks. This is experimental
@@ -773,7 +773,7 @@
config NTFS_RW
bool "NTFS write support (DANGEROUS)"
- depends on NTFS_FS && EXPERIMENTAL
+ depends on NTFS_FS && EXPERIMENTAL && DANGEROUS
help
This enables the experimental write support in the NTFS driver.
@@ -916,7 +916,7 @@
config QNX4FS_RW
bool "QNX4FS write support (DANGEROUS)"
- depends on QNX4FS_FS && EXPERIMENTAL
+ depends on QNX4FS_FS && EXPERIMENTAL && DANGEROUS
help
Say Y if you want to test write support for QNX4 file systems.
@@ -1098,7 +1098,7 @@
config UFS_FS_WRITE
bool "UFS file system write support (DANGEROUS)"
- depends on UFS_FS && EXPERIMENTAL
+ depends on UFS_FS && EXPERIMENTAL && DANGEROUS
help
Say Y here if you want to try writing to UFS partitions. This is
experimental, so you should back up your UFS partitions beforehand.
diff -urN linux-2.5.51/init/Kconfig linux-2.5.51-mj/init/Kconfig
--- linux-2.5.51/init/Kconfig Tue Dec 10 03:46:15 2002
+++ linux-2.5.51-mj/init/Kconfig Fri Dec 13 00:40:51 2002
@@ -32,6 +32,13 @@
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 DANGEROUS
+ bool "Prompt for dangerous code/drivers"
+ ---help---
+ If you say Y here, options that enable dangerous code will be shown.
+
+ Say N.
+
endmenu
reply other threads:[~2002-12-13 0:02 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=E18MdP2-0002WU-00@gandalf.math.uni-mannheim.de \
--to=lists@konfido.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 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.