The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Will Senn <will.senn@gmail.com>
To: TUHS main list <tuhs@minnie.tuhs.org>
Subject: [TUHS] CSR in V6
Date: Sat, 26 Feb 2022 18:29:48 -0600	[thread overview]
Message-ID: <3911910b-c205-25ce-a758-1f67a624028e@gmail.com> (raw)

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

I noticed in v6 source that putch in prf.c - the system kernel printf's 
character routine, only prints to the console if the Console Switch 
Register is non-zero.

My question is  - how did y'all run things - with CSR zero and no kernel 
messages (seems dangerous to me, being naive and all) or with CSR 
non-zero and kernel messages.

On my FreeBSD instance, I value the messages that show up on console as 
they've alerted me to big problems in the past, but on my Mac, not as 
much (sure you can run Console and see them, but they aren't immediate).

Oh, BTW, I know I've seen this noted elsewhere, but I can't remember 
where. Dennis's v6 doesn't have the Western Electric message:

    mem = 435
    RESTRICTED RIGHTS

    Use, duplication or disclosure is subject to
    restrictions stated in Contract with Western
    Electric Company, Inc.

It was a bit of a head scratcher as I was trying to read from the Dennis 
version of the distro on my mac while running Wellsch's tape on simh. I 
spent quite a while spinning my wheels looking for "Western" in the 
files to no avail. I thought something was screwy with the files or my mac.

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

             reply	other threads:[~2022-02-27  0:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-27  0:29 Will Senn [this message]
2022-02-27  7:38 Noel Chiappa

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=3911910b-c205-25ce-a758-1f67a624028e@gmail.com \
    --to=will.senn@gmail.com \
    --cc=tuhs@minnie.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).