On Tue, Sep 17, 2013 at 8:12 AM, Jakub Klinkovský <kuba.klinkovsky@xxxxxxxxx > wrote: > On 17.09.13 at 0:06, arnaud gaboury wrote: > > Dear all, > > > > this is my second arch install this month (archlinux-2013.09.01-dual.iso) > > on an usb key to get a live Arch. Both installs failed on a vfat formated > > device, when they succed on ext2. > > $ pacstrap /mnt base returns lot of these erros: > > warning: warning given when extracting usr/bin/vgrename (Can't create > > '/mnt/usr/bin/vgrename') > > ...... > > > > It seems, even in chroot, that I can't write the vfat formated device > > > > I would like to use vfat as these keys are aimed to boot Arch from > windows > > machines and share files. > > I used gdisk and fdisk to partition, then mkfs.vfat to format, on clean > usb > > keys. > > Is there anything I missed ? > > > > Then, there is an issue with package vi: > > error: could not open file > > /mnt/var/cache/pacman/pkg/vi-1:050325-3-x86_64.pkg.tar.xz.part: Invalid > > argument > > I first # pacman-key --init && pacman-key --populate archlinux > > and # pacman -Syy > > > > The only way to succed the install was : > > # pacstrap -i /mnt base --ignore vi > > > > I must add that earlier installs with earlier iso did not show this > issue. > > Maybe shall I open a bug report, or is this a known issue ? > > > > Last, the above command returns : > > :: vi is in IgnorePkg/IgnoreGroup. Install anyway? [Y/n] > > > > It seems weird to me that default is Yes, as I specified --ignore vi. > > Would' nt it makes more sense to default No ? > > > > Regards. > > vfat has a lot of reserved characters: > https://en.wikipedia.org/wiki/Filename#Comparison_of_filename_limitations > > Note the colon (':') in "vi-1:050325-3-x86_64.pkg.tar.xz.part", don't know > why > it couldn't write "/mnt/usr/bin/vgrename". > > Probably because it is a symbolic link, and those are not supported in vfat. And there are far more important symbolic links out there...
