Return to BSD News archive
Xref: sserve comp.unix.bsd:12601 comp.os.386bsd.misc:937
Newsgroups: comp.unix.bsd,comp.os.386bsd.misc
Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!elroy.jpl.nasa.gov!decwrl!csus.edu!netcom.com!jmonroy
From: jmonroy@netcom.com (Jesus Monroy Jr)
Subject: Re: Excuse me? [ was Re: Latest release of 386bsd ]
Message-ID: <jmonroyCD4qtC.22n@netcom.com>
Followup-To: comp.unix.bsd,comp.os.386bsd.misc
Organization: NETCOM On-line Communication Services (408 241-9760 guest)
X-Newsreader: TIN [version 1.1 PL8]
References: <JKH.93Sep9212249@whisker.lotus.ie>
Date: Fri, 10 Sep 1993 08:41:35 GMT
Lines: 77
Jordan K. Hubbard (jkh@whisker.lotus.ie) wrote:
: >I'm sorry -- we've had a death in the family and we're not much available
: >right now. The 0.2 update can be obtained by sending a SASE mailer and
: >an error free high-density floppy to: Dr. Dobbs Journal, Tiny 386BSD,
: >411 Borel Avenue, San Mateo, CA. 94402 USA. There is no charge for the
: >service, but if you'd like to send a dollar or more for the kids helped by
: >the Children's Support League (a local charity), it would be most kind. New
: >announcements will be in DDJ and the compuserve DDJ forum (go ddj).
: My sincere sympathies, of course (any differences I may have with the
: Jolitzen stop when it comes to loses of this sort), though I can't
: help but wonder at this "0.2 update". How much can you conceivably
: update on a floppy? It looks to me like some sort of reduced
: functionality kernel ("tiny 386bsd") configured to run off a floppy,
: which is hardly what most people had in mind for the 0.2 release!
: I can't see what use at all this would be. I'm not arguing with the
: practice, since it's certainly generous to be doing free distributions
: like this, I'm merely arguing the utility (or lack thereof) of such a
: release and perhaps wondering if it isn't more of a stalling tactic
: than anything else.
mail jkh@whisker.lotus.ie
Subject: Excuse me? [ was Re: Latest release of 386bsd ]
I pass along my sympathies along also,
but since the Jolitzes are busy I will make some defense.
Please understand I do not speak for them, I just cannot
let this comment pass.
About a month ago at a meeting of the SVNET Bill handed me
a diskette with a binary copy of the new kernel. The intent
at that time was so that people could test the new inners.
The kernel did not, at that time, have any new drivers as
part of it.
I took the diskette how and promptly tested it on a my 386sx.
It did not boot correctly. I immediately called Bill and
asked for the CRC or file size on the diskette. He stated
that he had already removed that copy and was on to a newer
version. He asked me to wait for a new copy that would have
the drivers installed. I agreed to wait.
Some time later a common associate that was helping Bill with
the new kernel ran into me at InterOP. He stated at the time
that Bill had found another large Bug in the memory section
(he wasn't specific) and a new version would be available in a
few *BSD* days.
Well, as you know a *BSD* day can last as long as a week or
more. I have been patient, as have others.
Along a simliar line a person from Stanford University can
and talk to us, at SVNET last night, about new research on
triple caching system and clustering. They were able to show
an increase of 100% with hardware driven triple caches.
These systems were all connected as clusters.
OK... Kids the hot new buzz word this week is "Clustering".
This is a position that Bill and I share. Clustering is
coming and 386BSD is heading in that directions.
I hope my grammer is swell and my speling was Okey.
This completes my comments on this subject.
Comments, discussions, retorts, critiziums, flames, roasting,
Toaster wars are welcome.
Please leave the social remarks to a minimum (I.E., "< 10%").
___________________________________________________________________________
Jesus Monroy Jr jmonroy@netcom.com
/386BSD/device-drivers /fd /qic /clock /documentation
___________________________________________________________________________