[arch-general] New kernel packages and mkinitcpio hooks? What does this mean to the average user?
All, I have read the latest note from 11-10-19 at archlinux.org, e.g. New kernel packages and mkinitcpio hooks https://www.archlinux.org/news/new-kernel-packages-and-mkinitcpio-hooks/ However, I'm still left confused exactly "What this means to the average user?" When I read: <quote> All our official kernels: linux, linux-lts, linux-zen and linux-hardened, do not install the actual kernel to /boot anymore. The installation is done by mkinitcpio hooks and scripts, as well as removals. There is no need for any manual intervention. ... </quote> That tells me that I am not going to have to change the way I update kernels and that I won't have to do anything special to ensure all current hooks are run (mdadm_udev, etc...). The only changes I see in the mkinitcpio.pacnew file is that all double-quotes have been replaced by parenthesis, e.g. HOOKS="base udev autodetect modconf block mdadm_udev filesystems keyboard fsck" to HOOKS=(base udev autodetect modconf block mdadm_udev filesystems keyboard fsck) Which appears to effectively turn HOOKS into a bash array instead of a simple list/string. But beyond that I don't see anything that will have an impact on how kernels are installed or removed on update. Am I missing something there? -- David C. Rankin, J.D.,P.E.
"David C. Rankin" <drankinatty@suddenlinkmail.com> on Mon, 2019/11/11 04:50:
The only changes I see in the mkinitcpio.pacnew file is that all double-quotes have been replaced by parenthesis, e.g.
That is a change back from March 2017 and appeared in mkinitcpio v24: https://git.archlinux.org/mkinitcpio.git/commit/?id=c5ad00c2e565eaae8e8b02b9... -- main(a){char*c=/* Schoene Gruesse */"B?IJj;MEH" "CX:;",b;for(a/* Best regards my address: */=0;b=c[a++];) putchar(b-1/(/* Chris cc -ox -xc - && ./x */b/42*2-3)*42);}
On 11/11/2019 04:54 AM, Christian Hesse wrote:
That is a change back from March 2017 and appeared in mkinitcpio v24:
POSIX list/bash array ... meh.. both work :) So I guess the rest of the answer would be that normal users won't have anything they need to do differently to manage their current hooks as this change plays out? -- David C. Rankin, J.D.,P.E.
Em novembro 11, 2019 13:39 David C. Rankin escreveu:
On 11/11/2019 04:54 AM, Christian Hesse wrote:
That is a change back from March 2017 and appeared in mkinitcpio v24:
POSIX list/bash array ... meh.. both work :)
So I guess the rest of the answer would be that normal users won't have anything they need to do differently to manage their current hooks as this change plays out?
The announcement is regarding new libalpm hooks, not mkinitcpio hooks. As I've said, no manual intervention is needed *at all*. Regards, Giancarlo Razzolini
participants (3)
-
Christian Hesse
-
David C. Rankin
-
Giancarlo Razzolini