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: Sat, 30 Dec 2006 11:28:50 +1100	[thread overview]
Message-ID: <87ejqikz0d.fsf@lion.rapttech.com.au> (raw)
In-Reply-To: 87odpmlnze.fsf@kobe.laptop

Giorgos Keramidas <keramida@ceid.upatras.gr> writes:

>
> First of all, there are other examples where "parts" have a different
> name from the "whole".  Consider for example the fine difference between
> "SunOS" and "The Solaris Operating Environment" :)
>

Can you expand on this point? I'm asking as this seems to contradict
what I was told by Sun and other sys admins and recall reading some
years ago. My understanding is that sunOS was what Sun called the
operating system they had prior to Solaris. When they brought out
Solaris, they faced a bit of industry resistance and released SunOS (I
can't remember, but think it might have been v4.5 or v5.4 or something
like that), which was essentially the same as solaris (v2.3?). If
there is a more precise difference, I'd be intrested in knowing it
and/or being corrected.

With respect to comments re kernel == OS, I don't agree. The kernel
and the operating system are two different things, but somewhat
dependent on each other. For example, you could run hurd instead of
the Linux kernel. 

Now for some final clarification - at what point does GNU/Linux become
something other than GNU/Linux? For example, I would expect a
distribution like Debian is certainly of the GNU/Linux variety.
However, what about Red Hat and SuSe? Possibly even more unclear, what
about the distribution Oracle is planning to release as the supported
platform for their Oracle databases, can you also call this GNU/Linux? 

If there are some distributions which are GNU/Linux and some which are
not, what is the generic name used to refer to all of them
collectively (i.e. in the sense of Unix or *nix)? In the old DOS days,
you referred to DOS when talking about the generic OS, and DR DOS, MS
DOS, PC MOS etc when referring to specific flavors. If we want to say
that something runs on all "Linux" based systems, what is the correct
terminology?

I also gather from listening to RMS and from some reading that we
should also avoid referring to GNU software as open source, but
instead as "Free Software". 

Tim

-- 
tcross (at) rapttech dot com dot au

  reply	other threads:[~2006-12-30  0:28 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                   ` Tim X [this message]
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=87ejqikz0d.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).