Date: Tue, 6 Sep 2005 20:59:46 +0530 From: "Kamal R. Prasad" <kamalpr@gmail.com> To: =?ISO-8859-1?Q?Dag-Erling_Sm=F8rgrav?= <des@des.no> Cc: freebsd-hackers@freebsd.org, Robert Watson <rwatson@freebsd.org>, Sergey Uvarov <uvarovsl@mail.pnpi.spb.ru> Subject: Re: vn_fullpath() again Message-ID: <ac7deb5050906082961c84a44@mail.gmail.com> In-Reply-To: <868xyack37.fsf@xps.des.no> References: <E1ECemU-0004dI-00.shmukler-mail-ru@f26.mail.ru> <868xyack37.fsf@xps.des.no>
next in thread | previous in thread | raw e-mail | index | archive | help
>=20 > [snip] =20 I did. You just don't get it. A file may be associated with zero, > one or more names and none of these names are more correct or > authoritative than any of the others. If a user does 'ln /bin/ls > /tmp' (assuming /bin and /tmp are on the same filesystem), it may be > obvious to you that /bin/ls is the "real name" is /tmp/ls is just an > alias, but it is not obvious to the kernel. In fact, the kernel is > unable to see any difference at all between these two names. Yes -but when a user requests a mapping of vnode to pathname, he is asking= =20 in the context of files he has accessed (recently). In this context, the=20 name cache does suffice -but unfortunately not every unix variant provides= =20 access to it. regards -kamal
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?ac7deb5050906082961c84a44>