From: Al Kossow <aek@bitsavers.org>
To: tuhs@tuhs.org
Subject: [TUHS] Re: Planning for the future was Re: Sad but not unexpected news about the LCM-L
Date: Wed, 26 Jun 2024 08:18:33 -0700 [thread overview]
Message-ID: <6ac3ca30-1181-314e-d465-1b5bce258fcd@bitsavers.org> (raw)
In-Reply-To: <3d1cbccf-e4c5-47bb-8ad9-81079b53d9b0@gmail.com>
On 6/26/24 7:30 AM, Will Senn wrote:
> what's the deal with Bitsavers (I see mirrors including
> content on Archive.org)?
They throw things into the Wayback Machine and mangle the filenames and destroy the directory heirarchy
somewhere else. I'm disappointed that the major search engines seem to return what is at IA first. It
isn't even necessarily the most recent version of a file.
The Computer History Museum has committed to being a mirror site
http://bitsavers.computerhistory.org
The intention in some day to integrate it with the "Open CHM" project, but the infrastructure for that
is still a work in progress.
next prev parent reply other threads:[~2024-06-26 15:18 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-25 18:17 [TUHS] " Clem Cole
2024-06-26 0:56 ` [TUHS] " Aron Insinga
2024-06-26 1:29 ` Larry McVoy
2024-06-26 3:34 ` [TUHS] Re: Trust stuff, " John Levine
2024-06-26 9:22 ` [TUHS] Wills. (Was: Sad but not unexpected news about the LCM-L) Ralph Corderoy
2024-06-26 1:42 ` [TUHS] Re: Sad but not unexpected news about the LCM-L George Michaelson
2024-06-26 17:22 ` aki
2024-06-26 1:44 ` Paul Guertin
2024-06-26 1:46 ` Dan Cross
2024-06-26 2:46 ` Paul Guertin
2024-06-26 5:36 ` Lars Brinkhoff
2024-06-26 14:30 ` [TUHS] Planning for the future was " Will Senn
2024-06-26 15:18 ` Al Kossow [this message]
2024-06-26 21:57 ` [TUHS] Re: Planning for the future Warren Toomey via TUHS
2024-06-30 13:05 ` Will Senn
2024-06-26 16:56 ` [TUHS] Re: Sad but not unexpected news about the LCM-L aki
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=6ac3ca30-1181-314e-d465-1b5bce258fcd@bitsavers.org \
--to=aek@bitsavers.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).