On Fri, November 10, 2006 15:53, Mike Paul said: > On Fri, 2006-11-10 at 09:09 +0100, David Härdeman wrote: >> On Fri, November 10, 2006 8:25, Miroslav Kure said: >> > On Thu, Nov 09, 2006 at 10:47:25PM -0500, Mike Paul wrote: >> >> Problem description: >> >> >> >> The partitioner treats the resulting encrypted volume like a raw >> hard >> >> drive -- it wants to put a partition table on it, and there's no >> way >> >> to use it directly as e.g. swapspace or a physical volume for LVM. >> > >> > Seems like a duplicate of #393728 >> >> Indeed, and fixing it would probably require major surgery to partman-md >> so that it doesn't wipe and recreate its state each time partman >> restarts. >> >> Perhaps we need to disable crypto-on-md for Etch...(as Max said in >> #393728) > > Oops, yes, it's a duplicate. I didn't realize partman-crypto is a > separate package, or I'd have checked its existing bug reports. > > Crypto-on-md works correctly in beta3 though... how could it have > gotten into a state where major surgery is needed to get it back? :-/
That was based on Max's analysis of the underlying problems, so not first-hand knowledge. There might be a simpler root cause though. I'm not sure when I'll have time to investigate this further... -- David Härdeman -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]