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!cs.utexas.edu!uunet!psgrain!m2xenix!agora!rgrimes From: rgrimes@agora.rain.com (Rodney Grimes) Subject: Re: So you say you want an interim release of 386bsd? (What to do?) Message-ID: <C5vrpA.F55@agora.rain.com> Organization: Open Communications Forum References: <1r067g$915@lobster.sid.mcet.edu> <CGD.93Apr19235932@eden.CS.Berkeley.EDU> <C5sCvr.3G1@unx.sas.com> <1r146qINNmbn@hrd769.brooks.af.mil> <CGD.93Apr20124927@gaia.CS.Berkeley.EDU> Date: Thu, 22 Apr 1993 10:27:10 GMT Lines: 77 cgd@gaia.CS.Berkeley.EDU (Chris G. Demetriou) writes: >In article <1r146qINNmbn@hrd769.brooks.af.mil> burgess@hrd769.brooks.af.mil (Dave Burgess) writes: >=>I have the patched 386bsd source tree, albeit not necessarily in the Netbsd >=>structure. IN addition, I have several 'server' processes, including an >=>enterprise wide News Server that I can't just 'dump' to load a new version of >=>an operating system. While tape backups are all well and good; seriously, >=>where do I go from here. Are the underlying disk structures of the 'old' >=>386bsd still there? Has the partition numbering scheme for DOS fdisk >=>changed? Are there other, more insidious questions that need asked that I >=>don't dare utter? >basically, the system as it is now is 386bsd 0.1 + patches, >plus improvements. to the best of my knowledge >"the gang" and i introduced no incompatibilities. >if you'd like to install the new stuff on top of what you've got, >dump your system, get a the binary/source distributions, >and >cat distname.??? | gunzip | (cd / ; tar xvf - ) >or wherever. >you can do the same to get the source tree, and build the sources >into binaries, then install them into the right place when you >feel up to it... >=>I suspect, and hope (fervently hope), that by keeping up with the patchkit, >=>I am actually in a position to be able to change the name on what I already >=>have and press on from there. I can move stuff around, and change source >=>directory names, but restarting from scratch is definitely out of the >=>question. >the patchkit is not going to converge on NetBSD, if i'm not mistaken... Chris is correct, the patch kit will not converge on NetBSD, but I am currently setting up a NetBSD source tree so I can obtain the BUG fixes that are applicable to 386BSD + patchkit 0.2.3 for inclusion patch kit 0.2.4. I will probably continue to do this on a regular bases so that significant bugs that are fixed in NetBSD also get fixed in 386BSD. Note that NetBSD's group is doing the same with each patch kit release and that both teams are cross connected pretty will via lots of mailing lists. >=>Also, what is to become of the FAQ? We have made serious progress on creating >=>a new FAQ (most everyone will see the first three or four sections of it on >=>Wednesday) and need to keep moving. Many of the questions/answer will >=>continue to apply to both the old 386bsd (v0.1) and the new NetBSD for >=>a while. >true. And I would suggest that NetBSD pick up the current FAQ and get some one to maintain it for NetBSD. Or that the current maintainer of the FAQ if he is going to move to NetBSD pass his current work on to some one else to maintain it for 386BSD. >=>The worried maintainer of somebody's FAQ, but not just sure whose!?!? >whosever you want... probably 386BSD's, if you plan to keep it in sync with >0.2 when it comes out... The FAQ is based up on 386BSD0.1 + the patch kits if I am not mistaken, NetBSD is going to diverge from this very rapidly. It would be best to chose one of the two and continue in that direction. But also pass a copy of your work on to some one from the other operating system to maintain it as a seperate FAQ. >-- >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 -- Rod Grimes rgrimes@agora.rain.com 386BSD patchkit coordinator Wish it paid real money! Accurate Automation Company All opinions belong to me and my company!