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.
