This script takes values from files stored in the FAT32 partition to set
up Wi-Fi and override/add settings to default retroarch.cfg.
inspired by the solution from @macmoritz
by default mke2fs assumes block size by the size of the partition. when
the partition is being resized on an 2TiB disk, the resize fails.
forcing 4 KiB block will allow resize of the parittion on such large
drives.
closes#1963
resize2fs creates a filesystem with unclean orphan file when resizing
to more than 32GB if the orphan_file option is enabled, resulting in
an unmountable storage partition after initial resize.
Explicitly disable the option until the issue is resolved.
Signed-off-by: Matthias Reichl <hias@horus.com>
* libva-utils: fix sha256
* linux: delete obsolete patches
* ppsspp: set USE_SYSTEM_FFMPEG=OFF by default
* show_config: update to match upstream
* Fix build Generic build error
```
.../Lakka-LibreELEC/build.Lakka-Generic.x86_64-5.0-devel/toolchain/share/grub/bootx64.efi: No such file or directory
```
* Move STORAGE_SIZE default to match upstream
* grub: update to latest release
* gnulib: update to match grub bootstrap.conf
* grub: build 32 and 64 bit EFI images
* syslinux: do not copy EFI image
* installer: adapt script to above changes
* mkimage: virtual: build only for 64-bit Generic
* mkimage: grub: create cfg / copy EFI images only for 64-bit Generic
* create temporary folder in the target folder
* move DISK_LABEL setting closer to the part where it is used
* te MBR without test (it should be already present and if not, dd
will fail anyway and error is caught)
* update output when vmdk is created
In case SYSTEM_SIZE was higher than 1024, mcopy would fail without the
failure being caught. The failure was probably due to invalid geometry
(number of sectors per track too high?). However mformat should be able
to determine the geometry on its own, when no geometry parameters are
supplied. After discussion on IRC with vpeter we came to this solution.
* create temporary folder in the target folder
* use sparse files to create image and partitions
* no extractions of the partitions from image
* modify mcopy alias to copy to the partition sparse file
* add `-o` switch to mcopy alias, so mcopy does not prompt in case of
existing file in the partition
* remove alias for mformat (is used only one time)
* catch errors for mformat/mcopy/mmd
* use mcopy alias when copying files to virtual appliance part1
* move DISK_LABEL setting closer to the part where it is used
* write MBR without test (it should be already present and if not, dd
will fail anyway and error is caught)
* update output when vmdk is created
Co-authored-by: Peter <peter.vicman@gmail.com>
In case SYSTEM_SIZE was higher than 1024, mcopy would fail without the
failure being caught. The failure was probably due to invalid geometry
(number of sectors per track too high?). After discussion on IRC with
vpeter we came to this solution.
* extract the FAT32 partition from the image
* format the extracted partition without any geometry parameters
(mformat is able to determine the geometry by itself)
* install/copy files to the extracted partition
* verify the partition
* merge the partition back to the image
The extraction of the FAT32 partition is also needed for the OVA image
in case of Generic project.
Errors while mformat/mcopy/mmd will now be caught and image creation
will be terminated with an error message.
Removed alias for mformat, as it is used only once. Added `-o` to alias
for mcopy, just in case, as the output is now redirected, in case a file
would already exist, the prompt would be not shown and image creation
would just hang (ctrl-c does not work, had to use kill -9 on mcopy
during my testing when I forgot the `-o` switch).
For OVA full path to toolchain is not needed, as the alias has already
the partition in it, not the image.
fsck.fat is available in toolchain, so use that instead of fsck from
build host (which may not support checking FAT filesystems).
Signed-off-by: Matthias Reichl <hias@horus.com>
If temporary folder is full error message can't be saved and shown to the user which doesn't know what the problem actually is. In this case file is empty and show other message.
