From: cyrille.lefevre@laposte.net (Cyrille Lefevre)
Subject: [TUHS] Re: non-broken 4.3BSD set?
Date: Thu, 29 May 2003 17:44:13 +0200 [thread overview]
Message-ID: <20030529154413.GA52289@gits.dyndns.org> (raw)
In-Reply-To: <200212112326.gBBNQlr04157@minnie.tuhs.org>
On Thu, Dec 12, 2002 at 09:26:47AM +1000, Warren Toomey wrote:
> In article by Robertdkeys at aol.com:
> > Warren... is there a non-broken 4.3BSD-Tahoe set somewhere?
> > Bob
>
> As in a bootable 4.3BSD-Tahoe kit? As far as I know, no. The Unix Archive
> has a broken copy in 4BSD/Distributions/4.3BSD-Tahoe, indicating that
> both usr.tar and src.tar are broken.
>
> It might/should be possible to merge files from the CRSG CD set from Kirk
> to recreate these tar files.
>
> Anybody out there have an unbroken Tahoe release?
Hi, take a look at http://mapage.noos.fr/clefevre/4bsd/
you will found the listings of some archives found around the net some years ago.
don't ask me where, I can't remember. If you are interrested by one or more
of them, let me know, I'll provide you in a way or another.
FYI, appart the 4.3BSD-Tahoe archive, the following one is also broken :
4BSD/Distributions/4.3BSD-Rev2-Foreign/usr.tar.gz
4BSD/Distributions/4.3BSD-Tahoe/src.tar.gz
4BSD/Distributions/4.3BSD-Tahoe/usr.tar.gz
Cyrille.
--
Cyrille Lefevre mailto:cyrille.lefevre at laposte.net
next prev parent reply other threads:[~2003-05-29 15:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <ca.15d9a70c.2b28d371@aol.com>
2002-12-11 23:26 ` Warren Toomey
2003-05-29 15:44 ` Cyrille Lefevre [this message]
2002-12-12 3:22 Robertdkeys
2002-12-12 5:26 Michael Sokolov
2002-12-12 20:26 Robertdkeys
2002-12-12 20:45 Michael Sokolov
2002-12-12 23:36 Robertdkeys
2002-12-13 2:04 ` Andru Luvisi
2002-12-13 3:09 Robertdkeys
2002-12-13 5:36 Michael Sokolov
2002-12-13 5:43 Michael Sokolov
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=20030529154413.GA52289@gits.dyndns.org \
--to=cyrille.lefevre@laposte.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).