I am curently developing a file system for my OS (D.eSystem) with the version 6.1.0.5. The file system is now not working,but it is in development, you can find D.eSystem 6.1.0.5 here: https://github.com/D-electronics-scratch/all_D.eSystem_versions/releases/tag/v.6.1.0.5
This is cool, good to see you wanting to learn and experiment with stuff. I would recommend you study on the different aspects of current and past OSes. Especially simpler older OSes can give you a lot of insight into what an OS is, what components it has and how those tie together. What you currently have I would describe more as a cool little UEFI demo program and less of an OS. But it's a great start to build out from.
I would recommend trying to decouple software from hardware. Currently your code is heavily tied to hardware, which is fine in a test environment, but can easily break if the environment is different. Another aspect I would recommend you do a deep dive into is task schedulars. Especially looking at early types like the one from Windows 3.1 compared to the one from Windows 95. These are often used as case studies in schools, because they are easy to understand and offer similar but different approaches.
Personally I can also recommend trying to develop your OS for a simpler chip. That puts constraints on the project, which both limits the scope and also gives you challenges because of those limits. But that might be my personal bias, as I once developed a full fledged OS for the Intel 8051 as part of my university studies. This was back in the olden days tho, these days I would probably use something like an ESP8266 or ESP32.
Keep up the good work, keep being curious and keep learning!
Thanks
Why are you making your own OS?
Is this a learning exercise or a TempleOS situation?
Because I want to build my own OS,I started with OS simulators on scratch.mit.edu,then I switched to Python simulators and then I swutched to C simulators and then I wanted to start building a real OS.
So, a little bit of both ;)
Down the rabbit hole you go. :D
Very cool. It’s hard to get into file system development because it’s a very small audience that’s willing to test, and it takes years to build trust. Administrators prefer boring and rock solid stability which is not typically conducive to innovation in this area.
Thanks
Good on you for building it yourself and not just prompting a chatbot to make something and taking credit.
He’s already admitted to using AI
But I do not give prompts to generate code or smth, I am coding it by myself,I am just talking with ai about the project or debuging.
Responsible use, imo.
When I opened the file manager, it gave a KMALLOC fail error.
Yes,because now its not working and its still in development
What is the name of the file system? Is it D.FS? Actually, I am the developer of Z.eSystem, and I would recommend that you add a journaling feature.
I think it will be D.FS
Btw,how did you find Lemmy.world
I actually stumbled upon it by accident. I had a Windows program called "wid" and needed a platform to share it with the world; I found programming.dev, but now I've been filtered.
Cool,now you see that D.eSystem is also on other platform,it is also on reddit
You or AI?
I am coding it by myself,I am only using AI for debuging and learning and talking about the project
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Follow the wormhole through a path of communities !webdev@programming.dev