| 1 |
swift 05/11/30 05:14:15 |
| 2 |
|
| 3 |
Modified: xml/htdocs/doc/en/draft bootstrapping-guide.xml |
| 4 |
Log: |
| 5 |
The simple part... |
| 6 |
|
| 7 |
Revision Changes Path |
| 8 |
1.2 +76 -1 xml/htdocs/doc/en/draft/bootstrapping-guide.xml |
| 9 |
|
| 10 |
file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/draft/bootstrapping-guide.xml?rev=1.2&content-type=text/x-cvsweb-markup&cvsroot=gentoo |
| 11 |
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/draft/bootstrapping-guide.xml?rev=1.2&content-type=text/plain&cvsroot=gentoo |
| 12 |
diff : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/draft/bootstrapping-guide.xml.diff?r1=1.1&r2=1.2&cvsroot=gentoo |
| 13 |
|
| 14 |
Index: bootstrapping-guide.xml |
| 15 |
=================================================================== |
| 16 |
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/draft/bootstrapping-guide.xml,v |
| 17 |
retrieving revision 1.1 |
| 18 |
retrieving revision 1.2 |
| 19 |
diff -u -r1.1 -r1.2 |
| 20 |
--- bootstrapping-guide.xml 26 Nov 2005 16:23:25 -0000 1.1 |
| 21 |
+++ bootstrapping-guide.xml 30 Nov 2005 05:14:15 -0000 1.2 |
| 22 |
@@ -1,6 +1,6 @@ |
| 23 |
<?xml version='1.0' encoding="UTF-8"?> |
| 24 |
|
| 25 |
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/draft/bootstrapping-guide.xml,v 1.1 2005/11/26 16:23:25 swift Exp $ --> |
| 26 |
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/draft/bootstrapping-guide.xml,v 1.2 2005/11/30 05:14:15 swift Exp $ --> |
| 27 |
|
| 28 |
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd"> |
| 29 |
|
| 30 |
@@ -151,24 +151,68 @@ |
| 31 |
<title>Installing Gentoo</title> |
| 32 |
<body> |
| 33 |
|
| 34 |
+<p> |
| 35 |
+With the bootable environment at your disposal, you can now boot the target |
| 36 |
+system into a small Linux environment. Once booted, follow the installation |
| 37 |
+instructions inside the <uri link="/doc/en/handbook">Gentoo Handbook</uri> to |
| 38 |
+the point where you chroot into your Gentoo environment. Of course, since you |
| 39 |
+only have a stage1 tarball at your disposal, you should use that one instead of |
| 40 |
+the stage3 used in the installation instructions. |
| 41 |
+</p> |
| 42 |
+ |
| 43 |
+<p> |
| 44 |
+After chrooting the system, you should update the Portage tree. |
| 45 |
+</p> |
| 46 |
+ |
| 47 |
+<pre caption="Updating the Portage tree"> |
| 48 |
+# <i>emerge --sync</i> |
| 49 |
+</pre> |
| 50 |
+ |
| 51 |
</body> |
| 52 |
</section> |
| 53 |
<section> |
| 54 |
<title>Using the Bootstrap Script</title> |
| 55 |
<body> |
| 56 |
|
| 57 |
+<p> |
| 58 |
+Next, we'll rebuild the toolchain provided by the stage1 tarball natively. |
| 59 |
+Gentoo provides a script that does this for you. |
| 60 |
+</p> |
| 61 |
+ |
| 62 |
+<pre caption="Rebuilding the toolchain"> |
| 63 |
+# <i>/usr/portage/scripts/bootstrap.sh</i> |
| 64 |
+</pre> |
| 65 |
+ |
| 66 |
</body> |
| 67 |
</section> |
| 68 |
<section> |
| 69 |
<title>Building the Core System</title> |
| 70 |
<body> |
| 71 |
|
| 72 |
+<p> |
| 73 |
+With the toolchain rebuild and ready for general usage, we'll build the core |
| 74 |
+system packages for the system: |
| 75 |
+</p> |
| 76 |
+ |
| 77 |
+<pre caption="Building the core system packages"> |
| 78 |
+# <i>emerge --emptytree system</i> |
| 79 |
+</pre> |
| 80 |
+ |
| 81 |
</body> |
| 82 |
</section> |
| 83 |
<section> |
| 84 |
<title>Finishing the Installation</title> |
| 85 |
<body> |
| 86 |
|
| 87 |
+<p> |
| 88 |
+Now that the core system packages are built, you can continue using the |
| 89 |
+installation instructions in the Gentoo Handbook. You will probably get a few |
| 90 |
+complaints by Portage telling you certain packages are masked. This is because |
| 91 |
+your architecture isn't supported by Gentoo yet, in which case you need to |
| 92 |
+unmask the packages in <path>/etc/portage/package.keywords</path> like you did |
| 93 |
+previously. |
| 94 |
+</p> |
| 95 |
+ |
| 96 |
</body> |
| 97 |
</section> |
| 98 |
</chapter> |
| 99 |
@@ -182,6 +226,25 @@ |
| 100 |
</title> |
| 101 |
<body> |
| 102 |
|
| 103 |
+<p> |
| 104 |
+No. After your changes, you should rebuild the toolchain first, after which you |
| 105 |
+can rebuild the entire system using the new toolchain. When your system suffers |
| 106 |
+from circular dependencies, you'll need to rebuild the participants in that |
| 107 |
+circle. For instance, if <c>openssl</c> depends on <c>python</c> which depends |
| 108 |
+on <c>perl</c> which depends on <c>openssl</c> again (yes, this is a fictuous |
| 109 |
+example), rebuild all those packages too. |
| 110 |
+</p> |
| 111 |
+ |
| 112 |
+<pre caption="Rebuilding the system"> |
| 113 |
+# <i>emerge --oneshot --emptytree glibc binutils glibc</i> |
| 114 |
+# <i>emerge --emptytree world</i> |
| 115 |
+</pre> |
| 116 |
+ |
| 117 |
+<p> |
| 118 |
+You don't need to bootstrap here because your architecture still remains the |
| 119 |
+same, as is the target system. |
| 120 |
+</p> |
| 121 |
+ |
| 122 |
</body> |
| 123 |
</section> |
| 124 |
<section> |
| 125 |
@@ -190,6 +253,18 @@ |
| 126 |
</title> |
| 127 |
<body> |
| 128 |
|
| 129 |
+<p> |
| 130 |
+Not if the system itself supports the new CHOST setting too (for instance, |
| 131 |
+i386-pc-linux-gnu and i686-pc-linux-gnu on a Pentium IV system). Otherwise, yes, |
| 132 |
+but then we are really interested in hearing how you managed to install Gentoo |
| 133 |
+using the current - wrong - CHOST settings in the first place ;) |
| 134 |
+</p> |
| 135 |
+ |
| 136 |
+<p> |
| 137 |
+If your system supports both CHOST settings, you can follow the same |
| 138 |
+instructions as given in the previous FAQ. |
| 139 |
+</p> |
| 140 |
+ |
| 141 |
</body> |
| 142 |
</section> |
| 143 |
</chapter> |
| 144 |
|
| 145 |
|
| 146 |
|
| 147 |
-- |
| 148 |
gentoo-doc-cvs@g.o mailing list |
Archives