Is Linux Worth the Effort?
I've spent the better part of the past 2 weeks banging away on 2 LTSP servers for our school district. I find myself lamenting to those around me, and being an otherwise cranky guy as well. This morning it dawned on me that people probably think I'm having such a hard time because I'm using Linux instead of the "norm" -- but that's just not the case.
Tomorrow morning, about 1200 people are going to log into thin clients strewn around the school district here in northern Michigan. I am using K12LTSP as my distribution, because the support is incredible, and it's designed for schools. The problem for me, however, is that Linux is so darn powerful, my users are overwhelmed by it. I'll admit, that's not really true of the students, but the teachers demand simplicity. And that's where my 2 weeks have gone. Here's some of the things I've done to prepare for tomorrow:
* Make a pretty login window, with the login and password on the same screen. (GDM doesn't have the 2 fields on the same screen, and my users don't like that. Thankfully, KDM fits the bill. I'd use XDM, but there are no asterisks when a user types their name, so they think the computer is locked up when they're typing their passwords. Ugh.)
* Get a SIMPLE window manager going. I've chosen xfce this time, because it's lightweight and pretty. In the past I've used icewm, but it requires another program to manage desktop icons, and I think nautilus is rather bloaty.
* Simplify the menu. A Fedora install comes with so many thousands of applications, it's hard for my users (again, not students so much) to find what they need. I have to manually create a "start" menu with just the applications regularly used.
And those are just the visible things. Behind the scenes we have network LDAP authentication, NFS home directories, CUPS printer installation, load balancing, pre-defined proxy rules inserted into firefox, defaulting openoffice to save in the Microsoft format, etc, etc.
Is it all worth it? Oh, heck yeah. Instead of managing 250 workstations, I'll be managing 2. I like that kind of math. There are still a couple hundred Macintosh computers, and handfuls of Windows PCs -- but I'd like not to think about those for a bit, and bask in my thin client glory. :)
Oh, and happy New Year everyone. :)
UPDATE: How'd it turn out? Here's a followup.
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
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- My +1 Sword of Productivity
- Managing Linux Using Puppet
- Non-Linux FOSS: Caffeine!
- 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