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

Legend:
Removed from v.1.76  
changed lines
  Added in v.1.96

  ViewVC Help
Powered by ViewVC 1.1.20