Hello misc. Yesterday I upgraded a laptop (i386) from 5.6 snapshot to 5.7. This laptop has no CD reader so I copied 5.7/i386 directory to an msdos formatted USB stick on a Windows 7 machine and adjusted all filenames manually according to the TRANS.TBL files.
I tested the USB stick before upgrading and found some oddities regarding long vs short filenames, something like this: $ ls BSD BSD.RD ... $ ls BSD.RD BSD.RD $ ls bsd.rd BSD.RD So it seems the filenames are case insensitive and lists with capitals. The upgrade went fine, the sets were installed, but with these glitches: * The file INSTALL.i386 was not found but that could be ignored * The file SHA256.sig was not found but that could be ignored - skipping the verification. I had verified the SHA256.sig after download, so no harm done. Note that both files did exist and could be listed at least when mounting msdos with the -l option and with the names the installer claimed could not be found. And the toplevel directory had filenames that should force the usage of long filenames. I am also pretty sure the filenames had lowercase suffixes when viewed on the Windows 7 machine. I suspect the installer lists the files and compares filenames by itself and therefore the filenames does not match. If it would list by explicit names I guess it would find the files. I tried to mount the msdos filesystem myself (with long filenames) and use the installer option to install sets from a mounted filesystem, but then it could not find any sets at all. What worked was to install from unmounted filesystem telling the installer which partition the sets were on and then it found all file sets but not the two files above. It is great that it worked, but installing sets from a msdos filesystem can be improved. I think it is a useful way around having no CD reader. Best Regards -- / Raimo Niskanen, Erlang/OTP, Ericsson AB
