mirror of
https://github.com/LCTT/TranslateProject.git
synced 2025-03-21 02:10:11 +08:00
Merge remote-tracking branch 'LCTT/master'
This commit is contained in:
Xingyu.Wang
commit
64465eb329
@ -0,0 +1,431 @@
|
||||
|
||||
如何在 Linux 上检查一个软件包的详细信息
|
||||
======
|
||||
|
||||
我们可以就这个已经被广泛讨论的话题写出大量的文章，大多数情况下，因为各种各样的原因，我们都愿意让<ruby>包管理器<rt>package manager</rt></ruby>来帮我们做这些事情。
|
||||
|
||||
每个 Linux 发行版都有自己的包管理器，并且每个都有各自有不同的特性，这些特性包括允许用户执行安装新软件包，删除无用的软件包，更新现存的软件包，搜索某些具体的软件包，以及更新整个系统到其最新的状态之类的操作。
|
||||
|
||||
习惯于命令行的用户大多数时间都会使用基于命令行方式的包管理器。对于 Linux 而言，这些基于命令行的包管理器有 `yum`、`dnf`、`rpm`、`apt`、`apt-get`、`dpkg`、`pacman` 和 `zypper`。
|
||||
|
||||
**推荐阅读**
|
||||
|
||||
- [Linux 命令行包管理器列表及其用法][1]
|
||||
- [一个图形化的 Linux 包管理器前端工具][2]
|
||||
- [如何搜索知道一个软件包是否存在于你的 Linux 发行版][3]
|
||||
- [如何使用 dnf/yum 配置包管理器在 Linux 上来添加、启用和禁用软件仓库][4]
|
||||
|
||||
作为一个系统管理员你应该清楚地知道：安装包来自何方，具体来自哪个软件仓库，包的具体版本，包的大小，版本，包的源代码 URL，包的许可证信息，等等。
|
||||
|
||||
这篇短文将用尽可能简单的方式帮你从随包自带的总结和描述中了解该包的用法。按你所使用的 Linux 发行版的不同，运行下面相应的命令，你能得到你所使用的发行版下的包的详细信息。
|
||||
|
||||
### YUM 命令：在 RHEL 和 CentOS 系统上获得包的信息
|
||||
|
||||
[YUM][5] 英文直译是“<ruby>黄狗更新器--修改版<rt>Yellowdog Updater, Modified</rt></ruby>”，它是一个开源的基于命令行的包管理器前端实用工具。它被广泛应用在基于 RPM 的系统上，例如：RHEL 和 CentOS。
|
||||
|
||||
Yum 是用于在官方发行版仓库以及其他第三方发行版仓库下获取、安装、删除、查询 RPM 包的主要工具。
|
||||
|
||||
（LCTT 译注：用 `yum info` 获取 python 包的信息）
|
||||
|
||||
```
|
||||
# yum info python
|
||||
Loaded plugins: fastestmirror, security
|
||||
Loading mirror speeds from cached hostfile
|
||||
* epel: epel.mirror.constant.com
|
||||
Installed Packages
|
||||
Name : python
|
||||
Arch : x86_64
|
||||
Version : 2.6.6
|
||||
Release : 66.el6_8
|
||||
Size : 78 k
|
||||
Repo : installed
|
||||
From repo : updates
|
||||
Summary : An interpreted, interactive, object-oriented programming language
|
||||
URL : http://www.python.org/
|
||||
License : Python
|
||||
Description : Python is an interpreted, interactive, object-oriented programming
|
||||
: language often compared to Tcl, Perl, Scheme or Java. Python includes
|
||||
: modules, classes, exceptions, very high level dynamic data types and
|
||||
: dynamic typing. Python supports interfaces to many system calls and
|
||||
: libraries, as well as to various windowing systems (X11, Motif, Tk,
|
||||
: Mac and MFC).
|
||||
:
|
||||
: Programmers can write new built-in modules for Python in C or C++.
|
||||
: Python can be used as an extension language for applications that need
|
||||
: a programmable interface.
|
||||
:
|
||||
: Note that documentation for Python is provided in the python-docs
|
||||
: package.
|
||||
:
|
||||
: This package provides the "python" executable; most of the actual
|
||||
: implementation is within the "python-libs" package.
|
||||
|
||||
```
|
||||
|
||||
### YUMDB 命令：查看 RHEL 和 CentOS 系统上的包信息
|
||||
|
||||
`yumdb info` 这个命令提供与 `yum info` 相类似的的信息，不过它还额外提供了诸如包校验值、包类型、用户信息（由何人安装）。从 yum 3.2.26 版本后，`yum` 开始在 rpm 数据库外储存额外的信息了（此处如显示 `user` 表明该包由用户安装，而 `dep` 说明该包是被作为被依赖的包而被安装的）。
|
||||
|
||||
（LCTT 译注：用 `yumdb info` 来获取 python 包的信息）
|
||||
|
||||
```
|
||||
# yumdb info python
|
||||
Loaded plugins: fastestmirror
|
||||
python-2.6.6-66.el6_8.x86_64
|
||||
changed_by = 4294967295
|
||||
checksum_data = 53c75a1756e5b4f6564c5229a37948c9b4561e0bf58076bd7dab7aff85a417f2
|
||||
checksum_type = sha256
|
||||
command_line = update -y
|
||||
from_repo = updates
|
||||
from_repo_revision = 1488370672
|
||||
from_repo_timestamp = 1488371100
|
||||
installed_by = 4294967295
|
||||
reason = dep
|
||||
releasever = 6
|
||||
```
|
||||
|
||||
### RPM 命令：在 RHEL/CentOS/Fedora 系统上查看包的信息
|
||||
|
||||
[RPM][6] 英文直译为“<ruby>红帽包管理器<rt>Red Hat Package Manager</rt></ruby>”，这是一个在 RedHat 以及其变种发行版（如RHEL、CentOS、Fedora、openSUSE、Megeia）下的功能强大的命令行包管理工具。它能让你轻松的安装、升级、删除、查询以及校验你的系统或服务器上的软件。RPM 文件以 `.rpm` 结尾。RPM 包由它所依赖的软件库以及其他依赖构成，它不会与系统上已经安装的包冲突。
|
||||
|
||||
（LCTT 译注：用 `rpm -qi` 查询 nano 包的具体信息）
|
||||
|
||||
```
|
||||
# rpm -qi nano
|
||||
Name : nano Relocations: (not relocatable)
|
||||
Version : 2.0.9 Vendor: CentOS
|
||||
Release : 7.el6 Build Date: Fri 12 Nov 2010 02:18:36 AM EST
|
||||
Install Date: Fri 03 Mar 2017 08:57:47 AM EST Build Host: c5b2.bsys.dev.centos.org
|
||||
Group : Applications/Editors Source RPM: nano-2.0.9-7.el6.src.rpm
|
||||
Size : 1588347 License: GPLv3+
|
||||
Signature : RSA/8, Sun 03 Jul 2011 12:46:50 AM EDT, Key ID 0946fca2c105b9de
|
||||
Packager : CentOS BuildSystem
|
||||
URL : http://www.nano-editor.org
|
||||
Summary : A small text editor
|
||||
Description :
|
||||
GNU nano is a small and friendly text editor.
|
||||
```
|
||||
|
||||
### DNF 命令：在 Fedora 系统上查看包信息
|
||||
|
||||
[DNF][7] 指“<ruby>时髦版的 Yum<rt>Dandified yum</rt></ruby>”，我们也可以认为 DNF 是下一代的 yum 包管理器（Yum 的一个分支），它在后台使用了 hawkey/libsolv 库。Aleš Kozumplík 在Fedora 18 上开始开发 DNF，在 Fedora 22 上正式最后发布。 `dnf` 命令用来在 Fedora 22 及以后的系统上安装、更新、搜索以及删除包。它能自动的解决包安装过程中的包依赖问题。
|
||||
|
||||
（LCTT 译注： 用 `dnf info` 查看 tilix 包信息）
|
||||
|
||||
```
|
||||
$ dnf info tilix
|
||||
Last metadata expiration check: 27 days, 10:00:23 ago on Wed 04 Oct 2017 06:43:27 AM IST.
|
||||
Installed Packages
|
||||
Name : tilix
|
||||
Version : 1.6.4
|
||||
Release : 1.fc26
|
||||
Arch : x86_64
|
||||
Size : 3.6 M
|
||||
Source : tilix-1.6.4-1.fc26.src.rpm
|
||||
Repo : @System
|
||||
From repo : @commandline
|
||||
Summary : Tiling terminal emulator
|
||||
URL : https://github.com/gnunn1/tilix
|
||||
License : MPLv2.0 and GPLv3+ and CC-BY-SA
|
||||
Description : Tilix is a tiling terminal emulator with the following features:
|
||||
:
|
||||
: - Layout terminals in any fashion by splitting them horizontally or vertically
|
||||
: - Terminals can be re-arranged using drag and drop both within and between
|
||||
: windows
|
||||
: - Terminals can be detached into a new window via drag and drop
|
||||
: - Input can be synchronized between terminals so commands typed in one
|
||||
: terminal are replicated to the others
|
||||
: - The grouping of terminals can be saved and loaded from disk
|
||||
: - Terminals support custom titles
|
||||
: - Color schemes are stored in files and custom color schemes can be created by
|
||||
: simply creating a new file
|
||||
: - Transparent background
|
||||
: - Supports notifications when processes are completed out of view
|
||||
:
|
||||
: The application was written using GTK 3 and an effort was made to conform to
|
||||
: GNOME Human Interface Guidelines (HIG).
|
||||
```
|
||||
|
||||
### Zypper 命令：在 openSUSE 系统上查看包信息
|
||||
|
||||
[zypper][8] 是一个使用 libzypp 库的命令行包管理器。`zypper` 提供诸如软件仓库访问，安装依赖解决，软件包安装等等功能。
|
||||
|
||||
（LCTT 译注： 用 `zypper info` 查询 nano 包的信息）
|
||||
|
||||
```
|
||||
$ zypper info nano
|
||||
|
||||
Loading repository data...
|
||||
Reading installed packages...
|
||||
|
||||
|
||||
Information for package nano:
|
||||
-----------------------------
|
||||
Repository : Main Repository (OSS)
|
||||
Name : nano
|
||||
Version : 2.4.2-5.3
|
||||
Arch : x86_64
|
||||
Vendor : openSUSE
|
||||
Installed Size : 1017.8 KiB
|
||||
Installed : No
|
||||
Status : not installed
|
||||
Source package : nano-2.4.2-5.3.src
|
||||
Summary : Pico editor clone with enhancements
|
||||
Description :
|
||||
GNU nano is a small and friendly text editor. It aims to emulate
|
||||
the Pico text editor while also offering a few enhancements.
|
||||
```
|
||||
|
||||
### Pacman 命令：在 ArchLinux 及 Manjaro 系统上查看包信息
|
||||
|
||||
[Pacman][9] 意即<ruby>包管理器<rt>package manager</rt></ruby>实用工具。`pacman` 是一个用于安装、构建、删除、管理 Arch Linux 上包的命令行工具。它后端使用 libalpm（Arch Linux package Manager（ALPM）库）来完成所有功能。
|
||||
|
||||
（LCTT 译注： 用 `pacman -Qi` 来查询 bash 包信息）
|
||||
|
||||
```
|
||||
$ pacman -Qi bash
|
||||
Name : bash
|
||||
Version : 4.4.012-2
|
||||
Description : The GNU Bourne Again shell
|
||||
Architecture : x86_64
|
||||
URL : http://www.gnu.org/software/bash/bash.html
|
||||
Licenses : GPL
|
||||
Groups : base
|
||||
Provides : sh
|
||||
Depends On : readline>=7.0 glibc ncurses
|
||||
Optional Deps : bash-completion: for tab completion
|
||||
Required By : autoconf automake bison bzip2 ca-certificates-utils db
|
||||
dhcpcd diffutils e2fsprogs fakeroot figlet findutils
|
||||
flex freetype2 gawk gdbm gettext gmp grub gzip icu
|
||||
iptables keyutils libgpg-error libksba libpcap libpng
|
||||
libtool lvm2 m4 man-db mkinitcpio nano neofetch nspr
|
||||
nss openresolv os-prober pacman pcre pcre2 shadow
|
||||
systemd texinfo vte-common which xdg-user-dirs xdg-utils
|
||||
xfsprogs xorg-mkfontdir xorg-xpr xz
|
||||
Optional For : None
|
||||
Conflicts With : None
|
||||
Replaces : None
|
||||
Installed Size : 7.13 MiB
|
||||
Packager : Jan Alexander Steffens (heftig)
|
||||
Build Date : Tue 14 Feb 2017 01:16:51 PM UTC
|
||||
Install Date : Thu 24 Aug 2017 06:08:12 AM UTC
|
||||
Install Reason : Explicitly installed
|
||||
Install Script : No
|
||||
Validated By : Signature
|
||||
```
|
||||
|
||||
### apt-cache 命令：在 Debian/Ubuntu/Mint 系统上查看包信息
|
||||
|
||||
[apt-cache][10] 命令能显示 apt 内部数据库中的大量信息。这些信息是从 `sources.list` 中的不同的软件源中搜集而来，因此从某种意义上这些信息也可以被认为是某种缓存。这些信息搜集工作是在运行 `apt update` 命令时执行的。
|
||||
|
||||
（LCTT 译注：用管理员权限查询 apache2 包的信息）
|
||||
|
||||
```
|
||||
$ sudo apt-cache show apache2
|
||||
Package: apache2
|
||||
Priority: optional
|
||||
Section: web
|
||||
Installed-Size: 473
|
||||
Maintainer: Ubuntu Developers
|
||||
Original-Maintainer: Debian Apache Maintainers
|
||||
Architecture: amd64
|
||||
Version: 2.4.12-2ubuntu2
|
||||
Replaces: apache2.2-common
|
||||
Provides: httpd, httpd-cgi
|
||||
Depends: lsb-base, procps, perl, mime-support, apache2-bin (= 2.4.12-2ubuntu2), apache2-utils (>= 2.4), apache2-data (= 2.4.12-2ubuntu2)
|
||||
Pre-Depends: dpkg (>= 1.17.14)
|
||||
Recommends: ssl-cert
|
||||
Suggests: www-browser, apache2-doc, apache2-suexec-pristine | apache2-suexec-custom, ufw
|
||||
Conflicts: apache2.2-common (<< 2.3~)
|
||||
Filename: pool/main/a/apache2/apache2_2.4.12-2ubuntu2_amd64.deb
|
||||
Size: 91348
|
||||
MD5sum: ab0ee0b0d1c6b3d19bd87aa2a9537125
|
||||
SHA1: 350c9a1a954906088ed032aebb77de3d5bb24004
|
||||
SHA256: 03f515f7ebc3b67b050b06e82ebca34b5e83e34a528868498fce020bf1dbbe34
|
||||
Description-en: Apache HTTP Server
|
||||
The Apache HTTP Server Project's goal is to build a secure, efficient and
|
||||
extensible HTTP server as standards-compliant open source software. The
|
||||
result has long been the number one web server on the Internet.
|
||||
.
|
||||
Installing this package results in a full installation, including the
|
||||
configuration files, init scripts and support scripts.
|
||||
Description-md5: d02426bc360345e5acd45367716dc35c
|
||||
Homepage: http://httpd.apache.org/
|
||||
Bugs: https://bugs.launchpad.net/ubuntu/+filebug
|
||||
Origin: Ubuntu
|
||||
Supported: 9m
|
||||
Task: lamp-server, mythbuntu-frontend, mythbuntu-desktop, mythbuntu-backend-slave, mythbuntu-backend-master, mythbuntu-backend-master
|
||||
```
|
||||
|
||||
### APT 命令：查看 Debian/Ubuntu/Mint 系统上的包信息
|
||||
|
||||
[APT][11] 意为<ruby>高级打包工具<rt>Advanced Packaging Tool</rt></ruby>，就像 DNF 将如何替代 YUM 一样，APT 是 apt-get 的替代物。它功能丰富的命令行工具包括了如下所有命令的功能如 `apt-cache`、`apt-search`、`dpkg`、`apt-cdrom`、`apt-config`、`apt-key` 等等，我们可以方便的通过 `apt` 来安装 `.dpkg` 包，但是我们却不能通过 `apt-get` 来完成这一点，还有一些其他的类似的功能也不能用 `apt-get` 来完成，所以 `apt-get` 因为没有解决上述功能缺乏的原因而被 `apt` 所取代。
|
||||
|
||||
（LCTT 译注： 用 `apt show` 查看 nano 包信息）
|
||||
|
||||
```
|
||||
$ apt show nano
|
||||
Package: nano
|
||||
Version: 2.8.6-3
|
||||
Priority: standard
|
||||
Section: editors
|
||||
Origin: Ubuntu
|
||||
Maintainer: Ubuntu Developers
|
||||
Original-Maintainer: Jordi Mallach
|
||||
Bugs: https://bugs.launchpad.net/ubuntu/+filebug
|
||||
Installed-Size: 766 kB
|
||||
Depends: libc6 (>= 2.14), libncursesw5 (>= 6), libtinfo5 (>= 6)
|
||||
Suggests: spell
|
||||
Conflicts: pico
|
||||
Breaks: nano-tiny (<< 2.8.6-2)
|
||||
Replaces: nano-tiny (<< 2.8.6-2), pico
|
||||
Homepage: https://www.nano-editor.org/
|
||||
Task: standard, ubuntu-touch-core, ubuntu-touch
|
||||
Supported: 9m
|
||||
Download-Size: 222 kB
|
||||
APT-Manual-Installed: yes
|
||||
APT-Sources: http://in.archive.ubuntu.com/ubuntu artful/main amd64 Packages
|
||||
Description: small, friendly text editor inspired by Pico
|
||||
GNU nano is an easy-to-use text editor originally designed as a replacement
|
||||
for Pico, the ncurses-based editor from the non-free mailer package Pine
|
||||
(itself now available under the Apache License as Alpine).
|
||||
.
|
||||
However, GNU nano also implements many features missing in pico, including:
|
||||
- undo/redo
|
||||
- line numbering
|
||||
- syntax coloring
|
||||
- soft-wrapping of overlong lines
|
||||
- selecting text by holding Shift
|
||||
- interactive search and replace (with regular expression support)
|
||||
- a go-to line (and column) command
|
||||
- support for multiple file buffers
|
||||
- auto-indentation
|
||||
- tab completion of filenames and search terms
|
||||
- toggling features while running
|
||||
- and full internationalization support
|
||||
```
|
||||
|
||||
### dpkg 命令：查看Debian/Ubuntu/Mint系统上的包信息
|
||||
|
||||
|
||||
[dpkg][12] 意指 <ruby>Debian 包管理器<rt>Debian package manager</rt></ruby>。`dpkg` 是用于 Debian 系统上安装、构建、移除以及管理 Debian 包的命令行工具。`dpkg` 使用 `aptitude`（因为它更为主流及用户友好）作为前端工具来完成所有的功能。其他的工具如` dpkg-deb` 和 `dpkg-query` 使用 `dpkg` 做为前端来实现功能。尽管系统管理员还是时不时会在必要时使用 `dpkg` 来完成一些软件安装的任务，他大多数情况下还是会因为 `apt`、`apt-get` 以及 `aptitude` 的健壮性而使用后者。
|
||||
|
||||
（LCTT 译注： 用 `dpkg -s` 查看 python 包的信息）
|
||||
|
||||
```
|
||||
$ dpkg -s python
|
||||
Package: python
|
||||
Status: install ok installed
|
||||
Priority: optional
|
||||
Section: python
|
||||
Installed-Size: 626
|
||||
Maintainer: Ubuntu Developers
|
||||
Architecture: amd64
|
||||
Multi-Arch: allowed
|
||||
Source: python-defaults
|
||||
Version: 2.7.14-2ubuntu1
|
||||
Replaces: python-dev (<< 2.6.5-2)
|
||||
Provides: python-ctypes, python-email, python-importlib, python-profiler, python-wsgiref
|
||||
Depends: python2.7 (>= 2.7.14-1~), libpython-stdlib (= 2.7.14-2ubuntu1)
|
||||
Pre-Depends: python-minimal (= 2.7.14-2ubuntu1)
|
||||
Suggests: python-doc (= 2.7.14-2ubuntu1), python-tk (>= 2.7.14-1~)
|
||||
Breaks: update-manager-core (<< 0.200.5-2)
|
||||
Conflicts: python-central (<< 0.5.5)
|
||||
Description: interactive high-level object-oriented language (default version)
|
||||
Python, the high-level, interactive object oriented language,
|
||||
includes an extensive class library with lots of goodies for
|
||||
network programming, system administration, sounds and graphics.
|
||||
.
|
||||
This package is a dependency package, which depends on Debian's default
|
||||
Python version (currently v2.7).
|
||||
Homepage: http://www.python.org/
|
||||
Original-Maintainer: Matthias Klose
|
||||
```
|
||||
|
||||
我们也可使用 `dpkg` 的 `-p` 选项，这个选项提供和 `dpkg -s` 相类似的信息，但是它还提供了包的校验值和包类型。
|
||||
|
||||
（LCTT 译注： 用 `dpkg -p` 查看 python3 包的信息）
|
||||
|
||||
```
|
||||
$ dpkg -p python3
|
||||
Package: python3
|
||||
Priority: important
|
||||
Section: python
|
||||
Installed-Size: 67
|
||||
Origin: Ubuntu
|
||||
Maintainer: Ubuntu Developers
|
||||
Bugs: https://bugs.launchpad.net/ubuntu/+filebug
|
||||
Architecture: amd64
|
||||
Multi-Arch: allowed
|
||||
Source: python3-defaults
|
||||
Version: 3.6.3-0ubuntu2
|
||||
Replaces: python3-minimal (<< 3.1.2-2)
|
||||
Provides: python3-profiler
|
||||
Depends: python3.6 (>= 3.6.3-1~), libpython3-stdlib (= 3.6.3-0ubuntu2), dh-python
|
||||
Pre-Depends: python3-minimal (= 3.6.3-0ubuntu2)
|
||||
Suggests: python3-doc (>= 3.6.3-0ubuntu2), python3-tk (>= 3.6.3-1~), python3-venv (>= 3.6.3-0ubuntu2)
|
||||
Filename: pool/main/p/python3-defaults/python3_3.6.3-0ubuntu2_amd64.deb
|
||||
Size: 8712
|
||||
MD5sum: a8bae494c6e5d1896287675faf40d373
|
||||
Description: interactive high-level object-oriented language (default python3 version)
|
||||
Original-Maintainer: Matthias Klose
|
||||
SHA1: 2daec885cea7d4dc83c284301c3bebf42b23e095
|
||||
SHA256: 865e509c91d2504a16c4b573dbe27e260c36fceec2add3fa43a30c1751d7e9bb
|
||||
Homepage: http://www.python.org/
|
||||
Task: minimal, ubuntu-core, ubuntu-core
|
||||
Description-md5: 950ebd8122c0a7340f0a740c295b9eab
|
||||
Supported: 9m
|
||||
```
|
||||
|
||||
### aptitude 命令：查看 Debian/Ubuntu/Mint 系统上的包信息
|
||||
|
||||
|
||||
`aptitude` 是 Debian GNU/Linux 包管理系统的文本界面。它允许用户查看已安装的包的列表，以及完成诸如安装、升级、删除包之类的包管理任务。这些管理行为也能从图形接口来执行。
|
||||
|
||||
（LCTT 译注： 用 `aptitude show` 查看 htop 包信息）
|
||||
|
||||
```
|
||||
$ aptitude show htop
|
||||
Package: htop
|
||||
Version: 2.0.2-1
|
||||
State: installed
|
||||
Automatically installed: no
|
||||
Priority: optional
|
||||
Section: universe/utils
|
||||
Maintainer: Ubuntu Developers
|
||||
Architecture: amd64
|
||||
Uncompressed Size: 216 k
|
||||
Depends: libc6 (>= 2.15), libncursesw5 (>= 6), libtinfo5 (>= 6)
|
||||
Suggests: lsof, strace
|
||||
Conflicts: htop:i386
|
||||
Description: interactive processes viewer
|
||||
Htop is an ncursed-based process viewer similar to top, but it allows one to scroll the list vertically and horizontally to see all processes and their full command lines.
|
||||
|
||||
Tasks related to processes (killing, renicing) can be done without entering their PIDs.
|
||||
Homepage: http://hisham.hm/htop/
|
||||
```
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://www.2daygeek.com/how-to-view-detailed-information-about-a-package-in-linux/
|
||||
|
||||
作者：[Prakash Subramanian][a]
|
||||
选题：[lujun9972](https://github.com/lujun9972)
|
||||
译者：[DavidChenLiang](https://github.com/davidchenliang)
|
||||
校对：[wxy](https://github.com/wxy)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
||||
[a]:https://www.2daygeek.com/author/prakash/
|
||||
[1]:https://www.2daygeek.com/list-of-command-line-package-manager-for-linux/
|
||||
[2]:https://www.2daygeek.com/list-of-graphical-frontend-tool-for-linux-package-manager/
|
||||
[3]:https://www.2daygeek.com/how-to-search-if-a-package-is-available-on-your-linux-distribution-or-not/
|
||||
[4]:https://www.2daygeek.com/how-to-add-enable-disable-a-repository-dnf-yum-config-manager-on-linux/
|
||||
[5]:https://www.2daygeek.com/yum-command-examples-manage-packages-rhel-centos-systems/
|
||||
[6]:https://www.2daygeek.com/rpm-command-examples/
|
||||
[7]:https://www.2daygeek.com/dnf-command-examples-manage-packages-fedora-system/
|
||||
[8]:https://www.2daygeek.com/zypper-command-examples-manage-packages-opensuse-system/
|
||||
[9]:https://www.2daygeek.com/pacman-command-examples-manage-packages-arch-linux-system/
|
||||
[10]:https://www.2daygeek.com/apt-get-apt-cache-command-examples-manage-packages-debian-ubuntu-systems/
|
||||
[11]:https://www.2daygeek.com/apt-command-examples-manage-packages-debian-ubuntu-systems/
|
||||
[12]:https://www.2daygeek.com/dpkg-command-to-manage-packages-on-debian-ubuntu-linux-mint-systems/
|
||||
@ -0,0 +1,131 @@
|
||||
Linux vs Mac: 7 Reasons Why Linux is a Better Choice than Mac
|
||||
======
|
||||
Recently, we highlighted a few points about [why Linux is better than Windows][1]. Unquestionably, Linux is a superior platform. But, like other operating systems it has its drawbacks as well. For a very particular set of tasks (such as Gaming), Windows OS might prove to be better. And, likewise, for another set of tasks (such as video editing), a Mac-powered system might come in handy. It all trickles down to your preference and what you would like to do with your system. So, in this article, we will highlight a number of reasons why Linux is better than Mac.
|
||||
|
||||
If you’re already using a Mac or planning to get one, we recommend you to thoroughly analyze the reasons and decide whether you want to switch/keep using Linux or continue using Mac.
|
||||
|
||||
### 7 Reasons Why Linux is Better Than Mac
|
||||
|
||||
![Linux vs Mac: Why Linux is a Better Choice][2]
|
||||
|
||||
Both Linux and macOS are Unix-like OS and give access to Unix commands, BASH and other shells. Both of them have fewer applications and games than Windows. But the similarity ends here.
|
||||
|
||||
Graphic designers and video editors swear by macOS whereas Linux is a favorite of developers, sysadmins and devops.
|
||||
|
||||
So the question is should you use Linux over Mac? If yes, why? Let me give you some practical and some ideological reasons why Linux is better than Mac.
|
||||
|
||||
#### 1\. Price
|
||||
|
||||
![Linux vs Mac: Why Linux is a Better Choice][3]
|
||||
|
||||
Let’s suppose, you use the system only to browse stuff, watch movies, download photos, write a document, create a spreadsheet, and other similar stuff. And, in addition to those activities, you want to have a secure operating system.
|
||||
|
||||
In that case, you could choose to spend a couple of hundred bucks for a system to get things done. Or do you think spending more for a MacBook is a good idea? Well, you are the judge.
|
||||
|
||||
So, it really depends on what you prefer. Whether you want to spend on a Mac-powered system or get a budget laptop/PC and install any Linux distro for free. Personally, I’ll be happy with a Linux system except for editing videos and music production. In that case, Final Cut Pro (for video editing) and Logic Pro X (for music production) will be my preference.
|
||||
|
||||
#### 2\. Hardware Choices
|
||||
|
||||
![Linux vs Mac: Why Linux is a Better Choice][4]
|
||||
|
||||
Linux is free. You can install it on computers with any configuration. No matter how powerful/old your system is, Linux will work. [Even if you have an 8-year old PC laying around, you can have Linux installed and expect it to run smoothly by selecting the right distro][5].
|
||||
|
||||
But, Mac is as an Apple-exclusive. If you want to assemble a PC or get a budget laptop (with DOS) and expect to install Mac OS, it’s almost impossible. Mac comes baked in with the system Apple manufactures.
|
||||
|
||||
There are [ways to install macOS on non Apple devices][6]. However, the kind of expertise and troubles it requires, it makes you question whether it’s worth the effort.
|
||||
|
||||
You will have a wide range of hardware choices when you go with Linux but a minimal set of configurations when it comes to Mac OS.
|
||||
|
||||
#### 3\. Security
|
||||
|
||||
![Linux vs Mac: Why Linux is a Better Choice][7]
|
||||
|
||||
A lot of people are all praises for iOS and Mac for being a secure platform. Well, yes, it is secure in a way (maybe more secure than Windows OS), but probably not as secure as Linux.
|
||||
|
||||
I am not bluffing. There are malware and adware targeting macOS and the [number is growing every day][8]. I have seen not-so-techie users struggling with their slow mac. A quick investigation revealed that a [browser hijacking malware][9] was the culprit.
|
||||
|
||||
There are no 100% secure operating systems and Linux is not an exception. There are vulnerabilities in the Linux world as well but they are duly patched by the timely updates provided by Linux distributions.
|
||||
|
||||
Thankfully, we don’t have auto-running viruses or browser hijacking malwares in Linux world so far. And that’s one more reason why you should use Linux instead of a Mac.
|
||||
|
||||
#### 4\. Customization & Flexibility
|
||||
|
||||
![Linux vs Mac: Why Linux is a Better Choice][10]
|
||||
|
||||
You don’t like something? Customize it or remove it. End of the story.
|
||||
|
||||
For example, if you do not like the [Gnome desktop environment][11] on Ubuntu 18.04.1, you might as well change it to [KDE Plasma][11]. You can also try some of the [Gnome extensions][12] to enhance your desktop experience. You won’t find this level of freedom and customization on Mac OS.
|
||||
|
||||
Besides, you can even modify the source code of your OS to add/remove something (which requires necessary technical knowledge) and create your own custom OS. Can you do that on Mac OS?
|
||||
|
||||
Moreover, you get an array of Linux distributions to choose from as per your needs. For instance, if you need to mimic the workflow on Mac OS, [Elementary OS][13] would help. Do you want to have a lightweight Linux distribution installed on your old PC? We’ve got you covered in our list of [lightweight Linux distros][5]. Mac OS lacks this kind of flexibility.
|
||||
|
||||
#### 5\. Using Linux helps your professional career [For IT/Tech students]
|
||||
|
||||
![Linux vs Mac: Why Linux is a Better Choice][14]
|
||||
|
||||
This is kind of controversial and applicable to students and job seekers in the IT field. Using Linux doesn’t make you a super-intelligent being and could possibly get you any IT related job.
|
||||
|
||||
However, as you start using Linux and exploring it, you gain experience. As a techie, sooner or later you dive into the terminal, learning your way to move around the file system, installing applications via command line. You won’t even realize that you have learned the skills that newcomers in IT companies get trained on.
|
||||
|
||||
In addition to that, Linux has enormous scope in the job market. There are so many Linux related technologies (Cloud, Kubernetes, Sysadmin etc.) you can learn, earn certifications and get a nice paying job. And to learn these, you have to use Linux.
|
||||
|
||||
#### 6\. Reliability
|
||||
|
||||
![Linux vs Mac: Why Linux is a Better Choice][15]
|
||||
|
||||
Ever wondered why Linux is the best OS to run on any server? Because it is more reliable!
|
||||
|
||||
But, why is that? Why is Linux more reliable than Mac OS?
|
||||
|
||||
The answer is simple – more control to the user while providing better security. Mac OS does not provide you with the full control of its platform. It does that to make things easier for you simultaneously enhancing your user experience. With Linux, you can do whatever you want – which may result in poor user experience (for some) – but it does make it more reliable.
|
||||
|
||||
#### 7\. Open Source
|
||||
|
||||
![Linux vs Mac: Why Linux is a Better Choice][16]
|
||||
|
||||
Open Source is something not everyone cares about. But to me, the most important aspect of Linux being a superior choice is its Open Source nature. And, most of the points discussed below are the direct advantages of an Open Source software.
|
||||
|
||||
To briefly explain, you get to see/modify the source code yourself if it is an open source software. But, for Mac, Apple gets an exclusive control. Even if you have the required technical knowledge, you will not be able to independently take a look at the source code of Mac OS.
|
||||
|
||||
In other words, a Mac-powered system enables you to get a car for yourself but the downside is you cannot open up the hood to see what’s inside. That’s bad!
|
||||
|
||||
If you want to dive in deeper to know about the benefits of an open source software, you should go through [Ben Balter’s article][17] on OpenSource.com.
|
||||
|
||||
### Wrapping Up
|
||||
|
||||
Now that you’ve known why Linux is better than Mac OS. What do you think about it? Are these reasons enough for you to choose Linux over Mac OS? If not, then what do you prefer and why?
|
||||
|
||||
Let us know your thoughts in the comments below.
|
||||
|
||||
Note: The artwork here is based on Club Penguins.
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://itsfoss.com/linux-vs-mac/
|
||||
|
||||
作者：[Ankush Das][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/ankush/
|
||||
[1]: https://itsfoss.com/linux-better-than-windows/
|
||||
[2]: https://4bds6hergc-flywheel.netdna-ssl.com/wp-content/uploads/2018/09/Linux-vs-mac-featured.png
|
||||
[3]: https://4bds6hergc-flywheel.netdna-ssl.com/wp-content/uploads/2018/09/linux-vs-mac-1.jpeg
|
||||
[4]: https://4bds6hergc-flywheel.netdna-ssl.com/wp-content/uploads/2018/09/linux-vs-mac-4.jpeg
|
||||
[5]: https://itsfoss.com/lightweight-linux-beginners/
|
||||
[6]: https://hackintosh.com/
|
||||
[7]: https://4bds6hergc-flywheel.netdna-ssl.com/wp-content/uploads/2018/09/linux-vs-mac-2.jpeg
|
||||
[8]: https://www.computerworld.com/article/3262225/apple-mac/warning-as-mac-malware-exploits-climb-270.html
|
||||
[9]: https://www.imore.com/how-to-remove-browser-hijack
|
||||
[10]: https://4bds6hergc-flywheel.netdna-ssl.com/wp-content/uploads/2018/09/linux-vs-mac-3.jpeg
|
||||
[11]: https://www.gnome.org/
|
||||
[12]: https://itsfoss.com/best-gnome-extensions/
|
||||
[13]: https://elementary.io/
|
||||
[14]: https://4bds6hergc-flywheel.netdna-ssl.com/wp-content/uploads/2018/09/linux-vs-mac-5.jpeg
|
||||
[15]: https://4bds6hergc-flywheel.netdna-ssl.com/wp-content/uploads/2018/09/linux-vs-mac-6.jpeg
|
||||
[16]: https://4bds6hergc-flywheel.netdna-ssl.com/wp-content/uploads/2018/09/linux-vs-mac-7.jpeg
|
||||
[17]: https://opensource.com/life/15/12/why-open-source
|
||||
@ -1,3 +1,4 @@
|
||||
LuMing translating
|
||||
How To Configure SSH Key-based Authentication In Linux
|
||||
======
|
||||
|
||||
|
||||
@ -1,159 +0,0 @@
|
||||
Installing Android on VirtualBox
|
||||
======
|
||||
If you are developing mobile apps Android can be a bit of a hassle. While iOS comes with its niceties, provided you are using macOS, Android comes with just Android Studio which is designed to support more than a few Android version, including wearables.
|
||||
|
||||
Needless to say, all the binaries, SDKs, frameworks and debuggers are going to pollute your filesystem with lots and lots of files, logs and other miscellaneous objects. An efficient work around for this is installing Android on your VirtualBox which takes away one of the sluggiest aspect of Android development — The device emulator. You can use this VM to run your test application or just fiddle with Android’s internals. So without further ado let’s set on up!
|
||||
|
||||
### Getting Started
|
||||
|
||||
To get started we will need to have VirtualBox installed on our system, you can get a copy for Windows, macOS or any major distro of Linux [here][1]. Next you would need a copy of Android meant to run on x86 hardware, because that’s what VirtualBox is going to offer to a Virtual Machine an x86 or an x86_64 (a.k.a AMD64) platform to run.
|
||||
|
||||
While most Android devices run on ARM, we can take help of the project [Android on x86][2]. These fine folks have ported Android to run on x86 hardware (both real and virtual) and we can get a copy of the latest release candidate (Android 7.1) for our purposes. You may prefer using a more stable release but in that case Android 6.0 is about as latest as you can get, at the time of this writing.
|
||||
|
||||
#### Creating VM
|
||||
|
||||
Open VirtualBox and click on “New” (top-left corner) and in the Create Virtual Machine window select the type to be Linux and version Linux 2.6 / 3.x /4.x (64-bit) or (32-bit) depending upon whether the ISO you downloaded was x86_64 or x86 respectively.
|
||||
|
||||
RAM size could be anywhere from 2 GB to as much as your system resources can allow. Although if you want to emulate real world devices you should allocate upto 6GB for memory and 32GB for disk size which are typical in Android devices.
|
||||
|
||||
![][3]
|
||||
|
||||
![][4]
|
||||
|
||||
Upon creation, you might want to tweak a few additional settings, add in an additional processor core and improve display memory for starters. To do this, right-click on the VM and open up settings. In the Settings → System → Processor section you can allocate a few more cores if your desktop can pull it off.
|
||||
|
||||
![][5]
|
||||
|
||||
And in Settings → Display → Video Memory you can allocate a decent chunk of memory and enable 3D acceleration for a more responsive experience.
|
||||
|
||||
![][6]
|
||||
|
||||
Now we are ready to boot the VM.
|
||||
|
||||
#### Installing Android
|
||||
|
||||
Starting the VM for the first time, VirtualBox will insist you to supply it with a bootable media. Select the Android iso that you previously downloaded to boot the machine of with.
|
||||
|
||||
![][7]
|
||||
|
||||
Next, select the Installation option if you wish to install Android on the VM for a long term use, otherwise feel free to log into the live media and play around with the environment.
|
||||
|
||||
![][8]
|
||||
|
||||
Hit <Enter>.
|
||||
|
||||
##### Partitioning the Drive
|
||||
|
||||
Partitioning is done using a textual interface, which means we don’t get the niceties of a GUI and we will have to use the follow careful at what is being shown on the screen. For example, in the first screen when no partition has been created and just a raw (virtual) disk is detected you will see the following.
|
||||
|
||||
![][9]
|
||||
|
||||
The red lettered C and D indicates that if you hit the key C you can create or modify partitions and D will detect additional devices. You can press D and the live media will detect the disks attached, but that is optional since it did a check during the boot.
|
||||
|
||||
Let’s hit C and create partitions in the virtual disk. The offical page recommends against using GPT so we will not use that scheme. Select No using the arrow keys and hit <Enter>.
|
||||
|
||||
![][10]
|
||||
|
||||
And now you will be ushered into the fdisk utility.
|
||||
|
||||
![][11]
|
||||
|
||||
We will create just a single giant partition so as to keep things simple. Using arrow keys navigate to the New option and hit <Enter>. Select primary as the type of partition, and hit <Enter> to confirm
|
||||
|
||||
![][12]
|
||||
|
||||
The maximum size will already be selected for you, hit <Enter> to confirm that.
|
||||
|
||||
![][13]
|
||||
|
||||
This partition is where Android OS will reside, so of course we want it to be bootable. So select Bootable and hit enter (Boot will appear in the flags section in the table above) and then you can navigate to the Write section and hit <Enter> to write the changes to the partitioning table.
|
||||
|
||||
![][14]
|
||||
|
||||
Then you can Quit the partitioning utility and move on with the installation.
|
||||
|
||||
![][15]
|
||||
|
||||
##### Formatting with Ext4 and installing Android
|
||||
|
||||
A new partition will come in the Choose Partition menu where we were before we down the partitioning digression. Let’s select this partition and hit OK.
|
||||
|
||||
![][16]
|
||||
|
||||
Select ext4 as the de facto file system in the next menu. Confirm the changes in the next window by selecting **Yes** and the formatting will begin. When asked, say **Yes** to the GRUB boot loader installation. Similarly, say **Yes** to allowing read-write operations on the /system directory. Now the installation will begin.
|
||||
|
||||
Once it is installed, you can safely reboot the system when prompted to reboot. You may have to power down the machine before the next reboot happens, go to Settings → Storage and remove the android iso if it is still attached to the VM.
|
||||
|
||||
![][17]
|
||||
|
||||
Remove the media and save the changes, before starting up the VM.
|
||||
|
||||
##### Running Android
|
||||
|
||||
In the GRUB menu you will get options for running the OS in debug mode or the normal way. Let’s take a tour of Android in a VM using the default option, as shown below:
|
||||
|
||||
![][18]
|
||||
|
||||
And if everything works fine, you will see this:
|
||||
|
||||
![][19]
|
||||
|
||||
Now Android uses touch screen as an interface instead of a mouse, as far as its normal use is concerned. While the x86 port does come with a mouse point-and-click support you may have to use arrow keys a lot in the beginning.
|
||||
|
||||
![][20]
|
||||
|
||||
Navigate to let’s go, and hit enter, if you are using arrow keys and then select Setup as New.
|
||||
|
||||
![][21]
|
||||
|
||||
It will check for updates and device info, before asking you to sign in using a Google account. You can skip this if you want and move on to setting up Data and Time and give your username to the device after that.
|
||||
|
||||
A few other options would be presented, similar to the options you see when setting up a new Android device. Select appropriate options for privacy, updates, etc and of course Terms of Service, which we might have to Agree to.
|
||||
|
||||
![][22]
|
||||
|
||||
After this, it may ask you to add another email account or set up “On-body detection” since it is a VM, neither of the options are of much use to us and we can click on “All Set”
|
||||
|
||||
It would ask you to select Home App after that, which is upto you to decide, as it is a matter of Preference and you will finally be in a virtualized Android system.
|
||||
|
||||
![][23]
|
||||
|
||||
You may benefit greatly from a touch screen laptop if you desire to do some intensive testing on this VM, since that would emulate a real world use case much closely.
|
||||
|
||||
Hope you have found this tutorial useful in case, you have any other similar request for us to write about, please feel free to reach out to us.
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://linuxhint.com/install_android_virtualbox/
|
||||
|
||||
作者：[Ranvir Singh][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://linuxhint.com/author/sranvir155/
|
||||
[1]:https://www.virtualbox.org/wiki/Downloads
|
||||
[2]:http://www.android-x86.org/
|
||||
[3]:https://linuxhint.com/wp-content/uploads/2018/08/a.png
|
||||
[4]:https://linuxhint.com/wp-content/uploads/2018/08/a1.png
|
||||
[5]:https://linuxhint.com/wp-content/uploads/2018/08/a2.png
|
||||
[6]:https://linuxhint.com/wp-content/uploads/2018/08/a3.png
|
||||
[7]:https://linuxhint.com/wp-content/uploads/2018/08/a4.png
|
||||
[8]:https://linuxhint.com/wp-content/uploads/2018/08/a5.png
|
||||
[9]:https://linuxhint.com/wp-content/uploads/2018/08/a6.png
|
||||
[10]:https://linuxhint.com/wp-content/uploads/2018/08/a7.png
|
||||
[11]:https://linuxhint.com/wp-content/uploads/2018/08/a8.png
|
||||
[12]:https://linuxhint.com/wp-content/uploads/2018/08/a9.png
|
||||
[13]:https://linuxhint.com/wp-content/uploads/2018/08/a10.png
|
||||
[14]:https://linuxhint.com/wp-content/uploads/2018/08/a11.png
|
||||
[15]:https://linuxhint.com/wp-content/uploads/2018/08/a12.png
|
||||
[16]:https://linuxhint.com/wp-content/uploads/2018/08/a13.png
|
||||
[17]:https://linuxhint.com/wp-content/uploads/2018/08/a14.png
|
||||
[18]:https://linuxhint.com/wp-content/uploads/2018/08/a16.png
|
||||
[19]:https://linuxhint.com/wp-content/uploads/2018/08/a17.png
|
||||
[20]:https://linuxhint.com/wp-content/uploads/2018/08/a18.png
|
||||
[21]:https://linuxhint.com/wp-content/uploads/2018/08/a19.png
|
||||
[22]:https://linuxhint.com/wp-content/uploads/2018/08/a20.png
|
||||
[23]:https://linuxhint.com/wp-content/uploads/2018/08/a21.png
|
||||
@ -1,3 +1,5 @@
|
||||
HankChow translating
|
||||
|
||||
5 Ways to Take Screenshot in Linux [GUI and Terminal]
|
||||
======
|
||||
Here are several ways you can take screenshots and edit the screenshots by adding text, arrows etc. Instructions and mentioned screenshot tools are valid for Ubuntu and other major Linux distributions.
|
||||
|
||||
57
sources/tech/20180914 A day in the life of a log message.md
Normal file
57
sources/tech/20180914 A day in the life of a log message.md
Normal file
@ -0,0 +1,57 @@
|
||||
A day in the life of a log message
|
||||
======
|
||||
|
||||
Navigating a modern distributed system from the perspective of a log message.
|
||||
|
||||
|
||||
|
||||
Chaotic systems tend to be unpredictable. This is especially evident when architecting something as complex as a distributed system. Left unchecked, this unpredictability can waste boundless amounts of time. This is why every single component of a distributed system, no matter how small, must be designed to fit together in a streamlined way.
|
||||
|
||||
[Kubernetes][1] provides a promising model for abstracting compute resources—but even it must be reconciled with other distributed platforms such as [Apache Kafka][2] to ensure reliable data delivery. If someone were to integrate these two platforms, how would it work? Furthermore, if you were to trace something as simple as a log message through such a system, what would it look like? This article will focus on how a log message from an application running inside [OKD][3], the Origin Community Distribution of Kubernetes that powers Red Hat OpenShift, gets to a data warehouse through Kafka.
|
||||
|
||||
### OKD-defined environment
|
||||
|
||||
Such a journey begins in OKD, since the container platform completely overlays the hardware it abstracts. This means that the log message waits to be written to **stdout** or **stderr** streams by an application residing in a container. From there, the log message is redirected onto the node's filesystem by a container engine such as [CRI-O][4].
|
||||
|
||||
|
||||
|
||||
ithin OpenShift, one or more containers are encapsulated within virtual compute nodes known as pods. In fact, all applications running within OKD are abstracted as pods. This allows the applications to be manipulated in a uniform way. This also greatly simplifies communication between distributed components, since pods are systematically addressable through IP addresses and [load-balanced services][5] . So when the log message is taken from the node's filesystem by a log-collector application, it can easily be delivered to another pod running within OpenShift.
|
||||
|
||||
### Two peas in a pod
|
||||
|
||||
To ensure ubiquitous dispersal of the log message throughout the distributed system, the log collector needs to deliver the log message into a Kafka cluster data hub running within OpenShift. Through Kafka, the log message can be delivered to the consuming applications in a reliable and fault-tolerant way with low latency. However, in order to reap the benefits of Kafka within an OKD-defined environment, Kafka needs to be fully integrated into OKD.
|
||||
|
||||
Running a [Strimzi operator][6] will instantiate all Kafka components as pods and integrate them to run within an OKD environment. This includes Kafka brokers for queuing log messages, Kafka connectors for reading and writing from Kafka brokers, and Zookeeper nodes for managing the Kafka cluster state. Strimzi can also instantiate the log collector to double as a Kafka connector, allowing the log collector to feed the log messages directly into a Kafka broker pod running within OKD.
|
||||
|
||||
### Kafka inside OKD
|
||||
|
||||
When the log-collector pod delivers the log message to a Kafka broker, the collector writes to a single broker partition, appending the message to the end of the partition. One of the advantages of using Kafka is that it decouples the log collector from the log's final destination. Thanks to the decoupling, the log collector doesn't care whether the logs end up in [Elasticsearch][7], Hadoop, Amazon S3, or all of them at the same time. Kafka is well-connected to all infrastructure, so the Kafka connectors can take the log message wherever it needs to go.
|
||||
|
||||
Once written to a Kafka broker's partition, the log message is replicated across the broker partitions within the Kafka cluster. This is a very powerful concept on its own; combined with the self-healing features of the platform, it creates a very resilient distributed system. For example, when a node becomes unavailable, the applications running on the node are almost instantaneously spawned on healthy node(s). So even if a node with the Kafka broker is lost or damaged, the log message is guaranteed to survive as many deaths as it was replicated and a new Kafka broker will quickly take the original's place.
|
||||
|
||||
### Off to storage
|
||||
|
||||
After it is committed to a Kafka topic, the log message waits to be consumed by a Kafka connector sink, which relays the log message to either an analytics engine or logging warehouse. Upon delivery to its final destination, the log message could be studied for anomaly detection, queried for immediate root-cause analysis, or used for other purposes. Either way, the log message is delivered by Kafka to its destination in a safe and reliable manner.
|
||||
|
||||
OKD and Kafka are powerful distributed platforms that are evolving rapidly. It is vital to create systems that can abstract the complicated nature of distributed computing without compromising performance. After all, how can we boast of systemwide efficiency if we cannot simplify the journey of a single log message?
|
||||
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://opensource.com/article/18/9/life-log-message
|
||||
|
||||
作者：[Josef Karásek][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/jkarasek
|
||||
[1]: https://kubernetes.io/
|
||||
[2]: https://kafka.apache.org/
|
||||
[3]: https://www.okd.io/
|
||||
[4]: http://cri-o.io/
|
||||
[5]: https://kubernetes.io/docs/concepts/services-networking/service/
|
||||
[6]: http://strimzi.io/
|
||||
[7]: https://www.elastic.co/
|
||||
@ -0,0 +1,394 @@
|
||||
Convert files at the command line with Pandoc
|
||||
======
|
||||
|
||||
This guide shows you how to use Pandoc to convert your documents into many different file formats
|
||||
|
||||
|
||||
|
||||
Pandoc is a command-line tool for converting files from one markup language to another. Markup languages use tags to annotate sections of a document. Commonly used markup languages include Markdown, ReStructuredText, HTML, LaTex, ePub, and Microsoft Word DOCX.
|
||||
|
||||
In plain English, [Pandoc][1] allows you to convert a bunch of files from one markup language into another one. Typical examples include converting a Markdown file into a presentation, LaTeX, PDF, or even ePub.
|
||||
|
||||
This article will explain how to produce documentation in multiple formats from a single markup language (in this case Markdown) using Pandoc. It will guide you through Pandoc installation, show how to create several types of documents, and offer tips on how to write documentation that is easy to port to other formats. It will also explain the value of using meta-information files to create a separation between the content and the meta-information (e.g., author name, template used, bibliographic style, etc.) of your documentation.
|
||||
|
||||
### Installation and requirements
|
||||
|
||||
Pandoc is installed by default in most Linux distributions. This tutorial uses pandoc-2.2.3.2 and pandoc-citeproc-0.14.3. If you don't intend to generate PDFs, those two packages are enough. However, I recommend installing texlive as well, so you have the option to generate PDFs.
|
||||
|
||||
To install these programs on Linux, type the following on the command line:
|
||||
|
||||
```
|
||||
sudo apt-get install pandoc pandoc-citeproc texlive
|
||||
```
|
||||
|
||||
You can find [installation instructions][2] for other platforms on Pandoc's website.
|
||||
|
||||
I highly recommend installing [pandoc][3][-crossref][3], a "filter for numbering figures, equations, tables, and cross-references to them." The easiest option is to download a [prebuilt executable][4], but you can install it from Haskell's package manager, cabal, by typing:
|
||||
|
||||
```
|
||||
cabal update
|
||||
cabal install pandoc-crossref
|
||||
```
|
||||
|
||||
Consult pandoc-crossref's GitHub repository if you need additional Haskell [installation information][5].
|
||||
|
||||
### Some examples
|
||||
|
||||
I'll demonstrate how Pandoc works by explaining how to produce three types of documents:
|
||||
|
||||
* A website from a LaTeX file containing math formulas
|
||||
* A Reveal.js slideshow from a Markdown file
|
||||
* A contract agreement document that mixes Markdown and LaTeX
|
||||
|
||||
|
||||
|
||||
#### Create a website with math formulas
|
||||
|
||||
One of the ways Pandoc excels is displaying math formulas in different output file formats. For instance, let's generate a website from a LaTeX document (named math.tex) containing some math symbols (written in LaTeX).
|
||||
|
||||
The math.tex document looks like:
|
||||
|
||||
```
|
||||
% Pandoc math demos
|
||||
|
||||
$a^2 + b^2 = c^2$
|
||||
|
||||
$v(t) = v_0 + \frac{1}{2}at^2$
|
||||
|
||||
$\gamma = \frac{1}{\sqrt{1 - v^2/c^2}}$
|
||||
|
||||
$\exists x \forall y (Rxy \equiv Ryx)$
|
||||
|
||||
$p \wedge q \models p$
|
||||
|
||||
$\Box\diamond p\equiv\diamond p$
|
||||
|
||||
$\int_{0}^{1} x dx = \left[ \frac{1}{2}x^2 \right]_{0}^{1} = \frac{1}{2}$
|
||||
|
||||
$e^x = \sum_{n=0}^\infty \frac{x^n}{n!} = \lim_{n\rightarrow\infty} (1+x/n)^n$
|
||||
```
|
||||
|
||||
Convert the LaTeX document into a website named mathMathML.html by entering the following command:
|
||||
|
||||
```
|
||||
pandoc math.tex -s --mathml -o mathMathML.html
|
||||
```
|
||||
|
||||
The flag **-s** tells Pandoc to generate a standalone website (instead of a fragment, so it will include the head and body HTML tags), and the **–mathml** flag forces Pandoc to convert the math in LaTeX to MathML, which can be rendered by modern browsers.
|
||||
|
||||
|
||||
|
||||
Take a look at the [website result][6] and the [code][7]; the code repository contains a Makefile to make things even simpler.
|
||||
|
||||
#### Make a Reveal.js slideshow
|
||||
|
||||
It's easy to generate simple presentations from a Markdown file using Pandoc. The slides contain top-level slides and nested slides underneath. The presentation can be controlled from the keyboard, and you can jump from one top-level slide to the next top-level slide or show the nested slides on a per-top-level basis. This structure is typical in HTML-based presentation frameworks.
|
||||
|
||||
Let's create a slide document named SLIDES (see the [code repository][8]). First, add the slides' meta-information (e.g., title, author, and date) prepended by the **%** symbol:
|
||||
|
||||
```
|
||||
% Case Study
|
||||
% Kiko Fernandez Reyes
|
||||
% Sept 27, 2017
|
||||
```
|
||||
|
||||
This meta-information also creates the first slide. To add more slides, declare top-level slides using Markdown heading H1 (line 5 in the example below, [heading 1 in Markdown][9] , designated by).
|
||||
|
||||
For example, if we want to create a presentation with the title Case Study that starts with a top-level slide titled Wine Management System, write:
|
||||
|
||||
```
|
||||
% Case Study
|
||||
% Kiko Fernandez Reyes
|
||||
% Sept 27, 2017
|
||||
|
||||
# Wine Management System
|
||||
```
|
||||
|
||||
To put content (such as slides that explain a new management system and its implementation) inside this top-level section, use a Markdown header H2. Let's add two more slides (lines 7 and 14 below, [heading 2 in Markdown][9], designated by **##** ):
|
||||
|
||||
* The first second-level slide has the title Idea and shows an image of the Swiss flag
|
||||
* The second second-level slide has the title Implementation
|
||||
|
||||
|
||||
|
||||
```
|
||||
% Case Study
|
||||
% Kiko Fernandez Reyes
|
||||
% Sept 27, 2017
|
||||
|
||||
# Wine Management System
|
||||
|
||||
## <img src="img/SwissFlag.png" style="vertical-align:middle"/> Idea
|
||||
|
||||
## Implementation
|
||||
```
|
||||
|
||||
We now have a top-level slide ( **# Wine Management System** ) that contains two slides ( **## Idea** and **## Implementation** ).
|
||||
|
||||
Let's put some content in these two slides using incremental bulleted lists by creating a Markdown list prepended by the symbol **>**. Continuing from above, add two items in the first slide (lines 9–10 below) and five items in the second slide (lines 16–20):
|
||||
|
||||
```
|
||||
% Case Study
|
||||
% Kiko Fernandez Reyes
|
||||
% Sept 27, 2017
|
||||
|
||||
# Wine Management System
|
||||
|
||||
## <img src="img/SwissFlag.png" style="vertical-align:middle"/> Idea
|
||||
|
||||
>- Swiss love their **wine** and cheese
|
||||
>- Create a *simple* wine tracker system
|
||||
|
||||
|
||||
|
||||
## Implementation
|
||||
|
||||
>- Bottles have a RFID tag
|
||||
>- RFID reader (emits and read signal)
|
||||
>- **Raspberry Pi**
|
||||
>- **Server (online shop)**
|
||||
>- Mobile app
|
||||
```
|
||||
|
||||
We added an image of the Matterhorn mountain. Your slides can be improved by using plain Markdown or adding plain HTML.
|
||||
|
||||
To generate the slides, Pandoc needs to point to the Reveal.js library, so it must be in the same folder as the SLIDES file. The command to generate the slides is:
|
||||
|
||||
```
|
||||
pandoc -t revealjs -s --self-contained SLIDES \
|
||||
-V theme=white -V slideNumber=true -o index.html
|
||||
```
|
||||
|
||||
|
||||
|
||||
The above Pandoc command uses the following flags:
|
||||
|
||||
* **-t revealjs** specifies we are going to output a **revealjs** presentation
|
||||
* **-s** tells Pandoc to generate a standalone document
|
||||
* **\--self-contained** produces HTML with no external dependencies
|
||||
* **-V** sets the following variables:
|
||||
– **theme=white** sets the theme of the slideshow to **white**
|
||||
– **slideNumber=true** shows the slide number
|
||||
* **-o index.html** generates the slides in the file named **index.html**
|
||||
|
||||
|
||||
|
||||
To make things simpler and avoid typing this long command, create the following Makefile:
|
||||
|
||||
```
|
||||
all: generate
|
||||
|
||||
generate:
|
||||
pandoc -t revealjs -s --self-contained SLIDES \
|
||||
-V theme=white -V slideNumber=true -o index.html
|
||||
|
||||
clean: index.html
|
||||
rm index.html
|
||||
|
||||
.PHONY: all clean generate
|
||||
```
|
||||
|
||||
You can find all the code in [this repository][8].
|
||||
|
||||
#### Make a multi-format contract
|
||||
|
||||
Let's say you are preparing a document and (as things are nowadays) some people want it in Microsoft Word format, others use free software and would like an ODT, and others need a PDF. You do not have to use OpenOffice nor LibreOffice to generate the DOCX or PDF file. You can create your document in Markdown (with some bits of LaTeX if you need advanced formatting) and generate any of these file types.
|
||||
|
||||
As before, begin by declaring the document's meta-information (title, author, and date):
|
||||
|
||||
```
|
||||
% Contract Agreement for Software X
|
||||
% Kiko Fernandez-Reyes
|
||||
% August 28th, 2018
|
||||
```
|
||||
|
||||
Then write the document in Markdown (and add LaTeX if you require advanced formatting). For example, create a table that needs fixed separation space (declared in LaTeX with **\hspace{3cm}** ) and a line where a client and a contractor should sign (declared in LaTeX with **\hrulefill** ). After that, add a table written in Markdown.
|
||||
|
||||
Here's what the document will look like:
|
||||
|
||||
|
||||
|
||||
The code to create this document is:
|
||||
|
||||
```
|
||||
% Contract Agreement for Software X
|
||||
% Kiko Fernandez-Reyes
|
||||
% August 28th, 2018
|
||||
|
||||
...
|
||||
|
||||
### Work Order
|
||||
|
||||
\begin{table}[h]
|
||||
\begin{tabular}{ccc}
|
||||
The Contractor & \hspace{3cm} & The Customer \\
|
||||
& & \\
|
||||
& & \\
|
||||
\hrulefill & \hspace{3cm} & \hrulefill \\
|
||||
%
|
||||
Name & \hspace{3cm} & Name \\
|
||||
& & \\
|
||||
& & \\
|
||||
\hrulefill & \hspace{3cm} & \hrulefill \\
|
||||
...
|
||||
\end{tabular}
|
||||
\end{table}
|
||||
|
||||
\vspace{1cm}
|
||||
|
||||
+--------------------------------------------|----------|-------------+
|
||||
| Type of Service | Cost | Total |
|
||||
+:===========================================+=========:+:===========:+
|
||||
| Game Engine | 70.0 | 70.0 |
|
||||
| | | |
|
||||
+--------------------------------------------|----------|-------------+
|
||||
| | | |
|
||||
+--------------------------------------------|----------|-------------+
|
||||
| Extra: Comply with defined API functions | 10.0 | 10.0 |
|
||||
| and expected returned format | | |
|
||||
+--------------------------------------------|----------|-------------+
|
||||
| | | |
|
||||
+--------------------------------------------|----------|-------------+
|
||||
| **Total Cost** | | **80.0** |
|
||||
+--------------------------------------------|----------|-------------+
|
||||
```
|
||||
|
||||
To generate the three different output formats needed for this document, write a Makefile:
|
||||
|
||||
```
|
||||
DOCS=contract-agreement.md
|
||||
|
||||
all: $(DOCS)
|
||||
pandoc -s $(DOCS) -o $(DOCS:md=pdf)
|
||||
pandoc -s $(DOCS) -o $(DOCS:md=docx)
|
||||
pandoc -s $(DOCS) -o $(DOCS:md=odt)
|
||||
|
||||
clean:
|
||||
rm *.pdf *.docx *.odt
|
||||
|
||||
.PHONY: all clean
|
||||
```
|
||||
|
||||
Lines 4–7 contain the commands to generate the different outputs.
|
||||
|
||||
If you have several Markdown files and want to merge them into one document, issue a command with the files in the order you want them to appear. For example, when writing this article, I created three documents: an introduction document, three examples, and some advanced uses. The following tells Pandoc to merge these files together in the specified order and produce a PDF named document.pdf.
|
||||
|
||||
```
|
||||
pandoc -s introduction.md examples.md advanced-uses.md -o document.pdf
|
||||
```
|
||||
|
||||
### Templates and meta-information
|
||||
|
||||
Writing a complex document is no easy task. You need to stick to a set of rules that are independent from your content, such as using a specific template, writing an abstract, embedding specific fonts, and maybe even declaring keywords. All of this has nothing to do with your content: simply put, it is meta-information.
|
||||
|
||||
Pandoc uses templates to generate different output formats. There is a template for LaTeX, another for ePub, etc. These templates have unfulfilled variables that are set with the meta-information given to Pandoc. To find out what meta-information is available in a Pandoc template, type:
|
||||
|
||||
```
|
||||
pandoc -D FORMAT
|
||||
```
|
||||
|
||||
For example, the template for LaTeX would be:
|
||||
|
||||
```
|
||||
pandoc -D latex
|
||||
```
|
||||
|
||||
Which outputs something along these lines:
|
||||
|
||||
```
|
||||
$if(title)$
|
||||
\title{$title$$if(thanks)$\thanks{$thanks$}$endif$}
|
||||
$endif$
|
||||
$if(subtitle)$
|
||||
\providecommand{\subtitle}[1]{}
|
||||
\subtitle{$subtitle$}
|
||||
$endif$
|
||||
$if(author)$
|
||||
\author{$for(author)$$author$$sep$ \and $endfor$}
|
||||
$endif$
|
||||
$if(institute)$
|
||||
\providecommand{\institute}[1]{}
|
||||
\institute{$for(institute)$$institute$$sep$ \and $endfor$}
|
||||
$endif$
|
||||
\date{$date$}
|
||||
$if(beamer)$
|
||||
$if(titlegraphic)$
|
||||
\titlegraphic{\includegraphics{$titlegraphic$}}
|
||||
$endif$
|
||||
$if(logo)$
|
||||
\logo{\includegraphics{$logo$}}
|
||||
$endif$
|
||||
$endif$
|
||||
|
||||
\begin{document}
|
||||
```
|
||||
|
||||
As you can see, there are **title** , **thanks** , **author** , **subtitle** , and **institute** template variables (and many others are available). These are easily set using YAML metablocks. In lines 1–5 of the example below, we declare a YAML metablock and set some of those variables (using the contract agreement example above):
|
||||
|
||||
```
|
||||
---
|
||||
title: Contract Agreement for Software X
|
||||
author: Kiko Fernandez-Reyes
|
||||
date: August 28th, 2018
|
||||
---
|
||||
|
||||
(continue writing document as in the previous example)
|
||||
```
|
||||
|
||||
This works like a charm and is equivalent to the previous code:
|
||||
|
||||
```
|
||||
% Contract Agreement for Software X
|
||||
% Kiko Fernandez-Reyes
|
||||
% August 28th, 2018
|
||||
```
|
||||
|
||||
However, this ties the meta-information to the content; i.e., Pandoc will always use this information to output files in the new format. If you know you need to produce multiple file formats, you better be careful. For example, what if you need to produce the contract in ePub and in HTML, and the ePub and HTML need specific and different styling rules?
|
||||
|
||||
Let's consider the cases:
|
||||
|
||||
* If you simply try to embed the YAML variable **css: style-epub.css** , you would be excluding the one from the HTML version. This does not work.
|
||||
* Duplicating the document is obviously not a good solution either, as changes in one version would not be in sync with the other copy.
|
||||
* You can add variables to the Pandoc command line as follows:
|
||||
|
||||
|
||||
|
||||
```
|
||||
pandoc -s -V css=style-epub.css document.md document.epub
|
||||
pandoc -s -V css=style-html.css document.md document.html
|
||||
```
|
||||
|
||||
My opinion is that it is easy to overlook these variables from the command line, especially when you need to set tens of these (which can happen in complex documents). Now, if you put them all together under the same roof (a meta.yaml file), you only need to update or create a new meta-information file to produce the desired output. You would then write:
|
||||
|
||||
```
|
||||
pandoc -s meta-pub.yaml document.md document.epub
|
||||
pandoc -s meta-html.yaml document.md document.html
|
||||
```
|
||||
|
||||
This is a much cleaner version, and you can update all the meta-information from a single file without ever having to update the content of your document.
|
||||
|
||||
### Wrapping up
|
||||
|
||||
With these basic examples, I have shown how Pandoc can do a really good job at converting Markdown documents into other formats.
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://opensource.com/article/18/9/intro-pandoc
|
||||
|
||||
作者：[Kiko Fernandez-Reyes][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/kikofernandez
|
||||
[1]: https://pandoc.org/
|
||||
[2]: http://pandoc.org/installing.html
|
||||
[3]: https://hackage.haskell.org/package/pandoc-crossref
|
||||
[4]: https://github.com/lierdakil/pandoc-crossref/releases/tag/v0.3.2.1
|
||||
[5]: https://github.com/lierdakil/pandoc-crossref#installation
|
||||
[6]: http://pandoc.org/demo/mathMathML.html
|
||||
[7]: https://github.com/kikofernandez/pandoc-examples/tree/master/math
|
||||
[8]: https://github.com/kikofernandez/pandoc-examples/tree/master/slides
|
||||
[9]: https://daringfireball.net/projects/markdown/syntax#header
|
||||
@ -1,432 +0,0 @@
|
||||
|
||||
如何在Linux上检查一个包（package）的详细信息
|
||||
======
|
||||
|
||||
|
||||
我们可以就这个已经被广泛讨论的话题写出大量的文档，大多数情况下，因为各种各样的原因，我们都愿意让包管理器（package manager）来帮我们做这些事情。
|
||||
|
||||
每个Linux发行版都有自己的包管理器，并且每个都有各自有不同的特性，这些特性包括允许用户执行安装新软件包，删除无用的软件包，更新现存的软件包，搜索某些具体的软件包，以及更新整个系统到其最新的状态之类的操作。
|
||||
|
||||
习惯于命令行的用户大多数时间都会使用基于命令行方式的包管理器。对于Linux而言，这些基于命令行的包管理器有Yum，Dnf, Rpm, Apt, Apt-Get, Deb, pacman 和zypper.
|
||||
|
||||
|
||||
**推荐阅读**
|
||||
**(#)** [List of Command line Package Managers For Linux & Usage][1]
|
||||
**(#)** [A Graphical frontend tool for Linux Package Manager][2]
|
||||
**(#)** [How To Search If A Package Is Available On Your Linux Distribution Or Not][3]
|
||||
**(#)** [How To Add, Enable And Disable A Repository By Using The DNF/YUM Config Manager Command On Linux][4]
|
||||
|
||||
|
||||
作为一个系统管理员你应该熟知以下事实：安装包来自何方，具体来自哪个软件仓库，包的具体版本，包的大小，发行版的版本，包的源URL，包的许可证信息，等等等等。
|
||||
|
||||
|
||||
这篇短文将用尽可能简单的方式帮你理解包管理器的用法，这些用法正是来自随包自带的总结和描述文件。按你所使用的Linux发行版的不同，运行下面相应的命令，你能得到你所使用的发行版下的包的详细信息。
|
||||
|
||||
### [YUM 命令][5] : 在RHEL和CentOS系统上获得包的信息
|
||||
|
||||
|
||||
YUM 英文直译是黄狗更新器--修改版，它是一个开源的基于命令行的包管理器前端实用工具。它被广泛应用在基于RPM的系统上，例如：RHEL和CentOS。
|
||||
|
||||
Yum是用于在官方发行版仓库以及其他第三方发行版仓库下获取，安装，删除，查询RPM包的主要工具。
|
||||
|
||||
```
|
||||
# yum info python（LCTT译注：用yum info 获取python包的信息）
|
||||
Loaded plugins: fastestmirror, security
|
||||
Loading mirror speeds from cached hostfile
|
||||
* epel: epel.mirror.constant.com
|
||||
Installed Packages
|
||||
Name : python
|
||||
Arch : x86_64
|
||||
Version : 2.6.6
|
||||
Release : 66.el6_8
|
||||
Size : 78 k
|
||||
Repo : installed
|
||||
From repo : updates
|
||||
Summary : An interpreted, interactive, object-oriented programming language
|
||||
URL : http://www.python.org/
|
||||
License : Python
|
||||
Description : Python is an interpreted, interactive, object-oriented programming
|
||||
: language often compared to Tcl, Perl, Scheme or Java. Python includes
|
||||
: modules, classes, exceptions, very high level dynamic data types and
|
||||
: dynamic typing. Python supports interfaces to many system calls and
|
||||
: libraries, as well as to various windowing systems (X11, Motif, Tk,
|
||||
: Mac and MFC).
|
||||
:
|
||||
: Programmers can write new built-in modules for Python in C or C++.
|
||||
: Python can be used as an extension language for applications that need
|
||||
: a programmable interface.
|
||||
:
|
||||
: Note that documentation for Python is provided in the python-docs
|
||||
: package.
|
||||
:
|
||||
: This package provides the "python" executable; most of the actual
|
||||
: implementation is within the "python-libs" package.
|
||||
|
||||
```
|
||||
|
||||
### YUMDB 命令： 查看RHEL和CentOS系统上的包信息
|
||||
|
||||
|
||||
Yumdb info这个命令提供与yum info相类似的的信息，不过它还额外提供了诸如包校验值，包类型，用户信息（由何人安装）。从yum 3.2.26版本后，yum开始在rpm数据库外储存额外的信息了（下文输出的用户信息指该python由该用户安装，而dep说明该包是被作为被依赖的包而被安装的）。
|
||||
|
||||
```
|
||||
# yumdb info python（LCTT译注：用yumdb info 来获取Python的信息）
|
||||
Loaded plugins: fastestmirror
|
||||
python-2.6.6-66.el6_8.x86_64
|
||||
changed_by = 4294967295
|
||||
checksum_data = 53c75a1756e5b4f6564c5229a37948c9b4561e0bf58076bd7dab7aff85a417f2
|
||||
checksum_type = sha256
|
||||
command_line = update -y
|
||||
from_repo = updates
|
||||
from_repo_revision = 1488370672
|
||||
from_repo_timestamp = 1488371100
|
||||
installed_by = 4294967295
|
||||
reason = dep
|
||||
releasever = 6
|
||||
|
||||
|
||||
```
|
||||
|
||||
### [RPM 命令][6] : 在RHEL/CentOS/Fedora系统上查看包的信息
|
||||
|
||||
|
||||
RPM 英文直译为红帽包管理器，这是一个在RedHat以及其变种发行版（如RHEL， CentOS， Fedora， openSUSE，Megeia）下的功能强大的命令行包管理工具。它能让你轻松的安装，升级，删除，查询以及校验你的系统或服务器上的软件。RPM文件以.rpm结尾。RPM包由它所依赖的软件库以及其他依赖构成，它不会与系统上已经安装的包冲突。
|
||||
|
||||
```
|
||||
# rpm -qi nano （LCTT译注：用RPM -qi 查询nano包的具体信息）
|
||||
Name : nano Relocations: (not relocatable)
|
||||
Version : 2.0.9 Vendor: CentOS
|
||||
Release : 7.el6 Build Date: Fri 12 Nov 2010 02:18:36 AM EST
|
||||
Install Date: Fri 03 Mar 2017 08:57:47 AM EST Build Host: c5b2.bsys.dev.centos.org
|
||||
Group : Applications/Editors Source RPM: nano-2.0.9-7.el6.src.rpm
|
||||
Size : 1588347 License: GPLv3+
|
||||
Signature : RSA/8, Sun 03 Jul 2011 12:46:50 AM EDT, Key ID 0946fca2c105b9de
|
||||
Packager : CentOS BuildSystem
|
||||
URL : http://www.nano-editor.org
|
||||
Summary : A small text editor
|
||||
Description :
|
||||
GNU nano is a small and friendly text editor.
|
||||
|
||||
```
|
||||
|
||||
### [DNF 命令][7] : 在Fedora系统上查看报信息
|
||||
|
||||
|
||||
DNF指时髦版的Yum,我们也可以认为DNF是下一代的YUM包管理器（Yum的一个分支），它在后台使用了hawkey/libsolv库。Aleš Kozumplík在Fedora 18上开始开发DNF，在Fedora 22上正式最后发布。 DNF命令用来在Fedora 22及以后系统安装， 更新，搜索以及删除包。它能自动的解决包安装过程中的包依赖问题。
|
||||
|
||||
```
|
||||
$ dnf info tilix （LCTT译注： 用dnf info 查看tilix的包信息）
|
||||
Last metadata expiration check: 27 days, 10:00:23 ago on Wed 04 Oct 2017 06:43:27 AM IST.
|
||||
Installed Packages
|
||||
Name : tilix
|
||||
Version : 1.6.4
|
||||
Release : 1.fc26
|
||||
Arch : x86_64
|
||||
Size : 3.6 M
|
||||
Source : tilix-1.6.4-1.fc26.src.rpm
|
||||
Repo : @System
|
||||
From repo : @commandline
|
||||
Summary : Tiling terminal emulator
|
||||
URL : https://github.com/gnunn1/tilix
|
||||
License : MPLv2.0 and GPLv3+ and CC-BY-SA
|
||||
Description : Tilix is a tiling terminal emulator with the following features:
|
||||
:
|
||||
: - Layout terminals in any fashion by splitting them horizontally or vertically
|
||||
: - Terminals can be re-arranged using drag and drop both within and between
|
||||
: windows
|
||||
: - Terminals can be detached into a new window via drag and drop
|
||||
: - Input can be synchronized between terminals so commands typed in one
|
||||
: terminal are replicated to the others
|
||||
: - The grouping of terminals can be saved and loaded from disk
|
||||
: - Terminals support custom titles
|
||||
: - Color schemes are stored in files and custom color schemes can be created by
|
||||
: simply creating a new file
|
||||
: - Transparent background
|
||||
: - Supports notifications when processes are completed out of view
|
||||
:
|
||||
: The application was written using GTK 3 and an effort was made to conform to
|
||||
: GNOME Human Interface Guidelines (HIG).
|
||||
|
||||
```
|
||||
|
||||
### [Zypper 命令][8] : 在openSUSE系统上查看包信息
|
||||
|
||||
|
||||
Zypper是一个使用libzypp库的命令行包管理器。Zypper提供诸如软件仓库访问，安装依赖解决，软件包安装等等功能。
|
||||
|
||||
```
|
||||
$ zypper info nano （译注： 用zypper info查询nano的信息）
|
||||
|
||||
Loading repository data...
|
||||
Reading installed packages...
|
||||
|
||||
|
||||
Information for package nano:
|
||||
-----------------------------
|
||||
Repository : Main Repository (OSS)
|
||||
Name : nano
|
||||
Version : 2.4.2-5.3
|
||||
Arch : x86_64
|
||||
Vendor : openSUSE
|
||||
Installed Size : 1017.8 KiB
|
||||
Installed : No
|
||||
Status : not installed
|
||||
Source package : nano-2.4.2-5.3.src
|
||||
Summary : Pico editor clone with enhancements
|
||||
Description :
|
||||
GNU nano is a small and friendly text editor. It aims to emulate
|
||||
the Pico text editor while also offering a few enhancements.
|
||||
|
||||
```
|
||||
|
||||
### [pacman 命令][9] ：在ArchLinux及Manjaro系统上查看包信息
|
||||
|
||||
Pacman指包管理器实用工具。pacman是一个用于安装，构建，删除，管理Arch Linux上包的命令行工具。它后端使用libalpm(Arch Linux package Manager（ALPM）库)来完成所有功能。
|
||||
|
||||
```
|
||||
$ pacman -Qi bash （LCTT译注： 用pacman -Qi 来查询bash）
|
||||
Name : bash
|
||||
Version : 4.4.012-2
|
||||
Description : The GNU Bourne Again shell
|
||||
Architecture : x86_64
|
||||
URL : http://www.gnu.org/software/bash/bash.html
|
||||
Licenses : GPL
|
||||
Groups : base
|
||||
Provides : sh
|
||||
Depends On : readline>=7.0 glibc ncurses
|
||||
Optional Deps : bash-completion: for tab completion
|
||||
Required By : autoconf automake bison bzip2 ca-certificates-utils db
|
||||
dhcpcd diffutils e2fsprogs fakeroot figlet findutils
|
||||
flex freetype2 gawk gdbm gettext gmp grub gzip icu
|
||||
iptables keyutils libgpg-error libksba libpcap libpng
|
||||
libtool lvm2 m4 man-db mkinitcpio nano neofetch nspr
|
||||
nss openresolv os-prober pacman pcre pcre2 shadow
|
||||
systemd texinfo vte-common which xdg-user-dirs xdg-utils
|
||||
xfsprogs xorg-mkfontdir xorg-xpr xz
|
||||
Optional For : None
|
||||
Conflicts With : None
|
||||
Replaces : None
|
||||
Installed Size : 7.13 MiB
|
||||
Packager : Jan Alexander Steffens (heftig)
|
||||
Build Date : Tue 14 Feb 2017 01:16:51 PM UTC
|
||||
Install Date : Thu 24 Aug 2017 06:08:12 AM UTC
|
||||
Install Reason : Explicitly installed
|
||||
Install Script : No
|
||||
Validated By : Signature
|
||||
|
||||
```
|
||||
|
||||
### [Apt-Cache 命令][10] ：在Debian/Ubuntu/Mint系统上查看包信息
|
||||
|
||||
|
||||
apt-cache命令能显示Apt内部数据库中的大量信息。这些信息是从sources.list中的不同的软件源中搜集而来，因此从某种意义上这些信息也可以被认为是某种缓存。
|
||||
这些信息搜集工作是在运行apt update命令时执行的。
|
||||
|
||||
```
|
||||
$ sudo apt-cache show apache2 （LCTT译注：用管理员权限查询apache2的信息）
|
||||
Package: apache2
|
||||
Priority: optional
|
||||
Section: web
|
||||
Installed-Size: 473
|
||||
Maintainer: Ubuntu Developers
|
||||
Original-Maintainer: Debian Apache Maintainers
|
||||
Architecture: amd64
|
||||
Version: 2.4.12-2ubuntu2
|
||||
Replaces: apache2.2-common
|
||||
Provides: httpd, httpd-cgi
|
||||
Depends: lsb-base, procps, perl, mime-support, apache2-bin (= 2.4.12-2ubuntu2), apache2-utils (>= 2.4), apache2-data (= 2.4.12-2ubuntu2)
|
||||
Pre-Depends: dpkg (>= 1.17.14)
|
||||
Recommends: ssl-cert
|
||||
Suggests: www-browser, apache2-doc, apache2-suexec-pristine | apache2-suexec-custom, ufw
|
||||
Conflicts: apache2.2-common (<< 2.3~)
|
||||
Filename: pool/main/a/apache2/apache2_2.4.12-2ubuntu2_amd64.deb
|
||||
Size: 91348
|
||||
MD5sum: ab0ee0b0d1c6b3d19bd87aa2a9537125
|
||||
SHA1: 350c9a1a954906088ed032aebb77de3d5bb24004
|
||||
SHA256: 03f515f7ebc3b67b050b06e82ebca34b5e83e34a528868498fce020bf1dbbe34
|
||||
Description-en: Apache HTTP Server
|
||||
The Apache HTTP Server Project's goal is to build a secure, efficient and
|
||||
extensible HTTP server as standards-compliant open source software. The
|
||||
result has long been the number one web server on the Internet.
|
||||
.
|
||||
Installing this package results in a full installation, including the
|
||||
configuration files, init scripts and support scripts.
|
||||
Description-md5: d02426bc360345e5acd45367716dc35c
|
||||
Homepage: http://httpd.apache.org/
|
||||
Bugs: https://bugs.launchpad.net/ubuntu/+filebug
|
||||
Origin: Ubuntu
|
||||
Supported: 9m
|
||||
Task: lamp-server, mythbuntu-frontend, mythbuntu-desktop, mythbuntu-backend-slave, mythbuntu-backend-master, mythbuntu-backend-master
|
||||
|
||||
```
|
||||
|
||||
### [APT 命令][11] : 查看Debian/Ubuntu/Mint系统上的包信息
|
||||
|
||||
|
||||
APT意为高级打包工具，就像DNF将如何替代YUM一样，APT是apt-get的替代物。它功能丰富的命令行工具包括了如下所有命令的功能如apt-cache,apt-search,dpkg, apt-cdrom, apt-config, apt-key等等，我们可以方便的通过apt来安装.dpkg包，但是我们却不能通过apt-get来完成这一点，还有一些其他的类似的功能也不能用apt-get来完成，所以apt-get因为没有解决上述功能缺乏的原因而被apt所取代。
|
||||
|
||||
```
|
||||
$ apt show nano （LCTT译注： 用apt show查看nano）
|
||||
Package: nano
|
||||
Version: 2.8.6-3
|
||||
Priority: standard
|
||||
Section: editors
|
||||
Origin: Ubuntu
|
||||
Maintainer: Ubuntu Developers
|
||||
Original-Maintainer: Jordi Mallach
|
||||
Bugs: https://bugs.launchpad.net/ubuntu/+filebug
|
||||
Installed-Size: 766 kB
|
||||
Depends: libc6 (>= 2.14), libncursesw5 (>= 6), libtinfo5 (>= 6)
|
||||
Suggests: spell
|
||||
Conflicts: pico
|
||||
Breaks: nano-tiny (<< 2.8.6-2)
|
||||
Replaces: nano-tiny (<< 2.8.6-2), pico
|
||||
Homepage: https://www.nano-editor.org/
|
||||
Task: standard, ubuntu-touch-core, ubuntu-touch
|
||||
Supported: 9m
|
||||
Download-Size: 222 kB
|
||||
APT-Manual-Installed: yes
|
||||
APT-Sources: http://in.archive.ubuntu.com/ubuntu artful/main amd64 Packages
|
||||
Description: small, friendly text editor inspired by Pico
|
||||
GNU nano is an easy-to-use text editor originally designed as a replacement
|
||||
for Pico, the ncurses-based editor from the non-free mailer package Pine
|
||||
(itself now available under the Apache License as Alpine).
|
||||
.
|
||||
However, GNU nano also implements many features missing in pico, including:
|
||||
- undo/redo
|
||||
- line numbering
|
||||
- syntax coloring
|
||||
- soft-wrapping of overlong lines
|
||||
- selecting text by holding Shift
|
||||
- interactive search and replace (with regular expression support)
|
||||
- a go-to line (and column) command
|
||||
- support for multiple file buffers
|
||||
- auto-indentation
|
||||
- tab completion of filenames and search terms
|
||||
- toggling features while running
|
||||
- and full internationalization support
|
||||
|
||||
```
|
||||
|
||||
### [dpkg 命令][12] : 查看Debian/Ubuntu/Mint系统上的包信息
|
||||
|
||||
|
||||
dpkg意指Debian包管理器（dpkg）。dpkg用于Debian系统上的安装，构建，移除以及管理Debian包的命令行工具。dpkg 使用Aptitude（因为它更为主流及用户友好）作为前端工具来完成所有的功能。其他的工具如dpkg-deb和dpkg-query使用dpkg做为前端来实现功能。尽管系统管理员还是时不时会在必要时使用dpkg来完成一些软件安装的任务，他大多数情况下还是会因为APt，Apt-Get以及Aptitude的健壮性而使用后者。
|
||||
|
||||
```
|
||||
$ dpkg -s python （LCTT译注： 用dpkg -s查看python）
|
||||
Package: python
|
||||
Status: install ok installed
|
||||
Priority: optional
|
||||
Section: python
|
||||
Installed-Size: 626
|
||||
Maintainer: Ubuntu Developers
|
||||
Architecture: amd64
|
||||
Multi-Arch: allowed
|
||||
Source: python-defaults
|
||||
Version: 2.7.14-2ubuntu1
|
||||
Replaces: python-dev (<< 2.6.5-2)
|
||||
Provides: python-ctypes, python-email, python-importlib, python-profiler, python-wsgiref
|
||||
Depends: python2.7 (>= 2.7.14-1~), libpython-stdlib (= 2.7.14-2ubuntu1)
|
||||
Pre-Depends: python-minimal (= 2.7.14-2ubuntu1)
|
||||
Suggests: python-doc (= 2.7.14-2ubuntu1), python-tk (>= 2.7.14-1~)
|
||||
Breaks: update-manager-core (<< 0.200.5-2)
|
||||
Conflicts: python-central (<< 0.5.5)
|
||||
Description: interactive high-level object-oriented language (default version)
|
||||
Python, the high-level, interactive object oriented language,
|
||||
includes an extensive class library with lots of goodies for
|
||||
network programming, system administration, sounds and graphics.
|
||||
.
|
||||
This package is a dependency package, which depends on Debian's default
|
||||
Python version (currently v2.7).
|
||||
Homepage: http://www.python.org/
|
||||
Original-Maintainer: Matthias Klose
|
||||
|
||||
```
|
||||
|
||||
|
||||
我们也可使用dpkg的‘-p’选项，这个选项提供和‘dpkg -s’相类似的信息，但是它还提供了包的校验值和包类型。
|
||||
|
||||
```
|
||||
$ dpkg -p python3 （LCTT译注： 用dpkg -p查看python3的信息）
|
||||
Package: python3
|
||||
Priority: important
|
||||
Section: python
|
||||
Installed-Size: 67
|
||||
Origin: Ubuntu
|
||||
Maintainer: Ubuntu Developers
|
||||
Bugs: https://bugs.launchpad.net/ubuntu/+filebug
|
||||
Architecture: amd64
|
||||
Multi-Arch: allowed
|
||||
Source: python3-defaults
|
||||
Version: 3.6.3-0ubuntu2
|
||||
Replaces: python3-minimal (<< 3.1.2-2)
|
||||
Provides: python3-profiler
|
||||
Depends: python3.6 (>= 3.6.3-1~), libpython3-stdlib (= 3.6.3-0ubuntu2), dh-python
|
||||
Pre-Depends: python3-minimal (= 3.6.3-0ubuntu2)
|
||||
Suggests: python3-doc (>= 3.6.3-0ubuntu2), python3-tk (>= 3.6.3-1~), python3-venv (>= 3.6.3-0ubuntu2)
|
||||
Filename: pool/main/p/python3-defaults/python3_3.6.3-0ubuntu2_amd64.deb
|
||||
Size: 8712
|
||||
MD5sum: a8bae494c6e5d1896287675faf40d373
|
||||
Description: interactive high-level object-oriented language (default python3 version)
|
||||
Original-Maintainer: Matthias Klose
|
||||
SHA1: 2daec885cea7d4dc83c284301c3bebf42b23e095
|
||||
SHA256: 865e509c91d2504a16c4b573dbe27e260c36fceec2add3fa43a30c1751d7e9bb
|
||||
Homepage: http://www.python.org/
|
||||
Task: minimal, ubuntu-core, ubuntu-core
|
||||
Description-md5: 950ebd8122c0a7340f0a740c295b9eab
|
||||
Supported: 9m
|
||||
|
||||
```
|
||||
|
||||
### Aptitude 命令 : 查看Debian/Ubuntu/Mint 系统上的包信息
|
||||
|
||||
|
||||
aptitude是Debian GNU/Linux包管理系统的面向文本的接口。它允许用户查看已安装的包的列表，以及完成诸如安装，升级，删除包之类的包管理任务。这些管理行为也能从图形接口来执行。
|
||||
|
||||
```
|
||||
$ aptitude show htop （LCTT译注： 用aptitude show查看htop信息）
|
||||
Package: htop
|
||||
Version: 2.0.2-1
|
||||
State: installed
|
||||
Automatically installed: no
|
||||
Priority: optional
|
||||
Section: universe/utils
|
||||
Maintainer: Ubuntu Developers
|
||||
Architecture: amd64
|
||||
Uncompressed Size: 216 k
|
||||
Depends: libc6 (>= 2.15), libncursesw5 (>= 6), libtinfo5 (>= 6)
|
||||
Suggests: lsof, strace
|
||||
Conflicts: htop:i386
|
||||
Description: interactive processes viewer
|
||||
Htop is an ncursed-based process viewer similar to top, but it allows one to scroll the list vertically and horizontally to see all processes and their full command lines.
|
||||
|
||||
Tasks related to processes (killing, renicing) can be done without entering their PIDs.
|
||||
Homepage: http://hisham.hm/htop/
|
||||
|
||||
```
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://www.2daygeek.com/how-to-view-detailed-information-about-a-package-in-linux/
|
||||
|
||||
作者：[Prakash Subramanian][a]
|
||||
选题：[lujun9972](https://github.com/lujun9972)
|
||||
译者：[DavidChenLiang](https://github.com/davidchenliang)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
||||
[a]:https://www.2daygeek.com/author/prakash/
|
||||
[1]:https://www.2daygeek.com/list-of-command-line-package-manager-for-linux/
|
||||
[2]:https://www.2daygeek.com/list-of-graphical-frontend-tool-for-linux-package-manager/
|
||||
[3]:https://www.2daygeek.com/how-to-search-if-a-package-is-available-on-your-linux-distribution-or-not/
|
||||
[4]:https://www.2daygeek.com/how-to-add-enable-disable-a-repository-dnf-yum-config-manager-on-linux/
|
||||
[5]:https://www.2daygeek.com/yum-command-examples-manage-packages-rhel-centos-systems/
|
||||
[6]:https://www.2daygeek.com/rpm-command-examples/
|
||||
[7]:https://www.2daygeek.com/dnf-command-examples-manage-packages-fedora-system/
|
||||
[8]:https://www.2daygeek.com/zypper-command-examples-manage-packages-opensuse-system/
|
||||
[9]:https://www.2daygeek.com/pacman-command-examples-manage-packages-arch-linux-system/
|
||||
[10]:https://www.2daygeek.com/apt-get-apt-cache-command-examples-manage-packages-debian-ubuntu-systems/
|
||||
[11]:https://www.2daygeek.com/apt-command-examples-manage-packages-debian-ubuntu-systems/
|
||||
[12]:https://www.2daygeek.com/dpkg-command-to-manage-packages-on-debian-ubuntu-linux-mint-systems/
|
||||
160
translated/tech/20180804 Installing Andriod on VirtualBox.md
Normal file
160
translated/tech/20180804 Installing Andriod on VirtualBox.md
Normal file
@ -0,0 +1,160 @@
|
||||
在VirtualBox中安装Andriod系统
|
||||
======
|
||||
|
||||
如果你正在开发安卓 app 应用，也许会遇到小麻烦。诚然，ios 移动开发有 macOS 系统平台为其提供友好便利性，安卓开发仅有支持少部分安卓系统（其中还包括可穿戴设备系统）的 Andriod Studio 工具。
|
||||
|
||||
毋庸置疑，所有的二进制工具、SDK 工具、开发框架工具以及调试器都会产生大量日志和其他各种文件来使得你的文件系统很混乱。一个有效的解决方法就是在 VirtualBox 中安装 Andriod 系统，这样还解决了 Andriod 开发中最为棘手问题之一——设备模拟器。你可以在该虚拟机里测试应用程序，也可以使用 Andriod 的内部功能。因此，让我们迫不及待的开始吧！
|
||||
|
||||
### 准备工作
|
||||
|
||||
首先，你需要在你的系统上安装 VirtualBox，可从[这里][1]下载 windows 版本、macOS 版本或者各种 Linux 版本的 VitualBox。然后，你需要一个能在 x86 平台运行的 Andriod 镜像，因为 VirtualBox 为虚拟机提供运行 x86 或者 x86_64（包括 AMD64）平台的功能。
|
||||
|
||||
虽然大部分 Andriod 设备都在 ARM 上运行，但我们依然可以在 x86 平台上获得 [Andriod 项目帮助][2]。这些优秀的开发者已经将 Andriod 移植到 x86 平台上运行（包括实体机和虚拟机），我们可以下载最新版本的 Andriod 7.1。你也可以用之前更为稳定的版本，本文写作时最新稳定版是 Andriod 6.0。
|
||||
|
||||
### 创建 VM 虚拟机
|
||||
|
||||
打开 VirtualBox，单击左上角的 ” 新建 ” 按钮，在弹出的窗口中选择 “ 类型：Linux ” ，然后根据下载的ISO镜像来确定版本，x86 对应 32-bit，x86_64 对应 64-bit，此处选择 Linux 2.6 / 3.x / 4.x (64-bit)。
|
||||
|
||||
RAM 大小设置 2 GB 到你系统能提供的最大内存之间。如果你想模拟真实的使用环境你可以设置 6 GB RAM和 32 GB ROM。
|
||||
|
||||
![][3]
|
||||
|
||||
![][4]
|
||||
|
||||
创建完成后，你还需要做一些设置，添加核心处理器，提高开机显示内存。在 VM 上打开设置选项，“ 设置 -> 系统 -> 处理器 ”，如果硬件条件允许，可以多分配一些处理器。
|
||||
|
||||
![][5]
|
||||
|
||||
在 “ 设置 -> 显示 -> 显存大小 ” 中，你可以分配一大块内存并开启 3D 加速功能。
|
||||
|
||||
![][6]
|
||||
|
||||
现在我们可以启动 VM 虚拟机了。
|
||||
|
||||
### 安装 Andriod
|
||||
|
||||
首次启动 VM 虚拟机，VirtualBox 会提示你需要提供启动媒介，选择之前下载好的Andriod 镜像。
|
||||
|
||||
![][7]
|
||||
|
||||
下一步，如果想长时间使用 Andriod，选择 Installation 选项，你也可以选择 Live 模式体验 Andriod 环境。
|
||||
|
||||
![][8]
|
||||
|
||||
##### 分区
|
||||
|
||||
分区是通过文本界面操作，并没有友好的 GUI 界面，所以每个操作都需要小心对待。例如，在首页中还没有创建分区并且只检测到很少的虚拟硬盘时显示如下。
|
||||
|
||||
![][9]
|
||||
|
||||
红色字母 C 和 D 提示 C 开头选项可以创建或者修改分区，D 开头选项可以检测设备。你可以选择 D 开头选项，然后它就会检测硬盘，也可不进行这步操作，因为在启动的时候它会自动检测。
|
||||
|
||||
我们选择 C 开头选项，在虚拟盘中创建分区。官方不推荐使用 GPT 格式，所以我们选择 No。
|
||||
|
||||
![][10]
|
||||
|
||||
现在你被引导到 fdisk 工具页面。
|
||||
|
||||
![][11]
|
||||
|
||||
为了简洁，我们就只创建一个较大的分区，使用方向键来选择 “ New ” ，然后选择“ Primary ”，确认。
|
||||
|
||||
![][12]
|
||||
|
||||
分区大小系统已经为你计算好了，确认。
|
||||
|
||||
![][13]
|
||||
|
||||
这个分区就是 Andriod 系统所在的分区，所以需要它是可启动的。选择 “ Bootable ”，然后 enter（上方表格中 Flags 标志下面会出现 boot 标志），进一步，选择 “ Write ” 选项，保存刚才的操作记录并写入分区表。
|
||||
|
||||
![][14]
|
||||
|
||||
现在你可以选择退出分区工具，然后继续安装过程。
|
||||
|
||||
![][15]
|
||||
|
||||
##### 文件系统格式化
|
||||
|
||||
在分区页面上会出现一个刚刚我们创建的分区，选择它并进入。
|
||||
|
||||
![][16]
|
||||
|
||||
选择 Ext4 文件系统，在下一页中选择 Yes 然后格式化开始。会提示是否安装 GRUB 引导工具以及是否允许在根目录 / 进行读写，都选择 Yes 。现在，安装进程开始。
|
||||
|
||||
安装完成后，当系统提示可以 reboot 的时候你可以 reboot 系统。在重启之前，你可以先关机，然后在 VitualBox 的 ” 设置 -> 存储 ” 中检查 Andriod iso 镜像是否还依附在虚拟机上，如果在，将它移除。
|
||||
|
||||
移除安装镜像并保存，再去启动 VM 虚拟机。
|
||||
|
||||
![][17]
|
||||
|
||||
##### 运行 Andriod
|
||||
|
||||
在 GRUB 引导界面，有 debug 模式和 normal 模式的选项。我们选择默认选项，如下图所示。
|
||||
|
||||
![][18]
|
||||
|
||||
如果一切正常，你将会看到如下界面：
|
||||
|
||||
![][19]
|
||||
|
||||
如今的 Andriod 系统使用触摸交互而不是鼠标。不过Andriod-x86 平台提供了鼠标操作支持，但开始时可能需要方向键来辅助操作。
|
||||
|
||||
![][20]
|
||||
|
||||
选择 “ Set up as new ” 选项，回车确认。
|
||||
|
||||
![][21]
|
||||
|
||||
在提示用谷歌账户登陆之前，系统检查更新并检测设备信息。你可以跳过这一步，直接去设置日期和时间、用户名等。
|
||||
|
||||
还有一些其他的选项，和让你选择创建一个新的 Andriod 设备类似。选择 “ I Agree ” 选项同意有关更新、服务等的 policy。
|
||||
|
||||
![][22]
|
||||
|
||||
在这之后，因为它是个虚拟机，所以可能需要添加额外的 email 账户来设置 “ On-body detection "，大部分的选项对我们来说都没有多大作用，因此可以选择 ” All Set “。
|
||||
|
||||
接下来，它会提示你选择家庭 App。这个根据个人需求选择。
|
||||
|
||||
![][23]
|
||||
|
||||
如果你需要在 VM 做一些交互测试，有个可触摸屏幕会提供很大的方便，因为那样才更接近真实使用环境。
|
||||
|
||||
希望这篇教程会给你带来帮助。如果还有类似的教程写作需求，欢迎联系我们。
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://linuxhint.com/install_android_virtualbox/
|
||||
|
||||
作者：[Ranvir Singh][a]
|
||||
选题：[lujun9972](https://github.com/lujun9972)
|
||||
译者：[jrglinux](https://github.com/jrglinux)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
||||
[a]:https://linuxhint.com/author/sranvir155/
|
||||
[1]:https://www.virtualbox.org/wiki/Downloads
|
||||
[2]:http://www.android-x86.org/
|
||||
[3]:https://linuxhint.com/wp-content/uploads/2018/08/a.png
|
||||
[4]:https://linuxhint.com/wp-content/uploads/2018/08/a1.png
|
||||
[5]:https://linuxhint.com/wp-content/uploads/2018/08/a2.png
|
||||
[6]:https://linuxhint.com/wp-content/uploads/2018/08/a3.png
|
||||
[7]:https://linuxhint.com/wp-content/uploads/2018/08/a4.png
|
||||
[8]:https://linuxhint.com/wp-content/uploads/2018/08/a5.png
|
||||
[9]:https://linuxhint.com/wp-content/uploads/2018/08/a6.png
|
||||
[10]:https://linuxhint.com/wp-content/uploads/2018/08/a7.png
|
||||
[11]:https://linuxhint.com/wp-content/uploads/2018/08/a8.png
|
||||
[12]:https://linuxhint.com/wp-content/uploads/2018/08/a9.png
|
||||
[13]:https://linuxhint.com/wp-content/uploads/2018/08/a10.png
|
||||
[14]:https://linuxhint.com/wp-content/uploads/2018/08/a11.png
|
||||
[15]:https://linuxhint.com/wp-content/uploads/2018/08/a12.png
|
||||
[16]:https://linuxhint.com/wp-content/uploads/2018/08/a13.png
|
||||
[17]:https://linuxhint.com/wp-content/uploads/2018/08/a14.png
|
||||
[18]:https://linuxhint.com/wp-content/uploads/2018/08/a16.png
|
||||
[19]:https://linuxhint.com/wp-content/uploads/2018/08/a17.png
|
||||
[20]:https://linuxhint.com/wp-content/uploads/2018/08/a18.png
|
||||
[21]:https://linuxhint.com/wp-content/uploads/2018/08/a19.png
|
||||
[22]:https://linuxhint.com/wp-content/uploads/2018/08/a20.png
|
||||
[23]:https://linuxhint.com/wp-content/uploads/2018/08/a21.png
|
||||
|
||||
|
||||
Loading…
Reference in New Issue
Block a user