Documentation FAQ
Frequently asked questions about using ProteanOS.
Frequently Asked Questions
What is ProteanOS?
ProteanOS is a free, open-source embedded operating system designed for flexibility and portability across embedded platforms.
Is ProteanOS free to use?
Yes, ProteanOS is free software. It is distributed under free software licenses that grant you the freedom to use, study, modify, and distribute the software.
Where can I get support?
Community support is available through the development mailing list. Check the mailing list archives for existing discussions or post your question.
Installation Questions
Frequently Asked Questions
What are the system requirements?
Requirements vary by target platform. Generally, you need a supported architecture, sufficient storage for the root filesystem, and appropriate boot configuration.
Can I dual-boot ProteanOS?
On platforms with bootloader support, you can configure multi-boot setups. The specific procedure depends on your hardware and existing operating system.
How do I update my installation?
Use the package management tools (opkg) to update installed packages. The update process fetches package lists from configured repositories and upgrades available packages.
Platform Support
Frequently Asked Questions
Which architectures are supported?
ProteanOS supports ARM architectures including Cortex-A8. Support for additional architectures may be available or in development — check the documentation for current status.
Can I port ProteanOS to my device?
Yes, the porting guide documents the process for adding support for new platforms. You need knowledge of your target hardware and familiarity with embedded development.
What bootloaders are supported?
ProteanOS can work with various bootloaders depending on the platform. U-Boot is commonly used on ARM devices. Consult platform-specific documentation.
Troubleshooting
Frequently Asked Questions
The system won't boot — what should I check?
Verify bootloader configuration, check that the kernel and rootfs are properly installed, and ensure storage device paths are correct. Serial console output often provides diagnostic information.
Package installation fails — how do I resolve this?
Check network connectivity, verify repository configuration, and ensure sufficient storage space. Dependency conflicts may require resolving package version issues.
How do I report a bug?
Report bugs on the development mailing list. Include the affected component, steps to reproduce, expected vs actual behavior, and relevant log output.
More Help
If your question isn't answered here, you can:
- Check the full documentation
- Search the development mailing list archives
- Ask on the mailing list — posting guidelines