| 1 |
On Tue, 04 May 2004 12:32:20 +1000 |
| 2 |
Jonathan Kelly <jonkelly@××××××××××××.au> wrote: |
| 3 |
> |
| 4 |
> Luckily I had one box that was still running gentoo so I've updated |
| 5 |
> that, after much mucking about. So now, I'd like to build a useable |
| 6 |
> stage1, so started to look at catalyst, but it seems to be have a |
| 7 |
> circular dependency like having a stage3 to start from, but I don't |
| 8 |
> have a stage3 ... huh? |
| 9 |
> |
| 10 |
> If i tared up my complete working system and called that a stage3, |
| 11 |
> would that work ... or anyone in the know who can give me pointers |
| 12 |
> about getting a useable stage1. |
| 13 |
> |
| 14 |
|
| 15 |
Can't you just use a 1.4-r1 stage 3 as the seed stage? I'm not really |
| 16 |
sure I understand the seed stage business, but according to the |
| 17 |
following it doesn't seem to matter too much what version the seed is. |
| 18 |
I'm actually giving this a shot right now, although I might not have |
| 19 |
enough disk space for this. I'll let you know if I come up with |
| 20 |
anything. |
| 21 |
|
| 22 |
>From the gentoo catalyst project page: |
| 23 |
|
| 24 |
Q: I thought that catalyst was able to build stages "from scratch." If |
| 25 |
catalyst builds stages from scratch, then why does it need a "seed |
| 26 |
stage"? |
| 27 |
|
| 28 |
A: Good question. As you know, a stage2 and stage3 are dependent on |
| 29 |
previous stages for building, which is expected and made clear by their |
| 30 |
name (ie. a "stage2" implies that there was a "stage1".) However, |
| 31 |
catalyst does need a seed stage for building a stage1, so in regards to |
| 32 |
building a stage1 it's worth looking into why this is necessary. When |
| 33 |
building a stage1, catalyst uses the seed (stage2 or stage3) to set up a |
| 34 |
chroot environment. Inside the chroot environment, the new stage1 is |
| 35 |
built by setting the ROOT environment variable to /tmp/stage1root. This |
| 36 |
instructs Portage to merge all new packages not to the current |
| 37 |
filesystem, but to the filesystem in /tmp/stage1root. /tmp/stage1root is |
| 38 |
then tarred up and becomes the target stage1. What this means is that |
| 39 |
when catalyst builds a stage1, the stage1 itself does not inherit any |
| 40 |
binaries or libraries from the seed that is used. The seed that is used |
| 41 |
does impact the target stage1 somewhat -- the Linux headers on the seed |
| 42 |
are used for building the stage1's glibc, and the compilers on the seed |
| 43 |
are used to compile all the programs on the stage1. The seed stage is |
| 44 |
used to isolate the stage1 build process from your local system, and |
| 45 |
also allows for x86 stage1s to be built on amd64 systems, for example. |
| 46 |
|
| 47 |
-- |
| 48 |
gentoo-alpha@g.o mailing list |
Archives