What does your OS look like? (Screen Shots..)

[sleephacker]

@sleephacker: Sweet! But is the kernel really <= 4096 bytes? $b000 - $a000 = 4096.

I don't have a kernel yet. The current "kernel" is just some code to fill the screen with a predefined color to demonstrate that the VBE mode works and that the framebuffer/resolution/bpp/bytes-per-line passed by the bootloader is correct. The "ramdisk" is currently just an ASCII string for debugging purposes.

[eekee]

Ah, so it's not an ultramicrokernel. (yet? ) The string reminds me of 9front where, if booted by multiboot, the 'ramdisk' is actually plan9.ini.

[klange]

I've finally re-implemented my weather panel widget after moving away from my old Python userspace:

[Kaisogen]

I started developing my OS a few months back, but kept restarting due to a lack of knowledge, and learning from my previous mistakes. I'm finally past the bootloader stage with something I can respect as a baseline, now I'm working on my kernel. I just implemented a PIT timer, with a sleep function. I tried testing how accurate delays were, and it seems like they work well enough. Now I'm onto developing a fdd driver!

This OS is also my capstone project for my Senior Year, so hopefully this COVID-19 quarantine stuff will give me some more time to work on it every day!

[nielsd]

Runs Wasm programs using the Cranelift compiler.
This is a simple Rust program which uses a Vec to calculate a sum (to test memory allocation in program) and prints some text.
Compiled with the Rust wasm32-wasi target.

[bzt]

Runs Wasm programs using the Cranelift compiler.

Cool! What's Cranelift compiler? Would you mind adding a link to it on wasm wiki page?

Thanks!
bzt

[nielsd]

Runs Wasm programs using the Cranelift compiler.

Cool! What's Cranelift compiler? Would you mind adding a link to it on wasm wiki page?

Thanks!
bzt

It's the compiler that wasmtime uses. It has builtin support for compiling wasm to native code, requiring you to implement some traits.
If you want to use it inside a kernel, you need to make some minor changes to get it to work in a no_std environment.
Recently, Cranelift was moved inside the wasmtime repository (which is linked on the wiki page already) for convenience reasons apparently.
However, you can use Cranelift independently from wasmtime.
I added a link now

[Monax]

Just finished porting my terminal to my widget library.

[gungomanj]

After a long period of inactivity I decided to start working on my ARM64 OS. I wrote an exception handler and some timer code that fires the exception handler every 5 seconds.

I think I am going to switch to 68k or another microcontroller as I dont like MMUs and complex processors.

[iProgramInCpp]

My operating system now accepts a VESA framebuffer! I've also been implementing a TinyBasic interpreter (sometime in 2019).

Here are some screenshots!

[ComputerFido]

I finally managed to get DOOM running!

[gungomanj]

My RISC-V based project, it can take keyboard interrupts and print to console now

[Peterbjornx]

Got back to my OS project after a few years and upgraded the toolchain to GCC 9.3.0, didn't seem to break much

[GeGuNa]

Got back to my OS project after a few years and upgraded the toolchain to GCC 9.3.0, didn't seem to break much

python!.png

Hello, can you give to us source link ?

[coderTrevor]

Hi ComputerFido, congrats on getting Doom running!

I took a look at Lemon-Doom and saw you had forked a project called doomgeneric, which I had never heard of before. It's really nice! I was looking for something like that but didn't know how to find it. Thanks for sharing your source and posting here because I was able to benefit a lot from that.

I hope you don't think I'm stealing your thunder, but after a couple of days and nights of hacking, I managed to port doomgeneric to my OS, which I creatively call MyOS.

Here's Doom running on MyOS:



Running Doom was the biggest goal I had for my OS from the get-go; kinda hard to believe I actually pulled it off, haha.