21–30 of 76 posts
Earlier quoted context omitted.
It's how you interact with daemons.
Ah, right. I suppose it could also be argued that the kernel is also unnecessarily complex as well?
http://yarchive.net/comp/linux/efi.html
And here he is on ACPI:
A lot of the painpoints are gone, understandbly, but some still exist. The biggest suck on EFI is that it uses PE fileformats. I would have liked it more if it would have just loaded a raw PIC binary or ELF. And not used Windows Calling Conventions.
(Security has nothing to do with it, the module can be crypto signed by user installed key.)
Plus the critical hardware setup documentation is not being released at all.
Another is the use of SMI to communicate with the thing which just does not play well with a preemptible OS.
Memory map handling is additional badness on top.
Earlier quoted context omitted.
Ah, right. I suppose it could also be argued that the kernel is also unnecessarily complex as well?
Possibly, but a pretty obvious retort is that it's necessarily complex; there is nothing else to do all the things that it does. Whereas for BIOS and EFI the argument would be that they should do as little as possible to hand over to the real operating system.
Earlier quoted context omitted.
Ah, right. I suppose it could also be argued that the kernel is also unnecessarily complex as well?
Possibly, but a pretty obvious retort is that it's necessarily complex; there is nothing else to do all the things that it does. Whereas for BIOS and EFI the argument would be that they should do as little as possible to hand over to the real operating system.
I would like to offer, as a counter example, every micro kernel ever.
Unfortunately his statement is still valid even after 6 yrs, it is still a complicated disaster. And it uses Fat32 and PE. An abomination in my view.
Unfortunately his statement is still valid even after 6 yrs, it is still a complicated disaster. And it uses Fat32 and PE. An abomination in my view.
FAT32 is a good choice IMO. It's the simplest of the "mainstream" filesystems.
Unfortunately his statement is still valid even after 6 yrs, it is still a complicated disaster. And it uses Fat32 and PE. An abomination in my view.
FAT32 is a good choice IMO. It's the simplest of the "mainstream" filesystems.
(I don't know, I just have some vague memory of some Tomtom/Microsoft conflict due to FAT)
edit: user 'xxs' managed to type up the same issue before me (while I was typing mine).
Earlier quoted context omitted.
FAT32 is a good choice IMO. It's the simplest of the "mainstream" filesystems.
Is it a good choice though? Isn't there a bunch of possible issues with FAT patents, in case someone wants to ship a product that boots, that could have been avoided by using something else? (I don't know, I just have some vague memory of some Tomtom/Microsoft conflict due to FAT) edit: user 'xxs' managed to type up the same issue before me (while I was typing mine).