From: Kevin Corry <kevcorry@us.ibm.com>
To: Josh Litherland <josh@emperorlinux.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Partitioned loop device..
Date: Tue, 15 Jul 2003 11:04:49 -0500 [thread overview]
Message-ID: <200307151104.49455.kevcorry@us.ibm.com> (raw)
In-Reply-To: <20030715155317.317B461FDE@sade.emperorlinux.com>
On Tuesday 15 July 2003 10:53, Josh Litherland wrote:
> In article <200307151001.44218.kevcorry@us.ibm.com> you wrote:
> > so there's not much of a reason to add partitioning support to the loop
> > driver itself.
>
> Working with sector images of hard drives? I use Linux for data
> recovery jobs and it would be very helpful to me to be able to look at
> DOS partitions inside a loopback device. As it is I must chunk it up
> into seperate files by hand.
Like I said, this exact thing can be done using Device-Mapper and EVMS. No
need to add new partitioning support to the loop driver.
Generally, EVMS does not look for loop devices when scanning for disks to use,
but I have a simple patch (to the EVMS tools) that will allow it to recognize
loop devices. Let me know if you're interested.
--
Kevin Corry
kevcorry@us.ibm.com
http://evms.sourceforge.net/
next prev parent reply other threads:[~2003-07-15 15:59 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-15 8:46 Partitioned loop device Dimitry V. Ketov
2003-07-15 15:01 ` Kevin Corry
2003-07-15 15:53 ` Josh Litherland
2003-07-15 16:04 ` Kevin Corry [this message]
2003-07-15 16:05 ` Herbert Pötzl
2003-07-17 2:44 ` kernel
-- strict thread matches above, loose matches on Subject: below --
2003-07-16 8:59 Dimitry V. Ketov
2003-07-16 13:51 ` Kevin Corry
2003-07-15 18:32 Dimitry V. Ketov
2003-07-15 21:15 ` Lars Marowsky-Bree
2003-07-18 14:20 ` Christophe Saout
2003-07-18 19:10 ` Mr. James W. Laferriere
2003-07-18 23:57 ` Christophe Saout
2003-07-15 7:10 Dimitry V. Ketov
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=200307151104.49455.kevcorry@us.ibm.com \
--to=kevcorry@us.ibm.com \
--cc=josh@emperorlinux.com \
--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 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.