[gentoo-user] Newb question on handling of kernels and patches in Gentoo
Initially I emerged and used a gentoo-source IIRC kernel which worked perfectly. I then wanted to use the swsusp2 patch to the kernel. emerged a package and in fact it was an entirely new kernel tree with the patches included. The swsusp2 patches in this tree are not at the latest level and I am having problems (kernel oops) with this when suspending. What is the correct way to deinstall this second kernel tree and if possible emerge only the swsusp2 patches (I would know how to do that manually of course). TIA, Bob -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Newb question on handling of kernels and patches in Gentoo
Bob Alexander wrote: Initially I emerged and used a gentoo-source IIRC kernel which worked perfectly. I then wanted to use the swsusp2 patch to the kernel. emerged a package and in fact it was an entirely new kernel tree with the patches included. The swsusp2 patches in this tree are not at the latest level and I am having problems (kernel oops) with this when suspending. What is the correct way to deinstall this second kernel tree and if possible emerge only the swsusp2 patches (I would know how to do that manually of course). You might just need to: echo sys-kernel/suspend2-sources ~x86 /etc/portage/package.keywords That will let you merge kernel 2.6.13 with suspend2 2.2-rc6 patches instead of 2.6.12 with suspend2-2.1.9.9. If you really need suspend2 2.2-rc7, then you can emerge vanilla-sources, then apply the suspend2 patch yourself. You could also try gentoo-sources if you want bootsplash and vesafb-tng, although the suspend2 patches might not apply cleanly to that. The only problem with this is that when you unmerge old kernel sources, emerge will refuse to remove any patched, backup, or object files, so you have to go delete the remaining files manually. But I think you end up having to do that in any case, so this isn't really a problem. -Richard -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Newb question on handling of kernels and patches in Gentoo
A. Khattri wrote: On Wed, 21 Sep 2005, Richard Fish wrote: The only problem with this is that when you unmerge old kernel sources, emerge will refuse to remove any patched, backup, or object files, so you have to go delete the remaining files manually. But I think you end up having to do that in any case, so this isn't really a problem. Doing a make clean in the kernel directory before unmerging should take care of that, no? I think you are correct, if I could ever remember to do it, or if it would annoy me enough to warrant writing a script for it. :-) Cheers, -Richard -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Newb question on handling of kernels and patches in Gentoo
On Wed, 21 Sep 2005, Richard Fish wrote: I think you are correct, if I could ever remember to do it, or if it would annoy me enough to warrant writing a script for it. :-) Since ebuilds have preinstall and postinstall functions, it would be nice if there were preunmerge and postunmerge functions - then it would be easy to re-write the kernel ebuilds to clean up after themselves. (I haven't done any serious ebuild development so this feature may already be there or impossible to implement). -- -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Newb question on handling of kernels and patches in Gentoo
On Wed, 21 Sep 2005 15:55:06 -0400 (EDT), A. Khattri wrote: Since ebuilds have preinstall and postinstall functions, it would be nice if there were preunmerge and postunmerge functions - then it would be easy to re-write the kernel ebuilds to clean up after themselves. Like these? pkg_preinstThe commands in this function are run just prior to merging a package image into the file system. pkg_postinst The commands in this function are run just following merging a package image into the file system. pkg_prerm The commands in this function are run just prior to unmerging a package image from the file system. pkg_postrm The commands in this function are run just following unmerging a package image from the file system. From http://www.gentoo.org/proj/en/devrel/handbook/handbook.xml?part=2chap=1 -- Neil Bothwick An example of hard water is ice. pgpBfPwNIPmH4.pgp Description: PGP signature
Re: [gentoo-user] Newb question on handling of kernels and patches in Gentoo
On Wed, 21 Sep 2005, Neil Bothwick wrote: On Wed, 21 Sep 2005 15:55:06 -0400 (EDT), A. Khattri wrote: Since ebuilds have preinstall and postinstall functions, it would be nice if there were preunmerge and postunmerge functions - then it would be easy to re-write the kernel ebuilds to clean up after themselves. Like these? pkg_preinstThe commands in this function are run just prior to merging a package image into the file system. pkg_postinst The commands in this function are run just following merging a package image into the file system. pkg_prerm The commands in this function are run just prior to unmerging a package image from the file system. pkg_postrm The commands in this function are run just following unmerging a package image from the file system. From http://www.gentoo.org/proj/en/devrel/handbook/handbook.xml?part=2chap=1 The gentoo-sources ebuilds dont seem to override them (for one thing, it could remove modules for the kernel you're unmerging). -- -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Newb question on handling of kernels and patches in Gentoo
On Wed, 21 Sep 2005 18:59:51 -0400 (EDT), A. Khattri wrote: The gentoo-sources ebuilds dont seem to override them (for one thing, it could remove modules for the kernel you're unmerging). The kernel ebuilds only merge/unmerge the source code, they don't handle compiled code, unlike most other ebuilds. I can think of situations where you may want to remove the sources but retain the kernel and modules, but I suppose it would be a nice option (USE=clean?) for those that want it. -- Neil Bothwick Any given program will expand to fill available memory. pgp3BONXXnHH2.pgp Description: PGP signature
