/[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.12 Revision 1.42
1<?xml version='1.0' encoding="UTF-8"?> 1<?xml version='1.0' encoding="UTF-8"?>
2<?xml-stylesheet href="/xsl/guide.xsl" type="text/xsl"?>
3
4<!DOCTYPE guide SYSTEM "/dtd/guide.dtd"> 2<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
5 3
6<guide link="/doc/en/faq.xml"> 4<guide link="/doc/en/faq.xml">
7<title>Gentoo Linux Frequently Asked Questions</title> 5<title>Gentoo Linux Frequently Asked Questions</title>
8<author title="Chief Architect"><mail link="drobbins@gentoo.org">Daniel Robbins</mail></author> 6<author title="Chief Architect"><mail link="drobbins@gentoo.org">Daniel Robbins</mail></author>
9<author title="Reviewer">Colin Morey</author> 7<author title="Reviewer">Colin Morey</author>
10<author title="Editor"><mail link="zhen@gentoo.org">John P. Davis</mail></author> 8<author title="Editor"><mail link="zhen@gentoo.org">John P. Davis</mail></author>
11<author title="Editor"><mail link="stocke2@gentoo.org">Eric Stockbridge</mail></author> 9<author title="Editor"><mail link="stocke2@gentoo.org">Eric Stockbridge</mail></author>
10<author title="Editor"><mail link="zhware@gentoo.org">Stoyan Zhekov</mail></author>
11<author title="Editor"><mail link="carl@gentoo.org">Carl Anderson</mail></author>
12<author title="Editor"><mail link="peesh@gentoo.org">Jorge Paulo</mail></author>
13<author title="Editor"><mail link="swift@gentoo.org">Sven Vermeulen</mail></author>
12<abstract>This FAQ is a collection of questions and answers collected from the gentoo-dev mailing list and from IRC -- if you have any questions (or answers!) to add, please contact either an author or a member of the documentation team.</abstract> 14<abstract>This FAQ is a collection of questions and answers collected from the gentoo-dev mailing list and from IRC -- if you have any questions (or answers!) to add, please contact either an author or a member of the documentation team.</abstract>
13 15
16<license/>
17
14<version>1.1.2</version> 18<version>1.1.8</version>
15<date>06 December 2002</date> 19<date>September 30, 2003</date>
20
21<chapter>
22<title>Featured Questions</title>
23<section>
24<title>Getting Started</title>
25<body>
26<ul>
27<li><uri link="#doc_chap2_sect1">How is Gentoo pronounced, and what does it mean? </uri></li>
28<li><uri link="#doc_chap2_sect2">What makes Gentoo different?</uri></li>
29</ul>
30</body>
31</section>
32<section>
33<title>Installation</title>
34<body>
35<ul>
36<li><uri link="#doc_chap3_sect1">What is the difference between the .iso and .tbz2 files?</uri></li>
37<li><uri link="#doc_chap3_sect2">Why do the build .iso and .tbz2 files sometimes have different -r (revision) numbers?</uri></li>
38<li><uri link="#doc_chap3_sect3">I'm finding things to be really unstable and I'm using "-O9 -ffast-math -fomit-frame-pointer" optimizations. What gives?</uri></li>
39<li><uri link="#doc_chap3_sect4">What's the default root password after installation?</uri></li>
40<li><uri link="#doc_chap3_sect5">How can i change the root (or indeed any other user's) password?</uri></li>
41<li><uri link="#doc_chap3_sect6">How do i add a normal user?</uri></li>
42<li><uri link="#doc_chap3_sect7">Why can't a user su to root? </uri></li>
43<li><uri link="#doc_chap3_sect8">How do I enable devfs?</uri></li>
44<li><uri link="#doc_chap3_sect9">How to I disable devfs?</uri></li>
45<li><uri link="#doc_chap3_sect10">How do I get a /dev/mouse that doesn't go away when I reboot (when using devfs)? </uri></li>
46<li><uri link="#doc_chap3_sect11">Grub can't find stage x.y?</uri></li>
47<li><uri link="#doc_chap3_sect12">My ASUS CUV4X-D won't boot and it freezes during various stages of kernel loading and hardware detection.</uri></li>
48<li><uri link="#doc_chap3_sect13">If I have Gentoo 1.4_rc1 can I upgrade to 1.4_rc2, 1.4_final/_rc3 without reinstalling?</uri></li>
49<li><uri link="#doc_chap3_sect14">My kernel doesn't boot (properly), what should I do now?</uri></li>
50<li><uri link="#doc_chap3_sect15">My proxy requires authentication, what do I have to do?</uri></li>
51</ul>
52</body>
53</section>
54<section>
55<title>Package Management</title>
56<body>
57<ul>
58<li><uri link="#doc_chap4_sect1">In what format are the packages stored?</uri></li>
59<li><uri link="#doc_chap4_sect2">Why write a new port system (Portage) instead of using BSD's version?</uri></li>
60<li><uri link="#doc_chap4_sect3">How does this differ from Debian's apt or BSD's ports?</uri></li>
61<li><uri link="#doc_chap4_sect4">How do I install and uninstall packages?</uri></li>
62<li><uri link="#doc_chap4_sect5">How can I set a global configuration for compiling packages?</uri></li>
63<li><uri link="#doc_chap4_sect6">What happened to /etc/make.defaults?</uri></li>
64<li><uri link="#doc_chap4_sect7">Is there a way to upgrade all installed packages e.g. apt-get upgrade or make World?</uri></li>
65<li><uri link="#doc_chap4_sect8">When updating a package using emerge or ebuild, how do I avoid clobbering my config files?</uri></li>
66<li><uri link="#doc_chap4_sect9">I want to perform the ./configure step myself. Can I?</uri></li>
67<li><uri link="#doc_chap4_sect10">What if rsync doesn't work for me?</uri></li>
68<li><uri link="#doc_chap4_sect11">How do I use emerge from behind a firewall?</uri></li>
69<li><uri link="#doc_chap4_sect12">Can I rsync from another operating system?</uri></li>
70<li><uri link="#doc_chap4_sect13">I have only slow modem connection at home. Can I download sources somewhere else and add them to my system?</uri></li>
71<li><uri link="#doc_chap4_sect14">.tar.gz sources for installed software are piling up in /usr/portage/distfiles/ using valuable space. Is it safe to delete these files?</uri></li>
72<li><uri link="#doc_chap4_sect15">I went to emerge blackdown-jdk and blackdown-jre, and afterwards java-config --list-available-vms would only list blackdown-jre. Openoffice would then refuse to emerge. What do I do? </uri></li>
73<li><uri link="#doc_chap4_sect16">What's in /var/tmp/portage? Is it safe to delete the files and directories in /var/tmp/portage? </uri></li>
74</ul>
75</body>
76</section>
77<section>
78<title>Usage</title>
79<body>
80<ul>
81<li><uri link="#doc_chap5_sect1">I have installed openssh on my box, but can only log in as root - my normal user account doesn't work.</uri></li>
82<li><uri link="#doc_chap5_sect2">I can start X applications as root only. </uri></li>
83<li><uri link="#doc_chap5_sect3">How do I set up an International Keyboard Layout?</uri></li>
84<li><uri link="#doc_chap5_sect4">DNS name resolution works for root only. </uri></li>
85<li><uri link="#doc_chap5_sect5">Why is KDE not reading /etc/profile? </uri></li>
86<li><uri link="#doc_chap5_sect6">Why can't my user use their own crontab? </uri></li>
87<li><uri link="#doc_chap5_sect7">How do I get numlock to start on boot?</uri></li>
88<li><uri link="#doc_chap5_sect8">How do I have my terminal cleared when
89I log out?</uri></li>
90</ul>
91</body>
92</section>
93<section>
94<title>Maintenance</title>
95<body>
96<ul>
97<li><uri link="#doc_chap6_sect1">ReiserFS and filesystem corruption issues -- how to fix'em, etc</uri></li>
98<li><uri link="#doc_chap6_sect2">How to I view the timestamps in /var/log/syslog.d, etc. on a pre-1.0_rc5 Gentoo system? </uri></li>
99<li><uri link="#doc_chap6_sect3">Metalogd doesn't log in real time!</uri></li>
100</ul>
101</body>
102</section>
103<section>
104<title>Development</title>
105<body>
106<ul>
107<li><uri link="#doc_chap7_sect1">Where can I report bugs?</uri></li>
108<li><uri link="#doc_chap7_sect2">How often are new releases made? </uri></li>
109<li><uri link="#doc_chap7_sect3">I would like a package to be added to Portage; how would I go about this?</uri></li>
110<li><uri link="#doc_chap7_sect4">How can I add a question or answer to this FAQ?</uri></li>
111<li><uri link="#doc_chap7_sect5">make -f Makefile.cvs on a KDE app produces "invalid unused variable" errors </uri></li>
112<li><uri link="#doc_chap7_sect6">My speaker beeps like crazy while compiling Mozilla. How do I disable console beeps? </uri></li>
113</ul>
114</body>
115</section>
116<section>
117<title>Resources</title>
118<body>
119<ul>
120<li><uri link="#doc_chap8_sect1">Where can I find more about supervise used by default in Gentoo Linux 1.0_rc5 and earlier? </uri></li>
121<li><uri link="#doc_chap8_sect2">Where can I find more information about Gentoo Linux? </uri></li>
122<li><uri link="#doc_chap8_sect3">Can I buy a CD of Gentoo Linux?</uri></li>
123<li><uri link="#doc_chap8_sect4">Why, when I hit reply to a post on a Gentoo mailing list, does my answer only go to the original poster and not the entire list?</uri></li>
124<li><uri link="#doc_chap8_sect5">This FAQ hasn't answered my question. What do I do now? </uri></li>
125</ul>
126</body>
127</section>
128</chapter>
129
16 130
17<chapter> 131<chapter>
18 <title>Getting Started</title> 132 <title>Getting Started</title>
19 133
20 <section> 134 <section>
77 </p> 191 </p>
78 </body> 192 </body>
79 </section> 193 </section>
80 194
81 <section> 195 <section>
82 <title>I have a Sony Super-Slim VAIO laptop, and the Gentoo Linux CD is having problems
83 finding my PCMCIA ATAPI CD-ROM.</title>
84 <body>
85 <p>Make sure the second IDE port is set to CDROM (it unsets itself if the device isn't
86 attached on boot) then do the following at the isolinux <c>boot:</c> prompt:</p>
87<pre>
88boot: <i>rescue ide2=0x180,0x386</i>
89</pre>
90<p>If you are using a 1.0_rc5 or earlier boot CD, apart from thinking about downloading the latest iso,
91type <c>gentoo</c> instead of <c>rescue</c>, above.</p>
92</body>
93
94</section>
95 <section>
96 <title>I'm finding things to be really unstable and I'm using "-O9 -ffast-math 196 <title>I'm finding things to be really unstable and I'm using "-O9 -ffast-math
97 -fomit-frame-pointer" optimizations. What gives?</title> 197 -fomit-frame-pointer" optimizations. What gives?</title>
98 <body> 198 <body>
99 <p>When you use any optimizations beyond <c>-O3</c>, you're really taking the risk of 199 <p>Don't bother using anything higher than <c>-O3</c> since it isn't support by current versions
100 having broken packages.
101 Very aggressive optimizations sometimes cause the compiler to streamline the assembly code 200 of gcc. Very aggressive optimizations sometimes cause the compiler to streamline the assembly code
102 to the point where it doesn't quite do the same thing anymore. <e>Loc-Dog</e> (on IRC) 201 to the point where it doesn't quite do the same thing anymore. A possible setting based on <e>Loc-Dog</e> (on IRC)'s CFLAGS
103 uses <c>-O3 -mcpu=i686 -march=i686 -fforce-addr -fomit-frame-pointer -funroll-loops 202 is <c>-O3 -mcpu=i686 -march=i686 -fforce-addr -fomit-frame-pointer -funroll-loops
104 -frerun-cse-after-loop -frerun-loop-opt -malign-functions=4</c>, which is about 203 -frerun-cse-after-loop -frerun-loop-opt -falign-functions=4</c>, which is about
105 as much as I'd want to push global optimization settings. Beyond this, it's best to use 204 as much as I'd want to push global optimization settings. Beyond this, it's best to use
106 ultra-high optimizations only with specific packages where you really need that extra 2%, 205 ultra-high optimizations only with specific packages where you really need that extra 2%,
107 (eg graphics and various multimedia programs), and where you can easily test the package 206 (eg graphics and various multimedia programs), and where you can easily test the package
108 to ensure that it hasn't been optimized into oblivion.</p> 207 to ensure that it hasn't been optimized into oblivion.</p>
109 <p>Please try first to compile with CFLAGS <c>-march= -O2</c> before reporting a bug</p> 208 <p>Please try first to compile with CFLAGS <c>-march= -O2</c> before reporting a bug</p>
121 for extra options and setting, please see <c>man passwd</c> once you've completed the install. 220 for extra options and setting, please see <c>man passwd</c> once you've completed the install.
122 </p></body> 221 </p></body>
123 </section> 222 </section>
124 <section> 223 <section>
125 <title>How do i add a normal user?</title> 224 <title>How do i add a normal user?</title>
126 <body><p>Everyone seems to think that i shouldn't be using <e>root</e> for everyday use, 225 <body>
127 how can i add another user?</p>
128 <p>The command <c>adduser gentoo</c> will add a user called gentoo. The next step is to give 226 <p>The command <c>adduser gentoo</c> will add a user called gentoo. The next step is to give
129 this user a password and <c>passwd</c> will do exactly that.</p> 227 this user a password and <c>passwd</c> will do exactly that.</p>
228 <p>Instead of <c>adduser</c> you can also use:
229 <pre># <i>useradd gentoo -m -G users,audio,wheel -s /bin/bash</i></pre>
230 This will add a user gentoo, will make possible for him to use sound-related devices (<path>/dev/sound/*</path>), will make possible for him to switch to root (using <c>su</c>) and will make <path>/bin/bash</path> his login shell.
231 </p>
232 <p>You can also install <c>superadduser</c> using <c>emerge superadduser</c> and then issue <c>superadduser gentoo</c> to add a user called gentoo. Just follow the instructions given to you by <c>superadduser</c>.
233 </p>
130 </body> 234 </body>
131 </section> 235 </section>
132 <section> 236 <section>
133 <title>Why can't a user su to root?</title> 237 <title>Why can't a user su to root?</title>
134 <body><p>For security reasons, users may only <c>su</c> to root if they belong to the 238 <body><p>For security reasons, users may only <c>su</c> to root if they belong to the
207 function to 1.1. By using this option you just switch the MPS version. The Multi-Processor-System 311 function to 1.1. By using this option you just switch the MPS version. The Multi-Processor-System
208 will still work properly. Make sure to boot Gentoo Linux with the following boot option, noapic. </p> 312 will still work properly. Make sure to boot Gentoo Linux with the following boot option, noapic. </p>
209 </body> 313 </body>
210 </section> 314 </section>
211 315
316 <section>
317 <title>If I have Gentoo 1.4_rc1 can I upgrade to 1.4_rc2, 1.4_final/_rc3 without reinstalling?</title>
318 <body>
319 In fact there is no difference between the 1.4 releases <b>after they&apos;ve installed</b>. Gentoo 1.4 and later are <c>glibc-2.3.x</c> based.
320 As such 1.4rc1 machine for example, that does <c>emerge sync; emerge -u world</c> is <b>exactly the same</b> as a machine with 1.4rc2 installed, after it does <c>emerge sync; emerge -u world</c>. The true differences lie in the installer.
321 </body>
322 </section>
323 <section>
324 <title>My kernel doesn't boot (properly), what should I do now?</title>
325 <body>
326 <p>
327 You don't need to redo every step of the installation, but only the
328 kernel-stuff and all associated steps. Suppose you have installed Gentoo
329 on <path>/dev/hda1</path> (/boot) and <path>/dev/hda3</path> (/) with
330 <path>/dev/hda2</path> being the swap space:
331 </p>
332 <pre caption = "Reconfiguring the kernel">
333<comment>Boot from the LiveCD and wait until you receive a prompt</comment>
334<comment>We first mount all partitions:</comment>
335# <i>mount /dev/hda3 /mnt/gentoo</i>
336# <i>mount /dev/hda1 /mnt/gentoo/boot</i>
337# <i>swapon /dev/hda2</i>
338# <i>mount -t proc none /mnt/gentoo/proc</i>
339<comment>Then we chroot into our Gentoo environment and configure the kernel:</comment>
340# <i>chroot /mnt/gentoo /bin/bash</i>
341# <i>env-update &amp;&amp; source /etc/profile</i>
342# <i>cd /usr/src/linux</i>
343# <i>make menuconfig</i>
344<comment>Now (de)select anything you have (de)selected wrongly at your</comment>
345<comment>previous attempt. Then quit and compile your kernel:</comment>
346# <i>make dep &amp;&amp; make bzImage modules modules_install</i>
347<comment>Now copy over your bzImage file, overwriting your previous one:</comment>
348# <i>cp arch/i386/boot/bzImage /boot</i>
349<comment>If you use LILO, rerun lilo -- GRUB users should skip this:</comment>
350# <i>/sbin/lilo</i>
351<comment>Now exit the chroot and reboot.</comment>
352# <i>exit</i>
353# <i>umount /mnt/gentoo/proc /mnt/gentoo/boot /mnt/gentoo</i>
354# <i>reboot</i>
355 </pre>
356 <p>
357 If on the other hand the problem lays with your bootloader configuration,
358 follow the same steps, but instead of configuring/compiling your kernel you
359 should reconfigure your bootloader (recompilation isn't necessary).
360 </p>
361 </body>
362 </section>
363 <section>
364 <title>My proxy requires authentication, what do I have to do?</title>
365 <body>
366
367 <p>
368 When you have to download something using <c>wget</c>, use the
369 following syntax to authenticate yourself:
370 </p>
371<pre caption = "Proxy-authentication using wget">
372# <i>wget --proxy-user=</i><comment>username</comment><i> --proxy-passwd=</i><comment>password</comment><i> &lt;url&gt;</i>
373</pre>
374 <p>
375 To have Portage automatically use this scheme, define it in
376 <path>/etc/make.conf</path>:
377 </p>
378<pre caption = "/etc/make.conf">
379FETCHCOMMAND="wget --proxy-user=<comment>username</comment> --proxy-passwd=<comment>password</comment> -t 5 --passive-ftp -P \${DISTDIR} \${URI}"
380RESUMECOMMAND="/usr/bin/wget --proxy-user=<comment>username</comment> --proxy-passwd=<comment>password</comment> -c -t 5 --passive-ftp -P \${DISTDIR} \${URI}"
381</pre>
382 <p>
383 Sadly, <c>rsync</c> doesn't seem to support username/password
384 authentication for proxies. See <uri link="#doc_chap4_sect10">What
385 if rsync doesn't work for me?</uri> for more information on how to
386 handle this situation.
387 </p>
388
389 </body>
390 </section>
391
212</chapter> 392</chapter>
213 393
214<chapter> 394<chapter>
215 <title>Package Management</title> 395 <title>Package Management</title>
216 <section> 396 <section>
217 <title>In what format are the packages stored?</title> 397 <title>In what format are the packages stored?</title>
218 <body><p>They exist in our portage tree as <e>ebuild</e> autobuild scripts; we are primarily 398 <body><p>They exist in our portage tree as <e>ebuild</e> autobuild scripts; we are primarily
219 a ports-based distribution, meaning that we provide scripts (<c>.ebuild</c> files) and a 399 a ports-based distribution, meaning that we provide scripts (<c>.ebuild</c> files) and a
220 special system (Portage) so that you can build apps from sources. We generally only build 400 special system (Portage) so that you can build apps from sources. We generally only build
221 binaries for releases and snapshots. The <uri link="/doc/gentoo-howto.html">Development HOWTO 401 binaries for releases and snapshots. The <uri link="/doc/en/gentoo-howto.xml">Development HOWTO
222 </uri> covers the contents of an ebuild script in detail. For full binary ISO releases, we 402 </uri> covers the contents of an ebuild script in detail. For full binary ISO releases, we
223 create a full suite of binary packages in an enhanced <c>.tbz2</c> format (<c>.tar.bz2</c> 403 create a full suite of binary packages in an enhanced <c>.tbz2</c> format (<c>.tar.bz2</c>
224 compatible with meta-information attached to the end of the file.)</p> 404 compatible with meta-information attached to the end of the file.)</p>
225 </body> 405 </body>
226 </section> 406 </section>
245 </section> 425 </section>
246 426
247 <section> 427 <section>
248 <title>How do I install and uninstall packages?</title> 428 <title>How do I install and uninstall packages?</title>
249 <body> 429 <body>
250 <p>The <uri link="/doc/portage-user.html">Portage User Guide</uri> details how to install 430 <p>The <uri link="/doc/en/portage-user.xml">Portage User Guide</uri> details how to install
251 and uninstall packages, and update Portage.</p> 431 and uninstall packages, and update Portage.</p>
252 </body> 432 </body>
253 </section> 433 </section>
254 434
255 <section> 435 <section>
330 <c>emerge --help config</c> for more details. The (overly) simple answer is that if 510 <c>emerge --help config</c> for more details. The (overly) simple answer is that if
331 a package installs <path>foo</path> somewhere under <path>/etc</path>, and 511 a package installs <path>foo</path> somewhere under <path>/etc</path>, and
332 another <path>foo</path> already exists there, then the new <path>foo</path> will 512 another <path>foo</path> already exists there, then the new <path>foo</path> will
333 instead be renamed to <path>._cfgxxxx_foo</path> in that directory. A useful 513 instead be renamed to <path>._cfgxxxx_foo</path> in that directory. A useful
334 tool for examining and updating any protected config files is <c>etc-update</c>, 514 tool for examining and updating any protected config files is <c>etc-update</c>,
335 currently obtained by <c>emerge app-admin/gentoolkit</c>. 515 which is now part of Portage.
336 </p></body> 516 </p></body>
337 </section> 517 </section>
338 518
339 <section> 519 <section>
340 <title>I want to perform the <c>./configure</c> step myself. Can I?</title> 520 <title>I want to perform the <c>./configure</c> step myself. Can I?</title>
354 534
355 <section> 535 <section>
356 <title>What if rsync doesn't work for me?</title> 536 <title>What if rsync doesn't work for me?</title>
357 <body><p> 537 <body><p>
358 If you're behind a firewall that doesn't permit 538 If you're behind a firewall that doesn't permit
359 rsync traffic, then you can instead download the daily 539 rsync traffic, then you can use <c>emerge-webrsync</c> which will fetch
360 /usr/portage snapshots from 540 and install a Portage snapshot for you through regular HTTP.
361 <uri>http://cvs.gentoo.org/snapshots/</uri>. Just unpack 541 <c>emerge-webrsync</c> uses <c>wget</c> to download, so proxy is fully
362 the tarball (using <c>tar xvjf portage-foo.tbz2</c>) in 542 supported.
363 the <path>/usr</path> directory. 543 <pre caption="Using emerge-webrsync">
544~# <c>emerge-webrsync</c></pre>
545 If you cannot do this either, you can manually download a snapshot
546 from <uri>http://distro.ibiblio.org/pub/linux/distributions/gentoo/snapshots/</uri>.
547 In order to install the snapshot correctly, you first need to remove
548 your current <path>/usr/portage</path> so that outdated ebuilds don't
549 stay available on your system. However, you might want to put
550 <path>/usr/portage/distfiles</path> somewhere safe if you don't want to
551 lose all your sourcecode.
552 <pre caption="Manually installing the snapshots">
553<codenote>(First download the snapshot and place it in /usr)</codenote>
554~# <c>cd /usr</c>
555~# <c>mv /usr/portage/distfiles /usr/distfiles-temp</c>
556~# <c>rm -rf /usr/portage</c>
557~# <c>tar xvjf portage-foo.tbz2</c>
558~# <c>mv /usr/distfiles-temp /usr/portage/distfiles</c></pre>
364 </p></body> 559 </p></body>
365 </section> 560 </section>
366 561
367 <section> 562 <section>
368 <title>How do I use <i>emerge</i> from behind a firewall?</title> 563 <title>How do I use <i>emerge</i> from behind a firewall?</title>
382 <section> 577 <section>
383 <title>I have only slow modem connection at home. Can I download sources somewhere else and 578 <title>I have only slow modem connection at home. Can I download sources somewhere else and
384 add them to my system?</title> 579 add them to my system?</title>
385 <body><p> 580 <body><p>
386 Definitely. You can run <c>emerge --pretend package</c> to see what programs 581 Definitely. You can run <c>emerge --pretend package</c> to see what programs
582 are going to be installed. To find out the sources for those packages and where to
583 download the sources from, you can run <c>emerge -fp package</c>.
387 are going to be installed. Download sources and bring them on any media 584 Download sources and bring them on any media
388 home. Put the sources into <path>/usr/portage/distfiles</path> and run 585 home. Put the sources into <path>/usr/portage/distfiles</path> and run
389 <c>emerge package</c> to see it picking up the sources you just brought in! 586 <c>emerge package</c> to see it picking up the sources you just brought in!
390 </p></body> 587 </p></body>
391 </section> 588 </section>
392 589
402 again. 599 again.
403 </p></body> 600 </p></body>
404 </section> 601 </section>
405 602
406 <section> 603 <section>
407 <title>How can I manage my own ebuilds without destroying them by (r)sync?</title>
408 <body>
409 <p>The simplest method is to use anonymous CVS instead of rsync, and
410 maintain your local
411 ebuilds in /usr/portage/local. Here's how to do it:</p>
412 <pre>
413# <i>emerge cvs</i> <comment>(if necessary)</comment>
414# <i>cd <path>/usr</path></i>
415# <i>cvs -d :pserver:anonymous@gentoo.org:/home/anoncvs login</i> <comment>(hit &lt;enter&gt;)</comment>
416# <i>cvs -d :pserver:anonymous@gentoo.org:/home/anoncvs get gentoo-x86</i>
417# <i>cp /usr/portage/distfiles/* gentoo-x86/distfiles/</i>
418# <i>cp -a /usr/portage/packages/* gentoo-x86/packages/</i>
419# <i>mv portage portage.old</i>
420# <i>ln -s gentoo-x86 portage</i>
421# <i>mkdir /usr/portage/local</i>
422# <i>echo local &gt;&gt; /usr/portage/profiles/categories</i>
423# <i>cp /etc/make.conf /etc/make.conf.orig</i>
424# <i>sed -e 's/#SYNC="cvs/SYNC="cvs/' /etc/make.conf.orig &gt; /etc/make.conf</i>
425 </pre>
426 </body>
427 </section>
428
429 <section>
430 <title>I went to emerge blackdown-jdk and blackdown-jre, and afterwards 604 <title>I went to emerge blackdown-jdk and blackdown-jre, and afterwards
431 <c>java-config --list-available-vms</c> would only list blackdown-jre. 605 <c>java-config --list-available-vms</c> would only list blackdown-jre.
432 Openoffice would then refuse to emerge. What do I do? </title> 606 Openoffice would then refuse to emerge. What do I do? </title>
433 607
434 <body> 608 <body>
436 <pre caption = "Solution"> 610 <pre caption = "Solution">
437# <c>emerge unmerge blackdown-jre blackdown-jdk </c> 611# <c>emerge unmerge blackdown-jre blackdown-jdk </c>
438# <c>CONFIG_PROTECT="" emerge blackdown-jdk </c> 612# <c>CONFIG_PROTECT="" emerge blackdown-jdk </c>
439 </pre> 613 </pre>
440 614
615 </body>
616 </section>
617 <section>
618 <title>What's in <path>/var/tmp/portage</path>? Is it safe to delete the files and directories in <path>/var/tmp/portage</path>?</title>
619 <body>
620 During compilation, Gentoo saves the sources of the package in <path>/var/tmp/portage</path>. It is safe to clean out all contents of this directory.
441 </body> 621 </body>
442 </section> 622 </section>
443</chapter> 623</chapter>
444 624
445<chapter> 625<chapter>
488 </path>, so that it reads as follows:</p> 668 </path>, so that it reads as follows:</p>
489 <pre>#!/bin/sh --login</pre> 669 <pre>#!/bin/sh --login</pre>
490 <p>This fix has been added to recent versions of KDE.</p> 670 <p>This fix has been added to recent versions of KDE.</p>
491 </body> 671 </body>
492 </section> 672 </section>
673
674 <section>
675 <title>Why can't my user use their own crontab?</title>
676 <body><p>You need to add that user to the <i>cron</i> group.
677 </p>
678 </body>
679 </section>
680
681 <section>
682 <title>How do I get numlock to start on boot?</title>
683 <body>
684 <p>
685 If you log on graphically, or want numlock to be activated when
686 you issue <c>startx</c>, then you must <c>emerge numlockx</c> and
687 add <c>/usr/X11R6/bin/numlockx</c> to
688 <path>/etc/X11/xinit/xinitrc</path> (for <c>startx</c>) or
689 <path>/etc/X11/Sessions/</path> (for any graphical login manager) such
690 as <path>/etc/X11/Sessions/Gnome</path> for GDM.
691 </p>
692 <p>
693 If you work in commandline, you only need to <c>rc-update add
694 numlock default</c> and numlock will be activated on the next
695 reboot.
696 </p>
697 </body>
698 </section>
699 <section>
700 <title>How do I have my terminal cleared when I log out?</title>
701 <body>
702 <p>
703 To have your terminal cleared, add <c>clear</c> to your
704 <path>~/.bash_logout</path> script:
705 </p>
706 <pre caption = "Clearing the terminal during logout">
707$ <i>echo clear &gt;&gt; ~/.bash_logout</i></pre>
708 <p>
709 If you want this to happen automatically when you add a new
710 user, do the same for the <path>/etc/skel/.bash_logout</path>:
711 </p>
712 <pre caption = "Making new users their terminal clear on logout">
713# <i>echo clear &gt;&gt; /etc/skel/.bash_logout</i></pre>
714 </body>
715 </section>
716
717
493</chapter> 718</chapter>
494 719
495<chapter> 720<chapter>
496 <title>Maintenance</title> 721 <title>Maintenance</title>
497 <section> 722 <section>
514 <body> 739 <body>
515 <p>To view multilog (Gentoo Linux 1.0_rc5 and earlier) timestamps, you need to pipe the 740 <p>To view multilog (Gentoo Linux 1.0_rc5 and earlier) timestamps, you need to pipe the
516 current log through the <c>tai64nlocal</c>command:</p> 741 current log through the <c>tai64nlocal</c>command:</p>
517 742
518<pre> 743<pre>
519# <i>cat /var/log/syslog.d/current | tai64nlocal | less</i> 744# <i>tai64nlocal &lt; /var/log/syslog.d/current | less</i>
520</pre> 745</pre>
521 746
522<p>Or, alternatively, if you want to "tail" the log:</p> 747<p>Or, alternatively, if you want to "tail" the log:</p>
523 748
524<pre> 749<pre>
525# <i>tail -f /var/log/syslog.d/current | tai64nlocal</i> 750# <i>tail -f /var/log/syslog.d/current | tai64nlocal</i>
526</pre> 751</pre>
527 752
528</body> 753</body>
529 </section> 754 </section>
755 <section>
756 <title>Metalogd doesn't log in real time!</title>
757 <body>
758
759<p>
760Metalog flushes output to the disk in blocks, so messages aren't immediately
761recorded into the system logs. If you are trying to debug a daemon, this
762performance-enhancing behavior is less than helpful. When your Gentoo Linux
763system is up and running, you can send metalog a USR1 signal to temporarily
764turn off this message buffering (meaning that <c>tail -f
765<path>/var/log/everything/current</path></c> will now work in real time, as
766expected) and a USR2 signal to turn buffering back on again. If you want to
767disable buffering permanently, you can change METALOG_OPTS="-B" to
768METALOG_OPTS="-B -s" in <path>/etc/conf.d/metalog</path>.
769</p>
770
771<pre caption="Turning metalog buffering on/off">
772<codenote>To turn the buffering off:</codenote>
773# <i>killall -USR1 metalog</i>
774<codenote>To turn the buffering back on:</codenote>
775# <i>killall -USR2 metalog</i>
776</pre>
777
778 </body>
779 </section>
530</chapter> 780</chapter>
531 781
532<chapter> 782<chapter>
533 <title>Development</title> 783 <title>Development</title>
534 <section> 784 <section>
535 <title>Where can I report bugs?</title> 785 <title>Where can I report bugs?</title>
536 <body><p>For bugs within a specific program, contact the program's author. Otherwise, use our 786 <body><p>For bugs within a specific program, contact the program's author. Otherwise, use our
537 Bugzilla bug tracker at <uri>http://bugs.gentoo.org</uri>. You can also visit us in 787 Bugzilla bug tracker at <uri>http://bugs.gentoo.org</uri>. You can also visit us in
538 <c>#gentoo</c> on the <uri link="http://www.openprojects.net">OpenProjects</uri> IRC network. 788 <c>#gentoo</c> on the <uri link="http://www.freenode.net">FreeNode</uri> IRC network.
539 </p></body> 789 </p></body>
540 </section> 790 </section>
541 791
542 <section> 792 <section>
543 <title>How often are new releases made?</title> 793 <title>How often are new releases made?</title>
544 <body><p>New releases are announced on the <uri link="http://lists.gentoo.org/mailman/listinfo/gentoo-announce">gentoo-announce</uri> 794 <body><p>New releases are announced on the <uri link="http://www.gentoo.org/main/en/lists.xml">gentoo-announce</uri>
545 mailing list<!-- TODO: approximatley every X months -->, In reality the packages themselves 795 mailing list<!-- TODO: approximatley every X months -->, In reality the packages themselves
546 are updated shortly after the main authors release new code. As for when new Cd images etc 796 are updated shortly after the main authors release new code. As for when new Cd images etc
547 are released, that tends to be whenever there are any major updates to the base code, or when 797 are released, that tends to be whenever there are any major updates to the base code, or when
548 new modules get added.</p></body> 798 new modules get added.</p></body>
549 </section> 799 </section>
555 </section> 805 </section>
556 806
557 <section> 807 <section>
558 <title>How can I add a question or answer to this FAQ?</title> 808 <title>How can I add a question or answer to this FAQ?</title>
559 <body><p>Submit a new bug over at <uri>http://bugs.gentoo.org</uri> and add it to the 809 <body><p>Submit a new bug over at <uri>http://bugs.gentoo.org</uri> and add it to the
560 "Docs-user" product.</p></body> 810 "Docs-user" product, "Gentoo Linux FAQ" component.</p></body>
561 </section> 811 </section>
562 812
563 <section> 813 <section>
564 <title>make -f Makefile.cvs on a KDE app produces "invalid unused variable" errors</title> 814 <title>make -f Makefile.cvs on a KDE app produces "invalid unused variable" errors</title>
565 <body><p> 815 <body><p>
651 </section> 901 </section>
652 902
653 <section> 903 <section>
654 <title>This FAQ hasn't answered my question. What do I do now?</title> 904 <title>This FAQ hasn't answered my question. What do I do now?</title>
655 <body> 905 <body>
656 <p>A good first step is to browse through the relevant doumentation <uri link="http://www.gentoo.org/index-docs.html">here</uri>, 906 <p>A good first step is to browse through the relevant doumentation <uri link="http://www.gentoo.org/main/en/docs.xml">here</uri>,
657 failing that, the various Gentoo Linux mailing 907 failing that, the various Gentoo Linux mailing
658 lists listed on <uri link="http://www.google.com">Google</uri>. To search through the Gentoo mailling lists, just enter "lists.gentoo.org foo" to search for "foo". If all else fails, or you just want 908 lists listed on <uri link="http://www.google.com">Google</uri>. To search through the Gentoo mailling lists,
909 just enter "lists.gentoo.org foo" to search for "foo". If all else fails, or you just want
659 to hang out with Gentoo folks, visit us on irc: <i>#gentoo</i> 910 to hang out with Gentoo folks, visit us on irc: <i>#gentoo</i>
660 on <i>irc.freenode.net</i>. 911 on <i>irc.freenode.net</i>.
661 </p> 912 </p>
662 </body> 913 </body>
663 </section> 914 </section>

Legend:
Removed from v.1.12  
changed lines
  Added in v.1.42

  ViewVC Help
Powered by ViewVC 1.1.20