> ## Documentation Index
> Fetch the complete documentation index at: https://mintlify.com/redox-os/redox/llms.txt
> Use this file to discover all available pages before exploring further.

# FAQ

> Frequently asked questions about Redox OS

## General Questions

<AccordionGroup>
  <Accordion title="What is Redox OS?">
    Redox is an open-source operating system written in Rust, a language with focus on safety, efficiency, and high performance. Redox uses a microkernel architecture and aims to be reliable, secure, usable, correct, and free. Redox is inspired by previous operating systems such as seL4, MINIX, Plan 9, Linux, and BSD.

    Redox is not just a kernel - it's a **full-featured operating system**, providing components (file system, display server, core utilities, etc.) that together make up a functional and convenient operating system. Redox uses the COSMIC desktop apps and provides source code compatibility with many Rust, Linux, and BSD programs.
  </Accordion>

  <Accordion title="What license does Redox use?">
    In general, contributions to Redox are governed by the [MIT License](https://en.wikipedia.org/wiki/MIT_License). Each project repository has a `LICENSE` file that provides the license terms for that specific project.

    The MIT license is used because it provides maximum freedom for developers while maintaining open source principles. See the [Philosophy](https://doc.redox-os.org/book/philosophy.html) page for more details on this choice.
  </Accordion>

  <Accordion title="What hardware does Redox support?">
    Redox supports x86-64 and i686 architectures, with experimental ARM64 support. However, hardware support varies:

    **Currently Supported:**

    * BIOS and UEFI firmware
    * PS/2 and USB input devices
    * Intel integrated graphics (via VESA/GOP)
    * Ethernet adapters (varies by model)
    * HDA audio (on supported hardware)

    **Not Yet Supported:**

    * Wi-Fi and Bluetooth
    * AMD, NVIDIA, ARM, and PowerVR GPUs (only BIOS VESA and UEFI GOP)
    * I2C devices (including many laptop touchpads)

    For detailed hardware compatibility, see the [Hardware Compatibility](https://doc.redox-os.org/book/hardware-support.html) page.
  </Accordion>

  <Accordion title="Is Redox a Linux distribution?">
    No, Redox is a completely independent operating system with its own kernel, not a Linux distribution. While Redox provides source code compatibility with many Linux programs through its C library (relibc), it has a unique microkernel architecture and is written entirely in Rust.
  </Accordion>
</AccordionGroup>

## Development

<AccordionGroup>
  <Accordion title="How do I build Redox?">
    Building Redox requires a Linux, macOS, or BSD system (or WSL on Windows). Follow these steps:

    1. Download the bootstrap script:

    ```sh theme={null}
    curl -sf https://gitlab.redox-os.org/redox-os/redox/raw/master/podman_bootstrap.sh -o podman_bootstrap.sh
    ```

    2. Run the bootstrap:

    ```sh theme={null}
    time bash -e podman_bootstrap.sh
    ```

    3. Build the system:

    ```sh theme={null}
    make all
    ```

    For systems without SELinux:

    ```sh theme={null}
    make all USE_SELINUX=0
    ```

    See the [Building Redox](https://doc.redox-os.org/book/podman-build.html) guide for complete instructions.
  </Accordion>

  <Accordion title="Can I contribute without knowing Rust?">
    Yes! There are many ways to contribute:

    **Without programming knowledge:**

    * Test Redox on your hardware and report compatibility
    * Write or improve documentation
    * Report bugs and feature requests
    * Help with graphic design (logos, icons, wallpapers)

    **With other programming languages:**

    * Web development for the website
    * Port C/C++ programs to Redox
    * Write unit tests

    See the [Contributing Guide](https://gitlab.redox-os.org/redox-os/redox/-/blob/master/CONTRIBUTING.md) for more ways to help.
  </Accordion>

  <Accordion title="What is the AI policy for contributions?">
    Redox OS does **not accept contributions generated by LLMs** (Large Language Models), sometimes also referred to as "AI". This policy is not open to discussion. Any content submitted that is clearly labeled as LLM-generated (including issues, merge requests, and merge request descriptions) will be immediately closed, and any attempt to bypass this policy will result in a ban from the project.
  </Accordion>

  <Accordion title="How do I port software to Redox?">
    Software is ported to Redox using the Cookbook recipe system. The general process:

    1. Check if a recipe already exists to avoid duplication
    2. Create a recipe file defining the build process
    3. Test the build and runtime on Redox
    4. Submit a merge request

    See the [Application Porting](https://doc.redox-os.org/book/porting-applications.html) guide for detailed instructions.

    <Note>
      If a program can't build, something may be missing in [relibc](https://gitlab.redox-os.org/redox-os/relibc), such as a POSIX/Linux function or there may be a bug.
    </Note>
  </Accordion>

  <Accordion title="Where can I find development documentation?">
    Key documentation resources:

    * [The Redox Book](https://doc.redox-os.org/book/) - Comprehensive guide
    * [Build System Reference](https://doc.redox-os.org/book/build-system-reference.html)
    * [Developer FAQ](https://doc.redox-os.org/book/developer-faq.html)
    * [Libraries and APIs](https://doc.redox-os.org/book/libraries-apis.html)
    * [References](https://doc.redox-os.org/book/references.html) - Learning resources for Rust and OS development
  </Accordion>
</AccordionGroup>

## Contributing

<AccordionGroup>
  <Accordion title="How do I submit changes?">
    Redox uses GitLab for code hosting and collaboration:

    1. Create a GitLab account (see [Signing in to GitLab](https://doc.redox-os.org/book/signing-in-to-gitlab.html))
    2. Fork the relevant repository
    3. Make your changes following the [style guidelines](https://doc.redox-os.org/book/creating-proper-pull-requests.html)
    4. Submit a merge request
    5. Post the MR link in the [MRs Matrix room](https://matrix.to/#/#redox-mrs:matrix.org)

    <Tip>
      For quick reviews, keep merge requests small. Large MRs take longer to review and may need to be split into smaller ones.
    </Tip>
  </Accordion>

  <Accordion title="What are the contribution terms?">
    When making a contribution, you agree to:

    * I (the contributor) am the copyright owner of these changes
    * I submit these changes according to the project's license with no additional requirements
    * I understand these changes in full and will be able to respond to review comments

    This is similar to the [Developer Certificate of Origin](https://developercertificate.org/) from the Linux Foundation.
  </Accordion>

  <Accordion title="What should I work on?">
    Based on your skill level:

    **Beginner-friendly:**

    * [Good first issue](https://gitlab.redox-os.org/groups/redox-os/-/issues/?label_name\[]=good%20first%20issue) issues
    * [Easy](https://gitlab.redox-os.org/groups/redox-os/-/issues/?label_name\[]=easy) issues
    * Documentation improvements
    * Testing and bug reports

    **Intermediate:**

    * [Help wanted](https://gitlab.redox-os.org/groups/redox-os/-/issues/?label_name\[]=help%20wanted) issues
    * Porting applications
    * Improving relibc compatibility

    **Advanced:**

    * [Critical](https://gitlab.redox-os.org/groups/redox-os/-/issues/?label_name\[]=critical) and [high-priority](https://gitlab.redox-os.org/groups/redox-os/-/issues/?label_name\[]=high-priority) issues
    * Kernel development
    * Device drivers
    * Performance optimization

    See the [Contributing Guide](https://gitlab.redox-os.org/redox-os/redox/-/blob/master/CONTRIBUTING.md) for the complete list.
  </Accordion>

  <Accordion title="How should I format my Git commits?">
    Follow the [Git style](https://doc.redox-os.org/book/creating-proper-pull-requests.html) guidelines. Run `rustfmt` on Rust code changes to ensure consistent formatting.
  </Accordion>
</AccordionGroup>

## Community

<AccordionGroup>
  <Accordion title="Where can I get help?">
    See the [Community](/reference/community) page for all chat platforms and support channels.
  </Accordion>

  <Accordion title="How do I report bugs?">
    1. Search [existing issues](https://gitlab.redox-os.org/groups/redox-os/-/issues) to check for duplicates
    2. Create a new issue on the appropriate repository
    3. Include:
       * System information (OS, Redox version)
       * Steps to reproduce
       * Complete error logs
    4. Post the issue link in the Dev or Support chat rooms

    See the [Filing Issues](https://doc.redox-os.org/book/filing-issues.html) guide for details.
  </Accordion>

  <Accordion title="Can I donate to support Redox?">
    Yes! You can support Redox development through:

    * [Patreon](https://www.patreon.com/redox_os)
    * [Direct donations](https://redox-os.org/donate/)
    * [Merchandise](https://redox-os.creator-spring.com/)

    For more information, see the [Donate](https://www.redox-os.org/donate/) page.
  </Accordion>
</AccordionGroup>

## Additional Resources

For more questions, see:

* [Developer FAQ](https://doc.redox-os.org/book/developer-faq.html) - Technical development questions
* [General FAQ](https://www.redox-os.org/faq/) - High-level project questions
* [Troubleshooting](/reference/troubleshooting) - Solutions to common problems