From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <f8fe6faf7127a3fd7f0f51d4ee13b012@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] my cpu-in-vmware problem: it's weird :-)
From: "Russ Cox" <rsc@plan9.bell-labs.com>
In-Reply-To: <Pine.LNX.4.44.0304222130190.26835-100000@maxroach.lanl.gov>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Date: Wed, 23 Apr 2003 11:12:09 -0400
Topicbox-Message-UUID: 9764f094-eacb-11e9-9e20-41e7f4b1d025

> 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.