From JPG at MIT-MC Thu Jun 14 00:00:00 1979 From: JPG at MIT-MC (JPG at MIT-MC) Date: 14 Jun 1979 00:00 Subject: No subject Message-ID: Say, this system is locking disk blocks! It just crashed, and I reloaded it from scratch. Before the crash, the number of available blocks on #0,#1,#13 respectively were 320,380,201 . (I checked this just before the crash.) After the crash, the number available was 547,552,257 + I dumped out a 171 block crash file on CRASH;. I noticed this phenomenon about 2 weeks ago when the system crashed and RWK reloaded it, and mentioned it to him, but I wasn't as certain then, so didn't report it. I wonder if this has something to do with swapping disk somehow using user blocks or whatever, and the system's marking them at high-use time getting screwed up. Whatever, something is doing this! From RWK Mon Jun 11 00:00:00 1979 From: RWK (Robert W. Kerns) Date: 11 JUN 1979, 00:00 Subject: E? USR:$ Message-ID: Date: 10 JUN 1979 1242-EDT From: EAK at MIT-MC (Earl A. Killian) To: RWK, (BUG ITS) cc: (BUG TECO) Re: E? USR:$ Date: 06/09/79 03:47:19 From: RWK at MIT-MC To: (BUG TECO) Re: E? USR:$ creates an inferior. It should set the bit saying to fail if the job doesn't exist. Even better would be to have the USR: device obey the same convention as the DSK: device, i.e. if you open for reading then it is an error if it doesn't exist. RWK, you said once DDT could be fixed if ITS were so changed, is that still true? Yes, it's still true. From EAK Sun Jun 10 00:00:00 1979 From: EAK (Earl A. Killian) Date: 10 JUN 1979, 00:00 Subject: E? USR:$ Message-ID: Date: 06/09/79 03:47:19 From: RWK at MIT-MC To: (BUG TECO) Re: E? USR:$ creates an inferior. It should set the bit saying to fail if the job doesn't exist. Even better would be to have the USR: device obey the same convention as the DSK: device, i.e. if you open for reading then it is an error if it doesn't exist. RWK, you said once DDT could be fixed if ITS were so changed, is that still true? From JKESS at MIT-MC Fri Jun 1 00:00:00 1979 From: JKESS at MIT-MC (JKESS at MIT-MC) Date: 01 Jun 1979 00:00 Subject: to whoever is maintaining the CROCKS again Message-ID: and CROCK loses its center point, writing randomly. Both of these are new bugs -- CROCK ran perfectly before today... From JKESS at MIT-MC Fri Jun 1 00:00:00 1979 From: JKESS at MIT-MC (JKESS at MIT-MC) Date: 01 Jun 1979 00:00 Subject: to whoever maintains the CROCKs... Message-ID: DCROCK fails totally to get its digit positioning right on VT100s.