https://bugzilla.novell.com/show_bug.cgi?id=338123 Cyril Hrubis changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mkoenig@novell.com AssignedTo|bnc-team-screening@forge.provo.novell.com |ro@novell.com -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=338123#c3 Ludwig Nussel changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|Major |Normal Status|NEW |RESOLVED Resolution| |WONTFIX --- Comment #3 from Ludwig Nussel 2007-11-08 03:48:30 MST --- OTOH if you have an encrypted image you want to loop mount you need the underlying filesystem mounted first. boot.crypto takes care of mount and fsck itself. Just add the device with option 'noauto' to fstab to prevent boot.localfs from mounting it. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=338123#c5 --- Comment #5 from Greg Kohring 2007-11-08 03:57:01 MST --- Hmm... The underlying file system is already mounted, i.e., the root file system is mounted rather early on, it does not get mounted by boot.localfs. Since the root file system is there, along with /dev/mapper, everything you need to create the mapped entries is present. What do you think is missing? -- 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.