All of lore.kernel.org
 help / color / mirror / Atom feed
From: <kerim.cagri.akbaba@accenture.com>
To: <yocto@yoctoproject.org>
Subject: Symlink Problem with Kernel-Image in Rootfs
Date: Mon, 8 May 2017 07:10:03 +0000	[thread overview]
Message-ID: <8e9ed5eb75ff4a4790b59bcd1f310724@BN1PR42MB081.048d.mgd.msft.net> (raw)

[-- Attachment #1: Type: text/plain, Size: 1403 bytes --]

Hi All,

Using IMAGE_INSTALL += "kernel-image-zimage" or IMAGE_INSTALL += "kernel-image" inside my image recipe, I am putting the kernel inside of the rootfs (/boot/zImage-4.4.52).

However, the symlink that is created by default, points to whole path instead of relative path (It used to point relative path). The problem is after bootloader mounts my rootfs partition, it loooks for kernel (zImage) and gives error because there is no "/boot" path.

$ ls /boot
zImage -> /boot/zImage-4.4.52  (what I want is zImage-> zImage-4.4.52)
zImage-4.4.52

How can I modify the symlink creation; Which class,script or recipe is responsible for creation of this symlink ?

Thanks & BR
Kerim


________________________________

This message is for the designated recipient only and may contain privileged, proprietary, or otherwise confidential information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the e-mail by you is prohibited. Where allowed by local law, electronic communications with Accenture and its affiliates, including e-mail and instant messaging (including content), may be scanned by our systems for the purposes of information security and assessment of internal compliance with Accenture policy.
______________________________________________________________________________________

www.accenture.com

[-- Attachment #2: Type: text/html, Size: 3776 bytes --]

                 reply	other threads:[~2017-05-08 10:45 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=8e9ed5eb75ff4a4790b59bcd1f310724@BN1PR42MB081.048d.mgd.msft.net \
    --to=kerim.cagri.akbaba@accenture.com \
    --cc=yocto@yoctoproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.