Follow Techotopia on Twitter

On-line Guides
All Guides
eBook Store
iOS / Android
Linux for Beginners
Office Productivity
Linux Installation
Linux Security
Linux Utilities
Linux Virtualization
Linux Kernel
System/Network Admin
Programming
Scripting Languages
Development Tools
Web Development
GUI Toolkits/Desktop
Databases
Mail Systems
openSolaris
Eclipse Documentation
Techotopia.com
Virtuatopia.com

How To Guides
Virtualization
General System Admin
Linux Security
Linux Filesystems
Web Servers
Graphics & Desktop
PC Hardware
Windows
Problem Solutions
Privacy Policy

  




 

 

OpenSolaris 2008.11 Image Packaging System Guide
Previous

Glossary

action

A name and a key attribute of a package. A package is a collection of files, directories, links, drivers, and dependencies in a defined format. This collection represents the installable objects of a package. This collection is referred to as an action.

attribute

A representation of the settings of a package or an action.

authority

1. A person, group, or corporation that designs, creates, and publishes a package to a repository.

2. A location that is configured to point to a repository and might contain additional information about the package, such as the publisher of the package. The repository, in turn, serves the packages from the (default) authority, for downloading purposes. The developer-quality packages managed by Sun and made available through https://pkg.opensolaris.com are an example of an authority.

beadm utility

The beadm utility is the user interface for managing boot environments in OpenSolaris software. The beadm command is the replacement for the Solaris Live Upgrade commands, for example, luupgrade(1M) and lucreate(1M).

boot environment (BE)

An instance of a bootable OpenSolaris environment consisting of a set of mount points, file systems, ZFS datasets, and possibly non-global zones. A boot environment is a collection of mandatory file systems that are critical to the operation of the Solaris OS. The active boot environment is the one that is currently booted. Exactly one active boot environment can be booted. An inactive boot environment is not currently booted, but can be in a state of waiting for activation on the next reboot.

catalog

All packages in a repository published by an authority. The packages in a catalog are associated with a specific authority.

clone

An exact copy. For installation, a clone could be an exact copy of an operating system, a file system, or a volume. This copy has 100–percent compatibility with the original.

dataset

A generic name for the following ZFS entities: clones, file systems, snapshots, or volumes. Each dataset is identified by a unique name in the ZFS namespace.

fault management resource identifier (FMRI)

The fault management resource identifier (FMRI) is an identifier in each package. The FMRI includes descriptive information about a package, such as the package name, version information, date, and authority. The pkg command uses these identifiers when performing actions on the package. See the pkg(1) Uses FMRIs section for more information.

file system (ZFS)

A ZFS dataset of the type “filesystem” that is mounted within the standard system namespace and behaves like other file systems.

image

A collection of software in a package that comprises an entire operating system. The package is suitable for installation. See ISO image, network installation image.

ISO image

A collection of software that comprises an entire operating system in a single file. The ISO image can be made available for distribution from the Internet. An ISO image contains file systems suitable for creating a bootable CD or DVD. The ISO image is bootable and is usable for installation and other purposes.

mirror
  1. In IPS, an identical copy of data in a repository. A repository can be copied and the data resynchronized to maintain identical repositories in separate locations.

  2. In ZFS, a virtual device that stores identical copies of data on two or more disks. If any disk in a mirror fails, any other disk in that mirror can provide the same data.

network installation image

A collection of software that comprises the entire operating system. The image can be installed over a local area network (LAN).

origin repository

The original repository where the package was first published. The pkg(5) clients always access the origin repository to obtain an authority's (repository's) catalog, even though the clients might download package content from a mirror repository.

package

A collection of files, directories, links, drivers, and dependencies in a defined format.

pool

A logical group of devices describing the layout and physical characteristics of the available storage. Space for datasets is allocated from a pool.

preferred repository

A default repository that is the source for packages. If a user does not explicitly specify a repository when installing and updating packages, the preferred authority is chosen as the source for packages.

During the creation of an image, the initially specified authority is marked as the preferred authority. Any one of the authorities associated with an image might be set as the preferred authority by using the set-authority command with the -P option.

relocatable package

A package that enables a user to specify the installation path of the package.

repository

A location where packages are available for download. A repository can contain packages from many authorities. Conversely, many repositories can contain packages from a single authority. Also called the depot server.

rollback

A reversion to the boot environment that ran prior to a specific transaction. Use rollback when you are activating an environment and the boot environment that is designated for booting fails or shows some undesirable behavior. Rollback is known as fallback in Solaris Live Upgrade.

snapshot

A read-only image of a file system or boot environment at a given point in time. A snapshot is not bootable.

tag

In IPS, a representation of the settings of a file.

upgrade

An installation that merges files with existing files and preserves modifications where possible.

An upgrade of the OpenSolaris OS merges the new version of the OpenSolaris OS with the existing files on the system's disk or disks. An upgrade saves as many modifications as possible that you have made to the previous version of the OS.

The OpenSolaris release use the pkg image-update command to upgrade all installed packages in the current image to the latest available version.

USB image

A collection of software that comprises an entire operating system in a single file. The image that can be copied to a USB flash drive. The usbcopy utility is the only method of copying and is available on OpenSolaris. The USB image is a bootable image and is usable for installation and other purposes. Note: The Distribution Constructor outputs a USB image that might work in other types of flash memory devices, but due to lack of driver support in Open Solaris, other devices are unlikely to work.

ZFS file system

A ZFS dataset of type “filesystem” that is mounted within the standard system namespace and behaves like other file systems.

Previous

 
 
  Published under the terms fo the Public Documentation License Version 1.01. Design by Interspire