Path: utzoo!attcan!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!samsung!uunet!virtech!cpcahil
From: cpcahil@virtech.uucp (Conor P. Cahill)
Newsgroups: comp.unix.i386
Subject: Re: X11R4 for i386 Unix
Message-ID: <1990Jun30.142109.23496@virtech.uucp>
Date: 30 Jun 90 14:21:09 GMT
References: <1990Jun22.211741.979@uicbert.eecs.uic.edu> <1990Jun23.015312.9456@virtech.uucp> <1990Jun25.134223.20131@virtech.uucp> <1990Jun28.125600.24155@brian386.uucp>
Reply-To: cpcahil@virtech.UUCP (Conor P. Cahill)
Distribution: comp
Organization: Virtual Technologies Inc., Sterling VA
Lines: 30

In article <1990Jun28.125600.24155@brian386.uucp> news@brian386.uucp (News Administrator) writes:
>
>>Obviously I don't know it all.  Reportedly both SCO Xenix and SCO Unix
>>have this capability.  I just wish I had it on my system (how about it
>>Interactive?  When can we expect such a feature?).
>
>How about this idea??
>/etc/rc.d/errlogger
>	(stty 1200; cat "/dev/osm" > /dev/tty01) < /dev/tty01 &
>
>This seems to work pretty well and will run as long as your system does.  Plus
>you get a copy of all the start up messages (free mem, etc, what a DEAL ;-).
>Of course you need to have Operating System Messages configured in your
>kernel for this to work.

This only partially solves the problems.  Only messages to the console from
the kernel are available.  Application program messages (like cron, acct, or
other vendor-specific daemons) that are sent to /dev/console do not get 
added to /dev/osm.

The true serial console also removes the requirement for a display card
and monitor for the system and allows the system to be remotely configured,
rebooted, etc.



-- 
Conor P. Cahill            (703)430-9247        Virtual Technologies, Inc.,
uunet!virtech!cpcahil                           46030 Manekin Plaza, Suite 160
                                                Sterling, VA 22170