On Thu, 2012-07-19 at 13:56 -0400, Josh Boyer wrote: > Distros aren't stationary things.
Exactly my point. > I mean, some of them certainly aim > for that goal, but userspace and kernels get upgraded all the time. So > if this distro-Kconfig file is provided by some package _other_ than the > kernel the distros are going to have a bit of a hassle keeping track of > it. How about a directory called /usr/share/Linux/Kconfig.d/ Then have anything installed that needs to work correctly put in its minimum (must have) requirement configs of the kernel. Say you are running Debian, and decide to try out systemd. If you set up your system to run that it would add a file called: /usr/share/Linux/Kconfig.d/systemd.conf or something, and this would select things like CGROUPS and the like. We could make the kernel build select all, or individual files in this directory. All for the 'make my distro work' or individual for a 'I want part of my distro to work' option. > Upgraded the kernel within the confines of that distro, right? So you > go back to what was already installed and working. You don't go back > arbitrarily far just to see what happens. I would think a reasonably > crafted distro config would work in those scenarios. A reasonable one, but still not the minimum. One issue with Linus's proposal is that he's asking us to focus on the 99%. But the 99% of who? Because 99% of Linux users do not compile their own kernels, so he must be asking about the 99% of Linux users that compile their own kernels. This 99% does not just simply compile their kernels, but only want to compile the absolutely necessary stuff. That is, they want their kernels not to include anything they are not using. A reasonable config would probably need to include a lot that's not used. -- Steve -- 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/
