# Introduction

The concept behind Penguins's eggs stems from the idea of **reproduction** and **population selection** applied to operating systems.

During the era of popular remastering programs like Remastersys and Systemback, both of which experienced maintenance issues and were eventually abandoned, the need for a new, modern tool became evident. The inspiration for Penguins' Eggs led to the development of a new tool written in a modern, cross - distribution language, utilizing its own packaging system. Initially built with nodejs and later transitioning to Typescript as the primary development language, the tool's design resembles an egg production process, consisting of operations such as `produce` for creating the eggs, and other commands like `kill` for removing produced ISOs, `update` for software updates, and `install` for configuring the graphical installer.

The eggs tool is written primarily in TypeScript, Penguins' eggs is designed to be compatible with various Linux distributions, despite differences in package managers, file paths, and more. The tool currently supports Debian, Devuan, Ubuntu, Arch, Manjaro, and their derivatives, across multiple architectures including `amd64`, `i386`, and `arm64`. With the release of version 9.6.x, Penguins' eggs is now available as a Debian package, catering to a wide range of systems including PCs, older machines, and single - board ARM systems like the Raspberry Pi, across `amd64`, `i386`, and `arm64` architectures.

For more information and updates, visit the [Penguins' eggs official website](https://penguins-eggs.net).

**Penguins' eggs are generated and new birds are ready to fly...**


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://penguins-eggs.gitbook.io/book/2-introduction.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.