The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Al Kossow <aek@bitsavers.org>
To: tuhs@minnie.tuhs.org
Subject: Re: [TUHS] Wanted: AT&T System V Release 3.2.{1,2,3} Source Code
Date: Fri, 1 Feb 2019 09:10:27 -0800	[thread overview]
Message-ID: <89b0ff51-70c9-1141-2174-bc1141ca08f8@bitsavers.org> (raw)
In-Reply-To: <CAK7dMtACY=LH_WpRc7Hp4=ZaRT8v51jFVxvc12r1Bw67Bvg-kg@mail.gmail.com>

I turned up some 3B2 3.2 binary floppies in the CHM collection.
Will see if I can get those archived.

I also just brought up V/386 3.2.3 on a 6386 WGS and am trying to find the C development floppies.


On 1/20/19 1:01 AM, Kevin Bowling wrote:
> As far as I could find, the binary distribution is not readily available (and maybe /was/ not readily available, this
> seemed to be late enough to just be a code dump for source licensees).
> 
> It would be fun to try and build this into a useable release, but I have not yet determined if everything is there as
> well as if a 3.2 system can hoist the build.
> 
> On Sat, Jan 19, 2019 at 5:15 PM Seth J. Morabito <web@loomcom.com <mailto:web@loomcom.com>> wrote:
> 
> 
>     Kevin Bowling writes:
> 
>     > I believe there is a sysvr4 source dump floating around with the 3b2
>     > base
> 
>     It turns out, you're quite right!
> 
>     I originally had an SVR4 dump from who knows where that did not contain
>     the /usr/src/uts/3b2 directory, but I recently was the benefactor of
>     *another* dump. This time, it looks like the real deal. /usr/src/uts/3b2
>     is there in all its glory.
> 
>     This is probably all I need to get going.
> 
>     All the best,
> 
>     -Seth
>     --
>       Seth Morabito
>       Poulsbo, WA, USA
>       web@loomcom.com <mailto:web@loomcom.com>
> 


  parent reply	other threads:[~2019-02-01 17:15 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-18 16:20 Seth J. Morabito
2019-01-19 14:09 ` Kevin Bowling
2019-01-20  0:08   ` Seth J. Morabito
2019-01-20  9:01     ` Kevin Bowling
2019-01-20 14:35       ` arnold
2019-02-01 17:10       ` Al Kossow [this message]
2019-02-03 20:18         ` Al Kossow

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=89b0ff51-70c9-1141-2174-bc1141ca08f8@bitsavers.org \
    --to=aek@bitsavers.org \
    --cc=tuhs@minnie.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).