Changes To Linux Journal
By the time you have reached this page, you may have noticed some changes in the appearance of Linux Journal. The changes are more than skin deep and, in this column, I will let you know what is happening.
The changes have come about both in response to reader feedback and in our attempt to streamline production of the magazine. Up through issue 11, layout was done on a contract basis by an outside person. This interface, both because of the physical location of layout being in a different place than the rest of magazine production and because there was a Macintosh involved, took more time and effort than was practical. With issue 12 we started to move layout in-house and, after a false start or two, we are happy to say all is under control.
Our new layout person is Amy Wood. She has previously worked for a weekly newspaper and the biggest problem we have with her is convincing her that she has a whole month between magazines instead of a week. The layout itself is still done in Quark XPress but it now runs on an MS-Windows system which is connected to our Linux network. The actual interface is handled by Samba (see LJ issue 7 for more info on Samba) and is transparent to Amy. For the rest of us, it means that files can be sent to and from that system without the need for sneaker-net. (In a future issue we will have an article on how Linux Journal is produced using mostly Linux systems.)
Because Amy had so much extra time after finishing up issue 13 she looked at the assorted comments about our layout and along with her own ideas, came up with the current layout. The major changes you should notice are a cleanup of the page format and the addition of “continued-from” lines on the continuation pages of articles which include a keyword so you know what article you are reading. Also, she is putting a lot of effort into minimizing the number of jumps within articles. Please let us know what you think of her work.
The second big change is still under way but should be done by the time you read this. We have established a WWW site, www.ssc.com. As well as having information on SSC products, we will be putting up information from Linux Journal. First we will put up the tables of contents and advertisers indices and then add some of the articles from the magazine. Advertisers can request links from their index entry to their web page and, if they don't have their own web site, for a nominal fee we will put their web pages on www.ssc.com. If you are an advertiser and need more information on this, contact Carlie Fairchild at (206) 782-7733.
As well as SSC and Linux Journal information, we will have some general Linux information on the site so if you are looking for something to browse try www.ssc.com. This is, of course, a Linux machine. If there are things you think should be added to the site, send e-mail to email@example.com.
Finally, with Linux 1.2 out there, more commercial vendors are starting to take Linux seriously. If you see anyone with a commercial interest in Linux, whether it is a vendor interested in making their product work with Linux or a company that is using Linux, please point them our way. The more information of commercial interest we can get in LJ, the easier it is for us to convince others that Linux is a viable alternative to other operating systems.
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