Thanks for the answer.
I do have access to the previous version of both files (I'm storing all of this in a Subversion repository), but there may be other issues. The files are firewall configuration files, Cisco PIX, to be exact. So, they contain data like:
access-list testing permit ip host 3.3.3.3 host 22.2.2.2
access-list testing deny tcp object-group first host 4.4.4.4 eq 99
or:
object-group network first
network-object host 9.9.9.9
The thing is, I'm not sure I'm going to be able to get enough context to dump it straight to patch...some of these sections may be as short as one or two lines.
What I'm trying to do here is give some users the ability to edit certain parts of device config, but limit their ability to edit other parts. (And, hopefully, apply some of these snippets to multiple devices, to make them all act the same.)
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
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, details, 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, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
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.