* [gentoo-dev] How to interrupt/resume? @ 2003-04-07 0:59 Paulo da Silva 2003-04-07 1:15 ` Jürgen Nagel ` (2 more replies) 0 siblings, 3 replies; 5+ messages in thread From: Paulo da Silva @ 2003-04-07 0:59 UTC (permalink / raw To: gentoo-dev I am about to give gentoo a try. Because of my relatively slow CPU, I would like to interrupt the compilation process and be able to resume it later. Is there a way to do that? If there are any docs where this is described, pls just tell me how/where to get them. TIA -- gentoo-dev@gentoo.org mailing list ^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [gentoo-dev] How to interrupt/resume? 2003-04-07 0:59 [gentoo-dev] How to interrupt/resume? Paulo da Silva @ 2003-04-07 1:15 ` Jürgen Nagel 2003-04-07 1:32 ` Alec Berryman 2003-04-07 2:10 ` George Shapovalov 2 siblings, 0 replies; 5+ messages in thread From: Jürgen Nagel @ 2003-04-07 1:15 UTC (permalink / raw To: gentoo-dev Paulo da Silva wrote: > I am about to give gentoo a try. > Because of my relatively slow CPU, I would like to interrupt > the compilation process and be able to resume it later. > Is there a way to do that? If there are any docs where this is > described, pls just tell me how/where to get them. > > TIA That should be no problem. In your case I would deviate a bit from the usual procedure. Instead of doing an "emerge system", I'd do an "emerge -vp system" first and then emerge packet by packet. This way you can stop the process at any time and re-enter later by following the installation instructions just without creating the partitions and files. Regards, Juergen -- gentoo-dev@gentoo.org mailing list ^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [gentoo-dev] How to interrupt/resume? 2003-04-07 0:59 [gentoo-dev] How to interrupt/resume? Paulo da Silva 2003-04-07 1:15 ` Jürgen Nagel @ 2003-04-07 1:32 ` Alec Berryman 2003-04-07 2:10 ` George Shapovalov 2 siblings, 0 replies; 5+ messages in thread From: Alec Berryman @ 2003-04-07 1:32 UTC (permalink / raw To: gentoo-dev [-- Attachment #1: Type: text/plain, Size: 599 bytes --] On Sun, 2003-04-06 at 19:59, Paulo da Silva wrote: > I am about to give gentoo a try. > Because of my relatively slow CPU, I would like to interrupt > the compilation process and be able to resume it later. > Is there a way to do that? If there are any docs where this is > described, pls just tell me how/where to get them. There's a function on the newer versions of portage '--resume' that seems to be what you're looking for. Another option is rmerge2, but I've never gotten that to work. -- Alec Berryman <alec@lorax.wox.org> gpg --keyserver pgp.mit.edu --recv-key DFB366F2 [-- Attachment #2: This is a digitally signed message part --] [-- Type: application/pgp-signature, Size: 189 bytes --] ^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [gentoo-dev] How to interrupt/resume? 2003-04-07 0:59 [gentoo-dev] How to interrupt/resume? Paulo da Silva 2003-04-07 1:15 ` Jürgen Nagel 2003-04-07 1:32 ` Alec Berryman @ 2003-04-07 2:10 ` George Shapovalov 2003-04-07 14:00 ` [gentoo-dev] " Paul 2 siblings, 1 reply; 5+ messages in thread From: George Shapovalov @ 2003-04-07 2:10 UTC (permalink / raw To: gentoo-dev As was pointed up above, yes, you can inerrupt and resume builds. To interrupt use... you won't believe me, Ctrl-C at any time ;). Portage registers installed packages (including lists of installed files and a bunch of other information) in the database as it goes along. So, when you run emerge again, it will pick up from the last package it was building. You will have to specifically force rebuild of *all* packages that are required for the one you are emerging if you so desire.. Therefore it is not necessary to emerge system package by package. Though this might be usefull during bootstrap (the precedeeng step), however even in this case it is IMHO easier to modify the script itself.. Now, there is the issue of that last package, that was interrupted. emerge --resume will only restart last emerge command, it will not pick up from where the compilation was interrupted. Instead you should consider using ccache (just emerge it, portage will see and use it. You might want to set CCACHE_DIR though). This will cache all compiles made by gcc, and thus significantly cut duplicated compile time. Also, if you have access to more boxes on a local LAN, you can try using distcc - this will distribute compile tasks to all involved hosts.. George On Sunday 06 April 2003 17:59, Paulo da Silva wrote: > I am about to give gentoo a try. > Because of my relatively slow CPU, I would like to interrupt > the compilation process and be able to resume it later. > Is there a way to do that? If there are any docs where this is > described, pls just tell me how/where to get them. > > TIA -- gentoo-dev@gentoo.org mailing list ^ permalink raw reply [flat|nested] 5+ messages in thread
* [gentoo-dev] Re: How to interrupt/resume? 2003-04-07 2:10 ` George Shapovalov @ 2003-04-07 14:00 ` Paul 0 siblings, 0 replies; 5+ messages in thread From: Paul @ 2003-04-07 14:00 UTC (permalink / raw To: gentoo-dev George Shapovalov <george@gentoo.org>, on Sun Apr 06, 2003 [07:10:42 PM] said: > As was pointed up above, yes, you can inerrupt and resume builds. > To interrupt use... you won't believe me, Ctrl-C at any time ;). > Hi; Or, even better, if you dont have to shutdown, just suspend emerge ( Ctrl-Z usually ). Then later type 'fg' to restart it without loss of state. (assuming bash shell) I do this occasionally if an emerge is sucking too much bandwidth or cpu from something else I want to do at the moment. Paul set@pobox.com -- gentoo-dev@gentoo.org mailing list ^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2003-04-07 14:00 UTC | newest] Thread overview: 5+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 2003-04-07 0:59 [gentoo-dev] How to interrupt/resume? Paulo da Silva 2003-04-07 1:15 ` Jürgen Nagel 2003-04-07 1:32 ` Alec Berryman 2003-04-07 2:10 ` George Shapovalov 2003-04-07 14:00 ` [gentoo-dev] " Paul
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox