The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Win Treese <treese@acm.org>
To: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: Re: [TUHS] reboot(2) system call
Date: Tue, 28 Jul 2020 12:35:13 -0400	[thread overview]
Message-ID: <26006DA8-EF6D-42FC-8A11-E84447E6946A@acm.org> (raw)
In-Reply-To: <alpine.BSF.2.21.9999.2007281403170.76447@aneurin.horsfall.org>



> On Jul 28, 2020, at 12:06 AM, Dave Horsfall <dave@horsfall.org> wrote:
> 
> On Mon, 27 Jul 2020, Warner Losh wrote:
> 
>> I've done some research for a friend about when the reboot() system call was added, and how it related to the sync, sync, sync dance. https://bsdimp.blogspot.com/2020/07/when-unix-learned-to-reboot2.html
>> may be of interest. Please do let me know if I've gotten something wrong...
> 
> Seems OK to me; I was taught never to use "sync; sync; sync" for precisely those reasons (the buffers may not have time to flush etc, as "sync" merely schedules the I/O, not cause it.

This was summarized at MIT’s Project Athena in the mid-80s as:

When thou shuttest down the system, thou shalt sync three times. No more, no less. Three shall be the number of the syncing, and the number of the syncing shall be three. Four times shalt thou not sync, neither sync twice, except that thou proceedest to sync a third time. Five is right out.

- Win



  reply	other threads:[~2020-07-28 16:36 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-27 18:57 Warner Losh
2020-07-28  0:36 ` Clem Cole
2020-07-28  4:06 ` Dave Horsfall
2020-07-28 16:35   ` Win Treese [this message]
2020-07-28 13:11 ` Jaap Akkerhuis
2021-01-27  6:01 ` Greg A. Woods
2021-01-30 22:27   ` Dave Horsfall
2021-01-30 22:31     ` Larry McVoy
2021-01-30 22:37       ` Warner Losh
2021-02-02  2:20     ` Greg A. Woods
2021-02-02  2:30       ` Warner Losh
2021-02-02 20:30         ` Greg A. Woods
2021-02-02  3:35       ` Dave Horsfall

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=26006DA8-EF6D-42FC-8A11-E84447E6946A@acm.org \
    --to=treese@acm.org \
    --cc=tuhs@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).