Floppyless Upgrade from 4.2 to 5.1

Floppyless Upgrade from 4.2 to 5.1

Post by Ashwin Biha » Fri, 07 Aug 1998 04:00:00

Quote:> I have (don't ask why!) a machine here with a CDROM but no floppy (had to
> be or the other) which has RedHat 4.2 on it and running happily and have
> now purchased RH5.1 and want to upgrade. Is there any way to boot the CD or
> kickstart the upgrader direct from the cdrom itself ? And of course, in
> simple terms, how!

Simple, on the CD, go to the DOSUTILS directory and type AUTOBOOT and when
prompted, choose UPGRADE..Regards

|Ashwin Bihari                              University of Massachusetts Lowell|

|Primary   URL: http://welcome.to/linuxresource                               |
|Secondary URL: http://members.xoom.com/abihari                               |
| NOTE: The E-mail address on top has been mangled to stop Spam Bots..please  |
|       use the address in this box for replying.                             |


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

        One of my customers just upgraded an RS/6000 43P from
AIX 4.1 to 4.2.1.  Before the upgrade he was able to NFS mount
a filesystem on a Sparc 1+ (yeah, an oldy) running SunOS 5.1.  As
near has he can tell (he did a preservation upgrade on the AIX)
he has not changed any TCP/IP configuration on either side.

Here is what he receives on the AIX side:

mount: 1831-008 giving up on:
vmount: There is an input or output error.
NFS getattr failed for server mrd2100-gw: error 7 (RPC: Authentication

While on the Sun side he receives on the console:

NFS request from unprivileged port.
nfs_server: weak authentication

The /etc/filesystems entry on the AIX side is:

        dev             = "/soma"
        vfs             = nfs
        nodename        = mrd2100-gw
        mount           = false
        options         = fg,hard,intr
        account         = false

while on the Sun side it's filesystem is being shared with a
/etc/dfs/dfstab entry of:

share -F nfs -orw=omronaix,root=omronaix /soma

He has tried changing parameters like hard/soft, intr/nointr, secure
vers=, proto=, but none of these has changed the symptom.

I went looking through IBMLink but didn't find any PTF about this
specifically.  We are going to pull down U450645 and see if that
helps, because it is pointed to by about a dozen APARs, but that is
just a blind guess.  We also found out that bos.net.tcp.client is
at, but bos.net.nfs.client is at, and it probably
should be at also.  

I also am going to try Sun patch 100884-27, the SunOS 5.1 NFS jumbo
patch, although I am not sure this will really help.  It hasn't been
updated since 1994.

Do any of you have any suggestions?

Thanks in advance,

John Schneider


* Lowery Systems, Inc.  ***********************************************
* 275 Axminister        * Disclaimer: Opinions expressed here are mine*
* Fenton, MO 63026      * and mine alone.  My company is off the hook.*

2. Remove files before a certain date

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

4. HELP!!! I cant explain these few loglines!

5. How do I upgrade Redhat 4.2 -> 5.1 via Ftp

6. Httpd Error.

7. Upgrade 4.2 to 5.1 or 5.2

8. Compiling PGP 2.6 for x86 Solaris

9. Upgrade...4.2 to 5.1(2)

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

11. RedHat 5.1 upgrade blew out 4.2 and MBR

12. RedHat: 4.2 vs 5.1

13. Huge network performance loss from RedHat 4.2 to 5.1