If you want to keep your server available for updates for another year then we suggest upgrading to Red Hat 9 through this tutorial.

Since no one has yet posted a how-to upgrade an old 7.3 redhat to the latest redhat 9.0, here is how you can do it. Commands you issue on shell are in GREEN as usual.

WARNING: GotoArticle.com and the author claim no responsibility for this HOWTO. If your computer doesn't function afterwards, blows up, or turns into a pile of ash, it wasn't my fault. I only list how to do the upgrade, it is up to you to decide if it is worth trying or not.

Lets Begin!
Log into your box using SSH and su to root.

# Now install it.
rpm -i apt-0.5.5cnc5-fr0.rh73.2.i386.rpm

# If you have dependancy issues, fix them. I had one machine
# that did, another that didn't. It just depends on what rpm's
# you've installed before, and your control panel.

# You don't have to do this part, but I did it just to make sure
# everything is already up to date, this upgrades your system
# packages, pretty much same as up2date -uv:
apt-get update
apt-get dist-upgrade

# You can't go from 7.3 to 9.0, so first we upgrade to 8.0.
# To do that, you must:
pico /etc/apt/sources.list

# Within sources.list, you'll see that the 7.3 lines are
# uncommented. Comment them out with # symbols. Then go
# to the 8.0 section and uncomment them.
# Now you can update your server to 8.0:
apt-get update
apt-get dist-upgrade

# That will take about an hour on a dual xeon.
# Fetched 224MB in 7m42s (484kB/s)

# Once done, edit your sources file again:
pico /etc/apt/sources.list

# Like last time, comment out the 8.0, and uncomment 9.0.
# Now upgrade to 9.0:
apt-get update
apt-get dist-upgrade

# Fetched 238MB in 7m24s (537kB/s)

# Now you are at redhat 9.0. I did a up2date just for sake
# of mind. This will proceed to upgrade your kernel ... on my
# dual xeons, I ended up with kernel-smp-2.4.20-19.9.i686
up2date -uv

# Now some misc stuff I did to make sure everything was okay:
lilo -v -v
sync

# If you have problems with lilo and it being unable to find
# /boot/messages, just create the file and enter random
# text in there.