Not logged in

NextGen LinuxOS - Hydra Architecture

"Hydra Lernaia was a gigantic, nine-headed water-serpent, which haunted the swamps of Lerna. Herakles was sent
to destroy her as one of his twelve labours, but for each of her heads that he decapitated, two more sprang forth."

1. Development Tools
1.1 Introduction
1.2 Programming with Lua and or C++
1.3 Working with Premake
1.4 Bmake
1.5 Debugging
1.6 Using Fossil (DVCS)
1.7 Further Reading

2. Packages and Patches
2.1 Introduction
2.2 All Programs
2.3 All Packages
2.4 Needed Patches

3. System Preparation
3.1 Introduction

4. Constructing the Cross-Compile Toolchain
4.1 Introduction
4.2 C Compiler Flags
4.3 Kernel Headers
4.4 Build Variables
4.5 Cross ElfToolChain
4.6 Cross Clang
4.7 Musl Libc

5. Installing Basic System Software
5.1 Introduction
5.2 Installing Coreutils
5.3 Installing Libc
5.4 Installing Process Monitor

6. Installing Development Software
6.1 Introduction

7. Designing a Package Manager
7.1 Introduction
7.2 Package Specification File

8. Installing Desktop Development Software
8.1 Introduction

9. Hydra Graphics Engine
9.1 Introduction
9.2 Declarative Markup Language
9.3 Path Rendering
9.4 Linear Incremental Constraint Solver
9.5 SceneGraph

What is the Hydra Architecture

The Hydra Architecture is a system development framework "

Our Vision

An ecosystem where "Open Source" and "Proprietary" software work's together, in an effort to build the best possible platform for current and future generation's of users.

Hydra Architectural Guidelines

When targeting Linux as a platform, application developers want to have some assurance that the code they write on one Linux distribution will run on other Linux distributions without having to go through extra effort. This matches their experiences on other popular platforms, such as Windows or Mac OS X.

In addition, application developers want to ensure that the platform as a whole does not diverge. Even if an application works on today's distributions, will it work on tomorrow's?

The Hydra Architecture has, as its core goal, to address these two concerns. We publish a standard that describes the minimum set of APIs a distribution must support. We also provide tests and tools which measure support for the standard, and enable application developers to target the common set. Finally, through our testing work, we seek to prevent unnecessary divergence between the distributions.

Understanding the Custom Filesystem Hierarchy Standard(CFHS)

Lorem Ipsum is simply dummy text of the printing and typesetting industry. Lorem Ipsum has been the industry's standard dummy text ever since the 1500s, when an unknown printer took a galley of type and scrambled it to make a type specimen book. It has survived not only five centuries, but also the leap into electronic typesetting, remaining essentially unchanged. It was popularised in the 1960s with the release of Letraset sheets containing Lorem Ipsum passages, and more recently with desktop publishing software like Aldus PageMaker including versions of Lorem Ipsum.

To be done.