[vishnu]

So I know I've asked this question before, but I've never received an answer that worked. Years ago it used to spout an error message that said "xsgi extension missing on host," but now it just says "Can't open display."

So here's the story: I do "xhost +" on my Linux computer, it responds "access control disabled, clients can connect from any host"

Okay, so far so good. So I telnet into my Octane, and do either one of two things (the shell on my Octane is BASH, as set in my ~/.profile):

export DISPLAY=starhunter:0.0 - (starhunter is my Linux computer's name, and yes it is in my Octane's host file). Or this:

export DISPLAY=10.4.0.103:0.0 - (that's my Linux computer's IP address on my LAN).

So let's test that last one:

echo $DISPLAY
10.4.0.103:0.0

So that's exactly what you'd expect.

So if anyone ALREADY knows how to do this, please respond. If you DON'T know how to do this, please ignore, I've already done enough Internet research (to no result) that no one else should bother to repeat. I'm sure I missed something obvious, just call me unobservant. 😆

[fleedwood]

Two ideas

- does your X on the Linux side has tcp enabled (-listen tcp)
- if you have firewalling on the linux machine, is port 6000 allowed ?

[vishnu]

Two ideas

- does your X on the Linux side has tcp enabled (-listen tcp)
- if you have firewalling on the linux machine, is port 6000 allowed ?

I have "LISTEN 10.4.0.106" - which is the IP address on my Octane set in /etc/X11/xdm/Xaccess set, but that obviously doesn't work, where would I set "-listen tcp" - which file? I know I feel like an idiot for not being able to figure this out on my own, but on my old Indigo2 that I had at work, it was never an issue, we could telnet into any SGI on our network and it would happily open its windows on our workstations.

[fleedwood]

Two ideas
- does your X on the Linux side has tcp enabled (-listen tcp)
- if you have firewalling on the linux machine, is port 6000 allowed ?

I have "LISTEN 10.4.0.106" - which is the IP addrehttps://docs.slackware.com/howtos:window_managers:remotex_linux2linuxss on my Octane set in /etc/X11/xdm/Xaccess set, but that obviously doesn't work, where would I set "-listen tcp" - which file? I know I feel like an idiot for not being able to figure this out on my own, but on my old Indigo2 that I had at work, it was never an issue, we could telnet into any SGI on our network and it would happily open its windows on our workstations.

depends a lot on the Linux distro and how your X server is started.

Iirc you are using slackware, so this https://docs.slackware.com/howtos:window...inux2linux might help.

grepping for nolisten in /etc/X11 might also give hints where to place the -listen tcp.

[vishnu]

Bingo bango bongo, that worked, thank you sir you ARE the man dammit!

The magic potion is "startx -- -listen tcp" ... Note that "startx -listen tcp" does NOT work, why? Why are two dashes needed before the listen dash? Who the hell knows. I don't mind diddling around with Xt but X itself is a fetid nightmare... 🤪 😂 😆 😎 😁

[jpstewart]

The magic potion is "startx -- -listen tcp" ... Note that "startx -listen tcp" does NOT work, why? Why are two dashes needed before the listen dash?

From the startx manpage:

Arguments immediately following the startx command are used to start a client in the same manner as xinit(1).  The special  argument '--' marks the end of client arguments and the beginning of server options.

You need some way to differentiate client options from server options, so why not use the two dashes?  It's not very different from the way things like 'rm' and 'grep' use two dashes to mark the "end of options" when necessary (e.g., while filenames for 'rm' or patterns for 'grep' start with a dash).

[vishnu]

From the startx manpage:

Arguments immediately following the startx command are used to start a client in the same manner as xinit(1).  The special  argument '--' marks the end of client arguments and the beginning of server options.

You need some way to differentiate client options from server options, so why not use the two dashes?  It's not very different from the way things like 'rm' and 'grep' use two dashes to mark the "end of options" when necessary (e.g., while filenames for 'rm' or patterns for 'grep' start with a dash).

Well I did not KNOW dat! 🤪 😎 😁 🤣