Path: utzoo!mnetor!tmsoft!torsqnt!lethe!yunexus!ists!helios.physics.utoronto.ca!alchemy.chem.utoronto.ca!system
From: system@alchemy.chem.utoronto.ca (System Admin (Mike Peterson))
Newsgroups: comp.sys.apollo
Subject: Re: SR10.3
Keywords: 10.3
Message-ID: <1991Feb23.183821.17805@alchemy.chem.utoronto.ca>
Date: 23 Feb 91 18:38:21 GMT
References: <1991Feb23.025815.28527@ux1.cso.uiuc.edu>
Organization: University of Toronto Chemistry Department
Lines: 25

In article <1991Feb23.025815.28527@ux1.cso.uiuc.edu> chlg1043@uxa.cso.uiuc.edu (Christopher H Lee) writes:
>We are planning on bringing our network up to 10.3 in the
>near future.  Do any of you out there with experience updating
>have any helpful hints?  I hope this will be less painful than
>9.7 to 10.2 updates.

Hardly any pain at all, but as I outlined a few weeks ago, don't put SR10.3
on a DN2500 until the patch for the racing clock is available (April
sometime I was told, but I am running a version of it now, and the node
is now functional). If you start X Windows at boot time, be aware that
the options in /etc/rc and /etc/daemons have changed: /etc/daemons/Xapollo
now gets you X in DM-owns-root, and /etc/daemons/X gets you X in 
X-owns-root (this didn't exist before).

>Oh...and can 10.3 coexist with 10.2 nodes?  We would like
>to keep some of the nodes up and running (10.2) as we do the
>system updates.

Yes - just keep using the 'tcpd -c' option in /etc/rc.local on the
SR10.3 nodes until they're all at 10.3; then get rid of it and reboot
the whole network (at the same time :-) ).
-- 
Mike Peterson, System Administrator, U/Toronto Department of Chemistry
E-mail: system@alchemy.chem.utoronto.ca
Tel: (416) 978-7094                  Fax: (416) 978-8775


Brought to you by Super Global Mega Corp .com