Talk:USB flash installation media
About making the installation media without overwriting
I'm not totally sure if I misunderstood something, but I had to change the path of the entries of the *.cfg files. For instance:
It was the only way it worked with the unofficial ISO x86_64 image of march 13th, 2012. Looks like the syslinux command described in the page doesn't get the path as it should.
I edited all of the .cfg files, but probably only editing this ones should have been enough:
archiso.cfg archiso_head.cfg archiso_sys_inc.cfg
I hope it could be useful to somebody, because I spend some time with this (I even thought that was a problem with the hardware). I think it could be possible to make a simple script (or give some command lines) to patch the files once they are copied into the USB and run syslinux.
- I cannot find that this is still relevant to the article as it now exists. I am striking it out as it looks like it could be good to remove. AdamT (talk) 10:33, 8 August 2013 (UTC)
- Just lunched from USB drive without UUID(don't have any idea why it didn't have one). Solution was to change label to appropriate in loader/entries/archiso-x86_64.conf. Not sure weither this should be added to article.
- Ok. For some reason ubuntu did not see USB UUID. So blkid -o value -s UUID /dev/sdx1 were returning empty string. The solution was:
- $ sed -i "s|label=ARCH_.*|label=$(blkid -o value -s LABEL /dev/sdx1)|" loader/entries/archiso-x86_64.conf
- It seems that sometimes you have to get the UUID by running the command as root. --Rongmu (talk) 11:23, 3 October 2013 (UTC)
BIOS and UEFI bootable USB in Windows
Maybe this applies also for Linux...
In section 1.2, where one reads:
It should be
At least with the ARCH_201311 iso...
Making an UEFI/BIOS ISO should be KISS
Following up on the discussion in the the bbs, I disagree that this edit should be kept as the first thing users see when hitting this page. I based this opinion on my feeling that the instructions are too many steps and, arguably too vague. Example, this method is 7 steps (depending on how you count) and requires that user read linked articles (i.e syslinux install and modifying master boot records). In contrast, the dd method is simple (KISS principal) and is both implemented and documented as pointed out by one of our developers in the aforementioned bbs thread.