[ previous ] [ Contents ] [ 1 ] [ 2 ] [ 3 ] [ 4 ] [ 5 ] [ 6 ] [ 7 ] [ 8 ] [ 9 ] [ 10 ] [ 11 ] [ 12 ] [ 13 ] [ 14 ] [ 15 ] [ 16 ] [ next ]
Debian GNU/Linux includes complete source-code for all of the included
programs, so it should work on all systems which are supported by the Linux
kernel; see the Linux
FAQ for details.
The current Debian GNU/Linux release, 9, contains a complete, binary distribution for the following architectures:
amd64: this covers systems based on AMD 64bit CPUs with AMD64 extension and all Intel CPUs with EM64T extension, and a common 64bit userspace.
arm64: supports the latest 64-bit ARM-powered devices.
armel: little-endian ARM machines.
armhf: an alternative to armel for ARMv7 machines with hard-float.
i386: this covers systems based on Intel and compatible processors, including Intel's 386, 486, Pentium, Pentium Pro, Pentium II (both Klamath and Celeron), and Pentium III, and most compatible processors by AMD, Cyrix and others.
ia64: Intel IA-64 ("Itanium") computers.
mips: SGI's big-endian MIPS systems, Indy and Indigo2; mipsel: little-endian MIPS machines, Digital DECstations.
powerpc: this covers some IBM/Motorola PowerPC machines, including the Apple Macintosh PowerMac models, and the CHRP and PReP open architecture machines.
ppc64el: 64-bit little-endian PowerPC port, supports several recent PowerPC/POWER processors.
s390x: 64-bit port for IBM System z machines, replaced s390.
The development of binary distributions of Debian for hurd-i386 (for GNU Hurd kernel on i386 32-bit PCs), mipsel64 (for 64 bit MIPS in little-endian mode), powerpcspe (port for the "Signal Processing Engine" hardware), sparc64 (for 64 bit SPARC processors), sh (for Hitachi SuperH processors), and x32 (for amd64/x86_64 CPUs using 32-bit pointers) is currently underway.
Support for the m68k architecture was dropped in the Etch (Debian 4.0) release, because it did not meet the criteria set by the Debian Release Managers. This architecture covers Amigas and ATARIs having a Motorola 680x0 processor for x>=2; with MMU. However, the port is still active and available for installation even if not a part of this official stable release and might be reactivated for future releases.
Support for the hppa (Hewlett-Packard's PA-RISC machines) and alpha (Compaq/Digital's Alpha systems) were dropped in the Squeeze (Debian 6.0) release for similar reasons. The arm was dropped too in this release, as it was superseded by the armel architecture.
Support for the 32-bit s390 port (s390) was discontinued and replaced with s390x in Jessie (Debian 8). In addition, the ports to IA-64 and Sparc had to be removed from this release due to insufficient developer support.
For more information on the available ports see the ports pages at the website.
For further information on booting, partitioning your drive, enabling PCMCIA
(PC Card) devices and similar issues please follow the instructions given in
the Installation Manual, which is available from our WWW site at http://www.debian.org/releases/stable/installmanual.
Beside Linux, Debian provides a complete, binary distribution for the following operating system kernels:
FreeBSD: provided through the kfreebsd-amd64 and kfreebsd-i386 ports, for 64-bit PCs and 32-bit PCs respectively. These ports were first released in Debian 6.0 Squeeze as a technology preview. However they were not part of the Debian 8 Jessie release.
In addition to these, work is in progress on the following adaptations:
avr32, port to Atmel's 32-bit RISC architecture,
hurd-i386, a port for 32-bit PC. This port will use GNU Hurd, the new operating system being put together by the GNU group,
sh, port to Hitachi SuperH processors.
There were attempts to port the distribution to the NetBSD kernel, providing netbsd-i386 (for 32-bit PCs) and netbsd-alpha (for Alpha machines) but these ports were never released and are currently abandoned.
For more information on the available ports see the ports pages at the website.
Debian developers communicate with other Linux distribution creators in an effort to maintain binary compatibility across Linux distributions. [1] Most commercial Linux products run as well under Debian as they do on the system upon which they were built.
Debian GNU/Linux adheres to the Linux Filesystem Hierarchy
Standard. However, there is room for interpretation in some of the
rules within this standard, so there may be slight differences between a Debian
system and other Linux systems.
For most applications Linux source code is compatible with other Unix systems. It supports almost everything that is available in System V Unix systems and the free and commercial BSD-derived systems. However in the Unix business such claim has nearly no value because there is no way to prove it. In the software development area complete compatibility is required instead of compatibility in "about most" cases. So years ago the need for standards arose, and nowadays POSIX.1 (IEEE Standard 1003.1-1990) is one of the major standards for source code compatibility in Unix-like operating systems.
Linux is intended to adhere to POSIX.1, but the POSIX standards cost real money and the POSIX.1 (and FIPS 151-2) certification is quite expensive; this made it more difficult for the Linux developers to work on complete POSIX conformance. The certification costs make it unlikely that Debian will get an official conformance certification even if it completely passed the validation suite. (The validation suite is now freely available, so it is expected that more people will work on POSIX.1 issues.)
Unifix GmbH (Braunschweig, Germany) developed a Linux system that has been certified to conform to FIPS 151-2 (a superset of POSIX.1). This technology was available in Unifix' own distribution called Unifix Linux 2.0 and in Lasermoon's Linux-FT.
Different Linux distributions use different package formats and different package management programs.
A program to unpack a Debian package onto a Linux host that is been built from
a `foreign' distribution is available, and will generally work, in the sense
that files will be unpacked. The converse is probably also true, that is, a
program to unpack a Red Hat or Slackware package on a host that is based on
Debian GNU/Linux will probably succeed in unpacking the package and placing
most files in their intended directories. This is largely a consequence of the
existence (and broad adherence to) the Linux Filesystem Hierarchy Standard.
The Alien package
is used to convert between different package formats.
Most package managers write administrative files when they are used to unpack an archive. These administrative files are generally not standardized. Therefore, the effect of unpacking a Debian package on a `foreign' host will have unpredictable (certainly not useful) effects on the package manager on that system. Likewise, utilities from other distributions might succeed in unpacking their archives on Debian systems, but will probably cause the Debian package management system to fail when the time comes to upgrade or remove some packages, or even simply to report exactly what packages are present on a system.
The Linux File System Standard (and therefore Debian GNU/Linux) requires that subdirectories under /usr/local/ be entirely under the user's discretion. Therefore, users can unpack `foreign' packages into this directory, and then manage their configuration, upgrade and removal individually.
Files under the directory /usr/local/ are not under the control of the Debian package management system. Therefore, it is good practice to place the source code for your program in /usr/local/src/. For example, you might extract the files for a package named "foo.tar" into the directory /usr/local/src/foo. After you compile them, place the binaries in /usr/local/bin/, the libraries in /usr/local/lib/, and the configuration files in /usr/local/etc/.
If your programs and/or files really must be placed in some other directory, you could still store them in /usr/local/, and build the appropriate symbolic links from the required location to its location in /usr/local/, e.g., you could make the link
ln -s /usr/local/bin/foo /usr/bin/foo
In any case, if you obtain a package whose copyright allows redistribution, you should consider making a Debian package of it, and uploading it for the Debian system. Guidelines for becoming a package developer are included in the Debian Policy manual (see What other documentation exists on and for a Debian system?, Section 12.1).
[ previous ] [ Contents ] [ 1 ] [ 2 ] [ 3 ] [ 4 ] [ 5 ] [ 6 ] [ 7 ] [ 8 ] [ 9 ] [ 10 ] [ 11 ] [ 12 ] [ 13 ] [ 14 ] [ 15 ] [ 16 ] [ next ]
The Debian GNU/Linux FAQ
version 9.0, 17 November 2018