From: corey@lod.com (Corey Lindsly)
Subject: [TUHS] hello, world
Date: Tue, 27 Dec 2011 16:53:44 -0800 (PST) [thread overview]
Message-ID: <20111228005345.1A4F540A1@lod.com> (raw)
In-Reply-To: <20111226211145.GA1335@minnie.tuhs.org>
> On Sun, Dec 25, 2011 at 08:10:04AM -0500, Norman Wilson wrote:
> > Rather a nice tribute to Dennis and C, published
> > in the New York Times Magazine:
> >
> > http://www.nytimes.com/interactive/2011/12/22/magazine/the-lives-they-lived.html?ref=magazine#view=dennis_ritchie
>
> Yes, a good reminder on the power that programming brings us. A question
> though: what command would "bring the system down"?
The one that has stuck with me since the first time I read it 30 years ago
is from an article titled "On the Security of UNIX" (dmr, 1978?) ...
Here is a particularly ghastly shell sequence guaranteed
to stop the system:
while :; do
mkdir x
cd x
done
Either a panic will occur because all the i-nodes on the
device are used up, or all the disk blocks will be consumed,
thus preventing anyone from writing files on the device.
(from the UNIX programmer's manual, vol.2 p.592)
---corey
next prev parent reply other threads:[~2011-12-28 0:53 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
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 [this message]
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=20111228005345.1A4F540A1@lod.com \
--to=corey@lod.com \
/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).