Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!wuarchive!psuvax1!psuvm!cunyvm!ndsuvm1!mtus5!tomiii
From: TOMIII@MTUS5.BITNET (Thomas Dwyer III)
Newsgroups: comp.protocols.nfs
Subject: Re: PC-NFS Wish List (Re: Enduring PC-NFS Annoyances)
Message-ID: <90305.173430TOMIII@MTUS5.BITNET>
Date: 1 Nov 90 22:34:29 GMT
References: <1990Oct31.102026.20561@cs.eur.nl>
Organization: Computing Technology Services, Michigan Technological Univ.
Lines: 39

Ok, I feel obligated to add these wishes...


-- How about a chgrp command?

-- Why leave unencrypted passwords sitting around in memory?
   Some security wouldn't be bad.

-- Why, oh why can't we get a non-serialized version of PC-NFS?  Or maybe
   get the serial number from a server?  Keeping track of 300+ boot disks,
   making sure each machine has the right one is not acceptable.

-- I 2nd the motion for a new telnet (with 3270 support)

-- How about a toolkit that interfaces with NET.EXE's structures (such as
   which drives are mounted & where?)

-- How about allowing set-uid programs?

-- We could use a software-license checkout feature.

-- Are we ever going to get a list of bug reports, as we do with SunOS?

-- Make the timezone (DST) functions work without the need for a battery
   clock in the PC.

-- Boot the PC off the network.

-- Add an "rdate" command.


On the other hand, PC-NFS has served most of our needs over the last three
years...


Thomas Dwyer III                        Email: tomiii@mtu.edu
Network Programmer                             tomiii@mtus5.BITNET
Computing Technology Services           Voice: (906) 487-2110
Michigan Technological University       Fax:   (906) 487-2787