[Infrastructures] isconf deprecates infrastructures.org?

[Steve Traugott]

(*Way* behind on my mail...)

Looks like everyone else covered this thread pretty well; just wanted
to inject a few more points:

On Sat, Aug 12, 2006 at 10:07:37PM -0700, Mark Ferlatte wrote:
> Let say that I have an environment with a bunch of developers, and those
> developers, for example, have root on a set of machines.  Being
> developers, they want to be able to install things temporarily "as
> needed", and I want to be able to restore the machines back to baseline
> quickly and easily.

People always want to be able to roll back to a previous baseline
while running within the context of the root filesystem that they're
modifying.  As a sysadmin, you quite frequently do rollbacks, for
instance by running a package uninstaller.  This works most of the
time, and this leads you to believe that a general rollback tool
is possible.  It's a myth.

The changes you've made are irreversible -- you can't run the code
backwards; you can only run other code that claims to be able to undo
those changes.  The "undo" outcome can't be predicted computationally,
so a general-purpose tool that can do this reliably can not be
written.  Any general rollback tool has to run outside the context of
the root filesystem being modified.

Use systemimager, running in a miniroot during reboot, if you want to
get outside the root filesystem and do clean rollbacks.  Then use
isconf to add the last few deltas on since the last image snapshot.

Steve
-- 
Stephen G. Traugott  (KG6HDQ)
Managing Partner, TerraLuna LLC
stevegt@TerraLuna.Org -- http://www.t7a.org