From: steve jenkin <email@example.com>
To: TUHS <firstname.lastname@example.org>
Subject: [TUHS] Re: Thoughts on Licenses
Date: Sun, 3 Jul 2022 18:11:36 +1000 [thread overview]
Message-ID: <93C473EA-F786-445D-9A03-FED3EBE4961A@canb.auug.org.au> (raw)
> On 3 Jul 2022, at 12:27, Larry McVoy <email@example.com> wrote:
> I love the early Unix releases because they were so simple, processors
> were simple then as well.
Bell’s Observation on Computer Classes has brought surprises
- we’ve had some very popular new devices appear at the bottom end of the market and sell in the billions.
Even 10yrs ago, I’d not have expected Apple to build their own Silicon & certainly not to make a high-performance system based on ARM.
I’d expect more surprises will come, selling in huge numbers.
An obvious application area is Networking + Storage, but many other possibilities exist.
$10 interface for SATA drives to Ethernet would solve a lot of SOHO / SME storage problems, if only a local backup to the Cloud.
MIT has produced ports of v6 for x86 & RISC-V - used for teaching purposes.
Could a version of v6 or v7 run on a microcontroller? Perhaps.
Not many versions of Linux run so leanly.
If a product based on a microcontroller & v6/v7 became a very popular product,
Copyright & Ownership might become an issue :(
Even after the “SCO v IBM” case someone might see a payday.
But why would anyone use "Version Zero" in what turned out to be quite a line of OS’s from Dept 1127 / CSRC??
Plan 9 or Inferno - born multi-processor, network aware and embedding 30+ years experience -
would be the obvious platform for a “new small thing”.
You’ve already covered on-list the Plan 9/ Inferno licensing, and there’s no impediment.
While Vintage Cars are fascinating to gawk at and may be rewarding to repair & rebuild,
they don’t include modern materials, designs, performance and safety.
Fun for a hobby & special event, but not 1st choice for daily use.
I think v6 on different platforms will have a very long life in a few areas,
but is not what I’d choose for a commercial product.
Steve Jenkin, IT Systems and Design
0412 786 915 (+61 412 786 915)
PO Box 38, Kippax ACT 2615, AUSTRALIA
next prev parent reply other threads:[~2022-07-03 8:12 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-02 18:15 [TUHS] " Clem Cole
2022-07-02 19:07 ` [TUHS] " Marc Donner
2022-07-02 20:57 ` Warner Losh
2022-07-02 21:02 ` Larry McVoy
2022-07-02 23:54 ` Clem Cole
2022-07-03 2:03 ` Warner Losh
2022-07-03 2:27 ` Larry McVoy
2022-07-03 8:11 ` steve jenkin [this message]
[not found] ` <F579710B-5568-431D-92CC-88D49C3D9BE6@gmail.com>
2022-07-03 14:39 ` Larry McVoy
2022-07-03 14:59 ` Clem Cole
2022-07-03 15:30 ` Bakul Shah
2022-07-03 16:26 ` Clem Cole
2022-07-03 16:55 ` Kevin Bowling
2022-07-03 17:15 ` Clem Cole
2022-07-03 17:48 ` Bakul Shah
2022-07-03 19:48 ` Clem Cole
2022-07-03 21:23 ` Matthias Bruestle
2022-07-03 22:40 ` Clem Cole
2022-07-04 3:01 ` Norman Wilson
2022-07-04 12:33 ` Paul Winalski
2022-07-03 21:38 ` Jay Logue via TUHS
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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).