Sure, I just tested it and I get to the (same) Result I was getting while performing preliminary Investigations. The boot time is around 22 Seconds (down from the Original 300 Seconds).
So it's Good, from what I can tell :).
# Test Procedure & Log
# Pin noble-proposed Packages with Lower Priority by Default
create /etc/apt/preferences.d/proposed-updates if it doesn't exist yet
###########################################################################
# Configure apt to allow selective installs of packages from proposed
Package: *
Pin: release a=noble-proposed
Pin-Priority: 400
###########################################################################
# Pin DHCPCD Packages with Maximum Priority
create /etc/apt/preferences.d/dhcpcd-proposed
# Priority is higher on noble-proposed, so that's good
# This means that a Package Upgrade will be performed
```
dhcpcd-base:
Installed: 1:10.0.6-1ubuntu3
Candidate: 1:10.0.6-1ubuntu3.1
Version table:
1:10.0.6-3 1
1 http://ftp.dk.debian.org/debian testing/main amd64 Packages
1:10.0.6-1ubuntu3.1 1000
400 http://archive.ubuntu.com/ubuntu noble-proposed/main amd64 Packages
*** 1:10.0.6-1ubuntu3 500
500 http://archive.ubuntu.com/ubuntu noble/main amd64 Packages
100 /var/lib/dpkg/status
1:10.0.2-3ubuntu3 1
1 http://archive.ubuntu.com/ubuntu mantic/main amd64 Packages
9.4.1-24~deb12u3 1
1 http://ftp.dk.debian.org/debian bookworm/main amd64 Packages
```
# Update Repositories
apt update
# Print Current Date
date
2024-05-10T13:32:00 CEST
# Before Upgrade
ls -l /usr/lib/dhcpcd/dhcpcd-hooks/30-hostname
-rw-r--r-- 1 root root 3764 May 9 09:42 /usr/lib/dhcpcd/dhcpcd-hooks/30-hostname
# Upgrade Package
apt dist-upgrade
# After Upgrade
ls -l /usr/lib/dhcpcd/dhcpcd-hooks/30-hostname
-rw-r--r-- 1 root root 3764 May 7 12:12 /usr/lib/dhcpcd/dhcpcd-hooks/30-hostname
# After Upgrade - Excerpt of the File Contents
```
set_hostname()
{
hfqdn=false hshort=false
case "$hostname_fqdn" in [Yy][Ee][Ss]|[Tt][Rr][Uu][Ee]|1) hfqdn=true;; ""|[Ss][Ee][Rr][Vv][Ee][Rr]) ;;
*) hshort=true;;
esac
need_hostname || return 0
```
# Final Remarks
The last line looks Good (it reflects the correct Fix, i.e. the `|| return` got modified into `|| return 0`).
Not sure why the File has a timestamp "so old" though (May 7 12:12), probably this is the time when the patch was written (https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2064926/comments/32).
Hello Timo.
Sure, I just tested it and I get to the (same) Result I was getting while performing preliminary Investigations. The boot time is around 22 Seconds (down from the Original 300 Seconds).
So it's Good, from what I can tell :).
# Test Procedure & Log
# Pin noble-proposed Packages with Lower Priority by Default preferences. d/proposed- updates if it doesn't exist yet ####### ####### ####### ####### ####### ####### ####### ####### ####### ##### ####### ####### ####### ####### ####### ####### ####### ####### ####### #####
create /etc/apt/
#######
# Configure apt to allow selective installs of packages from proposed
Package: *
Pin: release a=noble-proposed
Pin-Priority: 400
#######
# Pin DHCPCD Packages with Maximum Priority preferences. d/dhcpcd- proposed
create /etc/apt/
####### ####### ####### ####### ####### ####### ####### ####### ####### ####### ##### ####### ####### ####### ####### ####### ####### ####### ####### ####### #####
Package: dhcpcd dhcpcd-base dhcpcd5 dhcpcd-base-dbgsym
Pin: release a=noble-proposed
Pin-Priority: 1000
#######
# View Pinning Policy
apt policy dhcpcd-base
# Priority is higher on noble-proposed, so that's good ftp.dk. debian. org/debian testing/main amd64 Packages 10.0.6- 1ubuntu3. 1 1000 archive. ubuntu. com/ubuntu noble-proposed/main amd64 Packages archive. ubuntu. com/ubuntu noble/main amd64 Packages dpkg/status 10.0.2- 3ubuntu3 1 archive. ubuntu. com/ubuntu mantic/main amd64 Packages 4.1-24~ deb12u3 1 ftp.dk. debian. org/debian bookworm/main amd64 Packages
# This means that a Package Upgrade will be performed
```
dhcpcd-base:
Installed: 1:10.0.6-1ubuntu3
Candidate: 1:10.0.6-1ubuntu3.1
Version table:
1:10.0.6-3 1
1 http://
1:
400 http://
*** 1:10.0.6-1ubuntu3 500
500 http://
100 /var/lib/
1:
1 http://
9.
1 http://
```
# Update Repositories
apt update
# Print Current Date
date
2024-05-10T13:32:00 CEST
# Before Upgrade dhcpcd/ dhcpcd- hooks/30- hostname dhcpcd/ dhcpcd- hooks/30- hostname
ls -l /usr/lib/
-rw-r--r-- 1 root root 3764 May 9 09:42 /usr/lib/
# Upgrade Package
apt dist-upgrade
# After Upgrade dhcpcd/ dhcpcd- hooks/30- hostname dhcpcd/ dhcpcd- hooks/30- hostname
ls -l /usr/lib/
-rw-r--r-- 1 root root 3764 May 7 12:12 /usr/lib/
# After Upgrade - Excerpt of the File Contents
hshort= false
[Yy][Ee] [Ss]|[Tt] [Rr][Uu] [Ee]|1) hfqdn=true;;
""|[Ss] [Ee][Rr] [Vv][Ee] [Rr]) ;;
```
set_hostname()
{
hfqdn=false
case "$hostname_fqdn" in
*) hshort=true;;
esac
```
# Final Remarks /bugs.launchpad .net/ubuntu/ +source/ initramfs- tools/+ bug/2064926/ comments/ 32).
The last line looks Good (it reflects the correct Fix, i.e. the `|| return` got modified into `|| return 0`).
Not sure why the File has a timestamp "so old" though (May 7 12:12), probably this is the time when the patch was written (https:/
# Reboot
update-initramfs -k all -u; update-grub; update-initramfs -k all; update-grub; reboot
# Save dmesg
dmesg
# Save initramfs debug log initramfs. debug
cat /run/initramfs/
# Save systemd-analze
systemd-analyze
Startup finished in 22.809s (kernel) + 53.824s (userspace) = 1min 16.634s
graphical.target reached after 53.811s in userspace.