MichaIng

Just to verify, when you remove the symlink, the binary fails, right? ```sh rm /lib/arm-linux-gnueabihf/libmmal_core.so raspimjpeg # restore ln -s /lib/arm-linux-gnueabihf/libmmal_core.so.0 /lib/arm-linux-gnueabihf/libmmal_core.so ```

Btw, which sources for `raspimjpeg` are you using? It isn't from the archived [userland](https://github.com/silvanmelchior/userland/tree/master/host_applications/linux/apps/raspicam) repo, is it? Probably I can play with the build and see what I get.

Thanks! > Note that the software is now working OK under Bullseye using legacy camera support. So the links are now correctly pointing to `*.0` libraries? Great to see that...

> I understand that 64 bits BULLSEYE is not supported, no workaround ? => > i just use legacy cam support in sudo raspi-config

Also the migration from init.d to systemd via update seems to work fine, no orphaned process or so. But I could test it only with manual checkout + hacking owner+branch...

No, since the Docker image does not use systemd. AFAIK it doesn't use SysV either, but with s6 an entirely different init/service system.

Ah: ``` AmbientCapabilities=CAP_NET_BIND_SERVICE CAP_NET_RAW CAP_NET_ADMIN CAP_SYS_NICE CAP_IPC_LOCK CAP_CHOWN ``` actually is required here as well, for fresh installs with systemd where `setcap` was never applied. I'll add it once I'm...

> it's more or less a copy of the existing service It could use `pihole-FTL-prestart.sh`/`pihole-FTL-poststop.sh` scripts then as well, when this got merged, to reduce maintenance a bit.

The related (re)start limits can be set in the `[Unit]` section: https://www.freedesktop.org/software/systemd/man/systemd.unit.html#StartLimitIntervalSec=interval I see, I need to start doing the systemd integration 😅. I'm sorry for not doing so far...

@Power-onoff Pinging you here where your post fits better: USB boot did only work with the boot switch set to SPI previously, right? The MMC toggle should only allow eMMC...