Re: 4.1 STABLE broken since today!

2000-08-31 Thread Brian Fundakowski Feldman
On Thu, 31 Aug 2000 [EMAIL PROTECTED] wrote: > 1. The value of diff in chgsbsize was always positive > (unsigned - unsigned results in an unsigned value). > This causes bogus values in ui_sbsize. > > 2. chgsbsize was not called as when the 3-way tcp handshake > for incoming connect

STABLE once again stable...

2000-08-31 Thread Gary Kline
The news that was posted this morning was correct. 4.1 is back. I just finished a complete upgrade from 4.0 to 4.1 that was entire remote. gary -- Gary D. Kline [EMAIL PROTECTED] Public service Unix To Unsubscribe: send mail to [EMAIL PROTECTED] with "uns

Re: downgrading to 3.4

2000-08-31 Thread Salvo Bartolotta
>> Original Message << On 8/31/00, 10:21:22 PM, "Chad R. Larson" <[EMAIL PROTECTED]> wrote regarding Re: downgrading to 3.4: > As I recall, Jim Mock wrote: > > On Thu, 31 Aug 2000 at 11:00:31 -0700, Alfred Perlstein wrote: > >> * Jim Mock <[EMAIL PROTECTED]> [00

Re: XFREE86_VERSION

2000-08-31 Thread Andrew Reilly
On Mon, Aug 28, 2000 at 01:23:11AM +0300, Roman Shterenzon wrote: > Hello, > There's this variable that some ports rely on: XFREE86_VERSION > For example the Mesa port. > So, because I've installed the XFree86-4 from ports (it supports my > graphics card) I set it in the /etc/make.conf as: > XFRE

Re: downgrading to 3.4

2000-08-31 Thread Chad R. Larson
As I recall, Jim Mock wrote: > On Thu, 31 Aug 2000 at 11:00:31 -0700, Alfred Perlstein wrote: >> * Jim Mock <[EMAIL PROTECTED]> [000831 10:17] wrote: >>> On Thu, 31 Aug 2000 at 18:06:40 +0100, Theo PAGTZIS wrote: Hi Would there be a problem to downgrade to 3.4 stable from the >>>

subscribe...

2000-08-31 Thread Derrick
auth 254c24bc subscribe freebsd-stable [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message

Re: downgrading to 3.4

2000-08-31 Thread Alfred Perlstein
* Jim Mock <[EMAIL PROTECTED]> [000831 11:08] wrote: > On Thu, 31 Aug 2000 at 11:00:31 -0700, Alfred Perlstein wrote: > > * Jim Mock <[EMAIL PROTECTED]> [000831 10:17] wrote: > > > On Thu, 31 Aug 2000 at 18:06:40 +0100, Theo PAGTZIS wrote: > > > > Hi > > > > > > > > Would there be a problem to

Re: downgrading to 3.4

2000-08-31 Thread Jim Mock
On Thu, 31 Aug 2000 at 11:00:31 -0700, Alfred Perlstein wrote: > * Jim Mock <[EMAIL PROTECTED]> [000831 10:17] wrote: > > On Thu, 31 Aug 2000 at 18:06:40 +0100, Theo PAGTZIS wrote: > > > Hi > > > > > > Would there be a problem to downgrade to 3.4 stable from the > > > sources from the existing

Re: downgrading to 3.4

2000-08-31 Thread Alfred Perlstein
* Jim Mock <[EMAIL PROTECTED]> [000831 10:17] wrote: > On Thu, 31 Aug 2000 at 18:06:40 +0100, Theo PAGTZIS wrote: > > Hi > > > > Would there be a problem to downgrade to 3.4 stable from the > > sources from the existing 4.1 Stable? > > > > I try to cvsup with RELENG_3_4 but I do not see any re

Re: downgrading to 3.4

2000-08-31 Thread Jim Mock
On Thu, 31 Aug 2000 at 18:06:40 +0100, Theo PAGTZIS wrote: > Hi > > Would there be a problem to downgrade to 3.4 stable from the > sources from the existing 4.1 Stable? > > I try to cvsup with RELENG_3_4 but I do not see any receipt of > sources You want RELENG_3. - jim -- jim mock <[EMAIL

Re: stable status.... still hosed (no more)

2000-08-31 Thread Arno J. Klaassen
Arnout Boer <[EMAIL PROTECTED]> writes: > On Thu, Aug 31, 2000 at 10:07:12AM +0100, Steve O'Hara-Smith wrote: > > > Checking procedure is simple: load kernel, boot, then telnet from outside. > > ssh from outside will do it too (as I discovered this morning). > > ANy network connection will d

downgrading to 3.4

2000-08-31 Thread Theo PAGTZIS
Hi Would there be a problem to downgrade to 3.4 stable from the sources from the existing 4.1 Stable? I try to cvsup with RELENG_3_4 but I do not see any receipt of sources Theo To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message

Re: 4.1 STABLE broken since today!

2000-08-31 Thread Kent Stewart
[EMAIL PROTECTED] wrote: > > > > > As commented on freebsd-current, this seems to have hit the -CURRENT > > kernel at the same time. Someone should *not* have MFC'd some change > > immediately. Not clear who yet. I'm suspicious of the sbappend() changes > > that have been going in recently.