Linux in Government: Major Breakthrough in Linux Technology
Often, technology breakthroughs never see the light of day. Sometimes, they pop up and people simply go "ho-hum". I've had personal experiences with that kind of reception in the past and understand the frustrations and disappointments.
When you conceive an idea and bring it into reality, you have an expectation of an immediate embrace. In your mind, you see something like a ticker-tape parade welcome. But, then the phone doesn't ring, and the press release gets set on the shelf.
In the era of information overload, perhaps some people think of new technology as another thing with which they have to cope. They immediately put it off until tomorrow. But tomorrow never comes, so they put it to the side.
The same phenomenon occurs within the media. Many writers do not understand their beats. Instead, they regurgitate press releases, opinions of people in their networks and the insights of others.
Then, we have the skeptics and the "so-what" crowd. I read a comment following an article about FreeNX that said, "Excuse me if I'm skeptical of something that will claim to change the world". The comment came after numerous testimonials about how great FreeNX works in schools and companies.
Despite all of this, Fabian Franz and Kurt Pfeifle have a breakthrough technology. They created the first usable implementation of the GPL version of NX. In an interview conducted around the time FreeNX was announced, they expressed extreme optimism about their project's future. You can sense their vision and euphoria simply by reading the interview. In short, they expected their project to run away from them.
But Freinz and Pfeifle's project, the FreeNX project, has not received the coverage it deserves. Certainly, their dreams and aspirations have not yet materialized fully. Compared to VNC and Microsoft's RDP, the media treats NX seems like a blip on the screen, in spite of its vastly superior nature.
Gian Filippo Pinzari, who developed the original NX code, may have similar feelings, as he discontinued the NX developers and users mailing-lists on May 25th, 2005. He hopes to see the mailing-lists move to the FreeNX project. He explained his reasons in an e-mail dated May 19. Here's an excerpt:
It is not easy to build a presence in the Linux market...
We want to remain collaborative while being paid for support. We want to give away most of the software we produce and keep selling some of it. We want to dedicate ourselves to bringing an idea to success, invest money and most of our time, gather talents, cultivate a culture, remain entrepreneurs while being developers. They are all freedoms that, for us, are as important as having the chance of modifying the source code. In a perfect OSS world, users must be free to choose their software and avoid being locked into a single solution. At the same time, thousands of Linux companies around the world must be free to grow a business while remaining independent. If you like freedom as we do, you will surely understand our point.
Quite eloquently, Gian Filippo Pinzari sums up the dreams and aspirations of many open-source visionaries. He runs a small but growing company. In the spirit of free/open-source software, he released his core technology under GPL licenses.
Perhaps Pinzari has moments when he questions the viability of that decision. For those with an eye for significant discoveries, FreeNX should follow the successful open-source business model: give away the recipe and sell the cake.
For technically inclined people, imagine X server technology with compression so tight that GNOME and KDE sessions run over modems with SSH encryption. Image lightening-fast thin clients that use tiny amounts of bandwidth and handle audio and video, printing and session suspension instead of termination. Imagine real virtual KVM switches without hardware. Say goodbye to SunRay servers and all the thin clients that never lived up to their promise. Think about real heterogeneous interoperability on PCs and devices that scale.
For the less technically inclined, imagine system administrators being able to see and operate every server in their data centers with a single keyboard, video console and mouse--without a hardwire switch and hundreds of cables.
Or, imagine that when you call for support, someone logs on to your computer remotely and fixes it. Imagine logging onto your computer for work and forgetting you're at home. Or, imagine setting up a single computer in a closet that everyone in the family can access from an inexpensive device, and you control the content. How about clients for PlayStation2, iPAQ or Zaurus 5XXX?
Gian Filippo Pinzari invented NX based on X. He took the fat and insecure X client/server and utilized inventive compression to make it very thin. His company, NoMachine.com, released the code under the GPL license in 2003. Now, the Open Source community has something that goes beyond the "me-too" category. Some users have referred to FreeNX as a Citrix and Windows Terminal Server killer.
Practical Task Scheduling Deployment
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.View Now!
|The Firebird Project's Firebird Relational Database||Jul 29, 2016|
|Stunnel Security for Oracle||Jul 28, 2016|
|SUSE LLC's SUSE Manager||Jul 21, 2016|
|My +1 Sword of Productivity||Jul 20, 2016|
|Non-Linux FOSS: Caffeine!||Jul 19, 2016|
|Murat Yener and Onur Dundar's Expert Android Studio (Wrox)||Jul 18, 2016|
- Stunnel Security for Oracle
- The Firebird Project's Firebird Relational Database
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- SUSE LLC's SUSE Manager
- Managing Linux Using Puppet
- My +1 Sword of Productivity
- Non-Linux FOSS: Caffeine!
- Google's SwiftShader Released
- SuperTuxKart 0.9.2 Released
- 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