[632] in Release_7.7_team
What should mkserv NFS look like?
daemon@ATHENA.MIT.EDU (Bill Cattey)
Mon Jul 8 18:32:35 1996
Date: Mon, 8 Jul 1996 18:32:23 -0400 (EDT)
From: Bill Cattey <wdc@MIT.EDU>
To: release-team@MIT.EDU, f_l@MIT.EDU
Cc: delgado@MIT.EDU
I just finished a brief chat with Jonathon Weiss on the subject of mkserv NFS.
Diane has completed porting (and rudimentary testing) of Athena
Kerberized NFS for Solaris.
Now it comes time to decide what we will call it in our mkserv list of
services.
At this point, when you do:
mkserv nfs
you get:
vanilla NFS on Solaris
Athena NFS on DECStation
nothing on SGI
Athena NFS on a Vax
Athena NFS on an RT
(The latter two we don't care about, but the legacy code is there and working.)
There are FOUR choices of NFS for Solaris:
Vanilla NFS
Athena NFS
Sun Kerberized NFS
Sun Kerberized NFS with Athena interoperability (not done yet)
How can we sensibly differentiate among these?
1. We could call them all 'mkserv nfs' and ask the user to PICK one, but
that might end up adding an additional question that has to be
continually re-answered with every update.
2. We could call athena nfs 'knfs'. But this gets confusing when we
choose among the THREE kerberized nfs's. It also introduces the
question "Do we care that some ancient mkserv nfs really is this OTHER
thing now?"
I think we should pick unique names for each of these options that imply
the right thing.
mkserv nfs Vanilla NFS
mkserv aknfs Athena Kerberized NFS
mkserv sknfs Sun Kerberized NFS
mkserv asknfs Sun Kerberized NFS with interoperability enhanced.
Footnote: What interoperability? Sun Kerberized NFS uses NIS to get
kerberos principals. With enhanced Athena interoperability, knfsd would
be modified to use hesiod in addition.
-wdc
