From: "Michael Kjörling" <michael@kjorling.se>
To: coff@minnie.tuhs.org
Subject: Re: [COFF] [TUHS] 386BSD released
Date: Thu, 15 Jul 2021 06:33:14 +0000 [thread overview]
Message-ID: <e40f270f-421d-40f6-9e4f-1d205c6de115@localhost> (raw)
In-Reply-To: <CAKH6PiVCjo3YnTZUVYOCDeffQ6POVwGAQA1QMR9UinkfGn+AmQ@mail.gmail.com>
On 14 Jul 2021 22:21 -0400, from douglas.mcilroy@dartmouth.edu (Douglas McIlroy):
> IBM provided source code for the Fortran II compiler.
More recently than that, for the original IBM PC anyone could get (I
believe) the complete schematics, detailed technical information, and
a commented ROM BIOS source code listing just by purchasing their
Technical Reference for, what, $50 or thereabouts?
It certainly wasn't open source according to the Open Source
Definition, but it certainly was _available_ to anyone who wanted a
copy.
What kind of company does that today, in a similar market segment?
--
Michael Kjörling • https://michael.kjorling.se • michael@kjorling.se
“Remember when, on the Internet, nobody cared that you were a dog?”
_______________________________________________
COFF mailing list
COFF@minnie.tuhs.org
https://minnie.tuhs.org/cgi-bin/mailman/listinfo/coff
next parent reply other threads:[~2021-07-15 6:41 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <7wtukxtgag.fsf@junk.nocrew.org>
[not found] ` <CAKH6PiVCjo3YnTZUVYOCDeffQ6POVwGAQA1QMR9UinkfGn+AmQ@mail.gmail.com>
2021-07-15 6:33 ` Michael Kjörling [this message]
2021-07-15 20:44 ` Derek Fawcus
2021-07-15 15:07 ` Clem Cole
2021-07-15 19:33 ` Theodore Y. Ts'o
2021-07-15 20:30 ` Clem Cole
2021-07-16 1:58 ` Theodore Y. Ts'o
2021-07-16 2:14 ` George Michaelson
2021-07-16 18:02 ` Grant Taylor via COFF
2021-07-17 4:09 ` Theodore Y. Ts'o
2021-07-17 6:30 ` [COFF] " Tom Ivar Helbekkmo via COFF
2021-07-17 12:37 ` Theodore Y. Ts'o
2021-07-17 13:30 ` Tom Ivar Helbekkmo via COFF
2021-07-18 3:29 ` [COFF] [TUHS] " Grant Taylor via COFF
2021-07-18 3:42 ` David Arnold
2021-07-18 4:01 ` Grant Taylor via COFF
2021-07-19 13:41 ` Theodore Y. Ts'o
2021-07-19 14:50 ` Clem Cole
2021-07-19 17:38 ` Theodore Y. Ts'o
2021-07-19 19:33 ` John P. Linderman
2021-07-19 20:21 ` Clem Cole
2021-07-20 1:05 ` Grant Taylor via COFF
2021-07-19 20:08 ` Clem Cole
2021-07-20 0:55 ` Theodore Y. Ts'o
2021-07-18 6:44 ` Andy Kosela
2021-07-16 16:11 ` Jonathan Corbet
2021-07-15 23:02 ` joe mcguckin
[not found] <alpine.BSF.2.21.9999.2107140824460.15723@aneurin.horsfall.org>
[not found] ` <213a4c11-3ab2-4b4a-8d6b-b52105a19711@localhost>
[not found] ` <CAE49LGn-gY9eikkwUgS+i3p=ZQV+gk_3BJ5V4_6B4HPbdyRuZw@mail.gmail.com>
2021-07-14 15:01 ` Clem Cole
2021-07-14 17:40 ` Theodore Y. Ts'o
2021-07-14 17:50 ` Larry McVoy
2021-07-14 18:28 ` Clem Cole
2021-07-14 20:03 ` John Cowan
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=e40f270f-421d-40f6-9e4f-1d205c6de115@localhost \
--to=michael@kjorling.se \
--cc=coff@minnie.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).