You are not logged in.
Pages: 1
I don't have a /dev/inotify node when using 2.6.13-1 from testing. Can somebody help me there? I can see from the config file that inotify is enabled in the kernel build.
Offline
inotify is not part of the vanilla kernel. You need to apply the inotify patch. You can do this on its own, or by using a patchset that includes inotify. Offhand, I don't know which patchsets have it - cko used to but it's now dead, archck does not, but you could always try asking iphitus nicely.
Offline
As of 2.6.13 this is no longer true - it was merged into the standard kernel.
Offline
True - what a dumb post that was!
<Note to self - check FACTS before posting>
Anyway, in an attempt to recover a shred of dignity here, I have installed the same kernel 2.6.13 from testing, and also 2.6.13-archck1 from community. Both have inotify enabled, but both also fail to create /dev/inotify. inotify works fine with my own custom 2.6.12-cko2 build.
I think I'll roll my own 2.6.13 and see how that goes - not that I would expect that to make a particular difference, just that I'm used to doing my own kernels. By the time that's done, hopefully someone who knows what they're talking about will join in.
Offline
inotify no longer uses a device node interface, but uses syscalls... so there won't be a /dev/inotify device. Programs using inotify need to be updated to the new interface (gamin was updated almost immediately).
Offline
Pages: 1