Linux
Welcome to c/linux!
Welcome to our thriving Linux community! Whether you're a seasoned Linux enthusiast or just starting your journey, we're excited to have you here. Explore, learn, and collaborate with like-minded individuals who share a passion for open-source software and the endless possibilities it offers. Together, let's dive into the world of Linux and embrace the power of freedom, customization, and innovation. Enjoy your stay and feel free to join the vibrant discussions that await you!
Rules:
-
Stay on topic: Posts and discussions should be related to Linux, open source software, and related technologies.
-
Be respectful: Treat fellow community members with respect and courtesy.
-
Quality over quantity: Share informative and thought-provoking content.
-
No spam or self-promotion: Avoid excessive self-promotion or spamming.
-
No NSFW adult content
-
Follow general lemmy guidelines.
view the rest of the comments
That's an interesting problem in computer science. Generally it's called "bootstrapping" when you build a process that is used to build another process. For instance, compilers like gcc are bootstrapped from a purpose built compiler compiler but then gcc compiles its own source to result in the final product. But that can be done on one machine. Bootstrapping a machine from bare metal pretty much requires another machine.
This. It sounds like OP is trying to bootstrap the low-level system. On startup the CPU is instructed to read from the first 512 bytes from the designated hard drive if it's MBR and run it as native code. If OP has any mean (like a butterfly) to write his own invention of boot code and Grub equivalent then it totally goes off the ground there.
In case anybody has no idea what that means:
https://xkcd.com/378/