found 406697 2:1.0.4+svn26-1
found 406697 2:1.0.4-8
severity 406697 minor
thanks
On Wed, Jan 17, 2007 at 12:15:56PM +0100, Frans Pop wrote:
On Wednesday 17 January 2007 11:32, you wrote:
> Does _not_ seem to be the case. Here's the entire do_stop function
> from /lib/cryptsetup/cryptdisks.funct
On Wednesday 17 January 2007 11:32, you wrote:
> > Does _not_ seem to be the case. Here's the entire do_stop function
> > from /lib/cryptsetup/cryptdisks.functions on my box and I see no
> > calls to 'crytsetup remove' (indentation reduced a bit):
>
> Umm...but there is one to "do_close"?
Hmm. Rig
On Wed, January 17, 2007 11:02, Frans Pop said:
> On Wednesday 17 January 2007 10:23, you wrote:
>> In "do_stop" there is a call to "do_close" which does "cryptsetup
>> remove" or "cryptsetup luksClose" (if the use count of the device is
>> 0).
>
> Does _not_ seem to be the case. Here's the entire
On Wednesday 17 January 2007 10:23, you wrote:
> In "do_stop" there is a call to "do_close" which does "cryptsetup
> remove" or "cryptsetup luksClose" (if the use count of the device is
> 0).
Does _not_ seem to be the case. Here's the entire do_stop function from
/lib/cryptsetup/cryptdisks.functio
On Wed, January 17, 2007 1:18, Frans Pop said:
> On Wednesday 17 January 2007 00:47, Frans Pop wrote:
>> According to Marco d'Itri the /dev/md-* node _is_ removed if the
>> command 'cryptsetup remove $NAME"' is used to bring down a crypto
>> volume (I've not tested this myself).
>
> I've just confi
5 matches
Mail list logo
