This class provides support for satisfying writable locations at
runtime. It supports persistent and volatile configuration.

E.g.:

WRITABLES = "foo"
WRITABLE_PATH[foo] = "/foo/bar"

Signed-off-by: Andrei Gherzan <andrei.gherzan@huawei.com>

philippe coval authored 3 years ago and philippe coval committed 3 years ago

Relate-to: https://git.ostc-eu.org/OSTC/OHOS/docs/-/issues/74


Thanks-to: Marta Rybczynska <marta.rybczynska@huawei.com>
Signed-off-by: Philippe Coval <philippe.coval@astrolabe.coop>

GN meta-build system uses it's own meta-language to describe build process of
the project including toolchain definition, compiler flags, dependencies, etc.
GN tool parses the meta data and generates ninja file for the final build
process.

For the project to use Yocto-provided toolchain and flags it is necessary to
patch the BUILDCONFIG.gn file in following manner:
- change set_default_toolchain function call to use
  //build/toolchain/yocto:yocto_target
- append  [ "//build/toolchain/yocto:yocto_flags" ] to configs variable in all
  set_defaults function calls

Closes: https://git.ostc-eu.org/OSTC/OHOS/meta-ohos/-/issues/64
Closes: https://git.ostc-eu.org/OSTC/OHOS/meta-ohos/-/issues/65
Closes: https://git.ostc-eu.org/OSTC/OHOS/meta-ohos/-/issues/66



Signed-off-by: Robert Drab <robert.drab@huawei.com>

philippe coval authored 3 years ago and philippe coval committed 3 years ago

I have observed this in several places,
Without it's still understandable but it requiered me an extra effort.

This makes me think I think there are standards to check if
"Simple English" is used, this could help community adoption of project.

Forwarded: https://git.ostc-eu.org/OSTC/OHOS/meta-ohos/-/merge_requests/233


Signed-off-by: Philippe Coval <philippe.coval@astrolabe.coop>

The poky/dunfell uprev includes a minor upgrade for webkitgtk too:
2.28.2 -> 2.28.4.

Signed-off-by: Andrei Gherzan <andrei.gherzan@huawei.com>

Part of: https://git.ostc-eu.org/OSTC/OHOS/meta-ohos/-/issues/80



Signed-off-by: Andrei Gherzan <andrei.gherzan@huawei.com>

Split the reuse header in its own file to avoid confusing git am and
forcing the build system to other means of applying the patch.

Fixes: https://git.ostc-eu.org/OSTC/OHOS/meta-ohos/-/issues/99



Signed-off-by: Andrei Gherzan <andrei.gherzan@huawei.com>

philippe coval authored 3 years ago and philippe coval committed 3 years ago

List didn't display fine, if not prefixed by empty line.

Relate-to: https://allscenarios.readthedocs.io/en/latest/meta-ohos/blueprints/touchpanel.html
Forwarded: https://git.ostc-eu.org/OSTC/OHOS/meta-ohos/-/merge_requests/226


Signed-off-by: Philippe Coval <rzr@users.sf.net>

Signed-off-by: Andrei Gherzan <andrei.gherzan@huawei.com>

We work with GPT-based targets for some of our reference boards. Make
sure busybox has GPT support.

Signed-off-by: Andrei Gherzan <andrei.gherzan@huawei.com>

Signed-off-by: Andrei Gherzan <andrei.gherzan@huawei.com>

Currently, it only includes x-mounts.

Signed-off-by: Andrei Gherzan <andrei.gherzan@huawei.com>

This components defines, generates and provides systemd mount units for
the system partitions (based on filesystem labels) as it follows:

boot partition -> label "boot" -> "mountpoint: /run/mount/boot"
devdata partition -> label "devdata" -> "mountpoint: /run/mount/devdata"
sysdata partition -> label "sysdata" -> "mountpoint: /run/mount/sysdata"
appdata partition -> label "appdata" -> "mountpoint: /run/mount/appdata"

When installed, the units are enabled early in the boot process as part
of the local-fs.target.

Signed-off-by: Andrei Gherzan <andrei.gherzan@huawei.com>

Signed-off-by: Andrei Gherzan <andrei.gherzan@huawei.com>

Signed-off-by: Andrei Gherzan <andrei.gherzan@huawei.com>

The only difference in this plugin (as of now) is that it takes into
consideration the --label argument.

Signed-off-by: Andrei Gherzan <andrei.gherzan@huawei.com>

