[232] in Release_7.7_team
Athena 7.7 beta testing starting tomorrow, Wed Dec 28
daemon@ATHENA.MIT.EDU (salemme@MIT.EDU)
Tue Dec 27 18:35:47 1994
From: salemme@MIT.EDU
Date: Tue, 27 Dec 94 18:35:17 -0500
To: bert@MIT.EDU, bwmelans@MIT.EDU, cfields@MIT.EDU, coc@MIT.EDU, dkk@MIT.EDU,
dryfoo@MIT.EDU, ebarrett@MIT.EDU, edward@MIT.EDU, f_l@MIT.EDU,
ghudson@MIT.EDU, jawetzel@MIT.EDU, jdaly@MIT.EDU, jweiss@MIT.EDU,
kcunning@MIT.EDU, kim@MIT.EDU, mhbraun@MIT.EDU, miki@MIT.EDU,
op@MIT.EDU, probe@MIT.EDU, sipb-staff@MIT.EDU, tytso@MIT.EDU,
vrt@MIT.EDU, wchuang@MIT.EDU, wdc@MIT.EDU
Cc: release-77@MIT.EDU, testers@MIT.EDU
On the night of Wed Dec 28, Athena Patch Release 7.7 will be available
for Athena Suns, DECstations and RS/6000s in the "beta" clusters. I am
sending this mail to all the contact people for beta-cluster workstations
to let you know how to update your workstation, where to get information
about the release you'll be using, and how to report problems. This mail
is long and detailed, is based on mail sent out for previous releases, and
hopefully it is correct and complete. Please let me know if there are any
errors or omissions in this message. Thank you for participating in the
beta phase of the release process!
Anne
1) How to update your workstation
=================================
If you are the owner of a "beta-test" workstation, you may now take the
update. First, check that your workstation is in a beta cluster:
athena% hesinfo <hostname> cluster | grep syslib
athena% hesinfo <syslib> filsys
Example:
athena% hesinfo ki cluster | grep syslib
syslib beta-rssys
athena% hesinfo beta-rssys filsys
AFS /afs/dev.mit.edu/system/@sys/srvd.77 n /srvd
^^^ ^^
These indicate the workstation is getting its pack from the
dev cell, which means the workstation is in a beta cluster.
Next, check to see if your workstation has already updated:
athena% machtype -P (check the pack version)
athena% machtype -L (check the version on your ws)
If your workstation has already updated, you can skip the rest of this section.
If your workstation is in a beta cluster and it hasn't taken the update
automatically, here is how to update it manually:
0) Be aware of any changes you've made on the workstation's disk, so
you can make sure your changes survive the update.
1) Login as root on the console, not using xlogin.
On a Sun or DECstation:
Shutdown X, using CTRL-P at the Xlogin, then login as root at
the "login: " prompt (default password is mrroot).
On an RS/6000:
Hit ALT-ACT to switch to the "console" hft. Then login as
root (the default password is mrroot).
2) Ensure the right pack is attached.
Sun users
---------
Type:
/bin/athena/detach -h -n -a
/bin/athena/attach -h -n -a beta-sun4sys
DECstation users
----------------
Type:
/bin/athena/detach -h -n -a
/bin/athena/attach -h -n beta-dmusys
/etc/shutdown now
It will take about 30 seconds for the machine to shutdown. After
30 seconds, you will see a warning message of the form:
WARNING: Something is hung (wont die); ps axl advised
Ignore it.
You should now see a # prompt. Press <RETURN> and make sure a
new # prompt appears on the next line. If it appears on the
same line, typing
/usr/ucb/reset (which will not appear in this situation)
will correct the problem. This problem has been most evident
if you force a shutdown while X is running (ie. not following
the directions in step 1).
RISC/6000 users
---------------
Type:
/bin/athena/detach -h -n -a
/bin/athena/attach -h -n -a beta-rssys
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:
On a Sun: reboot
On a DECstation or RS/6000: /etc/reboot
2. Problems Updating?
=====================
If you have any problems with updating a beta test machine, contact
Release Engineering <rel-eng@mit.edu> after verifying that you followed
the above instructions.
3. What's in the Release? or What needs Testing?
================================================
If you're unsure just what is included in the release or what should be
tested, check out the files in the "release77" locker in the January95
directory. There's a description of each major release item there along
with a brief list of particular things we know need testing. There's also
a file called WhatShouldRun which is a summary of all the major pieces of
software which should be working on a good Athena workstation. Feel
free to send results of testing, especially things which actually work
to release-77@mit.
Additional information is in the release-77 discuss meeting (on menelaus:
/usr/spool/discuss/release-77), and Mike Barker is maintaining a web page
for the status of the release (use your favorite web browser and open the
local file /afs/athena.mit.edu/user/m/b/mbarker/www/status0195.html).
4. Reporting Bugs
=================
Bugs and problems with the release should be sent to <testers@mit.edu>.
Enjoy, and happy testing!
