dbfunk@ICAEN.UIOWA.EDU (David B. Funk) (03/28/89)
Does anybody know what the deal is with the install tool "fix_10_1_ri"? It wasn't on my sr10.1 release tapes, it just magically appeared when I loaded the sr10.1 compilers into my AA. There is nothing in any of the release notes that mentions it. There is a cryptic help file for it that says "corrects the version number in the ri.apollo.os.v.10.1 release index in the Authorized Area specified by the user". There is no mention of why you need to fix it, or if you need to go back and reinstall sr10.1 after fixing it. What happens if you do an sr10.1 install with out fixing it first? I've been having a bunch of install problems and wonder if they are related. Has anybody else been having problems with their sr10.1 installs? Dave Funk
lnz@LUCID.COM (Leonard N. Zubkoff) (03/28/89)
Dave, Here's the situation as I understand it. When SR10.1 was released, the release number stored in the release index was 10.0 rather than 10.1. Now this doesn't cause any problems until you try to install additional software that requires 10.1; if you were to try to install something that depends on 10.1, the installation would fail since the prerequisite is not installed. So what running fix_10_1_ri does is to bash the 10.0 stored in the SR10.1 release index into 10.1 as it should be; there is no need for any re-installation. Just bash the release index once and you're golden. Leonard
aaron@apollo.COM (Aaron Sawyer) (03/29/89)
In <8903280242.AA00386@icaen.uiowa.edu>, dbfunk@ICAEN.UIOWA.EDU (David B. Funk) writes: > Does anybody know what the deal is with the install tool "fix_10_1_ri"? Ahem. > It wasn't on my sr10.1 release tapes, it just magically appeared when > I loaded the sr10.1 compilers into my AA. There is nothing in any of > the release notes that mentions it. There is a cryptic help file for > it that says "corrects the version number in the ri.apollo.os.v.10.1 > release index in the Authorized Area specified by the user". > There is no mention of why you need to fix it, or if you need to go back > and reinstall sr10.1 after fixing it. What happens if you do an sr10.1 > install with out fixing it first? After Domain/OS sr10.1 shipped, we discovered that the release index misidentified itself as being sr10.0. This did/does not affect the installation of sr10.1 Domain/OS itself. Optional software products (like compilers) depend on the version of the OS installed; the baseline file describes what is actually installed on the node, and the release index has other information that is used by the install tool. If there is a conflict (such as which version of the OS is present), the release index overrides the baseline file. This causes problems. The fix_10_1_ri tool does what its name implies (and the cryptic help file states). Given the pathname of the Authorized Area where the install tree and the product subtrees reside, it will find and fix the Domain/OS sr10.1 release index. If the release index has already been fixed, no harm is done. If the tool can't find the sr10.1 OS release index, no harm is done, though the tool may complain. The MINST (Media INStall) tool (versions 1.14 and greater) will call fix_10_1_ri quietly to guarantee the sr10.1 release index is corrected. To repeat, the install of Domain/OS sr10.1 is not affected by the fix or its lack, only optional software products dependent on sr10.1. > I've been having a bunch of install problems and wonder if they are > related. Has anybody else been having problems with their sr10.1 > installs? They could be related. I won't presume to speak for others. :-) I hope this helps. -- Aaron Sawyer USPS: Apollo Computer, 330 Billerica Rd., Chelmsford MA. 01824 MY OPINIONS! Internet: aaron@apollo.com (preferred) cha-02-rd UUCP: ...{decwrl!decvax, mit-eddie, attunix}!apollo!aaron (Copyright 1988 by author. All rights reserved. Free redistribution allowed.)