From: Grant Taylor <gtaylor@tnetconsulting.net>
To: Linux Advanced Routing & Traffic Control <lartc@vger.kernel.org>
Subject: Re: Status of the LARTC project and of this list
Date: Tue, 31 Oct 2023 21:26:32 -0500 [thread overview]
Message-ID: <0bd248ff-b8df-541a-0fd0-c686a529385b@tnetconsulting.net> (raw)
In-Reply-To: <d94aab58-416c-48d9-8fd7-05ec041a9bf4@nospam.hostisimo.com>
On 10/31/23 7:16 PM, Mike Wright wrote:
> I'd like to second Lewis' comment. I've received help there that I
> couldn't have found elsewhere.
I'd like to third Lewis's comment as well as second Mike's comment.
> Every time I've poked around for things like traffic control, routing,
> and firewalls the most arcane information invariably points here.
Yep.
Just about everything I see beyond basic How To / README references
Linux Advanced Routing and Traffic Control mailing list.
I think closing the list will end up accelerating bit rot and be a
dis-service to many people in the community.
> That said, I don't know how many of the advanced routing members still
> haunt the list. Every now and then Grant Taylor shows up and he has a
> *wealth* of knowledge from the wayback to current.
I have been active on the LARTC mailing list for for years / decades.
For a long time the mailing list ended up having extremely high
(O(days)) latency between sending a message and it ending up passing
through the mailing list. I think that hurt the LARTC mailing list
quite a bit. But it's recovered somewhat since.
> WRT low traffic: rarely used doesn't mean unused.
I absolutely agree.
--
Grant. . . .
unix || die
prev parent reply other threads:[~2023-11-01 2:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-31 16:57 Status of the LARTC project and of this list Konstantin Ryabitsev
2023-10-31 20:53 ` Rich Brown
2023-10-31 22:46 ` Lewis Rosenthal
2023-11-01 0:16 ` Mike Wright
2023-11-01 2:26 ` Grant Taylor [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=0bd248ff-b8df-541a-0fd0-c686a529385b@tnetconsulting.net \
--to=gtaylor@tnetconsulting.net \
--cc=lartc@vger.kernel.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 read-only IMAP folder(s) and NNTP newsgroup(s).