Linux in Government: Major Breakthrough in Linux Technology
I tested FreeNX before I knew anything about it. I'm currently on assignment to produce material for another Linux book. The editor asked me to write about Microsoft's Remote Desktop Protocol (RDP) as implemented by the open-source rdesktop and VNC. During my research, I ran across an article on how to install FreeNX.
I installed FreeNX on Ubuntu first, after obtaining it from the Ubuntu backports community. I followed the directions on the site and added the recommended mirrors to my /etc/apt/sources.list. I then ran apt-get install FreeNX and had my server.
Once installed, I added myself as a user; see Figure 1.
Following the set up, I logged out and saw FreeNX added to my menu; see Figure 2.
Next, I found RPMs for Fedora Core 3 and installed the client and server. Again, I added myself as a user.
In the client configuration section, Rick Stout wrote, "The most important part of the initial connection is the key file. This file, client.id_dsa.key, must be copied from the server to your client machine". Following his directions, I executed the following commands:
bash-3.00# scp /var/lib/nxserver/home/.ssh/client.id_dsa.key email@example.com:~/ The authenticity of host '192.168.1.109 (192.168.1.109)' can't be established. RSA key fingerprint is 40:54:e3:c9:5e:81:39:2d:ac:70:b9:bf:44:a9:ec:a8. Are you sure you want to continue connecting (yes/no)? yes Warning: Permanently added '192.168.1.109' (RSA) to the list of known hosts. Password: client.id_dsa.key 100% 672 0.7KB/s 00:00 bash-3.00#
Switching between machines, I was surprised at FreeNX's performance as compared to every other thin client I have tested and used. I also noticed that I could set up the client to use VNC and RDP.
In the middle of doing some work, I remember thinking for some reason that OpenOffice.org Writer had started running faster than normal. I was amused when I realized I was running the word processor remotely.
FreeNX also opens sessions quickly. During testing, I suspended sessions rather than closed them. When I resumed a suspended session, the client revalidated but still resumed mid-session, at the point where I had left off. Although this is not a stateless session in the purest terms, it does save bandwidth; see Figures 3 and 4.
After discovering FreeNX and testing it in a heterogeneous environment, I decided to research it further. I found around 10% as much material on FreeNX and NX as I did on VNC. However, the reports I did find were wildly in favor of FreeNX. Here are a few excerpts from user comments reprinted from the link mentioned above:
It's not about simply remotely accessing a product, ala VNC, but creating a true "Thin Client" environment.
Imagine either a school or business with an Athlon 2400+ and 1[GB] RAM, as well as a pile of useless 486s laying about that they picked up for 2 cents each. Whack a network card in them and voila - you have a thin client - able to run all of the latest productivity apps. Why? Because it's all on the server! And yes, it scales. Think big!
Unlike RDP and VNC, the performance is great! It's actually usable and responsive over dialup - something that I cannot say about RDP or VNC! Ick!
No, it won't be a games machine - but it's not trying to be.
Here's one more:
We just got done with an implementation of this in a fairly good size school. We have modified the system to allow authentication by their Windows active directory. One Mandrake Linux server, with a nomachine client on 120 + Windows machines, which include one computer lab.
As usual, space requirements do not allow us to publish extensive user comments. If you would like to read more, simply do a Google search on FreeNX.
Fast/Flexible Linux OS Recovery
On Demand Now
In this live one-hour webinar, learn how to enhance your existing backup strategies for complete disaster recovery preparedness using Storix System Backup Administrator (SBAdmin), a highly flexible full-system recovery solution for UNIX and Linux systems.
Join Linux Journal's Shawn Powers and David Huffman, President/CEO, Storix, Inc.
Free to Linux Journal readers.Register Now!
- Back to Backups
- Download "Linux Management with Red Hat Satellite: Measuring Business Impact and ROI"
- Google's Abacus Project: It's All about Trust
- Secure Desktops with Qubes: Introduction
- Fancy Tricks for Changing Numeric Base
- Secure Desktops with Qubes: Installation
- Working with Command Arguments
- Linux Mint 18
- Seeing Red and Getting Sleep
- CentOS 6.8 Released
Until recently, IBM’s Power Platform was looked upon as being the system that hosted IBM’s flavor of UNIX and proprietary operating system called IBM i. These servers often are found in medium-size businesses running ERP, CRM and financials for on-premise customers. By enabling the Power platform to run the Linux OS, IBM now has positioned Power to be the platform of choice for those already running Linux that are facing scalability issues, especially customers looking at analytics, big data or cloud computing.
￼Running Linux on IBM’s Power hardware offers some obvious benefits, including improved processing speed and memory bandwidth, inherent security, and simpler deployment and management. But if you look beyond the impressive architecture, you’ll also find an open ecosystem that has given rise to a strong, innovative community, as well as an inventory of system and network management applications that really help leverage the benefits offered by running Linux on Power.Get the Guide