Because of something I did during an anthropology lecture, I learned the hard way to read the "The following packages will be REMOVED" list when upgrading a package to backports in Debian GNU + Linux.

dullbananas (Joseph Silva)@lemmy.ca · edit-2 2 months ago

Because of something I did during an anthropology lecture, I learned the hard way to read the "The following packages will be REMOVED" list when upgrading a package to backports in Debian GNU + Linux.

electricprism@lemmy.ml · 2 months ago

This was definitely one of my least favorite things when I used Debian.

It shows that we need to think about how users are performing tasks and how to intuitively make their usage more successful. The OS should try to get out of the way and always have the ability to easily revert in the case of platform failure.

SynopsisTantilize@lemm.ee · 2 months ago

There should be an undo oopsies feature you can turn on and off somewhere so in terminal when I accidentally rm -f * the entire system doesn’t eat it’s own tail.

ProgrammingSocks@pawb.social · 2 months ago

While that sounds good it would be extremely complex to actually implement. The only real-world feature like this is btrfs snapshots (or filesystem snapshots generally). The good thing is that snapshots only store the difference in data and so they don’t have to take up much space.

SynopsisTantilize@lemm.ee · 2 months ago

I still have to set mine up for my laptop. I’m using mine for dev use raw. No protection. Or backups

electricprism@lemmy.ml · 2 months ago

This is a fascinating concept.

If files are removed from the Index it would only seem natural that they can be undeleted until their physical address is recycled and overwritten.

In fact I remember something like this pre Windows 95 era where files were crossed out. Undeleting them was like magic.

This is why the windows term “Recycle” is more appropriate because the data remains until the space is reused or zero’d out.

This is the kind of reexamining we need, does our current iteration make sense from an engineering perspective or is it just a evolution of a bunch of archaic stuff from a time that doesn’t represent the present tech world at all.

I would be okay with replacing rm with recycle and shred as their function is more clear in the name.

SynopsisTantilize@lemm.ee · edit-2 2 months ago

Yes. Potentially make it wipe the undo action saved after a second reboot. As in;

1.“sudo apt dist upgrade -reverttool”

2.reboot #1

3.oops bricked my dependencies

4.sudo “ah shits fucked -reverttool!”

5.reboot #2

6.-reverttool completed the reversion of “sudo apt dist upgrade”

ALTERNATIVELY

1.sudo apt dist upgrade -reverttool

2.reboot #1

3.everything worked

4.forget about the -reverttool

5.reboot #2

6.-reverttool wipes it’s /tmp/revert.txt until next command.

Warning: Some posts on this platform may contain adult material intended for mature audiences only. Viewer discretion is advised. By clicking ‘Continue’, you confirm that you are 18 years or older and consent to viewing explicit content.

Because of something I did during an anthropology lecture, I learned the hard way to read the "The following packages will be REMOVED" list when upgrading a package to backports in Debian GNU + Linux.

Because of something I did during an anthropology lecture, I learned the hard way to read the "The following packages will be REMOVED" list when upgrading a package to backports in Debian GNU + Linux.