Why systemd is a problem for embedded Linux
kevinboone.me
Why systemd is a problem for embedded Linux
1–10 of 308 posts
Re: Why systemd is a problem for embedded Linux
#2You could checkout void and alpine.
Re: Why systemd is a problem for embedded Linux
#3The BSDs may be more to your liking. They're a lot more minimalist than Linux now.
Re: Why systemd is a problem for embedded Linux
#4> The more fundamental problem is that the people who most like systemd are distribution managers. (...) a distribution manager doesn’t have to maintain, integrate, and support a whole bunch of system utilities from different sources – systemd provides everything in one huge build.
That’s actually a great lesson in optimizing your product for adoption.
Re: Why systemd is a problem for embedded Linux
#5The BSDs may be more to your liking. They're a lot more minimalist than Linux now.
In the embedded world, BSP/driver support is the main thing that matters. Linux is undefeated in that area for embedded purposes.
Re: Why systemd is a problem for embedded Linux
#6I can only say that the obvious answer here is to throw effort into supporting & improving Gentoo.
Re: Why systemd is a problem for embedded Linux
#7I'm conflicted on the name/issue. I don't have any issues with Linux on embedded systems, because I'd use a minimal init with that one single app it should be running. (Or as mentioned in other comment, build your minimal distro yocto-style) RPi is a low spec general computer at this point. The idea of running gnome on an embedded system just doesn't make sense in my mind...
RPi took the form factor that was used for industrial control boards and made it into a usable desktop... which people use as a desktop (or home server). But it created a segment which really is neither. And a lot of the software just isn't written with that segment in mind. Maybe as it gets more popular, people will pay more attention. But currently it seems more of an expectations issue.
Re: Why systemd is a problem for embedded Linux
#8> The more fundamental problem is that the people who most like systemd are distribution managers. (...) a distribution manager doesn’t have to maintain, integrate, and support a whole bunch of system utilities from different sources – systemd provides everything in one huge build. That’s actually a great lesson in optimizing your product for adoption.
it's also why corporate software is so shit - it's shiny in all the ways it needs to be shiny for management to make the decision, but it's a pain for the actual users.
the trick in both cases is to know your customers!
Re: Why systemd is a problem for embedded Linux
#9https://chimera-linux.org/
https://chimera-linux.org/docs/faq#what-is-the-projects-take...
Is going a really interesting direction with it's service management and login / seat management.
Fwiw, I think it's author also has a more gounded perspective on systemd then many others.
For Chimera the main issue is systemd's high volume use of gnulibc and gcc extensions, which is a porabiluty issue for Chimera which uses a LLVM toolchain and musl libc (and a bunch of really cool hardening and compiler engineering)
Re: Why systemd is a problem for embedded Linux
#10> The more fundamental problem is that the people who most like systemd are distribution managers. (...) a distribution manager doesn’t have to maintain, integrate, and support a whole bunch of system utilities from different sources – systemd provides everything in one huge build. That’s actually a great lesson in optimizing your product for adoption.
it's also why corporate software is so shit - it's shiny in all the ways it needs to be shiny for management to make the decision, but it's a pain for the actual users. the trick in both cases is to know your customers!
Turns out, many people use systemd after what, 15? years of doomsday predictions :-)