Computer Old Farts Forum
 help / color / mirror / Atom feed
From: "Theodore Y. Ts'o" <tytso@mit.edu>
To: Tom Ivar Helbekkmo <tih@hamartun.priv.no>
Cc: coff@minnie.tuhs.org, Grant Taylor <gtaylor@tnetconsulting.net>
Subject: Re: [COFF] 386BSD released
Date: Sat, 17 Jul 2021 08:37:08 -0400	[thread overview]
Message-ID: <YPLO9O9hC4gOJaNO@mit.edu> (raw)
In-Reply-To: <m2o8b178pr.fsf@thuvia.hamartun.priv.no>

On Sat, Jul 17, 2021 at 08:30:56AM +0200, Tom Ivar Helbekkmo wrote:
> 
> I seem to remember, relatively shortly after that, a tendency on the net
> to differentiate between "open source" and "Open Source".  Earlier in
> this thread, I mentioned MINIX 1, from 1987.  That version of the OS was
> open source, but not, by the later definition, Open Source.
> (Prentice-Hall, being a publishing company, insisted on having the
> copyright, but the source code was printed in the book, and you could
> order it on floppies or tape for $80.)

Can you provide any references?  A quick Google Search doesn't turn up
what you've described.  Instead there are references such as this:

   "What you will find here is the contents of the last Minix 1 and 2
   releases, 1.7.5 and 2.0.4...

   You won't find all the source here, because Minix came with most
   source, but not all; the C compiler is ACKPACK, a special version
   of the Amsterdam Compiler Kit, carefully cut down and modified to
   run on Minix. Back when this was released, this wasn't open source."

   - https://github.com/davidgiven/minix2

I can imagine marketing folks trying to confuse people by trying to
claim that their product was something it was not --- such as from
Prentice Hall, the publisher of the Minix book. 

					- Ted
_______________________________________________
COFF mailing list
COFF@minnie.tuhs.org
https://minnie.tuhs.org/cgi-bin/mailman/listinfo/coff

  reply	other threads:[~2021-07-17 12:37 UTC|newest]

Thread overview: 26+ 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   ` [COFF] [TUHS] " Michael Kjörling
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 [this message]
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

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=YPLO9O9hC4gOJaNO@mit.edu \
    --to=tytso@mit.edu \
    --cc=coff@minnie.tuhs.org \
    --cc=gtaylor@tnetconsulting.net \
    --cc=tih@hamartun.priv.no \
    /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).