Torvalds Suggests DiBona for SCO Panel
Linux creator Linus Torvalds has suggested Damage Studios cofounder and former Slashdot editor Chris DiBona for membership on the panel of experts to which SCO executive Chris Sontag has offered to reveal evidence of copying code from SCO UnixWare to Linux.
Appointing a believable panel would be difficult, Torvalds said in an e-mail interview. "I suspect the people I'd like to see are not people SCO would care for or [who] would be able to sign an NDA on it. The thing I would want is somebody who is able to actually trace things back in time to be able to make a judgment of whether it came from UnixWare or from Linux. Somebody who is technical enough and has enough background in the kernel that he can follow it down without going mad", he said.
However, Torvalds did suggest DiBona as one possible candidate, along with suggestions to consider "the crowd around Tim O'Reilly" or "any journalist who is technically competent".
DiBona said in an e-mail interview that he is willing to look at SCO's evidence, and he does not have any legal "taint" from previous development work that would make him unable to do so. As an experienced programmer with a background in regression testing and security software, DiBona says he would have to consider the possibility that similar code could be evidence of convergence, not infringement.
"In millions upon millions of lines of code, you can likely expect that in two completely different codebases with much of the same desired outcome (OS, printer driver, whatever) you'll find similar code segments", he said.
Torvalds cited a linux-kernel mailing list (lkml) posting from Christoph Hellwig, a former employee at SCO, then called Caldera. Hellwig points out the impracticality of actually getting copied code from UnixWare accepted by the tough critics on the mailing list. "The kernel internals are so different that you'd need a big glue layer to actually make it work and you can guess how that would be ripped apart in a usual lkml review", Hellwig wrote.
Don Marti is Editor in Chief 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!
- Stunnel Security for Oracle
- SourceClear Open
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- SUSE LLC's SUSE Manager
- My +1 Sword of Productivity
- Managing Linux Using Puppet
- Non-Linux FOSS: Caffeine!
- Google's SwiftShader Released
- 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