Previous Next Contents

5. Software available in the Debian system

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

Like most Linux distributions, Debian GNU/Linux provides:

Nearly 700 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 50 software suites are available as Debian packages, but are not formally part of Debian due to license restrictions.

5.2 Who wrote all that software?

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

A complete list is available from any of the Debian mirrors.

The file indices/Packages-Master-i386.gz provides a list, including short descriptions, of all packages that are available for computers with 80386 (or more advanced) chips. The file indices/Packages-Master-m68k.gz provides a similar list of packages that are available for computers with Motorola 68k0x0 CPUs.

The WWW interface to the Debian packages conveniently summarizes the packages in each of about twenty "sections" of the Debian archive, as well as the 10 most recently uploaded packages.

5.4 What is missing from Debian GNU/Linux?

A list of packages which are most urgently needed for Debian is maintained by Sven Rudolph. For more details, see the section on contributing to the Debian project.

5.5 (How) Does Debian support Java?

The Java Development Kit from Sun is currently available as a Debian package (jdk_VVV-RRR.deb). The JDK will allow you to run Java programs and applets, and write your own. If your kernel is properly configured (see below), the JDK will allow you to run Java programs just like other executables. The JDK package also includes a number of demo programs.

Debian's kernel is configured with Java support built in as a module (i.e., CONFIG_BINFMT_JAVA=m). Users who wish to build their own custom kernel can of course omit this if they choose. Once module support is available in the kernel, you need to make sure the module is loaded. You can do it at boot time by inserting the line binfmt_java in the file /etc/modules. Alternatively, you can install the module from the command line by executing the command insmod DIRNAME/binfmt_java.o where DIRNAME is the name of the directory where the modules that have been built for the version of the kernel now running are stored. On a system with the 2.0.0 version of the kernel, DIRNAME is likely to be /lib/modules/2.0.0/fs/. You can check that a module is loaded using the command lsmod.

Running a Java applet requires a browser with the capability to recognize and execute them. The Netscape browser that can be installed as a Debian package will run Java applets. (The Netscape source code is not publicly available. The Debian netscape package provides a wrapper which aids the installation and management of Netscape on a Debian system. This is actually a good example of the integration of commercial packages with the Debian system.)

A final note of mixed blessings: Sun's licensing policies on the JDK are becoming more restricted with time, so this package may not be available as part of Debian soon. It is possible that it may be available in the same way that Netscape is available for Debian Linux. Better news is that a number of programs are currently being developed with may provide attractive publicly-available alternatives.

5.6 What are all those directories (stable/development/non-free/contrib/project) at the Debian FTP archives?

The software that has been packaged for Debian GNU/Linux is available in one of several directory trees on each Debian mirror site.

Top-level Directories

The Major Package Trees:

Supplementary directories:

Of particular interest to developers:

Sub-directories

Within each of the major directory trees (stable/, non-free/, contrib/, and development/, but not project/experimental/), which is too small to subdivide), the binary packages reside in sub-directories whose names indicate the chip architecture for which they were compiled:

5.7 Is source code included with the system?

Source code is included for everything in the Debian system. Most of the license terms of programs in the system require that source code be distributed along with the programs, or that an offer to provide the source code accompany the programs.

Source code may or may not be available for packages in the "contrib" and "non-free" directories, which are not formally part of the Debian system.

5.8 How can I check that I am using a Debian system?

The existence of the program dpkg shows that you should be able to install Debian packages on your system.

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.

5.9 How can I tell what "version" of the Debian system I am using?

There is a file, /etc/debian_version, which contains a single one-line entry giving the version number of the release, as defined by the package base.

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. (With no arguments, this command prints out versions of all installed packages.) For a more verbose description, use dpkg --status foo.

5.10 How does Debian support non-English languages?

5.11 What about the US export regulation limitations?

US laws place restrictions on the export of defense articles, which includes some types of cryptographic software. PGP and ssh fall into this category.

To prevent anyone from taking unnecessary legal risks, certain Debian GNU/Linux packages are only available from a non-US site ftp://os.inf.tu-dresden.de:/pub/debian-non-US/, there is a list of mirror sites ftp://os.inf.tu-dresden.de/pub/debian-non-US/README.mirrors


Previous Next Contents