
In markdown documents, text for bash should be contained in block as below: ```bash content ``` If not, the display in gitee will be strange, for example, $text$ will show as a ltalics text, some lines with special character will erasure line breaks. Thus the old text will show as follows: ├── headers-4.19.90-2003.4.0.0036.oe1.aarch64.cgz├── modules-4.19.90-2003.4.0.0036.oe1.aarch64.cgz├── vmlinuz-4.19.90-2003.4.0.0036.oe1.aarch64└── vmlinuz -> vmlinuz-4.19.90-2003.4.0.0036.oe1.aarch64 Signed-off-by: Xu Xijian <hdxuxijian@163.com> --- doc/job/kernel_version.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/doc/job/kernel_version.md b/doc/job/kernel_version.md index 4a193fb..b73d42e 100644 --- a/doc/job/kernel_version.md +++ b/doc/job/kernel_version.md @@ -26,6 +26,7 @@ Meaning: centos/aarch64/8.1.1911 - 4.18.0-147.el8(default) +```bash Related files: - In initramfs boot process, every kernel version is related with a vmlinuz, module and headers. - Files like below under $boot_dir, an example $boot_dir can be "/srv/os/openeuler/aarch64/20.03/boot". @@ -33,6 +34,7 @@ Related files: ├── modules-4.19.90-2003.4.0.0036.oe1.aarch64.cgz ├── vmlinuz-4.19.90-2003.4.0.0036.oe1.aarch64 └── vmlinuz -> vmlinuz-4.19.90-2003.4.0.0036.oe1.aarch64 +``` Usage example: - submit iperf.yaml testbox=vm-2p8g queue=vm-2p8g~$USER os=openeuler os_arch=aarch64 os_version=20.03 runtime=20 kernel_version=4.19.90-2003.4.0.0036.oe1.aarch64 -- 2.23.0