Xref: utzoo comp.sys.tandy:726 comp.unix.xenix:2108
Path: utzoo!mnetor!uunet!oddjob!ncar!ames!eos!labrea!decwrl!decvax!mandrill!hal!ncoast!mikes
From: mikes@ncoast.UUCP (Mike Squires)
Newsgroups: comp.sys.tandy,comp.unix.xenix
Subject: 68K XENIX 3.2 bugs
Message-ID: <7683@ncoast.UUCP>
Date: 26 Apr 88 05:04:54 GMT
Distribution: comp
Organization: Cleveland Public Access UN*X, Cleveland, OH
Lines: 38
Keywords: 6000 XENIX 3.2 bugs

I have heard of the following bugs in XENIX 3.2:

1.  The tsh restore won't pick files off a disk; must use
    tar instead. (This was not broken under XENIX 3.1.x).

2.  The /etc/inittab option for getty passes parameters to getty
    incorrectly; fix requires getty sources.

3.  The 3.2 time function and software created under 3.1 and earlier
    XENIX systmes are incompatible; between the current date for the
    change to daylight saving and the old date the "date" command
    yields the correct date but uucp, cron, etc., report standard
    time.  Fix: lie about whether daylight saving time applies and
    the location when setting time zone.

4.  My own experience suggests that 3.2 z80ctl is more sensitive to
    timing problems; two 12 with 6000 upgrades glitched with strange
    HD errors (including an inability to read track 32000 and something)
    but both systems have been rock solid before under 3.1.2.

Minor problems:

1.  help files are not included with new OS, not even those commands
    that are updated or completely new.

2.  Install disks are identified in such a way as to lead the unwary to
    attempt to install the wrong disks, leading to major hassles.

3.  tar install disks are DS, not SS; no II upgrades need apply (the
    letter sent out says that only 6000's are now supported).

Questions:  where is the MMU? Now that the whole 6000 world knows about it
it would seem that release is imminent. Also, how about the 3.2 developement
system (especially inlight of (3) above.

Mike Squires Allegheny College Meadville, PA 16335 814 724 3360
uucp: ..!mandrill!ncoast!{mikes,peng!sir-alan!mikes} or ..!pitt!sir-alan!mikes
BITNET: mikes%sir-alan@pitt.UUCP (VAX) MIKES AT SIR-ALAN!PITT.UUCP (IBM)