Arcanus Maximus

In a pinch tape fixes anything..

Posted by jtk at 09:38 AM | Permalink

'nuff said

Posted by jtk at 10:15 AM | Permalink

Netcat - a couple of useful examples

Posted by jtk at 01:47 PM | Permalink

IBM Developerworks had an article about bash functions. I found this little ditty tucked in the article and I liked it.

---

These basic steps and recommendations can be applied to many client/server applications that run in Linux.
Document the prerequisites and main sequence for running scripts
Divide actions into logical groups
Develop an execution sequence based on a common usage scenario
Provide comments and instructions in each shell script
Make an initial backup to create a baseline
Check for input parameters and environment variables
Try to provide "usage" feedback
Try to provide a "silent" running mode
Provide one function to terminate the script when there are errors
When possible, provide functions that do a single task well
Capture the output of each script, while watching the output being produced
Inside each script, capture the return code of each line command
Keep a count of the failed transactions
Highlight the error messages for easy identification in the output file
When possible, generate files "on the fly"
Provide feedback on the progress of the execution of the script
Provide a summary of the execution of the script
Try to provide an output file that is easy to interpret
When possible, provide cleanup scripts and a way to return to the baseline

1. Document the prerequisites and main sequence for running scripts


2. Divide actions into logical groups


3. Develop an execution sequence based on a common usage scenario


4. Provide comments and instructions in each shell script


5. Make an initial backup to create a baseline


6. Check for input parameters and environment variables


7. Try to provide "usage" feedback


8. Try to provide a "silent" running mode


9. Provide one function to terminate the script when there are errors


10. When possible, provide functions that do a single task well


11. Capture the output of each script, while watching the output being produced


12. Inside each script, capture the return code of each line command


13. Keep a count of the failed transactions


14. Highlight the error messages for easy identification in the output file


15. When possible, generate files "on the fly"


16. Provide feedback on the progress of the execution of the script


17. Provide a summary of the execution of the script


18. Try to provide an output file that is easy to interpret


19. When possible, provide cleanup scripts and a way to return to the baseline

Posted by jtk at 01:20 PM | Permalink

Mini Storage Tower from Addonics. I have been looking for a nice cheap storage enclosure. This looks to fit the bill. I wouldn't run sata drives with out mirroring though.....

Applying the innovative storage design concept from the original Storage Tower, the Mini Storage Tower features increased portability, almost half the size and weight of it's predecessor. The Mini Storage Tower stores up to 4 standard 3 1/2" or 4 2.5" Mobile Racks, and comes with a low noise cooling fan and stylish design with swing open front panel for easy drive access. Similar to the Storage Tower, all the hard drives inside can be connected to computer via a single USB, eSATA, Multilane cable or 4 eSATA cable with a choice of different back panel configurations.

Posted by jtk at 08:57 AM | Permalink

O'Reilly Radar points out two neat web 2.0 tools. I like how Ajax and web 2.0 apps work, but my biggest problem is the inability to use them offline. It looks like Zimbra is addressing that. I have played with Zimbra in a VM and it looks very neat.

The other is Stikkit. it is a web based sticky notes tool.

Posted by jtk at 08:53 AM | Permalink

I have been riving myself nuts trying to figure out why the line drawing in putty didn't work.

I finally figured out that it was the LANG variable.

export LANG=en_us did the trick.

Posted by jtk at 05:06 PM | Permalink