[530] in Release_7.7_team
Athena 8.0 Beta Test
daemon@ATHENA.MIT.EDU (release-team@MIT.EDU)
Mon May 13 19:12:14 1996
Date: Mon, 13 May 96 19:12:08 -0400
To: release-team@MIT.EDU
From: release-team@MIT.EDU
The first public release of Athena Release 8.0 is available for Sun
workstations in the beta cluster. This round of testing will
hereafter be refered to as "beta test". Release 8.0 supports Suns and
SGIs only; SGIs in the beta cluster will be updating to Release 8.0
later in May.
If your Sun is configured to update automatically, it will still not
take the first 8.0 release automatically. You must follow the
instructions for a manual update when you update to 8.0 initially,
and thereafter your machine will automatically take the updates to
8.0 (if so configured).
The following machine(s) are in the beta cluster, and you may
update them whenever you wish (see section IV, below):
shadowfax
I. Reporting Bugs
Report problems in the new release to testers@mit.edu.
II. Questions
If you have questions about taking the new release, send them
to the release team (release-team@mit).
III. Release Changes
The following features are included in this release:
Solaris
* Solaris 2.4 with AFS 3.4a
* Emacs 19.30 is the default
* Emacs 18 is available as a separate command
* /usr/athena/bin/cc now points to sun cc
* Transcript 4.1
* MIME support has been built into MH but is turned off in
the default environment.
IV. Updating a workstation manually
1) Login as root on the console.
On a Sun:
Shutdown X, by hitting CTRL-P on the machine. Then login as
"root" (the default password is "drroot", but I really hope
that your root password is different).
2) Shutdown timesharing
Sun users
-----------------------------
Type:
/bin/athena/detach -h -n -a
/bin/athena/attach -h -n beta-sun24sys
3) Type:
/srvd/update_ws reactivate
This may ask you to press <RETURN> or prompt you for other information.
The prompts should be intelligible (you've no doubt gone through all
these questions during previous updates; there's nothing radically new
in this update).
4) After the update says it has updated the version number and another
# prompt has appeared, type:
/etc/reboot
Sun users
---------
During the reboot process you may see several error messages,
all of which can be ignored. They include the following:
dm: X failed to be come ready
Unable to start X, doing console login instead
Also, the /usr file system does not fsck cleanly.
