32bit programs on 64bit kernel

Author: emojifreak

README.md

@@ -36,15 +36,15 @@ Hardware clock can be corrected by `sntp -S pool.ntp.org` as root.
 * [`gdm3` display manager and gnome session fail because of insufficient CMA](https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980536). Adding `cma=192M@256M` to `cmdline.txt` fixes this symptom.
 * ~~[Boot from USB is impossible](https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977694) unlike Linux 5.9. Kernel package capable of USB boot is available at http://153.240.174.134:64193/kernel-deb-5.9/~~
 * Kernel package in the above URL is built by `build-raspi4-kernel.sh` in this directory.
-* [When kernel is booted from USB, `udisks2` consumes lots of CPU power](https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980980). It can be prevented by `systemctl mask udisks2`.
+* ~~[When kernel is booted from USB, `udisks2` consumes lots of CPU power](https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980980). It can be prevented by `systemctl mask udisks2`.~~
 
 # 32-bit executables on 64-bit linux-image-arm64 kernel
 `linux-image-arm64` 64-bit kernel can run `armhf` 32-bit executables. If `armhf,arm64` is given to the above scripts as
 the target architecture in place of `armhf` or `arm64`,
-then an SD card with 32-bit executables and 64-bit kernel will be built. But
-[it does not boot](https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971748). To make it bootable,
-do the following steps as root after running the above script:
-~~It should boot. The following steps have become unnecessary.~~
+then an SD card with 32-bit executables and 64-bit kernel will be built.
+It should boot if `debian-rpi-sd-builder.sh` is used.
+It will not if `devuan-rpi-sd-builder.sh` is used,
+and the following steps are necessary. The difference comes from `systemd-nspawn` versus `chroot`.
 
 1. `mount /dev/mmcblk0p2 /mnt`
 2. `mount /dev/mmcblk0p1 /mnt/boot/firmware`