Xref: utzoo comp.unix.microport:1344 comp.unix.questions:8900 comp.unix.wizards:10592 Path: utzoo!utgpu!attcan!uunet!lll-winken!lll-tis!ames!ncar!boulder!spot!wu From: wu@spot.Colorado.EDU (WU SHI-KUEI) Newsgroups: comp.unix.microport,comp.unix.questions,comp.unix.wizards Subject: Re: SVR3 console message capturing Keywords: SVR3, Bell Tech, System V/386 Message-ID: <2865@boulder.Colorado.EDU> Date: 19 Aug 88 16:26:02 GMT References: <184@thebes.Thalatta.COM> <11426@lll-winken.llnl.gov> <13439@agate.BERKELEY.EDU> Sender: news@boulder.Colorado.EDU Reply-To: wu@spot.Colorado.EDU (WU SHI-KUEI) Distribution: na Organization: University of Colorado, Boulder Lines: 17 In article <13439@agate.BERKELEY.EDU> ewv@zippy.berkeley.edu (Eric Varsanyi) writes: >In article <11426@lll-winken.llnl.gov> bowles@lll-crg.llnl.gov.UUCP (Jeff Bowles) writes: >>In article <184@thebes.Thalatta.COM> gregoire@Thalatta.COM (Keith Gregoire) writes: >>>I am looking for a way of capturing console error messages (notices, >>Included in the Bell Tech release (and EVERY System V source release since >>SVR3.0) is a driver called "osm". Our console is a Qume 102 terminal with a printer port. That port feeds a PC serial to parallel buffer (Microfazer), which in turn feeds an ancient and slow Epson printer. This kludge lets the console run at 9600 while still capturing everything on paper (YECH). All this on a 3B2/400 running SV.2.04. Only a guest here, I really am: Carl Brandauer uunet!nbires!bdaemon!carl