lkml.org 
[lkml]   [2008]   [Apr]   [23]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [PATCH] Let SYSVIPC default to 'y'
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


\
 
 \ /
  Last update: 2008-04-24 02:03    [W:0.024 / U:0.584 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site