The bootimg-pcbios wic plugin in dunfell hardcodes the filesystem label
without taking into consideration the --label argument. This was
improved later on but it never landed in dunfell:

commit a79b5f0f2139bbd77df31704944630c8a5a0b562
Author: jbouchard <jeanbouch418@gmail.com>
Date:   Sun Jun 27 20:28:37 2021 -0400
Use the label provided when formating a dos partition

We workaround this by creating a version of this plugin that has this
change included and we will be using this new plugin until the
improvement (if at all) lands in dunfell.

Signed-off-by: Andrei Gherzan <andrei.gherzan@huawei.com>

x-boot - boot
x-sys-a - sys-a
x-sys-b - sys-b
x-dev-data - devdata
x-sys-data - sysdata
x-app-data - appdata

Signed-off-by: Andrei Gherzan <andrei.gherzan@huawei.com>

Signed-off-by: Andrei Gherzan <andrei.gherzan@huawei.com>

Our initial implementation defines the partitions labels as it follows:
x-boot
x-dev-data
x-sys-data
x-app-data

This was proven to be problematic in many ways.

First of all, this needs to be treated with care as the associated
systemd mount unit would need to escape the dashes. For example,
"x-dev-data" would need to have a mount unit associated escaping this to
"x\x2ddev\x2ddata".

Secondly, the yocto version we are using (dunfell) has a bug where
backslashes are not supported in SRC_URI[1]. This would require a
workaround when using mount points with an escaped filename.

The easiest way forward would be to just not use dashes for the labels.
In this way, we maintain consistentcy for the mountpoints (/mnt/<label>)
without having to deal with all the above.

[1] https://bugzilla.yoctoproject.org/show_bug.cgi?id=8161



Signed-off-by: Andrei Gherzan <andrei.gherzan@huawei.com>

The root b partition was initially set up using the assumption that a
wic part configuration without fstype would leave the partition empty
(no filesystem). Checking a bit deeper the wic implementation, that
never worked as expected as the tool defaults to a vfat partition[1] (when
no fstype is provided). Also, squashfs doesn't support an empty
filesystem.

Given the above, we switch the second rootfs (B) to using the same
content as the default one (A). This has an added advantage that we can
test switching the root filesystem A-B without any additional
operations.

[1] https://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/scripts/lib/wic/ksparser.py?h=dunfell#n158



Signed-off-by: Andrei Gherzan <andrei.gherzan@huawei.com>

This makes things cleaner and more consistent when the other partitions
use variables like:
SYSDATA_PARTITION_SIZE
APPDATA_PARTITION_SIZE
etc.

Keep this change consistent on the wic files too.

Signed-off-by: Andrei Gherzan <andrei.gherzan@huawei.com>

Signed-off-by: Andrei Gherzan <andrei.gherzan@huawei.com>

Cleanup description and let PROVIDES default to PN

Signed-off-by: Amit Kucheria <amit.kucheria.ext@huawei.com>

The build `make` metadata tracks sysroot dependencies as file suitable
for `make` to get the dependecies of the main source file. This is done
with a combination of preprocessor options: -MD and -MF. These files are
suffixed `.d`. When these files are generated with paths that include
the version of the dependency, later dependecy version bumps will
invalidate these paths as the sysroot gets regenerated.

For example, gcc headers file stdbool.h is defined as the dependecy to:
[BUILD]/tmp/work/stm32mp1_av96-poky-linux-musleabi/optee-os-stm32mp/3.12.0.r1-r0/recipe-sysroot-native/usr/lib/arm-poky-linux-musleabi/gcc/arm-poky-linux-musleabi/11.1.1/include/stdbool.h

This include the gcc version 11.1.1 in its path. When gcc is upgraded,
sysroot is regenerated, configure and compile retriggered but compile
will reuse the generated `.d` file from the old gcc version, hence
failing to find the header mentioned above (as the gcc version changed).

This recipe uses an out-of-tree build so the easiest and most effective
fix it to just clean B once configure is triggered (retriggered). This
will force make to regenerate the dependency files as per the new paths
in the sysroot (assuming a sysroot update).

Signed-off-by: Andrei Gherzan <andrei.gherzan@huawei.com>

Document how to wire the breadboards for the door lock blueprint

Signed-off-by: Bernhard Rosenkränzer <bernhard.rosenkraenzer.ext@huawei.com>

Bernhard Rosenkränzer authored 3 years ago and Stefan Schmidt committed 3 years ago

