1 |
On Thu, 2006-06-01 at 20:28 -0400, Walter Dnes wrote: |
2 |
|
3 |
> 1) How do I resume the build? |
4 |
|
5 |
emerge --resume |
6 |
so long as you can still boot :) which you should be able to. |
7 |
Otherwise, you may have to live-cd, chroot, emerge --resume. |
8 |
DONT do any other emerge commands in between, otherwise it won't know |
9 |
where to resume. |
10 |
|
11 |
> 2) Is it possible to get a list of packages to be built, including the |
12 |
> correct order, so that I can resume manually if necessary? |
13 |
|
14 |
usually a "-p" to the emerge command you want to run will show you the |
15 |
order. If you do reconstruct it by hand, make sure you use "--oneshot" |
16 |
otherwise you'll put lots of entries you don't need into your world |
17 |
file. |
18 |
|
19 |
> 3) A vaguely related item... will it make any noticable difference if |
20 |
> I rebuild my kernel with gcc.3.4.5 and reboot at the end of the process? |
21 |
> I may as well upgrade the entire system. |
22 |
|
23 |
If you've updated the rest of your system to 3.4.5, then do the kernel |
24 |
as well. Especially if you have proprietary modules, like vmware, |
25 |
ati-drivers, etc; or extra modules like ndiswrapper. Make sure you |
26 |
compile these modules after you compile your kernel, but before you |
27 |
reboot. |
28 |
|
29 |
IMHO `emerge -e world` isn't generally necessary to update gcc. Have |
30 |
you read the gcc upgrade howto on the gentoo-wiki? |
31 |
|
32 |
HTH, |
33 |
-- |
34 |
Iain Buchanan <iaindb at netspace dot net dot au> |
35 |
|
36 |
Consider the postage stamp: its usefulness consists in the ability to |
37 |
stick to one thing till it gets there. |
38 |
-- Josh Billings |
39 |
|
40 |
-- |
41 |
gentoo-user@g.o mailing list |