4 ms·
It's a .sh script, so he could have read it before running it. And when he saw "chown: Operation not permitted", he could have realized that the word Admin in t
by rmunn 7mo ago
It's a .sh script, so he could have read it before running it. And when he saw "chown: Operation not permitted", he could have realized that the word Admin in the script was a clue that it needed, well, admin-level privileges, and he should try running it with sudo (after reading it first, naturally). I'm with you, I feel like this is someone who caused himself a lot of self-inflicted pain.
I mean, if he had read the script before deleting it (that's the third time I've mentioned reading the script, do you think I'm dropping enough hints?), he might have found a handy list of ... ALL THE FILES HE WAS LOOKING FOR. You know, all the 18 or so locations that he had to find by hand.
But nope, he didn't ... yes, I'm going to say it for the fourth time ... READ THE SCRIPT.
- bobbob1921 7mo agoAnd what about for users that either can’t find this uninstall script or wouldn’t know how to read it or what the contents mean? While I think you do have a point, we also can’t assume that the uninstall script really would’ve removed all traces.
- deleted 7mo ago[deleted]
- rabf 7mo agoThose users have never heard of the word `uninstall` nor have any comprehension of what it would do. They will after a time, just buy a new computer because the old one is full up.
- rmunn 7mo agoThe fact that it reported "hundreds" (if the author is right about that, he might be misremembering) of permissions-related errors tells me that it was trying to clean up hundreds of files. Sure, not knowing what's in the script, I can't say for certain that it wouldn't have missed something... but it sounds like it was trying to be thorough. And it was written by the people in position to know what needed to be cleaned up, so I actually have no reason to assume that it wouldn't have removed all traces.