The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: newsham@lava.net (Tim Newsham)
Subject: [Unix-jun72] sh.s
Date: Sun, 11 May 2008 10:56:19 -1000 (HST)	[thread overview]
Message-ID: <Pine.BSI.4.64.0805111050460.20114@malasada.lava.net> (raw)

I did a comparison of s2's /bin/sh and the sh.s we have (notes in
the notes file about this).  There were a few changes, but they were
pretty similar.  I added a patch in the patches directory that reflects
the changes and I verified that if you build with the patch you get
an identical binary (modulo the padding bytes that the assembler
fills in for ".." and ".even").  It's currently marked as an optional
patch and the sh.s build isn't being installed over /bin/sh in the
rf0.dsk image.

I think the sh.s listing itself might be defective in two ways:

    - There's an rts missing at the end of the "error" function
    - It doesn't check for the "*" character when looking for globbing.

The 1e man page does list "*" as one of the globbing characters,
so its likely that these three instructions (1 rts, 2 for comparison)
somehow got dropped from the commented jun72 listing.  I'm torn between
adding them to the original "pages" sources as obvious mistakes or
just leaving it out and using a patch to fix it.  Right now we don't
have a patch that adds just these two fixes.  I guess if we did that and
made it a mandatory patch, we could use the sh we build from sh.s as
/bin/sh in the images.

I look forward to seeing what shell sources we might get from the s1
fragments recovery.

Tim Newsham
http://www.thenewsh.com/~newsham/



                 reply	other threads:[~2008-05-11 20:56 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=Pine.BSI.4.64.0805111050460.20114@malasada.lava.net \
    --to=newsham@lava.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).