[636] in Release_7.7_team
Re: What should mkserv NFS look like?
daemon@ATHENA.MIT.EDU (Jonathon Weiss)
Tue Jul 9 19:31:07 1996
From: Jonathon Weiss <jweiss@MIT.EDU>
To: Bill Cattey <wdc@MIT.EDU>
Cc: release-team@MIT.EDU, f_l@MIT.EDU, delgado@MIT.EDU
In-Reply-To: Your message of "Mon, 08 Jul 1996 18:32:23 EDT."
Date: Tue, 09 Jul 1996 19:31:00 EDT
> 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.
I suspect that it would not be too hard to set up a user interface
similar to mkserv remote, where it only asked you what type of nfs if
you were taking the update manually. It probably also wouldn't be too
hard to make it only ask the first time it is run. (Probably we'd
want it to re-ask if someone removed the nfs service and re-added it.)
> 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.
I think users are going to have a hard time remembering these
random-looking strings of letters.
Jonathon
