The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: ggm@algebras.org (George Michaelson)
Subject: And now ... Weirdnix?
Date: Wed, 4 Oct 2017 09:15:35 -0700	[thread overview]
Message-ID: <CAKr6gn0ry6uZEgKXzxuwJFGx9azqro2AV1LiTO+V45mp4EC=OA@mail.gmail.com> (raw)
In-Reply-To: <m260bvjvy0.fsf@thuvia.hamartun.priv.no>

I think the dual-boot state of the perq was pretty wierd. From memory,
you could peek into some UNIX state from the other OS, but not the
other way.

The weird bit was the 'hacky' nature of the OS/memory/screen boundary.
Compile? ok, you clearly don't need your screen memory because who
would think they could do useful mouse/keyboard work while compiling?
So.. I'll just rob that memory buffer to do this compilation... Very
interesting bitblt implications all over the screen. I suspect this
was considered a 'feature' because you got a free meter of your
compilation progress by crud on the screen..

On Tue, Oct 3, 2017 at 10:58 PM, Tom Ivar Helbekkmo
<tih at hamartun.priv.no> wrote:
> Warren Toomey <wkt at tuhs.org> writes:
>
>> To kick a more relevant thread off, what was the "weirdest" Unix
>> system you used & why? Could be an emulation like Eunice, could be the
>> hardware e.g NULL was not zero, NUXI byte ordering etc.
>
> That would be the userland Unix from the Norwegian company Norsk Data.
> For years, they made excellent mini machines with their own operating
> system, SINTRAN.  People kept telling them that that time was passing,
> and they needed to get with the times and adopt a standardized OS, like
> Unix, but they insisted that there was no need.
>
> When they finally started trying to do that, it was too late.
>
> They made two attempts.  One was a System V port to their hardware, the
> other a port to SINTRAN, having Unix run as an application under it.
> Neither attempt got any real traction, and today, the company is only a
> fond memory.
>
> Oh, and when Tim Berners-Lee invented the World Wide Web, he did it
> on a Norsk Data computer running SINTRAN.  :)
>
> -tih
> --
> Most people who graduate with CS degrees don't understand the significance
> of Lisp.  Lisp is the most important idea in computer science.  --Alan Kay


      reply	other threads:[~2017-10-04 16:15 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-17  7:03 [TUHS] " Warren Toomey
2017-09-17  7:28 ` arnold
2017-09-17  8:10   ` David Arnold
2017-09-17 12:52     ` Adam Sampson
2017-09-17 14:23     ` Steve Simon
2017-09-17 18:50   ` Chet Ramey
2017-09-17 19:01     ` Derrik Walker v2.0
2017-09-18 12:02     ` arnold
2017-09-17 14:49 ` Dennis Boone
2017-09-18  7:27   ` Nigel Williams
2017-09-18  8:31     ` arnold
2017-09-18 10:39       ` Andreas Kusalananda Kähäri
2017-09-18 11:59         ` Michael Kjörling
2017-09-19  1:54       ` Dave Horsfall
2017-09-19  7:07         ` Ian Zimmerman
2017-09-19 14:09         ` [TUHS] PR1ME - was " Toby Thain
2017-09-17 15:08 ` [TUHS] " Nemo
2017-09-18 23:57 ` Dave Horsfall
2017-10-04  5:58 ` Tom Ivar Helbekkmo
2017-10-04 16:15   ` George Michaelson [this message]

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='CAKr6gn0ry6uZEgKXzxuwJFGx9azqro2AV1LiTO+V45mp4EC=OA@mail.gmail.com' \
    --to=ggm@algebras.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).