9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Brandon Black photon@nol.net
Subject: It's alive!
Date: Thu,  7 Nov 1996 12:34:51 -0600	[thread overview]
Message-ID: <19961107183451.SM4Xo6Scc-4J2tdg4qjB71u4pi-5J3lmiEqN8Fg89Hw@z> (raw)



Thanks to everyone who has helped me... its alive!

To anyone else who basically knows what they're doing but is having a hard
time installing from the CD using the instructions in the book... here
were my three biggest problems:

1. When the auth server asks for the IP addres of the auth server, put in
0.1.0.0, _not_ 0.0.0.0

2. After you first boot up your auth server (the first time), and the
fileserver is still in allow mode (or you haven't rebooted it since installing
the CD, same thing)... do an "auth/changeuser authid" where authid is your
domain's authid.

3. When you're editing /lib/ndb/local, go down to the services and add:
il=ticket	port=566


Now I'm off to call AssureNet Pathways and get a securenet box.... before
I go, one other hint.... 

Re-typing the IP info on your auth server every time you boot is a bitch...
edit /sys/src/9/boot/ip.c, go down to the bootp section, wipe out the bootp
code, down to where is starts asking for the info manually after bootp failed.
remove the outin() calls and other such stuff, and hardcode the ip address
info for the auth server in.  The go to /sys/src/9/pc, and "mk CONF=pccpu".
(be sure to put the original ip.c back when you're done, and mk clean on
both directories...)
To save a few extra seconds and optimize the kernel a bit, I also took the
datakit stuff out of /sys/src/9/pc/pccpu (the dk lines in the devices list
and boot list, and the sturp line, I think it was), so that IL was the only
boot method, and the datakit code was not present, and modified
/sys/src/9/boot/boot.c to automatically pick the first boot method on the list.
To do that, pretty much wipe out the rootserver() function's internals, and
fill it in with:

mp=method;
return mp;

or something.. I don't have the sources here(my plan 9 setup is a half hour
drive from where I can get email... so... )

Brandon

..............................................
: Brandon Lee Black  : photon@gnu.ai.mit.edu :
:....................: photon@nol.net        :
: "Sanity is the     : photon@vanity.ops.org :
: trademark of a     : vis_blb@unx1.shsu.edu :
: weak mind. . ."    : +1 713 397 3490       :
:....................:.......................:





             reply	other threads:[~1996-11-07 18:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1996-11-07 18:34 Brandon [this message]
1996-11-07 18:41 forsyth
1996-11-07 19:08 Brandon
1996-11-07 19:08 Stephen

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=19961107183451.SM4Xo6Scc-4J2tdg4qjB71u4pi-5J3lmiEqN8Fg89Hw@z \
    --to=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).