From: Dave Horsfall <dave@horsfall.org>
To: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: Re: [TUHS] cat -v and other complaints
Date: Thu, 30 Aug 2018 08:34:05 +1000 (EST) [thread overview]
Message-ID: <alpine.BSF.2.21.9999.1808300825340.41601@aneurin.horsfall.org> (raw)
In-Reply-To: <CAC20D2ODDO+OTUf8wA4bXu9M5M0kswJqT97qRAnV9EOzMGKRvQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1059 bytes --]
On Wed, 29 Aug 2018, Clem Cole wrote:
[ Excellent screed elided ]
> That said, I give the Linux folks great credit for the addition of
> modules was huge and it took BSD and the other UNIX systems a few years
> really pick up that idea in the same way (yes Solaris, Tru64 and
> eventually HPUX etc.. had something too but again - my comment about
> being generally available applies).
Wasn't SunOS first with dynamic kernel modules, or is my memory worse than
I thought? Linux may have been around at the time, but we never used in
the shop until much later (Red Hat, nicknamed Dead Rat).
> So here is the issue, how to do move the ball forward? BSD, then
> Linux, became the 'stronger strain' and pushed out the old version.
> The problem is the ROMs in my fingers (like Dave) never got
> reprogrammed so some of the 'new' becomes annoying. Will I learned to
> like systemd? We shall see...
Never mind "systemd"; I'm having enough trouble coming to grips with
"launchd" on the Mac... Gimme /etc/inetd.conf any time.
-- Dave
next prev parent reply other threads:[~2018-08-29 22:34 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-29 14:25 Clem Cole
2018-08-29 22:34 ` Dave Horsfall [this message]
2018-08-29 23:36 ` Larry McVoy
2018-08-30 1:14 ` Clem cole
2018-08-30 1:15 ` Clem cole
2018-08-30 2:43 ` Kevin Bowling
2018-08-30 2:59 ` George Michaelson
2018-08-31 0:27 ` Dave Horsfall
2018-08-31 0:41 ` Dan Cross
2018-08-31 1:58 ` Larry McVoy
2018-08-31 11:38 ` ron
2018-08-31 14:41 ` [TUHS] UNIX System names - since UNIX was a Trademark Clem Cole
2018-08-31 15:13 ` Eric Wayte
2018-08-31 15:17 ` William Pechter
2018-08-31 15:25 ` Clem Cole
2018-09-01 0:10 ` John P. Linderman
2018-09-01 0:18 ` ron
2018-09-01 0:55 ` Nemo
2018-09-01 7:37 ` Dave Horsfall
2018-09-01 13:54 ` Nemo
2018-09-01 17:03 ` Paul Winalski
2018-09-03 1:14 ` Robert Brockway
2018-09-30 20:57 ` Lyndon Nerenberg
2018-10-01 16:26 ` Paul Winalski
2018-09-01 0:00 ` Dave Horsfall
2018-08-31 21:56 ` [TUHS] cat -v and other complaints Cág
2018-09-01 3:37 ` Andrew Warkentin
2018-09-03 18:04 ` Cág
2018-09-03 18:11 ` Kurt H Maier
2018-09-03 18:56 ` Cág
2018-09-04 6:10 ` Andy Kosela
2018-09-04 6:41 ` ron minnich
2018-09-04 9:34 ` Andy Kosela
2018-09-04 10:23 ` Dan Cross
2018-09-04 14:22 ` ron minnich
2018-09-06 20:02 ` Andy Kosela
2018-09-06 20:49 ` ron minnich
2018-09-06 21:55 ` Andy Kosela
2018-09-07 1:59 ` Dan Cross
2018-09-07 4:40 ` Andy Kosela
2018-09-30 21:32 ` Lyndon Nerenberg
2018-09-03 20:08 ` Bakul Shah
2018-09-03 20:41 ` Kurt H Maier
2018-09-03 21:46 ` Bakul Shah
2018-09-04 0:52 ` Kurt H Maier
2018-09-06 20:29 Norman Wilson
2018-09-06 22:16 ` Andy Kosela
2018-09-08 12:02 [TUHS] [TUHS} " Doug McIlroy
2018-09-08 13:36 ` Will Senn
2018-09-08 14:22 ` [TUHS] " Ralph Corderoy
2018-09-08 16:10 ` Arthur Krewat
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.1808300825340.41601@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).