From: arnold@skeeve.com
To: web@loomcom.com, kevin.bowling@kev009.com
Cc: tuhs@tuhs.org
Subject: Re: [TUHS] Wanted: AT&T System V Release 3.2.{1,2,3} Source Code
Date: Sun, 20 Jan 2019 07:35:46 -0700 [thread overview]
Message-ID: <201901201435.x0KEZkbj009115@freefriends.org> (raw)
In-Reply-To: <CAK7dMtACY=LH_WpRc7Hp4=ZaRT8v51jFVxvc12r1Bw67Bvg-kg@mail.gmail.com>
If it'd be possible to run SVr4 on the 3B2 emulator, that'd be really
cool, particularly if there's a C compiler available. That would give
us long filenames and the possible ability to bootstrap some version
of GCC for C89 compatibility, and from there, maybe, to more modern
tools.
Otherwise, I can't imagine (anymore) trying to do anything on a system with
only 14 character filenames.
Arnold
Kevin Bowling <kevin.bowling@kev009.com> 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> 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
> >
next prev parent reply other threads:[~2019-01-20 14:36 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 [this message]
2019-02-01 17:10 ` Al Kossow
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=201901201435.x0KEZkbj009115@freefriends.org \
--to=arnold@skeeve.com \
--cc=kevin.bowling@kev009.com \
--cc=tuhs@tuhs.org \
--cc=web@loomcom.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).