Path: utzoo!utgpu!jarvis.csri.toronto.edu!clyde.concordia.ca!uunet!mcsun!hp4nl!ctisbv!pim
From: pim@cti-software.nl (Pim Zandbergen)
Newsgroups: comp.unix.i386
Subject: /dev/osm (was: Re: Logging console messages to a printer.)
Message-ID: <1665@ctisbv.cti-software.nl>
Date: 5 Jan 90 12:41:46 GMT
References: <1016@rsiatl.UUCP> <399@zok.UUCP>
Organization: CTI Software BV, The Hague, the Netherlands
Lines: 23

mark@zok.UUCP (Mark W. Snitily) writes:

>   Device "osm" stands for "operating system messages".  You have to have
>the driver built into the kernel.  In kconfig this is selected under
>the  "ADD FACILITY" item.  The facility you want to add is "Operating
>System Messages".  (If you already have added it, it won't show up under
>ADD FACILITY but will be listed under REMOVE FACILITY.)

I have rebuilt the kernel (ISC 2.0.1) with osm installed
but no /dev/osm is created.
Apparently there is no /etc/conf/node.d/osm file.

Can anybody help me with major and minor numbers ?

On our AT&T 3B2 running SYS V R 3.2.1 there's a utility
called 'errint' for reading /dev/osm. 
Is this supposed to be standard in SYS V R 3.2?
I can't find it in ISC 386/ix.
-- 
Pim Zandbergen                           domain : pim@cti-software.nl
CTI Software BV                          uucp   : uunet!mcsun!hp4nl!ctisbv!pim
Laan Copes van Cattenburch 70            phone  : +31 70 3542302
2585 GD The Hague, The Netherlands       fax    : +31 70 3512837