It target x86 architecture,the kernel is modulare and its still in development. It also requires the UEFI Firmware

This Software is in development and its a operatingsystem,I found it when I booted on different hardware

Hi, thanks for this info abput pintos, I will look on it.

Limine includes its own license file. When I pushed my OS code to the repository, the Limine folder (with its license) was automatically included because it is part of the bootloader. I removed the misplaced copy of the license from the root directory because it does not apply to my OS. The file couldn’t be cleanly deleted at first, so I renamed it while preparing my own license file. The original Limine license is still correctly located inside the Limine folder.

This is the License from the opensource bootloader,I added my source code with a commit,and then it apeared,then I tried to delete it because I want my own license for my own OS,but it wassnt working,then I deleted the license in the file and renamed the file to I to create a new License file,but I think the License is still in the Limine(bootloader) folder.

Nope,how could a AI build kernel, memory managment, UI, UX, drivers.

Thanks,idk why they are rude,its a bit anpying,but I think many people like it because I got a lot of upvotes

Its not vibe coded,its my own OS project, I am working every day on it, it have its own kernel,memory managment and more and it uses the Limine bootloader

Thanks

The file calles i was a accident because that was the Limine license,and I did it in one repo and now IU amworking with different releases and tags

And Limine is the opensource bootloader,the OS is written completly by myself

Nope,its not copied,ist the license from Limine and it accendently in the repo,I tried to delete it

I used tags this and releases with commits this time.

Thanks

https://github.com/D-electronics-scratch/all_D.eSystem_versions

https://github.com/D-electronics-scratch/all_D.eSystem_versions

I will not continue creating new repos because I am using tags and releases now, It was bad creating always new reposs thats why I will not continue creating new repos.

Its now uploaded in the same release

I fixed the problem with the all new D.eSystem 6.0.2 beta

All versions before D.eSystem 6.0.x were OS simulations and OS prototypes written in high level languages liek Python or written as a C programm,the firstreal D.eSystem was 6.0.x and I go from 6.0.6 alpha to 6.0.1 beta because the D.eSystem 6 is now going drom alpha to beta,nd I planed a lot of new generations after D.eSystem 6.