linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stan Bubrouski <stan@ccs.neu.edu>
To: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: SCO's infringing files list
Date: Tue, 30 Dec 2003 12:27:38 -0500	[thread overview]
Message-ID: <1072805257.1760.13.camel@duergar> (raw)
In-Reply-To: <200312301517.27857.bruno@clisp.org>

Bruno,

Nice work! How many more files left unexplained?

-sb

On Tue, 2003-12-30 at 09:17, Bruno Haible wrote:
> Here's some info about include/linux/ipc.h, also in SCO's list.
> 
> * lxr.linux.no shows that since version 1.0.9, it had only small incremental
>   changes.
> 
> The earliest copy of this file that I've got is from Krishna
> Balasubramanian's ipcbeta+.tar.Z file. This was his second or third
> beta release of SysV IPC for Linux. The file is here:
> http://www.haible.de/bruno/ipcbeta+.tar.Z
> 
> * The include/linux/ipc.h from ipcbeta+.tar.Z is the same as the one in
>   linux-1.0.9 (http://lxr.linux.no/source/include/linux/ipc.h?v=1.0.9)
> 
> I claim that Krishna Balasubramanian wrote this file.
> 
> * The ipcbeta+.tar.Z contents shows how he developed this thing:
>   He looked at various documentation sources (books, manual pages - remember
>   POSIX didn't specify IPC at that time -).
>   He collected some examples like the "dining philosophers" that were floating
>   around on the net.
>   We ran some test programs on other Unices (SunOS 4, possibly also HP-UX).
>   He wrote 40 KB of documentation, explaining each and every system call.
>   ... and someone who puts so much work in testing and documentation should
>   steal the header file??!
> 
> * The value of IPC_PRIVATE is different in Linux. SysV systems define it as
>   (key_t)0, Linux defines it as ((key_t) 0), which extra parentheses.
> 
> * The members of 'struct ipc_perm' are in different order on Linux.
>   SysV systems have them in the order
>      uid, gid, cuid, cgid, mode, seq, key.
>   Linux has them in the order
>      key, uid, gid, cuid, cgid, mode, seq.
> 
> * The values for IPC_CREAT, IPC_EXCL, IPC_NOWAIT are written as octal numbers,
>   which is quite natural, since 9 bits having the same rwxrwxrwx semantics as
>   file permissions can be ORed into it. SysV systems write these constants
>   with 7 octal digits. Linux ipc.h writes them with 8 octal digits.
> 
> * The values of IPC_RMID, IPC_SET, IPC_STAT are different: on Solaris
>   10, 11, 12; on Linux 0, 1, 2.
> 
> * 'struct ipc_kludge' and the corresponding #defines for SEMOP, SEMGET etc.
>   don't exist in SysV systems. They arose only because we wanted to minimize
>   the number of system calls.
> 
> I hope that's enough evidence that Krishna didn't copy the file's contents
> from anywhere.
> 
> Bruno
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
> 


  reply	other threads:[~2003-12-30 17:27 UTC|newest]

Thread overview: 52+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-30 14:17 SCO's infringing files list Bruno Haible
2003-12-30 17:27 ` Stan Bubrouski [this message]
     [not found] <no.id>
2003-12-28  7:04 ` Rick Bressler
  -- strict thread matches above, loose matches on Subject: below --
2003-12-24 12:19 Norman Diamond
2003-12-24 13:11 ` Jussi Laako
2003-12-23 18:49 jpo234
2003-12-23 15:46 jpo234
2003-12-23 15:43 Xose Vazquez Perez
2003-12-22 20:42 Stan Bubrouski
2003-12-22 21:14 ` Joseph Pingenot
2003-12-22 21:23   ` Stan Bubrouski
2003-12-22 21:19 ` Tom Felker
2003-12-22 21:55   ` Linus Torvalds
2003-12-23  0:26     ` jw schultz
2003-12-23  1:17       ` Stan Bubrouski
2003-12-23  9:28       ` Florian Weimer
2003-12-23  9:58         ` Giacomo A. Catenazzi
2003-12-23 12:34           ` Linus Torvalds
2003-12-23 13:17             ` viro
2003-12-23 15:44             ` Giacomo A. Catenazzi
2003-12-23 16:04               ` Mitchell Blank Jr
2003-12-23 16:39                 ` Mitchell Blank Jr
2003-12-23 17:25                   ` Linus Torvalds
2003-12-23 18:40                     ` Charles Cazabon
2003-12-23 18:44                       ` viro
2003-12-23 18:45                       ` Mitchell Blank Jr
2003-12-23 18:52                       ` Matti Aarnio
2003-12-23 19:58                         ` Shawn
2003-12-23 20:08                           ` Stan Bubrouski
2003-12-23 20:25                           ` John Shifflett
2004-01-02 19:45                           ` Bill Davidsen
2003-12-23 18:47                     ` Steven Cole
2003-12-23 20:06                       ` Mitchell Blank Jr
2003-12-23 17:44                 ` Mitchell Blank Jr
2003-12-23 17:56                   ` Linus Torvalds
2003-12-23 18:12                     ` Stan Bubrouski
2003-12-23 18:14                     ` Harry McGregor
2003-12-23 18:27                       ` Stan Bubrouski
2003-12-23 18:40                       ` Disconnect
2003-12-23 18:14                     ` Stan Bubrouski
2003-12-23 19:02                     ` Stan Bubrouski
2003-12-23 19:06                     ` Andries Brouwer
2003-12-23 20:18                       ` Stan Bubrouski
2003-12-23 20:21                       ` Mitchell Blank Jr
2003-12-23 20:27                       ` Linus Torvalds
2003-12-23 16:15               ` venom
2003-12-23 15:50             ` Mitchell Blank Jr
2003-12-23 17:07             ` Andries Brouwer
2003-12-22 23:52   ` Erik Andersen
2003-12-22 23:01 ` Jesper Juhl
2003-12-23 11:18   ` Luiz Fernando Capitulino
2003-12-23  4:50 ` David Schwartz

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=1072805257.1760.13.camel@duergar \
    --to=stan@ccs.neu.edu \
    --cc=linux-kernel@vger.kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).