On Thursday 28 April 2005 06:20 am, Tamas Sarga
[EMAIL PROTECTED] 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
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
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
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
4 matches
Mail list logo
