https://bugzilla.novell.com/show_bug.cgi?id=724113 https://bugzilla.novell.com/show_bug.cgi?id=724113#c0 Summary: systemd: doesn't mount my encrypted /home Classification: openSUSE Product: openSUSE 12.1 Version: Factory Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: lnussel@suse.com ReportedBy: ke@suse.com QAContact: qa@suse.de CC: lnussel@suse.com, ke@suse.com, suse-beta@cboltz.de, vuntz@suse.com, fcrozat@suse.com Found By: --- Blocker: --- +++ This bug was initially created as a clone of Bug #716136 +++ Christian Boltz 2011-10-09 19:33:46 CEST If the example is changed to use "nofail", then the sentence Simply remove this flag. should be changed to Simply replace the "noauto" flag with "nofail". That said: I'd really welcome if this was fixed automatically by YaST or zypper dup. Shouldn't be too hard IMHO - the following sed command in %post of cryptsetup (or another package) should work: (Warning: untested!) sed -i '/^\/dev/mapper/cr_/ s/,noauto,nofail/' etc/fstab [reply] [-] Private Comment 13 Christian Boltz 2011-10-10 12:32:25 CEST (In reply to comment #12)
dup. Shouldn't be too hard IMHO - the following sed command in %post of cryptsetup (or another package) should work: (Warning: untested!) sed -i '/^\/dev/mapper/cr_/ s/,noauto,nofail/' etc/fstab
Argh, obviously untested :-/ sed -i '/^\/dev\/mapper\/cr_/ s/,noauto,/nofail/' etc/fstab Untested again, but at least the syntax should be correct now ;-) Christian Boltz 2011-10-13 21:25:58 CEST (In reply to comment #15)
I'm unsure what package would fix this on upgrades anyway
The boot.crypto initscript and /etc/crypttab are both owned by cryptsetup, which is maintained by Ludwig. I'm sure he's a better assignee than the screening team for this bug. Ludwig, what do you think about fixing this bug with sed on /etc/fstab in %post of cryptsetup? See comment #13 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.