Return to BSD News archive
Xref: sserve comp.periphs:4147 comp.realtime:3582 comp.os.386bsd.development:1090 Path: sserve!newshost.anu.edu.au!munnari.oz.au!yarrina.connect.com.au!belfast.dcd.wa.gov.au!belfast.dcd.wa.gov.au!not-for-mail From: juliane@belfast.dcd.wa.gov.au (Julian Elischer) Newsgroups: comp.periphs,comp.realtime,comp.os.386bsd.development Subject: Re: Why fix the RTC (Real Time Control) for 386bsd Date: 19 Aug 1993 10:17:15 +0800 Organization: Dept of Community Development, Perth, Australia Lines: 82 Sender: julian@dcd.wa.gov.au Distribution: world Message-ID: <24unrb$i67@belfast.dcd.wa.gov.au> References: <jmonroyCBuLr1.7L3@netcom.com> <CBvntC.Iys@jshark.inet-uk.co.uk> NNTP-Posting-Host: belfast.dcd.wa.gov.au Summary: What REALLY got said: Keywords: RTC report In article <CBvntC.Iys@jshark.inet-uk.co.uk> joe@jshark.inet-uk.co.uk (Joe Sharkey) writes: > >Oh, no, J.Monroy, you're doing "it" all over again.... > >Why:-( Will we learn anything? Will we get a better OS? A nice happy feeling? he can't help it.. he lives in his own imaginary world. He has a lot of interests and talents I'm sure, but reallity (sp?) isn't really involved. (I have met him but he probably doesn't remember..) > > >In article <jmonroyCBuLr1.7L3@netcom.com> jmonroy@netcom.com (Jesus Monroy Jr) writes: > >> At the request of Bill Jolitz and other, I have >> written this report. I should note that this is NOT a request >> for a Real-Time OS (Operating System). Also, I was a bit >> unaware of the lack of work done in this area, RTC (Real-Time >> Control). My assumption was that other had this knowledge, as >> second-hand, just as John Sokol and I. > >Geez, Jesus, subtle you aren't! from my knowledge of Bill, and Jesus my guess as to what happenned is: Jesus bombarded Bill with a 752 page report on social engineering with a summary of "We need to do something about RTC". (He may have deleivered the report over the phone) To which, Bill responded.. "well, if you think it's broken, you're always free to re-write it, (and by implication, No-one is required to use it)". Jesus has subltly changed this to: >> "At the request of Bill Jolitz and other, I have >> written this report." The 'others' being some other people who responded likewise. > >*I* thought preventing reactors going critical was in the "RTC" area - >well, maybe you're a bit more laid back in California? > >Real-Time Operating Systems are different from UNIX: have you managed >to work out why a QIC-40 driver is *so* difficult to write. that's why he wants to provide Real-time support I guess. > >> sections are broken up by a set of triple dashed lines with [...] >> Section Five are my comments and recommendations. > >I don't even understand the synopsis of section two :-( > >Jesus, are you using the same terminology as the rest of the world? no, it's his own world. I originally volunteered to do the BETA co-ordinating for his new all-singing floppy driver. After a while the most god-awful piece of cobol (well maybe it was C) turned up.. it Did compile, but it didn't work at all, and it came with patches that were obviously taken from some other version because they couldn't be easily applied, even manually. (and when you did as good as you could, it still didn't work) I asked him to send me a version that included the patches properly installed and I never received anything more, until I received a mail piece from him last week asking me to resign (resign? I thought it had died a thankful death) apparently he did his editing in DOS and didn't understand diff, patch or shar very well. He then proceeded to slag off at my patched version of the floppy driver ( hacked to support > 1 drive) claiming that it was the worst thing since Hitler decided to gas people, (and possibly worse than that). Hey I never said it was anything more than a hack on the old driver. The best thing to do is not answer, or you become "others". > julian temp email: julian@dcd.wa.gov.au