Return to BSD News archive
Newsgroups: comp.unix.bsd Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!bunyip.cc.uq.oz.au!munnari.oz.au!spool.mu.edu!howland.reston.ans.net!agate!library.ucla.edu!csulb.edu!csus.edu!netcom.com!jmonroy From: jmonroy@netcom.com (Jesus Monroy Jr) Subject: Re: PCMCIA support on FreeBSD/NetBsd Message-ID: <jmonroyCuwurq.Gur@netcom.com> Organization: NETCOM On-line Communication Services (408 261-4700 guest) X-Newsreader: TIN [version 1.2 PL1] References: <328pt4$pbp@flipper.rsmas.miami.edu> <JKH.94Aug10115802@freefall.cdrom.com> <MICHAELV.94Aug21043941@MindBender.HeadCandy.com> Date: Mon, 22 Aug 1994 00:31:02 GMT Lines: 86 Michael L. VanLoon (michaelv@MindBender.HeadCandy.com) wrote: : In article <jmonroyCuv41G.2rK@netcom.com> jmonroy@netcom.com (Jesus Monroy Jr) writes: : : ...And after a decent interval, what do we find? 386BSD 1.0 is : : unencumbered because there is no such product. : As of this time, 386bsd release 1.0 does not support : PCMCIA, nor does it support PCI. : However, any making submission to Bill Jolitz : about either bus will be consider, as well as : their code. :-) : And, why should we submit code to Bill so he can consider : incorporating it, without any attribution of the author, or without : any hint of its status for another year and a half, when such code is : already running in NetBSD, today? : Well, Mr Vanloomm-a-loom, if you want an answer next time. Try less run-on sentences and a few less inferences to logic.... and not your usual run-on dribble. : And, why should we submit code to Bill so he can consider : incorporating it, : Well, as I believe you don't speak for everyone and perhaps this is a question that you'd like answered, let's continue. If you believe that your code might be of some advantage to users, then it is concievable (sp?) that you might want to port your "wares" to as many platforms as possible. In the past, Bill's release have been very compliant with *BSD style and flavor. So for the highest degree of protability one might consider porting one's code to 386BSD Release 1.0. : without any attribution of the author, : Your commnet about attribution are quite incorrect, they are false, and to date most people making claims as such have been proven by electronic record that such claims were incorrect. My premise is that, perhaps, some code you submitted was substandard or not documented professional manner or your just a puzt. : or without : any hint of its status for another year and a half, : If your code was of any consequence, you would have received some e-mail from Bill or Lynn. And if you did not and your code was used by them you will receive proper attribution. : when such code is : already running in NetBSD, today? : Mr. VanLoon, Your concluding run-on sentence is the most illogical statement to date. By all means if your code is running on NetBSD it's worth is known, but if your code (or anyone's for that matter) is in 386bsd Release 1.0 there is no way hell you can tell me it's there, unless maybe you have privy information from Bill, Lynn or the author of such software, which it seems you don't. Q.E.D. : Just curious... seems to me that Bill should be looking to actively : *pursue* code for this, since he's so far behind the times. That way : he won't be *another* full generation behind the other BSD's when his : next version comes out. : Mr. VanLoon, your proposition is the silliest yet. -- Jesus Monroy Jr jmonroy@netcom.com Zebra Research /386BSD/device-drivers /fd /qic /clock /documentation ___________________________________________________________________________