Previous Next Table of Contents

2. upgrade to Linux 2.0

Linux 2.0 is vastly different from Linux-1.2.13, but is much the same as Linux-1.3.100+.

Other system components (such as libc) have also changed, so you should spend a few hours upgrading the various components.

Distributions of the 1.3.90+ era, didn't really follow the changes, and used 1.2.13 as the base of their distributions, the result being that you have to.

If your distribution is already configured for Linux 2.0, great!

2.1 Scratch build

If you are at home, and only have one machine, you should still have a second disk to buid the new system on. If you don't, you only have yourself to blame. However, boot diskettes may be enough.

If you are in an office, you really MUST have a second machine, for a week or so. The cost of your services being down may be much more! When the process is finished, you will be able to use that second machine as a general backup, or as your personal workstation.

Offices should have a general approach to backup systems (as well as backup tapes). There will always be a new kernel to test, or a new configuration to play with, and there is always the risk of a disk developing a fatal error.

The benefit of scratch building, is that you know what went into the system, and are starting from nothing. When you have tested your new machine, you can rename it, change the IP address and swop out the system being upgraded.

This does add to the cost, in that you need a spare machine, AND you may need to upgrade each machine twice!

The loss (and gain) of scratch building, is that a lot of rubbish on the disks gets dropped. Just hope that the runnish didn't contain any gems!

2.2 Beware!

There are several interconnected components, that need to be changed together, and some of the components are the ground that you are standing on!

For example, libc is needed by virtually every program on the disk, if it doesn't exist, you won't be able to put it back! Unless you have a boot disk, or other bootable partition, or you have statically linked mv or cp program.

The first thing you should do is locate a boot-disk-set, and use it to see what it look like. You might also like to try booting to single user mode, by adding "single" to the LILO boot line.

You should also locate and save all configuration files that might be lost during the process (/etc/passwd, /etc/hosts and many many others).

You should also be careful when connecting a machine with a broken sendmail, to the internet. You don't want any gaps in service, but you certainly don't want any email to actually be lost!

2.3 Fetching the components

This is one of the reasons for having a second working machine! I fetched what I wanted from the Internet, but you might only have the CDROM's for company. Be lucky.

Collect the list of things from this document. Don't be supprised if more recent versions are available. Be optimistic.


Previous Next Table of Contents