How to Install and Uninstall osmo-hlr Package on openSUSE Leap
Last updated: November 26,2024
1. Install "osmo-hlr" package
This guide let you learn how to install osmo-hlr on openSUSE Leap
$
sudo zypper refresh
Copied
$
sudo zypper install
osmo-hlr
Copied
2. Uninstall "osmo-hlr" package
Learn how to uninstall osmo-hlr on openSUSE Leap:
$
sudo zypper remove
osmo-hlr
Copied
3. Information about the osmo-hlr package on openSUSE Leap
Information for package osmo-hlr:
---------------------------------
Repository : Main Repository
Name : osmo-hlr
Version : 1.4.0-bp155.1.10
Arch : x86_64
Vendor : openSUSE
Installed Size : 358.2 KiB
Installed : No
Status : not installed
Source package : osmo-hlr-1.4.0-bp155.1.10.src
Upstream URL : https://projects.osmocom.org/projects/osmo-hlr
Summary : Osmocom Home Location Register for GSUP protocol towards OsmoSGSN and OsmoCSCN
Description :
The GSUP HLR is a stand-alone HLR (Home Location Register) for SIM
and USIM based subscribers which exposes the GSUP protocol towards
its users. OsmoSGSN supports this protocol.
osmo-gsup-hlr is still very simplistic. It is a single-threaded
architecture and uses only sqlite3 tables as back-end. It is suitable
for installations of the scale that OsmoNITB was able to handle. It
also lacks various features like fine-grained control of subscribed
services (like supplementary services).
---------------------------------
Repository : Main Repository
Name : osmo-hlr
Version : 1.4.0-bp155.1.10
Arch : x86_64
Vendor : openSUSE
Installed Size : 358.2 KiB
Installed : No
Status : not installed
Source package : osmo-hlr-1.4.0-bp155.1.10.src
Upstream URL : https://projects.osmocom.org/projects/osmo-hlr
Summary : Osmocom Home Location Register for GSUP protocol towards OsmoSGSN and OsmoCSCN
Description :
The GSUP HLR is a stand-alone HLR (Home Location Register) for SIM
and USIM based subscribers which exposes the GSUP protocol towards
its users. OsmoSGSN supports this protocol.
osmo-gsup-hlr is still very simplistic. It is a single-threaded
architecture and uses only sqlite3 tables as back-end. It is suitable
for installations of the scale that OsmoNITB was able to handle. It
also lacks various features like fine-grained control of subscribed
services (like supplementary services).