A simple POSIX-based operating system for 64-bit computers
Go to file
2023-01-22 11:27:37 +01:00
.vscode Bitmap: Introduce a new method 'find' and use it in MM and KernelVM 2023-01-09 17:59:52 +01:00
apps libc: Add a wide range of time manipulation functions, including reentrant variants 2023-01-13 21:06:27 +01:00
initrd/sys Initial commit :) 2022-11-13 10:09:09 +01:00
kernel Bitmap: Introduce new malloc-aware initialization functions 2023-01-21 23:16:50 +01:00
libc tools+CMake: Prefix all environment variables with LUNA_ 2023-01-21 22:44:16 +01:00
luna CString: Add strnlen() and strndup() 2023-01-22 11:27:37 +01:00
tools tools+CMake: Prefix all environment variables with LUNA_ 2023-01-21 22:44:16 +01:00
.clang-format Update .clang-format 2022-12-21 20:22:44 +01:00
.drone.yml Remove restart from CI configuration 2023-01-08 15:55:26 +01:00
.gdbconf Make GDB use the correct kernel file 2022-12-03 17:34:14 +01:00
.gitignore Switch to C for userspace, with a very bare-bones libc!! 2023-01-06 13:31:14 +01:00
CMakeLists.txt tools+CMake: Prefix all environment variables with LUNA_ 2023-01-21 22:44:16 +01:00
LICENSE Update year range in LICENSE :) 2023-01-02 13:08:42 +01:00
luna.json Don't build such a small image 2022-09-26 17:55:16 +02:00
README.md Update README.md 2023-01-09 18:16:39 +01:00

Luna

A simple kernel and userspace for desktop computers, written mostly in C++ and C. Build Status

Features

Setup

To build and run Luna, you will need to build a GCC Cross-Compiler and cross-binutils for x86_64-luna. (Yes, Luna is advanced enough that it can use its own OS-Specific Toolchain, instead of a bare metal target like x86_64-elf. It is the first of my OS projects to be able to do so. The patches for Binutils and GCC are binutils.patch and gcc.patch).

You should start by installing the required dependencies.

Then, run tools/setup.sh to build the toolchain.

This script will check whether you have the required versions of the toolchain already setup, and will skip building them if so. (This means that it is used by the build scripts to install the toolchain if it is missing before building, so you could skip running it manually.)

Please beware that building GCC and Binutils can take some time, depending on your machine.

Building

There are a variety of scripts for building Luna.

tools/build.sh will build the kernel, libc and binaries.

tools/rebuild.sh will do a full rebuild of the kernel, libc and binaries.

tools/install.sh will install those to the system root and initial ramdisk.

tools/sync-libc.sh will install the libc headers to the system root, build libc and install it.

tools/build-iso.sh will build, install, and make an ISO disk image named Luna.iso.

tools/build-stable-iso.sh does the same thing as build-iso.sh, but configures the kernel so that the version does not show the commit hash (used for stable versions).

tools/rebuild-iso.sh will do a clean rebuild, install, and make an ISO disk image.

In most cases, you should just use run.sh, but if you want to build without running, build-iso.sh.

Running

You should have QEMU installed.

You can choose between 3 run scripts:

tools/run.sh is the one you should use in most cases. It will build changed files, install, make an ISO image, and run Luna in QEMU.

tools/rebuild-and-run.sh will rebuild, install, make an ISO, and run Luna in QEMU.

tools/debug.sh will run Luna in QEMU with a port open for GDB to connect to. (run tools/build-debug.sh, tools/gdb.sh, and then tools/debug.sh in a separate terminal for an optimal debugging experience)

Essentially, since run.sh builds the toolchain if it hasn't been built, builds Luna if it hasn't been built, and runs it, you could just checkout this repo, run run.sh, and you're done. No need for the other scripts. Those are included for more fine-grained control/building step-by-step.

You can pass any arguments you want to the run scripts, and those will be forwarded to QEMU. Example: tools/run.sh -m 512M -net none -machine q35.

Prebuilt images

Prebuilt ISO images (numbered) for every version can be found at pub.cloudapio.eu.

These images are built manually whenever I decide to make a new version, and thus don't reflect the latest changes on the main branch.

Every hour, my server pulls the latest commits on main and builds an hourly ISO image. The ten most recent ones can be found in the hourly directory, and Luna-latest.iso should always be symlinked to the newest one.

These images do reflect the latest changes on the main branch, but are obviously less stable. Additionally, an hourly image will be skipped if building the latest commit of the project fails.

Is there third-party software I can use on Luna?

Not right now, but hopefully we can start porting some software soon!

License

Luna is open-source and free software under the BSD-2 License.