Linuxoids are a vivid example of the quality work of numerous teams of professional developers. In the field of Linux systems, the logic of development has acquired a completely different aspect, preserving and increasing promising relic ideas in the field of system programming.
Windows as a programming example and Apple as a technical one have achieved a lot, but the Linux family is something else. Like many diverse peoples, they simply settled and work successfully. In this article, we'll take a look at Debian: Versions, Builds, and Benchmarks.
Variety, assembly and source
Debian version 9 is a spectrum of options. In general, this is a special representative of the Linuxoid family, aimed at professionals. It is supported by qualified development teams around the world. Debian 9.8 supports a multi-million dollar army of information resources.
Meanwhile:
This release mainly adds fixes for security issues, but also introduces a fewamendments for serious problems.
So it says on the official website of the project. Please note that this release is not a new version of Debian 9, but only updates some of the included packages.
Similar to the appearance of almost every popular and full-featured software product. Skipping a version number has long been out of the question for consumers, if even Windows can do it.
Linuxoids tend to declare the openness of the code. In practice, this means "assembly". This is not a standalone software product, but it is the same product, only assembled by different people or in different combinations of components.
The first or last version of Debian downloaded from the official site is absolutely "meaningless". The source is important, and this has long been not only the official site. Often the "best source" for a stable version will be the system administrator of a stable, large company.
Time requirements and landmarks
Everything should work stably, "without panic". If the server was "upgraded" on Debian version 8, you need to seriously think before moving to the "next" level.
The opinion of authoritative sources is not much different from the quote above. As such, it's not as important to know the version of Debian that will close consumer tasks as it is to ensure that these tasks are completed in a continuous and fail-safe cycle.
The main requirement of the consumer is stability and continuity. Safety, reliability and other parametersare extremely important. But if the company's infrastructure can't move quickly from Debian version 9.8 to what is likely to be a radically new version 10, then what will be the consequences …
Linuxoids always follow their rule: don't panic. Today this is not enough. Obviously: the version number for any serious software product is just a guideline. It should not be considered the basis for making a decision.
The functionality of Debian version 8 is sufficient even today. There are no special reasons for choosing nine. For example, many current resources work on CentOS 6 and do not plan to switch to their older brother - the seven. Apparently there are serious reasons for this.
The consumer's guideline in choosing a particular software product is to study the functionality of the version, and not decide on a possible migration to the next version later.
Inviolability of functionality and updates
Feature: Updates. For Linux systems, "update" and "upgrade" are the holy of holies. Debian version 9 will be updated in the same way as version 8. In theory, each next version should include "updates" of the previous one. In some part of the code it is.
A characteristic feature of programming is the rigidity of syntactic constructions. In addition, the larger the development team, the faster the number of servers grows (for example, on Debian), the more difficult it is to change anything.
Updates come down to fixing bugs, fixing particular problems, refiningrelationships or data formats. Ultimately, the factor of the inviolability of the functional is formed.
The hardware component is constantly evolving. It works, but it may in some way or somehow not meet the expectations of the already written code.
A simple example. Downloading the assembly debian-live-9.8.0-amd64-xfce.iso from the official website for the purpose of deploying a virtual machine system will not allow you to install Proxmox Virtual Environment (Proxmox VE) on all computing platforms. But if desired, the problem can be easily solved - a matter of time and qualifications. Another build - debian-9.8.0-amd64-netinst.iso is installed on the fly and makes Proxmox VE work right away.
The server itself is of relative importance. Much more important is the functionality deployed on it, for example, Apache / NGiNX, PHP, MySQL or a higher level - Proxmox VE. The modern consumer is a demanding information system, even if two or three people work in it. The modern consumer can process huge amounts of information or take on serious responsibility for solving small problems.
In all cases, and here Debian is no exception, it is important to choose not so much a version as a product with a possible (accessible) environment for it to focus only on this "complex build" that is understandable to the consumer. Choosing such a comprehensive solution is a few years in which Debian can easily offer 10, 11, 12, … versions.
Migration of functionality and information
For more than ten years, the word "migration" has become not only understood, but also really in demand. ServersThe World Wide Web contains a huge amount of information. Collectively, they represent an "independently developing" functionality.
From this point of view, the consumer can hope for the developer: each next version of the software product will be able to take everything that the previous one provides.
But it would be better like this: the consumer considers the "complex assembly" kit he has chosen as a frame, and positions his information system:
- as mobile as possible;
- minimally tied to a specific framework.
Debian is a great system. It provides the possibility of stable and reliable operation, but this is a building. Information "lives" in this building. Its structure and "living" rules should not be tied to building elements.
