dd 命令在没有任何选项的情况下运行时会做什么？
[hannah@lenovo ~]$ dd
^C0+0 records in
0+0 records out
0 bytes copied, 7.71982 s, 0.0 kB/s
它会删除任何文件还是不用担心？谷歌搜索没有帮助
提前致谢
如何在 Windows 终端中制作自己的配色方案？更具体地说：制作配色方案的正确格式是什么？
一点解释：
让我们以这个方案为例：
{ "name" : "Campbell", "cursorColor": "#FFFFFF", "selectionBackground": "#FFFFFF", "background" : "#0C0C0C", "foreground" : "#CCCCCC", "black" : "#0C0C0C", "blue" : "#0037DA", "cyan" : "#3A96DD", "green" : "#13A10E", "purple" : "#881798", "red" : "#C50F1F", "white" : "#CCCCCC", "yellow" : "#C19C00", "brightBlack" : "#767676", "brightBlue" : "#3B78FF", "brightCyan" : "#61D6D6", "brightGreen" : "#16C60C", "brightPurple" : "#B4009E", "brightRed" : "#E74856", "brightWhite" : "#F2F2F2", "brightYellow" : "#F9F1A5" },
name像, cursorColor, selectionBackground,background和这样的术语foreground是不言自明的，但是它之后的颜色顺序呢？！！它们是按任何顺序写的吗？如果我将brightRed{3rd line from bottom} 更改为其他颜色会发生什么变化？我找不到任何文章回答我的问题。提前致谢 ！！
我已经搜索了一些相关文章以获得一些帮助：
Sda 是这样分区的：
注意具体顺序：sda11 > sda6 > sda7 > sda9 > ...
想要以相同的顺序打印分区信息并将其存储在文本文件中。
我试过的 -
gdisk -l /dev/sda
[manjaro@manjaro-10ahs0wn00 ~]$ sudo gdisk -l /dev/sda
GPT fdisk (gdisk) version 1.0.5
Partition table scan:
MBR: protective
BSD: not present
APM: not present
GPT: present
Found valid GPT with protective MBR; using GPT.
Disk /dev/sda: 500118192 sectors, 238.5 GiB
Model: Lexar 256GB SSD
Sector size (logical/physical): 512/512 bytes
Disk identifier (GUID): F07CA5E4-85FA-F247-855D-4DB101931C1C
Partition table holds up to 128 entries
Main partition table begins at sector 2 and ends at sector 33
First usable sector is 34, last usable sector is 500118158
Partitions will be aligned on 1-sector boundaries
Total free space is 135154 sectors (66.0 MiB)
Number Start (sector) End (sector) Size Code Name
1 19255304 500118143 229.3 GiB 8300 STATE
2 2117638 2183173 32.0 MiB 7F00 KERN-A
3 10866696 19255303 4.0 GiB 7F01 ROOT-A
4 2183174 2248709 32.0 MiB 7F00 KERN-B
5 2478088 10866695 4.0 GiB 7F01 ROOT-B
6 16448 16448 512 bytes 7F00 KERN-C
7 16456 2113607 1024.0 MiB 7F01 ROOT-C
8 2248712 2281479 16.0 MiB 8300 OEM
9 2113608 2113608 512 bytes 7F02 reserved
10 2113609 2113609 512 bytes 7F02 reserved
11 64 16447 8.0 MiB FFFF RWFW
12 2412552 2478087 32.0 MiB EF00 EFI-SYSTEM
fdisk -l /dev/sda
[manjaro@manjaro-10ahs0wn00 ~]$ sudo fdisk -l /dev/sda
[sudo] password for manjaro:
Disk /dev/sda: 238.47 GiB, 256060514304 bytes, 500118192 sectors
Disk model: Lexar 256GB SSD
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: F07CA5E4-85FA-F247-855D-4DB101931C1C
Device Start End Sectors Size Type
/dev/sda1 19255304 500118143 480862840 229.3G Linux filesystem
/dev/sda2 2117638 2183173 65536 32M ChromeOS kernel
/dev/sda3 10866696 19255303 8388608 4G ChromeOS root fs
/dev/sda4 2183174 2248709 65536 32M ChromeOS kernel
/dev/sda5 2478088 10866695 8388608 4G ChromeOS root fs
/dev/sda6 16448 16448 1 512B ChromeOS kernel
/dev/sda7 16456 2113607 2097152 1G ChromeOS root fs
/dev/sda8 2248712 2281479 32768 16M Linux filesystem
/dev/sda9 2113608 2113608 1 512B ChromeOS reserved
/dev/sda10 2113609 2113609 1 512B ChromeOS reserved
/dev/sda11 64 16447 16384 8M unknown
/dev/sda12 2412552 2478087 65536 32M EFI System
Partition table entries are not in disk order.
sfdisk -d /dev/sda
[manjaro@manjaro-10ahs0wn00 ~]$ sudo sfdisk -d /dev/sda
[sudo] password for manjaro:
label: gpt
label-id: F07CA5E4-85FA-F247-855D-4DB101931C1C
device: /dev/sda
unit: sectors
first-lba: 34
last-lba: 500118158
sector-size: 512
/dev/sda1 : start= 19255304, size= 480862840, type=0FC63DAF-8483-4772-8E79-3D69D8477DE4, uuid=0D2E3A01-7890-074A-9801-9407ED8D90E3, name="STATE"
/dev/sda2 : start= 2117638, size= 65536, type=FE3A2A5D-4F32-41A7-B725-ACCC3285A309, uuid=417541BD-8D79-A34C-AE63-CB8B79BE3D03, name="KERN-A", attrs="GUID:48,49,50,51,52,53,54,55"
/dev/sda3 : start= 10866696, size= 8388608, type=3CB8E202-3B7E-47DD-8A3C-7FF2A13CFCEC, uuid=C9D9828E-5FC8-9A42-A6A0-6E64FF8F3383, name="ROOT-A"
/dev/sda4 : start= 2183174, size= 65536, type=FE3A2A5D-4F32-41A7-B725-ACCC3285A309, uuid=3E6C72E3-744D-1B40-825D-570F4D1CB0DF, name="KERN-B", attrs="GUID:52,53,54,55"
/dev/sda5 : start= 2478088, size= 8388608, type=3CB8E202-3B7E-47DD-8A3C-7FF2A13CFCEC, uuid=4393B767-9292-3E4F-BC6A-FFCB3BB76B4C, name="ROOT-B"
/dev/sda6 : start= 16448, size= 1, type=FE3A2A5D-4F32-41A7-B725-ACCC3285A309, uuid=A2E8DF92-A885-D64A-9DCE-109DFD3A912D, name="KERN-C", attrs="GUID:52,53,54,55"
/dev/sda7 : start= 16456, size= 2097152, type=3CB8E202-3B7E-47DD-8A3C-7FF2A13CFCEC, uuid=105C4E07-0CD3-9A4D-8C31-E3D75A0B80AF, name="ROOT-C"
/dev/sda8 : start= 2248712, size= 32768, type=0FC63DAF-8483-4772-8E79-3D69D8477DE4, uuid=D80BFCAD-4771-6C48-9DBB-0ADFBE10DBF1, name="OEM"
/dev/sda9 : start= 2113608, size= 1, type=2E0A753D-9E48-43B0-8337-B15192CB1B5E, uuid=6D272F77-489E-E94A-B903-59BFD612F648, name="reserved"
/dev/sda10 : start= 2113609, size= 1, type=2E0A753D-9E48-43B0-8337-B15192CB1B5E, uuid=E0C92DB9-1C4D-9B4C-92C6-D002B685E39C, name="reserved"
/dev/sda11 : start= 64, size= 16384, type=CAB6E88E-ABF3-4102-A07A-D4BB9BE3C1D3, uuid=E9016D9E-426D-434E-ABA0-614273D7BA5A, name="RWFW"
/dev/sda12 : start= 2412552, size= 65536, type=C12A7328-F81F-11D2-BA4B-00A0C93EC93B, uuid=EE625F5C-40D7-614D-80A3-0C4DA423711B, name="EFI-SYSTEM"
sfdisk /dev/sda
[manjaro@manjaro-10ahs0wn00 ~]$ sudo sfdisk /dev/sda
Welcome to sfdisk (util-linux 2.36).
Changes will remain in memory only, until you decide to write them.
Be careful before using the write command.
Checking that no-one is using this disk right now ... OK
Disk /dev/sda: 238.47 GiB, 256060514304 bytes, 500118192 sectors
Disk model: Lexar 256GB SSD
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: F07CA5E4-85FA-F247-855D-4DB101931C1C
Old situation:
Device Start End Sectors Size Type
/dev/sda1 19255304 500118143 480862840 229.3G Linux filesystem
/dev/sda2 2117638 2183173 65536 32M ChromeOS kernel
/dev/sda3 10866696 19255303 8388608 4G ChromeOS root fs
/dev/sda4 2183174 2248709 65536 32M ChromeOS kernel
/dev/sda5 2478088 10866695 8388608 4G ChromeOS root fs
/dev/sda6 16448 16448 1 512B ChromeOS kernel
/dev/sda7 16456 2113607 2097152 1G ChromeOS root fs
/dev/sda8 2248712 2281479 32768 16M Linux filesystem
/dev/sda9 2113608 2113608 1 512B ChromeOS reserved
/dev/sda10 2113609 2113609 1 512B ChromeOS reserved
/dev/sda11 64 16447 16384 8M unknown
/dev/sda12 2412552 2478087 65536 32M EFI System
Partition table entries are not in disk order.
Type 'help' to get more information.
>>> ^C
sfdisk -l /dev/sda
[manjaro@manjaro-10ahs0wn00 ~]$ sudo sfdisk -l /dev/sda
[sudo] password for manjaro:
Disk /dev/sda: 238.47 GiB, 256060514304 bytes, 500118192 sectors
Disk model: Lexar 256GB SSD
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: F07CA5E4-85FA-F247-855D-4DB101931C1C
Device Start End Sectors Size Type
/dev/sda1 19255304 500118143 480862840 229.3G Linux filesystem
/dev/sda2 2117638 2183173 65536 32M ChromeOS kernel
/dev/sda3 10866696 19255303 8388608 4G ChromeOS root fs
/dev/sda4 2183174 2248709 65536 32M ChromeOS kernel
/dev/sda5 2478088 10866695 8388608 4G ChromeOS root fs
/dev/sda6 16448 16448 1 512B ChromeOS kernel
/dev/sda7 16456 2113607 2097152 1G ChromeOS root fs
/dev/sda8 2248712 2281479 32768 16M Linux filesystem
/dev/sda9 2113608 2113608 1 512B ChromeOS reserved
/dev/sda10 2113609 2113609 1 512B ChromeOS reserved
/dev/sda11 64 16447 16384 8M unknown
/dev/sda12 2412552 2478087 65536 32M EFI System
Partition table entries are not in disk order.
从输出中可以清楚地看出，我尝试过的所有命令都按顺序排列分区编号，而不是显示分区的实际顺序，即 11>6>7>9>...
使用 Manjaro linux
我的问题是如何以相同的顺序打印分区？
尝试使用 wget 下载时出现 WSL 错误
wget -O quotefile.txt "https://www.google.com"
输出
Will not apply HSTS. The HSTS database must be a regular and non-world-writable file.
ERROR: could not open HSTS store at '/home/atul/.wget-hsts'. HSTS will be disabled.
--2020-04-08 12:47:43-- https://www.google.com/
Resolving www.google.com (www.google.com)... 2404:6800:4002:80f::2004, 172.217.166.196
Connecting to www.google.com (www.google.com)|2404:6800:4002:80f::2004|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [text/html]
Saving to: ‘quotefile.txt’
quotefile.txt [ <=> ] 14.68K --.-KB/s in 0.002s
2020-04-08 12:47:45 (6.43 MB/s) - ‘quotefile.txt’ saved [15029]
为什么我收到此错误
Will not apply HSTS. The HSTS database must be a regular and non-world-writable file. ERROR: could not open HSTS store at '/home/atul/.wget-hsts'. HSTS will be disabled.
以及如何解决这个问题？
重新安装后我遇到了这个问题。之前我使用的是 Windows 10 Pro 版本 19035，但现在我使用的是 Windows 10 Pro 版本 1909。
代码 -
convert -size 2000x1000 xc:none -gravity center \
-stroke yellow -pointsize 50 -font Courier-BoldOblique -strokewidth 3 -annotate +100+100 caption:'Conflict is the gadfly of thought. It stirs us to observation and memory. It instigates to invention. It shocks us out of sheeplike passivity, and sets us at noting and contriving' \
-blur 0x25 -level 0%,50% \
-fill white -stroke none -annotate +100+100 caption:'Conflict is the gadfly of thought. It stirs us to observation and memory. It instigates to invention. It shocks us out of sheeplike passivity, and sets us at noting and contriving' \
1.jpg +swap -gravity center -geometry +0-3 \
-composite Walpaperquote.jpg
输出 ：
我的问题是：我怎样才能使完整的文本出现？哪里出了问题？
提前感谢您的帮助！尝试了很多方法，但无法弄清楚如何正确设置！我对 ImageMagick 很陌生！
如何在 Linux 上使用 Windows PE ISO 创建可启动 USB？
注意 - 任何支持从 linux 创建可引导 USB 的 Web 上可用的 Windows PE ISO 都会有所帮助（请同时提及步骤或参考）。
背景 - 我有 Hiren 的 BootCD PE，想从 Linux 创建一个可引导的 USB。遵循这个，但问题是所有答案都指的是 ISO 中不再存在的 HBCD 文件夹。（我注意到一个奇怪的事情，即使 menu.lst 文件也指的是 HBCD 文件夹）
其他指南需要 Windows 来创建可启动 USB，但目前我只能访问 Linux（并尝试对无法启动的窗口进行故障排除）
直接从使用 unetbootin 创建的 USB 引导没有帮助。
我不喜欢喝葡萄酒，所以不使用它们的答案会很有帮助。
提前致谢！！！