Okay, I admit to being quite the newbie when it comes to [ sh | bash ]
scripting. I can write a killer GCOS/6 EC file. I can spell TSO. I
almost got to the point of understanding DD statements in JCL.
Let's not run off on a religious war about what scripting language I
should use instead of sh. That is not the point of this exercise -
right or wrong.
Along about 1984, I discovered a "package" of .bat files (remember DOS
.bat files) for a simple menu. This "package" took advantage of the
fact that one could name a collection of files: 1.bat, 2.bat, 3.bat and
so on. Paint a text screen to fill the monitor leaving a place to enter
one's selection and PRESTO! you have a menu. Associated with this
"package" was a series of sample .bat files that basically taught me
everything I needed to know about writing .bat files. I used this
concept a very long time and deployed it in all manner of places.
Fast forward to present. We have a new-system-configuration process
that involves a whole bunch of steps. My predecessor took great pride
in their script writing skills. We have one big honking install script
that does a metric buttload of stuff, non-stop, dumping out all its
boo-boos to a log file.
So for sport, I went looking for a "menu.sh" script and I found a really
wonderful reference. I feel very capable of inserting this menu logic
into the monolith giving us a stepwise process.
But I am a greedy BOFH and I'd like to mark those steps completed.
Yeah, I can hear Tilghman lining up how to do this with perl. hmmmmm.
Just typing this out may be theraputic enough to get me to the answer.
sed and awk, here I come. :)
Howard
--
You received this message because you are subscribed to the Google Groups
"NLUG" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/nlug-talk?hl=en
