From: Kumba <kumba@gentoo.org>
To: Linux MIPS List <linux-mips@linux-mips.org>
Cc: Ralf Baechle <ralf@linux-mips.org>
Subject: [PATCH]: Set CONFIG_SECCOMP default to 'n'
Date: Thu, 24 Mar 2005 22:25:01 -0500 [thread overview]
Message-ID: <4243848D.3030201@gentoo.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 383 bytes --]
As I recently learned, CONFIG_SECCOMP's default value is "y", and this can
cause the build to fail until the remaining bits of this feature are
committed. The attached patch changes the default to "n".
--Kumba
--
"Such is oft the course of deeds that move the wheels of the world: small
hands do them because they must, while the eyes of the great are elsewhere."
--Elrond
[-- Attachment #2: misc-2.6.12-seccomp-no-default.patch --]
[-- Type: text/plain, Size: 431 bytes --]
--- arch/mips/Kconfig.orig 2005-03-21 14:31:08.757419840 -0500
+++ arch/mips/Kconfig 2005-03-21 14:31:20.955565440 -0500
@@ -1422,7 +1422,7 @@ config BINFMT_ELF32
config SECCOMP
bool "Enable seccomp to safely compute untrusted bytecode"
depends on PROC_FS && BROKEN
- default y
+ default n
help
This kernel feature is useful for number crunching applications
that may need to compute untrusted bytecode during their
reply other threads:[~2005-03-25 3:24 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=4243848D.3030201@gentoo.org \
--to=kumba@gentoo.org \
--cc=linux-mips@linux-mips.org \
--cc=ralf@linux-mips.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