Linux FAQs – Adaptiva Support Portal

What Linux versions does OneSite support?

Automated OS package updates, libraries, and applications from official repositories for key Linux distributions (updates within the same distribution release within those repositories). For more information on the supported operating systems, see Supported Operating Systems, Software, Drivers, and BIOS.
Tip

Support for repository-based library and application patching, including:
- OS package updates (security, system services, libraries, and kernel).
- Automated updates from the official repositories of each supported Linux distribution for each supported release.
- Patch support for approximately 18,000+ products sourced from distribution-specific repositories.
- Popular application support, such as Chromium, Firefox, Apache, OpenSSL, NGINX, and more.
Some limitations apply.
Does OneSite support third-party patching for Linux?

Currently, OneSite focuses on patching applications and libraries included in the official repositories of supported Linux distributions. These distributions include Ubuntu, Debian, RHEL, and CentOS. Third-party patching, such as managing packages from external repositories like the repositories for Google Chrome or Spotify, is not supported in this release.
What is included in the patching scope for Linux?

OneSite supports:
- Updates for applications and libraries found in the official distribution repositories. Examples include applications like Chromium, Firefox, Apache HTTP Server, NGINX, R, and core system components such as the Linux kernel, OpenSSL, and OpenSSH.
- OS updates (e.g., kernel or library updates) within the same distribution release are fully supported. Distribution upgrades (e.g., CentOS Stream9 to Stream10) are not supported.
Why isn’t third-party patching for Linux supported?

In the Linux ecosystem, most distributions centralize software management through their official repositories. These repositories are curated to maintain compatibility, stability, and security.

Third-party repositories are often managed independently, requiring manual configuration and maintenance, which adds complexity. For this reason, our initial focus is on ensuring seamless patching from the trusted and official sources provided by each distribution.
If an application is not part of the official repository, can OneSite still patch it?

Not at this time. Applications must be part of the official repositories of the supported distributions to be included in the patching scope. However, we welcome customer feedback to help us prioritize future enhancements.
What is the difference between repository-based patching and third-party patching?
- Repository-Based Patching: Involves managing updates from the official repositories of Linux distributions. These updates are curated by the distribution maintainers to ensure reliability and compatibility.
- Third-Party Patching: Refers to managing updates for software distributed outside the official repositories, such as Google Chrome directly from the repository for Google or custom enterprise applications hosted privately.
Can OneSite be customized to support third-party patching in the future?

Yes, our solution is flexible. If there is significant demand for specific third-party repositories, we could explore adding support in future releases. Custom repositories can technically be configured, but this requires additional setup and validation.
How does Linux patching for OneSite compare to other solutions?

OneSite stands out with features like:
- Unified patching management across multiple platforms (Windows, Linux, and Mac) from a single dashboard.
- Peer-to-peer content distribution eliminates the need for additional infrastructure.
- Support for updates within the official repositories of the five major Linux distributions.
Competitors often lack visibility into Linux libraries or focus only on high level OS upgrades, while OneSite provides granular control and insights.
What happens if a third-party repository is manually added by a user?

If a user manually adds a third-party repository, OneSite will not automatically detect or manage updates from it. Updates for third-party repositories must be handled outside of patching capabilities of OneSite for Linux.
How does OneSite ensure the stability of Linux updates?

By focusing on official repositories, OneSite leverages the vetting processes of each Linux distribution to ensure updates are stable and compatible. This minimizes risks associated with unverified third-party updates.
What are the future plans for Linux patching in OneSite?

We are continually enhancing our capabilities based on customer needs and feedback. Potential future enhancements include support for curated third-party repositories or custom enterprise applications, depending on demand.

Tip

Related articles