/[gentoo]/xml/htdocs/doc/en/gentoo-x86-quickinstall-after-reboot.xml
Gentoo

Contents of /xml/htdocs/doc/en/gentoo-x86-quickinstall-after-reboot.xml

Parent Directory Parent Directory | Revision Log Revision Log


Revision 1.1 - (hide annotations) (download) (as text)
Tue Jan 1 21:32:30 2008 UTC (6 years, 7 months ago) by neysx
Branch: MAIN
File MIME type: application/xml
Use include feature

1 neysx 1.1 <?xml version='1.0' encoding="UTF-8"?>
2     <!-- $Header$ -->
3     <!DOCTYPE included SYSTEM "/dtd/guide.dtd">
4    
5     <included>
6    
7     <version>1</version>
8     <date>2008-01-01</date>
9    
10     <section id="after-reboot">
11     <title>Finalizing the Installation</title>
12     <body>
13    
14     <note>
15     The <b>total</b> elapsed time between the display of the boot prompt on the
16     minimal CD and the display of the login prompt after the reboot was
17     <b>00:42:31</b> on our test box. Yes, less than one hour! Note that this time
18     also includes the stage3, Portage snapshot and several packages download time
19     and the time spent configuring the kernel.
20     </note>
21    
22     <p>
23     Log in as <c>root</c>, then add one or more users for daily use with
24     <c>useradd</c>.
25     </p>
26    
27     <pre caption="Connect to your new box from another PC">
28     <comment>(Clean up your known_hosts file because your new box
29     has generated a new definitive hostkey)</comment>
30     $ <i>nano -w ~/.ssh/known_hosts</i>
31     <comment>(Look for the IP of your new PC and delete the line,
32     then save the file and exit nano)</comment>
33    
34     <comment>(Use the IP address of your new box)</comment>
35     $ <i>ssh root@192.168.1.10</i>
36     The authenticity of host '192.168.1.10 (192.168.1.10)' can't be established.
37     RSA key fingerprint is 96:e7:2d:12:ac:9c:b0:94:90:9f:40:89:b0:45:26:8f.
38     Are you sure you want to continue connecting (yes/no)? <i>yes</i>
39     Warning: Permanently added '192.168.1.10' (RSA) to the list of known hosts.
40     Password: <comment>type_the_password</comment>
41     </pre>
42    
43     <pre caption="Add a new user">
44     mybox ~ # <i>adduser -g users -G lp,wheel,audio,cdrom,portage,cron -m john</i>
45     mybox ~ # <i>passwd john</i>
46     New UNIX password: <comment>Set John's password</comment>
47     Retype new UNIX password: <comment>Type John's password again</comment>
48     passwd: password updated successfully
49     </pre>
50    
51     </body>
52     </section>
53     <section>
54     <title>Last configuration touches</title>
55     <body>
56    
57     <p>
58     Start by selecting nearby mirrors either by defining the <c>SYNC</c> and
59     <c>GENTOO_MIRRORS</c> variables in <path>/etc/make.conf</path> or by using
60     <c>mirrorselect</c>. You can also define the number of concurrent compilation
61     processes at this point.
62     </p>
63    
64     <pre caption="Use mirrorselect and set MAKEOPTS">
65     mybox ~ # <i>emerge mirrorselect</i>
66     mybox ~ # <i>mirrorselect -i -o >> /etc/make.conf</i>
67     mybox ~ # <i>mirrorselect -i -r -o >> /etc/make.conf</i>
68     <comment>(Usually, (the number of processors + 1) is a good value)</comment>
69     mybox ~ # <i>echo 'MAKEOPTS="-j2"' >> /etc/make.conf</i>
70     </pre>
71    
72     <p>
73     Now is a good time to enable or disable some USE flags. Run <c>emerge -vpe
74     world</c> to list all currently installed packages and their enabled and
75     disabled USE flags. Either edit <path>/etc/make.conf</path> or use the
76     following command to define the USE variable:
77     </p>
78    
79     <pre caption="View USE flags in use and enable or disable some">
80     mybox ~ # <i>emerge -vpe world</i>
81     <comment>(Portage displays the packages and their USE flags, as an example, let's
82     disable ipv6 and fortran, and enable unicode)</comment>
83     mybox ~ # <i>echo 'USE="nptl nptlonly -ipv6 -fortran unicode"' >> /etc/make.conf</i>
84     </pre>
85    
86     <p>
87     Recent versions of glibc use <path>/etc/locale.gen</path> to define locale
88     settings.
89     </p>
90    
91     <pre caption="Define locales">
92     mybox ~ # <i>cd /etc</i>
93     mybox etc # <i>nano -w locale.gen</i>
94     </pre>
95    
96     <p>
97     Last but not least, you may want to alter the <c>CFLAGS</c> variable in your
98     <path>/etc/make.conf</path> to optimise the code to your specific needs. Please
99     note that using a long list of flags is rarely needed and can even lead to a
100     broken system. It is recommended to specify the processor type in the
101     <c>march</c> option and stick to <c>-O2 -pipe</c>.
102     </p>
103    
104     <p>
105     You may also want to switch to <b>~x86</b>. You should only do this if you can
106     deal with the odd broken ebuild or package. If you'd rather keep your system
107     stable, don't add the <c>ACCEPT_KEYWORDS</c> variable. Adding
108     <c>FEATURES="parallel-fetch ccache"</c> is also a good idea.
109     </p>
110    
111     <pre caption="Last edit of make.conf">
112     mybox etc # <i>nano -w make.conf</i>
113     <comment>(Set -march to your CPU type in CFLAGS)</comment>
114     CFLAGS="-O2 -march=<i>athlon-xp</i> -pipe"
115     <comment>(Add the following line)</comment>
116     FEATURES="parallel-fetch ccache"
117     <comment>(Only add the following if you know what you're doing)</comment>
118     ACCEPT_KEYWORDS="~x86"
119     </pre>
120    
121     <p>
122     You might want to recompile your whole system twice to make full use of your
123     latest configuration changes. It would take quite a long time to complete and
124     yield minimal speed benefits. You can let your system optimise itself gradually
125     over time when new versions of packages are released. However, recompiling is
126     a still good idea from the standpoint of maintaining system consistency. Please
127     see the <uri link="/doc/en/gcc-upgrading.xml">Gentoo GCC Upgrading Guide</uri>
128     for a discussion on the benefits of ensuring a consistently built system and
129     world.
130     </p>
131    
132     <p>
133     Recompiling only the packages that have already been updated since the release
134     or that are affected by your new USE flags will take enough time. You might
135     also have to remove packages that block your upgrade. Look for "[blocks
136     <brite>B</brite> ]" in the output of <c>emerge -vpuD --newuse world</c> and
137     use <c>emerge -C</c> to remove them.
138     </p>
139    
140     <pre caption="Update your packages">
141     <comment>(Install ccache)</comment>
142     mybox etc # <i>emerge ccache</i>
143    
144     <comment>(Please note that the switch to ~x86 causes many packages to be upgraded)</comment>
145     mybox etc # <i>emerge -vpuD --newuse world</i>
146     <comment>(Take a good look at the package list and their USE flags,
147     remove blocking packages if any, and start the lengthy process)</comment>
148     mybox etc # <i>time emerge -vuD --newuse world</i>
149     <comment>(79 packages have been (re)compiled)</comment>
150    
151     real 180m13.276s
152     user 121m22.905s
153     sys 36m31.472s
154    
155     <comment>(Remerge libtool to avoid further potential problems)</comment>
156     mybox etc # <i>emerge libtool</i>
157    
158     <comment>(Update config files, make sure you <b>do not</b> let etc-update
159     update config files you have edited)</comment>
160     mybox etc # <i>etc-update</i>
161    
162     <comment>(If perl has been updated, you should run the perl-cleaner script)</comment>
163     mybox etc # <i>time perl-cleaner all</i>
164     real 1m6.495s
165     user 0m42.699s
166     sys 0m10.641s
167    
168     <comment>(In case of a major upgrade of python, you should run the python-updater script)</comment>
169     mybox etc # <i>python-updater</i>
170     </pre>
171    
172     </body>
173     </section>
174     <section>
175     <title>What to do next</title>
176     <body>
177    
178     <p>
179     Depending on what your new Gentoo machine is supposed to do, you will probably
180     want to install server applications or a desktop system. Just as an example,
181     <c>emerge gnome</c> and <c>emerge kde</c> have been timed on the ~x86 system
182     installed as describe above. Both have been installed from the same starting
183     point.
184     </p>
185    
186     <p>
187     You should check our <uri link="/doc/en/">documentation index</uri> to find out
188     how to install and configure the applications of your choice.
189     </p>
190    
191     <impo>
192     The following is only an example. It is in no way meant as a recommended setup.
193     </impo>
194    
195     <pre caption="Emerge GNOME">
196     mybox etc # <i>emerge -vp gnome</i>
197     <comment>(Look at the list of packages and their USE flags,
198     then edit make.conf if required.</comment>
199     mybox etc # <i>nano -w /etc/make.conf</i>
200     <comment>(The following USE flags have been defined)</comment>
201     USE="nptl nptlonly -ipv6 -fortran unicode svg hal dbus \
202     -kde -qt3 -qt4 -arts -eds -esd gnome gstreamer gtk firefox"
203    
204     mybox etc # <i>time emerge gnome</i>
205     <comment>(326 packages have been emerged)</comment>
206    
207     real 520m44.532s
208     user 339m21.144s
209     sys 146m22.337s
210     </pre>
211    
212     <pre caption="Emerge KDE">
213     mybox etc # <i>emerge -vp kde-meta</i>
214     <comment>(Look at the list of packages and their USE flags,
215     then edit make.conf if required.</comment>
216     mybox etc # <i>nano -w /etc/make.conf</i>
217     <comment>The following USE flags have been defined)</comment>
218     USE="nptl nptlonly -ipv6 -fortran unicode svg hal dbus \
219     kde qt3 qt4 -arts -eds -esd -gnome -gstreamer -gtk -firefox"
220    
221     mybox etc # <i>time emerge kde-meta</i>
222     <comment>(391 packages have been emerged)</comment>
223    
224     real 1171m25.318s
225     user 851m26.393s
226     sys 281m45.629s
227     </pre>
228    
229     </body>
230     </section>
231    
232     </included>

  ViewVC Help
Powered by ViewVC 1.1.20