Learn what "begging the question" is and why you shouldn't refer to it when you've just thought of something to ask.

Packages generally contain all of the files necessary to implement a set of related commands or features. There are two types of Debian packages: Binary packages, which contain executables, configuration files, man/info pages, copyright information, and other documentation. These packages are distributed in a Debian-specific archive format; they are usually distinguished by having a '.deb' file extension.

A Debian "package", or a Debian archive file, contains the executable files, libraries, and documentation associated with a particular suite of program or set of related programs. Normally, a Debian archive file has a filename that ends in .deb. The internals of this Debian binary packages format are described in the deb(5) manual page. This internal format is subject to change, therefore always use dpkg-deb(8) for manipulating .deb files.

The Debian package names conform to the following convention: <foo>_<VersionNumber>-<DebianRevisionNumber>_<Arch>.deb Note that foo is supposed to be the package name. This naming convention is rather new, and some packages have slightly different name formats. As a check, one can learn the package name associated with a particular Debian archive file (.

Unfortunately, I am not a Debian user so I cannot personally provide a package for Debian use. However, Roberto Sanchez has provided a Debian package for ReleaseForge.

The Debian binary package file names conform to the following convention: <foo>_<VersionNumber>-<DebianRevisionNumber>.deb Note that foo is supposed to be the package name. As a check, one can learn the package name associated with a particular Debian archive file (.deb file) in one of these ways: inspect the "Packages" file in the directory where it was stored in a Debian FTP archive site.

Debian created by the Debian project, is a widely used distribution of free software developed through the collaboration of volounteers from around the world.

Daniel Gubser creates Debian packages, and versions of psad later than 1.2.2 are available in RPM form.

The version for a non-native Debian package looks like UpstreamVersion-DebianVersion for example: 2.8-1. In the diff.gz: These are the modifications you made to the package. It contains the debian directory and the modifications you made to the source tree, if any. In the orig.tar.gz: This is the upstream tarball. You should very rarely make changes to this file, and you should never ever make changes unless you explicitly understand why you are making them.

Debian GNU/Linux is a particular distribution of the Linux operating system, and numerous packages that run on it. In principle, users could obtain the Linux kernel via the Internet or from elsewhere, and compile it themselves. They could then obtain source code for many applications in the same way, compile the programs, then install them into their systems. For complicated programs, this process can be not only time-consuming but error-prone.

This is stable and well tested software, it changes if major security or usability fixes are incorporated. This is where packages that will be released as the next 'stable' are placed; they've had some testing in unstable but they may not be completely fit for release yet. This distribution is updated more often than 'stable', but not more often than 'unstable'. This is the version currently under development; it is updated continuously.

You can get the installation disks by downloading the appropriate files from one of the Debian mirrors. The installation system files are separated in subdirectories of dists/stable/main directory, and the names of these subdirectories correspond to your architecture like this: disks-arch (arch is "i386", "sparc", etc, check the site for an exact list).

Linux supports the ISO 9660 (CD-ROM) file system with Rock Ridge extensions (formerly known as "High Sierra". Several vendors provide Debian GNU/Linux in this format. Warning: When installing from CD-ROM, it is usually not a good idea to choose dselect's cdrom access method. This method is usually very slow.

Debian developers communicate with other Linux distribution creators in an effort to maintain binary compatibility across Linux distributions. 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.

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/.

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. 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).

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 software that has been packaged for Debian GNU/Linux is available in one of several directory trees on each Debian mirror site. The dists directory is short for "distributions", and it is the canonical way to access the currently available Debian releases (and pre-releases). DOS utilities for creating boot disks, partitioning your disk drive, compressing/decompressing files, and booting Linux.

There are three distributions, the "stable" distribution, the "testing" distribution, and the "unstable" distribution. The "testing" distribution is sometimes 'frozen' (see What about "testing"? How is it 'frozen'?, Section 5.6.1).

No, you do not need to have Crystal Reports the use any of the Report Writers that we offer. There are example report templates on the distribution for A44-B32 (GammaVision Report Writer), A46-B32 (ScintiVision Report Writer), and A47-B32 (AlphaVision Report Writer). These templates are fully functional and may be used.

Make sure you do all steps as root. Download and install Tomcat x@y:/$ cd /usr/local x@y:/usr/local/$ wget http://www.apache.org/dist/tomcat/tomcat-5/v5.0.28/bin/jakarta-tomcat-5.0.28.tar.gz x@y:/usr/local/$ tar -zxf jakarta-tomcat-5.0.28.tar.gz x@y:/usr/local/$ mv jakarta-tomcat-5.0.28 tomcat Make script so you can start-stop-restart Tomcat (make sure that java path is correct!). x@y:/$ cd /etc/init.d x@y:/etc/init.

The project name is pronounced Deb'-ee-en, with a short e in Deb, and emphasis on the first syllable. This word is a contraction of the names of Debra and Ian Murdock, who founded the project. (Dictionaries seem to offer some ambiguity in the pronunciation of Ian (!), but Ian prefers ee'-en.)

Yes. You can boot the Debian installation system from a set of files you can download from our FTP site and its mirrors. You can download a small CD image file, create a bootable CD from it, install the basic system from it and the rest over the network. For more information please see http://www.debian.org/CD/netinst/. You can also download even smaller floppy disk image files, create bootable diskettes from them, start the installation procedure and get the rest of Debian over the network.