Small question about mkinitcpio and linux.preset
Hello folks, With the latest update of mkinitcpio when running `mkinitcpio -P` you get the following warning: ``` WARNING: Deprecated option 'ALL_microcode' found. Update '/etc/mkinitcpio.d/linux.preset' to use the 'microcode' hook instead. ``` It is clear to me that this is because that option must be removed from the `/etc/mkinitcpio.d/linux.preset` file, but what surprises me is the following: ``` % pacman -Qo /etc/mkinitcpio.d/linux.preset error: No package owns /etc/mkinitcpio.d/linux.preset ``` Who generated the `linux.preset`? It is supposed to have been the `linux` package but right now I can't find how this file was generated. If someone could explain to me how this file is generated at the time of installation I would be very grateful. Greetings. -- Óscar García Amor | ogarcia at moire.org | http://ogarcia.me
On Sat, Mar 09, 2024 at 12:52:15PM +0100, Óscar García Amor wrote:
Hello folks,
With the latest update of mkinitcpio when running `mkinitcpio -P` you get the following warning:
``` WARNING: Deprecated option 'ALL_microcode' found. Update '/etc/mkinitcpio.d/linux.preset' to use the 'microcode' hook instead. ```
It is clear to me that this is because that option must be removed from the `/etc/mkinitcpio.d/linux.preset` file, but what surprises me is the following:
``` % pacman -Qo /etc/mkinitcpio.d/linux.preset error: No package owns /etc/mkinitcpio.d/linux.preset ```
Who generated the `linux.preset`? It is supposed to have been the `linux` package but right now I can't find how this file was generated.
They are generated by a libalpm hook that templates the preset file. Template: https://gitlab.archlinux.org/archlinux/mkinitcpio/mkinitcpio/-/blob/master/m... The hook: https://gitlab.archlinux.org/archlinux/mkinitcpio/mkinitcpio/-/blob/master/l... -- Morten Linderud PGP: 9C02FF419FECBE16
El sáb, 09-03-2024 a las 13:19 +0100, Morten Linderud escribió:
They are generated by a libalpm hook that templates the preset file.
Template: https://gitlab.archlinux.org/archlinux/mkinitcpio/mkinitcpio/-/blob/master/m...
The hook: https://gitlab.archlinux.org/archlinux/mkinitcpio/mkinitcpio/-/blob/master/l...
Many many thanks Morten, the truth is that I was going crazy thinking, but where does this come from? Greetings. -- Óscar García Amor | ogarcia at moire.org | http://ogarcia.me
Running `pacman -Qo <path/to/file>` usually, should tell you which packages own the file. -- Best Regards, Abraham Sent with Tutanota; https://tuta.com
On 24/03/09 06:08PM, Abraham S.A.H. wrote:
Running `pacman -Qo <path/to/file>` usually, should tell you which packages own the file.
This mechanic specifically does not work in this case because the files in question are not owned by a specific package (only created by the install file of a certain package). $ pacman -Qqo /etc/mkinitcpio.d/linux.preset error: No package owns /etc/mkinitcpio.d/linux.preset Cheers, gromit
(only created by the install file of a certain package).
Many thanks, I did know about this case. -- Best Regards, Abraham Sent with Tutanota; https://tuta.com
participants (4)
-
Abraham S.A.H.
-
Christian Heusel
-
Morten Linderud
-
Óscar García Amor