/[gentoo]/xml/htdocs/doc/en/gentoo-upgrading.xml
Gentoo

Diff of /xml/htdocs/doc/en/gentoo-upgrading.xml

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

Revision 1.18 Revision 1.34
1<?xml version='1.0' encoding="UTF-8"?> 1<?xml version='1.0' encoding="UTF-8"?>
2<!DOCTYPE guide SYSTEM "/dtd/guide.dtd"> 2<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
3<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/gentoo-upgrading.xml,v 1.18 2005/01/25 11:48:14 neysx Exp $ --> 3<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/gentoo-upgrading.xml,v 1.34 2006/11/08 07:31:20 nightmorph Exp $ -->
4 4
5<guide link="/doc/en/gentoo-upgrading.xml"> 5<guide link="/doc/en/gentoo-upgrading.xml">
6<title>Gentoo Upgrading Guide</title> 6<title>Gentoo Upgrading Guide</title>
7 7
8<author title="Author"> 8<author title="Author">
9 <mail link="greg_g@gentoo.org">Gregorio Guidi</mail> 9 <mail link="greg_g@gentoo.org">Gregorio Guidi</mail>
10</author> 10</author>
11<author title="Editor">
12 <mail link="wolf31o2@gentoo.org">Chris Gianelloni</mail>
13</author>
11 14
12<abstract> 15<abstract>
13This document explains how new Gentoo releases affect existing installs. 16This document explains how new Gentoo releases affect existing installs.
14</abstract> 17</abstract>
15 18
16<!-- The content of this document is licensed under the CC-BY-SA license --> 19<!-- The content of this document is licensed under the CC-BY-SA license -->
17<!-- See http://creativecommons.org/licenses/by-sa/2.0 --> 20<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
18<license/> 21<license/>
19 22
20<version>2.8</version> 23<version>2.5</version>
21<date>2005-01-22</date> 24<date>2006-11-07</date>
22 25
23<chapter> 26<chapter>
24<title>Gentoo and Upgrades</title> 27<title>Gentoo and Upgrades</title>
25<section> 28<section>
26<title>Philosophy</title> 29<title>Philosophy</title>
… …
37<p> 40<p>
38You know (being a Gentoo user after all) that this process is extremely 41You know (being a Gentoo user after all) that this process is extremely
39frustrating for power users that want to live on the bleeding edge. Even power 42frustrating for power users that want to live on the bleeding edge. Even power
40users from other distributions probably share the same feelings, given the 43users from other distributions probably share the same feelings, given the
41popularity and spread of tools like apt or apt-rpm which make it 44popularity and spread of tools like apt or apt-rpm which make it
42possible to have quick and frequent updates. However, no distibution is more 45possible to have quick and frequent updates. However, no distribution is more
43suited than Gentoo to satisfy these kind of demanding users. From the beginning, 46suited than Gentoo to satisfy these kind of demanding users. From the
44Gentoo was designed around the concept of fast, incremental updates. 47beginning, Gentoo was designed around the concept of fast, incremental
48updates.
45</p> 49</p>
46 50
47<p> 51<p>
48Ideally, you install once and never bother with releases: just follow the 52Ideally, you install once and never bother with releases: just follow the
49instructions in <uri 53instructions in <uri
… …
66There are various reasons: 70There are various reasons:
67</p> 71</p>
68 72
69<ul> 73<ul>
70 <li> 74 <li>
71 A new release means new LiveCDs with bugfixes and more features. 75 A new release means new Installation CDs with bugfixes and more features.
72 </li> 76 </li>
73 <li> 77 <li>
74 A new release provides an updated set of GRP packages, so that users that 78 A new release provides an updated set of GRP packages, so that users that
75 choose "the fast way" to install (stage3 + precompiled packages) end up 79 choose "the fast way" to install (stage3 + precompiled packages) end up
76 with a system that is not outdated. 80 with a system that is not outdated.
… …
95</p> 99</p>
96 100
97<p> 101<p>
98The profile in use is determined by the symbolic link 102The profile in use is determined by the symbolic link
99<path>/etc/make.profile</path>, which points to a subdirectory of 103<path>/etc/make.profile</path>, which points to a subdirectory of
100<path>/usr/portage/profiles</path> which holds the profile files. For instance, 104<path>/usr/portage/profiles</path> which holds the profile files. For
101the x86 2004.2 profile can be found at <path>/usr/portage/profiles/default-x86-2004.2</path> 105instance, the default x86 2006.1 profile can be found
102(old-style location) or at <path>/usr/portage/profiles/default-linux/x86/2004.2</path> (new-style 106at <path>/usr/portage/profiles/default-linux/x86/2006.1</path>.
103location - only for use with Portage 2.0.51 and later). With respect to new-style profile directories, note that the files in 107The files in the parent directories are part of the profile as well (and
104parent directories are part of the profile (and are therefore shared 108are therefore shared by different subprofiles). This is why we call these
105by different subprofiles). 109<e>cascaded profiles</e>.
106</p> 110</p>
107 111
108<p> 112<p>
109Profiles obsoleted by new ones are kept in <path>/usr/portage/profiles</path> 113Profiles obsoleted by new ones are kept in <path>/usr/portage/profiles</path>
110along with the current ones, but they are marked as deprecated. When that happens a 114along with the current ones, but they are marked as deprecated. When that
111file named <path>deprecated</path> is put in the profile directory. The content 115happens a file named <path>deprecated</path> is put in the profile directory.
112of this file is the name of the profile that should be "upgraded to"; portage uses 116The content of this file is the name of the profile that should be "upgraded
113this information to automatically warn you when you should update to a new profile. 117to"; portage uses this information to automatically warn you when you should
114</p> 118update to a new profile.
115
116<p> 119</p>
120
121<p>
117There are various reasons that a new profile may be created: the release of new 122There are various reasons that a new profile may be created: the release of
118versions of core packages (such as <c>baselayout</c>, <c>gcc</c>, or <c>glibc</c>) 123new versions of core packages (such as <c>baselayout</c>, <c>gcc</c>, or
119that are incompatible with previous versions, a change in the default USE flags or 124<c>glibc</c>) that are incompatible with previous versions, a change in
120in the virtual mappings, or maybe a change in system-wide settings (such as defining 125the default USE flags or in the virtual mappings, or maybe a change in
121udev to be the default manager for <path>/dev</path> instead of devfs). 126system-wide settings.
122</p> 127</p>
123 128
124</body> 129</body>
125</section> 130</section>
126</chapter> 131</chapter>
… …
130<section> 135<section>
131<title>Releases without profile changes</title> 136<title>Releases without profile changes</title>
132<body> 137<body>
133 138
134<p> 139<p>
135If a new Gentoo release is announced that does not include a new profile (such 140If a new Gentoo release is announced that does not include a new profile
136as the 2004.1 release for x86), then you can safely pretend that it never 141then you can safely pretend that it never happened :).
137happened :).
138</p> 142</p>
139 143
140<p> 144<p>
141If you update your installed packages 145If you update your installed packages
142<uri link="/doc/en/handbook/handbook-x86.xml?part=2&amp;chap=1">as explained in 146<uri link="/doc/en/handbook/handbook-x86.xml?part=2&amp;chap=1">as explained in
… …
149<section> 153<section>
150<title>Releases with profile changes</title> 154<title>Releases with profile changes</title>
151<body> 155<body>
152 156
153<p> 157<p>
154If a release introduces a new profile, you have the choice to migrate to the 158If a release (such as 2006.1 for x86) introduces a new profile, you have the
155new profile. 159choice to migrate to the new profile.
156</p>
157
158<p> 160</p>
161
162<p>
159Naturally, you are not forced to do so, and you can continue to use the old profile 163Naturally, you are not forced to do so, and you can continue to use the old
160and just update your packages 164profile and just update your packages
161<uri link="/doc/en/handbook/handbook-x86.xml?part=2&amp;chap=1">as explained in 165<uri link="/doc/en/handbook/handbook-x86.xml?part=2&amp;chap=1">as explained
162the Gentoo Handbook</uri>. 166in the Gentoo Handbook</uri>.
163</p>
164
165<p> 167</p>
168
169<p>
166However, Gentoo strongly recommends updating your profile if it becomes deprecated. 170However, Gentoo strongly recommends updating your profile if it becomes
167When this happens, it means that Gentoo developers no longer plan on supporting it. 171deprecated. When this happens, it means that Gentoo developers no longer
168Using the table below, you can quickly check to see what profiles are currently supported. 172plan on supporting it. Using the table below, you can quickly check to
173see what profiles are currently supported.
169</p> 174</p>
170 175
171<p> 176<p>
172If you decide to migrate to the new profile, then you will have to manually 177If you decide to migrate to the new profile, then you will have to manually
173perform the update. The way you update may vary significantly from release to release; it 178perform the update. The way you update may vary significantly from release
174depends on how deep the modifications introduced in the new profile are. 179to release; it depends on how deep the modifications introduced in the new
180profile are.
175</p> 181</p>
176 182
177<p> 183<p>
178In the simplest case you only have to change the <path>/etc/make.profile</path> 184In the simplest case you only have to change the <path>/etc/make.profile</path>
179symlink, in the worst case you may have to recompile your system from scratch 185symlink, in the worst case you may have to recompile your system from scratch
180while doing a neat voodoo dance. Migration is usually covered in the release 186while doing a neat voodoo dance. Migration is usually covered in the release
181notes (e.g. <uri 187notes. You can also find <uri link="#instructions">instructions</uri> at the
182link="/proj/en/releng/release/2004.3/x86-release-notes.xml">the x86 2004.3 188end of this guide.
183release notes</uri>). You can also find <uri
184link="#instructions">instructions</uri> at the end of this guide.
185</p> 189</p>
186 190
187</body> 191</body>
188</section> 192</section>
189<section> 193<section>
… …
195</p> 199</p>
196 200
197<table> 201<table>
198<tr> 202<tr>
199 <th>Architecture</th> 203 <th>Architecture</th>
200 <th>Most recent profile</th> 204 <th>Most recent profiles</th>
201 <th>Other supported profiles</th> 205 <th>Other supported profiles</th>
202</tr> 206</tr>
203<tr> 207<tr>
204 <th>alpha</th> 208 <th>alpha</th>
209 <ti>default-linux/alpha/2006.1</ti>
210 <ti>
211 default-linux/alpha/2006.0, default-linux/alpha/2006.1/desktop,
212 default-linux/alpha/2006.1/server, default-linux/alpha/no-nptl,
213 default-linux/alpha/no-nptl/2.4
214 </ti>
215</tr>
216<tr>
217 <th>arm</th>
218 <ti>default-linux/arm/2004.3</ti>
219 <ti></ti>
220</tr>
221<tr>
222 <th>amd64</th>
223 <ti>default-linux/amd64/2006.1</ti>
224 <ti>
225 default-linux/amd64/2006.0, default-linux/amd64/2006.0/no-multilib,
226 default-linux/amd64/2006.1/desktop, default-linux/amd64/2006.1/server,
227 default-linux/amd64/2006.1/no-multilib
228 </ti>
229</tr>
230<tr>
231 <th>hppa</th>
232 <ti>default-linux/hppa/2006.1</ti>
233 <ti>default-linux/hppa/2005.0</ti>
234</tr>
235<tr>
236 <th>ia64</th>
237 <ti>default-linux/ia64/2006.0</ti>
238 <ti>default-linux/ia64/2005.0</ti>
239</tr>
240<tr>
241 <th>ppc</th>
242 <ti>default-linux/ppc/ppc32/2006.1, default-linux/ppc/ppc64/2006.1</ti>
243 <ti>
244 default-linux/ppc/ppc32/2006.0, default-linux/ppc/ppc64,2006.0,
245 default-linux/ppc/ppc32/2006.0/G3,
246 default-linux/ppc/ppc32/2006.0/G3/Pegasos,
247 default-linux/ppc/ppc32/2006.0/G4,
248 default-linux/ppc/ppc32/2006.0/G4/Pegasos,
249 default-linux/ppc/ppc32/2006,1/G3,
250 default-linux/ppc/ppc32/2006.1/G3/Pegasos,
251 default-linux/ppc/ppc32/2006.1/G4,
252 default-linux/ppc/ppc32/2006.1/G4/Pegasos,
253 default-linux/ppc/ppc64/2006.0/32bit-userland,
254 default-linux/ppc/ppc64/2006.0/32bit-userland/970,
255 default-linux/ppc/ppc64/2006.0/32bit-userland/power3,
256 default-linux/ppc/ppc64/2006.0/32bit-userland/power4,
257 default-linux/ppc/ppc64/2006.0/32bit-userland/power5,
258 default-linux/ppc/ppc64/2006.0/64bit-userland/970,
259 default-linux/ppc/ppc64/2006.0/64bit-userland/power3,
260 default-linux/ppc/ppc64/2006.0/64bit-userland/power4,
261 default-linux/ppc/ppc64/2006.0/64bit-userland/power5,
262 default-linux/ppc/ppc64/2006.1/32bit-userland,
263 default-linux/ppc/ppc64/2006.1/32bit-userland/970,
264 default-linux/ppc/ppc64/2006.1/32bit-userland/power3,
265 default-linux/ppc/ppc64/2006.1/32bit-userland/power4,
266 default-linux/ppc/ppc64/2006.1/32bit-userland/power5,
267 default-linux/ppc/ppc64/2006.1/64bit-userland/970,
268 default-linux/ppc/ppc64/2006.1/64bit-userland/power3,
269 default-linux/ppc/ppc64/2006.1/64bit-userland/power4,
270 default-linux/ppc/ppc64/2006.1/64bit-userland/power5
271 </ti>
272</tr>
273<tr>
274 <th>mips</th>
275 <ti>2006.0</ti>
276 <ti>2005.0, 2004.2</ti>
277</tr>
278<tr>
279 <th>s390</th>
280 <ti>2006.0</ti>
205 <ti>2004.3</ti> 281 <ti>2004.3</ti>
206 <ti></ti>
207</tr>
208<tr> 282</tr>
209 <th>arm</th>
210 <ti>2004.3</ti>
211 <ti></ti>
212</tr> 283<tr>
213<tr>
214 <th>amd64</th>
215 <ti>2004.3</ti>
216 <ti>2004.2, 2004.0</ti>
217</tr>
218<tr>
219 <th>hppa</th> 284 <th>sh</th>
220 <ti>2004.3</ti> 285 <ti>default-linux/sh/2006.1</ti>
221 <ti>2004.2</ti>
222</tr>
223<tr>
224 <th>ia64</th>
225 <ti>2004.3</ti>
226 <ti></ti>
227</tr>
228<tr>
229 <th>ppc</th>
230 <ti>2004.3</ti>
231 <ti>2004.0</ti>
232</tr>
233<tr>
234 <th>mips</th>
235 <ti>2004.2</ti>
236 <ti></ti>
237</tr>
238<tr>
239 <th>s390</th>
240 <ti>2004.3</ti>
241 <ti></ti> 286 <ti></ti>
242</tr> 287</tr>
243<tr> 288<tr>
244 <th>sparc</th> 289 <th>sparc</th>
245 <ti>2004.3</ti> 290 <ti>
246 <ti>2004.0</ti> 291 default-linux/sparc/sparc64/2006.1, default-linux/sparc/sparc64/2006.1/2.4
292 </ti>
293 <ti>
294 default-linux/sparc/sparc64/2006.0, default-linux/sparc/sparc64/2006.0/2.4
295 </ti>
247</tr> 296</tr>
248<tr> 297<tr>
249 <th>x86</th> 298 <th>x86</th>
250 <ti>2004.3</ti> 299 <ti>
251 <ti>2004.2, 2004.0</ti> 300 default-linux/x86/2006.1, default-linux/x86/no-nptl,
301 default-linux/x86/no-nptl/2.4
302 </ti>
303 <ti>
304 default-linux/x86/2006.1/desktop, default-linux/x86/2006.1/server,
305 default-linux/x86/2006.0
306 </ti>
252</tr> 307</tr>
253</table> 308</table>
254 309
255</body> 310</body>
256</section> 311</section>
257</chapter> 312</chapter>
258 313
259<chapter id="instructions"> 314<chapter id="instructions">
260<title>Profile updating instructions</title> 315<title>Profile updating instructions</title>
316<section>
317<title>Updating to 2006.1</title>
318<body>
319
320<p>
321To switch to the 2006.1 profile, point the <path>/etc/make.profile</path>
322symlink to the new location. Make sure your Portage is updated before you
323change your profile.
324</p>
325
326<pre caption="Changing to a 2006.1 profile">
327# <i>rm /etc/make.profile</i>
328# <i>ln -s ../usr/portage/profiles/</i>&lt;selected profile&gt;<i> /etc/make.profile</i>
329</pre>
330
331<p>
332Please note that the <b>alpha</b>/2006.1, <b>amd64</b>/2006.1 and
333<b>x86</b>/2006.1 profiles are very minimal. They all have a <c>desktop</c>
334sub-profile that is likely what you want on a desktop machine.
335</p>
336
337</body>
338</section>
339<section>
340<title>Updating to 2006.0</title>
341<body>
342
343<p>
344To switch to the 2006.0 profile, point the <path>/etc/make.profile</path>
345symlink to the new location. Make sure your Portage is updated before you
346change your profile.
347</p>
348
349<pre caption="Changing to a 2006.0 profile">
350# <i>rm /etc/make.profile</i>
351# <i>ln -s ../usr/portage/profiles/</i>&lt;selected profile&gt;<i> /etc/make.profile</i>
352</pre>
353
354<p>
355<b>alpha</b> - Users that use a 2.4 kernel or don't want to use NPTL should use
356the default-linux/alpha/no-nptl profile. More information is available in <uri
357link="/proj/en/releng/release/2006.0/alpha-release-notes.xml">the alpha release
358notes</uri>.
359</p>
360
361<p>
362<b>ppc</b> - The merge of the ppc32 and ppc64 profiles went forward. The ppc32
363profile has been changed in a way that offers a minimalistic generic profile
364for all purposes, located in default-linux/ppc/ppc32. The release-dependent
365profile is optimized for desktop-usage and located in
366default-linux/ppc/ppc32/2006.0. There are some subprofiles available for G3 and
367G4 processors, and G3/Pegasos and G4/Pegasos for the Pegasos Open Desktop
368Workstation. Make sure you choose the correct subprofile for your system when
369migrating to a 2006.0 profile.
370</p>
371
372<p>
373<b>sparc</b> - Upgrading to the <b>2.4</b>-kernel based 2006.0/2.4 profile
374requires manual user intervention (unmerging java stuff) and an <c>emerge -e
375world</c> because of the <uri link="/doc/en/gcc-upgrading.xml">gcc
376upgrade</uri>.<br/>
377Upgrading to the <b>2.6</b>-kernel based 2006.0 profile which is not considered
378stable also requires an entry in <path>/etc/portage/package.unmask</path> to
379umask a 2.6 version of <c>gentoo-sources</c> and a full rebuild.
380</p>
381
382<p>
383<b>All other archs</b> - There are no fundamental changes in this profile. No
384specific action needs to be performed.
385</p>
386
387</body>
388</section>
389<section>
390<title>Updating to 2005.1</title>
391<body>
392
393<p>
394To switch to the 2005.1 profile, point the <path>/etc/make.profile</path>
395symlink to the new location. Make sure your Portage is updated before you
396change your profile.
397</p>
398
399<pre caption="Changing to a 2005.1 profile">
400# <i>rm /etc/make.profile</i>
401# <i>ln -s ../usr/portage/profiles/</i>&lt;selected profile&gt;<i> /etc/make.profile</i>
402</pre>
403
404<p>
405<b>All archs</b> - There are no fundamental changes in this profile. No
406specific action needs to be performed.
407</p>
408
409<p>
410<b>ppc</b> - With the 2005.1 release, the ppc and ppc64 profiles were merged
411and a number of subprofiles for specific subarchitectures were created. Make
412sure you choose the correct subprofile for your system when migrating to a
4132005.1 profile.
414</p>
415
416</body>
417</section>
418<section>
419<title>Updating to 2005.0</title>
420<body>
421
422<p>
423With the introduction of 2005.0, several architectures have decided to define
424additional profiles. Make sure you read the description of said profiles before
425you decide to migrate to one of them. Most architectures now also default to the
4262.6 kernel tree where 2.4 was chosen previously.
427</p>
428
429<p>
430Some architectures require a bit more actions to be completed in order to
431convert from one profile to another. If that is the case, the step-by-step
432guides are linked from the table.
433</p>
434
435<table>
436<tr>
437 <th>Profile</th>
438 <th>Description</th>
439 <th>Specific Upgrade Guide</th>
440</tr>
441<tr>
442 <ti>default-linux/alpha/2005.0</ti>
443 <ti>Default Alpha 2005.0 profile for 2.6 kernels</ti>
444 <ti></ti>
445</tr>
446<tr>
447 <ti>default-linux/alpha/2005.0/2.4</ti>
448 <ti>Alpha 2005.0 profile for 2.4 kernels</ti>
449 <ti></ti>
450</tr>
451<tr>
452 <ti>default-linux/amd64/2005.0</ti>
453 <ti>Default AMD64 2005.0 profile for 2.6 kernels</ti>
454 <ti></ti>
455</tr>
456<tr>
457 <ti>default-linux/amd64/2005.0/no-multilib</ti>
458 <ti>AMD64 2005.0 profile for multilib-disabled system installations</ti>
459 <ti></ti>
460</tr>
461<tr>
462 <ti>default-linux/arm/2005.0</ti>
463 <ti>Default ARM 2005.0 profile for 2.6 kernels</ti>
464 <ti></ti>
465</tr>
466<tr>
467 <ti>default-linux/hppa/2005.0</ti>
468 <ti>Default HPPA 2005.0 profile for 2.6 kernels</ti>
469 <ti></ti>
470</tr>
471<tr>
472 <ti>default-linux/hppa/2005.0/2.4</ti>
473 <ti>HPPA 2005.0 profile for 2.4 kernels</ti>
474 <ti></ti>
475</tr>
476<tr>
477 <ti>default-linux/mips/2005.0</ti>
478 <ti>Default MIPS 2005.0 profile</ti>
479 <ti></ti>
480</tr>
481<tr>
482 <ti>default-linux/mips/cobalt/2005.0</ti>
483 <ti>Cobalt specific MIPS 2005.0 profile</ti>
484 <ti></ti>
485</tr>
486<tr>
487 <ti>default-linux/mips/mips64/n32/2005.0</ti>
488 <ti>2005.0 profile for n32-supporting MIPS platforms</ti>
489 <ti></ti>
490</tr>
491<tr>
492 <ti>default-linux/mips/mips64/ip28/2005.0</ti>
493 <ti>Indigo2 Impact specific 64-bit 2005.0 profile</ti>
494 <ti></ti>
495</tr>
496<tr>
497 <ti>default-linux/mips/mips64/2005.0</ti>
498 <ti>64-bit MIPS 2005.0 profile</ti>
499 <ti></ti>
500</tr>
501<tr>
502 <ti>default-linux/ppc/2005.0</ti>
503 <ti>Default PPC 2005.0 profile for 2.6 kernels</ti>
504 <ti></ti>
505</tr>
506<tr>
507 <ti>default-linux/ppc64/2005.0</ti>
508 <ti>Default PPC64 2005.0 profile for 2.6 kernels</ti>
509 <ti></ti>
510</tr>
511<tr>
512 <ti>default-linux/s390/2005.0</ti>
513 <ti>Default S390 2005.0 profile</ti>
514 <ti></ti>
515</tr>
516<tr>
517 <ti>default-linux/sparc/sparc32/2005.0</ti>
518 <ti>Default Sparc 32-bit 2005.0 profile</ti>
519 <ti></ti>
520</tr>
521<!-- http://dev.gentoo.org/~dsd/kernel-2.6.htm
522 No subprofiles for sparc
523<tr>
524 <ti>default-linux/sparc/sparc32/2005.0/2.6</ti>
525 <ti>Sparc 32-bit 2005.0 profile for 2.6 kernels</ti>
526 <ti></ti>
527</tr>
528-->
529<tr>
530 <ti>default-linux/sparc/sparc64/2005.0</ti>
531 <ti>Default Sparc 64-bit 2005.0 profile</ti>
532 <ti></ti>
533</tr>
534<!-- http://dev.gentoo.org/~dsd/kernel-2.6.htm
535 No subprofiles for sparc
536<tr>
537 <ti>default-linux/sparc/sparc64/2005.0/2.6</ti>
538 <ti>Sparc 64-bit 2005.0 profile for 2.6 kernels</ti>
539 <ti></ti>
540</tr>
541-->
542<tr>
543 <ti>default-linux/x86/2005.0</ti>
544 <ti>Default x86 2005.0 profile for 2.6 kernels</ti>
545 <ti></ti>
546</tr>
547<tr>
548 <ti>default-linux/x86/2005.0/2.4</ti>
549 <ti>x86 2005.0 profile for 2.4 kernels</ti>
550 <ti></ti>
551</tr>
552</table>
553
554<p>
555To switch to the selected profile, point the <path>/etc/make.profile</path>
556symlink to the new location. Make sure your Portage is updated before you change
557your profile!
558</p>
559
560<pre caption="Changing to a 2005.0 profile">
561# <i>rm /etc/make.profile</i>
562# <i>ln -s ../usr/portage/profiles/</i>&lt;selected profile&gt;<i> /etc/make.profile</i>
563</pre>
564
565<p>
566If you are running a Linux 2.4-based system but want to migrate to a 2.6-based
567kernel, make sure you read our <uri link="/doc/en/migration-to-2.6.xml">Gentoo
568Linux 2.6 Migration Guide</uri>.
569</p>
570
571</body>
572</section>
261<section> 573<section>
262<title>Updating to 2004.3</title> 574<title>Updating to 2004.3</title>
263<body> 575<body>
264 576
265<p> 577<p>
… …
297<path>/var/lib/portage/world</path> after the profile switch, or manually 609<path>/var/lib/portage/world</path> after the profile switch, or manually
298emerge them. 610emerge them.
299</p> 611</p>
300 612
301<p> 613<p>
302<b>ppc</b> - <c>sys-fs/udev</c> is now the default instead of <c>sys-fs/devfs</c> 614<b>ppc</b> - <c>sys-fs/udev</c> is now the default instead of
303for newly installed machines. This has no effect on already installed machines, 615<c>sys-fs/devfs</c> for newly installed machines. This has no
304though. 616effect on already installed machines, though.
617</p>
618
619</body>
620</section>
621<section>
622<title>Updating Portage to Support Cascading Profiles</title>
623<body>
624
305</p> 625<p>
626Although this section does not seem to integrate well in this upgrading guide,
627it is quite important. Any profile listed above this section requires a Portage
628version that supports cascading profiles. However, some obsoleted profiles don't
629allow the user to upgrade Portage or the user is using a profile that isn't
630available anymore - any attempt to upgrade Portage will result in a failure.
631</p>
632
633<p>
634To work around this problem, users can set a temporary symbolic link to the
635<e>obsolete</e> profile, allowing them to upgrade their Portage after which
636they can continue with the upgrade procedure set forth in this guide. Please
637substitute <c>&lt;arch&gt;</c> with your respective architecture:
638</p>
639
640<pre caption="Updating Portage through the obsolete profile">
641# <i>rm /etc/make.profile</i>
642# <i>cd /etc</i>
643# <i>ln -sf ../usr/portage/profiles/obsolete/&lt;arch&gt; make.profile</i>
644# <i>emerge -n '>=sys-apps/portage-2.0.51'</i>
645</pre>
306 646
307</body> 647</body>
308</section> 648</section>
309<section> 649<section>
310<title>Updating to 2004.2</title> 650<title>Updating to 2004.2</title>
311<body> 651<body>
312 652
313<p> 653<p>
314To switch to the 2004.2 profile, point the <path>/etc/make.profile</path> symlink 654To switch to the 2004.2 profile, point the <path>/etc/make.profile</path>
315to the new location: 655symlink to the new location:
316</p> 656</p>
317 657
318<warn> 658<warn>
319Don't forget to upgrade Portage <e>before</e> you change your profile!!! 659Don't forget to upgrade Portage <e>before</e> you change your profile!!!
320</warn> 660</warn>
… …
344<section> 684<section>
345<title>Updating to 2004.0</title> 685<title>Updating to 2004.0</title>
346<body> 686<body>
347 687
348<p> 688<p>
349To switch to the 2004.0 profile, point the <path>/etc/make.profile</path> symlink 689To switch to the 2004.0 profile, point the <path>/etc/make.profile</path>
350to the new location: 690symlink to the new location:
351</p> 691</p>
352 692
353<pre caption="Updating the /etc/make.profile symlink"> 693<pre caption="Updating the /etc/make.profile symlink">
354<comment>substitute &lt;arch&gt; with your arch</comment> 694<comment>substitute &lt;arch&gt; with your arch</comment>
355# <i>rm /etc/make.profile</i> 695# <i>rm /etc/make.profile</i>
Legend:
Removed from v.1.18  
changed lines
  Added in v.1.34
  ViewVC Help
Powered by ViewVC 1.1.13