unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Matthew Flaschen <matthew.flaschen@gatech.edu>
Subject: Re: "MIT/GNU/Linux"
Date: Sat, 30 Dec 2006 12:13:16 -0500	[thread overview]
Message-ID: <45969E2C.6050409@gatech.edu> (raw)
In-Reply-To: <87ac15lh5f.fsf@lion.rapttech.com.au>


[-- Attachment #1.1: Type: text/plain, Size: 3818 bytes --]

Tim X wrote:
> So then, should that be Red Hat Enterprise GNU Linux?

Yes, that would be more accurate (and fair).

> Also, when Larry initially announced that Oracle would do their own
> distribution, while he indicated it would likely be based on RH
> Enterprise, he was not prepared to commit to that. I was not aware he
> (or Oracle) had yet made such a commitment.

It is my understanding from reviews (like
http://ultramookie.com/wayback/2006/10/26/uncompatible-linux/) that it
is based on CentOS, which is in turn recompiled RHEL.
> 
> Obviously, I wasn't clear enough. The point I wanted clarification on
> is whether GNU Linux refers to Linux distributions which comprise of
> only free software or whether it refers to all distributions which use
> both the Linux kernel and GNU utilities and other free software
> regardless of what other non-free software the distribution contains.

Correct, any distribution that is based on both GNU and the Linux kernel
should be called GNU/Linux.  RMS would prefer GNU/Linux distributions
were completely free, but that is separate from the question of naming.

> 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.

> 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.

 and an incresing number of
> companies attempted to jump on the band wagon by releasing their
> sources, but maintaining restrictive licenses etc.

Again, almost every OSI-approved license is also free (as defined by the
FSF).  These restrictive licenses (e.g Microsoft Shared Source) aren't
OSI-approved open source either.

 IIRC, even the
> Linux kernel was not initially released under the GPL. 

No, it was originally under a non-commercial only license, which
wouldn't be OSI-approved open source OR Free.

> it should not be any surprise that some find it unclear exactly when GNU
> Linux is appropriate.

Again, all popular "Linux distributions" are actually GNU/Linux.

You may want to reply off-list.

Matthew Flaschen






[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 252 bytes --]

[-- Attachment #2: Type: text/plain, Size: 152 bytes --]

_______________________________________________
help-gnu-emacs mailing list
help-gnu-emacs@gnu.org
http://lists.gnu.org/mailman/listinfo/help-gnu-emacs

  reply	other threads:[~2006-12-30 17:13 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                         ` Matthew Flaschen [this message]
     [not found]                         ` <mailman.2550.1167498938.2155.help-gnu-emacs@gnu.org>
2006-12-31  2:36                           ` "MIT/GNU/Linux" Tim X
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=45969E2C.6050409@gatech.edu \
    --to=matthew.flaschen@gatech.edu \
    /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).