The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Warner Losh <imp@bsdimp.com>
To: segaloco <segaloco@protonmail.com>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: [TUHS] Re: Any Bell 8-bit UNIX Efforts?
Date: Sun, 26 Feb 2023 20:55:24 -0700	[thread overview]
Message-ID: <CANCZdfoDe1dXZmn3Yb3FnUmnZKOGMRr5i-F_hUg30-AMnF_0dA@mail.gmail.com> (raw)
In-Reply-To: <SE2KEj9K7op4yx44W-GiLDGgvSYDSxKHJibUImHLsxywlUZ9UfG8pMOl5nzUs1SViPSN8gkOGAlq4YudSv6VhbQFrpDwsjTtLkyrZ6rXnxE=@protonmail.com>

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

On Sat, Feb 25, 2023 at 12:49 PM segaloco via TUHS <tuhs@tuhs.org> wrote:

> So in working on an unrelated 6502 project, I got to wondering about UNIX
> on it and other 8-bits. Did some Googling, and while I was able to turn up
> some attempts at UNIX-likes on 6502 as well as Z80, the only one I found
> that might have some Bell connection is "uNIX" as documented here:
> https://bitsavers.org/pdf/uNIX/uNIX_Jan82.pdf
>
> A forum post I read suggested those involved were some former Bell folks
> from NJ. In any case, this begs the question for me: Were there ever any
> serious attempts at an 8-bit UNIX in the labs or Bell System at large?
> Certainly it would've provided quite the challenge without much return
> compared with 16 and 32-bit efforts, but does anyone know if, say, an
> LSX/Mini-UNIX-ish attempt was ever made at the 6502, Z80, or other 8-bits?
> Thanks all!
>

FUZIX is one that I'm aware of, but it's a rewrite, not a port:
https://hackaday.com/2017/04/16/z80-fuzix-is-like-old-fashioned-unix/

Warner

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

  reply	other threads:[~2023-02-27  3:55 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-25 19:48 [TUHS] " segaloco via TUHS
2023-02-27  3:55 ` Warner Losh [this message]
2023-02-27 10:57 ` [TUHS] " Jonathan Gray
2023-02-28 18:59   ` segaloco via TUHS
2023-02-28 19:03     ` Larry McVoy
2023-02-28 19:42     ` Clem Cole
2023-02-28 19:57       ` Bakul Shah
2023-02-28 23:31       ` Dave Horsfall
2023-03-01  0:39         ` Larry McVoy
2023-03-01  1:21         ` Rich Salz
2023-03-01  1:27           ` Warner Losh
2023-03-01  2:07           ` Ronald Natalie
2023-03-01  2:35             ` Dan Cross
2023-03-01  2:38               ` Ronald Natalie
2023-03-01  3:02               ` [TUHS] IBM RT/PC compilers [was " Charles H. Sauer
2023-03-01  4:02                 ` [TUHS] " George Michaelson
2023-03-01 14:12               ` [TUHS] " Chet Ramey
2023-03-02  9:05                 ` Jaap Akkerhuis via TUHS
2023-03-02 19:26                   ` Clem Cole
2023-03-01  2:50             ` Jonathan Gray
2023-03-01  0:31       ` Jonathan Gray

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=CANCZdfoDe1dXZmn3Yb3FnUmnZKOGMRr5i-F_hUg30-AMnF_0dA@mail.gmail.com \
    --to=imp@bsdimp.com \
    --cc=segaloco@protonmail.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).