Date: Wed, 3 Jan 2001 23:20:18 -0800 From: "Crist J. Clark" <cjclark@reflexnet.net> To: groggy@iname.com Cc: freebsd-questions <questions@FreeBSD.ORG> Subject: Re: ln bug? Message-ID: <20010103232017.G95729@rfx-64-6-211-149.users.reflexco> In-Reply-To: <200101032338.XAA07211@groggy.anc.acsalaska.net>; from groggy@iname.com on Wed, Jan 03, 2001 at 11:38:39PM %2B0000 References: <200101032338.XAA07211@groggy.anc.acsalaska.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Jan 03, 2001 at 11:38:39PM +0000, groggy@iname.com wrote: > is this a bug in "ln"? > > if i am in a directory with a file xxx: > > ln -s xxx /tmp/xxx > > will create link /tmp/xxx, but it will point to itself in /tmp. > ln is not pointing the link to to xxx in the current directory > as specified/intended on the command line. doesn't seem right. No, that's right. When making symbolic links, the first argument is the _string_ that the link points to. It is better to not think of symbolic links pointing to a specific file. Rather, when a symbolic link is processed as part of a path, the string value of the link is substituted. -- Crist J. Clark cjclark@alum.mit.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010103232017.G95729>