After helping a few 2.6.x users who have problems due to not having emerged the devpts filesystem, I'm wondering why kernel source ebuilds don't include a .config with options enabled? Why should enabling of critical things be in the installation walkthrough? There's no reason for them not to be in the ebuild. The number of things that are *required* don't change *that* often, so it wouldn't be a horrible burden on maintainers. Didn't see a related bug, so posting this general request. Reproducible: Always Steps to Reproduce:
Good idea (for beginners) but me personally, I'd like to have an ebuild strictly for vanilla tree so please add this feature to the gentoo-sources only... Thanks... Radek
I think it actually would be a burden on us (mostly setting it up, maintaining it probably wouldn't be that bad). You also have to understand that the kernel team is horribly understaffed at the moment. Like comment 1 said, a lot of people get really upset when we start adding things to external patchsets or vanilla kernels. The biggest thing is, people don't learn if we do everything for them.
IMO this is what genkernel is supposed to achieve, and even though it is a good idea for the future (setting devfs/udev, ptyfs and so on) it isnt practical. The default config is set quite specifically by the linux kernel team and has always caused flamewars. genkernel will create a config as close as possible to the livecd image, and should work for everyone. If anyone disagrees with me here, im happy to look into a possible implementation, although tbh, it isnt very likely to me supported by many ebuild maintainers and may become quite outdated in favour for genkernel.
I agree with John. The devs have a default config. It's really there choice. Marking as something for upstream.
Closing. The default config won't be changed until 2.7 when devfs is finally removed.
