---------------------------------------- From: Giancarlo Razzolini via arch-general <arch-general@archlinux.org> Sent: Thu Oct 31 14:55:47 CET 2019 To: General Discussion about Arch Linux <arch-general@archlinux.org> Cc: Giancarlo Razzolini <grazzolini@archlinux.org> Subject: Re: [arch-general] new packaging of the kernel/mkinitcpio/kmod
Hi Damjan,
The kernel does not install itself anymore to /boot, as you've noticed. But, the mkinitcpio hook does that. For now, we are replicating the same behavior as before, but with a little more flexibility.
I'm working on dracut hooks for doing a similar job, but the idea is that we eventually will be more flexible with our booting, giving the user more options. Keep an eye on the Arch announce mailing list, as well as the news on the Arch site.
As for your hooks, we made so that the mkinitcpio hook runs at the same step the previous linux hook would. So, there shouldn't be any incompatibilities. But, it depends on what your hooks are. Also, you can completely override the mkinitcpio hooks by linking their filenames to /dev/null on /etc/pacmand.d/hooks directory. But you'll be left doing the kernel installation on your own.
Regards, Giancarlo Razzolini
What was the reason for not using kernel-install[1] standard instead of all of those Arch's exclusive hooks again?? https://www.freedesktop.org/software/systemd/man/kernel-install.html Yours sincerely G. K.