Linus is reminding people that the #LinuxKernel configuration should "NOT ASK PEOPLE STUIPID THINGS" and is "the most visible interface to NORMAL USERS that we want to encourage to build their own kernels so that they can participate in #kernel development":
https://lore.kernel.org/all/CAHk-%3Dwhigg3hvOy7c1j1MXFy6o6CHp0g4Tc3Y-MAk%[email protected]/
@kernellogger Hmm 🤔
I like what Linus is saying in spirit, but personally I think there's already a tremendous barrier to entry - kconfig asks about thousands of devices and features that normal users aren't familiar with. I suppose it's still worth trying not to make the problem worse than it is, but IMO we are long past the point where kernel configuration could be considered anything approaching user-friendly for all but the most dedicated users.
(this is most assuredly a non-expert opinion)
Thanks for sharing!
@diazona I fully agree, it's really "trying not to make the problem worse" at this point. And I tend to say that's okay, as reducing the number of options might not be time well spend; that time IMHO would be better spend on:
* providing better defaults (like a "make config.generic2026" config for typical systems (maybe based on Debian release from that year and a new one every two years)
* improve "localmodconfig" so that things like "usb-storage" or "kvm" are not disabled accidentally when you haven't used them since boot
* better help texts, as ever I sometimes need some time figuring out what something is about
@kernellogger Yeah that makes a lot of sense. Better defaults in particular would probably help quite a bit with this problem.
I will say, the work that has already been done by the kernel devs to make kconfig usable for moderately technical users really shows. It's far from an ideal system, but it could be (and, in the past, has been) a lot more difficult!
Thorsten Leemhuis (acct. 1/4)
David Zaslavsky