pizza2d1/tailwind-website
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

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

Browse Source
This commit is contained in:
pizza2d1
2026-10-01 13:53:29 -06:00
parent 7369d0a534
commit 5967222ec0
14 changed files with 148 additions and 28 deletions
Download Patch File Download Diff File Expand all files Collapse all files
assets/project_blogs/arch_chromebook/content.txt
+6
View File
@@ -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