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 firstname.lastname@example.org:~/ 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.
Practical Task Scheduling Deployment
July 20, 2016 12:00 pm CDT
One of the best things about the UNIX environment (aside from being stable and efficient) is the vast array of software tools available to help you do your job. Traditionally, a UNIX tool does only one thing, but does that one thing very well. For example, grep is very easy to use and can search vast amounts of data quickly. The find tool can find a particular file or files based on all kinds of criteria. It's pretty easy to string these tools together to build even more powerful tools, such as a tool that finds all of the .log files in the /home directory and searches each one for a particular entry. This erector-set mentality allows UNIX system administrators to seem to always have the right tool for the job.
Cron traditionally has been considered another such a tool for job scheduling, but is it enough? This webinar considers that very question. The first part builds on a previous Geek Guide, Beyond Cron, and briefly describes how to know when it might be time to consider upgrading your job scheduling infrastructure. The second part presents an actual planning and implementation framework.
Join Linux Journal's Mike Diehl and Pat Cameron of Help Systems.
Free to Linux Journal readers.Register Now!
- Google's SwiftShader Released
- SUSE LLC's SUSE Manager
- My +1 Sword of Productivity
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- Managing Linux Using Puppet
- Non-Linux FOSS: Caffeine!
- Interview with Patrick Volkerding
- SuperTuxKart 0.9.2 Released
- Parsing an RSS News Feed with a Bash Script
- Doing for User Space What We Did for Kernel Space
With all the industry talk about the benefits of Linux on Power and all the performance advantages offered by its open architecture, you may be considering a move in that direction. If you are thinking about analytics, big data and cloud computing, you would be right to evaluate Power. The idea of using commodity x86 hardware and replacing it every three years is an outdated cost model. It doesn’t consider the total cost of ownership, and it doesn’t consider the advantage of real processing power, high-availability and multithreading like a demon.
This ebook takes a look at some of the practical applications of the Linux on Power platform and ways you might bring all the performance power of this open architecture to bear for your organization. There are no smoke and mirrors here—just hard, cold, empirical evidence provided by independent sources. I also consider some innovative ways Linux on Power will be used in the future.Get the Guide