>>> "Chris" == Chris Smallhorne <[EMAIL PROTECTED]> writes:

[snip]

    Chris> Software requirements

    Chris>                  1.VMware host operating system
    Chris> requirements glibc2 to glibc6 (glibc1 does not work) Linux
    Chris> kernel 2.0.32 to 36 Linux kernel 2.2.0 and higher for SMP
    Chris> systems

    Chris>                    VMware will not run on systems that do
    Chris> not meet these requirements.

    Chris> Does this mean that I need to find a copy of kernel version
    Chris> 2.0.32 to 36, or should it work with 2.2.9-19mdk?  If I

It works with 2.2.9-19mdk. I've used it and I have only one CPU.
(I've also used it with 2.2.13-7 from the 6.1 release.)

    Chris> only need to go back to 2.2.9-19mdk, is it easier to do an
    Chris> "upgrade" install to go back to this kernel version, or
    Chris> won't this work and will I be stuck with doing an install
    Chris> from scratch?  I don't think I made a backup of the old
    Chris> kernel - if I did, I don't know where I put it.  Is there
    Chris> any way to find out?

Install or upgrade?

from man rpm:

      rpm -U [install-options] <package_file>+

       This  upgrades or installs the package currently installed
       to the version in the  new  RPM.   This  is  the  same  as
       install,  except  all  other  version  of  the package are
       removed from the system.

Since upgrade removes other versions of the package, you want install.

BUT: ***** watch out for symlinks in /boot and /lib/modules ******

You ought to rm the symlinks, so when you install, the existing
vmlinuz, module-info, and System.map in /boot and /lib/modules isn't
overwritten.

Where's your old kernel (was it -19?)?  It ought to be in /boot, if it
wasn't overwritten when you put in -27

What does ls /boot/ show?  Here is mine:

$ls /boot/
System.map@                 bzImage                  os2_d.b
System.map-2.2.13-5mdk      chain.b                  vmlinuz@
System.map-2.2.13-5mdkBOOT  core                     vmlinuz-2.2.13-5mdk
System.map-2.2.13-7mdk      initrd-2.2.9-19mdk.img   vmlinuz-2.2.13-5mdkBOOT
System.map-2.2.9-27mdk      map                      vmlinuz-2.2.13-7mdk
System.map-2.2.9-27mdkfb    module-info@             vmlinuz-2.2.9-27mdk
boot.0300                   module-info-2.2.13-5mdk  vmlinuz-2.2.9-27mdkfb
boot.0341                   module-info-2.2.13-7mdk
boot.b                      module-info-2.2.9-27mdk
$

The symlinks are to the 2.2.13-7 stuff.

    Chris> BTW, what does the -19mdk mean?

Probably that it's from a Mandrake distribution.

-- 
Mike Fieschko, West Orange, NJ, USA
X-Mailer: XEmacs 21.1, VM 6.71 and random-sig.el
X-Face header is me! http://www.cs.indiana.edu/picons/ftp/faq.html
Kernel 2.2.13-7mdk mailto:[EMAIL PROTECTED]
http://www.viconet.com/fieschko/home.htm
Sep 21 St Matthew 
"Civilization has run on ahead of the soul of man, and is producing
faster than he can think and give thanks." - [G.K. Chesterton, in
Daily News, 2/21/02]

Reply via email to