From mboxrd@z Thu Jan  1 00:00:00 1970
From: wkt@tuhs.org (Warren Toomey)
Date: Wed, 28 Dec 2011 17:34:06 +1000
Subject: [TUHS] hello, world
In-Reply-To: <20111228001354.GE1474@lisa.in-ulm.de>
References: <20111226211145.GA1335@minnie.tuhs.org>
	<1324934923.37156.YahooMailClassic@web82402.mail.mud.yahoo.com>
	<20111228001354.GE1474@lisa.in-ulm.de>
Message-ID: <20111228073405.GA26729@minnie.tuhs.org>

 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