Also one thing that made me file this bug under mountall is that cryptsetup-encrypted /tmp has worked for me for many previous Ubuntu version and suddently fails after upgrading to Karmic.
I don't believe that cryptsetup was much changed between Jaunty and Karmic, while the system startup sequence and the way filesystems are mounted has been deeply modified.
Observing that this (from a sysadmin PoV) results in a regression - something that used to work doesn't anymore - it looks quite obvious to me that the cause of the regression relates to what has been modified in a major way, not to what stayed the same but the overall result is that it doesn't work anymore...
And also, I could hardly consider that starting up a system with some fstab-defined filesystems unmounted is not a "bug"... of a serious kind, again from a sysadmin PoV.
Also one thing that made me file this bug under mountall is that cryptsetup- encrypted /tmp has worked for me for many previous Ubuntu version and suddently fails after upgrading to Karmic.
I don't believe that cryptsetup was much changed between Jaunty and Karmic, while the system startup sequence and the way filesystems are mounted has been deeply modified.
Observing that this (from a sysadmin PoV) results in a regression - something that used to work doesn't anymore - it looks quite obvious to me that the cause of the regression relates to what has been modified in a major way, not to what stayed the same but the overall result is that it doesn't work anymore...
And also, I could hardly consider that starting up a system with some fstab-defined filesystems unmounted is not a "bug"... of a serious kind, again from a sysadmin PoV.