Go to:
Gentoo Home
Documentation
Forums
Lists
Bugs
Planet
Store
Wiki
Get Gentoo!
Gentoo's Bugzilla – Attachment 3809 Details for
Bug 7776
The Upgrade to 1.4 Doc
Home
|
New
–
[Ex]
|
Browse
|
Search
|
Privacy Policy
|
[?]
|
Reports
|
Requests
|
Help
|
New Account
|
Log In
[x]
|
Forgot Password
Login:
[x]
The xml...
upgrade-to-gentoo-1.4.xml (text/xml), 8.16 KB, created by
Gustavo Felisberto (RETIRED)
on 2002-09-10 21:06:39 UTC
(
hide
)
Description:
The xml...
Filename:
MIME Type:
Creator:
Gustavo Felisberto (RETIRED)
Created:
2002-09-10 21:06:39 UTC
Size:
8.16 KB
patch
obsolete
><?xml version='1.0'?> ><guide> ><title>Upgrade to Gentoo 1.4 Guide</title> ><author title="Writer"><mail link="gustavo@felisberto.net"> > Gustavo Felisberto</mail> ></author> ><author title="Writer"><mail link="rjlouro@rjlouro.org"> > Ricardo Loureiro</mail> ></author> > ><abstract>This guide shows you how to upgrade a older system running Gentoo 1.1a, 1.2 or 1.3 to the new 1.4 system.</abstract> > > > ><version>0.1</version> ><date>9 September 2002</date> > ><chapter> > <title>Before you begin</title> ><section> > <title>Warning to the light hearted</title> > <body> ><warn>This procedure has been tested alot, but it can make your system unbootable.</warn> ><p>With this in mind please note that this procedure is a dangerous one. It is also very time consuming, if when installing you tought that your machine was not fast enough for using a stage 1 this is not for you. Please read the all document before starting, and think twice before starting the upgrade. If you dont have alot of Linux experience this is not for you. ></p> ><p>Some of the text in this file is taken from the README file in the upgrade scripts by <mail link="carpaski@gentoo.org">Nicholas Jones</mail></p> > </body> > ></section> > ><section> > <title>Files to get and general info</title> > <body> > <p>You will need to get the 4 scripts that Nicholas Jones made. You can get them <uri link="http://www.gentoo.org/~carpaski/system_update/">here</uri>. Get the files named 1,2,3 and 4. Don't forget to change the file permissions and make them executable. > </p> > <p><uri link="http://www.gentoo.org/~carpaski/system_update/1">Script 1</uri> will do some tests to see if everything is ok as it is. It will also make backups of gcc, glibc, binutils, ncurses, gettext, texinfo. You will need these if something goes really wrong. It is very unlikely (we have not seen it yet, but it can happen), so it is good to be prepared. > </p> > <p><uri link="http://www.gentoo.org/~carpaski/system_update/2">Script 2</uri> will do the first part of the upgrade, it will make changes to the profile symlinks, emerge portage and do a build+bootstap of gcc and binutils. ><note>For this script to work on non x86 machines you have to change the ARCH var at the beggining of the script. You can use x86, ppc, sparc and sparc64.</note> </p> > <p><uri link="http://www.gentoo.org/~carpaski/system_update/3">Script 3</uri> will continue the upgrade and will do a full stage 3 bootstrap acording to your <path>/etc/make.conf</path>, building gcc, glibc, binutils ..... > </p> > <p><uri link="http://www.gentoo.org/~carpaski/system_update/4">Script 4</uri> is optional and it will unmerge and re-emerge all broken packages that may exist after script 3. > </p> > </body> ></section> ><section> > <title>Authors advices</title> > <body> > <p><e>Dont overclock your system during upgrade!</e> I (Gustavo Felisberto) had a very painfull experience during my upgrade. My dual P3 866mhz system was overclocked to 1007mhz. And probably the memory did not like it alot and gcc would segfault randomly. > </p> > <p>Also after starting the second script don't logout, and don't log out until after step 3. The upgrade process affects init and login in a way as to lock the consoles upon logout due to missing libs. You may get "respawning to quickly, disabling". > </p> > </body> ></section> ></chapter> > ><chapter> > <title>The Upgrade</title> ><section> > <title>Script 1</title> > <body> > <p>Before starting to run any of the cripts please upgrade your portage tree and optionaly do a upgrade to your system</p> ><pre> ><i># emerge rsync</i> ><i># emerge -u world</i> <codenote> This one is optional, but a very good idea to do before going on</codenote> ></pre> ><p>The script 1 will do some cheks on your system, it will also install the Gentoo Toolkit just in case you dont have it. The most important part is that it will backup some basic packages to <path>/usr/portage/packages/All</path> . This will take about 10 minutes or something. ></p> > </body> ></section> ><section> > <title>Script 2</title> > <body> > <p>This script will change the <path>/etc/make.profile</path> symlink to the correct location for the upgrade. Again i must warn that in case you are not running on x86 you MUST change the ARCH var in this file to the correct value for your architecture (againg, good values are x86, ppc, sparc and sparc64) > </p> > <p>This script will take alot longer than the previous one, about 30 minutes on a dual P3 - 866 with 256MB.</p> > </body> > ></section> > ><section> > <title>Script 3</title> > <body> > <p>Ok, so you now have build and bootstrap the main packages with general flags, it's time to bootstrap again, this time with gcc 3.2 and with your personal flags. Edit <path>make.conf</path> just to make sure you have everything ok.</p> ><pre> ># <i>nano -w /etc/make.conf</i> ></pre> > > <note>If you are upgrading from gcc 2.* please note that in version 3.0 and up there have been introduced some new arch flags. Have a look at <uri>http://www.freehackers.org/gentoo/gccflags/</uri> for information about that and other gcc flags.</note> > > <p>Now, just run the script. I like to do a time, just to keep track of how long it took, but that's completely optional.So, just go ahead and execute the script. This one can take some time, took 156 minutes on a dual 1.5Ghz Athlon MP. The author suggests the movie Star Wars episode IV so the time passes fast.</p> > <p>When it's over you will get some instrucions to follow. It's very important you update your configuration since many important files need to be changed. Best way to this is by running <c>etc-update</c>.</p> ><pre> ># <i>etc-update</i> ></pre> > <p>This upgrade will most likely cause problems with init and login. There are 2 ways to solve this, either type <c>sync ; init u 3</c> or simply reboot your computer. SSH should still work, so you can allways log in to your computer. Reboot your computer if your console hangs or if it starts printing "respawning too quickly" messages.</p> ><pre> ># <i>sync ; init u 3</i> > ><codenote>If console hangs or you get "respawning too quickly messages:</codenote> ># <i>reboot</i> ></pre> > > > </body> ></section> ><section> > <title>Script 4</title> > <body> > <p>Ok, now you have a gcc 3.2 system ready. But, the drawback is that some packages are broken. That's what script 4 will do for you. Remember, this is an optional step, your base system is already updated according to the 1.4 profile. The reason why some packages is simple, some shared libraries were rebuilt or upgraded and programs that depend on it will fail, unless they are also rebuilt. > </p> ><pre> ># <i>./4</i> ></pre> ><p>This process will take even more thal all the others together. So, since you already saw Star Wars episode IV, I would advise you to see all the other 4 episodes. If you have a really slow machine, then probably the entire collection of Seinfeld Episodes (yes, all 180) is a better idea. Just to give an idea, on my dual 1.5Ghz Athlon MP it took 400 minutes and it failed on some packages like evolution and mozilla, so after that I had to recompile them. And we all know how long mozilla takes to build.</p> > <p>When done, script 4 will output the packages it could not compile. Some of them will fail cause they are not gcc 3.2 ready yet, you just will have to wait or do some changes to the ebuilds, if you know what you are doing.</p> > <note>Script 4 will not recompile all your installed packages. if you really want to recompile all your system you'll have to run <c>emerge -e world</c>. Be ready to have some packages who probably will not compile and also to a long waiting time.</note> > </body> ></section> > ></chapter> ><chapter> > <title>Final Considerations</title> ><section> > <body> > <p>As you have seen this is a very tricky update. One of the authors and several other people have been very happy with the upgrade with just minor things to adjust. The other author had minor problems and a really weired one (kde stoped working altough it emerged). > </p> > <p>One good alternative to the upgrade is doing a fresh install of 1.4 . Just backup your <path>/home</path> and your <path>/etc</path>, you will make your users happy by saving their files, and with your config files backed up installing your new system will be easier. > </p> > </body> > ></section> ></chapter> ></guide> > >
You cannot view the attachment while viewing its details because your browser does not support IFRAMEs.
View the attachment on a separate page
.
View Attachment As Raw
Actions:
View
Attachments on
bug 7776
: 3809