Return to BSD News archive
Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!bunyip.cc.uq.oz.au!munnari.oz.au!spool.mu.edu!sol.ctr.columbia.edu!howland.reston.ans.net!agate!violet.berkeley.edu!jkh From: jkh@violet.berkeley.edu (Jordan K. Hubbard) Newsgroups: comp.os.386bsd.bugs Subject: Re: FreeBSD 2.0-Release problems and praise Date: 27 Jan 1995 06:15:42 GMT Organization: University of California, Berkeley Lines: 43 Message-ID: <3ga32e$bvl@agate.berkeley.edu> References: <NICKEL.95Jan27003802@toftum.prz.tu-berlin.de> NNTP-Posting-Host: violet.berkeley.edu In article <NICKEL.95Jan27003802@toftum.prz.tu-berlin.de>, Juergen Nickelsen <nickel@cs.tu-berlin.de> wrote: > - When compiling the kernel, I get spurious compile errors due to a > character 0377 which seems to pop up at *different* places in > vnode_if.h -- another "make" fixes the problem for the moment, and > several other files get compiled, but then it is back again, at a > different place in vnode_if.h, but only *very* rarely in some > other file. (This one puzzles me in particular.) This is bad. It indicates that you're having some sort of cache problem, or something is flakey with your hardware. You should not see this kind of thing, needless to say! > - Some programs crash the system reliably, such as the "screen" > binary from the CD. There are some other programs I don't recall screen is known to be broken. Not sure if it's fixed just yet, but we'll look into it. > - The systems seems a little fragile in other respects, too. Sudden > crashes are moderately common. I didn't investigate them further > yet. Yes, this is not surprising. I've said it a number of times in this group (as have other core team members), but I'll repeat: 2.0, as nice as it is in many ways, is *rough*! We were fairly forced into releasing it due to the legal problems with USL killing off 1.x and us not wanting to go for months and months without anything to offer at all! 2.1, which should be out on March 15th, will represent a MUCH more polished release! I and everyone else on the team greatly look forward to bringing it to all of you! We're very grateful for those who stuck with us through 2.0's teething problems, and the occasional instability, and we hope that 2.1 will justify your faith in us! >I'd like to see a list of the reported and of the already analyzed >bugs so I can see which ones I should have a closer look at. There have been some delays, but the query-pr system should hopefully be up soon. This will allow you to see all reported bugs for 2.0, including those fixed. Jordan