Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/5/84; site umd5.UUCP
Path: utzoo!linus!philabs!cmcl2!seismo!umcp-cs!cvl!umd5!louie
From: louie@umd5.UUCP
Newsgroups: net.bugs.2bsd
Subject: 2.9BSD console select() problem
Message-ID: <480@umd5.UUCP>
Date: Mon, 29-Apr-85 18:16:10 EDT
Article-I.D.: umd5.480
Posted: Mon Apr 29 18:16:10 1985
Date-Received: Tue, 30-Apr-85 04:56:51 EDT
Reply-To: louie@umd5.UUCP (Louis Mamakos)
Organization: U of Md, CSC, College Park, Md
Lines: 35
Keywords: select console

I noticed a few days ago that the user telnet program acted "weird" when
it was run from the console; terminals on the dh worked just fine.  Upon
closer examination of the kl driver, I noticed that logic to support the
select() system call was missing.  It's a simple 5 line fix to the device
driver.  A diff -c follows (kl.c~ is the older one).

*** kl.c~	Fri Aug  5 19:05:24 1983
--- kl.c	Mon Apr 22 11:05:48 1985
***************
*** 113,118
  		else
  #endif
  			wakeup((caddr_t) &tp->t_outq);
  }
  
  klrint(dev)

--- 113,125 -----
  		else
  #endif
  			wakeup((caddr_t) &tp->t_outq);
+ #ifdef	UCB_NET
+ 	if (tp->t_wsel) {
+ 		selwakeup(tp->t_wsel, tp->t_state & TS_WCOLL);
+ 		tp->t_wsel = 0;
+ 		tp->t_state &= ~TS_WCOLL;
+ 	}
+ #endif	UCB_NET
  }
  
  klrint(dev)
-- 
Louis A. Mamakos WA3YMH   University of Maryland, Computer Science Center
 Internet: louie@umd5.arpa
 UUCP: {seismo!umcp-cs, ihnp4!rlgvax}!cvl!umd5!louie