Re: [gentoo-user] best practice for kernel mainteneance
On Friday 28 November 2008 10:41:55 Thanasis wrote: Regarding kernel maintenance, mostly from the point of view of security, which is the best way to go: 1) Having gentoo-sources in /var/lib/portage/world, which would mean the sources would be upgraded whenever portage marks a newer version as stable (provided someone follows stable)? 2) Not having gentoo-sources in /var/lib/portage/world, which would mean the sources would be upgraded only as a dependency for some other package (which is quite improbable/rare)? (or, I may be missing something :-) ) Yes, you are missing the entire point. Every kernel ebuild is in it's own SLOT so an upgrade will never change anything that's already there, it gets an entirely new source tree in /usr/src -- alan dot mckinnon at gmail dot com
Re: [gentoo-user] best practice for kernel mainteneance
On Fri, Nov 28, 2008 at 6:41 AM, Thanasis [EMAIL PROTECTED] wrote: Regarding kernel maintenance, mostly from the point of view of security, which is the best way to go: 1) Having gentoo-sources in /var/lib/portage/world, which would mean the sources would be upgraded whenever portage marks a newer version as stable (provided someone follows stable)? 2) Not having gentoo-sources in /var/lib/portage/world, which would mean the sources would be upgraded only as a dependency for some other package (which is quite improbable/rare)? A good way to be kept informed of new software releases is by mailing list. For vanilla-sources, use [EMAIL PROTECTED] Information (including how to subscribe) at http://vger.kernel.org/majordomo-info.htm For gentoo-sources, use [EMAIL PROTECTED] Information (including how to subscribe) at http://www.gentoo.org/main/en/lists.xml By the way I recommend you to subscribe to the announce lists of all software that matters to you. For example, gentoo-announce (which carries important notices such as glsa notices and new Gentoo releases), gcc-announce, etc. -- Software is like sex: it is better when it is free - Linus Torvalds
Re: [gentoo-user] best practice for kernel mainteneance
Thanasis wrote: Regarding kernel maintenance, mostly from the point of view of security, which is the best way to go: 1) Having gentoo-sources in /var/lib/portage/world, which would mean the sources would be upgraded whenever portage marks a newer version as stable (provided someone follows stable)? 2) Not having gentoo-sources in /var/lib/portage/world, which would mean the sources would be upgraded only as a dependency for some other package (which is quite improbable/rare)? (or, I may be missing something :-) ) This is my opinion and you are welcome to take it with a grain of salt. I rarely upgrade unless I have new hardware that needs it or there is some security thing that affects me. Since I am on dial-up, good luck with the last one. Basically, upgrade when you need to. It may be new hardware that is not in the older kernels, some security issue that affects you or maybe that something will work better with a newer kernel. If what you have works, use it. If you do upgrade, make sure to save your old sources and your old kernel. That way if something does not work with the new kernel, you can boot with the old one until you get things sorted. Don't ask me how I learned this because it brings up bad memories. :-( Just kidding about not asking though it is a bad memory. My $0.02 worth. Dale :-) :-)
Re: [gentoo-user] best practice for kernel mainteneance
on 11/28/2008 12:31 PM Jorge Peixoto de Morais Neto wrote the following: On Fri, Nov 28, 2008 at 6:41 AM, Thanasis [EMAIL PROTECTED] wrote: Regarding kernel maintenance, mostly from the point of view of security, which is the best way to go: 1) Having gentoo-sources in /var/lib/portage/world, which would mean the sources would be upgraded whenever portage marks a newer version as stable (provided someone follows stable)? 2) Not having gentoo-sources in /var/lib/portage/world, which would mean the sources would be upgraded only as a dependency for some other package (which is quite improbable/rare)? A good way to be kept informed of new software releases is by mailing list. For vanilla-sources, use [EMAIL PROTECTED] Information (including how to subscribe) at http://vger.kernel.org/majordomo-info.htm For gentoo-sources, use [EMAIL PROTECTED] Information (including how to subscribe) at http://www.gentoo.org/main/en/lists.xml By the way I recommend you to subscribe to the announce lists of all software that matters to you. For example, gentoo-announce (which carries important notices such as glsa notices and new Gentoo releases), gcc-announce, etc. Just subscribed to gentoo-kernel. :-) Thanks.
Re: [gentoo-user] best practice for kernel mainteneance
on 11/28/2008 10:53 AM Dirk Heinrichs wrote the following: Am Freitag 28 November 2008 09:41:55 schrieb ext Thanasis: Regarding kernel maintenance, mostly from the point of view of security, which is the best way to go: 1) Having gentoo-sources in /var/lib/portage/world, which would mean the sources would be upgraded whenever portage marks a newer version as stable (provided someone follows stable)? 2) Not having gentoo-sources in /var/lib/portage/world, which would mean the sources would be upgraded only as a dependency for some other package (which is quite improbable/rare)? (or, I may be missing something :-) ) Yes. Having the _sources_ upgraded doesn't gain you anything. You have to actually compile a new kernel from them and reboot the system with that new kernel. Do you do this right after every kernel source update? Yes, I always try to do it. I don't. I only do this when it's possible to reboot the machine. Of course. That's the reason why I don't care kernel source upgrades via package manager on any system. Only when it's possible to reboot the machine, I update the kernel sources via git (much faster than installing a complete package), build the new kernel and eventually update all out-of-tree modules via portage/paludis beforehand. HTH... Dirk OK, I'm not acquainted with git... :-\ , but that's another subject. :-)
Re: [gentoo-user] best practice for kernel mainteneance
Am Freitag 28 November 2008 13:47:48 schrieb ext Thanasis: OK, I'm not acquainted with git... :-\ , but that's another subject. :-) I only mentioned it because I find it most convinient for kernel source update. Only one source directory around (no cleanup of old source package needed), easy to switch from one version to another one, fast. Bye... Dirk -- Dirk Heinrichs | Tel: +49 (0)162 234 3408 Configuration Manager | Fax: +49 (0)211 47068 111 Capgemini Deutschland | Mail: [EMAIL PROTECTED] Wanheimerstraße 68 | Web: http://www.capgemini.com D-40468 Düsseldorf | ICQ#: 110037733 GPG Public Key C2E467BB | Keyserver: wwwkeys.pgp.net signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] best practice for kernel mainteneance
Am Freitag 28 November 2008 13:48:15 schrieb ext Thanasis: Am I supposed/ should I upgrade when a new source tree becomes stable? I'd say no, but that's a question that you can only answer yourself, it depend solely on your needs. Bye... Dirk -- Dirk Heinrichs | Tel: +49 (0)162 234 3408 Configuration Manager | Fax: +49 (0)211 47068 111 Capgemini Deutschland | Mail: [EMAIL PROTECTED] Wanheimerstraße 68 | Web: http://www.capgemini.com D-40468 Düsseldorf | ICQ#: 110037733 GPG Public Key C2E467BB | Keyserver: wwwkeys.pgp.net signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] best practice for kernel mainteneance
on 11/28/2008 11:54 AM Alan McKinnon wrote the following: On Friday 28 November 2008 10:41:55 Thanasis wrote: Regarding kernel maintenance, mostly from the point of view of security, which is the best way to go: 1) Having gentoo-sources in /var/lib/portage/world, which would mean the sources would be upgraded whenever portage marks a newer version as stable (provided someone follows stable)? 2) Not having gentoo-sources in /var/lib/portage/world, which would mean the sources would be upgraded only as a dependency for some other package (which is quite improbable/rare)? (or, I may be missing something :-) ) Yes, you are missing the entire point. Every kernel ebuild is in it's own SLOT so an upgrade will never change anything that's already there, it gets an entirely new source tree in /usr/src I knew that. :-) The question is: Am I supposed/ should I upgrade when a new source tree becomes stable?
