[Infrastructures] isconf deprecates infrastructures.org?

[Mark Ferlatte]

--3MwIy2ne0vdjdPXF
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Magnus said on Mon, Jul 31, 2006 at 09:57:07AM -0400:
> I am reading up on isconf at http://trac.t7a.org/isconf/ and a lot of
> what I'm reading would seem to contradict or deprecate the bootstrap
> checklist for infrastructures.org.
>=20
> Does the site need to be revamped to reflect this development?

Perhaps this is no longer the correct list, but:

Something that I don't see isconf doing is recovering from user error
(at least, not very well).

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.

isconf seems to indicate that it will just totally fail in that
scenerio, requiring a fully machine rebuild in order to bring the
machine back under control.

In fact, it seems that isconf will blow up if anybody forgets to make
changes using isconf at all (vs. restoring the machine to the known good
state).

Am I missing something?

M

--3MwIy2ne0vdjdPXF
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)

iD8DBQFE3rOZOtZWu2tc1lARAg0xAJ96ZzyhgR+F8OGCcuUkiLqM73GU2ACggLZb
2+mrt/LrYYH8UQGK1OId+NA=
=mwdf
-----END PGP SIGNATURE-----

--3MwIy2ne0vdjdPXF--