1 |
Hi |
2 |
|
3 |
i am currently trying out catalyst but have run into several questions |
4 |
and problems. |
5 |
|
6 |
1. what gets carried over from a stage1 to stage2 while bootstraping? |
7 |
the faq point out that when seeding a stage3 to create a stage1 the |
8 |
linux-headers of the seed will be used. but nowhere is described what |
9 |
happens when progressing from 1 to 2, and from 2 to 3. |
10 |
|
11 |
2. if nothing from the stage1 gets carried to the stage2 why should i |
12 |
even use anything but the stage1 from a gentoo-mirror? |
13 |
|
14 |
at this point i should possibly point out why i want to use catalyst: |
15 |
|
16 |
i plan to build a stage3 which already includes all packages which i |
17 |
always need. this could be things like gentoo-sources, grub, metalog, |
18 |
fcron. this would mean that the choices that i have already made will be |
19 |
reflected in the stages i use to setup new machines with. i would like |
20 |
to have several different stages for desktop, server and other |
21 |
specialised boxes. the desktop version eg would already contain X, my |
22 |
prefered wm, firefox ... , but this would already be more like a stage4. |
23 |
|
24 |
i also need some way to replace configuration files inside the stages |
25 |
with already modified versions of my current machine. (->6) |
26 |
|
27 |
3. is catalyst intended to create such a stage3/4 or should this rather |
28 |
be done with some seperate scripts? |
29 |
|
30 |
i am uncertain of how i can customise my stages. i think these ways are |
31 |
possible: |
32 |
- modify the profile that is used to build the stage (->4) |
33 |
- when building a livecd options like "livecd/packages" can be used in |
34 |
the spec file. (->5) |
35 |
|
36 |
instead of using /usr/portage/profiles/default-linux/x68/2004.3/ i made |
37 |
a copy of it. i made the copy as a subdir and also as a directory on the |
38 |
same level but both times i got this error: |
39 |
|
40 |
E1. |
41 |
|
42 |
Running command "/bin/bash /usr/lib/catalyst/targets/stage1/stage1.sh run" |
43 |
>>> Regenerating /etc/ld.so.cache... |
44 |
* Caching service dependencies... |
45 |
... |
46 |
|
47 |
** Skipping packages. Run 'fixpackages' or set it in FEATURES to fix the |
48 |
tbz2's in the packages directory. Note: This can take a very long time. |
49 |
!!! ARCH is not set... Are you missing the /etc/make.profile symlink? |
50 |
!!! Is the symlink correct? Is your portage tree complete? |
51 |
|
52 |
i checked the suggested causes for this but didnt find anything unusal. |
53 |
/etc/make.profile does not point to the new profile though. when i use |
54 |
another already profided profile which also isnt symlinked from |
55 |
/etc/make.profile catalyst procedes past this point without any problems. |
56 |
|
57 |
|
58 |
4. how do i create and use my own profile? is this the correct way to |
59 |
costumise a stage? |
60 |
|
61 |
5. why are there no options like "livecd/use" for normal stages? or are |
62 |
they just not listed? |
63 |
|
64 |
6. how are files that are not related to a package, or that replace |
65 |
files profides by a package moved into a stage? is there a spec option |
66 |
for this? |
67 |
|
68 |
7. how is the profile used when building a stage1/2? the following |
69 |
suggests that profile only has an effect on `emerge system`: |
70 |
|
71 |
from /usr/portage/profile/base/packages: |
72 |
OK, you're staring at this file and you have no idea what these stars |
73 |
are for. Here's the scoop. An initial "*" marks a package that is part |
74 |
of the official BASE system profile. If there is a "*" then `emerge |
75 |
system` will use the line in its calculations of what should be |
76 |
installed for the base profile. Lines without a "*" prefix will be |
77 |
ignored for profile system calculations. |
78 |
|
79 |
E2. i sucessfully build a stage1 but when i tried to use it as a seed |
80 |
for a stage2 it turned out it did not contain gcc. i have used the |
81 |
unmodified /usr/portage/default-linux/x86/2004.3/. |
82 |
|
83 |
i added "*>=sys-devel/gcc-3.3.4-r1" to |
84 |
/usr/portage/profiles/default-linux/x86/packages in the hope in getting |
85 |
a stage1 with gcc only to run into another problem. |
86 |
|
87 |
E3. after much copyling finally: |
88 |
|
89 |
Running command "/bin/bash /usr/lib/catalyst/targets/stage1/stage1.sh |
90 |
preclean" |
91 |
i386-pc-linux-gnu-3.3.5 i386-pc-linux-gnu-3.3.5-hardened |
92 |
i386-pc-linux-gnu-3.3.5-hardenednopie i386-pc-linux-gnu-3.3.5-hardenednossp |
93 |
* /usr/bin/gcc-config: Too many arguments! Run /usr/bin/gcc-config |
94 |
without parameters for help. |
95 |
|
96 |
thx ALOT |
97 |
to anyone willing to enlighten me on any of these questions/problems. |
98 |
there is quite a few of them i know... but there is also little |
99 |
documentation :-) |
100 |
|
101 |
h2o |
102 |
|
103 |
|
104 |
ps: accidently i have previously send this message with an unregistered |
105 |
address, but it seams it didnt get through. |
106 |
-- |
107 |
gentoo-catalyst@g.o mailing list |