LinuxQuestions.org
Share your knowledge at the LQ Wiki.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 09-25-2017, 03:14 AM   #1
WiseDraco
Member
 
Registered: Nov 2006
Location: Europe,Latvia,Riga
Distribution: slackware,slax, OS X, exMandriva
Posts: 591

Rep: Reputation: 72
slackpkg upgrade-all config file lists who was upgraded?


hello!
i still live on slackware64-current,as it crashes x server time from time, and wait to get stable work someday.
after every crash i do upgrade system to latest via spackpkg, and one thing really piss me off in that:
dialog with what to do with new config files: overwrite, write as .new, and so on.

i always choose "overwrite", and after that i get to
/etc/profile.d/lang.sh to check, it was not overwrited, and my locale was right, and to /etc/mdadm.conf to see, it was my original config ( i have raid1, and if it was overwrited, i do not have rightly mounted raid after restart).
there is a way to see, which configfiles is changed, and overwrited?
 
Old 09-25-2017, 03:31 AM   #2
Didier Spaier
LQ Addict
 
Registered: Nov 2008
Location: Paris, France
Distribution: Slint64-14.2.1.2 on Lenovo Thinkpad W520
Posts: 9,855

Rep: Reputation: Disabled
To list the config files in /etc that have been overwritten during the last 10 days:
Code:
su
find /etc -name "*.orig" -mtime -10
To list the config files in /etc for which an updated version is available, but you didn't decide what to do yet:
Code:
su
find /etc -name "*.new" -mtime -10
Also, if you run -current you should always carefully read the ChangeLog before using slackpkg upgrade.

If you wonder if a specific files was possibly updated you can grep /var/log/removed_scripts.

