Also, you may setup sysname in your plan9.ini. For CPU servers we do that, so that the machines know at least their names even if we screw things up.
On 8/17/07, Francisco J Ballesteros <[EMAIL PROTECTED]> wrote: > AFAIK, /rc/bin/cpurc now calls > /cfg/$sysname/cpurc.local > for local setup at $sysname. > > Thus, if it's enough for you just to start several custom stuff at $sysname, > just create your > /cfg/$sysname/cpurc.local. > > But otherwise, just do what is more simple for your site and does the job. > We still keep a single /bin/cpurc for all our cpu severs and that works fine. > Only that we have to keep an eye on changes made to cpurc in sources just > in case we have to update ours. > > hth > > On 8/17/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > Geoff, > > > > thanks for your time. Probably I am a dummy, but I have tree files: > > > > /rc/bin/cpurc > > /rc/bin/cpurc.local > > /cfg/example/cpurc > > > > The /rc/bin/cpurc is more complete than /cfg/example/cpurc, and I use it > > other times > > to create the cpuserver. > > Probably is better to create a /cfg/example/cpurc and a > > /cfg/example/cpurc.local > > (this file do not exist) very complete, > > modify them and copy to /rc/bin/cpurc*. > > > > In short, I do not what to do, because if I edit the /cfg/example/cpurc and > > overwrite /rc/bin/cpurc, probably I will lost some data. > > > > In the other hand, in the wiki, you can read "dircp /cfg/example to > > /cfg/$sysname, > > and cd /cfg/$sysname and edit cpurc*" > > normally, the $sysname is empty (I do not setup it) and cpurc* is only > > cpurc, the > > cpurc.local is not in /cfg/example". > > > > Thanks. > > > > kix. > > > > >
