Legato version: 16.01.2
Legato Linux source: Legato-Dist-Source-mdm9x15-SWI9X15Y_07.08.03.00
Questions about the tree installation and the startup sequence of Legato.
After building my Yocto virt-arm firmware image for QEMU, I meet some problem with the legato startup sequence.
It may be a misunderstanding on my part. I would like to discuss philosophy Legato installation within the image.
legato-af recipe create the following directory structure in the image:
- /mnt/legato with apps, mnt, system, usr directories.
legato-init recipe provides the startup scripts (startlegato.sh and startlegato-compat.sh):
startlegato.sh script checks if the /mnt/legato/start file exist.
=> If the file not exist, it is an older version, it runs the old startup script startlegato-compat.sh.
But NO “/mnt/legato/start” file is created by the legato-af recipe.
So legato 16.01.2 is “considered an old version”.
I think there is an error.
What is the legato version number to distinguish between a new and old startup sequence ?
startlegato-compat.sh script starts all fg_xx_scripts.
In the fg_00_BindMount script file:
First, it test if the “/mnt/legato/usr/local/bin/legato” exists.
if [ -f /mnt/legato/usr/local/bin/legato ]
Or the legato binaries are installed in the “/mnt/legato/system/bin” directory by legato-af framework.
The fg_00_BindMount script create mount points with the wrong variable INSTALL_BASE.
Remapping /home --> /mnt/flash/home
Remapping /usr/local --> /mnt/flash/usr/local
Remapping /opt --> /mnt/flash/opt
Remapping /etc/ld.so.conf --> /var/run/ld.so.conf
Remapping /etc/profile --> /var/run/profile
That is why I will like discuss to the philosophy of legato framework start sequence with you.
Temporarily, so I created a new script to start legato.