7d2a6f2d99
* Instead of fork()ing, which leaks memory (and runs a second BApplication inside the Run() of the original one, which was the source of a TODO), use posix_spawn to start a second process altogether. * Move session initialization code to the new user_main(), invoked from main() if we are starting a user session. * Send event registration messages to the new session daemon in _HandleRegisterSessionDaemon, as the child no longer has access to the old events list from before fork()ing and must receive it. The last of these fixes a race: previously, if an event was registered or triggered between when the child (user) launch_daemon was fork()ed off the parent and when it registered with the root launch_daemon, those events were "lost" and would never be forwarded to the child. That happened not altogether infrequently for some people (myself included) especially in virtual machines for the "initial_volumes_mounted" event, which was the most common remaining cause of "boot hangs on rocket" or "boots to blue screen with only mouse cursor" problems. So, in addition to being cleaner overall and resolving a number of TODOs, this also fixes #17365. Change-Id: I1ea28cba8938a38b3c27685d7f3943f596cfe7ec Reviewed-on: https://review.haiku-os.org/c/haiku/+/4968 Reviewed-by: waddlesplash <waddlesplash@gmail.com> Reviewed-by: Alex von Gluck IV <kallisti5@unixzen.com> Tested-by: Commit checker robot <no-reply+buildbot@haiku-os.org>
Haiku
Homepage | Mailing Lists | IRC Channels | Issue Tracker | API docs
Haiku is an open-source operating system that specifically targets personal computing. Inspired by the BeOS, Haiku is fast, simple to use, easy to learn and yet very powerful.
Goals
- Sensible defaults with minimal configuration required.
- Clean, clear, concise code.
- Unified desktop environment.
Trying Haiku
Haiku provides pre-built nightly images and release images. Haiku is compatible with a large variety of hardware, but in case you don't want to "take the plunge" and install Haiku on bare metal, you can install it on a virtual machine (VM) instead. If you've never used a VM before, you can follow one of the "Emulating Haiku" guides.
Compiling Haiku
See ReadMe.Compiling.
Contributing
Haiku is a meritocratic open source project with a large variety of tasks. Even if you can't write code, you can still help! Haiku needs designers, (technical) writers, translators, testers... Get involved and help out!
Contributing code
If you're submitting a patch to us, please make sure you're following the patch submitting guidelines.
If you're having trouble finding something in the source tree, you can use one of our web-based source code browsers:
- https://xref.landonf.org/ (OpenGrok, provided by Landon Fuller)
- https://git.haiku-os.org/ (git, provided by Haiku, Inc.)
Contributing documentation
The main piece of documentation that still needs work are the API docs (found
in the tree at docs/user). Just find an undocumented class, write
documentation for it, and submit a patch.
Contributing translations
See wiki:i18n.
Contributing software ports
See HaikuPorts.
Contributing to our infrastructure
See Infrastructure.