Date: Sun, 17 Nov 2002 16:51:47 -0400 (AST) From: "Marc G. Fournier" <scrappy@hub.org> To: Bill Moran <wmoran@potentialtech.com> Cc: kalts@estpak.ee, Eugene Grosbein <eugen@grosbein.pp.ru>, Kenneth Mays <kmays2000@hotmail.com>, <freebsd-stable@FreeBSD.ORG> Subject: Re: -STABLE was stable for long time (Re: FreeBSD: Server or Desktop OS?) Message-ID: <20021117164707.T23359-100000@hub.org> In-Reply-To: <3DD7E3D9.1040902@potentialtech.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 17 Nov 2002, Bill Moran wrote:
> Vallo Kallaste wrote:
> > On Sun, Nov 17, 2002 at 10:49:45PM +0700, Eugene Grosbein
> > <eugen@grosbein.pp.ru> wrote:
> >
> >
> >>>Your question brings up an issue that was talked about several
> >>>times, and it was addressed in the docs and the newsgroup.
> >>>-STABLE is an engineering development branch that is 'more
> >>>stable' than -CURRENT, but not more stable than -RELEASE.
> >>>-STABLE is NOT for end users/customers for official production
> >>>use (i.e. do so at your own risk).
> >>
> >>I wonder why no one says that -STABLE really WAS stable and WAS intended
> >>for end users less than 2 years ago. Moreover, Hanbook said you
> >>need -STABLE if you are using FreeBSD in production environment
> >>and you need stability, Handbook said it even 15 months ago.
> >>And it has been assetring so for long time, that's where the name
> >>of this branch came from. Anyone can see that in CVS.
> >
> > Exactly my point. The stability of FreeBSD is slowly but definitely
> > deteriorating. The more the OS is gaining complexity, more bugs will
> > be introduced or old bugs surface. As I understand it's very hard to
> > support ever changing hardware, growing needs of userbase and hold
> > the OS quality (in this context stability) on the track.
>
> I disagree.
> I think the impression of what could be done with -STABLE (in the
> developers eyes) has changed because of the RELENG_4_7 branches.
> Since anyone interested in production stability should track that
> branch instead.
What's to track? Nothing happens on that branch ... I just CVSup'd
RELEASE, followed by RELENG_4_7 and the only changes were pretty much
related to the latest BIND vulnerabilities ...
Here's all that has changed in 4_7:
Updating collection src-all/cvs
Edit src/Makefile.inc1
Edit src/UPDATING
Edit src/contrib/bind/CHANGES
Edit src/contrib/bind/bin/named/db_defs.h
Edit src/contrib/bind/bin/named/db_sec.c
Edit src/contrib/bind/bin/named/ns_defs.h
Edit src/contrib/bind/bin/named/ns_ncache.c
Edit src/contrib/bind/bin/named/ns_req.c
Edit src/contrib/bind/bin/named/ns_resp.c
Edit src/contrib/bind/lib/nameser/ns_name.c
Edit src/contrib/bind/lib/nameser/ns_samedomain.c
Edit src/contrib/tar/src/extract.c
Edit src/contrib/tar/src/misc.c
Edit src/crypto/heimdal/kadmin/version4.c
Edit src/crypto/kerberosIV/kadmin/kadm_ser_wrap.c
Edit src/kerberos5/include/version.h
Edit src/kerberosIV/include/version.h
Edit src/lib/libc/net/gethostbydns.c
Edit src/lib/libc/net/getnetbydns.c
Edit src/release/doc/de_DE.ISO8859-1/errata/article.sgml
Edit src/release/doc/de_DE.ISO8859-1/hardware/alpha/article.sgml
Edit src/release/doc/de_DE.ISO8859-1/hardware/alpha/proc-alpha.sgml
Edit src/release/doc/de_DE.ISO8859-1/hardware/common/dev.sgml
Edit src/release/doc/de_DE.ISO8859-1/hardware/i386/article.sgml
Edit src/release/doc/de_DE.ISO8859-1/hardware/i386/proc-i386.sgml
Edit src/release/doc/de_DE.ISO8859-1/installation/alpha/article.sgml
Edit src/release/doc/de_DE.ISO8859-1/installation/i386/article.sgml
Edit src/release/doc/de_DE.ISO8859-1/readme/article.sgml
Edit src/release/doc/de_DE.ISO8859-1/relnotes/alpha/article.sgml
Edit src/release/doc/de_DE.ISO8859-1/relnotes/common/new.sgml
Edit src/release/doc/de_DE.ISO8859-1/relnotes/i386/article.sgml
Edit src/release/doc/de_DE.ISO8859-1/share/sgml/catalog
Edit src/release/doc/de_DE.ISO8859-1/share/sgml/release.dsl
Delete src/release/doc/de_DE.ISO8859-1/share/sgml/release.ent
Edit src/share/examples/cvsup/standard-supfile
Edit src/sys/conf/newvers.sh
Finished successfully
20021113: p2 FreeBSD-SA-02:43.bind
Correct name server vulnerabilities.
20021023: p1 FreeBSD-SA-02:40.kadmind
Correct bug in the tar(1) contains_dot_dot function allowing
files to be extracted outside the intended directory tree.
Correct kadmind buffer overflow.
20021010:
FreeBSD 4.7-RELEASE.
Purely security vulnerabilities ... no 'critical patches' ... I would
consider most anything related to the VM subsystem to be 'critical', at
the very least ...
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20021117164707.T23359-100000>