From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
Subject: [TUHS] shutdown for pre-v7 unix
Date: Wed, 16 Jul 2014 15:47:51 -0400 (EDT) [thread overview]
Message-ID: <20140716194751.2291F18C0A3@mercury.lcs.mit.edu> (raw)
> From: Mark Longridge <cubexyz at gmail.com>
> I was wondering if there might be a better way to do a shutdown on
> early unix.
Not really; I don't seem to recall our having one on the MIT V6 machine.
(We did add a 'reboot' system call so we could reboot the machine without
having to take the elevator up to the machine room [the console was on our
floor, and the reboot() call just jumped into the hardware bootstrap], but in
the source it doesn't even bother to do an update(). Well, I should't say
that: I only have the source for the kernel, which doesn't; I don't at the
moment have access to the source for the rest of the system - although I do
have some full dump tapes, once I can work out how to read them. Anyway, so
maybe the user command for rebooting the system did a sync() first.)
I suppose you could set the switch register to 173030 and send a 'kill -1 1',
which IIRC kills of all shells except the one on the console, but somehow
I doubt you're running multi-user anyway... :-)
Noel
next reply other threads:[~2014-07-16 19:47 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-16 19:47 Noel Chiappa [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-07-17 3:55 Noel Chiappa
2014-07-17 2:40 Norman Wilson
2014-07-16 18:55 Mark Longridge
2014-07-16 20:52 ` Brantley Coile
2014-07-17 2:29 ` Win Treese
2014-07-16 21:12 ` Dave Horsfall
2014-07-16 21:23 ` Dave Horsfall
2014-07-17 2:09 ` Dan Stromberg
2014-07-17 15:58 ` Warner Losh
2014-07-17 16:15 ` Clem Cole
2014-07-17 18:04 ` Ronald Natalie
2014-07-17 20:16 ` Clem Cole
2014-07-18 2:26 ` Ronald Natalie
2014-07-18 2:52 ` Tim Newsham
2014-07-18 2:58 ` Milo Velimirovic
2014-07-18 3:42 ` 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=20140716194751.2291F18C0A3@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).