Linux Revision control
The Linux code used to be maintained without the aid of a version control system, mainly due to the chagrin of Linus Torvalds in relation to centralized systems.
In 2002, the development of Linux switched to BitKeeper, a version control system that met the technical requirements of Linus Torvalds. BitKeeper was made available for Linus and others for free, but it was not free software, which created controversy. The system did not provide any interoperability with open systems like CVS and Subversion.
In April 2005, however, a larger effort to carry out the reverse-engineering the BitKeeper system led by Andrew Tridgell BitMover, the company that held the BitKeeper, to stop supporting the Linux development community. In response, Linus Torvalds and others wrote a new version control system for the task, called Git. The new system was put in weeks and months doies the first official release of the core was performed using git. The git soon became a separate in their own right and won more choices in the community of free software.
Linux Version numbering
Linux provides three numbering schemes.
The first version of the core was 0.01. This was followed by 0.02, 0.03, 0.10, 0.11, 0.12 (the first release under GPL), 0.95, 0.96, 0.97, 0.98, 0.99 and then 1.0. From 0.95 there were several releases of fixes between versions.
After the release of 1.0, and until the release of 2.6, the version was made up of “ABC”, where A was defined as the kernel version, B as the major review of the core, and C minor revision to the core. The version was changed when major changes in the code and the concept of the core occurred twice in the history of the nucleus: in 1994 (version 1.0) and 1996 (version 2.0). The major revisions were used according to the numbering system even-odd traditional. A minor revision was changed when security fixes, defects or new features were implemented in the core.
Since 2004, after the release of version 2.6.0, the core developers discussed the scheme and release versions and finally, Linus Torvalds and others decided that a smaller release cycle would be beneficial. Since then, the version was composed of three or four numbers. The first two have become quite irrelevant, being the third number the current version of the core, and the room number has only updates for security patches and defects.
The first use of the room number when a serious error occurred that required immediate correction, was found in the NFS code of 2.6.8. However, there were no other changes to ligitimizar the launch of a new minor revision (which would have been 2.6.9). So, 126.96.36.199 was released, with only one amendment being made to correct the defect. With 2.6.11, it was adopted adopted as official policy for the new versions. Then it became common fixes for porting large already made and indicate this by updating the room number.
Prerelease regular development candidates are appointed to launch, which is indicated by adding the suffix ‘rc’ version of the core, followed by an ordinal number.
Some times, too, the release will have a suffix such as ‘tip’, indicating another extension of development, usually but not always, the initials of the person who created it. For example, ‘ck’ means Con Kolivas, ‘ac’ Alan Cox, etc.. Sometimes the letters are related to the development area of the main branch from which the nucleus is built, eg ‘wl’ indicates a test build wireless network (Wireless). Also, GNU / Linux distributions can create their own endings, with different numbering systems, and for transport of patches for their versions of distribution “Enterprise” (e.g., stable but older).
Torvalds and his team have continued to release new versions, consolidating contributions from other developers and introducing their amendments. Before the release of version 2.6, the lower version number (the second component) showed a steady pair: 1.0.x, 1.2.x, 2.0.x, 2.2.x and 2.4.x; launches with a lower version number odd versions correspond to development. The third component of the version number corresponds to corrections (releases) of version. From version 2.6, Torvalds changed this pattern, creating a fourth digit.
Thus, the tree and stable development of confused. Currently, it is a version much more stable the greater the fourth digit. While Torvalds continues to launch the latest development releases, maintenance releases of “stable” older is delegated to others, including David Weinehal (2.0), Alan Cox, and later Marc-Christian Petersen (2.2), Marcelo Tosatti and after Willy Tarreau (2.4) and even Torvalds, Andrew Morton and Adrian Bunk (2.6). In addition to the core “official”, “trees” alternatives can be obtained from other sources. Complete operating system vendors maintain their own versions of Linux, where, for example, include device drivers that are not included in the official version.
Study: From Wikipedia, the free encyclopedia. The text is available under the Creative Commons.
- Cloud Computing: The Concept and Examples of its Virtual Services | Part 1 - July 23, 2012
- Why Rapidly Growing Companies Need Cloud Computing | Part 1 - July 22, 2012
- Web Designing Process | Strategic Planning | Part 1 - August 7, 2011