Open source components are part of many industrial systems, including data infrastructure used in automation environments. The Scalar i6000 open source licenses disclosure for firmware release i13.2 explains which third-party software packages are included in the tape library and identifies the license associated with each. For engineers, system integrators, and technical decision-makers, the document is a practical reference for understanding software provenance and checking applicable use and redistribution terms.
The disclosure is specific to Scalar i6000 firmware release i13.2, identified as 770Q, and is dated April 2019. It describes an aggregate of vendor-proprietary programs and third-party software, including open source software (OSS). It should therefore be read as a release-specific license inventory, not as a general description of every Scalar i6000 configuration or later firmware release.
What the Scalar i6000 open source licenses disclosure covers
The document connects software components to the parts of the library in which they are used. Rather than presenting a single undifferentiated list, it separates packages by software area or hardware subsystem. These groupings include:
- Library Management Client Software: packages such as Ant, Guava, Apache HTTP components, and PostgreSQL JDBC.
- Library Control Firmware: software associated with the Main Controller Board and Chassis Management Blade (MCB2 and CMB2), as well as a separate listing for CMB1.
- Robotics Control Unit: the RCU2 listing identifies U-Boot.
- Ethernet Expansion Blade: its listed components include BusyBox, DHCP client software, and the uClinux kernel.
- WebGUI Software: a separate inventory identifies packages used in the web-based management interface.
This organization helps readers relate a license entry to a software area. It does not, by itself, describe what each package does in the product, how components communicate, or whether a package is active in a particular installation.
Why license terms vary by component
The inventory includes software under a range of licenses. Examples named in the disclosure include versions of the GNU General Public License (GPL) and GNU Lesser General Public License (LGPL), Apache licenses, BSD-style licenses, the MIT-style Expat license, the Boost Software License, and other terms. Some entries also identify more than one applicable license or a license exception.
That variety matters because “open source” does not mean that every component has identical conditions. Depending on the specific license and activity, requirements can relate to retaining notices, including license text with redistribution, marking modified files, or providing source code. A package’s name alone is not enough to determine the obligations: the applicable license entry and its full terms need to be reviewed.
For organizations that manage industrial equipment as part of a broader technology estate, the inventory can support software asset reviews, procurement documentation, and internal open source compliance processes. It can also help technical teams identify which subsystem or software area to investigate when a license question arises. The disclosure is not a substitute for interpreting the relevant license terms for a specific use or distribution scenario.
Source code access and LTO drive disclosures
The document states that OSS may be copied, distributed, or modified in accordance with the terms of its respective license. It also notes that some licenses provide rights to obtain corresponding source files. For the tape library firmware, Quantum says integrated OSS source files are available upon request, whether the software is licensed under GPL, LGPL, or another license. The disclosure directs readers to the Scalar i6000 Open Source License CD, part number 3-01638-xx, when making a request.
LTO tape drives installed in the library may contain additional OSS components. The firmware disclosure points readers to the Tape Automation disclosure listings under the Open Source Information link at Quantum support for the applicable package and license information for those drives, including source-file instructions. This distinction is important: the library firmware list should not be assumed to cover every component within an installed tape drive.
How engineering and compliance teams can use the inventory
A practical review can begin by matching the equipment and software release to the disclosure, then narrowing the review to the relevant subsystem. Teams can use a process such as:
- Confirm the release: check that the inventory applies to the Scalar i6000 firmware version under review.
- Locate the software area: use the document’s headings to distinguish management client software, control firmware, robotics, Ethernet expansion, and WebGUI listings.
- Record each package and license: preserve the component-to-license association rather than recording only a general “open source included” note.
- Review the full terms: consult the license text for any planned copying, modification, or redistribution.
- Check drive-specific information separately: use the cited Tape Automation disclosure listings for OSS included in LTO drives.
- Request source files when applicable: follow the request information identified in the disclosure and the relevant license terms.
These steps help keep software records tied to the correct release and subsystem. They also reduce the risk of treating the library firmware and the installed drive firmware as one shared license inventory.
Conclusion
The Scalar i6000 firmware i13.2 disclosure provides a structured view of third-party and open source packages across the library’s management software, control firmware, robotics unit, Ethernet expansion blade, and WebGUI. Its main practical value is traceability: teams can identify listed components, find their stated licenses, and follow the document’s directions for source requests and separate LTO drive disclosures. Because terms differ across packages and the inventory is release-specific, organizations should verify the applicable version and review the relevant license text before making decisions about use or redistribution.