From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1MbCwz-0007eV-E0 for garchives@archives.gentoo.org; Wed, 12 Aug 2009 12:29:05 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 8F343E02C3; Wed, 12 Aug 2009 12:29:03 +0000 (UTC) Received: from dcnode-02.unlimitedmail.net (smtp.unlimitedmail.net [94.127.184.242]) by pigeon.gentoo.org (Postfix) with ESMTP id 3BC49E02C3 for ; Wed, 12 Aug 2009 12:29:03 +0000 (UTC) Received: from ppp.zz ([82.108.46.35]) (authenticated bits=0) by dcnode-02.unlimitedmail.net (8.14.3/8.14.3) with ESMTP id n7CCSuMS014550 for ; Wed, 12 Aug 2009 14:28:56 +0200 From: Etaoin Shrdlu To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Knock on wood Date: Wed, 12 Aug 2009 13:28:53 +0100 User-Agent: KMail/1.11.2 (Linux/2.6.28-15-generic; KDE/4.2.2; x86_64; ; ) References: <7bef1f890908112213r5a7e08a4k7703ca14a9d9bcfb@mail.gmail.com> <20090812091028.GA4887@ca.inter.net> <4A82AADF.70600@gmail.com> In-Reply-To: <4A82AADF.70600@gmail.com> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200908121328.53856.shrdlu@unlimitedmail.org> X-UnlimitedMail-MailScanner-From: shrdlu@unlimitedmail.org X-Spam-Status: No X-Archives-Salt: 31c08420-e7f3-4a6f-8c3c-6108cb410408 X-Archives-Hash: abf6863fde361a037767a3230ab36c5a On Wednesday 12 August 2009 12:43:27 bn wrote: > 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". Keeping the previous (working) kernel, and having a rescue disk around usually is enough to fix most kinds of breakages. Also building binary packages is useful for quickly restored broken packages (FEATURES=buildpkg or something like that in make.conf).