Slashdot Mirror


Back To SCO

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..."

11 of 560 comments (clear)

  1. Time To Get Rick by Anonymous Coward · · Score: -1, Offtopic

    Great, you guys get the spammers, and i'll clean up on their 12 yr old daughters.

  2. STOP MODERATING THESE UP by Anonymous Coward · · Score: -1, Offtopic

    These stupid cut/paste posts are NOT USEFUL. The article is NOT SLASHDOTTED. These are trolls trying to get long/annoying posts moderated to the top of everyone's page, or when they're not an AC, a idiot karma whore. Please refrain from moderating these things up as you're doing nothing to help us.

  3. comp.sys.amiga.games by Anonymous Coward · · Score: -1, Offtopic

    Col Seddon wrote the following in usenet, comp.sys.amiga.games, in refrence to people asking where they can find games from the mid 80's to run on the amiga ( mostly via emulation).

    Secondly, EVERYONE WHO PUBLICISES, ADVOCATES, ATTEMPTS OR OTHERWISE AIDS PIRACY ON THIS NEWSGROUP WILL LIKELY BE REPORTED TO THEIR ISP.

    Sorry for the all caps, folks, but this needs to be said, and everyone needs to read it. If you don't like this policy (which I plan to enforce as strictly as I reasonably can, publicising when I report someone to make an example of them) don't post here, it's as simple as that. Feel free to also e-mail abuse@pol.co.uk and complain to them about what I'm doing - they will laugh at you, and probably forward your message to me so I can laugh too.


    Smackdown needs to be laid on comp.sys.amiga.games. I have already started the process, noble people who want to participate, please join the forumn and voice your valued oppinion. There will be much entertainment.

    1. Re:comp.sys.amiga.games by ivanmarsh · · Score: -1, Offtopic

      It's called CYA dude.

    2. Re:comp.sys.amiga.games by Anonymous Coward · · Score: -1, Offtopic

      Can you run BSD on an Amiga?

    3. Re:comp.sys.amiga.games by Anonymous Coward · · Score: -1, Offtopic

      It's called CYA dude.

      How is it CYA when none of the companies that produced games for the amiga in the mid 80's no longer exist? In fact, most of the games have been oficially released into the public domain and can be found legally at a number of sites. Most people just post to the forumn wanting to know weather a game is public domain and if not where can they buy it.

      90% of what random people are looking for is public domain, and this guy for the past few months has been on a threatening rampage. People have been posting crap to the forumn since at least 92' when i started reading it, and 6 months ago this guy comes along and starts trying to moderate what people are talking about. It's time for some smack down.

    4. Re:comp.sys.amiga.games by Anonymous Coward · · Score: -1, Offtopic

      Can you run BSD on an Amiga?

      yep, i've seen netbsd for the amiga

  4. Re:FIRST PS0T FOR THE PEOPLE OF NYC by Anonymous Coward · · Score: -1, Offtopic

    Notwithstanding senators.

  5. Re: Moderators are amazing... by MachineShedFred · · Score: 0, Offtopic

    One smartass remark is a -1 Troll, another that is almost exactly the same is +4 Funny.

    Pull your heads out!

    --
    Slashdot still doesnâ(TM)t support Unicode after it was added to the HTML standard in 1997.
  6. Re:Let's make this a press release! by Anonymous Coward · · Score: -1, Offtopic

    You just have to comment on everything dont you? Especially hours after the original post was made and hours after you've lost any chance at getting your lame attempt of a joke modded up. Are posts like this how you got to be the most prolific poster (3500+ posts! sheish!) this AC has ever seen?

  7. One Solution by Anonymous Coward · · Score: -1, Offtopic

    Because all operating systems are written by programmers, I assume that any operating system is much smarter than me. Thus, any good operating system should try to outsmart me by restricting my options at every turn. Linux, like all versions of Unix, is lousy at restricting my options because at the command line virtually any operation can be performed with ease. (For example, 'rm -rf /win' could 'delete an entire mounted directory, with no popup window warnings whatsoever.)

    I'm proud to say that there is no such danger in Windows Server 2003. Windows pop up when I want to make a change, and then more pop up to ask if I'm sure I want the change. Thankfully, Windows Server 2003 looks after my computer's well-being by occasionally switching configuration settings from the way I want them to what the OS programmers think they might probably ought to be. Boy, I'm just impressed with how smart they are. Once I learned to live with whatever the default settings are on any new hardware I install, I can't say the number of hours I have saved.

    I use that spare time to reboot my Windows Server 2003 machine multiple times a day. Technical support personnel recommend that I do it regularly-- kind of like brushing my teeth. To help remind me of this necessity, windows pop up to tell me to reboot whenever I make a configuration change. By now my machine is minty fresh, I figure.

    There is no such useful rebooting in a Linux system. It is as reliable as the sunrise, with uptimes in weeks, months and years. Virtually no configuration change requires a reboot, to boot. Imagine all that plaque in the computer. Gross!

    In Windows I am prevented from making dangerous fundamental configuration changes unless I use a special "registry editor". I have found it so useful to have this separate editor that I hope in future versions they go all the way and supply a separate editor for each file on the disk-- in that way windows could pop up at every keystroke to warn me that changing any line in the file I am editing could cause the system to not run properly. If this were only the case, people would finally learn that it is best to just stick with the mouse and they would be freed of the need to constantly move their hands back to the keyboard. (If one stops to think about it, the mouse is a much better device to use than the keyboard. Ever hear of someone getting carpal tunnel syndrome from a mouse? No. It's comfortable and ergonomic. Like Morse code devices. That's how long distance communication started, after all.)

    Linux, by contrast, requires no special editor to change configuration files. The fact that there is no "registry" in Linux allows the abomination of using any text editor whatsoever to do the configuration. Can you believe that configuration files are usually stored clear text? Talk about dangerous!

    I am also happy to report that I have experienced no truth to the rumor that Windows disks become corrupt after improper shutdowns. Indeed, I have been forced to improperly shutdown the machine innumerable times after it locks up, and I have no apparent problems to report regarding the disk. No such claim can be made for Linux. They say something about lack of data points. Excuses are all I ever seem to hear from the Linux crowd.

    By sheer size alone, Windows Server 2003 beats Linux hands down. It is so much bigger, it is _obvious_ that it is better. Why would you want a small OS with the large disks and RAM sizes we have these days? For this reason alone, I heartily recommend Windows as a way to maximize resource utilization. Your CPU and disk will constantly be pegged to the limit, the way god intended. The Linux kernel and drivers accounts for only about 750KB. Why, even the Microsoft Win16 subsystem uses more space than that.

    It is no surprise that Windows Server 2003 costs $300 on the retail market and Linux doesn't cost anything. People know what they want, and they want Windows Server 2003. Because Linux is free, that means it's basically worthless. T