Is there any good reason why my TC64:USBstik is a FATfileSystem?
Was it the confusion of the new EUFI and putting a whole installation
to USBstik !?
Apart from other problems, FATFS doesn't allow me to have symLinks.
Is there any unforessen problem if I make a 2nd partition and migrate
the FAT files to it ?
Can I just edit the <booter> to boot to the 2nd partition?
Here's an example of the use of wily [or ETHOberon that wily is copied
from], where I need to examine and paste fron various files, while I'm
writing this post. How do users do that, who can see only 1 text file
on the screen at a time? =====================
=> find the <booter> directory/files
=> first find the list of mounted partitions
-> Dzm <- my script: df| grep "/mnt/" | awk '{print $1 " : " $5 " : " $6}' | more
=> /dev/sdb1 : 9% : /mnt/sdb1 <- this device has plenty space for extra partitionS
=> just right-klik on /mnt/sdb1 shows a window of </mnt/sdb1's contents> including:
ldlinux.sys syslinux.cfg autorun.inf & also /mnt/sdb1/EFI/BOOT/efiboot.img ...
Did this all come from TC, or was it part of the drama that I had in handling
the unfamiliar EUFI & USBstik-Installation?
How to find the <booter config textFile> ?
/mnt/sdb1/syslinux.cfg cites /boot/isolinux/isolinux.cfg
That looks familiar, and the 1st entry, which I normally select is: ....
KERNEL /boot/vmlinuz64
INITRD /boot/corepure64.gz
APPEND loglevel=3 cde vga=788
? But what's the syntax to cause booting from the 2nd partition ?
How do I indicate the 2nd partition of the USBstik, when at the time of
booting there will only be the TC:USBstik and the laptop's 4-partition WinTel
Disk?
TIA.