9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: William Gunnells <thecount12@yahoo.com>
To: 9fans@cse.psu.edu
Subject: [9fans] install terminal
Date: Tue, 13 Aug 2002 09:57:36 -0700	[thread overview]
Message-ID: <20020813165736.84455.qmail@web21411.mail.yahoo.com> (raw)
In-Reply-To: <20020813055402.18697.40853.Mailman@psuvax1.cse.psu.edu>

Thanks for the help. Most of that was my poor typing.
Either way. I corrected auth=auth and netmask and I
still get the same error when I try to connect a
terminal.

Hello!

                I have managed to build the file
server via wiki's
                instruction. My CPU/auth is now
diskless and can
                connect to FS under user bootes. I can
also execute
                auth/changeuser and add user william
to system. I'm
                having trouble logging in as william
via term. I
                didn't think it was complicated. I
thought all you
                need is to add another entry to
/lib/ndb/local and
                compile a kernel for the term
bootdisk. Here
                /lib/ndb/local::

                database=
                        file=/lib/ndb/local
                        file=/lib/ndb/common

                ipnet=myipnet ip=10.56.32.0
ipmask=255.255.240.0
                        ipgw=10.56.32.1
                        dns=192.204.133.102
                        auth=auth
                        proto=il

                ip=10.56.35.118 ether=00c04f182de5
sys=auth
                        bootf=/386/9pcauth
                ip=10.56.35.117 ether=006008c78c0c
sys=fs
                        bootf=/386/9pcfs
                        proto=il
                ip=10.56.35.115 ether=009027626acc
sys=term
                        bootf=/386/9pc
                        proto=il

                I'm static and the machines seem to be
talking fine.

                Here is the error of the term machine
that I'm using
                to connect via bootdisk.

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

                The plan9.ini on the term bootdisk
is::

                bootfile=fd0!dos!9pc.gz
                bootargs=il -g 10.56.32.1 ether
/net/ether0
                10.56.35.115 255.255.240.0 0
10.56.35.117 10.56.35.118


                The FS see's that the terminal
10.56.35.115 is trying
                to connect and reads.
                fs: il: allocating
il!10.56.35.115!24958
                hangup! connectio timed out-3
24958/10.56.35.115.17008

                the hangup occurs after term cycles
through and
                reboots...

                Please let me know if I'm missing
something.
                Thanks
                William Gunnells-

__________________________________________________
Do You Yahoo!?
HotJobs - Search Thousands of New Jobs
http://www.hotjobs.com


       reply	other threads:[~2002-08-13 16:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20020813055402.18697.40853.Mailman@psuvax1.cse.psu.edu>
2002-08-13 16:57 ` William Gunnells [this message]
2002-08-14  4:56 Charles Forsyth
2002-08-14  6:56 okamoto

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=20020813165736.84455.qmail@web21411.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).