Fighting for Your Rights
The summer of 2002 saw quite a bit of political action regarding US threats to the very existence of Internet radio. The Copyright Arbitration Royalty Panel (CARP), created by the controversial Digital Millennium Copyright Act, would wipe out US internet radio through high, retroactive, payments that do not apply to ordinary radio. Doc Searls has been covering these developments in a series of articles on our web site. If you haven't been keeping up, read “Hollywood Steps Up Its Assault on the Net While Webcasting Death March Claims KPIG” (www.linuxjournal.com/article/6246) and “Why Are So Many Internet Radio Stations Still on the Air?” (www.linuxjournal.com/6218).
In addition, the US Department of Commerce's second Digital Rights Management (DRM) workshop was held in Washington, DC, and everyone was represented on the panel except the general public. Fortunately, Linux users crashed this little party that the government threw for RIAA, MPAA and other Hollywood-interest groups. Read about it in “DRM Is Theft: New Yorkers for Fair Use Go to Washington” (www.linuxjournal.com/6243) contributed by New York Linux Scene (NYLXS) founder Ruben Safir.
We are seeing more and more clearly that Hollywood has the money and the desire to turn the Internet into a super-regulated, privacy-invading, content-management system. As Doc and others keep asking, “So what are we going to do about it?” While the general public is asleep at the wheel on this one (they'll have a rude awakening before too long), some Linux users are learning how to get politicians' ears. Ruben Safir has more to say about that in “Politics Is Local, So Get Political Locally” (www.linuxjournal.com/6250). At the local level, you can knock on doors and get meetings with your Representative in Congress. Nobody's going to do it for you.
On the technical side, as long as we're still allowed to write software without paying some 21st-century stamp tax, Greg Ward's article on Quixote (www.linuxjournal.com/article/6178) describes a web application framework “written by and for Python programmers”. Quixote has its own templating language based on Python code “to generate long text strings such as HTML documents” instead of “embedding Python code in an HTML-like template language”. This definitely is an approach designed for web programmers rather than designers used to an HTML editor.
We get a lot of submissions for Linux Journal, and due to space limitations in print, many helpful tutorials, reviews and news items appear on the web site instead. Articles are available on the site dating back to 1994, and new ones are posted every day.
Heather Mead is senior editor of Linux Journal.
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