The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Warner Losh <imp@bsdimp.com>
To: Grant Taylor <gtaylor@tnetconsulting.net>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: [TUHS] Re: Historical application software
Date: Fri, 27 May 2022 11:29:26 -0600	[thread overview]
Message-ID: <CANCZdfovizoybaMgddsd_QS+KZTv52yfO9cLX8mPqG=_OB46vg@mail.gmail.com> (raw)
In-Reply-To: <66ae3ff2-bd07-e192-a00f-f9c701d857c8@spamtrap.tnetconsulting.net>

[-- Attachment #1: Type: text/plain, Size: 1673 bytes --]

On Fri, May 27, 2022 at 11:00 AM Grant Taylor via TUHS <tuhs@tuhs.org>
wrote:

> On 5/27/22 5:57 AM, Paul Ruizendaal wrote:
> > I came across a website that discusses reviving an old binary for Lotus
> > 1-2-3 for SysV Unix (386 COFF), on the way to making it run on Linux:
> >
> > https://lock.cmpxchg8b.com/linux123.html
>
> Yep.  That is a very interesting article.
>
> Though I do think that some of what Tavis did was borderline
> exceptional.  I don't know many people that would consider writing their
> own object utility to do things.  But this just goes to show what is
> possible if you are willing to do so.
>

People working on emulators run into these issues all the time as well.
There was a greater diversity of object formats when Unix was younger
as well, most have been displaced by ELF (PECOFF being the only exception
that's still around outside of Windows).

Also people that try to decompile things back into .o files run into these
issues as well... There's been efforts over the years to extract different
kinds
of drivers from old binary-only kernels, for example, that have met with
differing
degrees of success. Though putting the relocation info back in after the
fact can be quite tricky... The successful ones I know of disassembled and
reassembled to cope with this issue after some post-processing phase to
cope with places where there were tables...


> > The audience here may enjoy the read, and maybe it is of use when
> > reviving other old application software for 1980’s and 1990’s Unix.
>
> I've filed it away for future reference for this very reason.
>

 Yea, it's quite interesting...

[-- Attachment #2: Type: text/html, Size: 2422 bytes --]

  reply	other threads:[~2022-05-27 17:29 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-27 11:57 [TUHS] " Paul Ruizendaal
2022-05-27 17:00 ` [TUHS] " Grant Taylor via TUHS
2022-05-27 17:29   ` Warner Losh [this message]
2022-05-28 15:30     ` Paul Winalski
2022-05-29  0:57       ` Warner Losh
2022-05-29  9:43         ` Ralph Corderoy
2022-06-03  2:00         ` Chris Hanson
2022-06-03  2:09           ` Warner Losh
2022-06-03  2:02       ` Chris Hanson
2022-05-28 22:06 ` [TUHS] Anyone have an interest in really old analog multimeters and a vacuum tube tested circa 1960s or 1950s? Kenneth Goodwin
2022-05-28 22:09   ` [TUHS] " Kenneth Goodwin
2022-05-28 23:31     ` Ed Cashin
2022-05-28 23:45       ` Clem Cole
2022-05-29  2:11         ` Kenneth Goodwin
2022-05-29  2:18           ` Kenneth Goodwin
     [not found]             ` <99E8871E-035C-4A58-8091-189EDE4689BA@common-sense.com>
     [not found]               ` <CAMQbRb2uPTaqCrZCnVQuBtHhnFZWPpyZ_fHxs-4h8WGoOCrGJQ@mail.gmail.com>
2022-05-29 13:05                 ` Kenneth Goodwin
2022-05-29  2:08       ` Kenneth Goodwin
2022-05-29  2:10       ` Kenneth Goodwin

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='CANCZdfovizoybaMgddsd_QS+KZTv52yfO9cLX8mPqG=_OB46vg@mail.gmail.com' \
    --to=imp@bsdimp.com \
    --cc=gtaylor@tnetconsulting.net \
    --cc=tuhs@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).