Linux Device Mapper development
 help / color / mirror / Atom feed
From: Lars Marowsky-Bree <lmb@suse.de>
To: device-mapper development <dm-devel@redhat.com>
Cc: gregkh@suse.de, hare@suse.de
Subject: Re: A better solution than "md_component_detection = 1"
Date: Wed, 20 Apr 2005 12:13:41 +0200	[thread overview]
Message-ID: <20050420101341.GL29071@marowsky-bree.de> (raw)
In-Reply-To: <1113947755.24817.81.camel@zezette>

On 2005-04-19T23:55:55, christophe varoqui <christophe.varoqui@free.fr> wrote:

> > > For example, /sys/block/sda would have a sub/ directory with "dm-0" in
> > > there, pointing at /sys/block/dm-0 (surprise). The
> > > /sys/block/dm-0/parent/sd{a,b} entries would do a very surprising
> > > thing.
> > > 
> > > This would also allow us to handle partitions in DM better: as all
> > > linear mappings on top of /dev/dm-0 would show up in block/dm-0/sub/ and
> > > vice versa.
> > > 
> > > md could work the same: block/sys/md0/parent/ would list all the devices
> > > (or partitions) which it consists of.
> > > 
> Regardless of the implementation, am I the only one to think that
> dm-0/parent/ should contain "parents of dm-0" ? :)

I thought that was exactly what I was proposing.


Sincerely,
    Lars Marowsky-Brée <lmb@suse.de>

-- 
High Availability & Clustering
SUSE Labs, Research and Development
SUSE LINUX Products GmbH - A Novell Business

  reply	other threads:[~2005-04-20 10:13 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-15 14:47 md_component_detection = 1 shahid shaikh
2005-02-15 21:20 ` Christophe Varoqui
2005-02-15 21:34   ` Alasdair G Kergon
2005-02-15 21:51     ` Christophe Varoqui
2005-04-10 17:29 ` A better solution than "md_component_detection = 1" Lars Marowsky-Bree
2005-04-19 21:38   ` Lars Marowsky-Bree
2005-04-19 21:55     ` christophe varoqui
2005-04-20 10:13       ` Lars Marowsky-Bree [this message]
2005-04-20 10:36         ` christophe varoqui
2005-04-20 23:42   ` Greg KH
2005-05-03 11:20   ` Lars Marowsky-Bree

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=20050420101341.GL29071@marowsky-bree.de \
    --to=lmb@suse.de \
    --cc=dm-devel@redhat.com \
    --cc=gregkh@suse.de \
    --cc=hare@suse.de \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox