When something goes wrong, the first thing you might do is to try to recreate the problem.
This isn’t because you’re hoping something miraculously changed and that the hex is lifted (although I suppose it doesn’t hurt to hope). It’s so you can make sure that there is really a problem. Did you mistype the command? Were there any error messages that you missed the first time around?
It’s true that there are times when retyping the command may make things worse. For example, if you’ve lost data in an editor, opening the file again may overwrite any “backup” copies still on disk.
But if you feel secure that retyping the command can’t make things any worse, try to recreate it. Once you can recreate a problem, you’re one step closer to fixing it. In addition to giving you a process that you can break into components, it also gives you a way to test when the problem is solved.
Get WYNTK: UNIX System Admininistrator now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
