/[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.77 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.77 2004/12/22 22:03:15 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.12</version> 47<version>3.0.7</version>
44<date>2004-12-22</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>
117 <li> 128 <li>
118 <uri link="#configure">I want to perform the ./configure step myself. 129 <uri link="#configure">I want to perform the ./configure step myself.
119 Can I?</uri> 130 Can I?</uri>
120 </li> 131 </li>
121 <li> 132 <li>
122 <uri link="#norsync">What if rsync doesn't work for me?</uri>
123 </li>
124 <li>
125 <uri link="#firewall">How do I use emerge from behind a 133 <uri link="#firewall">How do I use emerge from behind a
126 firewall?</uri> 134 firewall?</uri>
127 </li> 135 </li>
128 <li> 136 <li>
129 <uri link="#unison">Can I rsync from another operating 137 <uri link="#norsync">What if rsync doesn't work for me?</uri>
130 system?</uri>
131 </li> 138 </li>
132 <li> 139 <li>
133 <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
134 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>
135 </li> 142 </li>
136 <li> 143 <li>
137 <uri link="#distfiles">.tar.gz sources for installed software are 144 <uri link="#distfiles">Source tarballs are collecting in
138 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>
139 delete there files?</uri>
140 </li> 146 </li>
141 <li> 147 <li>
142 <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
143 delete the files and directories in /var/tmp/portage?</uri> 149 delete the files and directories in /var/tmp/portage?</uri>
144 </li> 150 </li>
150<title>Usage</title> 156<title>Usage</title>
151<body> 157<body>
152 158
153<ul> 159<ul>
154 <li> 160 <li>
155 <uri link="#rootssh">I have installed openssh on my box, but can
156 only log in as root - my normal user account doesn't work.</uri>
157 </li>
158 <li>
159 <uri link="#rootX">I can start X applications as root only</uri>
160 </li>
161 <li>
162 <uri link="#intkeyboard">How do I set up an International Keyboard 161 <uri link="#intkeyboard">How do I set up an International Keyboard
163 Layout?</uri> 162 Layout?</uri>
164 </li> 163 </li>
165 <li> 164 <li>
166 <uri link="#rootdns">DNS name resolution works for root only.</uri> 165 <uri link="#rootdns">DNS name resolution works for root only.</uri>
188<body> 187<body>
189 188
190<ul> 189<ul>
191 <li> 190 <li>
192 <uri link="#filecorruption">ReiserFS and filesystem corruption issues -- 191 <uri link="#filecorruption">ReiserFS and filesystem corruption issues --
193 how to fix'em, etc.</uri> 192 how to fix them, etc.</uri>
194 </li>
195 <li>
196 <uri link="#metalogd">Metalogd doesn't log in real time!</uri>
197 </li> 193 </li>
198</ul> 194</ul>
199 195
200</body> 196</body>
201</section> 197</section>
209 </li> 205 </li>
210 <li> 206 <li>
211 <uri link="#releases">How often are new releases made?</uri> 207 <uri link="#releases">How often are new releases made?</uri>
212 </li> 208 </li>
213 <li> 209 <li>
214 <uri link="#addfaq">How can I add a question or answer to this
215 FAQ?</uri>
216 </li>
217 <li>
218 <uri link="#beeping">My speaker beeps like crazy while compiling 210 <uri link="#beeping">My speaker beeps like crazy. How do I disable console
219 Mozilla. How do I disable console beeps?</uri> 211 beeps?</uri>
220 </li> 212 </li>
221</ul> 213</ul>
222 214
223</body> 215</body>
224</section> 216</section>
233 </li> 225 </li>
234 <li> 226 <li>
235 <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>
236 </li> 228 </li>
237 <li> 229 <li>
238 <uri link="#mailinglist">Why, when I hit reply to a post on a Gentoo
239 mailinglist, does my answer only go to the original poster and not the
240 entire list?</uri>
241 </li>
242 <li>
243 <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
244 do now?</uri> 231 do now?</uri>
245 </li> 232 </li>
246</ul> 233</ul>
247 234
256<title>How is Gentoo pronounced, and what does it mean?</title> 243<title>How is Gentoo pronounced, and what does it mean?</title>
257<body> 244<body>
258 245
259<p> 246<p>
260A <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
261"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
262penguin 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
263penguin by the inhabitants of the Falkland Islands. 250penguin by the inhabitants of the Falkland Islands (Islas Malvinas).
264</p> 251</p>
265 252
266</body> 253</body>
267</section> 254</section>
268<section id="differences"> 255<section id="differences">
273Gentoo uses a BSD ports-like system called <uri 260Gentoo uses a BSD ports-like system called <uri
274link="/proj/en/portage">Portage</uri>. Portage is a package management system 261link="/proj/en/portage">Portage</uri>. Portage is a package management system
275that allows great flexibility while installing and maintaining software on a 262that allows great flexibility while installing and maintaining software on a
276Gentoo system. It provides compile-time option support (through <uri 263Gentoo system. It provides compile-time option support (through <uri
277link="/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>),
278conditional dependencies, "fake" installs, safe installation (through 265conditional dependencies, pre-package installation summary, safe installation
279sandboxing) and uninstallation of software, system profiles, <uri 266(through sandboxing) and uninstallation of software, system profiles, <uri
280link="/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
281file protection</uri> amongst several other <uri 268file protection</uri> amongst several other <uri
282link="/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>.
283</p> 270</p>
284 271
285<p> 272<p>
286With 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
287choice of optimizations. You have complete control over what packages are or 274optimizations. You have complete control over what packages are or aren't
288aren't installed. Gentoo provides you with numerous choices so you can install 275installed. Gentoo provides you with numerous choices, so you can install Gentoo
289Gentoo 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>.
290<e>meta-distribution</e>.
291</p>
292
293<p> 277</p>
294Gentoo is very actively developed. Not only the <e>ebuilds</e> themselves (the 278
295package format Gentoo uses) but the entire distribution uses a rapid pace 279<p>
280Gentoo is actively developed. The entire distribution uses a rapid pace
296development style. Patches to the packages are quickly integrated in the 281development style: patches to the packages are quickly integrated in the
297mainline tree, documentation is updated on daily basis, portage features are 282mainline tree, documentation is updated on daily basis, Portage features are
298added frequently, releases succeed each other quickly, ... 283added frequently, and official releases occur twice per year.
299</p> 284</p>
300 285
301</body> 286</body>
302</section> 287</section>
303</chapter> 288</chapter>
304 289
305<chapter> 290<chapter>
306<title>Installation</title> 291<title>Installation</title>
307<section id="optimizations"> 292<section id="optimizations">
308<title> 293<title>
309 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
310 -fomit-frame-pointer" optimizations. What gives? 295 -fomit-frame-pointer optimizations. What gives?
311</title> 296</title>
312<body> 297<body>
313 298
314<p> 299<p>
315Don'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
317compiler 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
318do the same thing anymore. 303do the same thing anymore.
319</p> 304</p>
320 305
321<p> 306<p>
322Please 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
323bug. 308reporting a bug.
324</p> 309</p>
325 310
326</body> 311</body>
327</section> 312</section>
328<section id="password"> 313<section id="password">
329<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>
330<body> 315<body>
331 316
332<p> 317<p>
333You 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
334into. 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
335completed the install. 320<c>passwd username</c> For extra options and setting, please <c>man passwd</c>.
336</p> 321</p>
337 322
338</body> 323</body>
339</section> 324</section>
340<section id="useradd"> 325<section id="useradd">
341<title>How do i add a normal user?</title> 326<title>How do I add a normal user?</title>
342<body> 327<body>
343 328
344<p>
345The command <c>adduser gentoo</c> will add a user called gentoo. The next step
346is to give this user a password and <c>passwd</c> will do exactly that.
347</p> 329<p>
348 330The command <c>adduser username</c> will add a user called "username". However,
349<p> 331this method does not give the user many of the rights you might want to grant
350Instead of <c>adduser</c> you can also use: 332him, so the following command is preferred:
351</p> 333</p>
352 334
353<pre caption="Using useradd"> 335<pre caption="Using useradd">
354# <i>useradd gentoo -m -G users,audio,wheel -s /bin/bash</i> 336# <i>useradd -m -G users,audio,wheel username</i>
355</pre> 337</pre>
356 338
357<p>
358This will add a user gentoo, will make possible for him to use sound-related
359devices (<path>/dev/sound/*</path>), will make possible for him to switch to
360root (using <c>su</c>) and will make <path>/bin/bash</path> his/her login shell.
361</p> 339<p>
362 340This will add a user named "username". The option <c>audio</c> adds them to the
363<p> 341<c>audio</c> group and allows the user to access sound devices. The option
364You 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
365then 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
366the instructions given to you by <c>superadduser</c>. 344privileges of the <c>root</c> user.
367</p> 345</p>
368 346
369</body> 347</body>
370</section> 348</section>
371<section id="su"> 349<section id="su">
372<title>Why can't a user su to root?</title> 350<title>Why can't a user su to root?</title>
373<body> 351<body>
374 352
375<p> 353<p>
376For 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
377<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
378the following command as root: 356as root:
379</p> 357</p>
380 358
381<pre caption="Adding a user to the wheel group"> 359<pre caption="Adding a user to the wheel group">
382# <i>gpasswd -a username wheel</i> 360# <i>gpasswd -a username wheel</i>
383</pre> 361</pre>
387<section id="devfs"> 365<section id="devfs">
388<title>How do I disable devfs?</title> 366<title>How do I disable devfs?</title>
389<body> 367<body>
390 368
391<p> 369<p>
392If 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
393can 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
394other hand you want to use <uri link="/doc/en/udev-guide.xml">udev</uri> (2.6 372archs, udev is recommended. Please see the <uri
395kernels only), you can disable devfs by passing the <c>devfs=nomount</c> option
396to the kernel. Don't forget to read up on our <uri
397link="/doc/en/udev-guide.xml">udev guide</uri> too. 373link="/doc/en/udev-guide.xml">udev guide</uri> for information on configuring
374udev.
398</p> 375</p>
399 376
400</body> 377</body>
401</section> 378</section>
402<section id="upgrade"> 379<section id="upgrade">
404 Can I upgrade Gentoo from one release to another without reinstalling? 381 Can I upgrade Gentoo from one release to another without reinstalling?
405</title> 382</title>
406<body> 383<body>
407 384
408<p> 385<p>
409In fact there is no difference between the various releases 386In fact, there is no difference between the various releases after they have
410<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,
411<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
412will bring your entire system up to speed with the "latest Gentoo". 389entire system up to speed with the "latest Gentoo". The differences between
413The true differences between individual releases lie in the installation. 390individual releases lie in the installation medium and pre-compiled packages.
414</p> 391See the <uri link="/doc/en/gentoo-upgrading.xml">Gentoo Upgrading Guide</uri>
415 392for more information about profiles and their role in upgrading.
416<p>
417More information can be found in our <uri link="gentoo-upgrading.xml">Gentoo
418Upgrading Guide</uri>.
419</p> 393</p>
420 394
421</body> 395</body>
422</section> 396</section>
423<section id="bootrescue"> 397<section id="bootrescue">
424<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>
425<body> 399<body>
426 400
427<p> 401<p>
428You 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
429kernel-stuff and all associated steps. Suppose you have installed Gentoo 403kernel and all associated steps is necessary. Suppose you have installed Gentoo
430on <path>/dev/hda1</path> (/boot) and <path>/dev/hda3</path> (/) with 404on <path>/dev/hda1</path> (/boot) and <path>/dev/hda3</path> (/) with
431<path>/dev/hda2</path> being the swap space: 405<path>/dev/hda2</path> being the swap space:
432</p> 406</p>
433 407
434<pre caption = "Reconfiguring the kernel"> 408<pre caption = "Reconfiguring the kernel">
435<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>
436<comment>We first mount all partitions:</comment> 410<comment>We first mount all partitions:</comment>
437# <i>mount /dev/hda3 /mnt/gentoo</i> 411# <i>mount /dev/hda3 /mnt/gentoo</i>
438# <i>mount /dev/hda1 /mnt/gentoo/boot</i> 412# <i>mount /dev/hda1 /mnt/gentoo/boot</i>
439# <i>swapon /dev/hda2</i> 413# <i>swapon /dev/hda2</i>
440# <i>mount -t proc none /mnt/gentoo/proc</i> 414# <i>mount -t proc none /mnt/gentoo/proc</i>
443# <i>env-update &amp;&amp; source /etc/profile</i> 417# <i>env-update &amp;&amp; source /etc/profile</i>
444# <i>cd /usr/src/linux</i> 418# <i>cd /usr/src/linux</i>
445# <i>make menuconfig</i> 419# <i>make menuconfig</i>
446<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>
447<comment>previous attempt. Then quit and compile your kernel:</comment> 421<comment>previous attempt. Then quit and compile your kernel:</comment>
448# <i>make dep &amp;&amp; make bzImage modules modules_install</i> 422# <i>make &amp;&amp; make modules_install</i>
449<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>
450# <i>cp arch/i386/boot/bzImage /boot</i> 424# <i>cp arch/i386/boot/bzImage /boot</i>
451<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>
452# <i>/sbin/lilo</i> 426# <i>/sbin/lilo</i>
453<comment>Now exit the chroot and reboot.</comment> 427<comment>Now exit the chroot and reboot.</comment>
455# <i>umount /mnt/gentoo/proc /mnt/gentoo/boot /mnt/gentoo</i> 429# <i>umount /mnt/gentoo/proc /mnt/gentoo/boot /mnt/gentoo</i>
456# <i>reboot</i> 430# <i>reboot</i>
457</pre> 431</pre>
458 432
459<p> 433<p>
460If on the other hand the problem lays with your bootloader configuration, 434If, on the other hand, the problem lays with your bootloader configuration,
461follow the same steps, but instead of configuring/compiling your kernel you 435follow the same steps, but instead of configuring/compiling your kernel, you
462should reconfigure your bootloader (recompilation isn't necessary). 436should reconfigure your bootloader (recompilation isn't necessary).
463</p> 437</p>
464 438
465</body> 439</body>
466</section> 440</section>
467<section id="proxy"> 441<section id="proxy">
468<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>
469<body> 443<body>
470 444
471<p> 445<p>
472When you have to download something using <c>wget</c>, use the
473following syntax to authenticate yourself:
474</p>
475
476<pre caption = "Proxy-authentication using wget">
477# <i>wget --proxy-user=</i><comment>username</comment><i> --proxy-passwd=</i><comment>password</comment><i> &lt;url&gt;</i>
478</pre>
479
480<p>
481To have Portage automatically use this scheme, define it in 446To have Portage automatically use this scheme, define it in
482<path>/etc/make.conf</path>: 447<path>/etc/make.conf</path>:
483</p> 448</p>
484 449
485<pre caption = "/etc/make.conf"> 450<pre caption = "/etc/make.conf">
486FETCHCOMMAND="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"
487RESUMECOMMAND="/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"
488</pre> 453RSYNC_PROXY="rsync://username:password@yourproxybox.server:portnumber"
489
490<p>
491Sadly, <c>rsync</c> doesn't seem to support username/password
492authentication for proxies. See <uri link="#doc_chap4_sect3">What
493if rsync doesn't work for me?</uri> for more information on how to
494handle this situation.
495</p> 454</pre>
496 455
497</body> 456</body>
498</section> 457</section>
499<section id="isoburning"> 458<section id="isoburning">
500<title>How do I burn an ISO file?</title> 459<title>How do I burn an ISO file?</title>
501<body> 460<body>
502 461
503<p> 462<p>
504You 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>
505should <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.
506entire CD.
507</p> 465</p>
508 466
509<p> 467<p>
510There 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
511Sisyphean problem. Describing a few popular tools however doesn't hurt :) 469Sisyphean problem. However, describing a few popular tools never hurts:
512</p> 470</p>
513 471
514<ul> 472<ul>
515 <li> 473 <li>
516 With EasyCD Creator you select <c>File</c>, <c>Record CD 474 With EasyCD Creator you select <c>File</c>, <c>Record CD
528 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
529 <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
530 by the path to the ISO file :) 488 by the path to the ISO file :)
531 </li> 489 </li>
532 <li> 490 <li>
533 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>.
534 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
535 <c>Start</c>. 493 click <c>Start</c>.
536 </li> 494 </li>
537 <li> 495 <li>
538 With Mac OS X Panther, launch <c>Disk Utility</c> from 496 With Mac OS X Panther, launch <c>Disk Utility</c> from
539 <path>Applications/Utilities</path>, select <c>Open</c> from the 497 <path>Applications/Utilities</path>, select <c>Open</c> from the
540 <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
554<title>What CD/stage should I use for my CPU?</title> 512<title>What CD/stage should I use for my CPU?</title>
555<body> 513<body>
556 514
557<p> 515<p>
558First you need to find our what CPU you use. Suppose it's a Pentium-M. Then you 516First you need to find our what CPU you use. Suppose it's a Pentium-M. Then you
559need to find out what CPU it is, instruction-wise, compatible with. You need to 517need to find out what CPU it is, instruction-wise, compatible with. You may
560consult the CPUs vendor website for this, although <uri 518need to consult the CPU's vendor website for this, although <uri
561link="http://www.google.com">Google</uri> is at least as efficient :-). 519link="http://www.google.com">Google</uri> is at least as efficient :-).
562</p> 520</p>
563 521
564<p> 522<p>
565For the Pentium-M, you'll find out that it is a Pentium-3 with SSE instructions,
566meaning it is instruction-compatible with the Pentium-4. So, for Pentium-M
567systems, you can choose the Pentium-4 CD/stage files.
568</p>
569
570<p>
571If you are uncertain, take a "lower" CD/stage file, for instance a i686 or even 523If you are uncertain, take a "lower" CD/stage file, for instance a i686 or even
572generic. 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>.
573</p> 533</p>
574 534
575</body> 535</body>
576</section> 536</section>
577</chapter> 537</chapter>
578 538
579<chapter> 539<chapter>
580<title>Package Management</title> 540<title>Package Management</title>
581<section id="ebuilds"> 541<section id="ebuilds">
582<title>In what format are the packages stored?</title> 542<title>In what form are the packages stored?</title>
583<body> 543<body>
584 544
585<p> 545<p>
586They 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
587primarily a ports-based distribution, meaning that we provide scripts 547which can resolve dependencies, fetch source code, and compile a version of the
588(<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
589apps from sources. We generally only build binaries for releases and snapshots. 549releases and snapshots. The <uri
590The <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
591Ebuild HOWTO</uri> covers the 551HOWTO</uri> covers the contents of an ebuild script in detail.
592contents of an ebuild script in detail. For full binary ISO releases, we 552</p>
593create a full suite of binary packages in an enhanced <c>.tbz2</c> format 553
594(<c>.tar.bz2</c> compatible with meta-information attached to the end of the 554<p>
595file). 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.
596</p> 565</p>
597 566
598</body> 567</body>
599</section> 568</section>
600<section id="configure"> 569<section id="configure">
601<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
602<body> 583</body>
584</section>
585<section id="firewall">
586<title>How do I use emerge from behind a firewall?</title>
587<body>
603 588
604<p>
605Yes, but it is not trivial, and the next method only works when it is a simple
606ebuild (i.e. just <c>./configure</c> and <c>make &amp;&amp; make install</c>).
607Be sure to read the ebuild itself to see how Gentoo handles it.
608</p> 589<p>
609 590See the questions on <uri link="#proxy">proxies</uri>, <uri
610<p> 591link="#norsync">rsync</uri>, and <uri link="#manualdownload">downloading source
611Start with unpacking the ebuild: <c>ebuild 592files manually</uri>.
612/usr/portage/&lt;category&gt;/&lt;package&gt;/&lt;ebuild&gt; unpack</c>.
613</p>
614
615<p>
616Next, go to <path>/var/tmp/portage/&lt;package&gt;-&lt;version&gt;/work</path>.
617Inside it you'll find the unpacked sources. Execute the steps you need to
618perform to configure and compile the package.
619</p>
620
621<p>
622When finished, execute <c>touch
623/var/tmp/portage/&lt;package&gt;-&lt;version&gt;/.compiled</c> to trick Portage
624into thinking it configured and compiled the package. Then finish up with
625<c>ebuild /usr/portage/&lt;category&gt;/&lt;package&gt;/&lt;ebuild&gt;
626merge</c>.
627</p> 593</p>
628 594
629</body> 595</body>
630</section> 596</section>
631<section id="norsync"> 597<section id="norsync">
633<body> 599<body>
634 600
635<p> 601<p>
636If 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
637<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
638through 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
639proxy is fully supported. 605document for information on downloading source files and Portage snapshots via
640</p> 606a proxy.
641
642<pre caption="Using emerge-webrsync">
643# <i>emerge-webrsync</i>
644</pre>
645
646</body>
647</section>
648<section id="firewall">
649<title>How do I use emerge from behind a firewall?</title>
650<body>
651
652<p>
653Edit the PROXY settings in <path>/etc/make.conf</path>. If that doesn't work,
654edit <path>/etc/wget/wgetrc</path> and edit http_proxy and ftp_proxy
655appropriately.
656</p>
657
658</body>
659</section>
660<section id="unison">
661<title>Can I rsync from another operating system?</title>
662<body>
663
664<p>
665There's a program called unison that works under both UNIX and Win32, available
666from <uri>http://www.cis.upenn.edu/~bcpierce/unison/</uri>.
667</p> 607</p>
668 608
669</body> 609</body>
670</section> 610</section>
671<section id="manualdownload"> 611<section id="manualdownload">
678<p> 618<p>
679Definitely. 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
680are 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
681to 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
682sources and bring them on any media home. Put the sources into 622sources and bring them on any media home. Put the sources into
683<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>.
684picking up the sources you just brought in! 624Be warned, however, that this is a tedious process.
685</p> 625</p>
686 626
687</body> 627</body>
688</section> 628</section>
689<section id="distfiles"> 629<section id="distfiles">
690<title> 630<title>
691 .tar.gz sources for installed software are piling up in 631 Source tarballs are collecting in /usr/portage/distfiles/. Is it safe to
692 /usr/portage/distfiles/ using valuable space. Is it safe to delete these 632 delete these files?
693 files?
694</title> 633</title>
695<body> 634<body>
696 635
697<p> 636<p>
698Yes, 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.
699connection, 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
700possible; 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
701a 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
702upgrade the software it will have to be downloaded from the internet 641be necessary to download them from the internet again. There are programs which
703again. 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.
704</p> 646</p>
705 647
706</body> 648</body>
707</section> 649</section>
708<section id="tmpportage"> 650<section id="tmpportage">
712</title> 654</title>
713<body> 655<body>
714 656
715<p> 657<p>
716During compilation, Gentoo saves the sources of the package in 658During compilation, Gentoo saves the sources of the package in
717<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
718directory. 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.
719</p> 663</p>
720 664
721</body> 665</body>
722</section> 666</section>
723</chapter> 667</chapter>
724 668
725<chapter> 669<chapter>
726<title>Usage</title> 670<title>Usage</title>
727<section id="rootssh">
728<title>
729 I have installed openssh on my box, but can only log in as root - my normal
730 user account doesn't work.
731</title>
732<body>
733
734<p>
735This is most probably because your user account doesn't have a valid shell
736specified. Check for your user entry in <path>/etc/passwd</path> and see if it
737ends in /bin/bash (or any other shell). If it doesn't, you must set a shell for
738the user. This is done using the usermod command, like this:
739</p>
740
741<pre caption="Using usermod">
742# <i>usermod -s /bin/bash myuser</i>
743</pre>
744
745</body>
746</section>
747<section id="rootX">
748<title>I can start X applications as root only.</title>
749<body>
750
751<p>
752Your <path>/tmp</path> directory has the wrong permissions (it needs the
753sticky bit set). Type the following as root:
754</p>
755
756<pre caption="Changing /tmp permissions">
757# <i>chmod 1777 /tmp</i>
758</pre>
759
760</body>
761</section>
762<section id="intkeyboard"> 671<section id="intkeyboard">
763<title>How do I set up an International Keyboard Layout?</title> 672<title>How do I set up an International Keyboard Layout?</title>
764<body> 673<body>
765 674
766<p> 675<p>
767Edit 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,
768Then either reboot or restart the keymaps script: 677either <c>reboot</c> or restart the keymaps script:
678</p>
679
680<pre caption="Restarting keymaps">
769<c>/etc/init.d/keymaps restart</c>. 681# <i>/etc/init.d/keymaps restart</i>
770</p> 682</pre>
771 683
772</body> 684</body>
773</section> 685</section>
774<section id="rootdns"> 686<section id="rootdns">
775<title>DNS name resolution works for root only.</title> 687<title>DNS name resolution works for root only</title>
776<body> 688<body>
777 689
778<p> 690<p>
779<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
780follows: 692follows:
799<section id="numlock"> 711<section id="numlock">
800<title>How do I get numlock to start on boot?</title> 712<title>How do I get numlock to start on boot?</title>
801<body> 713<body>
802 714
803<p> 715<p>
804If you log on graphically, or want numlock to be activated when
805you issue <c>startx</c>, then you must <c>emerge numlockx</c> and
806add <c>/usr/X11R6/bin/numlockx</c> to
807<path>/etc/X11/xinit/xinitrc</path> (for <c>startx</c>) or
808<path>/etc/X11/Sessions/</path> (for any graphical login manager) such
809as <path>/etc/X11/Sessions/Gnome</path> for GDM.
810</p>
811
812<p>
813GNOME 2.6 users however will notice that this doesn't work. Instead, they will
814need to start the <c>gnome-session-properties</c> tool. At the top of the
815Window, select <c>Startup Programs</c> and click the <c>Add</c> button. Now
816insert the location of the <c>numlockx</c> tool (for instance
817<path>/usr/X11R6/bin/numlockx</path>) and exit.
818</p>
819
820<p>
821If 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
822numlock default</c> and numlock will be activated on the next 717numlock default &amp;&amp;/etc/init.d/numlock start</c>.
823reboot. 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.
824</p> 723</p>
825 724
826</body> 725</body>
827</section> 726</section>
828<section id="clear"> 727<section id="clear">
870</chapter> 769</chapter>
871 770
872<chapter> 771<chapter>
873<title>Maintenance</title> 772<title>Maintenance</title>
874<section id="filecorruption"> 773<section id="filecorruption">
875<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>
876<body>
877
878<p>
879If your ReiserFS partition is corrupt, try booting the Gentoo
880Linux boot CD and run <c>reiserfsck --rebuild-tree</c> on
881the corrupted filesystem. This should make the filesystem consistent
882again, although you may have lost some files or directories due
883to the corruption.
884</p>
885
886</body> 775<body>
887</section>
888<section id="metalogd">
889<title>Metalogd doesn't log in real time!</title>
890<body>
891 776
892<p>
893Metalog flushes output to the disk in blocks, so messages aren't immediately
894recorded into the system logs. If you are trying to debug a daemon, this
895performance-enhancing behavior is less than helpful. When your Gentoo Linux
896system is up and running, you can send metalog a USR1 signal to temporarily
897turn off this message buffering (meaning that <c>tail -f
898<path>/var/log/everything/current</path></c> will now work in real time, as
899expected) and a USR2 signal to turn buffering back on again. If you want to
900disable buffering permanently, you can change METALOG_OPTS="-B" to
901METALOG_OPTS="-B -s" in <path>/etc/conf.d/metalog</path>.
902</p> 777<p>
903 778If your ReiserFS partition is corrupt, try booting the Gentoo Install CD and
904<pre caption="Turning metalog buffering on/off"> 779run <c>reiserfsck --rebuild-tree</c> on the corrupted filesystem. This should
905<codenote>To turn the buffering off:</codenote> 780make the filesystem consistent again, although you may have lost some files or
906# <i>killall -USR1 metalog</i> 781directories due to the corruption.
907<codenote>To turn the buffering back on:</codenote>
908# <i>killall -USR2 metalog</i>
909</pre> 782</p>
910 783
911</body> 784</body>
912</section> 785</section>
913</chapter> 786</chapter>
914 787
917<section id="reportbugs"> 790<section id="reportbugs">
918<title>Where can I report bugs?</title> 791<title>Where can I report bugs?</title>
919<body> 792<body>
920 793
921<p> 794<p>
922For 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
923use 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
924also visit us in <c>#gentoo</c> on the <uri
925link="http://www.freenode.net">FreeNode</uri> IRC network. 797link="http://www.freenode.net">FreeNode</uri> IRC network.
926</p> 798</p>
927 799
928</body> 800</body>
929</section> 801</section>
930<section id="releases"> 802<section id="releases">
931<title>How often are new releases made?</title> 803<title>How often are new releases made?</title>
932<body> 804<body>
933 805
934<p> 806<p>
935New releases are announced on the <uri 807Gentoo's packages are usually updated shortly after the main authors release
936link="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
937mailing list. In reality the packages themselves are updated shortly after the
938main authors release new code. As for when Gentoo makes new releases, check our
939<uri link="/proj/en/releng">Release Engineering Project</uri> page. 809our <uri link="/proj/en/releng">Release Engineering Project</uri> page. New
940</p> 810releases are announced on the <uri
941 811link="/main/en/lists.xml">gentoo-announce</uri> mailing list. See the question
942</body> 812on <uri link="#upgrade">upgrading</uri> for more information.
943</section>
944<section id="addfaq">
945<title>How can I add a question or answer to this FAQ?</title>
946<body>
947
948<p>
949Submit a new bug over at <uri>http://bugs.gentoo.org</uri> and add it to the
950"Docs-user" product, "Gentoo Linux FAQ" component.
951</p> 813</p>
952 814
953</body> 815</body>
954</section> 816</section>
955<section id="beeping"> 817<section id="beeping">
956<title> 818<title>
957 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?
958 beeps?
959</title> 820</title>
960<body> 821<body>
961 822
962<p> 823<p>
963Console beeps can be turned off using setterm, like this: 824Console beeps can be turned off using setterm, like this:
966<pre caption="Using setterm"> 827<pre caption="Using setterm">
967# <i>setterm -blength 0</i> 828# <i>setterm -blength 0</i>
968</pre> 829</pre>
969 830
970<p> 831<p>
971If 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
972you 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
973this only disables beeps for the current terminal. To disable 834beeps for the current terminal. To disable beeps for other terminals, pipe the
974beeps for other terminals, pipe the command output to the 835command output to the target terminal, like this: </p>
975target terminal, like this:
976</p>
977 836
978<pre caption="Using setterm (bis)"> 837<pre caption="Using setterm (bis)">
979# <i>setterm -blength 0 >/dev/vc/1</i> 838# <i>setterm -blength 0 >/dev/vc/1</i>
980</pre> 839</pre>
981 840
993<section id="resources"> 852<section id="resources">
994<title>Where can I find more information about Gentoo Linux?</title> 853<title>Where can I find more information about Gentoo Linux?</title>
995<body> 854<body>
996 855
997<p> 856<p>
998The official Gentoo documentation can be found on 857The official Gentoo documentation can be found at
999<uri>http://www.gentoo.org</uri>; general Linux information is at
1000<uri>http://www.tldp.org</uri>. 858<uri>http://www.gentoo.org/doc/en/</uri>.
1001</p> 859</p>
1002 860
1003</body> 861</body>
1004</section> 862</section>
1005<section id="buycd"> 863<section id="buycd">
1006<title>Can I buy a CD of Gentoo Linux?</title> 864<title>Can I buy a CD of Gentoo Linux?</title>
1007<body> 865<body>
1008 866
1009<p> 867<p>
1010Yes! LiveCDs for all supported architecture are available on 868Install CDs for all supported architectures are available on our <uri
1011our <uri link="http://store.gentoo.org/">Gentoo Store</uri>. When you 869link="http://www.cafepress.com/officialgentoo/">Gentoo Store</uri>. When you
1012purchase a CD from our store, you are also supporting our development. 870purchase a CD from our store, you are also supporting our development. So,
1013So, please consider buying from our store if possible :-) 871please consider buying from our store if possible.
1014</p>
1015
1016<p> 872</p>
1017You can also find fresh CDs from 873
1018<uri link = "http://www.tuxcds.com/section.php?section=42">
1019tuxcds</uri> for a very good price. These people also bounce back a
1020portion of the profits to the Gentoo project, so buy them while they are hot!
1021</p> 874<p>
1022 875You can also find fresh CDs from various resellers listed on our <uri
1023</body> 876link="/main/en/where.xml">Get Gentoo!</uri> page.
1024</section>
1025<section id="mailinglist">
1026<title>
1027 Why, when I hit reply to a post on a Gentoo mailing list, does my answer
1028 only go to the original poster and not the entire list?
1029</title>
1030<body>
1031
1032<p>
1033The mailing list administrators have decided to go with minimal munging
1034(altering of mail headers), which means that they have decided against
1035altering headers to have replies go to the mailing list. There are various
1036reasons for this. For example, if a subscriber has a full mailbox, the
1037entire list receives notice of this every time that something is posted.
1038</p>
1039
1040<p>
1041Most GUI based mailers have a "reply to all" function. This will ensure that
1042your reply goes to the mailing list as well as the original poster. Most
1043users of text based emailers already know the methods to use, but if you
1044don't, in Pine, there is a "reply to group" option. Setting Mutt to reply to
1045the list is covered in the unofficial documentation at
1046<uri link="http://forums.gentoo.org/viewtopic.php?t=1085">forums.gentoo.org</uri>.
1047</p>
1048
1049<p>
1050Some list members do not like this method, but it was very heavily
1051discussed when it went into effect, with arguments on both sides.
1052Eventually the list administrators decided to keep it this way. Discussing
1053it on the mailing list will sometimes bring a polite explanation and other
1054times a rather brusque comment to check the archives. Although the
1055administrators regret the inconvenience that it may cause some users, it is
1056felt that at present it is preferable to the alternative for several
1057reasons, many of these covered
1058<uri link="http://www.unicom.com/pw/reply-to-harmful.html">here</uri>.
1059</p>
1060
1061<p>
1062(There are other eloquent arguments in favor of munging, and yes, the list
1063administrators have seen them).
1064</p> 877</p>
1065 878
1066</body> 879</body>
1067</section> 880</section>
1068<section id="help"> 881<section id="help">
1069<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>
1070<body> 883<body>
1071 884
1072<p> 885<p>
1073A good first step is to browse through the relevant <uri 886A good first step is to browse through the relevant <uri
1074link="http://www.gentoo.org/doc/en/index.xml">documentation</uri>, failing that, 887link="/doc/en/index.xml">documentation</uri>, failing that, the various Gentoo
1075the various Gentoo Linux mailing lists listed on <uri 888Linux mailing lists listed on <uri link="http://www.google.com">Google</uri>.
1076link="http://www.google.com">Google</uri>. To search through the Gentoo 889To search through the Gentoo mailing lists, just enter "lists.gentoo.org foo"
1077mailing 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
1078else 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>.
1079<c>#gentoo</c> on <c>irc.freenode.net</c>.
1080</p> 892</p>
1081 893
1082</body> 894</body>
1083</section> 895</section>
1084</chapter> 896</chapter>

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

  ViewVC Help
Powered by ViewVC 1.1.20