Has anyone managed to get the FreeNX (or NoMachine NX) software running
under Slackware? After reading the documentation I have found, nothing
much is very clear to me; not even what components should be built and
installed.

The only thing I want to be able to do is to use this software in a way
similar to the way I am using VNC today: I start a VNC server on a box A,
and I get access to it from a remote machine B, as though it were local to
B.

If anybody has pulled this one off, I (for one) would be grateful if
they could share their experiences.

On Fri, 27 Jan 2006 22:43:44 +0000, Augustus SFX van Dusen wrote:

> Has anyone managed to get the FreeNX (or NoMachine NX) software running
> under Slackware? After reading the documentation I have found, nothing
> much is very clear to me; not even what components should be built and
> installed.

I played with it a while back. But I used a package from
linuxpackages.net, rather than building my own. There's one there for
Slack 10, and the description includes the "components" of freenx that
were used to build it...Maybe a good starting point.

Essentially, the package at linuxpackages would be installed/run on
the"remote" machine you want to access. You could then use the NX client
to connect to it, and run/display programs from that remote machine.

>
> The only thing I want to be able to do is to use this software in a way
> similar to the way I am using VNC today: I start a VNC server on a box
> A, and I get access to it from a remote machine B, as though it were
> local to B.
>
> If anybody has pulled this one off, I (for one) would be grateful if
> they could share their experiences.

When I did use it, it worked OK. But other than being more useable over
*very* slow links, I didn't see much benefit of it over ssh and X
forwarding. What I mean is, if your machines A + B are on the same LAN,
freenx won't do much for you that you can't do with an ssh session, and
forwarding X.
If your machines are connected by a slower link you'll probably see better
performance with NX than with ssh and X. At least that was my experience.

--
- Matt -

On Sat, 28 Jan 2006 00:20:05 +0000, Matt Payton wrote:

> On Fri, 27 Jan 2006 22:43:44 +0000, Augustus SFX van Dusen wrote:
>
>> Has anyone managed to get the FreeNX (or NoMachine NX) software running
>> under Slackware? After reading the documentation I have found, nothing
>> much is very clear to me; not even what components should be built and
>> installed.
>
> I played with it a while back. But I used a package from
> linuxpackages.net, rather than building my own. There's one there for
> Slack 10, and the description includes the "components" of freenx that
> were used to build it...Maybe a good starting point.
>
> Essentially, the package at linuxpackages would be installed/run on
> the"remote" machine you want to access. You could then use the NX client
> to connect to it, and run/display programs from that remote machine.
>
>
>> The only thing I want to be able to do is to use this software in a way
>> similar to the way I am using VNC today: I start a VNC server on a box
>> A, and I get access to it from a remote machine B, as though it were
>> local to B.
>>
>> If anybody has pulled this one off, I (for one) would be grateful if
>> they could share their experiences.
>
> When I did use it, it worked OK. But other than being more useable over
> *very* slow links, I didn't see much benefit of it over ssh and X
> forwarding. What I mean is, if your machines A + B are on the same LAN,
> freenx won't do much for you that you can't do with an ssh session, and
> forwarding X.
> If your machines are connected by a slower link you'll probably see better
> performance with NX than with ssh and X. At least that was my experience.

Thanks for your feedback.