— LiveStream

To install open source applications on AIX, mount the AIX Toolbox for Linux Applications media (or point to a repository) and install the RPM packages with SMIT, the geninstall command, or rpm directly. This guide walks through every method for getting open source software onto your IBM AIX system, the order to install bundles in, how to resolve failed dependencies, and the modern repository-based way to do all of this today with dnf.

Why install open source applications on AIX?

AIX is IBM's enterprise UNIX for Power Systems, and out of the box it ships with the proprietary base operating system rather than the broad catalog of GNU and open source tools that Linux administrators expect. Tools like bash, wget, vim, gcc, bc, cdrecord, and entire desktop environments such as GNOME or KDE are not part of the core install.

IBM closes that gap with the AIX Toolbox for Linux Applications (sometimes called the AIX Toolbox for Open Source Software). It is a curated collection of the most commonly used open source applications, pre-compiled for the Power architecture and packaged as RPM packages — the same package format used by Red Hat and SUSE Linux. Learning to install these packages is a core skill for any AIX system administrator.

Prerequisites and things to consider

Before you begin installing open source applications on AIX, confirm the following. Results can vary significantly between AIX versions and technology levels, so always match the procedure to your release.

• Root authority. Mounting media and installing packages requires the root user (or equivalent RBAC privileges).
• The rpm command is present. RPM Package Manager has been installed automatically with the base operating system since AIX 5.1, so the tooling is already on the system.
• Enough free space in the target filesystem. Desktop bundles in particular pull in dozens of libraries. Check with df -g and grow filesystems with chfs if needed.
• The media or a repository. You can install from the physical Toolbox media shipped with your OS, from an ISO, or — on modern AIX — straight from IBM's online package repository.

Check your AIX level first so you can pick the right packages:

1. Run oslevel -s to see the version, technology level, and service pack.
2. Run prtconf | grep 'Processor Type' to confirm you are on Power (the Toolbox is built for the ppc / ppc64 architecture).

Your options for installing open source applications on AIX

There is more than one supported path to get RPM software onto an AIX system. Choose based on whether you prefer a menu-driven interface or the command line, and whether you want a single tool or an entire environment.

• SMIT (install_software fast path) — the menu-driven System Management Interface Tool, ideal if you want to browse the media and select packages interactively.
• The geninstall command — a generic installer that understands AIX installp filesets and RPM packages, useful in scripts.
• Installing a bundle — bundles group the packages needed for a basic Linux environment, basic desktop use, a GNOME or KDE desktop, or application development, so you install a whole working environment in one step.
• Installing from a function directory — the media is organized into directories by purpose (shells, network applications, development tools, application libraries, and more) so you can pull in a related group of tools.
• Installing a single package with the rpm command — the most granular option for one specific application.

Method 1: Install RPM packages on AIX with SMIT

SMIT is the friendliest method for administrators who want to see what is on the media before committing. The following installs the cdrecord and mtools packages.

1. Insert the AIX Toolbox for Linux Applications media into the drive.
2. As root, start the installer with the fast path: smit install_software
3. For the input device or directory, enter the device name of the media — for example /dev/cd0 — and press Enter.
4. Move to the SOFTWARE to install field and press F4 to list the contents of the device.
5. Select the cdrecord and mtools packages from the list (use F7 to mark multiple entries), then press Enter.
6. Accept the default values for the remaining fields on the Install Software menu and press Enter.
7. Confirm that you want to install the software by pressing Enter again. The installation begins, and SMIT reports OK on success.

To install an entire bundle through the menus instead, use the smit install_bundle fast path and select the bundle (for example, the GNOME bundle) rather than individual packages.

Method 2: Install RPM packages from the command line with geninstall

For scripted or repeatable installs, geninstall is the fastest route. The R: prefix tells geninstall that the named software is an RPM package (as opposed to an installp fileset, which uses I:).

To install the same two packages directly from the media:

1. As root, run the installer pointing at the device with -d:
   geninstall -d /dev/cd0 R:cdrecord R:mtools
2. The software installation process begins immediately and prints progress for each package.

You can list what the device offers before installing by adding the preview flag: geninstall -L -d /dev/cd0. This is the safe, dry-run habit to build before pushing changes to production servers.

Method 3: Install a desktop with the rpm command and bundles

The rpm command gives you the most direct control and is how you install a complete environment such as the GNOME desktop. This walkthrough mounts the media manually, inspects it, then installs the GNOME bundles in dependency order followed by the bc calculator package.

Step 1 — Mount the media

With the system running AIX 5.1 or later and the Toolbox media inserted, mount it read-only as root:

1. Run: mount -v cdrfs -o ro /dev/cd0 /mnt

Here the flags mean:

• -v cdrfs sets the virtual filesystem type to cdrfs, the CD-ROM filesystem.
• -o ro mounts the filesystem read-only, which is correct for installation media.
• /dev/cd0 is the device, and /mnt is the directory you mount it on.

Step 2 — Inspect the media before installing

1. Change into the mount point: cd /mnt
2. List the contents: ls

Two files are worth reading first:

• The README file contains the complete, version-specific instructions for installing from this media. Always read it — package names and bundle layouts change between releases.
• The CONTENTS file lists every package on the media with a short description of its purpose, so you can decide exactly what you need.

You can also open /mnt/LICENSES/index.html in a web browser to review the open source license terms for the software you are about to install.

Step 3 — Install GNOME by installing its bundles in order

Change into the easy-install directory for the Power architecture and install the four GNOME bundles. Order matters: each bundle depends on the one before it, so install Base, then Desktop Base, then GNOME Base, then GNOME Apps.

