Date: Mon, 04 Mar 2024 08:54:12 -0800 From: Chris <bsd-lists@bsdforge.com> To: Daniel Braniss <danny@cs.huji.ac.il> Cc: freebsd-hackers <hackers@freebsd.org> Subject: Re: How to add -listen tcp to Xorg Message-ID: <9041d56f25e83e51f2e6c571fc0448ad@bsdforge.com> In-Reply-To: <20240303181000.52322886@ernst.home> References: <543CC273-7A51-4C12-981B-493CA69BE5FE@cs.huji.ac.il> <20240303181000.52322886@ernst.home>
next in thread | previous in thread | raw e-mail | index | archive | help
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. :)
...
DISPLAY NAMES
From the user's perspective, every X server has a display name of the
form:
hostname:displaynumber.screennumber
or
protocol/hostname:displaynumber.screennumber
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):
protocol
The protocol specifies the protocol to use for communication.
Exactly which protocols are supported is platform dependent,
but most commonly supported ones are:
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.
hostname
...
HTH
--Chris
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?9041d56f25e83e51f2e6c571fc0448ad>