Re: FIO* doc added to tty.4 (review)
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 documentation to the ioctl along with a comment saying to look at the individual driver man pages for information specific to the driver. ie: FIONREAD will succeed from a backgrounded process, but the data read itself with hang (tty driver). Thanks, John ps: Is cross-referencing #define values frowned upon? It would be nice if "man -k FIONREAD" (for instance) would return useful results. - Garrett Wollman's Original Message - On Sun, 15 Apr 2001 22:26:37 -0700, "John W. De Boskey" [EMAIL PROTECTED] 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, they are generic file ioctls and not specific to the teletype driver. They should be described in the ioctl(2) manual page. -GAWollman To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: FIO* doc added to tty.4 (review)
On Wed, 18 Apr 2001 06:40:38 +1000 (EST), Bruce Evans [EMAIL PROTECTED] 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 reading when a call to an input function with O_NONBLOCK clear would not block, whether or not the function would transfer data successfully. (The function might return data, an end-of-file indication, or an error other than one indicating that it is blocked, and in each of these cases the descriptor shall be considered ready for reading.) The socket semantic requirements come from 1003.1g-2000; this paragraph looks to have come from XSH4.2 (SUSv1). -GAWollman To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
FIO* doc added to tty.4 (review)
Hi, 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: http://people.freebsd.org/~jwd/doc/tty.4.html http://people.freebsd.org/~jwd/doc/tty.4.diff Any comments are welcome. Thanks, John To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
