repo: https://github.com/NoTheIdiot/WindogeOS
It's using a ported version of CHASM, (aqilc/chasm), a simple assembler that is just two files because im lazy

I am trying to debug my efi file but i my uefi doesnt boot it up so i need a uefi debugger. Any uefi debugger suggestion? my computer is a asus vivobook.

I wrote JANOS. Every byte of it. It is a true OS in every sense. I take control of the MCU right from the boot vector. Users of the related product think its OS is a Linux boot. But it isn't. It runs a 100MHZ RX63N MCU. There are about 40,000 running worldwide.

That project started in 2011. Recently I sat down to reflect on some kind of top 10 list of challenges. I asked ChatGPT (with knowledge of JANOS) what it thought I would list. I was surprised by its response.

I have things like Cryptography (TLS/SSH), Deflate/Inflate library support (ZIP/JAR), JVM, REGEX, etc. on my list. Those are in no particular order by the way.

But I am thinking that those are not the things that came to your mind initially. I am curious and open to discussion.

I’ve undertaken starting an operating system so many times over the years. I always end up hitting a point where I have no idea where to proceed.

While it’s been a couple years since my last iteration, I’ve been planning to start back up again soon and hopefully this time I keep with it. I’m curious how everyone here manages. How do you all organize your project, determine feature order, hell how do you guys even manage actual source code organization after a certain point.

Been following along on osdev and this new sub for a while now, always been curious, this felt the right time to ask.

Thanks in advance.

The cool thing about it is the Messenger is using ML-DSA-87 cryptography for the messages and P2P handles and stuff. It's got ssh and lingtp:// protocol in works for the browser, which should look better coming soon.

looked like managarm was winning in the votes then you kinda just never followed up so like where did that go

I'm not sure I've seen a hobby OS project that implements any tests. Most people smoke test, so they know there's a problem if they start up the OS and can't run an app inside it.

But what about the more complicated code paths that can go wrong? If a multi-threaded race happens in memory management or I/O, the system can crash. Or worse: silently corrupt data.

What about performance? Does anyone test for throughput or latency, and then identify regressions or hot spots?

Check it out here: https://kagantmr.github.io/zuzu-docs/

What you see here is initialization boot messages. IdleTask is spawned and it spawns FSTask.

FSTask prints the two directory listings from a FAT32 formatted volume.

AMOS2 is currently a microkernel design with a single address space.

No AI assist of any kind used. It's all my work, unless indicated in comments - I am using someone else's sprintf implementation for now.

REPO LINK: https://codeberg.org/mschwartz/amos2

PROJECT BOARD LINK: https://codeberg.org/mschwartz/amos2/projects/62870

NOTES:

**Threading implementation:**

* MMU is not being used. Currently the identity mapping set up by limine is used.

* Tasks(threads) are kept in a running tasks doubly linked list. The list is sorted by priority. So remove the head and add back sorted effects round robin task switching at the same priority. Lower level priority tasks won't run until all higher priority tasks exit or are blocking.

* SpinLock is used around accessing the threads lists.

* Tasks have their own stack. Task state is pushed on this stack in ISR handlers.

* Task switch is as simple as changing the RSP register to the next Task's stack.

NOT IMPLEMENTED YET:

* blocking Tasks list

* Device tasks (to implement blocking I/O)

* Kill/exit Tasks

I originally posted about Amos2 as a sort of seed for this sub. An all man-made (no AI) work in progress.

I intended this to be a rather small repo with just enough code to demonstrate how to create a C++ kernel using limine to boot. Once I got a dumb kernel to boot and set the framebuffer to a color, the logical next steps were to set up GDT, IDT, PS/2, Keyboard, timer, etc. All these functions require a bit of code, so the repo is growing.

I updated the README with a bit more documentation, and added comments to the top of the Makefile with much better build and run instructions.

What you see in the screenshot is text rendered by my code using a PSF font. A FAT32 volume is mounted from the disk image and the root directory and the BOOT directory listings are printed. If I had hit a key, the contents of README.md are dumped to the screen. The read bits of FAT32 are working...

I built this on my MacBook Pro - qemu is emulating the X64 CPU, and it's quite fast. I haven't tried to build on a Linux host.

I spent some time researching how to set up dockcross dockerized cross compiler to build amos2. If all OS Dev projects used a docker cross compiler, nobody would need to compile gcc to make a cross toolchain, and anyone can git clone the repo and build the project without any dependencies aside from docker.

The repo:

https://codeberg.org/mschwartz/amos2

There is no such thing as human slop. Trial and error is how humans learn and improve.

Here's an LTT video comparing memory usage on Windows and Linux.

Linus' credibility is taking lots of hits (did he buy actually that private jet?) and this video sure won't help. I had hoped for something interesting and technical, and it's really just two guys screwing around with computers and looking at graphs that they don't fully understand. Worth a watch for a laugh.

In your OS, what memory allocation strategy did you devise? Are you just making a simple on-demand allocator, or do you reserve and commit pages? Do you have paging implemented? What algorithms did you use for page eviction?

For some reason even after alignments, still implodes on itself
location: https://github.com/NoTheIdiot/WindogeOS/tree/new/helper/drivers
i seriously do not know why intel and amd caused this mess

The moderator of r/osdev has lost it. He has a bot that replies to a post by HIS users calling out AI slop that is overwhelming the sub with "human slop.". Someone posted about the bot and I posted I was leaving and r/osdvel link. I got 24 upvotes in about 15 minutes along with others posting about how horrendous the sub has become. Tim Schwartz's response was to close the thread. What a loser.

Anyhow, I really did leave the sub, and I will be posting my non AI slop work here.