Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!watmath!clyde!floyd!harpo!decvax!cca!z From: z@cca.UUCP (Steve Zimmerman) Newsgroups: net.unix-wizards Subject: Re: Terminal paging in the kernel Message-ID: <6954@cca.UUCP> Date: Wed, 21-Mar-84 09:12:59 EST Article-I.D.: cca.6954 Posted: Wed Mar 21 09:12:59 1984 Date-Received: Thu, 22-Mar-84 02:17:53 EST References: <6841@cca.UUCP> <690@ihuxx.UUCP> <216@masscomp.UUCP> <334@dual.UUCP> <1417@mit-eddie.UUCP> dual.372 Lines: 29 More answers to criticisms of page mode: First you have to find out what the terminal type is... this problem has not really been solved. Although there may be no 100% foolproof way of doing this that works automatically every time, the problem certainly has been solved in the general case. Whether people are using Berkeley Unix and ttytype or USG Unix and some other mechanism, the fact is that regular users of terminal dependent programs such as screen editors or "more" (and that should include just about everybody) already have some mechanism for getting their terminal type set correctly, either by the system or in their .login or .profile file. Once this is done, issuing the "stty page" command I described previously, typically in the .login or .profile file, works just fine. Although we run Berkeley Unix, most of our terminals hang off a port selector, so the ttytype file is of little use to us. Yet with a little intelligence in people's .login files, the terminal type is set correctly for whatever programs want to use it. In practice, no problems have arisen. A pager such as more knows when output is directed to a terminal and when it isn't, and behaves appropriately. Have you built the same knowledge into the kernel? Page mode is built into the terminal driver, and handles output from the terminal. When output is directed somewhere else, the page mode code is never called. Steve Zimmerman