The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Paul Riley <paul@rileyriot.com>
To: Noel Chiappa <jnc@mercury.lcs.mit.edu>
Cc: tuhs <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] Fwd: Choice of Unix for 11/03 and 11/23+ Systems
Date: Fri, 2 Oct 2020 08:23:43 +0800	[thread overview]
Message-ID: <CAD05_j0QxT1xn7w-9DT7u5WTOWmeib+HQviVg0mTueNKy+RBvw@mail.gmail.com> (raw)
In-Reply-To: <20201001125118.DDBBC18C0EB@mercury.lcs.mit.edu>

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

Seems like you're firmly in the footsteps of the creators now... :-)

*Paul Riley*

Mo: +86 186 8227 8332
Email: paul@rileyriot.com



On Thu, 1 Oct 2020 at 20:52, Noel Chiappa <jnc@mercury.lcs.mit.edu> wrote:

>     > From: Paul Riley
>
>     > So mounting Mini-Unix on a running V6 system I guess allows you to
> run
>     > Mini-Unix user mode binaries stuff
>
> Ah, no. They are all link-loaded to run at TOPSYS (060000), so won't run on
> V6 native.
>
>     > Or do you plan to recompile on a stable system?
>
> Well, I need to find out what the problem is, first.
>
>
> Still, notable progress: using my 'mount the Mini-Unix RK pack on a V6
> system'
> hack (which woked fine; the native V6 'icheck' and 'dcheck' work on that
> pack), I was able to sucessfully compile a few tweaked system modules (to
> get
> my usual line-editing chars, and turn off that irritating lower-case mode),
> and then build an OS load which could sucessfully boot. So good progress
> there. A couple of things I learned:
>
> - MiniUnix tools use the 'new' archive format, so the V6 vanilla 'ar'
> doen't
> grok MiniUnix archives (e.g. lib1/lib2). I have a 'nar', which I found on
> the
> 'Shoppa disks', which can deal with them. (We don't have source for it, but
> I'll bet the MIT PWB1 system has that; I'll get to that eventuallly.
> There's also
> an 'ar.c' on the MiniUnix disk; between the two, we'll be able to
> reconstitute
> source for 'nar'.)
>
> - Also, the vanilla V6 linker, 'ld', _also_ doesn't understand new
> archives;
> so the shell file to build a new system, 'shld':
>
>   ld -a -x low.o conf.o lib1 lib2
>
> blows out because it doesn't grok the libraries. Also, the '-a' flag, which
> says 'link starting at 0, not TOPSYS', doesn't exist in the V6 'ld'.
>
> I got around all that by unpacking lib1 (using 'nar', above) - it only
> contains
> two files - and then listing the files to link directly:
>
>   ld -x low.o conf.o syso emulo dev/kl.o dev/devstart.o dev/rk.o
>
> The vanilla V6 linker of course produces an output linked at 0 without
> the -a flag.
>
>
> At some point, I'll produce a 'MiniUnix ld' on vanilla V6, so I can build
> MiniUnix versions of applications there; the first will be the shell, so I
> don't have to keep typing 'chdir' instead of 'cd'! :-)
>
> Then on to trying to find out why MiniUnix crashes whenever I try and do
> anything significant.
>
>        Noel
>

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

  reply	other threads:[~2020-10-02  0:24 UTC|newest]

Thread overview: 70+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-01 12:51 Noel Chiappa
2020-10-02  0:23 ` Paul Riley [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-02-03  1:25 Noel Chiappa
2020-10-18 21:36 Norman Wilson
2020-10-12 22:43 Noel Chiappa
2020-10-12 19:27 Noel Chiappa
2020-10-10 23:29 Noel Chiappa
2020-10-11  2:30 ` Jay Logue
2020-10-11 23:24 ` Paul Riley
2020-10-12  0:53   ` Dave Horsfall
2020-10-12  1:56     ` Warner Losh
2020-10-12  2:09       ` Andrew Warkentin
2020-10-12 16:57       ` Arthur Krewat
2020-10-18 20:42     ` Michael Huff
2020-10-08 23:49 Noel Chiappa
2020-10-08 16:06 Noel Chiappa
2020-10-06 23:08 Noel Chiappa
2020-10-07  5:24 ` Jay Logue
2020-10-06 20:34 Noel Chiappa
2020-10-06 19:34 Noel Chiappa
2020-10-06 19:04 Noel Chiappa
2020-10-06 14:46 Noel Chiappa
2020-10-06 16:22 ` jay-tuhs9915
2020-10-02  0:39 Noel Chiappa
2020-09-30 23:16 Noel Chiappa
2020-09-30 18:51 Noel Chiappa
2020-09-30 17:58 Noel Chiappa
2020-09-28 23:21 Noel Chiappa
2020-09-30  1:50 ` Paul Riley
2020-09-27 21:07 Noel Chiappa
2020-09-27 21:12 ` Warner Losh
2020-09-28  0:22   ` Pete Turnbull
2020-09-27 20:50 Noel Chiappa
2020-09-29 13:20 ` Paul Riley
2020-09-25 22:08 Noel Chiappa
2020-09-26 14:52 ` John Foust
2020-09-28  0:03 ` Paul Riley
2020-09-28  0:06   ` Paul Riley
2020-09-24 18:56 Noel Chiappa
2020-09-24 13:04 Noel Chiappa
2020-09-24 18:24 ` John Cowan
2020-09-24 11:02 Paul Ruizendaal
2021-02-03  0:12 ` Greg A. Woods
2020-09-24  1:28 Noel Chiappa
2020-09-23 23:14 Noel Chiappa
2020-09-24  1:09 ` John Foust
2020-09-22 21:51 John Foust
2020-09-22 21:36 Noel Chiappa
2020-09-22 21:46 ` Warner Losh
2020-09-22 21:49 ` John Foust
2020-09-22 15:59 Noel Chiappa
2021-02-03  0:07 ` Greg A. Woods
2020-09-22  0:47 Noel Chiappa
2020-09-21 19:37 Noel Chiappa
2020-09-21 23:16 ` devin davison
2020-09-21 18:13 Noel Chiappa
2020-09-21 17:59 Noel Chiappa
2020-09-21 18:18 ` Arthur Krewat
2020-09-20 13:12 Noel Chiappa
2020-09-19 15:28 Noel Chiappa
2020-09-21 10:26 ` Paul Riley
2021-01-24 16:07 ` Tom Ivar Helbekkmo via TUHS
2021-01-25  4:58   ` Gregg Levine
2021-01-25  8:21     ` Tom Ivar Helbekkmo via TUHS
     [not found] <CAD05_j1bc6DDRtfPkd4QVeWXjwSp73bty46D=2ATozUbHThBWw@mail.gmail.com>
2020-09-19  3:22 ` Paul Riley
2020-09-19 14:20   ` Heinz Lycklama
2020-09-21 13:54     ` Paul Riley
2020-09-21 15:30       ` Heinz Lycklama
2020-09-21 23:27   ` Henry Bent
     [not found]     ` <4C35E6D2-8ABD-4DC2-BB2F-F15FA5BF30DD@icloud.com>
2020-09-22  0:22       ` Henry Bent

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=CAD05_j0QxT1xn7w-9DT7u5WTOWmeib+HQviVg0mTueNKy+RBvw@mail.gmail.com \
    --to=paul@rileyriot.com \
    --cc=jnc@mercury.lcs.mit.edu \
    --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).