This post is BS. You should delete it.
Zones are not VMs. If you need to vent your Linux hate at least save it for a post about Docker.
Depending on the bug class there may be users who never want "kill" to be the default option.
That had basically nothing to do with the architecture. The key reason was likely the diverging requirements between laptop (Apple) and server (IBM) chips.
That's a warning (~= assert()), not a segfault.
Yeah I agree. It would be great if parts of the kernel could be written in a safer language. I think in 10 years that will be happening in at least some widely used OS, but most likely one that only supports a small…
At least with GNU as you can use %r1, %r2 etc. as an "intrinsic part of the syntax". Which means you can't use a register name where an immediate is expected. However that doesn't fix the gotcha with r0 being special,…
This post is BS. You should delete it.
Zones are not VMs. If you need to vent your Linux hate at least save it for a post about Docker.
Depending on the bug class there may be users who never want "kill" to be the default option.
That had basically nothing to do with the architecture. The key reason was likely the diverging requirements between laptop (Apple) and server (IBM) chips.
That's a warning (~= assert()), not a segfault.
Yeah I agree. It would be great if parts of the kernel could be written in a safer language. I think in 10 years that will be happening in at least some widely used OS, but most likely one that only supports a small…
At least with GNU as you can use %r1, %r2 etc. as an "intrinsic part of the syntax". Which means you can't use a register name where an immediate is expected. However that doesn't fix the gotcha with r0 being special,…