The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: michael@kjorling.se (Michael Kjörling)
Subject: [TUHS] System Economics (was is Linux "officially branded UNIX")
Date: Wed, 15 Mar 2017 14:32:28 +0000	[thread overview]
Message-ID: <20170315143228.GG25424@yeono.kjorling.se> (raw)
In-Reply-To: <ddfb5858-5817-99b3-67fb-34cdc60314ed@kilonet.net>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 2025 bytes --]

On 14 Mar 2017 15:48 -0400, from krewat at kilonet.net (Arthur Krewat):
> Again, I'm including everything ... You could make a case for
> certain Unixes that do not include a pre-existing C compiler being
> bounded by their own development (or any other operating system that
> needs a precursor).  For example, say there was an operating system
> that used a C compiler to build itself that was developed 10 years
> before. That example operating system's timeline would have to
> include said C compiler IMHO.
> 
> On the other hand, an operating system who's sole method of creation
> was engineered in year 0, and was "developed" for 10 years and
> ended, we could say that OS's timeline was a solid 10 years.

Then why limit yourself to the C compiler? The operating system
probably relies on an early bootstrapper layer to start (on the IBM PC
and similar systems this is the BIOS or more recently UEFI; other
architectures are similar or different). The code was probably written
using keyboards, which may or may not rely on firmware for the
physical key to key code to operating system input mapping, let alone
the editor and file system code used to store those first few chunks
of code. And what about the timelines of _those_? At some point the
system becomes self-hosting in the software sense, but it took work to
get to that point. And so on.

I think you see where I am heading with this; if we're going to
include things that were not done specifically for the operating
system in question, then unless we draw a clear line somewhere, we end
up with some guy working on vacuum tube theory a century ago and
_still_ aren't anywhere near an answer to "how long is the timeline of
this piece of software?". Hence, absent some kind of demarcation, that
discussion becomes meaningless.

-- 
Michael Kjörling • https://michael.kjorling.se • michael at kjorling.se
                 “People who think they know everything really annoy
                 those of us who know we don’t.” (Bjarne Stroustrup)


  reply	other threads:[~2017-03-15 14:32 UTC|newest]

Thread overview: 67+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-14 14:43 Clem Cole
2017-03-14 15:38 ` Larry McVoy
2017-03-14 15:51   ` Arthur Krewat
2017-03-14 15:56     ` Larry McVoy
2017-03-14 15:57     ` Michael Kjörling
2017-03-14 16:20       ` Arthur Krewat
2017-03-14 18:06         ` Jason Stevens
2017-03-14 18:31           ` Clem Cole
2017-03-14 18:59             ` Jason Stevens
2017-03-14 18:20         ` Clem Cole
2017-03-14 19:48           ` Arthur Krewat
2017-03-15 14:32             ` Michael Kjörling [this message]
2017-03-15 15:36               ` Arthur Krewat
     [not found]                 ` <58c9623b.law1Aw2ufj3DFNA1%schily@schily.net>
2017-03-15 15:54                   ` Arthur Krewat
2017-03-15 15:59                 ` Larry McVoy
2017-03-15 17:43                   ` Warner Losh
2017-03-15 19:02                     ` Larry McVoy
2017-03-15 19:14                       ` Warner Losh
2017-03-14 18:41         ` Warner Losh
2017-03-17 18:16           ` [TUHS] GNU vs BSD before the lawsuit and before Linux Tony Finch
2017-03-17 18:52             ` Jeremy C. Reed
2017-03-19  7:18               ` arnold
2017-03-19  9:05                 ` Wesley Parish
2017-03-19 18:37                 ` Warner Losh
2017-03-17 19:54             ` Ron Natalie
2017-03-14 18:18   ` [TUHS] System Economics (was is Linux "officially branded UNIX") Clem Cole
2017-03-14 16:20 ` tfb
2017-03-14 22:45 ` Josh Good
2017-03-15  1:11   ` Clem Cole
2017-03-15  7:55     ` arnold
2017-03-15 19:28     ` Josh Good
2017-03-15 19:35       ` Clem Cole
2017-03-15 20:26         ` Ron Natalie
2017-03-15 23:22           ` 'Josh Good'
2017-03-15 19:45       ` Clem Cole
2017-03-15 20:27         ` Larry McVoy
2017-03-15 20:48           ` Clem Cole
2017-03-15 23:46           ` Arthur Krewat
2017-03-16  0:45             ` Clem Cole
2017-03-16  1:27               ` Steve Nickolas
2017-03-16  3:09                 ` Ron Natalie
2017-03-16  3:18                   ` Charles Anthony
2017-03-16  3:36               ` Dan Cross
2017-03-16  4:08                 ` arnold
2017-03-16 12:51               ` Arthur Krewat
2017-03-16 13:18                 ` William Pechter
2017-03-17 21:20               ` Josh Good
2017-03-16 15:42           ` Chet Ramey
2017-03-16 17:29             ` William Pechter
2017-03-15 23:55         ` Josh Good
2017-03-16  0:05           ` William Pechter
2017-03-15 20:08       ` Clem Cole
2017-03-16  0:46         ` Wesley Parish
2017-03-16  0:52           ` Clem Cole
2017-03-16 19:47       ` Dave Horsfall
2017-03-17  2:16         ` Jason Stevens
2017-03-17 15:55           ` Warner Losh
2017-03-17 21:11           ` Dave Horsfall
2017-03-14 19:01 Noel Chiappa
2017-03-14 20:05 Clem Cole
2017-03-14 20:16 ` Arthur Krewat
2017-03-14 20:54 ` Dan Cross
2017-03-14 21:19   ` Clem Cole
2017-03-16 15:40 Norman Wilson
2017-03-16 17:26 ` William Pechter
2017-03-16 18:45   ` Clem Cole
2017-03-16 22:17 ` Dave Horsfall

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

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

  git send-email \
    --in-reply-to=20170315143228.GG25424@yeono.kjorling.se \
    --to=michael@kjorling.se \
    /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 NNTP newsgroup(s).