From: Adrian Tritschler <ajft@ajft.org>
To: 9fans@cse.psu.edu
Subject: [9fans] Machine-specific cpurc customisation?
Date: Wed, 15 Oct 2003 17:14:07 +1000 [thread overview]
Message-ID: <3F8CF3BF.5040306@ajft.org> (raw)
I was looking at the way I've set up my *enormous* (two PC) plan9
network and thinking about adding changes to /rc/bin/cpurc. Since termrc
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=microsoft.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=1] &
|#
The only problem I can see so far is that termrc.local is called before
$sysname is available, but initialising the network in termrc.local
should solve that.
If not, what other suggestions would people make on machine-specific
configs, given that I'd like to be able to keep doing replica/pull from
sources to stay up to date.
thanks,
Adrian
---------------------------------------------------------------
Adrian Tritschler mailto:ajft@ajft.org
Latitude 38°S, Longitude 145°E, Altitude 50m, Shoe size 44
---------------------------------------------------------------
next reply other threads:[~2003-10-15 7:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-15 7:14 Adrian Tritschler [this message]
2003-10-15 9:51 ` Fco.J.Ballesteros
2003-10-15 10:13 ` Charles Forsyth
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3F8CF3BF.5040306@ajft.org \
--to=ajft@ajft.org \
--cc=9fans@cse.psu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).