OSTG | SourceForgeThinkGeekIT Product GuideLinux.comNewsForgefreshmeatNewslettersTechJobsSlashdot Broadband X 
Welcome to Slashdot
 Login
 Why Login?
 Why Subscribe?

 Sections
 Main
 Apache
 Apple
 AskSlashdot
  7 more
 Books
 BSD
 Developers
  1 more
 Games
  7 more
 Interviews
 IT
 Linux
  4 more
 Politics
 Science
  2 more
 YRO
 
 Help
 FAQ
 Bugs

 Stories
 Old Stories
 Old Polls
 Topics
 Hall of Fame
 Submit Story

 About
 Supporters
 Code
 Awards

 Services
 Broadband
 PriceGrabber
 Product Guide
 Special Offers
 Tech Jobs
 IT Research

Back To SCO
Caldera
Unix
Posted by timothy on Wed Sep 10, '03 02:45 PM
from the witty-repartee dept.
wampl3r writes " Eric Raymond and Bruce Perens deliver a great response to SCO's recent Letter to the Open Source Community. Their response does a good job of presenting many of the finer points we have been arguing about around here, but it's nice to see them in such a formal, well-thought-out letter." Munchola adds "Meanwhile, ComputerWire, from where McBride misquoted Perens in the first place, sets the record straight: 'In his statement McBride appears to have attributed a ComputerWire paraphrase as a quote from Perens.'" stefan points to this response to McBride's letter from Kevin Bedell, LinuxWorld Magazine's Editor. Below, find one reader's idea about the "stolen lines" SCO claims are in the Linux kernel, and one expert's claim that SCO might not know some of its own source code very well.

VikingBrad writes "The Sydney Morning Herald has an article on Dr Warwick Toomey of The Unix Heritage Society claiming that SCO may not know the origin of code in System V, including claims that there is a lot of BSD software in Sys V."

Alex writes "I wondered where the 100k+ lines of copied code in the linux kernel would come from in comparison to the SCO Unixware stuff. Then a thought popped up in my head: what if they just compared linewise? All those empty lines in the code would have the same content. But how many empty lines are in the Linux Kernel Code? This small shell script counts them for you:

emptylines=0; function parse_dir () { for file in $1/*; do if [ -d "$file" ]; then parse_dir $file; else while read line; do if [ "$line" = "" ]; then emptylines=$[$emptylines+1]; echo $emptylines; fi; done

Kernel 2.4.22, yet cleaned of the code which SCO claimed was stolen, has still 733140 empty lines, probably copied and pasted by the bad, bad kernel developers from the good, good SCO guys..."

 

 
Slashdot Log In
Nickname:

Password:

Public Terminal

[ Create a new account ]

Related Links
· Compare the best prices on: Software/Operating Systems
· VikingBrad
· article
· The Unix Heritage Society
· lot of BSD software in Sys V
· Alex
· wampl3r
· Eric Raymond and Bruce Perens deliver a great response
· Letter to the Open Source Community
· Munchola
· McBride misquoted Perens
· stefan
· response to McBride's letter from Kevin Bedell
· More Caldera stories
· Also by timothy
 
 
This discussion has been archived. No new comments can be posted.
Back To SCO | Log in/Create an Account | Top | 560 comments | Search Discussion
Threshold:
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 
  I enjoy the time that we spend together.
All trademarks and copyrights on this page are owned by their respective owners. Comments are owned by the Poster. The Rest © 1997-2004 OSTG.
[ home | awards | contribute story | older articles | OSTG | advertise | about | terms of service | privacy | faq | rss ]