Installing SysCare

This chapter describes how to install SysCare on openEuler.

Installing SysCare Core Components

Minimum Hardware Requirements

2 CPUs (x86_64 or AArch64)
4 GB memory
100 GB drive

Prerequisites

openEuler 22.03 LTS SP3 has been installed.
root permissions are required for patch making.

Installing from Source

Clone the SysCare source code https://gitee.com/openeuler/syscare.git and then compile and install SysCare as follows:

dnf install -y kernel-source-`uname -r` kernel-debuginfo-`uname -r` kernel-devel-`uname -r`
dnf install -y elfutils-libelf-devel openssl-devel dwarves flex python3-devel rpm-build bison cmake make gcc g++ rust cargo bpftool clang libbpf libbpf-devel llvm libbpf-static

git clone https://gitee.com/openeuler/syscare.git
cd syscare
mkdir build_tmp
cd build_tmp
cmake -DCMAKE_INSTALL_PREFIX=/usr ..
make
make install

Installing SysCare from a Repository

The repository of openEuler 22.03 LTS SP3 contains SysCare packages. You can use the dnf or yum command to download and install them.

dnf install syscare syscare-build

Uninstalling SysCare

dnf remove syscare*

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.