The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: grog@lemis.com (Greg 'groggy' Lehey)
Subject: [TUHS] Recovering flaky CDs (was:  mach & nextstep.)
Date: Wed, 31 Oct 2007 09:36:55 +1100	[thread overview]
Message-ID: <20071030223654.GA72133@dereel.lemis.com> (raw)
In-Reply-To: <20071011151401.1dff3613@veda.cnb.uam.es>

On Thursday, 11 October 2007 at 15:14:01 +0200, Jose R. Valverde wrote:
>> I *think* I have.
>>
>> Thank goodness yo mention this! I believe I have copies on CD-ROM dating back
>> from '94 or so. I'll dig them up. The problem is I believed I also had them on
>> the FTP server, but they aren't. I must have lost them on one disk crash or
>> another and didn't notice, so your question is great for I might part of the
>> original CDs and lose it.
>>
>> 'nuff said. I'll check this afternoon when I go back home and try to find again
>> those old CDs (cross your fingers).
>
> Bad luck. The CD's are lost (unreadable actually). Not surprising
> seeing as they were old and had been tossed around so many times
> (sic).

Is there anybody on this list who knows a way of recovering flaky CDs?

Greg
--
Finger grog at lemis.com for PGP public key.
See complete headers for address and phone numbers.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20071031/b18c63b2/attachment.sig>


  reply	other threads:[~2007-10-30 22:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-11 13:14 [TUHS] mach & nextstep Jose R. Valverde
2007-10-30 22:36 ` Greg 'groggy' Lehey [this message]
2007-10-30 23:26   ` [TUHS] Recovering flaky CDs Al Kossow
2007-10-31  9:22     ` asbesto
2007-11-05 17:07   ` [TUHS] Recovering flaky CDs (was: mach & nextstep.) Jose R. Valverde

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=20071030223654.GA72133@dereel.lemis.com \
    --to=grog@lemis.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).