0569123ad7
This syscall is a complement to pledge() and adds the same sort of incremental relinquishing of capabilities for filesystem access. The first call to unveil() will "drop a veil" on the process, and from now on, only unveiled parts of the filesystem are visible to it. Each call to unveil() specifies a path to either a directory or a file along with permissions for that path. The permissions are a combination of the following: - r: Read access (like the "rpath" promise) - w: Write access (like the "wpath" promise) - x: Execute access - c: Create/remove access (like the "cpath" promise) Attempts to open a path that has not been unveiled with fail with ENOENT. If the unveiled path lacks sufficient permissions, it will fail with EACCES. Like pledge(), subsequent calls to unveil() with the same path can only remove permissions, not add them. Once you call unveil(nullptr, nullptr), the veil is locked, and it's no longer possible to unveil any more paths for the process, ever. This concept comes from OpenBSD, and their implementation does various things differently, I'm sure. This is just a first implementation for SerenityOS, and we'll keep improving on it as we go. :^) |
||
---|---|---|
.github | ||
AK | ||
Applications | ||
Base | ||
Demos | ||
DevTools | ||
Documentation | ||
Games | ||
Kernel | ||
Libraries | ||
MenuApplets | ||
Meta | ||
Ports | ||
Servers | ||
Shell | ||
Tests/Kernel | ||
Toolchain | ||
Userland | ||
.clang-format | ||
.gitignore | ||
.travis.yml | ||
CODE_OF_CONDUCT.md | ||
CONTRIBUTING.md | ||
INSTALL.md | ||
LICENSE | ||
Makefile | ||
Makefile.common | ||
Makefile.subdir | ||
ReadMe.md |
SerenityOS
Graphical Unix-like operating system for x86 computers.
About
SerenityOS 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 the system on my github.io blog.
I'm also on Patreon and GitHub Sponsors if you would like to show some support that way.
Screenshot
Current features (all under development, some more mature than others)
- 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()
- Purgeable memory
- /proc filesystem
- Local sockets
- Pseudoterminals (with /dev/pts filesystem)
- Filesystem notifications
- JSON framework
- Low-level utility library (LibCore)
- Mid-level 2D graphics library (LibDraw)
- High-level GUI library (LibGUI)
- HTML/CSS engine
- Web browser
- C++ IDE
- Sampling profiler with GUI
- Emojis (UTF-8)
- HTTP downloads
- SoundBlaster 16 driver
- Software-mixing sound daemon
- WAV playback
- Simple desktop piano/synthesizer
- Visual GUI design tool
- PNG format support
- Text editor
- IRC client
- Simple painting application
- DNS lookup
- Desktop games: Minesweeper and Snake
- Color theming
- Ports system (needs more packages!)
- Other stuff I can't think of right now...
How do I build and run this?
See the SerenityOS build instructions
Wanna talk?
Come chat with us in #serenityos
on the Freenode IRC network.
Author
- Andreas Kling - awesomekling
Contributors
(And many more!) Feel free to append yourself here if you've made some sweet contributions. :)
License
SerenityOS is licensed under a 2-clause BSD license.