On Wed, 23 Jun 2004, Ronan Heffernan wrote:
> Eben King wrote:
>
> >>Actually, no. If I write a C program that calls:
> >>fopen("baz/myfile.txt","r"); then the symlink is followed automatically
> >>(the file foo/bar/myfile.txt is opened). I do not have to resolve the
> >>link target or anything like that. The hierarchy may not be identical,
> >>but as a container for files, the dereferencing is automatic.
> >I believe the point was that if the app does nothing special, then a user
> >who "cd baz"es from bar/ then "cd .."s will not end up back in bar.
> >Hence, links aren't truly _transparent_ without extra work by the
> >programmers.
> On my linux box, I do indeed end up back in 'bar' (RedHat 6.2):
> Whether or not the programmers have to do anything special to expose the
> hierarchy (and let's face it, there are two different hierarchies here),
> the programmers do not have to do anything special to access the files
> and subdirectories under a symlink!
True. But to make it transparent (including use of "..") they do.
-- -eben ebQenW1@EtaRmpTabYayU.rIr.OcoPm home.tampabay.rr.com/hactar VIRGO: All Virgos are extremely friendly and intelligent - except for you. Expect a big surprise today when you wind up with your head impaled upon a stick. -- Weird Al, _Your Horoscope for Today_----------------------------------------------------------------------- This list is provided as an unmoderated internet service by Networked Knowledge Systems (NKS). Views and opinions expressed in messages posted are those of the author and do not necessarily reflect the official policy or position of NKS or any of its employees.
This archive was generated by hypermail 2.1.3 : Fri Aug 01 2014 - 18:12:01 EDT