SlackWiki - User contributions [en]

FreeNX

Pwc101 — Mon, 17 Aug 2009 12:48:21 GMT

Pwc101: /* Connect to it */

Getting FreeNX working on Slackware -current as of writing (13/08/2009).

== Build it ==

Get Eric Hameleers' build script:

:<code>wget -np -r http://connie.slackware.com/~alien/slackbuilds/freenx/build/</code>
:<code>cd connie.slackware.com/\~alien/slackbuilds/freenx/build/</code>

Build nx and freenx:

:<code>./nx.SlackBuild && ./freenx.SlackBuild --cleanup</code>

Install the resultant packages:

:<code>installpkg /tmp/{nx-3.3.0-i486-1alien,freenx-0.7.3-i486-2alien}.tgz</code>

The installer runs the initial configuration (including adding a new user "nx" to the system).

== Configure it ==

The main config file is /etc/nxserver/node.conf. The comments are helpful, so read them.

Of interest to me was specifying the port that the system's sshd listens on. If you run your sshd on a non-standard port (i.e. not 22), then uncomment the line:
#SSHD_PORT=22
and replace 22 with whatever your port number is.

If you're a bit paranoid with your security settings in /etc/ssh/sshd_config (like I am), make sure you add the user nx to AllowUsers, otherwise the client you choose will fail to connect to your ssh daemon.

If you've made changes in /etc/ssh/sshd_config, then restart sshd. This is the command I use when I'm logged in remotely and I need to restart sshd:
:<code>/etc/rc.d/rc.sshd stop; sleep 5; /etc/rc.d/rc.sshd start</code>

== Run it ==

Check to see if the server is running (it was after my installation, but your mileage may vary):

:<code>nxserver --status</code>

If you see:

root@darkstar:~# nxserver --status
NX> 100 NXSERVER - Version 3.2.0-73 OS (GPL, using backend: 3.3.0)
NX> 110 NX Server is running
NX> 999 Bye

you're good to go. Otherwise, run:
:<code>nxserver --restart</code>

== Connect to it ==

http://en.opensuse.org/FreeNX_Server_HOWTO lists a number of clients able to connect to a (free)nx server. Since my main interest was in accessing my Linux box at home from my Windows box at work, I used the NoMachine client for Windows.

