/[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.8 - (show annotations) (download) (as text)
Sat Jan 19 20:59:22 2013 UTC (23 months, 1 week ago) by swift
Branch: MAIN
CVS Tags: HEAD
Changes since 1.7: +3 -5 lines
File MIME type: application/xml
Updates towards quickinstall to match with handbook settings, many thanks to Daniel Meltzer for the patches on gentoo-doc

1 <?xml version='1.0' encoding="UTF-8"?>
2 <!DOCTYPE included SYSTEM "/dtd/guide.dtd">
3 <!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/gentoo-x86-quickinstall-after-reboot.xml,v 1.7 2012/07/24 12:12:51 swift Exp $ -->
4
5 <included>
6
7 <version>7</version>
8 <date>2012-07-24</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>useradd -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/portage/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/portage/make.conf</i>
67 mybox ~ # <i>mirrorselect -i -r -o >> /etc/portage/make.conf</i>
68 <comment>(Usually, (the number of processors + 1) is a good value)</comment>
69 mybox ~ # <i>echo 'MAKEOPTS="-j2"' >> /etc/portage/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/portage/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 fortran, and enable ipv6 and unicode)</comment>
83 mybox ~ # <i>echo 'USE="nptl nptlonly ipv6 -fortran unicode"' >> /etc/portage/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 mybox etc # <i>locale-gen</i>
95 </pre>
96
97 <p>
98 Last but not least, you may want to alter the <c>CFLAGS</c> variable in your
99 <path>/etc/portage/make.conf</path> to optimise the code to your specific needs. Please
100 note that using a long list of flags is rarely needed and can even lead to a
101 broken system. It is recommended to specify the processor type in the
102 <c>march</c> option and stick to <c>-O2 -pipe</c>.
103 </p>
104
105 <p>
106 You may also want to switch to <b>~x86</b>. You should only do this if you can
107 deal with the odd broken ebuild or package. If you'd rather keep your system
108 stable, <e>don't</e> add the <c>ACCEPT_KEYWORDS</c> variable.
109 </p>
110
111 <pre caption="Last edit of make.conf">
112 mybox etc # <i>cd portage</i>
113 mybox portage # <i>nano -w make.conf</i>
114 <comment>(Set -march to your CPU type in CFLAGS)</comment>
115 CFLAGS="-O2 -march=<i>athlon-xp</i> -pipe"
116 <comment>(Only add the following if you know what you're doing)</comment>
117 ACCEPT_KEYWORDS="~x86"
118 </pre>
119
120 <p>
121 You might want to recompile your whole system twice to make full use of your
122 latest configuration changes. It would take quite a long time to complete and
123 yield minimal speed benefits. You can let your system optimise itself gradually
124 over time when new versions of packages are released. However, recompiling is
125 a still good idea from the standpoint of maintaining system consistency. Please
126 see the <uri link="/doc/en/gcc-upgrading.xml">Gentoo GCC Upgrading Guide</uri>
127 for a discussion on the benefits of ensuring a consistently built system and
128 world.
129 </p>
130
131 <p>
132 Recompiling only the packages that have already been updated since the release
133 or that are affected by your new USE flags will take enough time. You might
134 also have to remove packages that block your upgrade. Look for "[blocks
135 <brite>B</brite> ]" in the output of <c>emerge -vpuD --newuse world</c> and
136 use <c>emerge -C</c> to remove them.
137 </p>
138
139 <pre caption="Update your packages">
140 <comment>(Please note that the switch to ~x86 causes many packages to be upgraded)</comment>
141 mybox etc # <i>emerge -vpuD --newuse world</i>
142 <comment>(Take a good look at the package list and their USE flags,
143 remove blocking packages if any, and start the lengthy process)</comment>
144 mybox etc # <i>time emerge -vuD --newuse world</i>
145 <comment>(79 packages have been (re)compiled)</comment>
146
147 real 180m13.276s
148 user 121m22.905s
149 sys 36m31.472s
150
151 <comment>(Remerge libtool to avoid further potential problems)</comment>
152 mybox etc # <i>emerge --oneshot libtool</i>
153
154 <comment>(Update config files, make sure you <b>do not</b> let dispatch-conf
155 update config files you have edited)</comment>
156 mybox etc # <i>dispatch-conf</i>
157
158 <comment>(If perl has been updated, you should run the perl-cleaner script)</comment>
159 mybox etc # <i>time perl-cleaner all</i>
160 real 1m6.495s
161 user 0m42.699s
162 sys 0m10.641s
163
164 <comment>(In case of a major upgrade of python, you should run the python-updater script)</comment>
165 mybox etc # <i>python-updater</i>
166 </pre>
167
168 </body>
169 </section>
170 <section>
171 <title>What to do next</title>
172 <body>
173
174 <p>
175 Depending on what your new Gentoo machine is supposed to do, you will probably
176 want to install server applications or a desktop system. Just as an example,
177 <c>emerge gnome</c> and <c>emerge kde</c> have been timed on the ~x86 system
178 installed as describe above. Both have been installed from the same starting
179 point.
180 </p>
181
182 <p>
183 You should check our <uri link="/doc/en/">documentation index</uri> to find out
184 how to install and configure the applications of your choice.
185 </p>
186
187 <impo>
188 The following is only an example. It is in no way meant as a recommended setup.
189 </impo>
190
191 <pre caption="Emerge GNOME">
192 mybox etc # <i>emerge -vp gnome</i>
193 <comment>(Look at the list of packages and their USE flags,
194 then edit make.conf if required.</comment>
195 mybox etc # <i>nano -w /etc/portage/make.conf</i>
196 <comment>(The following USE flags have been defined)</comment>
197 USE="-fortran dbus -kde -qt4 -eds "
198
199 mybox etc # <i>time emerge gnome</i>
200 <comment>(326 packages have been emerged)</comment>
201
202 real 520m44.532s
203 user 339m21.144s
204 sys 146m22.337s
205 </pre>
206
207 <pre caption="Emerge KDE">
208 mybox etc # <i>emerge -vp kde-meta</i>
209 <comment>(Look at the list of packages and their USE flags,
210 then edit make.conf if required.</comment>
211 mybox etc # <i>nano -w /etc/portage/make.conf</i>
212 <comment>The following USE flags have been defined)</comment>
213 USE="-fortran -eds -gnome -gstreamer -gtk -firefox"
214
215 mybox etc # <i>time emerge kde-meta</i>
216 <comment>(391 packages have been emerged)</comment>
217
218 real 1171m25.318s
219 user 851m26.393s
220 sys 281m45.629s
221 </pre>
222
223 </body>
224 </section>
225
226 </included>

  ViewVC Help
Powered by ViewVC 1.1.20