I trying to study the usage of systemd init system in place of the procd.
Presently i followed the procedure in the below link , but it seems I could not succeed.
https://github.com/jdub/openwrt-systemd ,
Any pointers are welcome...
That repository looks like it's been abandoned - no activity since 2015.
Generally though - systemd is way too big and resource heavy for OpenWRT.
3 Likes
…and procd is way too ingrained into OpenWrt's core framework and all the existing procd-initscripts in packages. Of course it's possible, but really a heap of massive development to be done - and at the same time systemd won't fit on anything but x86 or one of the ARM SBCs (RPi, sunxi, rockchip) with >100 MB of usable storage.
Disclaimer: I'd really like to see this as a proof-of-concept with systemd, networkd and (maybe-) iwd, it would be interesting to compare, but none of that will work (~=fit) into >85% of all supported (plastic) routers with (usable) flash sizes ranging from 13 MB to 40 MB (even with 128 or 256 MB NAND, you'll rarely get to more than that to your disposal (dual-firmware and unfortunate OEM partitioning), only few will give you around 90 MB, those might work (pending bootloader constraints and limits for the maximum kernel size).
3 Likes
Thanks for your response, any steps you would recommend to get the systemd utility ported to Openwrt Rootfs (SquashFs)
there's also Error installing libsystemd on router
Let me quote from systemd.io:
systemd is a suite of basic building blocks for a Linux system. It provides a system and service manager that runs as PID 1 and starts the rest of the system.
It is not a utility. I'm not saying this to nit pick but rather to make a point of how involved this sort of undertaking would be. For a crude analogy, if an application is like an ingredient of a soup then an init system is like the base of the pot the soup is cooked in. You have to know a lot to redesign the pot as complex as an operating system.
1 Like
That said, if you really want to try this then my (admittedly layman) idea would be to start off by making your own little linux system out of a linux kernel and systemd, from scratch. This should be much easier to achieve than modifying an existing system, and should give you better understanding of the underlying technology. I'm pretty sure that you will be able to find some guides for this (and systemd documentation will probably be useful as well).
1 Like
Indeed, or to start from something like a minimal Debian (yocto?) system. Yes, those will be larger, you'd have to re-implement device specific support and will lack a webinterface, but that's still going to produce quicker results than shoehorning systemd into OpenWrt (without a concerted effort from all other developers). procd, ubus, netifd and luci are way too essential for OpenWrt to be replaced by systemd, dbus, networkd easily. Again, technically possible (for devices with generous storage), just a quite major undertaking.
1 Like