[ previous ] [ Contents ] [ 1 ] [ 2 ] [ 3 ] [ 4 ] [ 5 ] [ 6 ] [ 7 ] [ 8 ] [ 9 ] [ 10 ] [ 11 ] [ 12 ] [ 13 ] [ 14 ] [ 15 ] [ next ]
Installation instructions for the current release: see http://www.debian.org/releases/stable/installmanual
.
The Debian GNU/Linux reference covers many aspects of system administration through shell-command examples. Basic tutorials, tips, and other information are provided for many different topics ranging from system administration to programming.
Get it from the debian-reference
package, or at http://www.debian.org/doc/user-manuals#quick-reference
.
Policy manual documents the policy requirements for the distribution, i.e. the structure and contents of the Debian archive, several design issues of the operating system etc. It also includes the technical requirements that each package must satisfy to be included in the distribution, and documents the basic technical aspects of Debian binary and source packages.
Get it from the debian-policy
package, or at http://www.debian.org/doc/devel-manuals#policy
.
Documentation developed by the Debian Documentation Project. It is available
at http://www.debian.org/doc/
and
includes user guides, administration guides and security guides for the Debian
GNU/Linux operating system.
Documentation on installed Debian packages: Most packages have files that are unpacked into /usr/share/doc/PACKAGE.
Documentation on the Linux project: The Debian package doc-linux
installs all of the most recent versions of the HOWTOs and mini-HOWTOs from the
Linux Documentation Project
.
Unix-style `man' pages: Most commands have manual pages written in the style of the original Unix 'man' files. They are referenced by the section of the 'man' directory where they reside: e.g., foo(3) refers to a manual page which resides in /usr/share/man/man3/, and it can be called by executing the command: man 3 foo, or just man foo if section 3 is the first one containing a page on foo.
One can learn which directory of /usr/share/man/ contains a certain manual page by executing man -w foo.
New Debian users should note that the 'man' pages of many general system commands are not available until they install these packages:
man-db, which contains the man program itself, and other programs for manipulating the manual pages.
manpages, which contains the system manual pages. (see How does Debian support non-English languages?, Section 4.8).
GNU-style `info' pages: User documentation for many commands, particularly GNU tools, is available not in `man' pages, but in `info' files which can be read by the GNU tool info, by running M-x info within GNU Emacs, or with some other Info page viewer.
Its main advantage over the original `man' pages are that it is a hypertext system. It does not require the WWW, however; info can be run from a plain text console. It was designed by Richard Stallman and preceded the WWW.
Note that you may access a lot of documentation on your system by using a WWW browser, through `dwww', `dhelp' or `doccentral' commands, found in respective packages.
Yes. In fact, the main method of support Debian provides to our users is by the way of e-mail.
There are a lot of Debian-related mailing
lists
.
On a system with the doc-debian
package installed there is a
complete list of mailing lists in
/usr/share/doc/debian/mailing-lists.txt
.
Debian mailing lists are named following the pattern debian-list-subject. Examples are debian-announce, debian-user, debian-news. To subscribe to any list debian-list-subject, send mail to debian-list-subject-request@lists.debian.org with the word "subscribe" in the Subject: header. Be sure to remember to add -request to the e-mail address when using this method to subscribe or unsubscribe. Otherwise your e-mail will go to the list itself, which could be embarrassing or annoying, depending on your point of view.
If you have a forms-capable World Wide Web browser, you can subscribe to
mailing lists using the WWW form
. You
can also un-subscribe using a WWW form
.
The list manager's e-mail address is listmaster@lists.debian.org
,
in case you have any trouble.
The mailing lists are public forums. All e-mails sent to the lists are also
copied to the public archive, for anybody (even non-subscribers) to browse or
search. Please make sure you never send any confidential or unlicensed
material to the lists. This includes things like e-mail addresses. Of
particular note is the fact that spammers have been known to abuse e-mail
addresses posted to our mailing lists. See the Mailing
Lists Privacy policy
for more information.
Archives of the Debian mailing lists are available via WWW at http://lists.debian.org/
.
When using the Debian mailing lists, please follow these rules:
Do not send spam. See the Debian mailing list advertising
policy
.
Do not flame; it is not polite. The people developing Debian are all volunteers, donating their time, energy and money in an attempt to bring the Debian project together.
Do not use foul language; besides, some people receive the lists via packet radio, where swearing is illegal.
Make sure that you are using the proper list. Never post your (un)subscription requests to the mailing list itself[6]
See section How do I report a bug in Debian?, Section 11.5 for notes on reporting bugs.
Users can address questions to individual package maintainers using e-mail. To reach a maintainer of a package called xyz, send e-mail to xyz@packages.debian.org.
Users should post non-Debian-specific questions to one of the Linux USENET
groups, which are named comp.os.linux.* or linux.*. There are several lists of
Linux Usenet newsgroups and other related resources on the WWW, e.g. on the
Linux Online
and LinuxJournal
sites.
There is a variety of search engines that serve documentation related to Debian:
Google Groups
: a search
engine for newsgroups.
For example, to find out what experiences people have had with finding drivers for Promise controllers under Debian, try searching on the phrase Promise Linux driver. This will show you all the postings that contain these strings, i.e. those where people discussed these topics. If you add Debian to those search strings, you'll also get the postings specifically related to Debian.
Any of the common web spidering engines, such as AltaVista
or Google
, as long as you use the right
search terms.
For example, searching on the string "cgi-perl" gives a more detailed explanation of this package than the brief description field in its control file.
Reports on unsolved (and closed) issues are publicly available: Debian
promissed to do so by stating "We will not hide problems" in the
Debian Social
Contract
.
The Debian GNU/Linux distribution has a bug tracking system (BTS) which files details of bugs reported by users and developers. Each bug is given a number, and is kept on file until it is marked as having been dealt with.
Copies of this information are available at http://www.debian.org/Bugs/
.
A mail server provides access to the bug tracking system database via e-mail. In order to get the instructions, send an e-mail to request@bugs.debian.org with "help" in the body.
If you have found a bug in Debian, please read the instructions for reporting a bug in Debian. These instructions can be obtained in one of several ways:
By anonymous FTP. Debian mirror sites contain the instructions in the file doc/bug-reporting.txt.
From the WWW. A copy of the instructions is shown at http://www.debian.org/Bugs/Reporting
.
On any Debian system with the doc-debian
package installed. The
instructions are in the file
/usr/share/doc/debian/bug-reporting.txt
.
You can use the package reportbug
that will guide you through the
reporting process and mail the message to the proper address, with some extra
details about your system added automatically. It will also show you a list of
bugs already reported to the package you are reporting against in case your bug
has been reported previously, so that you can additional information to the
existing bug report.
If you want to mail the report with an e-mail program, send a message to
submit@bugs.debian.org
. The
message's first line must be similar to
Package: package-name
(replace package-name with the name of the package). The next line should relate the package version number in a similar way:
Version: version-number
The version number for any package installed on your system can be obtained using the command line
dpkg -s package-name
This section is referred to as the pseudo-header. The rest of the message should contain the description of the bug (please make it moderately detailed), the Debian release you are using, and versions of other relevant packages. The Debian release number will be displayed by the command
cat /etc/debian_version
Expect to get an automatic acknowledgement of your bug report. It will also be automatically given a bug tracking number, entered into the bug log and forwarded to the debian-bugs-dist mailing list.
[ 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