Computer Old Farts Forum
 help / color / mirror / Atom feed
From: bakul at bitblocks.com (Bakul Shah)
Subject: [COFF] [TUHS] man Macro Package and pdfmark
Date: Tue, 18 Feb 2020 15:04:30 -0800	[thread overview]
Message-ID: <01DD0405-D65B-4557-AD0E-4A128334DE2E@bitblocks.com> (raw)
In-Reply-To: <CAC20D2PAxqQROiu_JjfeT+OidZ78NakOf+cNk88Z7F5zCkgvmg@mail.gmail.com>

On Feb 18, 2020, at 1:51 PM, Clem Cole <clemc at ccc.com> wrote:
> 
> 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.'

Used to be that you would get schematics with your electrical or
electronic appliance. I used these to repair a few things, some
times by improvising. IIRC even the original IBM PC came with
schematics.

Given that experience, I felt that paid for software should
come with sources so that when something goes wrong you can
figure out what happened and may be find a way around it. I
had no problem trying to "use the source" but first they had
to provide it; the real documentation! If in the original
vendor goes out of business or decides to stop supporting a
product you bought, you're not stuck. Just as the original
Tektronix oscilloscopes continue being useful.

I do believe this should be a 'birth right'. If this was
always provided, RMS might not have come up with the copyleft!
This is a separate issue from giving away your own software
with sources or controlling what others can do with the sources
you gave away, or paying or being paid to produce such s/w.


  reply	other threads:[~2020-02-18 23:04 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
2020-02-18 23:04                           ` bakul [this message]
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=01DD0405-D65B-4557-AD0E-4A128334DE2E@bitblocks.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).