So basically, you're dealing with devices that use obsolete hardware and are designed to be extra-brittle (no safety margin), with a built-in planned obsolescence (what if the new update requires just a bit more space for "calibration data"?). Got it.
sysvinit indeed fits perfectly. Make the system extra unreliable, to provide a stimulus to buy a newer version.
> One of the main goals of OpenWRT is to support legacy networking hardware that vendors abandoned.
And OpenWRT abandoned this goal. OpenWRT also can do nothing about firmware vulnerabilities in the old WiFi chipsets.
Moreover, 10 years ago, systems with 32Mb were already common.
So basically, you're dealing with devices that use obsolete hardware and are designed to be extra-brittle (no safety margin), with a built-in planned obsolescence (what if the new update requires just a bit more space for "calibration data"?). Got it.
sysvinit indeed fits perfectly. Make the system extra unreliable, to provide a stimulus to buy a newer version.
> One of the main goals of OpenWRT is to support legacy networking hardware that vendors abandoned.
And OpenWRT abandoned this goal. OpenWRT also can do nothing about firmware vulnerabilities in the old WiFi chipsets.
Moreover, 10 years ago, systems with 32Mb were already common.