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:         Thu, 19 Nov 1992 19:48:17 -0600
Reply-To:     Novell LAN Interest Group <NOVELL@SUVM.BITNET>
From:         Joe Doupnik <JRD@USU.BITNET>
Subject:      Re: List of current 3.11 file versions

>Does anyone know where I can get a list of the current versions of the
>files (name, version number, size, date) which make up NetWare 3.11?
>Ideally, this list would be annotated to include information about prob-
>lems in and/or fixed by the versions listed.
>
>Frank Boimare
>sc0hass@vm.tcs.tulane.edu
-------------
        This will sound a little huffy without meaning to be, but there
are soooo many utilities and files comprising NW 3.11 that no one has the
time to maintain a compendeum (maybe not Novell either). Thus I suggest
the hard route for now, which is get file FORUM.DOS (01\forum.zip) from
the novlib area of ftp.is.sandy.novell.com or mirrors and start marking it
up with an editor. It's about 1+MB and the file collection in the novlib
area proper (forums 01..11, novfiles, temp) exceeds 1000 files. Right,
lots of fun sifting all of this. But, when faced with complex issues we
simplify and rank order, and that means attacking the core files and then
the lesser used ones.
        To help, file 01\311pt9.zip (same as novfiles\311pt9.zip) has
the latest round of Patches to NW 3.11, meaning mostly server items.
In novfiles are the new security editions of many many DOS utilities, so
grab those sec*.exe files too. Secos2.exe is for OS/2, natch. There are
other updates throughout the novlib area, depending on what you have
installed.
        After loading up with goodies the next step is keeping things
organized. So you might maintain an update directory on the server, into
which you place the archives you use on the network. I tend to keep both the
archive file and the unpacked version, so I (usually) know the geneology of
files. In my autoexec.ncf file I have a section at the end for Patches, and
it should be at the end so the original NLMs are loaded before they are patched.
        General net.wisdom says apply patches only when needed, and omit
those not pertaining to your installation (why ask for trouble, etc).
Similarly, keep the original DOS utilities under new names or in a new
directory so you can back away if things are not so nice with the new ones.
Don Provan had some interesting advice this morning on trying new NLMs with
the ability to backaway quickly. Console command MODULES will show what's
installed in the server o/s.
        Area novlib changes daily so touch base now and then to stay
current.
        If you use my NW 3.11 server netlab2.usu.edu for novlib etc material
then notice the time/date stamps shown by Novell's FTP.NLM are those when
the files were created on that machine, not the date of the files on Sandy.
It's a bug in that FTP which shows the creation rather than modification date.
The same material seen from Unix machine netlab1.usu.edu (an NFS mount from
netlab2) shows the same time/dates as Sandy (+/- a few NFS date/time
conversion bugs). So, when using mirror sites be aware of time/date stamp
differences. By the time you get the file home via FTP the stamp will be
your local value anyway. Also, all the files seen on netlab2 and netlab1
are stored as DOS files, so BINARY ftp transfers to DOS machines work all
the time for all of the files. Sandy maintains the same name space system.
        Joe D.
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU