Save the BBC from Windows DRM! - Update
The BBC has a long and glorious past as a technological innovator. Throughout the history of broadcasting, it has often been the first to develop and promote new technologies. Sadly, it seems now to be teetering on the brink of making technical choices that will not only damage its own reputation as a world-class institution, but which will also have serious knock-on consequences for free software.
As the worlds of computing and media began increasingly to overlap, it was inevitable that the BBC would need to make decisions about which formats and licensing schemes it would adopt for digital versions of its content that were delivered over the Internet.
To begin with, it offered RealMedia streams for its Audio on Demand service, which meant that GNU/Linux users were on an equal footing with those running Windows. Even more promising was the BBC's participation in the Creative Archive project. This was set up in April 2005 by the BBC and several other major UK institutions to make archive video and audio material available under the Creative Archive licence, which was based on the Creative Commons licences. As well as offering liberal licensing terms, the Creative Archive also chose to release the material in a variety of formats - Quicktime, Windows Media and MPEG1 - to promote the widest possible use.
Against this background, then, the hopes were obviously high that the BBC's latest foray into Internet broadcasting, its on-demand service that would allow people to download television and radio programmes after they were broadcast, would continue this even-handed approach and support all computer platforms.
But the current recommendations contain a real shocker, a consequence of the fact that the BBC has decided to use DRM in its new iPlayer software to control how on-demand material is viewed. That's bad enough, if understandable given the hideously complicated situation concerning the rights to the material that the BBC wants to make available. But worse is how it has decided to implement this approach. As the report explains:
the files would require DRM to ensure that they were appropriately restricted in terms of time and geographic consumption. The only system that currently provides this security is Windows Media 10 and above. Further, the only comprehensively deployed operating system that currently supports Windows Media Player 10 and above is the Windows XP operating system. As a result of these DRM requirements the proposed BBC iPlayer download manager element therefore requires Windows Media Player 10 and Windows XP.
Only those running Windows XP (or Vista) and Windows Media Player 10 will be able to access the BBC's proposed on-demand service. Users of GNU/Linux (and the Apple Macintosh for that matter) are to be cast into the outer darkness. That's around 25% of the potential audience according to this BBC podcast, which contains a fascinating discussion of many of the key issues around this decision. From this it also emerges that the reason that the BBC felt obliged to take this route was because “doing something is better than doing nothing
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!
- Paranoid Penguin - Building a Secure Squid Web Proxy, Part IV
- SUSE LLC's SUSE Manager
- Google's SwiftShader Released
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- Managing Linux Using Puppet
- My +1 Sword of Productivity
- Non-Linux FOSS: Caffeine!
- SuperTuxKart 0.9.2 Released
- Parsing an RSS News Feed with a Bash Script
- 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