[comp.sys.apollo] marginal installs on Apollos

leland@DRAGONFLY.WRI.COM (03/07/91)

Marc Hall (of Los Angeles Dept. of Water & Power) recently posted:

>>  If you have installed OS 10.3 without ansi support and wish to install
>>the Domain/C 6.8 with ansi support you must reinstall OS 10.3 with ansi
>>support.
>>
>>  Domain OS 10.3 shipped several weeks before the compiler.
>>
>>  The HP/Apollo 800 support confirms this and offers no workarounds.
>>
>>  I have to reinstall 11 nodes, whats your damage ?

The reason why the 800 folks don't give you a workaround is because
there is no supported workaround. There is, however, a rather simple
*unsupported* workaround.

HP support people, close your eyes! :)

The general problem is this: you need to install a componant of the
OS without going through a full reinstall. Here is a procedure for
doing so.

This procedure assumes that you kept your AA on line.

First, you need to find your table of contents file for your OS
tape.

% cd /install/toc
% ls
toc.apollo.CC0138.c	toc.apollo.PG0108.c
toc.apollo.CC0148.c	toc.apollo.PK0139.c
toc.apollo.DX0106.c	toc.apollo.PK0147.c
toc.apollo.GM0128.c	toc.apollo.ST0141.c
toc.apollo.NF0117.c	toc.apollo.ST0157.c
toc.apollo.OP0124.c


Ok...this is a list of all tapes from all products read on the
node. OS tapes are named STnnnn, where nnnn is the tape number. If
you have read lots of tapes, you can always rbak -index -f 1 -dev ct
the tape and find the name of this file.

In my case, I know it is toc.apollo.ST0157.c. You read the file
and find the component that you need. Here is an excerpt from
my toc file:

---------------------------------------------------------
Label  apollo          ST0157         C
Ident  018848   00
Ident  CRTG_std_sfw_1
Ident  std_sfw        10.3        57
Vers   1.1
Tools  90/07/20 19:56:17  1  1  ri.apollo.os.v.10.3
Prod  ri.apollo.os.v.10.3  1  2  2316
Subcomp  /base_sysboot  1  3  10
Subcomp  /base_sysboot.m68k  1  4  16
Subcomp  /base_install_utils  1  5  722
Subcomp  /base_install  1  6  1266
Subcomp  /base_bscom_link  0  0  0
Subcomp  /base_bscom_open_dir  0  0  0
..
End
--------------------------------------------------------

The format of this file is quite simple. The first lines are used for
consistency checking.

Each subcomponent line has the format:

Subcomp <name> <tape number> <file number> <comp size (in 1kb blocks>

Now, some of the components are included with other components, and
so you might have to do a little hunting to find what you want.
This case is probably the worst I've ever seen since the ansi files
are scattered throughout the OS.

Lets see here...the release notes say I need include files, a new cpp,
cc, and ld. Also, a new crt0.o (which will be in an isp_ directory)
may be needed.

Include files are in /usr/ansi (tape 3, file # 18). I would check
the base /usr (tape 3, file # 1) or bsd_bsd_dir for the additional
files.

If you use this procedure, there are a few things you will have to
do yourself.

First of all, you will have to create any links or do any copies out
of the authorized area.

Secondly, you will have to verify proper file protections. It is my
understanding that files are stored on the tape with open acls, that
if you want to close the installation (which is basically turning
off p rights for world in the acl) you'll have to do that yourself.

Anyway, while this is a bit involved for the ansi support (the person
who suggested one install, noting the actions and developing a 
shell script has the right idea for a medium size installation), it
is very useful for situations where you have to recover one specific
file from a distribution tape, or viewing without loading parts of
the OS.

---------------------------------------------------------------------
                         |
Leland Ray               |  I didn't write it, I just compile it.
Wolfram Research, Inc.   |
(217) 398-0700           |