From 5782436f79d20fc6ff24c7a380a1e6ff41c2afea Mon Sep 17 00:00:00 2001 From: fhxing168 Date: Sat, 18 Apr 2020 18:34:48 +0800 Subject: [PATCH] Modify the spaces and figures name. --- .../configurations-during-installation.md | 2 +- ...-mode-due-to-secure-boot-option-setting.md | 2 +- .../completing-the-automatic-installation.png | Bin .../figures/completing-the-configuration.png | Bin .../figures/enforce-secure-boot.png | Bin .../figures/semi-automatic-installation.png | Bin .../full-automatic-installation-guide.md | 2 +- .../en/docs/Installation/installation-mode.md | 116 ++++++++--------- .../Installation/installation-preparations.md | 50 ++++---- .../semi-automatic-installation-guide.md | 4 +- content/en/docs/Quickstart/quick-start.md | 100 +++++++-------- ...50\243\205\345\256\214\346\210\2201-0.png" | Bin 374 -> 0 bytes ...\350\243\205\345\256\214\346\210\2201.png" | Bin 374 -> 0 bytes ...1\350\243\205\345\256\214\346\210\220.png" | Bin ...11\350\243\205\346\214\207\345\257\274.md" | 2 +- ...11\350\243\205\346\214\207\345\257\274.md" | 2 +- ...11\350\243\205\345\207\206\345\244\207.md" | 51 +++----- ...71\345\274\217\344\273\213\347\273\215.md" | 120 +++++++++--------- ...53\351\200\237\345\205\245\351\227\250.md" | 53 ++++---- 19 files changed, 247 insertions(+), 257 deletions(-) rename "content/en/docs/Installation/figures/\345\256\211\350\243\205\345\256\214\346\210\2201-0.png" => content/en/docs/Installation/figures/completing-the-automatic-installation.png (100%) rename "content/en/docs/Installation/figures/\347\273\223\346\235\237\351\205\215\347\275\256-new-en.png" => content/en/docs/Installation/figures/completing-the-configuration.png (100%) rename "content/en/docs/Installation/figures/\351\200\211\346\213\251.png" => content/en/docs/Installation/figures/enforce-secure-boot.png (100%) rename "content/en/docs/Installation/figures/\345\215\212\350\207\252\345\212\250-new.png" => content/en/docs/Installation/figures/semi-automatic-installation.png (100%) delete mode 100644 "content/zh/docs/Installation/figures/\345\256\211\350\243\205\345\256\214\346\210\2201-0.png" delete mode 100644 "content/zh/docs/Installation/figures/\345\256\211\350\243\205\345\256\214\346\210\2201.png" rename "content/en/docs/Installation/figures/\345\256\211\350\243\205\345\256\214\346\210\2201.png" => "content/zh/docs/Installation/figures/\350\207\252\345\212\250\345\214\226\345\256\211\350\243\205\345\256\214\346\210\220.png" (100%) diff --git a/content/en/docs/Installation/configurations-during-installation.md b/content/en/docs/Installation/configurations-during-installation.md index e2887ecca..f62b1c276 100644 --- a/content/en/docs/Installation/configurations-during-installation.md +++ b/content/en/docs/Installation/configurations-during-installation.md @@ -65,5 +65,5 @@ After configuration, click **Done** in the left-upper corner to switch back to Click **Finish**. The configuration of openEuler is complete. -![](figures/结束配置-new-en.png) +![](figures/completing-the-configuration.png) diff --git a/content/en/docs/Installation/failed-to-install-openeuler-on-an-x86-pm-in-uefi-mode-due-to-secure-boot-option-setting.md b/content/en/docs/Installation/failed-to-install-openeuler-on-an-x86-pm-in-uefi-mode-due-to-secure-boot-option-setting.md index 18cb5a862..387bc660e 100644 --- a/content/en/docs/Installation/failed-to-install-openeuler-on-an-x86-pm-in-uefi-mode-due-to-secure-boot-option-setting.md +++ b/content/en/docs/Installation/failed-to-install-openeuler-on-an-x86-pm-in-uefi-mode-due-to-secure-boot-option-setting.md @@ -25,7 +25,7 @@ Access the BIOS, set **secure boot** to **disabled**, and reinstall the openE 3. Set **Enforce Secure Boot** to **Disabled**. - ![](figures/选择.png) + ![](figures/enforce-secure-boot.png) >![](public_sys-resources/icon-note.gif) **NOTE:** >After **Enforce Secure Boot** is set to **Disabled**, save the settings, and exit. Then, reinstall the system. diff --git "a/content/en/docs/Installation/figures/\345\256\211\350\243\205\345\256\214\346\210\2201-0.png" b/content/en/docs/Installation/figures/completing-the-automatic-installation.png similarity index 100% rename from "content/en/docs/Installation/figures/\345\256\211\350\243\205\345\256\214\346\210\2201-0.png" rename to content/en/docs/Installation/figures/completing-the-automatic-installation.png diff --git "a/content/en/docs/Installation/figures/\347\273\223\346\235\237\351\205\215\347\275\256-new-en.png" b/content/en/docs/Installation/figures/completing-the-configuration.png similarity index 100% rename from "content/en/docs/Installation/figures/\347\273\223\346\235\237\351\205\215\347\275\256-new-en.png" rename to content/en/docs/Installation/figures/completing-the-configuration.png diff --git "a/content/en/docs/Installation/figures/\351\200\211\346\213\251.png" b/content/en/docs/Installation/figures/enforce-secure-boot.png similarity index 100% rename from "content/en/docs/Installation/figures/\351\200\211\346\213\251.png" rename to content/en/docs/Installation/figures/enforce-secure-boot.png diff --git "a/content/en/docs/Installation/figures/\345\215\212\350\207\252\345\212\250-new.png" b/content/en/docs/Installation/figures/semi-automatic-installation.png similarity index 100% rename from "content/en/docs/Installation/figures/\345\215\212\350\207\252\345\212\250-new.png" rename to content/en/docs/Installation/figures/semi-automatic-installation.png diff --git a/content/en/docs/Installation/full-automatic-installation-guide.md b/content/en/docs/Installation/full-automatic-installation-guide.md index fe4c8f4d3..35b133041 100644 --- a/content/en/docs/Installation/full-automatic-installation-guide.md +++ b/content/en/docs/Installation/full-automatic-installation-guide.md @@ -169,6 +169,6 @@ To use kickstart to perform full-automatic installation of openEuler, perform th 2. The automatic installation window is displayed. 3. Verify that the installation is complete. - ![](figures/安装完成1-0.png) + ![](figures/completing-the-automatic-installation.png) diff --git a/content/en/docs/Installation/installation-mode.md b/content/en/docs/Installation/installation-mode.md index f5645eac1..c86b2e852 100644 --- a/content/en/docs/Installation/installation-mode.md +++ b/content/en/docs/Installation/installation-mode.md @@ -16,7 +16,7 @@ If you have obtained a CD/DVD-ROM, install the OS using the CD/DVD-ROM. If you h Perform the following operations to start the installation: ->![](C:/Users/Administrator/Downloads/Hugo/openeuler-website-master/website/content/en/docs/20.03_LTS/docs/Installation/public_sys-resources/icon-note.gif) **NOTE:** +>![](C:/Users/Administrator/Downloads/openDocs/docs/content/en/docs/Installation/public_sys-resources/icon-note.gif) **NOTE:** >Set the system to preferentially boot from the CD/DVD-ROM drive. Take the BIOS as an example. You need to move the **CD/DVD-ROM Drive** option under **Boot Type Order** to the top. 1. Disconnect all drives that are not required, such as USB drives. @@ -34,67 +34,67 @@ This section describes how to create or use a USB flash drive to install the ope Pay attention to the capacity of the USB flash drive. The USB flash drive must have sufficient space to store the entire image. It is recommended that the USB flash drive has more than 16 GB space. -1. Connect the USB flash drive to the system and run the **dmesg** command to view related log. At the end of the log, you can view the information generated by the USB flash drive that is just connected. The information is similar to the following: +1. Connect the USB flash drive to the system and run the **dmesg** command to view related log. At the end of the log, you can view the information generated by the USB flash drive that is just connected. The information is similar to the following: - ``` - [ 170.171135] sd 5:0:0:0: [sdb] Attached SCSI removable disk - ``` + ``` + [ 170.171135] sd 5:0:0:0: [sdb] Attached SCSI removable disk + ``` - >![](C:/Users/Administrator/Downloads/Hugo/openeuler-website-master/website/content/en/docs/20.03_LTS/docs/Installation/public_sys-resources/icon-note.gif) **NOTE:** - >Take the **sdb** USB flash drive as an example. + >![](C:/Users/Administrator/Downloads/openDocs/docs/content/en/docs/Installation/public_sys-resources/icon-note.gif) **NOTE:** + >Take the **sdb** USB flash drive as an example. -2. Switch to user **root**. When running the **su** command, you need to enter the password. +2. Switch to user **root**. When running the **su** command, you need to enter the password. - ``` - $ su - root - ``` + ``` + $ su - root + ``` -3. Ensure that the USB flash drive is not mounted. Run the following command: +3. Ensure that the USB flash drive is not mounted. Run the following command: - ``` - # findmnt /dev/sdb - ``` + ``` + # findmnt /dev/sdb + ``` - - If no command output is displayed, the file system is not mounted. Go to the next step. + - If no command output is displayed, the file system is not mounted. Go to the next step. - - If the following information is displayed, the USB flash drive is automatically mounted. + - If the following information is displayed, the USB flash drive is automatically mounted. - ``` - # findmnt /dev/sdb - TARGET SOURCE FSTYPE OPTIONS - /mnt/iso /dev/sdb iso9660 ro,relatime - ``` + ``` + # findmnt /dev/sdb + TARGET SOURCE FSTYPE OPTIONS + /mnt/iso /dev/sdb iso9660 ro,relatime + ``` - In this case, you need to run the **umount** command to uninstall the device. + In this case, you need to run the **umount** command to uninstall the device. - ``` - # umount /mnt/iso - ``` + ``` + # umount /mnt/iso + ``` -4. Run the **dd** command to write the ISO image to the USB flash drive. +4. Run the **dd** command to write the ISO image to the USB flash drive. - ``` - # dd if=/path/to/image.iso of=/dev/device bs=blocksize - ``` + ``` + # dd if=/path/to/image.iso of=/dev/device bs=blocksize + ``` - Replace **/path/to/image.iso** with the complete path of the downloaded ISO image file, replace **device** with the device name provided by the **dmesg** command, and set a proper block size \(for example, 512 KB\) to replace **blocksize** to accelerate the write progress. + Replace **/path/to/image.iso** with the complete path of the downloaded ISO image file, replace **device** with the device name provided by the **dmesg** command, and set a proper block size \(for example, 512 KB\) to replace **blocksize** to accelerate the write progress. - For example, if the ISO image file name is **/home/testuser/Downloads/openEuler-20.03-LTS-aarch64-dvd.iso** and the detected device name is **sdb**, run the following command: + For example, if the ISO image file name is **/home/testuser/Downloads/openEuler-20.03-LTS-aarch64-dvd.iso** and the detected device name is **sdb**, run the following command: - ``` - # dd if=/home/testuser/Downloads/openEuler-20.03-LTS-aarch64-dvd.iso of=/dev/sdb bs=512k - ``` + ``` + # dd if=/home/testuser/Downloads/openEuler-20.03-LTS-aarch64-dvd.iso of=/dev/sdb bs=512k + ``` -5. After the image is written, remove the USB flash drive. +5. After the image is written, remove the USB flash drive. - No progress is displayed during the image write process. When the number sign \(\#\) appears again, the write is complete. Exit the **root** account and remove the USB flash drive. In this case, you can use the USB flash drive as the installation source of the system. + No progress is displayed during the image write process. When the number sign \(\#\) appears again, the write is complete. Exit the **root** account and remove the USB flash drive. In this case, you can use the USB flash drive as the installation source of the system. ### Starting the Installation Perform the following operations to start the installation: ->![](C:/Users/Administrator/Downloads/Hugo/openeuler-website-master/website/content/en/docs/20.03_LTS/docs/Installation/public_sys-resources/icon-note.gif) **NOTE:** +>![](C:/Users/Administrator/Downloads/openDocs/docs/content/en/docs/Installation/public_sys-resources/icon-note.gif) **NOTE:** >Set the system to preferentially boot from the USB flash drive. Take the BIOS as an example. You need to move the **USB** option under **Boot Type Order** to the top. 1. Disconnect all drives that are not required. @@ -112,7 +112,7 @@ If the target hardware is installed with a PXE-enabled NIC, we can configure it For installation through the network using PXE, the client uses a PXE-enabled NIC to send a broadcast request for DHCP information and IP address to the network. The DHCP server provides the client with an IP address and other network information, such as the IP address or host name of the DNS and FTP server \(which provides the files required for starting the installation program\), and the location of the files on the server. ->![](C:/Users/Administrator/Downloads/Hugo/openeuler-website-master/website/content/en/docs/20.03_LTS/docs/Installation/public_sys-resources/icon-note.gif) **NOTE:** +>![](C:/Users/Administrator/Downloads/openDocs/docs/content/en/docs/Installation/public_sys-resources/icon-note.gif) **NOTE:** >The TFTP, DHCP, and HTTP server configurations are not described here. For details, see [Full-automatic Installation Guide](full-automatic-installation-guide.html). ## Installation Through a QCOW2 Image @@ -121,31 +121,31 @@ This section describes how to create or use a QCOW2 image to install the openEul ### Creating a QCOW2 Image -1. Install the **qemu-img** software package. +1. Install the **qemu-img** software package. - ``` - # dnf install -y qemu-img - ``` + ``` + # dnf install -y qemu-img + ``` -2. Run the **create** command of the qemu-img tool to create an image file. The command format is as follows: +2. Run the **create** command of the qemu-img tool to create an image file. The command format is as follows: - ``` - $ qemu-img create -f -o - ``` + ``` + $ qemu-img create -f -o + ``` - The parameters are described as follows: + The parameters are described as follows: - - _imgFormat_: Image format. The value can be **raw** or **qcow2**. - - _fileOption_: File option, which is used to set features of an image file, such as specifying a backend image file, compression, and encryption. - - _fileName_: File name. - - _diskSize_: Disk size, which specifies the size of a block disk. The unit can be K, M, G, or T, indicating KiB, MiB, GiB, or TiB. + - _imgFormat_: Image format. The value can be **raw** or **qcow2**. + - _fileOption_: File option, which is used to set features of an image file, such as specifying a backend image file, compression, and encryption. + - _fileName_: File name. + - _diskSize_: Disk size, which specifies the size of a block disk. The unit can be K, M, G, or T, indicating KiB, MiB, GiB, or TiB. - For example, to create an image file **openEuler-imge.qcow2** whose disk size is 32 GB and format is qcow2, the command and output are as follows: + For example, to create an image file **openEuler-imge.qcow2** whose disk size is 32 GB and format is qcow2, the command and output are as follows: - ``` - $ qemu-img create -f qcow2 openEuler-image.qcow2 32G - Formatting 'openEuler-image.qcow2', fmt=qcow2 size=34359738368 cluster_size=65536 lazy_refcounts=off refcount_bits=16 - ``` + ``` + $ qemu-img create -f qcow2 openEuler-image.qcow2 32G + Formatting 'openEuler-image.qcow2', fmt=qcow2 size=34359738368 cluster_size=65536 lazy_refcounts=off refcount_bits=16 + ``` ### Starting the Installation @@ -159,7 +159,7 @@ Perform the following operations to start the installation: 5. Create a VM. 6. Start the VM. -For details, see the _openEuler 20.03 LTS Virtualization User Guide_. +For details, see the [*openEuler 20.03 LTS Virtualization User Guide*](../Virtualization/virtualization.html). ## Installation Through a Private Image diff --git a/content/en/docs/Installation/installation-preparations.md b/content/en/docs/Installation/installation-preparations.md index 7e56f3712..60cf2b33c 100644 --- a/content/en/docs/Installation/installation-preparations.md +++ b/content/en/docs/Installation/installation-preparations.md @@ -30,7 +30,7 @@ Perform the following operations to obtain the openEuler release package: ## Release Package Integrity Check ->![](C:/Users/Administrator/Downloads/20200413/content/en/docs/Installation/public_sys-resources/icon-note.gif) **NOTE:** +>![](C:/Users/Administrator/Downloads/openDocs/docs/content/en/docs/Installation/public_sys-resources/icon-note.gif) **NOTE:** >This section describes how to verify the integrity of the release package in the AArch64 architecture. The procedure for verifying the integrity of the release package in the x86\_64 architecture is the same. ### Introduction @@ -51,23 +51,23 @@ Verification file: **openEuler-20.03-LTS-aarch64-dvd.iso.sha256sum** To verify the file integrity, perform the following operations: -1. Obtain the verification value in the verification file. Run the following command: +1. Obtain the verification value in the verification file. Run the following command: - ``` - #cat openEuler-20.03-LTS-aarch64-dvd.iso.sha256sum - ``` + ``` + #cat openEuler-20.03-LTS-aarch64-dvd.iso.sha256sum + ``` -2. Calculate the SHA256 verification value of the file. Run the following command: +2. Calculate the SHA256 verification value of the file. Run the following command: - ``` - #sha256sum openEuler-20.03-LTS-aarch64-dvd.iso - ``` + ``` + #sha256sum openEuler-20.03-LTS-aarch64-dvd.iso + ``` - After the command is run, the verification value is displayed. + After the command is run, the verification value is displayed. -3. Check whether the values calculated in step 1 and step 2 are consistent. +3. Check whether the values calculated in step 1 and step 2 are consistent. - If the verification values are consistent, the .iso file is not damaged. If they are inconsistent, you can confirm that the file is damaged and you need to obtain the file again. + If the verification values are consistent, the .iso file is not damaged. If they are inconsistent, you can confirm that the file is damaged and you need to obtain the file again. ## Installation Requirements for PMs @@ -77,7 +77,7 @@ To install the openEuler OS on a PM, the PM must meet the following hardware com You need to take hardware compatibility into account during openEuler installation. [Table 1](#table14948632047) describes the types of supported servers. ->![](C:/Users/Administrator/Downloads/20200413/content/en/docs/Installation/public_sys-resources/icon-note.gif) **NOTE:** +>![](C:/Users/Administrator/Downloads/openDocs/docs/content/en/docs/Installation/public_sys-resources/icon-note.gif) **NOTE:** > >- TaiShan 200 servers are backed by Huawei Kunpeng 920 processors. >- Currently, only Huawei TaiShan and FusionServer Pro servers are supported. More servers from other vendors will be supported in the future. @@ -113,7 +113,6 @@ You need to take hardware compatibility into account during openEuler installati - ### Minimum Hardware Specifications [Table 2](#tff48b99c9bf24b84bb602c53229e2541) lists the minimum hardware specifications supported by openEuler. @@ -122,7 +121,7 @@ You need to take hardware compatibility into account during openEuler installati -

Component

+ @@ -130,28 +129,28 @@ You need to take hardware compatibility into account during openEuler installati - - - - @@ -180,7 +179,7 @@ When installing openEuler, pay attention to the compatibility of the virtualizat -

Component

Minimum Hardware Specifications

Architecture

+

Architecture
  • AArch64
  • x86_64
  • 64-bit Arm architecture
  • 64-bit Intel x86 architecture

CPU

+

CPU
  • Huawei Kunpeng 920 series
  • Intel ® Xeon® processor

-

Memory

+

Memory

≥ 4 GB (8 GB or higher recommended for better user experience)

-

Hard disk

+

Hard disk

≥ 120 GB (for better user experience)

Component

+ @@ -188,28 +187,28 @@ When installing openEuler, pay attention to the compatibility of the virtualizat - - - - @@ -234,3 +233,6 @@ When installing openEuler, pay attention to the compatibility of the virtualizat + + + diff --git a/content/en/docs/Installation/semi-automatic-installation-guide.md b/content/en/docs/Installation/semi-automatic-installation-guide.md index 8539108c4..25d61eda7 100644 --- a/content/en/docs/Installation/semi-automatic-installation-guide.md +++ b/content/en/docs/Installation/semi-automatic-installation-guide.md @@ -104,7 +104,7 @@ To use kickstart to perform semi-automatic installation of openEuler, perform th 1. On the installation wizard page in [Starting the Installation](starting-the-installation.md), select **Install openEuler 20.03 LTS** and press **e**. 2. Add **inst.ks=http://server ip/ks/openEuler-ks.cfg** to the startup parameters. - ![](figures/半自动-new.png) + ![](figures/semi-automatic-installation.png) 3. Press **Ctrl**+**x** to start the automatic installation. @@ -112,6 +112,6 @@ To use kickstart to perform semi-automatic installation of openEuler, perform th After the installation is complete, the system automatically restarts. Then, the installation page is displayed again. Shut down the computer and change startup option to start from the hard disk preferentially. - ![](figures/安装完成1.png) + ![](figures/completing-the-automatic-installation.png) diff --git a/content/en/docs/Quickstart/quick-start.md b/content/en/docs/Quickstart/quick-start.md index b82a9ebbf..08fa9edf7 100644 --- a/content/en/docs/Quickstart/quick-start.md +++ b/content/en/docs/Quickstart/quick-start.md @@ -4,40 +4,39 @@ This document uses openEuler 20.03 LTS installed on the TaiShan 200 server as an ## Installation Preparations -- Hardware Compatibility - - [Table 1](#table14948632047) describes the types of supported servers. - - **Table 1** Supported servers - - - -

Component

Minimum Virtualization Space

Architecture

+

Architecture
  • AArch64
  • x86_64

-

CPU

+

CPU

Two CPUs

-

Memory

+

Memory

≥ 4 GB (8 GB or higher recommended for better user experience)

-

Hard disk

+

Hard disk

≥ 32 GB (120 GB or higher recommended for better user experience)

- - - - - - - - - - - - - -

Server Type

-

Server Name

-

Server Model

-

Rack server

-

TaiShan 200

-

2280 balanced model

-

Rack server

-

FusionServer Pro

-

FusionServer Pro 2288H V5

-
NOTE:

The server must be configured with the Avago SAS3508 RAID controller card and the LOM-X722 NIC.

-
-
+- Hardware Compatibility + + [Table 1](#table14948632047) describes the types of supported servers. + + **Table 1** Supported servers + + + + + + + + + + + + + + + + +

Server Type

+

Server Name

+

Server Model

+

Rack server

+

TaiShan 200

+

2280 balanced model

+

Rack server

+

FusionServer Pro

+

FusionServer Pro 2288H V5

+
NOTE:

The server must be configured with the Avago SAS3508 RAID controller card and the LOM-X722 NIC.

+
+
- Minimum Hardware Specifications @@ -46,8 +45,7 @@ This document uses openEuler 20.03 LTS installed on the TaiShan 200 server as an **Table 2** Minimum hardware specifications - -

Component

+ @@ -55,28 +53,28 @@ This document uses openEuler 20.03 LTS installed on the TaiShan 200 server as an - - - - @@ -273,24 +271,24 @@ After entering the GUI installation page, perform the following operations to in **Figure 11** Password of the **root** account -5. Create a user. +5. Create a user. - Click **User Creation**. [Figure 12](#en-us_topic_0186390266_en-us_topic_0122145909_fig1237715313319) shows the page for creating a user. Enter a username and set a password. The password complexity requirements are the same as those of the user **root**. By clicking **Advanced**, you can also configure a home directory and a user group, as shown in [Figure 13](#en-us_topic_0186390266_en-us_topic_0122145909_fig128716531312). + Click **User Creation**. [Figure 12](#en-us_topic_0186390266_en-us_topic_0122145909_fig1237715313319) shows the page for creating a user. Enter a username and set a password. The password complexity requirements are the same as those of the user **root**. By clicking **Advanced**, you can also configure a home directory and a user group, as shown in [Figure 13](#en-us_topic_0186390266_en-us_topic_0122145909_fig128716531312). - **Figure 12** Creating a user - + **Figure 12** Creating a user + - **Figure 13** Advanced user configuration - + **Figure 13** Advanced user configuration + - After configuration, click **Done** in the left-upper corner to switch back to the installation process page. + After configuration, click **Done** in the left-upper corner to switch back to the installation process page. -6. After the installation is complete, restart the system. +6. After the installation is complete, restart the system. - openEuler has been installed, as shown in [Figure 14](#en-us_topic_0186390267_en-us_topic_0122145917_fig1429512116338). Click **Reboot** to restart the system. + openEuler has been installed, as shown in [Figure 14](#en-us_topic_0186390267_en-us_topic_0122145917_fig1429512116338). Click **Reboot** to restart the system. - **Figure 14** Completing the installation - + **Figure 14** Completing the installation + ## Viewing System Information diff --git "a/content/zh/docs/Installation/figures/\345\256\211\350\243\205\345\256\214\346\210\2201-0.png" "b/content/zh/docs/Installation/figures/\345\256\211\350\243\205\345\256\214\346\210\2201-0.png" deleted file mode 100644 index f2169685ef202bae133ae74fec620ec64aea46df..0000000000000000000000000000000000000000 GIT binary patch literal 0 HcmV?d00001 literal 374 zcmeAS@N?(olHy`uVBq!ia0y~yVEh4O%W^OQ$&*`Nt_4z@1s;*b3=DinK$vl=HlH+5 zm4>H_V@SoEw|AoRnhgY41AFCn_WI=O_r3P6^l!Lcdp1wu?cJT4(;I(RoXLCeDeAoBJBEh(Zyfg549%k1 zY(KwvuXX&!$AwnEqn_tZT_az&{_~qC+gmpk|1$7wRGF+j`RL+f;>~u(fko?{lt@nf z8vXl>jBtad)%3hF@%@L7mtPTF#^5>E@&2q;i-UGVxZh!ZGv~|N+5BS3GNtv*0gtaP z$nRYnXsE8osHMB`QSRhrZ{7LRj7yF3H;X*??bBJce*VpQ>mMiT6fmxvRW2j&pli)V zagOo_ulV+tUf!ApZ(9h;IOBCR@(x0h*x3cgSdT+88g4}H_V@SoEw|AoRnhgY41AFCn_WI=O_r3P6^l!Lcdp1wu?cJT4(;I(RoXLCeDeAoBJBEh(Zyfg549%k1 zY(KwvuXX&!$AwnEqn_tZT_az&{_~qC+gmpk|1$7wRGF+j`RL+f;>~u(fko?{lt@nf z8vXl>jBtad)%3hF@%@L7mtPTF#^5>E@&2q;i-UGVxZh!ZGv~|N+5BS3GNtv*0gtaP z$nRYnXsE8osHMB`QSRhrZ{7LRj7yF3H;X*??bBJce*VpQ>mMiT6fmxvRW2j&pli)V zagOo_ulV+tUf!ApZ(9h;IOBCR@(x0h*x3cgSdT+88g4} 在安装开始前，您需要获取openEuler的发布包和校验文件。 @@ -28,9 +28,9 @@ 2. 单击“openEuler-20.03-LTS-x86\_64-dvd.iso”，将openEuler发布包下载到本地。 3. 单击“openEuler-20.03-LTS-x86\_64-dvd.iso.sha256sum”，将openEuler校验文件下载到本地。 -## 发布包完整性校验 +## 发布包完整性校验 ->![](C:/Users/Administrator/Downloads/20200413/content/zh/docs/Installation/public_sys-resources/icon-note.gif) **说明：** +>![](C:/Users/Administrator/Downloads/openDocs/docs/content/zh/docs/Installation/public_sys-resources/icon-note.gif) **说明：** >本章节以AArch64架构的发布包完整性校验为例，x86\_64架构的发布包完整性校验的操作方法相同。 ### 简介 @@ -51,33 +51,33 @@ iso文件：openEuler-20.03-LTS-aarch64-dvd.iso 文件完整性校验操作步骤如下： -1. 获取校验文件中的校验值。执行命令如下： +1. 获取校验文件中的校验值。执行命令如下： - ``` - #cat openEuler-20.03-LTS-aarch64-dvd.iso.sha256sum - ``` + ``` + #cat openEuler-20.03-LTS-aarch64-dvd.iso.sha256sum + ``` -2. 计算文件的sha256校验值。执行命令如下： +2. 计算文件的sha256校验值。执行命令如下： - ``` - #sha256sum openEuler-20.03-LTS-aarch64-dvd.iso - ``` + ``` + #sha256sum openEuler-20.03-LTS-aarch64-dvd.iso + ``` - 命令执行完成后，输出校验值。 + 命令执行完成后，输出校验值。 -3. 对比步骤1和步骤2计算的校验值是否一致。 +3. 对比步骤1和步骤2计算的校验值是否一致。 - 如果校验值一致说明iso文件完整性没有破坏，如果校验值不一致则可以确认文件完整性已被破坏，需要重新获取。 + 如果校验值一致说明iso文件完整性没有破坏，如果校验值不一致则可以确认文件完整性已被破坏，需要重新获取。 -## 物理机的安装要求 +## 物理机的安装要求 若需要在物理机环境上安装openEuler操作系统，则物理机需要满足如下的硬件兼容性和最小硬件要求。 -### 硬件兼容支持 +### 硬件兼容支持 openEuler安装时，应注意硬件兼容性方面的问题，当前已支持的服务器类型如[表1](#table14948632047)所示。 ->![](C:/Users/Administrator/Downloads/20200413/content/zh/docs/Installation/public_sys-resources/icon-note.gif) **说明：** +>![](C:/Users/Administrator/Downloads/openDocs/docs/content/zh/docs/Installation/public_sys-resources/icon-note.gif) **说明：** > >- TaiShan 200服务器基于华为鲲鹏920处理器。 >- 当前仅支持华为TaiShan服务器和FusionServer Pro 机架服务器，后续将逐步增加对其他厂商服务器的支持。 @@ -113,9 +113,7 @@ openEuler安装时，应注意硬件兼容性方面的问题，当前已支持

Component

Minimum Hardware Specifications

Architecture

+

Architecture
  • AArch64
  • x86_64
  • 64-bit Arm architecture
  • 64-bit Intel x86 architecture

CPU

+

CPU
  • Huawei Kunpeng 920 series
  • Intel ® Xeon® processor

-

Memory

+

Memory

≥ 4 GB (8 GB or higher recommended for better user experience)

-

Hard disk

+

Hard disk

≥ 120 GB (for better user experience)
- - -### 最小硬件要求 +### 最小硬件要求 openEuler所需的最小硬件要求如[表2](#tff48b99c9bf24b84bb602c53229e2541)所示。 @@ -162,18 +160,18 @@ openEuler所需的最小硬件要求如[表2](#tff48b99c9bf24b84bb602c53229e2541
-## 虚拟机的安装要求 +## 虚拟机的安装要求 若需要在虚拟机环境上安装openEuler操作系统，则虚拟机需要满足如下的虚拟化平台兼容性和最小虚拟化要求。 -### 虚拟化平台兼容性 +### 虚拟化平台兼容性 openEuler安装时，应注意虚拟化平台兼容性的问题，当前已支持的虚拟化平台为： - openEuler自有的虚拟化组件（HostOS为openEuler，虚拟化组件为发布包中的qemu、KVM）创建的虚拟化平台。 - 华为公有云的x86虚拟化平台。 -### 最小虚拟化空间要求 +### 最小虚拟化空间要求 openEuler所需的最小虚拟化空间要求如[表3](#tff48b99c9bf24b84bb602c53229e2541)所示。 @@ -222,10 +220,3 @@ openEuler所需的最小虚拟化空间要求如[表3](#tff48b99c9bf24b84bb602c5 - - - - - - - diff --git "a/content/zh/docs/Installation/\345\256\211\350\243\205\346\226\271\345\274\217\344\273\213\347\273\215.md" "b/content/zh/docs/Installation/\345\256\211\350\243\205\346\226\271\345\274\217\344\273\213\347\273\215.md" index 795c81642..e065c7c5f 100644 --- "a/content/zh/docs/Installation/\345\256\211\350\243\205\346\226\271\345\274\217\344\273\213\347\273\215.md" +++ "b/content/zh/docs/Installation/\345\256\211\350\243\205\346\226\271\345\274\217\344\273\213\347\273\215.md" @@ -16,7 +16,7 @@ 根据以下步骤启动安装程序： ->![](C:/Users/Administrator/Downloads/Hugo/openeuler-website-master/website/content/zh/docs/20.03_LTS/docs/Installation/public_sys-resources/icon-note.gif) **说明：** +>![](C:/Users/Administrator/Downloads/openDocs/docs/content/zh/docs/Installation/public_sys-resources/icon-note.gif) **说明：** >您需要先设置您的系统优先从光盘进行启动引导。以BIOS为例，您需要将“Boot Type Order”中的“CD/DVD-ROM Drive”选项调整到首位。 1. 断开所有安装不需要的驱动器，比如USB。 @@ -34,67 +34,67 @@ 您需要注意USB盘容量的大小，它必须有足够的的空间放下整个镜像，建议USB盘空间大于16G。 -1. 将USB盘连接到该系统中，并执行 dmesg 命令查看相关的日志信息。在该日志的最后可以看到刚刚连接的USB盘所生成的一组信息，应类似如下： +1. 将USB盘连接到该系统中，并执行 dmesg 命令查看相关的日志信息。在该日志的最后可以看到刚刚连接的USB盘所生成的一组信息，应类似如下： - ``` - [ 170.171135] sd 5:0:0:0: [sdb] Attached SCSI removable disk - ``` + ``` + [ 170.171135] sd 5:0:0:0: [sdb] Attached SCSI removable disk + ``` - >![](C:/Users/Administrator/Downloads/Hugo/openeuler-website-master/website/content/zh/docs/20.03_LTS/docs/Installation/public_sys-resources/icon-note.gif) **说明：** - >连接的USB盘名称以sdb进行举例。 + >![](C:/Users/Administrator/Downloads/openDocs/docs/content/zh/docs/Installation/public_sys-resources/icon-note.gif) **说明：** + >连接的USB盘名称以sdb进行举例。 -2. 切换为root用户。使用su命令，需要输入相应的密码。 +2. 切换为root用户。使用su命令，需要输入相应的密码。 - ``` - $ su - root - ``` + ``` + $ su - root + ``` -3. 确保USB盘没有被挂载。使用如下命令进行查询： +3. 确保USB盘没有被挂载。使用如下命令进行查询： - ``` - # findmnt /dev/sdb - ``` + ``` + # findmnt /dev/sdb + ``` - - 如果执行此命令后无输出，表明未挂载，可以继续执行下一步。 + - 如果执行此命令后无输出，表明未挂载，可以继续执行下一步。 - - 如果输出以下信息，表明USB盘已经自动挂载。 + - 如果输出以下信息，表明USB盘已经自动挂载。 - ``` - # findmnt /dev/sdb - TARGET SOURCE FSTYPE OPTIONS - /mnt/iso /dev/sdb iso9660 ro,relatime - ``` + ``` + # findmnt /dev/sdb + TARGET SOURCE FSTYPE OPTIONS + /mnt/iso /dev/sdb iso9660 ro,relatime + ``` - 此时，您需要使用umount命令卸载该设备。 + 此时，您需要使用umount命令卸载该设备。 - ``` - # umount /mnt/iso - ``` + ``` + # umount /mnt/iso + ``` -4. 使用dd命令将ISO安装镜像直接写入USB盘： +4. 使用dd命令将ISO安装镜像直接写入USB盘： - ``` - # dd if=/path/to/image.iso of=/dev/device bs=blocksize - ``` + ``` + # dd if=/path/to/image.iso of=/dev/device bs=blocksize + ``` - 使用您下载的ISO镜像文件的完整路径替换 /path/to/image.iso，使用之前由 dmesg 命令给出的设备名称替换device，同时设置合理的块大小（例如：512k）替换 blocksize，这样可以加快写入进度。 + 使用您下载的ISO镜像文件的完整路径替换 /path/to/image.iso，使用之前由 dmesg 命令给出的设备名称替换device，同时设置合理的块大小（例如：512k）替换 blocksize，这样可以加快写入进度。 - 例如：如果该ISO镜像文件位于 /home/testuser/Downloads/openEuler-20.03-LTS-aarch64-dvd.iso，同时探测到的设备名称为sdb，则该命令如下： + 例如：如果该ISO镜像文件位于 /home/testuser/Downloads/openEuler-20.03-LTS-aarch64-dvd.iso，同时探测到的设备名称为sdb，则该命令如下： - ``` - # dd if=/home/testuser/Downloads/openEuler-20.03-LTS-aarch64-dvd.iso of=/dev/sdb bs=512k - ``` + ``` + # dd if=/home/testuser/Downloads/openEuler-20.03-LTS-aarch64-dvd.iso of=/dev/sdb bs=512k + ``` -5. 等待镜像写入完成，拔掉USB盘。 +5. 等待镜像写入完成，拔掉USB盘。 - 镜像写入过程中不会有进度显示，当\#号再次出现时，表明写入完成。退出root账户，拔掉USB盘。此时，您可以使用该USB盘作为系统的安装源。 + 镜像写入过程中不会有进度显示，当\#号再次出现时，表明写入完成。退出root账户，拔掉USB盘。此时，您可以使用该USB盘作为系统的安装源。 ### 启动安装 请根据以下步骤启动安装程序： ->![](C:/Users/Administrator/Downloads/Hugo/openeuler-website-master/website/content/zh/docs/20.03_LTS/docs/Installation/public_sys-resources/icon-note.gif) **说明：** +>![](C:/Users/Administrator/Downloads/openDocs/docs/content/zh/docs/Installation/public_sys-resources/icon-note.gif) **说明：** >您需要先设置您的系统优先从USB进行启动引导。以BIOS为例，您需要将“Boot Type Order”中的USB选项调整到首位。 1. 断开所有安装不需要的驱动器。 @@ -112,7 +112,7 @@ 对于PXE网络安装，客户机通过支持PXE的网卡，向网络发送请求DHCP信息的广播，请求IP地址等信息。DHCP服务器给客户机提供一个IP地址和其他网络信息如域名服务器、ftp服务器（它提供启动安装程序所必须的文件）的IP地址或主机名，以及服务器上文件的位置。 ->![](C:/Users/Administrator/Downloads/Hugo/openeuler-website-master/website/content/zh/docs/20.03_LTS/docs/Installation/public_sys-resources/icon-note.gif) **说明：** +>![](C:/Users/Administrator/Downloads/openDocs/docs/content/zh/docs/Installation/public_sys-resources/icon-note.gif) **说明：** >此处不详细讨论tftp、DHCP、http等服务器配置，相关详细配置请参考“[全自动化安装指导](全自动化安装指导.html)”章节。 ## 通过qcow2镜像安装 @@ -121,31 +121,31 @@ ### 制作qcow2镜像 -1. 安装qemu-img软件包。 +1. 安装qemu-img软件包。 - ``` - # dnf install -y qemu-img - ``` + ``` + # dnf install -y qemu-img + ``` -2. 使用qemu-img工具的create命令，创建镜像文件，命令格式为： +2. 使用qemu-img工具的create命令，创建镜像文件，命令格式为： - ``` - $ qemu-img create -f -o - ``` + ``` + $ qemu-img create -f -o + ``` - 其中，各参数含义如下： + 其中，各参数含义如下： - - _imgFormat_ ：镜像格式，取值为raw, qcow2等。 - - _fileOption_ ：文件选项，用于设置镜像文件的特性，如指定后端镜像文件，压缩，加密等特性。 - - _f__ileName_ ：文件名称。 - - _diskSize_ ：磁盘大小，用于指定块磁盘设备的大小，支持的单位有K、M、G、T，分别代表KiB、MiB、GiB、TiB。 + - _imgFormat_ ：镜像格式，取值为raw, qcow2等。 + - _fileOption_ ：文件选项，用于设置镜像文件的特性，如指定后端镜像文件，压缩，加密等特性。 + - _fileName_ ：文件名称。 + - _diskSize_ ：磁盘大小，用于指定块磁盘设备的大小，支持的单位有K、M、G、T，分别代表KiB、MiB、GiB、TiB。 - 例如，创建一个磁盘设备大小为32GB、格式为qcow2的镜像文件openEuler-imge.qcow2，命令和回显如下： + 例如，创建一个磁盘设备大小为32GB、格式为qcow2的镜像文件openEuler-imge.qcow2，命令和回显如下： - ``` - $ qemu-img create -f qcow2 openEuler-image.qcow2 32G - Formatting 'openEuler-image.qcow2', fmt=qcow2 size=34359738368 cluster_size=65536 lazy_refcounts=off refcount_bits=16 - ``` + ``` + $ qemu-img create -f qcow2 openEuler-image.qcow2 32G + Formatting 'openEuler-image.qcow2', fmt=qcow2 size=34359738368 cluster_size=65536 lazy_refcounts=off refcount_bits=16 + ``` ### 启动安装 @@ -159,7 +159,7 @@ 5. 创建虚拟机。 6. 启动虚拟机。 -各步骤详细的操作请参考《openEuler 20.03 LTS 虚拟化用户指南》。 +各步骤详细的操作请参考《[openEuler 20.03 LTS 虚拟化用户指南](../Virtualization/virtualization.html)》。 ## 通过私有镜像安装 @@ -185,3 +185,7 @@ + + + + diff --git "a/content/zh/docs/Quickstart/\345\277\253\351\200\237\345\205\245\351\227\250.md" "b/content/zh/docs/Quickstart/\345\277\253\351\200\237\345\205\245\351\227\250.md" index e326d6d0a..cbd744467 100644 --- "a/content/zh/docs/Quickstart/\345\277\253\351\200\237\345\205\245\351\227\250.md" +++ "b/content/zh/docs/Quickstart/\345\277\253\351\200\237\345\205\245\351\227\250.md" @@ -1,4 +1,4 @@ -# 快速入门 +# 快速入门 本文档以TaiShan 200服务器上安装openEuler 20.03 LTS为例，旨在指导用户快速地安装和使用openEuler操作系统，更详细的安装要求和安装方法请参考《[openEuler 20.03 LTS 安装指南](https://openeuler.org/zh/docs/20.03_LTS/docs/Installation/installation.html)》。 @@ -240,39 +240,34 @@ 用户设置的root密码需要满足如下密码复杂度要求，否则会导致密码设置或用户创建失败。 - - 口令长度至少8个字符。 - - - 口令至少包含大写字母、小写字母、数字和特殊字符中的任意3种。 - - - 口令不能和账号一样。 + - 口令长度至少8个字符。 + - 口令至少包含大写字母、小写字母、数字和特殊字符中的任意3种。 + - 口令不能和账号一样。 + - 口令不能使用字典词汇。 + - 查询字典 - - 口令不能使用字典词汇。 + 在已装好的openEuler环境中，可以通过如下命令导出字典库文件dictionary.txt，用户可以查询密码是否在该字典中。 - - 查询字典 - - 在已装好的openEuler环境中，可以通过如下命令导出字典库文件dictionary.txt，用户可以查询密码是否在该字典中。 - - ``` - cracklib-unpacker /usr/share/cracklib/pw_dict > dictionary.txt - ``` - - - 修改字典 - - - 修改上面导出的字典文件，执行如下命令更新系统字典库。 - - ``` - create-cracklib-dict dictionary.txt - ``` - - - 在原字典库基础上新增其他字典内容custom.txt。 - - ``` - create-cracklib-dict dictionary.txt custom.txt - ``` + ``` + cracklib-unpacker /usr/share/cracklib/pw_dict > dictionary.txt + ``` + + - 修改字典 + - 修改上面导出的字典文件，执行如下命令更新系统字典库。 + + ``` + create-cracklib-dict dictionary.txt + ``` + + - 在原字典库基础上新增其他字典内容custom.txt。 + + ``` + create-cracklib-dict dictionary.txt custom.txt + ``` **图 11** root密码 - + 5. 创建用户。 单击“创建用户”，弹出创建用户的界面如[图12](#zh-cn_topic_0186390266_zh-cn_topic_0122145909_fig1237715313319)所示。输入用户名，并设置密码，其中密码复杂度要求与root密码复杂度要求一致。另外您还可以通过“高级”选项设置用户主目录、用户组等，如[图13](#zh-cn_topic_0186390266_zh-cn_topic_0122145909_fig128716531312)所示。 -- Gitee