View previous topic :: View next topic |
Author |
Message |
haVok n00b
Joined: 21 May 2013 Posts: 49
|
Posted: Wed May 22, 2013 10:03 pm Post subject: [SOLVED]: efistub and luks |
|
|
I will be doing a uefi install, but wanted to make sure I have all the info I need before I start. As before with a luks encrypted root i.e. with grub the kernel parameters had cryptdevice=/dev/sdaX:volgroup. Now with just using efistub and without grub, the wiki on efistub under (configuration enable built in kernel parameters), is that where I would like my cryptdevice=/dev/sdaX:volgroup? and and other parameters?
Last edited by haVok on Tue Jun 04, 2013 4:21 am; edited 2 times in total |
|
Back to top |
|
|
BradN Advocate
Joined: 19 Apr 2002 Posts: 2391 Location: Wisconsin (USA)
|
Posted: Thu May 23, 2013 1:25 am Post subject: |
|
|
I think that sounds reasonable - another place it can be done is inside the kernel config itself. |
|
Back to top |
|
|
srs5694 Guru
Joined: 08 Mar 2004 Posts: 434 Location: Woonsocket, RI
|
Posted: Thu May 30, 2013 1:46 pm Post subject: |
|
|
I've never used LUKS, but in theory, there are at least three options, depending on how you launch the kernel:
- Built into the kernel itself, as you suggest.
- If you launch the kernel from the firmware's built-in boot manager, you can add options to the NVRAM-resident set of options by using efibootmgr in Linux, bcfg in an EFI shell, or a similar tool.
- If you launch the kernel from a boot manager like rEFInd or gummiboot, you can pass the options using whatever mechanism the boot manager provides (typically in a configuration file, similar to what LILO or GRUB uses).
|
|
Back to top |
|
|
BradN Advocate
Joined: 19 Apr 2002 Posts: 2391 Location: Wisconsin (USA)
|
Posted: Thu May 30, 2013 7:16 pm Post subject: |
|
|
Doh, I gotta read slower, I suggested the same thing he did, I thought he was talking about setting it up in the EFI from some of the other words around it... |
|
Back to top |
|
|
|