When I boot my SuSE8.1 system, I get this message:
"
Please check the following files (see /var/adm/rpmconfigcheck):
/etc/X11/qtrc.rpmnew
/etc/isdn/isdn.conf.rpmnew
/etc/isdn/isdn.conf.rpmsave
/etc/samba/smb.conf.rpmnew
"
Since I am fairly new to Linux, I have no idea if this is serious, or
what I should do to fix it. Any help is welcome.
--
Frits Wüthrich
On Sunday 27 April 2003 08:31, Frits Wüthrich wrote:
When I boot my SuSE8.1 system, I get this message:
" Please check the following files (see /var/adm/rpmconfigcheck): /etc/X11/qtrc.rpmnew /etc/isdn/isdn.conf.rpmnew /etc/isdn/isdn.conf.rpmsave /etc/samba/smb.conf.rpmnew "
Since I am fairly new to Linux, I have no idea if this is serious, or what I should do to fix it. Any help is welcome.
-- Frits Wüthrich
===================
Frits, These are backups of files that have been replaced during an update or upgrade of some of your programs, etc. I believe it also mentions to check these against the new files for anything you need out of the old ones and delete them if all is behaving/working ok for you. Or it may not, that may be something I read in the books that came with my SuSE. ;o) Yes, I do read the manuals! :o) If everything on your system is working ok, then it is probably safe to remove those files to make the list go away on boot up. Patrick -- --- KMail v1.5.9.1i --- SuSE Linux Pro v8.2 --- Registered Linux User #225206 On any other day, that might seem strange...
On Sunday 27 April 2003 5:57 pm, O'Smith wrote:
On Sunday 27 April 2003 08:31, Frits Wüthrich wrote:
When I boot my SuSE8.1 system, I get this message:
" Please check the following files (see /var/adm/rpmconfigcheck): /etc/X11/qtrc.rpmnew /etc/isdn/isdn.conf.rpmnew /etc/isdn/isdn.conf.rpmsave /etc/samba/smb.conf.rpmnew "
Since I am fairly new to Linux, I have no idea if this is serious, or what I should do to fix it. Any help is welcome.
-- Frits Wüthrich
===================
Frits, These are backups of files that have been replaced during an update or upgrade of some of your programs, etc. I believe it also mentions to check these against the new files for anything you need out of the old ones and delete them if all is behaving/working ok for you. Or it may not, that may be something I read in the books that came with my SuSE. ;o) Yes, I do read the manuals! :o)
If everything on your system is working ok, then it is probably safe to remove those files to make the list go away on boot up.
Patrick -- --- KMail v1.5.9.1i --- SuSE Linux Pro v8.2 --- Registered Linux User #225206 On any other day, that might seem strange...
Thanks for this Patrick, I had Frits' question at the back of my mind for a week. Having looked at them, I think you are right they relate to an upgrade, but AFAICT, the files are related to user config files which were already in the system prior to an update, and are what a fresh install would supply. ie they are not replaced files, they are candidate replacement files. I shall remove these case by case, after evaluation. regards Vince Littler
On Sunday 27 April 2003 20:20, Vince Littler wrote:
Thanks for this Patrick, I had Frits' question at the back of my mind for a week. Having looked at them, I think you are right they relate to an upgrade, but AFAICT, the files are related to user config files which were already in the system prior to an update, and are what a fresh install would supply. ie they are not replaced files, they are candidate replacement files.
They are both. rpmnew is a "candidate replacement" file, as you say, but .rpmsave is a config file from the old package which was edited since the package was originally installed, and thus copied for backup by the upgrade
On Sunday 27 April 2003 20:20, Vince Littler wrote:
Thanks for this Patrick, I had Frits' question at the back of my mind for a week. Having looked at them, I think you are right they relate to an upgrade, but AFAICT, the files are related to user config files which were already in the system prior to an update, and are what a fresh install would supply. ie they are not replaced files, they are candidate replacement files.
They are both. rpmnew is a "candidate replacement" file, as you say, but .rpmsave is a config file from the old package which was edited since the package was originally installed, and thus copied for backup by the upgrade Thanks for all the contributions. I noticed over time I was getting more of these messages. As I have done some upgrading over time, some through YOU and some outside, I guess that is where they came from. I move all these files to a seperate directory I created under my home
On Sun, 2003-04-27 at 22:09, Anders Johansson wrote:
directory, so if needed I can place them back.
--
Frits Wüthrich
The 03.04.27 at 23:05, Frits Wüthrich wrote:
They are both. rpmnew is a "candidate replacement" file, as you say, but .rpmsave is a config file from the old package which was edited since the package was originally installed, and thus copied for backup by the upgrade Thanks for all the contributions. I noticed over time I was getting more of these messages. As I have done some upgrading over time, some through YOU and some outside, I guess that is where they came from. I move all these files to a seperate directory I created under my home directory, so if needed I can place them back.
Note that *.rpmnew refer to configuration files not updated; ie, the original was left intact when the package was updated (it should happen only if you had modified the original, compared with the file contained on the old rpm). Thus, new options of the new version of the package are not configured/enabled. You should check those files. On the other hand, *.rpmsave means that your file was replaced, and saved. You should also manually check if that is ok. -- Cheers, Carlos Robinson
participants (5)
-
Anders Johansson
-
Carlos E. R.
-
Frits Wüthrich
-
O'Smith
-
Vince Littler