* [dm-crypt] where is dm_task_create implemented?
@ 2009-12-14 19:18 Chris Cross
2009-12-14 19:45 ` Milan Broz
0 siblings, 1 reply; 2+ messages in thread
From: Chris Cross @ 2009-12-14 19:18 UTC (permalink / raw)
To: dm-crypt
[-- Attachment #1: Type: text/plain, Size: 278 bytes --]
Hi
I'm trying to figure out how "cryptsetup create" works so I'm looking at
dm_create_device() in libdevmapper.c. Can you tell me where the function
dm_task_create() is implemented? I actually don't see lidevmapper.c
compiled when I build cryptsetup...
Thanks,
Chris
[-- Attachment #2: Type: text/html, Size: 329 bytes --]
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: [dm-crypt] where is dm_task_create implemented?
2009-12-14 19:18 [dm-crypt] where is dm_task_create implemented? Chris Cross
@ 2009-12-14 19:45 ` Milan Broz
0 siblings, 0 replies; 2+ messages in thread
From: Milan Broz @ 2009-12-14 19:45 UTC (permalink / raw)
To: Chris Cross; +Cc: dm-crypt
On 12/14/2009 08:18 PM, Chris Cross wrote:
> I'm trying to figure out how "cryptsetup create" works so I'm looking at
> dm_create_device() in libdevmapper.c. Can you tell me where the function
> dm_task_create() is implemented? I actually don't see lidevmapper.c
> compiled when I build cryptsetup...
dm_task_create is implemented in libdevmapper, the device-mapper library.
libdevmapper.c (the only suported backend) must be compiled in otherwise cryptsetup
will not work (there is no other backend implemented).
Please be sure you are using recent source code, old code allowed compilation
without libdevmapper library resulting in non-functional code.
See http://code.google.com/p/cryptsetup/source/checkout
Milan
--
mbroz@redhat.com
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2009-12-14 19:45 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2009-12-14 19:18 [dm-crypt] where is dm_task_create implemented? Chris Cross
2009-12-14 19:45 ` Milan Broz
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox