Comment by bakugo 1 day ago Is it or is it not AI generated? That's all I said, and you didn't deny it. 5 comments bakugo Reply reverserdev 8 hours ago Focus! Whether it's AI generated or not is a form of ad hominem. Attack the content, not how it came to be. soraminazuki 1 day ago Calm down. You had the answer served on a platter.From "The Kernel in the Mind":> The Kernel Is Not a Process. It Is the System.https://www.linkedin.com/pulse/kernel-mind-moon-hee-lee-miwz...It's X but Y came from elsewhere. bakugo 1 day ago > This isn’t a guide to writing kernel code. It’s an effort to understand how the Linux kernel thinks.> not of function calls, but of how the kernel responds> The kernel is not a process but the very foundation> The Linux kernel is not just a set of subsystems—it is a layered system that enforces structure at runtime> This flexibility does not come from runtime detection or dynamic reconfiguration. It comes from structure.> Identity is not discovered at runtime. It is defined before execution begins.> The kernel doesn't view memory as a simple map, but as a responsibility> Memory Is Not a Place. It’s a System.> Memory safety relies on disciplined handoffs, not centralized control or type enforcement.> The Linux kernel goes beyond executing code; it enforces strict control> Kernel execution is not linear code—it’s structured controlThis legitimately hurts to read. I think I'm going to have an aneurysm if I continue. reverserdev 9 hours ago Do you have any constructive feedback on how I can fix it? 1 reply →
reverserdev 8 hours ago Focus! Whether it's AI generated or not is a form of ad hominem. Attack the content, not how it came to be.
soraminazuki 1 day ago Calm down. You had the answer served on a platter.From "The Kernel in the Mind":> The Kernel Is Not a Process. It Is the System.https://www.linkedin.com/pulse/kernel-mind-moon-hee-lee-miwz...It's X but Y came from elsewhere. bakugo 1 day ago > This isn’t a guide to writing kernel code. It’s an effort to understand how the Linux kernel thinks.> not of function calls, but of how the kernel responds> The kernel is not a process but the very foundation> The Linux kernel is not just a set of subsystems—it is a layered system that enforces structure at runtime> This flexibility does not come from runtime detection or dynamic reconfiguration. It comes from structure.> Identity is not discovered at runtime. It is defined before execution begins.> The kernel doesn't view memory as a simple map, but as a responsibility> Memory Is Not a Place. It’s a System.> Memory safety relies on disciplined handoffs, not centralized control or type enforcement.> The Linux kernel goes beyond executing code; it enforces strict control> Kernel execution is not linear code—it’s structured controlThis legitimately hurts to read. I think I'm going to have an aneurysm if I continue. reverserdev 9 hours ago Do you have any constructive feedback on how I can fix it? 1 reply →
bakugo 1 day ago > This isn’t a guide to writing kernel code. It’s an effort to understand how the Linux kernel thinks.> not of function calls, but of how the kernel responds> The kernel is not a process but the very foundation> The Linux kernel is not just a set of subsystems—it is a layered system that enforces structure at runtime> This flexibility does not come from runtime detection or dynamic reconfiguration. It comes from structure.> Identity is not discovered at runtime. It is defined before execution begins.> The kernel doesn't view memory as a simple map, but as a responsibility> Memory Is Not a Place. It’s a System.> Memory safety relies on disciplined handoffs, not centralized control or type enforcement.> The Linux kernel goes beyond executing code; it enforces strict control> Kernel execution is not linear code—it’s structured controlThis legitimately hurts to read. I think I'm going to have an aneurysm if I continue. reverserdev 9 hours ago Do you have any constructive feedback on how I can fix it? 1 reply →
Focus! Whether it's AI generated or not is a form of ad hominem. Attack the content, not how it came to be.
Calm down. You had the answer served on a platter.
From "The Kernel in the Mind":
> The Kernel Is Not a Process. It Is the System.
https://www.linkedin.com/pulse/kernel-mind-moon-hee-lee-miwz...
It's X but Y came from elsewhere.
> This isn’t a guide to writing kernel code. It’s an effort to understand how the Linux kernel thinks.
> not of function calls, but of how the kernel responds
> The kernel is not a process but the very foundation
> The Linux kernel is not just a set of subsystems—it is a layered system that enforces structure at runtime
> This flexibility does not come from runtime detection or dynamic reconfiguration. It comes from structure.
> Identity is not discovered at runtime. It is defined before execution begins.
> The kernel doesn't view memory as a simple map, but as a responsibility
> Memory Is Not a Place. It’s a System.
> Memory safety relies on disciplined handoffs, not centralized control or type enforcement.
> The Linux kernel goes beyond executing code; it enforces strict control
> Kernel execution is not linear code—it’s structured control
This legitimately hurts to read. I think I'm going to have an aneurysm if I continue.
Do you have any constructive feedback on how I can fix it?
1 reply →