On Fri, 2006-06-02 at 17:44 +0100, Neil Bothwick wrote:
> On Fri, 02 Jun 2006 10:25:11 +0930, Iain Buchanan wrote:
>
> > > 1) How do I resume the build?
> >
> > emerge --resume
> > so long as you can still boot :) which you should be able to.
> > Otherwise, you may have to live-cd, chroot, emer
On Fri, 02 Jun 2006 10:25:11 +0930, Iain Buchanan wrote:
> > 1) How do I resume the build?
>
> emerge --resume
> so long as you can still boot :) which you should be able to.
> Otherwise, you may have to live-cd, chroot, emerge --resume.
> DONT do any other emerge commands in between, otherwise
On Fri, 2006-06-02 at 03:21 +0200, Dave Jones wrote:
> Iain Buchanan wrote on 02/06/06 02:55:
> > On Thu, 2006-06-01 at 20:28 -0400, Walter Dnes wrote:
> >> 3) A vaguely related item... will it make any noticable difference if
> >>I rebuild my kernel with gcc.3.4.5 and reboot at the end of the pro
Iain Buchanan wrote on 02/06/06 02:55:
> On Thu, 2006-06-01 at 20:28 -0400, Walter Dnes wrote:
>> 3) A vaguely related item... will it make any noticable difference if
>>I rebuild my kernel with gcc.3.4.5 and reboot at the end of the process?
>>I may as well upgrade the entire system.
> If you've
Walter Dnes wrote on 02/06/06 02:28:
> I didn't intend to be running the emerge that long, but I wanted to
> try the gcc upgrade on my emergency backup machine first. It's a 1999
> 03:26 EDT. The "emerge -e world" took 36 hours and 37 minutes...
> 1) How do I resume the build?
emerge --resu
On Thu, 2006-06-01 at 20:28 -0400, Walter Dnes wrote:
> 1) How do I resume the build?
emerge --resume
so long as you can still boot :) which you should be able to.
Otherwise, you may have to live-cd, chroot, emerge --resume.
DONT do any other emerge commands in between, otherwise it won't know
6 matches
Mail list logo
