This one time, at band camp, James Gregory wrote: >I've also heard of people storing all of /etc in version control for >this purpose. In my opinion it would be unnecessary if you kept your >cfengine stuff in a source control system, but it would give you that >absolute confidence that you could roll back and forward, even if >cfengine failed.
cfengine vs all-etc-in-vc is like procedural vs functional programming; one of them lets you describe in detail how the operation is going to be done, the other one lets you describe the problem. That's probably not a good analogy, but with cfengine I can describe the goal state of the system and have cfengine sort out what needs to be done to get it there. Editing etc and rolling out changes also means handling heterogenous systems adds complexity to the system you use; cfengine effectively "factors out" the common parts and lets you describe the small changes meaningfully. >RHEL also lets you do centralised upgrades. Of course, I'm a total >amateur at this stuff, so I couldn't tell you if it lets you do the >reverse operation or lets you remove stuff. Jamie? You can flag packages for removal from within RHN, but its less fun than installing them. -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
