From: Larry McVoy <firstname.lastname@example.org> To: "Theodore Y. Ts'o" <email@example.com> Cc: Computer Old Farts Followers <firstname.lastname@example.org>, The Eunuchs Hysterical Society <email@example.com> Subject: Re: [COFF] [TUHS] 386BSD released Date: Wed, 14 Jul 2021 10:50:53 -0700 [thread overview] Message-ID: <20210714175053.GC15842@mcvoy.com> (raw) In-Reply-To: <YO8hpZ4VYln+QxNb@mit.edu> On Wed, Jul 14, 2021 at 01:40:53PM -0400, Theodore Y. Ts'o wrote: > If you must, you could try to claim that AT&T was "Source Available" > --- which is a terminology I've seen some used. But I think your > assumptions of how easily the AT&T License could be obtained, and how > "anyone who wanted it could get it" may be looking at the past with > rose-colored classes. Clem was in "the club". I do remember those times, barely, I was a bit too young to have a clear view of things. But it certainly seemed like some Universities made the source pretty available. UW Madison was not one of those, I had to beg and plead to get access to the source. So Clem's memory is fine, his experience was you could get the source. But that wasn't the universal experience at all, and I agree with Ted that just getting access to the source doesn't make it remotely open source. _______________________________________________ COFF mailing list COFF@minnie.tuhs.org https://minnie.tuhs.org/cgi-bin/mailman/listinfo/coff
next prev parent reply other threads:[~2021-07-14 17:52 UTC|newest] Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <alpine.BSF.firstname.lastname@example.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 [this message] 2021-07-14 18:28 ` Clem Cole 2021-07-14 20:03 ` John Cowan [not found] <email@example.com> [not found] ` <CAKH6PiVCjo3YnTZUVYOCDeffQ6POVwGAQA1QMR9UinkfGn+AmQ@mail.gmail.com> 2021-07-15 6:33 ` 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-18 3:29 ` 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=20210714175053.GC15842@mcvoy.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --subject='Re: [COFF] [TUHS] 386BSD released' \ /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
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).