Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!sol.ctr.columbia.edu!ira.uka.de!fauern!tumuc!lan!roell
From: roell@lan.informatik.tu-muenchen.dbp.de (Thomas Roell)
Newsgroups: comp.unix.i386
Subject: Console & Mouse Problems
Message-ID: <1833@tuminfo1.lan.informatik.tu-muenchen.dbp.de>
Date: 11 Apr 90 09:10:22 GMT
Sender: news@lan.informatik.tu-muenchen.dbp.de
Distribution: comp
Organization: Inst. fuer Informatik, Technische Univ. Muenchen, West Germany
Lines: 29

It may bee asked yet, but anyway..

I've build a graphics application, and the Problem ist that every time the
kernel sends a message (ex. FD(0): NO SPACE,... etc.) to the console my
graphics are destroyed. How can I prevent the kernel form sending messages
direct to the console? 

Does it perhaps linking /dev/console to /dev/null ? (not the good way) Or
is there a simple way. 


Next Question:

My Doc states that there is a special memory-mapped keyboard mode (especially
for X-Windows). Has anybody out there used it allready ? If so, please send me
some example code. Can I use this mode for a seriell driven mouse too ? Or is
there another way to get a signal from the kernal whenever a mouse-event 
arrives (currently I'm using poll(2) and nonblocking reads, but thats too 
slow!).

- Thomas

--
_______________________________________________________________________________
Thomas Roell             Inst. f. Informatik / Technische Universitaet M"unchen
                         Arcisstr. 21 / 8000 Munich 2 / Fed.Rep. of Germany
E-Mail (domain):	 roell@lan.informatik.tu-muenchen.dbp.de
UUCP (when above fails): roell@tumult.{uucp | informatik.tu-muenchen.de}
-------------------------------------------------------------------------------