Im just as confused as VS Codium, how is #include <system/syscalls.h> valid syntax while #include <system/elf.h> is not? Ive looked through all of the Cmake lists and I dont see anything that would make this make sense.

Please help!

How would I begin porting the Toy kernel to other architectures? Im creating a distribution of the Toy kernel for embedded systems and its a little hard for users to only use x86 embedded systems for it.

Im porting the Plan9 core utils to the toy kernel and many utils really need the exec syscall to function.o When looking at process.cpp and process.h I see Process::spawn and Thread::spawn have a 64 bit int call entry as one of its inputs. Could that section be skipped(when calling a application), and what does it do?

Is it just the variable thats passed?

This makes it look a little neater and may run better when more syscalls are added. Also if you havent already could you address this issue?[https://github.com/czapek1337/toy-kernel/issues/1]

I tried to compile the Toy kernel on my laptop that runs arch and I keep getting the error

c++: error: unrecognized command-line option ‘-target’
make[2]: *** [libs/core/CMakeFiles/core.dir/build.make:76: libs/core/CMakeFiles/core.dir/src/core/lock.cpp.o] Error 1
make[1]: *** [CMakeFiles/Makefile2:452: libs/core/CMakeFiles/core.dir/all] Error 2
make: *** [Makefile:91: all] Error 2
 

When patching c++ with clang another error pops up, im too lazy to fix this issue if you want to you can fix this, its a bit of a minor issue due to a work around.

I got a new error when trying to compile my set of core utils:

dd: invalid block size expression '1M'
Error: Could not stat device /home/yusufkhan/toy/toy-kernel/build/disk-uefi.img - No such file or directory.
Error: Could not stat device /home/yusufkhan/toy/toy-kernel/build/disk-uefi.img - No such file or directory.
[sudo] password for yusufkhan: 
Sorry, try again.
[sudo] password for yusufkhan: 
losetup: /home/yusufkhan/toy/toy-kernel/build/disk-uefi.img: failed to set up loop device: No such file or directory
umount: /home/yusufkhan/toy/toy-kernel/build/disk_root: not mounted.
losetup: option requires an argument -- 'd'
Try 'losetup --help' for more information.
[100%] Built target image-uefi

Compiling went fine but the disk-uefi.img was not generated.

CC=clang-13 CXX=clang++-13 cmake ..
make image-uefi

was used in /toy-kernel/build to compile it.

Ive created a basic keyboard driver in /src/dev and was wondering how I would configure it with the rest of the kernel to allow for it(with debugging and so on).

I have all the dependencies that you have specified(including limine) and when I run make kernel I get the error

[  3%] Building CXX object CMakeFiles/kernel.dir/src/acpi/acpi.cpp.o
/home/yusufkhan/toy/toy-kernel/kernel/src/acpi/acpi.cpp:1:10: fatal error: core/vector.h: No such file or directory
    1 | #include <core/vector.h>
      |          ^~~~~~~~~~~~~~~
compilation terminated.
make[3]: *** [CMakeFiles/kernel.dir/build.make:76: CMakeFiles/kernel.dir/src/acpi/acpi.cpp.o] Error 1
make[2]: *** [CMakeFiles/Makefile2:83: CMakeFiles/kernel.dir/all] Error 2
make[1]: *** [CMakeFiles/Makefile2:90: CMakeFiles/kernel.dir/rule] Error 2
make: *** [Makefile:124: kernel] Error 2

How do I fix this?

When running com::scan(1, 1); in maincpp(the com::scan thing comes from my borked branch where I put non-working things) and when running that I get kernel(0): fatal: intr.cpp:88: release( ) called when interrupts were not retained What does that mean and how would I fix that?

The main reason I am looking into the toy kernel is due to the fact that code size and the fact that it does not contain that that much bloat from POSIX and the "Everything is a File" approach to I/O.

I believe that the kernel shouldnt include very niche things in its design. This is ultimately a request, whatever you decide is what you decide, and not fully in my control, if there does become more bloat i will probably produce a stripped down fork that I would use personally.

This is a proposition for the kernel portion of the toy-kernel. I would also be fine/happy with the GPL with the following exception(Linux syscall exception):

NOTE! This copyright does not cover user programs that use kernel services by normal system calls - this is merely considered normal use of the kernel, and does not fall under the heading of "derived work". Also note that the GPL below is copyrighted by the Free Software Foundation, but the instance of code that it refers to (the toy kernel) is copyrighted by me and others who actually wrote it.