public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@stusta.de>
To: Andrew Morton <akpm@osdl.org>,
	Stephen Smalley <sds@tycho.nsa.gov>,
	jmorris@namei.org
Cc: linux-kernel@vger.kernel.org
Subject: [-mm patch] improve SECURITY_SELINUX_POLICYDB_VERSION_MAX{,_VALUE} help texts
Date: Wed, 30 Aug 2006 22:35:41 +0200	[thread overview]
Message-ID: <20060830203541.GN18276@stusta.de> (raw)
In-Reply-To: <20060826160922.3324a707.akpm@osdl.org>

We can't expect everyone to know what "FC3" is.

Signed-off-by: Adrian Bunk <bunk@stusta.de>

--- linux-2.6.18-rc4-mm3/security/selinux/Kconfig.old	2006-08-30 21:56:31.000000000 +0200
+++ linux-2.6.18-rc4-mm3/security/selinux/Kconfig	2006-08-30 21:58:21.000000000 +0200
@@ -135,8 +135,10 @@ config SECURITY_SELINUX_POLICYDB_VERSION
 	  It can be adjusted downward to support legacy userland (init) that
 	  does not correctly handle kernels that support newer policy versions.
 
-	  Examples:  For FC3 or FC4, enable this option and set the value via
-	  the next option.  For FC5 and later, do not enable this option.
+	  Examples:
+	  For the Fedora Core 3 or 4 Linux distributions, enable this option
+	  and set the value via the next option. For Fedore Core 5 and later,
+	  do not enable this option.
 
 	  If you are unsure how to answer this question, answer N.
 
@@ -149,7 +151,9 @@ config SECURITY_SELINUX_POLICYDB_VERSION
 	  This option sets the value for the maximum policy format version
 	  supported by SELinux.
 
-	  Examples:  For FC3, use 18.  For FC4, use 19.
+	  Examples:
+	  For Fedora Core 3, use 18.
+	  For Fedora Core 4, use 19.
 
 	  If you are unsure how to answer this question, look for the
 	  policy format version supported by your policy toolchain, by


      parent reply	other threads:[~2006-08-30 20:35 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-26 23:09 2.6.18-rc4-mm3 Andrew Morton
2006-08-26 23:56 ` 2.6.18-rc4-mm3: ROOT_NFS=y compile error Adrian Bunk
2006-08-27 18:25   ` Chuck Lever
2006-08-27 20:56     ` Andrew Morton
2006-08-28 17:36       ` Chuck Lever
2006-08-28 17:43         ` Trond Myklebust
2006-08-27  1:59 ` [-mm patch] drivers/i2c/busses/scx200_i2c.c: update struct scx200_i2c_data Adrian Bunk
2006-08-27  8:20   ` Jean Delvare
2006-08-27  2:42 ` 2.6.18-rc4-mm3: NF_CONNTRACK_FTP=y compile error Adrian Bunk
2006-08-27  2:49   ` David Miller
2006-08-27  2:47 ` [-mm patch] struct i2c_algo_pcf_data: remove the mdelay member Adrian Bunk
2006-08-27  8:44   ` Jean Delvare
2006-08-27 12:50 ` 2.6.18-rc4-mm3 Benoit Boissinot
2006-08-28  7:35   ` 2.6.18-rc4-mm3 Pablo Neira Ayuso
2006-08-27 16:00 ` 2.6.18-rc4-mm3 Benoit Boissinot
2006-08-28  9:07 ` 2.6.18-rc4-mm3 Mel Gorman
2006-08-28 18:34   ` 2.6.18-rc4-mm3 Andrew Morton
2006-08-29 14:44     ` 2.6.18-rc4-mm3 Mel Gorman
2006-08-28 20:07 ` divide error: 0000 in fib6_rule_match [Re: 2.6.18-rc4-mm3] Mattia Dongili
2006-08-28 20:28   ` Andrew Morton
2006-08-28 21:22     ` Andi Kleen
2006-08-28 21:30   ` Andrew Morton
2006-08-28 21:51     ` divide error: 0000 in fib6_rule_match David Miller
2006-08-29  6:33     ` divide error: 0000 in fib6_rule_match [Re: 2.6.18-rc4-mm3] Mattia Dongili
2006-08-28 20:24 ` one more ACPI Error (utglobal-0125): Unknown exception code: 0xFFFFFFEA " Mattia Dongili
2006-08-28 22:16 ` 2.6.18-rc4-mm3 Rafael J. Wysocki
2006-08-29 13:37 ` 2.6.18-rc4-mm3 Haavard Skinnemoen
2006-08-29 15:18   ` 2.6.18-rc4-mm3 Cedric Le Goater
2006-08-29 15:42     ` 2.6.18-rc4-mm3 Haavard Skinnemoen
2006-08-30 20:35 ` [-mm patch] net/sched/act_simple.c: make struct simp_hash_info static Adrian Bunk
2006-08-30 22:03   ` David Miller
2006-08-30 20:35 ` [-mm patch] drivers/input/misc/wistron_btns.c: fix section mismatch Adrian Bunk
2006-08-30 23:26   ` Dmitry Torokhov
2006-08-30 23:36     ` Adrian Bunk
2006-08-31  2:54       ` Dmitry Torokhov
2006-08-30 20:35 ` Adrian Bunk [this message]

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=20060830203541.GN18276@stusta.de \
    --to=bunk@stusta.de \
    --cc=akpm@osdl.org \
    --cc=jmorris@namei.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sds@tycho.nsa.gov \
    /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