7a7e7c82b5
This patch changes how exec() figures out which program image to actually load. Previously, we opened the path to our main executable in find_shebang_interpreter_for_executable, read the first page (or less, if the file was smaller) and then decided whether to recurse with the interpreter instead. We then then re-opened the main executable in do_exec. However, since we now want to parse the ELF header and Program Headers of an elf image before even doing any memory region work, we can change the way this whole process works. We open the file and read (up to) the first page in exec() itself, then pass just the page and the amount read to find_shebang_interpreter_for_executable. Since we now have that page and the FileDescription for the main executable handy, we can do a few things. First, validate the ELF header and ELF program headers for any shenanigans. ELF32 Little Endian i386 only, please. Second, we can grab the PT_INTERP interpreter from any ET_DYN files, and open that guy right away if it exists. Finally, we can pass the main executable's and optionally the PT_INTERP interpreter's file descriptions down to do_exec and not have to feel guilty about opening the file twice. In do_exec, we now have a choice. Are we going to load the main executable, or the interpreter? We could load both, but it'll be way easier for the inital pass on the RTLD if we only load the interpreter. Then it can load the main executable itself like any old shared object, just, the one with main in it :). Later on we can load both of them into memory and the RTLD can relocate itself before trying to do anything. The way it's written now the RTLD will get dibs on its requested virtual addresses being the actual virtual addresses. |
||
|---|---|---|
| .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.