The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
Subject: [TUHS] single user mode in v5 & v6
Date: Fri,  9 Jan 2015 01:18:48 -0500 (EST)	[thread overview]
Message-ID: <20150109061848.94B1918C0CC@mercury.lcs.mit.edu> (raw)

    > From: Mark Longridge <cubexyz at gmail.com>

    > I've finally managed to get Unix v5 and v6 to go into single user mode
    > while running under simh.
    > ...
    > dep system sr 173030 (simh command)

Just out of curiousity, why don't you set the SR before you boot the machine?
That way it'll come up single user, and you can icheck/dcheck before you go
to multi-user mode. I prefer doing it that way, there's as little as possible
going on, in case the disk is slightly 'confused', so less chance any bit-rot
will spread...

    > Now I'm in muti user mode .. but then if I do a "ps -alx" I get:
    >
    > TTY F S UID   PID PRI ADDR  SZ  WCHAN COMMAND
    > ?:  3 S   0     0-100 1227   2   5676 ????
    > ?:  1 W   0     1  40 1324   6   5740 -

    > The ps command doesn't show the /etc/init process explicitly, although
    > I'm pretty sure it is running.

No, it's there: the second line (PID 1). For some reason, the code for
/etc/init (in V6 at least, I don't know anything about V5) bashes the command
line so it just has '-' in it, so it looks just like a shell.

I fixed my copy so it says "/etc/init", or something like that. The machine
my source is on is powered down at the moment; if you want, I can upload the
'fixed' code tomorrow.

    > I'm not sure if unix of the v6 or v5 era was designed to go from multi
    > user to single user mode and then back again.

I seem to recall there's some issue, something like in some cases there's an
extra shell left running attached to the console, but I don't recall the
details (too lazy to look for the note I made about the bug; I can look it up
if you really want to know).

    > Would it be safer to just go to single user and then shut it down?

I don't usually bother; I just log out all the shells except the one on the
console, so the machine is basically idle; then do a 'sync', and shortly
after than completes, I just halt the machine.

	Noel



             reply	other threads:[~2015-01-09  6:18 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-09  6:18 Noel Chiappa [this message]
2015-01-09 14:23 ` Ronald Natalie
2015-01-09 14:36   ` Clem Cole
2015-01-09 14:36 ` Clem Cole
2015-01-09 14:44   ` Ronald Natalie
2015-01-09 16:52     ` Clem cole
  -- strict thread matches above, loose matches on Subject: below --
2015-01-09 18:38 Noel Chiappa
2015-01-09 20:54 ` Clem Cole
2015-01-09 20:57   ` Ronald Natalie
2015-01-09 21:18     ` Clem Cole
2015-01-09 18:06 Noel Chiappa
2015-01-09 18:59 ` Dave Horsfall
2015-01-09  4:59 Mark Longridge

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=20150109061848.94B1918C0CC@mercury.lcs.mit.edu \
    --to=jnc@mercury.lcs.mit.edu \
    /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).