Linux in Government: Linux System Administrators
According to traditional definitions, such as the one on the Sage Web site, you can find what many people believe fits a Linux system administrator:
system administrator n. a system administrator is one who, as a primary job function, manages computer and network systems on behalf of another, such as an employer or client.
Another page on that site provides classic definitions of UNIX system administrators. Sage divides them into Novice, Junior, Intermediate/Advanced and Senior. You should visit the Sage Web site if you want to look at these definitions.
Fortunately, we do not have to agree with the delineation used by Sage. Instead, we can see Linux administrators as specialists in a variety of areas. For example, a Linux person could be senior in administration of Web sites, networking, interoperability, kernel management, e-mail, network storage or maintaining a development environment. At a minimum, Linux system administrators should know user management, hardware and software maintenance and network administration. From there, a Linux guy probably specializes, as Linux now can be found in so many different areas of information technology, including embedded devices and virtual machines.
Is a Linux system administrator any less proficient if he deals with content management or streaming media servers instead of file and print servers? Undoubtedly, we would have to say no. In the world of Linux 2005, the old rules do not necessarily apply.
If you are looking for someone to manage Linux computer and network systems on behalf of another, such as an employer or client, be prepared. You may discover that the vast majority of Linux system administrators learned their trade on their own networks. Once they gained the knowledge they needed, they may have offered their services for hire.
When you find an appropriate Linux systems administration candidate, recognize that he probably does not fit your mold. But, if you use his skills correctly, he will empower your organization and make everyone around him better. If your are not getting that from your Linux guy, you could be facing one of two issues: your people have closed their minds to what Linux brings or you have the wrong person. You can correct them both.
Tom Adelstein lives in Dallas, Texas, with his wife, Yvonne, and works as a Linux and open-source software consultant with Hiser+Adelstein, headquartered in New York City. He's the co-author of the book Exploring the JDS Linux Desktop and author of an upcoming book on Linux system administration, to be published by O'Reilly and Associates. Tom has been writing articles and books about Linux since early 1999.
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