********** adduser ********** Template: adduser/title Type: title Description: Adduser Template: adduser/homedir-permission Type: boolean Default: true Description: Do you want system-wide readable home directories? By default, users' home directories are readable by all users on the system. If you want to increase security and privacy, you might want home directories to be readable only for their owners. But if in doubt, leave this option enabled. . This will only affect home directories of users added from now on with the adduser command. ********** adduser ********** Template: adduser/title Type: title Description: Adduser Template: adduser/homedir-permission Type: boolean Default: true Description: Do you want system-wide readable home directories? By default, users' home directories are readable by all users on the system. If you want to increase security and privacy, you might want home directories to be readable only for their owners. But if in doubt, leave this option enabled. . This will only affect home directories of users added from now on with the adduser command. ********** apt-cdrom-setup ********** Template: apt-setup/progress/cdrom Type: text Description: Scanning the CD-ROM... Template: apt-setup/cdrom/failed Type: error Description: apt configuration problem An attempt to configure apt to install additional packages from the CD failed. Template: apt-setup/cdrom/set-first Type: boolean Default: false Description: Scan another CD or DVD? Your installation CD or DVD has been scanned; its label is: . ${LABEL} . You now have the option to scan additional CDs or DVDs for use by the package manager (apt). Normally these should be from the same set as the installation CD/DVD. If you do not have any additional CDs or DVDs available, this step can just be skipped. . If you wish to scan another CD or DVD, please insert it now. Template: apt-setup/cdrom/set-next Type: boolean Default: false Description: Scan another CD or DVD? The CD or DVD with the following label has been scanned: . ${LABEL} . If you wish to scan another CD or DVD, please insert it now. Template: apt-setup/cdrom/set-double Type: boolean Default: true Description: Scan another CD or DVD? The CD or DVD with the following label has already been scanned: . ${LABEL} . Please replace it now if you wish to scan another CD or DVD. Template: apt-setup/cdrom/set-failed Type: boolean Default: true Description: Scan another CD or DVD? An attempt to configure apt to install additional packages from the CD/DVD failed. . Please check that the CD/DVD has been inserted correctly. Template: apt-setup/cdrom/media-change Type: text Description: Media change /cdrom/:Please insert the disc labeled: '${LABEL}' in the drive '/cdrom/' and press enter. Template: finish-install/progress/apt-cdrom-setup Type: text Description: Disabling netinst CD in sources.list... Template: apt-setup/use/netinst_old Type: text Description: If you are installing from a netinst CD and choose not to use a mirror, you will end up with only a very minimal base system. Template: apt-setup/use/netinst Type: text Description: You are installing from a netinst CD, which by itself only allows installation of a very minimal base system. Use a mirror to install a more complete system. Template: apt-setup/use/cd Type: text Description: You are installing from a CD, which contains a limited selection of packages. Template: apt-setup/use/cd-set1 Type: text Description: You have scanned %i CDs. Even though these contain a fair selection of packages, some may be missing (notably some packages needed to support languages other than English). Template: apt-setup/use/cd-set2 Type: text Description: You have scanned %i CDs. Even though these contain a large selection of packages, some may be missing. Template: apt-setup/use/cd-note Type: text Description: Note that using a mirror can result in a large amount of data being downloaded during the next step of the installation. Template: apt-setup/use/dvd Type: text Description: You are installing from a DVD. Even though the DVD contains a large selection of packages, some may be missing. Template: apt-setup/use/inet1 Type: text Description: Unless you don't have a good Internet connection, use of a mirror is recommended, especially if you plan to install a graphical desktop environment. Template: apt-setup/use/inet2 Type: text Description: If you have a reasonably good Internet connection, use of a mirror is suggested if you plan to install a graphical desktop environment. Template: apt-setup/disable-cdrom-entries Type: boolean Default: false Description: for internal use; can be preseeded When set to true, apt-setup always disables cdrom entries from APT's configuration. Otherwise, it disables them only when a netinst image has been used. . This option can be preseeded for automated installations that should not reference the installation media in the target system. ********** apt-cdrom-setup ********** Template: apt-setup/progress/cdrom Type: text Description: Scanning the CD-ROM... Template: apt-setup/cdrom/failed Type: error Description: apt configuration problem An attempt to configure apt to install additional packages from the CD failed. Template: apt-setup/cdrom/set-first Type: boolean Default: false Description: Scan another CD or DVD? Your installation CD or DVD has been scanned; its label is: . ${LABEL} . You now have the option to scan additional CDs or DVDs for use by the package manager (apt). Normally these should be from the same set as the installation CD/DVD. If you do not have any additional CDs or DVDs available, this step can just be skipped. . If you wish to scan another CD or DVD, please insert it now. Template: apt-setup/cdrom/set-next Type: boolean Default: false Description: Scan another CD or DVD? The CD or DVD with the following label has been scanned: . ${LABEL} . If you wish to scan another CD or DVD, please insert it now. Template: apt-setup/cdrom/set-double Type: boolean Default: true Description: Scan another CD or DVD? The CD or DVD with the following label has already been scanned: . ${LABEL} . Please replace it now if you wish to scan another CD or DVD. Template: apt-setup/cdrom/set-failed Type: boolean Default: true Description: Scan another CD or DVD? An attempt to configure apt to install additional packages from the CD/DVD failed. . Please check that the CD/DVD has been inserted correctly. Template: apt-setup/cdrom/media-change Type: text Description: Media change /cdrom/:Please insert the disc labeled: '${LABEL}' in the drive '/cdrom/' and press enter. Template: finish-install/progress/apt-cdrom-setup Type: text Description: Disabling netinst CD in sources.list... Template: apt-setup/use/netinst_old Type: text Description: If you are installing from a netinst CD and choose not to use a mirror, you will end up with only a very minimal base system. Template: apt-setup/use/netinst Type: text Description: You are installing from a netinst CD, which by itself only allows installation of a very minimal base system. Use a mirror to install a more complete system. Template: apt-setup/use/cd Type: text Description: You are installing from a CD, which contains a limited selection of packages. Template: apt-setup/use/cd-set1 Type: text Description: You have scanned %i CDs. Even though these contain a fair selection of packages, some may be missing (notably some packages needed to support languages other than English). Template: apt-setup/use/cd-set2 Type: text Description: You have scanned %i CDs. Even though these contain a large selection of packages, some may be missing. Template: apt-setup/use/cd-note Type: text Description: Note that using a mirror can result in a large amount of data being downloaded during the next step of the installation. Template: apt-setup/use/dvd Type: text Description: You are installing from a DVD. Even though the DVD contains a large selection of packages, some may be missing. Template: apt-setup/use/inet1 Type: text Description: Unless you don't have a good Internet connection, use of a mirror is recommended, especially if you plan to install a graphical desktop environment. Template: apt-setup/use/inet2 Type: text Description: If you have a reasonably good Internet connection, use of a mirror is suggested if you plan to install a graphical desktop environment. Template: apt-setup/disable-cdrom-entries Type: boolean Default: false Description: for internal use; can be preseeded When set to true, apt-setup always disables cdrom entries from APT's configuration. Otherwise, it disables them only when a netinst image has been used. . This option can be preseeded for automated installations that should not reference the installation media in the target system. ********** apt-cdrom-setup ********** Template: apt-setup/progress/cdrom Type: text Description: Scanning the CD-ROM... Template: apt-setup/cdrom/failed Type: error Description: apt configuration problem An attempt to configure apt to install additional packages from the CD failed. Template: apt-setup/cdrom/set-first Type: boolean Default: false Description: Scan another CD or DVD? Your installation CD or DVD has been scanned; its label is: . ${LABEL} . You now have the option to scan additional CDs or DVDs for use by the package manager (apt). Normally these should be from the same set as the installation CD/DVD. If you do not have any additional CDs or DVDs available, this step can just be skipped. . If you wish to scan another CD or DVD, please insert it now. Template: apt-setup/cdrom/set-next Type: boolean Default: false Description: Scan another CD or DVD? The CD or DVD with the following label has been scanned: . ${LABEL} . If you wish to scan another CD or DVD, please insert it now. Template: apt-setup/cdrom/set-double Type: boolean Default: true Description: Scan another CD or DVD? The CD or DVD with the following label has already been scanned: . ${LABEL} . Please replace it now if you wish to scan another CD or DVD. Template: apt-setup/cdrom/set-failed Type: boolean Default: true Description: Scan another CD or DVD? An attempt to configure apt to install additional packages from the CD/DVD failed. . Please check that the CD/DVD has been inserted correctly. Template: apt-setup/cdrom/media-change Type: text Description: Media change /cdrom/:Please insert the disc labeled: '${LABEL}' in the drive '/cdrom/' and press enter. Template: finish-install/progress/apt-cdrom-setup Type: text Description: Disabling netinst CD in sources.list... Template: apt-setup/use/netinst_old Type: text Description: If you are installing from a netinst CD and choose not to use a mirror, you will end up with only a very minimal base system. Template: apt-setup/use/netinst Type: text Description: You are installing from a netinst CD, which by itself only allows installation of a very minimal base system. Use a mirror to install a more complete system. Template: apt-setup/use/cd Type: text Description: You are installing from a CD, which contains a limited selection of packages. Template: apt-setup/use/cd-set1 Type: text Description: You have scanned %i CDs. Even though these contain a fair selection of packages, some may be missing (notably some packages needed to support languages other than English). Template: apt-setup/use/cd-set2 Type: text Description: You have scanned %i CDs. Even though these contain a large selection of packages, some may be missing. Template: apt-setup/use/cd-note Type: text Description: Note that using a mirror can result in a large amount of data being downloaded during the next step of the installation. Template: apt-setup/use/dvd Type: text Description: You are installing from a DVD. Even though the DVD contains a large selection of packages, some may be missing. Template: apt-setup/use/inet1 Type: text Description: Unless you don't have a good Internet connection, use of a mirror is recommended, especially if you plan to install a graphical desktop environment. Template: apt-setup/use/inet2 Type: text Description: If you have a reasonably good Internet connection, use of a mirror is suggested if you plan to install a graphical desktop environment. Template: apt-setup/disable-cdrom-entries Type: boolean Default: false Description: for internal use; can be preseeded When set to true, apt-setup always disables cdrom entries from APT's configuration. Otherwise, it disables them only when a netinst image has been used. . This option can be preseeded for automated installations that should not reference the installation media in the target system. ********** apt-mirror-setup ********** Template: apt-setup/progress/mirror Type: text Description: Scanning the mirror... Template: apt-setup/non-free Type: boolean Default: false Description: Use non-free software? Some non-free software has been made to work with Debian. Though this software is not at all a part of Debian, standard Debian tools can be used to install it. This software has varying licenses which may prevent you from using, modifying, or sharing it. . Please choose whether you want to have it available anyway. Template: apt-setup/contrib Type: boolean Default: false Description: Use contrib software? Some additional software has been made to work with Debian. Though this software is free, it depends on non-free software for its operation. This software is not a part of Debian, but standard Debian tools can be used to install it. . Please choose whether you want this software to be made available to you. Template: apt-setup/mirror/error Type: select Default: Retry Choices: Retry, Change mirror, Ignore Description: Downloading a file failed: The installer failed to access the mirror. This may be a problem with your network, or with the mirror. You can choose to retry the download, select a different mirror, or ignore the problem and continue without all the packages from this mirror. Template: apt-setup/use_mirror Type: boolean Description: Use a network mirror? A network mirror can be used to supplement the software that is included on the CD-ROM. This may also make newer versions of software available. . ${EXPLANATION} Template: apt-setup/no_mirror Type: boolean Default: false Description: Continue without a network mirror? No network mirror was selected. . If you are installing from a netinst CD and choose not to use a mirror, you will end up with only a very minimal base system. ********** apt-mirror-setup ********** Template: apt-setup/progress/mirror Type: text Description: Scanning the mirror... Template: apt-setup/non-free Type: boolean Default: false Description: Use non-free software? Some non-free software has been made to work with Debian. Though this software is not at all a part of Debian, standard Debian tools can be used to install it. This software has varying licenses which may prevent you from using, modifying, or sharing it. . Please choose whether you want to have it available anyway. Template: apt-setup/contrib Type: boolean Default: false Description: Use contrib software? Some additional software has been made to work with Debian. Though this software is free, it depends on non-free software for its operation. This software is not a part of Debian, but standard Debian tools can be used to install it. . Please choose whether you want this software to be made available to you. Template: apt-setup/mirror/error Type: select Default: Retry Choices: Retry, Change mirror, Ignore Description: Downloading a file failed: The installer failed to access the mirror. This may be a problem with your network, or with the mirror. You can choose to retry the download, select a different mirror, or ignore the problem and continue without all the packages from this mirror. Template: apt-setup/use_mirror Type: boolean Description: Use a network mirror? A network mirror can be used to supplement the software that is included on the CD-ROM. This may also make newer versions of software available. . ${EXPLANATION} Template: apt-setup/no_mirror Type: boolean Default: false Description: Continue without a network mirror? No network mirror was selected. . If you are installing from a netinst CD and choose not to use a mirror, you will end up with only a very minimal base system. ********** apt-setup-udeb ********** Template: debian-installer/apt-setup-udeb/title Type: text Description: Configure the package manager Template: apt-setup/progress/title Type: text Description: Configuring apt Template: apt-setup/progress/fallback Type: text Description: Running ${SCRIPT}... Template: apt-setup/progress/local Type: text Description: Scanning local repositories... Template: apt-setup/progress/security Type: text Description: Scanning the security updates repository... Template: apt-setup/progress/updates Type: text Description: Scanning the release updates repository... Template: apt-setup/progress/backports Type: text Description: Scanning the backports repository... Template: apt-setup/local/key-error Type: select Default: Retry Choices: Retry, Ignore Description: Downloading local repository key failed: The installer failed to download the public key used to sign the local repository at ${MIRROR}: . ${URL} . This may be a problem with your network, or with the server hosting this key. You can choose to retry the download, or ignore the problem and continue without all the packages from this repository. Template: apt-setup/security_host Type: string Default: security.debian.org Description: for internal use; can be preseeded Host to use for security updates Template: apt-setup/service-failed Type: error Description: Cannot access repository The repository on ${HOST} couldn't be accessed, so its updates will not be made available to you at this time. You should investigate this later. . Commented out entries for ${HOST} have been added to the /etc/apt/sources.list file. Template: apt-setup/services-select Type: multiselect Choices-C: security, updates, backports Choices: security updates (from ${SEC_HOST}), release updates, backported software Default: security, updates Description: Services to use: Debian has two services that provide updates to releases: security and release updates. . Security updates help to keep your system secured against attacks. Enabling this service is strongly recommended. . Release updates provide more current versions for software that changes relatively frequently and where not having the latest version could reduce the usability of the software. It also provides regression fixes. This service is only available for stable and oldstable releases. . Backported software are adapted from the development version to work with this release. Although this software has not gone through such complete testing as that contained in the release, it includes newer versions of some applications which may provide useful features. Enabling backports here does not cause any of them to be installed by default; it only allows you to manually select backports to use. Template: apt-setup/enable-source-repositories Type: boolean Default: true Description: Enable source repositories in APT? By default source repositories are listed in /etc/apt/sources.list (with appropriate "deb-src" lines) so that "apt-get source" works. However, if you don't need this feature, you can disable those entries and save some bandwidth during "apt-get update" operations. Template: apt-setup/multiarch Type: string Default: Description: for internal use; can be preseeded Set to the list of architectures for which packages can be installed without using 'dpkg --force-architecture', in addition to the native architecture. If empty, only allow installing packages from the native architecture. ********** apt-setup-udeb ********** Template: debian-installer/apt-setup-udeb/title Type: text Description: Configure the package manager Template: apt-setup/progress/title Type: text Description: Configuring apt Template: apt-setup/progress/fallback Type: text Description: Running ${SCRIPT}... Template: apt-setup/progress/local Type: text Description: Scanning local repositories... Template: apt-setup/progress/security Type: text Description: Scanning the security updates repository... Template: apt-setup/progress/updates Type: text Description: Scanning the release updates repository... Template: apt-setup/progress/backports Type: text Description: Scanning the backports repository... Template: apt-setup/local/key-error Type: select Default: Retry Choices: Retry, Ignore Description: Downloading local repository key failed: The installer failed to download the public key used to sign the local repository at ${MIRROR}: . ${URL} . This may be a problem with your network, or with the server hosting this key. You can choose to retry the download, or ignore the problem and continue without all the packages from this repository. Template: apt-setup/security_host Type: string Default: security.debian.org Description: for internal use; can be preseeded Host to use for security updates Template: apt-setup/service-failed Type: error Description: Cannot access repository The repository on ${HOST} couldn't be accessed, so its updates will not be made available to you at this time. You should investigate this later. . Commented out entries for ${HOST} have been added to the /etc/apt/sources.list file. Template: apt-setup/services-select Type: multiselect Choices-C: security, updates, backports Choices: security updates (from ${SEC_HOST}), release updates, backported software Default: security, updates Description: Services to use: Debian has two services that provide updates to releases: security and release updates. . Security updates help to keep your system secured against attacks. Enabling this service is strongly recommended. . Release updates provide more current versions for software that changes relatively frequently and where not having the latest version could reduce the usability of the software. It also provides regression fixes. This service is only available for stable and oldstable releases. . Backported software are adapted from the development version to work with this release. Although this software has not gone through such complete testing as that contained in the release, it includes newer versions of some applications which may provide useful features. Enabling backports here does not cause any of them to be installed by default; it only allows you to manually select backports to use. Template: apt-setup/enable-source-repositories Type: boolean Default: true Description: Enable source repositories in APT? By default source repositories are listed in /etc/apt/sources.list (with appropriate "deb-src" lines) so that "apt-get source" works. However, if you don't need this feature, you can disable those entries and save some bandwidth during "apt-get update" operations. Template: apt-setup/multiarch Type: string Default: Description: for internal use; can be preseeded Set to the list of architectures for which packages can be installed without using 'dpkg --force-architecture', in addition to the native architecture. If empty, only allow installing packages from the native architecture. ********** base-installer ********** Template: base-installer/use_unclean_target Type: boolean Default: true Description: Proceed with installation to unclean target? The target file system contains files from a past installation. These files could cause problems with the installation process, and if you proceed, some of the existing files may be overwritten. Template: base-installer/no_target_mounted Type: error Description: No file system mounted on /target Before the installation can proceed, a root file system must be mounted on /target. The partitioner and formatter should have done this for you. Template: base-installer/unclean_target_cancel Type: error Description: Not installing to unclean target The installation to the target file system has been canceled. You should go back and erase or format the target file system before proceeding with the install. Template: base-installer/progress/preparing Type: text Description: Preparing to install the base system... Template: base-installer/progress/installing-base Type: text Description: Installing the base system Template: base-installer/progress/fallback Type: text Description: Running ${SCRIPT}... Template: base-installer/section/setup_dev Type: text Description: Setting up the base system... Template: base-installer/section/configure_apt Type: text Description: Configuring APT sources... Template: base-installer/section/apt_update Type: text Description: Updating the list of available packages... Template: base-installer/section/install_extra Type: text Description: Installing extra packages... Template: base-installer/section/install_extra_package Type: text Description: Installing extra packages - retrieving and installing ${SUBST0}... Template: base-installer/install-recommends Type: boolean Default: true Description: for internal use; can be preseeded Will configure APT in the target system not to install recommened packages by default. For experienced users only. ********** base-installer ********** Template: base-installer/use_unclean_target Type: boolean Default: true Description: Proceed with installation to unclean target? The target file system contains files from a past installation. These files could cause problems with the installation process, and if you proceed, some of the existing files may be overwritten. Template: base-installer/no_target_mounted Type: error Description: No file system mounted on /target Before the installation can proceed, a root file system must be mounted on /target. The partitioner and formatter should have done this for you. Template: base-installer/unclean_target_cancel Type: error Description: Not installing to unclean target The installation to the target file system has been canceled. You should go back and erase or format the target file system before proceeding with the install. Template: base-installer/progress/preparing Type: text Description: Preparing to install the base system... Template: base-installer/progress/installing-base Type: text Description: Installing the base system Template: base-installer/progress/fallback Type: text Description: Running ${SCRIPT}... Template: base-installer/section/setup_dev Type: text Description: Setting up the base system... Template: base-installer/section/configure_apt Type: text Description: Configuring APT sources... Template: base-installer/section/apt_update Type: text Description: Updating the list of available packages... Template: base-installer/section/install_extra Type: text Description: Installing extra packages... Template: base-installer/section/install_extra_package Type: text Description: Installing extra packages - retrieving and installing ${SUBST0}... Template: base-installer/install-recommends Type: boolean Default: true Description: for internal use; can be preseeded Will configure APT in the target system not to install recommened packages by default. For experienced users only. ********** base-passwd ********** Template: base-passwd/user-move Type: boolean Default: true Description: Do you want to move the user ${name}? update-passwd has found a difference between your system accounts and the current Debian defaults. It is advisable to allow update-passwd to change your system; without those changes some packages might not work correctly. For more documentation on the Debian account policies, please see /usr/share/doc/base-passwd/README. . The proposed change is: . Move user "${name}" (${id}) to before the NIS compat "+" entry . If you allow this change, a backup of modified files will be made with the extension .org, which you can use if necessary to restore the current settings. If you do not make this change now, you can make it later with the update-passwd utility. Template: base-passwd/group-move Type: boolean Default: true Description: Do you want to move the group ${name}? update-passwd has found a difference between your system accounts and the current Debian defaults. It is advisable to allow update-passwd to change your system; without those changes some packages might not work correctly. For more documentation on the Debian account policies, please see /usr/share/doc/base-passwd/README. . The proposed change is: . Move group "${name}" (${id}) to before the NIS compat "+" entry . If you allow this change, a backup of modified files will be made with the extension .org, which you can use if necessary to restore the current settings. If you do not make this change now, you can make it later with the update-passwd utility. Template: base-passwd/user-add Type: boolean Default: true Description: Do you want to add the user ${name}? update-passwd has found a difference between your system accounts and the current Debian defaults. It is advisable to allow update-passwd to change your system; without those changes some packages might not work correctly. For more documentation on the Debian account policies, please see /usr/share/doc/base-passwd/README. . The proposed change is: . Add user "${name}" (${id}) . If you allow this change, a backup of modified files will be made with the extension .org, which you can use if necessary to restore the current settings. If you do not make this change now, you can make it later with the update-passwd utility. Template: base-passwd/group-add Type: boolean Default: true Description: Do you want to add the group ${name}? update-passwd has found a difference between your system accounts and the current Debian defaults. It is advisable to allow update-passwd to change your system; without those changes some packages might not work correctly. For more documentation on the Debian account policies, please see /usr/share/doc/base-passwd/README. . The proposed change is: . Add group "${name}" (${id}) . If you allow this change, a backup of modified files will be made with the extension .org, which you can use if necessary to restore the current settings. If you do not make this change now, you can make it later with the update-passwd utility. Template: base-passwd/user-remove Type: boolean Default: true Description: Do you want to remove the user ${name}? update-passwd has found a difference between your system accounts and the current Debian defaults. It is advisable to allow update-passwd to change your system; without those changes some packages might not work correctly. For more documentation on the Debian account policies, please see /usr/share/doc/base-passwd/README. . The proposed change is: . Remove user "${name}" (${id}) . If you allow this change, a backup of modified files will be made with the extension .org, which you can use if necessary to restore the current settings. If you do not make this change now, you can make it later with the update-passwd utility. Template: base-passwd/group-remove Type: boolean Default: true Description: Do you want to remove the group ${name}? update-passwd has found a difference between your system accounts and the current Debian defaults. It is advisable to allow update-passwd to change your system; without those changes some packages might not work correctly. For more documentation on the Debian account policies, please see /usr/share/doc/base-passwd/README. . The proposed change is: . Remove group "${name}" (${id}) . If you allow this change, a backup of modified files will be made with the extension .org, which you can use if necessary to restore the current settings. If you do not make this change now, you can make it later with the update-passwd utility. Template: base-passwd/user-change-uid Type: boolean Default: true Description: Do you want to change the UID of user ${name}? update-passwd has found a difference between your system accounts and the current Debian defaults. It is advisable to allow update-passwd to change your system; without those changes some packages might not work correctly. For more documentation on the Debian account policies, please see /usr/share/doc/base-passwd/README. . The proposed change is: . Change the UID of user "${name}" from ${old_uid} to ${new_uid} . If you allow this change, a backup of modified files will be made with the extension .org, which you can use if necessary to restore the current settings. If you do not make this change now, you can make it later with the update-passwd utility. Template: base-passwd/user-change-gid Type: boolean Default: true Description: Do you want to change the GID of user ${name}? update-passwd has found a difference between your system accounts and the current Debian defaults. It is advisable to allow update-passwd to change your system; without those changes some packages might not work correctly. For more documentation on the Debian account policies, please see /usr/share/doc/base-passwd/README. . The proposed change is: . Change the GID of user "${name}" from ${old_gid} (${old_group}) to ${new_gid} (${new_group}) . If you allow this change, a backup of modified files will be made with the extension .org, which you can use if necessary to restore the current settings. If you do not make this change now, you can make it later with the update-passwd utility. Template: base-passwd/user-change-gecos Type: boolean Default: true Description: Do you want to change the GECOS of user ${name}? update-passwd has found a difference between your system accounts and the current Debian defaults. It is advisable to allow update-passwd to change your system; without those changes some packages might not work correctly. For more documentation on the Debian account policies, please see /usr/share/doc/base-passwd/README. . The proposed change is: . Change the GECOS of user "${name}" from "${old_gecos}" to "${new_gecos}" . If you allow this change, a backup of modified files will be made with the extension .org, which you can use if necessary to restore the current settings. If you do not make this change now, you can make it later with the update-passwd utility. Template: base-passwd/user-change-home Type: boolean Default: true Description: Do you want to change the home directory of user ${name}? update-passwd has found a difference between your system accounts and the current Debian defaults. It is advisable to allow update-passwd to change your system; without those changes some packages might not work correctly. For more documentation on the Debian account policies, please see /usr/share/doc/base-passwd/README. . The proposed change is: . Change the home directory of user "${name}" from ${old_home} to ${new_home} . If you allow this change, a backup of modified files will be made with the extension .org, which you can use if necessary to restore the current settings. If you do not make this change now, you can make it later with the update-passwd utility. Template: base-passwd/user-change-shell Type: boolean Default: true Description: Do you want to change the shell of user ${name}? update-passwd has found a difference between your system accounts and the current Debian defaults. It is advisable to allow update-passwd to change your system; without those changes some packages might not work correctly. For more documentation on the Debian account policies, please see /usr/share/doc/base-passwd/README. . The proposed change is: . Change the shell of user "${name}" from ${old_shell} to ${new_shell} . If you allow this change, a backup of modified files will be made with the extension .org, which you can use if necessary to restore the current settings. If you do not make this change now, you can make it later with the update-passwd utility. Template: base-passwd/group-change-gid Type: boolean Default: true Description: Do you want to change the GID of group ${name}? update-passwd has found a difference between your system accounts and the current Debian defaults. It is advisable to allow update-passwd to change your system; without those changes some packages might not work correctly. For more documentation on the Debian account policies, please see /usr/share/doc/base-passwd/README. . The proposed change is: . Change the GID of group "${name}" from ${old_gid} to ${new_gid} . If you allow this change, a backup of modified files will be made with the extension .org, which you can use if necessary to restore the current settings. If you do not make this change now, you can make it later with the update-passwd utility. ********** bootstrap-base ********** Template: debian-installer/bootstrap-base/title Type: text Description: Install the base system Template: base-installer/cannot_install Type: error Description: Cannot install base system The installer cannot figure out how to install the base system. No installable CD-ROM was found and no valid mirror was configured. Template: base-installer/no_codename Type: error Description: Debootstrap Error Failed to determine the codename for the release. Template: base-installer/debootstrap-failed Type: error Description: Failed to install the base system The base system installation into /target/ failed. . Check /var/log/syslog or see virtual console 4 for the details. Template: base-installer/debootstrap/error-exitcode Type: error Description: Base system installation error The debootstrap program exited with an error (return value ${EXITCODE}). . Check /var/log/syslog or see virtual console 4 for the details. Template: base-installer/debootstrap/error-abnormal Type: error Description: Base system installation error The debootstrap program exited abnormally. . Check /var/log/syslog or see virtual console 4 for the details. Template: base-installer/debootstrap/fallback-error Type: error Description: Debootstrap Error The following error occurred: . ${ERROR} . Check /var/log/syslog or see virtual console 4 for the details. Template: base-installer/initramfs/generator Type: select Choices: ${GENERATORS} Description: Tool to use to generate boot initrd: The list shows the available tools. If you are unsure which to select, you should select the default. If your system fails to boot, you can retry the installation using the other options. Template: base-installer/initramfs/unsupported Type: error Description: Unsupported initrd generator The package ${GENERATOR} that was selected to generate the initrd is not supported. Template: base-installer/initramfs-tools/driver-policy Type: select Choices-C: most, dep Choices: generic: include all available drivers, targeted: only include drivers needed for this system Description: Drivers to include in the initrd: The primary function of an initrd is to allow the kernel to mount the root file system. It therefore needs to contain all drivers and supporting programs required to do that. . A generic initrd is much larger than a targeted one and may even be so large that some boot loaders are unable to load it but has the advantage that it can be used to boot the target system on almost any hardware. With the smaller targeted initrd there is a very small chance that not all needed drivers are included. Template: base-installer/kernel/failed-install Type: error Description: Unable to install the selected kernel An error was returned while trying to install the kernel into the target system. . Kernel package: '${KERNEL}'. . Check /var/log/syslog or see virtual console 4 for the details. Template: base-installer/kernel/image Type: select Choices: ${KERNELS}, none Description: Kernel to install: The list shows the available kernels. Please choose one of them in order to make the system bootable from the hard drive. Template: base-installer/kernel/altmeta Type: text Description: for internal use; can be preseeded Optional postfix for kernel meta packages; can be used for example to support installation of an updated kernel for stable. Don't include the leading hyphen: it will be prepended in the code. Template: base-installer/kernel/skip-install Type: boolean Default: false Description: Continue without installing a kernel? No installable kernel was found in the defined APT sources. . You may try to continue without a kernel, and manually install your own kernel later. This is only recommended for experts, otherwise you will likely end up with a machine that doesn't boot. Template: base-installer/kernel/no-kernels-found Type: error Description: Cannot install kernel The installer cannot find a suitable kernel package to install. Template: base-installer/kernel/failed-package-install Type: error Description: Unable to install ${PACKAGE} An error was returned while trying to install the ${PACKAGE} package onto the target system. . Check /var/log/syslog or see virtual console 4 for the details. Template: base-installer/debootstrap/error/nogetrel Type: error Description: Debootstrap Error Failed getting Release file ${SUBST0}. Template: base-installer/debootstrap/error/nogetrelsig Type: error Description: Debootstrap Error Failed getting Release signature file ${SUBST0}. Template: base-installer/debootstrap/error/unknownrelsig Type: error Description: Debootstrap Error Release file signed by unknown key (key id ${SUBST0}) Template: base-installer/debootstrap/error/invalidrel Type: error Description: Debootstrap Error Invalid Release file: no valid components. Template: base-installer/debootstrap/error/missingrelentry Type: error Description: Debootstrap Error Invalid Release file: no entry for ${SUBST0}. Template: base-installer/debootstrap/error/couldntdl Type: error Description: Debootstrap Error Couldn't retrieve ${SUBST0}. This may be due to a network problem or a bad CD, depending on your installation method. . If you are installing from CD-R or CD-RW, burning the CD at a lower speed may help. Template: base-installer/debootstrap/section/downrel Type: text Description: Retrieving Release file Template: base-installer/debootstrap/progress/downrelsig Type: text Description: Retrieving Release file signature Template: base-installer/debootstrap/section/sizedebs Type: text Description: Finding package sizes Template: base-installer/debootstrap/section/downpkgs Type: text Description: Retrieving Packages files Template: base-installer/debootstrap/section/downmainpkgs Type: text Description: Retrieving Packages file Template: base-installer/debootstrap/section/downdebs Type: text Description: Retrieving packages Template: base-installer/debootstrap/section/extractpkgs Type: text Description: Extracting packages Template: base-installer/debootstrap/section/instbase Type: text Description: Installing the base system Template: base-installer/debootstrap/section/instcore Type: text Description: Installing core packages Template: base-installer/debootstrap/section/unpackreq Type: text Description: Unpacking required packages Template: base-installer/debootstrap/section/confreq Type: text Description: Configuring required packages Template: base-installer/debootstrap/section/unpackbase Type: text Description: Unpacking the base system Template: base-installer/debootstrap/section/confbase Type: text Description: Configuring the base system Template: base-installer/debootstrap/fallback-info Type: text Description: ${SECTION}: ${INFO}... Template: base-installer/debootstrap/info/validating Type: text Description: Validating ${SUBST0}... Template: base-installer/debootstrap/info/retrieving Type: text Description: Retrieving ${SUBST0}... Template: base-installer/debootstrap/info/extracting Type: text Description: Extracting ${SUBST0}... Template: base-installer/debootstrap/info/unpacking Type: text Description: Unpacking ${SUBST0}... Template: base-installer/debootstrap/info/configuring Type: text Description: Configuring ${SUBST0}... Template: base-installer/debootstrap/info/releasesig Type: text Description: Checking Release signature Template: base-installer/debootstrap/info/validrelsig Type: text Description: Valid Release signature (key id ${SUBST0}) Template: base-installer/debootstrap/info/resolvebase Type: text Description: Resolving dependencies of base packages... Template: base-installer/debootstrap/info/newbase Type: text Description: Found additional base dependencies: ${SUBST0} Template: base-installer/debootstrap/info/newrequired Type: text Description: Found additional required dependencies: ${SUBST0} Template: base-installer/debootstrap/info/redundantbase Type: text Description: Found packages in base already in required: ${SUBST0} Template: base-installer/debootstrap/info/resolvereq Type: text Description: Resolving dependencies of required packages... Template: base-installer/debootstrap/info/checkingsizes Type: text Description: Checking component ${SUBST0} on ${SUBST1}... Template: base-installer/debootstrap/info/instcore Type: text Description: Installing core packages... Template: base-installer/debootstrap/info/unpackreq Type: text Description: Unpacking required packages... Template: base-installer/debootstrap/info/confreq Type: text Description: Configuring required packages... Template: base-installer/debootstrap/info/instbase Type: text Description: Installing base packages... Template: base-installer/debootstrap/info/unpackbase Type: text Description: Unpacking the base system... Template: base-installer/debootstrap/info/confbase Type: text Description: Configuring the base system... Template: base-installer/debootstrap/info/basesuccess Type: text Description: Base system installed successfully. Template: base-installer/debootstrap/fallback-warning Type: error Description: Debootstrap warning Warning: ${INFO} Template: base-installer/debootstrap/warning/retrying Type: text Description: Retrying failed download of ${SUBST0} Template: base-installer/section/configure_apt Type: text Description: Configuring APT sources... Template: base-installer/section/pick_kernel Type: text Description: Selecting the kernel to install... Template: base-installer/section/install_linux Type: text Description: Installing the kernel... Template: base-installer/section/install_kernel_package Type: text Description: Installing the kernel - retrieving and installing ${SUBST0}... Template: base-installer/includes Type: string Description: for internal use; can be preseeded Packages to be included in base installation Template: base-installer/excludes Type: string Description: for internal use; can be preseeded Packages to be excluded in base installation Template: base-installer/debootstrap_script Type: string Description: for internal use; can be preseeded Force use of a specific debootstrap script Template: base-installer/kernel/linux/initrd-2.6 Type: boolean Default: true Description: for internal use only Use an (initramfs) initrd (linux 2.6 and later only) Template: base-installer/kernel/linux/initramfs-tools/driver-policy Type: string Default: most Description: for internal use Default driver inclusion policy for initramfs-tools Template: base-installer/kernel/linux/extra-packages Type: string Description: for internal use; can be preseeded Default: Extra packages to install with init*-tools (linux only) Template: base-installer/kernel/linux/extra-packages-2.6 Type: string Description: for internal use; can be preseeded Default: Extra packages to install with init*-tools (linux 2.6 and later only) Template: base-installer/kernel/linux/link_in_boot Type: boolean Default: false Description: for internal use only Kernel needs a link in /boot/ (linux only) ********** bootstrap-base ********** Template: debian-installer/bootstrap-base/title Type: text Description: Install the base system Template: base-installer/cannot_install Type: error Description: Cannot install base system The installer cannot figure out how to install the base system. No installable CD-ROM was found and no valid mirror was configured. Template: base-installer/no_codename Type: error Description: Debootstrap Error Failed to determine the codename for the release. Template: base-installer/debootstrap-failed Type: error Description: Failed to install the base system The base system installation into /target/ failed. . Check /var/log/syslog or see virtual console 4 for the details. Template: base-installer/debootstrap/error-exitcode Type: error Description: Base system installation error The debootstrap program exited with an error (return value ${EXITCODE}). . Check /var/log/syslog or see virtual console 4 for the details. Template: base-installer/debootstrap/error-abnormal Type: error Description: Base system installation error The debootstrap program exited abnormally. . Check /var/log/syslog or see virtual console 4 for the details. Template: base-installer/debootstrap/fallback-error Type: error Description: Debootstrap Error The following error occurred: . ${ERROR} . Check /var/log/syslog or see virtual console 4 for the details. Template: base-installer/initramfs/generator Type: select Choices: ${GENERATORS} Description: Tool to use to generate boot initrd: The list shows the available tools. If you are unsure which to select, you should select the default. If your system fails to boot, you can retry the installation using the other options. Template: base-installer/initramfs/unsupported Type: error Description: Unsupported initrd generator The package ${GENERATOR} that was selected to generate the initrd is not supported. Template: base-installer/initramfs-tools/driver-policy Type: select Choices-C: most, dep Choices: generic: include all available drivers, targeted: only include drivers needed for this system Description: Drivers to include in the initrd: The primary function of an initrd is to allow the kernel to mount the root file system. It therefore needs to contain all drivers and supporting programs required to do that. . A generic initrd is much larger than a targeted one and may even be so large that some boot loaders are unable to load it but has the advantage that it can be used to boot the target system on almost any hardware. With the smaller targeted initrd there is a very small chance that not all needed drivers are included. Template: base-installer/kernel/failed-install Type: error Description: Unable to install the selected kernel An error was returned while trying to install the kernel into the target system. . Kernel package: '${KERNEL}'. . Check /var/log/syslog or see virtual console 4 for the details. Template: base-installer/kernel/image Type: select Choices: ${KERNELS}, none Description: Kernel to install: The list shows the available kernels. Please choose one of them in order to make the system bootable from the hard drive. Template: base-installer/kernel/altmeta Type: text Description: for internal use; can be preseeded Optional postfix for kernel meta packages; can be used for example to support installation of an updated kernel for stable. Don't include the leading hyphen: it will be prepended in the code. Template: base-installer/kernel/skip-install Type: boolean Default: false Description: Continue without installing a kernel? No installable kernel was found in the defined APT sources. . You may try to continue without a kernel, and manually install your own kernel later. This is only recommended for experts, otherwise you will likely end up with a machine that doesn't boot. Template: base-installer/kernel/no-kernels-found Type: error Description: Cannot install kernel The installer cannot find a suitable kernel package to install. Template: base-installer/kernel/failed-package-install Type: error Description: Unable to install ${PACKAGE} An error was returned while trying to install the ${PACKAGE} package onto the target system. . Check /var/log/syslog or see virtual console 4 for the details. Template: base-installer/debootstrap/error/nogetrel Type: error Description: Debootstrap Error Failed getting Release file ${SUBST0}. Template: base-installer/debootstrap/error/nogetrelsig Type: error Description: Debootstrap Error Failed getting Release signature file ${SUBST0}. Template: base-installer/debootstrap/error/unknownrelsig Type: error Description: Debootstrap Error Release file signed by unknown key (key id ${SUBST0}) Template: base-installer/debootstrap/error/invalidrel Type: error Description: Debootstrap Error Invalid Release file: no valid components. Template: base-installer/debootstrap/error/missingrelentry Type: error Description: Debootstrap Error Invalid Release file: no entry for ${SUBST0}. Template: base-installer/debootstrap/error/couldntdl Type: error Description: Debootstrap Error Couldn't retrieve ${SUBST0}. This may be due to a network problem or a bad CD, depending on your installation method. . If you are installing from CD-R or CD-RW, burning the CD at a lower speed may help. Template: base-installer/debootstrap/section/downrel Type: text Description: Retrieving Release file Template: base-installer/debootstrap/progress/downrelsig Type: text Description: Retrieving Release file signature Template: base-installer/debootstrap/section/sizedebs Type: text Description: Finding package sizes Template: base-installer/debootstrap/section/downpkgs Type: text Description: Retrieving Packages files Template: base-installer/debootstrap/section/downmainpkgs Type: text Description: Retrieving Packages file Template: base-installer/debootstrap/section/downdebs Type: text Description: Retrieving packages Template: base-installer/debootstrap/section/extractpkgs Type: text Description: Extracting packages Template: base-installer/debootstrap/section/instbase Type: text Description: Installing the base system Template: base-installer/debootstrap/section/instcore Type: text Description: Installing core packages Template: base-installer/debootstrap/section/unpackreq Type: text Description: Unpacking required packages Template: base-installer/debootstrap/section/confreq Type: text Description: Configuring required packages Template: base-installer/debootstrap/section/unpackbase Type: text Description: Unpacking the base system Template: base-installer/debootstrap/section/confbase Type: text Description: Configuring the base system Template: base-installer/debootstrap/fallback-info Type: text Description: ${SECTION}: ${INFO}... Template: base-installer/debootstrap/info/validating Type: text Description: Validating ${SUBST0}... Template: base-installer/debootstrap/info/retrieving Type: text Description: Retrieving ${SUBST0}... Template: base-installer/debootstrap/info/extracting Type: text Description: Extracting ${SUBST0}... Template: base-installer/debootstrap/info/unpacking Type: text Description: Unpacking ${SUBST0}... Template: base-installer/debootstrap/info/configuring Type: text Description: Configuring ${SUBST0}... Template: base-installer/debootstrap/info/releasesig Type: text Description: Checking Release signature Template: base-installer/debootstrap/info/validrelsig Type: text Description: Valid Release signature (key id ${SUBST0}) Template: base-installer/debootstrap/info/resolvebase Type: text Description: Resolving dependencies of base packages... Template: base-installer/debootstrap/info/newbase Type: text Description: Found additional base dependencies: ${SUBST0} Template: base-installer/debootstrap/info/newrequired Type: text Description: Found additional required dependencies: ${SUBST0} Template: base-installer/debootstrap/info/redundantbase Type: text Description: Found packages in base already in required: ${SUBST0} Template: base-installer/debootstrap/info/resolvereq Type: text Description: Resolving dependencies of required packages... Template: base-installer/debootstrap/info/checkingsizes Type: text Description: Checking component ${SUBST0} on ${SUBST1}... Template: base-installer/debootstrap/info/instcore Type: text Description: Installing core packages... Template: base-installer/debootstrap/info/unpackreq Type: text Description: Unpacking required packages... Template: base-installer/debootstrap/info/confreq Type: text Description: Configuring required packages... Template: base-installer/debootstrap/info/instbase Type: text Description: Installing base packages... Template: base-installer/debootstrap/info/unpackbase Type: text Description: Unpacking the base system... Template: base-installer/debootstrap/info/confbase Type: text Description: Configuring the base system... Template: base-installer/debootstrap/info/basesuccess Type: text Description: Base system installed successfully. Template: base-installer/debootstrap/fallback-warning Type: error Description: Debootstrap warning Warning: ${INFO} Template: base-installer/debootstrap/warning/retrying Type: text Description: Retrying failed download of ${SUBST0} Template: base-installer/section/configure_apt Type: text Description: Configuring APT sources... Template: base-installer/section/pick_kernel Type: text Description: Selecting the kernel to install... Template: base-installer/section/install_linux Type: text Description: Installing the kernel... Template: base-installer/section/install_kernel_package Type: text Description: Installing the kernel - retrieving and installing ${SUBST0}... Template: base-installer/includes Type: string Description: for internal use; can be preseeded Packages to be included in base installation Template: base-installer/excludes Type: string Description: for internal use; can be preseeded Packages to be excluded in base installation Template: base-installer/debootstrap_script Type: string Description: for internal use; can be preseeded Force use of a specific debootstrap script Template: base-installer/kernel/linux/initrd-2.6 Type: boolean Default: true Description: for internal use only Use an (initramfs) initrd (linux 2.6 and later only) Template: base-installer/kernel/linux/initramfs-tools/driver-policy Type: string Default: most Description: for internal use Default driver inclusion policy for initramfs-tools Template: base-installer/kernel/linux/extra-packages Type: string Description: for internal use; can be preseeded Default: Extra packages to install with init*-tools (linux only) Template: base-installer/kernel/linux/extra-packages-2.6 Type: string Description: for internal use; can be preseeded Default: Extra packages to install with init*-tools (linux 2.6 and later only) Template: base-installer/kernel/linux/link_in_boot Type: boolean Default: false Description: for internal use only Kernel needs a link in /boot/ (linux only) ********** ca-certificates ********** Template: ca-certificates/title Type: title Description: ca-certificates configuration Template: ca-certificates/trust_new_crts Type: select Choices: yes, no, ask Default: yes Description: Trust new certificates from certificate authorities? This package may install new CA (Certificate Authority) certificates when upgrading. You may want to check such new CA certificates and select only certificates that you trust. . - yes: new CA certificates will be trusted and installed; - no : new CA certificates will not be installed by default; - ask: prompt for each new CA certificate. Template: ca-certificates/new_crts Type: multiselect Choices: ${new_crts} Description: New certificates to activate: During upgrades, new certificates will be added. Please choose those you trust. Template: ca-certificates/enable_crts Type: multiselect Choices: ${enable_crts} Description: Certificates to activate: This package installs common CA (Certificate Authority) certificates in /usr/share/ca-certificates. . Please select the certificate authorities you trust so that their certificates are installed into /etc/ssl/certs. They will be compiled into a single /etc/ssl/certs/ca-certificates.crt file. ********** cdebconf-gtk-entropy ********** Template: debconf/entropy/gtk/action Type: text Description: Enter random characters or make random movements with the mouse Template: debconf/entropy/gtk/help Type: text Description: You can help speed up the process by entering random characters on the keyboard or by making random movements with the mouse. Template: debconf/entropy/success Type: text Description: Key data has been created successfully. ********** cdebconf-gtk-entropy ********** Template: debconf/entropy/gtk/action Type: text Description: Enter random characters or make random movements with the mouse Template: debconf/entropy/gtk/help Type: text Description: You can help speed up the process by entering random characters on the keyboard or by making random movements with the mouse. Template: debconf/entropy/success Type: text Description: Key data has been created successfully. ********** cdebconf-newt-entropy ********** Template: debconf/entropy/text/action Type: text Description: Enter random characters Template: debconf/entropy/text/help Type: text Description: You can help speed up the process by entering random characters on the keyboard, or just wait until enough key data has been collected (which can take a long time). Template: debconf/entropy/success Type: text Description: Key data has been created successfully. ********** cdebconf-newt-entropy ********** Template: debconf/entropy/text/action Type: text Description: Enter random characters Template: debconf/entropy/text/help Type: text Description: You can help speed up the process by entering random characters on the keyboard, or just wait until enough key data has been collected (which can take a long time). Template: debconf/entropy/success Type: text Description: Key data has been created successfully. ********** cdebconf-text-entropy ********** Template: debconf/entropy/text/action Type: text Description: Enter random characters Template: debconf/entropy/text/help Type: text Description: You can help speed up the process by entering random characters on the keyboard, or just wait until enough key data has been collected (which can take a long time). Template: debconf/entropy/success Type: text Description: Key data has been created successfully. ********** cdebconf-text-entropy ********** Template: debconf/entropy/text/action Type: text Description: Enter random characters Template: debconf/entropy/text/help Type: text Description: You can help speed up the process by entering random characters on the keyboard, or just wait until enough key data has been collected (which can take a long time). Template: debconf/entropy/success Type: text Description: Key data has been created successfully. ********** choose-mirror-bin ********** Template: mirror/country Type: string Description: country code or "manual" (for internal use) Template: mirror/suite Type: select Choices-C: ${CHOICES-C} Choices: ${CHOICES} Description: Debian version to install: Debian comes in several flavors. Stable is well-tested and rarely changes. Unstable is untested and frequently changing. Testing is a middle ground, that receives many of the new versions from unstable if they are not too buggy. . Only flavors available on the selected mirror are listed. Template: mirror/codename Type: string Description: for internal use only Template: mirror/checking_title Type: text Description: Checking the Debian archive mirror Template: mirror/checking_download Type: text Description: Downloading Release files... Template: mirror/no-default Type: boolean Default: true Description: Go back and try a different mirror? The specified (default) Debian version (${RELEASE}) is not available from the selected mirror. It is possible to continue and select a different release for your installation, but normally you should go back and select a different mirror that does support the correct version. Template: mirror/bad Type: error Description: Bad archive mirror An error has been detected while trying to use the specified Debian archive mirror. . Possible reasons for the error are: incorrect mirror specified; mirror is not available (possibly due to an unreliable network connection); mirror is broken (for example because an invalid Release file was found); mirror does not support the correct Debian version. . Additional details may be available in /var/log/syslog or on virtual console 4. . Please check the specified mirror or try a different one. Template: mirror/noarch Type: error Description: Architecture not supported The specified Debian archive mirror does not seem to support your architecture. Please try a different mirror. Template: mirror/suites/oldstable Type: text Description: oldstable Template: mirror/suites/stable Type: text Description: stable Template: mirror/suites/testing Type: text Description: testing Template: mirror/suites/unstable Type: text Description: unstable Template: debian-installer/choose-mirror/title Type: text Description: Choose a mirror of the Debian archive Template: mirror/http/countries Type: select Choices-C: manual, AR, AM, AU, AT, BD, BY, BE, BR, BG, CA, CL, CN, CO, CR, HR, CZ, DK, SV, EE, FI, FR, PF, GE, DE, GR, HU, IS, IN, ID, IR, IE, IL, IT, JP, KZ, KE, KR, LV, LT, LU, MK, MY, MX, MD, NL, NC, NZ, NO, PH, PL, PT, RO, RU, RE, RS, SG, SK, SI, ZA, ES, SE, CH, TW, TH, TR, UA, GB, US, UY, UZ, VU, VN Choices: enter information manually, Argentina, Armenia, Australia, Austria, Bangladesh, Belarus, Belgium, Brazil, Bulgaria, Canada, Chile, China, Colombia, Costa Rica, Croatia, Czechia, Denmark, El Salvador, Estonia, Finland, France, French Polynesia, Georgia, Germany, Greece, Hungary, Iceland, India, Indonesia, Iran\, Islamic Republic of, Ireland, Israel, Italy, Japan, Kazakhstan, Kenya, Korea\, Republic of, Latvia, Lithuania, Luxembourg, Macedonia\, Republic of, Malaysia, Mexico, Moldova, Netherlands, New Caledonia, New Zealand, Norway, Philippines, Poland, Portugal, Romania, Russian Federation, Réunion, Serbia, Singapore, Slovakia, Slovenia, South Africa, Spain, Sweden, Switzerland, Taiwan, Thailand, Turkey, Ukraine, United Kingdom, United States, Uruguay, Uzbekistan, Vanuatu, Vietnam Default: US Template: mirror/http/mirror Type: select Choices: ${mirrors} Description: Debian archive mirror: Please select a Debian archive mirror. You should use a mirror in your country or region if you do not know which mirror has the best Internet connection to you. . Usually, ftp..debian.org is a good choice. Template: mirror/http/hostname Type: string Default: mirror Description: Debian archive mirror hostname: Please enter the hostname of the mirror from which Debian will be downloaded. . An alternate port can be specified using the standard [hostname]:[port] format. Template: mirror/http/directory Type: string Default: /debian/ Description: Debian archive mirror directory: Please enter the directory in which the mirror of the Debian archive is located. Template: mirror/http/proxy Type: string Description: HTTP proxy information (blank for none): If you need to use a HTTP proxy to access the outside world, enter the proxy information here. Otherwise, leave this blank. . The proxy information should be given in the standard form of "http://[[user][:pass]@]host[:port]/". Template: mirror/https/countries Type: select Choices-C: manual Choices: enter information manually Default: US Description: Debian archive mirror country: The goal is to find a mirror of the Debian archive that is close to you on the network -- be aware that nearby countries, or even your own, may not be the best choice. Template: mirror/ftp/hostname Type: string Default: mirror Description: Debian archive mirror hostname: Please enter the hostname of the mirror from which Debian will be downloaded. . An alternate port can be specified using the standard [hostname]:[port] format. Template: mirror/ftp/directory Type: string Default: /debian/ Description: Debian archive mirror directory: Please enter the directory in which the mirror of the Debian archive is located. Template: mirror/ftp/proxy Type: string Description: FTP proxy information (blank for none): If you need to use a FTP proxy to access the outside world, enter the proxy information here. Otherwise, leave this blank. . The proxy information should be given in the standard form of "http://[[user][:pass]@]host[:port]/". Template: mirror/protocol Type: select Choices: ${protocols} Default: http Description: Protocol for file downloads: Please select the protocol to be used for downloading files. If unsure, select "http"; it is less prone to problems involving firewalls. ********** choose-mirror-bin ********** Template: mirror/country Type: string Description: country code or "manual" (for internal use) Template: mirror/suite Type: select Choices-C: ${CHOICES-C} Choices: ${CHOICES} Description: Debian version to install: Debian comes in several flavors. Stable is well-tested and rarely changes. Unstable is untested and frequently changing. Testing is a middle ground, that receives many of the new versions from unstable if they are not too buggy. . Only flavors available on the selected mirror are listed. Template: mirror/codename Type: string Description: for internal use only Template: mirror/checking_title Type: text Description: Checking the Debian archive mirror Template: mirror/checking_download Type: text Description: Downloading Release files... Template: mirror/no-default Type: boolean Default: true Description: Go back and try a different mirror? The specified (default) Debian version (${RELEASE}) is not available from the selected mirror. It is possible to continue and select a different release for your installation, but normally you should go back and select a different mirror that does support the correct version. Template: mirror/bad Type: error Description: Bad archive mirror An error has been detected while trying to use the specified Debian archive mirror. . Possible reasons for the error are: incorrect mirror specified; mirror is not available (possibly due to an unreliable network connection); mirror is broken (for example because an invalid Release file was found); mirror does not support the correct Debian version. . Additional details may be available in /var/log/syslog or on virtual console 4. . Please check the specified mirror or try a different one. Template: mirror/noarch Type: error Description: Architecture not supported The specified Debian archive mirror does not seem to support your architecture. Please try a different mirror. Template: mirror/suites/oldstable Type: text Description: oldstable Template: mirror/suites/stable Type: text Description: stable Template: mirror/suites/testing Type: text Description: testing Template: mirror/suites/unstable Type: text Description: unstable Template: debian-installer/choose-mirror/title Type: text Description: Choose a mirror of the Debian archive Template: mirror/http/countries Type: select Choices-C: manual, AR, AM, AU, AT, BD, BY, BE, BR, BG, CA, CL, CN, CO, CR, HR, CZ, DK, SV, EE, FI, FR, PF, GE, DE, GR, HU, IS, IN, ID, IR, IE, IL, IT, JP, KZ, KE, KR, LV, LT, LU, MK, MY, MX, MD, NL, NC, NZ, NO, PH, PL, PT, RO, RU, RE, RS, SG, SK, SI, ZA, ES, SE, CH, TW, TH, TR, UA, GB, US, UY, UZ, VU, VN Choices: enter information manually, Argentina, Armenia, Australia, Austria, Bangladesh, Belarus, Belgium, Brazil, Bulgaria, Canada, Chile, China, Colombia, Costa Rica, Croatia, Czechia, Denmark, El Salvador, Estonia, Finland, France, French Polynesia, Georgia, Germany, Greece, Hungary, Iceland, India, Indonesia, Iran\, Islamic Republic of, Ireland, Israel, Italy, Japan, Kazakhstan, Kenya, Korea\, Republic of, Latvia, Lithuania, Luxembourg, Macedonia\, Republic of, Malaysia, Mexico, Moldova, Netherlands, New Caledonia, New Zealand, Norway, Philippines, Poland, Portugal, Romania, Russian Federation, Réunion, Serbia, Singapore, Slovakia, Slovenia, South Africa, Spain, Sweden, Switzerland, Taiwan, Thailand, Turkey, Ukraine, United Kingdom, United States, Uruguay, Uzbekistan, Vanuatu, Vietnam Default: US Template: mirror/http/mirror Type: select Choices: ${mirrors} Description: Debian archive mirror: Please select a Debian archive mirror. You should use a mirror in your country or region if you do not know which mirror has the best Internet connection to you. . Usually, ftp..debian.org is a good choice. Template: mirror/http/hostname Type: string Default: mirror Description: Debian archive mirror hostname: Please enter the hostname of the mirror from which Debian will be downloaded. . An alternate port can be specified using the standard [hostname]:[port] format. Template: mirror/http/directory Type: string Default: /debian/ Description: Debian archive mirror directory: Please enter the directory in which the mirror of the Debian archive is located. Template: mirror/http/proxy Type: string Description: HTTP proxy information (blank for none): If you need to use a HTTP proxy to access the outside world, enter the proxy information here. Otherwise, leave this blank. . The proxy information should be given in the standard form of "http://[[user][:pass]@]host[:port]/". Template: mirror/https/countries Type: select Choices-C: manual Choices: enter information manually Default: US Description: Debian archive mirror country: The goal is to find a mirror of the Debian archive that is close to you on the network -- be aware that nearby countries, or even your own, may not be the best choice. Template: mirror/ftp/hostname Type: string Default: mirror Description: Debian archive mirror hostname: Please enter the hostname of the mirror from which Debian will be downloaded. . An alternate port can be specified using the standard [hostname]:[port] format. Template: mirror/ftp/directory Type: string Default: /debian/ Description: Debian archive mirror directory: Please enter the directory in which the mirror of the Debian archive is located. Template: mirror/ftp/proxy Type: string Description: FTP proxy information (blank for none): If you need to use a FTP proxy to access the outside world, enter the proxy information here. Otherwise, leave this blank. . The proxy information should be given in the standard form of "http://[[user][:pass]@]host[:port]/". Template: mirror/protocol Type: select Choices: ${protocols} Default: http Description: Protocol for file downloads: Please select the protocol to be used for downloading files. If unsure, select "http"; it is less prone to problems involving firewalls. ********** clock-setup ********** Template: debian-installer/clock-setup/title Type: text Description: Configure the clock Template: clock-setup/utc Type: boolean Default: true Description: Is the system clock set to UTC? System clocks are generally set to Coordinated Universal Time (UTC). The operating system uses your time zone to convert system time into local time. This is recommended unless you also use another operating system that expects the clock to be set to local time. Template: finish-install/progress/clock-setup Type: text Description: Configuring clock settings... Template: clock-setup/progress/title Type: text Description: Setting up the clock Template: clock-setup/ntp Type: boolean Default: true Description: Set the clock using NTP? The Network Time Protocol (NTP) can be used to set the system's clock. The installation process works best with a correctly set clock. Template: clock-setup/ntp-server Type: string Default: 0.debian.pool.ntp.org Description: NTP server to use: The default NTP server is almost always a good choice, but if you prefer to use another NTP server, you can enter it here. Template: clock-setup/progress/ntp Type: text Description: Getting the time from a network time server... Template: clock-setup/progress/hwclock Type: text Description: Setting the hardware clock... Template: clock-setup/hwclock-wait Type: boolean Default: false Description: Wait another 30 seconds for hwclock to set the clock? Setting the hardware clock is taking longer than expected. The 'hwclock' program used to set the clock may have problems talking to the hardware clock. . Check /var/log/syslog or see virtual console 4 for the details. . If you choose to not wait for hwclock to finish setting the clock, this system's clock may not be set correctly. Template: clock-setup/system-time-changed Type: boolean Default: false Description: for internal use only Set to true when rdate actually updates the system clock. ********** clock-setup ********** Template: debian-installer/clock-setup/title Type: text Description: Configure the clock Template: clock-setup/utc Type: boolean Default: true Description: Is the system clock set to UTC? System clocks are generally set to Coordinated Universal Time (UTC). The operating system uses your time zone to convert system time into local time. This is recommended unless you also use another operating system that expects the clock to be set to local time. Template: finish-install/progress/clock-setup Type: text Description: Configuring clock settings... Template: clock-setup/progress/title Type: text Description: Setting up the clock Template: clock-setup/ntp Type: boolean Default: true Description: Set the clock using NTP? The Network Time Protocol (NTP) can be used to set the system's clock. The installation process works best with a correctly set clock. Template: clock-setup/ntp-server Type: string Default: 0.debian.pool.ntp.org Description: NTP server to use: The default NTP server is almost always a good choice, but if you prefer to use another NTP server, you can enter it here. Template: clock-setup/progress/ntp Type: text Description: Getting the time from a network time server... Template: clock-setup/progress/hwclock Type: text Description: Setting the hardware clock... Template: clock-setup/hwclock-wait Type: boolean Default: false Description: Wait another 30 seconds for hwclock to set the clock? Setting the hardware clock is taking longer than expected. The 'hwclock' program used to set the clock may have problems talking to the hardware clock. . Check /var/log/syslog or see virtual console 4 for the details. . If you choose to not wait for hwclock to finish setting the clock, this system's clock may not be set correctly. Template: clock-setup/system-time-changed Type: boolean Default: false Description: for internal use only Set to true when rdate actually updates the system clock. ********** console-keymaps-mac ********** Template: console-keymaps-mac/keymap Type: select Choices-C: mac-us-std, mac-us-ext, mac-fr3, mac-fr2-ext, mac-de2-ext Choices: American English (82 keys), American English (extended kbd), French (alternate), French (extended kbd), German (extended kbd) Description: Keymap to use: ********** console-keymaps-mac ********** Template: console-keymaps-mac/keymap Type: select Choices-C: mac-us-std, mac-us-ext, mac-fr3, mac-fr2-ext, mac-de2-ext Choices: American English (82 keys), American English (extended kbd), French (alternate), French (extended kbd), German (extended kbd) Description: Keymap to use: ********** console-setup ********** Template: console-setup/use_system_font Type: text Description: Do not change the boot/kernel font Template: console-setup/guess_font Type: text Description: Let the system select a suitable font Template: console-setup/framebuffer_only Type: text Description: framebuffer only Template: console-setup/codeset47 Type: select Choices: . Arabic, # Armenian, # Cyrillic - KOI8-R and KOI8-U, # Cyrillic - non-Slavic languages, # Cyrillic - Slavic languages (also Bosnian and Serbian Latin), . Ethiopic, # Georgian, # Greek, # Hebrew, # Lao, # Latin1 and Latin5 - western Europe and Turkic languages, # Latin2 - central Europe and Romanian, # Latin3 and Latin8 - Chichewa; Esperanto; Irish; Maltese and Welsh, # Latin7 - Lithuanian; Latvian; Maori and Marshallese, . Latin - Vietnamese, # Thai, . Combined - Latin; Slavic Cyrillic; Hebrew; basic Arabic, . Combined - Latin; Slavic Cyrillic; Greek, . Combined - Latin; Slavic and non-Slavic Cyrillic, Guess optimal character set Description: Character set to support: Please choose the character set that should be supported by the console font. . If you don't use a framebuffer, the choices that start with "." will reduce the number of available colors on the console. Template: console-setup/fontface47 Type: select Choices: ${CHOICES} Description: Font for the console: "VGA" has a traditional appearance and has medium coverage of international scripts. "Fixed" has a simplistic appearance and has better coverage of international scripts. "Terminus" may help to reduce eye fatigue, though some symbols have a similar aspect which may be a problem for programmers. . If you prefer a bold version of the Terminus font, choose either TerminusBold (if you use a framebuffer) or TerminusBoldVGA (otherwise). Template: console-setup/fontsize-text47 Type: select Choices: ${CHOICES} Description: Font size: Please select the size of the font for the console. For reference, the font used when the computer boots has size 8x16. Template: console-setup/fontsize-fb47 Type: select Choices: ${CHOICES} Description: Font size: Please select the size of the font for the console. For reference, the font used when the computer boots has size 8x16. Some font sizes require the kbd console package (not console-tools) plus framebuffer. Template: console-setup/charmap47 Type: select Choices: ${CHOICES} Description: Encoding to use on the console: Template: console-setup/fontsize Type: string Description: for internal use Template: console-setup/codesetcode Type: string Description: for internal use Template: console-setup/store_defaults_in_debconf_db Type: boolean Default: true Description: for internal use ********** cryptsetup ********** Template: cryptsetup/prerm_active_mappings Type: boolean Default: true Description: Continue with cryptsetup removal? This system has unlocked dm-crypt devices: ${cryptmap} . If these devices are managed with cryptsetup, you might be unable to lock the devices after the package removal, though other tools can be used for managing dm-crypt devices. Any system shutdown or reboot will lock the devices. . Do not choose this option if you want to lock the dm-crypt devices before package removal. ********** dash ********** Template: dash/sh Type: boolean Default: true Description: Use dash as the default system shell (/bin/sh)? The system shell is the default command interpreter for shell scripts. . Using dash as the system shell will improve the system's overall performance. It does not alter the shell presented to interactive users. ********** debconf ********** Template: debconf/frontend Type: select Choices: Dialog, Readline, Gnome, Kde, Editor, Noninteractive Default: Dialog Description: Interface to use: Packages that use debconf for configuration share a common look and feel. You can select the type of user interface they use. . The dialog frontend is a full-screen, character based interface, while the readline frontend uses a more traditional plain text interface, and both the gnome and kde frontends are modern X interfaces, fitting the respective desktops (but may be used in any X environment). The editor frontend lets you configure things using your favorite text editor. The noninteractive frontend never asks you any questions. Template: debconf/priority Type: select Choices: critical, high, medium, low Default: high Description: Ignore questions with a priority less than: Debconf prioritizes the questions it asks you. Pick the lowest priority of question you want to see: - 'critical' only prompts you if the system might break. Pick it if you are a newbie, or in a hurry. - 'high' is for rather important questions - 'medium' is for normal questions - 'low' is for control freaks who want to see everything . Note that no matter what level you pick here, you will be able to see every question if you reconfigure a package with dpkg-reconfigure. Template: debconf-apt-progress/title Type: text Description: Installing packages Template: debconf-apt-progress/preparing Type: text Description: Please wait... Template: debconf-apt-progress/info Type: text Description: ${DESCRIPTION} Template: debconf-apt-progress/media-change Type: text Description: Media change ${MESSAGE} ********** discover ********** Template: discover/install_hw_packages Type: multiselect Choices: ${PACKAGES} Description: Packages to install: Some packages were found to be useful with your hardware. Please select those you want to install. ********** disk-detect ********** Template: debian-installer/disk-detect/title Type: text Description: Detect disks Template: disk-detect/detect_progress_title Type: text Description: Detecting disks and all other hardware Template: disk-detect/module_select Type: select Choices: continue with no disk drive, ${CHOICES}, none of the above Default: continue with no disk drive Description: Driver needed for your disk drive: No disk drive was detected. If you know the name of the driver needed by your disk drive, you can select it from the list. Template: disk-detect/cannot_find Type: error Description: No partitionable media No partitionable media were found. . Please check that a hard disk is attached to this machine. Template: disk-detect/dmraid/enable Type: boolean Default: false Description: for internal use; can be preseeded Check for the presence of Serial ATA RAID (dmraid) disks? Template: disk-detect/multipath/enable Type: boolean Default: false Description: for internal use; can be preseeded Check for the presence of multipath devices? ********** disk-detect ********** Template: debian-installer/disk-detect/title Type: text Description: Detect disks Template: disk-detect/detect_progress_title Type: text Description: Detecting disks and all other hardware Template: disk-detect/module_select Type: select Choices: continue with no disk drive, ${CHOICES}, none of the above Default: continue with no disk drive Description: Driver needed for your disk drive: No disk drive was detected. If you know the name of the driver needed by your disk drive, you can select it from the list. Template: disk-detect/cannot_find Type: error Description: No partitionable media No partitionable media were found. . Please check that a hard disk is attached to this machine. Template: disk-detect/dmraid/enable Type: boolean Default: false Description: for internal use; can be preseeded Check for the presence of Serial ATA RAID (dmraid) disks? Template: disk-detect/multipath/enable Type: boolean Default: false Description: for internal use; can be preseeded Check for the presence of multipath devices? ********** driver-injection-disk-detect ********** Template: debian-installer/driver-injection-disk-detect/title Type: text Description: Detect virtual driver disks from hardware manufacturer Template: driver-injection-disk/load Default: true Type: boolean Description: Load drivers from internal virtual driver disk? Installing on this hardware may require some drivers provided by the manufacturer to be loaded from the built-in driver injection disk. ********** driver-injection-disk-detect ********** Template: debian-installer/driver-injection-disk-detect/title Type: text Description: Detect virtual driver disks from hardware manufacturer Template: driver-injection-disk/load Default: true Type: boolean Description: Load drivers from internal virtual driver disk? Installing on this hardware may require some drivers provided by the manufacturer to be loaded from the built-in driver injection disk. ********** eject-udeb ********** Template: debian-installer/eject-udeb/title Type: text Description: Eject a CD from the drive ********** eject-udeb ********** Template: debian-installer/eject-udeb/title Type: text Description: Eject a CD from the drive ********** espeakup-udeb ********** Template: debian-installer/espeakup-udeb/title Type: text Description: Configure the speech synthesizer voice Template: espeakup/voice Type: string Description: for internal use Template: espeakup/card Type: string Description: for internal use ********** espeakup-udeb ********** Template: debian-installer/espeakup-udeb/title Type: text Description: Configure the speech synthesizer voice Template: espeakup/voice Type: string Description: for internal use Template: espeakup/card Type: string Description: for internal use ********** ethdetect ********** Template: ethdetect/module_select Type: select Choices: no ethernet card, ${CHOICES}, none of the above Default: no ethernet card Description: Driver needed by your Ethernet card: No Ethernet card was detected. If you know the name of the driver needed by your Ethernet card, you can select it from the list. Template: ethdetect/use_firewire_ethernet Type: boolean Default: false Description: Do you intend to use FireWire Ethernet? No Ethernet card was detected, but a FireWire interface is present. It's possible, though unlikely, that with the right FireWire hardware connected to it, this could be your primary Ethernet interface. Template: ethdetect/cannot_find Type: error Description: Ethernet card not found No Ethernet card was found on the system. Template: ethdetect/detect_progress_title Type: text Description: Detecting network hardware Template: ethdetect/prompt_missing_firmware Type: boolean Default: true Description: for internal use; can be preseeded Prompt for missing firmware to be provided before the network is up? Template: debian-installer/ethdetect/title Type: text Description: Detect network hardware ********** ethdetect ********** Template: ethdetect/module_select Type: select Choices: no ethernet card, ${CHOICES}, none of the above Default: no ethernet card Description: Driver needed by your Ethernet card: No Ethernet card was detected. If you know the name of the driver needed by your Ethernet card, you can select it from the list. Template: ethdetect/use_firewire_ethernet Type: boolean Default: false Description: Do you intend to use FireWire Ethernet? No Ethernet card was detected, but a FireWire interface is present. It's possible, though unlikely, that with the right FireWire hardware connected to it, this could be your primary Ethernet interface. Template: ethdetect/cannot_find Type: error Description: Ethernet card not found No Ethernet card was found on the system. Template: ethdetect/detect_progress_title Type: text Description: Detecting network hardware Template: ethdetect/prompt_missing_firmware Type: boolean Default: true Description: for internal use; can be preseeded Prompt for missing firmware to be provided before the network is up? Template: debian-installer/ethdetect/title Type: text Description: Detect network hardware ********** exim4-base ********** Template: exim4/purge_spool Type: boolean Default: false Description: Remove undelivered messages in spool directory? There are e-mail messages in the Exim spool directory /var/spool/exim4/input/ which have not yet been delivered. Removing Exim will cause them to remain undelivered until Exim is re-installed. . If this option is not chosen, the spool directory is kept, allowing the messages in the queue to be delivered at a later date after Exim is re-installed. Template: exim4-base/drec Type: error Description: Reconfigure exim4-config instead of this package Exim4 has its configuration factored out into a dedicated package, exim4-config. To reconfigure Exim4, use 'dpkg-reconfigure exim4-config'. ********** exim4-config ********** Template: exim4/dc_eximconfig_configtype Type: select Choices: internet site; mail is sent and received directly using SMTP, mail sent by smarthost; received via SMTP or fetchmail, mail sent by smarthost; no local mail, local delivery only; not on a network, no configuration at this time Default: local delivery only; not on a network Description: General type of mail configuration: Please select the mail server configuration type that best meets your needs. . Systems with dynamic IP addresses, including dialup systems, should generally be configured to send outgoing mail to another machine, called a 'smarthost' for delivery because many receiving systems on the Internet block incoming mail from dynamic IP addresses as spam protection. . A system with a dynamic IP address can receive its own mail, or local delivery can be disabled entirely (except mail for root and postmaster). Template: exim4/no_config Type: boolean Default: true Description: Really leave the mail system unconfigured? Until the mail system is configured, it will be broken and cannot be used. Configuration at a later time can be done either by hand or by running 'dpkg-reconfigure exim4-config' as root. Template: exim4/mailname Type: string Description: System mail name: The 'mail name' is the domain name used to 'qualify' mail addresses without a domain name. . This name will also be used by other programs. It should be the single, fully qualified domain name (FQDN). . Thus, if a mail address on the local host is foo@example.org, the correct value for this option would be example.org. . This name won't appear on From: lines of outgoing messages if rewriting is enabled. Template: exim4/dc_other_hostnames Type: string Default: Description: Other destinations for which mail is accepted: Please enter a semicolon-separated list of recipient domains for which this machine should consider itself the final destination. These domains are commonly called 'local domains'. The local hostname (${fqdn}) and 'localhost' are always added to the list given here. . By default all local domains will be treated identically. If both a.example and b.example are local domains, acc@a.example and acc@b.example will be delivered to the same final destination. If different domain names should be treated differently, it is necessary to edit the config files afterwards. Template: exim4/dc_relay_domains Type: string Default: Description: Domains to relay mail for: Please enter a semicolon-separated list of recipient domains for which this system will relay mail, for example as a fallback MX or mail gateway. This means that this system will accept mail for these domains from anywhere on the Internet and deliver them according to local delivery rules. . Do not mention local domains here. Wildcards may be used. Template: exim4/dc_relay_nets Type: string Default: Description: Machines to relay mail for: Please enter a semicolon-separated list of IP address ranges for which this system will unconditionally relay mail, functioning as a smarthost. . You should use the standard address/prefix format (e.g. 194.222.242.0/24 or 5f03:1200:836f::/48). . If this system should not be a smarthost for any other host, leave this list blank. Template: exim4/dc_readhost Type: string Description: Visible domain name for local users: The option to hide the local mail name in outgoing mail was enabled. It is therefore necessary to specify the domain name this system should use for the domain part of local users' sender addresses. Template: exim4/dc_smarthost Type: string Description: IP address or host name of the outgoing smarthost: Please enter the IP address or the host name of a mail server that this system should use as outgoing smarthost. If the smarthost only accepts your mail on a port different from TCP/25, append two colons and the port number (for example smarthost.example::587 or 192.168.254.254::2525). Colons in IPv6 addresses need to be doubled. . If the smarthost requires authentication, please refer to the Debian-specific README files in /usr/share/doc/exim4-base for notes about setting up SMTP authentication. Template: exim4/dc_postmaster Type: string Description: Root and postmaster mail recipient: Mail for the 'postmaster', 'root', and other system accounts needs to be redirected to the user account of the actual system administrator. . If this value is left empty, such mail will be saved in /var/mail/mail, which is not recommended. . Note that postmaster's mail should be read on the system to which it is directed, rather than being forwarded elsewhere, so (at least one of) the users listed here should not redirect their mail off this machine. A 'real-' prefix can be used to force local delivery. . Multiple user names need to be separated by spaces. Template: exim4/dc_local_interfaces Type: string Default: notset Description: IP-addresses to listen on for incoming SMTP connections: Please enter a semicolon-separated list of IP addresses. The Exim SMTP listener daemon will listen on all IP addresses listed here. . An empty value will cause Exim to listen for connections on all available network interfaces. . If this system only receives mail directly from local services (and not from other hosts), it is suggested to prohibit external connections to the local Exim daemon. Such services include e-mail programs (MUAs) which talk to localhost only as well as fetchmail. External connections are impossible when 127.0.0.1 is entered here, as this will disable listening on public network interfaces. Template: exim4/dc_minimaldns Type: boolean Default: false Description: Keep number of DNS-queries minimal (Dial-on-Demand)? In normal mode of operation Exim does DNS lookups at startup, and when receiving or delivering messages. This is for logging purposes and allows keeping down the number of hard-coded values in the configuration. . If this system does not have a DNS full service resolver available at all times (for example if its Internet access is a dial-up line using dial-on-demand), this might have unwanted consequences. For example, starting up Exim or running the queue (even with no messages waiting) might trigger a costly dial-up-event. . This option should be selected if this system is using Dial-on-Demand. If it has always-on Internet access, this option should be disabled. Template: exim4/exim4-config-title Type: title Description: Mail Server configuration Template: exim4/use_split_config Type: boolean Description: Split configuration into small files? The Debian exim4 packages can either use 'unsplit configuration', a single monolithic file (/etc/exim4/exim4.conf.template) or 'split configuration', where the actual Exim configuration files are built from about 50 smaller files in /etc/exim4/conf.d/. . Unsplit configuration is better suited for large modifications and is generally more stable, whereas split configuration offers a comfortable way to make smaller modifications but is more fragile and might break if modified carelessly. . A more detailed discussion of split and unsplit configuration can be found in the Debian-specific README files in /usr/share/doc/exim4-base. Template: exim4/hide_mailname Type: boolean Description: Hide local mail name in outgoing mail? The headers of outgoing mail can be rewritten to make it appear to have been generated on a different system. If this option is chosen, '${mailname}', 'localhost' and '${dc_other_hostnames}' in From, Reply-To, Sender and Return-Path are rewritten. Template: exim4/dc_localdelivery Type: select Choices: mbox format in /var/mail/, Maildir format in home directory Default: mbox format in /var/mail/ Description: Delivery method for local mail: Exim is able to store locally delivered email in different formats. The most commonly used ones are mbox and Maildir. mbox uses a single file for the complete mail folder stored in /var/mail/. With Maildir format every single message is stored in a separate file in ~/Maildir/. . Please note that most mail tools in Debian expect the local delivery method to be mbox in their default. ********** exim4-daemon-light ********** Template: exim4-daemon-light/drec Type: error Description: Reconfigure exim4-config instead of this package Exim4 has its configuration factored out into a dedicated package, exim4-config. To reconfigure Exim4, use 'dpkg-reconfigure exim4-config'. ********** exim4 ********** Template: exim4/drec Type: error Description: Reconfigure exim4-config instead of this package Exim4 has its configuration factored out into a dedicated package, exim4-config. To reconfigure Exim4, use 'dpkg-reconfigure exim4-config'. ********** finish-install ********** Template: debian-installer/finish-install/title Type: text Description: Finish the installation Template: finish-install/progress/title Type: text Description: Finishing the installation Template: finish-install/progress/fallback Type: text Description: Running ${SCRIPT}... Template: finish-install/progress/config-target-network Type: text Description: Configuring network... Template: finish-install/progress/framebuffer-module-linux-i386 Type: text Description: Setting up frame buffer... Template: finish-install/progress/umount Type: text Description: Unmounting file systems... Template: finish-install/progress/reboot Type: text Description: Rebooting into your new system... Template: finish-install/reboot_in_progress Type: note Description: Installation complete Installation is complete, so it is time to boot into your new system. Make sure to remove the installation media, so that you boot into the new system rather than restarting the installation. Template: finish-install/keep-consoles Type: boolean Default: false Description: for internal use; can be preseeded Don't comment out regular Virtual Consoles during serial console installs ********** finish-install ********** Template: debian-installer/finish-install/title Type: text Description: Finish the installation Template: finish-install/progress/title Type: text Description: Finishing the installation Template: finish-install/progress/fallback Type: text Description: Running ${SCRIPT}... Template: finish-install/progress/config-target-network Type: text Description: Configuring network... Template: finish-install/progress/framebuffer-module-linux-i386 Type: text Description: Setting up frame buffer... Template: finish-install/progress/umount Type: text Description: Unmounting file systems... Template: finish-install/progress/reboot Type: text Description: Rebooting into your new system... Template: finish-install/reboot_in_progress Type: note Description: Installation complete Installation is complete, so it is time to boot into your new system. Make sure to remove the installation media, so that you boot into the new system rather than restarting the installation. Template: finish-install/keep-consoles Type: boolean Default: false Description: for internal use; can be preseeded Don't comment out regular Virtual Consoles during serial console installs ********** grub-efi-amd64 ********** Template: grub2/linux_cmdline Type: string Description: Linux command line: The following Linux command line was extracted from /etc/default/grub or the `kopt' parameter in GRUB Legacy's menu.lst. Please verify that it is correct, and modify it if necessary. The command line is allowed to be empty. Template: grub2/linux_cmdline_default Type: string Default: quiet Description: Linux default command line: The following string will be used as Linux parameters for the default menu entry but not for the recovery mode. Template: grub2/force_efi_extra_removable Type: boolean Default: false Description: Force extra installation to the EFI removable media path? Some EFI-based systems are buggy and do not handle new bootloaders correctly. If you force an extra installation of GRUB to the EFI removable media path, this should ensure that this system will boot Debian correctly despite such a problem. However, it may remove the ability to boot any other operating systems that also depend on this path. If so, you will need to make sure that GRUB is configured successfully to be able to boot any other OS installations correctly. Template: grub2/update_nvram Type: boolean Default: true Description: Update NVRAM variables to automatically boot into Debian? GRUB can configure your platform's NVRAM variables so that it boots into Debian automatically when powered on. However, you may prefer to disable this behavior and avoid changes to your boot configuration. For example, if your NVRAM variables have been set up such that your system contacts a PXE server on every boot, this would preserve that behavior. Template: grub2/kfreebsd_cmdline Type: string Description: kFreeBSD command line: The following kFreeBSD command line was extracted from /etc/default/grub or the `kopt' parameter in GRUB Legacy's menu.lst. Please verify that it is correct, and modify it if necessary. The command line is allowed to be empty. Template: grub2/kfreebsd_cmdline_default Type: string Default: quiet Description: kFreeBSD default command line: The following string will be used as kFreeBSD parameters for the default menu entry but not for the recovery mode. Template: grub2/device_map_regenerated Type: note Description: /boot/grub/device.map has been regenerated The file /boot/grub/device.map has been rewritten to use stable device names. In most cases, this should significantly reduce the need to change it in future, and boot menu entries generated by GRUB should not be affected. . However, since more than one disk is present in the system, it is possible that the system is depending on the old device map. Please check whether there are any custom boot menu entries that rely on GRUB's (hdN) drive numbering, and update them if necessary. . If you do not understand this message, or if there are no custom boot menu entries, you can ignore this message. ********** grub-installer ********** Template: grub-installer/with_other_os Type: boolean Default: true Description: Install the GRUB boot loader to the master boot record? The following other operating systems have been detected on this computer: ${OS_LIST} . If all of your operating systems are listed above, then it should be safe to install the boot loader to the master boot record of your first hard drive. When your computer boots, you will be able to choose to load one of these operating systems or your new system. Template: grub-installer/only_debian Type: boolean Default: true Description: Install the GRUB boot loader to the master boot record? It seems that this new installation is the only operating system on this computer. If so, it should be safe to install the GRUB boot loader to the master boot record of your first hard drive. . Warning: If the installer failed to detect another operating system that is present on your computer, modifying the master boot record will make that operating system temporarily unbootable, though GRUB can be manually configured later to boot it. Template: grub-installer/sataraid Type: boolean Default: true Description: Install the GRUB boot loader to the Serial ATA RAID disk? Installation of GRUB on Serial ATA RAID is experimental. . GRUB is always installed to the master boot record (MBR) of the Serial ATA RAID disk. It is also assumed that disk is listed as the first hard disk in the boot order defined in the system's BIOS setup. . The GRUB root device is: ${GRUBROOT}. Template: grub-installer/sataraid-error Type: error Description: Unable to configure GRUB An error occurred while setting up GRUB for your Serial ATA RAID disk. . The GRUB installation has been aborted. Template: grub-installer/multipath Type: boolean Default: true Description: Install the GRUB boot loader to the multipath device? Installation of GRUB on multipath is experimental. . GRUB is always installed to the master boot record (MBR) of the multipath device. It is also assumed that the WWID of this device is selected as boot device in the system's FibreChannel adapter BIOS. . The GRUB root device is: ${GRUBROOT}. Template: grub-installer/multipath-error Type: error Description: Unable to configure GRUB An error occurred while setting up GRUB for the multipath device. . The GRUB installation has been aborted. Template: grub-installer/bootdev Type: string Description: Device for boot loader installation: You need to make the newly installed system bootable, by installing the GRUB boot loader on a bootable device. The usual way to do this is to install GRUB on the master boot record of your first hard drive. If you prefer, you can install GRUB elsewhere on the drive, or to another drive, or even to a floppy. . The device should be specified as a device in /dev. Below are some examples: - "/dev/sda" will install GRUB to the master boot record of your first hard drive; - "/dev/sda2" will use the second partition of your first hard drive; - "/dev/sdc5" will use the first extended partition of your third hard drive; - "/dev/fd0" will install GRUB to a floppy. Template: grub-installer/choose_bootdev Type: select Choices-C: manual, ${DEVICES_LIST} Choices: Enter device manually, ${DESCRIPTIONS} Description: Device for boot loader installation: You need to make the newly installed system bootable, by installing the GRUB boot loader on a bootable device. The usual way to do this is to install GRUB on the master boot record of your first hard drive. If you prefer, you can install GRUB elsewhere on the drive, or to another drive, or even to a floppy. Template: grub-installer/password Type: password Description: GRUB password: The GRUB boot loader offers many powerful interactive features, which could be used to compromise your system if unauthorized users have access to the machine when it is starting up. To defend against this, you may choose a password which will be required before editing menu entries or entering the GRUB command-line interface. By default, any user will still be able to start any menu entry without entering the password. . If you do not wish to set a GRUB password, leave this field blank. Template: grub-installer/password-again Type: password Description: Re-enter password to verify: Please enter the same GRUB password again to verify that you have typed it correctly. Template: grub-installer/password-mismatch Type: error Description: Password input error The two passwords you entered were not the same. Please try again. Template: grub-installer/password-crypted Type: password Description: for internal use; can be preseeded Template: grub-installer/apt-install-failed Type: error Description: GRUB installation failed The '${GRUB}' package failed to install into /target/. Without the GRUB boot loader, the installed system will not boot. Template: grub-installer/grub-install-failed Type: error Description: Unable to install GRUB in ${BOOTDEV} Executing 'grub-install ${BOOTDEV}' failed. . This is a fatal error. Template: grub-installer/update-grub-failed Type: error Description: Unable to configure GRUB Executing 'update-grub' failed. . This is a fatal error. Template: grub-installer/grub2_instead_of_grub_legacy Type: boolean Default: true Description: for internal use; can be preseeded Set this to false to install GRUB Legacy rather than GRUB 2, if possible. Template: grub-installer/grub_not_mature_on_this_platform Type: boolean Default: false Description: Install GRUB? GRUB 2 is the next generation of GNU GRUB, the boot loader that is commonly used on i386/amd64 PCs. It is now also available for ${ARCH}. . It has interesting new features but is still experimental software for this architecture. If you choose to install it, you should be prepared for breakage, and have an idea on how to recover your system if it becomes unbootable. You're advised not to try this in production environments. Template: grub-installer/progress/title Type: text Description: Installing GRUB boot loader Template: grub-installer/progress/step_os-probe Type: text Description: Looking for other operating systems... Template: grub-installer/progress/step_install Type: text Description: Installing the '${GRUB}' package... Template: grub-installer/progress/step_bootdev Type: text Description: Determining GRUB boot device... Template: grub-installer/progress/step_install_loader Type: text Description: Running "grub-install ${BOOTDEV}"... Template: grub-installer/progress/step_config_loader Type: text Description: Running "update-grub"... Template: grub-installer/progress/step_update_etc Type: text Description: Updating /etc/kernel-img.conf... Template: grub-installer/progress/step_force_efi_removable Type: text Description: Checking whether to force usage of the removable media path Template: grub-installer/progress/step_mount_filesystems Type: text Description: Mounting filesystems Template: grub-installer/progress/step_update_debconf_efi_removable Type: text Description: Configuring grub-efi for future usage of the removable media path Template: debian-installer/grub-installer/title Type: text Description: Install the GRUB boot loader on a hard disk Template: rescue/menu/grub-reinstall Type: text Description: Reinstall GRUB boot loader Template: grub-installer/skip Type: boolean Default: false Description: for internal use; can be preseeded Skip installing grub? Template: grub-installer/make_active Type: boolean Default: true Description: for internal use; can be preseeded Make sure that at least one partition is marked as active (bootable). Template: grub-installer/mounterr Type: error Description: Failed to mount /target/proc Mounting the proc file system on /target/proc failed. . Check /var/log/syslog or see virtual console 4 for the details. . Warning: Your system may be unbootable! Template: rescue/menu/grub-efi-force-removable Type: text Description: Force GRUB installation to the EFI removable media path Template: grub-installer/force-efi-extra-removable Type: boolean Default: false Description: Force GRUB installation to the EFI removable media path? It seems that this computer is configured to boot via EFI, but maybe that configuration will not work for booting from the hard drive. Some EFI firmware implementations do not meet the EFI specification (i.e. they are buggy!) and do not support proper configuration of boot options from system hard drives. . A workaround for this problem is to install an extra copy of the EFI version of the GRUB boot loader to a fallback location, the "removable media path". Almost all EFI systems, no matter how buggy, will boot GRUB that way. . Warning: If the installer failed to detect another operating system that is present on your computer that also depends on this fallback, installing GRUB there will make that operating system temporarily unbootable. GRUB can be manually configured later to boot it if necessary. ********** grub-installer ********** Template: grub-installer/with_other_os Type: boolean Default: true Description: Install the GRUB boot loader to the master boot record? The following other operating systems have been detected on this computer: ${OS_LIST} . If all of your operating systems are listed above, then it should be safe to install the boot loader to the master boot record of your first hard drive. When your computer boots, you will be able to choose to load one of these operating systems or your new system. Template: grub-installer/only_debian Type: boolean Default: true Description: Install the GRUB boot loader to the master boot record? It seems that this new installation is the only operating system on this computer. If so, it should be safe to install the GRUB boot loader to the master boot record of your first hard drive. . Warning: If the installer failed to detect another operating system that is present on your computer, modifying the master boot record will make that operating system temporarily unbootable, though GRUB can be manually configured later to boot it. Template: grub-installer/sataraid Type: boolean Default: true Description: Install the GRUB boot loader to the Serial ATA RAID disk? Installation of GRUB on Serial ATA RAID is experimental. . GRUB is always installed to the master boot record (MBR) of the Serial ATA RAID disk. It is also assumed that disk is listed as the first hard disk in the boot order defined in the system's BIOS setup. . The GRUB root device is: ${GRUBROOT}. Template: grub-installer/sataraid-error Type: error Description: Unable to configure GRUB An error occurred while setting up GRUB for your Serial ATA RAID disk. . The GRUB installation has been aborted. Template: grub-installer/multipath Type: boolean Default: true Description: Install the GRUB boot loader to the multipath device? Installation of GRUB on multipath is experimental. . GRUB is always installed to the master boot record (MBR) of the multipath device. It is also assumed that the WWID of this device is selected as boot device in the system's FibreChannel adapter BIOS. . The GRUB root device is: ${GRUBROOT}. Template: grub-installer/multipath-error Type: error Description: Unable to configure GRUB An error occurred while setting up GRUB for the multipath device. . The GRUB installation has been aborted. Template: grub-installer/bootdev Type: string Description: Device for boot loader installation: You need to make the newly installed system bootable, by installing the GRUB boot loader on a bootable device. The usual way to do this is to install GRUB on the master boot record of your first hard drive. If you prefer, you can install GRUB elsewhere on the drive, or to another drive, or even to a floppy. . The device should be specified as a device in /dev. Below are some examples: - "/dev/sda" will install GRUB to the master boot record of your first hard drive; - "/dev/sda2" will use the second partition of your first hard drive; - "/dev/sdc5" will use the first extended partition of your third hard drive; - "/dev/fd0" will install GRUB to a floppy. Template: grub-installer/choose_bootdev Type: select Choices-C: manual, ${DEVICES_LIST} Choices: Enter device manually, ${DESCRIPTIONS} Description: Device for boot loader installation: You need to make the newly installed system bootable, by installing the GRUB boot loader on a bootable device. The usual way to do this is to install GRUB on the master boot record of your first hard drive. If you prefer, you can install GRUB elsewhere on the drive, or to another drive, or even to a floppy. Template: grub-installer/password Type: password Description: GRUB password: The GRUB boot loader offers many powerful interactive features, which could be used to compromise your system if unauthorized users have access to the machine when it is starting up. To defend against this, you may choose a password which will be required before editing menu entries or entering the GRUB command-line interface. By default, any user will still be able to start any menu entry without entering the password. . If you do not wish to set a GRUB password, leave this field blank. Template: grub-installer/password-again Type: password Description: Re-enter password to verify: Please enter the same GRUB password again to verify that you have typed it correctly. Template: grub-installer/password-mismatch Type: error Description: Password input error The two passwords you entered were not the same. Please try again. Template: grub-installer/password-crypted Type: password Description: for internal use; can be preseeded Template: grub-installer/apt-install-failed Type: error Description: GRUB installation failed The '${GRUB}' package failed to install into /target/. Without the GRUB boot loader, the installed system will not boot. Template: grub-installer/grub-install-failed Type: error Description: Unable to install GRUB in ${BOOTDEV} Executing 'grub-install ${BOOTDEV}' failed. . This is a fatal error. Template: grub-installer/update-grub-failed Type: error Description: Unable to configure GRUB Executing 'update-grub' failed. . This is a fatal error. Template: grub-installer/grub2_instead_of_grub_legacy Type: boolean Default: true Description: for internal use; can be preseeded Set this to false to install GRUB Legacy rather than GRUB 2, if possible. Template: grub-installer/grub_not_mature_on_this_platform Type: boolean Default: false Description: Install GRUB? GRUB 2 is the next generation of GNU GRUB, the boot loader that is commonly used on i386/amd64 PCs. It is now also available for ${ARCH}. . It has interesting new features but is still experimental software for this architecture. If you choose to install it, you should be prepared for breakage, and have an idea on how to recover your system if it becomes unbootable. You're advised not to try this in production environments. Template: grub-installer/progress/title Type: text Description: Installing GRUB boot loader Template: grub-installer/progress/step_os-probe Type: text Description: Looking for other operating systems... Template: grub-installer/progress/step_install Type: text Description: Installing the '${GRUB}' package... Template: grub-installer/progress/step_bootdev Type: text Description: Determining GRUB boot device... Template: grub-installer/progress/step_install_loader Type: text Description: Running "grub-install ${BOOTDEV}"... Template: grub-installer/progress/step_config_loader Type: text Description: Running "update-grub"... Template: grub-installer/progress/step_update_etc Type: text Description: Updating /etc/kernel-img.conf... Template: grub-installer/progress/step_force_efi_removable Type: text Description: Checking whether to force usage of the removable media path Template: grub-installer/progress/step_mount_filesystems Type: text Description: Mounting filesystems Template: grub-installer/progress/step_update_debconf_efi_removable Type: text Description: Configuring grub-efi for future usage of the removable media path Template: debian-installer/grub-installer/title Type: text Description: Install the GRUB boot loader on a hard disk Template: rescue/menu/grub-reinstall Type: text Description: Reinstall GRUB boot loader Template: grub-installer/skip Type: boolean Default: false Description: for internal use; can be preseeded Skip installing grub? Template: grub-installer/make_active Type: boolean Default: true Description: for internal use; can be preseeded Make sure that at least one partition is marked as active (bootable). Template: grub-installer/mounterr Type: error Description: Failed to mount /target/proc Mounting the proc file system on /target/proc failed. . Check /var/log/syslog or see virtual console 4 for the details. . Warning: Your system may be unbootable! Template: rescue/menu/grub-efi-force-removable Type: text Description: Force GRUB installation to the EFI removable media path Template: grub-installer/force-efi-extra-removable Type: boolean Default: false Description: Force GRUB installation to the EFI removable media path? It seems that this computer is configured to boot via EFI, but maybe that configuration will not work for booting from the hard drive. Some EFI firmware implementations do not meet the EFI specification (i.e. they are buggy!) and do not support proper configuration of boot options from system hard drives. . A workaround for this problem is to install an extra copy of the EFI version of the GRUB boot loader to a fallback location, the "removable media path". Almost all EFI systems, no matter how buggy, will boot GRUB that way. . Warning: If the installer failed to detect another operating system that is present on your computer that also depends on this fallback, installing GRUB there will make that operating system temporarily unbootable. GRUB can be manually configured later to boot it if necessary. ********** grub-pc ********** Template: grub2/linux_cmdline Type: string Description: Linux command line: The following Linux command line was extracted from /etc/default/grub or the `kopt' parameter in GRUB Legacy's menu.lst. Please verify that it is correct, and modify it if necessary. The command line is allowed to be empty. Template: grub2/linux_cmdline_default Type: string Default: quiet Description: Linux default command line: The following string will be used as Linux parameters for the default menu entry but not for the recovery mode. Template: grub2/force_efi_extra_removable Type: boolean Default: false Description: Force extra installation to the EFI removable media path? Some EFI-based systems are buggy and do not handle new bootloaders correctly. If you force an extra installation of GRUB to the EFI removable media path, this should ensure that this system will boot Debian correctly despite such a problem. However, it may remove the ability to boot any other operating systems that also depend on this path. If so, you will need to make sure that GRUB is configured successfully to be able to boot any other OS installations correctly. Template: grub2/update_nvram Type: boolean Default: true Description: Update NVRAM variables to automatically boot into Debian? GRUB can configure your platform's NVRAM variables so that it boots into Debian automatically when powered on. However, you may prefer to disable this behavior and avoid changes to your boot configuration. For example, if your NVRAM variables have been set up such that your system contacts a PXE server on every boot, this would preserve that behavior. Template: grub2/kfreebsd_cmdline Type: string Description: kFreeBSD command line: The following kFreeBSD command line was extracted from /etc/default/grub or the `kopt' parameter in GRUB Legacy's menu.lst. Please verify that it is correct, and modify it if necessary. The command line is allowed to be empty. Template: grub2/kfreebsd_cmdline_default Type: string Default: quiet Description: kFreeBSD default command line: The following string will be used as kFreeBSD parameters for the default menu entry but not for the recovery mode. Template: grub2/device_map_regenerated Type: note Description: /boot/grub/device.map has been regenerated The file /boot/grub/device.map has been rewritten to use stable device names. In most cases, this should significantly reduce the need to change it in future, and boot menu entries generated by GRUB should not be affected. . However, since more than one disk is present in the system, it is possible that the system is depending on the old device map. Please check whether there are any custom boot menu entries that rely on GRUB's (hdN) drive numbering, and update them if necessary. . If you do not understand this message, or if there are no custom boot menu entries, you can ignore this message. Template: grub-pc/chainload_from_menu.lst Type: boolean Default: true Description: Chainload from menu.lst? GRUB upgrade scripts have detected a GRUB Legacy setup in /boot/grub. . In order to replace the Legacy version of GRUB in your system, it is recommended that /boot/grub/menu.lst is adjusted to load a GRUB 2 boot image from your existing GRUB Legacy setup. This step can be automatically performed now. . It's recommended that you accept chainloading GRUB 2 from menu.lst, and verify that the new GRUB 2 setup works before it is written to the MBR (Master Boot Record). . Whatever your decision, you can replace the old MBR image with GRUB 2 later by issuing the following command as root: . upgrade-from-grub-legacy Template: grub-pc/install_devices Type: multiselect Choices-C: ${RAW_CHOICES} Choices: ${CHOICES} Description: GRUB install devices: The grub-pc package is being upgraded. This menu allows you to select which devices you'd like grub-install to be automatically run for, if any. . Running grub-install automatically is recommended in most situations, to prevent the installed GRUB core image from getting out of sync with GRUB modules or grub.cfg. . If you're unsure which drive is designated as boot drive by your BIOS, it is often a good idea to install GRUB to all of them. . Note: it is possible to install GRUB to partition boot records as well, and some appropriate partitions are offered here. However, this forces GRUB to use the blocklist mechanism, which makes it less reliable, and therefore is not recommended. Template: grub-pc/install_devices_disks_changed Type: multiselect Choices-C: ${RAW_CHOICES} Choices: ${CHOICES} Description: GRUB install devices: The GRUB boot loader was previously installed to a disk that is no longer present, or whose unique identifier has changed for some reason. It is important to make sure that the installed GRUB core image stays in sync with GRUB modules and grub.cfg. Please check again to make sure that GRUB is written to the appropriate boot devices. . If you're unsure which drive is designated as boot drive by your BIOS, it is often a good idea to install GRUB to all of them. . Note: it is possible to install GRUB to partition boot records as well, and some appropriate partitions are offered here. However, this forces GRUB to use the blocklist mechanism, which makes it less reliable, and therefore is not recommended. Template: grub-pc/disk_description Type: text Description: ${DEVICE} (${SIZE} MB; ${MODEL}) Template: grub-pc/partition_description Type: text Description: - ${DEVICE} (${SIZE} MB; ${PATH}) Template: grub-pc/install_devices_failed Type: boolean Default: false Description: Writing GRUB to boot device failed - continue? GRUB failed to install to the following devices: . ${FAILED_DEVICES} . Do you want to continue anyway? If you do, your computer may not start up properly. Template: grub-pc/install_devices_failed_upgrade Type: boolean Default: true Description: Writing GRUB to boot device failed - try again? GRUB failed to install to the following devices: . ${FAILED_DEVICES} . You may be able to install GRUB to some other device, although you should check that your system will boot from that device. Otherwise, the upgrade from GRUB Legacy will be canceled. Template: grub-pc/install_devices_empty Type: boolean Default: false Description: Continue without installing GRUB? You chose not to install GRUB to any devices. If you continue, the boot loader may not be properly configured, and when this computer next starts up it will use whatever was previously in the boot sector. If there is an earlier version of GRUB 2 in the boot sector, it may be unable to load modules or handle the current configuration file. . If you are already using a different boot loader and want to carry on doing so, or if this is a special environment where you do not need a boot loader, then you should continue anyway. Otherwise, you should install GRUB somewhere. Template: grub-pc/postrm_purge_boot_grub Type: boolean Default: false Description: Remove GRUB 2 from /boot/grub? Do you want to have all GRUB 2 files removed from /boot/grub? . This will make the system unbootable unless another boot loader is installed. Template: grub-pc/mixed_legacy_and_grub2 Type: boolean Default: true Description: Finish conversion to GRUB 2 now? This system still has files from the GRUB Legacy boot loader installed, but it now also has GRUB 2 boot records installed on these disks: . ${DISKS} . It seems likely that GRUB Legacy is no longer in use, and that you should instead upgrade the GRUB 2 images on these disks and finish the conversion to GRUB 2 by removing old GRUB Legacy files. If you do not upgrade these GRUB 2 images, then they may be incompatible with the new packages and cause your system to stop booting properly. . You should generally finish the conversion to GRUB 2 unless these boot records were created by a GRUB 2 installation on some other operating system. Template: grub-pc/kopt_extracted Type: boolean Default: false Description: for internal use Template: grub-pc/timeout Type: string Default: 5 Description: GRUB timeout; for internal use Template: grub-pc/hidden_timeout Type: boolean Default: false Description: Hide the GRUB timeout; for internal use ********** initrd-kickseed ********** Template: initrd-kickseed/wget-failed Type: error # Note: not translatable, runs before language is chosen Description: Failed to download Kickstart file The Kickstart file at ${URL} could not be downloaded. The error was: . ${ERROR} Template: initrd-kickseed/nfs-mount-failed Type: error # Note: not translatable, runs before language is chosen Description: NFS mount failed An error occurred while mounting the directory ${DIR} from NFS server ${SERVER}. See /var/log/syslog for more information. ********** initrd-kickseed ********** Template: initrd-kickseed/wget-failed Type: error # Note: not translatable, runs before language is chosen Description: Failed to download Kickstart file The Kickstart file at ${URL} could not be downloaded. The error was: . ${ERROR} Template: initrd-kickseed/nfs-mount-failed Type: error # Note: not translatable, runs before language is chosen Description: NFS mount failed An error occurred while mounting the directory ${DIR} from NFS server ${SERVER}. See /var/log/syslog for more information. ********** irqbalance ********** Template: irqbalance/enable Type: boolean Default: true Description: Would you like to enable irqbalance? Enable the irqbalance daemon to balance IRQs on SMP systems and systems with hyperthreading. Template: irqbalance/oneshot Type: boolean Default: false Description: Would you like to balance the IRQs once? irqbalance can run in one shot mode, where the IRQs are balanced only once. This is advantageous on hyperthreading systems such as the Pentium 4, which appear to be SMP systems, but are really one physical CPU. ********** keyboard-configuration ********** Template: debian-installer/console-setup-udeb/title Type: text Description: Configure the keyboard Template: keyboard-configuration/other Type: text Description: Other Template: keyboard-configuration/model Type: select Choices: ${CHOICES} Description: Keyboard model: Please select the model of the keyboard of this machine. Template: keyboard-configuration/layout Type: select Choices: ${CHOICES} Description: Country of origin for the keyboard: The layout of keyboards varies per country, with some countries having multiple common layouts. Please select the country of origin for the keyboard of this computer. Template: keyboard-configuration/variant Type: select Choices: ${CHOICES} Description: Keyboard layout: Please select the layout matching the keyboard for this machine. Template: keyboard-configuration/unsupported_config_layout Type: boolean Default: true Description: Keep the current keyboard layout in the configuration file? The current keyboard layout in the configuration file /etc/default/keyboard is defined as XKBLAYOUT="${XKBLAYOUT}" and XKBVARIANT="${XKBVARIANT}". . Please choose whether you want to keep it. If you choose this option, no questions about the keyboard layout will be asked and the current configuration will be preserved. Template: keyboard-configuration/unsupported_layout Type: boolean Default: true Description: Keep default keyboard layout (${XKBLAYOUTVARIANT})? The default value for the keyboard layout is XKBLAYOUT="${XKBLAYOUT}" and XKBVARIANT="${XKBVARIANT}". This default value is based on the currently defined language/region and the settings in /etc/X11/xorg.conf. . Please choose whether you want to keep it. If you choose this option, no questions about the keyboard layout will be asked. Template: keyboard-configuration/unsupported_config_options Type: boolean Default: true Description: Keep current keyboard options in the configuration file? The current keyboard options in the configuration file /etc/default/keyboard are defined as XKBOPTIONS="${XKBOPTIONS}". . If you choose to keep these options, no questions about the keyboard options will be asked. Template: keyboard-configuration/unsupported_options Type: boolean Default: true Description: Keep default keyboard options (${XKBOPTIONS})? The default value for the options of the keyboard layout is XKBOPTIONS="${XKBOPTIONS}". It is based on the currently defined language/region and the settings in /etc/X11/xorg.conf. . If you choose to keep it, no questions about the keyboard options will be asked. Template: keyboard-configuration/toggle Type: select Choices: Caps Lock, Right Alt (AltGr), Right Control, Right Shift, Right Logo key, Menu key, Alt+Shift, Control+Shift, Control+Alt, Alt+Caps Lock, Left Control+Left Shift, Left Alt, Left Control, Left Shift, Left Logo key, Scroll Lock key, No toggling Default: Alt+Shift Description: Method for toggling between national and Latin mode: You will need a way to toggle the keyboard between the national layout and the standard Latin layout. . Right Alt or Caps Lock keys are often chosen for ergonomic reasons (in the latter case, use the combination Shift+Caps Lock for normal Caps toggle). Alt+Shift is also a popular combination; it will however lose its usual behavior in Emacs and other programs that use it for specific needs. . Not all listed keys are present on all keyboards. Template: keyboard-configuration/switch Type: select Choices: No temporary switch, Both Logo keys, Right Alt (AltGr), Right Logo key, Left Alt, Left Logo key Default: No temporary switch Description: Method for temporarily toggling between national and Latin input: When the keyboard is in national mode and one wants to type only a few Latin letters, it might be more appropriate to switch temporarily to Latin mode. The keyboard remains in that mode as long as the chosen key is kept pressed. That key may also be used to input national letters when the keyboard is in Latin mode. . You can disable this feature by choosing "No temporary switch". Template: keyboard-configuration/altgr Type: select Choices: The default for the keyboard layout, No AltGr key, Right Alt (AltGr), Right Control, Right Logo key, Menu key, Left Alt, Left Logo key, Keypad Enter key, Both Logo keys, Both Alt keys Default: Right Alt (AltGr) Description: Key to function as AltGr: With some keyboard layouts, AltGr is a modifier key used to input some characters, primarily ones that are unusual for the language of the keyboard layout, such as foreign currency symbols and accented letters. These are often printed as an extra symbol on keys. Template: keyboard-configuration/compose Type: select Choices: No compose key, Right Alt (AltGr), Right Control, Right Logo key, Menu key, Left Logo key, Caps Lock Default: No compose key Description: Compose key: The Compose key (known also as Multi_key) causes the computer to interpret the next few keystrokes as a combination in order to produce a character not found on the keyboard. . On the text console the Compose key does not work in Unicode mode. If not in Unicode mode, regardless of what you choose here, you can always also use the Control+period combination as a Compose key. Template: keyboard-configuration/ctrl_alt_bksp Type: boolean Default: false Description: Use Control+Alt+Backspace to terminate the X server? By default the combination Control+Alt+Backspace does nothing. If you want it can be used to terminate the X server. Template: keyboard-configuration/xkb-keymap Type: select Choices-C: us, al, ara, es(ast), bd, by, in(ben), be, ba, br, gb, bg, bg(phonetic), mm, ca, ca(multi), es(cat), cn, hr, cz, dk, nl, us(dvorak), bt, epo, ee, et, fi, fr(latin9), ge, de, gr, in(guj), in(jhelum), il, in, hu, is, ie, it, jp, in(kan), kz, kh, kg, kr(kr104), tr(ku_f), tr(ku), la, latam, lv, lt, mk, in(mal), np, no(smi), no, ir, ph, pl, pt, in(guru), ro, ru, rs, pk(snd), lk, sk, si, es, se, ch(fr), ch, tj, in(tam), in(tel), th, cn(tib), tr(f), tr, ua, cn(ug), vn Choices: American English, Albanian, Arabic, Asturian, Bangladesh, Belarusian, Bengali, Belgian, Bosnian, Brazilian, British English, Bulgarian (BDS layout), Bulgarian (phonetic layout), Burmese, Canadian French, Canadian Multilingual, Catalan, Chinese, Croatian, Czech, Danish, Dutch, Dvorak, Dzongkha, Esperanto, Estonian, Ethiopian, Finnish, French, Georgian, German, Greek, Gujarati, Gurmukhi, Hebrew, Hindi, Hungarian, Icelandic, Irish, Italian, Japanese, Kannada, Kazakh, Khmer, Kirghiz, Korean, Kurdish (F layout), Kurdish (Q layout), Lao, Latin American, Latvian, Lithuanian, Macedonian, Malayalam, Nepali, Northern Sami, Norwegian, Persian, Philippines, Polish, Portuguese, Punjabi, Romanian, Russian, Serbian (Cyrillic), Sindhi, Sinhala, Slovak, Slovenian, Spanish, Swedish, Swiss French, Swiss German, Tajik, Tamil, Telugu, Thai, Tibetan, Turkish (F layout), Turkish (Q layout), Ukrainian, Uyghur, Vietnamese Description: Keymap to use: Template: keyboard-configuration/modelcode Type: string Description: for internal use Template: keyboard-configuration/layoutcode Type: string Description: for internal use Template: keyboard-configuration/variantcode Type: string Description: for internal use Template: keyboard-configuration/optionscode Type: string Description: for internal use Template: keyboard-configuration/store_defaults_in_debconf_db Type: boolean Default: true Description: for internal use ********** libc6 ********** Template: glibc/upgrade Type: boolean Default: true Description: Do you want to upgrade glibc now? Running services and programs that are using NSS need to be restarted, otherwise they might not be able to do lookup or authentication any more. The installation process is able to restart some services (such as ssh or telnetd), but other programs cannot be restarted automatically. One such program that needs manual stopping and restart after the glibc upgrade by yourself is xdm - because automatic restart might disconnect your active X11 sessions. . This script detected the following installed services which must be stopped before the upgrade: ${services} . If you want to interrupt the upgrade now and continue later, please answer No to the question below. Template: glibc/restart-services Type: string Description: Services to restart for GNU libc library upgrade: Running services and programs that are using NSS need to be restarted, otherwise they might not be able to do lookup or authentication any more (for services such as ssh, this can affect your ability to login). Please review the following space-separated list of init.d scripts for services to be restarted now, and correct it if needed. . Note: restarting sshd/telnetd should not affect any existing connections. Template: glibc/restart-failed Type: error Description: Failure restarting some services for GNU libc upgrade The following services could not be restarted for the GNU libc library upgrade: . ${services} . You will need to start these manually by running '/etc/init.d/ start'. Template: glibc/disable-screensaver Type: error Description: xscreensaver and xlockmore must be restarted before upgrading One or more running instances of xscreensaver or xlockmore have been detected on this system. Because of incompatible library changes, the upgrade of the GNU libc library will leave you unable to authenticate to these programs. You should arrange for these programs to be restarted or stopped before continuing this upgrade, to avoid locking your users out of their current sessions. Template: libraries/restart-without-asking Type: boolean Default: false Description: Restart services during package upgrades without asking? There are services installed on your system which need to be restarted when certain libraries, such as libpam, libc, and libssl, are upgraded. Since these restarts may cause interruptions of service for the system, you will normally be prompted on each upgrade for the list of services you wish to restart. You can choose this option to avoid being prompted; instead, all necessary restarts will be done for you automatically so you can avoid being asked questions on each library upgrade. Template: glibc/kernel-too-old Type: error Description: Kernel must be upgraded This version of the GNU libc requires kernel version ${kernel_ver} or later. Please upgrade your kernel before installing glibc. Template: glibc/kernel-not-supported Type: note Description: Kernel version not supported This version of the GNU libc requires kernel version ${kernel_ver} or later. Older versions might work but are not officially supported. Please consider upgrading your kernel. ********** libpam0g ********** Template: libpam0g/restart-services Type: string Description: Services to restart for PAM library upgrade: Most services that use PAM need to be restarted to use modules built for this new version of libpam. Please review the following space-separated list of init.d scripts for services to be restarted now, and correct it if needed. Template: libpam0g/xdm-needs-restart Type: error Description: Display manager must be restarted manually The wdm and xdm display managers require a restart for the new version of libpam, but there are X login sessions active on your system that would be terminated by this restart. You will therefore need to restart these services by hand before further X logins will be possible. Template: libpam0g/restart-failed Type: error Description: Failure restarting some services for PAM upgrade The following services could not be restarted for the PAM library upgrade: . ${services} . You will need to start these manually by running '/etc/init.d/ start'. Template: libraries/restart-without-asking Type: boolean Default: false Description: Restart services during package upgrades without asking? There are services installed on your system which need to be restarted when certain libraries, such as libpam, libc, and libssl, are upgraded. Since these restarts may cause interruptions of service for the system, you will normally be prompted on each upgrade for the list of services you wish to restart. You can choose this option to avoid being prompted; instead, all necessary restarts will be done for you automatically so you can avoid being asked questions on each library upgrade. ********** libpam-modules ********** Template: libpam-modules/disable-screensaver Type: error Description: xscreensaver and xlockmore must be restarted before upgrading One or more running instances of xscreensaver or xlockmore have been detected on this system. Because of incompatible library changes, the upgrade of the libpam-modules package will leave you unable to authenticate to these programs. You should arrange for these programs to be restarted or stopped before continuing this upgrade, to avoid locking your users out of their current sessions. ********** libpam-runtime ********** Template: libpam-runtime/title Type: title Description: PAM configuration Template: libpam-runtime/profiles Type: multiselect Choices: ${profiles} Choices-C: ${profile_names} Description: PAM profiles to enable: Pluggable Authentication Modules (PAM) determine how authentication, authorization, and password changing are handled on the system, as well as allowing configuration of additional actions to take when starting user sessions. . Some PAM module packages provide profiles that can be used to automatically adjust the behavior of all PAM-using applications on the system. Please indicate which of these behaviors you wish to enable. Template: libpam-runtime/conflicts Type: error Description: Incompatible PAM profiles selected. The following PAM profiles cannot be used together: . ${conflicts} . Please select a different set of modules to enable. Template: libpam-runtime/override Type: boolean Default: false Description: Override local changes to /etc/pam.d/common-*? One or more of the files /etc/pam.d/common-{auth,account,password,session} have been locally modified. Please indicate whether these local changes should be overridden using the system-provided configuration. If you decline this option, you will need to manage your system's authentication configuration by hand. Template: libpam-runtime/no_profiles_chosen Type: error Description: No PAM profiles have been selected. No PAM profiles have been selected for use on this system. This would grant all users access without authenticating, and is not allowed. Please select at least one PAM profile from the available list. ********** libssl1 ********** Template: libssl1.0.2/restart-services Type: string Description: Services to restart to make them use the new libraries: This release of OpenSSL fixes some security issues. Services will not use these fixes until they are restarted. Please note that restarting the SSH server (sshd) should not affect any existing connections. . Please check the list of detected services that need to be restarted and correct it, if needed. The services names must be identical to the initialization script names in /etc/init.d and separated by spaces. No services will be restarted if the list is empty. . Any service that later fails unexpectedly after this upgrade should be restarted. It is recommended to reboot this host to avoid any SSL-related trouble. Template: libssl1.0.2/restart-failed Type: error Description: Failure restarting some services for OpenSSL upgrade The following services could not be restarted for the OpenSSL library upgrade: . ${services} . You will need to start these manually by running '/etc/init.d/ start'. ********** libssl1 ********** Template: libssl1.1/restart-services Type: string Description: Services to restart to make them use the new libraries: This release of OpenSSL fixes some security issues. Services will not use these fixes until they are restarted. Please note that restarting the SSH server (sshd) should not affect any existing connections. . Please check the list of detected services that need to be restarted and correct it, if needed. The services names must be identical to the initialization script names in /etc/init.d and separated by spaces. No services will be restarted if the list is empty. . Any service that later fails unexpectedly after this upgrade should be restarted. It is recommended to reboot this host to avoid any SSL-related trouble. Template: libssl1.1/restart-failed Type: error Description: Failure restarting some services for OpenSSL upgrade The following services could not be restarted for the OpenSSL library upgrade: . ${services} . You will need to start these manually by running '/etc/init.d/ start'. ********** lilo-installer ********** Template: lilo-installer/bootdev Type: select Choices: ${disc}: Master Boot Record, ${part}: new Debian partition, Other choice (Advanced) Description: LILO installation target: The LILO program needs to be installed to make your new system bootable. By installing it onto your disk's Master Boot Record, LILO will take complete control of the boot process, but if you want to use a different boot manager, just install LILO on the new Debian partition instead. . If unsure, install LILO into the Master Boot Record. Template: lilo-installer/bootdev_raid Type: select Choices: ${disc}: software RAID array, Other choice (Advanced) Description: LILO installation target: The LILO program needs to be installed to make your new system bootable. You may choose to install it onto a software RAID array or another device. Template: lilo-installer/manual_bootdev Type: string Description: LILO installation target: Please enter the device name of the partition or disk onto which LILO should be installed, such as /dev/hda or /dev/sda1. Template: lilo-installer/manual_bootdev_error Type: error Description: Invalid partition name The path ${path} does not represent a partition or hard disk device. Please try again. Template: lilo-installer/progress_title Type: text Description: Installing LILO... Template: lilo-installer/progress_active Type: text Description: Activating partition ${bootdev} Template: lilo-installer/progress_lilo_conf Type: text Description: Creating lilo.conf Template: lilo-installer/progress_installing Type: text Description: Installing the LILO package Template: lilo-installer/progress_running Type: text Description: Running LILO for ${bootdev} Template: lilo-installer/serial-console Type: note Description: LILO configured to use a serial console LILO is configured to use serial port ${PORT} as the console. ${PORT_SPEED} Template: lilo-installer/port-speed Type: text Description: The serial port speed is set to ${SPEED}. Template: lilo-installer/activate-part Type: boolean Default: true Description: Would you like to make this partition active? You have chosen to install LILO on a partition that is not the active one. If this partition is not marked active, then LILO will not be loaded by the boot loader. This may cause you to be unable to boot into the system that is being installed. . You should make this partition active unless you have another boot loader that will allow you to access your new Linux installation. Template: lilo-installer/apt-install-failed Type: boolean Default: true Description: LILO installation failed. Continue anyway? The lilo package failed to install into /target/. Installing LILO as a boot loader is a required step. The install problem might however be unrelated to LILO, so continuing the installation may be possible. Template: lilo-installer/failed Type: error Description: LILO installation failed Running "/sbin/lilo" failed with error code "${ERRCODE}". Template: debian-installer/lilo-installer/title Type: text Description: Install the LILO boot loader on a hard disk Template: lilo-installer/skip Type: boolean Default: false Description: for internal use; can be preseeded Skip installing lilo? ********** lilo-installer ********** Template: lilo-installer/bootdev Type: select Choices: ${disc}: Master Boot Record, ${part}: new Debian partition, Other choice (Advanced) Description: LILO installation target: The LILO program needs to be installed to make your new system bootable. By installing it onto your disk's Master Boot Record, LILO will take complete control of the boot process, but if you want to use a different boot manager, just install LILO on the new Debian partition instead. . If unsure, install LILO into the Master Boot Record. Template: lilo-installer/bootdev_raid Type: select Choices: ${disc}: software RAID array, Other choice (Advanced) Description: LILO installation target: The LILO program needs to be installed to make your new system bootable. You may choose to install it onto a software RAID array or another device. Template: lilo-installer/manual_bootdev Type: string Description: LILO installation target: Please enter the device name of the partition or disk onto which LILO should be installed, such as /dev/hda or /dev/sda1. Template: lilo-installer/manual_bootdev_error Type: error Description: Invalid partition name The path ${path} does not represent a partition or hard disk device. Please try again. Template: lilo-installer/progress_title Type: text Description: Installing LILO... Template: lilo-installer/progress_active Type: text Description: Activating partition ${bootdev} Template: lilo-installer/progress_lilo_conf Type: text Description: Creating lilo.conf Template: lilo-installer/progress_installing Type: text Description: Installing the LILO package Template: lilo-installer/progress_running Type: text Description: Running LILO for ${bootdev} Template: lilo-installer/serial-console Type: note Description: LILO configured to use a serial console LILO is configured to use serial port ${PORT} as the console. ${PORT_SPEED} Template: lilo-installer/port-speed Type: text Description: The serial port speed is set to ${SPEED}. Template: lilo-installer/activate-part Type: boolean Default: true Description: Would you like to make this partition active? You have chosen to install LILO on a partition that is not the active one. If this partition is not marked active, then LILO will not be loaded by the boot loader. This may cause you to be unable to boot into the system that is being installed. . You should make this partition active unless you have another boot loader that will allow you to access your new Linux installation. Template: lilo-installer/apt-install-failed Type: boolean Default: true Description: LILO installation failed. Continue anyway? The lilo package failed to install into /target/. Installing LILO as a boot loader is a required step. The install problem might however be unrelated to LILO, so continuing the installation may be possible. Template: lilo-installer/failed Type: error Description: LILO installation failed Running "/sbin/lilo" failed with error code "${ERRCODE}". Template: debian-installer/lilo-installer/title Type: text Description: Install the LILO boot loader on a hard disk Template: lilo-installer/skip Type: boolean Default: false Description: for internal use; can be preseeded Skip installing lilo? ********** lilo ********** Template: lilo/new-config Type: note Description: LILO configuration It seems to be your first LILO installation. It is absolutely necessary to run liloconfig(8) when you complete this process and execute /sbin/lilo after this. . LILO won't work if you don't do this. Template: lilo/add_large_memory Type: boolean Default: false Description: Do you want to add the large-memory option? Usually LILO loads the initrd file into the first 15MB of memory to avoid a BIOS limitation with older systems (earlier than 2001 and few systems until 2004). . With newer kernels the combination of kernel and initrd may not fit into the first 15MB of memory. LILO will compute the needed size of memory and will automatically use the memory above 15MB, too, if there is enough physical memory. . If this machine has a recent BIOS without a 15MB limitation and you want to use memory above 15MB for all kernels, set the 'large-memory' option. Template: lilo/runme Type: boolean Default: false Description: Do you want to run /sbin/lilo now? It was detected that it's necessary to run /sbin/lilo in order to activate the new LILO configuration. . WARNING: This procedure will write data in your MBR and may overwrite some data there. If you skip this step, you must run /sbin/lilo before rebooting your computer, or your system may not boot again. Template: lilo/diskid_uuid Type: boolean Default: false Description: Do you want to convert boot and root options? Since kernel using the newer disk interface 'libata' you need the newer DiskID and/or UUID in your /etc/lilo.conf for the boot and root options. For the most modern systems you should use this conversion and then run '/sbin/lilo'. ********** linux-base ********** Template: linux-base/removing-title Type: title Description: Removing ${package} Template: linux-base/removing-running-kernel Type: boolean Default: true Description: Abort kernel removal? You are running a kernel (version ${running}) and attempting to remove the same version. . This can make the system unbootable as it will remove /boot/vmlinuz-${running} and all modules under the directory /lib/modules/${running}. This can only be fixed with a copy of the kernel image and the corresponding modules. . It is highly recommended to abort the kernel removal unless you are prepared to fix the system after removal. ********** load-media ********** Template: retriever/media/loadnow Type: boolean Default: true Description: Load drivers from removable media now? You probably need to load drivers from removable media before continuing with the installation. If you know that the install will work without extra drivers, you can skip this step. . If you do need to load drivers, insert the appropriate removable media, such as a driver floppy or USB stick before continuing. Template: debian-installer/load-media/title Type: text Description: Load drivers from removable media Template: retriever/media/unknown Type: boolean Default: false Description: Unknown removable media. Try to load anyway? Detected removable media that is not a known driver media. Please make sure that the correct media is inserted. You can still continue if you have an unofficial removable media you want to use. Template: retriever/media/warning Type: text Description: Please insert ${DISK_LABEL} ('${DISK_NAME}') first. Due to dependencies between packages, drivers must be loaded in the correct order. Template: retriever/media/loadanother Type: boolean Default: true Description: Load drivers from another removable media? To load additional drivers from another removable media, please insert the appropriate removable media, such as a driver floppy or USB stick before continuing. ********** load-media ********** Template: retriever/media/loadnow Type: boolean Default: true Description: Load drivers from removable media now? You probably need to load drivers from removable media before continuing with the installation. If you know that the install will work without extra drivers, you can skip this step. . If you do need to load drivers, insert the appropriate removable media, such as a driver floppy or USB stick before continuing. Template: debian-installer/load-media/title Type: text Description: Load drivers from removable media Template: retriever/media/unknown Type: boolean Default: false Description: Unknown removable media. Try to load anyway? Detected removable media that is not a known driver media. Please make sure that the correct media is inserted. You can still continue if you have an unofficial removable media you want to use. Template: retriever/media/warning Type: text Description: Please insert ${DISK_LABEL} ('${DISK_NAME}') first. Due to dependencies between packages, drivers must be loaded in the correct order. Template: retriever/media/loadanother Type: boolean Default: true Description: Load drivers from another removable media? To load additional drivers from another removable media, please insert the appropriate removable media, such as a driver floppy or USB stick before continuing. ********** locales ********** Template: locales/locales_to_be_generated Type: multiselect Choices: All locales, ${locales} Description: Locales to be generated: Locales are a framework to switch between multiple languages and allow users to use their language, country, characters, collation order, etc. . Please choose which locales to generate. UTF-8 locales should be chosen by default, particularly for new installations. Other character sets may be useful for backwards compatibility with older systems and software. Template: locales/default_environment_locale Type: select Choices: None, C.UTF-8, ${locales} Default: None Description: Default locale for the system environment: Many packages in Debian use locales to display text in the correct language for the user. You can choose a default locale for the system from the generated locales. . This will select the default language for the entire system. If this system is a multi-user system where not all users are able to speak the default language, they will experience difficulties. ********** lowmem ********** Template: debian-installer/lowmem/title Type: text Description: Free memory (low memory install) ********** lvmcfg-utils ********** Template: lvmcfg/activevg Type: boolean Default: true Description: Activate existing volume groups? ${COUNT} existing volume groups have been found. Please indicate whether you want to activate them. Template: lvmcfg/mainmenu Type: select Choices: Modify volume groups (VG), Modify logical volumes (LV), Leave Description: LVM configuration action: This is the Logical Volume Manager configuration menu. Template: lvmcfg/vgmenu Type: select Choices: Create volume groups, Delete volume groups, Extend volume groups, Reduce volume groups, Leave Description: Volume groups configuration action: Template: lvmcfg/lvmenu Type: select Choices: Create logical volumes, Delete logical volumes, Leave Description: Logical volumes configuration action: Template: lvmcfg/vgcreate_parts Type: multiselect Choices: ${PARTITIONS} Description: Devices for the new volume group: Please select the devices for the new volume group. . You can select one or more devices. Template: lvmcfg/vgcreate_name Type: string Description: Volume group name: Please enter the name you would like to use for the new volume group. Template: lvmcfg/vgcreate_nosel Type: error Description: No physical volumes selected No physical volumes were selected. The creation of a new volume group was aborted. Template: lvmcfg/vgcreate_nonamegiven Type: error Description: No volume group name entered No name for the volume group has been entered. Please enter a name. Template: lvmcfg/vgcreate_nameused Type: error Description: Volume group name already in use The selected volume group name is already in use. Please choose another name. Template: lvmcfg/vgcreate_devnameused Type: error Description: Volume group name overlaps with device name The selected volume group name overlaps with an existing device name. Please choose another name. Template: lvmcfg/vgdelete_names Type: select Choices: ${GROUPS} Description: Volume group to delete: Please select the volume group you wish to delete. Template: lvmcfg/vgdelete_novg Type: error Description: No volume group found No volume group has been found. . The volume group may have already been deleted. Template: lvmcfg/vgdelete_confirm Type: boolean Default: true Description: Really delete the volume group? Please confirm the ${VG} volume group removal. Template: lvmcfg/vgdelete_error Type: error Description: Error while deleting volume group The selected volume group could not be deleted. One or more logical volumes may currently be in use. Template: lvmcfg/vgextend_novg Type: error Description: No volume group found No volume group has been found. . No volume group can be deleted. Template: lvmcfg/vgextend_names Type: select Choices: ${GROUPS} Description: Volume group to extend: Please select the volume group you wish to extend. Template: lvmcfg/vgextend_parts Type: multiselect Choices: ${PARTITIONS} Description: Devices to add to the volume group: Please select the devices you wish to add to the volume group. . You can select one or more devices. Template: lvmcfg/vgextend_nosel Type: error Description: No physical volumes selected No physical volumes were selected. Extension of the volume group was aborted. Template: lvmcfg/vgextend_error Type: error Description: Error while extending volume group The physical volume ${PARTITION} could not be added to the selected volume group. Template: lvmcfg/vgreduce_novg Type: error Description: No volume group found No volume group has been found. . No volume group can be reduced. Template: lvmcfg/vgreduce_names Type: select Choices: ${GROUPS} Description: Volume group to reduce: Please select the volume group you wish to reduce. Template: lvmcfg/vgreduce_parts Type: select Choices: ${PARTITIONS} Description: Device to remove from volume group: Please select the device you wish to remove from the volume group. Template: lvmcfg/vgreduce_minpv Type: error Description: Error while reducing volume group The selected volume group (${VG}) could not be reduced. There is only one physical volume attached. Please delete the volume group instead. Template: lvmcfg/vgreduce_error Type: error Description: Error while reducing volume group The physical volume ${PARTITION} could not be removed from the selected volume group. . Check /var/log/syslog or see virtual console 4 for the details. Template: lvmcfg/lvcreate_novg Type: error Description: No volume group found No volume groups were found for creating a new logical volume. Please create more physical volumes and volume groups. Template: lvmcfg/lvcreate_nofreevg Type: error Description: No volume group found No free volume groups were found for creating a new logical volume. Please create more physical volumes and volume groups, or reduce an existing volume group. Template: lvmcfg/lvcreate_name Type: string Description: Logical volume name: Please enter the name you would like to use for the new logical volume. Template: lvmcfg/lvcreate_vgnames Type: select Choices: ${GROUPS} Description: Volume group: Please select the volume group where the new logical volume should be created. Template: lvmcfg/lvcreate_nonamegiven Type: error Description: No logical volume name entered No name for the logical volume has been entered. Please enter a name. Template: lvmcfg/lvcreate_exists Type: error Description: Error while creating a new logical volume The name ${LV} is already in use by another logical volume on the same volume group (${VG}). Template: lvmcfg/lvcreate_size Type: string Description: Logical volume size: Please enter the size of the new logical volume. The size may be entered in the following formats: 10K (Kilobytes), 10M (Megabytes), 10G (Gigabytes), 10T (Terabytes). The default unit is Megabytes. Template: lvmcfg/lvcreate_error Type: error Description: Error while creating a new logical volume Unable to create a new logical volume (${LV}) on ${VG} with the new size ${SIZE}. . Check /var/log/syslog or see virtual console 4 for the details. Template: lvmcfg/lvdelete_novg Type: error Description: No volume group found No volume group has been found for deleting a logical volume. Template: lvmcfg/lvdelete_vgnames Type: select Choices: ${GROUPS} Description: Volume group: Please select the volume group which contains the logical volume to be deleted. Template: lvmcfg/lvdelete_nolv Type: error Description: No logical volume found No logical volume has been found. Please create a logical volume first. Template: lvmcfg/lvdelete_lvnames Type: select Choices: ${LVS} Description: Logical volume: Please select the logical volume to be deleted on ${VG}. Template: lvmcfg/lvdelete_error Type: error Description: Error while deleting the logical volume The logical volume (${LV}) on ${VG} could not be deleted. . Check /var/log/syslog or see virtual console 4 for the details. Template: lvmcfg/nopartitions Type: error Description: No usable physical volumes found No physical volumes (i.e. partitions) were found in your system. All physical volumes may already be in use. You may also need to load some required kernel modules or re-partition the hard drives. Template: lvmcfg/nolvm Type: error Description: Logical Volume Manager not available The current kernel doesn't support the Logical Volume Manager. You may need to load the lvm-mod module. ********** mdadm ********** Template: mdadm/autocheck Type: boolean Default: true Description: Should mdadm run monthly redundancy checks of the MD arrays? If the kernel supports it (versions greater than 2.6.14), mdadm can periodically check the redundancy of MD arrays (RAIDs). This may be a resource-intensive process, depending on the local setup, but it could help prevent rare cases of data loss. Note that this is a read-only check unless errors are found; if errors are found, mdadm will try to correct them, which may result in write access to the media. . The default, if turned on, is to check on the first Sunday of every month at 01:06. Template: mdadm/start_daemon Type: boolean Default: true Description: Do you want to start the MD monitoring daemon? The MD (RAID) monitor daemon sends email notifications in response to important MD events (such as a disk failure). . Enabling this option is recommended. Template: mdadm/mail_to Type: string Default: root Description: Recipient for email notifications: Please enter the email address of the user who should get the email notifications for important MD events. ********** mdcfg-utils ********** Template: debian-installer/mdcfg/title Type: text Description: Configure MD devices Template: mdcfg/nomd Type: error Description: Multidisk (MD) not available The current kernel doesn't seem to support multidisk devices. This should be solved by loading the needed modules. Template: mdcfg/mainmenu Type: select Choices: Create MD device, Delete MD device, Finish Description: Multidisk configuration actions This is the Multidisk (MD) and software RAID configuration menu. . Please select one of the proposed actions to configure multidisk devices. Template: mdcfg/noparts Type: error Description: No RAID partitions available No unused partitions of the type "Linux RAID Autodetect" are available. Please create such a partition, or delete an already used multidisk device to free its partitions. . If you have such partitions, they might contain actual file systems, and are therefore not available for use by this configuration utility. Template: mdcfg/notenoughparts Type: error Description: Not enough RAID partitions available There are not enough RAID partitions available for your selected configuration. You have ${NUM_PART} RAID partitions available but your configuration requires ${REQUIRED} partitions. Template: mdcfg/createmain Type: select Choices: RAID0, RAID1, RAID5, RAID6, RAID10, Cancel Description: Multidisk device type: Please choose the type of the multidisk device to be created. Template: mdcfg/raid0devs Type: multiselect Choices: ${PARTITIONS} Description: Active devices for the RAID0 multidisk device: You have chosen to create a RAID0 array. Please choose the active devices in this array. Template: mdcfg/raiddevcount Type: string Description: Number of active devices for the RAID${LEVEL} array: The RAID${LEVEL} array will consist of both active and spare partitions. The active partitions are those used, while the spare devices will only be used if one or more of the active devices fail. A minimum of ${MINIMUM} active devices is required. . NOTE: this setting cannot be changed later. Template: mdcfg/raiddevs Type: multiselect Choices: ${PARTITIONS} Description: Active devices for the RAID${LEVEL} multidisk device: You have chosen to create a RAID${LEVEL} array with ${COUNT} active devices. . Please choose which partitions are active devices. You must select exactly ${COUNT} partitions. Template: mdcfg/raidsparecount Type: string Description: Number of spare devices for the RAID${LEVEL} array: Template: mdcfg/raidsparedevs Type: multiselect Choices: ${PARTITIONS} Description: Spare devices for the RAID${LEVEL} multidisk device: You have chosen to create a RAID${LEVEL} array with ${COUNT} spare devices. . Please choose which partitions will be used as spare devices. You may choose up to ${COUNT} partitions. If you choose less than ${COUNT} devices, the remaining partitions will be added to the array as "missing". You will be able to add them later to the array. Template: mdcfg/raid10layout Type: string Description: Layout of the RAID10 multidisk device: The layout must be n, o, or f (arrangement of the copies) followed by a number (number of copies of each chunk). The number must be smaller or equal to the number of active devices. . The letter is the arrangement of the copies: n - near copies: Multiple copies of one data block are at similar offsets in different devices. f - far copies: Multiple copies have very different offsets o - offset copies: Rather than the chunks being duplicated within a stripe, whole stripes are duplicated but are rotated by one device so duplicate blocks are on different devices. . NOTE: this setting cannot be changed later. Template: mdcfg/deletemenu Type: select Choices: ${DEVICES}, Cancel Description: Multidisk device to be deleted: Deleting a multidisk device will stop it and clear the superblock of all its components. . Please note this will not immediately allow you to reuse the partitions or devices in a new multidisk device. The array will however be unusable after the deletion. . If you select a device for deletion, you will get some information about it and you will be given the option of aborting this operation. Template: mdcfg/delete_no_md Type: error Description: No multidisk devices available No multidisk devices are available for deletion. Template: mdcfg/deleteverify Type: boolean Default: false Description: Really delete this multidisk device? Please confirm whether you really want to delete the following multidisk device: . Device: ${DEVICE} Type: ${TYPE} Component devices: . ${DEVICES} Template: mdcfg/deletefailed Type: error Description: Failed to delete the multidisk device There was an error deleting the multidisk device. It may be in use. ********** media-retriever ********** Template: retriever/media/packages/progress Type: text Description: Scanning removable media Template: retriever/media/error Type: text Description: Cannot read removable media, or no drivers found. There was a problem reading data from the removable media. Please make sure that the right media is present. If you continue to have trouble, your removable media might be bad. ********** multipath-tools-boot ********** Template: multipath-tools-boot/scsi_id Type: note Description: The location of the getuid callout has changed Your /etc/multipath.conf still has a getuid_callout pointing to /sbin/scsi_id but the binary has moved to /lib/udev/scsi_id in udev 0.113-1. Please update your configuration. This is best done by removing the getuid_callout option entirely. . Don't forget to update your initramfs after these changes. Otherwise your system might not boot from multipath. ********** netcfg ********** Template: netcfg/enable Type: boolean Default: true Description: for internal use; can be preseeded Set to false to disable netcfg entirely via preseed. Template: netcfg/use_autoconfig Type: boolean Default: true Description: Auto-configure networking? Networking can be configured either by entering all the information manually, or by using DHCP (or a variety of IPv6-specific methods) to detect network settings automatically. If you choose to use autoconfiguration and the installer is unable to get a working configuration from the network, you will be given the opportunity to configure the network manually. Template: netcfg/get_domain Type: string Description: Domain name: The domain name is the part of your Internet address to the right of your host name. It is often something that ends in .com, .net, .edu, or .org. If you are setting up a home network, you can make something up, but make sure you use the same domain name on all your computers. Template: netcfg/get_nameservers Type: string Description: Name server addresses: The name servers are used to look up host names on the network. Please enter the IP addresses (not host names) of up to 3 name servers, separated by spaces. Do not use commas. The first name server in the list will be the first to be queried. If you don't want to use any name server, just leave this field blank. Template: netcfg/choose_interface Type: select Choices: ${ifchoices} Description: Primary network interface: Your system has multiple network interfaces. Choose the one to use as the primary network interface during the installation. If possible, the first connected network interface found has been selected. Template: netcfg/wireless_essid Type: string Description: Wireless ESSID for ${iface}: ${iface} is a wireless network interface. Please enter the name (the ESSID) of the wireless network you would like ${iface} to use. If you would like to use any available network, leave this field blank. Template: netcfg/wireless_essid_again Type: string Description: Wireless ESSID for ${iface}: Attempting to find an available wireless network failed. . ${iface} is a wireless network interface. Please enter the name (the ESSID) of the wireless network you would like ${iface} to use. To connect to any available network, leave this field blank. Template: netcfg/wireless_security_type Type: select Default: wpa Choices-C: wep/open, wpa Choices: WEP/Open Network, WPA/WPA2 PSK Description: Wireless network type for ${iface}: Choose WEP/Open if the network is open or secured with WEP. Choose WPA/WPA2 if the network is protected with WPA/WPA2 PSK (Pre-Shared Key). Template: netcfg/wireless_wep Type: string Description: WEP key for wireless device ${iface}: If applicable, please enter the WEP security key for the wireless device ${iface}. There are two ways to do this: . If your WEP key is in the format 'nnnn-nnnn-nn', 'nn:nn:nn:nn:nn:nn:nn:nn', or 'nnnnnnnn', where n is a number, just enter it as it is into this field. . If your WEP key is in the format of a passphrase, prefix it with 's:' (without quotes). . Of course, if there is no WEP key for your wireless network, leave this field blank. Template: netcfg/invalid_wep Type: error Description: Invalid WEP key The WEP key '${wepkey}' is invalid. Please refer to the instructions on the next screen carefully on how to enter your WEP key correctly, and try again. Template: netcfg/invalid_pass Type: error Description: Invalid passphrase The WPA/WPA2 PSK passphrase was either too long (more than 64 characters) or too short (less than 8 characters). Template: netcfg/wireless_wpa Type: string Description: WPA/WPA2 passphrase for wireless device ${iface}: Enter the passphrase for WPA/WPA2 PSK authentication. This should be the passphrase defined for the wireless network you are trying to use. Template: netcfg/invalid_essid Type: error Description: Invalid ESSID The ESSID "${essid}" is invalid. ESSIDs may only be up to ${max_essid_len} characters, but may contain all kinds of characters. Template: netcfg/wpa_progress Type: text Description: Attempting to exchange keys with the access point... Template: netcfg/wpa_progress_note Type: text Description: This may take some time. Template: netcfg/wpa_success_note Type: text Description: WPA/WPA2 connection succeeded Template: netcfg/wpa_supplicant_failed Type: note Description: Failure of key exchange and association The exchange of keys and association with the access point failed. Please check the WPA/WPA2 parameters you provided. Template: netcfg/get_hostname Type: string Default: debian Description: Hostname: Please enter the hostname for this system. . The hostname is a single word that identifies your system to the network. If you don't know what your hostname should be, consult your network administrator. If you are setting up your own home network, you can make something up here. Template: netcfg/hostname Type: string Description: for internal use; can be preseeded Hostname to set for the system; ignores names provided by DHCP or DNS. Template: netcfg/invalid_hostname Type: error Description: Invalid hostname The name "${hostname}" is invalid. . A valid hostname may contain only the numbers 0-9, upper and lowercase letters (A-Z and a-z), and the minus sign. It must be at most ${maxhostnamelen} characters long, and may not begin or end with a minus sign. Template: netcfg/error Type: error Description: Error An error occurred and the network configuration process has been aborted. You may retry it from the installation main menu. Template: netcfg/no_interfaces Type: error Description: No network interfaces detected No network interfaces were found. The installation system was unable to find a network device. . You may need to load a specific module for your network card, if you have one. For this, go back to the network hardware detection step. Template: netcfg/kill_switch_enabled Type: note Description: Kill switch enabled on ${iface} ${iface} appears to have been disabled by means of a physical "kill switch". If you intend to use this interface, please switch it on before continuing. Template: netcfg/wireless_adhoc_managed Type: select Default: Infrastructure (Managed) network Choices: Infrastructure (Managed) network, Ad-hoc network (Peer to peer) Description: Type of wireless network: Wireless networks are either managed or ad-hoc. If you use a real access point of some sort, your network is Managed. If another computer is your 'access point', then your network may be Ad-hoc. Template: netcfg/wifi_progress_title Type: text Description: Wireless network configuration Template: netcfg/wifi_progress_info Type: text Description: Searching for wireless access points... Template: netcfg/disable_autoconfig Type: boolean Default: false Description: for internal use; can be preseeded Set to true to force static network configuration Template: netcfg/disable_dhcp Type: boolean Default: false Description: for internal use; can be preseeded (deprecated) Set to true to force static network configuration (deprecated) Template: netcfg/link_detect_progress Type: text Description: Detecting link on ${interface}; please wait... Template: netcfg/internal-none Type: text Description: Template: netcfg/internal-wifi Type: text Description: Wireless ethernet (802.11x) Template: netcfg/internal-wireless Type: text Description: wireless Template: netcfg/internal-eth Type: text Description: Ethernet Template: netcfg/internal-tr Type: text Description: Token Ring Template: netcfg/internal-usb Type: text Description: USB net Template: netcfg/internal-arc Type: text Description: Arcnet Template: netcfg/internal-slip Type: text Description: Serial-line IP Template: netcfg/internal-plip Type: text Description: Parallel-port IP Template: netcfg/internal-ppp Type: text Description: Point-to-Point Protocol Template: netcfg/internal-sit Type: text Description: IPv6-in-IPv4 Template: netcfg/internal-ippp Type: text Description: ISDN Point-to-Point Protocol Template: netcfg/internal-ctc Type: text Description: Channel-to-channel Template: netcfg/internal-escon Type: text Description: Real channel-to-channel Template: netcfg/internal-hsi Type: text Description: Hipersocket Template: netcfg/internal-iucv Type: text Description: Inter-user communication vehicle Template: netcfg/internal-unknown-iface Type: text Description: Unknown interface Template: base-installer/progress/netcfg Type: text Description: Storing network settings... Template: debian-installer/netcfg/title Type: text Description: Configure the network Template: netcfg/target_network_config Type: select Choices-C: nm_config, ifupdown, loopback Choices: Network Manager, ifupdown (/etc/network/interfaces), No network configuration Description: for internal use; can be preseeded Specifies what kind of network connection management tool should be configured post-installation if multiple are available. Automatic selection is used in this order when not specified: network-manager if available (on Linux only), ethernet configuration through ifupdown on wired installation and loopback configuration through ifupdown on wireless installations. Template: netcfg/link_wait_timeout Type: string Default: 3 Description: Waiting time (in seconds) for link detection: Please enter the maximum time you would like to wait for network link detection. Template: netcfg/bad_link_wait_timeout Type: error Description: Invalid network link detection waiting time The value you have provided is not valid. The maximum waiting time (in seconds) for network link detection must be a positive integer. Template: netcfg/wireless_show_essids Type: select Choices-C: ${essid_list} manual Choices: ${essid_list} Enter ESSID manually Description: Wireless network: Select the wireless network to use during the installation process. Template: netcfg/dhcp_hostname Type: string Description: DHCP hostname: You may need to supply a DHCP host name. If you are using a cable modem, you might need to specify an account number here. . Most other users can just leave this blank. Template: netcfg/dhcp_progress Type: text Description: Configuring the network with DHCP Template: netcfg/dhcp_progress_note Type: text Description: This may take some time. Template: netcfg/dhcp_success_note Type: text Description: Network autoconfiguration has succeeded Template: netcfg/no_dhcp_client Type: error Description: No DHCP client found No DHCP client was found. This package requires pump or dhcp-client. . The DHCP configuration process has been aborted. Template: netcfg/dhcp_options Type: select Choices: Retry network autoconfiguration, Retry network autoconfiguration with a DHCP hostname, Configure network manually, ${wifireconf}, Do not configure the network at this time Default: Configure network manually Description: Network configuration method: From here you can choose to retry DHCP network autoconfiguration (which may succeed if your DHCP server takes a long time to respond) or to configure the network manually. Some DHCP servers require a DHCP hostname to be sent by the client, so you can also choose to retry DHCP network autoconfiguration with a hostname that you provide. Template: netcfg/dhcp_failed Type: note Description: Network autoconfiguration failed Your network is probably not using the DHCP protocol. Alternatively, the DHCP server may be slow or some network hardware is not working properly. Template: netcfg/no_default_route Type: boolean Description: Continue without a default route? The network autoconfiguration was successful. However, no default route was set: the system does not know how to communicate with hosts on the Internet. This will make it impossible to continue with the installation unless you have the first installation CD-ROM, a 'Netinst' CD-ROM, or packages available on the local network. . If you are unsure, you should not continue without a default route: contact your local network administrator about this problem. Template: netcfg/internal-wifireconf Type: text Description: Reconfigure the wireless network Template: netcfg/dhcp_timeout Type: string Description: for internal use; can be preseeded Timeout for trying DHCP Default: 25 Template: netcfg/dhcp_ntp_servers Type: text Description: for internal use NTP servers provided by DHCP Template: netcfg/slaac_wait_title Type: text Description: Attempting IPv6 autoconfiguration... Template: netcfg/ipv6_link_local_wait_title Type: text Description: Waiting for link-local address... Template: netcfg/ipv6_config_flags_wait_title Type: text Description: Attempting IPv6 autoconfiguration... Template: netcfg/dhcpv6_timeout Type: string Description: for internal use; can be preseeded Timeout for trying DHCPv6 Default: 15 Template: netcfg/dhcpv6_progress Type: text Description: Configuring the network with DHCPv6 Template: netcfg/get_ipaddress Type: string Description: IP address: The IP address is unique to your computer and may be: . * four numbers separated by periods (IPv4); * blocks of hexadecimal characters separated by colons (IPv6). . You can also optionally append a CIDR netmask (such as "/24"). . If you don't know what to use here, consult your network administrator. Template: netcfg/bad_ipaddress Type: error Description: Malformed IP address The IP address you provided is malformed. It should be in the form x.x.x.x where each 'x' is no larger than 255 (an IPv4 address), or a sequence of blocks of hexadecimal digits separated by colons (an IPv6 address). Please try again. Template: netcfg/get_pointopoint Type: string Description: Point-to-point address: The point-to-point address is used to determine the other endpoint of the point to point network. Consult your network administrator if you do not know the value. The point-to-point address should be entered as four numbers separated by periods. Template: netcfg/get_netmask Type: string Description: Netmask: The netmask is used to determine which machines are local to your network. Consult your network administrator if you do not know the value. The netmask should be entered as four numbers separated by periods. Template: netcfg/get_gateway Type: string Description: Gateway: The gateway is an IP address (four numbers separated by periods) that indicates the gateway router, also known as the default router. All traffic that goes outside your LAN (for instance, to the Internet) is sent through this router. In rare circumstances, you may have no router; in that case, you can leave this blank. If you don't know the proper answer to this question, consult your network administrator. Template: netcfg/gateway_unreachable Type: error Description: Unreachable gateway The gateway address you entered is unreachable. . You may have made an error entering your IP address, netmask and/or gateway. Template: netcfg/no_ipv6_pointopoint Type: error Description: IPv6 unsupported on point-to-point links IPv6 addresses cannot be configured on point-to-point links. Please use an IPv4 address, or go back and select a different network interface. Template: netcfg/confirm_static Type: boolean Default: true Description: Is this information correct? Currently configured network parameters: . interface = ${interface} ipaddress = ${ipaddress} netmask = ${netmask} gateway = ${gateway} pointopoint = ${pointopoint} nameservers = ${nameservers} Template: debian-installer/netcfg-static/title Type: text Description: Configure a network using static addressing ********** net-retriever ********** Template: retriever/net/error Type: select Choices: Retry, Change mirror, Cancel Default: Retry Description: Downloading a file failed: The installer failed to download a file from the mirror. This may be a problem with your network, or with the mirror. You can choose to retry the download, select a different mirror, or cancel and choose another installation method. ********** network-console ********** Template: debian-installer/network-console/title Type: text Description: Continue installation remotely using SSH Template: network-console/login Type: select Choices: Start installer, Start installer (expert mode), Start shell Default: Start menu Description: Network console option: This is the network console for the Debian installer. From here, you may start the Debian installer, or execute an interactive shell. . To return to this menu, you will need to log in again. Template: network-console/key Type: text Description: Generating SSH host key Template: network-console/password Type: password Description: Remote installation password: You need to set a password for remote access to the Debian installer. A malicious or unqualified user with access to the installer can have disastrous results, so you should take care to choose a password that is not easy to guess. It should not be a word found in the dictionary, or a word that could be easily associated with you, like your middle name. . This password is used only by the Debian installer, and will be discarded once you finish the installation. Template: network-console/password-again Type: password Description: Re-enter password to verify: Please enter the same remote installation password again to verify that you have typed it correctly. Template: network-console/password-empty Type: error Description: Empty password You entered an empty password, which is not allowed. Please choose a non-empty password. Template: network-console/password-mismatch Type: error Description: Password mismatch The two passwords you entered were not the same. Please enter a password again. Template: network-console/start Type: note Description: Start SSH To continue the installation, please use an SSH client to connect to the IP address ${ips} and log in as the "installer" user. For example: . ssh installer@${ip} . The fingerprint of this SSH server's host key is: ${fingerprint} . Please check this carefully against the fingerprint reported by your SSH client. Template: network-console/authorized_keys_url Type: string Description: for internal use; can be preseeded This variable contains the URL that provides a list of authorized SSH public keys Template: network-console/authorized_keys_fetch_failure Type: error Description: Could not fetch SSH authorized keys An error occurred while fetching SSH authorized keys from ${LOCATION}. . Check /var/log/syslog or see virtual console 4 for the details. ********** network-preseed ********** Template: debian-installer/network-preseed/title Type: text Description: Download debconf preconfiguration file Template: preseed/url Type: string Description: Location of initial preconfiguration file: In order to perform an automated install, you need to supply a preconfiguration file (which can in turn pull in other files). To do that, you need to provide a (perhaps partial) URL. . This can be as simple as the machine name where your preseed files reside up to a full URL. Any of these could be made to work: intra [for example.com, these three are equivalent] intra.example.com http://intra.example.com/d-i/./lenny/preseed.cfg http://192.168.0.1/~phil/test47.txt floppy://preseed.cfg file:///hd-media/kiosk/./preseed.cfg . For fully automated installs, preseed/url should itself be preseeded (via kernel command line, DHCP, or syslinux.cfg on customised media) . See http://wiki.debian.org/DebianInstaller/Preseed for inspiration. Template: preseed/url/checksum Type: string Description: for internal use; can be preseeded Optional md5sum (or sums) for the preconfiguration files Template: auto-install/enable Type: boolean Default: false Description: for internal use; can be preseeded If true, attempt a fully automatic install Template: auto-install/defaultroot Type: string Default: d-i/stretch/./preseed.cfg Description: for internal use; can be preseeded Path added to local server to give the preseed root ********** nobootloader ********** Template: debian-installer/nobootloader/title Type: text Description: Continue without boot loader Template: nobootloader/mounterr Type: error Description: Failed to mount /target/proc Mounting the proc file system on /target/proc failed. . Check /var/log/syslog or see virtual console 4 for the details. . Warning: Your system may be unbootable! Template: nobootloader/confirmation_powerpc_chrp_pegasos Type: note Description: Setting firmware variables for automatic boot Some variables need to be set in the Genesi firmware in order for your system to boot automatically. At the end of the installation, the system will reboot. At the firmware prompt, set the following firmware variables to enable auto-booting: . setenv boot-device ${OF_BOOT_DEVICE} setenv boot-file ${OF_BOOT_FILE} setenv auto-boot-timeout 5000 setenv auto-boot? true . You will only need to do this once. Afterwards, enter the "boot" command or reboot the system to proceed to your newly installed system. . Alternatively, you will be able to boot the kernel manually by entering, at the firmware prompt: . ${KERNEL_BOOT} Template: nobootloader/confirmation_powerpc_pasemi Type: note Description: Setting firmware variables for automatic boot Some variables need to be set in CFE in order for your system to boot automatically. At the end of installation, the system will reboot. At the firmware prompt, set the following variables to simplify booting: . setenv -p bootargs "${BOOTARGS}" setenv -p boot_debian "ramdisk -max=20000000 ${INITRD} ; boot ${KERNFILE}" . You will only need to do this once. This enables you to just issue the command "boot_debian" at the CFE prompt. . If you prefer to auto-boot on every startup, you can set the following variable in addition to the ones above: . setenv -p STARTUP "$boot_debian" Template: nobootloader/confirmation_common Type: note Description: No boot loader installed No boot loader has been installed, either because you chose not to or because your specific architecture doesn't support a boot loader yet. . You will need to boot manually with the ${KERNEL} kernel on partition ${BOOT} and ${ROOT} passed as a kernel argument. ********** open-iscsi ********** Template: open-iscsi/remove_even_with_active_sessions Type: boolean Description: Proceed with removing open-iscsi? There are currently active iSCSI sessions. If you remove open-iscsi now this may lead to data loss and/or hang the system at shutdown. . Do not do this if this system's root filesystem is on iSCSI. . If you do proceed, open-iscsi will try to unmount all filesystems on iSCSI and log out from current sessions. If that fails (because a filesystem is still in use), the kernel will keep the current iSCSI sessions open, but will not perform any recovery if there is an interruption of the network connection (or if the target is rebooted). . If you really intend to remove open-iscsi, you should abort here and then stop open-iscsi: . service open-iscsi stop . If that did not clean up everything, manually umount all filesystems that are on iSCSI, manually dismantle the storage stack, and only then log out from all iSCSI sessions: . iscsiadm -m node --logoutall=all . At that point, it should be safe to remove this package. Template: open-iscsi/upgrade_even_with_failed_sessions Type: boolean Description: Proceed with upgrading open-iscsi? There are currently failed iSCSI sessions. Upgrading open-iscsi may cause data loss. . If you do not proceed, the preinstallation script will be aborted and you will have the option to manually recover the iSCSI sessions. (Note that aborting an upgrade is problematic if you are dist-upgrading your entire system.) You may also recover the iSCSI sessions manually while keeping this prompt open and then choose to proceed. Or you may choose to proceed directly, after which iscsid will be restarted and session recovery will be attempted once more. Template: open-iscsi/upgrade_recovery_error Type: error Description: iSCSI recovery error on upgrade The iscsid daemon was restarted, but couldn't recover all iSCSI sessions. This is bad and could lead to data loss. Please check the system and kernel logs to determine the cause of the issue. . Please do not acknowledge this note until you have fixed the problem from a separate login shell. Template: open-iscsi/downgrade_and_break_system Type: boolean Description: Proceed with downgrading open-iscsi? You are trying to downgrade open-iscsi. Because of changes between the version you are downgrading to and the version currently installed, this downgrade will break the system. . If you really intend to downgrade, please follow the following procedure instead: umount all iSCSI file systems, log out of all iSCSI sessions, back up /etc/iscsi, purge open-iscsi, and reinstall the older version. ********** openssh-server ********** Template: openssh-server/permit-root-login Type: boolean Default: true Description: Disable SSH password authentication for root? Previous versions of openssh-server permitted logging in as root over SSH using password authentication. The default for new installations is now "PermitRootLogin prohibit-password", which disables password authentication for root without breaking systems that have explicitly configured SSH public key authentication for root. . This change makes systems more secure against brute-force password dictionary attacks on the root user (a very common target for such attacks). However, it may break systems that are set up with the expectation of being able to SSH as root using password authentication. You should only make this change if you do not need to do that. ********** partman-auto-crypto ********** Template: partman-auto-crypto/text/choice Type: text Description: Guided - use entire disk and set up encrypted LVM Template: partman-auto-crypto/erase_disks Type: boolean Default: true Description: for internal use; can be preseeded Set to false if you want to skip disk erase. ********** partman-auto-lvm ********** Template: partman-auto-lvm/text/choice Type: text Description: Guided - use entire disk and set up LVM Template: partman-auto-lvm/new_vg_name Type: string Description: Name of the volume group for the new system: Template: partman-auto-lvm/new_vg_name_exists Type: string Description: Name of the volume group for the new system: The selected volume group name is already in use. Please choose another name. Template: partman-auto-lvm/unusable_recipe Type: error Description: Failed to partition the selected disk This happened because the selected recipe does not contain any partition that can be created on LVM volumes. Template: partman-auto-lvm/no_boot Type: boolean Description: Continue installation without /boot partition? The recipe you selected does not contain a separate partition for /boot. This is normally needed to allow you to boot the system when using LVM. . You can choose to ignore this warning, but that may result in a failure to reboot the system after the installation is completed. Template: partman-auto-lvm/vg_exists Type: error Description: Volume group name already in use The volume group name used to automatically partition using LVM is already in use. Lowering the priority for configuration questions will allow you to specify an alternative name. Template: partman-auto-lvm/vg_create_error Type: error Description: Unexpected error while creating volume group Autopartitioning using LVM failed because an error occurred while creating the volume group. . Check /var/log/syslog or see virtual console 4 for the details. Template: partman-auto-lvm/text/multiple_disks Type: text Description: Multiple disks (%s) Template: partman-auto-lvm/no_such_pv Type: error Description: Non-existing physical volume A volume group definition contains a reference to a non-existing physical volume. . Please check that all devices are properly connected. Alternatively, please check the automatic partitioning recipe. Template: partman-auto-lvm/no_pv_in_vg Type: error Description: No physical volume defined in volume group The automatic partitioning recipe contains the definition of a volume group that does not contain any physical volume. . Please check the automatic partitioning recipe. ********** partman-auto-raid ********** Template: partman-auto-raid/error Type: error Description: Error while setting up RAID An unexpected error occurred while setting up a preseeded RAID configuration. . Check /var/log/syslog or see virtual console 4 for the details. Template: partman-auto-raid/recipe Type: string Description: for internal use; can be preseeded RAID recipe for automated install Template: partman-auto-raid/raidnum Type: string Description: for internal use only Initial RAID device used Template: partman-auto-raid/notenoughparts Type: error Description: Not enough RAID partitions specified There are not enough RAID partitions specified for your preseeded configuration. You need at least 3 devices for a RAID5 array. ********** partman-auto ********** Template: partman-auto/progress/title Type: text Description: Please wait... Template: partman-auto/progress/info Type: text Description: Computing the new partitions... Template: partman-auto/no_recipe Type: error Description: Failed to partition the selected disk This probably happened because the selected disk or free space is too small to be automatically partitioned. Template: partman-auto/autopartitioning_failed Type: error Description: Failed to partition the selected disk This probably happened because there are too many (primary) partitions in the partition table. Template: partman-auto/init_automatically_partition Type: select Choices-C: ${CHOICES} Choices: ${DESCRIPTIONS} Description: Partitioning method: The installer can guide you through partitioning a disk (using different standard schemes) or, if you prefer, you can do it manually. With guided partitioning you will still have a chance later to review and customise the results. . If you choose guided partitioning for an entire disk, you will next be asked which disk should be used. Template: partman-auto/disk Type: string Description: for internal use; can be preseeded Device to partition, in either devfs or non format Template: partman-auto/method Type: string Description: for internal use; can be preseeded Method to use for partitioning Template: partman-auto/automatically_partition Type: select Choices-C: ${CHOICES} Choices: ${DESCRIPTIONS} Description: Partitioning method: If you choose guided partitioning for an entire disk, you will next be asked which disk should be used. Template: partman-auto/choose_recipe Type: select Choices-C: ${CHOICES} Choices: ${DESCRIPTIONS} Description: Partitioning scheme: Selected for partitioning: . ${TARGET} . The disk can be partitioned using one of several different schemes. If you are unsure, choose the first one. Template: partman-auto/unusable_space Type: error Description: Unusable free space Partitioning failed because the chosen free space may not be used. There are probably too many (primary) partitions in the partition table. Template: partman-auto/expert_recipe_file Type: string Description: for internal use; can be preseeded File to load for expert recipe Template: partman-auto/expert_recipe Type: string Description: for internal use; can be preseeded Expert recipe content Template: partman-auto/text/automatically_partition Type: text Description: Guided partitioning Template: partman-auto/text/use_biggest_free Type: text Description: Guided - use the largest continuous free space Template: partman-auto/text/use_device Type: text Description: Guided - use entire disk Template: partman-auto/select_disk Type: select Choices-C: ${CHOICES} Choices: ${DESCRIPTIONS} Description: Select disk to partition: Note that all data on the disk you select will be erased, but not before you have confirmed that you really want to make the changes. Template: partman-auto/text/custom_partitioning Type: text Description: Manual Template: partman-auto/text/auto_free_space Type: text Description: Automatically partition the free space Template: partman-auto/text/atomic_scheme Type: text Description: All files in one partition (recommended for new users) Template: partman-auto/text/home_scheme Type: text Description: Separate /home partition Template: partman-auto/text/multi_scheme Type: text Description: Separate /home, /var, and /tmp partitions Template: partman-auto/text/small_disk Type: text Description: Small-disk (< 1GB) partitioning scheme ********** partman-base ********** Template: partman/progress/init/title Type: text Description: Starting up the partitioner Template: partman/progress/init/fallback Type: text Description: Please wait... Template: partman/progress/init/parted Type: text Description: Scanning disks... Template: partman/progress/init/update_partitions Type: text Description: Detecting file systems... Template: partman-base/devicelocked Type: error Description: Device in use No modifications can be made to the device ${DEVICE} for the following reasons: . ${MESSAGE} Template: partman-base/partlocked Type: error Description: Partition in use No modifications can be made to the partition #${PARTITION} of device ${DEVICE} for the following reasons: . ${MESSAGE} Template: partman/exception_handler Type: select Choices: ${CHOICES} Description: ${TYPE} ${DESCRIPTION} Template: partman/exception_handler_note Type: note Description: ${TYPE} ${DESCRIPTION} Template: partman/choose_partition Type: select Choices-C: ${CHOICES} Choices: ${DESCRIPTIONS} Description: This is an overview of your currently configured partitions and mount points. Select a partition to modify its settings (file system, mount point, etc.), a free space to create partitions, or a device to initialize its partition table. Template: partman/confirm_nochanges Type: boolean Default: false Description: Continue with the installation? No partition table changes and no creation of file systems have been planned. . If you plan on using already created file systems, be aware that existing files may prevent the successful installation of the base system. Template: partman/confirm Type: boolean Default: false Description: Write the changes to disks? If you continue, the changes listed below will be written to the disks. Otherwise, you will be able to make further changes manually. . WARNING: This will destroy all data on any partitions you have removed as well as on the partitions that are going to be formatted. . ${ITEMS} Template: partman/confirm_nooverwrite Type: boolean Default: false Description: Write the changes to disks? If you continue, the changes listed below will be written to the disks. Otherwise, you will be able to make further changes manually. . ${ITEMS} Template: partman/text/confirm_item_header Type: text Description: The following partitions are going to be formatted: Template: partman/text/confirm_item Type: text Description: partition #${PARTITION} of ${DEVICE} as ${TYPE} Template: partman/text/confirm_unpartitioned_item Type: text Description: ${DEVICE} as ${TYPE} Template: partman/text/confirm_partitem_header Type: text Description: The partition tables of the following devices are changed: Template: partman/storage_device Type: select Choices-C: ${CHOICES} Choices: ${DESCRIPTIONS} Description: What to do with this device: Template: partman/free_space Type: select Choices-C: ${CHOICES} Choices: ${DESCRIPTIONS} Description: How to use this free space: Template: partman/active_partition Type: select Choices-C: ${CHOICES} Choices: ${DESCRIPTIONS} Description: Partition settings: You are editing partition #${PARTITION} of ${DEVICE}. ${OTHERINFO} ${DESTROYED} Template: partman/text/there_is_detected Type: text Description: This partition is formatted with the ${FILESYSTEM}. Template: partman/text/none_detected Type: text Description: No existing file system was detected in this partition. Template: partman/text/destroyed Type: text Description: All data in it WILL BE DESTROYED! Template: partman/show_partition_chs Type: note Description: The partition starts from ${FROMCHS} and ends at ${TOCHS}. Template: partman/show_free_chs Type: note Description: The free space starts from ${FROMCHS} and ends at ${TOCHS}. Template: partman/text/please_wait Type: text Description: Please wait... Template: partman/text/formatting Type: text Description: Partitions formatting Template: partman/text/processing Type: text Description: Processing... Template: partman/text/text_template Type: text Description: ${DESCRIPTION} Template: partman/text/show_chs Type: text Description: Show Cylinder/Head/Sector information Template: partman/text/finished_with_partition Type: text Description: Done setting up the partition Template: partman/text/end_the_partitioning Type: text Description: Finish partitioning and write changes to disk Template: partman/text/undo_everything Type: text Description: Undo changes to partitions Template: partman/text/show_chs_free Type: text Description: Show Cylinder/Head/Sector information Template: partman/text/dump_partition_info Type: text Description: Dump partition info in %s Template: partman/text/free_space Type: text Description: FREE SPACE Template: partman/text/unusable Type: text Description: unusable Template: partman/text/primary Type: text Description: primary Template: partman/text/logical Type: text Description: logical Template: partman/text/pri/log Type: text Description: pri/log Template: partman/text/number Type: text Description: #%s Template: partman/text/ata_disk Type: text Description: ATA%s (%s) Template: partman/text/ata_partition Type: text Description: ATA%s, partition #%s (%s) Template: partman/text/ide_master_disk Type: text Description: IDE%s master (%s) Template: partman/text/ide_slave_disk Type: text Description: IDE%s slave (%s) Template: partman/text/ide_master_partition Type: text Description: IDE%s master, partition #%s (%s) Template: partman/text/ide_slave_partition Type: text Description: IDE%s slave, partition #%s (%s) Template: partman/text/scsi_disk Type: text Description: SCSI%s (%s,%s,%s) (%s) Template: partman/text/scsi_partition Type: text Description: SCSI%s (%s,%s,%s), partition #%s (%s) Template: partman/text/scsi_simple_disk Type: text Description: SCSI%s (%s) Template: partman/text/scsi_simple_partition Type: text Description: SCSI%s, partition #%s (%s) Template: partman/text/mmc_disk Type: text Description: MMC/SD card #%s (%s) Template: partman/text/mmc_partition Type: text Description: MMC/SD card #%s, partition #%s (%s) Template: partman/text/raid_device Type: text Description: RAID%s device #%s Template: partman/text/dmcrypt_volume Type: text Description: Encrypted volume (%s) Template: partman/text/dmraid_volume Type: text Description: Serial ATA RAID %s (%s) Template: partman/text/dmraid_part Type: text Description: Serial ATA RAID %s (partition #%s) Template: partman/text/multipath Type: text Description: Multipath %s (WWID %s) Template: partman/text/multipath_partition Type: text Description: Multipath %s (partition #%s) Template: partman/text/lvm_lv Type: text Description: LVM VG %s, LV %s Template: partman/text/zfs_volume Type: text Description: ZFS pool %s, volume %s Template: partman/text/loopback Type: text Description: Loopback (loop%s) Template: partman/text/dasd_disk Type: text Description: DASD %s (%s) Template: partman/text/dasd_partition Type: text Description: DASD %s (%s), partition #%s Template: partman/text/virtual_disk Type: text Description: Virtual disk %s (%s) Template: partman/text/virtual_partition Type: text Description: Virtual disk %s, partition #%s (%s) Template: partman/text/cancel_menu Type: text Description: Cancel this menu Template: debian-installer/partman-base/title Type: text Description: Partition disks Template: partman/early_command Type: string Description: for internal use; can be preseeded Shell command or commands to run immediately before partitioning Template: partman/default_filesystem Type: string Default: ext4 Description: for internal use; can be preseeded Default filesystem used for new partitions Template: partman/alignment Type: select Choices: cylinder, minimal, optimal Default: optimal Description: for internal use; can be preseeded Adjust the policy for starting and ending alignment of new partitions. You can generally leave this alone unless optimal alignment causes some kind of problem. . Cylinder alignment was required by very old DOS-era systems, and is not usually needed nowadays. However, a few buggy BIOSes may try to calculate cylinder/head/sector addresses for partitions and get confused if partitions aren't cylinder-aligned. . Minimal alignment ensures that new partitions are aligned to physical blocks on the disk, avoiding performance degradation that may occur with cylinder alignment particularly on modern disks. . Optimal alignment ensures that new partitions are aligned to a suitable multiple of the physical block size, guaranteeing optimal performance. ********** partman-basicfilesystems ********** Template: partman-basicfilesystems/progress_checking Type: text Description: Checking the ${TYPE} file system in partition #${PARTITION} of ${DEVICE}... Template: partman-basicfilesystems/progress_swap_checking Type: text Description: Checking the swap space in partition #${PARTITION} of ${DEVICE}... Template: partman-basicfilesystems/progress_formatting Type: text Description: Creating ${TYPE} file system in partition #${PARTITION} of ${DEVICE}... Template: partman-basicfilesystems/progress_formatting_mountable Type: text Description: Creating ${TYPE} file system for ${MOUNT_POINT} in partition #${PARTITION} of ${DEVICE}... Template: partman-basicfilesystems/progress_swap_formatting Type: text Description: Formatting swap space in partition #${PARTITION} of ${DEVICE}... Template: partman-basicfilesystems/check_failed Type: boolean Description: Go back to the menu and correct errors? The test of the file system with type ${TYPE} in partition #${PARTITION} of ${DEVICE} found uncorrected errors. . If you do not go back to the partitioning menu and correct these errors, the partition will be used as is. Template: partman-basicfilesystems/swap_check_failed Type: boolean Description: Go back to the menu and correct errors? The test of the swap space in partition #${PARTITION} of ${DEVICE} found uncorrected errors. . If you do not go back to the partitioning menu and correct these errors, the partition will be used as is. Template: partman-basicfilesystems/no_swap Type: boolean Default: true Description: Do you want to return to the partitioning menu? You have not selected any partitions for use as swap space. Enabling swap space is recommended so that the system can make better use of the available physical memory, and so that it behaves better when physical memory is scarce. You may experience installation problems if you do not have enough physical memory. . If you do not go back to the partitioning menu and assign a swap partition, the installation will continue without swap space. Template: partman-basicfilesystems/create_failed Type: error Description: Failed to create a file system The ${TYPE} file system creation in partition #${PARTITION} of ${DEVICE} failed. Template: partman-basicfilesystems/create_swap_failed Type: error Description: Failed to create a swap space The creation of swap space in partition #${PARTITION} of ${DEVICE} failed. Template: partman-basicfilesystems/no_mount_point Type: boolean Description: Do you want to return to the partitioning menu? No mount point is assigned for the ${FILESYSTEM} file system in partition #${PARTITION} of ${DEVICE}. . If you do not go back to the partitioning menu and assign a mount point from there, this partition will not be used at all. Template: partman-basicfilesystems/posix_filesystem_required Type: error Description: Invalid file system for this mount point The file system type ${FILESYSTEM} cannot be mounted on ${MOUNTPOINT}, because it is not a fully-functional Unix file system. Please choose a different file system, such as ${EXT2}. Template: partman-basicfilesystems/mountpoint Type: select Choices: / - the root file system, /boot - static files of the boot loader, /home - user home directories, /tmp - temporary files, /usr - static data, /var - variable data, /srv - data for services provided by this system, /opt - add-on application software packages, /usr/local - local hierarchy, Enter manually, Do not mount it Description: Mount point for this partition: Template: partman-basicfilesystems/fat_mountpoint Type: select Choices: /dos, /windows, Enter manually, Do not mount it Description: Mount point for this partition: Template: partman-basicfilesystems/mountpoint_manual Type: string Description: Mount point for this partition: Template: partman-basicfilesystems/bad_mountpoint Type: error Description: Invalid mount point The mount point you entered is invalid. . Mount points must start with "/". They cannot contain spaces. Template: partman-basicfilesystems/choose_label Type: string Description: Label for the file system in this partition: Template: partman-basicfilesystems/text/format_swap Type: text Description: Format the swap area: Template: partman-basicfilesystems/text/yes Type: text Description: yes Template: partman-basicfilesystems/text/no Type: text Description: no Template: partman-basicfilesystems/text/specify_label Type: text Description: Label: Template: partman-basicfilesystems/text/none Type: text Description: none Template: partman-basicfilesystems/text/reserved_for_root Type: text Description: Reserved blocks: Template: partman-basicfilesystems/specify_reserved Type: string Description: Percentage of the file system blocks reserved for the super-user: Template: partman-basicfilesystems/text/usage Type: text Description: Typical usage: Template: partman-basicfilesystems/text/typical_usage Type: text Description: standard Template: partman-basicfilesystems/specify_usage Type: select Choices: ${CHOICES} Description: Typical usage of this partition: Please specify how the file system is going to be used, so that optimal file system parameters can be chosen for that use. . standard = standard parameters, news = one inode per 4KB block, largefile = one inode per megabyte, largefile4 = one inode per 4 megabytes. Template: partman-basicfilesystems/text/specify_mountpoint Type: text Description: Mount point: Template: partman-basicfilesystems/text/no_mountpoint Type: text Description: none Template: partman/filesystem_long/ext2 Type: text Description: Ext2 file system Template: partman/filesystem_short/ext2 Type: text Description: ext2 Template: partman/filesystem_long/fat16 Type: text Description: FAT16 file system Template: partman/filesystem_short/fat16 Type: text Description: fat16 Template: partman/filesystem_long/fat32 Type: text Description: FAT32 file system Template: partman/filesystem_short/fat32 Type: text Description: fat32 Template: partman/filesystem_long/ntfs Type: text Description: NTFS journaling file system Template: partman/filesystem_short/ntfs Type: text Description: ntfs Template: partman/method_long/swap Type: text Description: swap area Template: partman/method_short/swap Type: text Description: swap Template: partman/filesystem_long/linux-swap Type: text Description: swap area Template: partman/filesystem_short/linux-swap Type: text Description: swap Template: partman-basicfilesystems/text/options Type: text Description: Mount options: Template: partman-basicfilesystems/mountoptions Type: multiselect Choices-C: ${options} Choices: ${descriptions} Description: Mount options: Mount options can tune the behavior of the file system. Template: partman-basicfilesystems/text/noatime Type: text Description: noatime - do not update inode access times at each access Template: partman-basicfilesystems/text/nodiratime Type: text Description: nodiratime - do not update directory inode access times Template: partman-basicfilesystems/text/relatime Type: text Description: relatime - update inode access times relative to modify time Template: partman-basicfilesystems/text/nodev Type: text Description: nodev - do not support character or block special devices Template: partman-basicfilesystems/text/nosuid Type: text Description: nosuid - ignore set-user-identifier or set-group-identifier bits Template: partman-basicfilesystems/text/noexec Type: text Description: noexec - do not allow execution of any binaries Template: partman-basicfilesystems/text/ro Type: text Description: ro - mount the file system read-only Template: partman-basicfilesystems/text/sync Type: text Description: sync - all input/output activities occur synchronously Template: partman-basicfilesystems/text/usrquota Type: text Description: usrquota - user disk quota accounting enabled Template: partman-basicfilesystems/text/grpquota Type: text Description: grpquota - group disk quota accounting enabled Template: partman-basicfilesystems/text/user_xattr Type: text Description: user_xattr - support user extended attributes Template: partman-basicfilesystems/text/quiet Type: text Description: quiet - changing owner and permissions does not return errors Template: partman-basicfilesystems/text/notail Type: text Description: notail - disable packing of files into the file system tree Template: partman-basicfilesystems/text/discard Type: text Description: discard - trim freed blocks from underlying block device Template: partman-basicfilesystems/text/acls Type: text Description: acls - support POSIX.1e Access Control List Template: partman-basicfilesystems/text/shortnames Type: text Description: shortnames - only use the old MS-DOS 8.3 style filenames Template: partman-basicfilesystems/boot_not_ext2 Type: boolean Description: Go back to the menu and correct this problem? Your boot partition has not been configured with the ext2 file system. This is needed by your machine in order to boot. Please go back and use the ext2 file system. . If you do not go back to the partitioning menu and correct this error, the partition will be used as is. This means that you may not be able to boot from your hard disk. Template: partman-basicfilesystems/boot_not_first_partition Type: boolean Description: Go back to the menu and correct this problem? Your boot partition is not located on the first partition of your hard disk. This is needed by your machine in order to boot. Please go back and use your first partition as a boot partition. . If you do not go back to the partitioning menu and correct this error, the partition will be used as is. This means that you may not be able to boot from your hard disk. ********** partman-basicmethods ********** Template: partman-basicmethods/method_only Type: boolean Description: Go back to the menu? No file system is specified for partition #${PARTITION} of ${DEVICE}. . If you do not go back to the partitioning menu and assign a file system to this partition, it won't be used at all. Template: partman-basicmethods/text/dont_use Type: text Description: do not use the partition Template: partman-basicmethods/text/format Type: text Description: Format the partition: Template: partman-basicmethods/text/yes_format Type: text Description: yes, format it Template: partman-basicmethods/text/no_dont_format Type: text Description: no, keep existing data Template: partman/method_long/dont_use Type: text Description: do not use Template: partman/method_short/dont_use Type: text Description: unused Template: partman/method_long/format Type: text Description: format the partition Template: partman/method_short/format Type: text Description: format Template: partman/method_long/keep Type: text Description: keep and use the existing data Template: partman/method_short/keep Type: text Description: keep ********** partman-btrfs ********** Template: partman-btrfs/text/btrfs Type: text Description: btrfs Template: partman/filesystem_long/btrfs Type: text Description: btrfs journaling file system Template: partman/filesystem_short/btrfs Type: text Description: btrfs Template: partman-btrfs/btrfs_root Type: error Description: btrfs root file system not supported without separate /boot Your root file system is a btrfs file system. This is not supported by the boot loader used by default by this installer. . You should use a small /boot partition with another file system, such as ext4. Template: partman-btrfs/btrfs_boot Type: error Description: btrfs file system not supported for /boot You have mounted a btrfs file system as /boot. This is not supported by the boot loader used by default by this installer. . You should use another file system, such as ext4, for the /boot partition. ********** partman-crypto ********** Template: partman/method_long/crypto Type: text Description: physical volume for encryption Template: partman/method_short/crypto Type: text Description: crypto Template: partman-crypto/crypto_type/dm-crypt Type: text Description: Device-mapper (dm-crypt) Template: partman-crypto/text/cryptdev_description Type: text Description: ${CIPHER} ${KEYTYPE} Template: partman-crypto/text/not_active Type: text Description: not active Template: partman-crypto/text/specify_crypto_type Type: text Description: Encryption method: Template: partman-crypto/crypto_type Type: select Choices-C: ${CHOICES} Choices: ${DESCRIPTIONS} Description: Encryption method for this partition: Changing the encryption method will set other encryption-related fields to their default values for the new encryption method. Template: partman-crypto/text/specify_cipher Type: text Description: Encryption: Template: partman-crypto/cipher Type: select Choices: ${CHOICES} Description: Encryption for this partition: Template: partman-crypto/text/specify_keysize Type: text Description: Key size: Template: partman-crypto/keysize Type: select Choices-C: ${CHOICES} Choices: ${DESCRIPTIONS} Description: Key size for this partition: Template: partman-crypto/text/specify_ivalgorithm Type: text Description: IV algorithm: Template: partman-crypto/ivalgorithm Type: select Choices-C: ${CHOICES} Choices: ${DESCRIPTIONS} Description: Initialization vector generation algorithm for this partition: Different algorithms exist to derive the initialization vector for each sector. This choice influences the encryption security. Normally, there is no reason to change this from the recommended default, except for compatibility with older systems. Template: partman-crypto/text/specify_keytype Type: text Description: Encryption key: Template: partman-crypto/keytype Type: select Choices-C: ${CHOICES} Choices: ${DESCRIPTIONS} Description: Type of encryption key for this partition: Template: partman-crypto/text/specify_keyhash Type: text Description: Encryption key hash: Template: partman-crypto/keyhash Type: select Choices-C: ${CHOICES} Choices: ${DESCRIPTIONS} Description: Type of encryption key hash for this partition: The encryption key is derived from the passphrase by applying a one-way hash function to it. Normally, there is no reason to change this from the recommended default and doing so in the wrong way can reduce the encryption strength. Template: partman-crypto/text/erase_data Type: text Description: Erase data: Template: partman-crypto/text/no_erase_data Type: text Description: no Template: partman-crypto/text/yes_erase_data Type: text Description: yes Template: partman-crypto/text/erase_data_partition Type: text Description: Erase data on this partition Template: partman-crypto/plain_warn_erase Type: boolean Default: false Description: Really erase the data on ${DEVICE}? The data on ${DEVICE} will be overwritten with zeroes. It can no longer be recovered after this step has completed. This is the last opportunity to abort the erase. Template: partman-crypto/progress/plain_erase_title Type: text Description: Erasing data on ${DEVICE} Template: partman-crypto/progress/plain_erase_text Type: text Description: The installer is now overwriting ${DEVICE} with zeroes to delete its previous contents. This step may be skipped by cancelling this action. Template: partman-crypto/plain_erase_failed Type: error Description: Erasing data on ${DEVICE} failed An error occurred while trying to overwrite the data on ${DEVICE} with zeroes. The data has not been erased. Template: partman-crypto/crypto_warn_erase Type: boolean Default: false Description: Really erase the data on ${DEVICE}? The data on ${DEVICE} will be overwritten with random data. It can no longer be recovered after this step has completed. This is the last opportunity to abort the erase. Template: partman-crypto/progress/crypto_erase_title Type: text Description: Erasing data on ${DEVICE} Template: partman-crypto/progress/crypto_erase_text Type: text Description: The installer is now overwriting ${DEVICE} with random data to prevent meta-information leaks from the encrypted volume. This step may be skipped by cancelling this action, albeit at the expense of a slight reduction of the quality of the encryption. Template: partman-crypto/crypto_erase_failed Type: error Description: Erasing data on ${DEVICE} failed An error occurred while trying to overwrite ${DEVICE} with random data. Recovery of the device's previous contents is possible and meta-information of its new contents may be leaked. Template: partman/progress/init/crypto Type: text Description: Setting up encryption... Template: partman-crypto/text/configure_crypto Type: text Description: Configure encrypted volumes Template: partman-crypto/nothing_to_setup Type: note Description: No partitions to encrypt No partitions have been selected for encryption. Template: partman-crypto/tools_missing Type: note Description: Required programs missing This build of debian-installer does not include one or more programs that are required for partman-crypto to function correctly. Template: partman-crypto/options_missing Type: error Description: Required encryption options missing The encryption options for ${DEVICE} are incomplete. Please return to the partition menu and select all required options. . ${ITEMS} Template: partman-crypto/text/missing Type: text Description: missing Template: partman-crypto/text/in_use Type: text Description: In use as physical volume for encrypted volume ${DEV} Template: partman-crypto/module_package_missing Type: error Description: Encryption package installation failure The kernel module package ${PACKAGE} could not be found or an error occurred during its installation. . It is likely that there will be problems setting up encrypted partitions when the system is rebooted. You may be able to correct this by installing the required package(s) later on. Template: partman-crypto/confirm Type: boolean Default: false Description: Write the changes to disk and configure encrypted volumes? Before encrypted volumes can be configured, the current partitioning scheme has to be written to disk. These changes cannot be undone. . After the encrypted volumes have been configured, no additional changes to the partitions on the disks containing encrypted volumes are allowed. Please decide if you are satisfied with the current partitioning scheme for these disks before continuing. . ${ITEMS} Template: partman-crypto/confirm_nochanges Type: boolean Default: false Description: Keep current partition layout and configure encrypted volumes? After the encrypted volumes have been configured, no additional changes to the partitions on the disks containing encrypted volumes are allowed. Please decide if you are satisfied with the current partitioning scheme for these disks before continuing. Template: partman-crypto/commit_failed Type: error Description: Configuration of encrypted volumes failed An error occurred while configuring encrypted volumes. . The configuration has been aborted. Template: partman-crypto/init_failed Type: error Description: Initialisation of encrypted volume failed An error occurred while setting up encrypted volumes. Template: partman-crypto/text/keytype/passphrase Type: text Description: Passphrase Template: partman-crypto/text/keytype/keyfile Type: text Description: Keyfile (GnuPG) Template: partman-crypto/text/keytype/random Type: text Description: Random key Template: partman-crypto/unsafe_swap Type: error Description: Unsafe swap space detected An unsafe swap space has been detected. . This is a fatal error since sensitive data could be written out to disk unencrypted. This would allow someone with access to the disk to recover parts of the encryption key or passphrase. . Please disable the swap space (e.g. by running swapoff) or configure an encrypted swap space and then run setup of encrypted volumes again. This program will now abort. Template: partman-crypto/passphrase Type: password Description: Encryption passphrase: You need to choose a passphrase to encrypt ${DEVICE}. . The overall strength of the encryption depends strongly on this passphrase, so you should take care to choose a passphrase that is not easy to guess. It should not be a word or sentence found in dictionaries, or a phrase that could be easily associated with you. . A good passphrase will contain a mixture of letters, numbers and punctuation. Passphrases are recommended to have a length of 20 or more characters. Template: partman-crypto/passphrase-again Type: password Description: Re-enter passphrase to verify: Please enter the same passphrase again to verify that you have typed it correctly. Template: partman-crypto/passphrase-mismatch Type: error Description: Passphrase input error The two passphrases you entered were not the same. Please try again. Template: partman-crypto/passphrase-empty Type: error Description: Empty passphrase You entered an empty passphrase, which is not allowed. Please choose a non-empty passphrase. Template: partman-crypto/weak_passphrase Type: boolean Default: false Description: Use weak passphrase? You entered a passphrase that consists of less than ${MINIMUM} characters, which is considered too weak. You should choose a stronger passphrase. Template: partman-crypto/entropy Type: entropy Description: The encryption key for ${DEVICE} is now being created. Template: partman-crypto/entropy-success Type: text Description: Key data has been created successfully. Template: partman-crypto/keyfile-problem Type: error Description: Keyfile creation failure An error occurred while creating the keyfile. Template: partman-crypto/crypto_root_needs_boot Type: error Description: Encryption configuration failure You have selected the root file system to be stored on an encrypted partition. This feature requires a separate /boot partition on which the kernel and initrd can be stored. . You should go back and setup a /boot partition. Template: partman-crypto/crypto_boot_not_possible Type: error Description: Encryption configuration failure You have selected the /boot file system to be stored on an encrypted partition. This is not possible because the boot loader would be unable to load the kernel and initrd. Continuing now would result in an installation that cannot be used. . You should go back and choose a non-encrypted partition for the /boot file system. Template: partman-crypto/use_random_for_nonswap Type: boolean Default: false Description: Are you sure you want to use a random key? You have chosen a random key type for ${DEVICE} but requested the partitioner to create a file system on it. . Using a random key type means that the partition data is going to be destroyed upon each reboot. This should only be used for swap partitions. Template: partman-crypto/install_udebs_failure Type: error Description: Failed to download crypto components An error occurred trying to download additional crypto components. Template: partman-crypto/install_udebs_low_mem Type: boolean Description: Proceed to install crypto components despite insufficient memory? There does not seem to be sufficient memory available to install additional crypto components. If you choose to go ahead and continue anyway, the installation process could fail. Template: partman-crypto/mainmenu Type: select Choices-C: create, finish Choices: Create encrypted volumes, Finish Description: Encryption configuration actions This menu allows you to configure encrypted volumes. Template: partman-crypto/create/partitions Type: multiselect Choices: ${PARTITIONS} Description: Devices to encrypt: Please select the devices to be encrypted. . You can select one or more devices. Template: partman-crypto/create/nosel Type: error Description: No devices selected No devices were selected for encryption. ********** partman-efi ********** Template: partman-target/arch_help/ia64 Type: text Description: In order to start your new system, the firmware on your Itanium system loads the boot loader from its private EFI partition on the hard disk. The boot loader then loads the operating system from that same partition. An EFI partition has a FAT16 file system formatted on it and the bootable flag set. Most installations place the EFI partition on the first primary partition of the same hard disk that holds the root file system. Template: partman-efi/text/efi Type: text Description: EFI System Partition Template: partman-efi/no_efi Type: boolean Description: Go back to the menu and resume partitioning? No EFI partition was found. Template: partman/method_long/efi Type: text Description: EFI System Partition Template: partman/method_short/efi Type: text Description: ESP Template: partman/filesystem_short/efi Type: text Description: EFI-fat16 Template: partman-efi/too_small_efi Type: error Description: EFI partition too small EFI System Partitions on this architecture cannot be created with a size less than 35 MB. Please make the EFI System Partition larger. Template: partman-efi/non_efi_system Type: boolean Description: Force UEFI installation? This machine's firmware has started the installer in UEFI mode but it looks like there may be existing operating systems already installed using "BIOS compatibility mode". If you continue to install Debian in UEFI mode, it might be difficult to reboot the machine into any BIOS-mode operating systems later. . If you wish to install in UEFI mode and don't care about keeping the ability to boot one of the existing systems, you have the option to force that here. If you wish to keep the option to boot an existing operating system, you should choose NOT to force UEFI installation here. ********** partman-ext3 ********** Template: partman-ext3/text/ext3 Type: text Description: ext3 Template: partman/filesystem_long/ext3 Type: text Description: Ext3 journaling file system Template: partman/filesystem_short/ext3 Type: text Description: ext3 Template: partman-ext3/text/ext4 Type: text Description: ext4 Template: partman/filesystem_long/ext4 Type: text Description: Ext4 journaling file system Template: partman/filesystem_short/ext4 Type: text Description: ext4 Template: partman-ext3/boot_not_ext2_or_ext3 Type: boolean Description: Go back to the menu and correct this problem? Your boot partition has not been configured with the ext2 or ext3 file system. This is needed by your machine in order to boot. Please go back and use either the ext2 or ext3 file system. . If you do not go back to the partitioning menu and correct this error, the partition will be used as is. This means that you may not be able to boot from your hard disk. Template: partman/boot_not_first_partition Type: boolean Description: Go back to the menu and correct this problem? Your boot partition is not located on the first primary partition of your hard disk. This is needed by your machine in order to boot. Please go back and use your first primary partition as a boot partition. . If you do not go back to the partitioning menu and correct this error, the partition will be used as is. This means that you may not be able to boot from your hard disk. Template: partman-ext3/boot_not_bootable Type: boolean Description: Return to the menu to set the bootable flag? The boot partition has not been marked as a bootable partition, even though this is required by your machine in order to boot. You should go back and set the bootable flag for the boot partition. . If you don't correct this, the partition will be used as is and it is likely that the machine cannot boot from its hard disk. Template: partman-ext3/bad_alignment Type: boolean Description: Do you want to return to the partitioning menu? The partition ${PARTITION} assigned to ${MOUNTPOINT} starts at an offset of ${OFFSET} bytes from the minimum alignment for this disk, which may lead to very poor performance. . Since you are formatting this partition, you should correct this problem now by realigning the partition, as it will be difficult to change later. To do this, go back to the main partitioning menu, delete the partition, and recreate it in the same position with the same settings. This will cause the partition to start at a point best suited for this disk. ********** partman-iscsi ********** Template: partman-iscsi/text/configure_iscsi Type: text Description: Configure iSCSI volumes Template: partman-iscsi/mainmenu Type: select Choices-C: login, finish Choices: Log into iSCSI targets, Finish Description: iSCSI configuration actions This menu allows you to configure iSCSI volumes. Template: partman-iscsi/login/address Type: string Description: iSCSI target portal address: Enter an IP address to scan for iSCSI targets. To use a port other than the default of 3260, use "IP:port" notation, for example "1.2.3.4:3261". Template: partman-iscsi/login/username Type: string Description: iSCSI initiator username for ${PORTAL}: Some iSCSI targets require the initiator (client) to authenticate using a username and password. If that is the case for this target, enter the username here. Otherwise, leave this blank. Template: partman-iscsi/login/password Type: password Description: iSCSI initiator password for ${PORTAL}: Enter the initiator password needed to authenticate to this iSCSI target. Template: partman-iscsi/login/incoming_username Type: string Description: iSCSI target username for ${PORTAL}: In some environments, the iSCSI target needs to authenticate to the initiator as well as the other way round. If that is the case here, enter the incoming username which the target is expected to supply. Otherwise, leave this blank. Template: partman-iscsi/login/incoming_password Type: password Description: iSCSI target password for ${PORTAL}: Enter the incoming password which the iSCSI target is expected to supply. Template: partman-iscsi/login/empty_password Type: error Description: Empty password You entered an empty password, which is not allowed. Please choose a non-empty password. Template: partman-iscsi/login/no_targets Type: error Description: No iSCSI targets discovered No iSCSI targets were discovered on ${PORTAL}. Template: partman-iscsi/login/all_targets Type: boolean Default: false Description: for internal use; can be preseeded If true, automatically log into all discovered targets. Template: partman-iscsi/login/targets Type: multiselect Choices: ${TARGETS} Description: iSCSI targets on ${PORTAL}: Select the iSCSI targets you wish to use. Template: partman-iscsi/login/failed Type: error Description: iSCSI login failed Logging into the iSCSI target ${TARGET} on ${PORTAL} failed. . Check /var/log/syslog or see virtual console 4 for the details. ********** partman-jfs ********** Template: partman-jfs/text/jfs Type: text Description: jfs Template: partman/filesystem_long/jfs Type: text Description: JFS journaling file system Template: partman/filesystem_short/jfs Type: text Description: jfs Template: partman-jfs/jfs_root Type: boolean Default: false Description: Use unrecommended JFS root file system? Your root file system is a JFS file system. This can cause problems with the boot loader used by default by this installer. . You should use a small /boot partition with another file system, such as ext3. Template: partman-jfs/jfs_boot Type: boolean Default: false Description: Use unrecommended JFS /boot file system? You have mounted a JFS file system as /boot. This is likely to cause problems with the boot loader used by default by this installer. . You should use another file system, such as ext3, for the /boot partition. ********** partman-lvm ********** Template: partman-lvm/text/configuration_freepvs Type: text Description: Unallocated physical volumes: Template: partman-lvm/text/configuration_vgs Type: text Description: Volume groups: Template: partman-lvm/text/configuration_pv Type: text Description: Uses physical volume: Template: partman-lvm/text/configuration_lv Type: text Description: Provides logical volume: Template: partman-lvm/text/configuration_none_pvs Type: text Description: none Template: partman-lvm/text/configuration_none_vgs Type: text Description: none Template: partman-lvm/text/configure_lvm Type: text Description: Configure the Logical Volume Manager Template: partman-lvm/text/pvs Type: text Description: PV Template: partman-lvm/text/in_use Type: text Description: In use by LVM volume group ${VG} Template: partman-lvm/menu/display Type: text Description: Display configuration details Template: partman-lvm/menu/createvg Type: text Description: Create volume group Template: partman-lvm/menu/deletevg Type: text Description: Delete volume group Template: partman-lvm/menu/extendvg Type: text Description: Extend volume group Template: partman-lvm/menu/reducevg Type: text Description: Reduce volume group Template: partman-lvm/menu/createlv Type: text Description: Create logical volume Template: partman-lvm/menu/deletelv Type: text Description: Delete logical volume Template: partman-lvm/menu/finish Type: text Description: Finish Template: partman-lvm/confirm Type: boolean Default: false Description: Write the changes to disks and configure LVM? Before the Logical Volume Manager can be configured, the current partitioning scheme has to be written to disk. These changes cannot be undone. . After the Logical Volume Manager is configured, no additional changes to the partitioning scheme of disks containing physical volumes are allowed during the installation. Please decide if you are satisfied with the current partitioning scheme before continuing. . ${ITEMS} Template: partman-lvm/confirm_nochanges Type: boolean Default: false Description: Keep current partition layout and configure LVM? After the Logical Volume Manager is configured, no additional changes to the partitions in the disks containing physical volumes are allowed. Please decide if you are satisfied with the current partitioning scheme in these disks before continuing. Template: partman-lvm/commit_failed Type: error Description: LVM configuration failure An error occurred while writing the changes to the disks. . Logical Volume Manager configuration has been aborted. Template: partman/method_long/lvm Type: text Description: physical volume for LVM Template: partman/method_short/lvm Type: text Description: lvm Template: debian-installer/partman-lvm/title Type: text Description: Configure the Logical Volume Manager Template: partman-lvm/mainmenu Type: select Choices-C: ${CHOICES} Choices: ${CHOICES_L10N} Description: LVM configuration action: Summary of current LVM configuration: . Free Physical Volumes: ${FREE_PVS} Used Physical Volumes: ${USED_PVS} Volume Groups: ${VGS} Logical Volumes: ${LVS} Template: partman-lvm/displayall Type: note Description: Current LVM configuration: ${CURRENT_CONFIG} Template: partman-lvm/vgcreate_parts Type: multiselect Choices: ${PARTITIONS} Description: Devices for the new volume group: Please select the devices for the new volume group. . You can select one or more devices. Template: partman-lvm/vgcreate_name Type: string Description: Volume group name: Please enter the name you would like to use for the new volume group. Template: partman-lvm/vgcreate_nosel Type: error Description: No physical volumes selected No physical volumes were selected. The creation of a new volume group has been aborted. Template: partman-lvm/vgcreate_nonamegiven Type: error Description: No volume group name entered No name for the volume group has been entered. Please enter a name. Template: partman-lvm/vgcreate_nameused Type: error Description: Volume group name already in use The selected volume group name is already in use. Please choose a different name. Template: partman-lvm/vgcreate_devnameused Type: error Description: Volume group name overlaps with device name The selected volume group name overlaps with an existing device name. Please choose a different name. Template: partman-lvm/vgcreate_error Type: error Description: Error while creating volume group The volume group ${VG} could not be created. . Check /var/log/syslog or see virtual console 4 for the details. Template: partman-lvm/vgdelete_names Type: select Choices: ${GROUPS} Description: Volume group to delete: Please select the volume group you wish to delete. Template: partman-lvm/vgdelete_novg Type: error Description: No volume group found No volume group has been found. . The volume group may have already been deleted. Template: partman-lvm/vgdelete_confirm Type: boolean Default: true Description: Really delete the volume group? Please confirm the ${VG} volume group removal. Template: partman-lvm/vgdelete_error Type: error Description: Error while deleting volume group The selected volume group could not be deleted. One or more logical volumes may currently be in use. Template: partman-lvm/vgextend_novg Type: error Description: No volume group found No volume group has been found. . No volume group can be deleted. Template: partman-lvm/vgextend_names Type: select Choices: ${GROUPS} Description: Volume group to extend: Please select the volume group you wish to extend. Template: partman-lvm/vgextend_parts Type: multiselect Choices: ${PARTITIONS} Description: Devices to add to the volume group: Please select the devices you wish to add to the volume group. . You can select one or more devices. Template: partman-lvm/vgextend_nosel Type: error Description: No physical volumes selected No physical volumes were selected. Extension of the volume group has been aborted. Template: partman-lvm/vgextend_error Type: error Description: Error while extending volume group The physical volume ${PARTITION} could not be added to the selected volume group. Template: partman-lvm/vgreduce_novg Type: error Description: No volume group found No volume group has been found. . No volume group can be reduced. Template: partman-lvm/vgreduce_names Type: select Choices: ${GROUPS} Description: Volume group to reduce: Please select the volume group you wish to reduce. Template: partman-lvm/vgreduce_parts Type: multiselect Choices: ${PARTITIONS} Description: Devices to remove from the volume group: Please select the devices you wish to remove from the volume group. . You can select one or more devices. Template: partman-lvm/vgreduce_nosel Type: error Description: No physical volumes selected No physical volumes were selected. Reduction of the volume group was aborted. Template: partman-lvm/vgreduce_error Type: error Description: Error while reducing volume group The physical volume ${PARTITION} could not be removed from the selected volume group. . Check /var/log/syslog or see virtual console 4 for the details. Template: partman-lvm/lvcreate_nofreevg Type: error Description: No volume group found No free volume groups were found for creating a new logical volume. Please create more physical volumes and volume groups, or reduce an existing volume group. Template: partman-lvm/lvcreate_name Type: string Description: Logical volume name: Please enter the name you would like to use for the new logical volume. Template: partman-lvm/lvcreate_vgnames Type: select Choices: ${GROUPS} Description: Volume group: Please select the volume group where the new logical volume should be created. Template: partman-lvm/lvcreate_nonamegiven Type: error Description: No logical volume name entered No name for the logical volume has been entered. Please enter a name. Template: partman-lvm/lvcreate_exists Type: error Description: Error while creating a new logical volume The name ${LV} is already in use by another logical volume on the same volume group (${VG}). Template: partman-lvm/lvcreate_size Type: string Description: Logical volume size: Please enter the size of the new logical volume. The size may be entered in the following formats: 10K (Kilobytes), 10M (Megabytes), 10G (Gigabytes), 10T (Terabytes). The default unit is Megabytes. Template: partman-lvm/lvcreate_error Type: error Description: Error while creating a new logical volume Unable to create a new logical volume (${LV}) on ${VG} with the new size ${SIZE}. . Check /var/log/syslog or see virtual console 4 for the details. Template: partman-lvm/lvdelete_nolv Type: error Description: No logical volume found No logical volume has been found. Please create a logical volume first. Template: partman-lvm/lvdelete_lvnames Type: select Choices: ${LVS} Description: Logical volume: Please select the logical volume to delete. Template: partman-lvm/text/lvdelete_invg Type: text Description: in VG ${VG} Template: partman-lvm/lvdelete_error Type: error Description: Error while deleting the logical volume The logical volume ${LV} on ${VG} could not be deleted. . Check /var/log/syslog or see virtual console 4 for the details. Template: partman-lvm/nopartitions Type: error Description: No usable physical volumes found No physical volumes (i.e. partitions) were found in your system. All physical volumes may already be in use. You may also need to load some required kernel modules or re-partition the hard drives. Template: partman-lvm/nolvm Type: error Description: Logical Volume Manager not available The current kernel doesn't support the Logical Volume Manager. You may need to load the lvm-mod module. Template: partman-lvm/pvcreate_error Type: error Description: Error while initializing physical volume The physical volume ${PV} could not be initialized. . Check /var/log/syslog or see virtual console 4 for the details. Template: partman-lvm/badnamegiven Type: error Description: Invalid logical volume or volume group name Logical volume or volume group names may only contain alphanumeric characters, hyphen, plus, period, and underscore. They must be 128 characters or less and may not begin with a hyphen. The names "." and ".." are not allowed. In addition, logical volume names cannot begin with "snapshot". . Please choose a different name. Template: partman-lvm/device_remove_lvm Type: boolean Default: false Description: Remove existing logical volume data? The selected device already contains the following LVM logical volumes, volume groups and physical volumes which are about to be removed: . Logical volume(s) to be removed: ${LVTARGETS} . Volume group(s) to be removed: ${VGTARGETS} . Physical volume(s) to be removed: ${PVTARGETS} . Note that this will also permanently erase any data currently on the logical volumes. Template: partman-lvm/device_remove_lvm_span Type: error Description: Unable to automatically remove LVM data Because the volume group(s) on the selected device also consist of physical volumes on other devices, it is not considered safe to remove its LVM data automatically. If you wish to use this device for partitioning, please remove its LVM data first. Template: partman-lvm/help Type: note Description: Logical Volume Management A common situation for system administrators is to find that some disk partition (usually the most important one) is short on space, while some other partition is underused. The Logical Volume Manager (LVM) can help with this. . LVM allows combining disk or partition devices ("physical volumes") to form a virtual disk ("volume group"), which can then be divided into virtual partitions ("logical volumes"). Volume groups and logical volumes may span several physical disks. New physical volumes may be added to a volume group at any time, and logical volumes can be resized up to the amount of unallocated space in the volume group. . The items on the LVM configuration menu can be used to edit volume groups and logical volumes. After you return to the main partition manager screen, logical volumes will be displayed in the same way as ordinary partitions, and should be treated as such. ********** partman-md ********** Template: partman-md/text/device Type: text Description: Software RAID device Template: partman-md/text/configure_md Type: text Description: Configure software RAID Template: partman-md/text/in_use Type: text Description: In use by software RAID device ${DEVICE} Template: partman-md/nomd Type: error Description: Software RAID not available The current kernel doesn't seem to support software RAID (MD) devices. This should be solved by loading the necessary modules. Template: partman-md/mainmenu Type: select Choices-C: create, delete, finish Choices: Create MD device, Delete MD device, Finish Description: Software RAID configuration actions This is the software RAID (or MD, "multiple device") configuration menu. . Please select one of the proposed actions to configure software RAID. Template: partman-md/createmain Type: select Choices: RAID0, RAID1, RAID5, RAID6, RAID10 Description: Software RAID device type: Please choose the type of the software RAID device to be created. Template: partman-md/noparts Type: error Description: No RAID partitions available No unused partitions of the type "Linux RAID Autodetect" are available. Please create such a partition, or delete an already used software RAID device to free its partitions. . If you have such partitions, they might contain actual file systems, and are therefore not available for use by this configuration utility. Template: partman-md/raid0devs Type: multiselect Choices: ${PARTITIONS} Description: Active devices for the RAID0 array: You have chosen to create a RAID0 array. Please choose the active devices in this array. Template: partman-md/raiddevcount Type: string Description: Number of active devices for the RAID${LEVEL} array: The RAID${LEVEL} array will consist of both active and spare devices. The active devices are those used, while the spare devices will only be used if one or more of the active devices fail. A minimum of ${MINIMUM} active devices is required. . NOTE: this setting cannot be changed later. Template: partman-md/raiddevs Type: multiselect Choices: ${PARTITIONS} Description: Active devices for the RAID${LEVEL} array: You have chosen to create a RAID${LEVEL} array with ${COUNT} active devices. . Please choose which partitions are active devices. You must select exactly ${COUNT} partitions. Template: partman-md/raidsparecount Type: string Description: Number of spare devices for the RAID${LEVEL} array: Template: partman-md/raidsparedevs Type: multiselect Choices: ${PARTITIONS} Description: Spare devices for the RAID${LEVEL} array: You have chosen to create a RAID${LEVEL} array with ${COUNT} spare devices. . Please choose which partitions will be used as spare devices. You may choose up to ${COUNT} partitions. If you choose less than ${COUNT} devices, the remaining partitions will be added to the array as "missing". You will be able to add them to the array later. Template: partman-md/notenoughparts Type: error Description: Not enough RAID partitions available There are not enough RAID partitions available for your selected configuration. You have ${NUM_PART} RAID partitions available but your configuration requires ${REQUIRED} partitions. Template: partman-md/raid10layout Type: string Default: n2 Description: Layout of the RAID10 array: The layout must be n, o, or f (arrangement of the copies) followed by a number (number of copies of each chunk). The number must be smaller or equal to the number of active devices. . The letter is the arrangement of the copies: n - near copies: Multiple copies of one data block are at similar offsets in different devices. f - far copies: Multiple copies have very different offsets o - offset copies: Rather than the chunks being duplicated within a stripe, whole stripes are duplicated but are rotated by one device so duplicate blocks are on different devices. . NOTE: this setting cannot be changed later. Template: partman-md/deletemenu Type: select Choices: ${DEVICES} Description: Software RAID device to be deleted: Deleting a software RAID device will stop it and clear the superblock of all its components. . Please note this will not immediately allow you to reuse the partitions or devices in a new software RAID device. The array will however be unusable after the deletion. . If you select a device for deletion, you will get some information about it and you will be given the option of aborting this operation. Template: partman-md/delete_no_md Type: error Description: No software RAID devices available No software RAID devices are available for deletion. Template: partman-md/deleteverify Type: boolean Default: false Description: Really delete this software RAID device? Please confirm whether you really want to delete the following software RAID device: . Device: ${DEVICE} Type: ${TYPE} Component devices: . ${DEVICES} Template: partman-md/deletefailed Type: error Description: Failed to delete the software RAID device There was an error deleting the software RAID device. It may be in use. Template: partman-md/confirm Type: boolean Default: false Description: Write the changes to the storage devices and configure RAID? Before RAID can be configured, the changes have to be written to the storage devices. These changes cannot be undone. . When RAID is configured, no additional changes to the partitions in the disks containing physical volumes are allowed. Please convince yourself that you are satisfied with the current partitioning scheme in these disks. . ${ITEMS} Template: partman-md/confirm_nochanges Type: boolean Default: false Description: Keep current partition layout and configure RAID? When RAID is configured, no additional changes to the partitions in the disks containing physical volumes are allowed. Please convince yourself that you are satisfied with the current partitioning scheme in these disks. Template: partman-md/commit_failed Type: error Description: RAID configuration failure An error occurred while writing the changes to the storage devices. . RAID configuration has been aborted. Template: partman/method_long/raid Type: text Description: physical volume for RAID Template: partman/method_short/raid Type: text Description: raid Template: partman-md/device_remove_md Type: boolean Default: false Description: Remove existing software RAID partitions? The selected device contains partitions used for software RAID devices. The following devices and partitions are about to be removed: . Software RAID devices about to be removed: ${REMOVED_DEVICES} . Partitions used by these RAID devices: ${REMOVED_PARTITIONS} . Note that this will also permanently erase any data currently on the software RAID devices. ********** partman-nbd ********** Template: partman-nbd/text/configure_nbd Type: text Description: Configure the Network Block Device Template: partman-nbd/mainmenu Type: select Choices-C: connect, disconnect, finish Choices: ${CHOICES} Description: NBD configuration action: There are currently ${NUMBER} devices connected. Template: partman-nbd/server Type: string Description: Network Block Device server: Please enter the host name or the IP address of the system running nbd-server. Template: partman-nbd/name Type: string Description: Name for NBD export Please enter the NBD export name needed to access nbd-server. The name entered here should match an existing export on the server. Template: partman-nbd/device Type: select Choices: ${CHOICES} Description: Network Block Device device node: Please select the NBD device node that you wish to connect or disconnect. Template: partman-nbd/error/noserver Type: error Description: Failed to connect to the NBD server Connecting to the nbd-server failed. Please ensure that the host and the export name which you entered are correct, that the nbd-server process is running on that host, that the network is configured correctly, and retry. Template: partman-nbd/error/nodev Type: error Description: No more Network Block Device nodes left Either all available NBD device nodes are in use or something went wrong with the detection of the device nodes. . No more NBD device nodes can be configured until a configured one is disconnected. Template: partman-nbd/error/noconnected Type: error Description: No connected Network Block Device nodes were found There are currently no Network Block Device nodes connected to any server. As such, you can't disconnect any of them. Template: partman-nbd/menu/connect Type: text Description: Connect a Network Block Device Template: partman-nbd/menu/disconnect Type: text Description: Disconnect a Network Block Device Template: partman-nbd/menu/finish Type: text Description: Finish and return to the partitioner ********** partman-partitioning ********** Template: partman-partitioning/progress_resizing Type: text Description: Resizing partition... Template: partman-partitioning/new_state Type: text Description: Computing the new state of the partition table... Template: partman-partitioning/impossible_resize Type: error Description: The resize operation is impossible Because of an unknown reason it is impossible to resize this partition. . Check /var/log/syslog or see virtual console 4 for the details. Template: partman-partitioning/confirm_resize Type: boolean Description: Write previous changes to disk and continue? Before you can select a new partition size, any previous changes have to be written to disk. . You cannot undo this operation. . Please note that the resize operation may take a long time. Template: partman-partitioning/new_size Type: string Default: some number Description: New partition size: The minimum size for this partition is ${MINSIZE} (or ${PERCENT}) and its maximum size is ${MAXSIZE}. . Hint: "max" can be used as a shortcut to specify the maximum size, or enter a percentage (e.g. "20%") to use that percentage of the maximum size. Template: partman-partitioning/bad_new_size Type: error Description: The size entered is invalid The size you entered was not understood. Please enter a positive integer size followed by an optional unit of measure (e.g. "200 GB"). The default unit of measure is the megabyte. Template: partman-partitioning/big_new_size Type: error Description: The size entered is too large The size you entered is larger than the maximum size of the partition. Please enter a smaller size to continue. Template: partman-partitioning/small_new_size Type: error Description: The size entered is too small The size you entered is smaller than the minimum size of the partition. Please enter a larger size to continue. Template: partman-partitioning/new_size_commit_failed Type: error Description: Resize operation failure An error occurred while writing the changes to the storage devices. . The resize operation has been aborted. Template: partman-partitioning/new_partition_size Type: string Default: some number Description: New partition size: The maximum size for this partition is ${MAXSIZE}. . Hint: "max" can be used as a shortcut to specify the maximum size, or enter a percentage (e.g. "20%") to use that percentage of the maximum size. Template: partman-partitioning/bad_new_partition_size Type: error Description: Invalid size Template: partman-partitioning/new_partition_place Type: select Choices: Beginning, End Description: Location for the new partition: Please choose whether you want the new partition to be created at the beginning or at the end of the available space. Template: partman-partitioning/new_partition_type Type: select Choices: Primary, Logical Description: Type for the new partition: Template: partman-partitioning/set_flags Type: multiselect Choices: ${CHOICES} Description: Flags for the new partition: Template: partman-partitioning/set_name Type: string Description: Partition name: Template: partman-partitioning/unknown_label Type: boolean Default: true Description: Continue with partitioning? This partitioner doesn't have information about the default type of the partition tables on your architecture. Please send an e-mail message to debian-boot@lists.debian.org with information. . Please note that if the type of the partition table is unsupported by libparted, then this partitioner will not work properly. Template: partman-partitioning/unsupported_label Type: boolean Default: false Description: Continue with partitioning? This partitioner is based on the library libparted which doesn't have support for the partition tables used on your architecture. It is strongly recommended that you exit this partitioner. . If you can, please help to add support for your partition table type to libparted. Template: partman-partitioning/default_label Type: string Description: for internal use; can be preseeded You may preseed this template to override the partitioner's platform-specific default choice of disk label. For example, on x86 architectures it may be useful to set this to "gpt" to cause new partition tables to be created using GPT. Template: partman-partitioning/choose_label Type: select Choices: ${CHOICES} Description: Partition table type: Select the type of partition table to use. Template: partman-partitioning/confirm_new_label Type: boolean Default: false Description: Create new empty partition table on this device? You have selected an entire device to partition. If you proceed with creating a new partition table on the device, then all current partitions will be removed. . Note that you will be able to undo this operation later if you wish. Template: partman-partitioning/confirm_write_new_label Type: boolean Default: false Description: Write a new empty partition table? Because of limitations in the current implementation of the Sun partition tables in libparted, the newly created partition table has to be written to the disk immediately. . You will NOT be able to undo this operation later and all existing data on the disk will be irreversibly removed. . Confirm whether you actually want to create a new partition table and write it to disk. Template: partman-partitioning/bootable_logical Type: boolean Default: false Description: Are you sure you want a bootable logical partition? You are trying to set the bootable flag on a logical partition. The bootable flag is generally only useful on primary partitions, so setting it on logical partitions is normally discouraged. Some BIOS versions are known to fail to boot if there is no bootable primary partition. . However, if you are sure that your BIOS does not have this problem, or if you are using a custom boot manager that pays attention to bootable logical partitions, then setting this flag may make sense. Template: partman-partitioning/text/set_flags Type: text Description: Set the partition flags Template: partman-partitioning/text/set_name Type: text Description: Name: Template: partman-partitioning/text/bootable Type: text Description: Bootable flag: Template: partman-partitioning/text/on Type: text Description: on Template: partman-partitioning/text/off Type: text Description: off Template: partman-partitioning/text/resize Type: text Description: Resize the partition (currently ${SIZE}) Template: partman-partitioning/text/delete Type: text Description: Delete the partition Template: partman-partitioning/text/new Type: text Description: Create a new partition Template: partman-partitioning/text/label Type: text Description: Create a new empty partition table on this device Template: partman/method_long/biosgrub Type: text Description: Reserved BIOS boot area Template: partman/method_short/biosgrub Type: text Description: biosgrub ********** partman-target ********** Template: partman-target/help Type: note Description: Help on partitioning Partitioning a hard drive consists of dividing it to create the space needed to install your new system. You need to choose which partition(s) will be used for the installation. . Select a free space to create partitions in it. . Select a device to remove all partitions in it and create a new empty partition table. . Select a partition to remove it or to specify how it should be used. At a bare minimum, you need one partition to contain the root of the file system (whose mount point is /). Most people also feel that a separate swap partition is a necessity. "Swap" is scratch space for an operating system, which allows the system to use disk storage as "virtual memory". . When the partition is already formatted you may choose to keep and use the existing data in the partition. Partitions that will be used in this way are marked with "${KEEP}" in the main partitioning menu. . In general you will want to format the partition with a newly created file system. NOTE: all data in the partition will be irreversibly deleted. If you decide to format a partition that is already formatted, it will be marked with "${DESTROY}" in the main partitioning menu. Otherwise it will be marked with "${FORMAT}". . ${ARCHITECTURE_HELP} Template: partman-target/arch_help/i386/generic Type: text Description: In order to start your new system, a so called boot loader is used. It can be installed either in the master boot record of the first hard disk, or in a partition. When the boot loader is installed in a partition, you must set the bootable flag for it. Such a partition will be marked with "${BOOTABLE}" in the main partitioning menu. Template: partman-target/arch_help/powerpc/powermac_newworld Type: text Description: In order to start your new system, a so called boot loader is used. It is installed in a boot partition. You must set the bootable flag for the partition. Such a partition will be marked with "${BOOTABLE}" in the main partitioning menu. Template: partman-target/same_label Type: error Description: Identical labels for two file systems Two file systems are assigned the same label (${LABEL}): ${PART1} and ${PART2}. Since file system labels are usually used as unique identifiers, this is likely to cause reliability problems later. . Please correct this by changing labels. Template: partman-target/same_mountpoint Type: error Description: Identical mount points for two file systems Two file systems are assigned the same mount point (${MOUNTPOINT}): ${PART1} and ${PART2}. . Please correct this by changing mount points. Template: partman-target/no_root Type: error Description: No root file system No root file system is defined. . Please correct this from the partitioning menu. Template: partman-target/must_be_on_root Type: error Description: Separate file system not allowed here You assigned a separate file system to ${MOUNTPOINT}, but in order for the system to start correctly this directory must be on the root file system. . Please correct this from the partitioning menu. Template: partman-target/mount_failed Type: boolean Default: true Description: Do you want to resume partitioning? The attempt to mount a file system with type ${TYPE} in ${DEVICE} at ${MOUNTPOINT} failed. . You may resume partitioning from the partitioning menu. Template: partman-target/choose_method Type: select Choices-C: ${CHOICES} Choices: ${DESCRIPTIONS} Description: How to use this partition: Template: partman-target/text/method Type: text Description: Use as: Template: partman-target/text/get_help Type: text Description: Help on partitioning Template: partman/mount_style Type: select Choices: traditional, label, uuid Default: uuid Description: for internal use; can be preseeded Normally, filesystems are mounted using a universally unique identifier (UUID) as a key; this allows them to be mounted properly even if their device name changes. UUIDs are long and difficult to read, so, if you prefer, the installer can mount filesystems based on the traditional device names, or based on a label you assign. However, note that traditional device names may change based on the order in which the kernel discovers devices at boot, which may cause the wrong filesystem to be mounted; similarly, labels are likely to clash if you plug in a new disk or a USB drive, and if that happens your system's behaviour when started will be random. . If you set "label" here, any filesystems without a label will be mounted using a UUID instead. . Devices with stable names, such as LVM logical volumes, will continue to use their traditional names rather than UUIDs. ********** partman-xfs ********** Template: partman-xfs/text/xfs Type: text Description: xfs Template: partman/filesystem_long/xfs Type: text Description: XFS journaling file system Template: partman/filesystem_short/xfs Type: text Description: xfs ********** pkgsel ********** Template: debian-installer/pkgsel/title Type: text Description: Select and install software Template: pkgsel/progress/init Type: text Description: Setting up... Template: pkgsel/upgrade Type: select Default: safe-upgrade Choices: none, safe-upgrade, full-upgrade Description: for internal use; can be preseeded type of upgrade to perform Template: pkgsel/progress/upgrade Type: text Description: Upgrading software... Template: pkgsel/progress/tasksel Type: text Description: Running tasksel... Template: pkgsel/progress/cleanup Type: text Description: Cleaning up... Template: pkgsel/include Type: string Description: for internal use; can be preseeded Comma/space-separated list of extra packages to install Template: pkgsel/progress/fallback Type: text Description: Running ${SCRIPT}... ********** popularity-contest ********** Template: popularity-contest/participate Type: boolean Default: false Description: Participate in the package usage survey? The system may anonymously supply the distribution developers with statistics about the most used packages on this system. This information influences decisions such as which packages should go on the first distribution CD. . If you choose to participate, the automatic submission script will run once every week, sending statistics to the distribution developers. The collected statistics can be viewed on http://popcon.debian.org/. . This choice can be later modified by running "dpkg-reconfigure popularity-contest". Template: popularity-contest/submiturls Type: string Description: for internal use Preseed this during installation to replace the URL used for submitting reports. ********** ppp-udeb ********** Template: debian-installer/ppp-udeb/title Type: text Description: Configure and start a PPPoE connection Template: ppp/no_concentrators Type: error Description: No PPPoE concentrator All network interfaces have been probed, but a PPPoE concentrator was not detected. . The configuration of PPPoE has been aborted. It can be attempted again by selecting the relevant menu entry. Template: ppp/interface Type: string Default: _ Description: Interface name: Please enter the name of the network interface connected to the PPPoE modem. Template: ppp/username Type: string Description: ISP account username: Please enter the username for the PPP connection. . This information should have been provided by your Internet Service Provider. Template: ppp/password Type: password Description: ISP account password: Please enter the password for the PPP connection. . This information should have been provided by your Internet Service Provider. Template: ppp/detect_failed Type: error Description: No Ethernet interface PPPoE networking cannot be configured because no Ethernet interface was detected. . The configuration of PPPoE has been aborted. It can be attempted again by selecting the relevant menu entry. Template: ppp/detect_progress Type: text Description: Searching for concentrators on ${IFACE}... Template: ppp/wrong_login Type: error Description: Failed authentication A PPPoE connection was attempted, but the provided login information was probably incorrect. . Please check the username and password you provided. . The configuration of PPPoE has been aborted. It can be attempted again by selecting the relevant menu entry. Template: ppp/unhandled Type: error Description: Unhandled error An unidentified error happened while attempting to create a connection. . The configuration of PPPoE has been aborted. It can be attempted again by selecting the relevant menu entry. Template: ppp/please_wait Type: text Description: Please wait... ********** rescue-mode ********** Template: debian-installer/rescue-mode/title Type: text Description: Enter rescue mode Template: rescue/no-partitions Type: text Description: No partitions found The installer could not find any partitions, so you will not be able to mount a root file system. This may be caused by the kernel failing to detect your hard disk drive or failing to read the partition table, or the disk may be unpartitioned. If you wish, you may investigate this from a shell in the installer environment. Template: rescue/root Type: select Choices-C: ${PARTITIONS}, assemble-raid, none Choices: ${PARTITIONS}, Assemble RAID array, Do not use a root file system Description: Device to use as root file system: Enter a device you wish to use as your root file system. You will be able to choose among various rescue operations to perform on this file system. . If you choose not to use a root file system, you will be given a reduced choice of operations that can be performed without one. This may be useful if you need to correct a partitioning problem. Template: rescue/no-such-device Type: error Description: No such device The device you entered for your root file system (${DEVICE}) does not exist. Please try again. Template: rescue/mount-failed Type: error Description: Mount failed An error occurred while mounting the device you entered for your root file system (${DEVICE}) on /target. . Please check the syslog for more information. Template: rescue/menu Type: select Choices: ${CHOICES} Description: Rescue operations Template: rescue/menu-error Type: error Description: Rescue operation failed The rescue operation '${OPERATION}' failed with exit code ${CODE}. Template: rescue/menu/shell Type: text Description: Execute a shell in ${DEVICE} Template: rescue/menu/initrd-shell Type: text Description: Execute a shell in the installer environment Template: rescue/menu/change-root Type: text Description: Choose a different root file system Template: rescue/menu/reboot Type: text Description: Reboot the system Template: rescue/shell/intro Type: text Description: Executing a shell After this message, you will be given a shell with ${DEVICE} mounted on "/". If you need any other file systems (such as a separate "/usr"), you will have to mount those yourself. Template: rescue/shell/run-failed Type: error Description: Error running shell in /target A shell (${SHELL}) was found on your root file system (${DEVICE}), but an error occurred while running it. Template: rescue/shell/not-found Type: error Description: No shell found in /target No usable shell was found on your root file system (${DEVICE}). Template: rescue/shell/title Type: text Description: Interactive shell on ${DEVICE} Template: rescue/initrd-shell/intro Type: text Description: Executing a shell After this message, you will be given a shell with ${DEVICE} mounted on "/target". You may work on it using the tools available in the installer environment. If you want to make it your root file system temporarily, run "chroot /target". If you need any other file systems (such as a separate "/usr"), you will have to mount those yourself. Template: rescue/initrd-shell/intro/no-target Type: text Description: Executing a shell After this message, you will be given a shell in the installer environment. No file systems have been mounted. Template: rescue/initrd-shell/title Type: text Description: Interactive shell in the installer environment Template: rescue/passphrase Type: password Description: Passphrase for ${DEVICE}: Please enter the passphrase for the encrypted volume ${DEVICE}. . If you don't enter anything, the volume will not be available during rescue operations. Template: rescue/assemble-raid Type: multiselect Choices-C: auto, ${PARTITIONS} Choices: Automatic, ${PARTITIONS} Description: Partitions to assemble: Select the partitions to assemble into a RAID array. If you select "Automatic", then all devices containing RAID physical volumes will be scanned and assembled. . Note that a RAID partition at the end of a disk may sometimes cause that disk to be mistakenly detected as containing a RAID physical volume. In that case, you should select the appropriate partitions individually. Template: rescue/separate-fs Type: boolean Default: true Description: Mount separate ${FILESYSTEM} partition? The installed system appears to use a separate ${FILESYSTEM} partition. . It is normally a good idea to mount it as it will allow operations such as reinstalling the boot loader. However, if the file system on ${FILESYSTEM} is corrupt then you may want to avoid mounting it. ********** resolvconf ********** Template: resolvconf/linkify-resolvconf Type: boolean Default: true Description: Prepare /etc/resolv.conf for dynamic updates? The resolvconf package contains the infrastructure required for dynamic updating of the resolver configuration file. Part of the necessary infrastructure is a symbolic link from /etc/resolv.conf to /etc/resolvconf/run/resolv.conf. If you choose this option then this link will be created; the existing /etc/resolv.conf file will be preserved as /etc/resolvconf/resolv.conf.d/original, and will be restored if this package is removed. . Declining this option will prevent future installations from recreating the symbolic link and therefore the resolver configuration file will not be dynamically updated. Dynamic updating can then be activated following instructions in the README file. . The presence of resolvconf can affect the behavior of other programs, so it should not be left installed if unconfigured. Template: resolvconf/downup-interfaces Type: note Description: Reboot recommended Suppliers of name server information such as local caching name servers and interface configurers are expected to supply name server information to the resolvconf program. However, although installation of the resolvconf package triggers them to supply their information, some of them fail to do so. . This bug would lead to loss of valid name server information on installation of the resolvconf package if the following workaround were not adopted: resolvconf includes the full contents of the pre-installation /etc/resolv.conf in its database until reboot. This has the drawback that name server information is retained even if the associated interface is later deconfigured. (This incorrect behavior is judged to be less harmful than the alternative of losing valid information.) . Until the bug in question is fixed and the workaround removed, the only way to ensure that resolvconf has fully correct name server information after the resolvconf package has been installed on a running system is to reboot the system. Template: resolvconf/reboot-recommended-after-removal Type: note Description: Reboot recommended The removal of the resolvconf package may have resulted in some information about name servers becoming unavailable. To correct this problem it is recommended that the system be rebooted. Template: resolvconf/link-tail-to-original Type: boolean Default: false Description: Append original file to dynamic file? If the original static resolver configuration file (/etc/resolv.conf) contains name server addresses, those addresses should be listed on "dns-nameservers" lines in /etc/network/interfaces. For more information, please consult the resolvconf(8) man page and the README file. . Until /etc/network/interfaces has been edited and the affected interfaces brought down and up again, the name server addresses will not be included in the dynamically generated resolver configuration file. . If you choose this option, a temporary workaround will be put in place: a symbolic link will be created (if it does not already exist) from /etc/resolvconf/resolv.conf.d/tail to /etc/resolvconf/resolv.conf.d/original. This will cause the whole of that original resolver configuration file to be appended to the dynamically generated file. . After the required "dns-nameservers" lines have been added to /etc/network/interfaces, the /etc/resolvconf/resolv.conf.d/tail link should be replaced by one to /dev/null. ********** save-logs ********** Template: debian-installer/save-logs/title Type: text Description: Save debug logs Template: save-logs/menu Type: select Choices: floppy, web, mounted file system Description: How should the debug logs be saved or transferred? Debugging log files for the installer can be saved to floppy, served up over the web, or saved to a mounted file system. Template: save-logs/directory Type: string Default: /mnt Description: Directory in which to save debug logs: Please make sure the file system you want to save debug logs on is mounted before you continue. Template: save-logs/bad_directory Type: error Description: Cannot save logs The directory "${DIR}" does not exist. Template: save-logs/no_network Type: note Description: Web server started, but network not running A simple web server has been started on this computer to serve log files and debug info. However, the network is not set up yet. The web server will be left running, and will be accessible once the network is configured. Template: save-logs/httpd_running Type: note Description: Web server started A simple web server has been started on this computer to serve log files and debug info. An index of all the available log files can be found at http://${ADDRESS}/ Template: save-logs/insert_floppy Type: note Description: Insert formatted floppy in drive Log files and debug info will be copied into this floppy. . The information will also be stored in /var/log/installer/ on the installed system. Template: save-logs/floppy_mount_failed Type: error Description: Failed to mount the floppy Either the floppy device cannot be found, or a formatted floppy is not in the drive. Template: finish-install/progress/save-logs Type: text Description: Gathering information for installation report... ********** tasksel ********** Template: tasksel/first Type: multiselect Choices-C: ${CHOICES_C} Choices: ${CHOICES} Description: Choose software to install: At the moment, only the core of the system is installed. To tune the system to your needs, you can choose to install one or more of the following predefined collections of software. Template: tasksel/tasks Type: multiselect Choices-C: ${CHOICES_C} Choices: ${CHOICES} Description: Choose software to install: You can choose to install one or more of the following predefined collections of software. Template: tasksel/desktop Type: multiselect Choices: gnome, kde, xfce, lxde, cinnamon, mate, lxqt Description: This can be preseeded to override the default desktop. Template: tasksel/title Type: title Description: Software selection ********** tzdata ********** Template: tzdata/Areas Type: select Choices: Africa, America, Antarctica, Australia, Arctic, Asia, Atlantic, Europe, Indian, Pacific, SystemV, US, Etc Description: Geographic area: Please select the geographic area in which you live. Subsequent configuration questions will narrow this down by presenting a list of cities, representing the time zones in which they are located. Template: tzdata/Zones/Africa Type: select Choices: Abidjan, Accra, Addis_Ababa, Algiers, Asmara, Bamako, Bangui, Banjul, Bissau, Blantyre, Brazzaville, Bujumbura, Cairo, Casablanca, Ceuta, Conakry, Dakar, Dar_es_Salaam, Djibouti, Douala, El_Aaiun, Freetown, Gaborone, Harare, Johannesburg, Juba, Kampala, Khartoum, Kigali, Kinshasa, Lagos, Libreville, Lome, Luanda, Lubumbashi, Lusaka, Malabo, Maputo, Maseru, Mbabane, Mogadishu, Monrovia, Nairobi, Ndjamena, Niamey, Nouakchott, Ouagadougou, Porto-Novo, Sao_Tome, Timbuktu, Tripoli, Tunis, Windhoek Description: Time zone: Please select the city or region corresponding to your time zone. Template: tzdata/Zones/America Type: select Choices: Adak, Anchorage, Anguilla, Antigua, Araguaina, Argentina/Buenos_Aires, Argentina/Catamarca, Argentina/Cordoba, Argentina/Jujuy, Argentina/La_Rioja, Argentina/Mendoza, Argentina/Rio_Gallegos, Argentina/Salta, Argentina/San_Juan, Argentina/San_Luis, Argentina/Tucuman, Argentina/Ushuaia, Aruba, Asuncion, Atikokan, Atka, Bahia, Bahia_Banderas, Barbados, Belem, Belize, Blanc-Sablon, Boa_Vista, Bogota, Boise, Cambridge_Bay, Campo_Grande, Cancun, Caracas, Cayenne, Cayman, Chicago, Chihuahua, Coral_Harbour, Costa_Rica, Creston, Cuiaba, Curacao, Danmarkshavn, Dawson, Dawson_Creek, Denver, Detroit, Dominica, Edmonton, Eirunepe, El_Salvador, Ensenada, Fort_Nelson, Fortaleza, Glace_Bay, Godthab, Goose_Bay, Grand_Turk, Grenada, Guadeloupe, Guatemala, Guayaquil, Guyana, Halifax, Havana, Hermosillo, Indiana/Indianapolis, Indiana/Knox, Indiana/Marengo, Indiana/Petersburg, Indiana/Tell_City, Indiana/Vevay, Indiana/Vincennes, Indiana/Winamac, Inuvik, Iqaluit, Jamaica, Juneau, Kentucky/Louisville, Kentucky/Monticello, Kralendijk, La_Paz, Lima, Los_Angeles, Lower_Princes, Maceio, Managua, Manaus, Marigot, Martinique, Matamoros, Mazatlan, Menominee, Merida, Metlakatla, Mexico_City, Miquelon, Moncton, Monterrey, Montevideo, Montreal, Montserrat, Nassau, New_York, Nipigon, Nome, Noronha, North_Dakota/Beulah, North_Dakota/Center, North_Dakota/New_Salem, Ojinaga, Panama, Pangnirtung, Paramaribo, Phoenix, Port-au-Prince, Port_of_Spain, Porto_Acre, Porto_Velho, Puerto_Rico, Punta_Arenas, Rainy_River, Rankin_Inlet, Recife, Regina, Resolute, Rio_Branco, Santa_Isabel, Santarem, Santiago, Santo_Domingo, Sao_Paulo, Scoresbysund, Shiprock, Sitka, St_Barthelemy, St_Johns, St_Kitts, St_Lucia, St_Thomas, St_Vincent, Swift_Current, Tegucigalpa, Thule, Thunder_Bay, Tijuana, Toronto, Tortola, Vancouver, Virgin, Whitehorse, Winnipeg, Yakutat, Yellowknife Description: Time zone: Please select the city or region corresponding to your time zone. Template: tzdata/Zones/Antarctica Type: select Choices: Casey, Davis, DumontDUrville, Macquarie, Mawson, McMurdo, Palmer, Rothera, Syowa, Troll, Vostok Description: Time zone: Please select the city or region corresponding to your time zone. Template: tzdata/Zones/Australia Type: select Choices: Adelaide, Brisbane, Broken_Hill, Canberra, Currie, Darwin, Eucla, Hobart, Lindeman, Lord_Howe, Melbourne, Perth, Sydney, Yancowinna Description: Time zone: Please select the city or region corresponding to your time zone. Template: tzdata/Zones/Arctic Type: select Choices: Longyearbyen Description: Time zone: Please select the city or region corresponding to your time zone. Template: tzdata/Zones/Asia Type: select Choices: Aden, Almaty, Amman, Anadyr, Aqtau, Aqtobe, Ashgabat, Atyrau, Baghdad, Bahrain, Baku, Bangkok, Barnaul, Beirut, Bishkek, Brunei, Chita, Choibalsan, Chongqing, Colombo, Damascus, Dhaka, Dili, Dubai, Dushanbe, Famagusta, Gaza, Harbin, Hebron, Ho_Chi_Minh, Hong_Kong, Hovd, Irkutsk, Istanbul, Jakarta, Jayapura, Jerusalem, Kabul, Kamchatka, Karachi, Kashgar, Kathmandu, Khandyga, Kolkata, Krasnoyarsk, Kuala_Lumpur, Kuching, Kuwait, Macau, Magadan, Makassar, Manila, Muscat, Nicosia, Novokuznetsk, Novosibirsk, Omsk, Oral, Phnom_Penh, Pontianak, Pyongyang, Qatar, Qyzylorda, Rangoon, Riyadh, Sakhalin, Samarkand, Seoul, Shanghai, Singapore, Srednekolymsk, Taipei, Tashkent, Tbilisi, Tehran, Tel_Aviv, Thimphu, Tokyo, Tomsk, Ujung_Pandang, Ulaanbaatar, Urumqi, Ust-Nera, Vientiane, Vladivostok, Yakutsk, Yangon, Yekaterinburg, Yerevan Description: Time zone: Please select the city or region corresponding to your time zone. Template: tzdata/Zones/Atlantic Type: select Choices: Azores, Bermuda, Canary, Cape_Verde, Faroe, Jan_Mayen, Madeira, Reykjavik, South_Georgia, St_Helena, Stanley Description: Time zone: Please select the city or region corresponding to your time zone. Template: tzdata/Zones/Europe Type: select Choices: Amsterdam, Andorra, Astrakhan, Athens, Belfast, Belgrade, Berlin, Bratislava, Brussels, Bucharest, Budapest, Busingen, Chisinau, Copenhagen, Dublin, Gibraltar, Guernsey, Helsinki, Isle_of_Man, Istanbul, Jersey, Kaliningrad, Kiev, Kirov, Lisbon, Ljubljana, London, Luxembourg, Madrid, Malta, Mariehamn, Minsk, Monaco, Moscow, Nicosia, Oslo, Paris, Podgorica, Prague, Riga, Rome, Samara, San_Marino, Sarajevo, Saratov, Simferopol, Skopje, Sofia, Stockholm, Tallinn, Tirane, Tiraspol, Ulyanovsk, Uzhgorod, Vaduz, Vatican, Vienna, Vilnius, Volgograd, Warsaw, Zagreb, Zaporozhye, Zurich Description: Time zone: Please select the city or region corresponding to your time zone. Template: tzdata/Zones/Indian Type: select Choices: Antananarivo, Chagos, Christmas, Cocos, Comoro, Kerguelen, Mahe, Maldives, Mauritius, Mayotte, Reunion Description: Time zone: Please select the city or region corresponding to your time zone. Template: tzdata/Zones/Pacific Type: select Choices: Apia, Auckland, Bougainville, Chatham, Chuuk, Easter, Efate, Enderbury, Fakaofo, Fiji, Funafuti, Galapagos, Gambier, Guadalcanal, Guam, Honolulu, Johnston, Kiritimati, Kosrae, Kwajalein, Majuro, Marquesas, Midway, Nauru, Niue, Norfolk, Noumea, Pago_Pago, Palau, Pitcairn, Pohnpei, Ponape, Port_Moresby, Rarotonga, Saipan, Samoa, Tahiti, Tarawa, Tongatapu, Truk, Wake, Wallis, Yap Description: Time zone: Please select the city or region corresponding to your time zone. Template: tzdata/Zones/SystemV Type: select Choices: AST4, AST4ADT, CST6, CST6CDT, EST5, EST5EDT, HST10, MST7, MST7MDT, PST8, PST8PDT, YST9, YST9YDT Description: Time zone: Please select the city or region corresponding to your time zone. Template: tzdata/Zones/US Type: select Choices: Alaska, Aleutian, Arizona, Central, Eastern, Hawaii, Indiana-Starke, Michigan, Mountain, Pacific, Pacific-New, Samoa Description: Time zone: Please select the city or region corresponding to your time zone. Template: tzdata/Zones/Etc Type: select Choices: GMT, GMT+0, GMT+1, GMT+10, GMT+11, GMT+12, GMT+2, GMT+3, GMT+4, GMT+5, GMT+6, GMT+7, GMT+8, GMT+9, GMT-0, GMT-1, GMT-10, GMT-11, GMT-12, GMT-13, GMT-14, GMT-2, GMT-3, GMT-4, GMT-5, GMT-6, GMT-7, GMT-8, GMT-9, GMT0, Greenwich, UCT, UTC, Universal, Zulu Description: Time zone: Please select the city or region corresponding to your time zone. ********** tzsetup-udeb ********** Template: finish-install/progress/tzsetup Type: text Description: Saving the time zone... Template: time/zone Type: select Choices-C: ${CHOICES-C} Choices: ${CHOICES} Description: ${DESCRIPTION} If the desired time zone is not listed, then please go back to the step "Choose language" and select a country that uses the desired time zone (the country where you live or are located). Template: tzsetup/text/UTC Type: text Description: Coordinated Universal Time (UTC) Template: tzsetup/descriptions/zone Type: text Description: Select your time zone: Template: tzsetup/descriptions/location Type: text Description: Select a location in your time zone: Template: tzsetup/descriptions/city Type: text Description: Select a city in your time zone: Template: tzsetup/descriptions/state Type: text Description: Select the state or province to set your time zone: Template: tzsetup/country/AQ Type: select Choices-C: Antarctica/McMurdo, Antarctica/Rothera, Antarctica/Palmer, Antarctica/Mawson, Antarctica/Davis, Antarctica/Casey, Antarctica/Vostok, Antarctica/DumontDUrville, Antarctica/Syowa Choices: McMurdo, Rothera, Palmer, Mawson, Davis, Casey, Vostok, Dumont-d'Urville, Syowa Description: location Template: tzsetup/country/AU Type: select Default: Australia/Canberra Choices-C: Australia/Canberra, Australia/Sydney, Australia/Melbourne, Australia/Darwin, Australia/Brisbane, Australia/Adelaide, Australia/Hobart, Australia/Perth, Australia/Eucla, Australia/Yancowinna, Australia/Lord_Howe Choices: Australian Capital Territory, New South Wales, Victoria, Northern Territory, Queensland, South Australia, Tasmania, Western Australia, Eyre Highway, Yancowinna County, Lord Howe Island Description: state Template: tzsetup/country/BR Type: select Default: America/Sao_Paulo Choices-C: America/Rio_Branco, America/Maceio, America/Manaus, America/Belem, America/Bahia, America/Fortaleza, America/Sao_Paulo, America/Sao_Paulo, America/Noronha, America/Sao_Paulo, America/Fortaleza, America/Sao_Paulo, America/Campo_Grande, America/Cuiaba, America/Belem, America/Fortaleza, America/Recife, America/Fortaleza, America/Sao_Paulo, America/Sao_Paulo, America/Fortaleza, America/Porto_Velho, America/Boa_Vista, America/Sao_Paulo, America/Sao_Paulo, America/Maceio, America/Sao_Paulo, America/Araguaina Choices: Acre, Alagoas, Amazonas, Amapá, Bahia, Ceará, Distrito Federal, Espírito Santo, Fernando de Noronha, Goiás, Maranhão, Minas Gerais, Mato Grosso do Sul, Mato Grosso, Pará, Paraíba, Pernambuco, Piauí, Paraná, Rio de Janeiro, Rio Grande do Norte, Rondônia, Roraima, Rio Grande do Sul, Santa Catarina, Sergipe, São Paulo, Tocantins Description: state Template: tzsetup/country/CA Type: select Default: Canada/Eastern Choices-C: Canada/Newfoundland, Canada/Atlantic, Canada/Eastern, Canada/Central, Canada/East-Saskatchewan, Canada/Saskatchewan, Canada/Mountain, Canada/Pacific Choices: Newfoundland, Atlantic, Eastern, Central, East Saskatchewan, Saskatchewan, Mountain, Pacific Description: zone Template: tzsetup/country/CD Type: select Choices-C: Africa/Kinshasa, Africa/Lubumbashi Choices: Kinshasa, Lubumbashi Default: Africa/Kinshasa Description: city Template: tzsetup/country/CL Type: select Choices-C: America/Santiago, Pacific/Easter Choices: Santiago, Easter Island Default: America/Santiago Description: zone Template: tzsetup/country/EC Type: select Choices-C: America/Guayaquil, Pacific/Galapagos Choices: Guayaquil, Galapagos Default: America/Guayaquil Description: location Template: tzsetup/country/ES Type: select Choices-C: Europe/Madrid, Africa/Ceuta, Atlantic/Canary Choices: Madrid, Ceuta, Canary Islands Default: Europe/Madrid Description: location Template: tzsetup/country/FM Type: select Choices-C: Pacific/Yap, Pacific/Truk, Pacific/Ponape, Pacific/Kosrae Choices: Yap, Truk, Pohnpei, Kosrae Default: Pacific/Ponape Description: location Template: tzsetup/country/GL Type: select Choices-C: America/Godthab, America/Danmarkshavn, America/Scoresbysund, America/Thule Choices: Godthab, Danmarkshavn, Scoresbysund, Thule Default: America/Godthab Description: location Template: tzsetup/country/ID Type: select Choices-C: Asia/Jakarta, Asia/Makassar, Asia/Jayapura Choices: Western (Sumatra\, Jakarta\, Java\, West and Central Kalimantan), Central (Sulawesi\, Bali\, Nusa Tenggara\, East and South Kalimantan), Eastern (Maluku\, Papua) Default: Asia/Jakarta Description: city Template: tzsetup/country/KI Type: select Choices-C: Pacific/Tarawa, Pacific/Enderbury, Pacific/Kiritimati Choices: Tarawa (Gilbert Islands), Enderbury (Phoenix Islands), Kiritimati (Line Islands) Default: Pacific/Tarawa Description: zone Template: tzsetup/country/KZ Type: select Choices-C: Asia/Almaty, Asia/Qyzylorda, Asia/Aqtobe, Asia/Aqtau, Asia/Oral Choices: Almaty, Qyzylorda, Aqtobe, Atyrau, Oral Default: Asia/Almaty Description: city Template: tzsetup/country/MN Type: select Choices-C: Asia/Ulaanbaatar, Asia/Hovd, Asia/Choibalsan Choices: Ulaanbaatar, Hovd, Choibalsan Default: Asia/Ulaanbaatar Description: city Template: tzsetup/country/MX Type: select Choices-C: Mexico/BajaNorte, Mexico/BajaSur, Mexico/Hermosillo, Mexico/General, Mexico/Cancun Choices: North-West, Pacific, Sonora, Central, South-East Default: Mexico/General Description: zone Template: tzsetup/country/NZ Type: select Choices-C: Pacific/Auckland, Pacific/Chatham Choices: Auckland, Chatham Islands Default: Pacific/Auckland Description: location Template: tzsetup/country/PF Type: select Choices-C: Pacific/Tahiti, Pacific/Marquesas, Pacific/Gambier Choices: Tahiti (Society Islands), Marquesas Islands, Gambier Islands Default: Pacific/Tahiti Description: location Template: tzsetup/country/PT Type: select Choices-C: Europe/Lisbon, Atlantic/Madeira, Atlantic/Azores Choices: Lisbon, Madeira Islands, Azores Default: Europe/Lisbon Description: location Template: tzsetup/country/RU Type: select Choices-C: Europe/Kaliningrad, Europe/Moscow, Europe/Samara, Asia/Yekaterinburg, Asia/Omsk, Asia/Krasnoyarsk, Asia/Irkutsk, Asia/Yakutsk, Asia/Vladivostok, Asia/Magadan Choices: Moscow-01 - Kaliningrad, Moscow+00 - Moscow, Moscow+01 - Samara, Moscow+02 - Yekaterinburg, Moscow+03 - Omsk, Moscow+04 - Krasnoyarsk, Moscow+05 - Irkutsk, Moscow+06 - Yakutsk, Moscow+07 - Vladivostok, Moscow+08 - Magadan Default: Europe/Moscow Description: zone Template: tzsetup/country/UM Type: select Choices-C: Pacific/Johnston, Pacific/Midway, Pacific/Wake Choices: Johnston Atoll, Midway Islands, Wake Island Default: Pacific/Midway Description: location Template: tzsetup/country/US Type: select Default: US/Eastern Choices-C: US/Eastern, US/Central, US/Mountain, US/Pacific, US/Alaska, US/Hawaii, US/Arizona, US/East-Indiana, US/Samoa Choices: Eastern, Central, Mountain, Pacific, Alaska, Hawaii, Arizona, East Indiana, Samoa Description: zone Template: tzsetup/country/PG Type: select Choices-C: Pacific/Port_Moresby, Pacific/Bougainville Choices: Port Moresby, Bougainville Description: zone Template: tzsetup/country/CY Type: select Choices-C: Asia/Nicosia, Asia/Famagusta Choices: Asia/Nicosia (Cyprus (most areas)), Asia/Famagusta (Northern Cyprus) Description: zone ********** ucf ********** Template: ucf/title Type: title Description: Modified configuration file Template: ucf/changeprompt_threeway Type: select Choices: install the package maintainer's version, keep the local version currently installed, show the differences between the versions, show a side-by-side difference between the versions, show a 3-way difference between available versions, do a 3-way merge between available versions (experimental), start a new shell to examine the situation Choices-C: install_new, keep_current, diff, sdiff, diff_threeway, merge_threeway, shell Default: keep_current Description: What do you want to do about modified configuration file ${BASENAME}? A new version (${NEW}) of configuration file ${FILE} is available, but the version installed currently has been locally modified. Template: ucf/changeprompt Type: select Choices: install the package maintainer's version, keep the local version currently installed, show the differences between the versions, show a side-by-side difference between the versions, start a new shell to examine the situation Choices-C: install_new, keep_current, diff, sdiff, shell Default: keep_current Description: What do you want to do about modified configuration file ${BASENAME}? A new version (${NEW}) of configuration file ${FILE} is available, but the version installed currently has been locally modified. Template: ucf/show_diff Type: note Description: Line by line differences between versions ${DIFF} Template: ucf/conflicts_found Type: error Description: Conflicts found in three-way merge Conflicts found during three-way merge! Please edit `${dest_file}' and sort them out manually. . The file `${dest_file}.${ERR_SUFFIX}' has a record of the failed merge of the configuration file. ********** user-setup-udeb ********** Template: passwd/root-password-crypted Type: password Description: for internal use only Template: passwd/user-password-crypted Type: password Description: for internal use only Template: passwd/user-uid Type: string Description: for internal use only Template: passwd/user-default-groups Type: string Default: audio cdrom dip floppy video plugdev netdev scanner bluetooth debian-tor lpadmin Description: for internal use only Template: passwd/root-login Type: boolean Default: true Description: Allow login as root? If you choose not to allow root to log in, then a user account will be created and given the power to become root using the 'sudo' command. Template: passwd/root-password Type: password Description: Root password: You need to set a password for 'root', the system administrative account. A malicious or unqualified user with root access can have disastrous results, so you should take care to choose a root password that is not easy to guess. It should not be a word found in dictionaries, or a word that could be easily associated with you. . A good password will contain a mixture of letters, numbers and punctuation and should be changed at regular intervals. . The root user should not have an empty password. If you leave this empty, the root account will be disabled and the system's initial user account will be given the power to become root using the "sudo" command. . Note that you will not be able to see the password as you type it. Template: passwd/root-password-again Type: password Description: Re-enter password to verify: Please enter the same root password again to verify that you have typed it correctly. Template: passwd/make-user Type: boolean Default: true Description: Create a normal user account now? It's a bad idea to use the root account for normal day-to-day activities, such as the reading of electronic mail, because even a small mistake can result in disaster. You should create a normal user account to use for those day-to-day tasks. . Note that you may create it later (as well as any additional account) by typing 'adduser ' as root, where is an username, like 'imurdock' or 'rms'. Template: passwd/user-fullname Type: string Description: Full name for the new user: A user account will be created for you to use instead of the root account for non-administrative activities. . Please enter the real name of this user. This information will be used for instance as default origin for emails sent by this user as well as any program which displays or uses the user's real name. Your full name is a reasonable choice. Template: passwd/username Type: string Description: Username for your account: Select a username for the new account. Your first name is a reasonable choice. The username should start with a lower-case letter, which can be followed by any combination of numbers and more lower-case letters. Template: passwd/username-bad Type: error Description: Invalid username The username you entered is invalid. Note that usernames must start with a lower-case letter, which can be followed by any combination of numbers and more lower-case letters, and must be no more than 32 characters long. Template: passwd/username-reserved Type: error Description: Reserved username The username you entered (${USERNAME}) is reserved for use by the system. Please select a different one. Template: passwd/user-password Type: password Description: Choose a password for the new user: A good password will contain a mixture of letters, numbers and punctuation and should be changed at regular intervals. Template: passwd/user-password-again Type: password Description: Re-enter password to verify: Please enter the same user password again to verify you have typed it correctly. Template: user-setup/password-mismatch Type: error Description: Password input error The two passwords you entered were not the same. Please try again. Template: user-setup/password-empty Type: error Description: Empty password You entered an empty password, which is not allowed. Please choose a non-empty password. Template: passwd/shadow Type: boolean Default: true Description: Enable shadow passwords? Shadow passwords make your system more secure because nobody is able to view even encrypted passwords. The passwords are stored in a separate file that can only be read by special programs. The use of shadow passwords is strongly recommended, except in a few cases such as NIS environments. Template: debian-installer/user-setup-udeb/title Type: title Description: Set up users and passwords Template: finish-install/progress/user-setup Type: text Description: Setting users and passwords...