Email or username:

Password:

Forgot your password?
Top-level
groxx

@b0rk I tried saferm and I still think that should be the default everywhere...

... but I've more come to terms with the paranoia. Care is fundamentally necessary, being paranoid about it is *correct*. Most tools are well-behaved by default, but some are designed to let you shoot your foot if that's what you want.

10 comments
groxx

@b0rk I assume no, because it doesn't exist in everything I connect to, but yeah - I pretty reliably forget about it for years at a time, but I do make sure to add it whenever I start up something new. I've got a check for it in some of my reused dotfiles setup scripts, for example.

groxx

@b0rk it has saved my bacon once, and I managed to ctrl-c early enough on another machine's `sudo rm -rf ~` to not lose anything important. Hence: paranoia is healthy.

It really should be the default. It's much too easy to accidentally do that in scripts with bad string handling, and the few legitimate uses are so rare and so special that "run /bin/real_rm` by hand" is entirely reasonable.

groxx

@b0rk otherwise, my general tactic, and what I recommend to lots of people who want to learn computers: get a burner laptop for like $100. Learn how to wipe it and start over. Then go wild. If there's no valuable data on it, it doesn't really matter what you do with it.

E.g. this is how I test backup software, because I don't want to hand my "real" data over until I think I can trust one.

People need playgrounds. Their sole machine with their entire life's worth of data is not a playground.

Julia Evans

@groxx did you use this playground approach yourself? did it help? what kinds of stuff did you do on your playground computer?

groxx

@b0rk backups and restore testing is a very big one - lots of backup software is easy to set up but awful to recover with. By that point they've already hooked you, they have little incentive to do much but take your rent money until you have a problem, because nobody wipes their main PC to test it.

I use it for new OS testing and sometimes trying things out for friends - resizing positions is a crapshoot much of the time, and a problematic install can hose the whole system, so yeah. Paranoia.

groxx

@b0rk sometimes it also serves as a trivial air-gap to use potentially-shady software - just transfer stuff on a USB and erase when done. If it works, yay. If not, the risk of harm is practically zero.

groxx

@b0rk and as to using it myself to learn: yep! It was by far my biggest and easiest "ok now it makes sense" stepping stone, and I still use it as such.

Plus, like, ever wondered what `sudo rm -rf /` actually does, how much it breaks, and how you can sometimes recover from it? I've done it a few times, it's interesting.

groxx

@b0rk there's always the "just run a virtual machine" option, but that's often more of a pain imo.
If I need a lot of test environments for something esoteric, sure (snapshots are great), but it's often quite far from being able to tell you "does this work with my hardware" or "what is the experience of this like".

Virtual machines are also definitely not something I can reasonably recommend to complete newbies. "Follow Microsoft's recovery instructions" is easy, translating to a vm is not.

@b0rk there's always the "just run a virtual machine" option, but that's often more of a pain imo.
If I need a lot of test environments for something esoteric, sure (snapshots are great), but it's often quite far from being able to tell you "does this work with my hardware" or "what is the experience of this like".

Go Up