From: jsteve@superglobalmegacorp.com (Jason Stevens)
Subject: [TUHS] Why Linux not another PC/UNIX [was Mach for i386 ...]
Date: Fri, 24 Feb 2017 10:07:13 +0800 [thread overview]
Message-ID: <BE423CA1-2D95-42CC-BE5D-68B7F13B324E@superglobalmegacorp.com> (raw)
In-Reply-To: <58af66a8.RixQ2R2YtVU32E8p%schily@schily.net>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 2510 bytes --]
Isn't the lack of notices and wide distribution which also lead VM/370 and friends being in the public domain? It's odd now that history is fluid they are now considered open source?
On February 24, 2017 6:48:08 AM GMT+08:00, Joerg Schilling <schily at schily.net> wrote:
>Random832 <random832 at fastmail.com> wrote:
>
>> On Thu, Feb 23, 2017, at 14:15, Clem Cole wrote:
>> > Copyright *protection* is automatic ??? as soon as the code is
>written it
>> > is
>> > considered protected. Copyright *registration* is just a formality
>> > necessary to instigate litigation. There is no time limit for
>> > registration.
>>
>> That's true today, but to my understanding wasn't true in 1988.
>(Well,
>> registration wasn't a requirement to be copyrighted - that
>requirement
>> went away retroactively in 1978, and only applied to unpublished
>works
>> then.) The change seems to have been March 1, 1989 from what I can
>find.
>
From what I have in mind, there have been changes from around 1992 from
>the
>Berne convention. Before, US code (even when it was copyrighted) was
>not
>protected in Europe.
>
>I know that in former times, code was only copyrighted in the USA in
>case a
>sample had been given to a governmental site. I thought this changed
>together
>with the Berne convention....
>
>Given that the AT&T code that was used by BSD does not have a copyright
>notice,
>it seems to be obvious that it was not copyrighted as AT&T did not give
>a
>sample to the government.
>
>So the question was whether there was a copyright problem with the fact
>that
>BSD included the code. The fact that AT&T did give away their code did
>exhaust
>the right to prevent distribution.
>
>BSD on the other side did bundle the right to distribute with the
>condition
>that the license notice must not be removed and that distributors need
>to
>announce that they include software developed at BSD.
>
>AT&T removed this notice and did not announce the porevenance.
>
>This is why BSD finally won...
>
>Jörg
>
>--
>EMail:joerg at schily.net (home) Jörg Schilling D-13353
>Berlin
>joerg.schilling at fokus.fraunhofer.de (work) Blog:
>http://schily.blogspot.com/
>URL: http://cdrecord.org/private/
>http://sourceforge.net/projects/schilytools/files/
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20170224/ab092751/attachment.html>
next prev parent reply other threads:[~2017-02-24 2:07 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-22 3:38 Clem Cole
2017-02-22 4:28 ` Dan Cross
2017-02-22 15:36 ` Clem Cole
2017-02-22 16:11 ` Larry McVoy
2017-02-22 17:00 ` Clem Cole
2017-02-22 17:06 ` Chet Ramey
2017-02-22 18:24 ` Larry McVoy
2017-02-22 19:35 ` Clem Cole
2017-02-22 20:18 ` arnold
2017-02-22 22:11 ` Clem Cole
2017-02-22 21:34 ` Larry McVoy
2017-02-22 22:56 ` Clem Cole
2017-02-22 23:13 ` Larry McVoy
2017-02-22 23:51 ` Clem Cole
2017-02-22 23:51 ` Paul Ruizendaal
2017-02-23 19:15 ` Clem Cole
2017-02-23 20:31 ` Random832
2017-02-23 22:48 ` Joerg Schilling
2017-02-24 2:07 ` Jason Stevens [this message]
2017-02-23 23:06 ` Wesley Parish
2017-02-22 17:41 ` Arthur Krewat
2017-02-22 21:00 ` Michael Kerpan
2017-02-22 22:03 ` Arno Griffioen
2017-02-22 22:51 ` Larry McVoy
2017-02-22 23:29 ` Clem Cole
2017-02-23 4:53 ` Gregg Levine
2017-02-22 22:18 ` Clem Cole
2017-02-24 3:53 ` Dan Cross
2017-02-22 5:56 ` Steve Nickolas
2017-02-24 5:31 ` John Labovitz
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=BE423CA1-2D95-42CC-BE5D-68B7F13B324E@superglobalmegacorp.com \
--to=jsteve@superglobalmegacorp.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).