Re: [arch-general] New kernel packages and mkinitcpio hooks
Hi, I have a question regarding the kernel changes. It sounds like it might break my dm-crypt/luks setup with un-encrypted /boot partition, if the kernel is not in /boot anymore? Are there migration steps needed? I set it up exactly following the wiki. It is my understanding that it is the kernel who handles the password prompt and decryption. Or am I misunderstanding how it works? Ondrej Hruska
Ondřej Hruška <ondra@ondrovo.com> on Mon, 2019/11/11 09:18:
Hi, I have a question regarding the kernel changes.
It sounds like it might break my dm-crypt/luks setup with un-encrypted /boot partition, if the kernel is not in /boot anymore? Are there migration steps needed? I set it up exactly following the wiki.
It is my understanding that it is the kernel who handles the password prompt and decryption. Or am I misunderstanding how it works?
You have (sd-)encrypt hook in your mkinitcpio configuration. That does the work and that does not change. No extra action is to be taken. -- 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 Mon, 11 Nov 2019 at 09:18, Ondřej Hruška <ondra@ondrovo.com> wrote:
Hi, I have a question regarding the kernel changes.
It sounds like it might break my dm-crypt/luks setup with un-encrypted /boot partition, if the kernel is not in /boot anymore?
the kernel is no longer installed in /boot by the kernel package, but by post-install mkinitcpio scripts. So it ends back there in /boot anyway. -- damjan
participants (3)
-
Christian Hesse
-
Damjan Georgievski
-
Ondřej Hruška