Re: FIO* doc added to tty.4 (review)

2001-04-17 Thread Garrett Wollman
< said: > Does POSIX now specify select() and/or poll() precisely enough to > show that the current behaviour is wrong? In addition to more explicit requirements for sockets, draft 6 has the following to say about select() and pselect(): A descriptor shall be considered ready for readin

Re: FIO* doc added to tty.4 (review)

2001-04-17 Thread Bruce Evans
On Tue, 17 Apr 2001, Garrett Wollman wrote: > < said: > > > ie: FIONREAD will succeed from a backgrounded process, but the > > data read itself with hang (tty driver). > > You are describing a general property of the terminal subsystem, which > any process dealing with terminals needs to be

Re: FIO* doc added to tty.4 (review)

2001-04-17 Thread Garrett Wollman
< said: > ie: FIONREAD will succeed from a backgrounded process, but the > data read itself with hang (tty driver). You are describing a general property of the terminal subsystem, which any process dealing with terminals needs to be aware of. (AFAIK, ioctl(tty, FIONREAD, &n) should set n t

Re: FIO* doc added to tty.4 (review)

2001-04-17 Thread Bruce Evans
On Mon, 16 Apr 2001, Garrett Wollman wrote: > < said: > > >I've been doing some tty related work and found the FIO* > > requests don't seem to be documented. > > >I've added some reasonable doc to tty.4 and put up the > > the diff and html forms: > > As the initial letter suggests, the

Re: FIO* doc added to tty.4 (review)

2001-04-17 Thread John W. De Boskey
Hi, I wondered about this. However, after looking around what I found was that the FIO* requests seemed to be documented in driver pages (and only a handful at that), and not documented with ioctl. Since I don't want to change the other existing driver man pages, what if I add generic docu