*BSD News Article 14761


Return to BSD News archive

Newsgroups: comp.os.386bsd.misc
Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!elroy.jpl.nasa.gov!usc!howland.reston.ans.net!gatech!concert!sas!mozart.unx.sas.com!torpid.unx.sas.com!sastdr
From: sastdr@torpid.unx.sas.com (Thomas David Rivers)
Subject: Re: So you say you want an interim release of 386bsd? (What to do?)
Sender: news@unx.sas.com (Noter of Newsworthy Events)
Message-ID: <C5sCvr.3G1@unx.sas.com>
Date: Tue, 20 Apr 1993 14:14:14 GMT
References: <1qvpc9$1e8@agate.berkeley.edu> <1r067g$915@lobster.sid.mcet.edu> <CGD.93Apr19235932@eden.CS.Berkeley.EDU>
Nntp-Posting-Host: torpid.unx.sas.com
Organization: SAS Institute Inc.
Lines: 57

In article <CGD.93Apr19235932@eden.CS.Berkeley.EDU> cgd@eden.CS.Berkeley.EDU (Chris G. Demetriou) writes:
>In article <1r067g$915@lobster.sid.mcet.edu> johnj@lobster.sid.mcet.edu (John Jackson) writes:
>>Does NetBSD fix silo overflows?
>
>a slightly better question would be:
>does it fix the serial driver.
>
>the answer to that is: right now, it's the stock
>serial driver plus patches.
>
>incorporation of Bruce Evans' interrupt, NPX, and
>serial driver code will probably happen
>by the first few source diff releases, i.e. probably
>within a month or so.
>
>
>
>
>chris
>--
>Chris G. Demetriou                                    cgd@cs.berkeley.edu
>
>   "386bsd as depth first search: whenever you go to fix something you
>       find that 3 more things are actually broken." -- Adam Glass



Well, while I applaud the effort generalizing 386BSD to NetBSD, and 
(hopefully) having it stay relatively close to whatever becomes
of BSD (not necessarilly the newest, most nifty-keen operating system
ideas that someone thought of last night - but not the drudgey old
Sys V 3.2 stuff...) - I'm now very confused.  I really like the idea
of divorcing from 386bsd; for all the reasons mentioned in the NetBSD
announcement, but just don't know where to go from here.

We now have at the moment; "another" 386BSD.   Should I abandon
my current sources and switch to NetBSD?  Will the patchkit, etc...
be moved from 386bsd to NetBSD - what is to be done?

We probably should reach a consensus about how our collective support
is to be applied.  Personally, I would like to go with NetBSD, as that
offers a set of goals which more closely matches my own.

Thus, I suggest we begin generating patch sets against that, and
encourage everyone to move over to NetBSD.

What do you think?

    - Uncertain and confused -
     - Dave Rivers -

    (sastdr@unx.sas.com (work))
    (rivers@ponds.uucp  (home))


-- 
UPDATE ALL INFORMATION AND POD INTO COSMOS - Federal Express