1 |
Mike Frysinger <vapier@g.o> posted |
2 |
200709210316.50222.vapier@g.o, excerpted below, on Fri, 21 Sep |
3 |
2007 03:16:49 -0400: |
4 |
|
5 |
> On Friday 21 September 2007, Duncan wrote: |
6 |
>> Mike Frysinger <vapier@g.o> posted |
7 |
>> 200709201234.42152.vapier@g.o, excerpted below, on Thu, 20 Sep |
8 |
>> |
9 |
>> 2007 12:34:41 -0400: |
10 |
>> > we know that someone taking a stage3 has never configured anything |
11 |
>> > before and so we can safely put defaults into /root/. |
12 |
>> |
13 |
>> Just to point out... I've seen people mention overlaying a stage-3 on |
14 |
>> an existing installation for recovery reasons[.] (Whether that's the |
15 |
>> right way to accomplish such recovery isn't the point[.] |
16 |
> |
17 |
> anyone who blindly unpacks a stage3 onto their system gets what they |
18 |
> deserve in my eyes |
19 |
|
20 |
Agreed, but I was trying to stay strictly on target and not go there |
21 |
(thus the whole whether that's the right way to do it is beside the point |
22 |
thing). I was/am just pointing out that the base assumption isn't always |
23 |
correct. |
24 |
|
25 |
If the policy is to be the "you do it, you get to keep the pieces" |
26 |
concept, great, but that's rather different than pretending it won't |
27 |
happen. |
28 |
|
29 |
I'd still rather not see anything going into /root based on principle, |
30 |
but the "only at stage-build time, and if there's something there, don't |
31 |
overwrite it" is IMO a reasonable compromise. (That's quite apart from |
32 |
the question of what package gets the "privilege" of dealing with it; |
33 |
I've no dog in that fight to have an opinion on.) |
34 |
|
35 |
-- |
36 |
Duncan - List replies preferred. No HTML msgs. |
37 |
"Every nonfree program has a lord, a master -- |
38 |
and if you use the program, he is your master." Richard Stallman |
39 |
|
40 |
-- |
41 |
gentoo-dev@g.o mailing list |