Slackware This Forum is for the discussion of Slackware Linux.
|
| Notices |
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
 |
GNU/Linux Basic Guide
This 255-page guide will provide you with the keys to understand the philosophy of free software, teach you how to use and handle it, and give you the tools required to move easily in the world of GNU/Linux. Many users and administrators will be taking their first steps with this GNU/Linux Basic guide and it will show you how to approach and solve the problems you encounter.
Click Here to receive this Complete Guide absolutely free. |
|
 |
03-02-2009, 01:27 AM
|
#1
|
|
Member
Registered: Feb 2007
Location: Washington state, USA
Distribution: Fedora 13, SUSE 11, Ubuntu 10.04, Mandriva 2010, Mint 8
Posts: 333
Rep:
|
keep old or install new configuration files during slackpkg upgrade-all ?
Is it best to keep the old, or overwrite with the new configuration files which are found during a "slackpkg upgrade-all", run in a terminal as root for the newer software packages? First "slackpkg update" is run, and then I run; "slackpkg install-new", and last that upgrade-all command. And here is that tool; http://sourceforge.net/projects/slackpkg/
|
|
|
|
03-02-2009, 02:23 AM
|
#2
|
|
Senior Member
Registered: Mar 2004
Location: Westray, Orkney
Distribution: Slackware64-14.0 (multi-lib)
Posts: 1,319
Rep: 
|
It depends if you have modified any of the configuration files. Slackpkg gives you the option to prompt for each file and to look at the differences. This will give you the information you need to make your decision.
samac
|
|
|
|
03-02-2009, 02:52 AM
|
#3
|
|
Member
Registered: Feb 2007
Location: Washington state, USA
Distribution: Fedora 13, SUSE 11, Ubuntu 10.04, Mandriva 2010, Mint 8
Posts: 333
Original Poster
Rep:
|
I did try the prompt option, and then the (D)differences option for the first package. Then I could not enter any more commands in that terminal window since the "user-name#" cursor was not there to type, it just had a small box at the bottom of the terminal, so it was like stuck then ?
|
|
|
|
03-02-2009, 03:32 AM
|
#4
|
|
Senior Member
Registered: Mar 2004
Location: Westray, Orkney
Distribution: Slackware64-14.0 (multi-lib)
Posts: 1,319
Rep: 
|
at that point you decide whether to keep or overwrite. I usually keep the old file and merge in any changes by text editor.
samac
|
|
|
|
03-02-2009, 03:37 AM
|
#5
|
|
Senior Member
Registered: Jun 2006
Location: Philadelphia PA USA
Distribution: Lubuntu, Slackware
Posts: 2,121
|
To find all the .new config files run:
Code:
find /etc -name "*.new"
To update the .new files run:
Code:
mv /etc/file_name.new /etc/file_name
|
|
|
|
03-02-2009, 04:04 AM
|
#6
|
|
Senior Member
Registered: Mar 2007
Location: Rio de Janeiro - Brazil
Distribution: Slackware64-current
Posts: 1,003
Rep:
|
Or, if you skipped some .new files (used the option "K"eep), you can let slackpkg search for them again later with
Code:
slackpkg new-config
|
|
|
|
03-02-2009, 10:51 AM
|
#7
|
|
Member
Registered: May 2005
Location: Leicester,UK
Distribution: Slackware
Posts: 108
Rep:
|
Personally I always keep the configs. Those configs that are unchanged between the new and the old packages are merged in principle anyway (see the doinst config() function in most packages).
Other than that, like I said, I keep the configs and as root I run `find /etc/ -name "*.new"' and diff all files by hand and then decide if they need to move over. I have found that colordiff (available at SlackBuilds.org) really makes things easier on my eyes there as well.
|
|
|
|
| Thread Tools |
Search this Thread |
|
|
|
Posting Rules
|
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
HTML code is Off
|
|
|
All times are GMT -5. The time now is 05:26 AM.
|
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|