On Thu, 29 Sep 2005, Yedidyah Bar-David wrote: > On Thu, Sep 29, 2005 at 04:37:32AM +0300, guy keren wrote: > > > just to make you happy, i went into the source tree, under > > Documentation/dnotify.txt. the text sais you can learn about various types > > of changes, that are NOT related to file opening/closing, but rather to > > changes done to the file or its inode. > > Well, I am happy, thanks. > As I already said, dnotify was indeed quite limited and that's why > inotify was created. I just checked and it was merged at 2.6.13, so > hopefully it will soon be integrated into distributions.
hopefully, not too fast - you should remember that there is no 2.7 kernel series any more - all the development is now done in the normal 2.6 kernel series, and they assume the distributions will do the stabilization work. as a result, there are quite massive changes in the newer 2.6 kernel releases. thus, distributions tend to update slower now (i'm not talking about 'cutting-user-fingers-edge distributions' - i'm talking about those that try to be somewhat stable). this is just a reminder to y'all, to be more catious then before about whether to upgrade your non-experimental machine(s) to the latest "stable" 2.6 kernel. does someone know if the 'unstable work' on the 2.6 tree was official started? i do know that some non-trivial changes were made in recent versions (e.g. in 2.6.12, the SCSI sub-system supports plug-and-play - this means that SCSI disks would disappear right under your nose if your fiber-channel's HBA got disconnected from the network for a short while). -- guy "For world domination - press 1, or dial 0, and please hold, for the creator." -- nob o. dy ================================================================= To unsubscribe, send mail to [EMAIL PROTECTED] with the word "unsubscribe" in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
