[118] in testers

home help back first fref pref prev next nref lref last post

6.3B ready for testing

daemon@ATHENA.MIT.EDU (daemon@ATHENA.MIT.EDU)
Thu Jul 20 16:46:05 1989

From: <probe@ATHENA.MIT.EDU>
Date: Thu, 20 Jul 89 16:42:57 -0400
To: testers-announce@ATHENA.MIT.EDU
Cc: sysdev@ATHENA.MIT.EDU
Reply-To: Richard Basch   <probe@ATHENA.MIT.EDU>

6.3B is available for testing and comment.  The update can be done from
AFS or from NFS, as described below.  If you are using NFS, you MUST
HAVE YOUR WORKSTATION REGISTERED AS A TESTER MACHINE; my previous
message to sysdev neglected to mention this.


To update:

If you are using the AFS testers packs for system libraries:

	- Login as root

	- Type:
		/srvd/bin/fs checkbackups
		/etc/shutdown now
		/srvd/update_ws
		/etc/reboot



If you are using NFS system packs:

	- CTRL-P login as root while the machine is DEACTIVATED

	- On a VAX, type:
		attach -h -n bldge40test-vs{sys,usr}-63b

	  On an RT, type:
		attach -h -n bldge40test-rt{sys,usr}-63b

	- Type:
		/etc/shutdown now
		/srvd/update_ws
		/etc/reboot



That is all there is to the update procedure.

If you wish to use AFS for system packs, read on... below is a policy
statement about the packs:

	- Manual pages on the AFS packs may not always be "formatted"
	  during the build of the release.  However, once the release
	  is announced, as it was above, any such problems should then
	  be reported.  It is usually known that some manual pages
	  have to have "catman" run over them; this is one of the last
	  steps that Release Engineering takes and thus a bug report
	  is not necessary while the building of the release is still
	  in progress.

	- During the build of the release, we will try to maintain an
	  entire suite of working software.  However, it is
	  occassionally not possible to do so, and during the building
	  of a release, if you encounter such problems, we would like
	  to hear about them; we do not know about all the things that
	  have gone wrong.

	- If there are any important notices that have to go out,
	  Zephyr messages will be transmitted on CLASS filsrv,
	  INSTANCE dot.mit.edu, RECIPIENT *.  It is your responsibility
	  to ensure you have a Zephyr subscription for this.  To add
	  a permanent subscription of this type, issue the following
	  command:

		zctl add filsrv dot.mit.edu \*

	- Occassionally, we have to re-release the read-only versions
	  of the packs.  This can cause some lossage since callbacks
	  are not performed on read-only volumes.  We will try to
	  announce all such releases over Zephyr, in advance.  However,
	  if you encounter problems of this nature, the following will
	  cure the problem:

		fs checkbackups

	- Disclaimer: Release Engineering reserves the right to change
	  this policy with or without notice at any given time.

-Richard

home help back first fref pref prev next nref lref last post