mirror of
https://github.com/LCTT/TranslateProject.git
synced 2025-03-09 01:30:10 +08:00
Merge remote-tracking branch 'LCTT/master'
This commit is contained in:
Xingyu.Wang
commit
3383c632d4
@ -1,11 +1,12 @@
|
|||||||
Free DOS 的简单介绍
|
FreeDOS 的简单介绍
|
||||||
======
|
======
|
||||||
|
> 学习如何穿行于 C:\ 提示符下，就像上世纪 90 年代的 DOS 高手一样。
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
FreeDOS 是一个古老的操作系统，但是对于多数人而言它又是陌生的。在 1994 年，我和几个开发者一起 [开发 FreeDOS][1]--一个完整、自由、DOS 兼容的操作系统，你可以用它来玩经典的 DOS 游戏、运行遗留的商业软件或者开发嵌入式系统。任何在 MS-DOS 下工作的程序在 FreeDOS 下也可以运行。
|
FreeDOS 是一个古老的操作系统，但是对于多数人而言它又是陌生的。在 1994 年，我和几个开发者一起 [开发了 FreeDOS][1] —— 这是一个完整、自由、兼容 DOS 的操作系统，你可以用它来玩经典的 DOS 游戏、运行过时的商业软件或者开发嵌入式系统。任何在 MS-DOS 下工作的程序在 FreeDOS 下也可以运行。
|
||||||
|
|
||||||
在 1994 年，任何一个曾经使用过微软专利的 MS-DOS 的人都会迅速地熟悉 FreeDOS。这是设计而为之的；FreeDOS 尽可能地去模仿 MS-DOS。结果，1990 年代的 DOS 用户能够直接转换到 FreeDOS。但是，时代变了。今天，开源的开发者们对于 Linux 命令行更熟悉或者他们可能倾向于像 [GNOME][2] 一样的图形桌面环境，这导致 FreeDOS 命令行界面最初看起来像个异类。
|
在 1994 年，任何一个曾经使用过微软的商业版 MS-DOS 的人都会迅速地熟悉 FreeDOS。这是设计而为之的；FreeDOS 尽可能地去模仿 MS-DOS。结果，1990 年代的 DOS 用户能够直接转换到 FreeDOS。但是，时代变了。今天，开源的开发者们对于 Linux 命令行更熟悉，或者他们可能倾向于像 [GNOME][2] 一样的图形桌面环境，这导致 FreeDOS 命令行界面最初看起来像个异类。
|
||||||
|
|
||||||
新的用户通常会问，“我已经安装了 [FreeDOS][3]，但是如何使用呢？”。如果你之前并没有使用过 DOS，那么闪烁的 `C:\>` DOS 提示符看起来会有点不太友好，而且可能有点吓人。这份 FreeDOS 的简单介绍将带你起步。它只提供了基础：如何浏览以及如何查看文件。如果你想了解比这里提及的更多的知识，访问 [FreeDOS 维基][4]。
|
新的用户通常会问，“我已经安装了 [FreeDOS][3]，但是如何使用呢？”。如果你之前并没有使用过 DOS，那么闪烁的 `C:\>` DOS 提示符看起来会有点不太友好，而且可能有点吓人。这份 FreeDOS 的简单介绍将带你起步。它只提供了基础：如何浏览以及如何查看文件。如果你想了解比这里提及的更多的知识，访问 [FreeDOS 维基][4]。
|
||||||
|
|
||||||
@ -15,13 +16,13 @@ FreeDOS 是一个古老的操作系统，但是对于多数人而言它又是陌
|
|||||||
|
|
||||||
|
|
||||||
|
|
||||||
DOS 是在个人电脑从软盘运行时期创建的一个“磁盘操作系统”。甚至当电脑支持硬盘了，在 1980 年代和 1990 年代，频繁地在不同的驱动器之间切换也是很普遍的。举例来说，你可能想将最重要的文件都备份一份拷贝到软盘中。
|
DOS 是在个人电脑从软盘运行时期创建的一个“<ruby>磁盘操作系统<rt>disk operating system</rt></ruby>”。甚至当电脑支持硬盘了，在 1980 年代和 1990 年代，频繁地在不同的驱动器之间切换也是很普遍的。举例来说，你可能想将最重要的文件都备份一份拷贝到软盘中。
|
||||||
|
|
||||||
DOS 使用一个字母来指代每个驱动器。早期的电脑仅拥有两个软盘驱动器，他们被分配了 `A:` 和 `B:` 盘符。硬盘上的第一个分区盘符是 `C:` ，然后其它的盘符依次这样分配下去。提示符中的 `C:` 表示你正在使用第一个硬盘的第一个分区。
|
DOS 使用一个字母来指代每个驱动器。早期的电脑仅拥有两个软盘驱动器，他们被分配了 `A:` 和 `B:` 盘符。硬盘上的第一个分区盘符是 `C:` ，然后其它的盘符依次这样分配下去。提示符中的 `C:` 表示你正在使用第一个硬盘的第一个分区。
|
||||||
|
|
||||||
从 1983 年的 PC-DOS 2.0 开始，DOS 也支持目录和子目录，非常类似 Linux 文件系统中的目录和子目录。但是跟 Linux 不一样的是，DOS 目录名由 `\` 分隔而不是 `/`。将这个与驱动器字母合起来看，提示符中的 `C:\` 表示你正在 `C:` 盘的顶端或者“根”目录。
|
从 1983 年的 PC-DOS 2.0 开始，DOS 也支持目录和子目录，非常类似 Linux 文件系统中的目录和子目录。但是跟 Linux 不一样的是，DOS 目录名由 `\` 分隔而不是 `/`。将这个与驱动器字母合起来看，提示符中的 `C:\` 表示你正在 `C:` 盘的顶端或者“根”目录。
|
||||||
|
|
||||||
`>` 修饰符提示你输入 DOS 命令的地方，就像众多 Linux shell 的 `$`。`>` 前面的部分告诉你当前的工作目录，然后你在 `>` 提示符这输入命令。
|
`>` 符号是提示你输入 DOS 命令的地方，就像众多 Linux shell 的 `$`。`>` 前面的部分告诉你当前的工作目录，然后你在 `>` 提示符这输入命令。
|
||||||
|
|
||||||
### 在 DOS 中找到你的使用方式
|
### 在 DOS 中找到你的使用方式
|
||||||
|
|
||||||
@ -33,7 +34,7 @@ DOS 使用一个字母来指代每个驱动器。早期的电脑仅拥有两个
|
|||||||
|
|
||||||
|
|
||||||
|
|
||||||
如果你不想显示单个文件大小的额外细节，你可以在 `DIR` 命令中使用 `/w` 选项来显示一个“宽泛”文件夹。注意，Linux 用户使用连字号（`-`）或者双连字号（`--`）来开启命令行选项，而 DOS 使用斜线字符（`/`）。
|
如果你不想显示单个文件大小的额外细节，你可以在 `DIR` 命令中使用 `/w` 选项来显示一个“宽”的目录列表。注意，Linux 用户使用连字号（`-`）或者双连字号（`--`）来开始命令行选项，而 DOS 使用斜线字符（`/`）。
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
@ -64,7 +65,7 @@ FreeDOS 也从 Linux 那借鉴了一些特性：你可以使用 `CD -` 跳转回
|
|||||||
|
|
||||||
|
|
||||||
|
|
||||||
小心不要尝试切换到一个不存在的磁盘。DOS 可能会将它设置为工作磁盘，但是如果你尝试在那做任何事，你将会遇到略微臭名昭著的“退出、重试、失败” DOS 错误信息。
|
小心不要尝试切换到一个不存在的磁盘。DOS 可能会将它设置为工作磁盘，但是如果你尝试在那做任何事，你将会遇到略微臭名昭著的“<ruby>退出、重试、失败<rt>Abort, Retry, Fail</rt></ruby>” DOS 错误信息。
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
@ -86,7 +87,7 @@ FreeDOS 也从 Linux 那借鉴了一些特性：你可以使用 `CD -` 跳转回
|
|||||||
|
|
||||||
在 FreeDOS 下，针对每个命令你都能够使用 `/?` 参数来获取简要的说明。举例来说，`EDIT /?` 会告诉你编辑器的用法和选项。或者你可以输入 `HELP` 来使用交互式帮助系统。
|
在 FreeDOS 下，针对每个命令你都能够使用 `/?` 参数来获取简要的说明。举例来说，`EDIT /?` 会告诉你编辑器的用法和选项。或者你可以输入 `HELP` 来使用交互式帮助系统。
|
||||||
|
|
||||||
像任何一个 DOS 一样，FreeDOS 被认为是一个简单的操作系统。仅使用一些基本命令就可以轻松浏览 DOS 文件系统。那么启动一个 QEMU 会话，安装 FreeDOS，然后尝试一下 DOS 命令行界面。也许它现在看起来就没那么吓人了。
|
像任何一个 DOS 一样，FreeDOS 被认为是一个简单的操作系统。仅使用一些基本命令就可以轻松浏览 DOS 文件系统。那么，启动一个 QEMU 会话，安装 FreeDOS，然后尝试一下 DOS 命令行界面吧。也许它现在看起来就没那么吓人了。
|
||||||
|
|
||||||
|
|
||||||
--------------------------------------------------------------------------------
|
--------------------------------------------------------------------------------
|
||||||
@ -96,7 +97,7 @@ via: https://opensource.com/article/18/4/gentle-introduction-freedos
|
|||||||
作者：[Jim Hall][a]
|
作者：[Jim Hall][a]
|
||||||
选题：[lujun9972](https://github.com/lujun9972)
|
选题：[lujun9972](https://github.com/lujun9972)
|
||||||
译者：[icecoobe](https://github.com/icecoobe)
|
译者：[icecoobe](https://github.com/icecoobe)
|
||||||
校对：[校对者ID](https://github.com/校对者ID)
|
校对：[wxy](https://github.com/wxy)
|
||||||
|
|
||||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
||||||
|
|
||||||
@ -3,7 +3,7 @@
|
|||||||
|
|
||||||
![AMD-Polaris][1]
|
![AMD-Polaris][1]
|
||||||
|
|
||||||
自从 sdfx 推出最初的 Voodoo 加速器以来，不起眼的显卡对你的 PC 是否可以玩游戏起到决定性作用，PC 上任何其它设备都无法与其相比。其它组件当然也很重要，但对于一个拥有 32GB 内存、价值 500 美金的 CPU 和 基于 PCIe 的存储设备的高端 PC，如果使用 10 年前的显卡，都无法以最高分辨率和细节质量运行当前<ruby>最高品质的游戏<rt>AAA titles</rt></ruby>，会发生卡顿甚至无响应。显卡（也常被称为 GPU，即<ruby>图形处理单元<rt>Graphic Processing Unit</rt></ruby>），对游戏性能影响极大，我们反复强调这一点；但我们通常并不会深入了解显卡的工作原理。
|
自从 3dfx 推出最初的 Voodoo 加速器以来，不起眼的显卡对你的 PC 是否可以玩游戏起到决定性作用，PC 上任何其它设备都无法与其相比。其它组件当然也很重要，但对于一个拥有 32GB 内存、价值 500 美金的 CPU 和 基于 PCIe 的存储设备的高端 PC，如果使用 10 年前的显卡，都无法以最高分辨率和细节质量运行当前<ruby>最高品质的游戏<rt>AAA titles</rt></ruby>，会发生卡顿甚至无响应。显卡（也常被称为 GPU，即<ruby>图形处理单元<rt>Graphic Processing Unit</rt></ruby>），对游戏性能影响极大，我们反复强调这一点；但我们通常并不会深入了解显卡的工作原理。
|
||||||
|
|
||||||
出于实际考虑，本文将概述 GPU 的上层功能特性，内容包括 AMD 显卡、Nvidia 显卡、Intel 集成显卡以及 Intel 后续可能发布的独立显卡之间共同的部分。也应该适用于 Apple、Imagination Technologies、Qualcomm、ARM 和其它显卡生产商发布的移动平台 GPU。
|
出于实际考虑，本文将概述 GPU 的上层功能特性，内容包括 AMD 显卡、Nvidia 显卡、Intel 集成显卡以及 Intel 后续可能发布的独立显卡之间共同的部分。也应该适用于 Apple、Imagination Technologies、Qualcomm、ARM 和其它显卡生产商发布的移动平台 GPU。
|
||||||
|
|
||||||
|
|||||||
@ -1,3 +1,5 @@
|
|||||||
|
pinewall translating
|
||||||
|
|
||||||
How to analyze your system with perf and Python
|
How to analyze your system with perf and Python
|
||||||
======
|
======
|
||||||
|
|
||||||
|
|||||||
@ -1,108 +0,0 @@
|
|||||||
translating----geekpi
|
|
||||||
|
|
||||||
How to install software from the Linux command line
|
|
||||||
======
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
If you use Linux for any amount of time, you'll soon learn there are many different ways to do the same thing. This includes installing applications on a Linux machine via the command line. I have been a Linux user for roughly 25 years, and time and time again I find myself going back to the command line to install my apps.
|
|
||||||
|
|
||||||
The most common method of installing apps from the command line is through software repositories (a place where software is stored) using what's called a package manager. All Linux apps are distributed as packages, which are nothing more than files associated with a package management system. Every Linux distribution comes with a package management system, but they are not all the same.
|
|
||||||
|
|
||||||
### What is a package management system?
|
|
||||||
|
|
||||||
A package management system is comprised of sets of tools and file formats that are used together to install, update, and uninstall Linux apps. The two most common package management systems are from Red Hat and Debian. Red Hat, CentOS, and Fedora all use the `rpm` system (.rpm files), while Debian, Ubuntu, Mint, and Ubuntu use `dpkg` (.deb files). Gentoo Linux uses a system called Portage, and Arch Linux uses nothing but tarballs (.tar files). The primary difference between these systems is how they install and maintain apps.
|
|
||||||
|
|
||||||
You might be wondering what's inside an `.rpm`, `.deb`, or `.tar` file. You might be surprised to learn that all are nothing more than plain old archive files (like `.zip`) that contain an application's code, instructions on how to install it, dependencies (what other apps it may depend on), and where its configuration files should be placed. The software that reads and executes all of those instructions is called a package manager.
|
|
||||||
|
|
||||||
### Debian, Ubuntu, Mint, and others
|
|
||||||
|
|
||||||
Debian, Ubuntu, Mint, and other Debian-based distributions all use `.deb` files and the `dpkg` package management system. There are two ways to install apps via this system. You can use the `apt` application to install from a repository, or you can use the `dpkg` app to install apps from `.deb` files. Let's take a look at how to do both.
|
|
||||||
|
|
||||||
Installing apps using `apt` is as easy as:
|
|
||||||
```
|
|
||||||
$ sudo apt install app_name
|
|
||||||
|
|
||||||
```
|
|
||||||
|
|
||||||
Uninstalling an app via `apt` is also super easy:
|
|
||||||
```
|
|
||||||
$ sudo apt remove app_name
|
|
||||||
|
|
||||||
```
|
|
||||||
|
|
||||||
To upgrade your installed apps, you'll first need to update the app repository:
|
|
||||||
```
|
|
||||||
$ sudo apt update
|
|
||||||
|
|
||||||
```
|
|
||||||
|
|
||||||
Once finished, you can update any apps that need updating with the following:
|
|
||||||
```
|
|
||||||
$ sudo apt upgrade
|
|
||||||
|
|
||||||
```
|
|
||||||
|
|
||||||
What if you want to update only a single app? No problem.
|
|
||||||
```
|
|
||||||
$ sudo apt update app_name
|
|
||||||
|
|
||||||
```
|
|
||||||
|
|
||||||
Finally, let's say the app you want to install is not available in the Debian repository, but it is available as a `.deb` download.
|
|
||||||
```
|
|
||||||
$ sudo dpkg -i app_name.deb
|
|
||||||
|
|
||||||
```
|
|
||||||
|
|
||||||
### Red Hat, CentOS, and Fedora
|
|
||||||
|
|
||||||
Red Hat, by default, uses several package management systems. These systems, while using their own terminology, are still very similar to each other and to the one used in Debian. For example, we can use either the `yum` or `dnf` manager to install apps.
|
|
||||||
```
|
|
||||||
$ sudo yum install app_name
|
|
||||||
|
|
||||||
$ sudo dnf install app_name
|
|
||||||
|
|
||||||
```
|
|
||||||
|
|
||||||
Apps in the `.rpm` format can also be installed with the `rpm` command.
|
|
||||||
```
|
|
||||||
$ sudo rpm -i app_name.rpm
|
|
||||||
|
|
||||||
```
|
|
||||||
|
|
||||||
Removing unwanted applications is just as easy.
|
|
||||||
```
|
|
||||||
$ sudo yum remove app_name
|
|
||||||
|
|
||||||
$ sudo dnf remove app_name
|
|
||||||
|
|
||||||
```
|
|
||||||
|
|
||||||
Updating apps is similarly easy.
|
|
||||||
```
|
|
||||||
$ yum update
|
|
||||||
|
|
||||||
$ sudo dnf upgrade --refresh
|
|
||||||
|
|
||||||
```
|
|
||||||
|
|
||||||
As you can see, installing, uninstalling, and updating Linux apps from the command line isn't hard at all. In fact, once you get used to it, you'll find it's faster than using desktop GUI-based management tools!
|
|
||||||
|
|
||||||
For more information on installing apps from the command line, please visit the Debian [Apt wiki][1], the [Yum cheat sheet][2], and the [DNF wiki][3].
|
|
||||||
|
|
||||||
--------------------------------------------------------------------------------
|
|
||||||
|
|
||||||
via: https://opensource.com/article/18/8/how-install-software-linux-command-line
|
|
||||||
|
|
||||||
作者：[Patrick H.Mullins][a]
|
|
||||||
选题：[lujun9972](https://github.com/lujun9972)
|
|
||||||
译者：[译者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/pmullins
|
|
||||||
[1]:https://wiki.debian.org/Apt
|
|
||||||
[2]:https://access.redhat.com/articles/yum-cheat-sheet
|
|
||||||
[3]:https://fedoraproject.org/wiki/DNF?rd=Dnf
|
|
||||||
@ -1,3 +1,5 @@
|
|||||||
|
pinewall translating
|
||||||
|
|
||||||
Add GUIs to your programs and scripts easily with PySimpleGUI
|
Add GUIs to your programs and scripts easily with PySimpleGUI
|
||||||
======
|
======
|
||||||
|
|
||||||
|
|||||||
@ -0,0 +1,68 @@
|
|||||||
|
How to Create a Slideshow of Photos in Ubuntu 18.04 and other Linux Distributions
|
||||||
|
======
|
||||||
|
Creating a slideshow of photos is a matter of a few clicks. Here’s how to make a slideshow of pictures in Ubuntu 18.04 and other Linux distributions.
|
||||||
|
|
||||||
|
![How to create slideshow of photos in Ubuntu Linux][1]
|
||||||
|
|
||||||
|
Imagine yourself in a situation where your friends and family are visiting you and request you to show the pictures of a recent event/trip.
|
||||||
|
|
||||||
|
You have the photos saved on your computers, neatly in a separate folder. You invite everyone near the computer. You go to the folder, click on one of the pictures and start showing them the photos one by one by pressing the arrow keys.
|
||||||
|
|
||||||
|
But that’s tiring! It will be a lot better if those images get changed automatically every few seconds.
|
||||||
|
|
||||||
|
That’s called a slideshow and I am going to show you how to create a slideshow of photos in Ubuntu. This will allow you to loop pictures from a folder and display them in fullscreen mode.
|
||||||
|
|
||||||
|
### Creating photo slideshow in Ubuntu 18.04 and other Linux distributions
|
||||||
|
|
||||||
|
While you could use several image viewers for this purpose, I am going to show you two of the most popular tools that should be available in most distributions.
|
||||||
|
|
||||||
|
#### Method 1: Photo slideshow with GNOME’s default image viewer
|
||||||
|
|
||||||
|
If you are using GNOME in Ubuntu 18.04 or any other distribution, you are in luck. The default image viewer of Gnome, Eye of GNOME, is well capable of displaying the slideshow of pictures in the current folder.
|
||||||
|
|
||||||
|
Just click on one of the pictures and you’ll see the settings option on the top right side of the application menu. It looks like three bars stacked over the top of one another.
|
||||||
|
|
||||||
|
You’ll see several options here. Check the Slideshow box and it will go fullscreen displaying the images.
|
||||||
|
|
||||||
|
![How to create slideshow of photos in Ubuntu Linux][2]
|
||||||
|
|
||||||
|
By default, the images change at an interval of 5 seconds. You can change the slideshow interval by going to the Preferences->Slideshow.
|
||||||
|
|
||||||
|
![change slideshow interval in Ubuntu][3]Changing slideshow interval
|
||||||
|
|
||||||
|
#### Method 2: Photo slideshow with Shotwell Photo Manager
|
||||||
|
|
||||||
|
[Shotwell][4] is a popular [photo management application for Linux][5]. and available for all major Linux distributions.
|
||||||
|
|
||||||
|
If it is not installed already, search for Shotwell in your distribution’s software center and install it.
|
||||||
|
|
||||||
|
Shotwell works slightly different. If you directly open a photo in Shotwell Viewer, you won’t see preferences or options for a slideshow.
|
||||||
|
|
||||||
|
For slideshow and other options, you have to open Shotwell and import the folders containing those pictures. Once you have imported the folder in here, select that folder from left side-pane and then click on View in the menu. You should see the option of Slideshow here. Just click on it to create the slideshow of all the images in the selected folder.
|
||||||
|
|
||||||
|
![How to create slideshow of photos in Ubuntu Linux][6]
|
||||||
|
|
||||||
|
You can also change the slideshow settings. This option is presented when the images are displayed in the full view. Just hover the mouse to the lower bottom and you’ll see a settings option appearing.
|
||||||
|
|
||||||
|
#### It’s easy to create photo slideshow
|
||||||
|
|
||||||
|
As you can see, it’s really simple to create slideshow of photos in Linux. I hope you find this simple tip useful. If you have questions or suggestions, please let me know in the comment section below.
|
||||||
|
|
||||||
|
--------------------------------------------------------------------------------
|
||||||
|
|
||||||
|
via: https://itsfoss.com/photo-slideshow-ubuntu/
|
||||||
|
|
||||||
|
作者：[Abhishek Prakash][a]
|
||||||
|
选题：[lujun9972](https://github.com/lujun9972)
|
||||||
|
译者：[译者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/
|
||||||
|
[1]: https://4bds6hergc-flywheel.netdna-ssl.com/wp-content/uploads/2018/08/Create-photos-Slideshow-Linux.png
|
||||||
|
[2]: https://4bds6hergc-flywheel.netdna-ssl.com/wp-content/uploads/2018/08/create-slideshow-photos-ubuntu-gnome.jpeg
|
||||||
|
[3]: https://4bds6hergc-flywheel.netdna-ssl.com/wp-content/uploads/2018/08/change-slideshow-interval-gnome-image.jpeg
|
||||||
|
[4]: https://wiki.gnome.org/Apps/Shotwell
|
||||||
|
[5]: https://itsfoss.com/linux-photo-management-software/
|
||||||
|
[6]: https://4bds6hergc-flywheel.netdna-ssl.com/wp-content/uploads/2018/08/create-slideshow-photos-shotwell.jpeg
|
||||||
@ -0,0 +1,268 @@
|
|||||||
|
8 Linux commands for effective process management
|
||||||
|
======
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
Generally, an application process' lifecycle has three main states: start, run, and stop. Each state can and should be managed carefully if we want to be competent administrators. These eight commands can be used to manage processes through their lifecycles.
|
||||||
|
|
||||||
|
### Starting a process
|
||||||
|
|
||||||
|
The easiest way to start a process is to type its name at the command line and press Enter. If you want to start an Nginx web server, type **nginx**. Perhaps you just want to check the version.
|
||||||
|
```
|
||||||
|
alan@workstation:~$ nginx
|
||||||
|
|
||||||
|
alan@workstation:~$ nginx -v
|
||||||
|
nginx version: nginx/1.14.0
|
||||||
|
```
|
||||||
|
|
||||||
|
### Viewing your executable path
|
||||||
|
|
||||||
|
The above demonstration of starting a process assumes the executable file is located in your executable path. Understanding this path is key to reliably starting and managing a process. Administrators often customize this path for their desired purpose. You can view your executable path using **echo $PATH**.
|
||||||
|
```
|
||||||
|
alan@workstation:~$ echo $PATH
|
||||||
|
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin
|
||||||
|
```
|
||||||
|
|
||||||
|
#### WHICH
|
||||||
|
|
||||||
|
Use the which command to view the full path of an executable file.
|
||||||
|
```
|
||||||
|
alan@workstation:~$ which nginx
|
||||||
|
/opt/nginx/bin/nginx
|
||||||
|
```
|
||||||
|
|
||||||
|
I will use the popular web server software Nginx for my examples. Let's assume that Nginx is installed. If the command **which nginx** returns nothing, then Nginx was not found because which searches only your defined executable path. There are three ways to remedy a situation where a process cannot be started simply by name. The first is to type the full path. Although, I'd rather not have to type all of that, would you?
|
||||||
|
```
|
||||||
|
alan@workstation:~$ /home/alan/web/prod/nginx/sbin/nginx -v
|
||||||
|
nginx version: nginx/1.14.0
|
||||||
|
```
|
||||||
|
|
||||||
|
The second solution would be to install the application in a directory in your executable's path. However, this may not be possible, particularly if you don't have root privileges.
|
||||||
|
|
||||||
|
The third solution is to update your executable path environment variable to include the directory where the specific application you want to use is installed. This solution is shell-dependent. For example, Bash users would need to edit the PATH= line in their .bashrc file.
|
||||||
|
```
|
||||||
|
PATH="$HOME/web/prod/nginx/sbin:$PATH"
|
||||||
|
```
|
||||||
|
|
||||||
|
Now, repeat your echo and which commands or try to check the version. Much easier!
|
||||||
|
```
|
||||||
|
alan@workstation:~$ echo $PATH
|
||||||
|
/home/alan/web/prod/nginx/sbin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin
|
||||||
|
|
||||||
|
alan@workstation:~$ which nginx
|
||||||
|
/home/alan/web/prod/nginx/sbin/nginx
|
||||||
|
|
||||||
|
alan@workstation:~$ nginx -v
|
||||||
|
nginx version: nginx/1.14.0
|
||||||
|
```
|
||||||
|
|
||||||
|
### Keeping a process running
|
||||||
|
|
||||||
|
#### NOHUP
|
||||||
|
|
||||||
|
A process may not continue to run when you log out or close your terminal. This special case can be avoided by preceding the command you want to run with the nohup command. Also, appending an ampersand (&) will send the process to the background and allow you to continue using the terminal. For example, suppose you want to run myprogram.sh.
|
||||||
|
```
|
||||||
|
nohup myprogram.sh &
|
||||||
|
```
|
||||||
|
|
||||||
|
One nice thing nohup does is return the running process's PID. I'll talk more about the PID next.
|
||||||
|
|
||||||
|
### Manage a running process
|
||||||
|
|
||||||
|
Each process is given a unique process identification number (PID). This number is what we use to manage each process. We can also use the process name, as I'll demonstrate below. There are several commands that can check the status of a running process. Let's take a quick look at these.
|
||||||
|
|
||||||
|
#### PS
|
||||||
|
|
||||||
|
The most common is ps. The default output of ps is a simple list of the processes running in your current terminal. As you can see below, the first column contains the PID.
|
||||||
|
```
|
||||||
|
alan@workstation:~$ ps
|
||||||
|
PID TTY TIME CMD
|
||||||
|
23989 pts/0 00:00:00 bash
|
||||||
|
24148 pts/0 00:00:00 ps
|
||||||
|
```
|
||||||
|
|
||||||
|
I'd like to view the Nginx process I started earlier. To do this, I tell ps to show me every running process ( **-e** ) and a full listing ( **-f** ).
|
||||||
|
```
|
||||||
|
alan@workstation:~$ ps -ef
|
||||||
|
UID PID PPID C STIME TTY TIME CMD
|
||||||
|
root 1 0 0 Aug18 ? 00:00:10 /sbin/init splash
|
||||||
|
root 2 0 0 Aug18 ? 00:00:00 [kthreadd]
|
||||||
|
root 4 2 0 Aug18 ? 00:00:00 [kworker/0:0H]
|
||||||
|
root 6 2 0 Aug18 ? 00:00:00 [mm_percpu_wq]
|
||||||
|
root 7 2 0 Aug18 ? 00:00:00 [ksoftirqd/0]
|
||||||
|
root 8 2 0 Aug18 ? 00:00:20 [rcu_sched]
|
||||||
|
root 9 2 0 Aug18 ? 00:00:00 [rcu_bh]
|
||||||
|
root 10 2 0 Aug18 ? 00:00:00 [migration/0]
|
||||||
|
root 11 2 0 Aug18 ? 00:00:00 [watchdog/0]
|
||||||
|
root 12 2 0 Aug18 ? 00:00:00 [cpuhp/0]
|
||||||
|
root 13 2 0 Aug18 ? 00:00:00 [cpuhp/1]
|
||||||
|
root 14 2 0 Aug18 ? 00:00:00 [watchdog/1]
|
||||||
|
root 15 2 0 Aug18 ? 00:00:00 [migration/1]
|
||||||
|
root 16 2 0 Aug18 ? 00:00:00 [ksoftirqd/1]
|
||||||
|
alan 20506 20496 0 10:39 pts/0 00:00:00 bash
|
||||||
|
alan 20520 1454 0 10:39 ? 00:00:00 nginx: master process nginx
|
||||||
|
alan 20521 20520 0 10:39 ? 00:00:00 nginx: worker process
|
||||||
|
alan 20526 20506 0 10:39 pts/0 00:00:00 man ps
|
||||||
|
alan 20536 20526 0 10:39 pts/0 00:00:00 pager
|
||||||
|
alan 20564 20496 0 10:40 pts/1 00:00:00 bash
|
||||||
|
```
|
||||||
|
|
||||||
|
You can see the Nginx processes in the output of the ps command above. The command displayed almost 300 lines, but I shortened it for this illustration. As you can imagine, trying to handle 300 lines of process information is a bit messy. We can pipe this output to grep to filter out nginx.
|
||||||
|
```
|
||||||
|
alan@workstation:~$ ps -ef |grep nginx
|
||||||
|
alan 20520 1454 0 10:39 ? 00:00:00 nginx: master process nginx
|
||||||
|
alan 20521 20520 0 10:39 ? 00:00:00 nginx: worker process
|
||||||
|
```
|
||||||
|
|
||||||
|
That's better. We can quickly see that Nginx has PIDs of 20520 and 20521.
|
||||||
|
|
||||||
|
#### PGREP
|
||||||
|
|
||||||
|
The pgrep command was created to further simplify things by removing the need to call grep separately.
|
||||||
|
```
|
||||||
|
alan@workstation:~$ pgrep nginx
|
||||||
|
20520
|
||||||
|
20521
|
||||||
|
```
|
||||||
|
|
||||||
|
Suppose you are in a hosting environment where multiple users are running several different instances of Nginx. You can exclude others from the output with the **-u** option.
|
||||||
|
```
|
||||||
|
alan@workstation:~$ pgrep -u alan nginx
|
||||||
|
20520
|
||||||
|
20521
|
||||||
|
```
|
||||||
|
|
||||||
|
#### PIDOF
|
||||||
|
|
||||||
|
Another nifty one is pidof. This command will check the PID of a specific binary even if another process with the same name is running. To set up an example, I copied my Nginx to a second directory and started it with the prefix set accordingly. In real life, this instance could be in a different location, such as a directory owned by a different user. If I run both Nginx instances, the **ps -ef** output shows all their processes.
|
||||||
|
```
|
||||||
|
alan@workstation:~$ ps -ef |grep nginx
|
||||||
|
alan 20881 1454 0 11:18 ? 00:00:00 nginx: master process ./nginx -p /home/alan/web/prod/nginxsec
|
||||||
|
alan 20882 20881 0 11:18 ? 00:00:00 nginx: worker process
|
||||||
|
alan 20895 1454 0 11:19 ? 00:00:00 nginx: master process nginx
|
||||||
|
alan 20896 20895 0 11:19 ? 00:00:00 nginx: worker process
|
||||||
|
```
|
||||||
|
|
||||||
|
Using grep or pgrep will show PID numbers, but we may not be able to discern which instance is which.
|
||||||
|
```
|
||||||
|
alan@workstation:~$ pgrep nginx
|
||||||
|
20881
|
||||||
|
20882
|
||||||
|
20895
|
||||||
|
20896
|
||||||
|
```
|
||||||
|
|
||||||
|
The pidof command can be used to determine the PID of each specific Nginx instance.
|
||||||
|
```
|
||||||
|
alan@workstation:~$ pidof /home/alan/web/prod/nginxsec/sbin/nginx
|
||||||
|
20882 20881
|
||||||
|
|
||||||
|
alan@workstation:~$ pidof /home/alan/web/prod/nginx/sbin/nginx
|
||||||
|
20896 20895
|
||||||
|
```
|
||||||
|
|
||||||
|
#### TOP
|
||||||
|
|
||||||
|
The top command has been around a long time and is very useful for viewing details of running processes and quickly identifying issues such as memory hogs. Its default view is shown below.
|
||||||
|
```
|
||||||
|
top - 11:56:28 up 1 day, 13:37, 1 user, load average: 0.09, 0.04, 0.03
|
||||||
|
Tasks: 292 total, 3 running, 225 sleeping, 0 stopped, 0 zombie
|
||||||
|
%Cpu(s): 0.1 us, 0.2 sy, 0.0 ni, 99.7 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st
|
||||||
|
KiB Mem : 16387132 total, 10854648 free, 1859036 used, 3673448 buff/cache
|
||||||
|
KiB Swap: 0 total, 0 free, 0 used. 14176540 avail Mem
|
||||||
|
|
||||||
|
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
|
||||||
|
17270 alan 20 0 3930764 247288 98992 R 0.7 1.5 5:58.22 gnome-shell
|
||||||
|
20496 alan 20 0 816144 45416 29844 S 0.5 0.3 0:22.16 gnome-terminal-
|
||||||
|
21110 alan 20 0 41940 3988 3188 R 0.1 0.0 0:00.17 top
|
||||||
|
1 root 20 0 225564 9416 6768 S 0.0 0.1 0:10.72 systemd
|
||||||
|
2 root 20 0 0 0 0 S 0.0 0.0 0:00.01 kthreadd
|
||||||
|
4 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 kworker/0:0H
|
||||||
|
6 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 mm_percpu_wq
|
||||||
|
7 root 20 0 0 0 0 S 0.0 0.0 0:00.08 ksoftirqd/0
|
||||||
|
```
|
||||||
|
|
||||||
|
The update interval can be changed by typing the letter **s** followed by the number of seconds you prefer for updates. To make it easier to monitor our example Nginx processes, we can call top and pass the PID(s) using the **-p** option. This output is much cleaner.
|
||||||
|
```
|
||||||
|
alan@workstation:~$ top -p20881 -p20882 -p20895 -p20896
|
||||||
|
|
||||||
|
Tasks: 4 total, 0 running, 4 sleeping, 0 stopped, 0 zombie
|
||||||
|
%Cpu(s): 2.8 us, 1.3 sy, 0.0 ni, 95.9 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st
|
||||||
|
KiB Mem : 16387132 total, 10856008 free, 1857648 used, 3673476 buff/cache
|
||||||
|
KiB Swap: 0 total, 0 free, 0 used. 14177928 avail Mem
|
||||||
|
|
||||||
|
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
|
||||||
|
20881 alan 20 0 12016 348 0 S 0.0 0.0 0:00.00 nginx
|
||||||
|
20882 alan 20 0 12460 1644 932 S 0.0 0.0 0:00.00 nginx
|
||||||
|
20895 alan 20 0 12016 352 0 S 0.0 0.0 0:00.00 nginx
|
||||||
|
20896 alan 20 0 12460 1628 912 S 0.0 0.0 0:00.00 nginx
|
||||||
|
```
|
||||||
|
|
||||||
|
It is important to correctly determine the PID when managing processes, particularly stopping one. Also, if using top in this manner, any time one of these processes is stopped or a new one is started, top will need to be informed of the new ones.
|
||||||
|
|
||||||
|
### Stopping a process
|
||||||
|
|
||||||
|
#### KILL
|
||||||
|
|
||||||
|
Interestingly, there is no stop command. In Linux, there is the kill command. Kill is used to send a signal to a process. The most commonly used signal is "terminate" (SIGTERM) or "kill" (SIGKILL). However, there are many more. Below are some examples. The full list can be shown with **kill -L**.
|
||||||
|
```
|
||||||
|
1) SIGHUP 2) SIGINT 3) SIGQUIT 4) SIGILL 5) SIGTRAP
|
||||||
|
6) SIGABRT 7) SIGBUS 8) SIGFPE 9) SIGKILL 10) SIGUSR1
|
||||||
|
11) SIGSEGV 12) SIGUSR2 13) SIGPIPE 14) SIGALRM 15) SIGTERM
|
||||||
|
|
||||||
|
```
|
||||||
|
|
||||||
|
Notice signal number nine is SIGKILL. Usually, we issue a command such as **kill -9 20896**. The default signal is 15, which is SIGTERM. Keep in mind that many applications have their own method for stopping. Nginx uses a **-s** option for passing a signal such as "stop" or "reload." Generally, I prefer to use an application's specific method to stop an operation. However, I'll demonstrate the kill command to stop Nginx process 20896 and then confirm it is stopped with pgrep. The PID 20896 no longer appears.
|
||||||
|
```
|
||||||
|
alan@workstation:~$ kill -9 20896
|
||||||
|
|
||||||
|
alan@workstation:~$ pgrep nginx
|
||||||
|
20881
|
||||||
|
20882
|
||||||
|
20895
|
||||||
|
22123
|
||||||
|
```
|
||||||
|
|
||||||
|
#### PKILL
|
||||||
|
|
||||||
|
The command pkill is similar to pgrep in that it can search by name. This means you have to be very careful when using pkill. In my example with Nginx, I might not choose to use it if I only want to kill one Nginx instance. I can pass the Nginx option **-s** **stop** to a specific instance to kill it, or I need to use grep to filter on the full ps output.
|
||||||
|
```
|
||||||
|
/home/alan/web/prod/nginx/sbin/nginx -s stop
|
||||||
|
|
||||||
|
/home/alan/web/prod/nginxsec/sbin/nginx -s stop
|
||||||
|
```
|
||||||
|
|
||||||
|
If I want to use pkill, I can include the **-f** option to ask pkill to filter across the full command line argument. This of course also applies to pgrep. So, first I can check with **pgrep -a** before issuing the **pkill -f**.
|
||||||
|
```
|
||||||
|
alan@workstation:~$ pgrep -a nginx
|
||||||
|
20881 nginx: master process ./nginx -p /home/alan/web/prod/nginxsec
|
||||||
|
20882 nginx: worker process
|
||||||
|
20895 nginx: master process nginx
|
||||||
|
20896 nginx: worker process
|
||||||
|
```
|
||||||
|
|
||||||
|
I can also narrow down my result with **pgrep -f**. The same argument used with pkill stops the process.
|
||||||
|
```
|
||||||
|
alan@workstation:~$ pgrep -f nginxsec
|
||||||
|
20881
|
||||||
|
|
||||||
|
alan@workstation:~$ pkill -f nginxsec
|
||||||
|
```
|
||||||
|
|
||||||
|
The key thing to remember with pgrep (and especially pkill) is that you must always be sure that your search result is accurate so you aren't unintentionally affecting the wrong processes.
|
||||||
|
|
||||||
|
Most of these commands have many command line options, so I always recommend reading the [man page][1] on each one. While most of these exist across platforms such as Linux, Solaris, and BSD, there are a few differences. Always test and be ready to correct as needed when working at the command line or writing scripts.
|
||||||
|
|
||||||
|
--------------------------------------------------------------------------------
|
||||||
|
|
||||||
|
via: https://opensource.com/article/18/9/linux-commands-process-management
|
||||||
|
|
||||||
|
作者：[Alan Formy-Duval][a]
|
||||||
|
选题：[lujun9972](https://github.com/lujun9972)
|
||||||
|
译者：[译者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/alanfdoss
|
||||||
|
[1]: https://www.kernel.org/doc/man-pages/
|
||||||
@ -1,3 +1,5 @@
|
|||||||
|
translating---geekpi
|
||||||
|
|
||||||
Why I love Xonsh
|
Why I love Xonsh
|
||||||
======
|
======
|
||||||
|
|
||||||
|
|||||||
290
sources/tech/20180905 5 tips to improve productivity with zsh.md
Normal file
290
sources/tech/20180905 5 tips to improve productivity with zsh.md
Normal file
@ -0,0 +1,290 @@
|
|||||||
|
5 tips to improve productivity with zsh
|
||||||
|
======
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
The Z shell known as [zsh][1] is a [shell][2] for Linux/Unix-like operating systems. It has similarities to other shells in the `sh` (Bourne shell) family, such as as `bash` and `ksh`, but it provides many advanced features and powerful command line editing options, such as enhanced Tab completion.
|
||||||
|
|
||||||
|
It would be impossible to cover all the options of zsh here; there are literally hundreds of pages [documenting][3] its many features. In this article, I'll present five tips to make you more productive using the command line with zsh.
|
||||||
|
|
||||||
|
### 1\. Themes and plugins
|
||||||
|
|
||||||
|
Through the years, the open source community has developed countless themes and plugins for zsh. A theme is a predefined prompt configuration, while a plugin is a set of useful aliases and functions that make it easier to use a specific command or programming language.
|
||||||
|
|
||||||
|
The quickest way to get started using themes and plugins is to use a zsh configuration framework. There are many available, but the most popular is [Oh My Zsh][4]. By default, it enables some sensible zsh configuration options and it comes loaded with hundreds of themes and plugins.
|
||||||
|
|
||||||
|
A theme makes you more productive as it adds useful information to your prompt, such as the status of your Git repository or Python virtualenv in use. Having this information at a glance saves you from typing the equivalent commands to obtain it, and it's a cool look. Here's an example of [Powerlevel9k][5], my theme of choice:
|
||||||
|
|
||||||
|
![zsh Powerlevel9K theme][7]
|
||||||
|
|
||||||
|
The Powerlevel9k theme for zsh
|
||||||
|
|
||||||
|
In addition to themes, Oh My Zsh bundles tons of useful plugins for zsh. For example, enabling the Git plugin gives you access to a number of useful aliases, such as:
|
||||||
|
```
|
||||||
|
$ alias | grep -i git | sort -R | head -10
|
||||||
|
g=git
|
||||||
|
ga='git add'
|
||||||
|
gapa='git add --patch'
|
||||||
|
gap='git apply'
|
||||||
|
gdt='git diff-tree --no-commit-id --name-only -r'
|
||||||
|
gau='git add --update'
|
||||||
|
gstp='git stash pop'
|
||||||
|
gbda='git branch --no-color --merged | command grep -vE "^(\*|\s*(master|develop|dev)\s*$)" | command xargs -n 1 git branch -d'
|
||||||
|
gcs='git commit -S'
|
||||||
|
glg='git log --stat'
|
||||||
|
```
|
||||||
|
|
||||||
|
There are plugins available for many programming languages, packaging systems, and other tools you commonly use on the command line. Here's a list of plugins I use in my Fedora workstation:
|
||||||
|
```
|
||||||
|
git golang fedora docker oc sudo vi-mode virtualenvwrapper
|
||||||
|
```
|
||||||
|
|
||||||
|
### 2\. Clever aliases
|
||||||
|
|
||||||
|
Aliases are very useful in zsh. Defining aliases for your most-used commands saves you a lot of typing. Oh My Zsh configures several useful aliases by default, including aliases to navigate directories and replacements for common commands with additional options such as:
|
||||||
|
```
|
||||||
|
ls='ls --color=tty'
|
||||||
|
grep='grep --color=auto --exclude-dir={.bzr,CVS,.git,.hg,.svn}'
|
||||||
|
```
|
||||||
|
|
||||||
|
In addition to command aliases, zsh enables two additional useful alias types: the suffix alias and the global alias.
|
||||||
|
|
||||||
|
A suffix alias allows you to open the file you type in the command line using the specified program based on the file extension. For example, to open YAML files using vim, define the following alias:
|
||||||
|
```
|
||||||
|
alias -s {yml,yaml}=vim
|
||||||
|
```
|
||||||
|
|
||||||
|
Now if you type any file name ending with `yml` or `yaml` in the command line, zsh opens that file using vim:
|
||||||
|
```
|
||||||
|
$ playbook.yml
|
||||||
|
# Opens file playbook.yml using vim
|
||||||
|
```
|
||||||
|
|
||||||
|
A global alias enables you to create an alias that is expanded anywhere in the command line, not just at the beginning. This is very useful to replace common filenames or piped commands. For example:
|
||||||
|
```
|
||||||
|
alias -g G='| grep -i'
|
||||||
|
```
|
||||||
|
|
||||||
|
To use this alias, type `G` anywhere you would type the piped command:
|
||||||
|
```
|
||||||
|
$ ls -l G do
|
||||||
|
drwxr-xr-x. 5 rgerardi rgerardi 4096 Aug 7 14:08 Documents
|
||||||
|
drwxr-xr-x. 6 rgerardi rgerardi 4096 Aug 24 14:51 Downloads
|
||||||
|
```
|
||||||
|
|
||||||
|
Next, let's see how zsh helps to navigate the filesystem.
|
||||||
|
|
||||||
|
### 3\. Easy directory navigation
|
||||||
|
|
||||||
|
When you're using the command line, navigating across different directories is one of the most common tasks. Zsh makes this easier by providing some useful directory navigation features. These features are enabled with Oh My Zsh, but you can enable them by using this command:
|
||||||
|
```
|
||||||
|
setopt autocd autopushd \ pushdignoredups
|
||||||
|
```
|
||||||
|
|
||||||
|
With these options set, you don't need to type `cd` to change directories. Just type the directory name, and zsh switches to it:
|
||||||
|
```
|
||||||
|
$ pwd
|
||||||
|
/home/rgerardi
|
||||||
|
$ /tmp
|
||||||
|
$ pwd
|
||||||
|
/tmp
|
||||||
|
```
|
||||||
|
|
||||||
|
To move back, type `-`:
|
||||||
|
|
||||||
|
Zsh keeps the history of directories you visited so you can quickly switch to any of them. To see the list, type `dirs -v`:
|
||||||
|
```
|
||||||
|
$ dirs -v
|
||||||
|
0 ~
|
||||||
|
1 /var/log
|
||||||
|
2 /var/opt
|
||||||
|
3 /usr/bin
|
||||||
|
4 /usr/local
|
||||||
|
5 /usr/lib
|
||||||
|
6 /tmp
|
||||||
|
7 ~/Projects/Opensource.com/zsh-5tips
|
||||||
|
8 ~/Projects
|
||||||
|
9 ~/Projects/ansible
|
||||||
|
10 ~/Documents
|
||||||
|
```
|
||||||
|
|
||||||
|
Switch to any directory in this list by typing `~#` where # is the number of the directory in the list. For example:
|
||||||
|
```
|
||||||
|
$ pwd
|
||||||
|
/home/rgerardi
|
||||||
|
$ ~4
|
||||||
|
$ pwd
|
||||||
|
/usr/local
|
||||||
|
```
|
||||||
|
|
||||||
|
Combine these with aliases to make it even easier to navigate:
|
||||||
|
```
|
||||||
|
d='dirs -v | head -10'
|
||||||
|
1='cd -'
|
||||||
|
2='cd -2'
|
||||||
|
3='cd -3'
|
||||||
|
4='cd -4'
|
||||||
|
5='cd -5'
|
||||||
|
6='cd -6'
|
||||||
|
7='cd -7'
|
||||||
|
8='cd -8'
|
||||||
|
9='cd -9'
|
||||||
|
```
|
||||||
|
|
||||||
|
Now you can type `d` to see the first ten items in the list and the number to switch to it:
|
||||||
|
```
|
||||||
|
$ d
|
||||||
|
0 /usr/local
|
||||||
|
1 ~
|
||||||
|
2 /var/log
|
||||||
|
3 /var/opt
|
||||||
|
4 /usr/bin
|
||||||
|
5 /usr/lib
|
||||||
|
6 /tmp
|
||||||
|
7 ~/Projects/Opensource.com/zsh-5tips
|
||||||
|
8 ~/Projects
|
||||||
|
9 ~/Projects/ansible
|
||||||
|
$ pwd
|
||||||
|
/usr/local
|
||||||
|
$ 6
|
||||||
|
/tmp
|
||||||
|
$ pwd
|
||||||
|
/tmp
|
||||||
|
```
|
||||||
|
|
||||||
|
Finally, zsh automatically expands directory names with Tab completion. Type the first letters of the directory names and `TAB` to use it:
|
||||||
|
```
|
||||||
|
$ pwd
|
||||||
|
/home/rgerardi
|
||||||
|
$ p/o/z (TAB)
|
||||||
|
$ Projects/Opensource.com/zsh-5tips/
|
||||||
|
```
|
||||||
|
|
||||||
|
This is just one of the features enabled by zsh's powerful Tab completion system. Let's look at some more.
|
||||||
|
|
||||||
|
### 4\. Advanced Tab completion
|
||||||
|
|
||||||
|
Zsh's powerful completion system is one of its hallmarks. For simplification, I call it Tab completion, but under the hood, more than one thing is happening. There's usually expansion and command completion. I'll discuss them together here. For details, check this [User's Guide][8].
|
||||||
|
|
||||||
|
Command completion is enabled by default with Oh My Zsh. To enable it, add the following lines to your `.zshrc` file:
|
||||||
|
```
|
||||||
|
autoload -U compinit
|
||||||
|
compinit
|
||||||
|
```
|
||||||
|
|
||||||
|
Zsh's completion system is smart. It tries to suggest only items that can be used in certain contexts—for example, if you type `cd` and `TAB`, zsh suggests only directory names as it knows `cd` does not work with anything else.
|
||||||
|
|
||||||
|
Conversely, it suggests usernames when running user-related commands or hostnames when using `ssh` or `ping`, for example.
|
||||||
|
|
||||||
|
It has a vast completion library and understands many different commands. For example, if you're using the `tar` command, you can press Tab to see a list of files available in the package as candidates for extraction:
|
||||||
|
```
|
||||||
|
$ tar -xzvf test1.tar.gz test1/file1 (TAB)
|
||||||
|
file1 file2
|
||||||
|
```
|
||||||
|
|
||||||
|
Here's a more advanced example, using `git`. In this example, when typing `TAB`, zsh automatically completes the name of the only file in the repository that can be staged:
|
||||||
|
```
|
||||||
|
$ ls
|
||||||
|
original plan.txt zsh-5tips.md zsh_theme_small.png
|
||||||
|
$ git status
|
||||||
|
On branch master
|
||||||
|
Your branch is up to date with 'origin/master'.
|
||||||
|
|
||||||
|
Changes not staged for commit:
|
||||||
|
(use "git add <file>..." to update what will be committed)
|
||||||
|
(use "git checkout -- <file>..." to discard changes in working directory)
|
||||||
|
|
||||||
|
modified: zsh-5tips.md
|
||||||
|
|
||||||
|
no changes added to commit (use "git add" and/or "git commit -a")
|
||||||
|
$ git add (TAB)
|
||||||
|
$ git add zsh-5tips.md
|
||||||
|
```
|
||||||
|
|
||||||
|
It also understands command line options and suggests only the ones that are relevant to the subcommand selected:
|
||||||
|
```
|
||||||
|
$ git commit - (TAB)
|
||||||
|
--all -a -- stage all modified and deleted paths
|
||||||
|
--allow-empty -- allow recording an empty commit
|
||||||
|
--allow-empty-message -- allow recording a commit with an empty message
|
||||||
|
--amend -- amend the tip of the current branch
|
||||||
|
--author -- override the author name used in the commit
|
||||||
|
--branch -- show branch information
|
||||||
|
--cleanup -- specify how the commit message should be cleaned up
|
||||||
|
--date -- override the author date used in the commit
|
||||||
|
--dry-run -- only show the list of paths that are to be committed or not, and any untracked
|
||||||
|
--edit -e -- edit the commit message before committing
|
||||||
|
--file -F -- read commit message from given file
|
||||||
|
--gpg-sign -S -- GPG-sign the commit
|
||||||
|
--include -i -- update the given files and commit the whole index
|
||||||
|
--interactive -- interactively update paths in the index file
|
||||||
|
--message -m -- use the given message as the commit message
|
||||||
|
... TRUNCATED ...
|
||||||
|
```
|
||||||
|
|
||||||
|
After typing `TAB`, you can use the arrow keys to navigate the options list and select the one you need. Now you don't need to memorize all those Git options.
|
||||||
|
|
||||||
|
There are many options available. The best way to find what is most helpful to you is by using it.
|
||||||
|
|
||||||
|
### 5\. Command line editing and history
|
||||||
|
|
||||||
|
Zsh's command line editing capabilities are also useful. By default, it emulates emacs. If, like me, you prefer vi/vim, enable vi bindings with the following command:
|
||||||
|
```
|
||||||
|
$ bindkey -v
|
||||||
|
```
|
||||||
|
|
||||||
|
If you're using Oh My Zsh, the `vi-mode` plugin enables additional bindings and a mode indicator on your prompt—very useful.
|
||||||
|
|
||||||
|
After enabling vi bindings, you can edit the command line using vi commands. For example, press `ESC+/` to search the command line history. While searching, pressing `n` brings the next matching line, and `N` the previous one. Most common vi commands work after pressing `ESC` such as `0` to jump to the start of the line, `$` to jump to the end, `i` to insert, `a` to append, etc. Even commands followed by motion work, such as `cw` to change a word.
|
||||||
|
|
||||||
|
In addition to command line editing, zsh provides several useful command line history features if you want to fix or re-execute previous used commands. For example, if you made a mistake, typing `fc` brings the last command in your favorite editor to fix it. It respects the `$EDITOR` variable and by default uses vi.
|
||||||
|
|
||||||
|
Another useful command is `r`, which re-executes the last command; and `r <WORD>`, which executes the last command that contains the string `WORD`.
|
||||||
|
|
||||||
|
Finally, typing double bangs (`!!`) brings back the last command anywhere in the line. This is useful, for instance, if you forgot to type `sudo` to execute commands that require elevated privileges:
|
||||||
|
```
|
||||||
|
$ less /var/log/dnf.log
|
||||||
|
/var/log/dnf.log: Permission denied
|
||||||
|
$ sudo !!
|
||||||
|
$ sudo less /var/log/dnf.log
|
||||||
|
```
|
||||||
|
|
||||||
|
These features make it easier to find and re-use previously typed commands.
|
||||||
|
|
||||||
|
### Where to go from here?
|
||||||
|
|
||||||
|
These are just a few of the zsh features that can make you more productive; there are many more. For additional information, consult the following resources:
|
||||||
|
|
||||||
|
[An Introduction to the Z Shell][9]
|
||||||
|
|
||||||
|
[A User's Guide to ZSH][10]
|
||||||
|
|
||||||
|
[Archlinux Wiki][11]
|
||||||
|
|
||||||
|
[zsh-lovers][12]
|
||||||
|
|
||||||
|
Do you have any zsh productivity tips to share? I would love to hear about them in the comments below.
|
||||||
|
|
||||||
|
--------------------------------------------------------------------------------
|
||||||
|
|
||||||
|
via: https://opensource.com/article/18/9/tips-productivity-zsh
|
||||||
|
|
||||||
|
作者：[Ricardo Gerardi][a]
|
||||||
|
选题：[lujun9972](https://github.com/lujun9972)
|
||||||
|
译者：[译者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/rgerardi
|
||||||
|
[1]: http://www.zsh.org/
|
||||||
|
[2]: https://en.wikipedia.org/wiki/Shell_(computing)
|
||||||
|
[3]: http://zsh.sourceforge.net/Doc/Release/zsh_toc.html
|
||||||
|
[4]: https://ohmyz.sh/
|
||||||
|
[5]: https://github.com/bhilburn/powerlevel9k
|
||||||
|
[7]: https://opensource.com/sites/default/files/uploads/zsh_theme_small.png (zsh Powerlevel9K theme)
|
||||||
|
[8]: http://zsh.sourceforge.net/Guide/zshguide06.html#l144
|
||||||
|
[9]: http://zsh.sourceforge.net/Intro/intro_toc.html
|
||||||
|
[10]: http://zsh.sourceforge.net/Guide/
|
||||||
|
[11]: https://wiki.archlinux.org/index.php/zsh
|
||||||
|
[12]: https://grml.org/zsh/
|
||||||
@ -0,0 +1,66 @@
|
|||||||
|
8 great Python libraries for side projects
|
||||||
|
======
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
We have a saying in the Python/Django world: We came for the language and stayed for the community. That is true for most of us, but something else that has kept us in the Python world is how easy it is to have an idea and quickly work through it over lunch or in a few hours at night.
|
||||||
|
|
||||||
|
This month we're diving into Python libraries we love to use to quickly scratch those side-project or lunchtime itches.
|
||||||
|
|
||||||
|
### To save data in a database on the fly: Dataset
|
||||||
|
|
||||||
|
[Dataset][1] is our go-to library when we quickly want to collect data and save it into a database before we know what our final database tables will look like. Dataset has a simple, yet powerful API that makes it easy to put data in and sort it out later.
|
||||||
|
|
||||||
|
Dataset is built on top of SQLAlchemy, so extending it will feel familiar. The underlying database models are a breeze to import into Django using Django's built-in [inspectdb][2] management command. This makes working with existing databases pretty painless.
|
||||||
|
|
||||||
|
### To scrape data from web pages: Beautiful Soup
|
||||||
|
|
||||||
|
[Beautiful Soup][3] (BS4 as of this writing) makes extracting information out of HTML pages easy. It's our go-to anytime we need to turn unstructured or loosely structured HTML into structured data. It's also great for working with XML data that might otherwise not be readable.
|
||||||
|
|
||||||
|
### To work with HTTP content: Requests
|
||||||
|
|
||||||
|
[Requests][4] is arguably one of the gold standard libraries for working with HTTP content. Anytime we need to consume an HTML page or even an API, Requests has us covered. It's also very well documented.
|
||||||
|
|
||||||
|
### To write command-line utilities: Click
|
||||||
|
|
||||||
|
When we need to write a native Python script, [Click][5] is our favorite library for writing command-line utilities. The API is straightforward, well thought out, and there are only a few patterns to remember. The docs are great, which makes looking up advanced features easy.
|
||||||
|
|
||||||
|
### To name things: Python Slugify
|
||||||
|
|
||||||
|
As we all know, naming things is hard. [Python Slugify][6] is a useful library for turning a title or description into a unique(ish) identifier. If you are working on a web project and you want to use SEO-friendly URLs, Python Slugify makes this easier.
|
||||||
|
|
||||||
|
### To work with plugins: Pluggy
|
||||||
|
|
||||||
|
[Pluggy][7] is relatively new, but it's also one of the best and easiest ways to add a plugin system to your existing application. If you have ever worked with pytest, you have used pluggy without knowing it.
|
||||||
|
|
||||||
|
### To convert CSV files into APIs: Datasette
|
||||||
|
|
||||||
|
[Datasette][8], not to be confused with Dataset, is an amazing tool for easily turning CSV files into full-featured read-only REST JSON APIs. Datasette has tons of features, including charting and geo (for creating interactive maps), and it's easy to deploy via a container or third-party web host.
|
||||||
|
|
||||||
|
### To handle environment variables and more: Envparse
|
||||||
|
|
||||||
|
If you need to parse environment variables because you don't want to save API keys, database credentials, or other sensitive information in your source code, then [envparse][9] is one of your best bets. Envparse handles environment variables, ENV files, variable types, and even pre- and post-processors (in case you want to ensure that a variable is always upper or lower case, for instance).
|
||||||
|
|
||||||
|
Do you have a favorite Python library for side projects that's not on this list? Please share it in the comments.
|
||||||
|
|
||||||
|
--------------------------------------------------------------------------------
|
||||||
|
|
||||||
|
via: https://opensource.com/article/18/9/python-libraries-side-projects
|
||||||
|
|
||||||
|
作者：[Jeff Triplett][a]
|
||||||
|
选题：[lujun9972](https://github.com/lujun9972)
|
||||||
|
译者：[译者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/laceynwilliams
|
||||||
|
[1]: https://dataset.readthedocs.io/en/latest/
|
||||||
|
[2]: https://docs.djangoproject.com/en/2.1/ref/django-admin/#django-admin-inspectdb
|
||||||
|
[3]: https://www.crummy.com/software/BeautifulSoup/
|
||||||
|
[4]: http://docs.python-requests.org/
|
||||||
|
[5]: http://click.pocoo.org/5/
|
||||||
|
[6]: https://github.com/un33k/python-slugify
|
||||||
|
[7]: https://pluggy.readthedocs.io/en/latest/
|
||||||
|
[8]: https://github.com/simonw/datasette
|
||||||
|
[9]: https://github.com/rconradharris/envparse
|
||||||
@ -0,0 +1,108 @@
|
|||||||
|
Find your systems easily on a LAN with mDNS
|
||||||
|
======
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
Multicast DNS, or mDNS, lets systems broadcast queries on a local network to find other resources by name. Fedora users often own multiple Linux systems on a router without sophisticated name services. In that case, mDNS lets you talk to your multiple systems by name — without touching the router in most cases. You also don’t have to keep files like /etc/hosts in sync on all the local systems. This article shows you how to set it up.
|
||||||
|
|
||||||
|
mDNS is a zero-configuration networking service that’s been around for quite a while. Fedora ships Avahi, a zero-configuration stack that includes mDNS, as part of Workstation. (mDNS is also part of Bonjour, found on Mac OS.)
|
||||||
|
|
||||||
|
This article assumes you have two systems running supported versions of Fedora (27 or 28). Their host names are meant to be castor and pollux.
|
||||||
|
|
||||||
|
### Installing packages
|
||||||
|
|
||||||
|
Make sure the nss-mdns and avahi packages are installed on your system. You might have a different version, which is fine:
|
||||||
|
```
|
||||||
|
$ rpm -q nss-mdns avahi
|
||||||
|
nss-mdns-0.14.1-1.fc28.x86_64
|
||||||
|
avahi-0.7-13.fc28.x86_64
|
||||||
|
|
||||||
|
```
|
||||||
|
|
||||||
|
Fedora Workstation provides both of these packages by default. If not present, install them:
|
||||||
|
```
|
||||||
|
$ sudo dnf install nss-mdns avahi
|
||||||
|
|
||||||
|
```
|
||||||
|
|
||||||
|
Make sure the avahi-daemon.service unit is enabled and running. Again, this is the default on Fedora Workstation.
|
||||||
|
```
|
||||||
|
$ sudo systemctl enable --now avahi-daemon.service
|
||||||
|
|
||||||
|
```
|
||||||
|
|
||||||
|
Although optional, you might also want to install the avahi-tools package. This package includes a number of handy utilities for checking how well the zero-configuration services on your system are working. Use this sudo command:
|
||||||
|
```
|
||||||
|
$ sudo dnf install avahi-tools
|
||||||
|
|
||||||
|
```
|
||||||
|
|
||||||
|
The /etc/nsswitch.conf file controls which services your system uses to resolve services, and in what order. You should see a line like this in that file:
|
||||||
|
```
|
||||||
|
hosts: files mdns4_minimal [NOTFOUND=return] dns myhostname
|
||||||
|
|
||||||
|
```
|
||||||
|
|
||||||
|
Notice the commands mdns4_minimal [NOTFOUND=return]. They tell your system to use the multicast DNS resolver to resolve a hostname to an IP address. Even if that service works, the remaining services are tried if the name doesn’t resolve.
|
||||||
|
|
||||||
|
If you don’t see a configuration similar to this, you can edit it (as the root user). However, the nss-mdns package handles this for you. Remove and reinstall that package to fix the file, if you’re uncomfortable editing it yourself.
|
||||||
|
|
||||||
|
Follow the steps above for **both systems**.
|
||||||
|
|
||||||
|
### Setting host name and testing
|
||||||
|
|
||||||
|
Now that you’ve done the common configuration work, set up each host’s name in one of these ways:
|
||||||
|
|
||||||
|
1. If you’re using Fedora Workstation, [you can use this procedure][1].
|
||||||
|
|
||||||
|
2. If not, use hostnamectl to do the honors. Do this for the first box:
|
||||||
|
```
|
||||||
|
$ hostnamectl set-hostname castor
|
||||||
|
|
||||||
|
```
|
||||||
|
|
||||||
|
3. You can also edit the /etc/avahi/avahi-daemon.conf file, remove the comment on the host-name setting line, and set the name there. By default, though, Avahi uses the system provided host name, so you **shouldn’t** need this method.
|
||||||
|
|
||||||
|
Next, restart the Avahi daemon so it picks up changes:
|
||||||
|
```
|
||||||
|
$ sudo systemctl restart avahi-daemon.service
|
||||||
|
|
||||||
|
```
|
||||||
|
|
||||||
|
Then set your other box properly:
|
||||||
|
```
|
||||||
|
$ hostnamectl set-hostname pollux
|
||||||
|
$ sudo systemctl restart avahi-daemon.service
|
||||||
|
|
||||||
|
```
|
||||||
|
|
||||||
|
As long as your network router is not disallowing mDNS traffic, you should now be able to login to castor and ping the other box. You should use the default .local domain name so resolution works correctly:
|
||||||
|
```
|
||||||
|
$ ping pollux.local
|
||||||
|
PING pollux.local (192.168.0.1) 56(84) bytes of data.
|
||||||
|
64 bytes from 192.168.0.1 (192.168.0.1): icmp_seq=1 ttl=64 time=3.17 ms
|
||||||
|
64 bytes from 192.168.0.1 (192.168.0.1): icmp_seq=2 ttl=64 time=1.24 ms
|
||||||
|
...
|
||||||
|
|
||||||
|
```
|
||||||
|
|
||||||
|
The same trick should also work from pollux if you ping castor.local. It’s much more convenient now to access your systems around the network!
|
||||||
|
|
||||||
|
Moreover, don’t be surprised if your router advertises services. Modern WiFi and wired routers often provide these services to make life easier for consumers.
|
||||||
|
|
||||||
|
This process works for most systems. However, if you run into trouble, use avahi-browse and other tools from the avahi-tools package to see what services are available.
|
||||||
|
|
||||||
|
|
||||||
|
--------------------------------------------------------------------------------
|
||||||
|
|
||||||
|
via: https://fedoramagazine.org/find-systems-easily-lan-mdns/
|
||||||
|
|
||||||
|
作者：[Paul W. Frields][a]
|
||||||
|
选题：[lujun9972](https://github.com/lujun9972)
|
||||||
|
译者：[译者ID](https://github.com/译者ID)
|
||||||
|
校对：[校对者ID](https://github.com/校对者ID)
|
||||||
|
|
||||||
|
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
||||||
|
|
||||||
|
[a]: https://fedoramagazine.org/author/pfrields/
|
||||||
|
[1]: https://fedoramagazine.org/set-hostname-fedora/
|
||||||
@ -0,0 +1,253 @@
|
|||||||
|
How To Run MS-DOS Games And Programs In Linux
|
||||||
|
======
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
If you ever wanted to try some good-old MS-DOS games and defunct C++ compilers like Turbo C++ in Linux? Good! This tutorial will teach you how to run MS-DOS games and programs under Linux environment using **DOSBox**. It is an x86 PC DOS-emulator that can be used to run classic DOS games or programs. DOSBox emulates an Intel x86 PC with sound, graphics, mouse, joystick, and modem etc., that allows you to run many old MS-DOS games and programs that simply cannot be run on any modern PCs and operating systems, such as Microsoft Windows XP and later, Linux and FreeBSD. It is free, written using C++ programming language and distributed under GPL.
|
||||||
|
|
||||||
|
### Install DOSBox In Linux
|
||||||
|
|
||||||
|
DOSBox is available in the default repositories of most Linux distributions.
|
||||||
|
|
||||||
|
On Arch Linux and its variants like Antergos, Manjaro Linux:
|
||||||
|
```
|
||||||
|
$ sudo pacman -S dosbox
|
||||||
|
|
||||||
|
```
|
||||||
|
|
||||||
|
On Debian, Ubuntu, Linux Mint:
|
||||||
|
```
|
||||||
|
$ sudo apt-get install dosbox
|
||||||
|
|
||||||
|
```
|
||||||
|
|
||||||
|
On Fedora:
|
||||||
|
```
|
||||||
|
$ sudo dnf install dosbox
|
||||||
|
|
||||||
|
```
|
||||||
|
|
||||||
|
### Configure DOSBox
|
||||||
|
|
||||||
|
There is no initial configuration required to use DOSBox and it just works out of the box. The default configuration file named `dosbox-x.xx.conf` exists in your **`~/.dosbox`** folder. In this configuration file, you can edit/modify various settings, such as starting DOSBox in fullscreen mode, use double buffering in fullscreen, set preferred resolution to use for fullscreen, mouse sensitivity, enable or disable sound, speaker, joystick and a lot more. As I mentioned earlier, the default settings will work just fine. You need not to make any changes.
|
||||||
|
|
||||||
|
### Run MS-DOS Games And Programs In Linux
|
||||||
|
|
||||||
|
To launch DOSBox, run the following command from the Terminal:
|
||||||
|
```
|
||||||
|
$ dosbox
|
||||||
|
|
||||||
|
```
|
||||||
|
|
||||||
|
This is how DOSBox interface looks like.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
As you can see, DOSBox comes with its own DOS-like command prompt with a virtual `Z:\` Drive, so if you’re familiar with MS-DOS, you wouldn’t find any difficulties to work in DOSBox environment.
|
||||||
|
|
||||||
|
Here is the output of `dir`command (Equivalent of `ls` command in Linux) output:
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
If you’re a new user and it is the first time you use DOSBox, you can view the short introduction about DOSBox by entering the following command in DOSBox prompt:
|
||||||
|
```
|
||||||
|
intro
|
||||||
|
|
||||||
|
```
|
||||||
|
|
||||||
|
Press ENTER to go through next page of the introduction section.
|
||||||
|
|
||||||
|
To view the list of most often used commands in DOS, use this command:
|
||||||
|
```
|
||||||
|
help
|
||||||
|
|
||||||
|
```
|
||||||
|
|
||||||
|
To view list of all supported commands in DOSBox, type:
|
||||||
|
```
|
||||||
|
help /all
|
||||||
|
|
||||||
|
```
|
||||||
|
|
||||||
|
Remember, these commands should be used in the DOSBox prompt, not in your Linux Terminal.
|
||||||
|
|
||||||
|
DOSBox also supports a good set of keyboard bindings. Here is the default keyboard shortcuts to effectively use DOSBox.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
To exit from DOSBox, simply type and hit ENTER:
|
||||||
|
```
|
||||||
|
exit
|
||||||
|
|
||||||
|
```
|
||||||
|
|
||||||
|
By default, DOSBox starts with a normal window-sized screen like above.
|
||||||
|
|
||||||
|
To start dosbox directly in fullscreen, edit your `dosbox-x.xx.conf` file and set the value of **fullscreen** variable as **enable**. Now, DosBox will start in fullscreen mode. To go back to normal screen, press **ALT+ENTER**.
|
||||||
|
|
||||||
|
Hope you get the basic usage of DOSBox.
|
||||||
|
|
||||||
|
Let us go ahead and install some DOS programs and games.
|
||||||
|
|
||||||
|
First, we need to create directories to save the programs and games in our Linux system. I am going to create two directories named **`~/dosprograms`** and **`~/dosgames`** , the first one for storing programs and latter for storing games.
|
||||||
|
```
|
||||||
|
$ mkdir ~/dosprograms ~/dosgames
|
||||||
|
|
||||||
|
```
|
||||||
|
|
||||||
|
For the purpose of this guide, I will show you how to install **Turbo C++** program and Mario game. First, we will see how to install Turbo.
|
||||||
|
|
||||||
|
Download the latest Turbo C++ compiler, extract it and save the contents file in **`~/dosprograms`** directory. I have save the contents turbo c++ in my **~/dosprograms/TC/** directory.
|
||||||
|
```
|
||||||
|
$ ls dosprograms/tc/
|
||||||
|
BGI BIN CLASSLIB DOC EXAMPLES FILELIST.DOC INCLUDE LIB README README.COM
|
||||||
|
|
||||||
|
```
|
||||||
|
|
||||||
|
Start Dosbox:
|
||||||
|
```
|
||||||
|
$ dosbox
|
||||||
|
|
||||||
|
```
|
||||||
|
|
||||||
|
And mount the **`~/dosprograms`** directory as virtual drive **C:\** in DOSBox.
|
||||||
|
```
|
||||||
|
Z:\>mount c ~/dosprograms
|
||||||
|
|
||||||
|
```
|
||||||
|
|
||||||
|
You will see an output something like below.
|
||||||
|
```
|
||||||
|
Drive C is mounted as local directory /home/sk/dosprograms.
|
||||||
|
|
||||||
|
```
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
Now, change to the C drive using command:
|
||||||
|
```
|
||||||
|
Z:\>c:
|
||||||
|
|
||||||
|
```
|
||||||
|
|
||||||
|
And then, switch to **tc/bin** directory:
|
||||||
|
```
|
||||||
|
Z:\>cd tc/bin
|
||||||
|
|
||||||
|
```
|
||||||
|
|
||||||
|
Finally, run turbo c++ executable file:
|
||||||
|
```
|
||||||
|
Z:\>tc.exe
|
||||||
|
|
||||||
|
```
|
||||||
|
|
||||||
|
**Note:** Just type first few letters and hit ENTER to autocomplete the file name.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
You will now be in Turbo C++ console.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
Create new file (ATL+F) and start coding:
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
Similarly, you can install and run other classic DOS programs.
|
||||||
|
|
||||||
|
**Troubleshooting:**
|
||||||
|
|
||||||
|
You might be encountered with following error while running turbo c++ or any other dos programs:
|
||||||
|
```
|
||||||
|
DOSBox switched to max cycles, because of the setting: cycles=auto. If the game runs too fast try a fixed cycles amount in DOSBox's options. Exit to error: DRC64:Unhandled memory reference
|
||||||
|
|
||||||
|
```
|
||||||
|
|
||||||
|
To fix this, edit your **~/.dosbox/dosbox-x.xx.conf** file:
|
||||||
|
```
|
||||||
|
$ nano ~/.dosbox/dosbox-0.74.conf
|
||||||
|
|
||||||
|
```
|
||||||
|
|
||||||
|
Find the following variable and change its value from:
|
||||||
|
```
|
||||||
|
core=auto
|
||||||
|
|
||||||
|
```
|
||||||
|
|
||||||
|
to
|
||||||
|
```
|
||||||
|
core=normal
|
||||||
|
|
||||||
|
```
|
||||||
|
|
||||||
|
Save and close the file. Now you can be able to run the dos programs without any problems.
|
||||||
|
|
||||||
|
Now, let us see how to run a dos-based game, for example **Mario Bros VGA**.
|
||||||
|
|
||||||
|
Download Mario game from [**here**][1] and extract the contents in **~/dosgames** directory in your Linux machine.
|
||||||
|
|
||||||
|
Start DOSBox:
|
||||||
|
```
|
||||||
|
$ dosbox
|
||||||
|
|
||||||
|
```
|
||||||
|
|
||||||
|
We have used virtual drive **c:** for dos programs. For games, let us use **d:** as virtual drive.
|
||||||
|
|
||||||
|
At the DOSBox prompt, run the following command to mount **~/dosgames** directory as virtuald drive **d**.
|
||||||
|
```
|
||||||
|
Z:\>mount d ~/dosgames
|
||||||
|
|
||||||
|
```
|
||||||
|
|
||||||
|
Switch to D: drive:
|
||||||
|
```
|
||||||
|
Z:\>d:
|
||||||
|
|
||||||
|
```
|
||||||
|
|
||||||
|
And then go to mario game directory and run the **mario.exe** file to launch the game.
|
||||||
|
```
|
||||||
|
Z:\>cd mario
|
||||||
|
|
||||||
|
Z:\>mario.exe
|
||||||
|
|
||||||
|
```
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
Start playing the game:
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
Similarly, you can run any dos-based games as described above. You can view the complete list of supported games that can be run using DOSBox [**here**][2].
|
||||||
|
|
||||||
|
### Conclusion
|
||||||
|
|
||||||
|
Even though DOSBOX is not a complete replacement for MS-DOS and it lacks many of the features found in MS-DOS, it is just enough to install and run most DOS games and programs.
|
||||||
|
|
||||||
|
For more details, refer the official [**DOSBox manual**][3].
|
||||||
|
|
||||||
|
And, that’s all for now. Hope this was useful. More good stuffs to come. Stay tuned!
|
||||||
|
|
||||||
|
Cheers!
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
--------------------------------------------------------------------------------
|
||||||
|
|
||||||
|
via: https://www.ostechnix.com/how-to-run-ms-dos-games-and-programs-in-linux/
|
||||||
|
|
||||||
|
作者：[SK][a]
|
||||||
|
选题：[lujun9972](https://github.com/lujun9972)
|
||||||
|
译者：[译者ID](https://github.com/译者ID)
|
||||||
|
校对：[校对者ID](https://github.com/校对者ID)
|
||||||
|
|
||||||
|
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
||||||
|
|
||||||
|
[a]: https://www.ostechnix.com/author/sk/
|
||||||
|
[1]: https://www.dosgames.com/game/mario-bros-vga
|
||||||
|
[2]: https://www.dosbox.com/comp_list.php
|
||||||
|
[3]: https://www.dosbox.com/DOSBoxManual.html
|
||||||
@ -0,0 +1,106 @@
|
|||||||
|
如何从 Linux 命令行安装软件
|
||||||
|
======
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
如果你在任何时间都使用 Linux，你很快就会发现有很多不同的方法可以做同样的事情。这包括通过命令行在 Linux 上安装应用。我已经是大约 25 年的 Linux 用户，我一次又一次地回到命令行来安装我的应用。
|
||||||
|
|
||||||
|
从命令行安装应用程序最常用的方法是使用称为包管理器的软件库（存储软件的地方）。所有 Linux 应用都作为软件包分发，这些软件包只不过是与软件包管理系统相关的文件。每个 Linux 发行版都附带一个包管理系统，但它们并不完全相同。
|
||||||
|
|
||||||
|
### 什么是包管理系统？
|
||||||
|
|
||||||
|
包管理系统由多组工具和文件格式组成，它们一起用于安装、更新和卸载 Linux 应用。两种最常见的包管理系统来自 Red Hat 和 Debian。 Red Hat、CentOS 和 Fedora 都使用 `rpm` 系统（.rpm 文件），而Debian、Ubuntu、Mint 和 Ubuntu 都使用 `dpkg`（.deb 文件）。Gentoo Linux 使用名为 Portage 的系统，Arch Linux 只使用 tarball（.tar 文件）。这些系统之间的主要区别在于它们如何安装和维护应用。
|
||||||
|
|
||||||
|
你可能想知道 `.rpm`、`.deb` 或 `.tar` 文件中的内容。你可能会惊讶地发现，所有这些都只是普通的老式归档文件（如 `.zip`），其中包含应用的代码，如何安装它的说明，依赖项（它可能依赖的其他应用），以及配置文件的位置。读取和执行所有这些指令的软件称为包管理器。
|
||||||
|
|
||||||
|
### Debian、Ubuntu、Mint 等
|
||||||
|
|
||||||
|
Debian、Ubuntu、Mint 和其他基于 Debian 的发行版都使用 `.deb` 文件和 `dpkg` 包管理系统。有两种方法可以通过此系统安装应用。你可以使用 `apt` 程序从仓库进行安装，也可以使用 `dpkg` 程序从 `.deb` 文件安装应用。我们来看看如何做到这两点。
|
||||||
|
|
||||||
|
使用 `apt` 安装应用非常简单：
|
||||||
|
```
|
||||||
|
$ sudo apt install app_name
|
||||||
|
|
||||||
|
```
|
||||||
|
|
||||||
|
通过 `apt` 卸载应用也非常简单：
|
||||||
|
```
|
||||||
|
$ sudo apt remove app_name
|
||||||
|
|
||||||
|
```
|
||||||
|
|
||||||
|
要升级已安装的应用，首先需要更新应用仓库：
|
||||||
|
```
|
||||||
|
$ sudo apt update
|
||||||
|
|
||||||
|
```
|
||||||
|
|
||||||
|
完成后，你可以使用以下命令更新任何程序：
|
||||||
|
```
|
||||||
|
$ sudo apt upgrade
|
||||||
|
|
||||||
|
```
|
||||||
|
|
||||||
|
如果你只想更新一个应用，该怎么办？没问题。
|
||||||
|
```
|
||||||
|
$ sudo apt update app_name
|
||||||
|
|
||||||
|
```
|
||||||
|
|
||||||
|
最后，假设你要安装的应用不存在于 Debian 仓库中，但有 `.deb` 下载。
|
||||||
|
```
|
||||||
|
$ sudo dpkg -i app_name.deb
|
||||||
|
|
||||||
|
```
|
||||||
|
|
||||||
|
### Red Hat、CentOS 和 Fedora
|
||||||
|
|
||||||
|
默认情况下，Red Hat 使用多个包管理系统。这些系统在使用自己的命令时，互相仍然非常相似，而且与 Debian 中使用的也相似。例如，我们可以使用 `yum` 或 `dnf` 管理器来安装应用。
|
||||||
|
```
|
||||||
|
$ sudo yum install app_name
|
||||||
|
|
||||||
|
$ sudo dnf install app_name
|
||||||
|
|
||||||
|
```
|
||||||
|
|
||||||
|
`.rpm` 格式的应用也可以使用 `rpm` 命令安装。
|
||||||
|
```
|
||||||
|
$ sudo rpm -i app_name.rpm
|
||||||
|
|
||||||
|
```
|
||||||
|
|
||||||
|
删除不需要的应用同样容易。
|
||||||
|
```
|
||||||
|
$ sudo yum remove app_name
|
||||||
|
|
||||||
|
$ sudo dnf remove app_name
|
||||||
|
|
||||||
|
```
|
||||||
|
|
||||||
|
更新应用同样容易。
|
||||||
|
```
|
||||||
|
$ yum update
|
||||||
|
|
||||||
|
$ sudo dnf upgrade --refresh
|
||||||
|
|
||||||
|
```
|
||||||
|
|
||||||
|
如你所见，从命令行安装、卸载和更新 Linux 应用并不难。事实上，一旦你习惯它，你会发现它比使用基于桌面 GUI 的管理工具更快！
|
||||||
|
|
||||||
|
有关从命令行安装应用程序的更多信息，请访问 Debian [Apt wiki][1]、[Yum 速查表][2] 和 [DNF wiki][3]。
|
||||||
|
|
||||||
|
--------------------------------------------------------------------------------
|
||||||
|
|
||||||
|
via: https://opensource.com/article/18/8/how-install-software-linux-command-line
|
||||||
|
|
||||||
|
作者：[Patrick H.Mullins][a]
|
||||||
|
选题：[lujun9972](https://github.com/lujun9972)
|
||||||
|
译者：[geekpi](https://github.com/geekpi)
|
||||||
|
校对：[校对者ID](https://github.com/校对者ID)
|
||||||
|
|
||||||
|
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
||||||
|
|
||||||
|
[a]:https://opensource.com/users/pmullins
|
||||||
|
[1]:https://wiki.debian.org/Apt
|
||||||
|
[2]:https://access.redhat.com/articles/yum-cheat-sheet
|
||||||
|
[3]:https://fedoraproject.org/wiki/DNF?rd=Dnf
|
||||||
Loading…
Reference in New Issue
Block a user