RPN01 wrote:
Don¹t laugh so hard... Sed has saved my rear many times when my only access
to a barely running penguin was through the 3270 virtual terminal.
Learn enough sed so that you aren¹t caught sitting dumb-founded at the
terminal when your guest doesn¹t come up because you left some critical
option (or character) out of one of many various innocent-looking config
files.
When sedding, I recommend first
cp /etc/someimportantconfigurationfile \
/etc/someimportantconfigurationfile.bak
and then
sed </etc/someimportantconfigurationfile \
>/etc/someimportantconfigurationfile.bak \
etc
If at first you don't succeed, you can try again without recovering what
you did wrong. It's also good documentation, for when you do the virtual
paperwork later;-)
Mostly, I do this in a script, and the script first tests for the
existance of the backup, creates it if there isn't one. Then, it's just
a matter of hacking and running until the script works.
Interactively, I'm more likely to use ed or ex, and we're back where we
started;-)
--
Cheers
John
-- spambait
[EMAIL PROTECTED] [EMAIL PROTECTED]
Please do not reply off-list
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
