From: Joshua Wood <josh@utopian.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] a small error in /rc/bin/cpurc
Date: Mon, 5 Nov 2007 06:51:25 -0800 [thread overview]
Message-ID: <51BFD236-7562-4B0C-8473-A46B66A9D95F@utopian.net> (raw)
>
> But... unfortunately I don't have spare machine to run Plan9 native.
> I must run Plan9 in VMware player.
Well understood. We use a virtual machine product ourselves for
terminals and for testing.
While you might not utilize all the possibilities of network
management with Plan 9 because you're on vmware, I think my first
sentence still applies: It appears you've found a good reason to make
a little, one-time edit to your ndb file. If you're running as a cpu
server for any good reason, you're going to want to set at least a
few values in ndb to help the system work smoothly. Things like the
value of $cpu, authserver, and fileserver for terminals, for starters.
If you're running as a cpu server in a vm just to log in at the
console, not run any terminals or even drawterms, and you like
termrc, I'm not sure I understand why you're even running a cpu
kernel for your current purposes.
Lastly, I may be missing something, but it seems like if you make
your call to ip/ipconfig to get your DHCP-provided ip address in
either of /bin/cpurc.local or /cfg/$sysname/cpurc, you would achieve
your desired behavior when the /bin/cpurc invocation of ndb/dns -r
happens.
--
Josh
next reply other threads:[~2007-11-05 14:51 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-05 14:51 Joshua Wood [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-11-07 5:51 Joshua Wood
2007-11-07 3:02 Joshua Wood
2007-11-07 3:17 ` erik quanstrom
2007-11-05 12:59 Joshua Wood
2007-11-05 13:27 ` Antonin Vecera
2007-11-06 21:57 ` maht-9fans
2007-11-03 17:12 Antonin Vecera
2007-11-03 21:30 ` erik quanstrom
2007-11-04 11:18 ` Antonin Vecera
2007-11-04 16:48 ` erik quanstrom
2007-11-05 7:31 ` Antonin Vecera
2007-11-05 10:18 ` arisawa
2007-11-05 14:02 ` Antonin Vecera
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=51BFD236-7562-4B0C-8473-A46B66A9D95F@utopian.net \
--to=josh@utopian.net \
--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).