Re: Linuxconf not losing info.
Craig Sanders <firstname.lastname@example.org> wrote:
> On Tue, 2 Jun 1998, Shaya Potter wrote:
> > I believe linuxconf will version every change that it makes, i.e. if you
> > make changes w/ linuxconf and see that it didn't work, you can go back to
> > your previous configuration or any one of many previous configurations, this
> > will probably work if you edited it outside of linuxconf, you then edited
> > the file manually, and then went into linuxconf, somehow or another
> > linuxconf messed up the file (though when I was playing with it last year,
> > it couldn't grok our dns setup, and just complained, didn't mess with it),
> > you should theoreticly be able to go back to the version you modified by
> > hand, because linuxconf should have saved it before modifying the file.
> good. i like the sound of that.
Yes, I like it too. I've always think that versioning would really
improve dpkg's handling of config files. I've always dreamt about
dpkg merging original package config files with local ones using
common ancestor merge. Or running one of those nice file mergers
instead of asking you to press some key to leave dpkg and fix the
situation by hand. That would be really neat, I'm sure...
> does it use RCS or similar to store the previous versions? if not, how
> hard would it be to make it do so?
>From what I heard in the Linuxconf mailing list some time ago (I'm not
subscribed these days) it thing yes, it uses RCS. It seems to me it
is able of doing things as nice as letting you keep many different
sets of config files for different purposes, and change between them
on the fly with automatic activation and deactivation of the affected
daemons. Way cool.
Martin A. Soto J. Profesor
Departamento de Ingenieria de Sistemas y Computacion
Universidad de los Andes email@example.com
To UNSUBSCRIBE, email to firstname.lastname@example.org
with a subject of "unsubscribe". Trouble? Contact email@example.com