Re: [Nolug] The Inevitable Thread

We have now identified lots of code copied source from
our precious SCO
Unix.

Here are 2 of the worst offending code snippets:

    kernel/sched.c: n++;
    kernel/signal.c: ++count;

Please look at our SCO-Unix code, you will see how
shamelessly those
lines were copied:

    drivers/scsi.c: n++;
    drivers/keybd.c: ++count;

(this appeared recently on the smlug list:))

M.R.F.

"If you need on_board BIOS you can contacting you
dealer."
"If open upper case is necessary, put out the 4 pads
in the upper case. then, the upper case could be
removing." -- fobonics examples from the Fobonics
Institute home page

--- jacklinux@cox.net wrote:
> One thing I’ve noticed is the lack of mention of
> this SCO law suit. I don’t know how contentious the
> subject is but if it can be friendly, I have a few
> questions that are more speculative. For example,
> there’s a lot of rhetoric online about who’s right
> and who’s wrong, the Microsoft® connection, etc. But
> I haven’t really seen anything definitive on the
> impact on Linux if SCO wins. And maybe I’m being
> simple-minded about it, but if SCO could identify
> the copied code then shouldn’t the distros be able
> to do the same thing and then rewrite it. Wouldn’t
> that make the suite moot? Or would it? And if this
> isn’t an option, then what are some of the
> alternatives? Are any of the distros immune? What
> about the kernel itself? I’m sure the philosophy
> from which Linux was born will survive, but I find
> myself full of FUD and I’m just one novice user so I
> can only imagine what IT shops using or considering
> an open source solution must be going through.
>
> Maybe I just need a hug…..I dunno.
>
>
> ___________________
> Nolug mailing list
> nolug@nolug.org

__________________________________
Do you Yahoo!?
SBC Yahoo! DSL - Now only $29.95 per month!
http://sbc.yahoo.com
___________________
Nolug mailing list
nolug@nolug.org
Received on 06/19/03