Hacker News Reader

Comment by jra101 | Hacker News Reader

Works pretty well, had a minimal X11 + GL app up and running in minutes.

Issue 1: Visual Studio doesn't pull header files from the target Linux system so Intellisense was useless.

Issue 2: Every time I compiled something or started a debug session, four new sshd processes and a new sftp-server process would start on the target Linux system (Ubuntu 14.04 running in a VM). Eventually I had 16-20 of these processes running and they never exit.

View on HN

1) this is something we're planning on making much better with automatic acquisition of the headers from the remote for IntelliSense 2) I think this might be a cleanup issue, I will fix this

Any plans to use your new linuxulator to locally deploy and develop linux binaries?

How exactly does the x11 part work. If I'm working remotely and have XServer running on windows, will it show the program when I hit run?

Or do I need to be logged in through a terminal session separately running the executables through that?

I've not tried anything with XServer on windows. What we showed in the blog post is setting export DISPLAY=:0.0 to the Pre-Launch command in the project properties. Then when the gui app gets launched from our session it pops open on the remote Linux desktop.

Hmm, I guess I would use a terminal then. I do C++ programming a lot on linux clusters for science. Being able to launch X11 compiled applications remotely would be great. I currently do this using netbeans on windows.

Interesting, give it a try and let me know how it goes. I'd love to talk to you more about your workflow here. Very interesting.

I don't know, but perhaps you could ssh -X and echo "$DISPLAY", then try to export that value instead.

How exactly does the x11 part work.

We've been asking that question for literally decades.

Why are they spinning up new sshd instances? That makes me raise an eyebrow.

sshd forks per connection.

The 'sshd' process on the target Linux apparently forks a process to handle each connection . . . with two SSH sessions the Linux target looks like this (pstree -p):

        |-sshd(1017)-+-sshd(5495)---sshd(5561)---bash(5562)
        |            `-sshd(5595)---sshd(5631)---bash(5632)

When the ssh sessions die, only process 1017 is left.

Reply on news.ycombinator.com