*BSD News Article 15844


Return to BSD News archive

Newsgroups: comp.os.386bsd.development
Path: sserve!newshost.anu.edu.au!munnari.oz.au!network.ucsd.edu!swrinde!gatech!howland.reston.ans.net!agate!boulder!ucsu!rintintin.Colorado.EDU!galbrait
From: galbrait@rintintin.Colorado.EDU (GALBRAITH JOHN)
Subject: Does anybody _REALLY_ know how to write a QIC80 driver?
Message-ID: <1993May10.033324.2975@ucsu.Colorado.EDU>
Summary: All I really wanted was a tape driver
Keywords: QIC80, sometime soon
Sender: news@ucsu.Colorado.EDU (USENET News System)
Nntp-Posting-Host: rintintin.colorado.edu
Organization: University of Colorado, Boulder
Date: Mon, 10 May 1993 03:33:24 GMT
Lines: 41

I am one of the ones who signed up with jmonroy when he first showed
up months ago to work on a QIC80 device driver.  Now, 3 months later,
there is no sign of any kind of driver - just a bunch of flames!! Jmonroy
does not even appear to be around anymore...  Almost like he was some
kind of mole set on sabatoging the effort.

So, lets forget about jmonroy and actually write a driver.  Questions:

1.  What is up with patch01001?  Is this a temporary floppy driver to be
	replaced by jmonroy (yeah, right) or a solid piece of code?  In
	otherwords, is it good enough to use as the basis of a QIC80 driver?

2.  The last I heard, jmonroy had the support of the Jolitzes.  Is this still
	true?  Does it really matter? Do they know something that we don't?

My summer vacation is coming up, so I am willing to volunteer much time
for this project.  It has to be well spent time, on stuff other than 
QIC NEWS.  I will even start out as being some kind of coordinator, although
it would be better for somebody with more experience to take it over 
after a while.

The last time I posted something like this, I recieved some very encouraging
responses of some really smart sounding people.  For instance: Dave Burgess
(now our FAQ coordinator) already has a HUGE start on the error correction
code as well as other areas.  I think that the expertise to write the
driver is available on this newsgoup!

So, if there is interest in starting a new QIC80 development group that
is actually going to do something NOW, please send me mail, and I will
start a list of interested people.  Also, lets see some discussion on
real QIC80 issues.  What are the stumbling blocks that we should try
to solve first?  Would people like to see a mailing list?

BTW, I _can't_ do this all myself because I don't know how.  I _do_ feel 
like I can make significant contributions however.  So please, sign up!

john galbraith
galbrait@rintintin.colorado.edu