public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Alexander Smirnov <asmirnov@ilbers.de>
To: Claudius Heine <claudius.heine.ext@siemens.com>,
	isar-users@googlegroups.com
Subject: Re: [URGENT][PATCH v3 0/2] Correctly determine kernel and initrd versions
Date: Wed, 18 Oct 2017 16:47:36 +0300	[thread overview]
Message-ID: <8f89e657-1496-7a12-a6ca-f8c51aad8b97@ilbers.de> (raw)
In-Reply-To: <462a48a1-571f-d25f-ebcc-c3d311605ba0@siemens.com>



On 10/18/2017 04:23 PM, Claudius Heine wrote:
> Hi,
> 
> On 10/18/2017 02:08 PM, Alexander Smirnov wrote:
>> Hi all,
>> On 10/18/2017 01:13 PM, Alexander Smirnov wrote:
>>> Hello all,
>>>
>>> IMPORTANT: lets try to review this series ASAP, becuase Isar build is
>>> broken again due to recent update of Raspbian kernel version in apt.
>>> Instead of yet-another-version update I'd like to commit proper
>>> solution.
>>>
>>> In current Isar implementation, multiconfig file contains hardcoded
>>> version for boot files: kernel and initrd. This is used for both:
>>>
>>>   - Add respective package to multistrap config.
>>>   - Copy boot files to deploy directory.
>>>
>>> This series drops this hardcoded versions, so now Isar is able to
>>> determine version of boot files during building.
>>>
>>> Changes since v2:
>>>   - Avoid races in 'deploy/images' folder creation.
>>>
>>> Changes since v1:
>>>   - Differentiate 'do_copy_boot_files' stamps.
>>>   - Update start_vm script accordingly.
>>>   - Check if symlinks 'vmlinuz' and 'initrd.img' exist before reading
>>>     them. If symlink doesn't exist, this function skips it.
>>
>> any feedback on this?
> 
> Just about Hennings readlink remark. You might want to try 'readlink -m' 
> instead of 'readlink -e'. It appears that the target of your symlink 
> didn't exist, so 'readlink -e' returns nothing.

I've tried '-m', but there is another problem:

1. If symlink references absolute path, then readlink returns this 
absolute path, i.e.:

$ ln -s /boot/abc l1
$ readlink -m l1
/boot/abc/

2. If symlink references relative path, so the absolute path is added:

$ ln -s boot/abc l2
$ readlink -m l2
/home/asmirnov/Work/isar/isar/boot/abc/


So then I propose to use basename and concatenate absolute path like:

KERNEL_IMAGE=$(basename $(readlink -m ...))
cp ${IMAGE_ROOTFS}/boot/$KERNEL_IMAGE ...

Alex

> 
> Cheers,
> Claudius
> 

-- 
With best regards,
Alexander Smirnov

ilbers GmbH
Baierbrunner Str. 28c
D-81379 Munich
+49 (89) 122 67 24-0
http://ilbers.de/
Commercial register Munich, HRB 214197
General manager: Baurzhan Ismagulov

  reply	other threads:[~2017-10-18 13:47 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-18 10:13 Alexander Smirnov
2017-10-18 10:13 ` [[URGENT][PATCH v3 1/2] meta-isar: Drop hardcoded kernel versions Alexander Smirnov
2017-10-18 10:13 ` [[URGENT][PATCH v3 2/2] meta-isar: Rework boot files copying Alexander Smirnov
2017-10-18 12:08 ` [URGENT][PATCH v3 0/2] Correctly determine kernel and initrd versions Alexander Smirnov
2017-10-18 13:23   ` Claudius Heine
2017-10-18 13:47     ` Alexander Smirnov [this message]
2017-10-18 17:15       ` Alexander Smirnov

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=8f89e657-1496-7a12-a6ca-f8c51aad8b97@ilbers.de \
    --to=asmirnov@ilbers.de \
    --cc=claudius.heine.ext@siemens.com \
    --cc=isar-users@googlegroups.com \
    /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