|
|
1.
|
|
|
Using the Debian Installer
|
|
|
Tag: title
|
|
|
|
|
Using the Debian Installer
|
|
Translated and reviewed by
Glenn J. Mason
|
|
|
|
Located in
using-d-i.xml:5
|
|
|
2.
|
|
|
How the Installer Works
|
|
|
Tag: title
|
|
|
|
|
How The Installer Works
|
|
Translated and reviewed by
Glenn J. Mason
|
|
|
|
Located in
using-d-i.xml:7
|
|
|
3.
|
|
|
The Debian Installer consists of a number of special-purpose components to perform each installation task. Each component performs its task, asking the user questions as necessary to do its job. The questions themselves are given priorities, and the priority of questions to be asked is set when the installer is started.
|
|
|
Tag: para
|
|
|
|
|
The Debian Installer consists of a number of special-purpose components to perform each installation task. Each component performs its installation task and asks any necessary questions. Each question is given a priority, and the priority of questions to be asked is set when the installer is started.
|
|
Translated and reviewed by
Glenn J. Mason
|
|
|
|
Located in
using-d-i.xml:8
|
|
|
4.
|
|
|
When a default installation is performed, only essential (high priority) questions will be asked. This results in a highly automated installation process with little user interaction. Components are automatically run in sequence; which components are run depends mainly on the installation method you use and on your hardware. The installer will use default values for questions that are not asked.
|
|
|
Tag: para
|
|
|
|
|
When a default installation is performed, only essential, high priority questions will be asked. This results is a highly automated installation process, with little user interaction. The components run each installation task in sequence, and which components are run depends on the installation method chosen and the hardware you are installing onto. The installer uses default values for any questions that aren't asked.
|
|
Translated and reviewed by
Glenn J. Mason
|
|
|
|
Located in
using-d-i.xml:16
|
|
|
5.
|
|
|
If there is a problem, the user will see an error screen, and the installer menu may be shown in order to select some alternative action. If there are no problems, the user will never see the installer menu, but will simply answer questions for each component in turn. Serious error notifications are set to priority <quote>critical</quote> so the user will always be notified.
|
|
|
Tag: para
|
|
|
|
|
If there is a problem, an error screen is shown and the installer menu may display some alternative actions to choose from. If there aren't any problems, the installer menu isn't shown, and the user will simply answer any necessary questions for each component in turn. Serious error notifications are set to priority <quote>critical</quote>, so the user will always be notified.
|
|
Translated and reviewed by
Glenn J. Mason
|
|
|
|
Located in
using-d-i.xml:25
|
|
|
6.
|
|
|
Some of the defaults that the installer uses can be influenced by passing boot arguments when &d-i; is started. If, for example, you wish to force static network configuration (DHCP is used by default if available), you could add the boot parameter <userinput>netcfg/disable_dhcp=true</userinput>. See <xref linkend="installer-args"/> for available options.
|
|
|
Tag: para
|
|
|
|
|
Some of the defaults that the installer uses can be influenced by passnig boot arguments when &d-i; is started. For example, you can force a static network configuration, rather than the default of DHCP, by adding the boot argument <userinput>netcfg/disable_dhcp=true</userinput>. See <xref linkend="installer-args"/> for other available options.
|
|
Translated and reviewed by
Glenn J. Mason
|
|
|
|
Located in
using-d-i.xml:34
|
|
|
7.
|
|
|
Power users may be more comfortable with a menu-driven interface, where each step is controlled by the user rather than the installer performing each step automatically in sequence. To use the installer in a manual, menu-driven way, add the boot argument <userinput>priority=medium</userinput>.
|
|
|
Tag: para
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
using-d-i.xml:42
|
|
|
8.
|
|
|
If your hardware requires you to pass options to kernel modules as they are installed, you will need to start the installer in <quote>expert</quote> mode. This can be done by either using the <command>expert</command> command to start the installer or by adding the boot argument <userinput>priority=low</userinput>. Expert mode gives you full control over &d-i;.
|
|
|
Tag: para
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
using-d-i.xml:50
|
|
|
9.
|
|
|
For this architecture the &d-i; supports two different user interfaces: a character-based one and a graphical one. The character-based interface is used by default unless you selected the <quote>Graphical install</quote> option in the initial boot menu. For more information about the graphical installer, please refer to <xref linkend="graphical"/>.
|
|
|
Tag: para
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
using-d-i.xml:59
|
|
|
10.
|
|
|
For this architecture the installer uses a character-based user interface. A graphical user interface is currently not available.
|
|
|
Tag: para
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
using-d-i.xml:67
|
