The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: cubexyz@gmail.com (Mark Longridge)
Subject: [TUHS] ed.c on Unix v5
Date: Sat, 19 Dec 2015 03:34:52 -0500	[thread overview]
Message-ID: <CADxT5N4HL7PgqGSRo_EDRD1crGSdSG5KthLR1CHXZ7w01eXs-Q@mail.gmail.com> (raw)
In-Reply-To: <alpine.BSF.2.11.1512191321060.54277@aneurin.horsfall.org>

>> I trimmed the source a bit, there's a function at the
>> end called getpid()  which is commented out.

> If your V5 has getpid(), then it's a...  strange version...

I went back to the original uv5swre.zip file which was what I started
with and had another look to be sure.

It's not listed on tuhs under v5 but if one looks at /lib/libc.a via
'ar t getpid.o' you can see the object file getpid.o

There's no other trace of getpid in v5 as it's not in the v5 manual
and there's no getpid.s in the disk image. I'm not sure if having
getpid in v5 is anomalous or not, perhaps you or someone else can
actually remember as I'm a johnny-come-lately to the party.  There's
even some commands mentioned in the v4 manual that don't exist in the
v5 disk image.

It's possible that there's another Unix v5 that really doesn't have
it, perhaps an older one.

Mark





On 12/18/15, Dave Horsfall <dave at horsfall.org> wrote:
> On Thu, 17 Dec 2015, Mark Longridge wrote:
>
>> It's not much bigger than the assembled ed, with 1314 lines of C code
>> the compiled executable is only 6518 bytes vs 4292 for the original. I
>> was looking at the source code and didn't see anything that the v5 cc
>> couldn't handle. I trimmed the source a bit, there's a function at the
>> end called getpid()  which is commented out.
>
> If your V5 has getpid(), then it's a...  strange version...
>
> --
> Dave Horsfall DTM (VK2KFU)  "Those who don't understand security will
> suffer."
>



  reply	other threads:[~2015-12-19  8:34 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-17 15:13 Mark Longridge
2015-12-19  2:27 ` Dave Horsfall
2015-12-19  8:34   ` Mark Longridge [this message]
2015-12-19 14:57     ` Random832
2015-12-19 16:18     ` John Cowan
2015-12-19 17:02       ` Craig Lennox
2015-12-19 20:05         ` Random832
2015-12-19 18:36       ` Marc Rochkind
2015-12-19 12:12 Noel Chiappa
2015-12-19 12:40 ` Mark Longridge
2015-12-19 13:56 Noel Chiappa
2015-12-19 15:10 Noel Chiappa
2015-12-19 15:22 ` Random832
2015-12-19 15:47 Noel Chiappa

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=CADxT5N4HL7PgqGSRo_EDRD1crGSdSG5KthLR1CHXZ7w01eXs-Q@mail.gmail.com \
    --to=cubexyz@gmail.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).