James wrote: > Alan Mackenzie <acm <at> muc.de> writes: > > >> I'm glad I wrote down my about-to-be-deleted config first. > > An an upgrade to anything that want to modify *.config, > > I so to the dir and save about-2-be-deleted version > of all config files. For example in /etc/cups/ > > printers.conf > printers.conf.31aug11 > printers.conf.5dec10 > printers.conf.6jun2011 > printers.conf.orig (original) > > I could use the optional names during the updates, > but those names are non sensical to me. > > It's saved my bacon on too many occasions, as cups > it not the only brain_dead software and keeping > config records that can be date correlated, helps > on a variety of issues. Occasionally I prune the > files.... I asways use hplip with HP printers. > > > ymmv, > James > > > >
I think dispatch.conf does this automatically. I use it here and it has backups of my config files. Of course, I also keep a backups manually from time to time. Usually if I have a good long uptime and can reboot with no errors, I make a new backup. I have never used dispatch.conf to recover a config tho. OP, you may want to check into this if you do have issues with updates. It may be handy and automatic too. Dale :-) :-) -- I am only responsible for what I said ... Not for what you understood or how you interpreted my words! Miss the compile output? Hint: EMERGE_DEFAULT_OPTS="--quiet-build=n"
