Misplaced Pages

#836163

42-410: OVF may refer to: Open Virtualization Format , an open standard for packaging and distributing virtual appliances Optical viewfinder Topics referred to by the same term [REDACTED] This disambiguation page lists articles associated with the title OVF . If an internal link led you here, you may wish to change the link to point directly to

84-526: A tarball , for distribution or backup purposes. The name is derived from "tape archive", as it was originally developed to write data to sequential I/O devices with no file system of their own, such as devices that use magnetic tape . The archive data sets created by tar contain various file system parameters, such as name, timestamps, ownership, file-access permissions, and directory organization. POSIX abandoned tar in favor of pax , yet tar sees continued widespread use. The command-line utility

126-566: A new empty directory and extract the archive into it—or avoid the tar file entirely. Most graphical tools can display the contents of the archive before extracting them. Vim can open tar archives and display their contents. GNU Emacs is also able to open a tar archive and display its contents in a dired buffer. The tar format was designed without a centralized index or table of content for files and their properties for streaming to tape backup devices. The archive must be read sequentially to list or extract files. For large tar archives, this causes

168-402: A performance penalty, making tar archives unsuitable for situations that often require random access to individual files. With a well-formed tar file stored on a seekable (i.e. allows efficient random reads) medium, the tar program can still relatively quickly (in linear time relative to file count) look for a file by skipping file reads according to the "size" field in the file headers. This

210-416: A specified date. Basic options: Create an archive file archive.tar from the file README.txt and directory src : Extract contents for the archive.tar into the current directory: Create an archive file archive.tar.gz from the file README.txt and directory src and compress it with gzip  : Extract contents for the archive.tar.gz into the current directory: A tarpipe

252-406: A user has only a very old tar available, which does not feature those security measures, these problems can be mitigated by first examining a tar file using the command tar tf archive.tar , which lists the contents and allows to exclude problematic files afterwards. These commands do not extract any files, but display the names of all files in the archive. If any are problematic, the user can create

294-479: Is a tar archive file with the OVF directory inside. OVF has generally been broadly accepted. Several virtualization players in the industry have announced support for OVF. Tar (computing) u s t a r \040 \040 \0  (for old GNU tar format) In computing , tar is a computer software utility for collecting many files into one archive file , often referred to as

336-452: Is designed so that all implementations able to read the UStar format will be able to read the pax format as well. The only exceptions are files that make use of extended features, such as longer file names. For compatibility, these are encoded in the tar files as special x or g type files, typically under a PaxHeaders.XXXX directory. A pax-supporting implementation would make use of

378-482: Is in use. The UStar format allows for longer file names and stores additional information about each file. The maximum filename size is 256, but it is split among a preceding path "filename prefix" and the filename itself, so can be much less. The type flag field can have the following values: POSIX.1-1988 vendor specific extensions using link flag values 'A'–'Z' partially have a different meaning with different vendors and thus are seen as outdated and replaced by

420-517: Is known as extended tar format or pax format. The new tar format allows users to add any type of vendor-tagged vendor-specific enhancements. The following tags are defined by the POSIX standard: In 2001, the Star program became the first tar to support the new format. In 2004, GNU tar supported the new format, though it does not write it as its default output from the tar program yet. The pax format

462-461: Is older versions of GNU tar, when running on the MASSCOMP RTU (Real Time Unix) operating system, which supported an O_CTG flag to the open() function to request a contiguous file; however, that support was removed from GNU tar version 1.24 onwards. In 1997, Sun proposed a method for adding extensions to the tar format. This method was later accepted for the POSIX.1-2001 standard. This format

SECTION 10

#1732794608837

