DISCLAMER: READ DEVLOG 14! This is the OpenHex project, it is a meta-distro for Linux systems, but the programs (hextools or hexcores) will be able to be used anywhere, and I honestly encourage you to. Also, I'm not at all related/affiliated with any other repo/project/OS named HexOS or OpenHex. Uhh another thing, please read the README. All credits to Linus for the Kernel! Please also read the GPLv3 license, as OpenHex is licensed under the GPL-3.0 license (or GPLv3). Therefore, you may use OpenHex and all of It's programs in the GPL's terms. It is also very important to READ THE BUILD GUIDE. To do so, go to the guides folder (the only folder, as of writing this) and choose guide1 and guide1bit. Oh, and btw this repo is active, although it may seem inactive at times. Im working on a big guide, so thats why it appears so inactive! Thanks!
::::::::::
:: ::
:: ::
:: ::
::::::::
ASCII art of the OpenHex logo, it sucks, I know.
real openhex logo much better, made in 2mins. This is the OFFICIAL LOGO for now, so if you wanna show the logo show them this monstrosity.
OpenHex has adopted Portage as its package manager, for now.. To get one, read the freaking IT guide. As for kernel support, I don't have to do much there because there's already support for every kernel. Ish. I'm sure it won't be too hard to make them gain actual support in the sense of being able to use them as the base instead of Linux-1.1.13. Also, here's some projects I think are cool. Right now, as of writing this, I'm not on my PC so I dunno how to provide links, so just search these up either in github or FireFox (or any browser): LensorOS SerenityOS CactusOS OS.js MikeOS StrayexOS Bedrock Linux GFOSS (Greek Free and Open Source Software) All of them are kinda cool and deserve MUCH more recognition in my opinion. OpenHex does NOT support the FHS, and by extention, POSIX fully. There is NOT: /etc /tmp /root /proc /usr (as of now) /lib (and it's variations) Userland seperation
There IS: /bin /home For POSIX, it gets a little strange. I know basically nothing about POSIX, so I can't compare it very well to OpenHex. There is NOT: FHS standards full fork() use (BIIIIG yet on this one)
There IS: exec family fork POSIX headers
So it is basically POSIX compliant, but just barely. It isn't FHS compliant, simply because I don't want to have to do a bunch of unessecary stuff on Linux-1.1.13 of all kernels... Also, you should really know C. If you don't, go ahead and learn C basics to the point your confident you can't possibly mess up passwordsys.c and shym.c.
As of now, the project is still in development, but I made this repo so you can see and follow my progress, or add suggestions and possibly help me. You can check in on the PROTOTYPE branch to see any prototypes of hextools or hexcores. If you consider yourself a person who'd like FULL control over their system, and a person that can: Troubleshoot errors in Linux, Operate tar correctly, Knows and can use the bash bare minimals (cd, cp, mv, rm, rm with rf and ls), this is much for you. You don't need to know these things, but they help a ton. Big thanks to GNU, also. The system right now is 64-bit, so modern features may not be avalible until development is complete. Correct me if I'm wrong, please! IMPORTANT (probably...): This is licensed under the GPLV3 license, plus it's on github (right now atleast) so your completley free to fork, read, study and overall use the code on the GPLv3's terms. The original author is stated in it too, so if you want to do anything with legal stuff, you should probably read the GPLv3 license it has first. It will probably be dual-licensed in the future. UPDATE: I just discovered bedrock linux, OpenHex is actually a lot like it! Atleast in the sense that you can 'Frankenstein' (if you will) bits of other distros to make your own. Anyway, they (Like GFOSS, Greek Free and Open Source Software) are actually pretty cool I'd recommend you try it out! Update 2: I think OpenHex is also a meta-distro on many ways. It's portable, It's an OS you make, not one that's pre-installed for you, there is many, MANY ways to install it, and you need an existing Linux system (No more LFS required!!!) to install. OpenHex is getting, or already has depending on the time you read this, a Gitlab, Sorceforge and Codeberg because if github is ever down for some reason, you can go ahead to it's gitlab or codeberg to access OpenHex in more ways. However, updates are NOT AT ALL frequent on it's alternatives. I might probably even forget about them.
So I am mainly building LFS as of now, and it's going on a VM because I only have and use 2 PCs, and I don't want to potentially lose the second PC.. Progress has been smooth, so far. I got past compiling GCC and the kernel headers, but my system kernel panicked mid-compilation (I was compiling glibc) and now I have to restart from my last snapshot. Wish me luck with this.
I have been doing loads of more general CS studying, and I have found out about the GFOSS (Greek Free and Open Source Software) and I find it pretty cool, esspecially because I am greek myself. As for LFS and general OpenHex building, it's been going pretty smooth, although I am still waiting on OpenHex sys/hextool building because I'm not done with LFS, but I am getting closer to finally getting past the cycle of extract, configure and compile.
Damn. I accidentally deleted the VM I was working on, and now I have to restart. Thats all there really is to this dev log and from now on these logs will have the date that they were made. 28/06/2025
Loads of things has changed, hopefully for the better. Big thanks to Linus for making his kernel open source so me and countless others can use it! (Im using the 0.11 kernel as of now, but it probably won't be forever (: ). Working on the SHELL file privately for now, dont worry I will upload it soon. LFS IS NO LONGER REQUIRED!!! I can't rename the repo so sorry for the name. Thats where the Important stuff ends, other than that bedrock linux is kinda cool! (Forgot the date srry)
So development will be severely slown down because the PC I'm using to develop OpenHex is my brother's PC, and where I'm at in the development of OpenHex is the Bash shell, and because the PC is EndeavorOS now, that's probably bad news for the system's shell. I could do --prefix=SHELL, I know, but I'm not risking it for the biscuit. My brother will probably be getting a new PC on his birthday (Late autumn). I also found an amazing workflow for meta OS devs. Basically, write the guide AND the OS at the same time, it's actually insanely good. You'll get addicted to it fast tbh.
Ditched the date thing, but big milestones are soon to be coming up! Bash shells (in autumn), daemons (Tomorrow, I'm preparing them for good use) and all!!! Finally, my project is a reality now, not a dream. I also got it Licensed (GPLv3), so now it's truly Open Source! (:
So i just realized ive been re-inventing the wheel, dammit. This whole time i was deadlocked on trying to backport ext4 to linux-1.1.13, when i could of just used ext2. I will (From now until needed) use ext2 or even ext3 as the main FS for OpenHex. I know, I know its not exactly the best in the world but its better than trying to make a cup fly with nothing but the letter A and without a cup.
So FINALLY, the first prototype is FINISHED!!!! So I can't test it, compilation and configuration is dangerous but I can use my now Arch Linux'd PC to try and compile it. I have lots of inspiration now, like SerenityOS's DE style (which I like a lot), Mem-something OS, idk it has a rainbow leaf as it's logo and it's linux compatible? Anyway, if the OpenHex prototype 1 kernel boots, I will be extatic. Probably testing today once my brother gets off. (Or so he thought...)
So... I have until September to get the major bits in (Wow, thanks High School.), but I haven't even tested it yet. As far as I'm aware, this repo has 0 (apart from my stars) stars and 0 support which basically means its up to ME to test it myself. I don't want to use a VM, so I might just use USB from PC1 to PC2. I'm just gonna install Debian real quick before I do it though, kinda tired of Arch's shenanigans. In DEV LOG 7, just know I added the final bit in the brackets. If your seeing this, please star it! It motivates me a lot to know people actually care enough to do so.
ok I'm getting a Lil lazy, but I swear I'll get to it. Anyway, a new section is being added to the README. I just wanted to point this out. Basically, it's just there to describe some things I might have forgotten to mention in the information section, and I MIGHT clean the README up a little. The whole Hexcore and Hextool thing is still being worked on, but I don't have to work on it much (or, at all really.) because it's pretty much part of OpenHex's modular nature. Anyway, I WILL focus on B2 today to install Debian on it. I know I can just use a TTY, but DEs are just more convenient. Anyway, I was mostly taking a break and studying the kernel. Hopefully, there will be lots of updates through the summer!
So finally, I got Debian working on the spare PC, USBs and other tools are on the way and arriving today, and I'm overall expecting some error with bash. When I hop on the PC today I'll update the guide, MAYBE compress it, and that's that. After this, It's IT time.
Now that I've I've formatted the USB, its time to get OpenHex compiled and booted. Also, after this, I will probably need lots of help getting OpenHex modern features, however this idea is still being fleshed out so don't worry yet!
So... I made the BPC2 into a general test bench, and so far it works. It's just an XC-330 Aspire that was insanity to get out of its case, but alas, I did it. Also, you know how Tux can appear on boot records? Sadly, it doesnt happen as often. I still want Linux devs to bring Tux back, but I do know OpenHex WILL get Tux support. WILL. I may have to update the guide for that though, because Tux can only appear before you compile, at least I think. Im not sure yet. Also, remember that you need to compile the kernel with GCC v2-4 which many systems don't have. Good luck, to you and me.
You MUST include /bin for GNU program support. There will probably be many errors I have not documented yet. I'd like real feedback on them. There is basically no security whatsoever, because I am not at all good in that field. I'd like help here too.
So I'm gonna start trying to add features to OpenHex now. They are all optional, so don't worry about bloat. The list of features that are currently prioritized (Im using big boy words :) ) are: Tux on boot logs (that thing where 1 tux represents 1 CPU thread/core) Check! USB support Uh.. working on it. Disc support (eh, maybe later) (little did he know, the kernel already had floppy and disc support.) Multi-user capabilities Check in the most primitive way! Interpreted and Compiled language support (e.g C, Python, Perl, etc.) GNU program support Check? POSSIBLY rust support for all the rust fans
Right now, I'm working on the 1st, 2nd and 5th features to OpenHex. I'll also be studying kernels for a while, so that might slow some things down. Also, I'm using QEMU because my Test Bench magically stopped working overnight.
So my test bench is down and getting a VM ready is a no go for some reason. It would be helpful if I had a tester. Please use the guide, and give me some feedback on if it works or it doesn't work. A common error is: fatal error: </asm/system.h>: no such file or directory. I think this happens because you have a newer compiler (it MUST be below 5 at least. I dunno, something old like Slackwzre 12...) so USE GCC 1-4!!!!!! Any other error you come across, please put it in the discussions section (at general feedback, preferably) so I can ignore it. Thanks! :3
I am working on passwords rn, and let me tell you I have not a clue if it works or not. You shouldn't use passwords right now, but if you want security reveiw the code FIRST. I will have probably made a bajillion mistakes because I don't know C++ all that well.
im taking a lil break, bcuz idk what to do next. That's it. Probably the shortest dev log yet lmao
Well im back. Im working on package managers now, and no OpenHex will NOT be getting its own package manager. Or, at the very least, not now. So far, I got portage on it. I haven't tested, but I think it works. Idk. (Or so I thought.)
Alright, I'm actually back. I don't really know where to go from here. I suppose I can continue writing the guide, but that'd take ages, and I only really have the weekend before high school comes back for the week. But hey, at least my schedule tells me no math on Monday, so that's awesome at least. Everybody else has to suffer. Also, the algorithm's TOTALLY doing a GREAT JOB at making this repo float in the sea. I don't even care anymore, whatever happens to this repo happens. I'm pretty sure it was just burn out getting to me. I mean, who wouldn't burn out from writing an index as big as the UAL before your even 13?!