Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 5 Mar 2024 07:22:13 +0200
From:      Daniel Braniss <danny@cs.huji.ac.il>
To:        Chris <bsd-lists@bsdforge.com>
Cc:        freebsd-hackers <hackers@freebsd.org>
Subject:   Re: How to add -listen tcp to Xorg
Message-ID:  <322E51C0-3105-4982-B10A-19F6AF3BB3E4@cs.huji.ac.il>
In-Reply-To: <9041d56f25e83e51f2e6c571fc0448ad@bsdforge.com>
References:  <543CC273-7A51-4C12-981B-493CA69BE5FE@cs.huji.ac.il> <20240303181000.52322886@ernst.home> <9041d56f25e83e51f2e6c571fc0448ad@bsdforge.com>

next in thread | previous in thread | raw e-mail | index | archive | help


> On 4 Mar 2024, at 18:54, Chris <bsd-lists@bsdforge.com> wrote:
>=20
> On 2024-03-03 09:10, Gary Jennejohn wrote:
>> On Sun, 3 Mar 2024 16:46:46 +0200
>> Daniel Braniss <danny@cs.huji.ac.il> wrote:
>>> Hi,
>>> In the past Xorg  listen on port 6000 was the default, now it?s =
disabled.
>>> Some years ago I changed this behavior back to enable, but now
>>> I can?t find my patch, and looking at the latest sources is mind =
boggling, trying to
>>> set listen tcp is not working.
>>> Any help is most welcome,
>>> 	Danny
> man 7 X
> should provide for your needs. :)
i didn=E2=80=99t have xorg-docs installed, so I missed that :-)
in any case problem solved,
	thanks
		danny

> ...
> DISPLAY NAMES
>       =46rom the user's perspective, every X server has a display name =
of the
>       form:
>=20
>              hostname:displaynumber.screennumber
>       or
>              protocol/hostname:displaynumber.screennumber
>=20
>       This information is used by the application to determine how it =
should
>       connect to the server and which screen it should use by default =
(on
>       displays with multiple monitors):
>=20
>       protocol
>               The protocol specifies the protocol to use for =
communication.
>               Exactly which protocols are supported is platform =
dependent,
>               but most commonly supported ones are:
>=20
>               tcp     TCP over IPv4 or IPv6
>               inet    TCP over IPv4 only
>               inet6   TCP over IPv6 only
>               unix    UNIX Domain Sockets (same host only)
>               local   Platform preferred local connection method
>               If the protocol is not specified, Xlib uses whatever it
>               believes is the most efficient transport.
>=20
>       hostname
> ...
>=20
> HTH
>=20
> --Chris




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?322E51C0-3105-4982-B10A-19F6AF3BB3E4>