Skip to content
This repository has been archived by the owner on Sep 11, 2024. It is now read-only.

Latest commit

 

History

History
130 lines (99 loc) · 7.45 KB

README.md

File metadata and controls

130 lines (99 loc) · 7.45 KB
Raw

duckOS

A hobby UNIX-like OS with a graphical window manager and applications for x86 PCs, with a work-in-progress aarch64 port.

duckOS

Screenshot

Demo | Features | Apps | Ports | How to Build

On Hold

Development of duckOS is currently on hold. Feel free to fork it and mess around with it though!

Try duckOS

Virtualize locally

A recent release can be downloaded from the releases page. Alternatively, a disk image of the latest duckOS can be downloaded from the artifacts of the duckOS GitHub workflow. This can then be virtualized or emulated using QEMU or your software of choice.

Emulate in the browser

Alternatively, thanks to the v86 project by copy, you can try a version of duckOS in your browser. This is a lot slower running it locally, and does not have copies of ported software like DOOM. You can try it here!

Features

  • A window manager / compositor plus a themable view-based UI toolkit for creating apps
  • A basic TCP/UDP over IP networking stack with unix sockets and an E1000 ethernet driver
  • Sound support for AC97 sound cards
  • Many ports of programs like DOOM, utilities like GCC, and libraries like SDL
  • Dynamic linking and loading of binaries
  • On-board debugging capabilities like ptrace and a sampling profiler
  • A software 3D rendering library
  • Runs on some real hardware
  • A WIP aarch64 port that boots past stage 1 on a raspberry pi 3b :)

Future plans

  • Finish aarch64 port
  • Revamp kernel IPC system to be more efficient
  • Better font rendering (Vector fonts, different sizes, etc.)
  • self-host
  • More s t a b i l i t y and s p e e d
  • A better filesystem cache implementation that can free memory when needed and periodically flushes writes
  • More kernel & userspace unit tests
  • Better documentation of kernel, libraries, and applications
  • Some more kernel & userspace debugging tools so I don't have to spend hours knee-deep in the qemu debugger whenever a segfault happens due to a simple bug that could've been avoided with some extra coffee in my system
  • Multiprocessor (multicore) support
  • Slowly transition various modules from the kernel to userspace (a la microkernel)
  • Add Rust into the mix (?)

Services

The code for these can be found in services.

  • Init (/bin/init): The init system for duckOS.
  • Pond (/bin/pond): The window manager / compositor for duckOS.
  • Quack (/bin/quack): The sound server for duckOS.
  • DHCP Client (/bin/dhcpclient): A DHCP client for assigning an IP address.

Apps

The code for these can be found in programs/applications.

  • Calculator (/apps/calculator.app): A basic calculator.
  • Terminal (/apps/terminal.app): A libui-based terminal application.
  • System Monitor (/apps/monitor.app): A basic system monitor showing memory and CPU utilization.
  • 4 In a Row (/apps/4inarow.app): A basic four-in-a-row game. Play with two players or against the computer.
  • Sandbar (/bin/sandbar): A basic "taskbar" that displays a row of buttons at the bottom of the screen to launch applications.
  • Files (/apps/files.app): A rudimentary file explorer application.
  • Viewer (apps/viewer.app): A basic media viewer that can view images and play sound files
  • Lib3d Demo (apps/3demo.app): A demo for the lib3d library. Displays a cube by default; can be used to view obj files.
  • Editor (/apps/editor.app): A basic app to edit text files.
  • About (/apps/about.app): Shows some system information.
  • Ducksweeper (/apps/ducksweeper.app): A grid-based duck avoidance game ;)

CLI Programs

The code for these can be found in programs/coreutils. Alongside the usual suspects, duckOS has:

  • dsh (/bin/dsh): A basic shell with support for piping, redirections, and command recall.
  • open (/bin/open): A utility to open files and applications from the command line using the appropriate program.
  • play (/bin/play): Plays audio files.
  • date (/bin/date): Shows the date and time.
  • profile (/bin/profile): Profiles a running application and outputs a FlameGraph / SpeedScope compatible file.
    • You can run scripts/debugd.py on the host (with speedscope installed) and pass the -r parameter to profile to send the output directly to the host via networking and open it in speedscope.

Programs that take arguments will provide you with the correct usage when you run them without arguments.

Libraries

  • libc: The standard C library.
  • libm: The math portion of the standard C library.
  • libpond: The library used for interfacing with the pond window manager / compositor.
  • libgraphics: A library which provides a few utilities for working with graphics such as image format loading.
  • libui: A UI framework for applications.
  • libtui: A framework for terminal applications.
  • libterm: A framework for handling terminals.
  • libduck: A library containing commonly used classes and utilities, such as argument and configuration file parsing.
  • libriver: An IPC library not dissimilar to D-Bus, which provides a framework for remote function calls and data passing.
  • libapp: A library providing methods to retrieve information about installed and running applications.
  • libsys: Provides higher-level C++ abstractions for retrieving system information, namely from procFS.
  • libsound: Provides a framework for audio applications and interfacing with the sound server, Quack.
  • lib3d: Provides basic software 3D rendering functionality.
  • libmatrix: Provides matrix math utilities.
  • libexec: Provides ELF support.
  • libdebug: Provides debugging functionality.

Ports

Ports can be installed by running ports.sh supplied with the desired port as an argument. The required dependencies will also be built and installed.

Some of the more exciting ports are:

Building / Running

Contributing

Credits

License