Mkinitcpio update - dealing with the pacnew

I’ve updated mkinitcpio to the latest v33-1 which hit the Arch repos today. During the update process the following warning appeared:

warning: /etc/mkinitcpio.conf installed as /etc/mkinitcpio.conf.pacnew

When I run eos-pacdiff to view the differences between the two files, there are a number of lines in blue where (in some cases at least) the differences seem to be accounted for by decisions made during installation, or choices made by :enos:

At the bottom of the pacnew file is a section in green as follows:

# MODULES_DECOMPRESS
# Decompress kernel modules during initramfs creation.
# Enable to speedup boot process, disable to save RAM
# during early userspace. Switch (yes/no).
#MODULES_DECOMPRESS="yes"

which appears to be a new option, and is not enabled.

My interpretation of all the differences is that I should leave the lines in blue in my existing /etc/mkinitcpio.conf unchanged, and, if I want to, add the new section from the pacnew at the bottom of the file.

Is my interpretation correct?

Can we see the diff? Just do a normal diff of the two files.

$ diff mkinitcpio.conf mkinitcpio.conf.pacnew
6,7c6,7
< #     MODULES=(piix ide_disk reiserfs)
< MODULES=""
---
> #     MODULES=(usbhid xhci_hcd)
> MODULES=()
19c19
< FILES="/crypto_keyfile.bin"
---
> FILES=()
32c32
< ##   No raid, lvm2, or encrypted root is needed.
---
> ##   No RAID, lvm2, or encrypted root is needed.
37c37
< #    HOOKS=(base udev autodetect block filesystems)
---
> #    HOOKS=(base udev autodetect modconf block filesystems fsck)
41c41
< #    HOOKS=(base udev block filesystems)
---
> #    HOOKS=(base udev modconf block filesystems fsck)
43,45c43,45
< ##   This setup assembles a pata mdadm array with an encrypted root FS.
< ##   Note: See 'mkinitcpio -H mdadm' for more information on raid devices.
< #    HOOKS=(base udev block mdadm encrypt filesystems)
---
> ##   This setup assembles a mdadm array with an encrypted root file system.
> ##   Note: See 'mkinitcpio -H mdadm_udev' for more information on RAID devices.
> #    HOOKS=(base udev modconf keyboard keymap consolefont block mdadm_udev encrypt filesystems fsck)
47,48c47,48
< ##   This setup loads an lvm2 volume group on a usb device.
< #    HOOKS=(base udev block lvm2 filesystems)
---
> ##   This setup loads an lvm2 volume group.
> #    HOOKS=(base udev modconf block lvm2 filesystems fsck)
51,52c51,52
< #    usr, fsck and shutdown hooks.
< HOOKS="base udev autodetect modconf block keyboard keymap consolefont encrypt filesystems fsck"
---
> #    usr and fsck hooks.
> HOOKS=(base udev autodetect modconf kms keyboard keymap consolefont block filesystems fsck)
57c57
< COMPRESSION="zstd"
---
> #COMPRESSION="zstd"
67a68,73
> 
> # MODULES_DECOMPRESS
> # Decompress kernel modules during initramfs creation.
> # Enable to speedup boot process, disable to save RAM
> # during early userspace. Switch (yes/no).
> #MODULES_DECOMPRESS="yes"

Strange i have the new mkinitcpio and no change. No /etc/mkinitcpio.conf.pacnew exists.

Edit: Probably because i just recently reinstalled my Kde desktop. :wink:

Yes, you can either add this part to the bottom or do nothing.

1 Like

Thank you :smiley:

1 Like

Did you choose to encrypt your installation?

No… i didn’t only because it takes longer to load if using grub. On systemd-boot it loads fast but on grub it’s slow.

That probably accounts for it. At least some of the differences in my post above relate to encryption.

I’m still a grubber… if that’s the correct collective noun :upside_down_face:

Me too …i just grub along! :rofl:

1 Like

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.