michaelb@vms.macc.wisc.edu (Michael Bloxham) (02/28/90)
I have finalized my list of files that I need to make my 1.3 version
of MINIX complete and ready for an upgrade to 1.5.0. I would really
appreciate some help in obtaining these files, either by ftp, bbs, email,
or ground mail. I have already looked at Bugs.nosc.mil, Simtel20,
LISTSERV, and the 1.3 diffs to no avail.
The following is a list of files that are missing or ones that I cannot
create or duplicate the crc from the P0 posting of the 1.5.0 distribution
kit:
1.3 crc size file what's wrong
------- ---- ---- ------------
17960 11073 * minix/commands/dis88/README <- different crc
19257 7600 * minix/commands/dis88/dis.h <- different crc
58032 17458 * minix/commands/dis88/dismain.c <- different crc
16516 777 * minix/commands/dis88/disrel.c <- different crc
55558 1473 * minix/commands/dis88/makefile <- different crc
60732 7645 * minix/commands/lorder.c <- different crc
57349 494 minix/commands/makefile <- different crc
49653 60035 minix/commands/mined/mined1.c <- different crc
58277 38509 * minix/commands/doc/USER_GUIDE <- different crc
42220 39018 minix/commands/doc/lib.doc <- missing
56449 474 minix/lib/IBM_PC/prtso.s <- missing
59092 251 minix/test/makefile <- different crc
59520 2249 * minix/tools/at_makefile <- different crc
39871 44 minix/tools/group <- missing
* These were obtained directly from the 1.3 diff postings
a year or so ago as whole files, and they do not match the
crc list posted by AST as the official 1.3. (see partial
list on left) Figure that out!
BTW - the crc list to the left are what I need; mine are
different!
That's it. Considering the number of files that make-up MINIX, I don't
consider this that many that I have missing or different. I would really
like to get my distribution straight! Like I say, any help is greatly
appreciated.
thanks much,
mike
-----------------------------------------------------------------------
Michael L. Bloxham | Real programmers don't comment their code.
michaelb@vms.macc.wisc.edu | If it was hard to write, it should be hard
michaelb@WISCMACC.bitnet | to understand.