From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=ham autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,583275b6950bf4e6 X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2003-05-25 13:46:49 PST Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!logbridge.uoregon.edu!arclight.uoregon.edu!wn13feed!wn12feed!wn14feed!worldnet.att.net!204.127.198.203!attbi_feed3!attbi.com!rwcrnsc51.ops.asp.att.net.POSTED!not-for-mail Message-ID: <3ED12BA1.8040908@attbi.com> From: "Robert I. Eachus" User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.0.2) Gecko/20021120 Netscape/7.01 X-Accept-Language: en-us, en MIME-Version: 1.0 Newsgroups: comp.lang.ada Subject: Re: Quality systems (Was: Using Ada for device drivers? (Was: the Ada mandate, and why it collapsed and died)) References: <3ec4b1c9$1@news.wineasy.se> <9fa75d42.0305161748.1735fc32@posting.google.com> <4W%xa.28765$cK5.11964@nwrdny02.gnilink.net> <1053353256.804734@master.nyc.kbcfp.com> <3RYza.7093$ca5.494@nwrdny02.gnilink.net> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit NNTP-Posting-Host: 24.62.164.137 X-Complaints-To: abuse@attbi.com X-Trace: rwcrnsc51.ops.asp.att.net 1053895609 24.62.164.137 (Sun, 25 May 2003 20:46:49 GMT) NNTP-Posting-Date: Sun, 25 May 2003 20:46:49 GMT Organization: AT&T Broadband Date: Sun, 25 May 2003 20:46:49 GMT Xref: archiver1.google.com comp.lang.ada:37767 Date: 2003-05-25T20:46:49+00:00 List-Id: Hyman Rosen wrote: > Dmitry A. Kazakov wrote: > >> But a modular type should have no "<" defined! A transitive "<" is >> incompatible with modular "+" and "-". > > > I will try this argument next time I come in to work at 10am > and am accused of being late! > Reminds me of an occasion when the main machine we were using for Ada compiler validatation crashed about a week before the validation team was scheduled to show up--during back-up. Worse the idiot manager for the machine room had "simplified" the explicit backup rules which used three disk volumes so that he only needed two. You guessed it the crash was in the operational pack, and the backup was half-erased and half-written. I found out about this when I checked the machine room on my way out the door. Computer room 1 was near the main entrance. And our server was near the computer room door. So my coat and briefcase went in a chair, and I told the operator to "touch nothing!" I put a bootable disk in a third drive and started putting the pieces together to see what should be recovered. (And then called my wife to tell her not to wait dinner.) It turned out that the damage was to the VTOC (volume table of contents) on the original drive. The files were all there, they just had to be recovered with a disk repair utility. Around 10 AM I finished validating that I had recreated a valid bootable disk with all the files and started making a copy to a third pack. I went up to my office, carrying my briefcase and coat. My boss ambushed me, literally frothing at the mouth. "The server is down, the machine room supervisor says you ordered him not to touch the machine, and I left word at the guard station to have you call me the moment you came in." "I didn't come in, but the server is up now." "Huh." "The guard didn't have me call you since I didn't come in. I was here all night..." We were back on schedule by that afternoon after a bit of schedule shifting to get the large server off the critical path. But the supervisor was gone. It turned out HE had called Dick and Alan (my boss's boss) to complain about being ordered not touch one of "his" machines. But he hadn't explained that I was in the machine room at the time--and what he had done to get to the top of my shit list. Earlier he had stopped one machine in the middle of a B-test series run: "It was printing out all these error messages, so I shut it down." In spite of a large "Do not touch" sign. Then he shut down a machine because it just sat there with 100% utilization, and no output. (Looking for a subtle memory leak. It turned out to be a case where the OS on a 32-bit machine was rounding an allocation from the stack up to a multiple of four, then rounding to a multiple of two when freeing the space.) This was the third time the machine room supervisor had disobeyed explicit instructions in the log in less than three weeks. Bye, bye.