Path: utzoo!mnetor!uunet!husc6!mailrus!umix!umich!mibte!gamma!ulysses!thumper!faline!bellcore!clyde!watmath!julian!deepthot!zaphod From: zaphod@deepthot.UUCP (millions of atoms of Lance) Newsgroups: comp.sys.hp Subject: Re: hp9000 ser. 500 hpux Message-ID: <1021@deepthot.UUCP> Date: 12 Feb 88 14:05:20 GMT References: <987@maccs.UUCP> <1018@deepthot.UUCP> <191@bnr-vpa.UUCP> Reply-To: zaphod@deepthot.UUCP (millions of atoms of Lance) Organization: UWO CS, London Canada Lines: 41 >In article <1018@deepthot.UUCP> zaphod@deepthot.UUCP writes: >> I have hands on experience with 5.2's bugs. > In article <191@bnr-vpa.UUCP> bruce@bnr-vpa.UUCP (Bruce Townsend) writes: > ... Could you please elaborate on the nature of >the bugs introduced by 5.2 ... apparently a new "has the file system been checked since last change" flag was added to the super-block (i don't have the HP reference to this near me) and the first indication of weirdness is that our 7935 would not mount at boot time. After a fsck on the device it would mount. a lot of the /usr/contrib/bin progs would not work, such as users (mem fault and core dump) dir (core dump) catman -w (core dump) fortune (hang) adventure (hang) now, granted, the last two do not generate a major crisis, but since nearly every user i've met has fortune in their .login/.profile, they would all "get stuck" when they tried to log in. sigh. there were more problems, but i am sure that you get the idea, for a while it seemed that half the world was hanging and half the world core dumping. this is why, as i stated in my first posting, that our software rep. advised all his customers to NOT use 5.2, and thus why I feel that in all respects, HP has frozen at 5.1 not 5.2. -- humbly yours, Lance Bailey Univ. Western Ontario | Robarts Research Institute Dept. of Computer Science | Clinical Trials Unit Graduate Studies | PO Box 5015 London, Canada | London, Canada N6A 5B7 | N6A 5K8 decvax!{utcs|utzoo|watmath}!deepthot!zaphod -or- zaphod@deepthot.uucp