> I'm not sure I'm clear on what the problem is... readlink() is only
> being used to get the _text_ of the symlink's "value", not to actually
> follow it. This is what readlink is _supposed_ to do, right? (At
> least, that's what is does in ext2 and nfs.) And it's only used when
For most filesystems, that's correct. However, there are exceptions,
such as the symlinks in /proc/*/fd. (My understanding is that those
now use the dcache to point to "real" paths when possible, but that
still isn't possible with, say, pipes, TCP/IP sockets, or linkless
files.)
-- Aaron M. Ucko, KB1CJC <amu@mit.edu> (finger amu@monk.mit.edu)- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu