Annvix:Documentation
|
This page contains content from the old Annvix.org wiki and has been moved here to preserve content. These pages have been retained for historical and nostalgic purposes only. |
Documentation
The Annvix Documentation is the official documentation for Annvix. It will cover various topics such as installation, configuration, etc. You may also wish to view the User Guide for further documentation.
Contents |
HOWTO's and Other Tutorials
- IPSec Working Configuration for Starters
- Configuring Serial Connection Support
- A urpmi user's guide to apt
- Writing run scripts with execline
- Installing and using nagios on Annvix
- Getting started with Squid
- Using your Annvix server as a Router
- Providing iSCSI targets
Frequently Asked Questions
Developer's Reference
The Annvix Developer's Reference is a currently in-progress work that will aim to cover all aspects of development for Annvix.
The document will aim to cover all procedures and resources required and available for individuals who currently maintain or wish to maintain Annvix packages. It is not a formal policy document, however, but rather it is a collection of generally agreed-upon best practices.
Due to some recent attacks on Linux vendor systems such as Debian and Gentoo, Annvix needs to have a clear policy indicating what is permissible and what is not by our developers. All developers, before obtaining commit access to the Annvix repositories, will be required to formally indicate their acceptance of acceptable behavior regarding the Annvix project.
As well, these recent attacks may shake the confidence in the vendors who were compromised. Because Annvix will follow a transparent development process, it is important that users and maintainers understand the development process and what steps are being taken to prevent tampering with the Annvix repositories.
By providing a strong and secure development process, we believe that we can avoid potential problems. This is not to infer that the development process of other Linux distributions is by any means inferior. On the contrary! We believe that both the Debian and Gentoo teams handled the compromises in an effective and professional manner. As a result of these problems, however, we have had to rethink the design of developer access to the repositories.
Because the project is still in the planning and development stages, these processes are subject to change.
