> For the complete documentation index, see [llms.txt](https://newmishka.gitbook.io/newmishka-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://newmishka.gitbook.io/newmishka-docs/nachalo-raboty/ustanovka.md).

# Установка

## Текущий `main`

```bash
git clone https://github.com/NewMishka/arm_info.git
cd arm_info
sudo bash arm_info.sh
```

Этот вариант устанавливает текущее состояние ветки `main`, где могут находиться ещё не выпущенные изменения.

## Stable release

Последний опубликованный релиз — **v1.3.0**. Для воспроизводимой установки конкретного релиза можно использовать tag:

```bash
git clone --branch v1.3.0 --depth 1 https://github.com/NewMishka/arm_info.git
cd arm_info
sudo bash arm_info.sh
```

Release assets также доступны на странице GitHub Releases.

## Установка системной команды

```bash
sudo bash install.sh
sudo arm_info
```

Начиная с версии **1.2.1**, базовая и корпоративная диагностика находятся в одном `arm_info.sh`. Отдельный enterprise-helper не требуется.

## Рекомендуемые зависимости для полной диагностики

```bash
sudo dnf install smartmontools dmidecode lm_sensors
```

Для корпоративных профилей дополнительно полезны: `sssd-tools`, `adcli`, `krb5-workstation`, `bind-utils`, `NetworkManager`, `openssl`, `cups-client`, `nc` / `nmap-ncat`.

`python3` нужен для сравнения JSON и безопасного разбора статических autofs-карт.

## Проверка release asset

Production release публикует `arm_info.sh` и `SHA256SUMS`:

```bash
sha256sum -c SHA256SUMS
```

{% hint style="warning" %}
Для максимально полного отчёта часть проверок требует root. Сам скрипт предназначен для диагностики; команды, способные изменить состояние системы, в рекомендациях отдельно помечаются.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://newmishka.gitbook.io/newmishka-docs/nachalo-raboty/ustanovka.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.