/[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.21
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<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> 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 13
14<version>1.1.2</version> 14<version>1.1.3</version>
15<date>06 December 2002</date> 15<date>21 March 2003</date>
16 16
17<chapter> 17<chapter>
18 <title>Getting Started</title> 18 <title>Getting Started</title>
19 19
20 <section> 20 <section>
125 <title>How do i add a normal user?</title> 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, 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> 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 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> 129 this user a password and <c>passwd</c> will do exactly that.</p>
130 <p>Insteed of <c>adduser</c> you can also use:
131 <pre># <i>useradd gentoo -m -G users,audio,wheel -s /bin/bash</i></pre>
132 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.
133 </p>
130 </body> 134 </body>
131 </section> 135 </section>
132 <section> 136 <section>
133 <title>Why can't a user su to root?</title> 137 <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 138 <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 211 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> 212 will still work properly. Make sure to boot Gentoo Linux with the following boot option, noapic. </p>
209 </body> 213 </body>
210 </section> 214 </section>
211 215
216 <section>
217 <title>If I have Gentoo 1.4_rc1 can I upgrade to 1.4_rc2, 1.4_final/_rc3 without reinstalling?</title>
218 <body>
219 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.
220 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.
221 </body>
222 </section>
212</chapter> 223</chapter>
213 224
214<chapter> 225<chapter>
215 <title>Package Management</title> 226 <title>Package Management</title>
216 <section> 227 <section>
217 <title>In what format are the packages stored?</title> 228 <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 229 <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 230 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 231 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 232 binaries for releases and snapshots. The <uri link="/doc/gentoo-howto.xml">Development HOWTO
222 </uri> covers the contents of an ebuild script in detail. For full binary ISO releases, we 233 </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> 234 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> 235 compatible with meta-information attached to the end of the file.)</p>
225 </body> 236 </body>
226 </section> 237 </section>
245 </section> 256 </section>
246 257
247 <section> 258 <section>
248 <title>How do I install and uninstall packages?</title> 259 <title>How do I install and uninstall packages?</title>
249 <body> 260 <body>
250 <p>The <uri link="/doc/portage-user.html">Portage User Guide</uri> details how to install 261 <p>The <uri link="/doc/portage-user.xml">Portage User Guide</uri> details how to install
251 and uninstall packages, and update Portage.</p> 262 and uninstall packages, and update Portage.</p>
252 </body> 263 </body>
253 </section> 264 </section>
254 265
255 <section> 266 <section>
438# <c>CONFIG_PROTECT="" emerge blackdown-jdk </c> 449# <c>CONFIG_PROTECT="" emerge blackdown-jdk </c>
439 </pre> 450 </pre>
440 451
441 </body> 452 </body>
442 </section> 453 </section>
454 <section>
455 <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>
456 <body>
457 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.
458 </body>
459 </section>
443</chapter> 460</chapter>
444 461
445<chapter> 462<chapter>
446 <title>Usage</title> 463 <title>Usage</title>
447 <section> 464 <section>
488 </path>, so that it reads as follows:</p> 505 </path>, so that it reads as follows:</p>
489 <pre>#!/bin/sh --login</pre> 506 <pre>#!/bin/sh --login</pre>
490 <p>This fix has been added to recent versions of KDE.</p> 507 <p>This fix has been added to recent versions of KDE.</p>
491 </body> 508 </body>
492 </section> 509 </section>
510
511 <section>
512 <title>Why can't my user use their own crontab?</title>
513 <body><p>You need to add that user to the <i>cron</i> group.
514 </p>
515 </body>
516 </section>
493</chapter> 517</chapter>
494 518
495<chapter> 519<chapter>
496 <title>Maintenance</title> 520 <title>Maintenance</title>
497 <section> 521 <section>
514 <body> 538 <body>
515 <p>To view multilog (Gentoo Linux 1.0_rc5 and earlier) timestamps, you need to pipe the 539 <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> 540 current log through the <c>tai64nlocal</c>command:</p>
517 541
518<pre> 542<pre>
519# <i>cat /var/log/syslog.d/current | tai64nlocal | less</i> 543# <i>tai64nlocal &lt; /var/log/syslog.d/current | less</i>
520</pre> 544</pre>
521 545
522<p>Or, alternatively, if you want to "tail" the log:</p> 546<p>Or, alternatively, if you want to "tail" the log:</p>
523 547
524<pre> 548<pre>
539 </p></body> 563 </p></body>
540 </section> 564 </section>
541 565
542 <section> 566 <section>
543 <title>How often are new releases made?</title> 567 <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> 568 <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 569 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 570 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 571 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> 572 new modules get added.</p></body>
549 </section> 573 </section>

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

  ViewVC Help
Powered by ViewVC 1.1.20