While flipping through the latest LJ, I saw a small section at the beginning, labeled “Important Linux Web Sites”. What surprised me the most was to see http://slashdot.org/ as the top site listed. This may be a result simply of a sort when putting the list together, but I think many readers would agree that slashdot.org is not a good representation of the Linux operating system or community. Opinions by both the maintainers and visitors of that site are usually overly biased, ignorant or flame bait. If someone were to open an issue of LJ for the first time and wanted to learn more about Linux, I would much rather see them go to a more professionally run site, such as www.linux.com/ or www.gnu.org, than sites that sometimes make me embarrassed to be involved with Linux, like slashdot.org.
—Brian M Dial email@example.com
In the August issue of LJ, Linley Gwennap reported that the Delphi Automotive Systems Palm docking station (or MPC, short for Mobile Productivity Center) uses Windows CE. While WinCE plays a prominent role in Delphi's overall product strategy, it was not an appropriate choice for the MPC. Instead, we chose to use the eCos real-time kernel from Red Hat. I would appreciate it if you would publish this correction in the next issue of LJ.
—Brad Coon MPC Product ArchitectDelphi Automotive Systems firstname.lastname@example.org
I was reading my fresh new copy of issue 75 of LJ. In particular, I was reading “Collecting RFCs” and found this first statement: “Requests for Comment (RFCs) are the standards of the Internet”.
It's not really true, because RFCs are what they claim to be, requests for comment from the Internet community. RFCs are the second stage of the life cycle of the “official” Internet community documents. They start as “drafts” proposed by someone. After a while, they become RFCs and then, after having received some comment from someone else, they become STD (Standard), FYI (For Your Information) or BCP (Best Current Practice). So, RFCs are not standard, but only a mature stage of a proposal for a standard.
You can find the same document with two different names, one for the last RFC status and one for the definitive status; e.g., we have RFC-2026 (modified from RFC-1602) and the BCP-9 that is titled “The Internet Standards Process—Revision 3”. Or STD-1 that collects (and obsoletes) RFCs 2500, 2400, 2300, 2200, 2000, 1920, 1880, 1800, 1780, 1720, 1610, 1600, 1540, 1500, 1410, 1360, 1280, 1250, 1200, 1140, 1130, 1100, 1083. For more information about this, try www.rfc-editor.org/rfc.html.
Anyway, I found your article very interesting and love LJ. Go on this way!
—Vincenzo Romano 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!
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- Tech Tip: Really Simple HTTP Server with Python
- SUSE LLC's SUSE Manager
- My +1 Sword of Productivity
- Non-Linux FOSS: Caffeine!
- Managing Linux Using Puppet
- Doing for User Space What We Did for Kernel Space
- Returning Values from Bash Functions
- Rogue Wave Software's Zend Server
- Google's SwiftShader Released
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