On 09/18/2014 02:20 PM, Philippe De Swert wrote:
Hi,
On 18/09/14 17:13, Emil Renner Berthing wrote:
On 18 September 2014 16:10, "Jóhann B. Guðmundsson" <johan...@gmail.com> wrote:
On 09/18/2014 01:24 PM, Emil Renner Berthing wrote:
The real reason is of course that I'd like to see systemd running
on my router and other small devices that usually run some OpenWRT
derivative.
The openwrt community is still going forward with their (re)-invention of
init system called procd since they were incapable of using systemd built
with --disable-alots right?
Or are you talking about you dont want to use OpenWRT but your own or
something else and thus the request?
Yes, indeed. Also I am hoping that having this option means other small
devices will run systemd in the future.
I think you are missing the point of musl.... So you have so little
space you need a smaller libc but then you want to use a binary of ~1MB
+ tools to replace an init of a few Kb?
Moreover systemd needs a lot more kernel options, so making smaller
kernels gets hard. Not to mention for example cgroups etc is often very
unstable in the earlier kernels that have the support for those devices.
IOW more kernel crashes due to systemd requiring cgroups.
The reason why OpenWrt would do their own init, is to keep it small.
Often those routers etc have only a few Mb of flash. Even with
compression just having a 2Mb just for the init system is a bit much.
It would be interesting to get some "how low can you go" numbers from
the embedded crowd regarding systemd and or systemd + udev-hwdb.
I would think 16MiB target should be fairly easy to achieved but
anything less than that might be well work...
JBG
_______________________________________________
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
