On 2017-01-04 16:29, Andrei Borzenkov wrote:
As long as you do "zypper dup" I do not expect any more problems than you may experience during normal package update.
ok, at least i can hope so, i have made not so good experience with such fiddling on most other mainstream distros
Looks like it. I wholeheartedly agree that p.2 is plain bug and it should be possible to manually enable encryption at least in the same configuration which installer offers. And it is not possible to enable encryption for LVM even without RAID at all (strictly speaking, the problem is that it is not possible to create encrypted partition). encryption for lvm without raid works as far as i could tell, also when manually creating. you have to enable the encryption when creating the lvm partitions on the physical drives, not when creating the lvm itself.
As for p.3 - I did it in the past so in general it should work. There could be arbitrary problems using new shiny tools, so YMMV. Unfortunately this will remain so until someone actually spends time and efforts to build and debug such configuration. ok, looks like i have to give it another shot. but somehow i didn't even get a password prompt at bootup for decrypting
although there is a bug in the installer that sometimes doesn't let you check the encryption checkbox even if it's supported for the current configuration. in that cases it helps to switch the listbox to a different filesystem / partitiontype, when switching back to what you want the checkbox gets enabled (not so for btrfs on md devices) the disks when i manually created the luks volume on the software raid, although the installer played just fine with the configuration. do you remember what configuration worked for you? raid -> luks -> lvm -> btrfs? -- Daniel Selinger, CEO Sourcy Software & Services GmbH Feldgasse 97, 3400 Kierling, Austria W: https://sourcy.io E: d.selinger@sourcy.io -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org