From: forsyth@caldo.demon.co.uk
To: 9fans@cse.psu.edu
Subject: Re: [9fans] micro vs monolithic kernels
Date: Mon, 9 Apr 2001 11:19:51 +0100 [thread overview]
Message-ID: <20010409102225.089A119A15@mail.cse.psu.edu> (raw)
the nvram isn't important. it will prompt for the values if necessary
and that's the easiest way to check that it is correctly booting the cpu server
kernel not the terminal kernel. once that's going you can worry about setting
up the nvram.
i set a cpu/auth system up recently (without a separate file server).
i think this is what i did:
0. build /lib/ndb/local correctly; in many ways, the hard part. you need to get
the ipmask= and ipsubmask= and ip-net= set up to describe your network correctly.
include proto=il in the entry for each plan 9 machine.
include default auth= and fs= entries in the network or subnet entries.
1. cd /sys/src/9/pc; mk 'CONF=pccpudisk' install
2. 9fat: ; cp /386/9pccpudisk /n/9fat/9pccpudisk
3. change /n/9fat/plan9.ini, bootfile=sdC0!9fat!9pccpudisk (replacing sdC0 by your disc name)
4. make sure /lib/ndb/auth contains
hostid=bootes
uid=!sys uid=!adm uid=*
this lets the cpu server believe that the auth server can vouch for others as described
5. cd /rc/bin/service; mv il566 _il566; mv tcp567 _tcp567
6. cd /rc/bin/service.auth; ensure the following contents
tcp567:
#!/bin/rc
/bin/auth/auth.srv -d $3
il566:
#!/bin/rc
/bin/auth/auth.srv -d $3
chmod a+rx tcp567 il566
7. modify /rc/bin/cpurc to uncomment the lines that are commented-out:
# uncomment the following for booting other systems
ip/dhcpd
ip/tftpd
# services available to networks (remove -t /rc/bin/service.auth
# if this isn't an auth server)
auth/keyfs -m /mnt/keys /adm/keys
aux/listen -q -d /rc/bin/service -t /rc/bin/service.auth il
aux/listen -q -d /rc/bin/service -t /rc/bin/service.auth tcp
auth/cron
you can add a switch($sysname){ ... } to select different cpu server services
if you've got more than one and only one is acting as auth server and file server.
8. if you're not setting up a separate file server (using the /sys/src/fs kernel) but are
serving files from a kfs partition on the cpu/auth server, then further do
8a. cd /rc/bin/service; mv il17008 _il17008
8b. in /rc/bin/cpurc above, after starting auth/keyfs and before aux/listen do
disk/kfscmd listen
next reply other threads:[~2001-04-09 10:19 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-09 10:19 forsyth [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-04-17 8:35 nemo
2001-04-10 11:56 forsyth
2001-04-10 11:50 forsyth
2001-04-10 11:35 Matt
2001-04-10 10:52 forsyth
[not found] <200104092210.RAA06371@einstein.ssz.com>
2001-04-09 22:12 ` Jim Choate
2001-04-10 9:00 ` Boyd Roberts
2001-04-09 22:00 jmk
2001-04-09 22:30 ` Jim Choate
2001-04-09 21:47 presotto
2001-04-09 21:43 Russ Cox
2001-04-09 22:16 ` Jim Choate
2001-04-10 8:59 ` Douglas A. Gwyn
2001-04-10 9:00 ` Boyd Roberts
2001-04-09 21:15 Russ Cox
2001-04-09 21:52 ` Jim Choate
2001-04-09 21:36 ` Lyndon Nerenberg
2001-04-09 22:08 ` Jim Choate
2001-04-09 22:34 ` Lyndon Nerenberg
2001-04-10 0:45 ` Steve Kilbane
2001-04-10 0:28 ` Jim Choate
2001-04-10 8:18 ` Steve Kilbane
2001-04-10 8:57 ` Douglas A. Gwyn
2001-04-09 21:40 ` William Josephson
2001-04-09 22:10 ` Jim Choate
2001-04-09 22:16 ` William Josephson
2001-04-09 22:42 ` Dan Cross
2001-04-09 23:10 ` Jim Choate
2001-04-10 0:30 ` Dan Cross
2001-04-09 22:10 ` Mike Haertel
[not found] <john@cs.york.ac.uk>
2001-04-09 14:33 ` John A. Murdie
2001-04-09 23:31 ` Steve Kilbane
2001-04-09 9:09 forsyth
2001-04-09 9:32 ` Dave Iafrate - CSCI/F1997
2001-04-09 16:14 ` Douglas A. Gwyn
2001-04-08 19:36 presotto
2001-04-08 17:55 Andrey A Mirtchovski
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=20010409102225.089A119A15@mail.cse.psu.edu \
--to=forsyth@caldo.demon.co.uk \
--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).