From mboxrd@z Thu Jan 1 00:00:00 1970 From: cubexyz@gmail.com (Mark Longridge) Date: Sat, 19 Dec 2015 03:34:52 -0500 Subject: [TUHS] ed.c on Unix v5 In-Reply-To: References: Message-ID: >> 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 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." >