504-464: Is preceded by a 512-byte header record. The file data is written unaltered except that its length is rounded up to a multiple of 512 bytes. The original tar implementation did not care about the contents of the padding bytes, and left the buffer data unaltered, but most modern tar implementations fill the extra space with zeros. The end of an archive is marked by at least two consecutive zero-filled records. (The origin of tar's record size appears to be

546-453: Is the basis for option -n in GNU tar. When a tar file is compressed whole, the compression format, being usually non-seekable, prevents this optimization from being done. A number of "indexed" compressors, which are aware of the tar format, can restore this feature for compressed files. To maintain seekability, tar files must be also concatenated properly, by removing the trailing zero block at

588-579: Is the method of creating an archive on the standard output file of the tar utility and piping it to another tar process on its standard input , working in another directory, where it is unpacked. This process copies an entire source directory tree including all special files, for example: The tar format continues to be used extensively for open-source software distribution . *NIX-distributions use it in various source- and binary-package distribution mechanisms, with most software source code made available in compressed tar archives. The original tar format

630-557: Is the number of blocks per record. The default is 20, producing 10  KiB records. There are multiple tar file formats, including historical and current ones. Two tar formats are codified in POSIX: ustar and pax . Not codified but still in current use is the GNU tar format. A tar archive consists of a series of file objects, hence the popular term tarball , referencing how a tarball collects objects of all kinds that stick to its surface. Each file object includes any file data, and

672-866: The Distributed Management Task Force (DMTF) a proposal for OVF, then named "Open Virtual Machine Format". The DMTF subsequently released the OVF Specification V1.0.0 as a preliminary standard in September, 2008, and V1.1.0 in January, 2010. In January 2013, DMTF released the second version of the standard, OVF 2.0 which applies to emerging cloud use cases and provides important developments from OVF 1.0 including improved network configuration support and package encryption capabilities for safe delivery. ANSI has ratified OVF 1.1.0 as ANSI standard INCITS 469-2010. OVF 1.1

714-412: The metadata for the OVF package, such as name, hardware requirements, references to the other files in the OVF package and human-readable descriptions. In addition to the OVF descriptor, the OVF package will typically contain one or more disk images , and optionally certificate files and other auxiliary files. The entire directory can be distributed as an Open Virtual Appliance (OVA) package, which

756-483: The 100 characters are stored in @LongLink entries that would be seen as ordinary files by TAR utilities unaware of this feature. Similarly, the PAX format uses PaxHeaders entries. Many older tar implementations do not record nor restore extended attributes (xattrs) or access-control lists (ACLs). In 2001, Star introduced support for ACLs and extended attributes, through its own tags for POSIX.1-2001 pax. bsdtar uses

798-535: The 512-byte disk sectors used in the Version 7 Unix file system.) The final block of an archive is padded out to full length with zeros. The file header record contains metadata about a file. To ensure portability across different architectures with different byte orderings , the information in the header record is encoded in ASCII . Thus if all the files in an archive are ASCII text files, and have ASCII names, then

840-410: The POSIX.1-2001 extensions that also include a vendor tag. Type '7' (Contiguous file) is formally marked as reserved in the POSIX standard, but was meant to indicate files which ought to be contiguously allocated on disk. Few operating systems support creating such files explicitly, and hence most TAR programs do not support them, and will treat type 7 files as if they were type 0 (regular). An exception

882-411: The archive is essentially an ASCII text file (containing many NUL characters ). The fields defined by the original Unix tar format are listed in the table below. The link indicator/file type table includes some modern extensions. When a field is unused it is filled with NUL bytes. The header uses 257 bytes, then is padded with NUL bytes to make it fill a 512 byte record. There is no "magic number" in

SECTION 20

#1732794608837

924-436: The checksum both ways, and treat it as good if either the signed or unsigned sum matches the included checksum. Unix filesystems support multiple links (names) for the same file. If several such files appear in a tar archive, only the first one is archived as a normal file; the rest are archived as hard links, with the "name of linked file" field set to the first one's name. On extraction, such hard links should be recreated in

966-410: The cloud era. The most significant improvements include support for network configuration along with the ability to encrypt the package to ensure safe delivery. An OVF package consists of several files placed in one directory. An OVF package always contains exactly one OVF descriptor (a file with extension .ovf). The OVF descriptor is an XML file which describes the packaged virtual machine; it contains

1008-508: The end of each file. Another issue with tar format is that it allows several (possibly different) files in archive to have identical paths and filenames. When extracting such archive, usually the latter version of a file overwrites the former. This can create a non-explicit (unobvious) tarbomb, which technically does not contain files with absolute paths or referring to parent directories, but still causes overwriting files outside current directory (for example, archive may contain two files with

1050-401: The file size, only 11 octal digits can be stored. This gives a maximum file size of 8 gigabytes on archived files. To overcome this limitation, in 2001 star introduced a base-256 coding that is indicated by setting the high-order bit of the leftmost byte of a numeric field. GNU-tar and BSD-tar followed this idea. Additionally, versions of tar from before the first POSIX standard from 1988 pad

1092-404: The file suffix .tar (e.g. somefile.tar ). A tar archive file contains uncompressed byte streams of the files which it contains. To achieve archive compression, a variety of compression programs are available, such as gzip , bzip2 , xz , lzip , lzma , zstd , or compress , which compress the entire tar archive. Typically, the compressed form of the archive receives a filename by appending

1134-477: The file system. Most modern tar programs read and write archives in the UStar ( Unix Standard TAR ) format, introduced by the POSIX IEEE P1003.1 standard from 1988. It introduced additional header fields. Older tar programs will ignore the extra information (possibly extracting partially named files), while newer programs will test for the presence of the "ustar" string to determine if the new format

1176-488: The header, for file identification. Pre-POSIX.1-1988 (i.e. v7) tar header: The pre-POSIX.1-1988 Link indicator field can have the following values: Some pre-POSIX.1-1988 tar implementations indicated a directory by having a trailing slash (/) in the name. Numeric values are encoded in octal numbers using ASCII digits, with leading zeroes. For historical reasons, a final NUL or space character should also be used. Thus although there are 12 bytes reserved for storing

1218-421: The implementations below). The history of tar is a story of incompatibilities, known as the "tar wars". Most tar implementations can also read and create cpio and pax (the latter actually is a tar -format with POSIX -2001-extensions). Key implementations in order of origin: Additionally, most pax and cpio implementations can read and create multiple types of tar files. tar archive files usually have

