qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: <jeebs@yango.us>
To: Qemu mailing list <Qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] What happened to linuxppc-img from Freeoszoo
Date: Mon, 27 Jun 2005 12:12:43 -0500	[thread overview]
Message-ID: <003701c57b3b$73bb0350$334d21d1@organiza3bfb0e> (raw)
In-Reply-To: 20050627144608.GA16320@jbrown.mylinuxbox.org

"Jim C. Brown"
>> Late last year, QEMU reworked the disk geometry, and that can confuse old
>> disk images.  The images expect an old style and the newer qemu offers a
>> different geometry.
>
> No, the geometry reported by 0.7.0 (which sees the disk properly and can
> mount
> partition) and CVS (which can't see the partition table) are the same.
>

Right... But most of the images on FreeOSZoo were done using the *old*
version of qemu, where the geometry is different.

That means the geometry on the images may not be what newer versions of qemu
expect.

That's why I was asking what the date of the image was.

> For the record, images I've used since qemu 0.5.2 still work fine with
> CVS.
> (I only use raw images though.)

That's good for you.

But some don't.

The ReactOS image is a case I tested myself.  When I saw it reported on the
qemu forum, it was small enough that I spent a few minutes downloading it to
test it.

And newer versions of qemu most definetly would not handle it.  Older 
versions (before the geometry change) could, though.


> Actually, the reason that linux-ppc.img broke was due to a hack for
> darwin/ppc.

I didn't know.

But I did know that a lot of the images on there are older ones that may
have problems like reactos did, which is why I said that somebody needed to
actually test each one, just to make sure they still work.

  reply	other threads:[~2005-06-27 18:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-27 14:46 [Qemu-devel] What happened to linuxppc-img from Freeoszoo Jim C. Brown
2005-06-27 17:12 ` jeebs [this message]
2005-06-27 18:24   ` Jim C. Brown
  -- strict thread matches above, loose matches on Subject: below --
2005-06-24 21:52 Tero Kaarlela
2005-06-24 19:21 ` jeebs

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='003701c57b3b$73bb0350$334d21d1@organiza3bfb0e' \
    --to=jeebs@yango.us \
    --cc=Qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).