mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Bart Van Assche" <bart.vanassche@gmail.com>
To: 7eggert@gmx.de
Cc: "Nick Piggin" <nickpiggin@yahoo.com.au>,
	"Laurent Vivier" <Laurent.Vivier@bull.net>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Modify loop device to be able to manage partitions of the disk image
Date: Fri, 7 Mar 2008 13:08:20 +0100	[thread overview]
Message-ID: <e2e108260803070408l4600ae4cx1ecd261318cb63c6@mail.gmail.com> (raw)
In-Reply-To: <E1JXbBo-0000ix-57@be1.7eggert.dyndns.org>

On Fri, Mar 7, 2008 at 12:56 PM, Bodo Eggert <7eggert@gmx.de> wrote:
> Nick Piggin <nickpiggin@yahoo.com.au> wrote:
>  > On Thursday 06 March 2008 21:16, Laurent Vivier wrote:
>  >> Le jeudi 06 mars 2008 à 20:57 +1100, Nick Piggin a écrit :
>
>  >> > Do you think we do something similar for drivers/block/brd.c too? I'd
>  >> > like to try to maintain parity between them where possible...
>  >>
>  >> I think it is possible  (I've the same patch for NBD too), but I think
>  >> it is completely useless.
>  >
>  > It's useful for testing, and for minimising the divergence in the
>  > code.
>
>  Maybe there should be a common mechanism to use partitions on any block
>  device. Maybe there is - I have dark memories about the device mapper
>  being able to parse partition tables, and plans on moving partition
>  support to userspace.

It's easy to add partition support to the loopback device. A patch
that realizes this was already published in 2004. See also
http://lwn.net/Articles/110426/.

Bart Van Assche.

  reply	other threads:[~2008-03-07 12:08 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <a4kTW-44U-25@gated-at.bofh.it>
     [not found] ` <a4l3D-4hn-11@gated-at.bofh.it>
     [not found]   ` <a4lmN-4Xt-7@gated-at.bofh.it>
     [not found]     ` <a4m9d-6iD-7@gated-at.bofh.it>
2008-03-07 11:56       ` Bodo Eggert
2008-03-07 12:08         ` Bart Van Assche [this message]
2008-03-07 12:13         ` Laurent Vivier
2008-03-06  9:43 Laurent Vivier
2008-03-06  9:57 ` Nick Piggin
2008-03-06 10:16   ` Laurent Vivier
2008-03-06 10:56     ` Nick Piggin
2008-03-06 11:29       ` Laurent Vivier
2008-03-06 11:34 ` Pádraig Brady
2008-03-06 11:45   ` Laurent Vivier
2008-03-06 12:21     ` Pádraig Brady
2008-03-06 12:44       ` Laurent Vivier
2008-03-06 12:35 ` Christoph Hellwig
2008-03-06 12:55   ` Laurent Vivier

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=e2e108260803070408l4600ae4cx1ecd261318cb63c6@mail.gmail.com \
    --to=bart.vanassche@gmail.com \
    --cc=7eggert@gmx.de \
    --cc=Laurent.Vivier@bull.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nickpiggin@yahoo.com.au \
    /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

all inboxes | Powered by JetHome®