Shulou(Shulou.com)06/01 Report--

1.2 the relationship between Kali and Debian

The Kali Linux distribution is based on the Debian beta. As a result, most of the packages in Kali Linux come directly from Debian's software repository.

Although Kali Linux is largely dependent on Debian, in a sense, we are also completely independent, we have our own infrastructure, we have our own freedom, and we can make any changes we want.

1.2.1 package flow

In the case of Debian, the contribution updates the package every day and uploads it to the unstable distribution of Debian. From here, once most of the annoying BUG is solved, these packages are migrated to the Debian test distribution. This migration process also ensures that the dependencies between packages are normal in the Debian beta.

The purpose of the Debian beta is to make Kali Linux quite consistent with it, so that we can build on the Debian beta. To add Kali proprietary packages to the distribution, we follow two steps:

First, we took the Debian beta and forcibly incorporated the Kali package (which is only located in the kali-dev-only software repository) into it, building the kali-dev software repository. This software repository will not be interrupted for a while: for example, our Kali proprietary packages may not be installed until they are recompiled based on updated libraries. In other cases, we may also update existing branches, whether to become installable again, or to fix the installability of packages that depend on the updated version of the branch software. In any case, kali-dev is not targeted at the end user.

Kali-rolling is a distribution that requires Kali Linux users to track. It is based on the kali-dev version, and the kali-dev version is built in the same way from the Debian beta built from the unstable version of Debian. The package is migrated only if all the dependencies of the package are complete in the target distribution.

1.2.2 differences between Management and Debian

As a design decision, we try to reduce the number of packages distributed as much as possible. However, in order to implement some of the unique features of Kali, some changes must be made. In order to limit the impact of these changes, we strive to send these changes upstream, either through direct integration or by adding the required requirements, in short, without having to modify the upstream package again. Directly enable the desired features.

The Kali package tracker can help us keep track of differences between Kali and Debian. At any time, we can find out which package has been branched, whether it is synchronized with Debian, or whether an update is required, and so on. All packages are maintained in the Git software repository based on the Debian branch, as well as a Kali branch. Thanks to this, updating a forked package requires only two simple steps: update the Debian branch, and then merge it into the Kali branch.

Although there are relatively few forked packages in Kali, many packages have been added: almost 400 as of April 2017. Most of these packages are free software and comply with Debian free software guidelines. Our ultimate goal is to make these packages as effective as Debian at all times. That's why we need to follow the Debian strategy and make these good packages available in Debian. Unfortunately, however, there are exceptions: some packages are almost impossible to create. Due to the lack of time, some software packages have been pushed into Debian.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.