From: Kevin Winchester <kjwinchester@gmail.com>
To: Jesper Juhl <jesper.juhl@gmail.com>
Cc: linux-kernel@vger.kernel.org,
Krishna Balasubramanian <balasub@cis.ohio-state.edu>,
Linus Torvalds <torvalds@linux-foundation.org>,
Sam Ravnborg <sam@ravnborg.org>
Subject: Re: [PATCH] Let SYSVIPC default to 'y'
Date: Wed, 23 Apr 2008 21:00:38 -0300 [thread overview]
Message-ID: <480FCDA6.6000509@gmail.com> (raw)
In-Reply-To: <alpine.LNX.1.00.0804240057240.2438@dragon.funnycrock.com>
Jesper Juhl wrote:
> SYSVIPC is a pretty crucial feature that I doubt very much if anyone
> except embedded people should even consider disabling - it simply
> breaks too much software for a Linux box to really be useful without it,
> for most purposes.
> For that reason I find it quite odd that the feature defaults to 'No'
> currently. I really cannot see any reason why we wouldn't want this to
> default to 'Yes', so this patch changes the default by adding 'default y'
> to Kconfig.
>
> Signed-off-by: Jesper Juhl <jesper.juhl@gmail.com>
> ---
>
> Kconfig | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/init/Kconfig b/init/Kconfig
> index ba3a389..023b2b6 100644
> --- a/init/Kconfig
> +++ b/init/Kconfig
> @@ -112,6 +112,7 @@ config SWAP
>
> config SYSVIPC
> bool "System V IPC"
> + default y
> ---help---
> Inter Process Communication is a suite of library functions and
> system calls which let processes (running programs) synchronize and
>
>
I am running up-to-date Kubuntu Hardy Heron, but...
kevin@alekhine:~/linux/linux-2.6$ grep SYSVIPC .config
# CONFIG_SYSVIPC is not set
What software that would be in a standard install would be broken? I don't seem to notice anything...
Not that I mind the default being changed - I just wonder if things on my box are broken and I just don't know it.
--
Kevin Winchester
next prev parent reply other threads:[~2008-04-24 0:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-23 23:01 [PATCH] Let SYSVIPC default to 'y' Jesper Juhl
2008-04-24 0:00 ` Kevin Winchester [this message]
2008-04-24 0:22 ` Jesper Juhl
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=480FCDA6.6000509@gmail.com \
--to=kjwinchester@gmail.com \
--cc=balasub@cis.ohio-state.edu \
--cc=jesper.juhl@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.org \
--cc=torvalds@linux-foundation.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.