FS#15679 - tell user about editing HOOKS in rc.conf and grub kernel line if using dm_crypt/lvm
Attached to Project:
Release Engineering
Opened by Dieter Plaetinck (Dieter_be) - Saturday, 25 July 2009, 10:26 GMT
Last edited by Dieter Plaetinck (Dieter_be) - Wednesday, 29 July 2009, 21:27 GMT
Opened by Dieter Plaetinck (Dieter_be) - Saturday, 25 July 2009, 10:26 GMT
Last edited by Dieter Plaetinck (Dieter_be) - Wednesday, 29 July 2009, 21:27 GMT
|
Details
12:19:02 <Dieterbe> we expect the user to configure
their menu.lst themselves, autogenerating the correct kernel
line is still a todo item
12:19:30 <brain0> in each case, you should use cryptdevice=... for encryption 12:20:03 <brain0> lvm2 + encrypted logical volume: HOOKS="... lvm2 encrypt ..." cryptdevice=/dev/vgname/lvname:root root=/dev/mapper/root 12:20:46 <brain0> encrypted lvm2 pv + root on a lv: HOOKS="... encrypt lvm2 ..." cryptdevice=/dev/sda6:somename_that_doesnt_matter root=/dev/vgname/root 12:21:08 <brain0> so depending on the setup, it might look completely different 12:21:24 <Dieterbe> IIRC we tell the user to update HOOKS when updating rc.conf and the kernel line when doing grub's menu.lst, but i'm not 100% sure 12:23:11 <brain0> we should add notes that encryption requires explicit modifications in those files just a reminder: we should check if aif tells the user about editing HOOKS in rc.conf and the kernel line in grubs menu.lst, if he's using lvm/dm_crypt |
This task depends upon
Closed by Dieter Plaetinck (Dieter_be)
Wednesday, 29 July 2009, 21:27 GMT
Reason for closing: Implemented
Wednesday, 29 July 2009, 21:27 GMT
Reason for closing: Implemented
But if all went well, they shouldn't even be needed, as both of them should be correct automatically now, for normal, encrypted, lvm and combinations of that setups