1260-410: The information, while non-supporting ones like 7-Zip would process them as additional files. Besides creating and extracting archives, the functionality of the various archival utilities varies. For example, implementations might automatically detect the format of compressed TAR archives for extraction so the user does not have to specify it, and let the user limit adding files to those modified after

1302-427: The intended article. Retrieved from " https://en.wikipedia.org/w/index.php?title=OVF&oldid=933033384 " Category : Disambiguation pages Hidden categories: Short description is different from Wikidata All article disambiguation pages All disambiguation pages Open Virtualization Format The standard describes an "open, secure, portable, efficient and extensible format for

OVF - Misplaced Pages Continue

1344-431: The packaging and distribution of software to be run in virtual machines ". The OVF standard is not tied to any particular hypervisor or instruction set architecture . The unit of packaging and distribution is a so-called OVF Package which may contain one or more virtual systems each of which can be deployed to a virtual machine. In September 2007 VMware , Dell , HP , IBM , Microsoft and XenSource submitted to

1386-402: The same path and filename, first of which is a symlink to some location outside current directory, and second of which is a regular file; then extracting such archive on some tar implementations may cause writing to the location pointed to by the symlink). Historically, many systems have implemented tar, and many general file archivers have at least partial support for tar (often using one of

1428-409: The star extensions to support ACLs. More recent versions of GNU tar support Linux extended attributes, reimplementing star extensions. A number of extensions are reviewed in the filetype manual for BSD tar, tar(5). A tarbomb , in hacker slang , is a tar file that contains many files that extract into the working directory. Such a tar file can create problems by overwriting files of the same name in

1470-410: The tape between blocks (for the tape to physically start and stop moving). Some tape drives (and raw disks) support only fixed-length data blocks. Also, when writing to any medium such as a file system or network, it takes less time to write one large block than many small blocks. Therefore, the tar command writes data in records of many 512  B blocks. The user can specify a blocking factor, which

1512-758: The tar command was indicated for withdrawal in favor of pax command at least since 1994. Today, Unix-like operating systems usually include tools to support tar files, as well as utilities commonly used to compress them, such as xz , gzip , and bzip2 . The tar command has also been ported to the IBM i operating system. BSD-tar has been included in Microsoft Windows since Windows 10 April 2018 Update , and there are otherwise multiple third party tools available to read and write these formats on Windows. Many historic tape drives read and write variable-length data blocks , leaving significant wasted space on

1554-473: The values with spaces instead of zeroes. The checksum is calculated by taking the sum of the unsigned byte values of the header record with the eight checksum bytes taken to be ASCII spaces (decimal value 32). It is stored as a six digit octal number with leading zeroes followed by a NUL and then a space. Various implementations do not adhere to this format. In addition, some historic tar implementations treated bytes as signed. Implementations typically calculate

1596-508: The working directory and, like a tarbomb, have the potential to overwrite existing files. However, modern versions of FreeBSD and GNU tar do not create or extract absolute paths and parent-directory references by default, unless it is explicitly allowed with the flag -P or the option --absolute-names . The bsdtar program, which is also available on many operating systems and is the default tar utility on Mac OS X v10.6, also does not follow parent-directory references or symbolic links. If

1638-491: The working directory, or mixing one project's files into another. It is at best an inconvenience to the user, who is obliged to identify and delete a number of files interspersed with the directory's other contents. Such behavior is considered bad etiquette on the part of the archive's creator. A related problem is the use of absolute paths or parent directory references when creating tar files. Files extracted from such archives will often be created in unusual locations outside

1680-644: Was adopted in August 2011 by ISO/IEC JTC 1/SC 38 of the International Organization for Standardization (ISO) and the International Electrotechnical Commission (IEC) as an International Standard ISO/IEC 17203. OVF 2.0 brings an enhanced set of capabilities to the packaging of virtual machines, making the standard applicable to a broader range of cloud use cases that are emerging as the industry enters

1722-451: Was created in the early days of Unix, and despite current widespread use, many of its design features are considered dated. Other formats have been created to address the shortcomings of tar. Due to the field size , the original TAR format was unable to store file paths and names in excess of 100 characters. To overcome this problem while maintaining readability by existing TAR utilities , GNU tar stores file paths and names in excess of

OVF - Misplaced Pages Continue

1764-515: Was first introduced in the Version 7 Unix in January 1979, replacing the tp program (which in turn replaced "tap"). The file structure to store this information was standardized in POSIX .1-1988 and later POSIX.1-2001, and became a format supported by most modern file archiving systems. The tar command was abandoned in POSIX.1-2001 in favor of pax command, which was to support ustar file format;

#836163