remove old CategoryIntroduction
converted to 1.6 markup
|Deletions are marked like this.||Additions are marked like this.|
|Line 2:||Line 2:|
|["DebianPackage"] > debconf||[[DebianPackage]] > debconf|
|Line 4:||Line 4:|
|||<tablestyle="width:65%;margin-left:35%;padding-left:30pt" style="border:1pt solid #b48;border-left:5pt solid #d4a">'''disambiguation :''' This page is about ''Debian configuration management system''.[[BR]] For ''Debian Conferences'', see ["DebConf"].||||||<tablestyle="width:65%;margin-left:35%;padding-left:30pt" style="border:1pt solid #b48;border-left:5pt solid #d4a">'''disambiguation :''' This page is about ''Debian configuration management system''.<<BR>> For ''Debian Conferences'', see [[DebConf]].|||
|Line 10:||Line 10:|
|To run it, type in a ["Console"]:||To run it, type in a [[Console]]:|
|Line 16:||Line 16:|
|The User/Administrator (["root"]) can configure the following aspects of debconf behavior :||The User/Administrator ([[root]]) can configure the following aspects of debconf behavior :|
DebianPackage > debconf
disambiguation : This page is about Debian configuration management system.
debconf is, to put it simply, "Install Shield Wizards Done Right," and is one of the main advantages of DebianAndOtherDistros. There is no debconf executable program. The name 'debconf' simply refers to the package configuration system as a whole.
More specifically, when installing (or upgrading) any single package or a group of packages, debconf asks the packages' configuration questions all at once, and stores the user/admin preferences in a database. Later as the packages are installing, their scripts use the configuration preferences in the database to generate configuration files and otherwise do adimnistrative tasks (e.g. set up servers to start or not start, install other software such as libdvdcss, etc.). This saves the hassle of editing configuration files by hand, and also of waiting for each individual package to install before responding to certain configuration questions.
To run it, type in a Console:
The User/Administrator (root) can configure the following aspects of debconf behavior :
- Ask again: debconf by default does not re-ask old configuration questions during upgrade of a package, instead it uses old answers to generate new versions of configuration files, providing seamless upgrade capability. But this behavior can be changed so such questions are always asked (with old answers provided as defaults).
Frontend: debconf can ask its questions using interfaces from plain text to Dialog (default) to GNOME control applet.
- Priority: all questions are assigned priority levels, either low, medium, high or critical, and the user/admin can decide below what priority level (s)he would like debconf to use the default configuration answer without asking (default medium).
In the same way, you can configure debconf-enabled packages by typing dpkg-reconfigure packagename and answering configuration questions.