Reputation
673
Top tag
Next privilege 1,000 Rep.
See votes, expandable usercard
Badges
8 26
Impact
~51k people reached

Jan
15
revised Prevent user typing accidental space between rm and wildcard
added 140 characters in body
Jan
15
comment Prevent user typing accidental space between rm and wildcard
It comes down to this: rm can't know if the files its deleting were meant to be deleted. Only the user knows this. Sure, there are some system files and big operations (like deleting /), those are easy. rm can't tell that rm -I stuff.txt just deleted an important phone number, but rm -Ir stuff/ things/ is all temporary junk and cat pictures. Any proxy is going to contain far more false alarms than real ones. Confirmation dialogs come too soon, are too easy to dismiss, and are usually wrong to change the user's thinking from "delete stuff" to "is this stuff important".
Jan
15
comment Prevent user typing accidental space between rm and wildcard
@Kundor Deleting more than three files and deleting recursively (the confirmation is disabled by the habitual -rf I just discovered) are poor proxies for detecting a likely screw up. Wanting to delete a sub-directory isn't a likely screw up. The message doesn't help because it just confirms what the user said to do without adding useful information at a point when the user is not looking to verify. "rm: remove 1 argument recursively?" "Yes, delete the directory, I just told you to do that! ... wait, which directory was that? CRAP!!!"
Jan
15
comment Prevent user typing accidental space between rm and wildcard
@Kundor Yes, and it doesn't change the equation. It probably makes it more likely the user will ignore it. The user has a goal: delete stuff. The prompt says "are you sure you want to delete the stuff you just told me to delete?" The user is still fixated on the goal of deleting stuff, not verifying what is to be deleted, so they say "yes" without thinking. -i might give the user time to change goals. This answer on a related question lays it all out.
Jan
14
revised Prevent user typing accidental space between rm and wildcard
added 386 characters in body; added 35 characters in body
Jan
14
answered Prevent user typing accidental space between rm and wildcard
Jan
9
revised How can I diagnose certain games crashing?
added 42 characters in body
Jan
9
answered How can I diagnose certain games crashing?
Jan
9
comment How can I diagnose certain games crashing?
This is getting downvotes and votes to close. Could people explain why? I've already dug up AppCrashView as an investigative tool myself, that's exactly the sort of thing I'm looking for.
Jan
9
revised How can I diagnose certain games crashing?
added 355 characters in body
Jan
9
revised How can I diagnose certain games crashing?
added 67 characters in body
Jan
9
asked How can I diagnose certain games crashing?
Dec
27
awarded  Notable Question
Dec
9
comment Why would you `cat /dev/null > /var/log/messages`?
truncate -s 0 would do the same thing and be less idiomatic. However, shell programmers are a conservative bunch and one might encounter systems old enough or wacky enough to be lacking that command.
Nov
13
comment scp “lost connection” but ssh works fine
I don't have access to that machine anymore, but that seems a likely answer.
Nov
13
accepted scp “lost connection” but ssh works fine
Oct
25
revised Can a 7 days full 100% CPU load “burn-in” / “stress test” damage a modern notebook?
Update with actual data!
Oct
23
awarded  Yearling
Oct
22
awarded  Good Answer
Oct
21
awarded  Citizen Patrol