From: Dave Horsfall <dave@horsfall.org>
To: The Unix Heritage Society mailing list <tuhs@tuhs.org>
Subject: Re: [TUHS] reboot(2) system call
Date: Tue, 2 Feb 2021 14:35:30 +1100 (EST) [thread overview]
Message-ID: <alpine.BSF.2.21.9999.2102021427590.70858@aneurin.horsfall.org> (raw)
In-Reply-To: <m1l6lJK-0036x9C@more.local>
On Mon, 1 Feb 2021, Greg A. Woods wrote:
> If waiting was the true reason, then any sane person would have put a
> sleep in there instead so as to avoid any variance in typing (and
> terminal) speed.
I dunno; that's merely what I was taught in the early Unix days and it got
ingrained into me.
Nowadays I just issue "shutdown -[r|h] now" (I'm the only user)...
More Unix lore: sleep(1) could return straight away at one time (the
granularity was 1 second).
-- Dave, who remembers when sleep(3) used to be sleep(2)
prev parent reply other threads:[~2021-02-02 3: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
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 [this message]
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=alpine.BSF.2.21.9999.2102021427590.70858@aneurin.horsfall.org \
--to=dave@horsfall.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).