p_l

28 ms·

541.
by p_l 1y ago
And a major issue with OpenFirmware was that like other comparable interfaces from its time it required you to release a new OS version to support a new machine if it used different devices. Something as simple as handling evolution in avai
542.
by p_l 1y ago
UEFI and ACPI is actually blowback from living in exactly that kind of world. ACPI even included "compatible interface discovery" to handle the possibility that newer features might confuse older OSes without requiring end user to
543.
by p_l 1y ago
Arguably, "full" UEFI implementation mandates use of ACPI, which solves discovery of components that don't have self-discovery mechanism to use (including finding the very roots of various self-discovering buses)
544.
by p_l 1y ago
People have rose-tinted glasses for BIOS, have no idea of all sorts of hidden complexity that was involved in it, assumptions, etc. Or all the broken ideas that vendors put into BIOS-era firmware [0]. People also rarely think of the complex
545.
by p_l 1y ago
Whenever I think of how various parts are insane, I'm reminded of numerous cases in different systems in the past where I missed the insane part I am reading about... Like the entire HII thing, with an UI toolkit!
546.
by p_l 1y ago
In both cases you might have had a plugin that worked on Git - I think one is even part of default VS Code install (at least I don't recall having to install it)
547.
by p_l 1y ago
There is no a better solution because "manufacturer loads broken description table" does not care for the technology of the description table, just that manufacturer borked it. On PC, the main check against it is Microsoft because
548.
by p_l 1y ago
Does it provide ACPI and the RuntimeServices fully enough to operate as SBSA system?
549.
by p_l 1y ago
0) Assuming Oracle actually retains the stewardship of license: 1) Making CDDL compatible with GPLv2 puts everyone using CDDL code at mercy of Oracle patents 2) OpenZFS is actually not required to upgrade, and the team has indicated they wo
550.
by p_l 1y ago
The derivative portions of the ZFS driver are dual-licensed GPLv2/CDDL. The CDDL-only parts of the driver are portable between OSes, removing the "derivative code" argument (similar argumentation goes back to introduction of
551.
by p_l 1y ago
Oracle has no standing. Additionally, GPLv2 does not prevent shipping ZFS combined with GPL code, because CDDL code is not derivative work of GPLv2 code . So it's legal to ship. It could be problematic to upstream, because kernel
552.
by p_l 1y ago
Oracle can't do anything. They can't relicense code that was already released as CDDL in any form other than what they did when they closed down Solaris. The CDDL being unacceptable is the same issue that GPL3 or Apache is unaccep
553.
by p_l 1y ago
The lack of traditional 'fsck' is because its operation would be exact same as normal driver operation. The most extreme case involves a very obscure option that lets you explicitly rewind transactions to one you specify, which I&
554.
by p_l 1y ago
... or the quite common case, make helm write the template once, fix, port to your own process, delete helm, live happy
555.
by p_l 1y ago
Oracle does not have copyright on OpenZFS code - only on the version in Solaris. The code in OpenZFS and Solaris has diverged after Oracle closed OpenSolaris.
556.
by p_l 1y ago
The legal issues between Linux kernel and ZFS are that Linux license does not allow incorporating licenses with more restrictions - including anything that puts protections against being sued for patented code contributed by license giver
557.
by p_l 1y ago
Oracle lawyers know how to spell ZFS. But Sun ensured that they can only gnash their teeth. The source of "license incompatibility" btw is the same as from using GPLv3 code in kernel - CDDL adds an extra restriction in form of pat
558.
by p_l 1y ago
Can you explain your definition of "extent"? Because under every definition I dealt with in filesystems before, ZFS is extent based at the lower layer, and flat out object storage system (closer to S3) at upper layer.
559.
by p_l 1y ago
K6 depended on motherboard having thermal sensors - and which had to properly attach to the CPU in the first place. Built-in thermal sensing came later.
560.
by p_l 1y ago
Semantically, most OOP models[1] (even C++) involve "messages" that are "sent" to an object. "Methods" are "how do I handle this kind of message". This usually resolves to a function call because it&#
561.
by p_l 1y ago
Crashing is optional, depending on error model of the language. C has pitiful error model, thus you'll usually end up jumping to 0... but I recall at least one C environment where that gave you an error back instead of crash. As far as
562.
by p_l 1y ago
OOP does not disallow instantiation with unimplemented functions, it's just an artefact of implementation in some languages.
563.
by p_l 1y ago
The splash screens usually "hide" various loading steps. In Excel it's often loading and initialization of various extensions, for example.
564.
by p_l 1y ago
At release it was "working fine, same as in dev". It slowed down gradually as the JSON manifest of optional content grew.
565.
by p_l 1y ago
The only peripherals that truly don't work in more modern boards would be AMR/ACR/CNR? ISA and plain PCI being reasonably easy to acquire expansion boxes (might be a problem for EISA though, I guess...)
566.
by p_l 1y ago
Very much not the only one. For example, a lot of systems used VxWorks that would run paravirtualized Windows 9x for user interface - you normally booted into windows, and during boot a .VXD file would get loaded that was actually a VxWorks
567.
by p_l 1y ago
only opened the page on mobile network, and something choked a CSS somewhere apparently. Then it stayed this way.
568.
by p_l 1y ago
Making ARM machine that fulfills Windows requirements is harder than making your typical throwaway arm gadget (and then you hit things like Qualcomm not implementing it right either). There is not much profit for a hardware maker, and thus
569.
by p_l 1y ago
Five users and a pet hamster? ; - )
570.
by p_l 1y ago
Unfortunately, also not-joy of completely unbreakable website ... https://usercontent.irccloud-cdn.com/file/TPJZ2AeN/100001246...

More ›