Bandits Give Microsoft a Lesson on Copying, Stealing
the451.com reported last week that Brad Smith, deputy general counsel for the company, asked at a meeting, "How can you steal something if the original is still there after you've made the copy?"
The answer to Smith's question is that copying and stealing are different, the bandit argued. "Any corporate counsel who didn't get his law degree out of the back of a comic book should know the difference between copying, which is often legal, and stealing, which is a crime", the bandit said. Customers have the right to make some copies, such as quotations, backups and personal copies on portable devices, and Microsoft's so-called "Digital Rights Management" attacks legitimate copying along with copyright infringement, he added.
Although Microsoft is free to disable copying functionality in its own software products, the bandit said, even people who don't use Microsoft's software should be concerned by the company's "close the PC" plan, described at http://research.microsoft.com/crypto/openbox.asp. The plan "involves making minor modifications to the PC's hardware to allow Microsoft to make a secure version of the Windows Media Player", and, according to the site, some hardware vendors are already close to signing on.
Will Microsoft be able to use the "minor modifications" to lock out non-Microsoft software? Will Microsoft's hardware-based attack on free speech and fair use succeed where software alone has failed? Nobody knows. And will Microsoft ever learn the difference between copying and stealing? "I'll keep stealing until they do", the bandit said.
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