Re: [gentoo-user] Questions about emerge -e world

2006-06-02 Thread Neil Bothwick
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 it won't know
 where to resume.

That's no longer quite true, at least with portage 2.1. You can now emerge
a single package without disturbing the information used by --resume. If
you emerge a list of packages, then the old resume information is lost.


-- 
Neil Bothwick

File Not Found - Loading something that looks similar


signature.asc
Description: PGP signature


Re: [gentoo-user] Questions about emerge -e world

2006-06-02 Thread Iain Buchanan
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, emerge --resume.
  DONT do any other emerge commands in between, otherwise it won't know
  where to resume.
 
 That's no longer quite true, at least with portage 2.1. You can now emerge
 a single package without disturbing the information used by --resume. If
 you emerge a list of packages, then the old resume information is lost.

cool!
-- 
Iain Buchanan iaindb at netspace dot net dot au

I don't want to live on in my work, I want to live on in my apartment.
-- Woody Allen

-- 
gentoo-user@gentoo.org mailing list



Re: [gentoo-user] Questions about emerge -e world

2006-06-01 Thread Iain Buchanan
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
where to resume.

   2) Is it possible to get a list of packages to be built, including the
 correct order, so that I can resume manually if necessary?

usually a -p to the emerge command you want to run will show you the
order.  If you do reconstruct it by hand, make sure you use --oneshot
otherwise you'll put lots of entries you don't need into your world
file.

   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 updated the rest of your system to 3.4.5, then do the kernel
as well.  Especially if you have proprietary modules, like vmware,
ati-drivers, etc; or extra modules like ndiswrapper.  Make sure you
compile these modules after you compile your kernel, but before you
reboot.

IMHO `emerge -e world` isn't generally necessary to update gcc.  Have
you read the gcc upgrade howto on the gentoo-wiki?

HTH,
-- 
Iain Buchanan iaindb at netspace dot net dot au

Consider the postage stamp: its usefulness consists in the ability to
stick to one thing till it gets there.
-- Josh Billings

-- 
gentoo-user@gentoo.org mailing list



Re: [gentoo-user] Questions about emerge -e world

2006-06-01 Thread Dave Jones
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 --resume

Use emerge --resume if it fails, and emerge --resume --skipfirst to skip
past a failing emerge.

   2) Is it possible to get a list of packages to be built, including the
 correct order, so that I can resume manually if necessary?

emerge -peD world

Why would you need manual intervention?

   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.

Rebuild your kernel with your latest gcc, especially if there have been
gcc ABI changes.  The peace of mind is worth it.

Cheers, Dave
-- 
gentoo-user@gentoo.org mailing list



Re: [gentoo-user] Questions about emerge -e world

2006-06-01 Thread Dave Jones
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 updated the rest of your system to 3.4.5, then do the kernel
 as well.  Especially if you have proprietary modules, like vmware,
 ati-drivers, etc; or extra modules like ndiswrapper.  Make sure you
 compile these modules after you compile your kernel, but before you
 reboot.

VMWare is a problem, it looks at uname, so you can only update it to use
your latest kernel *after* a reboot.  PITA.

nvidia-kernel uses the kernel that symlink /usr/src/linux points to, so
you can re-emerge ndvidia-kernel before a reboot.   YMMV.

Cheers, Dave
-- 
gentoo-user@gentoo.org mailing list



Re: [gentoo-user] Questions about emerge -e world

2006-06-01 Thread Iain Buchanan
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 process?
 I may as well upgrade the entire system.
 
  If you've updated the rest of your system to 3.4.5, then do the kernel
  as well.  Especially if you have proprietary modules, like vmware,
  ati-drivers, etc; or extra modules like ndiswrapper.  Make sure you
  compile these modules after you compile your kernel, but before you
  reboot.
 
 VMWare is a problem, it looks at uname, so you can only update it to use
 your latest kernel *after* a reboot.  PITA.

I assumed to OP was recompiling his kernel, not updating it (if I
rebuild my kernel with gcc.3.4.5).  In which case, vmware can be done
before the reboot.

I would recommend rebuilding with the new gcc, rather than updating and
rebuilding at the same time, cause you may get other issues.  So keeping
to the same kernel will single them to gcc.

-- 
Iain Buchanan iaindb at netspace dot net dot au

QOTD:
Don't let your mind wander -- it's too little to be let out alone.

-- 
gentoo-user@gentoo.org mailing list