You need some ansible love in your life!
bushvin
I have my moments… 😉 Feel free to pm me if you need more advice.
I would copy the existing system onto a new system:
- Update system to the latest packages
- Create a new base system using the same distro
- Check which packages are not on the new system, add them to your playbook
- Install packages on new system
- This will take some time. Run a find of all files and pass them to md5sum or sha512sum to get a list of files with their checksum. Compare the list from the old system to the new system.
- Update your playbook with these findings. Template is probably the way to go, Lineinfile might be good as well, use copy if nothimg else works.
- Check firewall settings and update your playbook.
Anyhow this will take some iterations, but while you have a copy of your ‘production’ system, you can test on your ‘test’ machine until you have the same functionality.
You assume I would think you’re wrong. I do not.
Morally, assassination is despicable. But so is fascism.
I applaud you for taking the high road, while I just say Fuck ‘em all. Fascism should not be tolerated, even in a democracy.
It doesn’t require Hitler-level Evil. Just pragmatism.
He did (at least) one good thing in life, and people feel the need to smear him…
Ise kde, not gnome.
Aside from the obvious (company providing all the necessary tools) why not using libreoffice and saving it as M$ excel?
Surprise… Surprise… It’s a snap!
dnf upgrade
And
package-cleanup --cleandupes
Should have fixed it.
This is why it’s important to make backups. If, by any chance you printed your disk configuration before the gpt operation, you want to copy it into a notepad NOW. You can use that to try and recreate your original partition layout after converting the disk back to MBR. Chances are nothing is wiped, except for your disk configuration. No guarantees, though…
Whatever you do, don’t format anything, as that WILL overwrite your data.