25
Repost: Accidents and Annoyances (programming.dev)
submitted 3 days ago by to c/linux@lemmy.ml
7 comments fedilink hide all child comments
 

If I'm breaking any rules, apologies.

I know, labeling something a repost is a lead weight, but I'm a fan of full disclosure. I posted this topic two years ago and I thoroughly enjoyed reading all the replies, I even learned a few things. Time has passed, and I figure some of you out there will have some new and interesting stories to share, so tell me:

So I was thinking of silly things I’ve done that pseudo-broke my system, or made me think I had a broken system. Like the time I put the cmd :

exit

in my ~/.bash_aliases file and I had to open a text editor to fix it because that broke all the terminals on my machine.

I’m curious what other silly things users have done to confuse themselves.

Op Op.

you are viewing a single comment's thread
view the rest of the comments
[–] 6 points 3 days ago

A few years ago at $DAYJOB, we were evaluating Apache Nifi, which is basically a data routing tool. I wanted to use it for reading some files from one directory and just writing them back out to another.

So, I figured, I have two stray files in my home-directory, I'll just tell it to read straight from the home-directory.
What I didn't expect, is that it would recurse into subdirectories.
And even less so, that it would remove the files it had read.

So, all the files in my home-directory were gone.

Although, it had written them dutifully to that other directory. So, in theory, I still had all my files.

But it hadn't copied the folder structure. Documents, SSH keys, cache files, everything was placed into a single, flat folder.

  • permalink
  • fedilink
  • source
    •