Mick wrote: > On Wednesday, 29 May 2019 23:23:58 BST Dale wrote: >> n952...@web.de wrote: >>> And, what are the consequences that I'm suffering, that I haven't done >>> that before, for over a year?> >>>> Gesendet: Mittwoch, 29. Mai 2019 um 23:55 Uhr >>>> Von: n952...@web.de >>>> An: gentoo-user@lists.gentoo.org >>>> Betreff: updating /etc/package.accept_keywords >>>> >>>> I have many files like ._cfg0000_package.accept_keywords. >>>> Is the right way to handle this to do something like: >>>> >>>> sort -u ._cfg????_package.accept_keywords >| package.accept_keywords >> Look into etc-update, dispatch-conf and other commands that help with >> updating those. I admit, I'm bad to let them sit to because I usually >> manually update important stuff. I don't wait that long tho. Keep in >> mind, there is a small chance that a bad config could result in >> something not working when you reboot or not being able to completely >> boot at all. It depends on what files are not updated. >> >> Hope that helps. >> >> Dale >> >> :-) :-) > I always run etc-update or dispatch-conf to see what the changes in default > config files may be and invariably accept or merge the changes with my > version > of the config files each time. If I am in a rush and the changes are not > trivial, I will leave this for a day in the near future and avoid restarting > the service affected. However, I would not leave a remote server in this > state in case an unintended reboot causes some critical service to fail to > restart, e.g. network, sshd, etc. >
This is good advice. I sometimes look to see if there is anything important to the changes. Most of the time, it is mostly the date or something at the top, sometimes it even detects that and just does it itself. Thing is, sometimes I just don't have time to wade through a somewhat large file with a lot of changes that may not be important or even worse, will change settings I made back to defaults that don't work. Some files I let sit until I can figure out if I need them updated or not. I'm fond of the zap new button. A prime example, KDE config files. I have my desktop set up like I like it. If I update the config file, it usually sets it back to the default. That's one I like to spend time on if I update it. Another is my network configs. Some settings are done differently and won't work if I use the updated file or it resets to default. I use the dispatch one because it is better. No matter what I attempt tho, I can not figure out how to use that dang merge thing. I wish there was a GUI tool to do this. Maybe that would help. Of course, someone will likely post that there is a GUI tool and then I'll wonder how I missed it. ROFL You can bet I'd use it tho. On a remote server, yea, it is certainly best to finish the entire update process before stopping. That could be bad. Dale :-) :-)
