From: Larry McVoy <firstname.lastname@example.org>
To: Adam Thornton <email@example.com>
Cc: Computer Old Farts Followers <firstname.lastname@example.org>
Subject: [COFF] Re: Useful Shell Scripts Network Connections , Logins and Block hacking attempts
Date: Thu, 11 May 2023 19:34:28 -0700 [thread overview]
Message-ID: <20230512023428.GK29399@mcvoy.com> (raw)
On Thu, May 11, 2023 at 07:19:50PM -0700, Adam Thornton wrote:
> > On May 11, 2023, at 7:13 PM, Greg 'groggy' Lehey <email@example.com> wrote:
> > Agreed. My guess is that the poster is really called Ken. You can't
> > blame him for that.
> You can fault his judgment for calling himself "Unix Ken" or whatever, because for most people around here, that would indicate a specific person who isn't him, but nothing he's posted seems to indicate malice or an intention to confuse people.
> I bet there are more than two people named Ken who are into Unix in the world.
Adding my voice to Unix Ken is just another Ken. Nothing I've seen from
him says he is trying to be Ken T.
And since I'm opining, I both liked and didn't like his scripts. I liked
that they were very classic Unix, a pleasant reminder of where we have
come from. What I didn't like was all that data flowing through all
those pipes. Yes, it is simple but it just doesn't scale that well
when you are processing gigabytes of data, which you frequently are
I'll date myself, but I could replace every one of those scripts
with a single pretty understandable perl script. Modern people might
prefer Python, I can program in Python but I have a huge aversion to a
programming language that doesn't include printf in the base language.
Too weird for me.
Larry McVoy Retired to fishing http://www.mcvoy.com/lm/boat
next prev parent reply other threads:[~2023-05-12 2:34 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAJXSPs92h7yVVJm9UPp06zPQwRy-XkGPDhL-=uVT5sw=hEcLkQ@mail.gmail.com>
2023-05-10 23:56 ` [COFF] Fwd: " KenUnix
2023-05-11 0:12 ` [COFF] " Niklas Karlsson
2023-05-11 5:58 ` steve jenkin
2023-05-11 9:18 ` [COFF] " Ralph Corderoy
2023-05-11 22:06 ` Dave Horsfall
2023-05-11 22:35 ` segaloco via COFF
2023-05-12 2:13 ` Greg 'groggy' Lehey
2023-05-12 2:19 ` Adam Thornton
2023-05-12 2:34 ` Larry McVoy [this message]
2023-05-12 4:30 ` Tomasz Rola
2023-05-12 8:34 ` Ralph Corderoy
2023-05-12 13:58 ` Larry McVoy
2023-05-12 4:24 ` Tomasz Rola
2023-05-12 5:02 ` segaloco via COFF
2023-05-12 8:14 ` Robert Stanford via COFF
2023-05-12 16:40 ` Adam Thornton
2023-05-12 11:42 ` Ralph Corderoy
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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).