Smart and "ldconfig && SuSEconfig "
Learned in the past weeks that it is necessary to run SuSEconfig after using Smart. During my DOS days I would have made a batfile where Smart would be followed by SuSEconfig. Could that be done easily in Suse 10.1? What wonders me is the instruction in one of the email's to use "ldconfig && SuSEconfig" From the short timespan I used Red Hat (RH 5.2) I remember ldconfig but since my happy Suse years I can't remember using ldconfig. What is the background of the combined instruction? Ldconfig does not do anything visual on my system. SuSEconfig does ;). -- Linux User 183145
On Tuesday 24 October 2006 08:07, C. Brouerius van Nidek wrote:
Learned in the past weeks that it is necessary to run SuSEconfig after using Smart. During my DOS days I would have made a batfile where Smart would be followed by SuSEconfig. Could that be done easily in Suse 10.1?
What wonders me is the instruction in one of the email's to use "ldconfig && SuSEconfig" From the short timespan I used Red Hat (RH 5.2) I remember ldconfig but since my happy Suse years I can't remember using ldconfig. What is the background of the combined instruction? Ldconfig does not do anything visual on my system. SuSEconfig does ;).
Hi Constant, ldconfig is sort of 'masked' behind the GUI... it says something like "preparing linker cache"... but ldconfig and SuSEconfig are run every single time packages or updates are installed with YaST/YOU. regards, Carl
Carl Hartung wrote:
On Tuesday 24 October 2006 08:07, C. Brouerius van Nidek wrote:
Learned in the past weeks that it is necessary to run SuSEconfig after using Smart. During my DOS days I would have made a batfile where Smart would be followed by SuSEconfig. Could that be done easily in Suse 10.1?
What wonders me is the instruction in one of the email's to use "ldconfig && SuSEconfig" From the short timespan I used Red Hat (RH 5.2) I remember ldconfig but since my happy Suse years I can't remember using ldconfig. What is the background of the combined instruction? Ldconfig does not do anything visual on my system. SuSEconfig does ;).
Hi Constant,
ldconfig is sort of 'masked' behind the GUI... it says something like "preparing linker cache"... but ldconfig and SuSEconfig are run every single time packages or updates are installed with YaST/YOU.
regards,
Carl
I have a smupdate.sh which executes this line "smart upgrade --update && ldconfig && SuSEconfig"
On Tuesday 24 October 2006 07:07, C. Brouerius van Nidek wrote:
Learned in the past weeks that it is necessary to run SuSEconfig after using Smart. During my DOS days I would have made a batfile where Smart would be followed by SuSEconfig. Could that be done easily in Suse 10.1?
I've edited my KDE menu entry for Smart GUI to be: smart --gui && ldconfig && SuSEconfig That way when I exit smart I know that ldconfig and SuSEconfig are run. There aren't any visual or audio notifications of success (failure may pop up a text window with errors?). htop shows the processes running. The HDD activity LEDs light up. Wait a few minutes for it to finish... You can also run ldconfig && SuSEconfig in a konsole, as root, while smart is idle. I do this if there are lots of KDE updates as well as others and am getting repository errors or slow Internet or dependency issues, etc.
What wonders me is the instruction in one of the email's to use "ldconfig && SuSEconfig" From the short timespan I used Red Hat (RH 5.2) I remember ldconfig but since my happy Suse years I can't remember using ldconfig. What is the background of the combined instruction? Ldconfig does not do anything visual on my system. SuSEconfig does ;).
Linux User 183145
Carl is correct that YaST Software Install runs ldconfig prior to running SuSEconfig as part of its normal process whenever you add/remove software. Synaptic for SUSE also did this after every add/remove software session. Smart may do this with openSUSE sometime in the future. I believe the smart developer(s) are aware of this need for SUSE. Stan
* Stan Glasoe
Carl is correct that YaST Software Install runs ldconfig prior to running SuSEconfig as part of its normal process whenever you add/remove software. Synaptic for SUSE also did this after every add/remove software session.
Smart may do this with openSUSE sometime in the future. I believe the smart developer(s) are aware of this need for SUSE.
Some versions, I have smart-0.42-67.1, do run SuSEconfig in particular cases, ie: postfix, apache, php5...., but I do not know about ldconfig. -- Patrick Shanahan Registered Linux User #207535 http://wahoo.no-ip.org @ http://counter.li.org HOG # US1244711 Photo Album: http://wahoo.no-ip.org/gallery2
On Tuesday 24 October 2006 8:07 am, C. Brouerius van Nidek wrote:
Learned in the past weeks that it is necessary to run SuSEconfig after using Smart. During my DOS days I would have made a batfile where Smart would be followed by SuSEconfig. Could that be done easily in Suse 10.1?
What wonders me is the instruction in one of the email's to use "ldconfig && SuSEconfig" From the short timespan I used Red Hat (RH 5.2) I remember ldconfig but since my happy Suse years I can't remember using ldconfig. What is the background of the combined instruction? Ldconfig does not do anything visual on my system. SuSEconfig does ;).
SuSEconfig runs ldconfig. ;) Smart runs SuSEconfig WHEN it's needed, and not auto when it gets done. Fred -- MickySoft, the ultimate corporate parasite.
On Tuesday 24 October 2006 18:16, Fred A. Miller wrote:
On Tuesday 24 October 2006 8:07 am, C. Brouerius van Nidek wrote:
Learned in the past weeks that it is necessary to run SuSEconfig after using Smart. During my DOS days I would have made a batfile where Smart would be followed by SuSEconfig. Could that be done easily in Suse 10.1?
What wonders me is the instruction in one of the email's to use "ldconfig && SuSEconfig" From the short timespan I used Red Hat (RH 5.2) I remember ldconfig but since my happy Suse years I can't remember using ldconfig. What is the background of the combined instruction? Ldconfig does not do anything visual on my system. SuSEconfig does ;).
SuSEconfig runs ldconfig. ;) Smart runs SuSEconfig WHEN it's needed, and not auto when it gets done.
A 'cat /sbin/SuSEconfig | grep ldconfig' comes back empty, Fred. I'm running 10.0, if that matters. Carl
* Carl Hartung
On Tuesday 24 October 2006 18:16, Fred A. Miller wrote:
SuSEconfig runs ldconfig. ;) Smart runs SuSEconfig WHEN it's needed, and not auto when it gets done.
A 'cat /sbin/SuSEconfig | grep ldconfig' comes back empty, Fred. I'm running 10.0, if that matters.
Not sure that SuSEconfig ever ran ldconfig. Yast ran both when doing software install/removal.
From reading about the development of 10.2 and future, I believe that SuSEconfig scripts are being reduced, removed and combined in an effort to reduce the system time usage.
-- Patrick Shanahan Registered Linux User #207535 http://wahoo.no-ip.org @ http://counter.li.org HOG # US1244711 Photo Album: http://wahoo.no-ip.org/gallery2
On Tuesday 24 October 2006 6:29 pm, Carl Hartung wrote:
On Tuesday 24 October 2006 18:16, Fred A. Miller wrote:
On Tuesday 24 October 2006 8:07 am, C. Brouerius van Nidek wrote:
Learned in the past weeks that it is necessary to run SuSEconfig after using Smart. During my DOS days I would have made a batfile where Smart would be followed by SuSEconfig. Could that be done easily in Suse 10.1?
What wonders me is the instruction in one of the email's to use "ldconfig && SuSEconfig" From the short timespan I used Red Hat (RH 5.2) I remember ldconfig but since my happy Suse years I can't remember using ldconfig. What is the background of the combined instruction? Ldconfig does not do anything visual on my system. SuSEconfig does ;).
SuSEconfig runs ldconfig. ;) Smart runs SuSEconfig WHEN it's needed, and not auto when it gets done.
A 'cat /sbin/SuSEconfig | grep ldconfig' comes back empty, Fred. I'm running 10.0, if that matters.
'Don't know if that matters or not. I've noted OFTEN that SuSEconfig is run via Smart during the install process. Fred -- MickySoft, the ultimate corporate parasite.
On Wednesday 25 October 2006 00:16, Fred A. Miller wrote:
On Tuesday 24 October 2006 8:07 am, C. Brouerius van Nidek wrote:
Learned in the past weeks that it is necessary to run SuSEconfig after using Smart. During my DOS days I would have made a batfile where Smart would be followed by SuSEconfig. Could that be done easily in Suse 10.1?
What wonders me is the instruction in one of the email's to use "ldconfig && SuSEconfig" From the short timespan I used Red Hat (RH 5.2) I remember ldconfig but since my happy Suse years I can't remember using ldconfig. What is the background of the combined instruction? Ldconfig does not do anything visual on my system. SuSEconfig does ;).
SuSEconfig runs ldconfig.
Where? YaST runs it, as part of inst_suseconfig, but I don't see it in suseconfig proper I think the trend is to move stuff like that into postinstall scripts of the rpms that actually need it
On Tuesday 24 October 2006 6:39 pm, Anders Johansson wrote:
On Wednesday 25 October 2006 00:16, Fred A. Miller wrote:
On Tuesday 24 October 2006 8:07 am, C. Brouerius van Nidek wrote:
Learned in the past weeks that it is necessary to run SuSEconfig after using Smart. During my DOS days I would have made a batfile where Smart would be followed by SuSEconfig. Could that be done easily in Suse 10.1?
What wonders me is the instruction in one of the email's to use "ldconfig && SuSEconfig" From the short timespan I used Red Hat (RH 5.2) I remember ldconfig but since my happy Suse years I can't remember using ldconfig. What is the background of the combined instruction? Ldconfig does not do anything visual on my system. SuSEconfig does ;).
SuSEconfig runs ldconfig.
Where? YaST runs it, as part of inst_suseconfig, but I don't see it in suseconfig proper
Ok.....could be wrong about that. I'm certain it used to, so assumed it still did.
I think the trend is to move stuff like that into postinstall scripts of the rpms that actually need it.
Ah......ok. Maybe that's why I see it run on occassion in Smart. Fred -- MickySoft, the ultimate corporate parasite.
participants (7)
-
Anders Johansson -
C. Brouerius van Nidek -
Carl Hartung -
Fred A. Miller -
Jan Karjalainen -
Patrick Shanahan -
Stan Glasoe