![]() I script up the several steps that require privilege and try to just execute these (by command recall) and nothing else - anything else requires much care. I know instinctively that the pink/red background root terminal deserves respect, and the straw-yelllow bkgnd is the remove development system, and. I have to stay alert to what I am doing, but that's exactly the price power demands, but I've given myself a big advantage by making it very easy to see the issue visually and then I can assess the risks. After accidentally typing commands in the wrong window (years ago) I started color coding them (different background text color), and putting related terminal sessions in a single window as tabs, sometimes even changing the font size. I often/usually have a bunch of terminal sessions open to different systems, remote development systems, embedded systems behind vpns or on my office, other systems in my office, and yes for some projects I have a window open as local root. You "just type it" to get over the tedious hurdle. ![]() Guard ralis and seat belts and redundant authentication challenges and "are you sure?" queries all lead people to adjust their behavior to more risky behavior. It's so tedious that it strongly encourages you to ignore and type.Įsp see the Peltzman effect & Risk homeostasis. Once you've seen it enough to get tired, you just ignore it. Once you've entered the passwd a dozen times in the past hour you just do it out of "muscle-memory". Typing vs doesn't help you understand what "something" did. If it doesn't you have no idea what just got done.Either way - you still have no idea what it's done.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |