Computer Old Farts Forum
 help / color / mirror / Atom feed
From: clemc at ccc.com (Clem Cole)
Subject: [COFF] [TUHS] man Macro Package and pdfmark
Date: Tue, 18 Feb 2020 16:51:05 -0500	[thread overview]
Message-ID: <CAC20D2PAxqQROiu_JjfeT+OidZ78NakOf+cNk88Z7F5zCkgvmg@mail.gmail.com> (raw)
In-Reply-To: <CACNPpeaeeXi_A13Nf0+oB8BHsQau5QTporX7CdhCXf2JTOBjZA@mail.gmail.com>

moved to coff

On Tue, Feb 18, 2020 at 4:29 PM Wesley Parish <wobblygong at gmail.com> wrote:

> I don't recall ever seeing "open source" used as a description of the
> Unix "ecosystem" during the 90s.
>
Yes, that's my point.  The term 'open' meant was published, open available
anyone could use .. i.e. UNIX

remember the SPEC 1170 work on the 1990s -- the define the 1170 interfaces
and >>publish<< them so anyone could write code to it.



> It was in the air with the (minimal) charges Prentice-Hall charged for
> the Minix 0.x and 1.x disks and source; not dissimilar in that sense
> to the charges the FSF were charging for their tapes at the time.
>
Right...   there were fees to write magtapes (or floppies)

Which comes back to my point... 'open source' was not picking.   The whole
community is standing on the shoulders of the UNIX ecosystem that really
started to take off in the 1970s and 1980s.  But the 'free' part was even
before UNIX.

We stood on the shoulders of things before us.    There just was not (yet)
a name for what we were doing.

As Ted saids, I'll give the Debian folks credit for naming it, but the idea
really, really goes back to the early manufacturers and the early community.

FSF was a reaction to the manufacturers taking away something that some
people thought was their 'birth right.'
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/coff/attachments/20200218/eb1f2334/attachment.html>


       reply	other threads:[~2020-02-18 21:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <202002171520.01HFKqKi026749@tahoe.cs.Dartmouth.EDU>
     [not found] ` <4d252035b323b7583c5760c952d1982c@firemail.de>
     [not found]   ` <202002171839.01HId8FT1358073@darkstar.fourwinds.com>
     [not found]     ` <e5b0fe5d7296bc11e4f380ec39a8f223@firemail.de>
     [not found]       ` <CAFH29tofawAMrywyW=S5ZW2F-U-1tbOm55+PMN+_vg=uDWFUNg@mail.gmail.com>
     [not found]         ` <202002180017.01I0HI0I1415945@darkstar.fourwinds.com>
     [not found]           ` <m1j3xUB-0036tPC@more.local>
     [not found]             ` <CAC20D2Mv_XqaBi=rx1rOaQLWmp3Ds_r7czG2OJV8nOuC=rrLaw@mail.gmail.com>
     [not found]               ` <202002181528.01IFSogM030831@freefriends.org>
     [not found]                 ` <alpine.BSF.2.02.2002181041410.44251@frieza.hoshinet.org>
     [not found]                   ` <20200218164031.GA147128@mit.edu>
     [not found]                     ` <alpine.BSF.2.02.2002181332010.54311@frieza.hoshinet.org>
     [not found]                       ` <CACNPpeaeeXi_A13Nf0+oB8BHsQau5QTporX7CdhCXf2JTOBjZA@mail.gmail.com>
2020-02-18 21:51                         ` clemc [this message]
2020-02-18 23:04                           ` bakul
2020-02-19  1:40                             ` clemc
2020-02-19 14:54                             ` [COFF] " 

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=CAC20D2PAxqQROiu_JjfeT+OidZ78NakOf+cNk88Z7F5zCkgvmg@mail.gmail.com \
    --to=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).