/[gentoo]/xml/htdocs/doc/en/faq.xml
Gentoo

Diff of /xml/htdocs/doc/en/faq.xml

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

Revision 1.68 Revision 1.110
1<?xml version='1.0' encoding="UTF-8"?> 1<?xml version='1.0' encoding="UTF-8"?>
2<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/faq.xml,v 1.68 2004/07/05 11:10:24 neysx Exp $ -->
3<!DOCTYPE guide SYSTEM "/dtd/guide.dtd"> 2<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
4 3
5<guide link="/doc/en/faq.xml"> 4<guide link="/doc/en/faq.xml">
6<title>Gentoo Linux Frequently Asked Questions</title> 5<title>Gentoo Linux Frequently Asked Questions</title>
7<author title="Chief Architect"> 6<author title="Author">
8 <mail link="drobbins@gentoo.org">Daniel Robbins</mail> 7 <mail link="drobbins@gentoo.org">Daniel Robbins</mail>
9</author> 8</author>
10<author title="Reviewer"> 9<author title="Reviewer">
11 Colin Morey 10 Colin Morey
12</author> 11</author>
26 <mail link="peesh@gentoo.org">Jorge Paulo</mail> 25 <mail link="peesh@gentoo.org">Jorge Paulo</mail>
27</author> 26</author>
28<author title="Editor"> 27<author title="Editor">
29 <mail link="swift@gentoo.org">Sven Vermeulen</mail> 28 <mail link="swift@gentoo.org">Sven Vermeulen</mail>
30</author> 29</author>
30<author title="Editor">
31 <mail link="bennyc@gentoo.org">Benny Chuang</mail>
32</author>
33<author title="Editor">
34 <mail link="smithj@gentoo.org">Jonathan Smith</mail>
35</author>
31 36
32<abstract> 37<abstract>
33This FAQ is a collection of questions and answers collected from the gentoo-dev 38This FAQ is a collection of questions and answers collected from the gentoo-dev
34mailing list and from IRC -- if you have any questions (or answers!) to add, 39mailing list and from IRC.
35please contact either an author or a member of the documentation team.
36</abstract> 40</abstract>
37 41
42<!-- The content of this document is licensed under the CC-BY-SA license -->
43<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
38<license/> 44<license/>
39 45
40<version>2.8</version> 46<version>3.9</version>
41<date>July 04, 2004</date> 47<date>2008-02-19</date>
42 48
43<chapter> 49<faqindex>
44<title>Featured Questions</title> 50<title>Questions</title>
45<section> 51<section>
46<title>Getting Started</title> 52<title>Introduction</title>
47<body>
48
49<ul>
50 <li>
51 <uri link="#pronunciation">How is Gentoo pronounced, and what does it
52 mean?</uri>
53 </li>
54 <li>
55 <uri link="#differences">What makes Gentoo different?</uri>
56 </li>
57</ul>
58
59</body> 53<body>
60</section> 54
55<p>
56Please note that many of these questions are answered within the official
57Gentoo documents and guides. This is simply a list of common questions. Please
58read the documentation and/or man pages to gain a greater understanding of how
59Gentoo and GNU/Linux works, and for answers to questions which may not be
60answered here.
61</p>
62
63</body>
61<section> 64</section>
62<title>Installation</title> 65</faqindex>
63<body>
64
65<ul>
66 <li>
67 <uri link="#optimizations">I'm finding things to be really unstable and
68 I'm using "-O9 -ffast-math -fomit-frame-pointer" optimizations. What
69 gives?</uri>
70 </li>
71 <li>
72 <uri link="#password">How can I change the root (or any other user's)
73 password?</uri>
74 </li>
75 <li>
76 <uri link="#useradd">How do I add a normal user?</uri>
77 </li>
78 <li>
79 <uri link="#su">Why can't a user su to root?</uri>
80 </li>
81 <li>
82 <uri link="#devfs">How do I disable devfs?</uri>
83 </li>
84 <li>
85 <uri link="#upgrade">Can I upgrade Gentoo from one release to
86 another without reinstalling?</uri>
87 </li>
88 <li>
89 <uri link="#bootrescue">My kernel doesn't boot (properly), what should
90 I do now?</uri>
91 </li>
92 <li>
93 <uri link="#proxy">My proxy requires authentication, what do I
94 have to do?</uri>
95 </li>
96 <li>
97 <uri link="#isoburning">How do I burn an ISO file?</uri>
98 </li>
99</ul>
100
101</body>
102</section>
103<section>
104<title>Package Management</title>
105<body>
106
107<ul>
108 <li>
109 <uri link="#ebuilds">In what format are the packages stored?</uri>
110 </li>
111 <li>
112 <uri link="#configure">I want to perform the ./configure step myself.
113 Can I?</uri>
114 </li>
115 <li>
116 <uri link="#norsync">What if rsync doesn't work for me?</uri>
117 </li>
118 <li>
119 <uri link="#firewall">How do I use emerge from behind a
120 firewall?</uri>
121 </li>
122 <li>
123 <uri link="#unison">Can I rsync from another operating
124 system?</uri>
125 </li>
126 <li>
127 <uri link="#manualdownload">I have only slow modem connection at home. Can
128 I download sources somewhere else and add them to my system?</uri>
129 </li>
130 <li>
131 <uri link="#distfiles">.tar.gz sources for installed software are
132 piling up in /usr/portage/distfiles using valuable space. Is it safe to
133 delete there files?</uri>
134 </li>
135 <li>
136 <uri link="#tmpportage">What's in /var/tmp/portage? Is it safe to
137 delete the files and directories in /var/tmp/portage?</uri>
138 </li>
139</ul>
140
141</body>
142</section>
143<section>
144<title>Usage</title>
145<body>
146
147<ul>
148 <li>
149 <uri link="#rootssh">I have installed openssh on my box, but can
150 only log in as root - my normal user account doesn't work.</uri>
151 </li>
152 <li>
153 <uri link="#rootX">I can start X applications as root only</uri>
154 </li>
155 <li>
156 <uri link="#intkeyboard">How do I set up an International Keyboard
157 Layout?</uri>
158 </li>
159 <li>
160 <uri link="#rootdns">DNS name resolution works for root only.</uri>
161 </li>
162 <li>
163 <uri link="#crontab">Why can't my user use their own crontab?</uri>
164 </li>
165 <li>
166 <uri link="#numlock">How do I get numlock to start on boot?</uri>
167 </li>
168 <li>
169 <uri link="#clear">How do I have my terminal cleared when I log
170 out?</uri>
171 </li>
172</ul>
173
174</body>
175</section>
176<section>
177<title>Maintenance</title>
178<body>
179
180<ul>
181 <li>
182 <uri link="#filecorruption">ReiserFS and filesystem corruption issues --
183 how to fix'em, etc.</uri>
184 </li>
185 <li>
186 <uri link="#metalogd">Metalogd doesn't log in real time!</uri>
187 </li>
188</ul>
189
190</body>
191</section>
192<section>
193<title>Development</title>
194<body>
195
196<ul>
197 <li>
198 <uri link="#reportbugs">Where can I report bugs?</uri>
199 </li>
200 <li>
201 <uri link="#releases">How often are new releases made?</uri>
202 </li>
203 <li>
204 <uri link="#addfaq">How can I add a question or answer to this
205 FAQ?</uri>
206 </li>
207 <li>
208 <uri link="#beeping">My speaker beeps like crazy while compiling
209 Mozilla. How do I disable console beeps?</uri>
210 </li>
211</ul>
212
213</body>
214</section>
215<section>
216<title>Resources</title>
217<body>
218
219<ul>
220 <li>
221 <uri link="#resources">Where can I find more information about Gentoo
222 Linux?</uri>
223 </li>
224 <li>
225 <uri link="#buycd">Can I buy a CD of Gentoo Linux?</uri>
226 </li>
227 <li>
228 <uri link="#mailinglist">Why, when I hit reply to a post on a Gentoo
229 mailinglist, does my answer only go to the original poster and not the
230 entire list?</uri>
231 </li>
232 <li>
233 <uri link="#help">This FAQ hasn't answered my question. What do I
234 do now?</uri>
235 </li>
236</ul>
237
238</body>
239</section>
240</chapter>
241 66
242<chapter> 67<chapter>
243<title>Getting Started</title> 68<title>Getting Started</title>
244 69
245<section id="pronunciation"> 70<section id="pronunciation">
246<title>How is Gentoo pronounced, and what does it mean?</title> 71<title>How is Gentoo pronounced, and what does it mean?</title>
247<body> 72<body>
248 73
249<p> 74<p>
250A <e>Gentoo</e> is a species of a small, fast penguin, pronounced "gen-too" (the 75<e>Gentoo</e> is pronounced "gen-too" (the "g" in "Gentoo" is a soft "g", as in
251"g" in "gentoo" is a soft "g", as in "gentle"). The latin name of the Gentoo 76"gentle"). The scientific name of the <uri
77link="http://en.wikipedia.org/wiki/Gentoo_penguin">Gentoo penguin</uri> is
252penguin is <e>Pygoscelis papua</e>. The name <e>Gentoo</e> has been given to the 78<e>Pygoscelis papua</e>. The name <e>Gentoo</e> has been given to the penguin
253penguin by the inhabitants of the Falkland Islands. 79by the inhabitants of the <uri
80link="http://en.wikipedia.org/wiki/Falkland_Islands">Falkland Islands</uri>.
254</p> 81</p>
255 82
256</body> 83</body>
257</section> 84</section>
258<section id="differences"> 85<section id="differences">
262<p> 89<p>
263Gentoo uses a BSD ports-like system called <uri 90Gentoo uses a BSD ports-like system called <uri
264link="/proj/en/portage">Portage</uri>. Portage is a package management system 91link="/proj/en/portage">Portage</uri>. Portage is a package management system
265that allows great flexibility while installing and maintaining software on a 92that allows great flexibility while installing and maintaining software on a
266Gentoo system. It provides compile-time option support (through <uri 93Gentoo system. It provides compile-time option support (through <uri
267link="/doc/en/handbook/handbook-x86.xml?part=2&amp;chap=1">USE flags</uri>), 94link="/doc/en/handbook/handbook-x86.xml?part=2&amp;chap=2">USE flags</uri>),
268conditional dependencies, "fake" installs, safe installation (through 95conditional dependencies, pre-package installation summary, safe installation
269sandboxing) and uninstallation of software, system profiles, <uri 96(through sandboxing) and uninstallation of software, system profiles, <uri
270link="/doc/en/handbook/handbook-x86.xml?part=2&amp;chap=4#doc_chap1">configuration 97link="/doc/en/handbook/handbook-x86.xml?part=3&amp;chap=2#doc_chap3">configuration
271file protection</uri> amongst several other <uri 98file protection</uri> amongst several other <uri
272link="/doc/en/handbook/handbook-x86.xml?part=2&amp;chap=3">features</uri>. 99link="/doc/en/handbook/handbook-x86.xml?part=2&amp;chap=1">features</uri>.
273</p>
274
275<p> 100</p>
101
102<p>
276With Gentoo you can build your entire system from source completely using your 103With Gentoo you can build your entire system from source, using your choice of
277choice of optimizations. You have complete control over what packages are or 104optimizations. You have complete control over what packages are or aren't
278aren't installed. Gentoo provides you with numerous choices so you can install 105installed. Gentoo provides you with numerous choices, so you can install Gentoo
279Gentoo to your own taste. This is why Gentoo is called a 106to your own preferences, which is why Gentoo is called a <e>meta-distribution</e>.
280<e>meta-distribution</e>.
281</p>
282
283<p> 107</p>
284Gentoo is very actively developed. Not only the <e>ebuilds</e> themselves (the 108
285package format Gentoo uses) but the entire distribution uses a rapid pace 109<p>
110Gentoo is actively developed. The entire distribution uses a rapid pace
286development style. Patches to the packages are quickly integrated in the 111development style: patches to the packages are quickly integrated in the
287mainline tree, documentation is updated on daily basis, portage features are 112mainline tree, documentation is updated on daily basis, Portage features are
288added frequently, releases succeed each other quickly, ... 113added frequently, and official releases occur twice per year.
289</p> 114</p>
290 115
291</body> 116</body>
292</section> 117</section>
293</chapter> 118</chapter>
294 119
295<chapter> 120<chapter>
296<title>Installation</title> 121<title>Installation</title>
297<section id="optimizations"> 122<section id="optimizations">
298<title> 123<title>
299 I'm finding things to be really unstable and I'm using "-O9 -ffast-math 124 Things are really unstable and I'm using -O9 -ffast-math
300 -fomit-frame-pointer" optimizations. What gives? 125 -fomit-frame-pointer optimizations. What gives?
301</title> 126</title>
302<body> 127<body>
303 128
304<p> 129<p>
305Don't bother using anything higher than <c>-O3</c> since it isn't supported by 130Don't bother using anything higher than <c>-O3</c> since it isn't supported by
307compiler to streamline the assembly code to the point where it doesn't quite 132compiler to streamline the assembly code to the point where it doesn't quite
308do the same thing anymore. 133do the same thing anymore.
309</p> 134</p>
310 135
311<p> 136<p>
312Please try to compile with CFLAGS <c>-march= -O2</c> first before reporting a 137Please try to compile with CFLAGS <c>-O2 -march=&lt;your_arch&gt;</c> before
313bug. 138reporting a bug.
314</p> 139</p>
315 140
316</body> 141</body>
317</section> 142</section>
318<section id="password"> 143<section id="password">
319<title>How can i change the root (or any other user's) password?</title> 144<title>How do I change the root (or any other user's) password?</title>
320<body> 145<body>
321 146
322<p> 147<p>
323You can use <c>passwd</c> to change the password for the user you are logged 148You can use <c>passwd</c> to change the password for the user you are logged
324into. For extra options and setting, please see <c>man passwd</c> once you've 149into. As root, you can change any user password by issuing the command
325completed the install. 150<c>passwd username</c> For extra options and setting, please <c>man passwd</c>.
326</p> 151</p>
327 152
328</body> 153</body>
329</section> 154</section>
330<section id="useradd"> 155<section id="useradd">
331<title>How do i add a normal user?</title> 156<title>How do I add a normal user?</title>
332<body> 157<body>
333 158
334<p>
335The command <c>adduser gentoo</c> will add a user called gentoo. The next step
336is to give this user a password and <c>passwd</c> will do exactly that.
337</p> 159<p>
338 160The command <c>adduser username</c> will add a user called "username". However,
339<p> 161this method does not give the user many of the rights you might want to grant
340Instead of <c>adduser</c> you can also use: 162him, so the following command is preferred:
341</p> 163</p>
342 164
343<pre caption="Using useradd"> 165<pre caption="Using useradd">
344# <i>useradd gentoo -m -G users,audio,wheel -s /bin/bash</i> 166# <i>useradd -m -G users,audio,wheel username</i>
345</pre> 167</pre>
346 168
347<p>
348This will add a user gentoo, will make possible for him/her to use sound-related
349devices (<path>/dev/sound/*</path>), will make possible for him/her to switch to
350root (using <c>su</c>) and will make <path>/bin/bash</path> his/her login shell.
351</p> 169<p>
352 170This will add a user named "username". The option <c>audio</c> adds them to the
353<p> 171<c>audio</c> group and allows the user to access sound devices. The option
354You can also install <c>superadduser</c> using <c>emerge superadduser</c> and 172<c>wheel</c> adds the user to the <c>wheel</c> group, which allows the user to
355then issue <c>superadduser gentoo</c> to add a user called gentoo. Just follow 173execute the command <c>su</c>, which in turn allows them to gain the
356the instructions given to you by <c>superadduser</c>. 174privileges of the <c>root</c> user.
357</p> 175</p>
358 176
359</body> 177</body>
360</section> 178</section>
361<section id="su"> 179<section id="su">
362<title>Why can't a user su to root?</title> 180<title>Why can't a user su to root?</title>
363<body> 181<body>
364 182
365<p> 183<p>
366For security reasons, users may only <c>su</c> to root if they belong to the 184For security reasons, users may only <c>su</c> to root if they belong to the
367<e>wheel</e> group. To add a <e>username</e> to the <e>wheel</e> group, issue 185wheel group. To add a username to the wheel group, issue the following command
368the following command as root: 186as root:
369</p> 187</p>
370 188
371<pre caption="Adding a user to the wheel group"> 189<pre caption="Adding a user to the wheel group">
372# <i>gpasswd -a username wheel</i> 190# <i>gpasswd -a username wheel</i>
373</pre> 191</pre>
374
375</body>
376</section>
377<section id="devfs">
378<title>How to I disable devfs?</title>
379<body>
380
381<p>
382If you plan on using Gentoo with the "old-style" <path>/dev</path> approach, you
383can disable devfs by passing the <c>gentoo=nodevfs</c> to the kernel. If on the
384other hand you want to use <uri link="/doc/en/udev-guide.xml">udev</uri> (2.6
385kernels only), you can disable devfs by passing the <c>devfs=nomount</c> option
386to the kernel. Don't forget to read up on our <uri
387link="/doc/en/udev-guide.xml">udev guide</uri> too.
388</p>
389 192
390</body> 193</body>
391</section> 194</section>
392<section id="upgrade"> 195<section id="upgrade">
393<title> 196<title>
394 Can I upgrade Gentoo from one release to another without reinstalling? 197 Can I upgrade Gentoo from one release to another without reinstalling?
395</title> 198</title>
396<body> 199<body>
397 200
398<p> 201<p>
399In fact there is no difference between the various releases 202In fact, there is no difference between the various releases after they have
400<b>after they have been installed</b>. Gentoo 1.4 and later are 203been installed. Gentoo 1.4 and later are <c>glibc-2.3.x</c> based. As such,
401<c>glibc-2.3.x</c> based. As such running <c>emerge sync; emerge -u world</c> 204running <c>emerge --sync &amp;&amp; emerge -uDN world</c> will bring your
402will bring your entire system up to speed with the "latest Gentoo". 205entire system up to speed with the "latest Gentoo". The differences between
403The true differences between individual releases lie in the installation. 206individual releases lie in the installation medium and pre-compiled packages.
404</p> 207See the <uri link="/doc/en/gentoo-upgrading.xml">Gentoo Upgrading Guide</uri>
405 208for more information about profiles and their role in upgrading.
406<p>
407More information can be found in our <uri link="gentoo-upgrading.xml">Gentoo
408Upgrading Guide</uri>.
409</p> 209</p>
410 210
411</body> 211</body>
412</section> 212</section>
413<section id="bootrescue"> 213<section id="bootrescue">
414<title>My kernel doesn't boot (properly), what should I do now?</title> 214<title>My kernel doesn't boot, what should I do now?</title>
415<body> 215<body>
416 216
417<p> 217<p>
418You don't need to redo every step of the installation, but only the 218You don't need to redo every step of the installation, but investigating the
419kernel-stuff and all associated steps. Suppose you have installed Gentoo 219kernel and all associated steps is necessary. Suppose you have installed Gentoo
420on <path>/dev/hda1</path> (/boot) and <path>/dev/hda3</path> (/) with 220on <path>/dev/hda1</path> (/boot) and <path>/dev/hda3</path> (/) with
421<path>/dev/hda2</path> being the swap space: 221<path>/dev/hda2</path> being the swap space:
422</p> 222</p>
423 223
424<pre caption = "Reconfiguring the kernel"> 224<pre caption = "Reconfiguring the kernel">
425<comment>Boot from the LiveCD and wait until you receive a prompt</comment> 225<comment>Boot from the Install CD and wait until you receive a prompt</comment>
426<comment>We first mount all partitions:</comment> 226<comment>We first mount all partitions:</comment>
427# <i>mount /dev/hda3 /mnt/gentoo</i> 227# <i>mount /dev/hda3 /mnt/gentoo</i>
428# <i>mount /dev/hda1 /mnt/gentoo/boot</i> 228# <i>mount /dev/hda1 /mnt/gentoo/boot</i>
429# <i>swapon /dev/hda2</i> 229# <i>swapon /dev/hda2</i>
430# <i>mount -t proc none /mnt/gentoo/proc</i> 230# <i>mount -t proc none /mnt/gentoo/proc</i>
433# <i>env-update &amp;&amp; source /etc/profile</i> 233# <i>env-update &amp;&amp; source /etc/profile</i>
434# <i>cd /usr/src/linux</i> 234# <i>cd /usr/src/linux</i>
435# <i>make menuconfig</i> 235# <i>make menuconfig</i>
436<comment>Now (de)select anything you have (de)selected wrongly at your</comment> 236<comment>Now (de)select anything you have (de)selected wrongly at your</comment>
437<comment>previous attempt. Then quit and compile your kernel:</comment> 237<comment>previous attempt. Then quit and compile your kernel:</comment>
438# <i>make dep &amp;&amp; make bzImage modules modules_install</i> 238# <i>make &amp;&amp; make modules_install</i>
439<comment>Now copy over your bzImage file, overwriting your previous one:</comment> 239<comment>Now copy over your bzImage file, overwriting your previous one:</comment>
440# <i>cp arch/i386/boot/bzImage /boot</i> 240# <i>cp arch/i386/boot/bzImage /boot/&lt;kernel_name&gt;</i>
441<comment>If you use LILO, rerun lilo -- GRUB users should skip this:</comment> 241<comment>If you use LILO, rerun lilo -- GRUB users should skip this:</comment>
442# <i>/sbin/lilo</i> 242# <i>/sbin/lilo</i>
443<comment>Now exit the chroot and reboot.</comment> 243<comment>Now exit the chroot and reboot.</comment>
444# <i>exit</i> 244# <i>exit</i>
445# <i>umount /mnt/gentoo/proc /mnt/gentoo/boot /mnt/gentoo</i> 245# <i>umount /mnt/gentoo/proc /mnt/gentoo/boot /mnt/gentoo</i>
446# <i>reboot</i> 246# <i>reboot</i>
447</pre> 247</pre>
448 248
449<p> 249<p>
450If on the other hand the problem lays with your bootloader configuration, 250If, on the other hand, the problem lies with your bootloader configuration,
451follow the same steps, but instead of configuring/compiling your kernel you 251follow the same steps, but instead of configuring/compiling your kernel, you
452should reconfigure your bootloader (recompilation isn't necessary). 252should reconfigure your bootloader (recompilation isn't necessary).
453</p> 253</p>
454 254
455</body> 255</body>
456</section> 256</section>
457<section id="proxy"> 257<section id="proxy">
458<title>My proxy requires authentication, what do I have to do?</title> 258<title>My proxy requires authentication, what do I have to do?</title>
459<body> 259<body>
460 260
461<p> 261<p>
462When you have to download something using <c>wget</c>, use the
463following syntax to authenticate yourself:
464</p>
465
466<pre caption = "Proxy-authentication using wget">
467# <i>wget --proxy-user=</i><comment>username</comment><i> --proxy-passwd=</i><comment>password</comment><i> &lt;url&gt;</i>
468</pre>
469
470<p>
471To have Portage automatically use this scheme, define it in 262To have Portage automatically use this scheme, define it in
472<path>/etc/make.conf</path>: 263<path>/etc/make.conf</path>:
473</p> 264</p>
474 265
475<pre caption = "/etc/make.conf"> 266<pre caption = "/etc/make.conf">
476FETCHCOMMAND="wget --proxy-user=<comment>username</comment> --proxy-passwd=<comment>password</comment> -t 5 --passive-ftp -P \${DISTDIR} \${URI}" 267HTTP_PROXY="http://username:password@yourproxybox.org:portnumber"
477RESUMECOMMAND="/usr/bin/wget --proxy-user=<comment>username</comment> --proxy-passwd=<comment>password</comment> -c -t 5 --passive-ftp -P \${DISTDIR} \${URI}" 268FTP_PROXY="ftp://username:password@yourproxybox.org:portnumber"
478</pre> 269RSYNC_PROXY="rsync://username:password@yourproxybox.server:portnumber"
479
480<p>
481Sadly, <c>rsync</c> doesn't seem to support username/password
482authentication for proxies. See <uri link="#doc_chap4_sect3">What
483if rsync doesn't work for me?</uri> for more information on how to
484handle this situation.
485</p> 270</pre>
486 271
487</body> 272</body>
488</section> 273</section>
489<section id="isoburning"> 274<section id="isoburning">
490<title>How do I burn an ISO file?</title> 275<title>How do I burn an ISO file?</title>
491<body> 276<body>
492 277
493<p> 278<p>
494You need to burn the file in so-called <e>raw</e> mode. This means that you 279You need to burn the file in raw mode. This means that you should <e>not</e>
495should <e>not</e> just place the file on the CD, but interpret the file as an 280just place the file on the CD, but interpret the file as an entire CD.
496entire CD.
497</p> 281</p>
498 282
499<p> 283<p>
500There are lots of CD burning tools available; covering them all would be a 284There are lots of CD burning tools available; covering them all would be a
501Sisyphean problem. Describing a few popular tools however doesn't hurt :) 285Sisyphean problem. However, describing a few popular tools never hurts:
502</p> 286</p>
503 287
504<ul> 288<ul>
505 <li> 289 <li>
506 With EasyCD Creator you select <c>File</c>, <c>Record CD 290 With EasyCD Creator you select <c>File</c>, <c>Record CD
508 file</c>. Then locate the ISO file and click <c>Open</c>. When you click on 292 file</c>. Then locate the ISO file and click <c>Open</c>. When you click on
509 <c>Start recording</c> the ISO image will be burned correctly onto the CD-R. 293 <c>Start recording</c> the ISO image will be burned correctly onto the CD-R.
510 </li> 294 </li>
511 <li> 295 <li>
512 With Nero Burning ROM, cancel the wizard which automatically pops up and 296 With Nero Burning ROM, cancel the wizard which automatically pops up and
513 select <c>Burn Image</c> from the <c>Recoder</c> menu. Select the image you 297 select <c>Burn Image</c> from the <c>File</c> menu. Select the image you
514 want to burn and click <c>Open</c>. Now hit the <c>Burn</c> button and watch 298 want to burn and click <c>Open</c>. Now hit the <c>Burn</c> button and watch
515 your brand new CD being burnt. 299 your brand new CD being burnt.
516 </li> 300 </li>
517 <li> 301 <li>
518 With cdrecord, you simply type <c>cdrecord dev=/dev/hdc</c> (replace 302 With cdrecord, you simply type <c>cdrecord dev=/dev/hdc</c> (replace
519 <path>/dev/hdc</path> with your CD-RW drive's device path) followed 303 <path>/dev/hdc</path> with your CD-RW drive's device path) followed
520 by the path to the ISO file :) 304 by the path to the ISO file :)
521 </li> 305 </li>
522 <li> 306 <li>
523 With K3B, select <c>Tools</c> &gt; <c>CD</c> &gt; <c>Burn Image</c>. Then 307 With K3B, select <c>Tools</c> &gt; <c>CD</c> &gt; <c>Burn CD Image</c>.
524 you can locate your ISO file within the 'Image to Burn' area. Finally click 308 Then you can locate your ISO file within the 'Image to Burn' area. Finally
525 <c>Start</c>. 309 click <c>Start</c>.
526 </li> 310 </li>
527 <li> 311 <li>
528 With Mac OS X Panther, launch <c>Disk Utility</c> from 312 With Mac OS X Panther, launch <c>Disk Utility</c> from
529 <path>Applications/Utilities</path>, select <c>Open</c> from the 313 <path>Applications/Utilities</path>, select <c>Open</c> from the
530 <c>Images</c> menu, select the mounted disk image in the main window and 314 <c>Images</c> menu, select the mounted disk image in the main window and
538</ul> 322</ul>
539 323
540 324
541</body> 325</body>
542</section> 326</section>
327<section id="cpus">
328<title>What CD/stage should I use for my CPU?</title>
329<body>
330
331<p>
332First you need to find our what CPU you use. Suppose it's a Pentium-M. Then you
333need to find out what CPU it is, instruction-wise, compatible with. You may
334need to consult the CPU's vendor website for this, although <uri
335link="http://www.google.com">Google</uri> is at least as efficient :-).
336</p>
337
338<p>
339If you are uncertain, take a "lower" CD/stage file, for instance a i686 or even
340generic x86 (or the equivalent in your arch). This will ensure that your system
341will work, but may not be as fast as further optimizations.
342</p>
343
344<p>
345Please note that many more options exist than those for which Gentoo builds
346binary stages. Please see the <uri
347link="http://gcc.gnu.org/onlinedocs/gcc-3.4.4/gcc/i386-and-x86_002d64-Options.html#i386-and-x86_002d64-Options">gcc
348guide</uri> for setting <c>-march</c>.
349</p>
350
351</body>
352</section>
353<section id="dhcp">
354<title>I can't get online after rebooting. What is wrong?</title>
355<body>
356
357<p>
358First you need to check if your network card is discovered properly by the
359kernel. Run <c>ifconfig&nbsp;-a</c> and look for eth0 or wlan0 (in case of
360certain wireless network cards). You might need to load specific kernel modules
361for the kernel to properly detect the network card. If that is the case, make
362sure that these kernel modules are listed in
363<path>/etc/modules.autoload.d/kernel-2.6</path> (or <path>kernel-2.4</path> if
364you are still using a 2.4 kernel).
365</p>
366
367<p>
368If you have forgotten to include support for your network card in your kernel,
369you will need to reconfigure your kernel.
370</p>
371
372<p>
373If your network card is found by your kernel, but you have set your networking
374configuration to use DHCP, you might have forgotten to
375<c>emerge&nbsp;dhcpcd</c>. You will need to reboot with your installation CD to
376install <c>dhcpcd</c>.
377</p>
378
379<p>
380Information on how to rescue your system using the installation CD is <uri
381link="#bootrescue">available</uri> as well.
382</p>
383
384</body>
385</section>
386<section id="dualboot">
387<title>
388I want to boot Windows from grub or lilo but it shows only black screen. What
389should I do?
390</title>
391<body>
392
393<p>
394This is a known problem. Windows refuses to boot when it isn't installed on the
395first hard drive and shows a black/blank screen. To handle this, you will have
396to "fool" Windows into believing that it is installed on the first hard drive
397with a little tweak in your boot loader configuration. Please note that in the
398below example, Gentoo is installed on <path>hda</path> (first disk) and Windows
399on <path>hdb</path> (second one). Adjust your config as needed.
400</p>
401
402<pre caption="Example dual boot entry for Windows in grub.conf">
403title Windows XP
404 map (hd1) (hd0)
405 map (hd0) (hd1)
406 rootnoverify (hd1,0)
407 chainloader +1
408</pre>
409
410<pre caption="Example dual boot entry for Windows in lilo.conf">
411other=/dev/hdb1
412 label=WindowsXP
413 table=/dev/hdb
414 map-drive = 0x80
415 to = 0x81
416 map-drive = 0x81
417 to = 0x80
418</pre>
419
420<p>
421This will make Windows believe it is installed on the first hard drive and boot
422without problems. More information can be found in the <uri
423link="http://www.gnu.org/software/grub/manual/html_node/DOS_002fWindows.html">GRUB
424documentation</uri> and in <c>man lilo.conf</c>, depending on the boot loader
425you're using.
426</p>
427
428</body>
429</section>
430<section id="stage12">
431<title>How do I Install Gentoo Using a Stage1 or Stage2 Tarball?</title>
432<body>
433
434<p>
435The Gentoo Handbook only describes a Gentoo installation using a stage3 tarball.
436However, Gentoo still provides stage1 and stage2 tarballs. This is for
437development purposes (the Release Engineering team starts from a stage1 tarball
438to obtain a stage3) but shouldn't be used by users: a stage3 tarball can very
439well be used to bootstrap the system. You do need a working Internet connection.
440</p>
441
442<p>
443Bootstrapping means building the toolchain (the C library and compiler) for
444your system after which you install all core system packages. To bootstrap the
445system, perform a stage3 installation. Before you start the chapter on
446<e>Configuring the Kernel</e>, modify the <path>bootstrap.sh</path> script to
447suit your needs and then run it:
448</p>
449
450<pre caption="Bootstrapping the system">
451# <i>cd /usr/portage/scripts</i>
452# <i>vi bootstrap.sh</i>
453
454# <i>./bootstrap.sh</i>
455</pre>
456
457<p>
458Next, rebuild all core system packages with the newly built toolchain. We need
459to rebuild them since the stage3 tarball already offers them:
460</p>
461
462<pre caption="Rebuilding the core system packages">
463# <i>emerge -e system</i>
464</pre>
465
466<p>
467Now you can continue with <e>Configuring the Kernel</e>. You can not use the
468prebuilt GRP packages anymore though.
469</p>
470
471</body>
472</section>
543</chapter> 473</chapter>
544 474
545<chapter> 475<chapter>
546<title>Package Management</title> 476<title>Package Management</title>
547<section id="ebuilds"> 477<section id="ebuilds">
548<title>In what format are the packages stored?</title> 478<title>In what form are the packages stored?</title>
549<body> 479<body>
550 480
481<p>
482Packages aren't "stored" per se. Instead, Gentoo provides a set of scripts
483which can resolve dependencies, fetch source code, and compile a version of the
484package specifically for your needs. We generally only build binaries for
485releases and snapshots. The <uri
486link="/proj/en/devrel/handbook/handbook.xml?part=2&amp;chap=1">Gentoo Ebuild
487HOWTO</uri> covers the contents of an ebuild script in detail.
551<p> 488</p>
552They exist in our portage tree as <e>ebuild</e> autobuild scripts; Gentoo is 489
553primarily a ports-based distribution, meaning that we provide scripts 490<p>
554(<c>.ebuild</c> files) and a special system (Portage) so that you can build 491For full ISO releases, we create a full suite of binary packages in an enhanced
555apps from sources. We generally only build binaries for releases and snapshots. 492<c>.tbz2</c> format, which is <c>.tar.bz2</c> compatible with meta-information
556The <uri link="/doc/en/gentoo-howto.xml">Development HOWTO</uri> covers the 493attached to the end of the file. These can be used to install a working (though
557contents of an ebuild script in detail. For full binary ISO releases, we 494not fully optimized) version of the package quickly and efficiently.
558create a full suite of binary packages in an enhanced <c>.tbz2</c> format 495</p>
559(<c>.tar.bz2</c> compatible with meta-information attached to the end of the 496
560file). 497<p>
498It is possible to create RPMs (Redhat package manager files) using Gentoo's
499Portage, but it is not currently possible to use already existing RPMs to
500install packages.
561</p> 501</p>
562 502
563</body> 503</body>
564</section> 504</section>
565<section id="configure"> 505<section id="configure">
566<title>I want to perform the ./configure step myself. Can I?</title> 506<title>I want to perform the ./configure step myself. Can I?</title>
507<body>
508
509<p>
510Yes, but it is not trivial, nor is it recommended. Since the method to do this
511requires a good understanding of Portage internals and commands, it is instead
512recommended that you patch the ebuild to do whatever it is that you want and
513place it in a Portage overlay (that's why overlays exist). This is <e>much</e>
514better for maintainability, and usually easier. See the <uri
515link="/proj/en/devrel/handbook/handbook.xml?part=2&amp;chap=1">Ebuild
516HOWTO</uri> for more information.
517</p>
518
567<body> 519</body>
520</section>
521<section id="firewall">
522<title>How do I use emerge from behind a firewall?</title>
523<body>
568 524
569<p>
570Yes, but it is not trivial, and the next method only works when it is a simple
571ebuild (i.e. just <c>./configure</c> and <c>make &amp;&amp; make install</c>).
572Be sure to read the ebuild itself to see how Gentoo handles it.
573</p> 525<p>
574 526See the questions on <uri link="#proxy">proxies</uri>, <uri
575<p> 527link="#norsync">rsync</uri>, and <uri link="#manualdownload">downloading source
576Start with unpacking the ebuild: <c>ebuild 528files manually</uri>.
577/usr/portage/&lt;category&gt;/&lt;package&gt;/&lt;ebuild&gt; unpack</c>.
578</p>
579
580<p>
581Next, go to <path>/var/tmp/portage/&lt;package&gt;-&lt;version&gt;/work</path>.
582Inside it you'll find the unpacked sources. Execute the steps you need to
583perform to configure and compile the package.
584</p>
585
586<p>
587When finished, execute <c>touch
588/var/tmp/portage/&lt;package&gt;-&lt;version&gt;/.compiled</c> to trick Portage
589into thinking it configured and compiled the package. Then finish up with
590<c>ebuild /usr/portage/&lt;category&gt;/&lt;package&gt;/&lt;ebuild&gt;
591merge</c>.
592</p> 529</p>
593 530
594</body> 531</body>
595</section> 532</section>
596<section id="norsync"> 533<section id="norsync">
598<body> 535<body>
599 536
600<p> 537<p>
601If you're behind a firewall that doesn't permit rsync traffic, then you can use 538If you're behind a firewall that doesn't permit rsync traffic, then you can use
602<c>emerge-webrsync</c> which will fetch and install a Portage snapshot for you 539<c>emerge-webrsync</c> which will fetch and install a Portage snapshot for you
603through regular HTTP. <c>emerge-webrsync</c> uses <c>wget</c> to download, so 540through regular HTTP. See the <uri link="#proxy">proxy section</uri> of this
604proxy is fully supported. 541document for information on downloading source files and Portage snapshots via
605</p> 542a proxy.
606
607<pre caption="Using emerge-webrsync">
608# <i>emerge-webrsync</i>
609</pre>
610
611</body>
612</section>
613<section id="firewall">
614<title>How do I use emerge from behind a firewall?</title>
615<body>
616
617<p>
618Edit the PROXY settings in <path>/etc/make.conf</path>. If that doesn't work,
619edit <path>/etc/wget/wgetrc</path> and edit http_proxy and ftp_proxy
620appropriately.
621</p>
622
623</body>
624</section>
625<section id="unison">
626<title>Can I rsync from another operating system?</title>
627<body>
628
629<p>
630There's a program called unison that works under both UNIX and Win32, available
631from <uri>http://www.cis.upenn.edu/~bcpierce/unison/</uri>.
632</p> 543</p>
633 544
634</body> 545</body>
635</section> 546</section>
636<section id="manualdownload"> 547<section id="manualdownload">
643<p> 554<p>
644Definitely. You can run <c>emerge --pretend package</c> to see what programs 555Definitely. You can run <c>emerge --pretend package</c> to see what programs
645are going to be installed. To find out the sources for those packages and where 556are going to be installed. To find out the sources for those packages and where
646to download the sources from, you can run <c>emerge -fp package</c>. Download 557to download the sources from, you can run <c>emerge -fp package</c>. Download
647sources and bring them on any media home. Put the sources into 558sources and bring them on any media home. Put the sources into
648<path>/usr/portage/distfiles</path> and run <c>emerge package</c> to see it 559<path>/usr/portage/distfiles/</path> and then simply run <c>emerge package</c>.
649picking up the sources you just brought in! 560Be warned, however, that this is a tedious process.
650</p> 561</p>
651 562
652</body> 563</body>
653</section> 564</section>
654<section id="distfiles"> 565<section id="distfiles">
655<title> 566<title>
656 .tar.gz sources for installed software are piling up in 567 Source tarballs are collecting in /usr/portage/distfiles/. Is it safe to
657 /usr/portage/distfiles/ using valuable space. Is it safe to delete these 568 delete these files?
658 files?
659</title> 569</title>
660<body> 570<body>
661 571
662<p> 572<p>
663Yes, you can safely delete these files. But if you are on a slow 573Deleting these files will have no negative impact on day-to-day performance.
664connection, such as a modem, you might want to keep the archives if 574However, it might be wise to keep the most recent version of the files; often
665possible; often several ebuilds will be released for the same version of 575several ebuilds will be released for the same version of a specific piece of
666a specific piece of software - if you have deleted the archive and you 576software. If you have deleted the archive and you upgrade the software it will
667upgrade the software it will have to be downloaded from the internet 577be necessary to download them from the internet again. There are programs which
668again. 578<uri link="http://forums.gentoo.org/viewtopic-t-337074.html">users have
579developed</uri> to clean out all but the most recent version of sourcefiles.
580Note that while this seems to work, it is <e>not</e> officially maintained. Use
581at your own risk.
669</p> 582</p>
670 583
671</body> 584</body>
672</section> 585</section>
673<section id="tmpportage"> 586<section id="tmpportage">
677</title> 590</title>
678<body> 591<body>
679 592
680<p> 593<p>
681During compilation, Gentoo saves the sources of the package in 594During compilation, Gentoo saves the sources of the package in
682<path>/var/tmp/portage</path>. It is safe to clean out all contents of this 595<path>/var/tmp/portage</path>. These files and folder are usually deleted upon
683directory. 596a successful merge, but this sometimes fails. It is safe to clean out all
597contents of this directory <e>if</e> emerge is not running. Just to be sure,
598always <c>pgrep emerge</c> before cleaning out this directory.
684</p> 599</p>
685 600
686</body> 601</body>
687</section> 602</section>
688</chapter> 603</chapter>
689 604
690<chapter> 605<chapter>
691<title>Usage</title> 606<title>Usage</title>
692<section id="rootssh">
693<title>
694 I have installed openssh on my box, but can only log in as root - my normal
695 user account doesn't work.
696</title>
697<body>
698
699<p>
700This is most probably because your user account doesn't have a valid shell
701specified. Check for your user entry in <path>/etc/passwd</path> and see if it
702ends in /bin/bash (or any other shell). If it doesn't, you must set a shell for
703the user. This is done using the usermod command, like this:
704</p>
705
706<pre caption="Using usermod">
707# <i>usermod -s /bin/bash myuser</i>
708</pre>
709
710</body>
711</section>
712<section id="rootX">
713<title>I can start X applications as root only.</title>
714<body>
715
716<p>
717Your <path>/tmp</path> directory has the wrong permissions (it needs the
718sticky bit set). Type the following as root:
719</p>
720
721<pre caption="Changing /tmp permissions">
722# <i>chmod 1777 /tmp</i>
723</pre>
724
725</body>
726</section>
727<section id="intkeyboard"> 607<section id="intkeyboard">
728<title>How do I set up an International Keyboard Layout?</title> 608<title>How do I set up an International Keyboard Layout?</title>
729<body> 609<body>
730 610
731<p> 611<p>
732Edit the <c>KEYMAP</c> variable in <path>/etc/rc.conf</path>. 612Edit the <c>KEYMAP</c> variable in <path>/etc/conf.d/keymaps</path>. To have
613console working correctly with extended characters in your keymap you might
614also need to set up variables <c>CONSOLETRANSLATION</c> and <c>CONSOLEFONT</c>
615in your <path>/etc/conf.d/consolefont</path> (for further information on
616localising your environment, refer to <uri
617link="/doc/en/guide-localization.xml">our localisation guide</uri>).
733Then either reboot or restart the keymaps script: 618Then, either <c>reboot</c>, or restart the keymaps and consolefont scripts:
619</p>
620
621<pre caption="Restarting keymaps">
734<c>/etc/init.d/keymaps restart</c>. 622# <i>/etc/init.d/keymaps restart</i>
623# <i>/etc/init.d/consolefont restart</i>
735</p> 624</pre>
736 625
737</body> 626</body>
738</section> 627</section>
739<section id="rootdns"> 628<section id="rootdns">
740<title>DNS name resolution works for root only.</title> 629<title>DNS name resolution works for root only</title>
741<body> 630<body>
742 631
743<p> 632<p>
744<path>/etc/resolv.conf</path> has the wrong permissions; <c>chmod</c> it as 633<path>/etc/resolv.conf</path> has the wrong permissions; <c>chmod</c> it as
745follows: 634follows:
764<section id="numlock"> 653<section id="numlock">
765<title>How do I get numlock to start on boot?</title> 654<title>How do I get numlock to start on boot?</title>
766<body> 655<body>
767 656
768<p> 657<p>
769If you log on graphically, or want numlock to be activated when
770you issue <c>startx</c>, then you must <c>emerge numlockx</c> and
771add <c>/usr/X11R6/bin/numlockx</c> to
772<path>/etc/X11/xinit/xinitrc</path> (for <c>startx</c>) or
773<path>/etc/X11/Sessions/</path> (for any graphical login manager) such
774as <path>/etc/X11/Sessions/Gnome</path> for GDM.
775</p>
776
777<p>
778GNOME 2.6 users however will notice that this doesn't work. Instead, they will
779need to start the <c>gnome-session-properties</c> tool. At the top of the
780Window, select <c>Startup Programs</c> and click the <c>Add</c> button. Now
781insert the location of the <c>numlockx</c> tool (for instance
782<path>/usr/X11R6/bin/numlockx</path>) and exit.
783</p>
784
785<p>
786If you work in commandline, you only need to <c>rc-update add 658If you work in command line, you only need to <c>rc-update add
787numlock default</c> and numlock will be activated on the next 659numlock default &amp;&amp;/etc/init.d/numlock start</c>.
788reboot. 660</p>
661
662<p>
663Each GUI provides different tools for this sort of thing; please check the help
664section or online manuals for assistance.
789</p> 665</p>
790 666
791</body> 667</body>
792</section> 668</section>
793<section id="clear"> 669<section id="clear">
810 686
811<pre caption = "Making new users their terminal clear on logout"> 687<pre caption = "Making new users their terminal clear on logout">
812# <i>echo clear &gt;&gt; /etc/skel/.bash_logout</i></pre> 688# <i>echo clear &gt;&gt; /etc/skel/.bash_logout</i></pre>
813</body> 689</body>
814 690
691</section>
692<section id="suinx">
693<title>I'm not able to run X applications as root after su'ing</title>
694<body>
695
696<p>
697This issue seems only to occur when you log on graphically. <c>startx</c> users
698don't have this behaviour. The problem is a <uri
699link="http://bugs.gentoo.org/show_bug.cgi?id=14560">bug</uri> in Gentoo's PAM,
700the solution however is quite simple: add the following line to
701<path>/etc/profile</path>.
702</p>
703
704<pre caption="Export the XAUTHORITY">
705export XAUTHORITY="${HOME}/.Xauthority"
706</pre>
707
708</body>
815</section> 709</section>
816</chapter> 710</chapter>
817 711
818<chapter> 712<chapter>
819<title>Maintenance</title> 713<title>Maintenance</title>
820<section id="filecorruption"> 714<section id="filecorruption">
821<title>ReiserFS and filesystem corruption issues -- how to fix'em, etc</title> 715<title>ReiserFS and filesystem corruption issues -- how to fix them, etc</title>
822<body>
823
824<p>
825If your ReiserFS partition is corrupt, try booting the Gentoo
826Linux boot CD and run <c>reiserfsck --rebuild-tree</c> on
827the corrupted filesystem. This should make the filesystem consistent
828again, although you may have lost some files or directories due
829to the corruption.
830</p>
831
832</body> 716<body>
833</section>
834<section id="metalogd">
835<title>Metalogd doesn't log in real time!</title>
836<body>
837 717
838<p>
839Metalog flushes output to the disk in blocks, so messages aren't immediately
840recorded into the system logs. If you are trying to debug a daemon, this
841performance-enhancing behavior is less than helpful. When your Gentoo Linux
842system is up and running, you can send metalog a USR1 signal to temporarily
843turn off this message buffering (meaning that <c>tail -f
844<path>/var/log/everything/current</path></c> will now work in real time, as
845expected) and a USR2 signal to turn buffering back on again. If you want to
846disable buffering permanently, you can change METALOG_OPTS="-B" to
847METALOG_OPTS="-B -s" in <path>/etc/conf.d/metalog</path>.
848</p> 718<p>
849 719If your ReiserFS partition is corrupt, try booting the Gentoo Install CD and
850<pre caption="Turning metalog buffering on/off"> 720run <c>reiserfsck --rebuild-tree</c> on the corrupted filesystem. This should
851<codenote>To turn the buffering off:</codenote> 721make the filesystem consistent again, although you may have lost some files or
852# <i>killall -USR1 metalog</i> 722directories due to the corruption.
853<codenote>To turn the buffering back on:</codenote>
854# <i>killall -USR2 metalog</i>
855</pre> 723</p>
856 724
857</body> 725</body>
858</section> 726</section>
859</chapter> 727</chapter>
860 728
863<section id="reportbugs"> 731<section id="reportbugs">
864<title>Where can I report bugs?</title> 732<title>Where can I report bugs?</title>
865<body> 733<body>
866 734
867<p> 735<p>
868For bugs within a specific program, contact the program's author. Otherwise, 736Use our <uri link="https://bugs.gentoo.org">Bugzilla</uri>. If you are unsure if
869use our Bugzilla bug tracker at <uri>http://bugs.gentoo.org</uri>. You can 737your problem is an actual bug, you can visit <c>#gentoo</c> on the <uri
870also visit us in <c>#gentoo</c> on the <uri
871link="http://www.freenode.net">FreeNode</uri> IRC network. 738link="http://www.freenode.net">FreeNode</uri> IRC network.
872</p> 739</p>
873 740
874</body> 741</body>
875</section> 742</section>
876<section id="releases"> 743<section id="releases">
877<title>How often are new releases made?</title> 744<title>How often are new releases made?</title>
878<body> 745<body>
879 746
880<p> 747<p>
881New releases are announced on the <uri 748Gentoo's packages are usually updated shortly after the main authors release
882link="http://www.gentoo.org/main/en/lists.xml">gentoo-announce</uri> 749new code. As for when Gentoo itself makes new stage/profile/ISO releases, check
883mailing list. In reality the packages themselves are updated shortly after the
884main authors release new code. As for when Gentoo makes new releases, check our
885<uri link="/proj/en/releng">Release Engineering Project</uri> page. 750our <uri link="/proj/en/releng">Release Engineering Project</uri> page. New
886</p> 751releases are announced on the <uri
887 752link="/main/en/lists.xml">gentoo-announce</uri> mailing list. See the question
888</body> 753on <uri link="#upgrade">upgrading</uri> for more information.
889</section>
890<section id="addfaq">
891<title>How can I add a question or answer to this FAQ?</title>
892<body>
893
894<p>
895Submit a new bug over at <uri>http://bugs.gentoo.org</uri> and add it to the
896"Docs-user" product, "Gentoo Linux FAQ" component.
897</p> 754</p>
898 755
899</body> 756</body>
900</section> 757</section>
901<section id="beeping"> 758<section id="beeping">
902<title> 759<title>
903 My speaker beeps like crazy while compiling Mozilla. How do I disable console 760 My speaker beeps like crazy. How do I disable console beeps?
904 beeps?
905</title> 761</title>
906<body> 762<body>
907 763
908<p> 764<p>
909Console beeps can be turned off using setterm, like this: 765Console beeps can be turned off using setterm, like this:
912<pre caption="Using setterm"> 768<pre caption="Using setterm">
913# <i>setterm -blength 0</i> 769# <i>setterm -blength 0</i>
914</pre> 770</pre>
915 771
916<p> 772<p>
917If you would like to turn off the console beeps on boot 773If you would like to turn off the console beeps on boot, you need to put this
918you need to put this command in <path>/etc/conf.d/local.start</path>. However, 774command in <path>/etc/conf.d/local.start</path>. However, this only disables
919this only disables beeps for the current terminal. To disable 775beeps for the current terminal. To disable beeps for other terminals, pipe the
920beeps for other terminals, pipe the command output to the 776command output to the target terminal, like this: </p>
921target terminal, like this:
922</p>
923 777
924<pre caption="Using setterm (bis)"> 778<pre caption="Using setterm (bis)">
925# <i>setterm -blength 0 >/dev/vc/1</i> 779# <i>setterm -blength 0 >/dev/vc/1</i>
926</pre> 780</pre>
927 781
939<section id="resources"> 793<section id="resources">
940<title>Where can I find more information about Gentoo Linux?</title> 794<title>Where can I find more information about Gentoo Linux?</title>
941<body> 795<body>
942 796
943<p> 797<p>
944The official Gentoo documentation can be found on 798The official Gentoo documentation can be found at
945<uri>http://www.gentoo.org</uri>; general Linux information is at
946<uri>http://www.tldp.org</uri>. 799<uri>http://www.gentoo.org/doc/en/</uri>.
947</p> 800</p>
948 801
949</body> 802</body>
950</section> 803</section>
951<section id="buycd"> 804<section id="buycd">
952<title>Can I buy a CD of Gentoo Linux?</title> 805<title>Can I buy a CD of Gentoo Linux?</title>
953<body> 806<body>
954 807
955<p> 808<p>
956Yes! LiveCDs for all supported architecture are available on 809Install CDs for all supported architectures are available on our <uri
957our <uri link="http://store.gentoo.org/">Gentoo Store</uri>. When you 810link="http://www.cafepress.com/officialgentoo/">Gentoo Store</uri>. When you
958purchase a CD from our store, you are also supporting our development. 811purchase a CD from our store, you are also supporting our development. So,
959So, please consider buying from our store if possible :-) 812please consider buying from our store if possible.
960</p>
961
962<p> 813</p>
963You can also find fresh CDs from 814
964<uri link = "http://www.tuxcds.com/section.php?section=42">
965tuxcds</uri> for a very good price. These people also bounce back a
966portion of the profits to the Gentoo project, so buy them while they are hot!
967</p> 815<p>
968 816You can also find fresh CDs from various resellers listed on our <uri
969</body> 817link="/main/en/where.xml">Get Gentoo!</uri> page.
970</section>
971<section id="mailinglist">
972<title>
973 Why, when I hit reply to a post on a Gentoo mailing list, does my answer
974 only go to the original poster and not the entire list?
975</title>
976<body>
977
978<p>
979The mailing list administrators have decided to go with minimal munging
980(altering of mail headers), which means that they have decided against
981altering headers to have replies go to the mailing list. There are various
982reasons for this. For example, if a subscriber has a full mailbox, the
983entire list receives notice of this every time that something is posted.
984</p>
985
986<p>
987Most GUI based mailers have a "reply to all" function. This will ensure that
988your reply goes to the mailing list as well as the original poster. Most
989users of text based emailers already know the methods to use, but if you
990don't, in Pine, there is a "reply to group" option. Setting Mutt to reply to
991the list is covered in the unofficial documentation at
992<uri link="http://forums.gentoo.org/viewtopic.php?t=1085">forums.gentoo.org</uri>.
993</p>
994
995<p>
996Some list members do not like this method, but it was very heavily
997discussed when it went into effect, with arguments on both sides.
998Eventually the list administrators decided to keep it this way. Discussing
999it on the mailing list will sometimes bring a polite explanation and other
1000times a rather brusque comment to check the archives. Although the
1001administrators regret the inconvenience that it may cause some users, it is
1002felt that at present it is preferable to the alternative for several
1003reasons, many of these covered
1004<uri link="http://www.unicom.com/pw/reply-to-harmful.html">here</uri>.
1005</p>
1006
1007<p>
1008(There are other eloquent arguments in favor of munging, and yes, the list
1009administrators have seen them).
1010</p> 818</p>
1011 819
1012</body> 820</body>
1013</section> 821</section>
1014<section id="help"> 822<section id="help">
1015<title>This FAQ hasn't answered my question. What do I do now?</title> 823<title>This FAQ hasn't answered my question. What do I do now?</title>
1016<body> 824<body>
1017 825
1018<p> 826<p>
1019A good first step is to browse through the relevant <uri 827A good first step is to browse through the relevant <uri
1020link="http://www.gentoo.org/doc/en/index.xml">documentation</uri>, failing that, 828link="/doc/en/index.xml">documentation</uri>, failing that, the various Gentoo
1021the various Gentoo Linux mailing lists listed on <uri 829Linux mailing lists listed on <uri link="http://www.google.com">Google</uri>.
1022link="http://www.google.com">Google</uri>. To search through the Gentoo 830To search through the Gentoo mailing lists, just enter "lists.gentoo.org foo"
1023mailing lists, just enter "lists.gentoo.org foo" to search for "foo". If all 831to search for "foo". If all else fails, or you just want to hang out with
1024else fails, or you just want to hang out with Gentoo folks, visit us on irc: 832Gentoo folks, visit us on irc: <c>#gentoo</c> on <c>irc.freenode.net</c>.
1025<c>#gentoo</c> on <c>irc.freenode.net</c>.
1026</p> 833</p>
1027 834
1028</body> 835</body>
1029</section> 836</section>
1030</chapter> 837</chapter>

Legend:
Removed from v.1.68  
changed lines
  Added in v.1.110

  ViewVC Help
Powered by ViewVC 1.1.20