` command displays slice information about a specified service, including its slice. This example shows the `at` daemon:
+
+
+```
+[root@testvm1 ~]# systemctl status atd.service
+● atd.service - Deferred execution scheduler
+ Loaded: loaded (/usr/lib/systemd/system/atd.service; enabled; vendor preset: enabled)
+ Active: active (running) since Wed 2020-09-23 12:18:24 EDT; 1 day 3h ago
+ Docs: man:atd(8)
+ Main PID: 1010 (atd)
+ Tasks: 1 (limit: 14760)
+ Memory: 440.0K
+ CPU: 5ms
+ CGroup: /system.slice/atd.service
+ └─1010 /usr/sbin/atd -f
+
+Sep 23 12:18:24 testvm1.both.org systemd[1]: Started Deferred execution scheduler.
+[root@testvm1 ~]#
+```
+
+This is an excellent example of one reason that I find systemd more usable than SystemV and the old init program. There is so much more information here than SystemV could provide. The cgroup entry includes the hierarchical structure where the `system.slice` is systemd (PID 1), and the `atd.service` is one level below and part of the `system.slice`. The second line of the cgroup entry also shows the process ID (PID) and the command used to start the daemon.
+
+The `systemctl` command shows multiple cgroup entries. The `--all` option shows all slices, including those that are not currently active:
+
+
+```
+[root@testvm1 ~]# systemctl -t slice --all
+ UNIT LOAD ACTIVE SUB DESCRIPTION
+ -.slice loaded active active Root Slice
+ system-getty.slice loaded active active system-getty.slice
+ system-lvm2\x2dpvscan.slice loaded active active system-lvm2\x2dpvscan.slice
+ system-modprobe.slice loaded active active system-modprobe.slice
+ system-sshd\x2dkeygen.slice loaded active active system-sshd\x2dkeygen.slice
+ system-systemd\x2dcoredump.slice loaded inactive dead system-systemd\x2dcoredump.slice
+ system-systemd\x2dfsck.slice loaded active active system-systemd\x2dfsck.slice
+ system.slice loaded active active System Slice
+ user-0.slice loaded active active User Slice of UID 0
+ user-1000.slice loaded active active User Slice of UID 1000
+ user.slice loaded active active User and Session Slice
+
+LOAD = Reflects whether the unit definition was properly loaded.
+ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
+SUB = The low-level unit activation state, values depend on unit type.
+
+11 loaded units listed.
+To show all installed unit files use 'systemctl list-unit-files'.
+[root@testvm1 ~]#
+```
+
+The first thing to notice about this data is that it shows user slices for UIDs 0 (root) and 1000, which is my user login. This shows only the slices and not the services that are part of each slice. This data shows that a slice is created for each user at the time they log in. This can provide a way to manage all of a user's tasks as a single cgroup entity.
+
+### Explore the cgroup hierarchy
+
+All is well and good so far, but cgroups are hierarchical, and all of the service units run as members of one of the cgroups. Viewing that hierarchy is easy and uses one old command and one new one that is part of systemd.
+
+The `ps` command can be used to map the processes and their locations in the cgroup hierarchy. Note that it is necessary to specify the desired data columns when using the `ps` command. I significantly reduced the volume of output from this command below, but I tried to leave enough so you can get a feel for what you might find on your systems:
+
+
+```
+[root@testvm1 ~]# ps xawf -eo pid,user,cgroup,args
+ PID USER CGROUP COMMAND
+ 2 root - [kthreadd]
+ 3 root - \\_ [rcu_gp]
+ 4 root - \\_ [rcu_par_gp]
+ 6 root - \\_ [kworker/0:0H-kblockd]
+ 9 root - \\_ [mm_percpu_wq]
+ 10 root - \\_ [ksoftirqd/0]
+ 11 root - \\_ [rcu_sched]
+ 12 root - \\_ [migration/0]
+ 13 root - \\_ [cpuhp/0]
+ 14 root - \\_ [cpuhp/1]
+<SNIP>
+ 625406 root - \\_ [kworker/3:0-ata_sff]
+ 625409 root - \\_ [kworker/u8:0-events_unbound]
+ 1 root 0::/init.scope /usr/lib/systemd/systemd --switched-root --system --deserialize 30
+ 588 root 0::/system.slice/systemd-jo /usr/lib/systemd/systemd-journald
+ 599 root 0::/system.slice/systemd-ud /usr/lib/systemd/systemd-udevd
+ 741 root 0::/system.slice/auditd.ser /sbin/auditd
+ 743 root 0::/system.slice/auditd.ser \\_ /usr/sbin/sedispatch
+ 764 root 0::/system.slice/ModemManag /usr/sbin/ModemManager
+ 765 root 0::/system.slice/NetworkMan /usr/sbin/NetworkManager --no-daemon
+ 767 root 0::/system.slice/irqbalance /usr/sbin/irqbalance --foreground
+ 779 root 0::/system.slice/mcelog.ser /usr/sbin/mcelog --ignorenodev --daemon --foreground
+ 781 root 0::/system.slice/rngd.servi /sbin/rngd -f
+ 782 root 0::/system.slice/rsyslog.se /usr/sbin/rsyslogd -n
+<SNIP>
+ 893 root 0::/system.slice/sshd.servi sshd: /usr/sbin/sshd -D [listener] 0 of 10-100 startups
+ 1130 root 0::/user.slice/user-0.slice \\_ sshd: root [priv]
+ 1147 root 0::/user.slice/user-0.slice | \\_ sshd: root@pts/0
+ 1148 root 0::/user.slice/user-0.slice | \\_ -bash
+ 1321 root 0::/user.slice/user-0.slice | \\_ screen
+ 1322 root 0::/user.slice/user-0.slice | \\_ SCREEN
+ 1323 root 0::/user.slice/user-0.slice | \\_ /bin/bash
+ 498801 root 0::/user.slice/user-0.slice | | \\_ man systemd.resource-control
+ 498813 root 0::/user.slice/user-0.slice | | \\_ less
+ 1351 root 0::/user.slice/user-0.slice | \\_ /bin/bash
+ 123293 root 0::/user.slice/user-0.slice | | \\_ man systemd.slice
+ 123305 root 0::/user.slice/user-0.slice | | \\_ less
+ 1380 root 0::/user.slice/user-0.slice | \\_ /bin/bash
+ 625412 root 0::/user.slice/user-0.slice | | \\_ ps xawf -eo pid,user,cgroup,args
+ 625413 root 0::/user.slice/user-0.slice | | \\_ less
+ 246795 root 0::/user.slice/user-0.slice | \\_ /bin/bash
+ 625338 root 0::/user.slice/user-0.slice | \\_ /usr/bin/mc -P /var/tmp/mc-root/mc.pwd.246795
+ 625340 root 0::/user.slice/user-0.slice | \\_ bash -rcfile .bashrc
+ 1218 root 0::/user.slice/user-1000.sl \\_ sshd: dboth [priv]
+ 1233 dboth 0::/user.slice/user-1000.sl \\_ sshd: dboth@pts/1
+ 1235 dboth 0::/user.slice/user-1000.sl \\_ -bash
+<SNIP>
+ 1010 root 0::/system.slice/atd.servic /usr/sbin/atd -f
+ 1011 root 0::/system.slice/crond.serv /usr/sbin/crond -n
+ 1098 root 0::/system.slice/lxdm.servi /usr/sbin/lxdm-binary
+ 1106 root 0::/system.slice/lxdm.servi \\_ /usr/libexec/Xorg -background none :0 vt01 -nolisten tcp -novtswitch -auth /var/run/lxdm/lxdm-:0.auth
+ 370621 root 0::/user.slice/user-1000.sl \\_ /usr/libexec/lxdm-session
+ 370631 dboth 0::/user.slice/user-1000.sl \\_ xfce4-session
+ 370841 dboth 0::/user.slice/user-1000.sl \\_ /usr/bin/ssh-agent /bin/sh -c exec -l bash -c "/usr/bin/startxfce4"
+ 370911 dboth 0::/user.slice/user-1000.sl \\_ xfwm4 --display :0.0 --sm-client-id 2dead44ab-0b4d-4101-bca4-e6771f4a8ac2
+ 370930 dboth 0::/user.slice/user-1000.sl \\_ xfce4-panel --display :0.0 --sm-client-id 2ce38b8ef-86fd-4189-ace5-deec1d0e0952
+ 370942 dboth 0::/user.slice/user-1000.sl | \\_ /usr/lib64/xfce4/panel/wrapper-2.0 /usr/lib64/xfce4/panel/plugins/libsystray.so 6 23068680 systr
+ay Notification Area Area where notification icons appear
+ 370943 dboth 0::/user.slice/user-1000.sl | \\_ /usr/lib64/xfce4/panel/wrapper-2.0 /usr/lib64/xfce4/panel/plugins/libpulseaudio-plugin.so 8 2306
+8681 pulseaudio PulseAudio Plugin Adjust the audio volume of the PulseAudio sound system
+ 370944 dboth 0::/user.slice/user-1000.sl | \\_ /usr/lib64/xfce4/panel/wrapper-2.0 /usr/lib64/xfce4/panel/plugins/libxfce4powermanager.so 9 2306
+8682 power-manager-plugin Power Manager Plugin Display the battery levels of your devices and control the brightness of your display
+ 370945 dboth 0::/user.slice/user-1000.sl | \\_ /usr/lib64/xfce4/panel/wrapper-2.0 /usr/lib64/xfce4/panel/plugins/libnotification-plugin.so 10 2
+3068683 notification-plugin Notification Plugin Notification plugin for the Xfce panel
+ 370948 dboth 0::/user.slice/user-1000.sl | \\_ /usr/lib64/xfce4/panel/wrapper-2.0 /usr/lib64/xfce4/panel/plugins/libactions.so 14 23068684 acti
+ons Action Buttons Log out, lock or other system actions
+ 370934 dboth 0::/user.slice/user-1000.sl \\_ Thunar --sm-client-id 2cfc809d8-4e1d-497a-a5c5-6e4fa509c3fb --daemon
+ 370939 dboth 0::/user.slice/user-1000.sl \\_ xfdesktop --display :0.0 --sm-client-id 299be0608-4dca-4055-b4d6-55ec6e73a324
+ 370962 dboth 0::/user.slice/user-1000.sl \\_ nm-applet
+<SNIP>
+```
+
+You can view the entire hierarchy with the `systemd-cgls` command, which is a bit simpler because it does not require any complex options.
+
+I have shortened this tree view considerably. as well, but I left enough to give you some idea of the amount of data as well as the types of entries you should see when you do this on your system. I did this on one of my virtual machines, and it is about 200 lines long; the amount of data from my primary workstation is about 250 lines:
+
+
+```
+[root@testvm1 ~]# systemd-cgls
+Control group /:
+-.slice
+├─user.slice
+│ ├─user-0.slice
+│ │ ├─session-1.scope
+│ │ │ ├─ 1130 sshd: root [priv]
+│ │ │ ├─ 1147 sshd: root@pts/0
+│ │ │ ├─ 1148 -bash
+│ │ │ ├─ 1321 screen
+│ │ │ ├─ 1322 SCREEN
+│ │ │ ├─ 1323 /bin/bash
+│ │ │ ├─ 1351 /bin/bash
+│ │ │ ├─ 1380 /bin/bash
+│ │ │ ├─123293 man systemd.slice
+│ │ │ ├─123305 less
+│ │ │ ├─246795 /bin/bash
+│ │ │ ├─371371 man systemd-cgls
+│ │ │ ├─371383 less
+│ │ │ ├─371469 systemd-cgls
+│ │ │ └─371470 less
+│ │ └─[user@0.service][6] …
+│ │ ├─dbus-broker.service
+│ │ │ ├─1170 /usr/bin/dbus-broker-launch --scope user
+│ │ │ └─1171 dbus-broker --log 4 --controller 12 --machine-id 3bccd1140fca488187f8a1439c832f07 --max-bytes 100000000000000 --max-fds 25000000000000 --max->
+│ │ ├─gvfs-daemon.service
+│ │ │ └─1173 /usr/libexec/gvfsd
+│ │ └─init.scope
+│ │ ├─1137 /usr/lib/systemd/systemd --user
+│ │ └─1138 (sd-pam)
+│ └─user-1000.slice
+│ ├─[user@1000.service][7] …
+│ │ ├─dbus\x2d:1.2\x2dorg.xfce.Xfconf.slice
+│ │ │ └─dbus-:[1.2-org.xfce.Xfconf@0.service][8]
+│ │ │ └─370748 /usr/lib64/xfce4/xfconf/xfconfd
+│ │ ├─dbus\x2d:1.2\x2dca.desrt.dconf.slice
+│ │ │ └─dbus-:[1.2-ca.desrt.dconf@0.service][9]
+│ │ │ └─371262 /usr/libexec/dconf-service
+│ │ ├─dbus-broker.service
+│ │ │ ├─1260 /usr/bin/dbus-broker-launch --scope user
+│ │ │ └─1261 dbus-broker --log 4 --controller 11 --machine-id
+<SNIP>
+│ │ └─gvfs-mtp-volume-monitor.service
+│ │ └─370987 /usr/libexec/gvfs-mtp-volume-monitor
+│ ├─session-3.scope
+│ │ ├─1218 sshd: dboth [priv]
+│ │ ├─1233 sshd: dboth@pts/1
+│ │ └─1235 -bash
+│ └─session-7.scope
+│ ├─370621 /usr/libexec/lxdm-session
+│ ├─370631 xfce4-session
+│ ├─370805 /usr/bin/VBoxClient --clipboard
+│ ├─370806 /usr/bin/VBoxClient --clipboard
+│ ├─370817 /usr/bin/VBoxClient --seamless
+│ ├─370818 /usr/bin/VBoxClient --seamless
+│ ├─370824 /usr/bin/VBoxClient --draganddrop
+│ ├─370825 /usr/bin/VBoxClient --draganddrop
+│ ├─370841 /usr/bin/ssh-agent /bin/sh -c exec -l bash -c "/usr/bin/startxfce4"
+│ ├─370910 /bin/gpg-agent --sh --daemon --write-env-file /home/dboth/.cache/gpg-agent-info
+│ ├─370911 xfwm4 --display :0.0 --sm-client-id 2dead44ab-0b4d-4101-bca4-e6771f4a8ac2
+│ ├─370923 xfsettingsd --display :0.0 --sm-client-id 261b4a437-3029-461c-9551-68c2c42f4fef
+│ ├─370930 xfce4-panel --display :0.0 --sm-client-id 2ce38b8ef-86fd-4189-ace5-deec1d0e0952
+│ ├─370934 Thunar --sm-client-id 2cfc809d8-4e1d-497a-a5c5-6e4fa509c3fb --daemon
+│ ├─370939 xfdesktop --display :0.0 --sm-client-id 299be0608-4dca-4055-b4d6-55ec6e73a324
+<SNIP>
+└─system.slice
+ ├─rngd.service
+ │ └─1650 /sbin/rngd -f
+ ├─irqbalance.service
+ │ └─1631 /usr/sbin/irqbalance --foreground
+ ├─fprintd.service
+ │ └─303383 /usr/libexec/fprintd
+ ├─systemd-udevd.service
+ │ └─956 /usr/lib/systemd/systemd-udevd
+<SNIP>
+ ├─systemd-journald.service
+ │ └─588 /usr/lib/systemd/systemd-journald
+ ├─atd.service
+ │ └─1010 /usr/sbin/atd -f
+ ├─system-dbus\x2d:1.10\x2dorg.freedesktop.problems.slice
+ │ └─dbus-:[1.10-org.freedesktop.problems@0.service][10]
+ │ └─371197 /usr/sbin/abrt-dbus -t133
+ ├─sshd.service
+ │ └─893 sshd: /usr/sbin/sshd -D [listener] 0 of 10-100 startups
+ ├─vboxservice.service
+ │ └─802 /usr/sbin/VBoxService -f
+ ├─crond.service
+ │ └─1011 /usr/sbin/crond -n
+ ├─NetworkManager.service
+ │ └─765 /usr/sbin/NetworkManager --no-daemon
+ ├─switcheroo-control.service
+ │ └─787 /usr/libexec/switcheroo-control
+ <SNIP>
+```
+
+This tree view shows all of the user and system slices and the services and programs running in each cgroup. Notice the units called "scopes," which group related programs into a management unit, within the `user-1000.slice` in the listing above. The `user-1000.slice/session-7.scope` cgroup contains the GUI desktop program hierarchy, starting with the LXDM display manager session and all of its subtasks, including things like the Bash shell and the Thunar GUI file manager.
+
+Scope units are not defined in configuration files but are generated programmatically as the result of starting groups of related programs. Scope units do not create or start the processes running as part of that cgroup. All processes within the scope are equal, and there is no internal hierarchy. The life of a scope begins when the first process is created and ends when the last process is destroyed.
+
+Open several windows on your desktop, such as terminal emulators, LibreOffice, or whatever you want, then switch to an available virtual console and start something like `top` or [Midnight Commander][11]. Run the `systemd-cgls` command on your host, and take note of the overall hierarchy and the scope units.
+
+The `systemd-cgls` command provides a more complete representation of the cgroup hierarchy (and details of the units that make it up) than any other command I have found. I prefer its cleaner representation of the tree than what the `ps` command provides.
+
+### With a little help from my friends
+
+After covering these basics, I had planned to go into more detail about cgroups and how to use them, but I discovered a series of four excellent articles by Red Hat's [Steve Ovens][12] on Opensource.com's sister site [Enable Sysadmin][13]. Rather then basically rewriting Steve's articles, I decided it would be much better to take advantage of his cgroup expertise by linking to them:
+
+ 1. [A Linux sysadmin's introduction to cgroups][14]
+ 2. [How to manage cgroups with CPUShares][15]
+ 3. [Managing cgroups the hard way—manually][16]
+ 4. [Managing cgroups with systemd][17]
+
+
+
+Enjoy and learn from them, as I did.
+
+### Other resources
+
+There is a great deal of information about systemd available on the internet, but much is terse, obtuse, or even misleading. In addition to the resources mentioned in this article, the following webpages offer more detailed and reliable information about systemd startup. This list has grown since I started this series of articles to reflect the research I have done.
+
+ * The Fedora Project has a good, practical [guide][18] [to systemd][18]. It has pretty much everything you need to know in order to configure, manage, and maintain a Fedora computer using systemd.
+ * The Fedora Project also has a good [cheat sheet][19] that cross-references the old SystemV commands to comparable systemd ones.
+ * The [systemd.unit(5) manual page][20] contains a nice list of unit file sections and their configuration options along with concise descriptions of each.
+ * Red Hat documentation contains a good description of the [Unit file structure][21] as well as other important information.
+ * For detailed technical information about systemd and the reasons for creating it, check out Freedesktop.org's [description of systemd][22]. This page is one of the best I have found because it contains many links to other important and accurate documentation.
+ * Linux.com's "More systemd fun" offers more advanced systemd [information and tips][23].
+ * See the man page for [systemd.resource-control(5)][24].
+ * In [_The Linux kernel user's and administrator's guide_][25], see the [Control Group v2][26] entry.
+
+
+
+There is also a series of deeply technical articles for Linux sysadmins by Lennart Poettering, the designer and primary developer of systemd. These articles were written between April 2010 and September 2011, but they are just as relevant now as they were then. Much of everything else good that has been written about systemd and its ecosystem is based on these papers.
+
+ * [Rethinking PID 1][27]
+ * [systemd for Administrators, Part I][28]
+ * [systemd for Administrators, Part II][29]
+ * [systemd for Administrators, Part III][30]
+ * [systemd for Administrators, Part IV][31]
+ * [systemd for Administrators, Part V][32]
+ * [systemd for Administrators, Part VI][33]
+ * [systemd for Administrators, Part VII][34]
+ * [systemd for Administrators, Part VIII][35]
+ * [systemd for Administrators, Part IX][36]
+ * [systemd for Administrators, Part X][37]
+ * [systemd for Administrators, Part XI][38]
+
+
+
+--------------------------------------------------------------------------------
+
+via: https://opensource.com/article/20/10/cgroups
+
+作者:[David Both][a]
+选题:[lujun9972][b]
+译者:[译者ID](https://github.com/译者ID)
+校对:[校对者ID](https://github.com/校对者ID)
+
+本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译,[Linux中国](https://linux.cn/) 荣誉推出
+
+[a]: https://opensource.com/users/dboth
+[b]: https://github.com/lujun9972
+[1]: https://opensource.com/sites/default/files/styles/image-full-size/public/lead-images/lenovo-thinkpad-laptop-concentration-focus-windows-office.png?itok=-8E2ihcF (Woman using laptop concentrating)
+[2]: https://en.wikipedia.org/wiki/Top_(software)
+[3]: https://opensource.com/article/19/11/monitoring-linux-glances
+[4]: https://opensource.com/article/20/4/systemd
+[5]: https://en.wikipedia.org/wiki/Cgroups
+[6]: mailto:user@0.service
+[7]: mailto:user@1000.service
+[8]: mailto:1.2-org.xfce.Xfconf@0.service
+[9]: mailto:1.2-ca.desrt.dconf@0.service
+[10]: mailto:1.10-org.freedesktop.problems@0.service
+[11]: https://midnight-commander.org/
+[12]: https://www.redhat.com/sysadmin/users/steve-ovens
+[13]: https://www.redhat.com/sysadmin/
+[14]: https://www.redhat.com/sysadmin/cgroups-part-one
+[15]: https://www.redhat.com/sysadmin/cgroups-part-two
+[16]: https://www.redhat.com/sysadmin/cgroups-part-three
+[17]: https://www.redhat.com/sysadmin/cgroups-part-four
+[18]: https://docs.fedoraproject.org/en-US/quick-docs/understanding-and-administering-systemd/index.html
+[19]: https://fedoraproject.org/wiki/SysVinit_to_Systemd_Cheatsheet
+[20]: https://man7.org/linux/man-pages/man5/systemd.unit.5.html
+[21]: https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html/configuring_basic_system_settings/managing-services-with-systemd_configuring-basic-system-settings#Managing_Services_with_systemd-Unit_File_Structure
+[22]: https://www.freedesktop.org/wiki/Software/systemd/
+[23]: https://www.linux.com/training-tutorials/more-systemd-fun-blame-game-and-stopping-services-prejudice/
+[24]: https://man7.org/linux/man-pages/man5/systemd.resource-control.5.html
+[25]: https://www.kernel.org/doc/html/latest/admin-guide/index.html
+[26]: https://www.kernel.org/doc/html/latest/admin-guide/cgroup-v2.html
+[27]: http://0pointer.de/blog/projects/systemd.html
+[28]: http://0pointer.de/blog/projects/systemd-for-admins-1.html
+[29]: http://0pointer.de/blog/projects/systemd-for-admins-2.html
+[30]: http://0pointer.de/blog/projects/systemd-for-admins-3.html
+[31]: http://0pointer.de/blog/projects/systemd-for-admins-4.html
+[32]: http://0pointer.de/blog/projects/three-levels-of-off.html
+[33]: http://0pointer.de/blog/projects/changing-roots
+[34]: http://0pointer.de/blog/projects/blame-game.html
+[35]: http://0pointer.de/blog/projects/the-new-configuration-files.html
+[36]: http://0pointer.de/blog/projects/on-etc-sysinit.html
+[37]: http://0pointer.de/blog/projects/instances.html
+[38]: http://0pointer.de/blog/projects/inetd.html
diff --git a/sources/tech/20201030 How to Use apt-cache Command in Debian, Ubuntu and Other Linux Distributions.md b/sources/tech/20201030 How to Use apt-cache Command in Debian, Ubuntu and Other Linux Distributions.md
new file mode 100644
index 0000000000..23b314319b
--- /dev/null
+++ b/sources/tech/20201030 How to Use apt-cache Command in Debian, Ubuntu and Other Linux Distributions.md
@@ -0,0 +1,167 @@
+[#]: collector: (lujun9972)
+[#]: translator: ( )
+[#]: reviewer: ( )
+[#]: publisher: ( )
+[#]: url: ( )
+[#]: subject: (How to Use apt-cache Command in Debian, Ubuntu and Other Linux Distributions)
+[#]: via: (https://itsfoss.com/apt-cache-command/)
+[#]: author: (Abhishek Prakash https://itsfoss.com/author/abhishek/)
+
+How to Use apt-cache Command in Debian, Ubuntu and Other Linux Distributions
+======
+
+_**With apt-cache command, you can search for package details in the local APT cache. Learn to use apt-cache command in this tutorial.**_
+
+### What is apt-cache command used for?
+
+The [apt][1] [package manager][2] works on a local cache of package metadata. The metadata usually consists information like package name, version, description, dependencies, its repository and developers. With the apt-cache command, you can query this local APT cache and get relevant information.
+
+You can search for the availability of a package, its version number, its dependencies among other things. I’ll show you how to use the apt-cache command with examples.
+
+The **location of APT cache** is /var/lib/apt/lists/ directory. Which repository metadata to cache depends on the repositories added in your source list in the /etc/apt/sources.list file and additional repository files located in ls /etc/apt/sources.list.d directory.
+
+Surprisingly, apt-cache doesn’t clear the APT cache. For that you’ll have to [use the apt-get clean command][3].
+
+Needless to say, the APT packaging system is used on Debian and Debian-based Linux distributions like Ubuntu, Linux Mint, elementary OS etc. You cannot use it on Arch or Fedora.
+
+### Using apt-cache command
+
+![][4]
+
+Like any other Linux command, there are several options available with apt-cache and you can always refer to its man page to read about them.
+
+However, you probably won’t need to use all of them. This is why I am going to show you only the most common and useful examples of the apt-cache command in this tutorial.
+
+Always update
+
+It is always a good idea to update the local APT cache to sync it with the remote repositories. How do you do that? You use the command:
+
+**sudo apt update**
+
+#### Search for packages
+
+The most common use of apt-cache command is for finding package. You can use a regex pattern to search for a package in the local APT cache.
+
+```
+apt-cache search package_name
+```
+
+By default, it looks for the search term in both the name and description of the package. It shows the matching package along with its short description in alphabetical order.
+
+![][5]
+
+You can narrow down your search to look for the search term in package names only.
+
+```
+apt-cache search --names-only package_name
+```
+
+![][6]
+
+If you want complete details of all the matched packages, you may use the `--full` flag. It can also be used with `--names-only` flag.
+
+![][7]
+
+#### Get detailed package information
+
+If you know the exact package name (or if you have manged to find it with the search), you can get the detailed metadata information on the package.
+
+```
+apt-cache show package_name
+```
+
+![][8]
+
+You can see all kind of details in the package metadata like name, version, developer, maintainer, repository, short and long description, package size and even checksum.
+
+There is another option showpkg that displays information about the package name, version and its forward and reverse dependencies.
+
+```
+apt-cache showpkg package_name
+```
+
+#### apt-cache policy
+
+This is one of the rarely used option of apt-cache command. The policy options helps you debug the issue related to the [preference file][9].
+
+If you specify the package name, it will show whether the package is installed, which version is available from which repository and its priority.
+
+![][10]
+
+By default, each installed package version has a priority of 100 and a non-installed package has a priority of 500. The same package may have more than one version with a different priority. APT installs the version with higher priority unless the installed version is newer.
+
+If this doesn’t make sense, it’s okay. It will be extremely rare for a regular Linux user to dwell this deep into package management.
+
+#### Check dependencies and reverse dependencies of a package
+
+You can [check the dependencies of a package][11] before (or even after) installing it. It also shows all the possible packages that can fulfill the dependency.
+
+```
+apt-cache depends package
+```
+
+![][12]
+
+You may also check which packages are dependent on a certain package by checking the reverse dependencies with apt-cahce.
+
+![][13]
+
+Frankly, I was also surprised to see that a DevOps tool like Ansible has a dependency on a [funny Linux command like Cowsay][14]. I think it’s perhaps because after [installing Ansible][15], it displays some message on the nodes.
+
+#### Check unmet dependencies
+
+You may get troubled with [unmet dependencies issue in Ubuntu][16] or other Linux. The apt-cache command provides option to check all the unmet dependencies of various available packages on your system.
+
+```
+apt-cache unmet
+```
+
+![][17]
+
+**Conclusion**
+
+You can list all available packages with the apt-cache command. The output would be huge, so I suggest combining it with [wc command][18] to get a total number of available packages like this:
+
+```
+apt-cache pkgnames | wc -l
+```
+
+Did you notice that you don’t need to be [root user][19] for using apt-cache command?
+
+The newer [apt command][20] has a few options available to match the features of apt-cache command. Since apt is new, apt-get and its associated commands like apt-cache are still preferred to be used in scripts.
+
+I hope you find this tutorial helpful. If you have questions about any point discussed above or suggestion to improve it, please let me know in the comments.
+
+--------------------------------------------------------------------------------
+
+via: https://itsfoss.com/apt-cache-command/
+
+作者:[Abhishek Prakash][a]
+选题:[lujun9972][b]
+译者:[译者ID](https://github.com/译者ID)
+校对:[校对者ID](https://github.com/校对者ID)
+
+本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译,[Linux中国](https://linux.cn/) 荣誉推出
+
+[a]: https://itsfoss.com/author/abhishek/
+[b]: https://github.com/lujun9972
+[1]: https://wiki.debian.org/Apt
+[2]: https://itsfoss.com/package-manager/
+[3]: https://itsfoss.com/clear-apt-cache/
+[4]: https://i1.wp.com/itsfoss.com/wp-content/uploads/2020/10/apt-cache-command.png?resize=800%2C450&ssl=1
+[5]: https://i2.wp.com/itsfoss.com/wp-content/uploads/2020/10/apt-cache-search.png?resize=759%2C437&ssl=1
+[6]: https://i1.wp.com/itsfoss.com/wp-content/uploads/2020/10/apt-cache-search-names-only.png?resize=759%2C209&ssl=1
+[7]: https://i2.wp.com/itsfoss.com/wp-content/uploads/2020/10/apt-cache-show-full.png?resize=759%2C722&ssl=1
+[8]: https://i2.wp.com/itsfoss.com/wp-content/uploads/2020/10/apt-cache-show-pkgname.png?resize=800%2C795&ssl=1
+[9]: https://debian-handbook.info/browse/stable/sect.apt-get.html#sect.apt.priorities
+[10]: https://i0.wp.com/itsfoss.com/wp-content/uploads/2020/10/apt-cache-policy.png?resize=795%2C456&ssl=1
+[11]: https://itsfoss.com/check-dependencies-package-ubuntu/
+[12]: https://i2.wp.com/itsfoss.com/wp-content/uploads/2020/10/apt-cache-dependency-check.png?resize=768%2C304&ssl=1
+[13]: https://i1.wp.com/itsfoss.com/wp-content/uploads/2020/10/apt-cache-reverse-dependency.png?resize=768%2C304&ssl=1
+[14]: https://itsfoss.com/funny-linux-commands/
+[15]: https://linuxhandbook.com/install-ansible-linux/
+[16]: https://itsfoss.com/held-broken-packages-error/
+[17]: https://i0.wp.com/itsfoss.com/wp-content/uploads/2020/10/apt-cache-unmet.png?resize=759%2C399&ssl=1
+[18]: https://linuxhandbook.com/wc-command/
+[19]: https://itsfoss.com/root-user-ubuntu/
+[20]: https://itsfoss.com/apt-command-guide/
diff --git a/translated/talk/20191105 My first contribution to open source- Making a decision.md b/translated/talk/20191105 My first contribution to open source- Making a decision.md
deleted file mode 100644
index 38cd62ac87..0000000000
--- a/translated/talk/20191105 My first contribution to open source- Making a decision.md
+++ /dev/null
@@ -1,56 +0,0 @@
-[#]: collector: (lujun9972)
-[#]: translator: ( chenmu-kk )
-[#]: reviewer: ( )
-[#]: publisher: ( )
-[#]: url: ( )
-[#]: subject: (My first contribution to open source: Making a decision)
-[#]: via: (https://opensource.com/article/19/11/my-first-open-source-contribution-mistake-decisions)
-[#]: author: (Galen Corey https://opensource.com/users/galenemco)
-
-我的第一次开源贡献:做出决定
-======
-一位新的开源贡献者记录了她加入到开源项目后开始犯得五个错误。
-
-![Lightbulb][1]
-
-先前,我将大量的责任归咎于[冒充综合症][2]因为这延迟了我的第一个开源贡献。但还有一个我无法忽视的因素:我无法做决定来拯救我的生活。 在[成千上百万][3]的开源项目中抉择时,选择一个要做贡献的项目势不可挡。如此压迫以至于我常常不得不关掉我的笔记本去思考:“或许我可以改天再做一次”。
-
-错误二是让我对做决定的恐惧妨碍了我做出第一次贡献。在理想世界里,也许我会带着一个我真正关心和想去做的特定项目开始我的开源之旅,但我有的只是总得为开源项目做出的贡献的模糊目标。对于那些处于同一处境的人来说,这儿有一些策略可以为自己的贡献挑选合适的项目(或者至少是一个好的项目)。
-
-### 我经常使用的工具
-
-一开始,我不认为有必要将自己局限于已经熟悉的工具或项目。有一些我之前从未使用过,但由于他们活跃的社区,或者他们解决了有趣的问题,因此看起来很有吸引力。
-
-但是,考虑我投入到这个项目中的时间有限,我决定继续使用我了解的工具。要了解工具需求,你需要熟悉它的工作方式。如果您想为自己不熟悉的项目做贡献,则需要完成一个额外的步骤来了解代码的功能和目标。这个额外的工作量是有趣且值得的,但也会使你的工作时间加倍。因为我的目标主要是贡献,坚持我所知道的是缩小范围一个很好的方式。回馈一个你认为有用的项目也是一种回报。
-
-### 我经常使用的工具
-
-一开始,我不认为有必要将自己局限于已经熟悉的工具或项目。有一些我之前从未使用过,但由于他们活跃的社区,或者他们解决了有趣的问题,因此看起来很有吸引力。
-
-但是,考虑我投入到这个项目中的时间有限,我决定继续使用我了解的工具。要了解工具需求,你需要熟悉它的工作方式。如果您想为自己不熟悉的项目做贡献,则需要完成一个额外的步骤来了解代码的功能和目标。这个额外的工作量是有趣且值得的,但也会使你的工作时间加倍。因为我的目标主要是贡献,坚持我所知道的是缩小范围一个很好的方式。回馈一个你认为有用的项目也是一种回报。
-
-因为这是我第一次为开源项目做出贡献,在此过程中我有很多问题。一些项目社区非常擅长记录选择问题和提出请求的程序。一些项目社区在记录流程方面很优秀,可以用来挑选其中的项目并提交请求。尽管那时我没有选择它们,因为在此之前我从未使用过该产品,[Gatsby][4]是该实践的一个范例。
-
-这种细致的文件帮助我们缓解一些不知如何去做的不安全感。它也给了我希望,项目是开放给新的贡献者,并将花时间来查看我的工作。除了贡献准则外,我还查看了问题部分,看看这个项目是否利用了“好的第一个问题”标志。这是该项目对初学者开放的另一个标志(并帮助你学会如何操作)。
-
-### 总结
-
-如果你还没有计划好一个项目,那么选择合适的领域进行您的第一个开源贡献已势不可挡。列出一系列标准可以帮助自己缩减选择范围,并为自己的首次提交找到一个好的项目。
-
---------------------------------------------------------------------------------
-
-via: https://opensource.com/article/19/11/my-first-open-source-contribution-mistake-decisions
-
-作者:[Galen Corey][a]
-选题:[lujun9972][b]
-译者:[chenmu-kk](https://github.com/chenmu-kk)
-校对:[校对者ID](https://github.com/校对者ID)
-
-本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译,[Linux中国](https://linux.cn/) 荣誉推出
-
-[a]: https://opensource.com/users/galenemco
-[b]: https://github.com/lujun9972
-[1]: https://opensource.com/sites/default/files/styles/image-full-size/public/lead-images/lightbulb-idea-think-yearbook-lead.png?itok=5ZpCm0Jh (Lightbulb)
-[2]: https://opensource.com/article/19/10/my-first-open-source-contribution-mistakes
-[3]: https://github.blog/2018-02-08-open-source-project-trends-for-2018/
-[4]: https://www.gatsbyjs.org/contributing/
diff --git a/translated/tech/20200521 Use the internet from the command line with curl.md b/translated/tech/20200521 Use the internet from the command line with curl.md
new file mode 100644
index 0000000000..156b195494
--- /dev/null
+++ b/translated/tech/20200521 Use the internet from the command line with curl.md
@@ -0,0 +1,161 @@
+[#]: collector: (lujun9972)
+[#]: translator: (MjSeven)
+[#]: reviewer: ( )
+[#]: publisher: ( )
+[#]: url: ( )
+[#]: subject: (Use the internet from the command line with curl)
+[#]: via: (https://opensource.com/article/20/5/curl-cheat-sheet)
+[#]: author: (Seth Kenlon https://opensource.com/users/seth)
+
+使用 curl 从命令行访问互联网
+======
+下载我们整理的 curl 备忘录。在不使用图形界面的情况下从互联网上获取所需的信息,curl 是一种快速有效的方法。
+
+![Cheat Sheet cover image][1]
+
+Curl 通常被认为是非交互式 Web 浏览器,这意味着它能够从互联网上获取信息并在你的终端中显示或将其保存到文件中。从表面看,这是 Web 浏览器,例如 Firefox 或 Chromium 所做的工作,只是它们默认情况下会 _渲染_ 信息,而 curl 会下载并显示原始信息。实际上,curl 命令可以做更多的事情,并且能够使用多种协议与服务器进行双向传输数据,这些协议包括 HTTP、FTP、SFTP、IMAP、POP3、LDAP、SMB、SMTP 等。对于普通终端用户来说,这是一个有用的工具;而对于系统管理员,这非常便捷;对于微服务和云开发人员来说,它是质量保证的工具。
+
+Curl 被设计为在没有用户交互的情况下工作,因此与 Firefox 不同,你必须从头到尾考虑与在线数据的交互。例如,如果想要在 Firefox 中查看网页,你需要启动 Firefox 窗口。打开 Firefox 后,在地址栏或搜索引擎中输入要访问的网站。然后,导航到网站,然后单击要查看的页面。
+
+对于 curl 来说也是如此,不同之处在于你需要一次执行所有操作:在启动 curl 的同时提供需要访问的 Internet 位置,并告诉它是否要将数据保存在终端或文件中。当你必须与需要身份验证的网站或 API 进行交互时,会变得有点复杂,但是一旦你学习了 **curl** 命令语法,它就会成为你的第二天性。为了帮助你掌握它,我们在一个方便的[备忘录][2]中收集了相关的语法信息。
+
+### 使用 curl 下载文件
+
+你可以通过提供指向特定 URL 的链接来使用 **curl** 命令下载文件。如果你提供的 URL 默认为 **index.html**,那么将下载此页面,并将下载的文件显示在终端屏幕上。你可以将数据通过管道传递到 less、tail 或任何其它命令:
+```
+$ curl "http://example.com" | tail -n 4
+ Example Domain
+ This domain is for use in illustrative examples in documents. You may use this domain in literature without prior coordination or asking for permission.
+ More information...
+