Re: Bug#626641: cryptsetup: bug #587220 re-introduced

2011-05-17 Thread Christoph Anton Mitterer
On Mon, 16 May 2011 22:35:12 -0300, Henrique de Moraes Holschuh wrote: > Then, 'stop' tries to close all managed crypto devices and aborts *with > an error* if it cannot. 'Start' tries to open all managed crypto > devices, and aborts *with an error* if it cannot. > > And 'restart' should not be

Re: Bug#626641: cryptsetup: bug #587220 re-introduced

2011-05-16 Thread Henrique de Moraes Holschuh
On Tue, 17 May 2011, Jonas Meurer wrote: > > I tire of this thread. There are apparently bugs in the initscripts, well, > > if that's correct, just get them fixed. Then, the package will not allow > > itself to be removed with crypt disks still active in the first place. > > > > It'd have to swi

Re: Bug#626641: cryptsetup: bug #587220 re-introduced

2011-05-16 Thread Jonas Meurer
Hey, On 15/05/2011 Henrique de Moraes Holschuh wrote: > On Mon, 16 May 2011, Christoph Anton Mitterer wrote: > > With the most recent upload (and this is the very reason why I've reopened > > the bug), you can have the situation (package removed but not pruged) where > > you say: > > /etc/init.d/c

Re: Bug#626641: cryptsetup: bug #587220 re-introduced

2011-05-15 Thread Henrique de Moraes Holschuh
On Mon, 16 May 2011, Christoph Anton Mitterer wrote: > With the most recent upload (and this is the very reason why I've reopened > the bug), you can have the situation (package removed but not pruged) where > you say: > /etc/init.d/cryptdisks stop > and it gives you just $? = 0, as /lib/cryptsetup

Re: Bug#626641: cryptsetup: bug #587220 re-introduced

2011-05-15 Thread Christoph Anton Mitterer
On Sun, 15 May 2011 18:18:39 -0300, Henrique de Moraes Holschuh wrote: > OTOH, all it takes to handle a dm-crypt device you forgot open is the > direct use of dmsetup, or simply reinstalling cryptsetup. Or a system > reboot/reset. Or a system power off. A system power off or dropping the mapping

Re: Bug#626641: cryptsetup: bug #587220 re-introduced

2011-05-15 Thread Henrique de Moraes Holschuh
On Sun, 15 May 2011, Christoph Anton Mitterer wrote: > And honestly, I don't see much of a difference with the warnings > when removing the running kernel or are there any bigger > problems that modules that should be newly loaded would not be > found?! An immediate panic makes it impossible f

Re: Bug#626641: cryptsetup: bug #587220 re-introduced

2011-05-15 Thread Christoph Anton Mitterer
Hey... I really don't wanna step on anyone's toes, especially not Jonas' (as I'm in many cases quite satisfied and happy with his work for cryptsetup), but sometimes I really wonder why this is packaged for Debian at all, as it seems that it's merely intended to be a toy, and not to be us