GNU/Linux- multinational OS. And each country creates its own distributions, which are used both on workstations and on servers. Russia is not far behind, and there are several good (and not so good) Linux distributions which I will talk about. At the same time, I will talk about the most famous and popular distributions that are well developed and actively used. Go!
Rosa Linux- a distribution based on the now deceased Mandriva, and continuing its development. This distribution has several editions designed for different applications. The free desktop edition is Fresh, which includes the most recent and stable software. Editions "Cobalt", "Nickel", "Chromium" created for government agencies, and certified by the Russian Ministry of Defense and FSTEC. These distributions are not freely available. The server version was originally based on Red Hat Enterprise Linux (RHEL), was subsequently also transferred to the Mandriva base. Based on the Rosa project, the distribution kit is being developed OpenMandriva, which is "polygon" to test new software and technologies (like Fedora for RHEL).
Calculate Linux is a line of enterprise distributions based on the famous Gentoo(the one that is assembled from source codes during installation), but unlike it, they have a simple and understandable installer, high quality assembly and system utilities, as well as a very wide range of pre-installed software (in the Desktop edition there is even Skype). At the same time, Calculate is fully compatible with Gentoo, using its native system Portage for building and installing software, and also contains a large number of binary packages in the repository. Calculate has the following editions:
All versions of the distribution are distributed as bootable livecd image with the ability to install on HDD, USB-Flash or USB-HDD.
There are two editions of Runtu:
Russian Fedora Remix(or RFRemix) is a build based on the Fedora distribution. In addition to full Russification, it has the following differences:
Otherwise, it's a regular Fedora. Official site
Initially based on Mandrake(which later became Mandriva), but gradually began to turn into an independent system. A distinctive feature of ALT Linux is its package manager: it uses packages of the format RPM, as in RedHat-derived distributions, but they are controlled using the utility APT (Advanced Packaging Tool), which is "native" for Debian and its derivatives (such as Ubuntu). ALT Linux is also famous for being sent to many schools, and computer science textbooks contain tasks specifically for it (except for Windows). The distribution kit has both public free editions and versions for government agencies, FSTEC certified and the Ministry of Defense of the Russian Federation. The Simply Linux distribution is a lightweight edition of ALT Linux, containing a large amount of educational and multimedia software, as well as a simple and convenient desktop based on Xfce. Development of packages for ALT Linux, conducted in a special repository Sysyphus. The following editions are available:
School Server
School teacher
School Junior
School Master
The main feature of the kit is the integration of student and teacher workplaces. This feature allows not only to centrally manage the educational process, but also provides interaction between students and teachers in the usual form of chats and forums. Messages can contain tasks, their solutions and comments. It is also possible to exchange files of any format, both between a teacher and a student, and between students;
The manufacturer is developing the basic version of Astra Linux - Common Edition ( general purpose) and its modification Special Edition (special purpose):
This is a lightweight distro designed specifically for low-end hardware. The small size of the system (about 120 megabytes), allows it to fully boot into RAM for maximum performance. PuppyRus Linux is focused on x86 computers, optimized for maximum performance, and due to low hardware requirements, it can breathe a “second” life into outdated models.
PuppyRus inherited two original package systems from its predecessor Puppy Linux: .PET And .PUP. They are gzip-compressed files that contain directories containing files for installation. These directories have the same names and structure as standard directories in the UNIX file system.
Thus, the process of installing new packages is accompanied by unpacking the packages to the root directory. Package manager program PetGet monitors the installation process, registers the files that are copied from the package to the system, and records these changes in a separate file - the installation log. After unpacking, PetGet executes the installation script (script) also contained within the package.
When a package is uninstalled, PetGet removes all files derived from it, according to its installation log. After that, PetGet executes the post-installation script (script) that was previously included in the package. Official site
It is a Linux distribution based on the now undeveloped MOPS Linux(which in turn is based on Slackware). The main principles that the developers of the distribution adhere to are the ease of installation and development of the system, as well as the selection of the most stable programs.
Historically, AgiliaLinux is a direct descendant of the defunct MOPSLinux. At the time, MOPSLinux was generally based on the Slackware package base, gradually increasing its share of its own packages towards the end of its existence. AgiliaLinux has continued on this path and the package base is now independent. The package format is txz, and mpkg is used as the package manager. Official site
It would be perfectly legal for them to sell copies of this slightly modified Ubuntu versions(Let's call it Mubuntu = Modified Ubuntu)?
No. While software licenses may allow you to do this, a trademark license does not:
Any redistribution of modified versions of Ubuntu must be approved, certified or provided by Canonical if you intend to associate it with trademarks. Otherwise, you must remove and replace the Trademarks, and you will need to recompile the source code to create your own binaries. This does not affect your rights under any open source license applicable to any of the Ubuntu components. If you need to approve, certify, or submit modified versions for redistribution, you will need a license agreement from Canonical, which you can pay for. Behind additional information please contact us (as below).
You will need Canonical's permission to use: (i) any mark ending with the letters UBUNTU or BUNTU that is reasonably similar to trademarks or any similar similar brand, and (ii) any trademark in a domain name or URL or for merchandising purposes ,
You will be allowed to sell an unmodified version of Ubuntu, you will be allowed to sell a heavily modified version of Ubuntu that no longer mentions the Ubuntu name, but for this slightly modified version of Ubuntu you need an agreement with Canonical.
Yes, provided you meet the license terms for everything packaged software(sending source code, etc.) and don't violate any trademarks, copyright laws, etc. Also, you must make sure that your actions will not cause any harm to third parties like murder, etc.
Included closed source software must not violate the licenses of any libraries it uses (some licenses allow a binary dependency on closed source software and some do not).
As Serge said, yes. However, you may not modify parts that are GPL ( window manager GPL) and then close the source. You can't even use GPL libraries in a closed source code. So actually the answer should be: " NO", as if you closed the source with most of the system or desktop, by the time you are free and free from the GPL, it will no longer be relevant to Ubuntu. Also, I believe you require explicit permission from Canonical to use a word like Mubuntu. The question is really difficult. You need to do a lot of research and possibly hire a lawyer if you do this.
UPDATE
I thought I'd update the question because the comments are very long on whether you can use the GPL libraries in closed source. LGPL allows it *, GPL does not **. From the topic authority gnu.org/licenses/why-not-lgpl.html:
… the use of the Minor GPL allows the library to be used in proprietary programs; using the normal GPL for a library makes it only available to free software.
However, since most libraries are LGPL these days, the OP might not be as hard as I originally thought.
* There are still certain conditions that must be met in order to use the LGPL libraries.
** There are certain cases where you can use a closed source GPL library, for example if the software is not public and if the use of the library is not considered a modification or derivative work (for example, prelinking).
Suppose someone has downloaded a Linux distribution such as Ubuntu. Suppose it changes one part, let's say Window Manager.
No, you can't, because there are some projects protected by Canonical, but if you need to contribute, you need to sign the Canonical agreement:
Next projects covered by the Canonical agreement. If you would like to contribute to any of the projects below, please contact the project contacts listed in the third column.
To contribute, you need to sign the Canonical Agreement.
Would it be perfectly legal for them to sell copies of this slightly modified version of Ubuntu (let's call it Mubuntu = Modified Ubuntu)?
What if they made the original section of the new window closed? Will it still be legal to sell?
You cannot do this without permission from Canonical:
Limited use requiring trademark license
Permission from us must be used by any of the Trademarks under any circumstances other than those specifically permitted above. These include:
Any commercial use
Use on or in relation to a software product that includes or builds on top of a product supplied by us, if there is any commercial intent associated with that product.
- Use in a domain name or URL.
- Use for merchandising, such as on T-shirts and the like.
- Use of a name that includes the letters BUNTU in reference to computer hardware or software.
- Services relating to any of the above.
Choosing a LINUX distribution
Fedora Core
It is the most widely used Linux distribution for many years. Until recently, it was known as Red Hat. However, now the developer (the company of the same name) has retained this name for commercial implementations of its system. Its free implementation, intended for end users, is called Fedora Core.
Flaws:
Advantages:
ASPLinux
This is a domestically produced distribution developed by the company of the same name. It is a clone of Fedora Core (formerly Red Hat), slightly modified in terms of application software and adapted for our conditions.
It is distributed in several versions (not counting purely server versions): Deluxe with many disks and with a complete set of documentation, Standard - half as many disks, only the installation manual from the documentation, Express - a three-disc set with a short booklet.
Flaws:
Advantages:
Eyewitness impressions:
ASPLinux 9.0 was used on home computer, at work, and with two friends for over a year. Plus:
very good DIY constructor;
quite decent assembly of packages, Russification, documentation;
man pages in Russian in most cases, some in the translation of your disobedient servant;
everything bad that is usually rightly said about the rpm package management system has been successfully eliminated by the developers;
there were very few problems with addictions even in conditions of severe mockery of the system;
stability and security at a high level;
no inexplicable glitches were noticed, nothing distracted from the work itself;
repeatedly had to install ASPLinux 9.0 (only tsssss!!!) on top-secret equipment, on which, according to the general idea, the WSWS OS should have been installed;
bugs and rakes - none;
absolutely specific equipment simply could not be supported, but under an additional agreement, the drivers were written by specialists from the same ASP;
it is worth noting the correct technical support of a fairly high class - an argument that in those days favorably distinguished ASP from any competitors;
In minus:
the release of the ASPLinux 9.2 distribution kit, and then ASPLinux 10, coupled with a change in the company's management, crossed out many of the past merits of this respected team;
it cannot be said that they are unambiguously bad in all respects, but in comparison with ASPLinux distributions of versions 7.1, 7.3 and 9.0 they lose on all the points that I described above as advantages;
now the packages in the distribution are at least unconfigured.
As recently as today, I discussed with a novice user a problem that arose in ASPLinux 9.2 - there was no sound. Kernel 2.4.22, oss, graphic environment by default - Gnome (according to the precepts of Red Hat). and at the same time, in the xmms settings, the output extension used was the default ... attention! arts, and optionally - alsa; the problem is easy for some advanced user, but the beginner sees only that there is no sound.
Developers positioning their product as a desktop distribution shouldn't make such stupid mistakes.
It has three user editions: multi-disk Altlinux Master, lightweight Altlinux Junior and single-disk ALT Linux Compact.
Advantages(best ones first):
Flaws(in the beginning - the worst):
Peculiarities:
Developed by the German company of the same name, this distribution is now owned by Novell. It has a free Download-edition and several "boxed" options. The status of the latter is different, exhaustive information on this issue can be obtained from the following discussion.
Flaws:
Advantage and disadvantage at the same time:
Advantages:
All distributions listed above are based on *.rpm packages. We will not discuss the advantages and disadvantages of the batch system here. However, whatever the latter, two advantages of the rpm format are indisputable. The first is that it is the most common (after source) free software format. And the second - both the format itself and the utilities for working with it are described in detail in many "thick" books on Linux (Red Hat).
Unlike all distributions described earlier, backed by commercial firms, more or less large, Debian is the result of the work of a free community of developers (project website - http://www.debian.org). It is distributed in various forms (as iso-images, file sets, etc.), available both for free download and for replication and distribution.
Peculiarities
1. Unlike other common distributions (at least I don't know any analogues), Debian has three main branches: stable, testing and unstable.
The main convenience for the home user is that packages from several different branches can easily coexist in one system (with a footnote to dependencies, of course) at the same time; those. if you want to upgrade, say, one program to unstable, you can leave the rest of the system in the testing state.
It should be noted that the inclusion of specific software versions in other distributions included in the main branch into testing, unstable or even experimental is due not to less software stability compared to other distributions, but, on the contrary, to the greater strictness of the distribution kit authors to the mentioned stability.
2. Only free software; if ideology is important to you in open source/free software, you will find full adherence to it here. All programs with the slightest license deviations either fall into the non-free section, or are generally available only in third-party sources; thus, you are left with a choice - to use only free software in the strictest sense of this term, or to add something that does not fall under this strict understanding.
3. Debian doesn't actually have any release schedule for new versions. The motto of its developers is "it will come out when it's ready." On the one hand, this sometimes leads (as recently, for example) to protracted expectations, on the other hand, it completely excludes the release of a somehow cobbled together distribution kit, just to be in time for the announced release date (which happens with almost any software that has a declared release date - I speak as a developer).
Flaws
Perhaps the main disadvantage of Debian for a beginner compared to the distributions described above is the almost complete absence of centralized graphical configuration utilities (except, of course, such distribution-non-specific things, such as the KDE control center). Instead, there is a text mode interface for configuring individual packages (and the installer itself is made in the same style of text menus). The reverse side of this approach is the ability to reconfigure any individual package at any time with the command
$ dpkg-reconfigure package-name
without the need to remember in which branch of the system-wide customizer its settings are located.
The second drawback is that as a result of a strict attitude to the status of the software that is included in the main part of the distribution kit, this main part does not include drivers, say, for heaped video cards and soft printers. But if you have access to the Internet, this problem is easily solved, because. video drivers are in the non-free section of the distribution itself, and besides, semi-commercial distributions based on Debian (and fully compatible with it in terms of package format) are very rich in drivers.
Advantages
An additional factor, which can also be attributed to the advantages, is that a considerable number of so-called. LiveCD (of which the most famous, but far from the only one is Knoppix), which allow you to get acquainted with the features of the distribution kit without installing it, and with a positive result, deploy a full-fledged Debian system.
All of the distributions listed above are usually unequivocally recommended for novice users. For the following systems, however, this is not so obvious. However, they are sufficiently well-known, and therefore we consider it necessary to give some information about them - in a more free form. So that everyone could decide for themselves whether they are suitable for him as a "test of the pen", or not.
Slackware
It is the oldest (living) Linux distribution, from the very beginning to this day associated with the name of its creator - Patrick Volkerding. For more than 10 years, nothing has changed much (except for package versions, of course). Namely:
The lack of dependency control is both an advantage and a disadvantage. For example, I have about 150 packages in one folder, to install them all I need to run one command
$ installpkg ./*.tgz
Note, without any keys. But the fact that then something from the installed may not start is up to you to figure it out yourself.
However, there are also mechanisms for automated installation / updating from the Internet - there are a huge number of them: slapt-get, swaret, getpkg, slackpkg and a few more.
Russification is now reduced to the launch of just one script, there are many such scripts on the Web.
More or less decent desired settings can be done through the pkgtool utility (it also serves to manage packages), many graphical front-ends have been released for it.
There is an incredible amount of documentation on the distribution, answers to all questions have long been found - you just need to look a little. Since essentially nothing changes in the distribution, it is practically not subject to the aging factor. By the way, the documentation itself comes with the distribution - in English, but not bad.
There is no technical support in principle - and in principle it is not needed. You just need to remember the site www.slackware.ru - there are docks and a forum, and www.linuxpackages.net - here you can find ready-made packages and links to iso images.
Unicode is not yet brilliantly supported, at some points you need to take a tambourine and shaman.
In general, children, that is, beginners, are scared with this distribution: you should not start with it - it is complicated. Nothing of the kind, it is as simple as the first Soviet ruble, but its simplicity is just as well hidden.
Gentoo Linux is a distribution that is becoming more and more popular in the OpenSource community both due to its support for a large number of hardware platforms, as well as its exceptionally flexible and convenient system"portage", based on FreeBSD's PORTS.
Gentoo is a typical representative of the family of source-based distributions, which is the result of most of both its advantages and disadvantages. Whether this distribution is suitable for a novice user is a moot point. However, recently it has become widely known, and we felt it necessary to provide information so that this very novice user could answer it himself.
Advantages:
Peculiarities:
Flaws:
FreeBSD
Its difference from those described above is that it is not a Linux distribution, but a completely separate (albeit related) operating system. It is usually regarded as purely server platform(According to various estimates, up to 40% of Runet servers operate under its control). However, its use as a desktop operating system for ordinary users is not prohibited by anyone. Developed by FreeBSD by a community of independent developers, available for free download and replication from the project's servers.
Flaws:
Advantages:
And so that good finally triumphs -
In conclusion, the most important thing: no matter what distribution kit, and no matter what operating system you choose, this choice is unlikely to be the last and final in your life. You should be prepared for the fact that in search of the ideal, more than one or two options will be tried.
In the Linux world, we are used to seeing only clones. Debian, Ubuntu, Red Hat, SUSE - these are all different distributions, in which there is no fundamental difference. Half of the popular Linux distributions are forks of Debian or Ubuntu, others are forks of the ancient Slackware with a modified package manager and beautiful configurators. There is no trace of the former diversity, but maybe we are just looking badly?
A modern Linuxoid cannot be understood, but in the past, choosing a distribution was a real epic. Distributions really differed in many ways, and due to the lack of high speed internet and virtual machines, these differences played a very important role. Slackware offered end-to-end simplicity, Red Hat was detailed to the smallest detail and built-in configurators, Mandrake was equipped with a graphical installer, and Debian's mega-feature was APT, which allowed (you won't believe it!) Automatically download software from the Internet.
The greatest success was to get a four-disc set of Red Hat, which included everything graphic shells and a bunch of application software, but if that didn't work, Mandrake on two discs was fine. In those days, only a few could download a disk image, so numerous discs with the most popular distributions went around. The distro building itself was relatively simple and imbued with the just for fun spirit that produced numerous Frankensteins, including my own, which died somewhere at the bottom of a 10 GB Seagate drive.
Years passed, Seagate was killed by Kingston, and distributions turned into huge complex colossus, created to extort money from companies whose administrator suddenly persuaded the authorities to transfer servers to Linux. But somewhere among the numerous installations of Ubuntu and Linux Mint there are still those Frankensteins who bring something new to the world of Linux, albeit in honor of the next pulling money.
At the time, Slax impressed me so much that I joined a group of developers who intended to create a distribution based on his ideas. The group, however, quickly ceased to exist due to the unrealizability of the idea, but Slax continues to exist and be healthy.
Slax is not just a distribution, it's a purebred LiveCD, which, among other things, can be extended with modules. This is done using an elegant mechanism, which, I'm sure, is used in a bunch of other projects, but for the first time for such purposes it was used here - the Unionfs file system. The essence of the method is as follows: not being able to change the distribution's file system on a CD in order to install additional software, the Slax developers came up with a method for connecting file system images to it over the root.
All additional software for Slax is distributed as modules with the sb extension. The module is an image of the Squashfs file system (a simple FS with compression), which contains the application and all the files it needs, located in the file system paths where they should be in the running system (usr/bin/abiword, for example). It is worth putting this module in a special directory on a USB flash drive (/slax/modules) or cutting it onto a disk, and the system will automatically pick it up and mount it on top of the LiveCD root at boot (Unionfs mounts file systems on top of each other, like layers of a pie). As a result, an application will appear in the system that is not physically there.
The beauty of this idea is not only in its suitability for the LiveCD extension, but also in the absolute simplicity of implementation. No package managers, no version conflicts, no leftover applications in the file system, absolute protection from FS failures, the ability to roll back to a clean version of the OS. In general, the list can be long. But the main thing is that all this is obtained using a very simple mechanism that can be implemented in a few lines in the command interpreter language.
There's just one problem: building a complete distribution from hundreds of overlay filesystems will cost both performance and stability.
Another uncommon on Linux (but standard on OS X and Windows) approach to installing third-party software is the GoboLinux distribution. Instead of the /bin, /usr/bin, /usr/share and other directories familiar to any Unixoid, containing installed apps in a "spread" form across the system, GoboLinux uses a set of directories /Programs, /Users, /System, /Files, /Mount and /Depot.
In fact, the distribution follows the path of OS X. All system files are in the /System directory, and user-installed applications are in /Programs, each in its own separate directory (for example, /Programs/Firefox). As a result, it becomes possible to install different versions of one application (as an option - libraries), and to remove the software, it is enough to physically erase the directory.
However, there is a flaw in this directory organization that forced the GoboLinux developers to use several crutches. The problem is that, unlike applications for OS X, software for UNIX is written in accordance with the FHS standard, which assumes that the system has a standard directory tree that includes the very /bin, /etc, /lib, /usr and etc. Applications expect to see this structure on disk and may behave unpredictably if it is violated.
To solve this problem, the GoboLinux developers used two hacks: a special kernel module and symbolic links. The module hides all standard directories (/bin, /etc, etc.) when listing the root directory, but leaves it possible to access them directly. This makes it possible to hide the real directory structure from the user.
Links, in turn, solve the compatibility problem. All system libraries and applications stored in /System are symlinked in the /bin and /lib directories to allow the system to function properly. Compatibility third party applications provides an installer that creates new links for each installed application. So, when installing Firefox, the /usr/bin/firefox file will appear, which actually links to /Programs/Firefox/bin/firefox, as well as a number of other links.
Yes, this is a typical representative of the Frankenstein family, but it has its fans, especially among those who find the standard organization of the UNIX file system outdated and inefficient. And this, let's not argue, is true.
Speaking of package managers and the organization of the file system, one cannot fail to mention NixOS, perhaps the most interesting and “correct” distribution in terms of the technologies used. NixOS is built around two main ideas: a declarative system configuration model and a modern package manager, devoid of almost all the problems familiar to dpkg, rpm and the like.
Both of these technologies are closely related to each other and, working together, implement a very interesting principle of organizing a distribution kit, which allows you to describe any of its states (including all configuration files and a set of installed packages) using one central config. For example, I will give the following simple config /etc/nixos/configuration.nix:
# Loader location boot.loader.grub.device = "/dev/sda"; # The root partition of the system fileSystems."/".device = "/dev/sda1"; # Enable SSH by default services.sshd.enable = true; # Enable Apache (+ settings) services.httpd.enable = true; services.httpd.adminAddr=" [email protected]"; services.httpd.documentRoot = "/webroot";
This file describes standard settings a simple web server with SSH access. Yes, NixOS does allow you to keep settings different services in one file, but the point is not in this, but in the fact that, having this config, it is easy to clone the entire distribution. It is enough to copy this file to a freshly installed NixOS instance and run the command
$ nixos-rebuild switch
And voila. In a few minutes, we will have a distribution with SSH and Apache preconfigured and running. But the most interesting thing is that given command not just installs, configures and runs the software, but actually brings the distribution kit to the described state. This means that after executing the command, only SSH and the pre-configured Apache will really remain in the system and nothing but their dependencies and configs (in fact, an analogue of installing from scratch).
This functionality can be used to quickly deploy a distribution, switch between states, quickly transfer the system between physical or virtual machines, expand clusters, and more. In addition, thanks to the package manager, NixOS guarantees the integrity of the system during updates and even allows you to roll back to a previous state.
This is possible because different versions(or assemblies) of the same package have different paths on the system inside the /nix/store directory and are identified by the system by hash, so updating is just an operation to download new versions of packages, deploy them to a unique path and "switch" the system to them usage. No one forbids you to switch back at any time. Indirectly, this approach solves the DLL Hell problem, allows you to roll back applications to previous versions and, of course, install two versions of the same software next to each other.
NixOS is an incredibly interesting system, and I recommend that anyone who is not indifferent to Linux should definitely try it. And we move on, next in line is QubesOS and its virtual environments.
At different times, many attempts have been made to create a secure operating system based on application isolation and virtualization technologies. At one time, even Microsoft did this as part of the Syngularity project, but none of these attempts were successful. No matter how good the ideas embedded in the OS were, in almost 100% of cases they became a “victim of the second system” - it was not possible to drag users and developers to the new platform.
The QubesOS project, started by the well-known Polish security expert Joanna Rutkowska, compares favorably with them in that it offers to use existing developments to build a secure OS, without the need to break compatibility with applications, drivers and write millions of lines of code from scratch. QubesOS is just a Fedora-based Linux distribution, but unlike others, it is built from the ground up with the idea of hard isolation of applications and system components through virtualization.
The system is based on the Xen hypervisor, on top of which several virtual machines (domains) are launched, each of which is responsible for performing its own system function. In separate domains, the network stack (including a set of drivers), file systems and RAID drivers, as well as a graphics stack that includes an X server run here. Separate domains are also used to launch applications, but not one for each of them (otherwise the system would die from the rapid exhaustion of RAM), but divided into “interest groups”: entertainment, work, Internet banking, and so on.
The data transmission channel between domains is encrypted and has strict restrictions on the type of information transmitted and possible recipients. This means, for example, that if an attacker finds a hole in network stack Linux and can access the network domain, then it will actually be locked inside it, since all the network domain can do is process requests for network connections and transmission of data from authorized domains. This will not save you from sniffing and spoofing, but it will protect the data stored in the storage domain.
QubesOS uses KDE as its graphical environment, modified to hide the organization of the system from the user's eyes. Applications automatically run in different domains, and the environment uses color-coded window borders to indicate which domain an application is running in.
Currently, QubesOS developers are preparing to release the second release of the system (RC2 is already available), which will have a separate domain for Windows applications and a USB domain for safe work with USB devices.
ChromeOS is one of the most atypical, weird and controversial Linux distributions. For most people, it's just a browser running almost bare metal, but for someone familiar with Linux, it's a complete operating system that has many of the standard features of regular distributions, interspersed with Google's own tweaks.
By and large, ChromeOS is a heavily stripped-down Ubuntu, on top of which runs a graphical environment based on the achievements of the Chromium project. The same Ubuntu Upstart is responsible for booting the system, however, due to the need to launch a much smaller number of components, a cold start of ChromeOS is much faster (literally in a second). X.org is responsible for the graphics here, but it is used solely for the purpose of properly supporting equipment and input devices, the image itself almost always bypasses the X protocol directly to the video adapter (therefore, X will soon be replaced by Wayland or Mir).
From other components also used graphics library Clutter, PAM, D-Bus, NTP, syslog and cron. There are no package ideas in the system, and all OS updates occur during the OTA update “in one piece”. During the update, the system is never overwritten, but instead uses the second system partition, which becomes the first after reboot. Thus, ChromeOS can always be rolled back to a previous state, and the update itself cannot kill the system.
Due to the absence of many standard components of Linux distributions and the focus on running browser-only applications, ChromeOS is highly resistant to hacks. As with a desktop browser, each web application (read: tab) runs in its own sandbox, preventing the entire system from being compromised if an attacker finds a hole in the browser itself. System partition always mounted read-only. Chromebooks use the TPM (Trusted Platform Module) to verify system integrity.
In general, ChromeOS is not a full-fledged operating system, but rather a very non-standard Linux distribution, which cannot be said, for example, about Android or Firefox OS.
The Debian distribution has always had broad support for a wide variety of computer architectures. It is capable of running on ARM, MIPS, PowerPC, Sparc, and a variety of other officially and unofficially supported machines and processors. However, one of the most interesting ports of Debian has been done... to the FreeBSD kernel.
At its core, Debian GNU/kFreeBSD is the same distribution but modified to run on the FreeBSD kernel. There is the usual apt-get, a set of configurators, a System V-style initialization system, binary package repositories, KDE and GNOME, so the difference will be absolutely invisible to the end user. But the system administrator will find many interesting goodies for himself.
The main reason for the existence of this project is to be able to use FreeBSD technologies that are not available in the Linux kernel. These include native support for ZFS, a modular subsystem for working with data warehouses GEOM, a modular Netgraph network subsystem, and, of course, a reference implementation of the TCP / IP stack. All this is available in Debian GNU/kFreeBSD along with the usual Debian goodies.
The model for installing applications in separate directories first appeared in the GNU Stow installer.
Interestingly, in addition to Debian GNU/kFreeBSD, there is also a port to the Hurd microkernel, but its condition leaves much to be desired.
Version Chrome browser for Windows 8 is nothing but ChromeOS in miniature.
Many users have no doubts and download the most latest version. People think that in the updated version, the developers have eliminated all the bugs, added useful features, made the design more attractive, the interface is friendlier. But this is not always true. Only in 2016 they released several modifications and assemblies. Among them there are different systems: both good and bad. Therefore, you need to think about which Linux to choose. And only then, after evaluating all the pros and cons, install the distribution.
There is no universal system that will suit all users. Each person needs something different. The administrator cares about functionality, security and opportunities remote control. For beginners - friendly and simple interface. For a lover of innovation - interesting options that are not in previous versions.
In 2016, many distributions were released. Among them, you will definitely find the one that you need. But no rating will make a choice for you. It is better to independently evaluate the option you like.
There are a few general criteria that are important in any version of Linux:
When deciding which Linux distribution to choose, don't settle for the most common version. Review several options. What other people like may not suit you personally.
Run your favorite build on virtual machine or with LiveCD. No rating, review or opinion can replace personal experience. Linux is unpredictable in this regard. You will be able to understand if the program is right for you only after you work with it for a while.
A build that is constantly being improved. New versions are released frequently. Ubuntu is still popular in 2016. Although it was released 10 years ago.
The system is suitable for beginners who decide to "try" Linux. It's easy to install. It has a convenient and beautiful interface. There is nothing superfluous in it.
You can work with Ubuntu without even using a terminal. It is not like "classic" Linux - you have to work with command line. This is both a plus and a minus. You will easily get used to the new environment. But if you decide to install another build, you won't be able to use it without instructions.
New features are often added to Ubuntu. And with them - new bugs. They are removed as soon as they are discovered.
Intuitive graphical interface. There is a module that will speed up the adaptation if you switched to Mint from a Win system. They have a similar taskbar, desktop, navigation. You will quickly get used to the new “environment”. There are several working environments. Just choose the one you feel comfortable working with.
Mint is based on Ubuntu. The creators of Mint decided to remove all the disadvantages that are inherent in Linux. The peculiarity of the assembly is that it has built-in multimedia codecs. And the programs that are needed for full-fledged work on the computer are already included.
Well established Feedback. The creators of the modification are interested in the opinion of users, listen to it.
One of the oldest representatives of Linux. But it is popular in 2016 due to its stability and security. He has a huge development team. But new versions are rarely released.
Debian is installed on servers. It is suitable for remote administration. In him best systems package management.
Assembly is not suitable for beginners. She has more programs and settings that you need to understand. But installing the build is easy.
Here are the best Linux distributions 2016 designed for highly specialized tasks.
To decide which Linux to choose, you need to try a few builds you like. In reviews and tops, you can only look at the options. But if you know exactly what you need, install without hesitation.
Which Linux do you think is the best?