The NoMachine Linux client works just as well. Simply download the archive (http://64.34.161.181/download/3.3.0/Linux/nxclient-3.3.0-6.i386.tar.gz or http://64.34.161.181/download/3.3.0/Linux/nxclient-3.3.0-6.x86_64.tar.gz, depending on your architecture), unpack it and run NX/bin/nxclient. When prompted, enter the IP or hostname of the machine you wish to connect to, the port through which you would SSH into it and which DE you want to run (KDE, Gnome etc.). Obviously Slackware doesn't ship with Gnome, but I've successfully tested it with KDE. I have yet to get XFCE to work.

FreeNX

Pwc101 — Mon, 17 Aug 2009 12:00:10 GMT

Pwc101: /* Connect to it */ Added 64bit client download location

Getting FreeNX working on Slackware -current as of writing (13/08/2009).

== Build it ==

Get Eric Hameleers' build script:

:<code>wget -np -r http://connie.slackware.com/~alien/slackbuilds/freenx/build/</code>
:<code>cd connie.slackware.com/\~alien/slackbuilds/freenx/build/</code>

Build nx and freenx:

:<code>./nx.SlackBuild && ./freenx.SlackBuild --cleanup</code>

Install the resultant packages:

:<code>installpkg /tmp/{nx-3.3.0-i486-1alien,freenx-0.7.3-i486-2alien}.tgz</code>

The installer runs the initial configuration (including adding a new user "nx" to the system).

== Configure it ==

The main config file is /etc/nxserver/node.conf. The comments are helpful, so read them.

Of interest to me was specifying the port that the system's sshd listens on. If you run your sshd on a non-standard port (i.e. not 22), then uncomment the line:
#SSHD_PORT=22
and replace 22 with whatever your port number is.

If you're a bit paranoid with your security settings in /etc/ssh/sshd_config (like I am), make sure you add the user nx to AllowUsers, otherwise the client you choose will fail to connect to your ssh daemon.

If you've made changes in /etc/ssh/sshd_config, then restart sshd. This is the command I use when I'm logged in remotely and I need to restart sshd:
:<code>/etc/rc.d/rc.sshd stop; sleep 5; /etc/rc.d/rc.sshd start</code>

== Run it ==

Check to see if the server is running (it was after my installation, but your mileage may vary):

:<code>nxserver --status</code>

If you see:

root@darkstar:~# nxserver --status
NX> 100 NXSERVER - Version 3.2.0-73 OS (GPL, using backend: 3.3.0)
NX> 110 NX Server is running
NX> 999 Bye

you're good to go. Otherwise, run:
:<code>nxserver --restart</code>

== Connect to it ==

http://en.opensuse.org/FreeNX_Server_HOWTO lists a number of clients able to connect to a (free)nx server. Since my main interest was in accessing my Linux box at home from my Windows box at work, I used the NoMachine client for Windows.

The NoMachine Linux client works just as well. Simply download the archive (http://64.34.161.181/download/3.3.0/Linux/nxclient-3.3.0-6.i386.tar.gz or http://64.34.161.181/download/3.3.0/Linux/nxclient-3.3.0-6.x86_64.tar.gz, depending on your architecture), unpack it and run bin/nxclient. When prompted, enter the IP or hostname of the machine you wish to connect to, the port through which you would SSH into it and which DE you want to run (KDE, Gnome etc.). Obviously Slackware doesn't ship with Gnome, but I've successfully tested it with KDE. I have yet to get XFCE to work.

FreeNX

Pwc101 — Thu, 13 Aug 2009 20:40:24 GMT

Pwc101:

Getting FreeNX working on Slackware -current as of writing (13/08/2009).

== Build it ==

Get Eric Hameleers' build script:

:<code>wget -np -r http://connie.slackware.com/~alien/slackbuilds/freenx/build/</code>
:<code>cd connie.slackware.com/\~alien/slackbuilds/freenx/build/</code>

Build nx and freenx:

:<code>./nx.SlackBuild && ./freenx.SlackBuild --cleanup</code>

Install the resultant packages:

:<code>installpkg /tmp/{nx-3.3.0-i486-1alien,freenx-0.7.3-i486-2alien}.tgz</code>

The installer runs the initial configuration (including adding a new user "nx" to the system).

== Configure it ==

The main config file is /etc/nxserver/node.conf. The comments are helpful, so read them.

Of interest to me was specifying the port that the system's sshd listens on. If you run your sshd on a non-standard port (i.e. not 22), then uncomment the line:
#SSHD_PORT=22
and replace 22 with whatever your port number is.

If you're a bit paranoid with your security settings in /etc/ssh/sshd_config (like I am), make sure you add the user nx to AllowUsers, otherwise the client you choose will fail to connect to your ssh daemon.

If you've made changes in /etc/ssh/sshd_config, then restart sshd. This is the command I use when I'm logged in remotely and I need to restart sshd:
:<code>/etc/rc.d/rc.sshd stop; sleep 5; /etc/rc.d/rc.sshd start</code>

== Run it ==

Check to see if the server is running (it was after my installation, but your mileage may vary):

:<code>nxserver --status</code>

If you see:

root@darkstar:~# nxserver --status
NX> 100 NXSERVER - Version 3.2.0-73 OS (GPL, using backend: 3.3.0)
NX> 110 NX Server is running
NX> 999 Bye

you're good to go. Otherwise, run:
:<code>nxserver --restart</code>

== Connect to it ==

http://en.opensuse.org/FreeNX_Server_HOWTO lists a number of clients able to connect to a (free)nx server. Since my main interest was in accessing my Linux box at home from my Windows box at work, I used the NoMachine client for Windows.

The NoMachine Linux client works just as well. Simply download the archive (http://64.34.161.181/download/3.3.0/Linux/nxclient-3.3.0-6.i386.tar.gz), unpack it and run bin/nxclient. When prompted, enter the IP or hostname of the machine you wish to connect to, the port through which you would SSH into it and which DE you want to run (KDE, Gnome etc.). Obviously Slackware doesn't ship with Gnome, but I've successfully tested it with KDE. I have yet to get XFCE to work.

FreeNX

Pwc101 — Thu, 13 Aug 2009 20:40:02 GMT

Pwc101:

Getting FreeNX working on Slackware (-current as of writing (13/08/2009)).

== Build it ==

Get Eric Hameleers' build script:

:<code>wget -np -r http://connie.slackware.com/~alien/slackbuilds/freenx/build/</code>
:<code>cd connie.slackware.com/\~alien/slackbuilds/freenx/build/</code>

Build nx and freenx:

:<code>./nx.SlackBuild && ./freenx.SlackBuild --cleanup</code>

Install the resultant packages:

:<code>installpkg /tmp/{nx-3.3.0-i486-1alien,freenx-0.7.3-i486-2alien}.tgz</code>

The installer runs the initial configuration (including adding a new user "nx" to the system).

== Configure it ==

The main config file is /etc/nxserver/node.conf. The comments are helpful, so read them.

Of interest to me was specifying the port that the system's sshd listens on. If you run your sshd on a non-standard port (i.e. not 22), then uncomment the line:
#SSHD_PORT=22
and replace 22 with whatever your port number is.

If you're a bit paranoid with your security settings in /etc/ssh/sshd_config (like I am), make sure you add the user nx to AllowUsers, otherwise the client you choose will fail to connect to your ssh daemon.

If you've made changes in /etc/ssh/sshd_config, then restart sshd. This is the command I use when I'm logged in remotely and I need to restart sshd:
:<code>/etc/rc.d/rc.sshd stop; sleep 5; /etc/rc.d/rc.sshd start</code>

== Run it ==

Check to see if the server is running (it was after my installation, but your mileage may vary):

:<code>nxserver --status</code>

If you see:

root@darkstar:~# nxserver --status
NX> 100 NXSERVER - Version 3.2.0-73 OS (GPL, using backend: 3.3.0)
NX> 110 NX Server is running
NX> 999 Bye

you're good to go. Otherwise, run:
:<code>nxserver --restart</code>

== Connect to it ==

http://en.opensuse.org/FreeNX_Server_HOWTO lists a number of clients able to connect to a (free)nx server. Since my main interest was in accessing my Linux box at home from my Windows box at work, I used the NoMachine client for Windows.

The NoMachine Linux client works just as well. Simply download the archive (http://64.34.161.181/download/3.3.0/Linux/nxclient-3.3.0-6.i386.tar.gz), unpack it and run bin/nxclient. When prompted, enter the IP or hostname of the machine you wish to connect to, the port through which you would SSH into it and which DE you want to run (KDE, Gnome etc.). Obviously Slackware doesn't ship with Gnome, but I've successfully tested it with KDE. I have yet to get XFCE to work.

FreeNX

Pwc101 — Thu, 13 Aug 2009 19:44:57 GMT

Pwc101: /* Connect to it */

Getting FreeNX working on Slackware (12.2 as of writing).

== Build it ==

Get Eric Hameleers' build script:

:<code>wget -np -r http://connie.slackware.com/~alien/slackbuilds/freenx/build/</code>
:<code>cd connie.slackware.com/\~alien/slackbuilds/freenx/build/</code>

Build nx and freenx:

:<code>./nx.SlackBuild && ./freenx.SlackBuild --cleanup</code>

Install the resultant packages:

:<code>installpkg /tmp/{nx-3.3.0-i486-1alien,freenx-0.7.3-i486-2alien}.tgz</code>

The installer runs the initial configuration (including adding a new user "nx" to the system).

== Configure it ==

The main config file is /etc/nxserver/node.conf. The comments are helpful, so read them.

Of interest to me was specifying the port that the system's sshd listens on. If you run your sshd on a non-standard port (i.e. not 22), then uncomment the line:
#SSHD_PORT=22
and replace 22 with whatever your port number is.

If you're a bit paranoid with your security settings in /etc/ssh/sshd_config (like I am), make sure you add the user nx to AllowUsers, otherwise the client you choose will fail to connect to your ssh daemon.

If you've made changes in /etc/ssh/sshd_config, then restart sshd. This is the command I use when I'm logged in remotely and I need to restart sshd:
:<code>/etc/rc.d/rc.sshd stop; sleep 5; /etc/rc.d/rc.sshd start</code>

== Run it ==

Check to see if the server is running (it was after my installation, but your mileage may vary):

:<code>nxserver --status</code>

If you see:

root@darkstar:~# nxserver --status
NX> 100 NXSERVER - Version 3.2.0-73 OS (GPL, using backend: 3.3.0)
NX> 110 NX Server is running
NX> 999 Bye

you're good to go. Otherwise, run:
:<code>nxserver --restart</code>

== Connect to it ==

http://en.opensuse.org/FreeNX_Server_HOWTO lists a number of clients able to connect to a (free)nx server. Since my main interest was in accessing my Linux box at home from my Windows box at work, I used the NoMachine client for Windows.

The NoMachine Linux client works just as well. Simply download the archive (http://64.34.161.181/download/3.3.0/Linux/nxclient-3.3.0-6.i386.tar.gz), unpack it and run bin/nxclient. When prompted, enter the IP or hostname of the machine you wish to connect to, the port through which you would SSH into it and which DE you want to run (KDE, Gnome etc.). Obviously Slackware doesn't ship with Gnome, but I've successfully tested it with KDE. I have yet to get XFCE to work.

FreeNX

Pwc101 — Thu, 13 Aug 2009 17:04:23 GMT

Pwc101: /* Configure it */

Freenx

Pwc101 — Thu, 13 Aug 2009 17:01:32 GMT

Pwc101: moved Freenx to FreeNX: Added correct name.

#REDIRECT [[FreeNX]]

FreeNX

Pwc101 — Thu, 13 Aug 2009 17:01:31 GMT

Pwc101: moved Freenx to FreeNX: Added correct name.

Getting FreeNX working on Slackware (12.2 as of writing).

== Build it ==

Get Eric Hameleers' build script:

:<code>wget -np -r http://connie.slackware.com/~alien/slackbuilds/freenx/build/</code>
:<code>cd connie.slackware.com/\~alien/slackbuilds/freenx/build/</code>

Build nx and freenx:

:<code>./nx.SlackBuild && ./freenx.SlackBuild --cleanup</code>

Install the resultant packages:

:<code>installpkg /tmp/{nx-3.3.0-i486-1alien,freenx-0.7.3-i486-2alien}.tgz</code>

The installer runs the initial configuration (including adding a new user "nx" to the system).

== Configure it ==

The main config file is /etc/nxserver/node.conf. The comments are helpful, so read them.

Of interest to me was specifying the port that the system's sshd listens on. If you run your sshd on a non-standard port (i.e. not 22), then uncomment the line:
#SSHD_PORT=22
and replace 22 with whatever you port number is.

If you're a bit paranoid with your security settings in /etc/ssh/sshd_config (like I am), make sure you add the user nx to AllowUsers, otherwise the client you choose will fail to connect to your ssh daemon.

If you've made changes in /etc/ssh/sshd_config, then restart sshd. This is the command I use when I'm logged in remotely and I need to restart sshd:
:<code>/etc/rc.d/rc.sshd stop; sleep 5; /etc/rc.d/rc.sshd start</code>

== Run it ==

Check to see if the server is running (it was after my installation, but your mileage may vary):

:<code>nxserver --status</code>

If you see:

root@darkstar:~# nxserver --status
NX> 100 NXSERVER - Version 3.2.0-73 OS (GPL, using backend: 3.3.0)
NX> 110 NX Server is running
NX> 999 Bye

you're good to go. Otherwise, run:
:<code>nxserver --restart</code>

== Connect to it ==

http://en.opensuse.org/FreeNX_Server_HOWTO lists a number of clients able to connect to a (free)nx server. Since my main interest was in accessing my Linux box at home from my Windows box at work, I used the NoMachine client for Windows.

FreeNX

Pwc101 — Thu, 13 Aug 2009 17:00:35 GMT

Pwc101: Created page with 'Getting FreeNX working on Slackware (12.2 as of writing). == Build it == Get Eric Hameleers' build script: :<code>wget -np -r http://connie.slackware.com/~alien/slackbuilds/fr...'

Getting FreeNX working on Slackware (12.2 as of writing).

== Build it ==

Get Eric Hameleers' build script:

:<code>wget -np -r http://connie.slackware.com/~alien/slackbuilds/freenx/build/</code>
:<code>cd connie.slackware.com/\~alien/slackbuilds/freenx/build/</code>

Build nx and freenx:

:<code>./nx.SlackBuild && ./freenx.SlackBuild --cleanup</code>

Install the resultant packages:

:<code>installpkg /tmp/{nx-3.3.0-i486-1alien,freenx-0.7.3-i486-2alien}.tgz</code>

The installer runs the initial configuration (including adding a new user "nx" to the system).

== Configure it ==

The main config file is /etc/nxserver/node.conf. The comments are helpful, so read them.

Of interest to me was specifying the port that the system's sshd listens on. If you run your sshd on a non-standard port (i.e. not 22), then uncomment the line:
#SSHD_PORT=22
and replace 22 with whatever you port number is.

If you're a bit paranoid with your security settings in /etc/ssh/sshd_config (like I am), make sure you add the user nx to AllowUsers, otherwise the client you choose will fail to connect to your ssh daemon.

If you've made changes in /etc/ssh/sshd_config, then restart sshd. This is the command I use when I'm logged in remotely and I need to restart sshd:
:<code>/etc/rc.d/rc.sshd stop; sleep 5; /etc/rc.d/rc.sshd start</code>

== Run it ==

Check to see if the server is running (it was after my installation, but your mileage may vary):

:<code>nxserver --status</code>

If you see:

root@darkstar:~# nxserver --status
NX> 100 NXSERVER - Version 3.2.0-73 OS (GPL, using backend: 3.3.0)
NX> 110 NX Server is running
NX> 999 Bye

you're good to go. Otherwise, run:
:<code>nxserver --restart</code>

== Connect to it ==

http://en.opensuse.org/FreeNX_Server_HOWTO lists a number of clients able to connect to a (free)nx server. Since my main interest was in accessing my Linux box at home from my Windows box at work, I used the NoMachine client for Windows.