Messages in this thread | | | Date | Sat, 16 Jan 1999 17:55:25 -0500 (EST) | From | Alexander Viro <> | Subject | Re: [RFC] What should we do with FAT inode numbers? |
| |
On Sat, 16 Jan 1999, Colin Plumb wrote:
> Well, the usual Unix guarantee is that for the lifetime of a single file, > (device,inode) uniquely identifies it.
Not true for AFS.
> For example, Nethack save files store the inode number so they can't be > (easily) copied. Qmail uses the inode number to generate unique filenames. > Various backup and archive utilities use (device,inode) comparisons to > detect hard links.
[snip] > Frankly, it's a hard problem. In VFAT, don't directory entries get > shuffled when they're renamed, in case the new long name requires more > slots to store than are available at the old location?
In Linux implementation - always.
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
| |