From: Ben Greenfield via TUHS <tuhs@minnie.tuhs.org>
To: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Cc: Noel Chiappa <jnc@mercury.lcs.mit.edu>
Subject: Re: [TUHS] Isaacson v Unix
Date: Sat, 5 Jan 2019 10:37:36 -0500 [thread overview]
Message-ID: <0A800C0E-3D9C-4C76-9A91-BFC3226C42CC@cogs.com> (raw)
In-Reply-To: <CANCZdfqswWuOdOWT=FhpbXb5QX_rdDPhgeCbmoR9u3j1pWYX2w@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1931 bytes --]
> On Jan 5, 2019, at 10:26 AM, Warner Losh <imp@bsdimp.com> wrote:
>
>
>
> On Sat, Jan 5, 2019 at 8:04 AM Ed Carp <erc@pobox.com <mailto:erc@pobox.com>> wrote:
> > I looked, and it too says next to nothing about Unix (which it describes as a
> > "programming language" - pg. 346). Oh well.
>
> Pretty funny, or sad, depending on your viewpoint!
>
> > This is really a pretty serious omission, given that the vast majority of
> > mobile devices now run Android, which is a Unix derivative (Linux). So just
> > about everyone has a Unix-derived thing in their pocket.
>
> To hear some people talk, everything started with Linux, and Torvalds
> is a god. Nonsense.
>
> Even iOS and MacOS are derived from BSD, I believe. I know that MacOS
> is (or has been until relatively recently, at any rate) derived from
> BSD.
>
> MacOS X is derived from BSD + Mach VM, with lots of infusions from BSD and other projects. iOS is derived from MacOS.
I think that it is more clearly expressed as MacOS X has a BSD interface to the Mach VM. Mach has always had this sort of relationship with BSD and it still exists.
iOS…
Ben
>
> Warner
>
> On 1/5/19, Noel Chiappa <jnc@mercury.lcs.mit.edu <mailto:jnc@mercury.lcs.mit.edu>> wrote:
> > >> From: Doug McIlroy
> >
> > >> I have heard also that Isaacson's "Idea Factory" (about Bell Labs)
> >
> > > Did you mean the work of this title by Jon Gertner? (I have yet to
> > pull
> > > down my copy to see what it says about Unix
> >
> > I looked, and it too says next to nothing about Unix (which it describes as
> > a
> > "programming language" - pg. 346). Oh well.
> >
> > This is really a pretty serious omission, given that the vast majority of
> > mobile devices now run Android, which is a Unix derivative (Linux). So just
> > about everyone has a Unix-derived thing in their pocket.
> >
> > Noel
> >
[-- Attachment #2: Type: text/html, Size: 4669 bytes --]
next prev parent reply other threads:[~2019-01-05 15:45 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-05 14:30 Noel Chiappa
2019-01-05 15:04 ` Ed Carp
2019-01-05 15:26 ` Warner Losh
2019-01-05 15:37 ` Ben Greenfield via TUHS [this message]
[not found] <mailman.2.1546724053.30035.tuhs@minnie.tuhs.org>
2019-01-06 3:45 ` Paul McJones
-- strict thread matches above, loose matches on Subject: below --
2019-01-05 21:34 Doug McIlroy
2019-01-05 4:20 Noel Chiappa
2019-01-05 2:26 Doug McIlroy
2019-01-05 2:35 ` Ronald Natalie
2019-01-05 15:31 ` Larry McVoy
2019-01-05 17:01 ` A. P. Garcia
2019-01-05 20:27 ` Paul Winalski
2019-01-05 21:38 ` A. P. Garcia
2019-01-05 21:51 ` Rob Pike
2019-01-05 21:53 ` Rob Pike
2019-01-05 21:52 ` Larry McVoy
2019-01-06 1:50 ` Chris Hanson
2019-01-06 2:18 ` A. P. Garcia
2019-01-05 17:07 ` Donald ODona
2019-01-05 21:20 ` joe mcguckin
2019-01-06 1:43 ` Chris Hanson
2019-01-05 9:08 ` William Corcoran
2019-01-05 12:09 ` Ed Carp
2019-01-05 14:15 ` Paul Winalski
2019-01-05 15:01 ` Ed Carp
2019-01-06 4:35 ` Bakul Shah
2019-01-06 4:52 ` Bakul Shah
2019-01-06 5:00 ` Toby Thain
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=0A800C0E-3D9C-4C76-9A91-BFC3226C42CC@cogs.com \
--to=tuhs@minnie.tuhs.org \
--cc=ben@cogs.com \
--cc=jnc@mercury.lcs.mit.edu \
--cc=tuhs@tuhs.org \
/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).