mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Sascha Hauer <s.hauer@pengutronix.de>
To: Ian Abbott <abbotti@mev.co.uk>
Cc: Barebox List <barebox@lists.infradead.org>
Subject: Re: [BUG v2017.07.0] readlink -f command broken?
Date: Sat, 1 Jul 2017 23:50:15 +0200	[thread overview]
Message-ID: <20170701215015.2rlkcde2mdsgr3yl@pengutronix.de> (raw)
In-Reply-To: <54f52983-da4d-35a6-e0ed-edfe286f61c5@mev.co.uk>

Hi Ian,

On Fri, Jun 30, 2017 at 02:28:49PM +0100, Ian Abbott wrote:
> Hi folks,
> 
> I know there were changes to do with links to directories in v2017.07.0, but
> this looks like a bug in readlink with the -f option:
> 
> barebox@fred:/ ls -l /mnt/root
> lrwxrwxrwx              7 bin -> usr/bin
> drwxr-xr-x            304 boot
> drwxr-xr-x            160 dev
> drwxr-xr-x           1920 etc
> drwxrwsr-x            160 home
> lrwxrwxrwx              7 lib -> usr/lib
> drwxr-xr-x            160 mnt
> dr-xr-xr-x            160 proc
> drwx------            160 root
> drwxr-xr-x            160 run
> lrwxrwxrwx              8 sbin -> usr/sbin
> drwxr-xr-x            224 srv
> drwxr-xr-x            160 sys
> drwxrwxrwt            160 tmp
> drwxr-xr-x            480 usr
> drwxr-xr-x            544 var
> barebox@fred:/ readlink -f /mnt/root/lib libdir
> barebox@fred:/ echo $libdir
> /usr
> 
> (I expected $libdir to contain "/mnt/root/usr/lib" here, as it did in
> barebox v2017.06.1.)
> 
> (Let's try it without the -f option....)
> 
> barebox@fred:/ readlink /mnt/root/lib libdir2
> barebox@fred:/ echo $libdir2
> usr/lib
> 
> (That is the same as barebox v2017.06.1.)

I can confirm this. It's the same here. So far I was not able to find a
solution. I think readlink for directories must have been broken before
the directory link support though, since links to directories were not
supported. It may have worked in this simple case, but if multiple
levels of links were involved I don't think it could have been working
before.

Sascha

-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

      parent reply	other threads:[~2017-07-01 21:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-30 13:28 Ian Abbott
2017-06-30 17:37 ` Jean-Christophe PLAGNIOL-VILLARD
2017-07-01 21:50 ` Sascha Hauer [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20170701215015.2rlkcde2mdsgr3yl@pengutronix.de \
    --to=s.hauer@pengutronix.de \
    --cc=abbotti@mev.co.uk \
    --cc=barebox@lists.infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox