Xref: utzoo comp.unix.microport:1325 comp.unix.questions:8873 comp.unix.wizards:10548 Path: utzoo!utgpu!water!watmath!clyde!motown!vilya!lcuxlm!whuts!att!rutgers!cmcl2!nrl-cmf!ames!lll-tis!lll-winken!lll-crg.llnl.gov!bowles From: bowles@lll-crg.llnl.gov (Jeff Bowles) 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: <11426@lll-winken.llnl.gov> Date: 18 Aug 88 13:42:38 GMT References: <184@thebes.Thalatta.COM> Sender: usenet@lll-winken.llnl.gov Reply-To: bowles@lll-crg.llnl.gov.UUCP (Jeff Bowles) Distribution: na Organization: Lawrence Livermore National Laboratory Lines: 19 In article <184@thebes.Thalatta.COM> gregoire@Thalatta.COM (Keith Gregoire) writes: > >I am running Bell Tech System V/386, release 3 on a Bell Tech 386. > >I am looking for a way of capturing console error messages (notices, >warnings and panics) to a file (or at least a printer) such as >the way BSD and XENIX do with dmesg... Yes, I know this is going to three groups, but the answer is useful to people who read all three groups. Included in the Bell Tech release (and EVERY System V source release since SVR3.0) is a driver called "osm". In effect, it's a driver that provides read/write access to the circular buffer (that's by default a couple of thousand bytes) that captures kernel printf messages. Investigate your OS directories, you'll find it - add the driver to your kernel, reboot, make the nodes for it (CHARACTER-SPECIAL devices, mind you!) and then you can just cat(1) the device.... Nothing more needed. Jeff Bowles