'ping' (one per second), which should start failing when I disconnect the correct cable.
Every time I add a new rule to my firewall, I first set up a demonstration of what I want to block and show that it isn't blocked. Then I add the firewall rule. Then I repeat the demonstration and show that it now fails. (If I don't do the demo before I add the rule, I can't be sure the rule works for the reason I think it does.)
A More Useful Ping
It can be useful to have ping produce a beep for every successful ping. That way you can be elsewhere in the room disconnecting cables and not have to keep running back to your screen to see whether the pings are working.
Linux
Solaris and other Unix systems without the -a option can use the following trick. The output of 'ping' happens to include a colon only on lines that report success. You simply pass the output through the tr command to translate each colon into a Ctrl-G (the 'bell' character). $ ping -s
(Solaris requires the -s option to make it a continuous ping. Others do not.)
To get a Ctrl-G to appear on the command line, you may have to precede it with a Ctrl-V. That is, you type: $ ping -s
Routine #9: Always Back Up a File Before You Edit
When I'm about to edit a configuration file, I always make a backup. I don't waste time thinking, 'Gosh, is this file important enough?' If I have to ask, the answer is 'Yes.' I make backups the same way every time so there is no time wasted figuring out the best way. My system is to copy the file to a file with today's date on it. For example,
It's tempting to convince yourself, 'I'm making a small change that I'll be able to manually undo' or 'I'm an expert, I can't mess this up.' However, hindsight has found that a backup is better. Especially three weeks from now when you can't figure out why that service has stopped functioning.
Routine #10: Record 'To Take' Items for Trips
I travel a lot. I used to forget to bring things, and when I hadn't, I'd still be nervous that I might have forgotten to bring something. Who needs that kind of stress?
Now, I write a 'things to pack' list on the righthand side of my to do list for the day I'll be traveling. For weeks (or months) leading up to the trip, anytime I think of something I should bring on the trip I pop open my organizer and write it on that list. Since I always have the organizer with me, I never fail to record an idea.
When I pack, I check off the items as they go into my suitcase.
I also create a second list of the things to have in hand when I leave. That's usually my tickets, my wallet, my suitcases, and so on. I use this list to help me pack the car. If someone else is picking me up, this list includes the items I keep near my front door so they are there when my ride arrives.
I use these lists for both work and nonwork trips. I'd hate to get out of the habit just because I was traveling for pleasure. I reuse these lists to form my next list. I have culled items from past lists to create a master checklist that I keep in my Notes section.
How to Develop Your Own Routines
Now that you've seen some example routines that work for me, how can you develop routines for yourself? Here are some things to look for:
Repeated events that aren't scheduled. Often there is a task or meeting that you repeat many times a week (or month) that isn't scheduled regularly. Would things be helped if it was scheduled in advance? Are you spending more energy scheduling the meeting than preparing for it? If so, develop a schedule. Propose either a regular time and day or a series of dates and times and get agreement up front.
Maintenance tasks. A lot of
