[Search for users]
[Overall Top Noters]
[List of all Conferences]
[Download this site]
Title: | DECWINDOWS 26-JAN-89 to 29-NOV-90 |
Notice: | See 1639.0 for VMS V5.3 kit; 2043.0 for 5.4 IFT kit |
Moderator: | STAR::VATNE |
|
Created: | Mon Oct 30 1989 |
Last Modified: | Mon Dec 31 1990 |
Last Successful Update: | Fri Jun 06 1997 |
Number of topics: | 3726 |
Total number of notes: | 19516 |
1144.0. "Ultrix DECwindows UWS V2.2 EFT1 kit available" by CRLVMS::HALBERT (CRL, Trellis) Thu Jul 20 1989 10:22
[I saw this, and then lost it because it was posted in an obscure
place. It deserves a note of its own. --Dan]
================================================================================
Note 1019.9 VMS DECwindows V2 IFT1 Kit 9 of 9
SMURF::COUTU "He who will not risk, cannot win." 197 lines 19-JUL-1989 16:52
-< ULTRIX DECwindows V2 FT1 kit (UWS T2.2) >-
--------------------------------------------------------------------------------
This is the announcement of availability of the Field Test Kit for UWS T2.2
(you can call it ULTRIX DECwindows V2, same thing with different names.)
AVAILABILITY
External Field Test 1 of ULTRIX Workstation Software (UWS V2.2 EFT1)
is now available for your use. Note that this baselevel and all related
documentation and project information are COMPANY CONFIDENTIAL.
It is available internally for two audiences of users:
- those who are now running UWS T2.2-BL3 or T2.2-pre-FT1 and wish
to upgrade their system to the latest UWS V2.2 bits slated to ship
to external Field Test.
- users of the present UWS V2.1/V3.1 software who wish to upgrade
their system.
All the information contained here should not be distributed or shown
to non-Digital employees without the express written consent of UWS
product management (Jon Hall hall on sonora::).
CONTENTS
The software described in this memo and available by the below
means is not a complete UWS V2.2/ULTRIX-32 V3.1 kit. Only the UWS V2.2
bits can be obtained in this enet manner.
This baselevel contains all the basic functions that UWS Engineering
Development plans to ship in Version 2.2 (and V2.4) of UWS.
Requirement: To run this software you must be running
ULTRIX-32 V3.1, SDC version.
KIT LOCATION for ENET installation
These bits were last updated July 8 5PM PDT. If you retrived bits
prior to this date you will need to re-install this more current version.
EFT1 kits are located on gilroy in the standard place:
/kits/uwsft1/{max,vax}/kit
The uwsinstall script in /a13c/uws/kits/ft1 will install the bits
for you if you don't want to grab them.
NOTE
To run this software you should be running ULTRIX-32 V3.1 SDC version.
If you are not, you will need to edit your /etc/ttys file to use
login.patch as opposed to login.
DOCUMENTATION
The release notes and associated documentation describing EFT1 and its
installation are located in these directories:
EFT1 Documents* ravine:/usr/staff/r0/maler/uws/fieldtest
release notes
other DWs docs
DPS Documents gilroy /a13c/uws/phases/v22/phase2
Preliminary SPD gilroy /a13c/uws/phases/v22/phase2
UWS Software Change gilroy /a13c/uws/phases/v22/phase2
Submit forms
(* Installation Notes intended for external FT may not apply to the enet kit)
INSTALLATION
The UWS V2.2 EFT1 kit files are maintained in setld-format for easy use
by the Ultrix ris and dms utilities.
To obtain and install the EFT1 subsets, copy the "uwsinstall" script
from GILROY and run it. You may also intervene manually on your own
initiative.
"UWS" is used to refer to both the VAX UWS subsets and the RISC UDW subsets.
INITIAL SETUP
1. Preparation: become the root user with "su" and change your current
directory to a partition with adequate free disk space. To acquire
adequate space, you may choose to delete the old subsets prior to EFT1
installation.
On disk space: the full VAX distribution requires 20 megabytes; the full
RISC distribution requires 45mb. These figures more than double to do
a standalone installation.
2. Copy uwsinstall script from gilroy
Type:
dcp gilroy::/a13c/uws/kits/ft1/uwsinstall
chmod u+x uwsinstall
3. Run uwsinstall
Type:
./uwsinstall
and answer the questions.
You may copy the mandatory subsets, all the subsets, or individually
chosen subsets. You may also choose to install immediately or defer
installation to a later time. If you have ris or dms servers and
clients, you must add the subsets to your own ris or dms configuration.
4. Clean up afterwards.
Delete the subsets in the current directory unless you have determined
you will need them later.
*IMPORTANT INSTALLATION NOTES*
Once the subsets have been copied to your machine, there are several
issues to keep in mind.
Previously existing UWS subsets which are going to be overwritten,
(in particular, the fonts) should be deleted with "/etc/setld -d".
If fatal verification errors occur, check the subsets to see if
they've copied correctly.
Consult the ULTRIX documentation set for further information
on the ris, dms, and setld utilities.
Once again, remember to be sure to reboot your systems after completing
the installation.
QAR SYSTEM
Please use the ULTRIX QAR database, UWS_QAR, for reporting quality problems
with this baselevel.
This QAR system is set up on GORGE (in ZKO) to allow you to report
all internal problems you have with UWS software. Each DRI should already have
an account on this machine. Or you may use the general account,
Name: QAR_INTERNAL
Password: QAR
Contact the Account manager: Eileen Horner decvax::eileen with any questions.
When you enter a QAR, the system will ask you a series of questions. Please
be sure to explicitly state you are reporting problems against product
version V2.2 EFT1.
PROBLEM REPORTS
Unsupported software: there are a number of software product components
which continue, as in UWS V2.1, to be unsupported in UWS V2.2. QARs will not
be honored for these components and will be automatically closed with a
statement of non-support provided. A statement of support is contained both
in the Release Notes and in the preliminary SPD.
INSTALLATION & PROCEDURAL PROBLEMS
Please contact, in this order: Rich Hyde 415-853-6671 sonora::hyde
Tom Patterson 415-853-6731 sonora::tp
CONFIDENTIALITY
Once again remember, this project, baselevel kit, and memo are COMPANY
CONFIDENTIAL. Do not discuss the contents of this BL with people
outside the company.
T.R | Title | User | Personal Name | Date | Lines
|
---|