aight
so I've recently learned that you can usually directly call kernel functions from user space, so this means Goldspace is pretty much suitable for being a functioning and usable kernel now
to test it all out, I'll be making an OS named PolarisOS, named for the North Star (alternatively called Polaris) and its role as a guide
it will contain a Windows 3.1-like GUI using the memory address 0xA0000 (VGA graphics mode) and if I'm up to it, will have a CLI mode using the memory address 0xB8000 (VGA text mode), but idk, I've got a font set up for 0xA0000 so I might just port the whole kernel to graphics mode so that graphics tasks are deeply rooted into the OS
my first steps will be to port and configure glibc (along with its dependencies, such as coreutils, make, etc), which I'll have to achieve with cross-compiling, then comes gcc so I can shift development over to PolarisOS natively
speaking of that, I also plan to be at least semi-POSIX compliant with PolarisOS, so binaries will be in /bin, libraries in /lib, config files in /etc, user folders go in /home/username, and so on
another major thing I'm working on is networking, one of the first things I'm gonna do in PolarisOS once I have it connected to Internet (which I will likely do via Ethernet to avoid the hassle of Wi-Fi support) is make a post to MS_memer_group
I'm not too sure about program execution, though, all I've got in terms of that is a shitty syscall that loads a program into memory and executes its main function
welp, there you go
Caption this Meme
