Slashdot Mirror
Open Source Community Approaches SCO
An anonymous reader writes "eWeek has an article about the open source community approaching SCO. SCO now says there are over a million lines of offending code in Linux and they still won't show them to anybody."
but they're still bluring out other parts
http://news.com.com/2100-1016_3-5065286.html
The One Rule Of Chess You'll Ever Need: Don't play someone who carries a kit in their bookbag.
~4.4 million. They're saying at least 1/4 of the code is Unix System V. Yeah, whatever.
My journal has hot
Google does. According to this site:
Linux 2.5.37 (Sep 2002) is 5100081 lines of code, 152 MB.
So according to SCO, almost 20% of Linux is copied directly from their code. I can't believe they're even seriously trying any more, what with this and their blatant misreading of copyright law claiming that licenses allowing multiple copies to be made are invalid.
++ Say to Elrond "Hello.".
Elrond says "No.". Elrond gives you some lunch.
According to here:
Linux 0.01 (Sep 1991) is 10239 lines of code, 0.2 MB.
Linux 0.10 (Dec 1991) is 17750 lines of code, 0.4 MB.
Linux 0.99 (Dec 1992) is 81091 lines of code, 2.2 MB.
Linux 1.0.0 (Mar 1994) is 176250 lines of code, 4.7 MB.
Linux 1.2.0 (Mar 1995) is 310950 lines of code, 8.4 MB.
Linux 2.0.0 (Jun 1996) is 777956 lines of code, 22 MB.
Linux 2.2.0 (Jan 1999) is 1800847 lines of code, 52 MB.
Linux 2.4.0 (Jan 2001) is 3377902 lines of code, 100 MB.
Linux 2.5.37 (Sep 2002) is 5100081 lines of code, 152 MB.
We've been discussing this on the gentoo forums just now, and we've found that:
1) Their example is from the IA64 port of linux 2.4 (its not in 2.6)
2) Their example can be traced back to 2.11BSD
3) The greek in the sco code is actually english, with the font changed to english (Stupid obfucation attempt) heres what it says:
"As part of the kernel evolution towards modular naming, the functions malloc and mfree are being renamed to rmalloc and rmfree. Compatibility will be maintained by the following assembler code: (also see mfree/rmfree below)"
We're still discussing it on the gentoo forums here
This is from a heise.de article .
Two slides show some code (1 2)
that may come from Fifth Edition UNIX.
Clickable links
Heise News shows the code:
The code seems to come from arch/ia64/sn/io/ate_utils.c, copyright by SGI:
Does this code come from: Here (V5) or Here (V7)?
Meanwhile, over at news.com they are reporting more announcements from the conference:
"The SCO Forum crowd applauded when SCO executives announced that an upcoming version of its OpenServer--code-named Legend--will support the latest releases of Java; include new hardware support, such as universal serial bus (USB) printer drivers; contain expanded security features; and provide better compatibility with Microsoft Windows through version 3 of Samba, which is developed by an open-source group. The OpenServer update is scheduled to debut in the fourth quarter of next year."
So we can safely assume that none of the infringing lines of code come from the (working for years now) USB, Samba or Java support. My goodness I'd forgotten just how monumentally useless SCO Unix is.
"I Know You Are But What Am I?"
I wonder, isn't there some requirement for a plaintiff to try to resolve a dispute *before* going to the courts? By refusing to let the kernel developers fix the kernel, they're insisting on the infringement rather than trying to fix it.
main(O){10<putchar((O--,102-((O&4)*16| (31&60>>5*(O&3)))))&&main(2+ O);}
LN2 is cool!
Well, if you look at the freely available and downloadable code for Unix System III, which I nabbed a while back, you can see this code for malloc:
malloc(mp, size)
struct map *mp;
{
register unsigned int a;
register struct map *bp;
for (bp=mp; bp->m_size; bp++) {
if (bp->m_size >= size) {
a = bp->m_addr;
bp->m_addr += size;
if ((bp->m_size -= size) == 0) {
do {
bp++;
(bp-1)->m_addr = bp->m_addr;
} while ((bp-1)->m_size = bp->m_size);
}
return(a);
}
}
return(0);
}
I'm sure this code is included in every Unix internals textbook ever made. I bet you if you grab one of the BSD's malloc.c file, it will look at lot like this too. How many ways can you implement malloc?!
-- Jason
http://www.heise.de/newsticker/data/jk-19.08.03-0
The code seems to come from arch/ia64/sn/io/ate_utils.c, copyright by SGI:a tch-html/patch-2.4.19/linux-2.4.19_arch_ia64_sn_io _ate_utils.c.html
http://www.funet.fi/pub/Linux/PEOPLE/Linus/v2.4/p
Does this code come from:l loc.c.html l loc.c.html
http://minnie.tuhs.org/UnixTree/V5/usr/sys/ken/ma
http://minnie.tuhs.org/UnixTree/V7/usr/sys/sys/ma
Plus...
For version referencing, look here
Justin.
You're only jealous cos the little penguins are talking to me.
Bruce Perens pointed out over at lwn.net that Caldera put this particular code under a BSD license in 2000.
It is tempting, if the only tool you have is a hammer, to treat everything as if it were a nail. - Abraham Maslow