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 03-18-2013, 06:56 PM   #1
papazulu
LQ Newbie
 
Registered: Mar 2013
Posts: 3

Rep: Reputation: Disabled
After slackpkg upgrade, (K)eep, (O)verwrite, (R)emove, or (P)rompt?


After running upgrade scripts slackware offers following. Which should I choose?:

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)?
 
Old 03-18-2013, 07:05 PM   #2
ponce
Senior Member
 
Registered: Aug 2004
Location: Pisa, Italy
Distribution: Slackware
Posts: 2,460

Rep: Reputation: 888Reputation: 888Reputation: 888Reputation: 888Reputation: 888Reputation: 888Reputation: 888
go for prompt and it will ask you for the modified files.

if you haven't customized anything you can overwrite the proposed file: if you are in doubt, select diff and see if you have made modifications that you want to preserve.

in the case you have customized the file you can delete the new one if it doesn't introduce new things/options: if it does maybe is better to keep it and re-customize the new later.
 
Old 03-18-2013, 08:21 PM   #3
michaelslack
Member
 
Registered: Feb 2013
Location: Sydney
Distribution: slackware
Posts: 85

Rep: Reputation: 34
A good example where I got caught out here: I have been mucking around a bit with php. To get it working (just locally), among other things you uncomment out the line

Code:
Include /etc/httpd/mod_php.conf
in /etc/httpd/httpd.conf

Now recently there was a security upgrade of httpd in slackware-14.0 which I implemented using slackpkg and I wasn't careful and I ended up replacing my /etc/httpd/httpd.conf with a fresh new one, which of course had the line above commented out again.

This is the kind of thing to keep in mind at that stage of slackpkg!

Cheers,

Michael
 
Old 03-18-2013, 08:25 PM   #4
zbreaker
Member
 
Registered: Dec 2008
Location: New York
Distribution: Slack -current, #!, vsido
Posts: 223

Rep: Reputation: 27
If your running a conservative system, I've never gone wrong with the overwrite option for the upgraded packages.
 
  


Reply


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
[SOLVED] After upgrade all using slackpkg upgrade, configuration is failed to read ethereal1m Linux - Newbie 3 04-28-2010 01:03 AM
slackpkg upgrade-all does not show an upgrade sycamorex Slackware 6 11-03-2009 05:29 AM
slackpkg upgrade matter zbreaker Slackware 6 04-01-2009 01:52 AM
Upgrade with slackpkg STARHARVEST Slackware 11 05-17-2008 07:07 PM
slackpkg upgrade _mu_ Slackware 9 01-29-2004 08:28 PM


All times are GMT -5. The time now is 06:04 PM.

Main Menu
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
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration