Letters to the Editor
I have been using Linux for a couple of years now, and when I saw your magazine I immediately subscribed. I love it.
Only ONE downside.
...continued on page 46 ...continued on page 44
What's the story with this format? I've got to find it one of the most annoying techniques that magazines use, and cannot personally figure out a reason for it. Skipping a page because of a full page ad is fine-I even scan the ad if it looks interesting. The Economist, a weekly magazine that calls itself a newspaper and runs over 100 pages, does NOT do this and I find it much easier to follow the content and spirit of what the author is trying to get across. Everyone else is breaking up their articles into linked lists-a big drag.
What motivates you to make reading your excellent magazine a chore?
—Graham R. Leach email@example.com
Only one downside? That's pretty good...
We do it only as much as is strictly necessary. Several things determine the need to do this. The first is that we do not impose exact article length limits on our authors, which means that the articles don't come out anywhere near even pages much of the time, and the numbers of advertisements of different sizes may not fit the empty spaces. The second is that we have decided that all one page or more articles must start at the top of a page; we tried not doing that and it looked awful. Another consideration is to start “important” articles near the front of the magazine. Readers expect to find them there but that means that something must be continued to the back half of the magazine. The last consideration is that some articles require color, and we have only so many color pages to work with per issue. The magazine is made up of a number of 16-page “forms” or “signatures” and, in some cases, color is only present on one side of the form. This means that we have to link through the color pages for ads and articles that contain color and then print the non-color material on the other pages. Right now, printing in all color is not affordable. As our press run increases the cost of this additional color becomes less significant. While this will not totally eliminate the “linked list” syndrome it will help decrease its frequency.
When we have more subscribers and advertisers, and can afford to expand the magazine, our options for laying out each article will be widened. Our goal is no articles ever split; although this will probably never be completely possible, we hope to come closer over time.
I want to tell how Linux has helped supporting Costa Rica's national network.
We've installed some Linux name and mail servers in the main subdomains of our national Internet networks. Linux is now stable enough for doing administrative chores like nameserving, mail serving and the like.
So CRNet (which is the entity coordinating and giving impulse to our national network) likes the idea of using Linux for these tasks.
In fact, places like the Presidential House, the Universidad Latina (Latin University) and the Veterinary School of the Universidad Nacional use Linux both as name and mail servers.
In the University of Costa Rica (UCR), where I'm working, we are setting up a Linux box as a temporary and limited newsserver.
—Mario A. Guerra firstname.lastname@example.org
I recently decided to purchase a “real” Linux Distribution. My prime motivation was the fact that I couldn't seem to get my very unsupported Procom CDROM mounted. Don't feel bad, it didn't work under (IN)Coherent, Oh Esse Too, or even well under Windoze. Procom tech support told me simply “We no longer support those old drives”, click...buzz. So I was getting desperate.
I had tried under my old system (Linux 1.0.9), by using the drivers there. I was under the assumption that most of these drives are similar, just VAR-ed under different labels. I thought this might be a Mitsumi. Anyway, I broke down and ordered Release 4 and a supplement from Trans-Ameritech, mostly because they claimed to work under any drive DOS could recognise.
Not only did T-A send the Distribution Release 4 and the July Supplement, they also included a free copy of the November supplement with Debian and Bogus and BSD4.4R2.0. (at no extra cost to me!) Thanks T-A. Unfortunately, the only scheme I could run my disc from was through UMSDOS running from my true DOS partition. I didn't have the room, nor did I want to. I already had a root partition that I wanted. So, I gave up.
Then, on Martin Luther King Day, I was goofing with the system and I decided, on a lark, to do a raw scan of the DOS binary drivers for the Procom drive. I don't know what I was looking for, but I found it-at the tail of the file was the list of some Sony 500-series drives! I knew this latest distribution had some cdu535 stuff on it, so I forced a boot from loadlin (a story in itself) and (TaDa!) I could talk to the disc! But, I went from PL 1.1.18 back down to 1.0.9 . I scanned the distribution again and found a 1.1.18 kernel with cdu535 support and setup installed that nicely! Happy ending! Drop in if you're in the neighborhood and we'll split a Guiness. Have fun, I know I am. Thanks for doing what the big boys couldn't do!
—Mike Allison email@example.com
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
- Tech Tip: Really Simple HTTP Server with Python
- Managing Linux Using Puppet
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- Non-Linux FOSS: Caffeine!
- Returning Values from Bash Functions
- Rogue Wave Software's Zend Server
- Doing for User Space What We Did for Kernel Space
- Parsing an RSS News Feed with a Bash Script
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