70
submitted 4 weeks ago by gun@lemmy.ml to c/linux@lemmy.ml

I'm a complete moron, I should've had that backed up and used trash...
I had to learn the hard way lol

top 50 comments
sorted by: hot top controversial new old
[-] davel@lemmy.ml 41 points 4 weeks ago

I should’ve […] used trash

For those who don’t know: trash-cli

[-] gazby@lemmy.dbzer0.com 7 points 4 weeks ago

It upsets me to no end that this isn't a standard package 😭

[-] UnRelatedBurner@sh.itjust.works 5 points 4 weeks ago

What an awesome tool that I wish I knew sooner. Also the && operator in sh. I think you can figure out what happened.

[-] clb92@feddit.dk 4 points 4 weeks ago* (last edited 4 weeks ago)

Also the && operator in sh. I think you can figure out what happened.

I'm guessing something like... Copy file/dir from location A to location B and then delete from A, but the copy had failed (and the delete unfortunately worked fine)?

[-] UnRelatedBurner@sh.itjust.works 6 points 4 weeks ago

I left the last sentence open ended, for comedic effect, but if you really wanna know:

I transcoded videos with ffmpeg, and tried to exit out of the bash script with ctrl C. the script was something like:

for
    ffmpeg file finishedFile;
    rm file;

my ^C broke out only from ffmpeg and before I realized what happened the file got removed and the next ffmpeg call filled my terminal. I tought the key didn't register, or something was stuck, so I pressed it again.. and again.. it cost like 45minutes of footage, wasn't that important tho.

[-] TGhost@lemm.ee 32 points 4 weeks ago

I’m a complete moron,

You are not,
Every person learning with the hardway isnt a moron,

You have to do, to really learn,

[-] RenardDesMers@lemmy.ml 3 points 4 weeks ago

If you do it again though...

[-] TGhost@lemm.ee 4 points 4 weeks ago

🫢 🤷‍♀️ I would say, that depend the personnal situation,

But i think, OP learned :)

[-] ExtremeDullard@lemmy.sdf.org 22 points 4 weeks ago

Here's a rule I learned the hard way a few decades ago:

  • If you type "rm", take you hands off the keyboard and take one deliberate breath before continuing your command.
  • If you then type "-r", do it again.
  • If you then type "-f" do it again.
  • In all cases, re-read what you wrote before hitting ENTER.
[-] xor@lemmy.blahaj.zone 11 points 4 weeks ago

I'm a big fan of starting the command with a #, then removing it once I'm happy with the command to defend against accidentally hitting enter

Putting ~ next to the enter key on keyboards (at least UK ones) was an evil villain level decision

[-] Zykino@programming.dev 13 points 4 weeks ago

When I'm unsure, I ls <the-glob>, chek, then replace ls with rm.

[-] torgeir@lemmy.ml 4 points 3 weeks ago

This. When the ls command works, hit ctrl-a, meta-d, type rm, enter.

[-] Zykino@programming.dev 3 points 3 weeks ago

Oh, didn't knew about Alt d. Thx

[-] Corr@lemm.ee 4 points 4 weeks ago

I really like this # idea. I've also taken to holding off on adding sudo when deleting privileged files

[-] ExtremeDullard@lemmy.sdf.org 2 points 4 weeks ago

I never thought of doing that in 40 years. It's a great idea actually. Thanks!

[-] 30p87@feddit.org 7 points 4 weeks ago
[-] Atemu@lemmy.ml 24 points 4 weeks ago
[-] 30p87@feddit.org 2 points 4 weeks ago

In the few years of me exclusively using the command line to manage files, even having rm aliased to rm -rf, and at some point to sudo rm -rf, out of convenience, I think it has happened thrice that I deleted the wrong file, and twice I was able to restore it with (hourly) backups. The third time, it was a minecraft world which I had created to test some mods and the server start script, and I had excluded it from backups because my ~/games dir is usually only used by steam.

[-] superkret@feddit.org 1 points 1 week ago

Also, triple-check which machine you're actually logged into.

[-] JackbyDev@programming.dev 1 points 3 weeks ago

-i doesn't exist?

[-] eldavi@lemmy.ml 17 points 4 weeks ago

if your session is still running you can use env to help reconstruct it

[-] OneCardboardBox@lemmy.sdf.org 11 points 4 weeks ago

I once had a directory in /tmp called etc which contained subdirectories for something I was migrating.

I thought that I was in /tmp when I ran rm -rf etc... I was actually in /

[-] Zozano@lemy.lol 9 points 3 weeks ago* (last edited 3 weeks ago)

That's why I always:

  • cd .cache
  • ls
  • rm -r *
[-] Peer@discuss.tchncs.de 13 points 3 weeks ago

