From owner-freebsd-hackers Wed Oct 16 12:57:01 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA00746 for hackers-outgoing; Wed, 16 Oct 1996 12:57:01 -0700 (PDT) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id MAA00741 for ; Wed, 16 Oct 1996 12:56:59 -0700 (PDT) Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.7.6/8.6.9) with ESMTP id MAA29590; Wed, 16 Oct 1996 12:54:14 -0700 (PDT) To: Jake Hamby cc: Jeremy Sigmon , freebsd-hackers@FreeBSD.org Subject: Re: FreeBSD 2.2.x release question In-reply-to: Your message of "Wed, 16 Oct 1996 11:50:44 PDT." Date: Wed, 16 Oct 1996 12:54:14 -0700 Message-ID: <29588.845495654@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > 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). Jordan