How do I upgrade Redhat 4.2 -> 5.1 via Ftp

How do I upgrade Redhat 4.2 -> 5.1 via Ftp

Post by mr. redha » Wed, 15 Jul 1998 04:00:00

I am trying to upgrade my linux system via ftp.  I used the boot.img and
supp.img that came with my redhat 4.1 cd to do the upgrade.  But when I
get to the ftp menu and enter the ftp server and
dir(.../redhat/redhat-5.1/i386) nothing happens.  Some meesage pops up
so fast that I can't see it.  Then I'm sent back to the ftp menu.

Please help



1. Upgrading from Redhat 4.2 to 5.1 remotely - suggestions??

I'm considering upgrading my system from Redhat 4.2 to 5.1.  The version of
4.2 is vanilla - no recompiled kernel, no additional packages - it's
straight off the FTP site from last June.

Here's the hitch - the machine is in a secure server room which I don't
have routine access to - it's a bit of a haul over there, and I have to
coordinate with the site manager to get in the room.  So I want to do the
upgrade remotely, telnetting in from home, gaining root access vi "su",
and proceeding with the upgrade.

Is this doable?  Reasonable?

I want to do this in such a way as to minimize the chances of crashing
the system - I'd like to avoid having the system off-line for hours or
more until I get access.  The way I'd like to proceed is:

1) Replace the 2.0.30 kernel with 2.0.34-pre using rpm -U to
   (Note - there are no IDE hard drives on the system, although the floppy
    and CD are on the IDE chain.  The SCSI Drivers and ethernet card are
    handled as modules ...

2) Begin replacing system packages by manually running rpm -U in a
   reasonable order - hopefully there are no circular dependancies in the
   RPMS files.
   (Question:  in order for "-U" to uninstall previous versions, do I
   need the *old* .rpm file from v4.2 on disk as well as the v5.1 version,
   or is the package information available without the old .rpm file present?)

3) reboot (shutdown -r now) and hopefully have the new v5.1 system come up.

The system is used as a web server and telnet host for about a half dozen
users.  We don't use X-Windows (yet); there are no dial-in lines; if I
can get it to a state where the system boots and telnet, mail, ftp, and
httpd are running, I'm in good shape - I can bang on the other packages

So, am I nuts, or is this a reasonable way to proceed.  (I'm also concerned
about lib5/lib6/glibc conflicts I've seen talkes about - I want to know that
when I reboot remotely, I'll get a system back up that I can telnet back into).

Many thanks in advance.

Mike Heney

2. Gone for a couple of weeks

3. RedHat 5.1 upgrade blew out 4.2 and MBR

4. Lost Return key on new Linux ncurses recompile?

5. RedHat 4.2 install via FTP + updated .rpm files

6. avi player

7. RedHat 4.2 .rpm updates and install via FTP

8. lp0 1 & 2 problem

9. NFS mount from AIX 4.2 to SunOS 5.1 fails after upgrade

10. Redhat upgrade 4.1 --> 4.2

11. Upgrade problem: RedHat 4.2 -> 5.0

12. Floppyless Upgrade from 4.2 to 5.1

13. upgrade redhat 4.1 -> 4.2