On 25Aug2015 08:34, Paolo Galtieri wrote:
On 08/24/2015 02:19 PM, Cameron Simpson wrote:
On 24Aug2015 13:55, Paolo Galtieri wrote:
Symlinks are strings resolved with respect to the directory in which
the symlink exists.
So the example above "Test/afile" => "Test/afile2" makes a symlink
_in_
On 08/25/2015 11:52 AM, Andras Simon wrote:
I'm not sure, but maybe this is what -r is for:
-r, --relative
create symbolic links relative to link location
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedora
2015-08-24 22:55 GMT+02:00, Paolo Galtieri :
> I've tried this on 2 different systems, and on both systems ln -s fails
> in the same way.
>
> Here's the steps
>
> mkdir Test
> cd Test
> >afile
> cd ..
> ln -s Test/afile Test/afile2
> ls -l Test
>
> This is the output:
> /bin/ls: cannot access Test
On Tue, Aug 25, 2015 at 08:34:23AM -0700, Paolo Galtieri wrote:
>
> The correct way to do the link is
>
> mkdir Test2
> cd Test2
> ln -s ../Test/file file
$ ln -s afile2 afile
Shouldn't this suffice? After all they are in the same directory. With
your solution, the link will break if the di
On 08/24/2015 02:19 PM, Cameron Simpson wrote:
On 24Aug2015 13:55, Paolo Galtieri wrote:
I've tried this on 2 different systems, and on both systems ln -s
fails in the same way.
Here's the steps
mkdir Test
cd Test
afile
cd ..
ln -s Test/afile Test/afile2
ls -l Test
This is the output:
/bi
On 24Aug2015 13:55, Paolo Galtieri wrote:
I've tried this on 2 different systems, and on both systems ln -s
fails in the same way.
Here's the steps
mkdir Test
cd Test
afile
cd ..
ln -s Test/afile Test/afile2
ls -l Test
This is the output:
/bin/ls: cannot access Test/afile2: No such file or
I've tried this on 2 different systems, and on both systems ln -s fails
in the same way.
Here's the steps
mkdir Test
cd Test
>afile
cd ..
ln -s Test/afile Test/afile2
ls -l Test
This is the output:
/bin/ls: cannot access Test/afile2: No such file or directory
total 0
-rw-rw-r--. 1 pgaltieri pg
