Porteus ~ rEFInd

[spare_head]

wrt : Problems booting Porteus under rEFInd 'Problems booting Porteus under rEFInd'

download iso extract files or mount iso & copt files


install refind ( which creates its own partition ! ) disk
and create 2 partitions (as is advised in USB_INSTALLATION.txt ) with eg gparted

one
fat16 containing /boot and /EFI (copy from iso)

one
ext4 containing /porteus (copy from iso)

reboot!

this works for me


... i think if an "efi" "driver"? for ext* exist??! for and was included with syslinux
then all files/dir's copyed from iso could exist on one ext partition !

perhaps its just as simple to write a similar grub2.cfg ( which afaik can load/work from /EFI on ext partition *on my hw =P *ymmv )

[Ed_P]

EFI systems require a FAT32 partition. If you're able to boot with a FAT16 partition your system is BIOS not EFI.

[i3slkiller]

EFI systems require a FAT32 partition. If you're able to boot with a FAT16 partition your system is BIOS not EFI.

I don't quite agree with that. Maybe I will show that on example of Chromium OS image (thoriumos_M120_v2) - this image have FAT16 ESP filesystem and somehow its booting on UEFI systems.

By the way I found something else like this:

The EFI firmware must support the FAT32, FAT16, and FAT12 variants of the EFI file system.

although this sentence above in the same PDF makes me wonder especially when various systems (on some cases at least bootloaders) was started successfully many times from FAT32 partition on pendrive on UEFI on Lenovo G580

EFI encompasses the use of FAT32 for a system partition, and FAT12 or FAT16 for removable
media

[Ed_P]

EFI encompasses the use of FAT32 for a system partition, and FAT12 or FAT16 for removable
media

Definitely wasn't aware of the FAT12 & FAT16 format support, but then again, when, and why, would someone use them today.