Archive for July, 2011
I bought myself a gasoline power-washer last year to replace my old washer and was really pleased with its performance. At the beginning of summer this year, I set up my new washer for my annual outdoor cleaning. I hooked everything up and gave the engine a pull. As expected it cranked right up and then all of a sudden – BAM – it stopped!! It wasn’t a “ran out of gas” kind of stop it was a very sudden “the engine has seized” kind of stop.
I gripped the pull-crank, gave it a pull and the pull-cord ripped right out of my hand. The engine wouldn’t budge. I take meticulous care of my stuff so I was perplexed … what could it be? A visual inspection of the crankcase didn’t show any blowouts or cracks … hmmmm. I pulled the spark plug and inspected the top of the piston and cylinder, all seemed fine. I then pulled the top of the engine off and again, everything was fine. That left one thing — the water pump itself. I pulled the pump off and manually rotated the engine’s crankshaft and thankfully it turned with very little effort, so I knew the engine was fine.
The pumps that ship with store bought pressure washers are notoriously “cheap” but my unit had less than 10 hours of use, it shouldn’t have failed already! I continued my investigation by removing the three external valve caps from the pump. I immediately noticed a fowl smell …. that’s strange, what could that be? I then pulled one of the valves out and found the remains of, what we call locally, a lizard (Carolina Anole)! My guess is he had decided to make the water-hose or the water intake on the pump itself his home …. poor little guy!
The pump has a total of six valves which, unfortunately, are made of plastic. Most of the valves were damaged as I removed them from their seats which meant I had to order a replacement pump or buy a new kit. The replacement pump would have been easier but this kind of DIY project is therapeutic for me so I ordered the kit ($72) and did the repair myself.
Following is a 60 second video that captures the repair.
Until next time – GEEK OUT!
Most of my computer time is spent on my Mac inside the gorgeous OS/X GUI using the tools that are necessary for me to run my business. Many of my side projects, however, take me back to my beloved Bash Shell which I can use on my Mac, where it gets plenty of use, but is especially used on my many Linux servers, all of which are run without a fancy GUI (Gnome, KDE, X, etc).
If you’re not familiar with Bash, it is a Unix shell that is part of the GNU Project and is a replacement for the Bourne shell. Bash has been distributed widely as the default shell for numerous Linux distributions, various BSD distributions and Mac OS/X. Simply put, “Bash is a command processor that’s typically run in a text window, allowing the user to type commands which cause actions. Bash can also read commands from a file, called a script. Like all Unix shells, it supports filename wildcarding, piping, here documents, command substitution, variables and control structures for condition-testing and iteration.”1 Bash is a POSIX shell with a number of extensions. The foundation of bash such as its keywords, syntax and other basic features were copied from Bourne Shell. Other features, e.g., history, were copied from C Shell and Korn Shell.
As I manage my Linux servers the tool that gets the most use, by far, is the text-editor vi. Many of today’s younger Linux geeks run full GUIs on their boxes. If they work at the command line at all, they often use “simpler” editors such as Pico or nano but for me, I prefer vi – thank you very much!!
Anyone with even a casual understanding of the *nix world knows that there are many-a-topics that can start a nasty flame-war. One such topic is vi -vs- Emacs and if you’re a Hacker on any level then you’re obliged to pick a side and hold your ground (I’m only kidding … let’s all be happy ;)
Want to be a respectable “hacker“? Learn to use vi or Emacs and you’ll have my respect!
Following are few of the basic vi commands I use on a regular basis:
|vi filename||edit filename starting at line 1|
|vi -r filename||recover filename that was being edited when system crashed|
|:x<Return>||quit vi, writing out modified file to file named in original invocation|
|:wq<Return>||quit vi, writing out modified file to file named in original invocation|
|:q<Return>||quit (or exit) vi|
|:q!<Return>||quit vi even though latest changes have not been saved for this vi call|
|1G<Return>||move cursor to first line in file|
|nG<Return>||move cursor to line n|
|G<Return>||move cursor to last line in file|
|^f||move forward one screen|
|^b||move backward one screen|
Adding & Changing Text
|i||insert text before cursor, until <Esc> hit|
|I||insert text at beginning of current line, until hit|
|a||append text after cursor, until <Esc> hit|
|A||append text to end of current line, until hit|
|o||open and put text in a new line below current line, until hit|
|O||open and put text in a new line above current line, until hit|
|x||delete single character under cursor|
|Nx||delete N characters, starting with character under cursor|
|dw||delete the single word beginning with character under cursor|
|dNw||delete N words beginning with character under cursor;|
|D||delete the remainder of the line, starting with current cursor position|
|dd||delete entire current line|
|Ndd||delete N lines, beginning with the current line;|
Copy & Paste
|yy||copy (yank, cut) the current line into the buffer|
|Nyy||copy (yank, cut) the next N lines, including the current line, into the buffer|
|p||put (paste) the line(s) in the buffer into the text after the current line|
|/string||search forward for occurrence of string in text|
|?string||search backward for occurrence of string in text|
|n||move to next occurrence of search string|
|N||move to next occurrence of search string in opposite direction|
Until next time – GEEK OUT!