Bug#989552: [patch] expand description of --variant
Package: debootstrap Severity: wishlist Tags: patch Thanks Hello please consider applying this small patch to the manpage. Kind regards Vince From 1e15507bacfb2547e1c2bace7c3781dd3ab2f45c Mon Sep 17 00:00:00 2001 From: Vincent McIntyre Date: Mon, 7 Jun 2021 20:29:08 +1000 Subject: [PATCH] Improve description of --variant A discussion on debian-boot@lists.d.o elicited an explanation of how deboostrap selects packages to install, which seems to be a point of confusion for some users While here, add a colon before the first item in the list of variants. --- debootstrap.8 | 5 - 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/debootstrap.8 b/debootstrap.8 index e3ed5d7..2527707 100644 --- a/debootstrap.8 +++ b/debootstrap.8 @@ -80,7 +80,10 @@ set this option to track them through debootstrap.log. .IP .IP "\fB\-\-variant=minbase|buildd|fakechroot\fP" Name of the bootstrap script variant to use. -Currently, the variants supported are minbase, which only includes +Debootstrap reads the Packages file and determines which packages +to install based on the \fIPriority:\fR field of each package and +the selected variant. +Currently, the variants supported are: minbase, which only includes \fIrequired\fR packages and apt; buildd, which installs the build-essential packages and fakechroot, which installs the packages without root privileges. The default, with no \fB\-\-variant=X\fP argument, is to create a -- 2.31.1 --
Bug#962925: partman-efi: improve non_efi_system question
Package: partman-efi Version: 84 Severity: minor If find the partman-efi/non_efi_system question somewhat confusing. If one sets it to 'false' that means the installer will configure the system for BIOS mode booting, even if the installer is running in EFI mode. If one sets it 'true', then even if there are partitions that look like they require non-EFI booting, the system will be set up to boot in EFI mode. The default is not indicated in the template but seems to be 'false'. I feel this could be improved by either inverting the logic of the setting or changing the question name. If we think how 'non_efi_system: false' reads (to a nonspecialist) it suggests we have an EFI(-only) system, does it not? But in fact it is intended to mean the opposite case. A better question name might be: partman-efi/efi_boot_only. This would work with the existing logic settings and I think conveys the intent of the question more clearly. I'm not sure how name changes like this are effected in d-i, presumably one adds the new one and starts a deprecation of the old one? Kind regards Vince tiny patch to show what the default setting is: diff --git a/debian/partman-efi.templates b/debian/partman-efi.templates index af3f8e4..cf766da 100644 --- a/debian/partman-efi.templates +++ b/debian/partman-efi.templates @@ -44,6 +44,7 @@ _Description: EFI partition too small Template: partman-efi/non_efi_system Type: boolean +Default: false # :sl2: _Description: Force UEFI installation? This machine's firmware has started the installer in UEFI mode but
Bug#924290: [rfc] information about EFI partitions
On Mon, Jun 01, 2020 at 02:34:40PM +1000, Vincent McIntyre wrote:
>
>Revised patch below. I'll test it on amd64 and let you know
>if it works.
This has now been tested on a number of installs and works ok.
I think it's good to go now.
The partman-efi/non_efi_system question is somewhat confusing,
but setting it to 'true' is what one wants if you want to be sure
the system boots in EFI mode.
Regards
Vince
>diff --git a/en/appendix/preseed.xml b/en/appendix/preseed.xml
>index d7570d6b3..9757883b3 100644
>--- a/en/appendix/preseed.xml
>+++ b/en/appendix/preseed.xml
>@@ -1206,6 +1211,20 @@ d-i partman-auto/choose_recipe select atomic
># system labels, volume group names and which physical devices to include
># in a volume group.
>
>+## Partitioning for EFI
>+# If your system needs an EFI partition you could add something like
>+# this to the recipe above, as the first element in the recipe:
>+# 538 538 1075 free \
>+# $iflabel{ gpt } \
>+# $reusemethod{ } \
>+# method{ efi } \
>+# format{ } \
>+# . \
>+#
>+# The fragment above is for the amd64 architecture; the details may be
>+# different on other architectures. The 'partman-auto' package in the
>+# D-I source repository may have an example you can follow.
>+
># This makes partman automatically partition without confirmation, provided
># that you told it what to do using one of the methods above.
>d-i partman-partitioning/confirm_write_new_label boolean true
>@@ -1213,6 +1232,12 @@ d-i partman/choose_partition select finish
>d-i partman/confirm boolean true
>d-i partman/confirm_nooverwrite boolean true
>
>+# Force UEFI booting ('BIOS compatibility' will be lost). Default: false.
>+#d-i partman-efi/non_efi_system boolean true
>+# Ensure the partition table is GPT - this is required for EFI
>+#d-i partman-partitioning/choose_label string gpt
>+#d-i partman-partitioning/default_label string gpt
>+
># When disk encryption is enabled, skip wiping the partitions beforehand.
>#d-i partman-auto-crypto/erase_disks boolean false
>
>
--
Bug#924290: [rfc] information about EFI partitions
On Fri, May 29, 2020 at 11:29:17PM +0200, Holger Wansing wrote:
>Hi,
>
>"McIntyre, Vincent (CASS, Marsfield)" wrote:
>> diff --git a/en/appendix/preseed.xml b/en/appendix/preseed.xml
>> index d7570d6b3..817749bb9 100644
>> --- a/en/appendix/preseed.xml
>> +++ b/en/appendix/preseed.xml
>> @@ -1206,6 +1211,20 @@ d-i partman-auto/choose_recipe select atomic
>> # system labels, volume group names and which physical devices to include
>> # in a volume group.
>>
>> +## Partitioning for EFI
>> +# If your system needs an EFI partition you could add something like
>> +# this to the recipe above, as the first element in the recipe:
>> +# 538 538 1075 free \
>> +# $iflabel{ gpt } \
>> +# $reusemethod{ } \
>> +# method{ efi } \
>> +# format{ } \
>> +# . \
>> +#
>> +# The fragment above is for the amd64 architecture; the details may be
>> +# different on other architectures. The 'partman-auto' package in the
>> +# D-I source repository may have an example you can follow.
>> +
>> # This makes partman automatically partition without confirmation, provided
>> # that you told it what to do using one of the methods above.
>> d-i partman-partitioning/confirm_write_new_label boolean true
>> @@ -1213,6 +1232,16 @@ d-i partman/choose_partition select finish
>> d-i partman/confirm boolean true
>> d-i partman/confirm_nooverwrite boolean true
>>
>> +# Force UEFI booting ('BIOS compatibility' will be lost). Default: false.
>> +#d-i partman-efi/non_efi_system boolean true
>> +# Ensure the partition table is GPT - this is required for EFI
>> +#d-i partman-basicfilesystems/choose_label string gpt
>> +#d-i partman-basicfilesystems/default_label string gpt
>> +#d-i partman-partitioning/choose_label string gpt
>> +#d-i partman-partitioning/default_label string gpt
>> +#d-i partman/choose_label string gpt
>> +#d-i partman/default_label string gpt
>
>I might wonder why this is needed: to set the same setting in three different
>packages...
>However there seem to be a reason for this?
>
I went back and double-checked (this _was_ marked RFC...).
The partman/ questions don't appear to exist, doh! Sorry about that.
partman-basicfilesystems/{choose,default}_label
refer to a +filesystem+ label, tsk. So shouldn't be needed either.
partman-partitioning/default_label
has a platform-specific default that also depends on the disk size
(packages/partman-partitioning/lib/disk-label.sh)
Revised patch below. I'll test it on amd64 and let you know
if it works.
Regards
Vince
diff --git a/en/appendix/preseed.xml b/en/appendix/preseed.xml
index d7570d6b3..9757883b3 100644
--- a/en/appendix/preseed.xml
+++ b/en/appendix/preseed.xml
@@ -1206,6 +1211,20 @@ d-i partman-auto/choose_recipe select atomic
# system labels, volume group names and which physical devices to include
# in a volume group.
+## Partitioning for EFI
+# If your system needs an EFI partition you could add something like
+# this to the recipe above, as the first element in the recipe:
+# 538 538 1075 free \
+# $iflabel{ gpt } \
+# $reusemethod{ } \
+# method{ efi } \
+# format{ } \
+# . \
+#
+# The fragment above is for the amd64 architecture; the details may be
+# different on other architectures. The 'partman-auto' package in the
+# D-I source repository may have an example you can follow.
+
# This makes partman automatically partition without confirmation, provided
# that you told it what to do using one of the methods above.
d-i partman-partitioning/confirm_write_new_label boolean true
@@ -1213,6 +1232,12 @@ d-i partman/choose_partition select finish
d-i partman/confirm boolean true
d-i partman/confirm_nooverwrite boolean true
+# Force UEFI booting ('BIOS compatibility' will be lost). Default: false.
+#d-i partman-efi/non_efi_system boolean true
+# Ensure the partition table is GPT - this is required for EFI
+#d-i partman-partitioning/choose_label string gpt
+#d-i partman-partitioning/default_label string gpt
+
# When disk encryption is enabled, skip wiping the partitions beforehand.
#d-i partman-auto-crypto/erase_disks boolean false
Bug#886642: fixed? (please default to a larger /boot for guided partitioning)
Hi I thought this would have been fixed by this commit https://salsa.debian.org/installer-team/partman-auto/-/commit/79bea1c75d2fd9fbd6eb01c1bea6de2914d24d22 which will be available in the 'daily' build of the installer. I don't know what the prospects are for having this applied to the 'stable' installer. Kind regards Vince
Bug#924290: [rfc] information about EFI partitions
On Sun, May 17, 2020 at 02:34:47PM +0200, Holger Wansing wrote:
>Hi,
>
> wrote:
>> Package: installation-guide
>> Version: 20180930
>> Severity: wishlist
>> Tags: patch
>>
>> Hi
>>
>> recently I was learning about presseding UEFI installs and
>> I think the install guide could use a small addition to make
>> that journey easier. I also sent a patch to partman-auto-recipe.txt
>> but I am sure the readership of that is much less than the d-i manual.
>
>I am unable to proof the patch correct or not, could anyone comment on that?
All I can say is It Works For Us, on plenty of amd64 installs
over the last year. The patch has evolved a little since then,
inline below. Please let me know if you'd rather a MR.
Vince
diff --git a/en/appendix/preseed.xml b/en/appendix/preseed.xml
index d7570d6b3..817749bb9 100644
--- a/en/appendix/preseed.xml
+++ b/en/appendix/preseed.xml
@@ -1206,6 +1211,20 @@ d-i partman-auto/choose_recipe select atomic
# system labels, volume group names and which physical devices to include
# in a volume group.
+## Partitioning for EFI
+# If your system needs an EFI partition you could add something like
+# this to the recipe above, as the first element in the recipe:
+# 538 538 1075 free \
+# $iflabel{ gpt } \
+# $reusemethod{ } \
+# method{ efi } \
+# format{ } \
+# . \
+#
+# The fragment above is for the amd64 architecture; the details may be
+# different on other architectures. The 'partman-auto' package in the
+# D-I source repository may have an example you can follow.
+
# This makes partman automatically partition without confirmation, provided
# that you told it what to do using one of the methods above.
d-i partman-partitioning/confirm_write_new_label boolean true
@@ -1213,6 +1232,16 @@ d-i partman/choose_partition select finish
d-i partman/confirm boolean true
d-i partman/confirm_nooverwrite boolean true
+# Force UEFI booting ('BIOS compatibility' will be lost). Default: false.
+#d-i partman-efi/non_efi_system boolean true
+# Ensure the partition table is GPT - this is required for EFI
+#d-i partman-basicfilesystems/choose_label string gpt
+#d-i partman-basicfilesystems/default_label string gpt
+#d-i partman-partitioning/choose_label string gpt
+#d-i partman-partitioning/default_label string gpt
+#d-i partman/choose_label string gpt
+#d-i partman/default_label string gpt
+
# When disk encryption is enabled, skip wiping the partitions beforehand.
#d-i partman-auto-crypto/erase_disks boolean false
daily images not deploying?
Hello I was trying to retrieve http://d-i.debian.org/daily-images/amd64/daily/netboot/debian-installer/amd64/ > and got a 404. Further investigation showed and found there were no images at all in https://d-i.debian.org/daily-images/amd64/daily/ just log files. > The last directory containing cd-rom/ hdmedia/ and netboot/ subdirectories is https://d-i.debian.org/daily-images/amd64/20200418-00:21/ Sorry if I'm behind the play here but is this expected? Kind regards Vince
Re: daily images not deploying?
(Resending to -boot, no response from -cd) Hello I was trying to retrieve http://d-i.debian.org/daily-images/amd64/daily/netboot/debian-installer/amd64/ and got a 404. Further investigation showed and found there were no images at all in https://d-i.debian.org/daily-images/amd64/daily/ just log files. The last directory containing cd-rom/ hdmedia/ and netboot/ subdirectories is https://d-i.debian.org/daily-images/amd64/20191026-00:17/ Sorry if I'm behind the play here but is this expected? Kind regards Vince PS I now see the build_netboot.log (and others) contains this failure: The following packages have unmet dependencies: haveged-udeb : Depends: libhavege2 (>= 1.9.8) but it is not installable E: Unable to correct problems, you have held broken packages.
