/[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.30
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
14<version>1.1.2</version> 16<version>1.1.4</version>
15<date>06 December 2002</date> 17<date>6 May 2003</date>
16 18
17<chapter> 19<chapter>
18 <title>Getting Started</title> 20 <title>Getting Started</title>
19 21
20 <section> 22 <section>
97 -fomit-frame-pointer" optimizations. What gives?</title> 99 -fomit-frame-pointer" optimizations. What gives?</title>
98 <body> 100 <body>
99 <p>When you use any optimizations beyond <c>-O3</c>, you're really taking the risk of 101 <p>When you use any optimizations beyond <c>-O3</c>, you're really taking the risk of
100 having broken packages. 102 having broken packages.
101 Very aggressive optimizations sometimes cause the compiler to streamline the assembly code 103 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) 104 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 105 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 106 -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 107 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%, 108 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 109 (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> 110 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> 111 <p>Please try first to compile with CFLAGS <c>-march= -O2</c> before reporting a bug</p>
125 <title>How do i add a normal user?</title> 127 <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, 128 <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> 129 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 130 <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> 131 this user a password and <c>passwd</c> will do exactly that.</p>
132 <p>Insteed of <c>adduser</c> you can also use:
133 <pre># <i>useradd gentoo -m -G users,audio,wheel -s /bin/bash</i></pre>
134 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.
135 </p>
130 </body> 136 </body>
131 </section> 137 </section>
132 <section> 138 <section>
133 <title>Why can't a user su to root?</title> 139 <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 140 <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 213 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> 214 will still work properly. Make sure to boot Gentoo Linux with the following boot option, noapic. </p>
209 </body> 215 </body>
210 </section> 216 </section>
211 217
218 <section>
219 <title>If I have Gentoo 1.4_rc1 can I upgrade to 1.4_rc2, 1.4_final/_rc3 without reinstalling?</title>
220 <body>
221 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.
222 As such 1.4rc1 machine for example, that does <c>emerge rsync; emerge -u world</c> is <b>exactly the same</b> as a machine with 1.4rc2 installed, after it does <c>emerge rsync; emerge -u world</c>. The true differences lie in the installer.
223 </body>
224 </section>
212</chapter> 225</chapter>
213 226
214<chapter> 227<chapter>
215 <title>Package Management</title> 228 <title>Package Management</title>
216 <section> 229 <section>
217 <title>In what format are the packages stored?</title> 230 <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 231 <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 232 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 233 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 234 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 235 </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> 236 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> 237 compatible with meta-information attached to the end of the file.)</p>
225 </body> 238 </body>
226 </section> 239 </section>
245 </section> 258 </section>
246 259
247 <section> 260 <section>
248 <title>How do I install and uninstall packages?</title> 261 <title>How do I install and uninstall packages?</title>
249 <body> 262 <body>
250 <p>The <uri link="/doc/portage-user.html">Portage User Guide</uri> details how to install 263 <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> 264 and uninstall packages, and update Portage.</p>
252 </body> 265 </body>
253 </section> 266 </section>
254 267
255 <section> 268 <section>
330 <c>emerge --help config</c> for more details. The (overly) simple answer is that if 343 <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 344 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 345 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 346 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>, 347 tool for examining and updating any protected config files is <c>etc-update</c>,
335 currently obtained by <c>emerge app-admin/gentoolkit</c>. 348 which is now part of Portage.
336 </p></body> 349 </p></body>
337 </section> 350 </section>
338 351
339 <section> 352 <section>
340 <title>I want to perform the <c>./configure</c> step myself. Can I?</title> 353 <title>I want to perform the <c>./configure</c> step myself. Can I?</title>
354 367
355 <section> 368 <section>
356 <title>What if rsync doesn't work for me?</title> 369 <title>What if rsync doesn't work for me?</title>
357 <body><p> 370 <body><p>
358 If you're behind a firewall that doesn't permit 371 If you're behind a firewall that doesn't permit
359 rsync traffic, then you can instead download the daily 372 rsync traffic, then you can use <c>emerge-webrsync</c> which will fetch
360 /usr/portage snapshots from 373 and install a Portage snapshot for you through regular HTTP.
361 <uri>http://cvs.gentoo.org/snapshots/</uri>. Just unpack 374 <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 375 supported.
363 the <path>/usr</path> directory. 376 <pre caption="Using emerge-webrsync">
377~# <c>emerge-webrsync</c></pre>
378 If you cannot do this either, you can manually download a snapshot
379 from <uri>http://distro.ibiblio.org/pub/linux/distributions/gentoo/snapshots/</uri>.
380 In order to install the snapshot correctly, you first need to remove
381 your current <path>/usr/portage</path> so that outdated ebuilds don't
382 stay available on your system. However, you might want to put
383 <path>/usr/portage/distfiles</path> somewhere safe if you don't want to
384 lose all your sourcecode.
385 <pre caption="Manually installing the snapshots">
386<codenote>(First download the snapshot and place it in /usr)</codenote>
387~# <c>cd /usr</c>
388~# <c>mv /usr/portage/distfiles /usr/distfiles-temp</c>
389~# <c>rm -rf /usr/portage</c>
390~# <c>tar xvjf portage-foo.tbz2</c>
391~# <c>mv /usr/distfiles-temp /usr/portage/distfiles</c></pre>
364 </p></body> 392 </p></body>
365 </section> 393 </section>
366 394
367 <section> 395 <section>
368 <title>How do I use <i>emerge</i> from behind a firewall?</title> 396 <title>How do I use <i>emerge</i> from behind a firewall?</title>
382 <section> 410 <section>
383 <title>I have only slow modem connection at home. Can I download sources somewhere else and 411 <title>I have only slow modem connection at home. Can I download sources somewhere else and
384 add them to my system?</title> 412 add them to my system?</title>
385 <body><p> 413 <body><p>
386 Definitely. You can run <c>emerge --pretend package</c> to see what programs 414 Definitely. You can run <c>emerge --pretend package</c> to see what programs
415 are going to be installed. To find out the sources for those packages and where to
416 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 417 Download sources and bring them on any media
388 home. Put the sources into <path>/usr/portage/distfiles</path> and run 418 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! 419 <c>emerge package</c> to see it picking up the sources you just brought in!
390 </p></body> 420 </p></body>
391 </section> 421 </section>
392 422
402 again. 432 again.
403 </p></body> 433 </p></body>
404 </section> 434 </section>
405 435
406 <section> 436 <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 437 <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. 438 <c>java-config --list-available-vms</c> would only list blackdown-jre.
432 Openoffice would then refuse to emerge. What do I do? </title> 439 Openoffice would then refuse to emerge. What do I do? </title>
433 440
434 <body> 441 <body>
436 <pre caption = "Solution"> 443 <pre caption = "Solution">
437# <c>emerge unmerge blackdown-jre blackdown-jdk </c> 444# <c>emerge unmerge blackdown-jre blackdown-jdk </c>
438# <c>CONFIG_PROTECT="" emerge blackdown-jdk </c> 445# <c>CONFIG_PROTECT="" emerge blackdown-jdk </c>
439 </pre> 446 </pre>
440 447
448 </body>
449 </section>
450 <section>
451 <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>
452 <body>
453 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> 454 </body>
442 </section> 455 </section>
443</chapter> 456</chapter>
444 457
445<chapter> 458<chapter>
488 </path>, so that it reads as follows:</p> 501 </path>, so that it reads as follows:</p>
489 <pre>#!/bin/sh --login</pre> 502 <pre>#!/bin/sh --login</pre>
490 <p>This fix has been added to recent versions of KDE.</p> 503 <p>This fix has been added to recent versions of KDE.</p>
491 </body> 504 </body>
492 </section> 505 </section>
506
507 <section>
508 <title>Why can't my user use their own crontab?</title>
509 <body><p>You need to add that user to the <i>cron</i> group.
510 </p>
511 </body>
512 </section>
493</chapter> 513</chapter>
494 514
495<chapter> 515<chapter>
496 <title>Maintenance</title> 516 <title>Maintenance</title>
497 <section> 517 <section>
514 <body> 534 <body>
515 <p>To view multilog (Gentoo Linux 1.0_rc5 and earlier) timestamps, you need to pipe the 535 <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> 536 current log through the <c>tai64nlocal</c>command:</p>
517 537
518<pre> 538<pre>
519# <i>cat /var/log/syslog.d/current | tai64nlocal | less</i> 539# <i>tai64nlocal &lt; /var/log/syslog.d/current | less</i>
520</pre> 540</pre>
521 541
522<p>Or, alternatively, if you want to "tail" the log:</p> 542<p>Or, alternatively, if you want to "tail" the log:</p>
523 543
524<pre> 544<pre>
533 <title>Development</title> 553 <title>Development</title>
534 <section> 554 <section>
535 <title>Where can I report bugs?</title> 555 <title>Where can I report bugs?</title>
536 <body><p>For bugs within a specific program, contact the program's author. Otherwise, use our 556 <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 557 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. 558 <c>#gentoo</c> on the <uri link="http://www.freenode.net">FreeNode</uri> IRC network.
539 </p></body> 559 </p></body>
540 </section> 560 </section>
541 561
542 <section> 562 <section>
543 <title>How often are new releases made?</title> 563 <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> 564 <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 565 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 566 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 567 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> 568 new modules get added.</p></body>
549 </section> 569 </section>
555 </section> 575 </section>
556 576
557 <section> 577 <section>
558 <title>How can I add a question or answer to this FAQ?</title> 578 <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 579 <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> 580 "Docs-user" product, "Gentoo Linux FAQ" component.</p></body>
561 </section> 581 </section>
562 582
563 <section> 583 <section>
564 <title>make -f Makefile.cvs on a KDE app produces "invalid unused variable" errors</title> 584 <title>make -f Makefile.cvs on a KDE app produces "invalid unused variable" errors</title>
565 <body><p> 585 <body><p>
651 </section> 671 </section>
652 672
653 <section> 673 <section>
654 <title>This FAQ hasn't answered my question. What do I do now?</title> 674 <title>This FAQ hasn't answered my question. What do I do now?</title>
655 <body> 675 <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>, 676 <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 677 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 678 lists listed on <uri link="http://www.google.com">Google</uri>. To search through the Gentoo mailling lists,
679 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> 680 to hang out with Gentoo folks, visit us on irc: <i>#gentoo</i>
660 on <i>irc.freenode.net</i>. 681 on <i>irc.freenode.net</i>.
661 </p> 682 </p>
662 </body> 683 </body>
663 </section> 684 </section>

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

  ViewVC Help
Powered by ViewVC 1.1.20