unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Giorgos Keramidas <keramida@ceid.upatras.gr>
Subject: Re: "MIT/GNU/Linux"
Date: Sun, 31 Dec 2006 17:34:33 +0200	[thread overview]
Message-ID: <87lkkot6ye.fsf@kobe.laptop> (raw)
In-Reply-To: 87ejqikz0d.fsf@lion.rapttech.com.au

On Sat, 30 Dec 2006 11:28:50 +1100, Tim X <timx@nospam.dev.null> wrote:
>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?

"Solaris" is considered to be the "SunOS" operating system, plus a
graphical user environment, and a few other components.

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

"SunOS" 4.X was BSD-based.  Sun replaced the BSD-based core of the
system with a System V derivative, creating SunOS release 5.0.  At the
same time, a new marketing name was introduced for SunOS 5.0 and it
accompanying set of components.  This name was "Solaris 2".

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

There is a nice table of Solaris vs. SunOS versions here:

    http://en.wikipedia.org/wiki/Solaris_Operating_System

I can't verify the correctness of *all* these release versions, but it
may help a bit.

The *real* point, however, is that there is ample precedent for calling
parts of a system with a codename that is different from the whole.

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

Exactly :)

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

Also true.

  parent reply	other threads:[~2006-12-31 15:34 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                           ` "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                     ` Giorgos Keramidas [this message]
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=87lkkot6ye.fsf@kobe.laptop \
    --to=keramida@ceid.upatras.gr \
    /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).