From: Hans Reiser <reiser@namesys.com>
To: Jason Holt <jason@lunkwill.org>
Cc: reiserfs-list@namesys.com
Subject: Re: reiserfs_fs.h listed in SCO court docs
Date: Wed, 12 Nov 2003 04:23:46 -0800 [thread overview]
Message-ID: <3FB22652.3020700@namesys.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0311122306430.18264-100000@potato.zayda.com>
Jason Holt wrote:
>Just looking through the list of supposedly infringing files at groklaw:
>
>http://www.groklaw.net/article.php?story=2003111203544653
>
>And they list:
>
>fs/reiserfs/do_balan.c
>fs/reiserfs/fix_node.c
>include/linux/reiserfs_fs.h
>
>Hans, did you sneaky look through SCO's IP and use it when writing your code?
>
>
> -J
>
>
>
>
>
Hunh?
Do they claim that we call some function that infringes (I have no idea
what, kmalloc or something....) or that our code in that file itself
infringes? When someone doesn't tell you what is allegedly infringing
it is reallly hard to do anything.
It is really really hard to imagine do_balan.c infringing, as it is not
interface code, and nobody else uses trees like we do, and thus it would
be harder for it to be contaminated by ext2 code (I am always worrying
someone will get lazy and use some ext2 code without my noticing it, and
we audit the code before each time we license it to prevent that) as
part of someone conforming to VFS interfaces..... though I do see some
tiny bit of VFS interface code there in do_balan.c....
I had decided that this was something to ignore and let IBM deal with
but, sigh......
I am coming more and more to believe that Microsoft is almost surely
funding this lawsuit. It is very much their style to do something like
that.
--
Hans
next prev parent reply other threads:[~2003-11-12 12:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-12 23:14 reiserfs_fs.h listed in SCO court docs Jason Holt
2003-11-12 12:23 ` Hans Reiser [this message]
2003-11-13 0:43 ` Stefan Traby
2003-11-12 16:44 ` Hans Reiser
2003-11-13 0:43 ` Andreas Dilger
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=3FB22652.3020700@namesys.com \
--to=reiser@namesys.com \
--cc=jason@lunkwill.org \
--cc=reiserfs-list@namesys.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.