From: William Gunnells <thecount12@yahoo.com>
To: 9fans@cse.psu.edu
Subject: [9fans] help connect a terminal to kfs or Standalone CPU
Date: Fri, 13 Sep 2002 12:50:02 -0700 [thread overview]
Message-ID: <20020913195002.53869.qmail@web21408.mail.yahoo.com> (raw)
In-Reply-To: <20020912160003.27268.89675.Mailman@psuvax1.cse.psu.edu>
Having trouble getting a terminal to connect to
Standalone CPU. Used wiki resource but still no luck.
This is the error I receive:
authentication failed (auth_proxy rpc write
::connection rejected), trying mount anyways
boot: /: attach -- unknown user or failed
authentication
Then the system just cycles through and reboots...
Also used disk/kfscmd chat. I think its a ticket
problem. Not sure how to correct it. Maybe I have
something set up wrong.
Here are my configs
#!/bin/rc
echo -n cpu > /env/service
date > /env/boottime
# replace FILESERVER with the name of your file server
# here we start with kfs, your local disk file system
fileserver=kfs
# replace FACEDOM with the local domain to be used in
the faces database
facedom=FACEDOM
for (i in '#m' '#i' '#S' '#t')
bind -a $i /dev >/dev/null >[2]/dev/null
ip/ipconfig -g 192.168.0.1 ether /net/ether0
192.168.0.2 255.255.255.0
# name translation, cs sets /dev/sysname
ndb/cs
sysname=`{cat /dev/sysname}
sysname=kfs
ndb/dns -r
# parallelism for mk
NPROC=`{wc -l /dev/sysstat}
NPROC=`{echo $NPROC|sed 's/ .*//'}
prompt=($sysname^'# ' ' ')
# pick a timeserver closer to you when you can or
we'll get clogged
#aux/timesync plan9.bell-labs.com
# uncomment the following for booting other systems
ip/dhcpd
ip/tftpd
# If you are on an auth server, start these before
listening:
#
auth/keyfs -wp -m /mnt/keys /adm/keys >/dev/null
>[2=1]
auth/cron >>/sys/log/cron >[2=1] &
#
# also rename some files:
#
# if(! test -e /rc/bin/service.auth/il566){
# mv /rc/bin/service.auth/authsrv.il566
/rc/bin/service.auth/il566
# mv /rc/bin/service.auth/authsrv.tcp567
/rc/bin/service.auth/tcp567
# mv /rc/bin/service/il566
/rc/bin/service/_il566
# mv /rc/bin/service/tcp567
/rc/bin/service/_tcp567
# }
# for standalone cpu only
disk/kfscmd 'listen il!*!17008'
# services available to networks
aux/listen -q -d /rc/bin/service.auth -t
/rc/bin/service il
aux/listen -q -d /rc/bin/service.auth -t
/rc/bin/service tcp
and local
database=
file=/lib/ndb/local
file=/lib/ndb/common
ipnet=myipnet ip=192.168.0.0 ipmask=255.255.255.0
ipgw=192.168.0.1
auth=kfs
proto=il
ip=192.168.0.2 ether=00c04f182de5 sys=kfs
bootf=/386/9pcauth
proto=il
ip=192.168.0.3 ether=009027626acc sys=term
bootf=/386/9pc
proto=il
__________________________________________________
Do you Yahoo!?
Yahoo! News - Today's headlines
http://news.yahoo.com
next parent reply other threads:[~2002-09-13 19:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20020912160003.27268.89675.Mailman@psuvax1.cse.psu.edu>
2002-09-13 19:50 ` William Gunnells [this message]
2002-09-13 20:44 Russ Cox
[not found] <20020914160005.21633.45193.Mailman@psuvax1.cse.psu.edu>
2002-09-14 20:43 ` William Gunnells
2002-09-14 21:18 Russ Cox
[not found] <20020915160003.13605.25991.Mailman@psuvax1.cse.psu.edu>
2002-09-16 17:47 ` William Gunnells
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=20020913195002.53869.qmail@web21408.mail.yahoo.com \
--to=thecount12@yahoo.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).