I'm not exactly Linus Torvalds but I'm pretty sure a program that prints one line of text is not "a kernel". :)
If someone here has gone to college, then they'll know what 101 means - course numbering.
Kernel 101 – Let’s write a Kernel
11–20 of 104 posts
Re: Kernel 101 – Let’s write a Kernel
#12I'm not exactly Linus Torvalds but I'm pretty sure a program that prints one line of text is not "a kernel". :)
I'm going to give OP the benefit of the doubt on this one. A couple things worth noting, it successfully boots, does not cause a fault of any kind, and is in a position to interact directly with the bare metal. The tools that we use to interact with a *nix system are often just that, bits of code in user-space. This is a kernel-space program. That it does not do any of the memory management or device access yet doesn…
Reminds me of the old "booter" games on the PC that used their own kernel instead of MS DOS [1]
It would be fun to see how far one could go with modern hardware. Writing your own driver for a modern graphics card sounds absolutely terrifying (and fun).
Re: Kernel 101 – Let’s write a Kernel
#13I'm not exactly Linus Torvalds but I'm pretty sure a program that prints one line of text is not "a kernel". :)
If someone here has gone to college, then they'll know what 101 means - course numbering.
The courses that I've taken that were very basic and introductory was named 100. The next one was perhaps 101. Introductory courses in more specialized courses often had numbers signifying which research group they belonged to, with a low number at the end. Practices vary, even at my own university.
I'm guessing that 101 specifically is an americanism.
Re: Kernel 101 – Let’s write a Kernel
#14Great! except that to be called a kernel it's missing just a process manager, memory manager, filesystem, process separation and hardware abstraction. Yeah I'm that guy, down vote me as you wish, the article is still wrong.
It's a way to load a ring-0 application into grub. Pretty cool, but not a kernel.
Re: Kernel 101 – Let’s write a Kernel
#15I'm not exactly Linus Torvalds but I'm pretty sure a program that prints one line of text is not "a kernel". :)
That's how the Linux kernel started.
(technically it was two lines of text printing alternately to prove the scheduler worked, but close enough)
Re: Kernel 101 – Let’s write a Kernel
#16Why C?
I'm just curious if another language can be used. (c++, go, rust).
Re: Kernel 101 – Let’s write a Kernel
#17Great! except that to be called a kernel it's missing just a process manager, memory manager, filesystem, process separation and hardware abstraction. Yeah I'm that guy, down vote me as you wish, the article is still wrong. It's a way to load a ring-0 application into grub. Pretty cool, but not a kernel.
It's a statically linked program, real memory, diskless system, kernel-mode-only kernel without too much fluff in the video i/o abstraction.
Re: Kernel 101 – Let’s write a Kernel
#18I really like the new HN. Quality of articles is way up.
Re: Kernel 101 – Let’s write a Kernel
#19Great! except that to be called a kernel it's missing just a process manager, memory manager, filesystem, process separation and hardware abstraction. Yeah I'm that guy, down vote me as you wish, the article is still wrong. It's a way to load a ring-0 application into grub. Pretty cool, but not a kernel.
It's a statically linked program, real memory, diskless system, kernel-mode-only kernel without too much fluff in the video i/o abstraction.
Kernel means "core". Kernel-mode-only kernel is a contradiction. If you don't have separate parts, you can't have a core.
Re: Kernel 101 – Let’s write a Kernel
#20Very cool. I personally (as a developer without a CS background) find these sorts of posts wonderfully interesting, even if this kernel, as pointed out in this thread, lacks a lot of what a normal kernel does. I'd love to see one of these for a compiler!