From: Michael Usher via TUHS <tuhs@minnie.tuhs.org>
To: Rob Pike <robpike@gmail.com>
Cc: TUHS main list <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] Remember the ed thread?
Date: Mon, 29 Mar 2021 13:50:55 -0700 [thread overview]
Message-ID: <4B1F03CA-6387-4FE1-8116-0CB7B5175DE7@ucsc.edu> (raw)
In-Reply-To: <CAKzdPgz1HqEoDcL_8QuYxVrhHqkR8c1Ajiq9T9g4B9gV2uBJNg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1671 bytes --]
I think you can only truly appreciate ed when you were forced to use a DECwriter as your terminal because all the VT100s were in use. (Undergrad student lab)
—
Michael Usher
Network Operations Manager
University of California, Santa Cruz
musher@ucsc.edu 831-459-3697
> On Mar 29, 2021, at 12:50 PM, Rob Pike <robpike@gmail.com> wrote:
>
> Ed is the standard editor.
>
> -rob
>
>
> On Tue, Mar 30, 2021 at 1:36 AM Larry McVoy <lm@mcvoy.com <mailto:lm@mcvoy.com>> wrote:
> I had *.clients.your-server.de <http://clients.your-server.de/> crawling mcvoy.com <http://mcvoy.com/> in violation of my
> robots.txt. For whatever reason, the tty settings (or something)
> made vi not work, I dunno what the deal is, stty -tabs didn't help.
>
> So I had to resort to ed to write and debug the little program below.
> It was surprisingly pleasant, it's probably the first time I've used ed
> for anything real in at least a decade. My fingers still know it.
>
> +1 for ed. It's how many decades old and still useful?
>
>
> #!/usr/libexec/bitkeeper/bk tclsh
>
> int
> main(void)
> {
> FILE log = popen("/var/log/apache2/dns.l", "r");
> string buf, ip;
> string dropped{string};
>
> fconfigure(log, buffering: "line");
> while (buf = <log>) {
> unless (buf =~ /([^ ]+\.your-server\.de\.) /) continue;
> ip = $1;
> if (defined(dropped{ip})) continue;
> dropped{ip} = "yes";
> warn("DROP ${ip}\n");
> system("/sbin/iptables -I INPUT -s ${ip} -j DROP");
> }
> }
[-- Attachment #2: Type: text/html, Size: 5024 bytes --]
next prev parent reply other threads:[~2021-03-29 20:51 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-29 14:34 Larry McVoy
2021-03-29 15:09 ` Anders Damsgaard
2021-03-29 15:26 ` Brantley Coile
2021-03-29 15:36 ` Mark van Atten
2021-03-29 15:43 ` Brantley Coile
2021-03-29 15:52 ` Mark van Atten
2021-03-29 15:45 ` Andy Kosela
2021-03-29 15:51 ` Clem Cole
2021-03-29 17:22 ` arnold
[not found] ` <CALMnNGgWrFRjXk5N4PgTj0_Yw3W5nCR2=CYSASM6dnqTooy8Dw@mail.gmail.com>
2021-03-30 8:53 ` arnold
2021-03-29 15:37 ` Clem Cole
2021-03-29 15:42 ` Anders Damsgaard
2021-03-29 15:49 ` Larry McVoy
2021-03-29 16:01 ` Andy Kosela
2021-03-29 18:12 ` Tom Ivar Helbekkmo via TUHS
2021-03-29 16:20 ` Steve Nickolas
2021-03-29 19:50 ` Rob Pike
2021-03-29 20:50 ` Michael Usher via TUHS [this message]
2021-03-29 20:55 ` Larry McVoy
2021-03-29 21:10 ` Erik E. Fair
2021-03-29 21:14 ` Larry McVoy
2021-03-29 21:53 ` Clem Cole
2021-03-29 22:29 ` John P. Linderman
2021-03-30 4:30 ` Rob Pike
2021-03-30 7:37 ` Harald Arnesen
2021-03-30 15:00 ` Kenneth Goodwin
2021-03-29 15:58 Norman Wilson
2021-03-30 0:11 ` John Cowan
2021-03-29 23:21 M Douglas McIlroy
2021-03-30 3:39 ` Rich Morin
[not found] <CAKH6PiXmR6Jv0bkyOtHuk1ZLV64aeW7bnQkUnzV9-G_JaUVDAA@mail.gmail.com>
2021-03-30 23:38 ` John Cowan
2021-03-31 2:34 ` Bakul Shah
2021-03-31 0:54 Norman Wilson
2021-03-31 1:29 ` John Cowan
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=4B1F03CA-6387-4FE1-8116-0CB7B5175DE7@ucsc.edu \
--to=tuhs@minnie.tuhs.org \
--cc=musher@ucsc.edu \
--cc=robpike@gmail.com \
/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).