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

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

Parent Directory Parent Directory | Revision Log Revision Log


Revision 1.7 - (hide annotations) (download) (as text)
Fri Dec 6 20:55:43 2002 UTC (11 years, 4 months ago) by zhen
Branch: MAIN
Changes since 1.6: +2 -2 lines
File MIME type: application/xml
changed simple tag error

1 zhen 1.3 <?xml version='1.0' encoding="UTF-8"?>
2 drobbins 1.1 <?xml-stylesheet href="/xsl/guide.xsl" type="text/xsl"?>
3    
4     <!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
5    
6 zhen 1.2 <guide link="/doc/en/faq.xml">
7 drobbins 1.1 <title>Gentoo Linux Frequently Asked Questions</title>
8     <author title="Chief Architect"><mail link="drobbins@gentoo.org">Daniel Robbins</mail></author>
9     <author title="Reviewer">Colin Morey</author>
10     <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>
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>
13    
14     <version>1.1.2</version>
15 zhen 1.5 <date>20 November 2002</date>
16 drobbins 1.1
17     <chapter>
18     <title>Getting Started</title>
19    
20     <section>
21     <title>How is Gentoo pronounced, and what does it mean?</title>
22     <body><p>Gentoo is a species of small fast penguin, pronounced "jen-two".</p></body>
23     </section>
24    
25     <section>
26     <title>What makes Gentoo different?</title>
27     <body>
28     <p>Gentoo Linux is a fast, modern distribution with a clean and flexible
29     design -- in this respect, Gentoo may appeal to
30     <uri link="http://www.slackware.com/">Slackware</uri>,
31     <uri link="http://www.linuxfromscratch.org">Linux From Scratch</uri> or
32     <uri link="http://www.bsd.org">BSD</uri> users. Unlike most Linux
33     distros, Gentoo has a package system reminiscent of BSD's ports,
34     meaning the packages are continually updated to the lastest
35     versions.
36 zhen 1.5 </p>
37     </body>
38     </section>
39     </chapter>
40 drobbins 1.1
41     <chapter>
42     <title>Installation</title>
43 zhen 1.6
44 zhen 1.7 <warning>REPORT all bugs to <uri>bugs.gentoo.org</uri>! Do not report bugs to upstream (original)
45 zhen 1.6 authors. Report the bugs to Gentoo, and we will move them upstream if necessary.
46 zhen 1.7 </warning>
47 drobbins 1.1
48     <section>
49     <title>What is the difference between the .iso and .tbz2 files?</title>
50     <body><p>The build <e>.tbz2</e> file is a minimal set of system files
51     that is necessary for allowing a user to bootstrap and install
52     Gentoo Linux. The build <e>.iso</e> is a complete, bootable CD image that
53     contains a system kernel, a reasonably complete set of kernel modules,
54     necessary system tools such as <c>mkfs</c> and networking support,
55     as well as the <e>.tbz2</e> minimal-system tarball. Most users will install
56     Gentoo Linux by burning the .iso file onto a CD, booting off of the CD,
57     and installing from within the minimal linux environment provided by
58     the Gentoo boot CD. It is possible, however, for users to install
59     Gentoo Linux directly from an already-existing Linux distribution.
60     Such users need only download the .tbz2 file, install the contents
61     on a spare partition (making sure to use the <c>p</c> flag when
62     untarring the tarball!), chroot, and install in the usual fashion.</p>
63     </body>
64     </section>
65    
66     <section>
67     <title>Why do the build .iso and .tbz2 files sometimes have different -r (revision) numbers?</title>
68     <body><p>
69     The .tbz2 minimal-system tarball only needs to be revised when there have
70     been significant changes to the core Gentoo Linux system (such as baselayout
71     changes, or a new profile), and as such .tbz2 updates are relatively rare.
72     The .iso file tends to get updated whenever we discover that somebody has
73     hardware that won't boot from our .iso. Since new kernel modules and
74     patches are constantly being generated, this situation probably won't
75     stabilise anytime soon.
76     </p>
77     </body>
78     </section>
79    
80     <section>
81     <title>I have a Sony Super-Slim VAIO laptop, and the Gentoo Linux CD is having problems
82     finding my PCMCIA ATAPI CD-ROM.</title>
83     <body>
84     <p>Make sure the second IDE port is set to CDROM (it unsets itself if the device isn't
85     attached on boot) then do the following at the isolinux <c>boot:</c> prompt:</p>
86     <pre>
87     boot: <i>rescue ide2=0x180,0x386</i>
88     </pre>
89     <p>If you are using a 1.0_rc5 or earlier boot CD, apart from thinking about downloading the latest iso,
90     type <c>gentoo</c> instead of <c>rescue</c>, above.</p>
91     </body>
92    
93     </section>
94     <section>
95     <title>I'm finding things to be really unstable and I'm using "-O9 -ffast-math
96     -fomit-frame-pointer" optimizations. What gives?</title>
97     <body>
98     <p>When you use any optimizations beyond <c>-O3</c>, you're really taking the risk of
99     having broken packages.
100     Very aggressive optimizations sometimes cause the compiler to streamline the assembly code
101     to the point where it doesn't quite do the same thing anymore. <e>Loc-Dog</e> (on IRC)
102     uses <c>-O3 -mcpu=i686 -march=i686 -fforce-addr -fomit-frame-pointer -funroll-loops
103     -frerun-cse-after-loop -frerun-loop-opt -malign-functions=4</c>, which is about
104     as much as I'd want to push global optimization settings. Beyond this, it's best to use
105     ultra-high optimizations only with specific packages where you really need that extra 2%,
106     (eg graphics and various multimedia programs), and where you can easily test the package
107     to ensure that it hasn't been optimized into oblivion.</p>
108 zhware 1.4 <p>Please try first to compile with CFLAGS <c>-march= -O2</c> before reporting a bug</p>
109 drobbins 1.1 </body>
110     </section>
111    
112     <section>
113     <title>What's the default root password after installation?</title>
114     <body><p>The default password is blank; hit enter.</p></body>
115     </section>
116    
117     <section>
118     <title>How can i change the root (or indeed any other user's) password?</title>
119     <body><p>You can use <c>passwd</c> to change the password for the user you are logged into.
120     for extra options and setting, please see <c>man passwd</c> once you've completed the install.
121     </p></body>
122     </section>
123     <section>
124     <title>How do i add a normal user?</title>
125     <body><p>Everyone seems to think that i shouldn't be using <e>root</e> for everyday use,
126     how can i add another user?</p>
127     <p>The command <c>adduser gentoo</c> will add a user called gentoo. The next step is to give
128     this user a password and <c>passwd</c> will do exactly that.</p>
129     </body>
130     </section>
131     <section>
132     <title>Why can't a user su to root?</title>
133     <body><p>For security reasons, users may only <c>su</c> to root if they belong to the
134     <e>wheel</e> group. To add a <i>username</i> to the <e>wheel</e> group, issue the following
135     command as root:</p>
136     <pre># <i>usermod -G users,wheel username</i></pre>
137     </body>
138     </section>
139     <section>
140     <title>How do I enable devfs?</title>
141     <body>
142     <p>
143     If you're using 1.0_rc5 or greater, you don't need to do anything special to get
144     devfs working; it's already active (you did make sure that devfs was built into the
145     kernel, didn't you?).
146     However, if you are using a version of Gentoo Linux <e>prior</e> to version 1.0_rc5, add
147     <c>devfs=mount</c> to your <c>GRUB</c> kernel boot options so that the line looks something
148     like <c>kernel /boot/boot/bzImage devfs=mount foo=bar</c> The kernel will then mount the
149     <path>/dev</path> <e>devfs</e> filesystem automatically at boot-time.
150     </p>
151     </body>
152     </section>
153     <section>
154     <title>How to I disable devfs?</title>
155     <body>
156     <p>Under Gentoo Linux 1.0_rc6 and later, you can disable devfs by passing the
157     <c>gentoo=nodevfs</c> to the kernel.</p>
158     </body>
159     </section>
160     <section>
161     <title>How do I get a <path>/dev/mouse </path> that
162     doesn't go away when I reboot (when using devfs)?</title>
163     <body>
164     <p>
165     If you are using 1.0_rc6 or later, then you can just use <c>ln -s</c>
166     to make the usual symbolic link from <path>/dev/mouse</path>, and
167     it will be preserved between reboots.
168     </p>
169     <p>All other users need to edit <path>/etc/devfsd.conf</path>
170     and add these lines:</p>
171     <pre>
172     REGISTER ^misc/psaux$ CFUNCTION GLOBAL symlink misc/psaux mouse
173     UNREGISTER ^misc/psaux$ CFUNCTION GLOBAL unlink mouse
174     </pre>
175     <p>If you are not using the devfs PS/2 mouse <path>/dev/misc/psaux</path> device,
176     adjust the <c>misc/psaux</c> strings above accoringly. You'll then want to
177     <c>killall -HUP devfsd</c>
178     to get devfsd to reread <path>/etc/devfsd.conf</path>.</p>
179     </body>
180     </section>
181     <section>
182     <title>Grub can't find stage x.y?</title>
183     <body><p>
184     During installation the grub boot files are copied
185     to <path>/boot/grub</path> (<path>/boot/boot/grub</path> in Gentoo Linux 1.0_rc5 and
186     earlier.) Grub automatically looks in the <path>/boot/grub</path> directory on the boot
187     partition. (We strongly recommend having a separate no-auto boot partition mounted at
188     <path>/boot</path>, since that way it is much more difficult to clobber your kernel and boot
189     info by accident.) The above error generally arises from (a) not using a separate boot
190     partition, (b) forgetting to mount the boot partition at <path>/boot</path> before either
191     unpacking the build snapshot or running
192     <c>emerge --usepkg system</c>, or (c) forgetting the
193     <c>notail</c> option when mounting a ReiserFS <path>/boot</path> partition.
194     You can get more information on grub, including how to
195     debug grub from the grub prompt, by reading the
196     <uri link="http://www-105.ibm.com/developerworks/education.nsf/linux-onlinecourse-bytitle/0F1731DC664023B7862569D0005C44AF?OpenDocument">IBM developerWorks Grub tutorial</uri>.
197     </p>
198     </body>
199     </section>
200    
201     <section>
202     <title>My ASUS CUV4X-D won't boot and it freezes during various stages of kernel loading and hardware
203     detection. </title>
204     <body>
205     <p>Disable MPS 1.4 (multi-processor-system) in the BIOS or switch this
206     function to 1.1. By using this option you just switch the MPS version. The Multi-Processor-System
207     will still work properly. Make sure to boot Gentoo Linux with the following boot option, noapic. </p>
208     </body>
209     </section>
210    
211     </chapter>
212    
213     <chapter>
214     <title>Package Management</title>
215     <section>
216     <title>In what format are the packages stored?</title>
217     <body><p>They exist in our portage tree as <e>ebuild</e> autobuild scripts; we are primarily
218     a ports-based distribution, meaning that we provide scripts (<c>.ebuild</c> files) and a
219     special system (Portage) so that you can build apps from sources. We generally only build
220     binaries for releases and snapshots. The <uri link="/doc/gentoo-howto.html">Development HOWTO
221     </uri> covers the contents of an ebuild script in detail. For full binary ISO releases, we
222     create a full suite of binary packages in an enhanced <c>.tbz2</c> format (<c>.tar.bz2</c>
223     compatible with meta-information attached to the end of the file.)</p>
224     </body>
225     </section>
226    
227     <section>
228     <title>Why write a new port system (Portage) instead of using BSD's version?</title>
229     <body>
230     <p>In one sentence, because Portage is much better in so many ways. One of the design
231     philosophies of the <c>.ebuild</c> syntax was to make it an analog of what you'd type to
232     install the program manually, thus making Portage very easy to learn and modify to your
233     needs. We also have OpenBSD-style "fake" installs, safe unmerging, system profiles,
234     package masking, a real dependency system, and lots of other good stuff.</p>
235     </body>
236     </section>
237    
238     <section>
239     <title>How does this differ from Debian's apt or BSD's ports?</title>
240     <body><p>Portage features the best of apt and ports; for example, USE options, a full
241     dependency system, safe installs and uninstalls, and a true package database. Think of
242     Portage as the best of both worlds; a ports system with the sensibilities and safety of a
243     Linux package management system built-in.</p></body>
244     </section>
245    
246     <section>
247     <title>How do I install and uninstall packages?</title>
248     <body>
249     <p>The <uri link="/doc/portage-user.html">Portage User Guide</uri> details how to install
250     and uninstall packages, and update Portage.</p>
251     </body>
252     </section>
253    
254     <section>
255     <title>How can I set a global configuration for compiling packages?</title>
256     <body><p><path>/etc/make.conf</path> should be modified to override global and
257     profile-specific default options used to compile and merge packages. The most common options
258     are as follows:</p>
259     <table>
260     <tr>
261     <th>Flag</th>
262     <th>Description</th>
263     </tr>
264     <tr>
265     <ti>CHOST</ti>
266     <ti>This sets the HOST variable for compiles, e.g. <c>i686-pc-linux-gnu</c></ti>
267     </tr>
268     <tr>
269     <ti>CFLAGS</ti>
270     <ti>The options for <c>gcc</c> when compiling programs written in C (*.c files)</ti>
271     </tr>
272     <tr>
273     <ti>CXXFLAGS</ti>
274     <ti>The options for <c>gcc</c> when compiling programs written in C++ (*.c,*.cpp etc.
275     files)</ti>
276     </tr>
277     <tr>
278     <ti>USE</ti>
279     <ti>This allows you to set what optional components you'd like compiled-in, if
280     available. For example, if you have <c>gnome</c> inside the USE string, then when
281     you compile <c>xchat</c>, it will include GNOME support. All our dependencies are
282     also USE-aware.</ti>
283     </tr>
284     <tr>
285     <ti>GENTOO_MIRRORS</ti>
286     <ti>A space separated list of URIs currently mirroring the Gentoo packages. Portage
287     will attempt download from a <c>GENTOO_MIRROR</c> first before trying the official
288     <c>SRC_URI</c>. To force Portage to skip mirrors, set this variable to "".</ti>
289     </tr>
290     </table>
291     </body>
292     </section>
293    
294     <section>
295     <title>What happened to <path>/etc/make.defaults</path>?</title>
296     <body>
297     <p>As of Portage 1.5 onwards, <path>/etc/make.defaults</path> is antiquated;
298     if you have portage-1.5-r1 or above installed then you can safely delete it.
299     This file has been replaced by <path>/etc/make.profile/make.defaults</path>
300     (<path>/etc/make.profile</path> should actually be a symlink to,
301     <path>/usr/portage/profiles/default</path>),
302     which contains system profile-specific default settings. The priority order of
303     the various configuration files is as follows (highest first):
304     <ol>
305     <li>Environment variables</li>
306     <li><path>/etc/make.conf</path>, for your use</li>
307     <li><path>/etc/make.profile/make.defaults</path>, for profile-specific defaults</li>
308     <li><path>/etc/make.globals</path>, for global defaults (settings not specified in
309     any other place come from here)</li>
310     </ol></p></body>
311     </section>
312    
313     <section>
314     <title>Is there a way to upgrade all installed packages
315     e.g. <e>apt-get upgrade</e> or <e>make World</e>?</title>
316     <body><p><b>YES!</b> Type <c>emerge --update system</c> (use it with <c>--pretend</c> first) to
317     update all core system packages, and use <c>emerge --update world</c> (again, use it with
318     <c>--pretend</c> first) to do a complete system upgrade of all installed packages.
319    
320    
321     </p></body>
322     </section>
323    
324     <section>
325     <title>When updating a package using <c>emerge</c> or <c>ebuild</c>, how do I avoid
326     clobbering my config files?</title>
327     <body><p>
328     Portage now includes config file management support by default. Type
329     <c>emerge --help config</c> for more details. The (overly) simple answer is that if
330     a package installs <path>foo</path> somewhere under <path>/etc</path>, and
331     another <path>foo</path> already exists there, then the new <path>foo</path> will
332     instead be renamed to <path>._cfgxxxx_foo</path> in that directory. A useful
333     tool for examining and updating any protected config files is <c>etc-update</c>,
334     currently obtained by <c>emerge app-admin/gentoolkit</c>.
335     </p></body>
336     </section>
337    
338     <section>
339     <title>I want to perform the <c>./configure</c> step myself. Can I?</title>
340     <body><p>
341     Yes, but it is not trivial. First do <c>man ebuild</c> followed by
342     <c>ebuild foo-x.y.z.ebuild unpack</c>. Then <c>cd</c> to
343     <path>/var/tmp/portage/foo-x.y.z/work</path>. You can manually perform
344     the <c>./configure</c> and <c>make</c> steps yourself (you'll have to do
345     both, since Portage does not separate the configure and build steps). To
346     have Portage finish the installation (so that you can easily remove it later,
347     should you desire to do so, and it will be registered in Portage as a possible
348     dependency) you first need to <c>touch /var/tmp/portage/foo-x.y.z/.compiled</c>
349     (tricking Portage into thinking that <c>ebuild foo-x.y.z.ebuild compile</c> has
350     completed), followed by <c>ebuild foo-x.y.z.ebuild merge</c>.
351     </p></body>
352     </section>
353    
354     <section>
355     <title>What if rsync doesn't work for me?</title>
356     <body><p>
357     If you're behind a firewall that doesn't permit
358     rsync traffic, then you can instead download the daily
359     /usr/portage snapshot from
360     <uri>http://cvs.gentoo.org/snapshots</uri>. Just unpack
361     the tarball (using <c>tar xvjf portage-foo.tbz2</c>) in
362     the <path>/usr</path> directory.
363     </p></body>
364     </section>
365    
366     <section>
367     <title>How do I use <i>emerge</i> from behind a firewall?</title>
368     <body><p>
369     Edit the PROXY settings in <path>/etc/make.conf</path>. If that doesn't work,
370     edit <path>/etc/wget/wgetrc</path> and edit http_proxy and ftp_proxy
371     appropriately.
372     </p></body>
373     </section>
374    
375     <section>
376     <title>Can I rsync from another operating system?</title>
377     <body><p>There's a program called unison that works under both UNIX and Win32, available from
378     <uri>http://www.cis.upenn.edu/~bcpierce/unison/</uri>.</p></body>
379     </section>
380    
381     <section>
382     <title>I have only slow modem connection at home. Can I download sources somewhere else and
383     add them to my system?</title>
384     <body><p>
385     Definitely. You can run <c>emerge --pretend package</c> to see what programs
386     are going to be installed. Download sources and bring them on any media
387     home. Put the sources into <path>/usr/portage/distfiles</path> and run
388     <c>emerge package</c> to see it picking up the sources you just brought in!
389     </p></body>
390     </section>
391    
392     <section>
393     <title>.tar.gz sources for installed software are piling up in /usr/portage/distfiles/ using
394     valuable space. Is it safe to delete these files?</title>
395     <body><p>
396     Yes, you can safely delete these files. But if you are on a slow
397     connection, such as a modem, you might want to keep the archives if
398     possible; often several ebuilds will be released for the same version of
399     a specific piece of software - if you have deleted the archive and you
400     upgrade the software it will have to be downloaded from the internet
401     again.
402     </p></body>
403     </section>
404    
405     <section>
406     <title>How can I manage my own ebuilds without destroying them by (r)sync?</title>
407     <body>
408     <p>The simplest method is to use anonymous CVS instead of rsync, and
409     maintain your local
410     ebuilds in /usr/portage/local. Here's how to do it:</p>
411     <pre>
412     # <i>emerge cvs</i> <comment>(if necessary)</comment>
413     # <i>cd <path>/usr</path></i>
414     # <i>cvs -d :pserver:anonymous@gentoo.org:/home/anoncvs login</i> <comment>(hit &lt;enter&gt;)</comment>
415     # <i>cvs -d :pserver:anonymous@gentoo.org:/home/anoncvs get gentoo-x86</i>
416     # <i>cp /usr/portage/distfiles/* gentoo-x86/distfiles/</i>
417     # <i>cp -a /usr/portage/packages/* gentoo-x86/packages/</i>
418     # <i>mv portage portage.old</i>
419     # <i>ln -s gentoo-x86 portage</i>
420     # <i>mkdir /usr/portage/local</i>
421     # <i>echo local &gt;&gt; /usr/portage/profiles/categories</i>
422     # <i>cp /etc/make.conf /etc/make.conf.orig</i>
423     # <i>sed -e 's/#SYNC="cvs/SYNC="cvs/' /etc/make.conf.orig &gt; /etc/make.conf</i>
424     </pre>
425 zhen 1.5 </body>
426     </section>
427    
428     <section>
429     <title>I went to emerge blackdown-jdk and blackdown-jre, and afterwards
430     <c>java-config --list-available-vms</c> would only list blackdown-jre.
431     Openoffice would then refuse to emerge. What do I do? </title>
432    
433     <body>
434     <p>Solution: </p>
435     <pre caption = "Solution">
436     # <c>emerge unmerge blackdown-jre blackdown-jdk </c>
437     # <c>CONFIG_PROTECT="" emerge blackdown-jdk </c>
438     </pre>
439    
440 drobbins 1.1 </body>
441     </section>
442     </chapter>
443    
444     <chapter>
445     <title>Usage</title>
446     <section>
447     <title>I have installed openssh on my box, but can only log in as root - my normal user
448     account doesn't work. </title>
449     <body>
450     <p>
451     This is most probably because your user account doesn't have a valid shell specified. Check
452     for your user entry in
453     <path>/etc/passwd</path> and see if it ends in /bin/bash (or any other shell). If it doesn't,
454     you must set a shell for the user. This is done using the usermod command, like this ;
455     </p>
456     <pre># <i>usermod -s /bin/bash myuser</i></pre>
457     </body>
458     </section>
459    
460     <section>
461     <title>I can start X applications as root only.</title>
462     <body><p>Your <path>/tmp</path> directory has the wrong permissions (it needs the sticky bit
463     set). Type the following as root:</p>
464     <pre># <i>chmod 1777 /tmp</i></pre>
465     </body>
466     </section>
467    
468     <section>
469     <title>How do I set up an International Keyboard Layout?</title>
470     <body><p>Edit the <c>KEYMAP</c> variable in <path>/etc/rc.conf</path>.
471     Then either reboot or restart the keymaps script:
472     <c>/etc/init.d/keymaps restart</c>.</p>
473     </body>
474     </section>
475    
476     <section>
477     <title>DNS name resolution works for root only.</title>
478     <body><p><path>/etc/resolv.conf</path> has the wrong permissions; <c>chmod</c> it as follows:
479     </p>
480     <pre># <i>chmod 0644 /etc/resolv.conf</i></pre>
481     </body>
482     </section>
483    
484     <section>
485     <title>Why is KDE not reading <path>/etc/profile</path>?</title>
486     <body><p>You need to add <c>--login</c> to the first line in <path>/opt/kde2.1/bin/startkde
487     </path>, so that it reads as follows:</p>
488     <pre>#!/bin/sh --login</pre>
489     <p>This fix has been added to recent versions of KDE.</p>
490     </body>
491     </section>
492     </chapter>
493    
494     <chapter>
495     <title>Maintenance</title>
496     <section>
497     <title>ReiserFS and filesystem corruption issues -- how to fix'em, etc</title>
498     <body>
499     <p>
500     If your
501     ReiserFS partition is corrupt, try booting the Gentoo
502     Linux boot CD and run <c>reiserfsck --rebuild-tree</c> on
503     the corrupted filesystem. This should make the filesystem consistent
504     again, although you may have lost some files or directories due
505     to the corruption.
506     </p>
507     </body>
508     </section>
509     <!-- is this still relevant? -cpm -->
510     <section>
511     <title>How to I view the timestamps in /var/log/syslog.d, etc. on a pre-1.0_rc5 Gentoo
512     system?</title>
513     <body>
514     <p>To view multilog (Gentoo Linux 1.0_rc5 and earlier) timestamps, you need to pipe the
515     current log through the <c>tai64nlocal</c>command:</p>
516    
517     <pre>
518     # <i>cat /var/log/syslog.d/current | tai64nlocal | less</i>
519     </pre>
520    
521     <p>Or, alternatively, if you want to "tail" the log:</p>
522    
523     <pre>
524     # <i>tail -f /var/log/syslog.d/current | tai64nlocal</i>
525     </pre>
526    
527     </body>
528     </section>
529     </chapter>
530    
531     <chapter>
532     <title>Development</title>
533     <section>
534     <title>Where can I report bugs?</title>
535     <body><p>For bugs within a specific program, contact the program's author. Otherwise, use our
536     Bugzilla bug tracker at <uri>http://bugs.gentoo.org</uri>. You can also visit us in
537     <c>#gentoo</c> on the <uri link="http://www.openprojects.net">OpenProjects</uri> IRC network.
538     </p></body>
539     </section>
540    
541     <section>
542     <title>How often are new releases made?</title>
543     <body><p>New releases are announced on the <uri link="http://lists.gentoo.org/mailman/listinfo/gentoo-announce">gentoo-announce</uri>
544     mailing list<!-- TODO: approximatley every X months -->, In reality the packages themselves
545     are updated shortly after the main authors release new code. As for when new Cd images etc
546     are released, that tends to be whenever there are any major updates to the base code, or when
547     new modules get added.</p></body>
548     </section>
549    
550     <section>
551     <title>I would like a package to be added to Portage; how would I go about this?</title>
552     <body><p>Head over to <uri>http://bugs.gentoo.org</uri> and submit a new bug of the type
553     "ebuild". Attach your ebuild to the bug report.</p></body>
554     </section>
555    
556     <section>
557     <title>How can I add a question or answer to this FAQ?</title>
558     <body><p>Submit a new bug over at <uri>http://bugs.gentoo.org</uri> and add it to the
559     "Docs-user" product.</p></body>
560     </section>
561    
562     <section>
563     <title>make -f Makefile.cvs on a KDE app produces "invalid unused variable" errors</title>
564     <body><p>
565     Export <c>WANT_AUTOMAKE_1_4=1</c> for all KDE projects before running
566     <c>make -f Makefile.cvs</c>. Also, for KDE2 apps export <c>WANT_AUTOCONF_2_1=1</c>,
567     and for KDE3 apps export <c>WANT_AUTOCONF_2_5=1</c>.
568     </p></body>
569     </section>
570    
571    
572     <section>
573     <title>My speaker beeps like crazy while compiling Mozilla. How do I disable console beeps?
574     </title>
575     <body>
576     <p>
577     Console beeps can be turned off using setterm, like this ;
578    
579     <pre># <i>setterm -blength 0</i></pre>
580    
581     If you would like to turn off the console beeps on boot
582     you need to put this command in
583     <path>/etc/conf.d/local.start</path>. However, this only
584     disables beeps for the current terminal. To disable
585     beeps for other terminals, pipe the command output to the
586     target terminal, like this ;
587    
588     <pre># <i>setterm -blength 0 >/dev/vc/1</i></pre>
589    
590     You need to replace /dev/vc/1 with the terminal
591     you would like to disable console beeps for.
592     </p>
593     </body>
594     </section>
595     </chapter>
596    
597     <chapter>
598     <title>Resources</title>
599     <section>
600     <title>Where can I find more about supervise used by default in Gentoo Linux 1.0_rc5 and earlier?</title>
601     <body><p><!-- TODO: --><uri>http://cr.yp.to/daemontools.html</uri></p></body>
602     </section>
603    
604     <section>
605     <title>Where can I find more information about Gentoo Linux?</title>
606     <body><p>The official Gentoo documentation can be found on <uri>http://www.gentoo.org</uri>; general Linux information is at <uri>http://www.linuxdoc.org</uri>.</p></body>
607     </section>
608    
609     <section>
610     <title>Can I buy a CD of Gentoo Linux?</title>
611     <body><p>Yes! Fresh CDRs are available for $5 USD apiece from
612     <uri link = "http://cart.cheapbytes.com/cgi-bin/cart/0070010805">Cheapbytes</uri>.
613     </p>
614     <p>There are also CDs for sale at <uri link = "http://www.tuxcds.com/section.php?section=42">
615     tuxcds</uri> for a very good price. These people also bounce back a portion of the profits
616     to the Gentoo project, so buy them while they are hot! </p>
617     </body>
618     </section>
619    
620     <section>
621     <title>Why, when I hit reply to a post on a Gentoo mailing list, does my answer
622     only go to the original poster and not the entire list?</title>
623     <body>
624     <p>The mailing list administrators have decided to go with minimal munging
625     (altering of mail headers), which means that they have decided against
626     altering headers to have replies go to the mailing list. There are various
627     reasons for this. For example, if a subscriber has a full mailbox, the
628     entire list receives notice of this every time that something is posted.
629    
630     Most GUI based mailers have a "reply to all" function. This will ensure that
631     your reply goes to the mailing list as well as the original poster. Most
632     users of text based emailers already know the methods to use, but if you
633     don't, in Pine, there is a "reply to group" option. Setting Mutt to reply to
634     the list is covered in the unofficial documentation at
635     <uri link="http://forums.gentoo.org/viewtopic.php?t=1085">forums.gentoo.org</uri>.
636    
637     Some list members do not like this method, but it was very heavily
638     discussed when it went into effect, with arguments on both sides.
639     Eventually the list administrators decided to keep it this way. Discussing
640     it on the mailing list will sometimes bring a polite explanation and other
641     times a rather brusque comment to check the archives. Although the
642     administrators regret the inconvenience that it may cause some users, it is
643     felt that at present it is preferable to the alternative for several
644     reasons, many of these covered
645     <uri link="http://www.unicom.com/pw/reply-to-harmful.html">here</uri>.
646    
647     (There are other eloquent arguments in favor of munging, and yes, the list
648     administrators have seen them.) </p>
649     </body>
650     </section>
651    
652     <section>
653     <title>This FAQ hasn't answered my question. What do I do now?</title>
654     <body>
655     <p>A good first step is to browse through the relevant doumentation <uri link="http://www.gentoo.org/index-docs.html">here</uri>,
656     failing that, the various Gentoo Linux mailing
657     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
658     to hang out with Gentoo folks, visit us on irc: <i>#gentoo</i>
659     on <i>irc.freenode.net</i>.
660     </p>
661     </body>
662     </section>
663     </chapter>
664     </guide>

  ViewVC Help
Powered by ViewVC 1.1.20