Live data from Hacker News

Kernel bugs hide for 2 years on average. Some hide for 20

pebblebed.com

181–186 of 186 posts

Re: Kernel bugs hide for 2 years on average. Some hide for 20

#181
post #3

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/

How are SEL4 and Genode going for you in your day-to-day compute usage?

I'm quite happy using SculptOS (Genode/NOVA) for all my productive work - every day ;-)

Re: Kernel bugs hide for 2 years on average. Some hide for 20

#182

Earlier quoted context omitted.

Yes, but a lot of other things use Mach messages.

All the major OSes have components of the larger operating system that run in userspace and communicate via IPC, including Linux. But userspace drivers and basic system services (VFS, network stack, etc.) are very limited in their use of userspace/IPC. If macOS is a microkernel in the sense of those built on L4, then so are Windows and Linux, and the word doesn't have any meaning anymore.

Is that IPC called Mach?

Re: Kernel bugs hide for 2 years on average. Some hide for 20

#183
post #167

Earlier quoted context omitted.

I've been using rust for several years now and I like the way you explain the essence of the issue: tree instead of spaghetti :-) However: https://www.reddit.com/r/typescript/comments/wbkfsh/which_pr... so looks like it's not written in go :-)

> so looks like it's not written in go :-) That post is three years old, before the rewrite.

I missed that. For the curious:

https://www.reddit.com/r/golang/comments/1j8shzb/microsoft_r...

When asked why go and not rust, they said: "The existing (javascript) code base makes certain assumptions -- specifically, it assumes that there is automatic garbage collection -- and that pretty much limited our choices. That heavily ruled out Rust. I mean, in Rust you have memory management, but it's not automatic; you can get reference counting or whatever you could, but then, in addition to that, there's the borrow checker and the rather stringent constraints it puts on you around ownership of data structures. In particular, it effectively outlaws cyclic data structures, and all of our data structures are heavily cyclic. "

sharp!

Re: Kernel bugs hide for 2 years on average. Some hide for 20

#184

Earlier quoted context omitted.

All the major OSes have components of the larger operating system that run in userspace and communicate via IPC, including Linux. But userspace drivers and basic system services (VFS, network stack, etc.) are very limited in their use of userspace/IPC. If macOS is a microkernel in the sense of those built on L4, then so are Windows and Linux, and the word doesn't have any meaning anymore.

Is that IPC called Mach?

Yes, and it’s quite inefficient compared to L4 or Zircon’s IPC so it isn’t used for anything that wouldn’t work just fine over a SEQPACKET socket using SCM_RIGHTS like Linux does. Is modern Windows a microkernel because ALPC exists?

Re: Kernel bugs hide for 2 years on average. Some hide for 20

#185

Earlier quoted context omitted.

How are SEL4 and Genode going for you in your day-to-day compute usage?

I'm quite happy using SculptOS (Genode/NOVA) for all my productive work - every day ;-)

But you're a main project contributor. What about everyone else?

Re: Kernel bugs hide for 2 years on average. Some hide for 20

#186

Earlier quoted context omitted.

I'm quite happy using SculptOS (Genode/NOVA) for all my productive work - every day ;-)

But you're a main project contributor. What about everyone else?

Come round tonight and see for yourself https://hedgedoc.c3d2.de/GenodeUserGroupDD
Post reply on HN