From: Jeff Sickel <jas@corpus-callosum.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Stupid question...
Date: Sat, 15 Nov 2008 11:12:22 -0600 [thread overview]
Message-ID: <A20E10A1-7AAD-43F0-8DC2-385102F156E5@corpus-callosum.com> (raw)
In-Reply-To: <a4e6962a0811150855n5854c9at76c1597cfdba9831@mail.gmail.com>
On Nov 15, 2008, at 10:55 AM, Eric Van Hensbergen wrote:
> Haven't run into this scenario before myself, so I'm not quite sure
> how to get out of it.
>
> I just installed a new virtual standalone CPU server on my home
> machine. I followed the instructions on the wiki for standalone
> cpu/auth.
>
> I'm drawterming in this case from a windows box. I can drawterm in as
> bootes, but when I try to drawterm in as my user account I get
> cpu: cannot get auth tickets in p9sk1: The operation completed
> successfully.
>
> What step did I miss?
you /lib/ndb has the loopback interface and auth settings for your
virtual net?
I remember putting in something like the following on my VMWare
instance (:
ipnet=vmnet ip=192.168.254.0 ipmask=255.255.255.0
auth=vm
cpu=vm
fs=vm
bootf=/386/9pc
dns=192.168.254.2
dnsdom=YOURDOMAIN
authdom=YOURDOMAIN auth=vm
ip=192.168.254.105 sys=vm ether=VIRTETHER
dom=YOURDOMAIN
VMWare created it's NAT'd address on 192.168.254.X
So I also do the following to ease the pain:
[home:~] jas% cat `which cpu`
#!/usr/local/plan9/bin/rc
if(! ~ $#* 1){
echo 'usage: cpu <user>'
exit usage
}
drawterm -a 192.168.254.105 -c 192.168.254.105 -u $1
-jas
next prev parent reply other threads:[~2008-11-15 17:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-15 16:55 Eric Van Hensbergen
2008-11-15 17:12 ` Jeff Sickel [this message]
2008-11-15 17:21 ` Eric Van Hensbergen
2008-11-15 17:55 ` Eric Van Hensbergen
2008-11-15 18:18 ` Nathaniel W Filardo
2008-11-15 18:30 ` andrey mirtchovski
2008-11-15 21:36 ` Nathaniel W Filardo
2008-11-18 20:49 ` john
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=A20E10A1-7AAD-43F0-8DC2-385102F156E5@corpus-callosum.com \
--to=jas@corpus-callosum.com \
--cc=9fans@9fans.net \
/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).