Return to BSD News archive
Xref: sserve comp.os.os2.programmer.misc:12151 comp.os.linux.development:13233 comp.os.minix:24049 comp.os.mach:4074 comp.periphs:5976 comp.unix.bsd:14552 comp.unix.pc-clone.32bit:6858 comp.os.386bsd.development:2378 comp.sys.ibm.pc.hardware.storage:8708 comp.sys.ibm.ps2.hardware:7171
Newsgroups: comp.os.os2.programmer.misc,comp.os.linux.development,comp.os.minix,comp.os.mach,comp.periphs,comp.unix.bsd,comp.unix.pc-clone.32bit,comp.os.386bsd.development,comp.sys.ibm.pc.hardware.storage,comp.sys.ibm.ps2.hardware
Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!msuinfo!netnews.upenn.edu!news.amherst.edu!news.mtholyoke.edu!uhog.mit.edu!news.kei.com!yeshua.marcam.com!charnel.ecst.csuchico.edu!csusac!csus.edu!netcom.com!jmonroy
From: jmonroy@netcom.com (Jesus Monroy Jr)
Subject: Call for 386BSD Rel.1.0 SIG (Special Interest Group)
Message-ID: <jmonroyCuFvqp.BKv@netcom.com>
Followup-To: comp.os.386bsd.development
Keywords: 386bsd release 1.0 SIG
Organization: NETCOM On-line Communication Services (408 261-4700 guest)
Date: Fri, 12 Aug 1994 20:32:49 GMT
Lines: 155
-------------------------------
Call for Special Interest Group
Call for Special Interest Group
Call for Special Interest Group
-------------------------------
OVERVIEW
--------
In the beginning there was BASIC and there was Bill!
And then Bill said unto the users,
Let there be DOS, and there was DOS
Let there be CD-ROM, and there was CD-ROM
Let there be Mice, and there were mice
Let there be Windows for mice to run in, and there were.
It's all very BASIC you see
McNealy is saving Jobs,
Sculley is out of the job, and
Hewlett-Packard is giving us the Wave.
Luckily, Cray is still Super,
DEC is doing the Alpha,
Wang is no longer in the Lab, and
Philips is just one screw loose.
AT&T has called it quits (or so they say),
Xerox still can't 'C', for the life of me,
Kodak is back into the picture, but is no longer Interactive,
Novell had to Unix, just to be Word Perfect,
And IBM has bitten the Apple in a RISCy sort of way.
To make this perfectly clear,
To be PC the master/slave relationship is now client/server.
So now NT is out and Chicago, Cairo, and OLE (2.0) are on the the way.
Sure it's great, unless your OPEN, COSE or ready to P-P-P.
Mach my words, OSays I! Enterprise-wide or Right-Size,
the biggest GUI still comes from Nintendo, and
whether you ISDN (via a baby bell) or not,
WAN you least expect it Bill will turn the boat.
-----------------------------------------
A call for a 386bsd release 1.0 SIG group
A call for a 386bsd release 1.0 SIG group
A call for a 386bsd release 1.0 SIG group
-----------------------------------------
In the years that have past, one might consider
casualty to be a detrimental commodity; it is not.
Foul words, sharp metaphors, colourful reflections and
attributes for change bring us volte-face. Even today
my considerations are how many more sleepless vigils
will be necessary.
Taking everything into account would be an abnormal
expenditure of time; I can only reflect on what might be
considered good. So today, I call upon you to appraise
the advent of release 1.0.
Official - no less, this version promises more!
"What", I can not say. None the less, the i386 (and family)
are quickly becoming the de facto standard for personal
computer development. This and the accomplishments of fast
BUSes (PCI and VESA) have determined the uses and
applications that we must adapt to.
Looking more toward the future, parallel and 64-bit
processors are our next paradigms to consider. Yet at the
same time -- we are keep constant with a common neumonic set.
This is not to say that other ideas such as RISC, AI and
robotics will not come into our perspective, it is just
that as a purely volunteer effort our resources are
constrained.
In conclusion, we must assume that our best guesses
are only confirmable by their creativeness -- which is a factor
of our science.
What is 386BSD release 1.0?
---------------------------
386BSD release 1.0 is THE OFFICIAL release from
William and Lynn Jolitz for the computer science community.
Rumored to be using a Tardis in his development effort,
Bill state plainly, "This is AT&T source free."
Vaporware.. is term we use to describe the undelivered
promise. Many companies (groups, corporations, individuals,
clusters, cliques) are considering the "next step" (no pun
intended). Indeed, some fantasies consist of the belief that
the game is played with "wild cards" and "the queen of
spades".
Certainly, one or two of you are wondering, what the
hell I'm babbling about. The winter of '91 was time I decide
to join in the work for 386bsd. Certainly, like the next
person I have my had share of disappointments, but I believe
I have put my differences aside.
386BSD is the hope that what is familiar to us will
return. 386BSD is more than just another effort by Bill and
Lynn. It is a new direction. It is a turn -- to counter
indifference.
Why a SIG?
------------
Everyone-of-us is believing that there is something
in this "*BSD" for us. There is.
SIGs in the past had been a mecca, have you, for
similar "types" to gather. Not just for consuling, but for
a locale to conclude that the decision "to collect resources
here" is correct. I still don't own a HP logic analyzer,
but I still have the dialect to say, "What can I do?"
This means that a forum must develop where new
ideas can be discussed without the bicker of despise.
I will ask that comp.os.386bsd.*, and others, consider
my proposition. After all -- this is the day when we must
survive by our minds, not our physical abandonment.
The aim here is, of course, to put comp.os.386bsd.* back
on track.
I ask for your help.
To aid in the recover, I ask that someone start a
newsletter. Not just any newsletter, but letter for
*BSDer's.
When will you hear more?
------------------------
August the 17th is said the day to be William and Lynn
Jolitz will discuss their new strategy for 386bsd. We will
meet at Sun MicroSystems in building 6.
Your presence is requested.
More announcements will follow.
--
Jesus Monroy Jr jmonroy@netcom.com
Zebra Research
/386BSD/device-drivers /fd /qic /clock /documentation
___________________________________________________________________________