[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Wrong behavior of ``readlink -f''?

From: Thomas Schwinge
Subject: Wrong behavior of ``readlink -f''?
Date: Wed, 13 Feb 2008 02:03:51 +0100
User-agent: Mutt/1.5.11


I'm a bit stumped with this behavior of ``readlink -f'', as it doesn't
match what I had expected.

address@hidden:~/tmp $ mkdir a-long
address@hidden:~/tmp $ touch a-long/f
address@hidden:~/tmp $ ln -s a-long a
address@hidden:~/tmp $ readlink -f a/f
address@hidden:~/tmp $ readlink -f a-long/../a/f
address@hidden:~/tmp $ readlink -f a/../a-long/f
address@hidden:~/tmp $ readlink -f a/../a/f
address@hidden:~/tmp $ echo $?

Why doesn't it resolve the latter case just as the previous ones?
Because there are two symbolic links involved?  Or two times the same
one?  Strange.

address@hidden:~/tmp $ readlink --version | head -n 2
readlink (GNU coreutils) 5.97
Copyright (C) 2006 Free Software Foundation, Inc.
address@hidden:~/tmp $ apt-cache policy coreutils | grep Installed
  Installed: 5.97-5.3ubuntu3

I even decided to give the git master branch an try, but:
``configure.ac:35: require Automake 1.10.1, but have 1.10''.  There I
decided to stop and not begin upgrading my whole toolchain.


Attachment: signature.asc
Description: Digital signature

reply via email to

[Prev in Thread] Current Thread [Next in Thread]