Xref: utzoo comp.emacs:4901 comp.unix.microport:2304
Path: utzoo!attcan!uunet!uport!plocher
From: plocher@uport.UUCP (John Plocher)
Newsgroups: comp.emacs,comp.unix.microport
Subject: Re: GNU Emacs
Message-ID: <279@uport.UUCP>
Date: 16 Dec 88 19:22:39 GMT
References: <828@ubu.warwick.UUCP> <28173@tut.cis.ohio-state.edu> <10960@bigtex.cactus.org> <8791@wright.mips.COM> <1138@csuchico.EDU> <429@lehi3b15.UUCP> <121@cbw1.UUCP> <8525@alice.UUCP> <778@splut.UUCP> <8530@alice.UUCP>
Reply-To: plocher@uport.UUCP (John Plocher)
Organization: Microport Systems, Scotts Valley, CA
Lines: 18

In article <8530@alice.UUCP> debra@alice.UUCP () writes:
>I hate to tell you this, Jay, but Microbug clearly blew it on this one
>again. With SCO Xenix you would get the messages no matter on which virtual
>console you are. So you can figure out my next suggestion...
>
>Paul.

The messages printed by Unix kernels use a version of printf() which
bypasses the complete Virtual Console Subsystem and dumps the text directly
to the screen.

This is done by the ATT, ISC, Microport, and SCO versions of Unix to make sure
the messages get seen (what would happen if there was a bug in the console
driver and you couldn't change to the console VC?  You'd still want to see the
message! These messages also pass thru the osm (Operating System Messages)
driver so you can log them to a file amd find them with crash(1M).

  -John Plocher