Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!bloom-beacon!gatech!galbp!bing
From: bing@galbp.LBP.HARRIS.COM (Bing Bang)
Newsgroups: comp.os.minix
Subject: tty signals
Message-ID: <1836@galbp.LBP.HARRIS.COM>
Date: Tue, 13-Oct-87 10:21:38 EDT
Article-I.D.: galbp.1836
Posted: Tue Oct 13 10:21:38 1987
Date-Received: Thu, 15-Oct-87 01:48:56 EDT
Reply-To: bing@galbp.UUCP (Bing Bang)
Organization: Harris/Lanier, Atlanta, GA
Lines: 13

when the tty task has to send a signal (SIGINT, SIGQUIT, SIGHUP...), deciding
which process to send the signal to is a real bad kludge. this is caused by
the fact that the kernel does not know which process owns the tty.

i think the easiest way to fix this is to make the tty task send fs a message
telling him what signal and what tty, and let fs (who keeps track of tty owner-
ship) make the KSIG call to mm.

any ideas?
-- 
Bing H. Bang           +----------------------------------------------------+
Harris/Lanier          |MSDOS and OS/2 (whenever it gets here): just say no.|
Atlanta GA             +----------------------------------------------------+