The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Gregg Levine <gregg.drwho8@gmail.com>
To: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: [TUHS] Re: Other UNIX Archival Efforts?
Date: Mon, 21 Oct 2024 19:50:00 -0400	[thread overview]
Message-ID: <CAC5iaNFLO1rB4hYBRzaKiQ06eKQ4HWQA9Vqru2cCwwsBmmUqHA@mail.gmail.com> (raw)
In-Reply-To: <BDPvmQAx5K8T7ISJDcPVNGE5mMemhDrNQoNJVMwA_19C_PW3D9g7ybOWFlF9gpgS02koDb1IphQLaW-ofYm6dfxeF_jcVgGHPaQm9FpSGYQ=@protonmail.com>

Hello!
I normally prefer to lurk in the background on this list, but, I agree
with the gentleman asking that question. Warren I believe you
mentioned such a storage place. Please do consider his request.
-----
Gregg C Levine gregg.drwho8@gmail.com
"This signature was present when the impossible happened 23 years ago, twice."

On Mon, Oct 21, 2024 at 7:37 PM segaloco via TUHS <tuhs@tuhs.org> wrote:
>
> So with all that has happened with the Internet Archive lately, I
> do find myself a bit concerned regarding the UNIX materials that
> I know to only exist there.  Selfishly, this includes my own
> uploads here: https://archive.org/details/@segaloco
>
> I was curious if anyone has any suggestions on places beyond just
> IA and TUHS where I could see about getting this stuff mirrored?
> Unfortunately my stuff runs afoul of bitsavers's DPI requirements,
> that's the only other source that immediately comes
> to mind where these materials would find home.  Any thoughts?
>
> Warren, I know you had mentioned a "write only" archive you
> maintain regarding materials that need to be mothballed until legal
> understandings are reached, would you be comfortable with my
> contributing any of my materials the Caldera license does not apply
> to there?
>
> - Matt G.

  reply	other threads:[~2024-10-21 23:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-21 23:36 [TUHS] " segaloco via TUHS
2024-10-21 23:50 ` Gregg Levine [this message]
2024-10-22  2:34 ` [TUHS] " Warren Toomey via TUHS

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=CAC5iaNFLO1rB4hYBRzaKiQ06eKQ4HWQA9Vqru2cCwwsBmmUqHA@mail.gmail.com \
    --to=gregg.drwho8@gmail.com \
    --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).