Apache Felix is an open source implementation of the OSGi Core Release 6 framework specification. The initial codebase was donated from the Oscar project at ObjectWeb . The developers worked on Felix for a full year and have made various improvements while retaining the original footprint and performance. On June 21, 2007, the project graduated from incubation as a top level project and is considered the smallest size software at Apache Software Foundation .
22-427: ‹The template How-to is being considered for merging .› To run Apache Felix OSGi, you need to download the felix-framework-4.x.x.tar.gz or felix-framework-4.x.x.zip compressed file from the site. Once you have extracted the Felix framework distribution, from the command line in the extracted directory type the following: java -jar bin/felix.jar After bundles are installed and running, typing
44-794: A POSIX standard when formally approved by the ISO. POSIX.1-2001 (or IEEE Std 1003.1-2001) equates to the Single UNIX Specification, version 3 minus X/Open Curses . This standard consisted of: IEEE Std 1003.1-2004 involved a minor update of POSIX.1-2001. It incorporated two minor updates or errata referred to as Technical Corrigenda (TCs). Its contents are available on the web. Base Specifications, Issue 7 (or IEEE Std 1003.1-2008 , 2016 Edition). This standard consists of: IEEE Std 1003.1-2017 (Revision of IEEE Std 1003.1-2008) - IEEE Standard for Information Technology—Portable Operating System Interface (POSIX(R)) Base Specifications, Issue 7
66-515: A command like help from the console will display all available commands, which are: Felix Framework Distribution List of subprojects of which the Apache Felix framework consists. The projects listed below highlight the adoption of Apache Felix: Compress compress is a Unix shell compression program based on the LZW compression algorithm. Compared to gzip 's fastest setting, compress
88-571: A patent on the algorithm. Spencer Thomas of the University of Utah took this article and implemented compress in 1984, without realizing that a patent was pending on the LZW algorithm. The GIF image format also incorporated LZW compression in this way, and Unisys later claimed royalties on implementations of GIF. Joseph M. Orost led the team and worked with Thomas et al. to create the 'final' (4.0) version of compress and published it as free software to
110-502: A presence on Unix and BSD systems and the compress and uncompress commands have also been ported to the IBM i operating system. The US LZW patent expired in 2003, so it is now in the public domain in the United States. All patents on the LZW worldwide have also expired (see Graphics Interchange Format#Unisys and LZW patent enforcement ). As of POSIX.1-2024 compress supports
132-465: Is actually a bug. LZW does not require any alignment. This bug existed for more than 35 years and was in the original UNIX compress , ncompress , gzip and the Windows port. All application/x-compress files were created using this bug. Some compress implementations write random bits from uninitialized buffer in paddings. There is no guarantee that the paddings will be zeroes. The decompressor must ignore
154-503: Is allowed for Point-to-Point Protocol in RFC 1977 and for HTTP/1.1 in RFC 9110 , though it is rarely used in modern deployments as the better deflate/gzip is available. The gunzip utility is able to decompress .Z files. POSIX#POSIX.1-2024 The Portable Operating System Interface ( POSIX ; IPA : / ˈ p ɒ z . ɪ k s / ) is a family of standards specified by
176-441: Is available from either The Open Group or IEEE. It is technically identical to POSIX.1-2008 with Technical Corrigenda 1 and 2 applied. Its contents are available on the web. IEEE Std 1003.1-2024 - IEEE Standard for Information Technology—Portable Operating System Interface (POSIX(R)) Base Specifications, Issue 8 was published on 14 June 2024. Its contents are available on the web. POSIX mandates 512-byte default block sizes for
198-605: Is divided into two parts: The development of the POSIX standard takes place in the Austin Group (a joint working group among the IEEE, The Open Group , and the ISO/IEC JTC 1/SC 22 /WG 15). Before 1997, POSIX comprised several standards: After 1997, the Austin Group developed the POSIX revisions. The specifications are known under the name Single UNIX Specification , before they become
220-438: Is not merely to create an uncompressed copy of the file, but also to restore the timestamp and other attributes of the compressed file. For files produced by compress on other systems, uncompress supports 9- to 16-bit compression. The LZW algorithm used in compress was patented by Sperry Research Center in 1983. Terry Welch published an IEEE article on the algorithm in 1984, but failed to note that he had applied for
242-485: Is slightly slower at compression, slightly faster at decompression, and has a significantly lower compression ratio . 1.8 MiB of memory is used to compress the Hutter Prize data, slightly more than gzip's slowest setting. The uncompress utility will restore files to their original state after they have been compressed using the compress utility. If no files are specified, the standard input will be uncompressed to
SECTION 10
#1732885141110264-492: The DEFLATE algorithm used in gzip . The output binary consists of bit groups. Each bit group consists of codes with fixed amount of bits (9–16). Each group, except the last group, is aligned to the number of bits per code multiplied by 8 and right padded with zeroes. The last group is aligned to 8 bit octets and padded with zeroes. More information can be found at an issue on the ncompress GitHub repository. Example: It
286-491: The IEEE Computer Society for maintaining compatibility between operating systems . POSIX defines application programming interfaces (APIs), along with command line shells and utility interfaces, for software compatibility (portability) with variants of Unix and other operating systems. POSIX is also a trademark of the IEEE. POSIX is intended to be used by both application and system developers. Originally,
308-553: The UNIX System V shell. Many user-level programs, services, and utilities (including awk , echo , ed ) were also standardized, along with required program-level services (including basic I/O : file , terminal , and network ). POSIX also defines a standard threading library API which is supported by most modern operating systems. In 2008, most parts of POSIX were combined into a single standard (IEEE Std 1003.1-2008 , also known as POSIX.1-2008). As of 2014 , POSIX documentation
330-463: The df and du utilities, reflecting the typical size of blocks on disks. When Richard Stallman and the GNU team were implementing POSIX for the GNU operating system , they objected to this on the grounds that most people think in terms of 1024 byte (or 1 KiB ) blocks. The environment variable POSIX_ME_HARDER was introduced to allow the user to force the standards-compliant behaviour. The variable name
352-590: The 'net.sources' USENET group in 1985. U.S. patent 4,558,302 was granted in 1985, and this is why compress could not be used without paying royalties to Sperry Research, which was eventually merged into Unisys. compress has fallen out of favor in particular user-groups because it makes use of the LZW algorithm, which was covered by a Unisys patent – because of this, gzip and bzip2 increased in popularity on Linux -based operating systems due to their alternative algorithms, along with better file compression. compress has, however, maintained
374-696: The automated conformance tests and their certification has not expired and the operating system has not been discontinued. Some versions of the following operating systems had been certified to conform to one or more of the various POSIX standards. This means that they passed the automated conformance tests. The certification has expired and some of the operating systems have been discontinued. The following are not certified as POSIX compliant yet comply in large part: Mostly POSIX compliant environments for OS/2 : Partially POSIX compliant environments for DOS include: The following are not officially certified as POSIX compatible, but they conform in large part to
396-558: The name "POSIX" referred to IEEE Std 1003.1-1988, released in 1988. The family of POSIX standards is formally designated as IEEE 1003 and the ISO/IEC standard number is ISO / IEC 9945. The standards emerged from a project that began in 1984 building on work from related activity in the /usr/group association. Richard Stallman suggested the name POSIX to the IEEE instead of the former IEEE-IX . The committee found it more easily pronounceable and memorable, and thus adopted it. Unix
418-489: The standard output. Files compressed by compress are typically given the extension ".Z" (modeled after the earlier pack program which used the extension ".z"). Most tar programs will pipe their data through compress when given the command line option " -Z ". (The tar program in its own does not compress; it just stores multiple files within one tape archive.) Files can be returned to their original state using uncompress . The usual action of uncompress
440-619: The values in the paddings for compatibility. compress was standardized in X/Open CAE Specification in 1994, and further in The Open Group Base Specifications, Issue 6 and 7. Linux Standard Base does not requires compress. compress is often not installed by default in Linux distributions, but can be installed from an additional package. compress is available for FreeBSD, OpenBSD, MINIX, Solaris and AIX. compress
462-407: Was later changed to POSIXLY_CORRECT . This variable is now also used for a number of other behaviour quirks. Depending upon the degree of compliance with the standards, one can classify operating systems as fully or partly POSIX compatible. Current versions of the following operating systems have been certified to conform to one or more of the various POSIX standards. This means that they passed
SECTION 20
#1732885141110484-499: Was selected as the basis for a standard system interface partly because it was "manufacturer-neutral". However, several major versions of Unix existed—so there was a need to develop a common-denominator system. The POSIX specifications for Unix-like operating systems originally consisted of a single document for the core programming interface , but eventually grew to 19 separate documents (POSIX.1, POSIX.2, etc.). The standardized user command line and scripting interface were based on
#109890