Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 16 Oct 1996 15:08:27 -0700
From:      Julian Elischer <julian@whistle.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:  <32655CDB.59E2B600@whistle.com>
References:  <29588.845495654@time.cdrom.com>

next in thread | previous in thread | raw e-mail | index | archive | help
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)

real work (TM)

> and people running
> with it as their /dev still show an unfortunate tendency to crash
> a lot,

that's actually not true at all.

> so no.
personally I don't think persistance is of any importance
but I hear the crowd yelling for their placebo's so I will do it some
time.. but it tripples the complexity of the filesystem.

> 
> > 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
> 
sure..

> 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).
> 
we're using 2.2 heavily..
we have 3 outstanding problems
one of which might be solved but I haven't checked..

>                                         Jordan



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?32655CDB.59E2B600>