Messages in this thread |  | | Subject | Re: Adding checkpointing API to Linux kernel | | Date | Fri, 22 Jan 1999 17:54:43 -0500 | | From | "Brandon S. Allbery KF8NH" <> |
| |
In message <199901221512.JAA11852@duracef.shout.net>, Michael Elizabeth Chastai n writes: +----- | > PS: How many things would break if we forced ioctls to _always_ pass | > | > struct foo { | > int len; | > char data[len]; | > } ? | | Everything would break. Remember that lots of programs use terminal | control ioctls. | | So far I've seen two design ideas. One is an new 'nioctl' system call | which takes 'len' as a fourth parameter. The other is to add | 'ioctl_register' and 'ioctl_unregister' to the kernel, so that the | kernel knows this information and can export it, even though the | information is not present in the API. +--->8
Why am I having sudden memories of ioctl(s, I_STR)?
-- brandon s. allbery [os/2][linux][solaris][japh] allbery@kf8nh.apk.net system administrator [WAY too many hats] allbery@ece.cmu.edu carnegie mellon / electrical and computer engineering KF8NH We are Linux. Resistance is an indication that you missed the point.
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
|  |