Type a space before rm to prevent it from being added to your history to be a extra careful.

[-] wh0_cares@lemmy.blahaj.zone 12 points 3 weeks ago

Holy shit, I never knew you could do that! I've always really wanted a feature to stop random commands from being added to my history.

[-] Edo78@feddit.it 1 points 3 weeks ago

Some shells provide ways to prevent some commands to be added to the history

[-] Cyber@feddit.uk 2 points 3 weeks ago

For which shell? I just tried that on a bash system and the command was still stored in .bash_history 😔

[-] Peer@discuss.tchncs.de 2 points 3 weeks ago

Set the HISTCONTROLvariable. If it is set to ignorespace then commands entered with a leading-space will not be stored in the history.

load more comments (1 replies)
[-] fmstrat@lemmy.nowsci.com 7 points 4 weeks ago

ZFS and dotfiles are your friend. Sorry for your loss.

[-] sadTruth@lemmy.hogru.ch 7 points 4 weeks ago

Tipps to prevent future accidents:

  • Set up BTRFS snapshots with Timeshift or Snapper. Switching to BTRFS is worth it for snapshots alone.
  • Do regular backups on a device that can not be reached by rm: vorta local on external hdd that you connect once a week OR vorta/borg2 to a NAS/Server that does BTRFS snapshots itself OR Nextcloud to sync to a server that has a trashbin OR git to a server. Just remember that Nextcloud and git are unencrypted, so the server has to be secure and trustworthy. Vorta and borg2 can be set up with encryption.

Mistakes are unpreventable due to our error-prone brains, but it is a choice to repeat them.

load more comments (1 replies)
[-] cakeistheanswer@lemmy.dbzer0.com 7 points 4 weeks ago

You're just the latest member of a long and storied fraternity of the best worst operating system architecture.

https://web.mit.edu/~simsong/www/ugh.pdf

One of us...

[-] Dirk@lemmy.ml 6 points 4 weeks ago

I should’ve had that backed up

Absolutely! IT's time to check out Stow now. With this you can easily manage your configuration and dotfiles (and all other data) in a single location.

https://venthur.de/2021-12-19-managing-dotfiles-with-stow.html

[-] RenardDesMers@lemmy.ml 6 points 4 weeks ago

Sorry for your loss. I did something similar recently. A script was creating a "~" folder in my notes folder. I wanted to delete it... Thankfully it stopped at some file it couldn't remove and my dotfiles are in git.

load more comments (2 replies)
[-] xlash123@sh.itjust.works 5 points 3 weeks ago

I've started adopting the habit of putting "-rf" as the last argument to avoid accidentally deleting something before I've double-checked my input. Good luck, and may this never happen again.

[-] Edo78@feddit.it 1 points 3 weeks ago

I do exactly the same. It's not foolproof but it's better than nothing. I remember, almost a decade ago, when I discovered that rm on mac didn't accept flags as last arguments... I hope they changed that behavior

[-] ryannathans@aussie.zone 5 points 4 weeks ago

I should have had backups of important files in my home directory

Lessons learned the hard way

[-] MachineFab812@discuss.tchncs.de 4 points 4 weeks ago* (last edited 4 weeks ago)

Reason's I never use auto-complete in the terminal. Sadly, that's sometimes not enough.

[-] yum13241@lemm.ee 8 points 4 weeks ago

just be careful and review what tab-suggest shows.

[-] ryannathans@aussie.zone 5 points 4 weeks ago* (last edited 3 weeks ago)

Reasons to have backups more like. No need to make life hard

load more comments (4 replies)
[-] circuitfarmer@lemmy.sdf.org 3 points 4 weeks ago
load more comments (2 replies)
[-] notprogrammer@programming.dev 3 points 4 weeks ago

Can you say why were you trying to rm -r your .cache anyway? Also RIP.

[-] pineapple@lemmy.ml 7 points 4 weeks ago
[-] gun@lemmy.ml 2 points 3 weeks ago

Yeah my system was running out of space and I wanted to free a bit quickly. Turns out the issue was Rust building 20GB of binaries and I should have deleted those instead.

[-] superkret@feddit.org 4 points 4 weeks ago* (last edited 4 weeks ago)

Probably the number one cause of borked Linux systems - trying to "de-bloat".

[-] scriptGoober@linux.community 2 points 3 weeks ago
[-] bennieandthez@lemmygrad.ml 2 points 4 weeks ago

thats the sort of command you need to make an alias for

[-] GustavoM@lemmy.world 2 points 4 weeks ago
load more comments
view more: next ›
this post was submitted on 21 Nov 2024
70 points (97.3% liked)

Linux

48648 readers
1182 users here now

From Wikipedia, the free encyclopedia

Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).

Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.

Rules

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 5 years ago
MODERATORS