[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CA+5PVA5H0merTWq=wAe38m2WPg1_A06saHcST+VUfgkk9OuSOA@mail.gmail.com>
Date: Thu, 7 Feb 2013 08:37:01 -0500
From: Josh Boyer <jwboyer@...il.com>
To: Bruno Wolff III <bruno@...ff.to>
Cc: linux-kernel@...r.kernel.org
Subject: Re: Problems with late 3.8-rc5 and 3.8-rc6 on i686
On Wed, Feb 6, 2013 at 8:52 PM, Bruno Wolff III <bruno@...ff.to> wrote:
> On Fri, Feb 01, 2013 at 14:13:32 -0600,
> Bruno Wolff III <bruno@...ff.to> wrote:
>>
>> I have been testing 3.8 kernels on Fedora. The last good kernel was
>> 3.8.0-0.rc5.git1.1.fc19.i686.PAE. I tested 3.8.0-0.rc5.git2.1.fc19.i686.PAE,
>> 3.8.0-0.rc5.git3.1.fc19.i686 and 3.8.0-0.rc6.git0.1.fc19.i686.PAE and found
>> these all had two odd effects.
>
>
> This turned out to be due Fedora changing some config options to turn off
> namespaces for i686 when it was thought by some people that they had been
> off previously. (And so this wasn't thought to be a change.) This broke the
> private network feature of systemd, used by rtkit-daemon.
Yeah, the Kconfig entry for NAMESPACES is... misleading. It seems it
should depend on CONFIG_EXPERT, but if you have one of the _NS options
set in the config it gets flipped on regardless. It's either that or
the weird "default !EXPERT" causing it to be enabled even when the
CONFIG_EXPERT option is not set.
Anyway, still seems to me that systemd/rtkit-daemon should be _checking_
to see if that feature is present instead of assuming it is and failing
in weird ways when it isn't.
josh
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists