Path: utzoo!attcan!uunet!mcvax!hp4nl!botter!star.cs.vu.nl!ast
From: ast@cs.vu.nl (Andy Tanenbaum)
Newsgroups: comp.os.minix
Subject: Re: 1.3c upgrade results[LONG]
Keywords: Minix, 1.3c, bugs, lorder, ls, fputc, fgetc, fsck, bootblok, peek, port_in, port_out
Message-ID: <1454@ast.cs.vu.nl>
Date: 3 Oct 88 13:28:12 GMT
References: <1429@ast.cs.vu.nl> <14243@comp.vuw.ac.nz>
Reply-To: ast@cs.vu.nl (Andy Tanenbaum)
Organization: VU Informatica, Amsterdam
Lines: 36

In article <14243@comp.vuw.ac.nz> jonathan@comp.vuw.ac.nz (Jonathan) writes:
>	    Perhaps ast would care to post his libc.a ordering again?
Ok.  I'll do this shortly, but be warned that my libc.a does not contain
Everything in lib (to keep libc.a manageable for floppy-only users).
>The documentation updates (posting 1.3c #07) are mostly ok.
>There are still a few typos, though (what's a WD1003E?).  Are these
>worth fixing?
>
>I found 4 more problems with the commands updates.
>
>	(5) the patch to sed.c causes the preprocessor symbol
>	"CMASK" to be multiply #defined.  The standard definition
>	in <stdio.h> is 0377, to defeat sign extension of characters.
>	Is it safe to ignore the warning message this causes?
Yes, ignore it. Sorry about that.

>	(6) readclock.c calls functions port_in(), port_out(), and
>	peek() that aren't defined anywhere.  
I moved them to portio.s in lib.  I guess I forgot to post it.  Soon.

>	(10) the new bootblok.s seems broken.  
Good grief.  I have made up the 1.3 diskettes and put them in a box full
of styrofoam and sealed it and am waiting to send it off.  I am not
enthusiastic about starting all over, but this bug, if true, is deadly.
My suspicion is that the trouble is with the changes made for the PS/2,
namely trying to use 720K diskettes.  Will people please reassemble
bootblok.s and build a new boot diskette, and report back on what happens.

>	(11) The patch for fsck.c didn't match my source.  
I may well have screwed up on some files.  Once everything is stable, I
will list everything and maybe we can figure out which files are wrong.
If it's not too many, I will just report them.
No more Amoeba postings.  Only one person has reported using it, so no bug
reports have come in.

Andy Tanenbaum (ast@cs.vu.nl)