* Rewrite most hook functions, modeling many after FreeBSD hooks and making use of support functions ported from FreeBSD. As it stands now, most of the FreeBSD driver files are present with minimal changes, with a pseudo-BSD compatability layer added to make them work in Haiku. Performance is not what it could be if the BSD code was rewritten to interface directly with the Haiku kernel, but under the current approach the driver might be easier to maintain in terms of porting future FreeBSD bugfixes. * Add support for FAT in userlandfs. Aside from being useful for debugging, the userlandfs module provides better filename support for characters that are not in code page 850, because it can link libiconv. * Update the fat_test.sh script to use dosfstools to format the tested device, instead of the internal dosfs_initialize hook. The script is written to test specific cluster sizes, but the initialize hook still does not support user-specified cluster sizes. * Coding guidelines: lightly-modified BSD files and lightly-modified original Haiku driver files have not been revised to adhere to the Haiku style guidelines. For BSD files, this is meant to make it easier to compare with the FreeBSD repository when merging future FreeBSD patches. For existing driver files, this is to highlight the functional changes made in this change request (I can submit a separate patch later to clean up style in these files). Also, some #include lines are not alphbetized (they are instead ordered like they would be in FreeBSD, because one header relies on another). Change-Id: I92521d4b700d7aa52fe6c664cf8f83a4d9395809 Reviewed-on: https://review.haiku-os.org/c/haiku/+/7660 Reviewed-by: Adrien Destugues <pulkomandy@pulkomandy.tk> Tested-by: Commit checker robot <no-reply+buildbot@haiku-os.org> Reviewed-by: Jérôme Duval <jerome.duval@gmail.com>
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.