what-happens-when VS littleosbook

Agreed!

It reminds me of:

https://github.com/alex/what-happens-when

and how many of today’s CS-degree holders would barely understand any of it. As someone who has also “grown up with all the technology”, I’ve learned and experienced all that. But as a percentage of “software engineers”, there’s fewer and fewer that do every day.

There is a pretty comprehensive answer to number 2 here

Ask them to describe what happens when you visit a website and grill them on every layer of abstraction, every implementation detail.

This is a classic interview question and it basically means "How does internet work?" It is great because it allows to check how many levels of understanding it a developer has. The answer may be quite lengthy, for example: https://github.com/alex/what-happens-when

Perhaps you will find https://github.com/alex/what-happens-when useful.

Can't remember if it covers more practical stuff like GRUB but I really like https://littleosbook.github.io/

A good place to start learning about OS programming is https://littleosbook.github.io/

Little book about OS development\ (15 comments)

using combination of https://littleosbook.github.io/ and https://github.com/cfenollosa/os-tutorial

I also found "The little book about OS development" useful.

https://littleosbook.github.io/

So a non 9p disk is more work than getting TCP? (UDP is my first goal but before that I'll read https://littleosbook.github.io/)

Knowing all this, you are ready to follow this operating system development tutorial: https://littleosbook.github.io/