Mailing List Archive

On Thursday 28 April 2005 20:20, Tamas Sarga wrote:
> Hi,
>
> I'd like to do an emerge -e world. It would take 3 days, but I can't
> sleep next to my machine, 'cause of the sound of the 7000RPM CPU cooler.
> If I start an emerge, then C-c it, shutdown, start the PC at morning,
> can I resume the emerge -e?

Sure. emerge --resume. --resume functionality is planned to be improved in the
future. However, at the moment emerging something else will kill the record
of the previous emerge. I usually do a quick manual loop for it like this:

# emerge -ep world | grep ebuild | awk '{print "="substr($0, 17)}' > world
# for x in $(<world); do emerge --oneshot $x && grep -v $x world > world2 &&
mv world2 world || break; done

The second and third lines are one line.

This allows me to stop and emerge something else first if I want to. If
something fails, it also means that I can play around with it until it is
merged without having to use --resume every time. Or you could remove the
"|| break" and have it continue on regardless of failures and you'll have a
list of problems at the end.

Regards,
Jason Stubbs
--
gentoo-user@gentoo.org mailing list

use software suspend2, just put it to sleep when needed - it will take
off again at boot. Much better than "emerge --resume" - especially
after a few hours into openoffice ...

After trialling it on my laptop, Ive even converted my 24/7 gateway over
- can sleep it and restart it faster than a clean boot when needed
(passing thunderstorms, expected power outages etc) A much undervalued
function!

BillK


On Thu, 2005-04-28 at 13:20 +0200, Tamas Sarga wrote:
> Hi,
>
> I'd like to do an emerge -e world. It would take 3 days, but I can't
> sleep next to my machine, 'cause of the sound of the 7000RPM CPU cooler.
> If I start an emerge, then C-c it, shutdown, start the PC at morning,
> can I resume the emerge -e?
>
> TIA.
> Cheers,
> Tamas Sarga Sárga Tamás
> --
> Make the world confused! Zavard össze a világot!
> Smile on monday morning! Mosolyogj hétfõ reggel!
>
--
William Kenworthy <billk@iinet.net.au>
Home!

--
gentoo-user@gentoo.org mailing list

No, 'emerge --resume' is lame. It doesn't do what you're thinking it does.

What you want is:

ebuild <path to last ebuild that was worked on> merge

should do the trick -- at least for the last package that was worked
on. To find the last ebuild that was worked on, check
/var/log/emerge.log... it'll be one of the last lines in the file.

After that, you should be able to just issue the original emerge
command, and it should pick up where it left off.

> -----Original Message-----
> From: Tamas Sarga [mailto:tamas@wansite.homelinux.net]
> Sent: Thursday, April 28, 2005 4:20 AM
> To: gentoo-user@lists.gentoo.org
> Subject: [gentoo-user] resume emerge after reboot
>
> Hi,
>
> I'd like to do an emerge -e world. It would take 3 days, but I can't
> sleep next to my machine, 'cause of the sound of the 7000RPM
> CPU cooler.
> If I start an emerge, then C-c it, shutdown, start the PC at morning,
> can I resume the emerge -e?

--
gentoo-user@gentoo.org mailing list

On Friday 29 April 2005 10:23, Daevid Vincent wrote:
> No, 'emerge --resume' is lame. It doesn't do what you're thinking it does.
>
> What you want is:
>
> ebuild <path to last ebuild that was worked on> merge
>
> should do the trick -- at least for the last package that was worked
> on. To find the last ebuild that was worked on, check
> /var/log/emerge.log... it'll be one of the last lines in the file.
>
> After that, you should be able to just issue the original emerge
> command, and it should pick up where it left off.

This can be dangerous depending on the package you are trying to resume the
compile of. There are also other side-effects of using ebuild (such as
packages not being added to world) that will invariably lead to INVALID bugs.

Regards,
Jason Stubbs
--
gentoo-user@gentoo.org mailing list

On Thursday 28 April 2005 06:20 am, Tamas Sarga
<tamas@wansite.homelinux.net> wrote:
> I'd like to do an emerge -e world. It would take 3 days, but I can't
> sleep next to my machine, 'cause of the sound of the 7000RPM CPU cooler.
> If I start an emerge, then C-c it, shutdown, start the PC at morning,
> can I resume the emerge -e?

Yes, sort of.

emerge --resume will restart the last incomplete emerge with the first
incomplete package. However, the first step in emerging a package is
cleaning up its chroot jail.

So, make sure your C-c is at close to starting a new package as possible to
minimize repetition of work. Or, you could go with the earlier suggestion
and use software suspend. As a 3rd, sort of out-there option you may be
able to C-z the emerge, minimize CPU usage (preferrably zero it), and turn
down or off the CPU fan via ACPI/APM.

Note that the suggestion of not using emerge --resume and simply reissueing
the emerge -e command doesn't work, because of the -e. If it was just a
long emerge -uND world, it would be as valid as the other suggestions.

Other options would be to sleep on the couch, or remove your computer from
the bedroom for those 3 days. ;)

--
Boyd Stephen Smith Jr.
bss03@volumehost.com
ICQ: 514984 YM/AIM: DaTwinkDaddy
--
gentoo-user@gentoo.org mailing list