Gentoo Archives: gentoo-user

From: Thanasis <thanasis@××××××××××.org>
To: gentoo-user@l.g.o
Subject: Re: [gentoo-user] Re: best practice for kernel maintenance
Date: Fri, 28 Nov 2008 18:57:08
Message-Id: 49303EFF.4050100@asyr.hopto.org
In Reply to: [gentoo-user] Re: best practice for kernel mainteneance by Nikos Chantziaras
1 on 11/28/2008 07:59 PM Nikos Chantziaras wrote the following:
2 > Thanasis wrote:
3 >> The question is:
4 >> Am I supposed/ should I upgrade when a new source tree becomes stable?
5 >
6 > >From a security point of view, you're supposed to upgrade the kernel
7 > as soon as a release is made upstream. When a security fix is made
8 > upstream, the vulnerability in question has been disclosed and any
9 > machines not updated to that version are considered vulnerable.
10 >
11 > This means that the package will probably be in ~arch in portage and
12 > not marked stable until it's tested for 30 days or more. So
13 > "unstable" (in portage terms) kernels are more secure then stable ones
14 > simply because they're the latest available.
15 >
16 Hmm...OK, let's see...
17
18 # eix --nocolor -l gentoo-sources
19 [U] sys-kernel/gentoo-sources
20 Available versions:
21 (2.6.16-r13)
22 2.6.16-r13 "~alpha amd64 arm ~ia64 ~ppc ~ppc64 s390 sparc
23 x86" [build symlink ultra1]
24 (2.6.20-r10)
25 ~ 2.6.20-r10 "~amd64 ~arm ~ppc ~ppc64 ~s390 ~sparc ~x86"
26 [build symlink]
27 (2.6.22-r10)
28 ~ 2.6.22-r10 "alpha ~amd64 ia64 ~ppc ~ppc64 sparc x86" [build
29 symlink]
30 (2.6.23-r9)
31 2.6.23-r9 "alpha amd64 hppa ia64 ppc ppc64 sparc x86" [build
32 symlink]
33 (2.6.24-r3)
34 2.6.24-r3 "alpha amd64 ~arm hppa ia64 ppc ppc64 ~sh sparc
35 x86" [build symlink]
36 (2.6.24-r4)
37 2.6.24-r4 "~alpha amd64 arm -hppa ia64 ~ppc ~ppc64 ~sh sparc
38 x86" [build symlink]
39 (2.6.24-r8)
40 2.6.24-r8 "alpha amd64 arm -hppa ia64 ~ppc ~ppc64 ~sh sparc
41 x86" [build symlink]
42 (2.6.25)
43 ~ 2.6.25 "~amd64 arm ~sparc ~x86" [build symlink]
44 (2.6.25-r1)
45 ~ 2.6.25-r1 "~alpha ~amd64 arm ~hppa ~ia64 ~ppc ~ppc64 ~sparc
46 ~x86" [build symlink]
47 (2.6.25-r2)
48 ~ 2.6.25-r2 "~alpha ~amd64 arm ~hppa ~ia64 ~ppc ~ppc64 ~sparc
49 ~x86" [build symlink]
50 (2.6.25-r3)
51 ~ 2.6.25-r3 "~alpha ~amd64 arm ~hppa ~ia64 ~ppc ~ppc64 ~sparc
52 ~x86" [build symlink]
53 (2.6.25-r4)
54 ~ 2.6.25-r4 "~alpha ~amd64 arm ~hppa ~ia64 ~ppc ~ppc64 ~sparc
55 ~x86" [build symlink]
56 (2.6.25-r5)
57 ~ 2.6.25-r5 "~alpha ~amd64 arm ~hppa ~ia64 ~ppc ~ppc64 ~sparc
58 ~x86" [build symlink]
59 (2.6.25-r6)
60 [m] 2.6.25-r6 "alpha amd64 arm hppa ia64 ~ppc ~ppc64 sparc
61 x86" [build symlink]
62 (2.6.25-r7)
63 2.6.25-r7 "~alpha amd64 arm hppa ia64 ~ppc ~ppc64 sparc x86"
64 [build symlink]
65 (2.6.25-r8)
66 ~ 2.6.25-r8 "~alpha ~amd64 arm hppa ia64 ~ppc ~ppc64 sparc
67 x86" [build symlink]
68 (2.6.25-r9)
69 ~ 2.6.25-r9 "~alpha ~amd64 arm ~hppa ia64 ~ppc ~ppc64 sparc
70 x86" [build symlink]
71 (2.6.26)
72 ~ 2.6.26 "~alpha ~amd64 ~hppa ~ia64 ~ppc ~ppc64 ~sparc ~x86"
73 [build symlink]
74 (2.6.26-r1)
75 ~ 2.6.26-r1 "~alpha ~amd64 ~hppa ~ia64 ~ppc ~ppc64 ~sparc
76 ~x86" [build symlink]
77 (2.6.26-r2)
78 ~ 2.6.26-r2 "alpha ~amd64 ~arm hppa ia64 ppc ppc64 sparc
79 ~x86" [build symlink]
80 (2.6.26-r3)
81 2.6.26-r3 "~alpha amd64 ~arm ~hppa ~ia64 ~ppc ~ppc64 ~sparc
82 x86" [build symlink]
83 (2.6.27)
84 ~ 2.6.27 "~amd64 ~hppa ~ia64 ~ppc ~ppc64 ~sparc ~x86" [build
85 symlink]
86 (2.6.27-r1)
87 ~ 2.6.27-r1 "~amd64 ~hppa ~ia64 ~ppc ~ppc64 ~sparc ~x86"
88 [build symlink]
89 (2.6.27-r2)
90 ~ 2.6.27-r2 "~amd64 ~arm ~hppa ~ia64 ~ppc ~ppc64 ~sparc ~x86"
91 [build symlink]
92 (2.6.27-r3)
93 ~ 2.6.27-r3 "~amd64 ~arm ~hppa ~ia64 ~ppc ~ppc64 ~sparc ~x86"
94 [build symlink]
95 (2.6.27-r4)
96 ~ 2.6.27-r4 "~amd64 ~arm ~hppa ~ia64 ~ppc ~ppc64 ~sparc ~x86"
97 [build symlink]
98 Installed versions: 2.6.24-r8(2.6.24-r8)(09:42:56 AM
99 08/01/2008)(-build -symlink)
100 Homepage: http://dev.gentoo.org/~dsd/genpatches
101 Description: Full sources including the Gentoo patchset for
102 the 2.6 kernel tree
103 #
104
105 ....Which one should I upgrade to? :-\

Replies

Subject Author
[gentoo-user] Re: best practice for kernel maintenance Nikos Chantziaras <realnc@×××××.de>