For instance try:
Code:
grep mdadm.conf /var/log/removed_scripts/*
If you get at least one line of output, then the file was possibly updated (depending on your decision to keep it or not)

Last edited by Didier Spaier; 09-26-2017 at 03:08 AM. Reason: s/input/output/
 
3 members found this post helpful.
Old 09-25-2017, 04:54 AM   #3
WiseDraco
Member
 
Registered: Nov 2006
Location: Europe,Latvia,Riga
Distribution: slackware,slax, OS X, exMandriva
Posts: 591

Original Poster
Rep: Reputation: 72
ok, thanks.
thewre are no more easy option for that?
suppose, option somewhere in slackpkg, for it writes all configfiles, who it plan to overwrite in that case, or so on?
 
Old 09-25-2017, 05:17 AM   #4
Didier Spaier
LQ Addict
 
Registered: Nov 2008
Location: Paris, France
Distribution: Slint64-14.2.1.2 on Lenovo Thinkpad W520
Posts: 9,855

Rep: Reputation: Disabled
Quote:
Originally Posted by WiseDraco View Post
thewre are no more easy option for that?
suppose, option somewhere in slackpkg, for it writes all configfiles, who it plan to overwrite in that case, or so on?
That would actually need a modification of /sbin/installpkg, that installs the .new files case occurring running the script install/doinst.sh in the package. I doubt that the devs would consider this modification worthwhile, but that doesn't prevent you to request it.

What you can do is create a directory in /tmp, download the package there and unpack it with tar or explodepkg, then read the file install/doinst.sh if there is one.

Last edited by Didier Spaier; 09-25-2017 at 05:19 AM.
 
Old 09-25-2017, 06:05 AM   #5
WiseDraco
Member
 
Registered: Nov 2006
Location: Europe,Latvia,Riga
Distribution: slackware,slax, OS X, exMandriva
Posts: 591

Original Poster
Rep: Reputation: 72
Quote:
Originally Posted by Didier Spaier View Post
That would actually need a modification of /sbin/installpkg, that installs the .new files case occurring running the script install/doinst.sh in the package. I doubt that the devs would consider this modification worthwhile, but that doesn't prevent you to request it.

What you can do is create a directory in /tmp, download the package there and unpack it with tar or explodepkg, then read the file install/doinst.sh if there is one.

what is with all another slackpkg users?
after all updates most of us with hands do look, what configs changed?
that was good way to waste our time? :-O
 
Old 09-25-2017, 06:37 AM   #6
Didier Spaier
LQ Addict
 
Registered: Nov 2008
Location: Paris, France
Distribution: Slint64-14.2.1.2 on Lenovo Thinkpad W520
Posts: 9,855

Rep: Reputation: Disabled
Quote:
Originally Posted by WiseDraco View Post
after all updates most of us with hands do look, what configs changed?
that was good way to waste our time? :-O
Don't tell me that you are still not using the --new-config option of slackpkg after having used Slackware since at least seven years. I couldn't believe that.

But if instead you mean that's too much of a hassle to check these .new files, why are you running -current at all?
 
1 members found this post helpful.
Old 09-25-2017, 06:58 AM   #7
WiseDraco
Member
 
Registered: Nov 2006
Location: Europe,Latvia,Riga
Distribution: slackware,slax, OS X, exMandriva
Posts: 591

Original Poster
Rep: Reputation: 72
Quote:
Originally Posted by Didier Spaier View Post
Don't tell me that you are still not using the --new-config option of slackpkg after having used Slackware since at least seven years. I couldn't believe that.

But if instead you mean that's too much of a hassle to check these .new files, why are you running -current at all?

xmm, yes, remember something like that.
try to use that --new-config next time. if i remember correctly, on slackware wiki about system upgrade is something about that?

in last years i try to maximally minimize effort and complexity of maintaining systems.

current -yes, current is ab is mistake in my case.
it was because a long ago ( about slackware 12) i remember, current is pretty good and stable in slackware, and "temporary" install current in work computer, and as most of "temporar" solutions, it going and going...
 
Old 09-25-2017, 07:05 AM   #8
bassmadrigal
LQ Guru
 
Registered: Nov 2003
Location: West Jordan, UT, USA
Distribution: Slackware
Posts: 8,118

Rep: Reputation: 5644Reputation: 5644Reputation: 5644Reputation: 5644Reputation: 5644Reputation: 5644Reputation: 5644Reputation: 5644Reputation: 5644Reputation: 5644Reputation: 5644
Quote:
Originally Posted by WiseDraco View Post
what is with all another slackpkg users?
after all updates most of us with hands do look, what configs changed?
that was good way to waste our time? :-O
Waste our time? Replacing configs blind is a recipe for disaster, or at least mild inconvenience. I absolutely check the diff between every config file to verify if the changes are needed and what they'll replace. This prevents the new-config from overwriting my changes to my conf files, possibly breaking some applications. It is much better for me to spend a few minutes (if that) to verify my configs are the way they should be rather than the much larger amount of time if one of my changes leads to an unbootable machine.

It doesn't take long if you just hit the "p" to prompt you for the changes and hit "d" to check the diff of each one before you decide to overwrite or keep (I never choose merge, figuring I'll manually merge configs if needed).

But then, I'm not running -current, because I don't have the time to manage the constantly changing system (and I don't like rebooting or restarting X and lose my workflow).

In regards to those two files you mentioned, /etc/profile.d/lang.sh and /etc/mdadm.conf, both should have .new files if their programs were upgraded (etc and mdadm respectively). If you were to use new-config and overwrite them, you'd lose your language in the first case, and probably an unbootable system in the second case (assuming your raid is for the system partitions). Luckily for you, those packages haven't changed since April. But if they were to change, and you blindly overwrote their contents, you'd have a borked system.
 
1 members found this post helpful.
Old 09-25-2017, 07:10 AM   #9
Didier Spaier
LQ Addict
 
Registered: Nov 2008
Location: Paris, France
Distribution: Slint64-14.2.1.2 on Lenovo Thinkpad W520
Posts: 9,855

Rep: Reputation: Disabled
Quote:
Originally Posted by WiseDraco View Post
try to use that --new-config next time. if i remember correctly, on slackware wiki about system upgrade is something about that?
Just type
Code:
man slackpkg
and read it carefully. It will always save you a lot of hassle to do that for a command you use. And if this command doesn't have a man page, at least try:
Code:
<command> --help
Also, there is a lot of useful information on https://docs.slackware.com/

Last edited by Didier Spaier; 09-25-2017 at 07:36 AM.
 
Old 09-25-2017, 07:50 AM   #10
Paulo2
Member
 
Registered: Aug 2012
Distribution: Slackware64 -current (started with 13.37(32))
Posts: 676

Rep: Reputation: 313Reputation: 313Reputation: 313Reputation: 313
@bassmadrigal +1
Since slackpkg overwrote my rc.local I choose <prompt> to see what is going on, file by file.
 
1 members found this post helpful.
Old 09-25-2017, 01:52 PM   #11
bormant
Member
 
Registered: Jan 2008
Posts: 401

Rep: Reputation: 223Reputation: 223Reputation: 223
U can select Prompt instead of Overwrite and make individual decision on every file (diff, overwrite, skip, merge).
 
1 members found this post helpful.
  


Reply

Tags
slackpkg


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
slackpkg upgrade-all: comm: file 2 is not in sorted order hba Slackware 7 07-11-2015 10:39 PM
[SOLVED] Can't boot into -current partition after slackpkg upgrade-all, after kernel upgraded gabytf Slackware 7 08-12-2012 10:42 AM
dependency lists w/ slackware slackpkg vendtagain Linux - Newbie 1 12-13-2009 03:51 PM
Will a 'slackpkg upgrade-all overwrite my wireless config? mutexe Slackware 24 08-31-2009 06:44 AM
Upgraded to Kernel ver. 2.6.1 and the config.in file is missing massai Debian 4 01-28-2004 12:50 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 03:05 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration