From the Editor - Desktop Success Is in the Details
Back in December 1995, Linux Journal reviewed a new Linux distribution called Caldera Network Desktop (CND) from a new company called, as you might remember, Caldera. Although CND made a big splash with a GUI environment and Novell client support, it didn't exactly get the corporate desktop migrated to Linux right away.
In the almost nine years since CND came out, more waves of Linux desktop releases have crashed against the rocks, then rolled back. But each wave has fixed important obstacles to putting Linux on everyone's computer.
The GNOME and KDE Projects, and the freedesktop.org interoperability effort that is making their software work together, are finally bringing user interface sanity to the X Window System. Ambitious contributions from companies, AOL to Ximian, have filled in big pieces, including a world-class browser, office suite and graphics libraries.
All that is keeping corporate users away from Linux now is the details. It's the little things in real-world IT environments that seem to make desktop Linux a “maybe-next-year” project. You might have a stubborn, difficult-to-port, in-house application written for a legacy, non-Linux, OS. You might be working with an embedded device or application service provider whose supposedly Web-based software has a bug that keeps it from working with the Web browsers available for Linux.
Successful Linux desktop plans depend on the details. The office suite is an anchor that keeps non-Linux desktops around. But it might be easier to switch than you think. Bruce Byfield breaks down this intimidating task on page 52.
If you think that integrating your own programs and scripts with office suite documents means you have to wait for some office suite vendor to release an upgrade, think again. James Britt shows how to write simple software that handles OpenOffice.org documents on page 78.
Even if you don't have a Linux desktop migration planned now, make sure not to make development choices that will cause migration problems later. Future-proof software is cross-platform, and you'll be able to upgrade from your legacy Mac OS systems to Linux seamlessly, if you develop now with Renaissance, which Ludovic Marcotte explains on page 58. You can even move scripts from any platform to Linux using Tcl/Tk, which Derek Fountain covers on page 83.
Moving to Linux doesn't mean users have to give up fun with photos and sounds. Learn about XMMS and a fun photo editing trick on pages 68 and 88. Last and most important, in most companies, if you can't sell management on it, you won't get it. Make the case for your desktop Linux migration in style, on Linux, with Rob Reilly's presentation advice for speakers on page 46.
Don Marti is editor in chief of Linux Journal.
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!
- SUSE LLC's SUSE Manager
- My +1 Sword of Productivity
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- Non-Linux FOSS: Caffeine!
- Managing Linux Using Puppet
- Doing for User Space What We Did for Kernel Space
- SuperTuxKart 0.9.2 Released
- Google's SwiftShader Released
- Parsing an RSS News Feed with a Bash Script
- Rogue Wave Software's Zend Server
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