From: dave@horsfall.org (Dave Horsfall)
Subject: [TUHS] System Economics (was is Linux "officially branded UNIX")
Date: Fri, 17 Mar 2017 06:47:55 +1100 (EST) [thread overview]
Message-ID: <alpine.BSF.2.20.1703170646020.9589@aneurin.horsfall.org> (raw)
In-Reply-To: <20170315192815.GA15120@naleco.com>
On Wed, 15 Mar 2017, Josh Good wrote:
> It is obvious to me that RMS's GNU movement was aimed at solving that
> very problem. And if that was a problem, then the "UNIX openness" you
> talk about does not seem to have been very practical at all. At least,
> it was totally useless to PC hackers, like Linus Torvalds - he had to
> write his own UNIX, because he was not able to get any UNIX source code
> he could readily compile and run on his i386.
Perhaps I'm confused (not uncommon) but I have distinct memories of having
a source licence for my BSD/OS system on a 386...
--
Dave Horsfall DTM (VK2KFU) "Those who don't understand security will suffer."
next prev parent reply other threads:[~2017-03-16 19:47 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
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 [this message]
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=alpine.BSF.2.20.1703170646020.9589@aneurin.horsfall.org \
--to=dave@horsfall.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).