Millions of lines of code, all running in supervisor mode. One bug is all it takes to compromise the entire system. The monolithic UNIX kernel was a good design in the 60s; Today, we should know better[0][1]. 0. https://sel4.systems/ 1. https://genode.org/
Yeah cause windows is amazing Or maybe macos? Ignore their freebsd parts of course.
Kernel bugs hide for 2 years on average. Some hide for 20
11–20 of 186 posts
Re: Kernel bugs hide for 2 years on average. Some hide for 20
#12Millions of lines of code, all running in supervisor mode. One bug is all it takes to compromise the entire system. The monolithic UNIX kernel was a good design in the 60s; Today, we should know better[0][1]. 0. https://sel4.systems/ 1. https://genode.org/
Yeah cause windows is amazing Or maybe macos? Ignore their freebsd parts of course.
Re: Kernel bugs hide for 2 years on average. Some hide for 20
#13Millions of lines of code, all running in supervisor mode. One bug is all it takes to compromise the entire system. The monolithic UNIX kernel was a good design in the 60s; Today, we should know better[0][1]. 0. https://sel4.systems/ 1. https://genode.org/
Yeah cause windows is amazing Or maybe macos? Ignore their freebsd parts of course.
Re: Kernel bugs hide for 2 years on average. Some hide for 20
#14Imagine if no one outside a select circle ever got to examine the code.
Everything is open source if you're skilled with Ghidra. We call AI models "open source" if you can download the binary and not the source. Why not programs?
Who's "we"? There's been quite a lot of pushback on this naming scheme from the OSS community, with many preferring the term "open weights".
Re: Kernel bugs hide for 2 years on average. Some hide for 20
#15Re: Kernel bugs hide for 2 years on average. Some hide for 20
#16Imagine if no one outside a select circle ever got to examine the code.
Everything is open source if you're skilled with Ghidra. We call AI models "open source" if you can download the binary and not the source. Why not programs?
the weights of a model aren't equivalent to the binary output of source code, no matter how you try to stretch the metaphor.
>why not
because we aren't beholden to change all definitions and concepts because some guy at some corp said so.
Re: Kernel bugs hide for 2 years on average. Some hide for 20
#17It may be just my system, but the times look like hyperlinks but aren't for some reason. It is especially disappointing that the commit hashes don't link to the actual commit in the kernel repo.
Re: Kernel bugs hide for 2 years on average. Some hide for 20
#18Re: Kernel bugs hide for 2 years on average. Some hide for 20
#19Earlier quoted context omitted.
Yes. As far as kernels go, NT was pretty damn good. So is Mach, by the way, if you can afford the microkernel performance overhead.
If you include all the drivers too (which surely makes the comparison more accurate), is that still the case?
The Linux kernel was and is a monstrosity.
Re: Kernel bugs hide for 2 years on average. Some hide for 20
#20Earlier quoted context omitted.
Yeah cause windows is amazing Or maybe macos? Ignore their freebsd parts of course.
NT is actually a pretty good kernel. NTFS and the userland is what is shit.