Usage Instructions

Overview

Root permissions are required for using and configuring sysBoost.
Only one sysBoost instance can exist.
The system administrator must ensure the configuration file is correct.

Configuration

Configuration File Description

Configuration file directory: /etc/sysboost.d/

Table 1 Client YAML configuration file

Item	Description	Type	Value Range
elf_path	ELF file to be combined	String	ELF path supported by sysBoost
mode	sysBoost running mode	String	"static"
libs	Dependency library of the ELF file specified by elf_path. This is optional because sysBoost can automatically detects dependency libraries.	String	Path of the dependent library of the ELF file supported by sysBoost

Configuration Example

sysBoost TOML configuration file example:

# /etc/sysboost.d/bash.toml
elf_path = "/usr/bin/bash"
mode = "static-nolibc"
libs = ["/usr/lib64/libtinfo.so.6"]

Usage

Start sysBoost.
```
systemctl start sysboost.service
```
Stop sysBoost.
```
systemctl stop sysboost.service
```
Query sysBoost status. If there is no text in red, sysBoost is running normally.
```
systemctl status sysboost.service
```
View logs. If sysBoost fails, see the system logs for details.
```
cat /var/log/messages
```

Bug Catching

Buggy Content

Bug Description

Submit As Issue

It's a little complicated....

I'd like to ask someone.

Just a small problem.

I can fix it online!

Bug Type

Specifications and Common Mistakes

● Misspellings or punctuation mistakes;

● Incorrect links, empty cells, or wrong formats;

● Chinese characters in English context;

● Minor inconsistencies between the UI and descriptions;

● Low writing fluency that does not affect understanding;

● Incorrect version numbers, including software package names and version numbers on the UI.

Usability

● Incorrect or missing key steps;

● Missing prerequisites or precautions;

● Ambiguous figures, tables, or texts;

● Unclear logic, such as missing classifications, items, and steps.

Correctness

● Technical principles, function descriptions, or specifications inconsistent with those of the software;

● Incorrect schematic or architecture diagrams;

● Incorrect commands or command parameters;

● Incorrect code;

● Commands inconsistent with the functions;

● Wrong screenshots.

Risk Warnings

● Lack of risk warnings for operations that may damage the system or important data.

Content Compliance

● Contents that may violate applicable laws and regulations or geo-cultural context-sensitive words and expressions;

● Copyright infringement.

We may contact you through email in regard to the bug fixing solution. You will also be notified through email if you win any prize during the activity.