You can still forward to text syslog or to a central logging server like Loki if working with multiple hosts. I still don't get the issue with binary logs.
Why do you consider it as poisoning? I've heard the argument about not doing things the traditional Linux way (binary logs for example). But if the alternative provides so many benefits, why is it an issue? Systemd is a piece of cake for all parties compared to sysvinit and alternatives, so why is it bad when it solves so many issued, and makes it super easy to use by just adding e.g. a new option to a Unit?
Another example: timers are more complex than cronjobs, but timers offer additional needed features like dependencies, persistence, easy and understandable syntax, and more. So although more complex, once you get the hang of them, they're a very welcomed feature imo
I can understand that it makes it easier to add changes that would benefit systemd and distros in general. I read that they introduced run0 to solve long shortcomings of sudo (I'm not aware of which). That sounds logical.
Actually no. The thing is just that systemd handles so many things that makes the lives both developers/distro maintainers and users easier, but most of it happens in the background. You can forget about having to learning complexer tools, just do it all via systemd
Systemctl edit: create an extension for the unit file and add some changes S edit --full: edit the full unit file (and timer too iirc) S enable --now: enable + start S disable --now: disable + stop
Arch could use better standard MAC security applied to systemd units like Debian does.
Arch could have an easy few clicks installer, something like a default modern setup.
Live kernel patching.
Don't wanna be a whiner but wireless in ears never last long enough for me. I'm forced to stop using them after a while because they need to be charged. Even a 2 and a half hour phone call is enough to deplete them. This is a non existing problem with wired ones
I still have 200 euro wired in ear headphones that are my favorite pair so I need to 3,5mm port. But I never got the loud commotion over the disappearance of the port, because you can easily use a 3,5mm to USB-c cable. Having said that,I do still appreciate such a port in my phone because sometimes I forget to take the cable with me or I lose it.
I'm not a supporter of the approach of blocking sudo access from capable people (non tech yes), because they can still download and execute binaries as their user. Or go to rescue mode to make modifications. I had to do that myself because of a micro managing IT team. Allowed? No. Allows me to focus on my work and let me be efficient? Yes. Usually this approach also requires a backdoor tool on your device that they install, which is just ridiculous.
Just communicate setup requirements (drive encryption, firewall, AV,...) And have some tool to check the security requirements and rating and this way you can apply proper security policies in the company and respect the user's privacy
Tbf you only need iwd, as systemd can take care of the rest. But it's not an option for me on desktop anyway because signal and vpn connection visibility are important for me and that's not possible without a GUI running
Different purposes true, but not exclusively. RAID only has effect on drive failure specifically. If downtime is intolerable then it's not the right solution to just use RAID and you should look into total redundancy of the hardware and more. It also comes with performance bottlenecks or improvements depending on the setup, that's another factor to take into account. So in the end it really depends on your requirements and backups can actually serve as an alternative, depending on your setup and as long as it meets your RTO
I think it's just that there are too many options and the communities are so fragmented. I'm trying out simplex but it still feels like beta software. Regardless I'd like to see it succeed so we have a real private alternative that doesn't rely on big tech or shady government sponsorship.
Plus you need to hire less people to manage all services yourself. You can also avoid vendor lock in if you have z proper policy, but most managers don't think long-term or even care. I started not caring about costs much anymore, it's not a me problem, it's a manager problem. I just do enough effort to choose the right setup
You can still forward to text syslog or to a central logging server like Loki if working with multiple hosts. I still don't get the issue with binary logs.