From: Skip Tavakkolian <fst@real.com>
To: 9fans@cse.psu.edu, 9fans@cse.psu.edu
Subject: Re: [9fans] multiple cpu servers and /rc/bin/cpurc pickle
Date: Wed, 10 Oct 2001 00:16:53 -0700 [thread overview]
Message-ID: <3.0.5.32.20011010001653.01747508@mail.real.com> (raw)
In-Reply-To: <20011010060900.D3FFF199DD@mail.cse.psu.edu>
Thanks.
This also seems to work. I first try ipconfig without params, and after, if
/net/ndb doesn't exist or is zero length, I run it with hand coded params.
Since dhcpd is only run on the main cpu/auth, I think I'm safe with this
approach.
At 02:08 AM 10/10/2001 -0400, Russ Cox wrote:
>Set sysname in plan9.ini and then
>switch($sysname). There are other ways,
>like look yourself up in the cs database
>by ethernet address to set sysname.
>The plan9.ini is simplest for small
>configurations, the cs one is probably
>best in general.
>
>
next prev parent reply other threads:[~2001-10-10 7:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-10 6:08 Russ Cox
2001-10-10 7:16 ` Skip Tavakkolian [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-10-10 5:04 Skip Tavakkolian
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=3.0.5.32.20011010001653.01747508@mail.real.com \
--to=fst@real.com \
--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).