From owner-freebsd-hackers@FreeBSD.ORG  Tue Mar  3 18:45:52 2009
Return-Path: <owner-freebsd-hackers@FreeBSD.ORG>
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 9293B106567C
	for <freebsd-hackers@freebsd.org>; Tue,  3 Mar 2009 18:45:52 +0000 (UTC)
	(envelope-from avg@icyb.net.ua)
Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140])
	by mx1.freebsd.org (Postfix) with ESMTP id C8A3B8FC1C
	for <freebsd-hackers@freebsd.org>; Tue,  3 Mar 2009 18:45:51 +0000 (UTC)
	(envelope-from avg@icyb.net.ua)
Received: from odyssey.starpoint.kiev.ua (alpha-e.starpoint.kiev.ua
	[212.40.38.101])
	by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id UAA14756;
	Tue, 03 Mar 2009 20:44:31 +0200 (EET) (envelope-from avg@icyb.net.ua)
Message-ID: <49AD7A8F.2030802@icyb.net.ua>
Date: Tue, 03 Mar 2009 20:44:31 +0200
From: Andriy Gapon <avg@icyb.net.ua>
User-Agent: Thunderbird 2.0.0.19 (X11/20090110)
MIME-Version: 1.0
To: Nate Eldredge <neldredge@math.ucsd.edu>
References: <49AD73C8.7010500@icyb.net.ua>
	<Pine.GSO.4.64.0903031029010.642@zeno.ucsd.edu>
In-Reply-To: <Pine.GSO.4.64.0903031029010.642@zeno.ucsd.edu>
X-Enigmail-Version: 0.95.7
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: freebsd-hackers@freebsd.org
Subject: Re: ln: posixly confused
X-BeenThere: freebsd-hackers@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Technical Discussions relating to FreeBSD
	<freebsd-hackers.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hackers>, 
	<mailto:freebsd-hackers-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-hackers>
List-Post: <mailto:freebsd-hackers@freebsd.org>
List-Help: <mailto:freebsd-hackers-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hackers>,
	<mailto:freebsd-hackers-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 03 Mar 2009 18:45:53 -0000

on 03/03/2009 20:32 Nate Eldredge said the following:
> On Tue, 3 Mar 2009, Andriy Gapon wrote:
> 
>>
>> Test case.
>> Preparation:
>> $ mkdir linktest
>> $ cd linktest
>> $ mkdir some_dir
>> $ mkdir other_dir
>> The test:
>> $ ln -s some_dir the_link
>> $ ln -s -f other_dir the_link
>>
>> Expected: the_link points to other_dir.
>> Actual result: some_dir contains symlink other_dir -> other_dir.
>>
>>> From ln(1):
>> SYNOPSIS
>>     ln [-s [-F]] [-f | -iw] [-hnv] source_file [target_file]
>>     ln [-s [-F]] [-f | -iw] [-hnv] source_file ... target_dir
>>
>> I thought that only true directory would trigger the second form.
>> I thought that the second argument being a symlink (to a file or to a
>> directory)
>> should trigger the first form.
>>
>> I also read this:
>> http://www.opengroup.org/onlinepubs/009695399/utilities/ln.html
>>
>> I think that the text there (and in ln(1)) implies what I expected,
>> but this is
>> not spelled out clearly.
> 
> FWIW, Linux and Solaris have the same behavior as FreeBSD.
> 
> The standard says the second form is triggered if the second argument
> "names an existing directory".  An informative note in the symlink()
> specification at
> http://www.opengroup.org/onlinepubs/009695399/functions/symlink.html
> says "a symbolic link allows a file to have multiple logical names".
> Therefore, I think it's a fair interpretation to say that a symbolic
> link to an existing directory "names" it.

Thank you for the info!

-- 
Andriy Gapon