mirror of https://github.com/tLDP/LDP
revised old docuemnt that had been archived; converted to docbook and submitted by original author
This commit is contained in:
parent
44bbd74a19
commit
17019908e5
|
@ -1,28 +1,39 @@
|
|||
<!doctype linuxdoc system>
|
||||
<!DOCTYPE Article PUBLIC "-//OASIS//DTD DocBook V4.1//EN">
|
||||
|
||||
<!-- This is the second revision of the original upgrade.how document.
|
||||
<!-- This is the third revision of the original upgrade.how document.
|
||||
-->
|
||||
|
||||
<article>
|
||||
|
||||
<title>Upgrading your Linux Distribution mini-HOWTO
|
||||
<author>Greg Louis, <tt/glouis@dynamicro.on.ca/
|
||||
<date>v1.11, 6 June 1996
|
||||
<articleinfo>
|
||||
<title>Upgrading Your linux Distribution mini-HOWTO</title>
|
||||
<authorgroup>
|
||||
<author>
|
||||
<firstname>Greg</firstname>
|
||||
<surname>Louis</surname>
|
||||
<affiliation>
|
||||
<address>
|
||||
<email>glouis@dynamicro.on.ca</email>
|
||||
</address
|
||||
</affiliation>
|
||||
</author>
|
||||
</authorgroup>
|
||||
<pubdate>v1.2, 9 March 2002</pubdate>
|
||||
<copyright>
|
||||
<year>1996, 2002</year>
|
||||
<holder>Dynamicro Consulting Limited</holder>
|
||||
</copyright>
|
||||
<abstract>
|
||||
Hints and tips on upgrading from one linux distribution to
|
||||
another.
|
||||
<p>
|
||||
<bf>Archived Document Notice:</bf> This document has been archived by the LDP
|
||||
because it does not apply to modern Linux systems. It is no longer
|
||||
being actively maintained.
|
||||
</p>
|
||||
<para>
|
||||
Hints and tips on upgrading from one linux distribution to
|
||||
another. This is version 1.2, 2002-03-09.
|
||||
</para>
|
||||
</abstract>
|
||||
</articleinfo>
|
||||
|
||||
<toc>
|
||||
<sect1>
|
||||
<title>IMPORTANT!!! Disclaimer and Copyright</title>
|
||||
|
||||
<sect>IMPORTANT!!! Disclaimer and Copyright
|
||||
|
||||
<p>
|
||||
<para>
|
||||
The procedure to which this document attempts to be a guide is
|
||||
inherently dangerous to the programs and data stored in your computer.
|
||||
You carry out any such procedure entirely at your own risk. The steps
|
||||
|
@ -33,60 +44,100 @@ data. You are entirely on your own in any use you may make of the
|
|||
information presented herein, and the author shall not be liable in
|
||||
any way whatsoever for any damage or inconvenience of any kind that
|
||||
you may suffer in so doing.
|
||||
|
||||
This document is copyright 1996, Dynamicro Consulting Limited, and is
|
||||
released under the terms of the GNU General Public License. This
|
||||
</para>
|
||||
<para>
|
||||
This document is copyright © 1996, 2000 Dynamicro Consulting Limited,
|
||||
and is released under the terms of the GNU General Public
|
||||
License. This
|
||||
basically means that you may copy and modify it at will, but may not
|
||||
prevent others from doing likewise.
|
||||
|
||||
</para>
|
||||
<para>
|
||||
Comments and questions may be directed to the author. Especially
|
||||
welcome, for use in future revisions, are accounts of successful
|
||||
upgrades of complex systems.
|
||||
|
||||
<sect>Changes since version 1.1
|
||||
|
||||
<p>
|
||||
<itemize>
|
||||
<item>Added this history section
|
||||
<item>Added Zoltán Hidvégi's suggestion re mtime and ctime.
|
||||
Thanks, Zoltán!
|
||||
<item>Added an Acknowledgements section
|
||||
</itemize>
|
||||
|
||||
<sect>Introduction
|
||||
|
||||
<p>
|
||||
<sect1>How to slay and reincarnate your linux box!
|
||||
|
||||
<p>
|
||||
</para>
|
||||
</sect1>
|
||||
<sect1>
|
||||
<title>Changes since version 1.1</title>
|
||||
<para>
|
||||
<itemizedlist>
|
||||
<listitem>
|
||||
<para>
|
||||
Converted to docbook
|
||||
</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>
|
||||
Corrected some obsolete information
|
||||
</para
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>
|
||||
Added this history section
|
||||
</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>
|
||||
Added Zoltán Hidvégi's suggestion re mtime and ctime.
|
||||
Thanks, Zoltán!
|
||||
</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>
|
||||
Added an Acknowledgements section
|
||||
</para>
|
||||
</listitem>
|
||||
</itemizedlist>
|
||||
</para>
|
||||
</sect1>
|
||||
<sect1>
|
||||
<title>Introduction</title>
|
||||
<sect2>
|
||||
<title>How to slay and reincarnate your linux box!</title>
|
||||
<para>
|
||||
The purpose of this document is to offer tips to help you through the
|
||||
destruction and reinstallation of a linux system. It's not a
|
||||
foolproof cookbook by any means; but I hope it will serve as some
|
||||
foolproof cookbook by any means, but I hope it will serve as some
|
||||
indication of what you need to think about, and of the order in which
|
||||
to do things. It would have been a help to me, if someone else had
|
||||
written something like this before I did my first upgrade; so I hope
|
||||
it will be a help to you, if you have a linux machine to rebuild.
|
||||
|
||||
</para>
|
||||
<para>
|
||||
Don't take it as gospel, though: your mileage will almost certainly
|
||||
vary. Even the directory names in this document may be different from
|
||||
the ones you need to use; some people have /usr/home instead of /home,
|
||||
for example; others call it /u, and some (delicate shudder :) even put
|
||||
all their users directly under /usr itself! I can't be specific about
|
||||
your system, so I've just used the names the way they are in mine.
|
||||
|
||||
</para>
|
||||
<para>
|
||||
You'll also notice that I use Slackware distributions, and that I
|
||||
assume you've enough RAM and hard disk space to install linux kernel
|
||||
source and build your own kernel. If your system is different, some
|
||||
of my recommendations won't apply; but I hope you'll still find the
|
||||
general outline to be of assistance in your rebuild project.
|
||||
|
||||
<sect1>Why would anyone want to do that?
|
||||
|
||||
<p>
|
||||
</para>
|
||||
</sect2>
|
||||
<sect2>
|
||||
<title>Why would anyone want to do that?</title>
|
||||
<para>
|
||||
Good question! If it can possibly be avoided, don't do it! (That's
|
||||
the single most important recommendation in this whole guide!!!) But
|
||||
there are times when you may have to.
|
||||
|
||||
the single most important recommendation in this whole guide!!!) When
|
||||
this guide was first written, not many people had hard disks big enough
|
||||
to accomodate two whole Linux installations; these days, that's by no
|
||||
means uncommon. If you possibly can, build your new system in a
|
||||
separate partition (or group of partitions), keeping the old one intact
|
||||
till you're satisfied that the new one is just the way you want it. If
|
||||
you can avoid destroying the old system to make room for the new, by
|
||||
all means avoid it! But there are times when you may have no choice.
|
||||
</para>
|
||||
<para>
|
||||
(These examples are a bit dated, but they serve to illustrate my
|
||||
point:)
|
||||
</para>
|
||||
<para>
|
||||
For example, I installed a 4Gb hard disk and then found out that
|
||||
Slackware 2.0 vintage linux didn't know a hard disk could have more
|
||||
than 2Gb, and it got horribly confused. So I had to upgrade to the
|
||||
|
@ -94,7 +145,8 @@ then-current Slackware 2.3. That upgrade was a gruelling experience,
|
|||
and it's part of the reason I'm writing these notes. I did just about
|
||||
everything wrong, and only good luck and the fact that I had another
|
||||
running linux box beside me saved me from disaster.
|
||||
|
||||
</para>
|
||||
<para>
|
||||
As another example, I found that I just couldn't succeed in building a
|
||||
working a.out linux kernel in the 1.3 series, using an out-of-the-box
|
||||
Slackware 2.3 installation (another machine, not the one I botched
|
||||
|
@ -102,12 +154,20 @@ before). I took the plunge, bought Slackware 3.0 on CDROM and
|
|||
converted to ELF. This time the reinstallation went better, thanks in
|
||||
part to the previous bitter experience, and it served as the source of
|
||||
most of the ideas I'm offering you here.
|
||||
|
||||
<sect1>Do you have to ``destroy and reinstall?''
|
||||
|
||||
<p>
|
||||
It's safer, oddly enough. If you install over top of an existing
|
||||
linux system, chances are you'll have a mixture of old and new
|
||||
</para>
|
||||
</sect2>
|
||||
<sect2>
|
||||
<title>Do you have to ``destroy and reinstall?''</title>
|
||||
<para>
|
||||
See above. If you can build your new system in otherwise empty disk
|
||||
space, do it! For the rest of this document, however, I'll assume that
|
||||
this is one of those times when that option isn't available; you either
|
||||
have to reinstall "in place," over top of the existing system, or you
|
||||
have to bite the bullet and rebuild from scratch.
|
||||
</para>
|
||||
<para>
|
||||
The latter is safer, oddly enough. If you install over top of an
|
||||
existing linux system, chances are you'll have a mixture of old and new
|
||||
binaries, old and new configuration files, and generally a mess to try
|
||||
to administer. Wiping the system clean, and then putting back only
|
||||
what you know you need, is a drastic but effective way to get a clean
|
||||
|
@ -118,18 +178,11 @@ the individual bits -- especially gcc and its libraries, and binutils
|
|||
-- current. If the stuff you use is reasonably up-to-date, and you
|
||||
can keep it so by bringing in, and if need be compiling, new code from
|
||||
time to time, then there's no need for a mass upgrade.)
|
||||
|
||||
As Patrick Volkerding points out (he too recommends the wipe-it-clean
|
||||
procedure for upgrades), installing ELF on top of a running a.out
|
||||
system is a recipe for disaster; at least, if you know enough to try
|
||||
it, you needn't read this guide!
|
||||
|
||||
Even without that complication, though, you're better to build from
|
||||
scratch.
|
||||
|
||||
<sect1>How long will it take?
|
||||
|
||||
<p>
|
||||
</para>
|
||||
</sect2>
|
||||
<sect2>
|
||||
<title>How long will it take?</title>
|
||||
<para>
|
||||
Depends, of course, on how complex your system is. But I figure that,
|
||||
for the successful upgrade (the other one? -- don't ask! :) I spent
|
||||
about ten hours making backups, six hours rebuilding the system to the
|
||||
|
@ -141,29 +194,41 @@ suffice for a reasonably complex rebuilding job. Maybe less if you're
|
|||
reinstalling from hard disk (I used CDROM) or more if you need to
|
||||
install from floppies. Maybe less if you've got a fast Pentium, more
|
||||
if it's a 386. You get the idea.
|
||||
|
||||
</para>
|
||||
<para>
|
||||
Those were the bad old days. Now, with faster disks and faster
|
||||
machines and CD writers, things go better. My notebook was stolen in
|
||||
December, 2002, and when the new one came, I was up and pretty near
|
||||
complete -- despite having lost the old system without the chance to
|
||||
save the latest changes -- after about seven hours of effort.
|
||||
</para>
|
||||
<para>
|
||||
So much for the introduction. Here's how to set about it, once you've
|
||||
decided it must be done. Arm yourself with fortitude and Jolt or
|
||||
whatever, and:
|
||||
|
||||
<sect>Write down everything you do.
|
||||
|
||||
<p>
|
||||
</para>
|
||||
</sect2>
|
||||
</sect1>
|
||||
<sect1>
|
||||
<title>Write down everything you do.</title>
|
||||
<para>
|
||||
It's extremely valuable to have a record of what you've done in the
|
||||
process of preparing for, and carrying out, the changeover.
|
||||
Especially important is a list of the backups you'll be making in
|
||||
preparation for the destruction of your existing system.
|
||||
|
||||
<sect>Make a full backup of the existing system.
|
||||
|
||||
<p>
|
||||
Generally speaking, backups tend to be written on media that are
|
||||
</para>
|
||||
</sect1>
|
||||
<sect1>
|
||||
<title>Make a full backup of the existing system.</title>
|
||||
<para>
|
||||
Generally speaking, big backups tend to be written on media that are
|
||||
sequentially accessed. That being so, you won't want to use this
|
||||
complete backup for restoring significant numbers of files; it's got
|
||||
too many files on it that you don't want. It's better to create small
|
||||
backups of individual segments that you know you're going to restore
|
||||
in their entirety. I'll list a bunch of examples later.
|
||||
|
||||
</para>
|
||||
<para>
|
||||
Why then should you start with a full backup? Two basic reasons:
|
||||
first, in the event of a catastrophic failure installing the new
|
||||
system, you'll have a way to get back to the starting point with
|
||||
|
@ -172,15 +237,18 @@ installation, there is a very large chance that one or two important
|
|||
files will be overlooked. In that case the clumsiness of restoring
|
||||
those one or two files from the full backup set will be preferable to
|
||||
the inconvenience of doing without them.
|
||||
|
||||
</para>
|
||||
<para>
|
||||
To save time and space, if you've still got the distribution medium
|
||||
for your old linux version, you might want to back up only those files
|
||||
the mtime or ctime of which is more recent than the date of the
|
||||
original installation.
|
||||
|
||||
<sect>Back up /etc and its subdirectories on one or more floppies.
|
||||
|
||||
<p>
|
||||
</para>
|
||||
</sect1>
|
||||
<sect1>
|
||||
<title>Back up /etc and its subdirectories on one or more floppies.
|
||||
</title>
|
||||
<para>
|
||||
This is the other extreme: you won't be restoring these files (for the
|
||||
most part, anyway); you'll be comparing them with the new ones that
|
||||
get created during installation. Why? Because the new ones may have
|
||||
|
@ -191,141 +259,181 @@ formats of the configuration files and startup scripts that the /etc
|
|||
tree contains, and you'll very likely have to edit your old data into
|
||||
these files so as to preserve the new formats and take advantage of
|
||||
the improvements.
|
||||
|
||||
<sect>Make separate backups of each group of files you want to preserve.
|
||||
|
||||
<p>
|
||||
</para>
|
||||
</sect1>
|
||||
<sect1>
|
||||
<title>Make separate backups of each group of files you want to preserve.
|
||||
</title>
|
||||
<para>
|
||||
This is the most variable part of the job, and all I can really do to
|
||||
help is to describe what I did in my system, in the hope that it will
|
||||
serve as a rough guide. Basically, you want to look at every
|
||||
directory that contains any
|
||||
|
||||
<itemize>
|
||||
<item> files that aren't part of your standard linux installation, or
|
||||
<item> files that are actually newer than the ones you'll
|
||||
install when you do your new linux installation
|
||||
</itemize>
|
||||
|
||||
</para>
|
||||
<para>
|
||||
<itemizedlist>
|
||||
<listitem>
|
||||
<para>
|
||||
files that aren't part of your standard linux installation, or
|
||||
</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>
|
||||
files that are actually newer than the ones you'll install when you do
|
||||
your new linux installation.
|
||||
</para>
|
||||
</listitem>
|
||||
</itemizedlist>
|
||||
</para>
|
||||
<para>
|
||||
and separate out only those files that you want to carry over.
|
||||
|
||||
</para>
|
||||
<para>
|
||||
(Another possible strategy is to back up all files with mtime or
|
||||
ctime more recent than the day of the previous linux installation,
|
||||
as mentioned above, and then restore from that. If you do that,
|
||||
you have to take into account that the new linux distribution may
|
||||
contain versions of some files that are newer still than the ones
|
||||
you saved.)
|
||||
|
||||
</para>
|
||||
<para>
|
||||
In my case, I ended up making a .tgz file on the backup medium for
|
||||
each of
|
||||
|
||||
<itemize>
|
||||
<item> /usr/lib/rn
|
||||
<item> /usr/lib/smail
|
||||
<item> /usr/lib/trn (the rest of /usr/lib would be reinstalled)
|
||||
<item> /usr/local/src
|
||||
<item> /usr/local/bin
|
||||
<item> /usr/local/lib
|
||||
<item> /usr/local/lpfont
|
||||
<item> /usr/local/man
|
||||
<item> /usr/local/sbin
|
||||
<item> /usr/local/thot (there were other /usr/local files I didn't need)
|
||||
<item> /usr/openwin
|
||||
<item> /usr/src/lilo-17 (because my new Slackware still had version 16)
|
||||
<item> /usr/src/linux-1.2.13 (because I'd done some customizing)
|
||||
<item> /usr/X11R6/lib/X11/app-defaults
|
||||
<item> /usr/X11R6/lib/X11/initrc (the rest of Xfree86 was to be reinstalled)
|
||||
<item> /var/named
|
||||
<item> /var/openwin
|
||||
<item> /var/texfonts
|
||||
</itemize>
|
||||
|
||||
</para>
|
||||
<para>
|
||||
<itemizedlist>
|
||||
<listitem><para>/usr/lib/rn</para></listitem>
|
||||
<listitem><para>/usr/lib/smail</para></listitem>
|
||||
<listitem><para>/usr/lib/trn (the rest of /usr/lib would be
|
||||
reinstalled)</para></listitem
|
||||
<listitem><para>/usr/local/src</para></listitem>
|
||||
<listitem><para>/usr/local/bin</para></listitem>
|
||||
<listitem><para>/usr/local/lib</para></listitem>
|
||||
<listitem><para>/usr/local/lpfont</para></listitem>
|
||||
<listitem><para>/usr/local/man</para></listitem>
|
||||
<listitem><para>/usr/local/sbin</para></listitem>
|
||||
<listitem><para>/usr/local/thot (there were other /usr/local files
|
||||
I didn't need)</para></listitem>
|
||||
<listitem><para>/usr/openwin</para></listitem>
|
||||
<listitem><para>/usr/src/lilo-17 (because my new Slackware still
|
||||
had version 16)</para></listitem>
|
||||
<listitem><para>/usr/src/linux-1.2.13 (because I'd done some
|
||||
customizing)</para></listitem>
|
||||
<listitem><para>/usr/X11R6/lib/X11/app-defaults</para></listitem>
|
||||
<listitem><para>/usr/X11R6/lib/X11/initrc (the rest of Xfree86 was
|
||||
to be reinstalled)</para></listitem>
|
||||
<listitem><para>/var/named</para></listitem>
|
||||
<listitem><para>/var/openwin</para></listitem>
|
||||
<listitem><para>/var/texfonts</para></listitem>
|
||||
</itemizedlist>
|
||||
</para>
|
||||
<para>
|
||||
My machine was relatively easy in that there were no spool files to
|
||||
worry about. I don't run a news spool on this box, and since there
|
||||
are only two users, it was easiest just to get all the mail read
|
||||
before shutting down. Otherwise, /var/spool directories would have
|
||||
had to be backed up at the last minute. (And, of course, the news
|
||||
library and site directories!)
|
||||
|
||||
<sect>Prepare root and boot floppies for the new installation.
|
||||
|
||||
<p>
|
||||
Details of how to do this will be found in the installation guide for
|
||||
your new distribution.
|
||||
|
||||
<sect>Format floppies for the temporary kernel and the final build.
|
||||
|
||||
<p>
|
||||
</para>
|
||||
</sect1>
|
||||
<sect1>
|
||||
<title>Prepare root and boot floppies for the new
|
||||
installation.</title>
|
||||
<para>
|
||||
If you're lucky, your new package will include a bootable CD and this
|
||||
step won't be needed. If you haven't got a CDROM drive, or can't boot
|
||||
from it, details of how to make the floppies will be found in the
|
||||
installation guide for your new distribution.
|
||||
</para>
|
||||
</sect1>
|
||||
<sect1>
|
||||
<title>Format floppies for the temporary kernel and the final
|
||||
build.</title>
|
||||
<para>
|
||||
You'll need two, one floppy for each.
|
||||
|
||||
</para>
|
||||
<para>
|
||||
After all that's done, you're ready for the Big Moment. The next
|
||||
step removes the system from production.
|
||||
|
||||
<sect>Inhibit logins and back up the /root and /home trees.
|
||||
|
||||
<p>
|
||||
</para>
|
||||
</sect1>
|
||||
<sect1>
|
||||
<title>Inhibit logins and back up the /root and /home trees.</title>
|
||||
<para>
|
||||
This is the last thing to be done on the old system before you destroy
|
||||
it, so as to carry forward the most current user and root information.
|
||||
|
||||
<sect>Boot from the new installation's boot and root floppies.
|
||||
|
||||
<p>
|
||||
<sect>Delete the linux partitions with fdisk and recreate them.
|
||||
|
||||
<p>
|
||||
To inhibit logins, just echo "getting ready for upgrade" >/etc/nologin
|
||||
(as root, of course).
|
||||
</para>
|
||||
</sect1>
|
||||
<sect1>
|
||||
<title>Boot from the new installation's boot and root
|
||||
floppies.</title>
|
||||
<para>
|
||||
Or, if you have that capability, boot the installation CD itself.
|
||||
</para>
|
||||
</sect1>
|
||||
<sect1>
|
||||
<title>Delete the linux partitions with fdisk and recreate
|
||||
them.</title>
|
||||
<para>
|
||||
The installation guide will explain how to set about doing this, which
|
||||
will destroy the old system. From now on you're dependent on the
|
||||
quality of the backups you made in the earlier steps! You have been
|
||||
warned!
|
||||
|
||||
<sect>Run the new linux installation.
|
||||
|
||||
<p>
|
||||
</para>
|
||||
</sect1>
|
||||
<sect1>
|
||||
<title>Run the new linux installation.</title>
|
||||
<para>
|
||||
There are already several good documents describing how to do this, so
|
||||
I'm not going into any detail. Continue from here when the new system
|
||||
can boot from its hard disk.
|
||||
|
||||
</para>
|
||||
<para>
|
||||
Along the way, be sure to make a floppy that you can boot as well,
|
||||
since the kernel that the linux setup installs has to be replaced and
|
||||
accidents can happen during that process. Be sure to install the
|
||||
development packages and the kernel source.
|
||||
|
||||
<sect>With the new linux system booted from the hard disk, edit /etc/fstab
|
||||
|
||||
<p>
|
||||
and add your swap partition. Then run the command "swapon -a".
|
||||
I don't know why, but Slackware setup doesn't offer to do this for you
|
||||
if your swap partition exists already. Then, when you boot your new
|
||||
system and the rc.S script tries to turn swapping on, it can't find
|
||||
the partition in the fstab file and swapping doesn't get enabled.
|
||||
This step fixes it.
|
||||
|
||||
<sect>Restore configuration data to the /etc directory and subdirectories.
|
||||
|
||||
<p>
|
||||
</para>
|
||||
</sect1>
|
||||
<sect1>
|
||||
<title>Restore configuration data to the /etc directory and
|
||||
subdirectories.</title>
|
||||
<para>
|
||||
As described above, you can't just copy all of the old files back into
|
||||
/etc and expect things to work properly afterward. Some files you can
|
||||
do that with; for example, /etc/XF86Config (as long as you're using
|
||||
the same version of Xfree86 -- and the same video hardware -- in the
|
||||
the same version of XFree86 -- and the same video hardware -- in the
|
||||
new installation as you did in the old). For the most part, though,
|
||||
it's best to use diff to compare the old and new files before doing
|
||||
any copying. Watch out especially for significant changes in the
|
||||
files in /etc/rc.d, which may require you to reestablish your old
|
||||
configuration by hand editing, instead of by copying the old rc
|
||||
scripts from your backup. Once it's all done, reboot.
|
||||
|
||||
<sect>Configure and rebuild the linux kernel.
|
||||
|
||||
<p>
|
||||
files in /etc/rc.d and friends, which may require you to reestablish
|
||||
your old configuration by hand editing, instead of by copying the old
|
||||
rc scripts from your backup. Once it's all done, reboot.
|
||||
</para>
|
||||
</sect1>
|
||||
<sect1>
|
||||
<title>Configure and rebuild the linux kernel.</title>
|
||||
<para>
|
||||
Even if you don't absolutely have to do this in order to get a kernel
|
||||
that supports your hardware, it's worth doing it in order to get a
|
||||
kernel that doesn't contain masses of drivers for stuff your machine
|
||||
doesn't have. For details, see the Kernel HOWTO. Install the rebuilt
|
||||
kernel on a floppy at first; once that boots ok, install on the hard
|
||||
disk, run lilo if you're using it, and reboot.
|
||||
|
||||
<sect>Restore the stuff from the backups you made earlier.
|
||||
|
||||
<p>
|
||||
doesn't have -- and even more so, in order to get a good understanding
|
||||
of how your kernel configuration options affect the behaviour of your
|
||||
system! As linux grows, the ability of the distribution vendors to
|
||||
configure a one-size-fits-all kernel has become very limited. For
|
||||
details on how it's done, see the Kernel HOWTO; it looks complicated at
|
||||
first, but it's not rocket science; just take it a step at a time.
|
||||
</para>
|
||||
<para>
|
||||
Install the rebuilt kernel on a floppy at first; once that boots ok,
|
||||
install on the hard disk, run lilo if you're using it, and reboot.
|
||||
</para>
|
||||
</sect1>
|
||||
<sect1>
|
||||
<title>Restore the stuff from the backups you made earlier.</title>
|
||||
<para>
|
||||
Some of the binaries may need to be reinstalled from the source
|
||||
directories; I had to do that with lilo, for example, since my version
|
||||
was newer than the one on the Slackware installation and I hadn't
|
||||
|
@ -334,35 +442,57 @@ your restored programs and confirm the existence and correctness of
|
|||
configuration files, libraries and so on. In some cases, you may have
|
||||
to restore things in a specific order; you did make notes during
|
||||
backup, didn't you? ;-)
|
||||
|
||||
<sect>Review security.
|
||||
|
||||
<p>
|
||||
</para>
|
||||
</sect1>
|
||||
<sect1>
|
||||
<title>Review security.</title>
|
||||
<para>
|
||||
(Sigh...) When I wrote this, this step was important but not crucial;
|
||||
the Internet was a friendlier place even in 1996 than it is today.
|
||||
Now, if your machine has Internet access, this step is utterly vital,
|
||||
and there are whole books devoted to getting it right; I can do nothing
|
||||
more here than offer a few very basic pointers:
|
||||
</para>
|
||||
<para>
|
||||
Check file permissions and directory permissions to be sure that
|
||||
access is neither too restricted nor too easy. I find that Slackware
|
||||
tends to lean toward a more open environment than I like, so I go
|
||||
around changing 755's to 711's for binaries in the .../bin directories
|
||||
and stuff like that. Or even 700's in the .../sbin ones. Especial
|
||||
care is needed if you've carried over an ftp server; but then, if you
|
||||
were running an ftp server, you probably thought of that already. :)
|
||||
|
||||
<sect>Enable logins.
|
||||
|
||||
<p>
|
||||
care is needed if you've carried over ftp, telnet or web servers; but
|
||||
then, if you were running those, you probably thought of that already. :)
|
||||
</para>
|
||||
<para>
|
||||
Look at /etc/inetd.conf or /etc/xinetd.conf and make sure you're not
|
||||
running any Internet services you don't need to. Also go through the
|
||||
boot scripts in /etc/rc.d and friends for the same purpose. Check your
|
||||
firewall rules if your box is an Internet gateway or has Internet
|
||||
access.
|
||||
</para>
|
||||
</sect1>
|
||||
<sect1>
|
||||
<title>Enable logins.</title>
|
||||
<para>
|
||||
You're up and running. Over the next little while, there'll probably
|
||||
be details to clean up; but the bulk of the work is done. Enjoy!
|
||||
|
||||
<sect>Sorry, but once again:
|
||||
|
||||
<p>
|
||||
<bf>USE THIS INFORMATION AT YOUR OWN RISK!</bf>
|
||||
|
||||
</para>
|
||||
</sect1>
|
||||
<sect1>
|
||||
<title>Sorry, but once again:
|
||||
<emphasis>USE THIS INFORMATION AT YOUR OWN RISK!</emphasis>
|
||||
</title>
|
||||
<para>
|
||||
(See the disclaimer at the start of this document.)
|
||||
|
||||
<sect>Acknowledgements
|
||||
|
||||
<p>
|
||||
</para>
|
||||
</sect1>
|
||||
<sect1>
|
||||
<title>Acknowledgements</title>
|
||||
<para>
|
||||
Thanks for contributing to the content of this mini-HOWTO are
|
||||
gratefully tendered to Zoltán Hidvégi.
|
||||
|
||||
gratefully tendered to Zoltán Hidvégi; and for motivating me to bring
|
||||
it a bit closer to modern practice, to Steve Sanfratello, author of the
|
||||
rpmupgrade-HOWTO.
|
||||
</para>
|
||||
</sect1>
|
||||
</article>
|
||||
|
Loading…
Reference in New Issue