The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: clemc@ccc.com (Clem Cole)
Subject: [TUHS] pre-more pager?
Date: Wed, 8 Nov 2017 22:00:21 +0000	[thread overview]
Message-ID: <CAC20D2PMX58fkxaeJ8_hziaBsrzTXTX-p0a5VjQLDO5B6FGarA@mail.gmail.com> (raw)
In-Reply-To: <fcf85cee-b863-fbc7-82d2-32177d15eef9@gmail.com>

fout and flush -- Looks like the V6 version of cr3 - which is using the
portable C library which was done before the standard C library.
I bet if you grab the one from 2BSD that should have been updated to V7

On Wed, Nov 8, 2017 at 9:18 PM, Will Senn <will.senn at gmail.com> wrote:

> On 11/8/17 1:22 PM, Random832 wrote:
>
>> Some of these are for V7 or V6 contemporary PDP-11 Unixes, and most of
>> them are far simpler than more so you should have little difficulty
>> getting them working anyway.
>>
>> Links:
>> http://minnie.tuhs.org/cgi-bin/utree.pl?file=1BSD/s6/cr3.c
>> http://minnie.tuhs.org/cgi-bin/utree.pl?file=2BSD/src/cr3.c
>> http://minnie.tuhs.org/cgi-bin/utree.pl?file=2.9BSD/usr/src/ucb/more.c
>> http://minnie.tuhs.org/cgi-bin/utree.pl?file=32V/usr/src/cmd/pg.c
>> http://minnie.tuhs.org/cgi-bin/utree.pl?file=AUSAM/source/S/pg.c
>> (apparently unrelated to the 32V version)
>> http://minnie.tuhs.org/cgi-bin/utree.pl?file=SRI-NOSC/s2/pg.c
>> http://minnie.tuhs.org/cgi-bin/utree.pl?file=OpenSolaris_b135/cmd/pg/pg.c
>>
>> https://danhalbert.org/more.html - mentions cr3
>>
>
> It makes sense that it used to be paper based and slow on screen.
>
> Regarding the links and old bsd's. The binary cr3 on 1bsd works in v7.
> Also, the book I'm reading has a c program that does paging. But, I'm
> always off down the rabbit hole... I tried to compile the cr3.c source and
> I get this error:
>
> # cc cr3.c
> Undefined:
> _fout
> _flush
> _getc
> _end
>
> My understanding is that cc includes libc by default, so these must not be
> in libc. But getc is standard lib, so what am I missing?
>
> Thanks,
>
> Will
>
> --
> GPG Fingerprint: 68F4 B3BD 1730 555A 4462  7D45 3EAA 5B6D A982 BAAF
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20171108/c76d0157/attachment.html>


  parent reply	other threads:[~2017-11-08 22:00 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-08 18:54 Will Senn
2017-11-08 18:59 ` Clem Cole
2017-11-08 19:06 ` Arthur Krewat
2017-11-08 19:31   ` Jeremy C. Reed
2017-11-08 22:43   ` Dave Horsfall
2017-11-08 22:47     ` Arthur Krewat
2017-11-08 23:21       ` Dave Horsfall
2017-11-09  4:38         ` Will Senn
2017-11-09 13:18           ` Dan Cross
2017-11-09 14:29             ` Will Senn
2017-11-09 20:53           ` Dave Horsfall
2017-11-10  0:15             ` Arthur Krewat
2017-11-10  2:14               ` Ralph Corderoy
2017-11-08 19:12 ` Bakul Shah
2017-11-08 19:22 ` Random832
2017-11-08 21:18   ` Will Senn
2017-11-08 21:59     ` Ron Natalie
2017-11-08 22:00     ` Clem Cole [this message]
2017-11-08 22:18       ` Will Senn
2017-11-09  2:01   ` Steve Johnson
2017-11-09  2:16     ` Lyndon Nerenberg
2017-11-08 19:29 ` Forrest, Jon
2017-11-08 19:43   ` Ron Natalie
2017-11-08 21:03   ` Mark Green
2017-11-08 19:23 Noel Chiappa
2017-11-08 20:02 Noel Chiappa
2017-11-08 20:11 ` Forrest, Jon
2017-11-10  5:26   ` Random832
2017-11-10  7:31     ` Otto Moerbeek
2017-11-08 20:18 ` Clem Cole
2017-11-08 20:28   ` Ron Natalie
2017-11-08 22:47 ` Dave Horsfall
2017-11-08 20:28 Noel Chiappa
2017-11-08 22:02 Paul Ruizendaal
2017-11-08 22:20 ` Will Senn
2017-11-08 22:58 Doug McIlroy
2017-11-09 13:33 Doug McIlroy
2017-11-09 16:19 Norman Wilson
2017-11-09 16:48 ` Arthur Krewat
2017-11-09 17:19   ` Steve Nickolas
2017-11-09 18:15     ` Don Hopkins
2017-11-09 18:26     ` Arthur Krewat

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=CAC20D2PMX58fkxaeJ8_hziaBsrzTXTX-p0a5VjQLDO5B6FGarA@mail.gmail.com \
    --to=clemc@ccc.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).