On 2/23/06, Bahadir Balban <bilgehan.balban@xxxxxxxxx> wrote: > Hi, > > As you know the ioctl() call is notoriously overused in all sorts of > driver classes. It's a single call that does so many different things. > If you were to replace it, what would you come up with as a solution? > Would it be tedious to introduce new system calls for each class, to > manipulate network devices, or character devices separately? Or maybe > new calls per ioctl() purpose, rather than per class? What would be > the best division? > Like it or not, ioctl's are part of the kernel<->userspace ABI, you can't replace them without breaking userspace and that's a big no no. Best you can do is introduce saner alternatives, for better or worse ioctl's are here to stay. -- Jesper Juhl <jesper.juhl@xxxxxxxxx> Don't top-post http://www.catb.org/~esr/jargon/html/T/top-post.html Plain text mails only, please http://www.expita.com/nomime.html -- Kernelnewbies: Help each other learn about the Linux kernel. Archive: http://mail.nl.linux.org/kernelnewbies/ FAQ: http://kernelnewbies.org/faq/
