On Wed, Nov 26, 2014 at 12:36:52AM +0100, Richard Weinberger wrote: > systemd has a hard dependency on CONFIG_FHANDLE.
It's been this way for a very long time, why is this suddenly an issue? And what about all of the other systemd kernel requirements, are you ignoring them here? > If you run systemd with CONFIG_FHANDLE=n it will somehow > boot but fail to spawn a getty or other basic services. > As systemd is now used by most x86 distributions it > makes sense to enabled this by default and save kernel > hackers a lot of value debugging time. > > Signed-off-by: Richard Weinberger <rich...@nod.at> > --- > arch/x86/configs/i386_defconfig | 1 + > arch/x86/configs/x86_64_defconfig | 1 + Do these files even make any sense anymore? Who uses them? The distros sure do not... greg k-h -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
