Image Packaging System
In today's world, Image Packaging System is a topic that has captured the attention of people of all ages and interests. From academics and subject matter experts, to those simply seeking general information, Image Packaging System has become a crucial reference point in modern culture. With its impact on various aspects of society, Image Packaging System has generated debates, discussions and reflections that seek to understand its relevance in the current context. In this article, we will explore the different angles of Image Packaging System, from its origin to its evolution, in order to shed light on one of the most relevant topics today.
 | This article has multiple issues. Please help improve it or discuss these issues on the talk page. (Learn how and when to remove these messages)
|
The Image Packaging System, also known as IPS,[1] is a cross-platform package management system created by the OpenSolaris community in coordination with Sun Microsystems. It is used by Solaris 11 and several Illumos-based distributions: OpenIndiana, OmniOS, XStreamOS[2] and a growing number of layered applications, including GlassFish, across a variety of Operating System platforms. IPS is coded in the Python programming language.
Features
IPS enables a superuser to search for, install, and remove software packages from the Solaris system.[3]
- Use of ZFS, allowing multiple boot environments and easy package operation rollbacks
- Transactional actions
- Support for multiple platform architectures within a single package
- Legacy support for SVR4 packages
- Extensive search grammar
- Remote search capability
- Changes-only based package updates
- Network package repository
- File and network-based package publication
- Package operation history
- On-disk package format (p5p)
- Multi-platform ports for layered applications:
- Broad platform support: Windows, Linux, OS X, Darwin, Solaris, OpenSolaris, Illumos and AIX
- Cross-platform update notification and package management Graphical user interfaces.
Considerations
Due to the fact that IPS delivers each file in a separate shelf[clarification needed] with a separate checksum, a package update only needs to replace files that have been modified. When dealing with ELF binaries, IPS computes checksums only from the loaded parts of an ELF binary[citation needed]. This means in practice that when only the ELF comment section has been changed, there would be no need to update it. However, this method of delivery can cause slower operation when the input source is on a medium with high latency (e.g. internet with higher round trip time or CD/DVD media with slow seeks).
References
- ^ "Packaging and Delivering Software With the Image Packaging System in Oracle Solaris 11.1". Oracle Solaris 11.1 Information Library. Retrieved 18 December 2012.
- ^ "Distributions - illumos - illumos wiki". Illumos wiki. Retrieved 12 May 2015.
- ^ Bhuse, Vijay; Hekhuis, Kyle (9 March 2018). "Support for Secure Code Execution in Server Operating Systems". ICCWS 2018 13th International Conference on Cyber Warfare and Security. Academic Conferences and Publishing Limited: 21–30. ISBN 978-1-911218-73-9 – via Google Books.
External links
- GitHub Project: Image Packaging System
- Multi-Platform Packaging for Layered Distros
- GlassFish Update Center Toolkit Archived 2017-04-04 at the Wayback Machine
- Update Center 2.0 (multiplatform IPS) Archived 2017-04-04 at the Wayback Machine
 | This Unix-related article is a stub. You can help Wikipedia by expanding it. |
 | This installation software article is a stub. You can help Wikipedia by expanding it. |