The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Andy Kosela <akosela@andykosela.com>
To: Adam Thornton <athornton@gmail.com>
Cc: TUHS main list <tuhs@tuhs.org>
Subject: [TUHS] Re: UNIX on (not quite bare) System/370
Date: Tue, 20 Dec 2022 16:29:21 +0100	[thread overview]
Message-ID: <CALMnNGg35YBJWj1dk2GhrUR-B4+Hv6WAj32qDS7X7aNM74c7yQ@mail.gmail.com> (raw)
In-Reply-To: <4942C729-FCE2-4075-9B1B-08CB7FC33813@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1203 bytes --]

On Tuesday, December 20, 2022, Adam Thornton <athornton@gmail.com> wrote:

> I mean, just a Unix, without all the cruft of a modern Linux, but which
> can actually take advantage of the resources of a modern machine.  I don't
> care about a desktop, or even a graphical environment, I don't care about
> all the strange syscalls that are there to support particular databases, I
> don't care much about being a virtualization host.


But then...what would the purpose of such a system? A mini-Unix just to run
vi(1) or text based game? If you want to run retro games there are much
better retro platforms for that, e.g. I do not need a Unix machine if I
want to run MS-DOS era games. I prefer period correct hardware and software.

If you want a modern Unix for production systems, then most of the real
world modern workloads are run in Kubernetes which is a very Linux
orientated technology anyway.

It appears to me there is really no need for such a modern mini-Unix system
outside of hard core O/S theorists community.

There are already a myriad of similar projects like Alan Cox's Fuzix OS
which can run e.g. on Amiga, but it will not play Centurion or Another
World anytime soon anyway.

--Andy

[-- Attachment #2: Type: text/html, Size: 1510 bytes --]

  reply	other threads:[~2022-12-20 15:31 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-19 17:38 [TUHS] " Phil Budne
2022-12-19 18:53 ` [TUHS] " segaloco via TUHS
2022-12-19 21:01   ` Clem Cole
2022-12-19 21:19     ` Rob Pike
2022-12-19 22:15       ` segaloco via TUHS
2022-12-20  0:02         ` Brad Spencer
2022-12-20  1:04           ` Adam Thornton
2022-12-20  2:35             ` segaloco via TUHS
2022-12-20 14:25           ` Andrew Hume
2022-12-19 23:02       ` Clem Cole
2022-12-20  1:20         ` Larry Stewart
2022-12-20  1:33           ` Larry McVoy
2022-12-20  1:57             ` George Michaelson
2022-12-20  2:06               ` Dan Cross
2022-12-20 15:04                 ` Chet Ramey
2022-12-20  2:12               ` Adam Thornton
2022-12-20 15:29                 ` Andy Kosela [this message]
2022-12-20 15:35                   ` Adam Thornton
2022-12-21  2:43                     ` Luther Johnson
2022-12-20 23:18                 ` David Arnold
2022-12-20  2:52       ` Bakul Shah
2022-12-20  3:09         ` Larry McVoy
2022-12-20  3:27           ` Bakul Shah
2022-12-20  3:48           ` Warner Losh
2022-12-20  4:21           ` Jonathan Gray
2022-12-19 21:36 ` Marc Donner
2022-12-19 22:52   ` Charles H Sauer (he/him)
     [not found]   ` <01428a75-3507-7b8a-fd35-cef74c8c0bd2@ucsb.edu>
2022-12-20  1:49     ` [TUHS] Re: pre-1991 USENIX proceedings Marc Donner
2022-12-20  3:11 ` [TUHS] Re: UNIX on (not quite bare) System/370 Warner Losh
2022-12-20  8:56 ` arnold
2022-12-20  9:31   ` segaloco via TUHS
2022-12-20  9:39     ` arnold
2022-12-20  9:55       ` Jonathan Gray
2022-12-20 14:27     ` Clem Cole
2022-12-23  1:53       ` Rob Gingell
2022-12-22 19:00 ` Andrew Hume
2022-12-20 22:25 Noel Chiappa
2022-12-20 23:18 ` Bakul Shah
2022-12-22 17:26 Noel Chiappa
2022-12-22 17:33 ` Dan Cross
2022-12-22 20:25 ` Warner Losh
2022-12-22 23:06   ` Warner Losh

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=CALMnNGg35YBJWj1dk2GhrUR-B4+Hv6WAj32qDS7X7aNM74c7yQ@mail.gmail.com \
    --to=akosela@andykosela.com \
    --cc=athornton@gmail.com \
    --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).