[[!meta copyright="Copyright © 2011 Free Software Foundation, Inc."]] [[!meta license="""[[!toggle id="license" text="GFDL 1.2+"]][[!toggleable id="license" text="Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation; with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license is included in the section entitled [[GNU Free Documentation License|/fdl]]."]]"""]] [[!tag open_issue_documentation]] IRC, freenode, #hurd, 2011-10-31: is there some example of translator replying to custom ioctl's? let's say you define some ioctl (those which can be represented) using the _IOW etc macros; how would a translator (or something else) "register" and reply to them? it's not an easy thing see hurd/hurd/tioctl.defs for instance that's where the 't' ioctls end up ('t' being the group in the _IOW macro) it's not that hard either youpi: so you "roll" the ioctl to an ipc call with proper parameters? yes ah ok, i thought there was some way to hook new ioctl's, and have libc send the whole stuff at once and the proper number (with a clear name) hm for many ioctls, you don't have to change libc yes, there's a script which produces the .defs from _IOW calls, iirc or something like this there's also a hook thing in glibc, but for "sane" ioctls, that's not needed (_hurd_lookup_ioctl_handler called by ioctl()) yes, see the rules in hurd/hurd/Makefile "The following rules assist in creating an `Xioctl.defs' file to define RPCs that are sent primarily by ioctl commands." well, you can have perfectly sane ioctl()s that still can't be expressed within the constraints of the IO* macros... but admittedly that's rather uncommon (unless you consider passing of structs generally insane...) I didn't want to spend time on finding an appropriate adjective instaed of "sane" while I knew he would understand what I meant (and you did) (though maybe not actually) by "sane", I mean, which use _IOW properly i.e. with a group, proper numbers, etc. (the imposed contraints on the parameters is obviously a flaw in the hurdish ioctl design, and not insanity from structures)