X-Envelope-to: NOVELL@SUVM.BITNET
X-VMS-To: IN%"NOVELL@SUVM.BITNET"
X-VMS-Cc: JRD
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Newsgroups: bit.listserv.novell
Date:         Tue, 1 Sep 1992 13:25:15 -0600
Reply-To:     Novell LAN Interest Group <NOVELL@SUVM.BITNET>
From:         Joe Doupnik <JRD@USU.BITNET>
Subject:      Re: Internet Services

On Mon, 31 Aug 1992 15:36:55 -0700 <sdchrist@NOVELL.COM> said:
>To all NetWare users:
>
>Novell is looking for ways to improve on the services offered to its customers
>via the Internet.
        The current novlib archive is terrific! However, as people note, it
is rather difficult to locate material and to know which files are available
for specific topics. Master file FORUM.DOS has this information but it does
require an editor (person) to bring it back into shape. The shear quantity of
files is part of the problem: about 1000 files, 60+MB compressed, in 11
directories under a wide variety of naming conventions.

        My suggestion is for Novell to allocate some person-time to maintaining
the master list, Forum.dos, on a regular basis. Some indication of patch levels
and a list of the current plus previous patches by product would be helpful.
A good list of files is as much benefit to Novell Tech Support as it is to
us end users.

        I've asked around here and offering novlib across Bitnet as a
listserver is a little more than we (Utah State) can undertake easily. The
Utah State copy of novlib is mountable across the network by NFS so maybe a
site could offer Bitnet service with say the USU mirror as the source. That
mount point is currently netlab2.usu.edu:/sys/anonftp/novlib, read-only, soft.
If there is sufficient demand & need I could make small numbers of tape images
of the archive, as either QIC150/250 Unix TAR format, or TK50 VMS Saveset
format, or if you have Novastor's novaback program then their DOS format on
DAT. There would have to be a small fee to cover media and equipment wear and
tear. I think it is important to note the library is dynamic, files appear,
and a few vanish (typically age away), on a nearly daily basis so a tape copy
becomes dated fairly quickly.

        My other suggestion for Novell is to take note of frequent complaints
and pass along the digest to the program managers for action. The current
list sysops can help a lot here. For example, the number one problem is
printing, especially rprinter. Number two is attaching Macs to NW servers,
and again particularly printing operations. Number three might be mixing
ESDI drives with other kinds, competing with PS/2 Model 80 problems of all
descriptions, and the ambiguity of upgrading servers while preserving what's
keepable. Vrepair (all the variants) is indeed a problem brewing and needs
attention. For Novell I would suggest they view this list as a wonderful
bunch of highly vocal experienced managers providing feedback on products
they live with day by day; beta testers are never so good as this **wide
variety** of folks. The participation of Novell from time to time is great,
and is much appreciated; the nice part of this list is Novell is not obliged
to respond since the list members assume that duty.
        Joe D.
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU