We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hi there, We updated the kernel from petelinux 2020 to 2021 with Ubuntu rootfs which released for KV260.
The check_init() function was added by 2021, we got a problem at check_init() where was at /scripts/functions.sh in ramdisk. Put differently, at here
Root cause: if you checked the path "/rootfs/sbin/init", it means "/rootfs/sbin/lib/systemd", the checking always return 1 to umount $path here
and why it not happen with petalinux rootfs? buz checked the path "/rootfs/sbin/inin", it means "/rootfs/sbin/init.sysvinit".
That's all.
If so, we suggest considering the situation for using Ubuntu rootfs user.
Thank you so much!
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Hi there,
We updated the kernel from petelinux 2020 to 2021 with Ubuntu rootfs which released for KV260.
The check_init() function was added by 2021, we got a problem at check_init() where was at /scripts/functions.sh in ramdisk. Put differently, at here
Root cause:
if you checked the path "/rootfs/sbin/init", it means "/rootfs/sbin/lib/systemd", the checking always return 1 to umount $path here
and why it not happen with petalinux rootfs?
buz checked the path "/rootfs/sbin/inin", it means "/rootfs/sbin/init.sysvinit".
That's all.
If so, we suggest considering the situation for using Ubuntu rootfs user.
Thank you so much!
The text was updated successfully, but these errors were encountered: