[OE-core] Could oe-core be infected by virus?
jupiter.hce at gmail.com
Thu Jan 23 12:22:12 UTC 2020
On 1/23/20, Ross Burton <ross.burton at intel.com> wrote:
> On 21/01/2020 11:21, JH wrote:
>> The wired
>> thing was that image injected so many new messages, including "Welcome
>> to OpenEmbedded nodistro.0!" I have never seen in previous built image
> If you've never seen that before, but now you do, then the problem is
> that you're not setting DISTRO in your build as 'nodistro' is the default.
I do have a DISTRO defined in local.conf, and I do have a distro file
as follows since day one to use OE / Yocto to build the imx6 image, I
have never changed it:
$ cat build/conf/local.conf
DISTRO = "solar"
$ cat conf/distro/solar.conf
#TCLIBC = "musl"
DISTRO_FEATURES = "largefile 3g wifi usbhost systemd xattr ext2 ipv4
DISTRO_FEATURES_BACKFILL_CONSIDERED = "pulseaudio sysvinit bluez5
# Drop WiSPR support from connman to drop GnuTLS dependency
#PACKAGECONFIG_pn-connman = "systemd iptables"
# Use OpenSSL instead of GnuTLS
PACKAGECONFIG_pn-wpa-supplicant = "openssl"
VIRTUAL-RUNTIME_init_manager = "systemd"
VIRTUAL-RUNTIME_initscripts = ""
# If we don't want to build all locales we can select the ones we want here...
# just comment this out in order to build all locales. These are not
# automatically installed into the image, that is selected elsewhere.
GLIBC_GENERATE_LOCALES = "en_US.UTF-8"
Are there any issues in my distro file?
So my root is root at solar as well, I did not see nodistro.0 before. Let
me further clarify it, in my build system, the source of oe-core,
bitbake, meta-freescal and all configure files are all stored in a
persistent local repository, it has not been changed for a year, the
only changes are those packages downloaded from remote URLs.
This is why I am very concerned, how could the boot sequence and
messages changed dramatically where the source and configure files
have not been changed for a year. But I am more worried that the boot
caused error after 2 - 3 good cycles of booting. Why wasn't the boot
broken in the first boot cycle, only broken after 2 - 3 good bootings?
I cannot comprehend it, appreciate your explanation.
Thank you very much Ross.
More information about the Openembedded-core