/[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.10 - (hide annotations) (download) (as text)
Sat Dec 7 20:46:17 2002 UTC (11 years, 7 months ago) by zhen
Branch: MAIN
Changes since 1.9: +2 -2 lines
File MIME type: application/xml
fix for bug #11601

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

  ViewVC Help
Powered by ViewVC 1.1.20