![](/static/253f0d9b/assets/icons/icon-96x96.png)
![](https://lemmy.ml/pictrs/image/q98XK4sKtw.png)
I also don’t like the duplication of logs in journald and syslog, so I always disable forwarding to syslog
I also don’t like the duplication of logs in journald and syslog, so I always disable forwarding to syslog
Encryption and compression don’t play well together though. You should consider that when storing sensitive files. That’s why it’s recommended to leave compression off in https because it weakens the encryption strength
Sounds ridiculous to me. If politicians didn’t decide on the rail system because of elon, it’s still a problem caused by the politicians
Just buy one ticket to a Taylor Swift concert and you’re already a billion dollar richer
Already India and chine have had working ones for many years. It’s not speculative and I recommend you to research the tech. It’s unfortunately not very present in western nuclear energy debates. Could be a political reason but that’s just a dirty guess
The problem with these arguments and the focus of debates is that they are based on nuclear energy from uranium, not thorium. Thorium is ubiquitous in nature, power centers are much easier to set up and can be small and the waste, while initially (a bit) more radioactive than uranium waste, loses it’s radiation level much faster
Edit:typo
Wealth predator. It has more of that negative connotation it deserves
Good is relative tbf. I’ve had issues installing something natively while installing flatpak just worked
As KVM is part if the Linux kernel, I assume you’ll have to look into kernel hardening instead, next to OS hardening. Hardware is also important to consider when talking about VM escaping. A CPU that supports better VM isolation features and encrypted memory
Scaleway has educative blog posts about water usage footprint of datacenters and how they’re approaching it more efficiently. Recommended reads
I was arguing how it is a very useful tool with many great additions, rather than rely on the: “no old better!” reply based on ignorance. But it looks like your replies have turned full removed, so no point in continuing here to try and educate you.
You can set the space limit for journals logs really low then, to avoid double space usage. As for the last argument, that also was an issue for me years ago because not all tools were compatible with the journald format, but that’s since long fixed now and I’ve not experienced any issue for a long time. Journal logs provide a standard format for all applications, so third party tools don’t need to be compatible with every log format of your applications. And it also comes with great additional features like -b or --since etc. So I still don’t get the issue here
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
Here’s some more examples:
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 can’t explain, perhaps due to my limited knowledge about the subject. I understood that compression was a weakening factor for encryption years ago when I heard about it. Always good to do your own research in the end 🙃