OSDev.org

• Arch: x86 (32-bit), Multiboot compliant.
• Memory Management: Higher-half kernel, PMM (bitmap), VMM using Red-Black Trees for tracking free virtual memory regions (O(log n) allocation).
• Multiprocessing (SMP): Full SMP support, parsing MADT, APIC/IOAPIC setup, and AP trampoline at 0x1000.
• Scheduler: Preemptive multitasking with basic priority handling.

• Storage: AHCI driver with MSI support (supports read/write).
• Input: PS/2 Keyboard and Mouse.
• Graphics: VBE Linear Framebuffer with SSE-accelerated software rendering.

• Window Manager: Custom compositing WM with support for overlapping windows, transparency, and "dirty rectangles" tracking to minimize redraws.
• Filesystem: YulaFS - a custom Unix-like filesystem with a block cache layer.
• Shell: Features command history, piping (`|`), and process management.

• scc: A Small C Compiler. It performs lexical analysis, parsing (AST), generates IR (Intermediate Representation), and emits ELF object files.
• asmc: A custom assembler for x86 instructions.
• uld: A linker that combines object files into an executable ELF.

Yula wrote: ↑Mon Jan 05, 2026 10:51 pm
My name is Vladimir (aka Yula), I am a 15-year-old student, and I would like to share my hobby operating system project: YulaOS.

I have been working on this intensely for the past few weeks (a massive development sprint of sleepless nights), aiming to build a unix-like environment from scratch.

Alexey1994 wrote: ↑Sun Jan 11, 2026 10:13 am3) используйте только ассемблер, никаких си, на нём легко научиться писать, программы получаются хорошего качества

Octocontrabass wrote: ↑Sun Jan 11, 2026 6:18 pm

Alexey1994 wrote: ↑Sun Jan 11, 2026 10:13 am3) используйте только ассемблер, никаких си, на нём легко научиться писать, программы получаются хорошего качества

This seems like bad advice. (Can you post in English too?)

Alexey1994 wrote: ↑Mon Jan 12, 2026 4:49 am Of course. My point is this: C doesn't give you complete control over the code, even if you write the compiler yourself. Assembler, on the other hand, doesn't impose any restrictions. If you need AVX optimizations, you just use them. C speeds up development, but the product itself will never be finished, even if new features aren't added. The optimal solution is to develop a prototype in C and manually translate it to assembler.

// echo.c

#include <stdio.h>

int main(int argc, char **argv) {
        const char *pre = "";
        for (int i = 1; i < argc; i++) {
                printf("%s%s", pre, argv[i]);
                pre = " ";
        }
        puts("");
        return 0;
}

Demindiro wrote: ↑Mon Jan 12, 2026 5:48 am intrinsics

Demindiro wrote: ↑Mon Jan 12, 2026 5:48 am Intrinsics have the advantage that compilers know about them, allowing more optimizations than with an opaque block of assembly.

Demindiro wrote: ↑Mon Jan 12, 2026 5:48 am An assembly program arguably is never "finished" either as it is:
1. architecture-specific, i.e. non-portable.

Demindiro wrote: ↑Mon Jan 12, 2026 5:48 am isn't able to take advantage of new processor features without modification. A program in a HLL could however take advantage of it with a simple recompilation (or by upgrading the interpreter).

Demindiro wrote: ↑Mon Jan 12, 2026 5:48 am But what does "finished" even mean in this context? Consider:

// SPDX-License-Identifier: GPL-2.0
// Copyright (C) 2025 Yula1234

#include <yula.h>

#define BUF_SIZE 1024

int main(int argc, char** argv) {
    if (argc < 2) {
        printf("Usage: cat <filename>\n");
        return 1;
    }

    int fd = open(argv[1], 0);
    if (fd < 0) {
        printf("cat: %s: No such file or directory\n", argv[1]);
        return 1;
    }

    char buf[BUF_SIZE];
    int n;

    while ((n = read(fd, buf, BUF_SIZE)) > 0) {
        write(1, buf, n);
    }

    close(fd);
    
    print("\n");
    
    return 0;
}

Alexey1994 wrote: ↑Sun Jan 11, 2026 10:13 am 5) если вы Владимир, не называйте себя Юля

Alexey1994 wrote: ↑Mon Jan 12, 2026 10:28 am Damn it, the author is a clever guy, he wrote a nice-looking code, and I didn't immediately notice that his cat is not concat at all, and he even puts \n at the end. Oh, I shouldn't have looked too closely.

Don't provoke fights or participate in fights started by others. Windows vs linux and programming language battles have been fought many times and resulted in a draw every single time.

Alexey1994 wrote: ↑Sun Jan 11, 2026 10:13 am Добрый день.

Есть один вопрос:
1) вы действительно 15 летний студент, или это проблема перевода?

Хоть меня никто не просил, но могу дать некоторые советы:
1) никогда не публикуйте свои собственные работы под GPL, вы не сможете их продать, на поиск работы это тоже никак не влияет, скорее мешает
2) изучайте схемотехнику, электротехнику, современные программисты в этом ничего не смыслят
3) используйте только ассемблер, никаких си, на нём легко научиться писать, программы получаются хорошего качества
4) попробуйте вместо красно-черных деревьев префиксные деревья
5) если вы Владимир, не называйте себя Юля
6) миру нужны изобретатели, ибо автоматизировать мы так и не научились. На сегодняшний день автоматизировано только оболванивание людей всякими психолого-философскими приёмами из СМИ. Чтобы оболваненные люди делали всю работу по автоматизации за почти бесплатно по 8 часов в день 5 раз в неделю. И нужда совсем не означает что за это будут платить. Платить вам будут за видимость работы, лояльность и покорность, а не за результат

Alexey1994 wrote: ↑Mon Jan 12, 2026 10:28 am Damn it, the author is a clever guy, he wrote a nice-looking code, and I didn't immediately notice that his cat is not concat at all, and he even puts \n at the end. Oh, I shouldn't have looked too closely.