aboutsummaryrefslogtreecommitdiffstats
path: root/mageia4arm.cfg.template
diff options
context:
space:
mode:
authorNeal Gompa <ngompa13@gmail.com>2020-01-11 13:49:16 -0500
committerNeal Gompa <ngompa13@gmail.com>2020-01-11 13:49:16 -0500
commit57d9815a4882677ebdffec0d3d568e00addc34a8 (patch)
tree3124d78e398af7fe117d08554002558573f9a971 /mageia4arm.cfg.template
parentba52a77532de2af6e29ab228f58d82fc33c262d1 (diff)
downloadmageia4arm-57d9815a4882677ebdffec0d3d568e00addc34a8.tar
mageia4arm-57d9815a4882677ebdffec0d3d568e00addc34a8.tar.gz
mageia4arm-57d9815a4882677ebdffec0d3d568e00addc34a8.tar.bz2
mageia4arm-57d9815a4882677ebdffec0d3d568e00addc34a8.tar.xz
mageia4arm-57d9815a4882677ebdffec0d3d568e00addc34a8.zip
Drop copying qemu binaries and ensure qemu-user is configured on host
Since Mageia 6, it has not been necessary to copy the qemu binaries and the binfmt files into the chroot to run ARM binaries inside a chroot. This change finally stops doing that. In order to make sure this works properly, we ensure that systemd-binfmt is restarted to apply binfmt changes on the system. This ensures that the host qemu-user-static is configured to execute binaries, even in chroots.
Diffstat (limited to 'mageia4arm.cfg.template')
0 files changed, 0 insertions, 0 deletions