unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Tim X <timx@nospam.dev.null>
Subject: Re: "MIT/GNU/Linux"
Date: Sun, 31 Dec 2006 13:36:52 +1100	[thread overview]
Message-ID: <871wmglrjv.fsf@lion.rapttech.com.au> (raw)
In-Reply-To: mailman.2550.1167498938.2155.help-gnu-emacs@gnu.org

Matthew Flaschen <matthew.flaschen@gatech.edu> writes:

>
>> I think you missed the point. RMS does not like the use of the term
>> open source, but prefers free software. 
>
> I'm well aware of that.
>
> The problem is that open source does not necessarily mean free (as in
> liberty) as you can have
>> software in which the sources are open, but the licensing is
>> restrictive and non-free. I personally agree with this distinction
>> unless I have misunderstood his arguement (which is possible and why I
>> mentioned it.).
>
> This is mostly a misconception.  The reason that Stallman doesn't like
> the open source movement is that it is based solely on practical
> expediency, while free software is about morality.  I agree with him
> here, and prefer "free software".  However, in practice, almost all open
> source (as defined by the Open Source Initiative) licenses are also
> free.  The Open Source Definition
> (http://opensource.org/docs/definition.php) has detailed requirements,
> including free redistribution (modified or unmodified) for free or for a
> fee, and access to source.
>
Maybe we are getting down to "hair splitting" a little too much.
However, in an interview I heard with RMS on a podcast, he was very
critical of OSI and the problem with the use of the term open source.
Your quite correct regarding is arguments concerning expediency and
the danger this can represent for general freedom, especially in the
long term. However, he was very very clear about not using the term
open source and I have had e-mails from him correcting me for
referring to GPL's software as open source (this was software released
under the GPL, but not GNU software). AFter a few exchanges and after
listening to that interview, I think I understand exactly what his
concerns are and I have to say I agree. In the interview, the
arguement centred around provision of MS media codecs - one side
argued that it should be easier for people to obtain and install these
codecs as this would increase the number of people switching to GNU
Linux. On the other side, RMS argued that the cost to freedom this
would result in was too high and he would rather see a truely free
system used by less people than pseudo free OS used by a lot. Being a
bit of an old idealist and readily admitting to finding Marxist
theory, while flawed, better than any other, I could appreciate this
point.

>> You might believe that this is all self evident, but I have been using
>> systems based on the Linux kernel since the first release of Slackware
>> and the terminology and how it is applied has not been a static thing.
>> The move away from the general term "Linux" to GNU Linux, while
>> positive in reducing confusion between the OS and kernel references,
>> was not emphasised initially as much as it seems to be now.
>
> Yes, the FSF says (http://www.gnu.org/gnu/gnu-linux-faq.html#always) "It
> took a few years for us to realize what a problem this was and ask
> people to correct the practice. By that time, the confusion had a big
> head start."
>
>> Open source was considered as synonymous with "free software" until Eric
>> Raymond and the OSI blurred things
>
> If I understand right, "open source" was not much used at all until the
> OSI (and their founders) popularized it.

Hmm, not sure. The OSI wold seem a bit of a late arrival in my
chronology. The CS department at the University I worked at in '94 was
already starting to make a bit of a 'big deal' about the fact they
were moving to open source then and even started using the term in
their publicity in '94/95. All PCs in the CS labs were running
slackware at that time (but to be honest, a fair part of this was
because MS Win 31 and DOS were just crippled pretend OSs at that time
and even early, limited and buggy GNU Linux was better). 

Tim

-- 
tcross (at) rapttech dot com dot au

  parent reply	other threads:[~2006-12-31  2:36 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-27 11:46 gnu vs. xemacs H.
2006-12-27 12:57 ` Lennart Borgman (gmail)
2006-12-27 13:10 ` Peter Dyballa
2006-12-27 13:59 ` Sven Bretfeld
2006-12-28 10:27   ` Ramprasad
     [not found]   ` <mailman.2429.1167301573.2155.help-gnu-emacs@gnu.org>
2006-12-28 11:27     ` Tim X
2006-12-28 18:57       ` Matthew Flaschen
     [not found]       ` <mailman.2457.1167332268.2155.help-gnu-emacs@gnu.org>
2006-12-28 23:53         ` Tim X
2006-12-29  1:12           ` Leo
2006-12-29 12:46             ` "MIT/GNU/Linux" (was: gnu vs. xemacs) B. Smith-Mannschott
2006-12-29 13:59               ` Micha Feigin
2006-12-29 14:17                 ` Gian Uberto Lauri
2006-12-29 17:27                 ` "MIT/GNU/Linux" Alexey Pustyntsev
2006-12-29 18:35                   ` "MIT/GNU/Linux" Kim F. Storm
     [not found]               ` <mailman.2488.1167400944.2155.help-gnu-emacs@gnu.org>
2006-12-29 15:29                 ` "MIT/GNU/Linux" Giorgos Keramidas
2006-12-30  0:28                   ` "MIT/GNU/Linux" Tim X
2006-12-30  6:05                     ` "MIT/GNU/Linux" Matthew Flaschen
     [not found]                     ` <mailman.2537.1167458715.2155.help-gnu-emacs@gnu.org>
2006-12-30 12:09                       ` "MIT/GNU/Linux" Tim X
2006-12-30 17:13                         ` "MIT/GNU/Linux" Matthew Flaschen
     [not found]                         ` <mailman.2550.1167498938.2155.help-gnu-emacs@gnu.org>
2006-12-31  2:36                           ` Tim X [this message]
2006-12-31 15:42                             ` "MIT/GNU/Linux" Giorgos Keramidas
2007-01-01  2:45                               ` "MIT/GNU/Linux" Tim X
2006-12-31 15:34                     ` "MIT/GNU/Linux" Giorgos Keramidas
2007-01-01  2:21                       ` "MIT/GNU/Linux" Tim X
2006-12-29 23:12                 ` "MIT/GNU/Linux" Jay Belanger
2006-12-30 15:13                   ` "MIT/GNU/Linux" Micha Feigin
     [not found]                   ` <mailman.2547.1167491771.2155.help-gnu-emacs@gnu.org>
2006-12-30 17:19                     ` "MIT/GNU/Linux" Robert Thorpe
2006-12-30 17:49                 ` "MIT/GNU/Linux" (was: gnu vs. xemacs) Robert Thorpe
2006-12-30 19:20                   ` Matthew Flaschen
     [not found]             ` <mailman.2487.1167396377.2155.help-gnu-emacs@gnu.org>
2007-01-03  6:42               ` "MIT/GNU/Linux" Stefan Monnier
2007-01-03  8:17                 ` "MIT/GNU/Linux" Drew Adams
2007-01-03 10:03                 ` "MIT/GNU/Linux" Matthew Flaschen
     [not found]                 ` <mailman.2685.1167818637.2155.help-gnu-emacs@gnu.org>
2007-01-03 20:33                   ` "MIT/GNU/Linux" Stefan Monnier
2007-01-04  9:14                     ` "MIT/GNU/Linux" Matthew Flaschen
     [not found]           ` <mailman.2475.1167354778.2155.help-gnu-emacs@gnu.org>
2006-12-29 18:23             ` gnu vs. xemacs Hadron Quark
2006-12-29 18:32               ` Ralf Angeli
2006-12-27 19:52 ` David Kastrup
2006-12-28 14:36 ` insert name
2006-12-28 20:25   ` David Kastrup

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=871wmglrjv.fsf@lion.rapttech.com.au \
    --to=timx@nospam.dev.null \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).