1 | <?xml version='1.0' encoding="UTF-8"?> |
1 | <?xml version='1.0' encoding="UTF-8"?> |
2 | <!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/faq.xml,v 1.93 2005/07/14 09:34:23 neysx Exp $ --> |
2 | <!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/faq.xml,v 1.94 2005/07/14 09:37:58 neysx Exp $ --> |
3 | <!DOCTYPE guide SYSTEM "/dtd/guide.dtd"> |
3 | <!DOCTYPE guide SYSTEM "/dtd/guide.dtd"> |
4 | |
4 | |
5 | <guide link="/doc/en/faq.xml"> |
5 | <guide link="/doc/en/faq.xml"> |
6 | <title>Gentoo Linux Frequently Asked Questions</title> |
6 | <title>Gentoo Linux Frequently Asked Questions</title> |
7 | <author title="Author"> |
7 | <author title="Author"> |
… | |
… | |
53 | <title>Getting Started</title> |
53 | <title>Getting Started</title> |
54 | <body> |
54 | <body> |
55 | |
55 | |
56 | <p> |
56 | <p> |
57 | Please note that many of these questions are answered within the official |
57 | Please note that many of these questions are answered within the official |
58 | gentoo documents and guides. This is simply a list of common questions. Please |
58 | Gentoo documents and guides. This is simply a list of common questions. Please |
59 | read the documentation and/or man pages to gain a greater understanding of how |
59 | read the documentation and/or man pages to gain a greater understanding of how |
60 | Gentoo and GNU/Linux works, and for answers to questions which may not be |
60 | Gentoo and GNU/Linux works, and for answers to questions which may not be |
61 | answered here. |
61 | answered here. |
62 | </p> |
62 | </p> |
63 | |
63 | |
… | |
… | |
188 | <body> |
188 | <body> |
189 | |
189 | |
190 | <ul> |
190 | <ul> |
191 | <li> |
191 | <li> |
192 | <uri link="#filecorruption">ReiserFS and filesystem corruption issues -- |
192 | <uri link="#filecorruption">ReiserFS and filesystem corruption issues -- |
193 | how to fix'em, etc.</uri> |
193 | how to fix them, etc.</uri> |
194 | </li> |
194 | </li> |
195 | </ul> |
195 | </ul> |
196 | |
196 | |
197 | </body> |
197 | </body> |
198 | </section> |
198 | </section> |
… | |
… | |
278 | </p> |
278 | </p> |
279 | |
279 | |
280 | <p> |
280 | <p> |
281 | Gentoo is actively developed. The entire distribution uses a rapid pace |
281 | Gentoo is actively developed. The entire distribution uses a rapid pace |
282 | development style: patches to the packages are quickly integrated in the |
282 | development style: patches to the packages are quickly integrated in the |
283 | mainline tree, documentation is updated on daily basis, portage features are |
283 | mainline tree, documentation is updated on daily basis, Portage features are |
284 | added frequently, and official releases occur twice per year. |
284 | added frequently, and official releases occur twice per year. |
285 | </p> |
285 | </p> |
286 | |
286 | |
287 | </body> |
287 | </body> |
288 | </section> |
288 | </section> |
… | |
… | |
559 | not fully optimized) version of the package quickly and efficiently. |
559 | not fully optimized) version of the package quickly and efficiently. |
560 | </p> |
560 | </p> |
561 | |
561 | |
562 | <p> |
562 | <p> |
563 | It is possible to create RPMs (Redhat package manager files) using Gentoo's |
563 | It is possible to create RPMs (Redhat package manager files) using Gentoo's |
564 | portage, but it is not currently possible to use already existing RPMs to |
564 | Portage, but it is not currently possible to use already existing RPMs to |
565 | install packages. |
565 | install packages. |
566 | </p> |
566 | </p> |
567 | |
567 | |
568 | </body> |
568 | </body> |
569 | </section> |
569 | </section> |
… | |
… | |
571 | <title>I want to perform the ./configure step myself. Can I?</title> |
571 | <title>I want to perform the ./configure step myself. Can I?</title> |
572 | <body> |
572 | <body> |
573 | |
573 | |
574 | <p> |
574 | <p> |
575 | Yes, but it is not trivial, nor is it recommended. Since the method to do this |
575 | Yes, but it is not trivial, nor is it recommended. Since the method to do this |
576 | requires a good understanding of portage internals and commands, it is instead |
576 | requires a good understanding of Portage internals and commands, it is instead |
577 | recommended that you patch the ebuild to do whatever it is that you want and |
577 | recommended that you patch the ebuild to do whatever it is that you want and |
578 | place it in the portage overlay (thats why it exists). This is <e>much</e> |
578 | place it in the Portage overlay (that's why it exists). This is <e>much</e> |
579 | better for maintainability, and usually easier. See the <uri |
579 | better for maintainability, and usually easier. See the <uri |
580 | link="/proj/en/devrel/handbook/handbook.xml?part=2&chap=1">Ebuild |
580 | link="/proj/en/devrel/handbook/handbook.xml?part=2&chap=1">Ebuild |
581 | HOWTO</uri> for more information. |
581 | HOWTO</uri> for more information. |
582 | </p> |
582 | </p> |
583 | |
583 | |
… | |
… | |
601 | |
601 | |
602 | <p> |
602 | <p> |
603 | If you're behind a firewall that doesn't permit rsync traffic, then you can use |
603 | If you're behind a firewall that doesn't permit rsync traffic, then you can use |
604 | <c>emerge-webrsync</c> which will fetch and install a Portage snapshot for you |
604 | <c>emerge-webrsync</c> which will fetch and install a Portage snapshot for you |
605 | through regular HTTP. See the <uri link="#proxy">proxy section</uri> of this |
605 | through regular HTTP. See the <uri link="#proxy">proxy section</uri> of this |
606 | document for information on downloading source files and portage snapshots via |
606 | document for information on downloading source files and Portage snapshots via |
607 | a proxy. |
607 | a proxy. |
608 | </p> |
608 | </p> |
609 | |
609 | |
610 | </body> |
610 | </body> |
611 | </section> |
611 | </section> |
… | |
… | |
770 | </chapter> |
770 | </chapter> |
771 | |
771 | |
772 | <chapter> |
772 | <chapter> |
773 | <title>Maintenance</title> |
773 | <title>Maintenance</title> |
774 | <section id="filecorruption"> |
774 | <section id="filecorruption"> |
775 | <title>ReiserFS and filesystem corruption issues -- how to fix'em, etc</title> |
775 | <title>ReiserFS and filesystem corruption issues -- how to fix them, etc</title> |
776 | <body> |
776 | <body> |
777 | |
777 | |
778 | <p> |
778 | <p> |
779 | If your ReiserFS partition is corrupt, try booting the Gentoo Install CD and |
779 | If your ReiserFS partition is corrupt, try booting the Gentoo Install CD and |
780 | run <c>reiserfsck --rebuild-tree</c> on the corrupted filesystem. This should |
780 | run <c>reiserfsck --rebuild-tree</c> on the corrupted filesystem. This should |
… | |
… | |
864 | <section id="buycd"> |
864 | <section id="buycd"> |
865 | <title>Can I buy a CD of Gentoo Linux?</title> |
865 | <title>Can I buy a CD of Gentoo Linux?</title> |
866 | <body> |
866 | <body> |
867 | |
867 | |
868 | <p> |
868 | <p> |
869 | Install CDs for all supported architecture are available on our <uri |
869 | Install CDs for all supported architectures are available on our <uri |
870 | link="http://www.cafepress.com/officialgentoo/">Gentoo Store</uri>. When you |
870 | link="http://www.cafepress.com/officialgentoo/">Gentoo Store</uri>. When you |
871 | purchase a CD from our store, you are also supporting our development. So, |
871 | purchase a CD from our store, you are also supporting our development. So, |
872 | please consider buying from our store if possible. |
872 | please consider buying from our store if possible. |
873 | </p> |
873 | </p> |
874 | |
874 | |