Gecko [ ifk.uw.edu.pl ]

Name	Size	Permission
ch-basic_defs.en.html	34.93 KB	-rw-r--r--
ch-basic_defs.html	34.93 KB	-rw-r--r--
ch-choosing.en.html	44.66 KB	-rw-r--r--
ch-choosing.html	44.66 KB	-rw-r--r--
ch-compat.en.html	33.45 KB	-rw-r--r--
ch-compat.html	33.45 KB	-rw-r--r--
ch-contributing.en.html	27.15 KB	-rw-r--r--
ch-contributing.html	27.15 KB	-rw-r--r--
ch-customizing.en.html	37.07 KB	-rw-r--r--
ch-customizing.html	37.07 KB	-rw-r--r--
ch-faqinfo.en.html	26.29 KB	-rw-r--r--
ch-faqinfo.html	26.29 KB	-rw-r--r--
ch-ftparchives.en.html	39.02 KB	-rw-r--r--
ch-ftparchives.html	39.02 KB	-rw-r--r--
ch-getting.en.html	28.45 KB	-rw-r--r--
ch-getting.html	28.45 KB	-rw-r--r--
ch-kernel.en.html	25.53 KB	-rw-r--r--
ch-kernel.html	25.53 KB	-rw-r--r--
ch-nexttime.en.html	27.64 KB	-rw-r--r--
ch-nexttime.html	27.64 KB	-rw-r--r--
ch-pkg_basics.en.html	48.23 KB	-rw-r--r--
ch-pkg_basics.html	48.23 KB	-rw-r--r--
ch-pkgtools.en.html	41.75 KB	-rw-r--r--
ch-pkgtools.html	41.75 KB	-rw-r--r--
ch-redistrib.en.html	25.88 KB	-rw-r--r--
ch-redistrib.html	25.88 KB	-rw-r--r--
ch-software.en.html	34.18 KB	-rw-r--r--
ch-software.html	34.18 KB	-rw-r--r--
ch-support.en.html	34.63 KB	-rw-r--r--
ch-support.html	34.63 KB	-rw-r--r--
ch-uptodate.en.html	32.38 KB	-rw-r--r--
ch-uptodate.html	32.38 KB	-rw-r--r--
debian-faq.en.pdf.gz	300.34 KB	-rw-r--r--
debian-faq.en.ps.gz	245.87 KB	-rw-r--r--
debian-faq.en.txt.gz	58.04 KB	-rw-r--r--
debian-faq.pdf.gz	300.34 KB	-rw-r--r--
debian-faq.ps.gz	245.87 KB	-rw-r--r--
debian-faq.txt.gz	58.04 KB	-rw-r--r--
footnotes.en.html	25.56 KB	-rw-r--r--
footnotes.html	25.56 KB	-rw-r--r--
index.en.html	42.78 KB	-rw-r--r--
index.html	42.78 KB	-rw-r--r--

Code Editor : footnotes.en.html

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">

<html>

<head>

<title>The Debian GNU/Linux FAQ - Footnotes</title>

</head>

<body>

<hr>

<h1>
The Debian GNU/Linux FAQ
<br>Footnotes</h1>

<p>
The <code><a href="http://www.linuxbase.org/">Linux Standard Base</a></code> is
a specification for allowing the same binary package to be used on multiple
distributions.  After Jessie (Debian 8) was released, Debian <code><a
href="https://sources.debian.org/src/lsb/9.20170808/debian/README.Debian/">abandoned</a></code>
the pursuit of LSB compatibility.  See this <code><a
href="https://lists.debian.org/4526217.myWFlvm1rM@gyllingar">July 3, 2015
message from Didier Raboud</a></code> and the following discussion for
background information.
</p>

<p>
When the present-day sid did not exist, the FTP site organization had one major
flaw: there was an assumption that when an architecture is created in the
current unstable, it will be released when that distribution becomes the new
stable.  For many architectures that isn't the case, with the result that those
directories had to be moved at release time.  This was impractical because the
move would chew up lots of bandwidth.
</p>

<p>
The archive administrators worked around this problem for several years by
placing binaries for unreleased architectures in a special directory called
&quot;sid&quot;.  For those architectures not yet released, the first time they
were released there was a link from the current stable to sid, and from then on
they were created inside the unstable tree as normal.  This layout was somewhat
confusing to users.
</p>

<p>
With the advent of package pools (see <a href="#s-pools">What's in the
<samp>pool</samp> directory?, Section 6.10</a>), binary packages began to be
stored in a canonical location in the pool, regardless of the distribution, so
releasing a distribution no longer causes large bandwidth consumption on the
mirrors (there is, however, a lot of gradual bandwidth consumption throughout
the development process).
</p>

<p>
<samp>dists/stable/main</samp>, <samp>dists/stable/contrib</samp>,
<samp>dists/stable/non-free</samp>, and <samp>dists/unstable/main/</samp>, etc.
</p>

<p>
Historically, packages were kept in the subdirectory of <samp>dists</samp>
corresponding to which distribution contained them.  This turned out to cause
various problems, such as large bandwidth consumption on mirrors when major
changes were made.  This was fixed with the introduction of the package pool.
</p>

<p>
The <samp>dists</samp> directories are still used for the index files used by
programs like <samp>apt</samp>.
</p>

<p>
Notice that there are ports that make this tool available with other package
management systems, like Red Hat package manager, also known as
<code>rpm</code>
</p>

<p>
In 2014, Debian changed its default init system from System V init to systemd.
Debian 8 &quot;jessie&quot; in April 2015 was the first release to ship with
systemd as default init.  Four <code><a
href="https://www.debian.org/devel/tech-ctte#status">decisions</a></code> of
the Debian Technical Committee were involved: <code><a
href="https://lists.debian.org/20140211193904.GX24404@rzlab.ucr.edu">Bug
#727708</a></code> 2014-02-11: &quot;The committee decided that the default
init system for Linux architectures in jessie should be systemd.&quot; <code><a
href="https://lists.debian.org/20140801023630.GF12356@teltox.donarmstrong.com">Bug
#746715</a></code> 2014-08-01: &quot;The technical committee expects
maintainers to continue to support the multiple available init systems&quot;,
and merge reasonable contributions.  <code><a
href="https://lists.debian.org/20141116001628.GO32192@teltox.donarmstrong.com">Bug
#746578</a></code> 2014-11-15: &quot;The committee decided that systemd-shim
should be the first listed alternative dependency of libpam-systemd instead of
systemd-sysv.&quot; This decision made it easier to keep running a non-systemd
Debian system.  <code><a
href="https://lists.debian.org/21592.61064.527547.410074@chiark.greenend.org.uk">Bug
#762194</a></code>2017-11-04: &quot;On automatic init system switching on
upgrade&quot;
</p>

<p>
Use the debian-<var>list-subject</var>-REQUEST@lists.debian.org address for
that.
</p>

<hr>

<p>
The Debian GNU/Linux FAQ
</p>

<address>
version 9.0, 17 November 2018<br>
<br>
Authors are listed at <a href="ch-faqinfo.en.html#s-authors">Debian FAQ Authors</a><br>
<br>
</address>
<hr>

</body>

</html>

${this.title}

Code Editor : footnotes.en.html