diff options
| author | Josh Boyer <jwboyer@redhat.com> | 2013-02-06 11:44:09 -0500 |
|---|---|---|
| committer | Josh Boyer <jwboyer@redhat.com> | 2013-02-06 11:49:05 -0500 |
| commit | f39ad019437fa300f5d2e05ee89154825cae737c (patch) | |
| tree | fc554dc9e8d3cbcd113fd0a35aa545d1a5d76db8 /config-generic | |
| parent | 27e48a69995096472390d6e9a87d58502c88e47f (diff) | |
| download | kernel-f39ad019437fa300f5d2e05ee89154825cae737c.tar.gz kernel-f39ad019437fa300f5d2e05ee89154825cae737c.tar.xz kernel-f39ad019437fa300f5d2e05ee89154825cae737c.zip | |
Enable CONFIG_NAMESPACES everywhere (rhbz 907576)
So apparently we've been enabling CONFIG_NAMESPACES in Fedora kernels for
a very long time even though it was never explicitly set. The kconfig entry
for it looks like it should depend on CONFIG_EXPERT (which isn't set), but
either the fact that we've had CONFIG_NET_NS, etc enabled explicitly or the
fact that it defaults to !EXPERT seems to do something weird with menuconfig
and enables it in the final config. Whatever, just turn it back on. It
seems to break rtkit-daemon for some reason.
Diffstat (limited to 'config-generic')
| -rw-r--r-- | config-generic | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/config-generic b/config-generic index fb1d92b56..200995146 100644 --- a/config-generic +++ b/config-generic @@ -55,7 +55,7 @@ CONFIG_IOSCHED_CFQ=y CONFIG_CFQ_GROUP_IOSCHED=y CONFIG_DEFAULT_CFQ=y # CONFIG_CHECKPOINT_RESTORE is not set -# CONFIG_NAMESPACES is not set +CONFIG_NAMESPACES=y CONFIG_PID_NS=y CONFIG_UTS_NS=y CONFIG_IPC_NS=y |