From: "Xu, Yanfei" <yanfei.xu@windriver.com>
To: Bruce Ashfield <bruce.ashfield@gmail.com>
Cc: He Zhe <zhe.he@windriver.com>, openembedded-core@lists.openembedded.org
Subject: [OE-core] kernel: update rpm failed for the vfat
Date: Tue, 9 Jun 2020 18:32:34 +0800 [thread overview]
Message-ID: <d384f6b7-dff7-ab38-7abc-348727f67d40@windriver.com> (raw)
Hi Bruce,
I encountered an issue that updating kernel rpm package will fail when
the /boot dir was mount with vfat filesystem. The root cause is vfat
don't support symlink.
--------cut here----------
error: unpacking of archive failed on file /boot/Image;5eda8385: cpio:
symlink failed - Resource temporarily unavailable
error:
kernel-image-image-5.4.43-yocto-standard-5.4.x+git0+f8c88c4331_9961cc8b79-r0.bcm_2xxx_rpi4:
install failed
root@bcm-2xxx-rpi4:/boot#
Currently I have two ideas to fix it:
1. we use 'install' cmd instead of 'ln -sf' in kernel_do_install to
avoid generating symlink in kernel-image-image*.rpm. And then add an
postinstall to this rpm. It will check if the /boot dir is vfat, if not,
we remove the copy image* and make a softlink for the image.
2. we specially add an package type which doesn't contain symlink for
the vfat filesystem.
For the first idea, I met an problem when I try to add
pkg_postinst_packagename function in kernel.bbclass file. Due to there
are not package name variables defined for the kernel-image-image.gz
kernel-image-image or other type kernel images. So I can not add
postinst functions statically why that how many packages and packages'
name are not certainly.
Do you have any opinions about these?
Regards,
Yanfei
next reply other threads:[~2020-06-09 10:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-09 10:32 Xu, Yanfei [this message]
[not found] <1616D997B5533366.13968@lists.openembedded.org>
2020-06-12 7:46 ` [OE-core] kernel: update rpm failed for the vfat Xu, Yanfei
2020-06-12 13:27 ` Bruce Ashfield
2020-06-15 11:43 ` Xu, Yanfei
2020-06-15 12:31 ` Bruce Ashfield
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=d384f6b7-dff7-ab38-7abc-348727f67d40@windriver.com \
--to=yanfei.xu@windriver.com \
--cc=bruce.ashfield@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=zhe.he@windriver.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