From: bqt@update.uu.se (Johnny Billquist)
Subject: [TUHS] PDP-10 UNIX?
Date: Mon, 18 Sep 2017 04:34:56 +0200 [thread overview]
Message-ID: <9e3b00fa-3688-73d1-b79c-b88c3bd99bdb@update.uu.se> (raw)
In-Reply-To: <mailman.1031.1505666037.3779.tuhs@minnie.tuhs.org>
On 2017-09-17 18:33, Arthur Krewat <krewat at kilonet.net> wrote:
> Was there ever a UNIX or even the thought of porting one to a PDP-10?
Definitely a thought. An attempt was started on NetBSD for the PDP-10,
and it sortof got halfway of getting into single-user, but I'm not sure
if the person who worked on it just got distracted, or if he hit
problems that were really hard to solve. I certainly know the person,
and can find out more if people really are interested.
> 36-bit machine, 18-bit addresses (more on KL10 and KS10), and:
>
> *0 would return register 0 instead of a SIGSEGV ;)
Yes. Not the first machine that would be true for. You don't have
address 0 unmapped on a PDP-11 either.
> 8-bit bytes would have been a wasteful exercise, but you never know.
> (losing 4 bits of every 36-bit word)
Uh... Why 8 bit bytes? That way lies madness. There exists a really good
C compiler for TOPS-20 - KCC. It uses 9 bits per byte. Works like a
charm, except when some people write portable code that is not so
portable. ;-)
KCC was written by KLH, unless I remember wrong. Same guy who also wrote
the KLH-10 emulator.
Johnny
--
Johnny Billquist || "I'm on a bus
|| on a psychedelic trip
email: bqt at softjar.se || Reading murder books
pdp is alive! || tryin' to stay hip" - B. Idol
next parent reply other threads:[~2017-09-18 2:34 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.1031.1505666037.3779.tuhs@minnie.tuhs.org>
2017-09-18 2:34 ` Johnny Billquist [this message]
2017-09-18 15:30 ` Arthur Krewat
2017-09-18 16:46 ` Steve Johnson
2017-09-18 17:25 ` Clem Cole
2017-09-18 17:40 ` Larry McVoy
2017-09-18 20:08 ` Chris Torek
2017-09-20 18:40 Nelson H. F. Beebe
2017-09-24 18:29 ` arnold
-- strict thread matches above, loose matches on Subject: below --
2017-09-18 21:14 Noel Chiappa
2017-09-19 6:46 ` Lars Brinkhoff
2017-09-18 17:24 Nelson H. F. Beebe
2017-09-18 18:10 ` Lars Brinkhoff
2017-09-20 4:55 ` Warner Losh
2017-09-17 14:28 Arthur Krewat
2017-09-17 14:31 ` Warner Losh
2017-09-17 15:01 ` Lars Brinkhoff
2017-09-17 15:22 ` Arthur Krewat
2017-09-18 13:50 ` Clem Cole
2017-09-18 16:42 ` Arthur Krewat
2017-09-18 19:58 ` Lars Brinkhoff
2017-09-18 20:10 ` Clem Cole
2017-09-18 20:22 ` Lars Brinkhoff
2017-09-18 20:43 ` Clem cole
2017-09-19 9:06 ` Mutiny
2017-09-19 9:56 ` Lars Brinkhoff
2017-09-17 16:33 ` 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=9e3b00fa-3688-73d1-b79c-b88c3bd99bdb@update.uu.se \
--to=bqt@update.uu.se \
/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).