9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Francisco J Ballesteros" <nemo@lsub.org>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] Re: CPU Server
Date: Fri, 17 Aug 2007 13:54:02 +0200	[thread overview]
Message-ID: <8ccc8ba40708170454u4856b33dj1080ab73660ce6cd@mail.gmail.com> (raw)
In-Reply-To: <8ccc8ba40708170452g4f6fe55aq700a8ba03c971e7b@mail.gmail.com>

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 <nemo@lsub.org> 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, kix@kix.es <kix@kix.es> 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.
> >
> >
>


  reply	other threads:[~2007-08-17 11:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-17 11:03 kix
2007-08-17 11:52 ` Francisco J Ballesteros
2007-08-17 11:54   ` Francisco J Ballesteros [this message]
2007-08-17 18:10 ` geoff
2007-08-17 22:40   ` kix

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=8ccc8ba40708170454u4856b33dj1080ab73660ce6cd@mail.gmail.com \
    --to=nemo@lsub.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).