From: Warner Losh <imp@bsdimp.com>
To: Steve Nickolas <usotsuki@buric.co>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: Re: [TUHS] Isaacson v Unix [really RMS bashing]
Date: Sun, 6 Jan 2019 19:39:30 -0700 [thread overview]
Message-ID: <CANCZdfrsrv0ATMssJC7dS=sx8tfggMHHvvSH9L1RJFeFG8TQFQ@mail.gmail.com> (raw)
In-Reply-To: <alpine.BSF.2.02.1901062058370.86901@frieza.hoshinet.org>
[-- Attachment #1: Type: text/plain, Size: 1586 bytes --]
On Sun, Jan 6, 2019, 7:06 PM Steve Nickolas <usotsuki@buric.co wrote:
> On Sun, 6 Jan 2019, A. P. Garcia wrote:
>
> > On Sun, Jan 6, 2019, 7:43 PM Jon Steinhart <jon@fourwinds.com wrote
> >
> > <snip>
> >
> >>
> > I would argue that Linux would not have happened without the internet
> >> making it possible for folks around the world to participate. And I
> think
> >> that there's a good chance that the tools would have been created
> anyway.
> >>
> >
> > That's more or less how I look at it. Back in the day there was
> > comp.sources.unix for example. In Unix itself, there was /usr/ where
> tools
> > developed by users other than the core developers belonged, and there was
> > /usr/ucb/ where they put stuff from Berkeley. The culture surrounding
> Unix
> > has always seemed to encourage outside participation, going back to the
> > lenient licensing of Research Unix, and even before that, when it just
> > existed at Murray Hill.
> >
> >>
> >
>
> If not for GNU, Unix would still have been cloned. Net/2 happened in
> parallel, did it not?
>
Berkeley actively rewrote most of unix yes. Net/1 was released about the
same time GNU was getting started. Net/2 and later 4.4 BSD continued this
trend, where 4.4 was finally a complete system. BSD386 only lagged Linux by
about a year and had much stronger networking support, but supported fewer
obscure devices than linux...
Warner
Ps I know this glosses over a lot, and isn't intended to be pedantic as to
who got where first. Only they were about the same time... and I'm
especially glossing over the AT&T suits, etc.
>
[-- Attachment #2: Type: text/html, Size: 2389 bytes --]
next prev parent reply other threads:[~2019-01-07 2:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-06 23:41 Jon Steinhart
2019-01-07 1:29 ` A. P. Garcia
2019-01-07 1:59 ` Steve Nickolas
2019-01-07 2:39 ` Warner Losh [this message]
2019-01-07 2:59 ` A. P. Garcia
2019-01-07 3:32 ` Warner Losh
2019-01-07 5:05 ` Toby Thain
2019-01-07 5:36 ` Andy Kosela
2019-01-07 1:38 ` Toby Thain
2019-01-07 2:11 ` Larry McVoy
2019-01-07 2:31 ` A. P. Garcia
2019-01-07 0:49 Larry McVoy
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='CANCZdfrsrv0ATMssJC7dS=sx8tfggMHHvvSH9L1RJFeFG8TQFQ@mail.gmail.com' \
--to=imp@bsdimp.com \
--cc=tuhs@tuhs.org \
--cc=usotsuki@buric.co \
/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).