From: "Richard B. Johnson" <root@chaos.analogic.com>
To: Bart Samwel <bart@samwel.tk>
Cc: Brandon Stewart <rbrandonstewart@yahoo.com>,
linux-kernel@vger.kernel.org
Subject: Re: SCO's "proof"
Date: Tue, 19 Aug 2003 11:31:10 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.53.0308191129540.6161@chaos> (raw)
In-Reply-To: <3F423D35.7010603@samwel.tk>
On Tue, 19 Aug 2003, Bart Samwel wrote:
> For those of you who don't speek greek, the greek text is English and reads:
>
> "As part of the kernel evolution towords modular naming, the functions
> malloc and free are being renamed to rmalloc and rfree.
> Compatibility will be maintained by the following assembler code:
> (also see free/malloc below)"
>
> What a way of obfuscating their IP. :)
>
> Bart
>
> Brandon Stewart wrote:
>
> > compliments of "d1rkinator" from yahoo finance message board:
> >
> > The code SCO finds offending:
> >
> > www.heise.de/newsticker/data/jk-19.08.03-000/imh0.jpg
> > www.heise.de/newsticker/data/jk-19.08.03-000/imh1.jpg
> >
> > Its location in Linux:
> >
> > /usr/src/linux-2.4.20/arch/ia64/sn/io/ate_utils.c
> >
> > And its heritage:
> >
> > minnie.tuhs.org/UnixTree/V7/usr/sys/sys/malloc.c.html
> >
> > Ok, SCO: This was easy. Now, show us the other many examples.
> >
> >
> > -
confuse.S follows.
----------------
#
# Enormously complicated assembly-language program released
# under GPL, herein referenced ;)
#
# This program will actually work. Am I violating somebody's
# patent? Sue me.
#
.section .text
rmalloc: jmp malloc
rfree: jmp free
print: jmp printf # Fix typical typos
.global rmalloc
.type rmalloc,@function
.global rfree
.type rfree,@function
.global print
.type print,@function
.end
---------------
Cheers,
Dick Johnson
Penguin : Linux version 2.4.20 on an i686 machine (797.90 BogoMips).
Note 96.31% of all statistics are fiction.
next prev parent reply other threads:[~2003-08-19 15:29 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-19 13:37 Brandon Stewart
2003-08-19 14:52 ` Dr. David Alan Gilbert
2003-08-19 15:01 ` Frank Gevaerts
2003-08-19 15:22 ` Tupshin Harper
2003-08-19 15:25 ` Colin Paul Adams
2003-08-19 20:46 ` Kurt Wall
2003-08-20 18:27 ` bill davidsen
2003-08-20 18:46 ` Valdis.Kletnieks
2003-08-21 3:09 ` Stuart Longland
2003-08-21 10:22 ` Stephan von Krawczynski
2003-08-19 15:07 ` Bart Samwel
2003-08-19 15:31 ` Richard B. Johnson [this message]
2003-08-19 15:14 ` Richard B. Johnson
2003-08-19 15:30 ` Jeff Garzik
2003-08-19 16:52 ` David Mosberger
2003-08-19 17:22 ` Matti Aarnio
2003-08-19 18:00 ` J.A. Magallon
2003-08-19 20:02 ` Richard B. Johnson
2003-08-22 2:31 ` Sulaiman Alhasawi
2003-08-22 7:25 ` Paul Rolland
2003-08-22 8:33 ` Geert Uytterhoeven
2003-08-22 10:35 ` Måns Rullgård
2003-08-23 13:16 ` Leandro Guimarães Faria Corsetti Dutra
2003-08-19 19:18 ` Vojtech Pavlik
2003-08-19 23:34 ` Andrei Barbu "T'Eval"
2003-08-22 9:36 P. Christeas
2003-08-22 9:51 ` Christoph Hellwig
2003-08-22 13:58 ` Kurt Wall
2003-08-22 12:37 ` Con Kolivas
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.4.53.0308191129540.6161@chaos \
--to=root@chaos.analogic.com \
--cc=bart@samwel.tk \
--cc=linux-kernel@vger.kernel.org \
--cc=rbrandonstewart@yahoo.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®