Date: Wed, 24 May 2006 11:47:02 +1000 From: Sam Lawrance <boris@brooknet.com.au> To: gs_stoller@juno.com, freebsd-hackers@freebsd.org Subject: Re: The 'ln -s' command Message-ID: <3E55A43D-7017-4897-9D10-758F8F393404@brooknet.com.au> In-Reply-To: <61DC5A82-3742-4FB0-9B7E-9655F4E4FC60@brooknet.com.au> References: <20060523.182218.19235.1026225@webmail29.nyc.untd.com> <61DC5A82-3742-4FB0-9B7E-9655F4E4FC60@brooknet.com.au>
next in thread | previous in thread | raw e-mail | index | archive | help
On 24/05/2006, at 11:42 AM, Sam Lawrance wrote: > > On 24/05/2006, at 1:21 AM, gs_stoller@juno.com wrote: > >> I tried the 'ln -s' command in bothe 4.3 & 4.7 in a situation >> where it should fail and it did, but it still had a return/exit >> code of 0 , I think it should have been nonzero. I tried 'ln -s >> a b' where the file b existed (and was a directory) and I >> wanted to create the file named a also pointing to it. The >> correct form was 'ln -s b a'. > > See the synopsis in the manpage for 'ln'. It exited nonzero > because you successfully put a symlink under the directory 'b', > pointing to 'a'. > > oddie:~ sam$ mkdir b > oddie:~ sam$ ln -s a b > oddie:~ sam$ ls -l b > total 8 > lrwxr-xr-x 1 sam sam 1 May 24 11:42 a -> a Oops, I meant: "it exited with zero status because ..."
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3E55A43D-7017-4897-9D10-758F8F393404>