Bob Johnson wrote:
>
> On Saturday 16 November 2002 08:19 pm, Lefteris Tsintjelis wrote:
> > It sure is misleading. Why is it called -stable then? You would expect
> > to stand up to its name.
>
> It is called -stable because once upon a time it was intended to
> BE stable. Commits to -stable we
Green!
A.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message
On Mon, Nov 18, 2002 at 01:02:55AM +0100, Thomas Seck wrote:
> * Marc G. Fournier ([EMAIL PROTECTED]):
>
> > On Sun, 17 Nov 2002, Thomas Seck wrote:
> >
> >> You have chosen to maintain systems which stretch FreeBSD to its limits
> >> and uncover bugs lurking in the code. This is great. But you c
* Marc G. Fournier ([EMAIL PROTECTED]):
> On Sun, 17 Nov 2002, Thomas Seck wrote:
>
>> You have chosen to maintain systems which stretch FreeBSD to its limits
>> and uncover bugs lurking in the code. This is great. But you cannot do
>> so on the one hand and refuse to face the administrative work
> You have chosen to maintain systems which stretch FreeBSD to its limits
> and uncover bugs lurking in the code. This is great. But you cannot do
> so on the one hand and refuse to face the administrative work on the
> other hand.
And this is not a FreeBSD problem either - if you are doing stres
* Marc G. Fournier ([EMAIL PROTECTED]):
> 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 ...
The "security branches" are fortunately a very slowly moving targe
On Sat, 16 Nov 2002, Marc G. Fournier wrote:
> Over the past couple of months, I've been starting to wonder if the
> Quality of FreeBSD's -STABLE branch has been deteriorating, to the point
> that trusting it for any sort of "loaded server" environment is coming
> into question ...
[snip]
> Am I
Over the past couple of months, I've been starting to wonder if the
Quality of FreeBSD's -STABLE branch has been deteriorating, to the point
that trusting it for any sort of "loaded server" environment is coming
into question ...
I have two servers sitting at Rackspace right now, both running Tya
