06-03-2012
6,384,
2,214
Join Date: May 2005
Last Activity: 28 October 2019, 4:59 PM EDT
Location: In the leftmost byte of /dev/kmem
Posts: 6,384
Thanks Given: 143
Thanked 2,214 Times in 1,548 Posts
I have no SuSe to give you an exact recipe, but i can point you in the general direction:
A Linux distribution is a collection of "packages" - sets of files, which are somehow connected to each other - and some means to install them or remove them from the system.
For instance, such a package could be a "web browser": it would contain all the binaries needed to run the web browser, some libraries, probably some configuration files, etc.. It also will contain some scripts to integrate the browser in the desktop (i.e. by creating icons on your desktop or something such) and some "metadata": information about the version, a description, a list of files it contains, and so on. With this metadata, it is possible to not only install the package but also to remove it completely, bringing the system to the state it was in before the installation.
Every Linux distribution has such a package manager: RedHat and several others have "rpm" (RedHat Package Manager), Debian and some others use "apt-get", SuSe uses either "YaST" or the commandline tool "zypper".
The procedure is simple: first you get the information to which package to the glibc belongs to. I can't tell you how this is done with zypper, but have a look in the man page (enter man zypper on the command line) and i am sure you will find that.
When you got the name of the package you look for you simply search for it on the web. Enter "SuSe <name-of-package> download" into your favorite search engine and you will surely find lots of pages.
After downloading it you use again zypper to update the package with the new version you just downloaded - that was it.
...or maybe not: there could be "dependencies" to update: Maybe a packages content can only work if some other software from another package is already installed. Or maybe a certain version of one package needs the content of another package to be at least on a certain version or newer. All this is part of the metadata i wrote above. The package manager will tell you if such dependencies exist. You can't break the system by following what the package manager tells you - so stay away from any "force" option! They are for very rare opportunities and to be used by people who know exactly what they do.
If the package manager tells you that you need to install/update other packages too you simply repeat the above process for these.
Good luck and i hope this helps.
bakunin
