From: toby@telegraphics.com.au (Toby Thain)
Subject: [TUHS] Early Clones / Rewrites for TUHS archives
Date: Mon, 18 Dec 2017 12:41:07 -0500 [thread overview]
Message-ID: <b7b6edf9-d798-509e-5f30-9666a7585645@telegraphics.com.au> (raw)
In-Reply-To: <9B5822A8-8F46-4FC4-B12C-681CF0ACB362@quintile.net>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1341 bytes --]
On 2017-12-18 12:35 PM, Steve Simon wrote:
>
> maybe i am wrong but i thought QNX was open source for a while, but then
> it changed hands and the new owners “removed it from the internet”.
>
> interestingly if this is true its only the 2nd time i have heard of this
> happening ever happening. the other one was years ago with the Khronos
> dataflow signal processing system.
What about Solaris.
--T
>
> -Steve
>
>
> On 18 Dec 2017, at 16:34, Andy Kosela <akosela at andykosela.com
> <mailto:akosela at andykosela.com>> wrote:
>
>>
>>
>> On Monday, December 18, 2017, Henry Bent <henry.r.bent at gmail.com
>> <mailto:henry.r.bent at gmail.com>> wrote:
>>
>> On 18 December 2017 at 10:46, Larry McVoy <lm at mcvoy.com
>> <mailto:lm at mcvoy.com>> wrote:
>>
>>
>> I think that it lives on in cars, someone told me that QNX is
>> the basis
>> for a lot of the car stuff. Anyone know?
>>
>>
>> Quite a few car systems, it seems:
>> http://qnxauto.blogspot.ca/2015/06/the-to-z-of-qnx-in-cars.html
>> <http://qnxauto.blogspot.ca/2015/06/the-to-z-of-qnx-in-cars.html>
>>
>>
>> I remember in the late 90s there was a demo of QNX running the whole
>> OS with GUI including web browser etc. from 1.44MB floppy. It was
>> very fast too! Too bad they never open sourced it.
>>
>> --Andy
next prev parent reply other threads:[~2017-12-18 17:41 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-12 14:40 Clem Cole
2017-12-12 16:29 ` Random832
2017-12-12 16:41 ` Random832
2017-12-13 4:16 ` Jason Stevens
2017-12-13 21:22 ` Nemo
2017-12-14 0:26 ` Robert Swierczek
2017-12-18 10:10 ` Peter Jeremy
2017-12-18 15:46 ` Larry McVoy
2017-12-18 15:57 ` Steve Nickolas
2017-12-18 15:59 ` Larry McVoy
2017-12-18 16:13 ` Steve Simon
2017-12-18 16:18 ` Arthur Krewat
2017-12-18 16:15 ` Henry Bent
2017-12-18 16:34 ` Andy Kosela
2017-12-18 16:39 ` Gregg Levine
2017-12-18 17:35 ` Steve Simon
2017-12-18 17:41 ` Toby Thain [this message]
2017-12-18 18:41 ` Brad Spencer
2017-12-18 16:37 ` Gregg Levine
2017-12-18 18:32 ` Bakul Shah
2017-12-18 16:53 ` Clem Cole
2017-12-18 17:08 ` Kurt H Maier
2017-12-12 15:16 Noel Chiappa
2017-12-12 16:01 ` Warner Losh
2017-12-13 2:15 ` Nigel Williams
2017-12-13 13:46 ` Clem Cole
2017-12-13 16:58 ` Larry McVoy
2017-12-13 19:03 ` Clem Cole
2017-12-16 4:50 ` 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=b7b6edf9-d798-509e-5f30-9666a7585645@telegraphics.com.au \
--to=toby@telegraphics.com.au \
/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).