On Wed, 11 Jul 2007 09:42:22 -0400, Stephen Clark wrote
> viper wrote:
>
> >On Tue, 10 Jul 2007 15:59:46 -0400, Stephen Clark wrote
> >
> >
> >>Hello List,
> >>
> >>I posted a while ago that our testers of our network appliance were
> >
Hi all.
I am just want ask question only out of curiosity.
Are there any reasons why a file src/sys/netinet/in_pcb.c(rev. 1.165.2.6) is
not included to RELEASE_6_2?
What a kind of race condition closing that revision.
Thanks to help me :-)
[Vladimir]
Hi!
Again NULL pointer in m_copyx.
Looks like similar to PR kern/108963.
Are there any suggestions or ideas?
___
Best regards,
Vladimir
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Alexey Sopov
Sent: Tuesday, February 20, 2007
t block on the socket zone limit during the socket()
syscall which can lock up a system otherwise; instead, return
ENOBUFS as documented, which matches the FreeBSD 4.x behavior."
As far as me is concerned, panics disappeared, but there is they appeared freeze
__
days"
Today is 29 March 2007.
Who can MFC that rev. to STABLE_6.
Thanks.
__
Best regards,
VipeR
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail
Hi,
I had a similar query about just this very thing when 4.4 just went into
release mode and Warner Losh had replied to the post saying that UPDATING
in different tags (namely RELENG_4 and RELENG_4_4) are maintained
independantly of each other, so one UPDATING could differ to the other.
Makes sen