I was also 50++ when I first got serious about learning Perl. The worst part was going back and forth across languages. If / test syntax is different for Perl vs. ksh vs. Oracle (my "native tongue"). When substringing, some languages use start_byte,length; others use start_byte, end_byte.
It got a whole lot easier when I decided that, for a while, I'd simply do everything in Perl. So I second the idea that you should try to stop writing shell scripts and create Perl scripts instead.
What type of scripts? Hey, you're a storage admin. Start by creating some scripts that mimic the reporting that EMC / Promise / Sun / whomever have for their disk-carving tool. Create a script into which you can put a slice name, and verify that it's not already allocated to a LUN. Create a script that goes out and identifies slices which are no longer associated with a LUN (maybe their server's being rebuilt). In other words, think about cool tools that'd make your life easier. That's what I did to handle Oracle alert logs, listener logs, /var/adm/message, etc. It works pretty well because all the work you do in Perl saves you from getting headaches outside Perl.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Outside of code tags, you may need to use entities for some characters:
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
|
|
