1 |
On Friday 02 May 2008, Alan McKinnon wrote: |
2 |
> On Friday 02 May 2008, Mark Knecht wrote: |
3 |
> > Before I waste a lot of time I just noticed that I'm using a |
4 |
> > 2007.0 install CD but downloading and setting up a 2008.0 beta2 |
5 |
> > system. Is there any problem building the 2008.0 system files |
6 |
> > using whatever I get when I chroot into the new installation? |
7 |
> > |
8 |
> > At this moment I'm doing the tar xjf portage-latest step and |
9 |
> > noticed the inconsistency. Apparently all the 2007.0 snapshots, |
10 |
> > etc., are now gone from the servers. |
11 |
> |
12 |
> There shouldn't be a problem. Aside from the fact that a LiveCD is |
13 |
> quite a complex thing, as far as installation goes it's sole |
14 |
> purpose is to provide an environment where you can unpack a stage3 |
15 |
> and chroot into it. |
16 |
> |
17 |
> When you have chrooted, you are essentially in a self-contained |
18 |
> environment and all that is left of the original environment is the |
19 |
> kernel it provides. |
20 |
|
21 |
Well, plus all running services/daemons unless you take them down |
22 |
after chrooting and bring them up again within the chroot. |
23 |
|
24 |
This can be a life saver. I have my portage tree on box A while box B |
25 |
NFS mounts it. At one stage, NFS versions of A and B got so out of |
26 |
sync, B couldn't NFS mount /usr/portage any more. A LiveCD with an |
27 |
NFS version matching (well, at least fitting) the one on box A was my |
28 |
path to salvation. ;-) |
29 |
|
30 |
> The build system is provided entirely by the |
31 |
> chroot and nothing in user space can come from or be influenced by |
32 |
> what's outside it (this is the entire point of chroot). |
33 |
|
34 |
This, of course, is absolutely true. |
35 |
|
36 |
Uwe |
37 |
|
38 |
-- |
39 |
Ignorance killed the cat, sir, curiosity was framed! |
40 |
-- |
41 |
gentoo-user@l.g.o mailing list |