/usr/local/lib ? do I need to manually update the cache?
On 15.1 and 15.2 both, ld.so.conf contains: # cat /etc/ld.so.conf /usr/local/lib64 /usr/local/lib include /etc/ld.so.conf.d/*.conf # /lib64, /lib, /usr/lib64 and /usr/lib gets added # automatically by ldconfig after parsing this file. # So, they do not need to be listed. On 15.1 - long-running system: # ldconfig -p | grep local libbwbemag.so (libc6,x86-64) => /usr/local/lib/libbwbemag.so libbulwark.so (libc6,x86-64) => /usr/local/lib/libbulwark.so On 15.2, newly booted, 'ldconfig -p' shows nothing. I have copied some new libs to /usr/local/lib, do I now need to rebuild/update the cache manually? I ran 'ldconfig' and now the cache is fine. I feel like I must be missing something. -- Per Jessen, Zürich (17.1°C) http://www.hostsuisse.com/ - virtual servers, made in Switzerland.
On 31/03/2021 12.19, Per Jessen wrote:
I ran 'ldconfig' and now the cache is fine. I feel like I must be missing something.
My notes say that ldconfig has to be run after installing libraries. -- Cheers / Saludos, Carlos E. R. (from 15.2 x86_64 at Telcontar)
On 3/31/21 5:19 AM, Per Jessen wrote:
On 15.2, newly booted, 'ldconfig -p' shows nothing. I have copied some new libs to /usr/local/lib, do I now need to rebuild/update the cache manually?
I ran 'ldconfig' and now the cache is fine.
That's how you do it. If zypper or rpm installs a new lib, it calls ldconfig behind the scene. If you install a lib, well... it's up to you to do it... -- David C. Rankin, J.D.,P.E.
David C. Rankin wrote:
On 3/31/21 5:19 AM, Per Jessen wrote:
On 15.2, newly booted, 'ldconfig -p' shows nothing. I have copied some new libs to /usr/local/lib, do I now need to rebuild/update the cache manually?
I ran 'ldconfig' and now the cache is fine.
That's how you do it.
If zypper or rpm installs a new lib, it calls ldconfig behind the scene. If you install a lib, well... it's up to you to do it...
I guess it's been too long since I did it, must have forgotten. Thanks David and Carlos. -- Per Jessen, Zürich (10.8°C) http://www.cloudsuisse.com/ - your owncloud, hosted in Switzerland.
On 01/04/2021 08.24, Per Jessen wrote:
David C. Rankin wrote:
On 3/31/21 5:19 AM, Per Jessen wrote:
On 15.2, newly booted, 'ldconfig -p' shows nothing. I have copied some new libs to /usr/local/lib, do I now need to rebuild/update the cache manually?
I ran 'ldconfig' and now the cache is fine.
That's how you do it.
If zypper or rpm installs a new lib, it calls ldconfig behind the scene. If you install a lib, well... it's up to you to do it...
I guess it's been too long since I did it, must have forgotten. Thanks David and Carlos.
I also forgot, I have not done that in ages. Which is why I searched my notees ;-) I have a file, named "programs_for.txt" which contains a list of programs and a short description of what they are for. -- Cheers / Saludos, Carlos E. R. (from 15.2 x86_64 at Telcontar)
On 4/1/21 4:21 AM, Carlos E. R. wrote:
I guess it's been too long since I did it, must have forgotten. Thanks David and Carlos.
I also forgot, I have not done that in ages. Which is why I searched my notees ;-)
I have a file, named "programs_for.txt" which contains a list of programs and a short description of what they are for.
In the old days, we learned how to manage Linux. It was all done via text config files and short utility commands. There was one way of doing things (recall make mrproper?). Over the years different apps and installers came along that would automate much of the manual config maintenance and executed the short utilities to tidy up for you -- for their specific app or part of Linux. That thinking has proliferated over the past 20 years. We have somewhat screwed ourselves in that regard. Now we have a hodgepodge of some 5,000 apps that implement some aspect of configuration of their own app and the required libraries. We have systemd that tries to automate a great deal. Then there is the alternatives framework, wicked, zypper and YAST above that, drakut, network manager, etc... The one config where automation has been stunning is X. No more crafting modelines with xvidtune to transfer to xorg.conf -- it all works by automated defaults (most of the time) So instead of learning how to admin Linux, much effort is now spent trying to keep track of what each of the new great automated tools does and does not do for you. Don't get me wrong, I'm not against the automation. Much of the automation provides a net time savings over doing it from scratch, but it has made Linux less about Linux and more about what tools your distro uses to admin it. I do find I actually like to know what config value in which file I'm setting rather than learning which radio button on what page of the GUI helper to check.... In using just about all distros, I'm not sure which is actually the easier route. It has been an interesting ride. -- David C. Rankin, J.D.,P.E.
On 01/04/2021 20.25, David C. Rankin wrote:
On 4/1/21 4:21 AM, Carlos E. R. wrote:
I guess it's been too long since I did it, must have forgotten. Thanks David and Carlos.
I also forgot, I have not done that in ages. Which is why I searched my notees ;-)
I have a file, named "programs_for.txt" which contains a list of programs and a short description of what they are for.
In the old days, we learned how to manage Linux. It was all done via text config files and short utility commands. There was one way of doing things (recall make mrproper?).
Indeed I do. Very dangerous.
Over the years different apps and installers came along that would automate much of the manual config maintenance and executed the short utilities to tidy up for you -- for their specific app or part of Linux.
That thinking has proliferated over the past 20 years. We have somewhat screwed ourselves in that regard. Now we have a hodgepodge of some 5,000 apps that implement some aspect of configuration of their own app and the required libraries. We have systemd that tries to automate a great deal. Then there is the alternatives framework, wicked, zypper and YAST above that, drakut, network manager, etc...
The one config where automation has been stunning is X. No more crafting modelines with xvidtune to transfer to xorg.conf -- it all works by automated defaults (most of the time)
So instead of learning how to admin Linux, much effort is now spent trying to keep track of what each of the new great automated tools does and does not do for you.
Don't get me wrong, I'm not against the automation. Much of the automation provides a net time savings over doing it from scratch, but it has made Linux less about Linux and more about what tools your distro uses to admin it. I do find I actually like to know what config value in which file I'm setting rather than learning which radio button on what page of the GUI helper to check....
Yes, there is that...
In using just about all distros, I'm not sure which is actually the easier route. It has been an interesting ride.
-- Cheers / Saludos, Carlos E. R. (from 15.2 x86_64 at Telcontar)
David C. Rankin wrote:
On 4/1/21 4:21 AM, Carlos E. R. wrote:
I guess it's been too long since I did it, must have forgotten. Thanks David and Carlos.
I also forgot, I have not done that in ages. Which is why I searched my notees ;-)
I have a file, named "programs_for.txt" which contains a list of programs and a short description of what they are for.
In the old days, we learned how to manage Linux. It was all done via text config files and short utility commands. There was one way of doing things (recall make mrproper?).
Just a make target in the kernel Makefile ?
The one config where automation has been stunning is X. No more crafting modelines with xvidtune to transfer to xorg.conf -- it all works by automated defaults (most of the time)
So instead of learning how to admin Linux, much effort is now spent trying to keep track of what each of the new great automated tools does and does not do for you.
There is some truth to that, although I cannot put a finger on much except systemd. What an improvement over sysvinit.
Don't get me wrong, I'm not against the automation. Much of the automation provides a net time savings over doing it from scratch,
Which is the whole idea of having a Linux distribution ... I did once install/build Gentoo on HPPA, that was pretty much from scratch. Last week, I had a name server crash, in a datacentre some 600km away. The entire hardware had to be replaced, and unfortunately, both RAID disks were history. Installing openSUSE as a xenhost was fortunately easy-peasy, as well a installing a couple of guests, but not much of that was particularly automated. Further down the line I had some routing and bridging issues, but nothing that any automation would have helped much with.
but it has made Linux less about Linux and more about what tools your distro uses to admin it.
I admit I really only do openSUSE. I have tried *buntu et al, but it is too tiresome.
In using just about all distros, I'm not sure which is actually the easier route. It has been an interesting ride.
It depends solely on your needs. We use openSUSE in the office, for plain office machines it is quick and efficient to install. Upgrades are easy, it _just_ works. For servers, we are a little more conservative, but openSUSE also just works. For ARM boards, it sometimes takes a little more involvement. -- Per Jessen, Zürich (16.8°C) http://www.hostsuisse.com/ - virtual servers, made in Switzerland.
On 01/04/2021 20.54, Per Jessen wrote:
David C. Rankin wrote:
On 4/1/21 4:21 AM, Carlos E. R. wrote:
I guess it's been too long since I did it, must have forgotten. Thanks David and Carlos.
I also forgot, I have not done that in ages. Which is why I searched my notees ;-)
I have a file, named "programs_for.txt" which contains a list of programs and a short description of what they are for.
In the old days, we learned how to manage Linux. It was all done via text config files and short utility commands. There was one way of doing things (recall make mrproper?).
Just a make target in the kernel Makefile ?
mrproper refers to "Mr Proper", a brand of house cleaner with an intense TV add campaign. I missed the significance for years, because of course, for me the adverts say "Don Limpio": <https://images.app.goo.gl/VoeWksoCrkitczbx7> That makefile target in the kernel sources does an in depth cleanout. At least in the past, it could even erase things added by the SuSE package, thus my comment that it was dangerous to use.
The one config where automation has been stunning is X. No more crafting modelines with xvidtune to transfer to xorg.conf -- it all works by automated defaults (most of the time)
So instead of learning how to admin Linux, much effort is now spent trying to keep track of what each of the new great automated tools does and does not do for you.
There is some truth to that, although I cannot put a finger on much except systemd. What an improvement over sysvinit.
Network systems: wicked, NM,...
Don't get me wrong, I'm not against the automation. Much of the automation provides a net time savings over doing it from scratch,
Which is the whole idea of having a Linux distribution ... I did once install/build Gentoo on HPPA, that was pretty much from scratch.
Last week, I had a name server crash, in a datacentre some 600km away. The entire hardware had to be replaced, and unfortunately, both RAID disks were history. Installing openSUSE as a xenhost was fortunately easy-peasy, as well a installing a couple of guests, but not much of that was particularly automated. Further down the line I had some routing and bridging issues, but nothing that any automation would have helped much with.
but it has made Linux less about Linux and more about what tools your distro uses to admin it.
I admit I really only do openSUSE. I have tried *buntu et al, but it is too tiresome.
Ditto. That way I know the quirks and tricks. Less effort overall.
In using just about all distros, I'm not sure which is actually the easier route. It has been an interesting ride.
It depends solely on your needs. We use openSUSE in the office, for plain office machines it is quick and efficient to install. Upgrades are easy, it _just_ works. For servers, we are a little more conservative, but openSUSE also just works. For ARM boards, it sometimes takes a little more involvement.
-- Cheers / Saludos, Carlos E. R. (from 15.2 x86_64 at Telcontar)
Carlos E. R. wrote:
The one config where automation has been stunning is X. No more crafting modelines with xvidtune to transfer to xorg.conf -- it all works by automated defaults (most of the time)
So instead of learning how to admin Linux, much effort is now spent trying to keep track of what each of the new great automated tools does and does not do for you.
There is some truth to that, although I cannot put a finger on much except systemd. What an improvement over sysvinit.
Network systems: wicked, NM,...
Yes and no. Haven't they always been around, more or less, in some variation? when did you last have to configure eth0 by hand, using 'ip' commands ? What I was trying to say was - the automation and the scripting deals with the mundane stuff, leaving us to do what we really need. I don't think it takes anything away, or prevents anyone from learning how to admin Linux. Anyway, it is somewhat off-topic. -- Per Jessen, Zürich (12.1°C) http://www.dns24.ch/ - free dynamic DNS, made in Switzerland.
On 02/04/2021 09.19, Per Jessen wrote:
Carlos E. R. wrote:
The one config where automation has been stunning is X. No more crafting modelines with xvidtune to transfer to xorg.conf -- it all works by automated defaults (most of the time)
So instead of learning how to admin Linux, much effort is now spent trying to keep track of what each of the new great automated tools does and does not do for you.
There is some truth to that, although I cannot put a finger on much except systemd. What an improvement over sysvinit.
Network systems: wicked, NM,...
Yes and no. Haven't they always been around, more or less, in some variation? when did you last have to configure eth0 by hand, using 'ip' commands ?
Never. Never ever since my first SuSE in 1998 :-D
What I was trying to say was - the automation and the scripting deals with the mundane stuff, leaving us to do what we really need. I don't think it takes anything away, or prevents anyone from learning how to admin Linux.
Exactly. I just pointed to some other automation systems different than systemd. And in the case of wicked, I use YaST on top of it.
Anyway, it is somewhat off-topic.
-- Cheers / Saludos, Carlos E. R. (from 15.2 x86_64 at Telcontar)
participants (3)
-
Carlos E. R. -
David C. Rankin -
Per Jessen