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 1Qg8nd-0003Zl-LS for garchives@archives.gentoo.org; Mon, 11 Jul 2011 05:12:56 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 1A32E21C23F for ; Mon, 11 Jul 2011 05:12:52 +0000 (UTC) Received: from mail-gw0-f53.google.com (mail-gw0-f53.google.com [74.125.83.53]) by pigeon.gentoo.org (Postfix) with ESMTP id 08FB021C25C for ; Mon, 11 Jul 2011 05:09:23 +0000 (UTC) Received: by gwj20 with SMTP id 20so1901854gwj.40 for ; Sun, 10 Jul 2011 22:09:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=bvQXAMyvtfWDTsI/BLuCmvS+SHGwZUpQ0rml7DZZ+Ds=; b=VBJS6Oj0IIFkC98ZvyvUWND1IUYbTTJ824qU9d80Q1CHg8AkPHqhhnKw9BWg4MaW3H Yp/8CmgKV1jBtXz09t4mbyltxyGf0t9k8qt2R835isLoTikanqUpo+VGdbA7G7fHP6MS ioxITxMjthVnEvAhi16C4TD5NEqPy7bdlB1PI= Received: by 10.150.159.9 with SMTP id h9mr3743365ybe.18.1310360963504; Sun, 10 Jul 2011 22:09:23 -0700 (PDT) Received: from [192.168.2.5] (adsl-74-240-57-83.jan.bellsouth.net [74.240.57.83]) by mx.google.com with ESMTPS id c63sm4784897yhe.74.2011.07.10.22.09.22 (version=SSLv3 cipher=OTHER); Sun, 10 Jul 2011 22:09:22 -0700 (PDT) Message-ID: <4E1A8581.2070205@gmail.com> Date: Mon, 11 Jul 2011 00:09:21 -0500 From: Dale User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.19) Gecko/20110708 Gentoo/2.0.14-r1 SeaMonkey/2.0.14 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 To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Re: Firefox and kernel panics. References: <4E11EEF3.70804@gmail.com> <4E168B0E.2070100@gmail.com> <201107080702.58452.michaelkintzios@gmail.com> <4E16B251.6080204@gmail.com> <4E16B548.5050105@gmail.com> <4E17B3C3.4010009@gmail.com> <4E187F60.9080400@gmail.com> <4E18ABC3.1090909@orlitzky.com> <4E18C082.4070209@gmail.com> <4E18C977.9070001@orlitzky.com> <4E18D5A7.8040309@gmail.com> <4E18EA55.8030904@gmail.com> <20110710194957.215c37c6@digimed.co.uk> <4E1A0029.7030606@gmail.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Archives-Salt: X-Archives-Hash: d720f2e16395674746015c34df27cf15 walt wrote: > On 07/10/2011 12:40 PM, Dale wrote: > >> Neil Bothwick wrote: >> >>> On Sat, 09 Jul 2011 18:55:01 -0500, Dale wrote: >>> >>> >>> >>>> My old rig was in the middle of a update and we just had a nasty >>>> little thunderstorm here. It was OOo of course. It was 7 hours >>>> into a 9 hour compile when the lights blinked. >>>> >>>> >>> It won't have reached the install stage, so the only filesystem >>> being written to would have been the one holding $PORTAGE_TMPDIR. >>> It would be advisable to restart the emerge though :) >>> >>> >>> >>> >> My deal was the lost compile time. If I had started it about 3 hours >> earlier or the lights would have blinked a few hours later then not >> so much would have been lost. >> > That's when I use ebuild instead of starting the emerge from scratch. > Let's say I'm emerging libreoffice and the machine goes down (shudder). > > After fixing the problem I would try the following: > #cd /usr/portage/app-office/libreoffice/ > #ebuild ./libreoffice-3.3.3.ebuild install > > That should pick up where the previous emerge stopped, although the > patches may be reapplied before continuing the compile/install phase. > > But, hold on. The "install" phase does only a temporary install in > the portage build directory, not the 'real' install in /usr. > > That final step is very easy, though: > > #ebuild ./libreoffice-3.3.3.ebuild qmerge > > For more detail see man ebuild and search on 'qmerge'. Pretty nifty > for situations like yours. Never hurts to use fsck beforehand. even > if the journal was "recovered" during your first reboot after the > disaster. > > > > I just had to do some of that with KDE. Some things were still buggy in the tree. It may work but I won't be needing the machine while it compiles anyway. It's my spare rig. I learned not to let it go to long between updates tho. Funny thing is, I was still trying to dodge storms and update the last KDE. It wasn't even finished with it yet and there is a new release of KDE. I always boot, let it clean up a little then reboot again. If no errors are found, I'm good to go. I've gotten pretty good at cleaning up after a power fail or hard reset. Sort of had some experience here lately. :-( Thanks. Dale :-) :-)