All of lore.kernel.org
 help / color / mirror / Atom feed
From: Uwe Menges <uwe.menges@web.de>
To: Peter Rajnoha <prajnoha@redhat.com>
Cc: dm-crypt@saout.de, "Thomas Bächler" <thomas@archlinux.org>,
	"Milan Broz" <mbroz@redhat.com>
Subject: Re: [dm-crypt] 1.1.0rc2: device-mapper: remove ioctl failed: Device or	resource busy
Date: Fri, 23 Oct 2009 15:41:58 +0200	[thread overview]
Message-ID: <4AE1B2A6.9040805@web.de> (raw)
In-Reply-To: <4AE07AD6.9020701@redhat.com>

Peter Rajnoha wrote:
> Maybe some important notes and problems we already know about and track:
>  
>  - these rules change the layout in /dev a little:
>      - the nodes are created in /dev directly with the name of dm-X
>        (this is internal kernel name that is not the same as actual DM name)

Is this really necessary? I tried to find out what the motivation is for
that, and I came across a posting from you where you state:
  "The reason for doing so is that creating nodes root /dev directory is
considered to be the "standard way"."

I'm currently on Ubuntu 9.04 and I don't have any /dev/dm-* devices,
only /dev/mapper/* (eg. "raid5-root"), which have much more meaning for
humans. The system works, so there seems to be no actual need for
/dev/dm-* devices.

Maybe it's time to loosen the "standard way". I have the strong feeling
that we're going backwards with respect to usability if eg. df reports
meaningless /dev/dm-* names, so the human has to look up what this
actually means.

Yours, Uwe

  reply	other threads:[~2009-10-23 13:41 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-20  8:35 [dm-crypt] 1.1.0rc2: device-mapper: remove ioctl failed: Device or resource busy Thomas Bächler
2009-10-20  8:55 ` Milan Broz
2009-10-20  9:07   ` Thomas Bächler
     [not found]   ` <4ADD9876.8000006@redhat.com>
2009-10-20 12:13     ` Thomas Bächler
2009-10-20 12:53       ` Peter Rajnoha
2009-10-20 13:05         ` Thomas Bächler
2009-10-20 13:29           ` Peter Rajnoha
2009-10-22 13:36       ` Peter Rajnoha
2009-10-22 15:01         ` Thomas Bächler
2009-10-22 15:31           ` Peter Rajnoha
2009-10-23 13:41             ` Uwe Menges [this message]
2009-10-23 13:57               ` Milan Broz
  -- strict thread matches above, loose matches on Subject: below --
2009-10-20  7:29 Thomas Bächler

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=4AE1B2A6.9040805@web.de \
    --to=uwe.menges@web.de \
    --cc=dm-crypt@saout.de \
    --cc=mbroz@redhat.com \
    --cc=prajnoha@redhat.com \
    --cc=thomas@archlinux.org \
    /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.