From: segaloco via TUHS <tuhs@tuhs.org>
To: josh <joshnatis0@gmail.com>
Cc: "tuhs@tuhs.org" <tuhs@tuhs.org>
Subject: [TUHS] Re: Setting up an X Development Environment for Mac OS
Date: Thu, 26 Jan 2023 16:07:31 +0000 [thread overview]
Message-ID: <R5wOXkWssqxYtpNAmdT90jQP2qCwEv2mH-jCH6NHeIHzamFBCq7h63fwNQP1wEVfWBD56jJ19sO3PtMNxBFE3IzP68H4JxEffZWy2IqPoQk=@protonmail.com> (raw)
In-Reply-To: <CAFZukdRGG6xWCyLsF_wiPsf5JsPFwRm7Hty=BbK2a4UjxaAyYQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 969 bytes --]
Excellent post, thanks for the share! I think about that loss of information often. Its a shame preservation hasn't been more of a theme, there are probably countless iconic video games for which the original source code doesn't exist anymore. If "digital archivist" was more in-demand in tech companies I'd love to engage with that sort of work professionally...maybe someday.
- Matt G.
------- Original Message -------
On Thursday, January 26th, 2023 at 7:28 AM, josh <joshnatis0@gmail.com> wrote:
> On Thursday, January 26, 2023, Ralph Corderoy <ralph@inputplus.co.uk> wrote:
>
>> Rob Pike wrote of magnetic tapes he had which could no longer be read.
>> The coating had failed off IIRC. I tried to find the text but failed.
>> Perhaps it was on one of those Google+, Posterous, ... transient things.
>
> Hi Ralph, I think you’re referring to this blog post (which I’ve also previously struggled to find): https://commandcenter.blogspot.com/2014/08/prints.html
[-- Attachment #2: Type: text/html, Size: 1695 bytes --]
next prev parent reply other threads:[~2023-01-26 16:07 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-25 20:38 Noel Chiappa
2023-01-25 21:25 ` Clem Cole
2023-01-26 6:30 ` Lars Brinkhoff
2023-01-26 10:56 ` Ralph Corderoy
2023-01-26 12:01 ` arnold
2023-01-26 13:25 ` Lars Brinkhoff
2023-01-26 15:28 ` [TUHS] " josh
2023-01-26 16:07 ` segaloco via TUHS [this message]
2023-01-26 16:48 ` [TUHS] " emanuel stiebler
2023-01-26 21:19 ` segaloco via TUHS
2023-01-26 22:51 ` Andy Kosela
2023-01-27 0:48 ` segaloco via TUHS
2023-01-27 4:07 ` Will Senn
2023-01-27 14:08 ` Chet Ramey
2023-01-27 14:49 ` Ron Natalie
2023-01-27 15:53 ` Dan Cross
2023-01-27 16:12 ` [TUHS] NEXTSTEP 486 [was " Charles H Sauer (he/him)
2023-01-27 14:17 ` [TUHS] " Ralph Corderoy
2023-01-27 13:56 ` Ralph Corderoy
2023-01-27 14:54 ` Ron Natalie
2023-01-27 16:10 ` Larry McVoy
2023-01-28 22:15 ` Dave Horsfall
2023-01-29 0:31 ` Kevin Bowling
2023-01-29 11:07 ` emanuel stiebler
2023-01-27 21:42 ` Tom Perrine
2023-01-28 2:18 ` Larry McVoy
2023-01-28 2:49 ` Tom Perrine
2023-01-26 6:32 ` Lars Brinkhoff
2023-01-26 9:45 ` emanuel stiebler via TUHS
-- strict thread matches above, loose matches on Subject: below --
2023-01-25 1:46 [TUHS] " Will Senn
2023-01-25 7:45 ` [TUHS] " segaloco via TUHS
2023-01-25 8:00 ` Lars Brinkhoff
2023-01-25 16:41 ` Rich Salz
2023-01-25 19:53 ` Theodore Ts'o
2023-01-25 20:04 ` Dan Cross
2023-01-25 20:23 ` Larry McVoy
2023-01-25 20:27 ` Chet Ramey
2023-01-27 4:49 ` Theodore Ts'o
2023-01-27 18:05 ` Henry Mensch
2023-01-27 18:24 ` Charles H Sauer (he/him)
2023-01-26 13:17 ` Marc Donner
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='R5wOXkWssqxYtpNAmdT90jQP2qCwEv2mH-jCH6NHeIHzamFBCq7h63fwNQP1wEVfWBD56jJ19sO3PtMNxBFE3IzP68H4JxEffZWy2IqPoQk=@protonmail.com' \
--to=tuhs@tuhs.org \
--cc=joshnatis0@gmail.com \
--cc=segaloco@protonmail.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).