The goal here is to generate most of this code from IPC protocol descriptions, but for now I've spelled them all out to get started. Each message gets a wrapper class in the ASAPI_Client or ASAPI_Server namespace. They are convertible to and from the old message structs. The real hotness happens when you want to make a synchronous request to the other side: auto response = send_sync<ASAPI_Client::GetMainMixVolume>(); Each request class knows his corresponding response class, so in the above example, "response" will be an ASAPI_Server::DidGetMainMixVolume object, and we can get the volume like so: int volume = response.volume(); For posting messages that don't expect a response, you can still use post_message() since the message classes are convertible: post_message(ASAPI_Server::DidGetMainMixVolume(volume)); It's not perfect yet, but I already really like it. :^) |
||
---|---|---|
AK | ||
Applications | ||
Base | ||
Demos | ||
DevTools | ||
Documentation | ||
Games | ||
Kernel | ||
Lagom | ||
Libraries | ||
Meta | ||
Ports | ||
Servers | ||
Shell | ||
Toolchain | ||
Userland | ||
.clang-format | ||
.gitignore | ||
.travis.yml | ||
Contributing.md | ||
LICENSE | ||
Makefile.common | ||
ReadMe.md |
Serenity
Graphical Unix-like operating system for x86 computers.
About
I always wondered what it would be like to write my own operating system, but I never took it seriously. Until now.
Serenity is a love letter to '90s user interfaces with a custom Unix-like core. It flatters with sincerity by stealing beautiful ideas from various other systems.
Roughly speaking, the goal is a marriage between the aesthetic of late-1990s productivity software and the power-user accessibility of late-2000s *nix. This is a system by me, for me, based on the things I like.
If you like some of the same things, you are welcome to join the project. It would be great to one day change the above to say "this is a system by us, for us, based on the things we like." :^)
I regularly post raw hacking sessions and demos on my YouTube channel.
Sometimes I write about about the system on my github.io blog.
There's also a Patreon if you would like to show some support that way.
Screenshot
Current features
- Pre-emptive multitasking
- Multithreading
- Compositing window server
- IPv4 networking with ARP, TCP, UDP and ICMP
- ext2 filesystem
- Unix-like libc and userland
- POSIX signals
- Shell with pipes and I/O redirection
- mmap()
- /proc filesystem
- Local sockets
- Pseudoterminals (with /dev/pts filesystem)
- JSON framework
- Low-level utility library (LibCore)
- High-level GUI library (LibGUI)
- Visual GUI design tool
- PNG format support
- Text editor
- IRC client
- Simple painting application
- DNS lookup
- Desktop games: Minesweeper and Snake
- Ports system (needs more packages!)
- Other stuff I can't think of right now...
How do I build and run this?
Make sure you have all the dependencies installed:
sudo apt install libmpfr-dev libmpc-dev libgmp-dev e2fsprogs qemu-system-i386 qemu-utils
Go into the Toolchain/
directory and run the BuildIt.sh script. Then source the UseIt.sh script to put the i686-pc-serenity
toolchain in your $PATH
.
Once you've done both of those, go into the Kernel/
directory, then run
./makeall.sh, and if nothing breaks too much, take it for a spin by using
./run.
Later on, when you git pull
to get the latest changes, there's no need to rebuild the toolchain. You can simply rerun ./makeall.sh in the Kernel/
directory and you'll be good to ./run again.
IRC
Come chat in #serenityos
on the Freenode IRC network.
Author
- Andreas Kling - awesomekling
Contributors
- Robin Burchell - rburchell
Feel free to append yourself here if you've made some sweet contributions. :)
License
Serenity is licensed under a 2-clause BSD license.