A.P. Lawrence

custom installation

If this isn't exactly what you wanted, please try our Search (there's a LOT of techy and non-techy stuff here about Linux, Unix, Mac OS X and just computers in general!):

From: Bela Lubkin <belal@caldera.com>
Subject: Re: Fresh install of OSR506
Date: Sun, 4 Nov 2001 03:05:28 GMT References: <5.0.0.25.2.20011103152223.041896e0@scogr1.cscc.maximus.com> <5.0.0.25.2.20011103154534.02227440@scogr1.cscc.maximus.com>

Ken Wolff wrote:

> At 08:30 PM 11/3/01 +0000, Ken Wolff wrote:
> >We're performing a fresh install of 506 this weekend and I want to make 
> >sure I'm applying supplements in the correct order.  I've looked through 
> >the rs506a.txt file and the various oss*.ltr files and I have not seen any 
> >specific order in which these should be installed.  Here's the path I plan 
> >on taking at this point.
> >
> >- Install 506 (including TCP/IP and all network support)
> >- Install SMP
[...]
> 
> As a followup, I just noticed that on the 506 CD from SCO there appears to 
> be 2 SMP versions.  One is at the "top" level and is SCO SMP Ver 1.1.1Ga 
> (which I have installed during my testing process).  The other is under SCO 
> Openserver Software and is SMP Support Ver 5.0.6j.  Anyone have an idea 
> which I should be using?

A simple, general rule: _NEVER_ install _ANYTHING_ off the CD from under
the "SCO OpenServer Software" branch.

The CD presents several views of the same software.  For instance, if
you went looking for "SCO Unix Operating System" [whatever its exact
name is], you would find it under SCO OpenServer Enterprise System,
SCO OpenServer Desktop System, SCO OpenServer Host System, as well as
under SCO OpenServer Software.  These multiple views contain the same
software, but different packaging details in order for them to install
under their respective marketing names.

Unfortunately, you can really screw up a system by trying to install the
right software from the wrong marketing-inspired branch of the install
CD.

The CD contains branches for all the different packaged products SCO
used to sell.  It also contains the generic "SCO OpenServer Software"
branch.  This is the branch that gets invoked by certain special-order
bundled packages.  Those packages are not available via retail or
distributor channels.  I believe they also have the property that once
they're installed, no other software can be installed on top of them
from the CD.  The license key data tells the CD which branch to use (in
this case, the "OpenServer Software" branch).  When you install a retail
product with an "Enterprise" or "Desktop" key, the install uses the
corresponding branch; you need to know, later, to install additional
components from the same branch.  For user interface purposes, the
generic "OpenServer Software" branch really shouldn't be visible at all
since it can never be used from within `custom`.  But there it sits,
waiting to trap you...

>Bela<

Enter your email address for automatic notification of new posts here
(be sure to whitelist 'feedburner.com' if you use spam filtering)

/Bofcusm/1077.html copyright 1997-2004 Bela Lubkin All Rights Reserved

Have you tried Searching this site?

Unix/Linux/Mac OS X support by phone, email or on-site: Support Rates

This is a Unix/Linux resource website. It contains technical articles about Unix, Linux and general computing related subjects, opinion, news, help files, how-to's, tutorials and more. We appreciate comments and article submissions.

Publishing your articles here