From: "Russ Cox" <rsc@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] my cpu-in-vmware problem: it's weird :-)
Date: Wed, 23 Apr 2003 11:12:09 -0400 [thread overview]
Message-ID: <f8fe6faf7127a3fd7f0f51d4ee13b012@plan9.bell-labs.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0304222130190.26835-100000@maxroach.lanl.gov>
> Anyway, with that vmware vmnet1 dhcpd out of the say, things on the cpu
> server work better, except it still comes up with the wrong sysname -- p9
> instead of cpu2. Right IP address, I can cpu -h cpu2, but the cpu server
> has the wrong sysname.
you said before that you were setting sysname=p9 in your
termrc or cpurc. that might have something to do with it.
next prev parent reply other threads:[~2003-04-23 15:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-23 3:49 ron minnich
2003-04-23 12:52 ` David Presotto
2003-04-23 17:08 ` Micah Stetson
2003-04-23 17:20 ` David Presotto
2003-04-30 0:24 ` Boyd Roberts
2003-04-30 0:26 ` Boyd Roberts
2003-04-23 15:12 ` Russ Cox [this message]
2003-04-23 16:11 ` ron minnich
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=f8fe6faf7127a3fd7f0f51d4ee13b012@plan9.bell-labs.com \
--to=rsc@plan9.bell-labs.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).