From: "roland" <devzero@web.de>
To: <linux-kernel@vger.kernel.org>
Subject: Re: max_loop limit
Date: Fri, 23 Mar 2007 00:37:44 +0100 [thread overview]
Message-ID: <05e401c76cdb$178be430$eeeea8c0@aldipc> (raw)
partitions on loop or device-mapper devices ?
you can use kpartx tool for this.
bryn m. reeves told me, that it's probably poissible to create udev rules
that will automatically create partition maps when a new loop device is
setup, which is better than adding partitioning logig into dm-loop for
example.
example:
>kpartx -a /dev/mapper/loop0
>
># ls /dev/mapper/loop0*
>/dev/mapper/loop0 /dev/mapper/loop0p1 /dev/mapper/loop0p2
>/dev/mapper/loop0p3
i have seen a patch for loop.c doing this, though. search the archives for
this
regards
roland
On Thu, Mar 22, 2007 at 02:33:14PM +0000, Al Viro wrote:
> Correction: current ABI is crap. To set the thing up you need to open
> it and issue an ioctl. Which is a bloody bad idea, for obvious reasons...
Agreed. What would be a right way? Global device ala ptmx/tun/tap?
New syscall? Something else?
OG.
-
]
next reply other threads:[~2007-03-22 23:34 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-22 23:37 roland [this message]
2007-03-29 14:20 ` max_loop limit Bill Davidsen
-- strict thread matches above, loose matches on Subject: below --
2007-03-22 23:23 devzero
2007-03-23 8:59 ` Tomas M
2007-03-22 13:53 devzero
2007-03-22 7:57 Tomas M
2007-03-22 11:00 ` markus reichelt
2007-03-22 11:37 ` Tomas M
2007-03-22 13:42 ` Eric Dumazet
2007-03-22 13:42 ` Jens Axboe
2007-03-22 13:52 ` Eric Dumazet
2007-03-22 13:54 ` Jens Axboe
2007-03-22 14:11 ` William Lee Irwin III
2007-03-22 15:22 ` Arjan van de Ven
2007-03-22 16:09 ` Pádraig Brady
2007-03-28 23:34 ` Karel Zak
2007-03-22 14:33 ` Al Viro
2007-03-22 19:51 ` Olivier Galibert
2007-03-22 14:25 ` Tomas M
2007-03-23 1:34 ` Jan Engelhardt
2007-03-29 14:16 ` Bill Davidsen
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='05e401c76cdb$178be430$eeeea8c0@aldipc' \
--to=devzero@web.de \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox