unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: "Micha Feigin" <michf@post.tau.ac.il>
Subject: RE: "MIT/GNU/Linux" (was: gnu vs. xemacs)
Date: Fri, 29 Dec 2006 15:59:39 +0200	[thread overview]
Message-ID: <000101c72b51$94f5f1c0$0200a8c0@meravi> (raw)
In-Reply-To: <53DBB117-63D5-45D2-8863-7B90BEDB0D54@gmail.com>

 

> -----Original Message-----
> From: help-gnu-emacs-bounces+michf=post.tau.ac.il@gnu.org 
> [mailto:help-gnu-emacs-bounces+michf=post.tau.ac.il@gnu.org] 
> On Behalf Of B. Smith-Mannschott
> Sent: Friday, December 29, 2006 2:46 PM
> To: help-gnu-emacs@gnu.org
> Subject: "MIT/GNU/Linux" (was: gnu vs. xemacs)
> 
> 
> On Dec 29, 2006, at 02:12, Leo wrote:
> > In every emacs-* mailing lists, it has been extremely consistent to 
> > use Linux and GNU/Linux i.e. Linux means the kernel and 
> GNU/Linux is 
> > the operating system that contains a Linux kernel.
> 

The operating system is the kernel. GNU is one of the more popular option (but
not the only one) for the tools running over the operating system. I think
GNU/Linux is just RMS being overly pushy and and egomaniac.

> So lemme see...
> (1) "Linux" is just kernel

Linux is the operating system

> (2) GNU/Linux is the operating system formed by running the 
> GNU tools on top of that kernel
> 
> =>
> 
> Actually, we should use "MIT/GNU/Linux", at least when 

What about qt etc ?

> including X11 on top of GNU/Linux. I'm sure I wouldn't feel 

What if you replace GNU tools? (there are alternative options to most if not
all)

> at all tempted to shorten a handy phrase like 
> "MIT/GNU/Linux". It just rolls of the tongue.
> 
> I'm inclined to agree with the point made by the pedants of 
> "GNU/ Linux", but I do wonder: where does it end?
> 
> *ducks*
> 
> 
> // ben
> 
> 
> 
> 
> 
> _______________________________________________
> help-gnu-emacs mailing list
> help-gnu-emacs@gnu.org
> http://lists.gnu.org/mailman/listinfo/help-gnu-emacs
> 
> 
> 
> +++++++++++++++++++++++++++++++++++++++++++
>  This Mail Was Scanned By Mail-seCure System  at the Tel-Aviv 
> University CC.
> 
> 

  reply	other threads:[~2006-12-29 13:59 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 [this message]
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                           ` "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='000101c72b51$94f5f1c0$0200a8c0@meravi' \
    --to=michf@post.tau.ac.il \
    /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).