4 ms·
They have come up with plenty more ways to talk to the kernel. Just look at the absolute abortion that is "netlink". Very deeply nested structures with self-re
by revelation 9y ago
They have come up with plenty more ways to talk to the kernel.
Just look at the absolute abortion that is "netlink". Very deeply nested structures with self-referencing pointers and sizeofs everywhere. You are looking at 300 LoC for the most trivial operations unless you want to use a shitty (like extfs tools shitty) library.
I actually prefer the ioctl, it keeps the insanity in check of these structure astronauts that gave us netlink.
- simplicio 9y agoYea, I think ioctl is probably the most elegant solution. The fact that hardware has a wide-variation in properties, requests, etc. mean some part of the interface is going to be inelegant and case dependent. ioctl at least puts all that variation behind a single system call.