*BSD News Article 14765


Return to BSD News archive

Newsgroups: comp.os.386bsd.misc
Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!agate!howland.reston.ans.net!newsserver.jvnc.net!gmd.de!mururoa!veit
From: veit@mururoa.gmd.de (Holger Veit)
Subject: Re: So you say you want an interim release of 386bsd? (What to do?)
Message-ID: <1993Apr20.160109.17689@gmd.de>
Sender: veit@mururoa (Holger Veit)
Nntp-Posting-Host: mururoa
Organization: GMD, Sankt Augustin, Germany
References: <1r067g$915@lobster.sid.mcet.edu> <CGD.93Apr19235932@eden.CS.Berkeley.EDU> <C5sCvr.3G1@unx.sas.com> <1r146qINNmbn@hrd769.brooks.af.mil>
Date: Tue, 20 Apr 1993 16:01:09 GMT
Lines: 67

In article <1r146qINNmbn@hrd769.brooks.af.mil>, burgess@hrd769.brooks.af.mil (Dave Burgess) writes:
|> In article <C5sCvr.3G1@unx.sas.com> sastdr@torpid.unx.sas.com (Thomas David Rivers) writes:
|> >
|> >
|> [...crunch...]
|> >
|> >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?
|> >
|> 
|> Another question is what do I do now?

[..specific problems with secondary software not from the distribution..]

I also asked the same question when I read the NetBSD announcement. Apparently
many people will grab the "new release of 386bsd" just because it is new.
What is missing is a procedure to upgrade from a src01dist+patchkit-0.2.2
to the new release for all persons who do not want to start from scratch.
Besides some reorgs of trees and splitting into separate packages the real
difference to src01+pk022 cannot be so extreme that an upgrade kit is impossible
(it just has to be done).
The situation becomes more interesting with the release of 386bsd-0.2
(even if it looks as if everyone will get a grey beard until it arrives;-)).
In this case we have three releases people can offer patches for:
The 386bsd-0.1+pk0.2.*, NetBSD with its own patchkit possibly, and 386bsd-0.2.
In the latter case we again have the difficulty whether to drop NetBSD and
take the latest and best (?). Probably there will be a set of diffs to upgrade
NetBSD to the 0.2 level, or vice versa (?).
So what?
Personally I would wait for 0.2, but the question is whether many people 
are as patient, and it is really possible that NetBSD will become the currently 
most stable BSD available (if upgraded with GNU software). 0.2 will be
(according to the numbering scheme) an experimental system with possibly 
several new bugs (and old corrected, of course). On the other hand, this brings
386bsd back into the research area that has been left when it was entirely
released to the real world (and not requiring to adopt any real world standard
is not the worst for experimenting with novel approaches). 

BTW: I just saw the announcement of pk-0.2.3, and wonder if this brings my system
to NetBSD. 

Maybe the patchkit people and the NetBSD people (who are mainly the same group)
comment some more about the expected future.

Holger

|> TSgt Dave Burgess
|> NCOIC AL/Management Information Systems Office
|> Brooks AFB, TX

-- 
         Dr. Holger Veit                   | INTERNET: Holger.Veit@gmd.de
|  |   / GMD-SET German National Research  | Phone: (+49) 2241 14 2448
|__|  /  Center for Computer Science       | Fax:   (+49) 2241 14 2342
|  | /   P.O. Box 13 16                    |    Three lines Signature space
|  |/    Schloss Birlinghoven              |    available for rent. Nearly
         DW-5205 St. Augustin, Germany     |    unused, good conditions