From mboxrd@z Thu Jan  1 00:00:00 1970
From: Adrian Tritschler <ajft@ajft.org>
To: 9fans@cse.psu.edu
Message-id: <3F8CF3BF.5040306@ajft.org>
MIME-version: 1.0
Content-type: text/plain; format=flowed; charset=ISO-8859-1
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5)
 Gecko/20031008 Thunderbird/0.3
Subject: [9fans] Machine-specific cpurc customisation?
Date: Wed, 15 Oct 2003 17:14:07 +1000
Content-Transfer-Encoding: quoted-printable
Topicbox-Message-UUID: 6f300216-eacc-11e9-9e20-41e7f4b1d025

I was looking at the way I've set up my *enormous* (two PC) plan9=20
network and thinking about adding changes to /rc/bin/cpurc. Since termrc=20
includes termrc.local (if it exists), should cpurc include cpurc.local?

This would make it possible to have things like:

/rc/bin/cpurc

|...
|if (test -e /rc/bin/cpurc.local)
|	. /rc/bin/cpurc.local
|...

/rc/bin/cpurc.local

|...
|#global site-specific stuff, eg
|facedom=3Dmicrosoft.con
|if (test -e /rc/bin/cpurc.$sysname)
|	. /rc/bin/cpurc.$sysname
|...

/rc/bin/cpurc.machine1

|# Machine-specific items for CPU/Auth machine "machine1"
|# for example
|auth/secstored >> /sys/log/secstored >[2=3D1] &
|#

The only problem I can see so far is that termrc.local is called before=20
$sysname is available, but initialising the network in termrc.local=20
should solve that.

If not, what other suggestions would people make on machine-specific=20
configs, given that I'd like to be able to keep doing replica/pull from=20
sources to stay up to date.

thanks,
	Adrian

---------------------------------------------------------------
Adrian Tritschler                          mailto:ajft@ajft.org
Latitude 38=B0S, Longitude 145=B0E, Altitude 50m,      Shoe size 44
---------------------------------------------------------------