Linux in general: all the big distributions come with their own repositories of pre-prepared packages, and you normally don't have to go to a website, download, and install anything. The distribution will fetch the program and install it for you. For Arch, neither.debs or.rpms are appropriate to use. Re: Install deb or rpm package (SOLVED) pacman needs.pkg.tar.gz files, not just.tar.gz. I think you can use rpmextract for rpm's, not sure of an equivalent for deb but if all else fails, you can try using alien to convert from deb to rpm and then rpm extract. For the strength of the pack is the wolf, and the strength of the wolf is the pack. Node.js and npm packages are available in the Community Repository. Pacman -S nodejs npm Debian and Ubuntu based Linux distributions, Enterprise Linux/Fedora and Snap packages. So on Ubuntu all i do is change the package to deb and use dpkg to install it and its dependencies. How do i install an rpm package on arch with its dependencies.
- Install Rpm Package On Arch Linux Operating System
- Install Rpm Package On Arch Linux Mint
- Install Rpm Package On Arch Linux Free
- Install Rpm Package On Arch Linux
This page uses a table to display the correspondence of package management commands among some of the most popular Linux distributions. The original inspiration was given by openSUSE's Software Management Command Line Comparison.
-Qk option is new in pacman 4.1.Basic operations
| Action | Arch | Red Hat/Fedora | Debian/Ubuntu | SLES/openSUSE | Gentoo |
|---|---|---|---|---|---|
| Install a package(s) by name | pacman -S | dnf install | apt install | zypper install or zypper in | emerge [-a] |
| Remove a package(s) by name | pacman -Rs | dnf remove | apt remove | zypper remove or zypper rm | emerge -[a]vc |
| Search for package(s) by searching the expression in name, description, short description. What exact fields are being searched by default varies in each tool. Mostly options bring tools on par. | pacman -Ss | dnf search | apt search | zypper search or zypper se [-s] | emerge -S |
| Upgrade Packages - Install packages which have an older version already installed | pacman -Syu | dnf upgrade | apt update and then apt upgrade | zypper update or zypper up | emerge -[a]uDN @world |
| Upgrade Packages - Another form of the update command, which can perform more complex updates -- like distribution upgrades. When the usual update command will omit package updates, which include changes in dependencies, this command can perform those updates. | pacman -Syu | dnf distro-sync | apt update and then apt dist-upgrade | zypper dup | emerge -[a]uDN @world |
| Clean up all local caches. Options might limit what is actually cleaned. | pacman -Sc or pacman -Scc | dnf clean all | apt autoclean removes only unneeded, obsolete information or apt clean | zypper clean | eclean distfiles |
| Remove dependencies that are no longer needed, because e.g. the package which needed the dependencies was removed. | pacman -Qdtq | pacman -Rs - | dnf autoremove | apt autoremove | zypper rm -u (just for removing a package) or zypper packages --unneeded (listing only and without recursion) | emerge [-a] --depclean |
| Remove packages no longer included in any repositories. | pacman -Qmq | pacman -Rs - | dnf repoquery --extras | aptitude purge '~o' | ||
| Mark a package previously installed as a dependency as explicitly required. | pacman -D --asexplicit | dnf mark install | apt-mark manual | zypper install --force (workaround which needs to reinstall the package) | emerge --select |
| Install package(s) as dependency / without marking as explicitly required. | pacman -S --asdeps | dnf install and then dnf mark remove | apt-mark auto | n/a (feature request) | emerge [-a] --oneshot or emerge [-a] -1 |
| Only downloads the given package(s) without unpacking or installing them | pacman -Sw | dnf download | apt install --download-only (into the package cache) or apt download (bypass the package cache) | zypper --download-only | emerge [-a] --fetchonly |
| Start a shell to enter multiple commands in one session | dnf shell | apt-config shell | zypper shell | ||
| Show a log of actions taken by the software management. | read /var/log/pacman.log | dnf history | read /var/log/dpkg.log | read /var/log/zypp/history | read /var/log/portage |
| Get a dump of the whole system information - Prints, Saves or similar the current state of the package management system. Preferred output is text or XML. (Note: Why either-or here? No tool offers the option to choose the output format.) | see /var/lib/pacman/local | see /var/lib/rpm/Packages | apt-cache stats | emerge --info | |
| e-mail delivery of package changes | apt install apt-listchanges |
Querying specific packages
| Action | Arch | Red Hat/Fedora | Debian/Ubuntu | SLES/openSUSE | Gentoo |
|---|---|---|---|---|---|
| Show all or most information about a package. The tools' verbosity for the default command vary. But with options, the tools are on par with each other. | pacman -Si or pacman -Qi | dnf list or dnf info | apt show or apt-cache policy | zypper info or zypper if | emerge -S, emerge -pv or eix |
| Display local package information: Name, version, description, etc. | pacman -Qi | rpm -qi / dnf info installed | dpkg -s or aptitude show | zypper info or rpm -qi | emerge -pv or emerge -S |
| Display remote package information: Name, version, description, etc. | pacman -Si | dnf info | apt-cache show or aptitude show | zypper info | emerge -pv and emerge -S or equery meta |
| Display files provided by local package | pacman -Ql | rpm -ql | dpkg -L | rpm -ql | equery files or qlist |
| Display files provided by a remote package | pacman -Fl | dnf repoquery -l or repoquery -l (from package yum-utils) | apt-file list | pfl | |
| Query the package which provides FILE | pacman -Qo | rpm -qf (installed only) or dnf provides (everything) or repoquery -f (from package yum-utils) | dpkg -S or dlocate | zypper search -f | equery belongs or qfile |
| List the files that the package holds. Again, this functionality can be mimicked by other more complex commands. | pacman -Ql or pacman -Fl | dnf repoquery -l | dpkg-query -L | rpm -ql | equery files or qlist |
| Displays packages which provide the given exp. aka reverse provides. Mainly a shortcut to search a specific field. Other tools might offer this functionality through the search command. | pacman -F | dnf provides | apt-file search | zypper what-provides or zypper wp | equery belongs (only installed packages) or pfl |
| Search all packages to find the one which holds the specified file. | pacman -F | dnf provides | apt-file search or auto-apt is using this functionality. | zypper search -f | equery belongs or qfile |
| Show the changelog of a package | pacman -Qc | dnf changelog | apt-get changelog | rpm -q --changelog | equery changes -f |
Querying package lists
| Action | Arch | Red Hat/Fedora | Debian/Ubuntu | SLES/openSUSE | Gentoo |
|---|---|---|---|---|---|
| Search for package(s) by searching the expression in name, description, short description. What exact fields are being searched by default varies in each tool. Mostly options bring tools on par. | pacman -Ss | dnf search | apt search | zypper search or zypper se -s | emerge -S or eix |
| Lists packages which have an update available. Note: Some provide special commands to limit the output to certain installation sources, others use options. | pacman -Qu | dnf list updates or dnf check-update | apt list --upgradable | zypper list-updates or zypper patch-check (just for patches) | emerge -uDNp @world |
| Display a list of all packages in all installation sources that are handled by the packages management. Some tools provide options or additional commands to limit the output to a specific installation source. | pacman -Sl | dnf list available | apt-cache dumpavail or apt-cache dump (Cache only) or apt-cache pkgnames | zypper packages | portageq all_best_visible / |
| Generates a list of installed packages | pacman -Q | dnf list installed | dpkg --list | grep ^i | zypper search --installed-only | qlist -IC |
| List packages that are installed but are not available in any installation source (anymore). | pacman -Qm | dnf list extras | apt --installed list | grep ,local | zypper se -si | grep 'System Packages' | eix-test-obsolete |
| List packages that were recently added to one of the installation sources, i.e. which are new to it. | dnf list recent | aptitude search '~N' or aptitude forget-new | eix-diff | ||
| List installed local packages along with version | pacman -Q | rpm -qa | dpkg -l or apt list --installed | zypper search -s or rpm -qa | qlist -ICv |
| Search locally installed package for names or descriptions | pacman -Qs | rpm -qa '*<str>*' | aptitude search '~i(~n $name|~d $description)' | eix -S -I | |
| List packages not required by any other package | pacman -Qtt | dnf leaves or package-cleanup --leaves --all | deborphan -anp1 | emerge -pc | |
| List packages installed explicitly (not as dependencies) | pacman -Qe | dnf history userinstalled | apt-mark showmanual | grep -E '^i+' (workaround) | emerge -pvO @selected or eix --selected |
| List packages installed automatically (as dependencies) | pacman -Qd | grep -E '^i[^+]' (workaround) | apt-mark showauto |
Querying package dependencies
| Action | Arch | Red Hat/Fedora | Debian/Ubuntu | SLES/openSUSE | Gentoo |
|---|---|---|---|---|---|
| Display packages which require X to be installed, aka show reverse dependencies. | pacman -Sii | dnf repoquery --alldeps --whatrequires or repoquery --whatrequires | apt-cache rdepends or aptitude search ~D$pattern | zypper search --requires | emerge -pvc |
| Display packages which conflict with given expression (often package). Search can be used as well to mimic this function. | dnf repoquery --conflicts | aptitude search '~C$pattern' | |||
| List all packages which are required for the given package, aka show dependencies. | pacman -Si or pacman -Qi | dnf repoquery --requires or repoquery -R | apt-cache depends or apt-cache show | zypper info --requires | emerge -ep |
| List what the current package provides | dnf repoquery --provides | dpkg -s or aptitude show | zypper info --provides | equery files or qlist | |
| List all packages that require a particular package | dnf repoquery --installed --alldeps --whatrequires | aptitude search ~D{depends,recommends,suggests}:$pattern or aptitude why | zypper search --requires | equery depends -a | |
| Display all packages that the specified packages obsoletes. | dnf list obsoletes | apt-cache show | |||
| Generates an output suitable for processing with dotty for the given package(s). | apt-cache dotty |
Installation sources management
Install Rpm Package On Arch Linux Operating System
| Action | Arch | Red Hat/Fedora | Debian/Ubuntu | SLES/openSUSE | Gentoo |
|---|---|---|---|---|---|
| Installation sources management | edit /etc/pacman.conf | edit /etc/yum.repos.d/${REPO}.repo | edit /etc/apt/sources.list | edit /etc/zypp/repos.d/${REPO}.repo | layman or eselect repository |
| Add an installation source to the system. Some tools provide additional commands for certain sources, others allow all types of source URI for the add command. Again others, like apt and dnf force editing a sources list. apt-cdrom is a special command, which offers special options design for CDs/DVDs as source. | edit /etc/pacman.conf | /etc/yum.repos.d/*.repo | apt-cdrom add | zypper service-add | layman or overlays |
| Refresh the information about the specified installation source(s) or all installation sources. | pacman -Sy (always upgrade the whole system afterwards) | dnf clean expire-cache and then dnf check-update | apt-get update | zypper refresh or zypper ref | emerge --sync or layman -S |
| Prints a list of all installation sources including important information like URI, alias etc. | cat /etc/pacman.d/mirrorlist | cat /etc/yum.repos.d/* | apt-cache policy | zypper service-list | layman -l or eselect repository list |
| List all packages from a certain repo | paclist <repo> | eix --in-overlay | |||
| Disable an installation source for an operation | dnf --disablerepo= | emerge package::repo-to-use | |||
| Download packages from a different version of the distribution than the one installed. | dnf --releasever= | apt-get install -t release package or apt-get install package/release (dependencies not covered) | echo 'category/package ~amd64' >> /etc/portage/package.keywords and then emerge package |
Overrides
| Action | Arch | Red Hat/Fedora | Debian/Ubuntu | SLES/openSUSE | Gentoo |
|---|---|---|---|---|---|
| Add a package lock rule to keep its current state from being changed | edit /etc/pacman.conf modifying IgnorePkg array | edit dnf.conf adding/amending the exclude option | apt-mark hold pkg | zypper al or put package name in /etc/zypp/locks | /etc/portage/package.mask |
| Delete a package lock rule | edit /etc/pacman.conf removing package from IgnorePkg line | apt-mark unhold pkg | zypper rl or remove package name from /etc/zypp/locks | /etc/portage/package.mask (or package.unmask) | |
| Show a listing of all lock rules | cat /etc/pacman.conf | /etc/apt/preferences | zypper ll or view /etc/zypp/locks | cat /etc/portage/package.mask | |
| Set the priority of the given package to avoid upgrade, force downgrade or to overwrite any default behavior. Can also be used to prefer a package version from a certain installation source. | edit /etc/pacman.conf modifying HoldPkg and/or IgnorePkg arrays | /etc/apt/preferences, apt-cache policy | zypper mr -p | edit /etc/portage/package.accept_keywords adding a line with =category/package-version | |
| Remove a previously set priority | /etc/apt/preferences | zypper mr -p | edit /etc/portage/package.accept_keywords removing offending line | ||
| Show a list of set priorities | apt-cache policy or /etc/apt/preferences | zypper lr -p | grep -r . /etc/portage/package.accept_keywords | ||
| Ignore problems that priorities may trigger. | n/a |
Verification and repair
| Action | Arch | Red Hat/Fedora | Debian/Ubuntu | SLES/openSUSE | Gentoo |
|---|---|---|---|---|---|
| Verify single package | pacman -Qk (can add another k) | rpm -V | debsums | rpm -V | equery check |
| Verify all packages | pacman -Qk (can add another k) | rpm -Va | debsums | rpm -Va | equery check |
| Reinstall given package; this will reinstall the given package without dependency hassle | pacman -S | dnf reinstall | apt install --reinstall | zypper install --force | emerge -1O |
| Verify dependencies of the complete system; used if installation process was forcefully killed | pacman -Dk | dnf repoquery --requires | apt-get check | zypper verify | emerge -uDN @world |
| Use some magic to fix broken dependencies in a system | for pacman dependency level, use pacman -Dk; for shared library level, use findbrokenpkgsAUR or lddd (from devtools) | dnf repoquery --unsatisfied | apt-get --fix-broken and then aptitude install | zypper verify | revdep-rebuild |
| Add a checkpoint to the package system for later rollback | (unnecessary, it is done on every transaction) | n/a | |||
| Remove a checkpoint from the system | n/a | n/a | n/a | ||
| Provide a list of all system checkpoints | n/a | dnf history list | n/a | ||
| Rolls entire packages back to a certain date or checkpoint | n/a | dnf history rollback | n/a | ||
| Undo a single specified transaction | n/a | dnf history undo | n/a |
Using package files and building packages
| Action | Arch | Red Hat/Fedora | Debian/Ubuntu | SLES/openSUSE | Gentoo |
|---|---|---|---|---|---|
| Query a package supplied on the command line rather than an entry in the package management database | pacman -Qp | rpm -qp | dpkg -I | ||
| List the contents of a package file | pacman -Qpl | rpmls rpm -qpl | dpkg -c | rpm -qpl | |
| Install local package file, e.g. app.rpm and uses the installation sources to resolve dependencies | pacman -U | dnf install | apt install | zypper in | emerge |
| Updates package(s) with local packages and uses the installation sources to resolve dependencies | pacman -U | dnf upgrade | debi | emerge | |
| Add a local package to the local package cache mostly for debugging purposes. | cp package-filename /var/cache/pacman/pkg/ | apt-cache add package-filename | n/a | cp package-filename /usr/portage/distfiles | |
| Extract a package | tar -Jxvf | rpm2cpio | cpio -vid | dpkg-deb -x | rpm2cpio | cpio -vid | tar -jxvf |
| Install/Remove packages to satisfy build-dependencies. Uses information in the source package | Use ABS and makepkg -seoc | dnf builddep | apt-get build-dep | zypper si -d | emerge -o |
| Display the source package to the given package name(s) | dnf repoquery -s | apt-cache showsrc | n/a | ||
| Download the corresponding source package(s) to the given package name(s) | Use ABS and makepkg -o | dnf download --source | apt-get source or debcheckout | zypper source-install | emerge --fetchonly |
| Build a package | makepkg -s | rpmbuild -ba (normal) or mock (in chroot) | debuild | rpmbuild -ba, then build, and then osc build | ebuild or quickpkg |
| Check for possible packaging issues | namcap (requires namcap) | rpmlint | lintian | rpmlint | repoman |
Log file rotation
By default, Arch Linux does not rotate pacman.log. See, for example, FS#11272 and FS#20428#comment66480. This is in contrast to the default policy of most other Linux distributions. Some distributions, notably Gentoo, hardly write log files by default.
See also
This section describes how to install Privilege Management for Unix and Linux using a package installer for Red Hat Enterprise Linux (RHEL) 4 or 5 on an x86, x86_64, ia64, or S/390 computer. Use the Linux package installation if you want to install Privilege Management for Unix and Linux using the Linux RPM package manager.
The Privilege Management for Unix and Linux Linux package installer that is described here is not compatible with the Privilege ManagementPrivilege Management v5.x packages. You must remove BeyondTrustPrivilege Management packages v5.x before installing Privilege Management for Unix and Linux Linux packages.
Prerequisites
To use the Linux package installer, you must have the following:
- Package tarball file for the appropriate Privilege Management for Unix and Linux flavor
For the Privilege Management for Unix and Linux Linux package installer, the tarball files are cumulative. That is, an update tarball file contains a complete Privilege Management for Unix and Linux installation. It is not necessary to install a baseline version of Privilege Management for Unix and Linux before installing an upgrade.
- Root access or superuser privileges
- RPM Package Manager (rpm) v4.4 or later
The Privilege Management for Unix and Linux Linux package installer does not support prefix or suffix installations.
Plan Your Installation
When preparing to use the Privilege Management for Unix and Linux package installer, you should be familiar with the following concepts and restrictions:
Component packages: A Privilege Management for Unix and Linux component package is an RPM package manager (.rpm) file that installs a part of the Privilege Management for Unix and Linux application. The Privilege Management for Unix and Linux component packages are listed below with the format powerbroker-component-v.v.r.bb-pv.arch.rpm, where:
- component = Privilege Management component package name
- v = major version v = minor version r = release
- bb = build
- pv = version number of the package
- arch = architecture (for example, i386)
| Component Package | Description |
|---|---|
| powerbroker-loghost-v.v.r.bb-pv.arch.rpm | Contains log host, pbsync, and pbsyncd. |
| powerbroker-shlibs-v.v.r.bb-pv.arch.rpm | Contains shared libraries. |
| powerbroker-pbrest-v.v.r.bb-pv.arch.rpm | Contains REST API files. |
| powerbroker-rnssvr-v.v.r.bb-pv.arch.rpm | Contains Registry Name Service files. |
| powerbroker-licsvr-v.v.r.bb-pv.arch.rpm | Contains license server files. |
| powerbroker-master-v.v.r.bb-pv.arch.rpm | Contains policy server host, pbsync, and pbsyncd. |
| powerbroker-submithost-v.v.r.bb-pv.arch.rpm | Contains submit host and Privilege Management for Unix and Linux shells. |
| powerbroker-runhost-v.v.r.bb-pv.arch.rpm | Contains run host and Privilege Management for Unix and Linux utilities. |
| powerbroker-guihost-v.v.r.bb-pv.arch.rpm | Contains GUI host and secure GUI host. |
Which component packages are required depends on the type of Privilege Management for Unix and Linux host you create, such as policy server host, submit host, and so on. You can select the types of Privilege Management for Unix and Linux hosts in the pbinstall installation menu, as shown in the following table. For readability the ending of each component in the table (-v.v.r.bb-pv.arch.rpm) is removed.
Menu Selection | Required Components (-v.v.r.bb-pv.arch.rpm) |
Install everything here (demo mode)? = Yes | powerbroker-master powerbroker-runhost powerbroker-submithost powerbroker-loghost powerbroker-guihost powerbroker-shlibs |
Install Master Host? = Yes | powerbroker-master |
Install Run Host? = Yes | powerbroker-runhost |
Install Submit Host? = Yes | powerbroker-submithost |
| Install Log Host? = Yes | powerbroker-loghost |
| Install GUI Host? = Yes | powerbroker-guihost |
| Install Secure GUI Host? = Yes | powerbroker-guihost |
| Install BeyondTrust built-in third-party libraries? = Yes | powerbroker-shlibs |
| Install Registry Name Services Server? [yes] | powerbroker-rnssvr |
| Install License Server? [yes] | powerbroker-licsvr |
Configuration package: RPM package that is used to install the following files:
- pb.settings: Hardcoded target location /etc/pb.settings
- pb.cfg: Hardcoded target location /etc/pb.cfg
- All the encryption keyfiles defined for networkencryption, eventlogencryption, iologencryption, reportencryption, policyencryption, and restkeyencryption
- By default, two key files are created: pb.key and pb.rest.key
- The sysadmin can define multiple encryption with different keyfiles in locations other than /etc. To upgrade and retain settings on the target machine, view all encryption settings in /etc/pb.settings and copy the files to the settings_files directory before running 'pbinstall -z' and pbcreate*cfgpkg
- pb.conf (for policy server hosts)
- Man pages for the pbinstall and pbcreatelincfgpkg programs
The Privilege Management for Unix and Linux configuration package is created by the pbcreatelincfgpkg program. The component packages must be installed before you install the configuration package.
Package name: Name of the package as stored in the RPM package manager database. For Privilege Management for Unix and Linux package installations, this name is the same as the package file name without the .arch.rpm extension.
Relocated base directory: The directory where the Privilege Management for Unix and Linux binary files and log files are installed. You can choose an alternative directory in which to install these files.
pbinstall program: To create the Privilege Management for Unix and Linux settings files, you use the pbinstall program with the -z (settings only) option. pbinstall -z only creates the settings files, and is incompatible with the following command line options:
Options Incompatible with pbinstall -z | Description |
| -b | Runs pbinstall in batch mode. |
| -c | Skip the steps that process or update the Privilege Management for Unix and Linux settings file. |
| -e | Runs install script automatically by bypassing the menu step of pbinstall. |
| -i | Ignores previous pb.settings and pb.cfg files. |
| -p | Sets the pb installation prefix. |
| -s | Sets the pb installation suffix. |
| -u | Installs the utility programs. |
| -x | Creates a log synchronization host (installs pbsyncd). |
When you execute pbinstall with the -z option, you can see two menu items that are not otherwise available:
- Enter existing pb.settings path: This enables you to specify your own pb.settings file. pbinstall reads this settings file and populates the remaining menu choices. You can override some menu choices. If set to none, then pbinstall does not read a settings file. The remaining menu choices are populated with default values.
- Enter directory path for settings file creation: This enables you to specify an alternative output directory for the settings files. The default directory is /unzip-dir/powerbroker/v<flavor>/<flavor>install/settings_files, where unzip-dir is the directory where the package tarball file was unzipped.
The behavior of pbinstall -z depends on whether certain additional command line options are specified:
- If no other command line options are specified, pbinstall initially presents a short version of the installation menu. Depending on the choices you make in these items, further menu items become available.
- If command line options -g, -l, -m, -o, -r, or -w are specified, pbinstall presents an expanded version of the installation menu that reflects the host types that you are configuring.
When running pbinstall with the -z option, the following menu items are preprogrammed and cannot be changed:
Install Rpm Package On Arch Linux Mint
- Install man pages?
- Privilege Management daemon location
- Administration programs location
- User programs location
- GUI library directory
- Policy include (sub) file directory
- User man page location
- Admin man page location
- Policy filename
- BeyondTrust built-in third-party library directory
In addition, the values of the following menu items determine the values of other menu items:
| Options Preset When Running pbinstall -z | |
|---|---|
Setting this menu option to Yes | Sets these values to Yes |
| Install Master Host? | Install Synchronization? Synchronization can be initiated from this host? |
| Install Run Host? | Install Utilities? |
| Install Submit Host? | Install PBSSH? Install pbksh? Install pbsh? Will this host use a Log Host? |
| Install Log Host? | Install Synchronization? Synchronization can be initiated from this host? |
If you plan to use the package installer to install Privilege Management for Unix and Linux on a computer that already has an interactive Privilege Management for Unix and Linux installation on it, see Interactive Versus Packaged Installation for additional considerations.
If you plan to use Registry Name Service and are running pbinstall -z on a client host (non-primary server), you must perform client registration. This is necessary to properly set up the registry name service database. Client registration also requires that you collect from the Privilege Management for Unix and Linux primary server the following information:
- REST Application ID
- REST Application Key
- Primary server network name or IP address
- Primary License Server REST TCP/IP port
- Registration Client Profile name
Registering client with Primary RNS: If Registry Name Services is enabled for Privilege Management for Unix and Linux, each client host (after the first server installation) needs to be registered with the Primary Registry Name Server. When using package installers on a target host, a post-install configuration script (/opt/pbul/scripts/pbrnscfg.sh) is provided to be manually executed on that host to properly register it. This post-install configuration script asks for information about the Primary Registry Name Server, including the Application ID (appid), Application Key (appkey), address/domain name, and the REST TCP/IP port number. This is the same information provided during the client registration part of a pbinstall -z install which generates the settings file.
Install Rpm Package On Arch Linux Free
If you prefer a more convenient method of registering RNS clients where the post-install configuration script is non-interactive, Privilege Management for Unix and Linux can save the relevant information in a hidden file during the settings-only run of pbinstall, bundle it with the configuration package, and automatically apply it to the target host when that package is installed. However, understand that this is not secure, but is available if the security-convenience trade-off is acceptable. To enable this, refer to the question regarding post-install configuration script displayed when running pbinstall -z.
For more information, please see the following:
- On pbinstall command-line options, Installation Programs
Overview of Steps
Use of the Linux package installer involves the following steps:
- Unpack the Privilege Management for Unix and Linux package tarball file.
- Use the pbinstall program to create Privilege Management for Unix and Linux settings files.
- Use the pbcreatelincfgpkg program to create the Privilege Management for Unix and Linux configuration package.
- Perform a package installation using the Linux rpm command for any required components.
- Perform a package installation using the Linux rpm command for the Privilege Management for Unix and Linux configuration package.
- If Registry Name Service is enabled and installing on a non-primary servery, run /opt/pbul/scripts/pbrnscfg.sh to register the host.
Install Rpm Package On Arch Linux
For additional details on the above steps, please see Installation Procedure.