1 |
Lindsay Haisley posted on Sat, 11 Sep 2010 12:44:06 -0500 as excerpted: |
2 |
|
3 |
> On Fri, 2010-09-10 at 07:02 +0000, Duncan wrote: |
4 |
>> 2.6.32 is the current long-term-stable-support release. If I were |
5 |
>> running my kernels as long as you do, that's what I'd be upgrading to, |
6 |
>> because it'll be supported (and get security and bug patch support in |
7 |
>> further stable releases) for some time yet, not the 2.6.29 that's no |
8 |
>> longer upstream supported. |
9 |
>> |
10 |
>> I'd STRONGLY suggest you do whatever research you might wish to, to |
11 |
>> confirm what I just stated, and then then seriously consider 2.6.32. |
12 |
>> Either that, or go back to 2.6.27, because altho its support is about |
13 |
>> to end (again, unless someone else picks it up), it has been supported |
14 |
>> as a long-term-stable for quite some time now and has a lot more of the |
15 |
>> bugs worked out than 2.6.29 will ever get. |
16 |
> |
17 |
> Well you're right about that. The current portage tree, in fact, has |
18 |
> 2.6.34-r6 as the stable release. |
19 |
> |
20 |
> I run a couple of small businesses, one of which (my music biz) requires |
21 |
> me to periodically do some traveling, so I'm away and pretty busy a lot. |
22 |
> My pattern has been to get my various Gentoo and Ubuntu systems into a |
23 |
> stable state and leave them, especially my desktop, since I'm often |
24 |
> critically strapped for time, and tinkering with Linux gets pushed to a |
25 |
> back burner. |
26 |
> |
27 |
> I'll probably get kernel 2.6.34, update udev, and give it another shot. |
28 |
|
29 |
But note that 2.6.34 isn't a long-term-support kernel either, and will |
30 |
only have a relatively few updates (until shortly after 2.6.36 is |
31 |
released, and it's on rc3 or 4 already...). Given how seldom you change |
32 |
kernels, I expect you really do want the latest long-term-support version, |
33 |
2.6.32. |
34 |
|
35 |
... |
36 |
|
37 |
While leaving updates that long isn't me, I understand how it can be for |
38 |
some users (and have put off updates myself recently, uncharacteristically |
39 |
for me for weeks at a time, for this very reason). The point I was trying |
40 |
to get across is that if you are such a user (and really, regardless, |
41 |
whether you are or not), it's very critical that you read the news items |
42 |
if there are any before doing your updates (portage will tell you so if |
43 |
you do an ask or pretend; you can list and read them using eselect news |
44 |
<whatever>), and that you read and follow-thru on the ewarns, which |
45 |
portage by default displays again after the emerge is finished and which |
46 |
you can configure to be mailed to you or logged, etc, before you consider |
47 |
your upgrade done. If you fail to do so, especially for boot-critical |
48 |
packages like udev, it's not a question of IF, but WHEN, such an update |
49 |
WILL break your system. Unfortunately, you just found that out the hard |
50 |
way. |
51 |
|
52 |
If you don't have time for reading those, you don't have time for the |
53 |
update, because you can't consider it done until you do, and follow thru, |
54 |
and failing to do so is risking spending a lot MORE time figuring out what |
55 |
broke and how to fix it, when things inevitably DO break, because the |
56 |
followups weren't done. As I said, skipping the warnings, it's not a |
57 |
question of if, but when, and just how bad the breakage is going to be and |
58 |
how long it'll take to figure out and resolve the problem, so skipping |
59 |
them really is NOT a viable option. |
60 |
|
61 |
I wish there were some way to really drum this into every Gentoo user's |
62 |
head when they started, so they never ended up having to learn it the hard |
63 |
way, as you did. But as they say, if wishes were fishes... |
64 |
|
65 |
-- |
66 |
Duncan - List replies preferred. No HTML msgs. |
67 |
"Every nonfree program has a lord, a master -- |
68 |
and if you use the program, he is your master." Richard Stallman |