iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
Exploidus is described by its author, Rahad Bhuiya, as an x86-64 operating-system kernel built from scratch with C and assembly. Its reported scope goes well beyond booting: memory management, a filesystem, networking, system calls, a shell, and a graphical compositor. Those details come from Bhuiya’s first-person account, not an independent code audit or test report.
What Exploidus is—and what its story claims
Bhuiya introduces the project this way: “That question led to Exploidus—a custom x86-64 reactive capability operating system kernel built completely from scratch.” The article frames the work as an answer to a basic systems question: what happens when Linux, Windows, libc, and runtime libraries are stripped away, leaving a developer directly on x86-64 hardware with C and assembly?
In the author’s account, the result is not just a small kernel that reaches a prompt. It includes a range of operating-system components, from virtual memory to user-facing graphics. The available description does not establish the project’s current release state, build reproducibility, or independently verified behavior, so the feature list should be read as reported scope rather than a confirmed test record. Bhuiya’s Exploidus article links to the code, but the repository’s documentation and source are not assessed here.
Recommended Free Tools
How the reported boot path reaches 64-bit mode
The author says Exploidus uses a Multiboot2 header and GRUB2 to load an ELF64 image. Its startup sequence begins before the processor is running in 64-bit long mode; the kernel performs the setup needed to make that transition.
#1 Best Overall
- GRUB2 loads the kernel image. The Multiboot2 header provides the bootloader-facing entry point, and GRUB2 loads the ELF64 kernel.
- Protected-mode setup prepares the CPU. Early startup code configures a Global Descriptor Table (GDT) and enables Physical Address Extension (PAE), among the steps Bhuiya describes.
- The kernel enables long mode. After the necessary processor configuration, startup code transitions execution into 64-bit mode.
That sequence depends on assembly and exact processor state, not on a C runtime doing setup on the kernel’s behalf. The author highlights the absence of familiar tools at this stage: no printf, standard library, or memory allocator. Even basic text output and diagnosing a fault require deliberate early-boot mechanisms.
Memory management: page tables and executable permissions
Bhuiya reports implementing four-level paging with the standard hierarchy of PML4, PDPT, page directory (PD), and page table (PT). The article also describes allocating physical memory in 4 KB frames and marking data, heap, and stack pages NX/XD, so those pages are designated non-executable by the implementation.
These are architecture and implementation details, not evidence that the project has been security-tested. NX/XD page permissions can help express which memory regions should not contain executable code, but the account does not establish how comprehensively the permissions are applied or what protections have been validated.
Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Repair Windows errors before they cause bigger problemsFix Now →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Beyond the kernel: filesystem, networking, and system calls
The article presents Exploidus as a collection of connected subsystems rather than only a boot routine. The following are features reported by Bhuiya; the article does not supply independent tests for them.
- ExFS: a custom journaling filesystem.
- Networking: an in-kernel TCP/IP stack and Gigabit Ethernet drivers.
- Capability tokens: cryptographic tokens based on BLAKE3.
- System calls: 82 POSIX-style calls, according to the author’s feature count.
The article’s label “reactive capability” is part of the project’s self-description. The feature list alone does not establish the security model, compatibility level, protocol coverage, or practical performance of these components.
The user-facing layer: a shell and graphical compositor
Bhuiya names two user-facing components: exploish, the shell, and alien, a userspace compositor. The account says graphics are drawn through a framebuffer blit system call and that the compositor uses double buffering and dirty-region redraws. Those techniques describe how the project says it updates the display; they do not, by themselves, establish supported hardware, display performance, or compatibility with applications.
What the author says the work taught
Bhuiya’s reflections center on details that higher-level software often hides. Hardware behavior can be quirky; interrupts make concurrency difficult; abstractions have costs; and low-level debugging rewards careful reasoning. These are the author’s lessons from building Exploidus, rather than measured conclusions about every operating-system project.
PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchThe practical implication for learners is that an operating system is not a single leap from C code to a usable desktop. Booting, printing diagnostics, managing memory, responding to interrupts, and drawing to a framebuffer each expose a different boundary between software and hardware. The early work is especially unforgiving because a fault may occur before standard debugging facilities exist.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.How to investigate or learn from the project
For a reader considering Exploidus as a study project, the first useful questions are about evidence and reproducibility, not just the headline feature count. The linked repository is the place to look for its current README, license, build procedure, and testing instructions; those details are not established by the article alone. If comparing it with another hobby operating system, check the target architecture and firmware assumptions, boot method, implementation language, documented feature scope, source transparency, reproducible build steps, and published test evidence.
For a structured introduction to x86 operating-system work, The Little Book of OS Development describes setting up a development environment, booting in a virtual machine, and beginning kernel work in C. It is a general guide, not documentation for Exploidus.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →
