#Limine

1 messages · Page 3 of 1

leaden rivet
#

i think that this is reasonable, but you'd have to be careful to not make it orthogonal to existing features.

#

e.g. does $symlink mean that the symlink is gzcompressed or the target. how to make this non vulnerable on secure boot, etc

#

natural answer to the first question is the target, but this is orthogonal with the current spec that says that $ preceeds gz compressed names.

#

perhaps you could have another prefix for symlinks and then the ordering would decide on the behaviour.

gentle hemlock
#

blessed mouse cursor angle

leaden rivet
gentle hemlock
#

neat

tribal lagoon
#

custom mouse cursor themes? :^)

leaden rivet
#

don't tempt me

#

in principle it could be a direct config field, saying that a cursor is 16x16, 15 colours + transparency, with the hot w/h values. 'only' 128 bytes of hex. maybe RLE-coded.

jolly trout
#

also doesn't uefi supports custom file systems through external .efi drivers anyway? idk if limine uefi just uses the simple file protocol instead of directly accessing the disk like in limine bios but if it does, you can just write a shim that loads some kind of uefi fs driver (uefi drivers have to be loaded from an external program like the efi shell and couldn't be loaded automatically from what i know) and then loads limine which should be able to access the ext4 partition

#

nobody uses bios anymore anyway so

leaden rivet