On Fri, Oct 21, 2016 at 13:39:54 CEST wrote Rich Freeman: > On Fri, Oct 21, 2016 at 12:22 PM, Alexander Kapshuk > [...] > > So, if you're staying in the same kernel series (4.4) you should just > be able to run make oldconfig and that's it. You can take a look but > I'd be shocked if you're either prompted for any new settings or if > anything doesn't work exactly as before. You might just be missing a > random patch or two (gentoo-sources doesn't have that many of them). > > Going between kernel series is going to be the same as always, you'll > be asked a dozen questions for new options. > > Now, the one thing you'll lose without the Gentoo options is that if > an openrc/systemd/udev/whatever requirement changes it won't just > automatically get pulled in. You'll need to find out about it and > manually update your config. Regarding this matter I’d like to share my usage here, hoping it would help to avoid the missing-config-entries issue (in short: I patch vanilla upstream myself):
I run vanilla upstream kernels and just pick the patches from genpatches/ gentoo-sources I think I need. Currently mine are: 1500_XATTR_USER_PREFIX.patch 1510_fs-enable-link-security-restrictions-by-default.patch 2900_dev-root-proc-mount-fix.patch 4567_distro-Gentoo-Kconfig.patch 5010_enable-additional-cpu-optimizations-for-gcc.patch My workflow for kernel upgrades there for is - downloading the kernel, checking with GPG signatures - extraction to /usr/src/ - patching the new kernel - copy the old .config - run make nconfig, maybe change something if needed, save and quit - run make and install the rest as usual (maybe create initramfs and other things) Or in short: "cd /usr/src/<fancy-new-kernel>/ && patch -p1 < ../patches/ patches-<kernel-major>/* && cp ../usr/src/<last-used-kernel>/.config .config && make nconfig" That way I have full control over the patches I use and can use *my* config from minor release to minor release without running into any trouble. Maybe I`ll put that stuff into an ebuild…someday.. :P > [...]
signature.asc
Description: This is a digitally signed message part.
