It's okay. Not good, not terrible, but okay. Needing separate boot partitions for everything and storing entries in NVRAM is just fundamentally retarded though and Secure Boot needs redesigned from the ground up to not be completely bypassable from a booted userland.
>What do you think about the UEFI booting scheme?
another """open standard""" by microsoft, for microsoft, released with dogshit documentation, just like ACPI
>completely bypassable from a booted userland.
what, you fucking retard, you want your system to be even more toddlerized?
compared to what was before, it's not bad
secureboot and chain of trust needs to go. SKINIT-like reinitialization and measurement should be the way forward
>SKINIT >dude microcode lmao
all those VM autism instructions are unique to x64. what, you WANT to be stuck on x86 for another century?
because none of them are used anywhere where it's needed. reinit-remeasure is meaningful if the state is uncertain, like because it's a modular computer with god knows what hardware and their oproms were loaded.
I hope that modular computers will survive the death of x86
>I hope that modular computers will survive the death of x86
lmao, consumer x86 hasnt been modular for years >soldered CPU >soldered RAM >soldered wifi chipset >soldered keycaps >soldered charging cord
>storing entries in NVRAM is just fundamentally retarded
Can you explain to a fellow retard why this is retarded? I mean, you could store the entries on the hard disk, but you can move that to a different motherboard. What's the right place to store those entries?
UEFI in general is a bloated mess
In theory it's more flexible than BIOSes were but in practice this just means that manufacturers fill it up with shitty buggy modules and let the users live with the consequences
>Doesnt really do anything better than BIOS except muh secure boot
lol, comparing a 16 bit unstandardized mess with several calling conventions and error reporting mechanisms to a proper standard with 64 bit PE module loading is "not really better"?
So I was right with my post. You're a retarded Wayland fanboy too. Figures.
8 months ago
Anonymous
(checked)
you sound like one of those freetrannies running debian on a 10 year old thinkpad convincing thenselves it's the most secure device ever because you totally reviewed all the source code so permissions and sandboxing are unnecessary
>16 bit unstandardized mess
de-facto industry standard interface with very few exceptions, like the rest of the AT-clone world. 16-bit-only makes it a pain in the cunt to use in 64-bit mode. >UEFI >proper standard
lol, lmao even. in practice, UEFI is less standardized than fucking BIOS. there is a "standard" but its written so terribly that it may as well not exist. vendors never follow the standard. >64-bit PE module loading >"not really better"
correct. i want to write an OS, not sit and fuck with your special-snowflake 64-bit MS-DOS clone and its million APIs and structures.
OpenFirmware was a simpler, better designed technology sitting around for the lifetime of x86-64 but no, Intel had to be different and bring their Microsofty retardation straight into the boot process because that's what they were used to. They'd rather shit up the boot process with unnecessary bloat than change their habits. Idiot fucks.
a clusterfuck despite being a standard
It's okay. Not good, not terrible, but okay. Needing separate boot partitions for everything and storing entries in NVRAM is just fundamentally retarded though and Secure Boot needs redesigned from the ground up to not be completely bypassable from a booted userland.
compared to what was before, it's not bad
secureboot and chain of trust needs to go. SKINIT-like reinitialization and measurement should be the way forward
>What do you think about the UEFI booting scheme?
another """open standard""" by microsoft, for microsoft, released with dogshit documentation, just like ACPI
>completely bypassable from a booted userland.
what, you fucking retard, you want your system to be even more toddlerized?
>SKINIT
>dude microcode lmao
all those VM autism instructions are unique to x64. what, you WANT to be stuck on x86 for another century?
>i dont know what -like means
no other ISA implements anything remotely like SKINIT
because none of them are used anywhere where it's needed. reinit-remeasure is meaningful if the state is uncertain, like because it's a modular computer with god knows what hardware and their oproms were loaded.
I hope that modular computers will survive the death of x86
>I hope that modular computers will survive the death of x86
lmao, consumer x86 hasnt been modular for years
>soldered CPU
>soldered RAM
>soldered wifi chipset
>soldered keycaps
>soldered charging cord
>soldered keycaps
I always use extra solder
>storing entries in NVRAM is just fundamentally retarded
Can you explain to a fellow retard why this is retarded? I mean, you could store the entries on the hard disk, but you can move that to a different motherboard. What's the right place to store those entries?
Not that poster
It's retarded because it can't be reset to a known good state by unplugging the battery
>Year of our lord 2222
>We're still booting off of fat32
this lol
would it kill microsoft to write the ~200 lines of driver code to replace it with ext2?
Doesnt really do anything better than BIOS except muh secure boot
Some newer BIOSes support NTFS, and Applel uses HFS+ for UEFI
>Some newer BIOSes support NTFS
Holy bloat.
UEFI in general is a bloated mess
In theory it's more flexible than BIOSes were but in practice this just means that manufacturers fill it up with shitty buggy modules and let the users live with the consequences
as if they werent doing that to BIOS
>Doesnt really do anything better than BIOS except muh secure boot
lol, comparing a 16 bit unstandardized mess with several calling conventions and error reporting mechanisms to a proper standard with 64 bit PE module loading is "not really better"?
The end result is worse, now you have hundreds of buggy modules instead of something that isn't too bloated to debug
Not to that extent.
>unstandardized mess
You talk exactly like the Wayland fanboys.
anti-waylanders are the antivaxxers of Linux
So I was right with my post. You're a retarded Wayland fanboy too. Figures.
(checked)
you sound like one of those freetrannies running debian on a 10 year old thinkpad convincing thenselves it's the most secure device ever because you totally reviewed all the source code so permissions and sandboxing are unnecessary
>HURRR DURRR MAH SKUB
we're talking about UEFI here, bots, pay attention.
>16 bit unstandardized mess
de-facto industry standard interface with very few exceptions, like the rest of the AT-clone world. 16-bit-only makes it a pain in the cunt to use in 64-bit mode.
>UEFI
>proper standard
lol, lmao even. in practice, UEFI is less standardized than fucking BIOS. there is a "standard" but its written so terribly that it may as well not exist. vendors never follow the standard.
>64-bit PE module loading
>"not really better"
correct. i want to write an OS, not sit and fuck with your special-snowflake 64-bit MS-DOS clone and its million APIs and structures.
OpenFirmware was a simpler, better designed technology sitting around for the lifetime of x86-64 but no, Intel had to be different and bring their Microsofty retardation straight into the boot process because that's what they were used to. They'd rather shit up the boot process with unnecessary bloat than change their habits. Idiot fucks.