From: "Jim C. Brown" <jma5@umd.edu>
To: Salvador Fandino <sfandino@yahoo.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Re: RE : Re: Re: NBD server for QEMU images
Date: Wed, 13 Dec 2006 17:55:00 -0500 [thread overview]
Message-ID: <20061213225500.GA826@jbrown.mylinuxbox.org> (raw)
In-Reply-To: <elpt96$lg0$1@sea.gmane.org>
On Wed, Dec 13, 2006 at 11:07:54PM +0100, Salvador Fandino wrote:
> Jim C. Brown wrote:
> > On Wed, Dec 13, 2006 at 08:03:13PM +0100, Salvador Fandino wrote:
> >>> The code of lomount might be what you're looking for. Lomount allows one
> >>> to mount partions (via loop) from a raw diskimage.
> >> That was my intention, but I have found that lomount handling of EBR and
> >> logical partition is not correct, they perform as if EBR where
> >> structured as MBR, what is wrong!
> >>
> >> Cheers,
> >>
> >> - Salva
> >>
> >
> > How is it incorrect? What needs to be fixed?
> >
> > My understanding is that the extended partition has a partition table
> > set up with the first partition entry pointing to the logical partition,
> > the second entry pointing to a partition table that exists immediately
> > after the logical partition, and then the 3rd and 4th entries are not
> > used. The second partition table is structed the same way, so you
> > essentially have a linked list of extended partitions. (Unlike the MBR,
> > there are no boot sectors associated with these partition tables.)
> >
>
> yes, that's right, but it's not what lomount does. It parses the data on
> the EBR in the same way as the MBR, reading 4 partition registers from them.
>
It only uses the first two. It reads in the rest but ignores them.
> Cheers,
>
> - Salva
>
>
>
> _______________________________________________
> Qemu-devel mailing list
> Qemu-devel@nongnu.org
> http://lists.nongnu.org/mailman/listinfo/qemu-devel
>
--
Infinite complexity begets infinite beauty.
Infinite precision begets infinite perfection.
next prev parent reply other threads:[~2006-12-13 22:56 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-12 12:48 [Qemu-devel] NBD server for QEMU images Salvador Fandiño
2006-12-12 13:37 ` Martin Guy
2006-12-12 17:00 ` [Qemu-devel] " Salvador Fandino
2006-12-12 16:58 ` Paul Brook
2006-12-12 17:13 ` Daniel Jacobowitz
2006-12-12 17:33 ` RE : " Sylvain Petreolle
2006-12-12 17:39 ` Paul Brook
2006-12-12 18:54 ` Anthony Liguori
2006-12-12 17:41 ` RE : " Johannes Schindelin
2006-12-12 17:42 ` Daniel Jacobowitz
2006-12-12 18:41 ` [Qemu-devel] Re: RE : " Salvador Fandino
2006-12-13 12:23 ` Jan Marten Simons
2006-12-13 19:03 ` Salvador Fandino
2006-12-13 20:03 ` Jim C. Brown
2006-12-13 22:07 ` Salvador Fandino
2006-12-13 22:55 ` Jim C. Brown [this message]
2006-12-14 8:37 ` Salvador Fandino
2006-12-14 14:58 ` Jim C. Brown
2006-12-12 19:00 ` Salvador Fandino
2006-12-12 17:45 ` [Qemu-devel] " Mark Williamson
2006-12-12 19:30 ` Christian MICHON
2006-12-12 15:09 ` Anthony Liguori
2006-12-12 17:32 ` Salvador Fandino
2006-12-12 20:13 ` Anthony Liguori
2006-12-13 2:14 ` Mark Williamson
2006-12-13 11:37 ` Avi Kivity
2006-12-13 13:19 ` Martin Guy
2006-12-13 13:29 ` Avi Kivity
2006-12-13 19:14 ` Salvador Fandino
2006-12-14 8:34 ` Avi Kivity
2006-12-13 16:58 ` [Qemu-devel] " Mulyadi Santosa
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=20061213225500.GA826@jbrown.mylinuxbox.org \
--to=jma5@umd.edu \
--cc=qemu-devel@nongnu.org \
--cc=sfandino@yahoo.com \
/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;
as well as URLs for NNTP newsgroup(s).