Long-Term Supported Versions

    Innovation Versions

      Installation and Deployment

      Currently, devmaster can be used in the VM environment where sysmaster is used as PID 1. This section describes the requirements and procedure of devmaster installation and deployment.

      Software

      • OS: openEuler 22.03 LTS SP3

      Hardware

      • x86_64 or AArch64 architecture

      Installation and Deployment

      1. Run the following yum command to install the devmaster package:

        # yum install devmaster
        
      2. The devmaster package includes a service configuration file for sysmaster. After the package is installed, devmaster overwrites udev services and will be started by sysmaster upon startup. After the devmaster package is uninstalled, udev services are restored automatically.

      3. Restart the system.

      4. Check the /run/devmaster/data/ directory. If the device database file is generated, the deployment is successful.

        # ll /run/devmaster/data/
        

      Bug Catching

      Buggy Content

      Bug Description

      Submit As Issue

      It's a little complicated....

      I'd like to ask someone.

      PR

      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.

      How satisfied are you with this document

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