http://bugzilla.suse.com/show_bug.cgi?id=909912 http://bugzilla.suse.com/show_bug.cgi?id=909912#c40 Franck Bui <fbui@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|systemd-maintainers@suse.de |ancor@suse.com --- Comment #40 from Franck Bui <fbui@suse.com> --- (In reply to Ancor Gonzalez Sosa from comment #39)
So I'm afraid of opening the can of worms behind the second option. Implementing the first one looks like a safer bet to me.
Using /dev/mapper/xxx in fstab looks safe at a first glance since this path should be stable across reboots. And the major advantage of this solution is that if new options must be added/modified in the future, this can be done simply (especially during updates) by fixing the cryptsetup generator. OTOH fixing fstab to add the new options doesn't seem appealing. But if you feel that implementing the other solution is safer then fine. Anyway, it seems that the fix will belong to YaST, so I'm re-assigning the bug accordingly. Hope that makes sense. -- You are receiving this mail because: You are on the CC list for the bug.