[ previous ] [ Contents ] [ 1 ] [ 2 ] [ 3 ] [ 4 ] [ 5 ] [ 6 ] [ 7 ] [ 8 ] [ 9 ] [ 10 ] [ 11 ] [ 12 ] [ 13 ] [ 14 ] [ 15 ] [ next ]


The Debian GNU/Linux FAQ
Chapter 4 - Software available in the Debian system


4.1 What types of applications and development software are available for Debian GNU/Linux?

Like most Linux distributions, Debian GNU/Linux provides:

More than 15180 packages, ranging from news servers and readers to sound support, FAX programs, database and spreadsheet programs, image processing programs, communications, net, and mail utilities, Web servers, and even ham-radio programs are included in the distribution. Another 450 software suites are available as Debian packages, but are not formally part of Debian due to license restrictions.


4.2 Who wrote all that software?

For each package the authors of the program(s) are credited in the file /usr/share/doc/PACKAGE/copyright, where PACKAGE is to be substituted with the package's name.

Maintainers who package this software for the Debian GNU/Linux system are listed in the Debian control file (see What is a Debian control file?, Section 6.4) that comes with each package. The Debian changelog, in /usr/share/doc/PACKAGE/changelog.Debian.gz, mentions the people who've worked on the Debian packaging too.


4.3 How can I get a current list of programs that have been packaged for Debian?

A complete list is available from any of the Debian mirrors, in the file indices/Maintainers. That file includes the package names and the names and e-mails of their respective maintainers.

The WWW interface to the Debian packages conveniently summarizes the packages in each of about twenty "sections" of the Debian archive.


4.4 What is missing from Debian GNU/Linux?

A list of packages which are still needed to be packaged for Debian exists, the Work-Needing and Prospective Packages list.

For more details about adding the missing things, see How can I become a Debian software developer?, Section 12.1.


4.5 Why do I get "ld: cannot find -lfoo" messages when compiling programs? Why aren't there any libfoo.so files in Debian library packages?

Debian Policy requires that such symbolic links (to libfoo.so.x.y.z or similar) are placed in separate, development packages. Those packages are usually named libfoo-dev or libfooX-dev (presuming the library package is named libfooX, and X is a whole number).


4.6 (How) Does Debian support Java?

Since the official Java Development kit and Runtime Environment from Sun Microsystems is non-free software, even undistributeable by Debian, it cannot properly be included in Debian. If you want those installed anyway, please refer to the java-package package in contrib.

However, both the JDK and several free implementations of Java technology are available as Debian packages. You can write, debug and run Java programs using Debian.

Running a Java applet requires a web browser with the capability to recognize and execute them. Several web browsers available in Debian, such as Mozilla or Konqueror, support Java plug-ins that enable running Java applets within them. Netscape Navigator, while non-free, is also available as a Debian package and it can run Java applets.

Please refer to the Debian Java FAQ for more information.


4.7 How can I check that I am using a Debian system, and what version is it?

In order to make sure that your system has been installed from the real Debian base disks check for the existence of /etc/debian_version file, which contains a single one-line entry giving the version number of the release, as defined by the package base-files.

The existence of the program dpkg shows that you should be able to install Debian packages on your system, but as the program has been ported to many other operating systems and architectures, this is no longer a reliable method of determining is a system Debian GNU/Linux.

Users should be aware, however, that the Debian system consists of many parts, each of which can be updated (almost) independently. Each Debian "release" contains well defined and unchanging contents. Updates are separately available. For a one-line description of the installation status of package foo, use the command dpkg --list foo. To view versions of all installed packages, run:

     dpkg -l

For a more verbose description, use:

     dpkg --status foo

4.8 How does Debian support non-English languages?


4.9 What about the US export regulation limitations?

US laws placed restrictions on the export of defense articles, which includes some types of cryptographic software. PGP and ssh, among others, fall into this category. For the sarge release packages in this archive were moved to the main archive (or to non-free, if applicable) due to the US relaxing its regulations on the export of cryptography.

To prevent anyone from taking unnecessary legal risks, certain Debian GNU/Linux packages were only available from a non-US site ftp://non-US.debian.org/debian-non-US/, with numerous mirror sites all of which are also outside of the US, see ftp://non-US.debian.org/debian-non-US/README.non-US for a full list. These sites still exist (for the benefit of users of woody) but its contents are no longer supported and are considered obsolete. Please remove any mentions to non-US from your sources in your /etc/apt/sources.list configuration file.


4.10 Where is pine?

Due to its restrictive license, it's in the non-free area. Moreover, since license does not even allow modified binaries to be distributed, you have to compile it yourself from the source and the Debian patches.

The source package name is pine. You can use the pine-tracker package to be notified about when you need to upgrade.

Note that there are many replacements for both pine and pico, such as mutt and nano, that are located in the main section.


4.11 Where is qmail/ezmlm/djbdns?

Dan J. Bernstein distributes all software he has written with a restrictive license, consequently, it's in the non-free area. Since the license he uses does not allow modified binaries to be distributed, you have to compile it yourself from the source and the Debian patches to obtain a binary package you can install in your Debian GNU/Linux system.

The source package names are qmail-src, ezmlm-src and djbdns-installer, respectively.

For qmail you need to install qmail-src first and then run build-qmail to build the Debian package. You also need to do install the ucspi-tcp-src package to get ucspi-tcp, which qmail depends on.

Dan J. Bernstein maintains a FAQ from distributors page if you are interested in reading his reasons (one of which is Cross-platform compatibility)


[ previous ] [ Contents ] [ 1 ] [ 2 ] [ 3 ] [ 4 ] [ 5 ] [ 6 ] [ 7 ] [ 8 ] [ 9 ] [ 10 ] [ 11 ] [ 12 ] [ 13 ] [ 14 ] [ 15 ] [ next ]


The Debian GNU/Linux FAQ

version 3.1.3, 25 April 2006

Authors are listed at Debian FAQ Authors