4 May
2022
4 May
'22
8:08 a.m.
Hi all, I've just changed the DNS CNAME record of www.tuhs.org from
minnie.tuhs.org (45.79.103.53) to newmin.tuhs.org (50.116.15.146).
Minnie is running Ubuntu 18.04LTS and is getting a bit long in the
tooth. Newmin is running 22.04LTS. So far I've got the web service
up and running on newmin. Doing the e-mail migration will be fun :-)
Let me know if you spot anything wrong with the new web server. I've
also set up oldwww.tuhs.org which points at minnie, so you can still
get to things on the old server.
Cheers, Warren
4 May
4 May
7:27 p.m.
Thank you, Warren for making the tremendous resource available to us all.
Clem
ᐧ
On Tue, May 3, 2022 at 10:11 PM Warren Toomey via TUHS <tuhs(a)minnie.tuhs.org>
wrote:
Hi all, I've just changed the DNS CNAME record of
www.tuhs.org from
minnie.tuhs.org (45.79.103.53) to newmin.tuhs.org (50.116.15.146).
Minnie is running Ubuntu 18.04LTS and is getting a bit long in the
tooth. Newmin is running 22.04LTS. So far I've got the web service
up and running on newmin. Doing the e-mail migration will be fun :-)
Let me know if you spot anything wrong with the new web server. I've
also set up oldwww.tuhs.org which points at minnie, so you can still
get to things on the old server.
Cheers, Warren
5 May
5 May
1:37 a.m.
Amen. A migration is a lot of work. Thank you for all you do!
Mary Ann
On 5/4/22 06:27, Clem Cole wrote:
Thank you, Warren for making the tremendous resource
available to us all.
Clem
ᐧ
On Tue, May 3, 2022 at 10:11 PM Warren Toomey via TUHS
<tuhs(a)minnie.tuhs.org> wrote:
Hi all, I've just changed the DNS CNAME record of www.tuhs.org
<http://www.tuhs.org> from
minnie.tuhs.org <http://minnie.tuhs.org> (45.79.103.53) to
newmin.tuhs.org <http://newmin.tuhs.org> (50.116.15.146).
Minnie is running Ubuntu 18.04LTS and is getting a bit long in the
tooth. Newmin is running 22.04LTS. So far I've got the web service
up and running on newmin. Doing the e-mail migration will be fun :-)
Let me know if you spot anything wrong with the new web server. I've
also set up oldwww.tuhs.org <http://oldwww.tuhs.org> which points
at minnie, so you can still
get to things on the old server.
Cheers, Warren
11:43 a.m.
On 5/5/22, Dave Horsfall <dave(a)horsfall.org> wrote:
On Wed, 4 May 2022, Clem Cole wrote:
And thank you for keeping the website plain and simple with pure HTML
so it is readable even with text browsers. These modern trends in web
design are horrible. We are in a situation you need to buy a new
computer every few years just to read the web! Binary and encryption
protocols and standards, js crap that change in an increasing pace.
The public information should be accessible by all, even with an old
486dx.
--Andy
Thank you, Warren for making the tremendous
resource available to us
all.
And so say all of us!
11:57 a.m.
On 5/4/22 11:43 PM, Andy Kosela wrote:
Binary and encryption protocols and standards, js crap
that change
in an increasing pace. The public information should be accessible
by all, even with an old 486dx.
I believe there is a time and a place for some encryption. It's
probably more than you think, but definitely less than zealots want.
Yes, even the venerable 486 should be able to handle the level of
encryption that I'm referencing. -- At least it could do the math if
the software would run on it.
My main reasons for encryption are privacy and generating more noise for
others to hide their signal in that /need/ to do so.
Privacy also includes some security in that middle boxes can't inject
questionable (read: malicious) content.
--
Grant. . . .
unix || die
6 May
6 May
2:48 a.m.
On Thu, 5 May 2022, Andy Kosela wrote:
And thank you for keeping the website plain and simple
with pure HTML so
it is readable even with text browsers. These modern trends in web
design are horrible. We are in a situation you need to buy a new
computer every few years just to read the web! Binary and encryption
protocols and standards, js crap that change in an increasing pace. The
public information should be accessible by all, even with an old 486dx.
My pet peeve too; if the message cannot be spread without CPU-consuming
fancy graphics then the message is wrong (and I like to use Lynx).
-- Dave
4 May
4 May
11:54 p.m.
On 5/3/22 8:08 PM, Warren Toomey via TUHS wrote:
Doing the e-mail migration will be fun :-)
I'm curious what your thoughts / plans are on migrating email.
I /think/ that TUHS (and presumably COFF) is using Mailman 2.x which I
believe is dependent on Python 2.x. Are you going to be migrating to
Mailman 3.x / Python 3.x? Or are you going to go a different direction?
--
Grant. . . .
unix || die
6 May
6 May
3:26 a.m.
On Wed, May 04, 2022 at 11:54:25AM -0600, Grant Taylor via TUHS wrote:
I'm curious what your thoughts / plans are on
migrating email.
I /think/ that TUHS (and presumably COFF) is using Mailman 2.x which I
believe is dependent on Python 2.x. Are you going to be migrating to
Mailman 3.x / Python 3.x? Or are you going to go a different direction?
Firstly, thanks to you all for your thanks! I announced minnie as an ftp
site on comp.archives back in May 1991, so she must be one of the longest
continually operating Internet sites.
Yes, I plan on moving to Mailman 3.x. I'm hoping that I can import the raw
TUHS mbox (currently 130Mbytes). This, unfortunately, will break the hyperlinks
in the current mail archive at https://minnie.tuhs.org/pipermail/tuhs/
Anyway, first I've got to get SPF, DKIM and friends set up :-)
Cheers, Warren
5:42 a.m.
Hello!
And a definite thank you from this end of things as well Warren. Next
question, what about the FTP site?
-----
Gregg C Levine gregg.drwho8(a)gmail.com
"This signature fought the Time Wars, time and again."
On Thu, May 5, 2022 at 5:31 PM Warren Toomey via TUHS
<tuhs(a)minnie.tuhs.org> wrote:
On Wed, May 04, 2022 at 11:54:25AM -0600, Grant Taylor via TUHS wrote:
I'm curious what your thoughts / plans are
on migrating email.
I /think/ that TUHS (and presumably COFF) is using Mailman 2.x which I
believe is dependent on Python 2.x. Are you going to be migrating to
Mailman 3.x / Python 3.x? Or are you going to go a different direction?
Firstly, thanks to you all for your thanks! I announced minnie as an ftp
site on comp.archives back in May 1991, so she must be one of the longest
continually operating Internet sites.
Yes, I plan on moving to Mailman 3.x. I'm hoping that I can import the raw
TUHS mbox (currently 130Mbytes). This, unfortunately, will break the hyperlinks
in the current mail archive at https://minnie.tuhs.org/pipermail/tuhs/
Anyway, first I've got to get SPF, DKIM and friends set up :-)
Cheers, Warren
8:38 a.m.
On 5/5/22 3:26 PM, Warren Toomey via TUHS wrote:
Yes, I plan on moving to Mailman 3.x. I'm hoping
that I can import
the raw TUHS mbox (currently 130Mbytes). This, unfortunately,
will break the hyperlinks in the current mail archive
athttps://minnie.tuhs.org/pipermail/tuhs/
Let's chat about this when the time comes.
I strongly suspect there is a way to retain functionality for the old
links, even if they are simply redirects to the new location. -- I have
some ideas. }:-)
--
Grant. . . .
unix || die
8:52 a.m.
On Thu, May 5, 2022 at 8:41 PM Grant Taylor via TUHS <tuhs(a)minnie.tuhs.org>
wrote:
On 5/5/22 3:26 PM, Warren Toomey via TUHS wrote:
FreeBSD's archives were updated recently to not use mailman 3
despite the project using mailman 2 due to the link changing issue.
Warner
Yes, I plan on moving to Mailman 3.x. I'm
hoping that I can import
the raw TUHS mbox (currently 130Mbytes). This, unfortunately,
will break the hyperlinks in the current mail archive
athttps://minnie.tuhs.org/pipermail/tuhs/
Let's chat about this when the time comes.
I strongly suspect there is a way to retain functionality for the old
links, even if they are simply redirects to the new location. -- I have
some ideas. }:-)
10:32 a.m.
Pardon my ignorance as I am not familiar with mailman and its storage
format but I assume that running the mailbox through a Sed filter to change
Minnie to newmin would not work??? Minnie and newmin are the same length.
Any size data would therefore presumably remain valid. This assumes the
mail archive is text based for the most part.
Just thinking out loud....
On Thu, May 5, 2022, 10:41 PM Grant Taylor via TUHS <tuhs(a)minnie.tuhs.org>
wrote:
On 5/5/22 3:26 PM, Warren Toomey via TUHS wrote:
Yes, I plan on moving to Mailman 3.x. I'm
hoping that I can import
the raw TUHS mbox (currently 130Mbytes). This, unfortunately,
will break the hyperlinks in the current mail archive
athttps://minnie.tuhs.org/pipermail/tuhs/
Let's chat about this when the time comes.
I strongly suspect there is a way to retain functionality for the old
links, even if they are simply redirects to the new location. -- I have
some ideas. }:-)
--
Grant. . . .
unix || die
7 May
7 May
10:13 p.m.
On Thu., May 5, 2022, 7:38 p.m. Grant Taylor via TUHS,
<tuhs(a)minnie.tuhs.org> wrote:
On 5/5/22 3:26 PM, Warren Toomey via TUHS wrote:
When I saw this, I started to think, "I bet we can make a regexp for that".
Apparently, I do too much text processing. I'm up for helping process the
archive if needed with sed, perl or some such.
--
"...one of the main causes of the fall of the Roman Empire was that,
lacking zero, they had no way to indicate successful termination of
their C programs." -- Robert Firth
Yes, I plan on moving to Mailman 3.x. I'm
hoping that I can import
the raw TUHS mbox (currently 130Mbytes). This, unfortunately,
will break the hyperlinks in the current mail archive
athttps://minnie.tuhs.org/pipermail/tuhs/
Let's chat about this when the time comes.
I strongly suspect there is a way to retain functionality for the old
links, even if they are simply redirects to the new location. -- I have
some ideas. }:-)
9 May
9 May
10:12 p.m.
On 5/7/22 10:13 AM, Patrick Audley via TUHS wrote:
When I saw this, I started to think, "I bet we
can make a regexp for that".
:-D
Apparently, I do too much text processing.
Na. I don't think so. Text processing seems to be one (of the many)
thing(s) that Unix, et al., excel at. So I think it's probably natural
for anyone well versed in Unix ... to think "RegEx"!
I'm up for helping process the archive if needed
with sed, perl or
some such.
I think we're thinking about two different layers of actions. Both
using their own form of RegEx like behavior.
It sounds like you're talking about processing / munging an mbox mail
archive.
I'm thinking about URL re-writing in the web server, be it on the fly or
static configuration (for fixed list of old URLs).
--
Grant. . . .
unix || die
11:55 p.m.
Url rewriting
That would mean supporting that forever including the overhead in contrast
to the "SED modify the archive" approach is a one shot or so deal.
On Mon, May 9, 2022, 12:15 PM Grant Taylor via TUHS <tuhs(a)minnie.tuhs.org>
wrote:
On 5/7/22 10:13 AM, Patrick Audley via TUHS wrote:
When I saw this, I started to think, "I bet
we can make a regexp for
that".
:-D
Apparently, I do too much text processing.
Na. I don't think so. Text processing seems to be one (of the many)
thing(s) that Unix, et al., excel at. So I think it's probably natural
for anyone well versed in Unix ... to think "RegEx"!
I'm up for helping process the archive if
needed with sed, perl or
some such.
I think we're thinking about two different layers of actions. Both
using their own form of RegEx like behavior.
It sounds like you're talking about processing / munging an mbox mail
archive.
I'm thinking about URL re-writing in the web server, be it on the fly or
static configuration (for fixed list of old URLs).
--
Grant. . . .
unix || die
10 May
10 May
1:22 a.m.
It depends on what status you send; 301 is "moved permanently" and search
engines will get the hint; 302 is a temporary condition.
A quick look shows it's running Apache; mod_rewrite can handle things.
(And hey, on Linode, my $DAYJOB's latest acquisition :)
1:57 a.m.
On 5/9/22 11:55 AM, Kenneth Goodwin wrote:
Url rewriting
Yes.
That would mean supporting that forever including the
overhead in
contrast to the "SED modify the archive" approach is a one shot or so deal.
I'm concerned with supporting the URLs that are in all of the emails
that have been sent out over the years that point back to the archive.
sed won't change what's in someone else's email box. URL rewriting will
make sure that was was sent out in the past will continue to work in the
future. ;-)
--
Grant. . . .
unix || die
12:37 a.m.
Hi Warren,
пт, 6 мая 2022 г., 00:31 Warren Toomey via TUHS <tuhs(a)minnie.tuhs.org>:
Yes, I plan on moving to Mailman 3.x. I'm hoping
that I can import the raw
TUHS mbox (currently 130Mbytes). This, unfortunately, will break the
hyperlinks
in the current mail archive at https://minnie.tuhs.org/pipermail/tuhs/
I can provide you with advice on migration based on my vast experience.
Feel free to ask!
Sincerely,
Danil Smirnov
Mailman3.com
958
days inactive
963
days old
18 comments
12 participants
participants (12)
-
Andy Kosela -
Clem Cole -
Danil Smirnov -
Dave Horsfall -
Grant Taylor -
Gregg Levine -
Kenneth Goodwin -
Mary Ann Horton -
Patrick Audley -
Richard Salz -
Warner Losh -
Warren Toomey