I thought I would try to apply the fatdog64 usb install instructions to fossapup64 and see what happens. This of course will only work if fossapup64 is created by isohybird and I think it is.
The first step is the dd command:
Code: Select all
dd if=./fossapup64-9.5.iso of=/dev/sdc1 bs=4M
This seems to take quite a while. I wonder if it stops once the end of the iso data is reached or it stops when the end of the drive is reached. Also not sure if I should just have "sdc" or "sdc1"
Next the fatdog64 instructions say that I should be able to use the extra space at the end of the drive be using the fix-usb.sh command. This script doesn't work as expected on fossapup. I think the utility on fossapup outputs a different format that fatdog64. For instance I get:
Code: Select all
sfdisk -uS -l /dev/sdc
Disk /dev/sdc: 28.9 GiB, 31042043904 bytes, 60628992 sectors
Disk model: USB DISK 3.0
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0xf404eeaa
The script apears to be looking for the sector field so I want field 7 but the fix-usb.sh script has the following command:
Code: Select all
ACTUAL_USED=$(sfdisk -uS -l $1 2>/dev/null | awk '/^\/.*\*/ {print $4}')
so I can modify it per my output:
Code: Select all
ACTUAL_USED=$(sfdisk -uS -l $1 2>/dev/null | awk '/^Disk \/.*/ {print $7}')
but the size given apears to be the whole usb drive. Maybe I should have formatted the drive first? If so how? Should I specify a partition table and if so what type?
Anyway, rather than using the above function. I realized that the fosspup64 iso is only 409 MB so if I reserve 500MB I should have more than enough.
Code: Select all
#RESERVED_SPACE=262144 #128 MB
RESERVED_SPACE=1024000 #500 MB
and the code to calculate space actually used was commented out. The resevered space is the sector (or block size 512 bytes). Here is a link for a calculator that coverts block size to magabytes:
http://www.unitconversion.org/data-stor ... rsion.html
but the actual steps are first to multiply 512 by the number of sectors to get the number of bytes and then devide the number of bytes by "1048576" to get the number of megabytes. See:
https://www.techspot.com/news/68482-qui ... kb-mb.html
Or in reverse we multiple the 500MB we want to reserve by 1048576 to get the number of bytes and then divide by 512 to get the number of sectors.
Anyway, after making my changes to the script it tells me that there is no space on the device. This makes me think that I should have formatted the device first.