This is a backport of openembedded-core commit
b4bc29cf19d811c0ec948dbe69c0bc79fe31e0e8:

Source: https://sourceware.org/git/glibc.git
Tracking -- https://sourceware.org/bugzilla/show_bug.cgi?id=27896

Backported upstream commit 42d359350510506b87101cf77202fefcbfc790cb to
glibc-2.33 source with dependent commit id 217b6dc298156bdb0d6aea9ea93e7e394a5ff091.

Upstream-Status: Backport [https://sourceware.org/git/?p=glibc.git;a=commit;h=42d359350510506b87101cf77202fefcbfc790cb

]

Signed-off-by: Vinay Kumar <vinay.m.engg@gmail.com>
Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Signed-off-by: Bernhard Rosenkränzer <bernhard.rosenkraenzer.ext@huawei.com>

Update to gcc 11.2. This is a bugfix release and shouldn't cause any
problems.

Drop patches that have been merged upstream.

Signed-off-by: Bernhard Rosenkränzer <bernhard.rosenkraenzer.ext@huawei.com>

Clarify the image name we use for the blueprint as well as the used
distro config.

Signed-off-by: Stefan Schmidt <stefan.schmidt@huawei.com>

This is a first stab at documenting the network properties used in the
gateway blueprint. It reflects the current status and needs to be kept
in sync with changes.

Fixes: https://git.ostc-eu.org/OSTC/planning/core-os/-/issues/201



Signed-off-by: Stefan Schmidt <stefan.schmidt@huawei.com>

Without the extra empty line the formatting for the numbered would not
kick in.

Signed-off-by: Stefan Schmidt <stefan.schmidt@huawei.com>

Update the Linux kernel recipe to the 5.10.52 version from OE [1],
log available from [2].

[1] 9cec9a92c3e8451d1b9875e97e63c24543a6f787
[2] https://git.openembedded.org/openembedded-core/commit/meta/recipes-kernel/linux/linux-yocto_5.10.bb?id=9cec9a92c3e8451d1b9875e97e63c24543a6f787



Signed-off-by: Marta Rybczynska <marta.rybczynska@huawei.com>

Marta Rybczynska authored 3 years ago and Bernhard Rosenkränzer committed 3 years ago

Compilers and related utils are better restricted on production platforms.
Change permissions of all installed binutils tools to remove access from
users outside of the root group.

Signed-off-by: Marta Rybczynska <marta.rybczynska@huawei.com>

Add meta-riscv to bblayers.conf.sample to enable RISC-V support
in all ASOS builds

Signed-off-by: Bernhard Rosenkränzer <bernhard.rosenkraenzer.ext@huawei.com>

Use binutils 2.37 by default in allscenarios-linux

Signed-off-by: Bernhard Rosenkränzer <bernhard.rosenkraenzer.ext@huawei.com>

Update binutils to 2.37 -- it brings many improvements, including some
needed to get a working RISC-V 32 toolchain.

Signed-off-by: Bernhard Rosenkränzer <bernhard.rosenkraenzer.ext@huawei.com>

It is a good practice to timeout the shell if no activity. Add a timeout
to the /etc/profile* settings in a separate script.

Signed-off-by: Marta Rybczynska <marta.rybczynska@huawei.com>

Remove the hardening distro requirement from the recipe,
we do not want to rename our distro and this feature is useful
in all cases.

One thing that needs to be added is setting up the password min/max
age, and the minimum password length.

Signed-off-by: Marta Rybczynska <marta.rybczynska@huawei.com>

Marta Rybczynska authored 3 years ago and Bernhard Rosenkränzer committed 3 years ago

The append in the meta-security layer works for a "harden" distro
only. We remove this limit as we do want it by default and we do not
want to rename our distro.

A discussion on the mailing list [1] mentions that we might get
DISTRO_FEATURE in the future.

[1] https://patchwork.openembedded.org/patch/174773/



Signed-off-by: Marta Rybczynska <marta.rybczynska@huawei.com>

Marta Rybczynska authored 3 years ago and Bernhard Rosenkränzer committed 3 years ago

Backports the recipes of the meta-hardening layer from meta-security in
hardknott, synced up to 5050d1267ad41288c903086030594f8702bfa039

It includes recipes for hardening base-files (/etc/profile) and shadow
(/etc/login.defs).

Signed-off-by: Marta Rybczynska <marta.rybczynska@huawei.com>