The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: grog@lemis.com (Greg 'groggy' Lehey)
Subject: [TUHS] SCO vs. IBM: NOVELL steps up to the plate
Date: Fri, 30 May 2003 10:50:30 +0930	[thread overview]
Message-ID: <20030530012030.GA39063@wantadilla.lemis.com> (raw)
In-Reply-To: <20030530010126.GA90870@minnie.tuhs.org>

On Friday, 30 May 2003 at 11:01:26 +1000, Warren Toomey wrote:
> On Fri, May 30, 2003 at 10:07:46AM +0930, Greg 'groggy' Lehey wrote:
>> There are plenty of cases where you need to initialize a data
>> structure.  Many data structures are public knowledge, and
>> initialization is a brainless enough task that the code could have
>> been written independently and look almost the same.  Does this line
>> ring a bell?
>>
>> 	(*bdevsw[major(bp->b_dev)].d_strategy) (bp);
>
> And you've got to watch out for these ones, which have been around
> since 1973:
>
> #define EPERM           1               /* Operation not permitted */
> #define ENOENT          2               /* No such file or directory */
> #define ESRCH           3               /* No such process */
> #define EINTR           4               /* Interrupted system call */
>
> So that that extent, there is real UNIX code in Linux 8-)

Heh.  Also in the Third Edition:

/src/UNIX/PDP-11/Third-Edition/dmr/bio.c:       (*bdevsw[dev.d_major].d_strategy)(rbp);
/src/UNIX/PDP-11/Third-Edition/dmr/bio.c:       (*bdevsw[rbp->b_dev.d_major].d_strategy)(rbp);

Yes, this is the reason why I asked Kieran if it was really UnixWare
or UNIX System V.  They need to prove where the code originally came
from before they have any kind of case.

Greg
--
Finger grog at lemis.com for PGP public key
See complete headers for address and phone numbers
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20030530/9f90c188/attachment.sig>


  reply	other threads:[~2003-05-30  1:20 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-28 19:25 Norman Wilson
2003-05-28 23:24 ` Cornelius Keck
2003-05-29  0:02   ` Warren Toomey
2003-05-29  7:49 ` Mike Haertel
2003-05-29 12:16   ` Robert Tillyard
2003-05-29 12:33     ` M. Warner Losh
2003-05-29 23:50       ` Greg 'groggy' Lehey
2003-05-29 23:56         ` M. Warner Losh
2003-05-30  0:37           ` Greg 'groggy' Lehey
2003-05-30  1:01             ` Warren Toomey
2003-05-30  1:20               ` Greg 'groggy' Lehey [this message]
2003-05-29 13:18     ` Kenneth Stailey
  -- strict thread matches above, loose matches on Subject: below --
2003-06-09 14:00 Norman Wilson
2003-06-09 10:20 zmkm zmkm
2003-06-09 15:33 ` Boyd Lynn Gerber
2003-06-08 13:09 Aharon Robbins
2003-06-08 10:32 zmkm zmkm
2003-06-08  9:56 Aharon Robbins
2003-06-09  2:32 ` Kenneth Stailey
2003-05-30  9:01 Wesley Parish
2003-05-30  1:00 Norman Wilson
2003-05-28 12:11 [TUHS] SCO vs. IBM: Eric Raymond striking a blow for ... something Kenneth Stailey
2003-05-28 18:49 ` [TUHS] SCO vs. IBM: NOVELL steps up to the plate Kenneth Stailey

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=20030530012030.GA39063@wantadilla.lemis.com \
    --to=grog@lemis.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;
as well as URLs for NNTP newsgroup(s).