The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Dave Horsfall <dave@horsfall.org>
To: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: Re: [TUHS] Origin of the name 'strategy'
Date: Wed, 9 Jan 2019 16:42:32 +1100 (EST)	[thread overview]
Message-ID: <alpine.BSF.2.21.9999.1901091624410.65590@aneurin.horsfall.org> (raw)

On Tue, 8 Jan 2019, Warner Losh wrote:

> The name seems obvious because I've seen it for the last 30 years. But 
> I've not seen it used elsewhere, nor have I seen it documented except in 
> relationship to Unix. It could have been called blkio or bufio or bio or 
> even just work or morework and still been as meaningful. VMS uses the 
> FDT table to process the IRPs sent down. RT-11 has a series of entry 
> points that have boring names. Other systems have a start routine 
> (though more often that is a common routine used by both the queue me 
> and isr functions). There is a wide diversity here...

I must admit that this is an interesting thread, just as long as it wasn't 
called XXoptimize() unless you wanted a backlash from British English 
speakers :-)

In hindsight I suppose that XXstrategy() is obvious, but back then, as you 
ask?  Dunno, but Ken might (if he's reading this thread).

One of my favo[u]rites is sched(); some pronounce it as "shed" and others 
as "sked".  Another American/British thing, I think...

Wasn't it Mark Twain who said "Two nations divided by a common language"?

I no longer have my Lions books on me, sadly enough (lost in a house move) 
but there certainly were some peculiar names in the kernel...

ObGripe: Could anyone replying to the digest version please take the 
trouble to update the Subject: line accordingly?  I've now put the 
original back as a courtesy to others, but I shouldn't have to; it's as 
bad as top-posting.

-- Dave

             reply	other threads:[~2019-01-09  5:43 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-09  5:42 Dave Horsfall [this message]
2019-01-09 12:02 ` Dan Cross
2019-01-09 15:12 ` [TUHS] Lions book (not " Bakul Shah
2019-01-09 16:09   ` Warner Losh
2019-01-09 16:20     ` Clem Cole
2019-01-09 16:50       ` Warner Losh
2019-01-09 22:53         ` Dave Horsfall
2019-01-09 17:50       ` Bakul Shah
2019-01-09 17:55         ` Warner Losh
2019-01-09 17:20     ` Andy Kosela
2019-01-09 22:24   ` Dave Horsfall
2019-01-09 23:09   ` Cág
  -- strict thread matches above, loose matches on Subject: below --
2019-01-07 21:21 [TUHS] " Warner Losh
2019-01-07 21:27 ` Dave Horsfall
2019-01-07 21:28 ` Dan Cross
2019-01-07 22:28   ` Erik E. Fair
2019-01-09 20:51 ` Clem Cole
2019-01-09 23:30   ` 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=alpine.BSF.2.21.9999.1901091624410.65590@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).