Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: version B 2.10 5/3/83; site utcsrgv.UUCP Path: utzoo!utcsrgv!dudek From: dudek@utcsrgv.UUCP (Gregory Dudek) Newsgroups: net.unix-wizards Subject: Terminal paging. Message-ID: <3311@utcsrgv.UUCP> Date: Fri, 17-Feb-84 15:31:21 EST Article-I.D.: utcsrgv.3311 Posted: Fri Feb 17 15:31:21 1984 Date-Received: Fri, 17-Feb-84 16:36:18 EST References: mi-cec.195, <6667@cca.UUCP> Organization: CSRG, University of Toronto Lines: 14 <> Personally, I don't really like the idea of terminal paging, and in fact am usually happy with just ^S/^Q (although I never use a terminal faster than 9600 baud). For those who really want it though, I wonder if it wouldn't be possible to hook it in as a user process that would be "called" by the kernel. A terminal preprocessor could be identified on a per-process basis. This would allow users to use a standard terminal pager, a unique one, or none at all. Clearly this would involve a certain overhead, but is it unacceptably large? Several distributed file systems (eg. cocanet, I think) use this type of extra-kernel service routine, and it seems to work for them. Greg Dudek utcsrgv!dudek