The issue tracker has been moved https://gitlab.archlinux.org/archlinux/archiso/-/issues
FS#35998 - Current ISO (archlinux-2013.07.01-dual.iso), not readable after dd
Attached to Project:
Release Engineering
Opened by Matt Parnell (parnmatt) - Tuesday, 02 July 2013, 14:55 GMT
Last edited by Gerardo Exequiel Pozzi (djgera) - Monday, 08 July 2013, 16:02 GMT
Opened by Matt Parnell (parnmatt) - Tuesday, 02 July 2013, 14:55 GMT
Last edited by Gerardo Exequiel Pozzi (djgera) - Monday, 08 July 2013, 16:02 GMT
|
DetailsDetails described in
https://bbs.archlinux.org/viewtopic.php?pid=1295294 Simply, after using `dd` to copy the ISO onto memory stick, it fails to produce a readable disk. Using the previous ISO, it does create a readable disk, therefore there is an issue with the is ISO. |
This task depends upon
Closed by Gerardo Exequiel Pozzi (djgera)
Monday, 08 July 2013, 16:02 GMT
Reason for closing: Not a bug
Additional comments about closing: Many other distros does the same thing. If you dislike it, then setup usb-media manually https://projects.archlinux.org/archiso.g it/tree/docs/README.transfer
Monday, 08 July 2013, 16:02 GMT
Reason for closing: Not a bug
Additional comments about closing: Many other distros does the same thing. If you dislike it, then setup usb-media manually https://projects.archlinux.org/archiso.g it/tree/docs/README.transfer
Comment by Gerardo Exequiel Pozzi (djgera) -
Tuesday, 02 July 2013, 15:25 GMT
- Field changed: Severity (Critical → Low)
Right, this change was made to also work on EFI systems via ISOHYBRID-GPT like with ISOHYBRID-MBR. Now the ISO contains an MBR and GPT. You may restore old behaviour, but destroying this duality using: isohybrid <iso> | <dev-where-iso-is-dumped>