*BSD News Article 23211


Return to BSD News archive

Xref: sserve comp.os.386bsd.development:1365 rec.arts.poems:36568
Newsgroups: comp.os.386bsd.development,rec.arts.poems
Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!pacbell.com!amdahl!netcomsv!netcom.com!jmonroy
From: jmonroy@netcom.com (Jesus Monroy Jr)
Subject: Status of FDC Driver for *BSD
Message-ID: <jmonroyCFvw53.H6K@netcom.com>
Keywords: FDC BSD 
 
Organization: NETCOM On-line Communication Services (408 241-9760 guest)
Date: Tue, 2 Nov 1993 21:39:02 GMT
Lines: 71

status of FDC driver
 
        My friends,
                        the rumors that BSDI has sent hitmen after me
        has been quite unfounded.  The truth is I am alive and well
        here in RWC.  I have made several promises which I must now
        contend with.   The first is to my self.   I promise not to
        live in a cave and wear clean clothes once in a while.  I also
        promised to speak to the PC Unix users group of the SVNET.
 
                The FDC driver is done.  It works.  It lives with the
        flaws of the components that respond to it.
 
                So why haven't any of you seen the FDC driver?
        Basically the assumptions made about the UNIX and the
        conventions, as to it's operations, continue to hamper our
        channels.
 
                You wonder if I'm just making this up or exaggerate
        for pity.   Far from it.  We've all seen a decline in the
        articles posted to comp.os.386bsd.*, while the C.O.L.* groups
        continue in the bickering.
 
                The crux is this we all expect the PC, this silly
        boxed over-grown Altair, to miraculously accept and behave
        well with all play things.  Well, it doesn't and we know it.
        None the less we (the developers)  are expected to make this
        work, somehow.
 
                I presented the idea, not too long ago, that the RTC
        needs to be fixed.    Many people agreed, but we're still
        here.
 
                Fate is depriving us of the further intention at this
        point.  And the hopeless backwardness of Unix is the detention
        and the convention.   We want 4.3 with the bells and
        whistles of todays' invention, but we are unwilling to make
        the jump.   I related this problem to a friend with the help
        of an old mainframer.  He must of understood the problem
        because the next day he wrote this:
 
                --------------------------------
                        High Priority
 
                High priority, 3 years too late
                in the making the hypothetical state.
                To catch the salmon spawning out of season
                could wash away, untie, anticipate (for any reason)
 
                Bringing up a good point
                Sodom and Gomorrah on the rise
                penetrating every orifice.
                Government computers crippled, paralyzed
                speaking insufficient language.
 
                To achieve the missing link
                could mean disaster -- a silicon prison.
                IBM in sink.
 
                Imminent, inevitable, someday.
                But with political maelstrom
                and the inability to harmonize
                we remain a ghost to the system,
                innocent until proven otherwise.
 
___________________________________________________________________________
Jesus Monroy Jr                                          jmonroy@netcom.com
Zebra Research
/386BSD/device-drivers /fd /qic /clock /documentation
___________________________________________________________________________