UbiquityAutomation

Differences between revisions 10 and 11
⇤ ← Revision 10 as of 2008-11-26 09:46:01 →
Size: 2430
Editor: 82-69-40-219
Comment: update installation-guide link to hardy
← Revision 11 as of 2008-11-26 09:55:06 → ⇥
Size: 2685
Editor: 82-69-40-219
Comment: divide into sections and expand a bit
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
= Automating Ubiquity =
Line 3: Line 5:
Like debian-installer, you have three options for passing your preseed file to the installer. You can place it in the root of the initrd as the preseed.cfg file, you can place it on the cdrom and specify its location using the file= boot parameter, or you can specify its location on a webserver using the url= boot parameter. == Using preseed files ==
Line 5: Line 7:
Unlike debian-installer, ubiquity may be invoked several times in a session without restarting the computer, such as when the user chooses to cancel the install and return later to finish it. For this reason, ubiquity ignores the 'seen' flag (which is used by debconf to indicate that a question should not be asked again) by default. This means that preseeding will not work without passing the --automatic argument to ubiquity. With this argument set, ubiquity will respect the seen flag and will not present pages where all of the questions have been successfully answered. Like debian-installer, you have three options for passing your preseed file to the installer. You can place it in the root of the initrd as the preseed.cfg file, you can place it on the CD-ROM and specify its location using the file= boot parameter, or you can specify its location on a web server using the url= boot parameter.
Line 7: Line 9:
In addition to manually passing the --automatic flag to ubiquity, you also have the option of adding the 'automatic-ubiquity' option to the boot parameters. Doing so will cause the graphical environment to be started with just ubiquity (with its automatic flag set). Unlike debian-installer, ubiquity may be invoked several times in a session without restarting the computer, such as when the user chooses to cancel the install and return later to finish it. For this reason, ubiquity ignores the 'seen' flag (which is used by debconf to indicate that a question should not be asked again) by default. This is usually inappropriate for preseeding, so you need to arrange for ubiquity to start up in "automatic mode", either by adding the 'automatic-ubiquity' option as a boot parameter, or by passing the --automatic argument to ubiquity if you are starting it up in some other way. In automatic mode, ubiquity will respect the seen flag and will not present pages where all of the questions have been successfully answered.

== Available preseeding keys ==
Line 13: Line 17:
 * '''ubiquity/success_command''': similar to preseed/late_command. Specifiy a command to be run when the install completes successfully (runs outside of /target, but /target is mounted when the command is invoked).  * '''ubiquity/success_command''': similar to preseed/late_command. Specify a command to be run when the install completes successfully (runs outside of /target, but /target is mounted when the command is invoked).

Preseeding keys for the following installer components cannot be used in Ubiquity, usually because they do not fit with Ubiquity's mode of operation:

 * netcfg
 * LVM and RAID partitioning
 * base-installer
 * pkgsel/tasksel
 * finish-install

Automating Ubiquity

With respect to automation, ubiquity, the desktop CD installer, works much in the same way that debian-installer, the alternate CD installer does. Therefore, it is recommended that you first read the debian-installer installation guide and create a working preseed file for that before continuing here.

Using preseed files

Like debian-installer, you have three options for passing your preseed file to the installer. You can place it in the root of the initrd as the preseed.cfg file, you can place it on the CD-ROM and specify its location using the file= boot parameter, or you can specify its location on a web server using the url= boot parameter.

Unlike debian-installer, ubiquity may be invoked several times in a session without restarting the computer, such as when the user chooses to cancel the install and return later to finish it. For this reason, ubiquity ignores the 'seen' flag (which is used by debconf to indicate that a question should not be asked again) by default. This is usually inappropriate for preseeding, so you need to arrange for ubiquity to start up in "automatic mode", either by adding the 'automatic-ubiquity' option as a boot parameter, or by passing the --automatic argument to ubiquity if you are starting it up in some other way. In automatic mode, ubiquity will respect the seen flag and will not present pages where all of the questions have been successfully answered.

Available preseeding keys

Ubiquity uses a subset of the components that Ubuntu's version of debian-installer uses and therefore asks the same questions for those components. However, there are some additional questions provided. These are as follows:

  • ubiquity/summary: preseed empty to avoid the summary page.

  • ubiquity/reboot: automatically reboot when the installer completes. Be sure to add 'noprompt' to the kernel command line to also skip the "please remove the disc, close the tray (if any) and press ENTER to continue" usplash prompt.

  • ubiquity/failure_command: specify a command to be run when the install fails.

  • ubiquity/success_command: similar to preseed/late_command. Specify a command to be run when the install completes successfully (runs outside of /target, but /target is mounted when the command is invoked).

Preseeding keys for the following installer components cannot be used in Ubiquity, usually because they do not fit with Ubiquity's mode of operation:

  • netcfg
  • LVM and RAID partitioning
  • base-installer
  • pkgsel/tasksel
  • finish-install

UbiquityAutomation (last edited 2019-07-12 07:07:21 by tsimonq2)