9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Lucio De Re <lucio@proxima.alt.za>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] AUTH, FS, etc.
Date: Wed, 19 Jul 2000 11:54:11 +0200	[thread overview]
Message-ID: <20000719115411.D3081@cackle.proxima.alt.za> (raw)
In-Reply-To: <200007190937.FAA26687@cse.psu.edu>; from okamoto@granite.cias.osakafu-u.ac.jp on Wed, Jul 19, 2000 at 06:37:45PM +0900

On Wed, Jul 19, 2000 at 06:37:45PM +0900, okamoto@granite.cias.osakafu-u.ac.jp wrote:
> 
> I don't know exactly.  I wrote just my successfull route for you.  ^_^
> This is a temporal way untli the 3rd release will have all the capability
> which now my 2nd release have, then, I think it's enough if it works.
> 
Well, as it stands, 3ed has some way to go before it is ready for
shrink-wrap.  But this is the exciting stage, when the path ahead is
still being established.

> In our setting, we rarely experience the confusion by which file server
> responds, only once for a PC terminal.  Therefore, I suppose something
> very tricky conditions must be there.
> 
I'm sticking to the 2ed fileserver, because I have only 1542CP
adapters and only one host to run it on.  It seems to work just fine,
now that I've figured out most of the ins and outs.

What I can't quite decide is whether I need a second CPU server, or I
should update the 2ed one to 3ed.  I'm very keen to check out the new
mailer facilities of ACME and upas/fs.  My present facility is
adequate but ready to be improved on.

And I really need to grasp the DHCP/BOOTP aspects of the boot
procedure properly, both in 2nd and 3rd edition.

> Your network texture beyonds my understanding!   What are you doing
> on that network, anyway?  :-)
> 
Learning, mostly.  It takes me a long time to understand things to my
satisfaction, and I have far too many interests.  Occasionally, a
client will need something I learnt and will pay me for it :-)

The confusion is much greater when one looks at the NAT and IP filter
rules and the multihoming in place at the client whose Internet
services I'm privileged to share.

++L


  reply	other threads:[~2000-07-19  9:54 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-07-19  9:37 okamoto
2000-07-19  9:54 ` Lucio De Re [this message]
  -- strict thread matches above, loose matches on Subject: below --
2000-07-19  7:49 okamoto
2000-07-19  8:28 ` Lucio De Re
2000-07-18 12:11 forsyth
2000-07-18 11:35 forsyth
2000-07-18 11:50 ` Lucio De Re
2000-07-18  8:27 forsyth
2000-07-18  8:40 ` Lucio De Re
2000-07-18  8:50 ` Lucio De Re
2000-07-18  7:49 Lucio De Re

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=20000719115411.D3081@cackle.proxima.alt.za \
    --to=lucio@proxima.alt.za \
    --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).