- En Linux There is no single universal command to know if the system is up to date, but each distribution offers commands to check for pending packages using your package manager (APT, yum/dnf, zypper, pacman).
- fwupd and the LVFS service are the standard option for managing firmware updates on compatible devices, although for many hardware Manufacturer utilities are still necessary.
- Specific tools such as BIOS/UEFI menus, bootable media with FreeDOS, executables of WindowsArcGIS patchnotification or Oracle System Assistant cover scenarios where fwupd does not reach.
- Following the manufacturer's instructions, ensuring a stable power supply, and verifying the correct firmware for each model are key to updating safely without rendering the equipment unusable.
When we talk about keeping a Linux system up to date, we almost always think about software packages and operating system security patchesBut we often forget something equally critical: firmware. BIOS/UEFI, controllers, embedded devices, and even specific platforms like ArcGIS Enterprise depend on updated firmware to function stably and securely. And yes, you can also check for new versions and update them from Linux, although sometimes you have to resort to slightly more manual methods.
In corporate, university, or other environments with strict security requirements, it's common to require that machines be up to date. This is usually the case in Windows and macOS. unified tools to check the status of updatesBut in Linux, things are different: each distribution has its own package system, and firmware is managed in very different ways. This article will show you, in detail, how to check for package and firmware updates, what tools are available in Linux, and what alternatives exist when fwupd doesn't cover your hardware.
Check if a Linux system has package updates
First of all, if what you need is a quick check to see if your machine is up to date, you should know that There is no single magic command that works the same in all distributionsBecause the package management system varies between Debian/Ubuntu, Red Hat, SUSE, Arch, and others. Even so, the logic is the same: ask the package manager if there's anything pending an update and, in some cases, interpret its output to get a yes/no answer.
In Debian-based systems (Debian, Ubuntu and derivatives) the usual practice is to use APT to update the package list and check for possible updates and a script Simply put, you could use commands like apt update followed by apt list --upgradable And, if the list is not empty, conclude that updates are available. From the command line, you can process this output to convert it into a binary result for other scripts, for example, by integrating it into a system of VPN or supervisory.
In the Red Hat world (RHEL, CentOS, Rocky, AlmaLinux), the classic tool is yum, and in more recent versions dnf. With yum check-update o dnf check-update The system queries the configured repositories and returns a list of packages that could be updated, including their dependencies. From there, you could automate a check: if the list is empty, the system is up to date; if there are results, then there are pending updates, either to install all of them or to select specific packages.
In SUSE and derivatives, it is used zypper, while in Arch Linux the management is handled by pacmanIn both cases, it's also possible to query for updates without installing them, so a shell script can interpret the command's result and respond with a simple "yes" or "no." The important thing here is to understand that, although the goal is the same, Each distribution family has its own command to check the status of packages.
To integrate this verification into corporate processes (such as the Boot (from a VPN client), the most reasonable thing to do is to write a script that detect the available package manager and execute the appropriate command. In this way, it is possible to emulate, to some extent, the "centralized verification" that many companies take for granted in Windows and macOS, but adapted to the diversity of the Linux ecosystem.
Firmware updates in Linux: fwupd and beyond
Once the issue of the packages is resolved, the delicate part begins: Check and apply firmware updates from LinuxFirmware controls the lowest layer of the hardware (BIOS/UEFI, integrated controllers, BMC/ILOM, PCIe devices, etc.), and a failure during an update can render the computer unusable. Therefore, it's essential to be familiar with the available tools.
The standard solution in modern Linux is fwupd combined with LVFS (Linux Vendor Firmware Service)fwupd offers a unified interface for managing firmware updates from different manufacturers and components, provided the vendor participates in the LVFS platform and publishes their firmware images there. Many well-known brands (especially in portable and professional-grade desktop computers) already support this system.
With fwupd you can check which devices on your system are compatible and if there are any pending updates. The typical workflow involves asking the tool what hardware it detects, requesting that it check for new versions on the LVFS servers, and, if so, downloading and installing the firmware. In many cases, The process is fully integrated into the operating system and can even be managed through graphical environments.although it's also easy from the console.
However, not all hardware is covered. Older systems, specific motherboards, servers, or certain integrated devices may not offer updates through fwupd. In those cases, it is necessary resort to alternative methods provided directly by the manufacturer: utilities included in the BIOS/UEFI itself, executables prepared for Windows, DOS/FreeDOS boot images, or other specific tools. This is where "manual" work from Linux becomes more important.
Patch and component updates in ArcGIS Enterprise from Linux
In the realm of specialized software, we also find utilities specifically designed to manage updates from Linux. A good example is ArcGIS Enterprise, which offers its own patchnotification tool to consult and apply patches to the various components of the system (servers, additional roles, extensions, etc.).
The patchnotification utility is installed with the product itself and allows the administrator to check which patches and updates are available for ArcGIS Enterprise components deployed on a machine. When run, it displays detailed information about pending patches and, at the bottom of the dialog box, A list of the patches already installed and QFE present in the systemIf there are multiple ArcGIS Enterprise products on the same server, the tool also displays update information for all of them.
In order for the utility to display the complete catalog of available patches, it needs access to several specific web addresses. These include a URL with a JSON file describing the available patches, as well as other paths from which updates are downloaded. Without connectivity to these sites, the patch list will not be complete and updates will not be downloadable.Therefore, it is essential to review the network and proxy configuration in corporate environments.
From PatchNotification's graphical interface, you can download and install specific patches, limit yourself to security patches only, or apply all available patches. The tool downloads the necessary files, launches the corresponding installer, and once the process is complete, It keeps downloaded packages in the system's temporary folder. without automatically deleting them. If you wish to modify this behavior or change the download path, you can do so from the utility's installation settings tab.
The tool also supports a console mode or command lineThis is very useful for automating checks in scripts or integrations with management systems. In this mode, you can specify, for example, that only security patches should be installed or that all available patches should be applied, using specific parameters such as -i sec for security patches or -i all for all updates. If internet access is through a proxy server, it can be specified using a dedicated argument, including username, password, address, and port, so that patchnotification can connect without problems.
In distributed deployments of ArcGIS Enterprise, it is very important that all machines that are part of the site receive the same set of patchesFor example, if you use ArcGIS Mission Server, you should apply the same patch or update to all instances that make up the site to avoid inconsistencies and compatibility issues between nodes.
Managing updates and firmware in Oracle System Assistant
In the server sector, many manufacturers offer their own integrated tools for managing system firmware and software. In the case of Oracle, one of the most representative solutions is... Oracle System Assistant, which facilitates the updating of the various firmware components of the server., including the service processor and other critical elements.
This utility allows you to check, directly from the manufacturer's environment, whether new firmware versions are available for system components. Once the check is complete, the wizard displays a list of the items that can be updated and offers options for updating them. Install all updates at once or select specific components to update them individually.
The typical process begins by starting Oracle System Assistant according to the manufacturer's instructions. From its navigation panel, you can access the firmware update section The check then begins, during which a progress bar appears indicating the status of the search for new versions. When this is complete, the wizard displays buttons such as "Install all updates" or "View details," which allow you to explore the changes further and decide what to update.
Clicking on the option to view details opens a dialog box with a detailed list of the changes involved in each firmware updateFrom there, you can select the components you want to update and, after confirming your selection, start the installation process. During this procedure, the server may restart automatically several times, restarting Oracle System Assistant after each restart to continue the update until it is complete.
It's important to note that some components, such as the Oracle ILOM firmware (remote server management), can disconnect remote console sessions during the flashing process. Additionally, There total update It depends on whether the interconnection between the host and the ILOM management is enabled.When this connection is active, the process is usually faster. For this reason, Oracle recommends properly preparing the environment before starting the updates, following the procedures outlined in its documentation.
In general, Oracle System Assistant recommends maintaining all firmware components in their latest versionsBecause improvements in one module often depend on changes made in another. While it may be tempting to update only a part, it's good practice to review the entire system and apply updates consistently, always during planned maintenance windows and with strict control over potential service interruptions.
Passionate writer about the world of bytes and technology in general. I love sharing my knowledge through writing, and that's what I'll do on this blog, show you all the most interesting things about gadgets, software, hardware, tech trends, and more. My goal is to help you navigate the digital world in a simple and entertaining way.