On Sun, Nov 30, 2003 at 03:45:17PM +0100, Matthieu Herrb wrote:
>David Dawes wrote (in a message from Thursday 27)
> >
> > Incidentally related to this is another problem I've run in to. Old
> > FreeBSD X apps, that use a version of libc without IPv6 support, crash
> > when run on a recent system
A related problem is that I was not able to connect to a v4 only X
server running on a machine which happens to have a DNS record,
from a NetBSD or OpenBSD host with IPv6 configured.
The following patch fixes that:
Index: xc/lib/xtrans/Xtranssock.c
==
David Dawes wrote (in a message from Thursday 27)
>
> Incidentally related to this is another problem I've run in to. Old
> FreeBSD X apps, that use a version of libc without IPv6 support, crash
> when run on a recent system when trying to connect to a remote display
> when using our newly b
unsuscribe
--
___
Sign-up for Ads Free at Mail.com
http://promo.mail.com/adsfreejump.htm
___
Devel mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/devel
On Thu, Nov 27, 2003 at 06:33:47PM -0500, David Dawes wrote:
>On Wed, Nov 26, 2003 at 12:27:26PM -0500, David Dawes wrote:
>>With the new IPv6 code, clients connect to IPv4 addresses using AF_INET6
>>with the compatibility address ':::a.b.c.d' where a.b.c.d is the IPv4
>>address.
>>
>>I noticed
On Wed, Nov 26, 2003 at 12:27:26PM -0500, David Dawes wrote:
>With the new IPv6 code, clients connect to IPv4 addresses using AF_INET6
>with the compatibility address ':::a.b.c.d' where a.b.c.d is the IPv4
>address.
>
>I noticed this while trying to figure out why connections from a
>FreeBSD 5.
On Wed, Nov 26, 2003 at 07:33:10PM +0200, Meelis Roos wrote:
>> With the new IPv6 code, clients connect to IPv4 addresses using AF_INET6
>> with the compatibility address ':::a.b.c.d' where a.b.c.d is the IPv4
>> address.
>>
>> I noticed this while trying to figure out why connections from a
>>
> With the new IPv6 code, clients connect to IPv4 addresses using AF_INET6
> with the compatibility address ':::a.b.c.d' where a.b.c.d is the IPv4
> address.
>
> I noticed this while trying to figure out why connections from a
> FreeBSD 5.1 system to another system (via IPv4 addresses) weren't
