11–20 of 308 posts
The 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.
Earlier quoted context omitted.
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 :-)
Earlier quoted context omitted.
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 :-)
The 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.
systemd CVEs: https://ubuntu.com/security/cves?package=systemd&limit=100
Rust PoC: https://github.com/KillingSpark/rustysd
> Rustysd is a service manager that tries to replicate systemd behaviour for a subset of the configuration possibilities. It focuses on the core functionality of a service manager, not requiring to be PID1 (aka init process).. core systemd functionality is not very hard to replicate.. the advantages of having a systemd-like service manager can be brought to many other platforms.. (like alpine linux, commonly used in docker containers and small vms) and freebsd.
Earlier quoted context omitted.
In the embedded world, BSP/driver support is the main thing that matters. Linux is undefeated in that area for embedded purposes.
I thought there was a compatibility layer available that made it possible to run Linux drivers on at least FreeBSD.
Earlier quoted context omitted.
Turns out, many people use systemd after what, 15? years of doomsday predictions :-)
i don't notice anything good systemd does for me, just where it interferes, and that's a constant annoyance, a few days a week.
This is anti-systemd FUD. Implying that applications which work without systemd are going to stop doing so. Suggesting that Linux distributions adopted systemd because it's good for distributors and not because users actually want it. We are "forced" to use systemd's udev implementation. Please.