From: norman@oclsc.org (Norman Wilson)
Subject: [TUHS] shutdown for pre-v7 unix
Date: Wed, 16 Jul 2014 22:40:06 -0400 [thread overview]
Message-ID: <1405564809.9840.for-standards-violators@oclsc.org> (raw)
After a day and an evening of fighting with modern hardware,
the modern tangle that passes for UNIX nowadays, and modern
e-merchandising, I am too lazy to go look up the details.
But as I remember it, two syncs was indeed probably enough.
I believe that when sync(2) returned, all unflushed I/O had
been queued to the device driver, but not necessarily finished,
so the second sync was just a time-filling no-op. If all the
disks were in view, it probably sufficed just to watch them
until all the lights (little incandescent bulbs in those days,
not LEDs) had stopped blinking.
I usually typed sync three or four times myself. It gave me
a comfortable feeling (the opposite of a syncing feeling, I
suppose). I still occasionally type `sync' to the shell as
a sort of comfort word while thinking about what I'm going
to do next. Old habits die hard.
(sync; sync; sync)
Norman Wilson
Toronto ON
next reply other threads:[~2014-07-17 2:40 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-17 2:40 Norman Wilson [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-07-17 3:55 Noel Chiappa
2014-07-16 19:47 Noel Chiappa
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=1405564809.9840.for-standards-violators@oclsc.org \
--to=norman@oclsc.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).