Distro packages don’t really matter much in my experience. You either use project-specific package management or install stuff with Homebrew or Nix package manager. Sometimes maybe even containers.
One problem with distro packages is that you can only install one version. And in practise a lot of software projects have outdated dependencies. Sometimes you have multiple projects with conflicting version dependencies.
When I checked a long time ago, there wasn’t.
And not only failures, often it’s useful to get mail for all executions.
I guess cron continues to have its place.
Is there any easy way to get mail of the runs like with cron?
Valve hasn’t heard of imperative mood for changelog entries, it seens.
Everything except mobile support points towards Emacs org-mode indeed.
If you can find something even close to it, I would be interested to know as well.
Thanks for the comments. I agree on the general consensus, that once an encryption key enters the VPS, the encryption is compromised.
However, I’m thinking more in practical terms, eg. the service provider doing just casual scanning across all disks of VPS instances. Some examples could be: cloud authentication keys, torrc files, specific installed software, SSH private keys, TLS certificates.
Wow, I didn’t know reads deteriorate SSDs. What’s the reason? Is the rate significant?
Do unplugged SSDs eventually lose the data?
I use Debian stable because I’m tired of constantly twiddling with breaking stuff, I just want a distro that keeps working without issues and tinkering.
If you still want to learn Linux stuff and debug packages, then go for a bleeding edge distro.
Use software owned by Oracle? Fuck that, I would rather get mauled by a bear.
Just put your system configuration in Ansible playbook. When your distro has new release, go through your changes and remove ones that are no longer relevant.
For home, I recommend a dotfiles repository with subdirectories for each tool, like bash, git, vim, etc. Use GNU stow to symlink the required files in place on each machine.
This is the way.
Add unattended-upgrades, and never worry about security updates.
I recommend just backing up the files.
But if you really have to back up the disk image, dd a copy of it, mount the copied image as loopback device, write the loopback filesystem full of /dev/zero, sync, delete the zero file(s), unmount, cp --sparse=always and store the result.
The reason for using the loopback image step is to prevent wearing out the SD card with writing the free space full of zeros every time you make a backup.
There may be an existing tool for this, but I don’t remember it.
Dan Goodin seems to write sensationalist articles of vulnerabilities. Then buried in a footnote you notice that the vulnerability doesn’t really affect anyone in real world.
How does systemd-run/run0 handle what /etc/sudoers currently does?
I’m disappointed in how little technical discussion there is in this thread.
Someone excitedly demonstrated to me how easy it is to code with copilot. They generated a bunch of code easily. And then proceeded to debug subtle bugs for longer than it would have taken to write it yourself in the first place.
And in the end they were still left with badly structured and maintainable code.
LLMs will do exactly what Stackoverflow has done, but more efficiently: allow profileration of bad/outdated solutions to problems, and application of those with no real understanding.
More garbage code and more work for the few people who continue to actually read manuals and understand what they are doing.
RIP Bram
Any ideas how to get sound working in Proton for Doronko Wanko?
Heh, Distrobox came to my mind when writing my comment. I haven’t used it enough to recommend it yet though.
I recall there are some other development container projects, but can’t remember the names right now.
Development containers are nice in theory. In practice, sometimes development environments are so complex that it might not be worth the trouble. But it’s good to have options.