From: Steve Nickolas <usotsuki@buric.co>
To: TUHS <tuhs@tuhs.org>
Subject: [TUHS] Re: Re-implementations/Clean-Rooms et al.
Date: Thu, 8 Sep 2022 20:05:44 -0400 (EDT) [thread overview]
Message-ID: <alpine.DEB.2.21.2209081957440.12972@sd-119843.dedibox.fr> (raw)
In-Reply-To: <CANCZdfoHB2RSa+XVHfbQ9MxJsVL7dr8Bh0bBpsk7Z7hMEyaXhg@mail.gmail.com>
On Thu, 8 Sep 2022, Warner Losh wrote:
> On Thu, Sep 8, 2022 at 5:29 PM Steve Nickolas <usotsuki@buric.co> wrote:
>
>> On Thu, 8 Sep 2022, Warner Losh wrote:
>>
>>> But it likely didn't matter, since 32v likely lost its copyright
>>> protection due to AT&T distributing too many copies without the required
>>> copyright markings. At least that was the preliminary ruling that caused
>>> the suit to be settled... AT&T didn't want it finalized, though the cat
>>> was somewhat out of the bag at this point...
>>
>> It would be nice if that were an absolute rather than a probably, because
>> then the status for 32V wouldn't be clouded.
>>
>
> It would be nice. At this late date, one wonders what would happen if it
> were litigated again... I suspect that nobody would bother given the
> small possible gain and the huge expense... But it would also reduce
> shareholder values to explicitly say there's no copyright here or to
> clarify that the ancient licenses are valid. So we're in this state
> where it's basically free and clear, treated like it's free and clear,
> but really isn't free and clear.
>
> Warner
I'm probably the only one brazen enough to put it to the test.
For some years, I've wanted to create a free implementation of System V,
and then move on from there. (I know there's limited utility for such a
thing, because of the BSDs.)
A few things actually hinge on this. If it were considered a fact, and
not a mere opinion, that 32V was PD, then I could be sure that certain
things were safe to use, rather than having to rewrite (including some
particularly tricky stuff the BSDs never fully reimplemented, like
diff(1)).
I actually did write a replacement for the Caldera header. (I still hold
that the Caldera license is void because it has a Caldera copyright claim,
and it has been proven in court that they didn't have the copyright to
give.) It just says why I think it *should* be safe to use the code.
-uso.
next prev parent reply other threads:[~2022-09-09 0:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-08 21:50 Clem Cole
2022-09-08 22:16 ` Larry McVoy
2022-09-08 22:26 ` Warner Losh
2022-09-08 22:28 ` Warner Losh
2022-09-08 23:30 ` Steve Nickolas
2022-09-08 23:42 ` Warner Losh
2022-09-09 0:05 ` Steve Nickolas [this message]
2022-09-09 0:17 ` Larry McVoy
2022-09-09 0:52 ` Steve Nickolas
2022-09-09 2:16 ` Larry McVoy
2022-09-08 23:34 ` Clem Cole
2022-09-08 22:17 ` Warner Losh
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=alpine.DEB.2.21.2209081957440.12972@sd-119843.dedibox.fr \
--to=usotsuki@buric.co \
--cc=tuhs@tuhs.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).