public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: bn <brullonulla@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Knock on wood
Date: Thu, 13 Aug 2009 00:06:21 +0100	[thread overview]
Message-ID: <4A834AED.40601@gmail.com> (raw)
In-Reply-To: <2FA4E683-920D-453C-B6E4-3AA7F3F82DF9@stellar.eclipse.co.uk>

Stroller ha scritto:
> 
> On 12 Aug 2009, at 12:43, bn wrote:
>>> ...
>>> Yes, that seems to be the usual reason users leave Gentoo:
>>> like owning a dog, you have to find time to maintain/exercise it.
>>
>> I am starting to be in trouble using Gentoo for this very reason. ...
>>
>> So I am becoming very reluctant in updating critical components -one
>> example is my kernel, which is basically untouched since I installed, in
>> late 2007. I know it's counterproductive, because the more I wait, the
>> worse it is, but it's always a matter of time, and I don't have that
>> time -not to update per se, which I have, but to face problems in case
>> critical updates don't go smooth.
>>
>> Any advice on this kind of situation? I would rather not buy a "backup
>> laptop".
> 
> Don't worry. After you've *once* fallen behind far enough, you won't
> make this mistake again!

LOL, you're scaring me.

> The kernel is the *easiest* part to keep up to date, IMO. You can easily
> reboot & go back to the old one. For me, it's other software packages
> which can become the problem.

Oh no, other packages I more or less regularly update -now I'm just
behind with Xorg 1.5 because of all the horror stories I've heard on
this list.



  reply	other threads:[~2009-08-12 23:14 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-12  5:13 [gentoo-user] Knock on wood Alan E. Davis
2009-08-12  8:38 ` Neil Bothwick
2009-08-12 12:58   ` Dale
2009-08-12  9:10 ` Philip Webb
2009-08-12 11:43   ` bn
2009-08-12 12:13     ` William Kenworthy
2009-08-12 12:28     ` Etaoin Shrdlu
2009-08-12 12:44       ` Ward Poelmans
2009-08-12 12:51         ` Volker Armin Hemmann
2009-08-12 18:34           ` Ward Poelmans
2009-08-12 18:41             ` Volker Armin Hemmann
2009-08-12 15:52         ` bn
2009-08-12 13:37     ` Dale
2009-08-12 13:41       ` Neil Bothwick
2009-08-12 14:20         ` Dale
2009-08-12 18:02           ` Neil Bothwick
2009-08-12 20:19           ` Stroller
2009-08-12 20:36             ` Neil Bothwick
2009-08-12 23:48               ` Dale
2009-08-12 20:58             ` Mike Edenfield
2009-08-12 21:08               ` Volker Armin Hemmann
2009-08-12 21:25                 ` Mike Edenfield
2009-08-12 21:46               ` BRM
2009-08-12 21:59                 ` Neil Bothwick
2009-08-13  3:46                   ` Mike Kazantsev
2009-08-13  7:31                     ` Neil Bothwick
2009-08-14  4:41                       ` Mike Kazantsev
2009-08-14  8:15                         ` Neil Bothwick
2009-08-12 22:07               ` Stroller
2009-08-12 23:43                 ` Neil Bothwick
2009-08-12 13:51       ` Philip Webb
2009-08-12 14:22         ` Dale
2009-08-12 20:01           ` Dan Farrell
2009-08-12 23:54             ` Dale
2009-08-13 17:08               ` Dan Farrell
2009-08-13 19:34                 ` Dale
2009-08-13 19:58                   ` Paul Hartman
2009-08-12 20:17     ` Stroller
2009-08-12 23:06       ` bn [this message]
2009-08-12 23:59         ` Dale
2009-08-12 15:28 ` Paul Hartman
2009-08-19  7:08   ` Keith Dart

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4A834AED.40601@gmail.com \
    --to=brullonulla@gmail.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox