| |||||||||||||
Watching filesystem events with inotifyWatching filesystem events with inotifyPosted Sep 30, 2004 9:36 UTC (Thu) by rjw (guest, #10415)Parent article: Watching filesystem events with inotify
I remember long ago reading ( I believe on these very pages) that ioctl() was considered a bit skanky, and really people should be making devices that just need read() & write().
And if one of them has another meaning already, a separate control device should be created.
That way echo & friends can be used to test/use all this functionality...
What happened to this idea?
(Log in to post comments)
Watching filesystem events with inotify Posted Sep 30, 2004 13:27 UTC (Thu) by elanthis (guest, #6227) [Link] The ioctl is simply easier to code and use, so it was used.
The inotify developer is quite willing to switch to a write() based interface, if Linus/Andrew decide it's necessary.
Watching filesystem events with inotify Posted Sep 30, 2004 14:18 UTC (Thu) by rjw (guest, #10415) [Link] I wasn't really asking about this specific case.I was just wondering if this principle was still current... it seems like new ioctl() calls are coming thick and fast.
Watching filesystem events with inotify Posted Sep 30, 2004 20:10 UTC (Thu) by elanthis (guest, #6227) [Link] ioctls are still frowned upon, yes. they just happen to have their uses.
|
|||||||||||||