Projects are now able to read from a content dir, posted two projects

2026-10-01 13:53:29 -06:00
parent 7369d0a534
commit 5967222ec0
14 changed files with 148 additions and 28 deletions
@@ -0,0 +1,6 @@
+A while ago I had acquired a chromebook from my school as they were doing a cleanout, so I was able to nab this crappy school chromebook that had a detachable battery and a 5GB 2.5" internal SSD
+!image assets/img/projects/arch_chromebook/arch_chromebook.jpg
+I wanted to try and install a new operating system on it, and since I was in my distrohopping phase I wanted to try installing Arch Linux on it, since I figure that would allow it to be actually usable rather than in it's chromeOS state
+The main issue was that the current operating system had a lock on it that made it so that you as a student wouldn't be able to boot into a different operating system, either through installing a new OS on the current drive or through using a LiveCD.
+So what I had to do was go INTO the currently installed operating system, toggle a setting, and then use a tool that would install <a href='https://chromeos.google/products/chromeos-flex/'>ChromeFlex</a>, which basically acted as an intermediary operating system so that I could unlock the actual firmware, letting me plug in a better drive
+Now that I could put in my own drive and not have the device yell at me for not having a ChromeOS operating system I went ahead and installed Arch Linux on the drive and booted it up
@@ -0,0 +1,6 @@
+A while ago I had acquired a chromebook from my school as they were doing a cleanout, so I was able to nab this crappy school chromebook that had a detachable battery and a 5GB 2.5" internal SSD
+!image assets/img/projects/arch_chromebook/arch_chromebook.jpg
+I wanted to try and install a new operating system on it, and since I was in my distrohopping phase I wanted to try installing Arch Linux on it, since I figure that would allow it to be actually usable rather than in it's chromeOS state
+The main issue was that the current operating system had a lock on it that made it so that you as a student wouldn't be able to boot into a different operating system, either through installing a new OS on the current drive or through using a LiveCD.
+So what I had to do was go INTO the currently installed operating system, toggle a setting, and then use a tool that would install <a href='https://chromeos.google/products/chromeos-flex/'>ChromeFlex</a>, which basically acted as an intermediary operating system so that I could unlock the actual firmware, letting me plug in a better drive
+Now that I could put in my own drive and not have the device yell at me for not having a ChromeOS operating system I went ahead and installed Arch Linux on the drive and booted it up
@@ -0,0 +1,6 @@
+When I was in high school I starting watching some youtube videos from this one guy: <a href='https://www.youtube.com/@dpacarana'>abel cirilo</a> who had made an operating system completely dedicated to a single character (Osaka) in the popular anime - Azumanga Daioh
+<iframe width='560' height='315' src='https://www.youtube.com/embed/vYImR-wrTV0?si=ODkfGwTBbsNOC_Lg' title='YouTube video player' frameborder='0' allow='accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share' referrerpolicy='strict-origin-when-cross-origin' allowfullscreen></iframe>
+So I decided that I might as well take a crack at something similar since I had a lot of time on my hands with summer break and all, so I started looking at what resources he used and I came upon a website called <a href='https://osdev.org/'>osdev.org</a> which had a bunch of resources and books on how to make your own operating system COMPLETELY from scratch, I'm not talking "I'll just build from the linux kernel" I'm talking you are writing/compiling the bootloader, the different ways different CPUs interact with the OS, and adding in ASCII support.
+Obviously I there was a TON of things that I was not ready for, I had barely even written a line of C/C++ code before so this was very strange and I eventually stopped working on it
+!image assets/img/projects/os_making/qemu1.png
+I was able to finish the <a href='https://wiki.osdev.org/Bare_Bones'>"Bare Bones"</a> part of the documentation but I still feel very proud of it.