Innovation Version

      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


      1. openEuler 22.03 LTS SP2 has been installed.
      2. root permissions are required for patch making.

      Installing Dependencies

      The kernel source code and kpatch are required during SysCare patch making. Related dependencies need to be installed.

      yum install -y kernel-source-`uname -r` kernel-debuginfo-`uname -r` kernel-devel-`uname -r`
      yum 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

      Installing from Source

      Clone the SysCare source code and then compile and install SysCare as follows:

      git clone
      cd syscare
      mkdir tmp
      cd tmp
      cmake -DCMAKE_INSTALL_PREFIX=/usr -DKERNEL_VERSION=$(uname -r) ..
      make install

      Installing SysCare from a Repository

      If the repository source 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.


      ● Incorrect or missing key steps;

      ● Missing prerequisites or precautions;

      ● Ambiguous figures, tables, or texts;

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


      ● 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.

      How satisfied are you with this document

      Not satisfied at all
      Very satisfied
      Click to create an issue. An issue template will be automatically generated based on your feedback.
      Bug Catching
      编组 3备份