LWN.net Logo

why not a syscall

why not a syscall

Posted Oct 7, 2004 20:10 UTC (Thu) by huaz (guest, #10168)
Parent article: Watching filesystem events with inotify

Seems a syscall is more appropriate than a special device interface.


(Log in to post comments)

why not a syscall

Posted Dec 2, 2004 14:43 UTC (Thu) by fursten (guest, #26401) [Link]

My first reaction was "Why not add pioctl and use that?". For those who don't know pioctl: it's a syscall used by AFS and a couple of other remote fs implmementations. It's essentially ioctl on paths instead of file descriptors. This means that you get rid of the dnotify problems with the need of having the watched file open.

I have on the other hand not studied this in any depth...

Copyright © 2013, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds