All of lore.kernel.org
 help / color / mirror / Atom feed
From: Taavi Ilves <ilvez@ut.ee>
To: dm-devel@redhat.com
Subject: Writing basic functions using libdevmapper.h
Date: Mon, 01 Aug 2005 17:47:34 +0300	[thread overview]
Message-ID: <42EE3606.8030003@ut.ee> (raw)

Hi!

I'm a quite C newbie, but for my school-project I need something to be 
done with device-mapper.

Problem is quite simple: I have a device-mapper device ( in /dev/mapper 
) and I must find out which loop ( or actually whatever ) device is 
behind that mapper-device device.

Example: status output with cryptsetup

# cryptsetup status /dev/mapper/secret10
/dev/mapper//dev/mapper/secret10 is active:
   cipher:  aes-cbc-plain
   keysize: 256 bits
   device:  /dev/loop/1
   offset:  0 sectors
   size:    917 sectors
   mode:    read/write

This device field is what I'm looking for. I have looked into dm-setup 
and cryptsetup too, where libdevmapper.h is being used to get such 
information, but those applications were quite advance for me to study.

So I seek documentation and maybe some simple examples to learn how to 
use libdevmapper.h . I don't need full source-code solution for my 
problem, but still I welcome anything that leads to the solution. Thanks 
ahead!

Best wishes,
Taavi Ilves

                 reply	other threads:[~2005-08-01 14:47 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=42EE3606.8030003@ut.ee \
    --to=ilvez@ut.ee \
    --cc=dm-devel@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.