1. cd /mnt/ezinstall/ppc
2. rpm -Uhv base/*
3. rpm -Uhv desktop.base/*
4. rpm -Uhv gnome.base/*
5. rpm -Uhv gnome.apps/*

The rpm flags do the following:

• -U (upgrade) installs each package and updates any earlier version already on the system. If the package is not present, -U installs it fresh, which makes it safer than -i for repeat runs.
• -h prints hash marks (#) as a progress bar so you can see the install advancing.
• -v is verbose, showing relevant informational and error messages.

A successful run of the desktop base bundle looks similar to this:

• gdbm ##################################################
• libjpeg ##################################################
• libpng ##################################################
• libtiff ##################################################
• libungif ##################################################
• readline ##################################################
• zlib ##################################################

Step 4 — Install a single application package

Finally, install the bc arbitrary-precision calculator from the RPMS directory. The wildcard matches whatever version ships on your media:

1. rpm -Uhv /mnt/RPMS/ppc/bc-*.rpm

Installing a directory of packages by function

The Toolbox media groups packages into function directories so you can install a related set at once — for example all the shell environments, all the network applications, or all the development tools. You can either point rpm at the whole directory:

1. rpm -Uhv /mnt/RPMS/ppc//*.rpm

...or use the helper script provided on the media, which installs only the packages that are not already present on your system, skipping anything you already have:

1. /mnt/contrib/installmissing.sh ezinstall/ppc/desktop.base/*

Common pitfalls and how to fix them

If the rpm command returns an error, it is almost always one of three causes. Each has a clear fix.

A few more real-world gotchas worth knowing:

• Architecture mismatch. A package built for ppc will not install on the wrong word size or platform. Stick to the ppc / ppc64 trees that match your hardware.
• Mixing installp and RPM. Use geninstall when a payload contains both AIX filesets and RPMs — it dispatches each to the correct installer automatically.
• Forgetting to unmount. When finished with optical media, release it cleanly with umount /mnt before ejecting.

The modern way: install open source applications on AIX with DNF/YUM

Optical media and ezinstall bundles still work, but on supported AIX releases (AIX 7.1 TL5, 7.2, 7.3 and later) IBM now ships and recommends the DNF package manager (the successor to YUM) wired to an online repository. This resolves dependencies for you automatically — the single biggest improvement over hand-installing RPMs from a directory.

To get started, download and run IBM's bootstrap script as root:

1. Fetch the installer: curl -O https://public.dhe.ibm.com/aix/freeSoftware/aixtoolbox/ezinstall/ppc/dnf_aixtoolbox.sh
2. Make it executable and run it: chmod +x dnf_aixtoolbox.sh then ./dnf_aixtoolbox.sh -y

After that, installing software is a one-liner, with all dependencies pulled in for you:

• Install a package: dnf install bc
• Search the catalog: dnf search wget
• Keep everything current: dnf update
• Remove a package: dnf remove cdrecord

Because dnf handles dependency resolution, it eliminates almost all of the failed-dependency errors that the manual RPM method produces. Use the media-based methods above for air-gapped systems with no internet access, and use dnf everywhere else.

Verification: confirm the open source applications installed correctly

After any of these methods, verify the result rather than assuming success. AIX gives you several ways to confirm an RPM is properly installed.

1. List all installed RPM packages: rpm -qa
2. Query a specific package and its version: rpm -q bc
3. List the files a package installed: rpm -ql bc
4. Verify the integrity of an installed package: rpm -V bc (no output means everything matches).
5. Confirm the binary actually runs and is on your PATH: which bc then test it, e.g. echo "scale=4; 22/7" | bc

If the command runs and returns the expected output, the open source application is installed and ready to use. For desktop bundles, log in through the graphical login manager (or start the session) to confirm GNOME loads.

Key Takeaways

• Three classic methods install RPM software on AIX: the menu-driven smit install_software, the scriptable geninstall -d /dev/cd0 R:, and the direct rpm -Uhv command.
• Use -Uhv with rpm — upgrade-or-install, hash-mark progress, and verbose output — and install bundles in order: Base, Desktop Base, GNOME Base, GNOME Apps.
• Most errors are one of three: not enough filesystem space, package already installed, or failed dependencies — each with a straightforward fix.
• The modern, recommended way is dnf, which auto-resolves dependencies from IBM's online AIX Toolbox repository; keep the media method for air-gapped servers.
• Always verify with rpm -q, rpm -V, and by actually running the new command before considering the install complete.

Frequently Asked Questions

What is the AIX Toolbox for Linux Applications?

It is IBM's curated collection of popular open source applications and libraries — such as bash, wget, gcc, and desktop environments — pre-compiled for the Power architecture and delivered as RPM packages. It ships with the base operating system and is also available from IBM's online repository.

How do I install an RPM package on AIX from the command line?

As root, run rpm -Uhv /path/to/package.rpm for a local file, or geninstall -d /dev/cd0 R:packagename to pull it from the Toolbox media. On modern AIX, dnf install packagename is simplest because it resolves dependencies automatically.

What does the rpm error "failed dependencies" mean on AIX?

It means the package you are installing needs other packages that are not yet present. Install the prerequisites listed in the error message first, install the bundles in dependency order, or switch to dnf, which downloads and installs all required dependencies for you.

Should I still use SMIT and geninstall, or just dnf?

Use dnf on any internet-connected, supported AIX release — it is the current IBM-recommended approach and far less error-prone. Keep smit, geninstall, and the media-based rpm methods for air-gapped systems, older AIX levels, or when you must install from physical media.

If you found this AIX guide useful, subscribe to @explorenystream on YouTube for more system administration and DevOps walkthroughs.