SEO

I'm trying to shift a systemm from an old hardware platform to a new
VMware installation, all clean and shiny with the latest patches. But
I'm remember some old comments about SCO licensses. In order to use
the full hardware capabilities, do I need to do any license
installation other than the basic server license and the developer
license I'm using for the system? The Skunkware published version of
'top' reports the 1 Gig of RAM accurately, and I haven't installed an
SMP license yet.

----- Original Message -----
From: "Nico Kadel-Garcia" <nkadel@gmail.com>
Newsgroups: comp.unix.sco.misc
To: <distro@jpr.com>
Sent: Thursday, April 10, 2008 3:35 AM
Subject: RAM/CPU licensing for SCO OpenServer under VMware


> I'm trying to shift a systemm from an old hardware platform to a new
> VMware installation, all clean and shiny with the latest patches. But
> I'm remember some old comments about SCO licensses. In order to use
> the full hardware capabilities, do I need to do any license
> installation other than the basic server license and the developer
> license I'm using for the system? The Skunkware published version of
> 'top' reports the 1 Gig of RAM accurately, and I haven't installed an
> SMP license yet.

If you are ever going to use smp, then you should install smp immediately after base install (before rs506a / rs507a)
Otherwise, you should reinstall just about every patch after you install smp, because many of the patches updated smp.
The same is true for the native development system.
Install order should be (today, for 5.0.7):
1 base OS (using this updated iso image ftp://ftp.sco.com/pub/openserver5/50...Jun05_1800.iso)
2 smp
3 devsys
4 touch /tmp/gnutools.nocheck
5 gnutools
6 mp5
7 oss672a
8 oss674a
9 wd_3.0

and then whatever else may apply to your particular case from this list
http://www.sco.com/support/update/do...sr507list.html
Bearing in mind that any patch or driver whose date is earlier than that of mp5, has probably been included in and superceded by mp5.

The gnutools oddness above is because mp5 includes gwxlibs, and gwxlibs slightly overlaps gnutools.
The files that are in both gnutools and gwxlibs are much newer in gwxlibs, and so you want to install gnutools before gwxlibs. The touch command works around the problem that gnutools will complain that you need gwxlibs first. You _could_ install an older gwxlibs first, then gnutools, then the current gwxlibs, but there is no need.

And today (this wasn't true when 5.0.7 first came out so many existing boxes won't have done this, and that wasn't a fault at the time) but today, you should always install smp, unlicensed, because starting with mp4 or mp5 you now get multi-core and hyperthreading support for free for a single cpu, but it needs smp to actually do it. So install smp, don't license it, then when mp5 gets installed it updates smp and makes it partially active. That is, if you have a single dual or quad core cpu, you get to use all the cores now, which used to require buying smp.

I beleive this is only true for 5.0.7. (and 6.0.x and unixware but who cares about those?
Well, except I see now there is samba 3.0.24 for osr6 and unixware only, and that is the first and only so-far version of samba on any sco product that is new enough to fully work with Vista.

--
Brian K. White brian@aljex.com http://www.myspace.com/KEYofR
+++++[>+++[>+++++>+++++++<<-]<-]>>+.>.+++++.+++++++.-.[>+<---]>++.
filePro BBx Linux SCO FreeBSD #callahans Satriani Filk!