From: wkt@tuhs.org (Warren Toomey)
Subject: [TUHS] hello, world
Date: Wed, 28 Dec 2011 17:34:06 +1000 [thread overview]
Message-ID: <20111228073405.GA26729@minnie.tuhs.org> (raw)
In-Reply-To: <20111228001354.GE1474@lisa.in-ulm.de>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1518 bytes --]
On Mon, 12/26/11, Warren Toomey <wkt at tuhs.org> wrote:
> > A question though: what command would "bring the system down"?
On Wed, Dec 28, 2011 at 01:13:54AM +0100, Sven Mascheck wrote:
> I wonder if Warren rather had different issues in mind,
I just took umbrage at the article, in that it implied Unix provided
machanisms for the ordinary user to "bring the system down". This is,
of course, not true, at least once the hardware supported
inter-process and kernel protection.
However, it does remind me of Dennis' story about the days before proper
memory protection (from http://cm.bell-labs.com/cm/cs/who/dmr/odd.html):
Back around 1970-71, Unix on the PDP-11/20 ran on hardware that
not only did not support virtual memory, but didn't support
any kind of hardware memory mapping or protection, for example
against writing over the kernel. This was a pain, because we were
using the machine for multiple users. When anyone was working on
a program, it was considered a courtesy to yell "A.OUT?" before
trying it, to warn others to save whatever they were editing.
At some point several were sitting around working away. Bob
Morris asked, almost conversationally, "what are the arguments to
ld?" Someone told him. We continued typing for the next minute,
as a thought began to percolate, not quite to the top of the
brain -- in other words, not quite fast enough. The terminal
stopped echoing before anyone could stop and say "Hold on Bob,
what is it you're trying to do?"
Cheers,
Warren
next prev parent reply other threads:[~2011-12-28 7:34 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-25 13:10 Norman Wilson
2011-12-26 21:11 ` Warren Toomey
2011-12-26 21:15 ` Wilko Bulte
2011-12-26 21:20 ` Lyndon Nerenberg
2011-12-26 21:53 ` Armando Stettner
2011-12-26 22:13 ` Michael Davidson
2011-12-26 21:28 ` A. P. Garcia
2011-12-27 1:08 ` A. P. Garcia
2011-12-26 21:28 ` Michael Davidson
2011-12-28 0:13 ` Sven Mascheck
2011-12-28 0:20 ` Wilko Bulte
2011-12-28 7:34 ` Warren Toomey [this message]
2011-12-28 10:16 ` Ori Idan
2011-12-27 6:11 ` Adam
2012-01-04 3:37 ` Cyrille Lefevre
[not found] ` <Pine.BSI.4.64.1112271711290.603@dave.horsfall.org>
2011-12-27 18:01 ` Tim Newsham
2011-12-28 0:53 ` Corey Lindsly
2011-12-28 10:54 ` asbesto
2011-12-28 18:32 ` John Cowan
[not found] <mailman.1.1325037601.24307.tuhs@minnie.tuhs.org>
2011-12-28 20:56 ` David Barto
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=20111228073405.GA26729@minnie.tuhs.org \
--to=wkt@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).