1 |
On Wed, Sep 14, 2011 at 5:16 PM, Dale <rdalek1967@×××××.com> wrote: |
2 |
> Mark Knecht wrote: |
3 |
>> |
4 |
>> On Wed, Sep 14, 2011 at 4:46 PM, Neil Bothwick<neil@××××××××××.uk> wrote: |
5 |
>>> |
6 |
>>> On Wed, 14 Sep 2011 15:37:15 -0700, Mark Knecht wrote: |
7 |
>>> |
8 |
>>>> 3) Do the rest of the work |
9 |
>>>> |
10 |
>>>> emerge -fDuN @world |
11 |
>>>> emerge -pvDuN @world |
12 |
>>>> |
13 |
>>>> Fix USE flag issues, if any |
14 |
>>>> |
15 |
>>>> 4) Do the build |
16 |
>>>> |
17 |
>>>> emerge -DuN -j13 @world |
18 |
>>> |
19 |
>>> There's not point in doing the fetch first, portage has done parallel |
20 |
>>> fetching for some time - it's faster to let the distfiles download while |
21 |
>>> the first package is compiling. |
22 |
>>> |
23 |
>>> emerge -auDN @world covers all of that - except the -j which is |
24 |
>>> system-dependent. |
25 |
>>> |
26 |
>>> |
27 |
>>> -- |
28 |
>>> Neil Bothwick |
29 |
>> |
30 |
>> Quite true about the parallel fetch, but I still do this anyway |
31 |
>> because I want to know all the code is local before I start. With 12 |
32 |
>> processor cores I often build the first file before the second has |
33 |
>> been downloaded. Also I don't want to start a big build, say 50-70 |
34 |
>> updates, and then find out an hour later when I come back that some |
35 |
>> portage mirror choked on finding a specific file and the whole thing |
36 |
>> died 10 minutes in. This way I have a better chance of getting to the |
37 |
>> end in one pass. |
38 |
>> |
39 |
>> Anyway, it works well for this old dog, and in my mind there is a good |
40 |
>> reason to fetch before building but I can see how others might not |
41 |
>> want to do that. |
42 |
>> |
43 |
>> - Mark |
44 |
>> |
45 |
>> |
46 |
> |
47 |
> tail -f /var/log/emerge-fetch.log |
48 |
> |
49 |
> That way you can be compiling and watching the fetching process at the same |
50 |
> time. If something fails, it'll be printer there. I use it all the time |
51 |
> here. I only have 4 cores here tho. :-P |
52 |
> |
53 |
> Dale |
54 |
|
55 |
Nahh, you miss my point. I don't want my attention to be anywhere near |
56 |
the machine except for the 1 minute it takes to run the fetch, and |
57 |
then assuming that worked, for the 1 minute it takes to start the |
58 |
build. I then come back an hour or two later, make sure everything got |
59 |
done and I spent no time of my own fixated on a Gentoo box. Most of |
60 |
these machines get updated during the day when family is away, but I'm |
61 |
busy working here at home and don't want to pay much attention just to |
62 |
get updates done. |
63 |
|
64 |
I know others are way more involved with every little thing happening |
65 |
on their machines but I'm not. I run stable with a few ~amd64 |
66 |
packages. I just want to box to get updated and work without a lot of |
67 |
my time involved. I've done my wife's machine, my father's machine and |
68 |
my mother's machine this way for years and it doesn't take much |
69 |
effort. (It just works... (@tm) |
70 |
|
71 |
On my own 3 Gentoo machines I am a little more involved, but typically |
72 |
I'm working on them while updating so that's not such a bog deal. My |
73 |
attention is there. |
74 |
|
75 |
That said, maybe someone who hasn't touched the machine for 5 months |
76 |
shouldn't try to do a (mostly) unattended update... ;-) |
77 |
|
78 |
- Mark |