Like a rollback mechanism? Last known good? Or just a place to store the old versions. RedHat recently introduced a rollback mechanism/repository for RPM. you have to install the RPM with the proper switches and have the repository ready. I read about it in Linux Journal.
Brian Kelsay
Gerald Combs <> 03/24/05 08:31AM >>>
Brian Kelsay wrote:
Get with Cymor and interrogate him about what Debian does exactly. When I do an upgrade, if a package has a config file and the author has added new default features, the apt/dpkg system compares it to your config file to see if you have customized it yet. I've been told the best thing to do is to say no to an update of the config file to preserve your changes. I have chosen on one box to look at the changes, but got a bit lost. I assume that once you are familiar w/ a given pkg, you could change this stuff on the fly to get new features.
Gentoo does this too, in its own annoying way. What I want is something that will automatically detect when I make a change to a given file in /etc, and check that change into SVN. That way I can see all the changes that have been made to a configuration file, and revert back to a specific revision if needed.
Like CiscoWorks Resource Manager Essentials. Any time anyone makes a change to a router configuration, RME saves off a copy of the config, along with other information (such as who made the change). It lets you compare different config versions, see who made what changes, and revert to a previous config.
Brian Kelsay wrote:
Like a rollback mechanism? Last known good? Or just a place to store the old versions. RedHat recently introduced a rollback mechanism/repository for RPM. you have to install the RPM with the proper switches and have the repository ready. I read about it in Linux Journal.
Brian Kelsay
Gerald Combs <> 03/24/05 08:31AM >>>
Brian Kelsay wrote:
Get with Cymor and interrogate him about what Debian does exactly. When I do an upgrade, if a package has a config file and the author has added new default features, the apt/dpkg system compares it to your config file to see if you have customized it yet. I've been told the best thing to do is to say no to an update of the config file to preserve your changes. I have chosen on one box to look at the changes, but got a bit lost. I assume that once you are familiar w/ a given pkg, you could change this stuff on the fly to get new features.
Gentoo does this too, in its own annoying way. What I want is something that will automatically detect when I make a change to a given file in /etc, and check that change into SVN. That way I can see all the changes that have been made to a configuration file, and revert back to a specific revision if needed.
Kclug mailing list Kclug@kclug.org http://kclug.org/mailman/listinfo/kclug
Quoting Brian Kelsay Brian.Kelsay@kcc.usda.gov:
Like a rollback mechanism? Last known good? Or just a place to store the old versions. RedHat recently introduced a rollback mechanism/repository for RPM. you have to install the RPM with the proper switches and have the repository ready. I read about it in Linux Journal.
Interesting. The up2date application has supported roll back for years, but you've got to have the disk space to save older versions of everything. I've got servers configured to use rollback, but I've never needed it yet.
-- Dave Hull http://insipid.com
-
Brian Kelsay -
Dave Hull -
Gerald Combs