new configuration files installed...

paranoid_penguin · 07-09-2016, 12:06 PM

Code:

Searching for NEW configuration files

Some packages had new configuration files installed.
You have four choices:

	(K)eep the old files and consider .new files later

	(O)verwrite all old files with the new ones. The
	   old files will be stored with the suffix .orig

	(R)emove all .new files

	(P)rompt K, O, R selection for every single file
	
What do you want (K/O/R/P)?

how to act ?

thanks in advance !

montagdude · 07-09-2016, 12:20 PM

I usually use the P option. That way it will prompt you for each file and you can decide from there. If it's a file I haven't changed, I let it overwrite it, but if I have changed it, I usually keep the old one and merge in any changes from the *.new manually.

Didier Spaier · 07-09-2016, 12:20 PM

Quote:

Originally Posted by paranoid_penguin

Code:

Searching for NEW configuration files

Some packages had new configuration files installed.
You have four choices:

    (K)eep the old files and consider .new files later

    (O)verwrite all old files with the new ones. The
       old files will be stored with the suffix .orig

    (R)emove all .new files

    (P)rompt K, O, R selection for every single file
    
What do you want (K/O/R/P)?

how to act ?

thanks in advance !

Type p.

allend · 07-09-2016, 12:40 PM

My first response is to hit 'p' for prompt.
As each .new file is presented, I choose to view the diff.
My action then varies.
If the diff involves changes to local settings (e.g. location customisation or inittab), I remove the incoming .new file.
If the diff involves changes to daemons that I do not use, I overwrite the existing file.
If the diff involves changes to daemons that I do use, I will either overwrite the existing file or keep the incoming .new file (which I later inspect against the existing using "vimdiff').

You can run 'slackpkg new-config' multiple times after an upgrade in -current, to cycle through the incoming .new files.

Paulo2 · 07-09-2016, 12:48 PM

Same as montagdude, "(P)rompt K, O, R selection for every single file"
If it is a .new file of something that I don't use or I know that I didn't edit the ".old" file, I just overwrite.
Others .new files I run kompare to see what changed.

przemo · 07-10-2016, 10:06 AM

that is with .new files but how to treat .orig files in /etc/rc.d/ ????

glorsplitz · 07-10-2016, 11:07 AM

Quote:

Originally Posted by przemo

that is with .new files but how to treat .orig files in /etc/rc.d/ ????

I diff them to the one in use and compare the differences, like diff /etc/rc.d/rc.local /etc/rc.d/rc.local.orig.

przemo · 07-10-2016, 12:03 PM

sorry for that question but i am not familiar with diff tool and i think i should chenge it
i have read man but still....

for example :

Code:

diff /etc/rc.d/rc.cgred /etc/rc.d/rc.cgred.orig 
46,47c46,47
< if [ -f $CGRED_CONF ] ; then
<       . $CGRED_CONF
---
> if [ -f "/etc/sysconfig/cgred.conf" ] ; then
>       . /etc/sysconfig/cgred.conf
75,76c75,79
<       num=`grep "cgroup" /proc/mounts | awk '$3=="cgroup"' | wc -l`
<       if [ $num -eq 0 ]; then
---
>       if [ ! -s $CGRED_CONF ]; then
>               echo "not configured"
>               return 6
>       fi
>       if ! grep "^cgroup" /proc/mounts &>/dev/null; then

how i should read that ???

ok i got it now, /etc/sysconfig/cgred.conf is merged to /etc/cgrules.conf

smart tool that diff ;-) good to know it.