Date: Mon, 16 Mar 2009 12:06:17 -0400 From: John Almberg <jalmberg@identry.com> To: John Almberg <jalmberg@identry.com> Cc: freebsd-questions@freebsd.org Subject: Re: links vs real directories Message-ID: <281DCAD1-CA1B-4D07-9A9B-DCA4C2F41A7F@identry.com> In-Reply-To: <33BEAB1A-A0AB-4684-95EE-8C2C4328ABA7@identry.com> References: <AA5A8761-794A-427B-9E9F-2872BD746038@identry.com> <20090316153923.GA13043@owl.midgard.homeip.net> <33BEAB1A-A0AB-4684-95EE-8C2C4328ABA7@identry.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mar 16, 2009, at 11:47 AM, John Almberg wrote: > > On Mar 16, 2009, at 11:39 AM, Erik Trulsson wrote: > >> On Mon, Mar 16, 2009 at 11:22:13AM -0400, John Almberg wrote: >>> I always thought that links to real directories were pretty much the >>> same as real directories, but I've just discovered a situation where >>> they are not and I'm wondering if I'm doing something wrong... >> >> A *soft* link to a directory entry (be it a directory or a file or >> something >> else) is not quite equivalent to the original entry since they are >> easily >> distinguished and some programs do treat softlinks differently >> from other >> targets. > > I can see that, now... If I create a soft link to ~/shared/config, > and then cd into the directory, when I type 'ls ..', I get the > listing for ~/shared, not ~/app. > > Bummer... > > I've just dug through man ln, and don't see any obvious solution. > Since this must be a problem for anyone who wants to do something > like this, I guess I am taking the wrong approach, altogether. > > Will have to re-think this.... > > <smell of burning rubber commences...> Okay! I guess I wasn't the first to have this problem... lndir (in ports) solves the problem by creating a set of soft links for all the files in the 'linked' directory. Kinda kludgy, but it works. -- John
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?281DCAD1-CA1B-4D07-9A9B-DCA4C2F41A7F>