Comment 165 for bug 1325801
Revision history for this message
| Mathieu Trudel-Lapierre (cyphermox) wrote | #165 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
9199653
demo site
(Get the code!)
sudodus:
That's simply false. Sure, there are some gotchas, but it largely works modulo this bug report. You're not answering the question I asked.
As you may have noticed I've reset the statuses for this bug to something I think is closer to reality, and we'll close things as appropriate. We also have to consider architecture matching issues separately -- those are in bug 1446646.
Architecture matching is unfortunately an unavoidable issue. Either we run the syslinux from the system, and then you'll get the COM32R error when you boot an >utopic image written from a Trusty system, or we run the syslinux from the image about to be written and we have to match architecture or pick in-between and run the system syslinux if an i386 system tries to write a 64-bit image, and the image syslinux otherwise. Some careful application of syslinux parameters or copying additional files on the image may help too.
So I got these results from Marc Deslauriers:
- Vivid amd64 can write images from Precise and up, amd64 or i386.
I think we also should strongly suggest that users run usb-creator on a recent enough system if they don't want this bug here to happen. I'll see how release notes can be updated accordingly.
In light of all this, this bug should be Triaged/Critical for all supported releases -- we'll do another upload to -proposed to re-do the changes from Yu Ning (which appear to be fine), along with a fix for bug 1446646.