![]() | |||||||||||||
Messages in this thread |
Joerg Schilling wrote: > "Christopher Friesen" <cfriesen@nortel.com> wrote: >>There's nothing there that says the mapping cannot change with >>time...just that it has to be unique. > > > If it changes over the runtime of a program, it is not unique from the > view of that program. That depends on what "uniquely identified" actually means. One possible definition is that at any time, a particular path maps to a single unique st_ino/st_dev tuple. The other possibility (and this is what you seem to be advocating) is that a st_ino/st_dev tuple always maps to the same file over the entire runtime of the system. This second possibility seems easily disproved. If you delete and recreate files on a filesystem (assuming nobody has open files in the filesystem), at some point a new file will end up with the same inode as an old (deleted) file. The two files are different, but have the same st_ino/st_dev tuple. This leaves the first possibility as the only choice... Chris - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ | ||||||||||||
| Last update: 2006-02-10 15:17 [from the cache] ©2003-2008 | |||||||||||||