Date: Thu, 17 Oct 1996 12:28:10 +0100 (BST) From: Doug Rabson <dfr@render.com> To: "Jordan K. Hubbard" <jkh@time.cdrom.com> Cc: Jake Hamby <jehamby@lightside.com>, Jeremy Sigmon <jsigmon@www.hsc.wvu.edu>, freebsd-hackers@FreeBSD.org Subject: Re: FreeBSD 2.2.x release question Message-ID: <Pine.BSF.3.95.961017121620.10204E-100000@minnow.render.com> In-Reply-To: <29588.845495654@time.cdrom.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 16 Oct 1996, Jordan K. Hubbard wrote: > > 1) More pounding on devfs (is it planned as a standard feature installed > > by sysinstall, or more of an optional feature installed by hand?) > > The latter. AFAIK, Julian still hasn't solved the persistance problem > (though we discussed a number of different ways it could be done > fairly trivially and I don't know what's holding him up) and people running > with it as their /dev still show an unfortunate tendency to crash a lot, > so no. > > > So the way I see things (and since I'm not a core team person, this is > > just my opinion), FreeBSD 2.2 could easily be released by Christmas, or > > even the end of November. I think if the core team puts the squeeze on > > NFS weirdness seems to be the #1 monster under the bed with 2.2 - > might some of you folks out there with multiple machines be willing to > assist John and Doug with some stress-testing? If you can find and > reproduce bugs yourselves, that's even better (e.g. they need someone > to help play QA team on NFS). I am in a slightly dodgy position here as the 'maintainer' of our NFS code. I don't run NFS much here. I spend most of my time running my employer's 'operating systems' and even when I do spend a bit of time on FreeBSD, I only have one machine which can possibly run -current. I am perfectly willing to attempt to find and fix problems in the NFS system but a lot of the time I simply *can't* reproduce the problems that people are seeing. It would be extremely helpful if those of you who have NFS problems to actually get your hands into the code and figure out what is happening in your environment. I know this is not always possible but certainly some of you can. A good example here is Hidetoshi Shimokawa who had a problem with write performance, got into the code and found a solution. This has two benefits: better performance for NFS and one more person who understands (some of) how this monster works. -- Doug Rabson, Microsoft RenderMorphics Ltd. Mail: dfr@render.com Phone: +44 171 734 3761 FAX: +44 171 734 6426
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.95.961017121620.10204E-100000>