From: macbiesz@optonline.net (Maciek Bieszczad)
Subject: [TUHS] v6on286
Date: Tue, 08 Jul 2003 22:34:51 -0400 [thread overview]
Message-ID: <000001c345c2$ad14f670$06fea8c0@maciek> (raw)
In-Reply-To: <20030709002523.GA7146@minnie.tuhs.org>
Ah, silly of me. If I used FTP, that could have saved a couple wasted
hours compiling v6on286 :)
--
Maciek (macbiesz at optonline.net)
-----Original Message-----
From: Warren Toomey [mailto:wkt@tuhs.org]
Sent: Tuesday, July 08, 2003 8:25 PM
To: Maciek Bieszczad
Subject: Re: [TUHS] v6on286
?! It's still here at ftp://minnie.tuhs.org/UnixArchive/Other/V6on286/
but I'm not sure why Apache hides the README when the same directory
is viewed with http://www.tuhs.org/Archive/Other/V6on286/, I'd better
check that out.
Warren
next parent reply other threads:[~2003-07-09 2:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20030709002523.GA7146@minnie.tuhs.org>
2003-07-09 2:34 ` Maciek Bieszczad [this message]
2003-08-11 18:38 JStevens
-- strict thread matches above, loose matches on Subject: below --
2003-08-08 22:14 JStevens
2003-07-09 16:25 Steve Nickolas
2003-07-08 16:08 Steve Nickolas
2003-07-08 5:21 Steve Nickolas
2003-07-08 15:07 ` Maciek Bieszczad
2003-07-09 7:00 ` SZIGETI Szabolcs
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='000001c345c2$ad14f670$06fea8c0@maciek' \
--to=macbiesz@optonline.net \
/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).