From: Jesus Monroy Jr (jmonroy@netcom.com) Subject: [386bsd] hello to all Newsgroups: comp.unix.bsd, comp.os.386bsd.development View: (This is the only article in this thread) | Original Format Date: 1993-02-11 18:43:03 PST To all 386BSDers "Surviving depends upon quality, flexibility, and constant innovation, which inturn depends upon people." -Tom Peters "Thriving on Chaos",p.344 Now that I have finally got a reliable e-mail drop (thank God for Netcom), I can relay to all of you that I am going to do and who I am. When Bill Jolitz was making the tours (talks), I happened to be at an SVNET meeting. After his talk I was quite excited, I had been preparing for this type of enterprise since the announcement of the Intel i386. Although not the best of chips or designs, it promised the best comprimise in "buck for bang" and I knew then as I do today it is going to be a powerful force in tomorrows' technologies. Initally I offered my help to Bill, but he stated (at the time) that he had over 200 people volunteered for various projects and my particular idea was taken. After more that a year and amist many vile rumors, I was able to contact Bill and Lynn again and my help was readily accepted. However, my e-mail contact with them was at best a disaster. My e-mail went out through a friends' account and was labeled to reply to me through a different machine. Sometime later my friend filed for separation, divorce, and bankruptcy, which put my mail status into a black-hole. I proceeded to get service on the SVNET machine, unfortunately, my good friend Paul Fromberg was literally putting out fires at SUN Microsystems at the time and as the SYS Administrator, he could offer no help beyond a log-on account. Frustrated, one day at a PC Unix users group meeting of the SVNET, Amancio Hasty was demoing and explaining his patches to the X-Windows system. I explained my situation to him. He suggested NETCOM.COM. I now have a porthole to the world with NETCOM. In a few days I will post problems with the FDC, the LP, and the use of the QIC-40/80 through the FDC. I will address issues relevant to all device drivers and with your help, as protagonists, 386BSD will be and do everything you want it to. I am not depending on a team of 30 or 40 paid personel, but a cast of hundreds of unpaid volunteer people, like yourselves. If you have any doubt as to the number and diversity, watch the newsgroup(s) daily for about two weeks. There is no corner of the world where 386BSD is not in operation. ---------- I will post more info in a few days at the FDC on comp.unix.bsd comp.os.386bsd.development (when it comes on-line) I am will post new code in a few days also at FTP sites. ---------- People interested in helping with the FDC and QIC-40/80 should e-mail me. I am also starting a FAQ (Frequently Asked Questions) list for the devices I mentioned. From: Jesus Monroy Jr (jmonroy@netcom.com) Subject: [386bsd] Error Theory Newsgroups: comp.unix.bsd, comp.os.386bsd.development View this article only Date: 1993-02-17 01:11:58 PST The following is message I sent to William Jolitz a while back. --------------------------------------- ======================================= RE: Error Theory/Error bit Dear Bill, 03:10:44 Mon 01-04-1993 In my most recent efforts to rewrite the FDC code in use for 386BSD, I have been unable to find a correct paradigim in which recovery for an insatanciated error can be salvaged in a concise manner. Before giving you my thoughs I must share some fundamental Ideas I think that we can agree on. 1) At present we measure time as decay. ie. decay of the the sun rising, a clock ticking the half life of Uranimum 2) An Error is and embedded or integral process. An Error can be removed from a process. 3) An Error can cause failure. 4) A Failure is not an Error, it is a response to an Error. My thoughts have been that the premise for my algorithm is incorrect. That is most code is written with the thought that the code will run correctly most all of the time, this part is correct for efficient and active code, but treatment of errors is limited at the present to traps. Traps being an enclosure or encapsulation of the data recovery process, with most if not all data being information that the unit must digest. Because the Error Process is feed or contains data extranious to the Instanciated Error, a recovery calls for sifting through data that is completely unassociated with the current. Current being the time flow which speaks to the process Read the rest of this message... (86 more lines) Message 2 in thread From: Greg Hackney (hackney@moxie.hou.tx.us) Subject: Re: [386bsd] Error Theory Newsgroups: comp.unix.bsd, comp.os.386bsd.development View this article only Date: 1993-02-17 15:54:56 PST jmonroy@netcom.com (Jesus Monroy Jr) writes: > The paradigim insatanciated concise manner of the Uranimum > algorithm in an integrated discrete state of derivation > causes precision calibration in error magnitude, > if you cut your apple in 1/5 parts. Methamphetamine? Just say No!!! Message 3 in thread From: Jesus Monroy Jr (jmonroy@netcom.com) Subject: Re: [386bsd] Error Theory Newsgroups: comp.unix.bsd, comp.os.386bsd.development View this article only Date: 1993-02-18 03:45:03 PST hackney@moxie.hou.tx.us >> jmonroy@netcom.com (Jesus Monroy Jr) writes: >> >> > The paradigim insatanciated concise manner of the Uranimum >> > algorithm in an integrated discrete state of derivation >> > causes precision calibration in error magnitude, >> > if you cut your apple in 1/5 parts. >> >> Methamphetamine? Just say No!!! Listen, Jack........ I don't care if you don't like my ideas or if you are on some kind of kick trip... but do not miss quote me... You have the pleasure to make an semibalances of logic you like from my statements. BUT DO NOT MISS QUOTE ME. I did not write what you have posted. And I will make that clear. Message 4 in thread From: JAMES R DOYLE (jdoyle@titan.ucs.umass.edu) Subject: Re: [386bsd] Error Theory Newsgroups: comp.unix.bsd, comp.os.386bsd.development View this article only Date: 1993-02-20 00:37:58 PST > Aristotle and the Greeks called it "Logos eritakos", > in English, quibble. We might call it "Eritalogics". > > How can this be implemented in 386BSD you ask?(maybe) > > I am not quite sure, but I can see major parts in my > mind, not the whole. > > Will this require major hardware redesign? RULE NUMBER 1: Never Drink and Drive. RULE NUMBER 2: Never drop acid and log into your account and post something to news. ...... Jim Doyle