Thanks for info. It came out that hal didn't work for me because of some bugs in KDE. Marek Aaron Sapota On Sunday 30 November 2008 19:53:11 Jan Engelhardt wrote: > On Sunday 2008-11-30 19:22, projects.gg.aaron@xxxxxxxxx wrote: > >Trying to reproduce it I found what happened - I've made ext3 filesystem > > on file before I did cryptsetup luksFormat, but shouldn't it overwrite > > ext3 filesystem? > > There is no reason to explicitly zero the device - it would take much too > long. It simply writes the LUKS header. Since ext3's header begins some > 16-32KB from the start of the device, nothing is lost unless you start > making a filesystem on the crypto device (/dev/mapper/...). > > >One more question - can hal be made to recognize luks and automount such > >devices? > > It already does recognize them as I gather from developers. > > --------------------------------------------------------------------- > dm-crypt mailing list - http://www.saout.de/misc/dm-crypt/ > To unsubscribe, e-mail: dm-crypt-unsubscribe@xxxxxxxx > For additional commands, e-mail: dm-crypt-help@xxxxxxxx
Attachment:
signature.asc
Description: This is a digitally signed message part.
