I don't know if it should be reported as a seperate bugreport for JeOS, but
if it uses Ubuntu's repo's then it will likely be fixed as soon as Ubuntu's
bug is.
I'm rather curious a to what is causing this bug.
Any ideas?
On Nov 20, 2007 12:38 PM, ubuntu_demon <email address hidden> wrote:
> This bug affects JeOS too. Should I report it as a seperate bug against
> JeOS ?
>
> I used the ISO with MD5(ubuntu-7.10-jeos-i386.iso)=
> 341ca65a187c71643079a2f9ee5523b5 to create an image from it.
>
> I created the image like this :
> qemu-img create -f qcow jeos.img 10G
> qemu -m 512 -cdrom ubuntu-7.10-jeos-i386.iso -boot d jeos.img -no-acpi
> -std-vga
> I needed this workaround to create the QEMU image :
> https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.22/+bug/120316/comments/7
>
> --
> gutsy install cd (alternate or desktop) will not detect cdrom within qemu
> https://bugs.launchpad.net/bugs/120316
> You received this bug notification because you are a direct subscriber
> of a duplicate bug.
>
I don't know if it should be reported as a seperate bugreport for JeOS, but
if it uses Ubuntu's repo's then it will likely be fixed as soon as Ubuntu's
bug is.
I'm rather curious a to what is causing this bug.
Any ideas?
On Nov 20, 2007 12:38 PM, ubuntu_demon <email address hidden> wrote:
> This bug affects JeOS too. Should I report it as a seperate bug against 7.10-jeos- i386.iso) = 43079a2f9ee5523 b5 to create an image from it. 7.10-jeos- i386.iso -boot d jeos.img -no-acpi /bugs.launchpad .net/ubuntu/ +source/ linux-source- 2.6.22/ +bug/120316/ comments/ 7 /bugs.launchpad .net/bugs/ 120316
> JeOS ?
>
> I used the ISO with MD5(ubuntu-
> 341ca65a187c716
>
> I created the image like this :
> qemu-img create -f qcow jeos.img 10G
> qemu -m 512 -cdrom ubuntu-
> -std-vga
> I needed this workaround to create the QEMU image :
> https:/
>
> --
> gutsy install cd (alternate or desktop) will not detect cdrom within qemu
> https:/
> You received this bug notification because you are a direct subscriber
> of a duplicate bug.
>