Comment 26 for bug 82528

Celso Pinto wrote:
> Right, I'm a bit hot headed now so bear with me: I've just shut down my
> laptop, which was applying Hardy's upgrades (152 IIRC), because as soon
> as it started to actually install the packages my desktop completely
> locked up. I put up with it for about *30 f****** minutes* until I
> decided I actually needed to get some work done instead of watching the
> disk access led blinking while kcryptd did it's stuff. Come on guys!
> Come on! I replaced openSUSE 10.3 which also had luks encryption and was
> a whole lot more responsive with Hardy to give it a shot.
<snip rant>

I feel your pain man. Seems like they focus on other things, and this
is not a hot feature in the marketplace. To be fair though, isn't this
a kernel issue? Maybe Novell do extra fixes in their kernels to get
certain features working, whilst Canonical focuses on desktop stuff.
Suppose that if we want a working dmcrypt, then we need to stick to
Suse/Redhat. I swapped to CentOS5 on my server just because of this
issue (not dmcrypt, as it sucks as bad there cause its an old kernel,
but there is more focus on the server side than I think canonical does).

--andrew