mirror of
https://github.com/LCTT/TranslateProject.git
synced 2025-01-25 23:11:02 +08:00
struggling
commit
24f7ad7338
@ -1,27 +1,28 @@
|
||||
在 Ubuntu 和 Linux Mint 上安装 Terminator 0.98
|
||||
================================================================================
|
||||
[Terminator][1]，在一个窗口中有多个终端。该项目的目标之一是为管理终端提供一个有用的工具。它的灵感来自于类似 gnome-multi-term，quankonsole 等程序，这些程序关注于在窗格中管理终端。 Terminator 0.98 带来了更完美的标签功能，更好的布局保存/恢复，改进了偏好用户界面和多出 bug 修复。
|
||||
[Terminator][1]，它可以在一个窗口内打开多个终端。该项目的目标之一是为摆放终端提供一个有用的工具。它的灵感来自于类似 gnome-multi-term，quankonsole 等程序，这些程序关注于按网格摆放终端。 Terminator 0.98 带来了更完美的标签功能，更好的布局保存/恢复，改进了偏好用户界面和多处 bug 修复。
|
||||
|
||||
|
||||
|
||||
###TERMINATOR 0.98 的更改和新特性
|
||||
|
||||
- 添加了一个布局启动器，允许在不用布局之间简单切换（用 Alt + L 打开一个新的布局切换器）；
|
||||
- 添加了一个新的手册（使用 F1 打开）；
|
||||
- 保存的时候，布局现在会记住：
|
||||
- * 最大化和全屏状态
|
||||
- * 窗口标题
|
||||
- * 激活的标签
|
||||
- * 激活的终端
|
||||
- * 每个终端的工作目录
|
||||
- 添加选项用于启用/停用非同质标签和滚动箭头；
|
||||
- 最大化和全屏状态
|
||||
- 窗口标题
|
||||
- 激活的标签
|
||||
- 激活的终端
|
||||
- 每个终端的工作目录
|
||||
- 添加选项用于启用/停用非同类（non-homogenous）标签和滚动箭头；
|
||||
- 添加快捷键用于按行/半页/一页向上/下滚动;
|
||||
- 添加使用 Ctrl+鼠标滚轮放大/缩小，Shift+鼠标滚轮向上/下滚动页面；
|
||||
- 为下一个/上一个 profile 添加快捷键
|
||||
- 添加使用 Ctrl+鼠标滚轮来放大/缩小，Shift+鼠标滚轮向上/下滚动页面；
|
||||
- 为下一个/上一个配置文件（profile）添加快捷键
|
||||
- 改进自定义命令菜单的一致性
|
||||
- 新增快捷方式/代码来切换所有/标签分组;
|
||||
- 改进监视插件
|
||||
- 增加搜索栏切换；
|
||||
- 清理和重新组织窗口偏好，包括一个完整的全局便签更新
|
||||
- 清理和重新组织偏好（preferences）窗口，包括一个完整的全局便签更新
|
||||
- 添加选项用于设置 ActivityWatcher 插件静默时间
|
||||
- 其它一些改进和 bug 修复
|
||||
- [点击此处查看完整更新日志][2]
|
||||
@ -37,10 +38,6 @@ Terminator 0.98 有可用的 PPA，首先我们需要在 Ubuntu/Linux Mint 上
|
||||
如果你想要移除 Terminator，只需要在终端中运行下面的命令（可选）
|
||||
|
||||
$ sudo apt-get remove terminator
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
@ -48,7 +45,7 @@ via: http://www.ewikitech.com/articles/linux/terminator-install-ubuntu-linux-min
|
||||
|
||||
作者：[admin][a]
|
||||
译者：[ictlyh](http://mutouxiaogui.cn/blog)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
校对：[wxy](https://github.com/wxy)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创翻译，[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
||||
@ -1,10 +1,10 @@
|
||||
对 Linux 用户10个有用的工具
|
||||
10 个给 Linux 用户的有用工具
|
||||
================================================================================
|
||||
|
||||
|
||||
### 引言 ###
|
||||
|
||||
在本教程中，我已经收集了对 Linux 用户10个有用的工具，其中包括各种网络监控，系统审计和一些其它实用的命令，它可以帮助用户提高工作效率。我希望你会喜欢他们。
|
||||
在本教程中，我已经收集了10个给 Linux 用户的有用工具，其中包括各种网络监控，系统审计和一些其它实用的命令，它可以帮助用户提高工作效率。我希望你会喜欢他们。
|
||||
|
||||
#### 1. w ####
|
||||
|
||||
@ -14,19 +14,18 @@
|
||||
|
||||
|
||||
|
||||
显示帮助信息
|
||||
不显示头部信息（LCTT译注：原文此处有误）
|
||||
|
||||
$w -h
|
||||
|
||||
（LCTT译注：-h为不显示头部信息）
|
||||
|
||||
显示当前用户信息
|
||||
显示指定用户的信息
|
||||
|
||||
$w <username>
|
||||
|
||||
|
||||
|
||||
#### 2. nmon ####
|
||||
|
||||
Nmon（nigel’s monitor 的简写）是一个显示系统性能信息的工具。
|
||||
|
||||
$ sudo apt-get install nmon
|
||||
@ -37,7 +36,7 @@ Nmon（nigel’s monitor 的简写）是一个显示系统性能信息的工具
|
||||
|
||||
|
||||
|
||||
nmon 可以转储与 netwrok，cpu, memory 和磁盘使用情况的信息。
|
||||
nmon 可以显示与 netwrok，cpu, memory 和磁盘使用情况的信息。
|
||||
|
||||
**nmon 显示 cpu 信息 (按 c)**
|
||||
|
||||
@ -53,7 +52,7 @@ nmon 可以转储与 netwrok，cpu, memory 和磁盘使用情况的信息。
|
||||
|
||||
#### 3. ncdu ####
|
||||
|
||||
是一个基于‘du’的光标版本的命令行程序，这个命令是用来分析各种目录占用的磁盘空间。
|
||||
是一个支持光标的`du`程序，这个命令是用来分析各种目录占用的磁盘空间。
|
||||
|
||||
$apt-get install ncdu
|
||||
|
||||
@ -71,7 +70,7 @@ nmon 可以转储与 netwrok，cpu, memory 和磁盘使用情况的信息。
|
||||
|
||||
#### 4. slurm ####
|
||||
|
||||
一个基于网络接口的带宽监控命令行程序，它会基于图形来显示 ascii 文件。
|
||||
一个基于网络接口的带宽监控命令行程序，它会用字符来显示文本图形。
|
||||
|
||||
$ apt-get install slurm
|
||||
|
||||
@ -94,7 +93,7 @@ nmon 可以转储与 netwrok，cpu, memory 和磁盘使用情况的信息。
|
||||
|
||||
#### 5.findmnt ####
|
||||
|
||||
Findmnt 命令用于查找挂载的文件系统。它是用来列出安装设备，当需要时也可以挂载或卸载设备，它也是 util-linux 的一部分。
|
||||
Findmnt 命令用于查找挂载的文件系统。它用来列出安装设备，当需要时也可以挂载或卸载设备，它是 util-linux 软件包的一部分。
|
||||
|
||||
例子:
|
||||
|
||||
@ -122,7 +121,7 @@ Findmnt 命令用于查找挂载的文件系统。它是用来列出安装设备
|
||||
|
||||
#### 6. dstat ####
|
||||
|
||||
一种组合和灵活的工具，它可用于监控内存，进程，网络和磁盘的性能，它可以用来取代 ifstat, iostat, dmstat 等。
|
||||
一种灵活的组合工具，它可用于监控内存，进程，网络和磁盘性能，它可以用来取代 ifstat, iostat, dmstat 等。
|
||||
|
||||
$apt-get install dstat
|
||||
|
||||
@ -134,27 +133,27 @@ Findmnt 命令用于查找挂载的文件系统。它是用来列出安装设备
|
||||
|
||||
|
||||
|
||||
- **-c** cpu
|
||||
**-c** cpu
|
||||
|
||||
$ dstat -c
|
||||
|
||||
|
||||
|
||||
显示 cpu 的详细信息。
|
||||
|
||||
$ dstat -cdl -D sda1
|
||||
|
||||
|
||||
|
||||
- **-d** 磁盘
|
||||
**-d** 磁盘
|
||||
|
||||
$ dstat -d
|
||||
|
||||
|
||||
|
||||
显示 cpu、磁盘等的详细信息。
|
||||
|
||||
$ dstat -cdl -D sda1
|
||||
|
||||
|
||||
|
||||
#### 7. saidar ####
|
||||
|
||||
另一种基于 CLI 的系统统计数据监控工具，提供了有关磁盘使用，网络，内存，交换等信息。
|
||||
另一种基于命令行的系统统计数据监控工具，提供了有关磁盘使用，网络，内存，交换分区等信息。
|
||||
|
||||
$ sudo apt-get install saidar
|
||||
|
||||
@ -172,7 +171,7 @@ Findmnt 命令用于查找挂载的文件系统。它是用来列出安装设备
|
||||
|
||||
#### 8. ss ####
|
||||
|
||||
ss（socket statistics）是一个很好的选择来替代 netstat，它从内核空间收集信息，比 netstat 的性能更好。
|
||||
ss（socket statistics）是一个很好的替代 netstat 的选择，它从内核空间收集信息，比 netstat 的性能更好。
|
||||
|
||||
例如:
|
||||
|
||||
@ -196,7 +195,7 @@ ss（socket statistics）是一个很好的选择来替代 netstat，它从内
|
||||
|
||||
#### 9. ccze ####
|
||||
|
||||
一个自定义日志格式的工具 :).
|
||||
一个美化日志显示的工具 :).
|
||||
|
||||
$ apt-get install ccze
|
||||
|
||||
@ -222,7 +221,7 @@ ss（socket statistics）是一个很好的选择来替代 netstat，它从内
|
||||
|
||||
一种基于 Python 的终端工具，它可以用来以图形方式显示系统活动状态。详细信息以一个丰富多彩的柱状图来展示。
|
||||
|
||||
安装 python:
|
||||
安装 python（LCTT 译注：一般来说，你应该已经有了 python，不需要此步）：
|
||||
|
||||
$ sudo apt-add-repository ppa:fkrull/deadsnakes
|
||||
|
||||
@ -234,7 +233,7 @@ ss（socket statistics）是一个很好的选择来替代 netstat，它从内
|
||||
|
||||
$ sudo apt-get install python3.2
|
||||
|
||||
- [下载 ranwhen.py][1]
|
||||
[点此下载 ranwhen.py][1]
|
||||
|
||||
$ unzip ranwhen-master.zip && cd ranwhen-master
|
||||
|
||||
@ -246,7 +245,7 @@ ss（socket statistics）是一个很好的选择来替代 netstat，它从内
|
||||
|
||||
### 结论 ###
|
||||
|
||||
这都是些冷门但重要的 Linux 管理工具。他们可以在日常生活中帮助用户。在我们即将发表的文章中，我们会尽量多带来些管理员/用户工具。
|
||||
这都是些不常见但重要的 Linux 管理工具。他们可以在日常生活中帮助用户。在我们即将发表的文章中，我们会尽量多带来些管理员/用户工具。
|
||||
|
||||
玩得愉快！
|
||||
|
||||
@ -256,7 +255,7 @@ via: http://www.unixmen.com/10-useful-utilities-linux-users/
|
||||
|
||||
作者：[Rajneesh Upadhyay][a]
|
||||
译者：[strugglingyouth](https://github.com/strugglingyouth)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
校对：[wxy](https://github.com/wxy)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
||||
@ -1,8 +1,8 @@
|
||||
Mytodo： 为 DIY 爱好者准备的待办事项管理软件
|
||||
Mytodo：为 DIY 爱好者准备的待办事项管理软件
|
||||
================================================================================
|
||||
|
||||
|
||||
通常我关注的软件都是那些不用折腾并且易用的（对图形界面而言）。这就是我把 [Go For It][1] 待办事项程序归到 [Linux 生产力工具][2] 列表的原因。今天，我要向你们展示另一款待办事项列表应用，和其它的待办事项软件有点不一样。
|
||||
通常我关注的软件都是那些不用折腾并且易用的（对图形界面而言）。这就是我把 [Go For It][1] 待办事项程序归到 [Linux 产能工具][2] 列表的原因。今天，我要向你们展示另一款待办事项列表应用，和其它的待办事项软件有点不一样。
|
||||
|
||||
[Mytodo][3] 是个开源的待办事项列表程序，让你能够掌管一切。与其它类似的程序不同的是，Mytodo 更加面向 DIY 爱好者，因为它允许你配置服务器（如果你想在多台电脑上使用的话），除了主要的功能外还提供一个命令行界面。
|
||||
|
||||
@ -19,15 +19,15 @@ Mytodo 的一些主要特性：
|
||||
|
||||
|
||||
|
||||
图形界面
|
||||
*图形界面*
|
||||
|
||||
|
||||
|
||||
命令行
|
||||
*命令行*
|
||||
|
||||
|
||||
|
||||
Conky 显示着待办事项
|
||||
*Conky 显示着待办事项*
|
||||
|
||||
你可以在下面的 Github 链接里找到源码和配置介绍：
|
||||
|
||||
@ -43,13 +43,13 @@ via: http://itsfoss.com/mytodo-list-manager/
|
||||
|
||||
作者：[Abhishek][a]
|
||||
译者：[alim0x](https://github.com/alim0x)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
校对：[wxy](https://github.com/wxy)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
||||
[a]:http://itsfoss.com/author/abhishek/
|
||||
[1]:http://itsfoss.com/go-for-it-to-do-app-in-linux/
|
||||
[2]:http://itsfoss.com/productivity-tips-ubuntu/
|
||||
[2]:https://linux.cn/article-6425-1.html
|
||||
[3]:https://github.com/mohamed-aziz/mytodo
|
||||
[4]:http://itsfoss.com/conky-gui-ubuntu-1304/
|
||||
[5]:https://github.com/mohamed-aziz/mytodo
|
||||
@ -1,9 +1,9 @@
|
||||
Linux 中 df 命令的11个例子
|
||||
================================================================================
|
||||
|
||||
df（可用磁盘）命令用于显示文件系统的磁盘使用情况。默认情况下 df 命令将以 1KB 为单位进行显示所有当前已挂载的文件系统，如果你想以人类易读的格式显示 df 命令的输出，像这样“df -h”使用 -h 选项。
|
||||
df 即“可用磁盘”（disk free），用于显示文件系统的磁盘使用情况。默认情况下 df 命令将以每块 1K 的单位进行显示所有当前已挂载的文件系统，如果你想以人类易读的格式显示 df 命令的输出，像这样“df -h”使用 -h 选项。
|
||||
|
||||
在这篇文章中，我们将讨论 ‘**df**‘ 命令在 Linux 下11种不同的实例
|
||||
在这篇文章中，我们将讨论 `df` 命令在 Linux 下11种不同的实例。
|
||||
|
||||
在 Linux 下 df 命令的基本格式为：
|
||||
|
||||
@ -13,7 +13,7 @@ df（可用磁盘）命令用于显示文件系统的磁盘使用情况。默认
|
||||
|
||||
|
||||
|
||||
df 的原样输出 :
|
||||
df 的样例输出 :
|
||||
|
||||
[root@linux-world ~]# df
|
||||
Filesystem 1K-blocks Used Available Use% Mounted on
|
||||
@ -28,9 +28,9 @@ df 的原样输出 :
|
||||
/dev/mapper/vg00-sap 14987656 37636 14165636 1% /sap
|
||||
[root@linux-world ~]#
|
||||
|
||||
### 例1：使用 ‘-a’ 选项列出所有文件系统的磁盘使用量 ###
|
||||
### 例1：使用 -a 选项列出所有文件系统的磁盘使用量 ###
|
||||
|
||||
当我们在 df 命令中使用 ‘-a’ 选项时，它会显示所有文件系统的磁盘使用情况。
|
||||
当我们在 df 命令中使用 `-a` 选项时，它会显示所有文件系统的磁盘使用情况。
|
||||
|
||||
[root@linux-world ~]# df -a
|
||||
Filesystem 1K-blocks Used Available Use% Mounted on
|
||||
@ -69,7 +69,7 @@ df 的原样输出 :
|
||||
|
||||
### 例2：以人类易读的格式显示 df 命令的输出 ###
|
||||
|
||||
在 df 命令中使用‘-h’选项，输出以人易读的格式输出（例如，5K，500M ＆ 5G）
|
||||
在 df 命令中使用`-h`选项，以人类易读的格式输出（例如，5K，500M 及 5G）
|
||||
|
||||
[root@linux-world ~]# df -h
|
||||
Filesystem Size Used Avail Use% Mounted on
|
||||
@ -95,7 +95,7 @@ df 的原样输出 :
|
||||
|
||||
### 例4：输出所有已挂载文件系统的类型 ###
|
||||
|
||||
‘**-T**’ 选项用在 df 命令中用来显示文件系统的类型。
|
||||
`-T` 选项用在 df 命令中用来显示文件系统的类型。
|
||||
|
||||
[root@linux-world ~]# df -T
|
||||
Filesystem Type 1K-blocks Used Available Use% Mounted on
|
||||
@ -110,7 +110,7 @@ df 的原样输出 :
|
||||
/dev/mapper/vg00-sap ext3 14987656 37636 14165636 1% /sap
|
||||
[root@linux-world ~]#
|
||||
|
||||
### 例5：输出文件系统磁盘使用的块大小 ###
|
||||
### 例5：按块大小输出文件系统磁盘使用情况 ###
|
||||
|
||||
[root@linux-world ~]# df -k
|
||||
Filesystem 1K-blocks Used Available Use% Mounted on
|
||||
@ -127,7 +127,7 @@ df 的原样输出 :
|
||||
|
||||
### 例6：输出文件系统的 inode 信息 ###
|
||||
|
||||
‘**-i**’ 选项用在 df 命令用于显示文件系统的 inode 信息。
|
||||
`-i` 选项用在 df 命令用于显示文件系统的 inode 信息。
|
||||
|
||||
所有文件系统的 inode 信息：
|
||||
|
||||
@ -151,9 +151,9 @@ df 的原样输出 :
|
||||
/dev/mapper/vg00-sap 960992 11 960981 1% /sap
|
||||
[root@linux-world ~]#
|
||||
|
||||
### 例7：输出所有文件系统总的使用情况 ###
|
||||
### 例7：输出所有文件系统使用情况汇总 ###
|
||||
|
||||
‘–total‘ 选项在 df 命令中用于显示所有文件系统的磁盘使用情况。
|
||||
`-total` 选项在 df 命令中用于显示所有文件系统的磁盘使用情况汇总。
|
||||
|
||||
[root@linux-world ~]# df -h --total
|
||||
Filesystem Size Used Avail Use% Mounted on
|
||||
@ -171,7 +171,7 @@ df 的原样输出 :
|
||||
|
||||
### 例8：只打印本地文件系统磁盘的使用情况 ###
|
||||
|
||||
假设网络文件系统也挂载在 Linux 上，但我们只想显示本地文件系统的信息，这可以通过使用 df 命令的 ‘-l‘ 选项来实现。
|
||||
假设网络文件系统也挂载在 Linux 上，但我们只想显示本地文件系统的信息，这可以通过使用 df 命令的 `-l` 选项来实现。
|
||||
|
||||
|
||||
|
||||
@ -192,7 +192,7 @@ df 的原样输出 :
|
||||
|
||||
### 例9：打印特定文件系统类型的磁盘使用情况 ###
|
||||
|
||||
‘**-t**’ 选项在 df 命令中用来打印特定文件系统类型的信息，‘-t’ 指定文件系统的类型，如下所示：
|
||||
`-t` 选项在 df 命令中用来打印特定文件系统类型的信息，用 `-t` 指定文件系统的类型，如下所示：
|
||||
|
||||
对于 ext4 :
|
||||
|
||||
@ -209,11 +209,11 @@ df 的原样输出 :
|
||||
192.168.1.5:/opensuse 301545472 266833920 19371008 94% /data
|
||||
[root@linux-world ~]#
|
||||
|
||||
### 例10：使用 ‘-x’ 选项排除特定的文件系统类型 ###
|
||||
### 例10：使用 -x 选项排除特定的文件系统类型 ###
|
||||
|
||||
“**-x** 或 **–exclude-type**” 在 df 命令中用来在输出中排出某些文件系统类型。
|
||||
`-x` 或 `–exclude-type` 在 df 命令中用来在输出中排出某些文件系统类型。
|
||||
|
||||
假设我们想打印排出 ext3 外所有的文件系统。
|
||||
假设我们想打印除 ext3 外所有的文件系统。
|
||||
|
||||
[root@linux-world ~]# df -x ext3
|
||||
Filesystem 1K-blocks Used Available Use% Mounted on
|
||||
@ -228,9 +228,9 @@ df 的原样输出 :
|
||||
|
||||
### 例11：在 df 命令的输出中只打印特定的字段 ###
|
||||
|
||||
‘**–output={field_name1,field_name2….}**‘ 选项用于显示 df 命令某些字段的输出。
|
||||
`-output={field_name1,field_name2...}` 选项用于显示 df 命令某些字段的输出。
|
||||
|
||||
可用的字段名有: ‘source’, ‘fstype’, ‘itotal’, ‘iused’, ‘iavail’, ‘ipcent’, ‘size’, ‘used’, ‘avail’, ‘pcent’ 和 ‘target’
|
||||
可用的字段名有: `source`, `fstype`, `itotal`, `iused`, `iavail`, `ipcent`, `size`, `used`, `avail`, `pcent` 和 `target`
|
||||
|
||||
[root@linux-world ~]# df --output=fstype,size,iused
|
||||
Type 1K-blocks IUsed
|
||||
@ -252,7 +252,7 @@ via: http://www.linuxtechi.com/11-df-command-examples-in-linux/
|
||||
|
||||
作者：[Pradeep Kumar][a]
|
||||
译者：[strugglingyouth](https://github.com/strugglingyouth)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
校对：[wxy](https://github.com/wxy)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
||||
@ -1,53 +1,51 @@
|
||||
|
||||
在 Linux 中如何使用 ‘Mdadm’ 工具管理软件 RAID - 第9部分
|
||||
在 Linux 下使用 RAID（九）：如何使用 ‘Mdadm’ 工具管理软件 RAID
|
||||
================================================================================
|
||||
|
||||
无论你以前有没有使用 RAID 阵列的经验，以及是否完成了 [此 RAID 系列][1] 的所有教程，一旦你在 Linux 中熟悉了 `mdadm --manage` 命令的使用，管理软件 RAID 将不是很复杂的任务。
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
在 Linux 中使用 mdadm 管理 RAID 设备 - 第9部分
|
||||
*在 Linux 中使用 mdadm 管理 RAID 设备 - 第9部分*
|
||||
|
||||
在本教程中，我们会再介绍此工具提供的功能，这样当你需要它，就可以派上用场。
|
||||
|
||||
#### RAID 测试方案 ####
|
||||
|
||||
在本系列的最后一篇文章中，我们将使用一个简单的 RAID 1（镜像）阵列，它由两个 8GB 的磁盘（/dev/sdb 和 /dev/sdc）和一个备用设备（dev/sdd）来演示，但在此使用的方法也适用于其他类型的配置。也就是说，放心去用吧，把这个页面添加到浏览器的书签，然后让我们开始吧。
|
||||
在本系列的最后一篇文章中，我们将使用一个简单的 RAID 1（镜像）阵列，它由两个 8GB 的磁盘（/dev/sdb 和 /dev/sdc）和一个备用设备（/dev/sdd）来演示，但在此使用的方法也适用于其他类型的配置。也就是说，放心去用吧，把这个页面添加到浏览器的书签，然后让我们开始吧。
|
||||
|
||||
### 了解 mdadm 的选项和使用方法 ###
|
||||
|
||||
幸运的是，mdadm 有一个 `built-in --help` 参数来对每个主要的选项提供说明文档。
|
||||
幸运的是，mdadm 有一个内建的 `--help` 参数来对每个主要的选项提供说明文档。
|
||||
|
||||
因此，让我们开始使用：
|
||||
因此，让我们开始输入：
|
||||
|
||||
# mdadm --manage --help
|
||||
|
||||
`mdadm --manage` 将使我们看到能够执行哪些任务：
|
||||
就会使我们看到 `mdadm --manage` 能够执行哪些任务：
|
||||
|
||||
|
||||
|
||||
使用 mdadm 工具来管理 RAID
|
||||
*使用 mdadm 工具来管理 RAID*
|
||||
|
||||
正如我们在上面的图片看到，管理一个 RAID 阵列可以在任意时间执行以下任务：
|
||||
|
||||
- (重新)将设备添加到阵列中.
|
||||
- 把设备标记为故障.
|
||||
- 从阵列中删除故障设备.
|
||||
- 使用备用设备更换故障设备.
|
||||
- 先创建部分阵列.
|
||||
- 停止阵列.
|
||||
- 标记阵列为 ro（只读）或 rw（读写）.
|
||||
- （重新）将设备添加到阵列中
|
||||
- 把设备标记为故障
|
||||
- 从阵列中删除故障设备
|
||||
- 使用备用设备更换故障设备
|
||||
- 先创建部分阵列
|
||||
- 停止阵列
|
||||
- 标记阵列为 ro（只读）或 rw（读写）
|
||||
|
||||
### 使用 mdadm 工具管理 RAID 设备 ###
|
||||
|
||||
需要注意的是，如果用户忽略 `--manage` 选项，mdadm 默认使用管理模式。请记住这其实一点，以避免出现最坏的情况。
|
||||
需要注意的是，如果用户忽略 `--manage` 选项，mdadm 默认使用管理模式。请记住这一点，以避免出现最坏的情况。
|
||||
|
||||
上面图像中的高亮文本显示了管理 RAIDs 的基本的语法：
|
||||
上图中的高亮文本显示了管理 RAID 的基本语法：
|
||||
|
||||
# mdadm --manage RAID options devices
|
||||
|
||||
让我们来演示几个例子.
|
||||
让我们来演示几个例子。
|
||||
|
||||
#### 例1：为 RAID 阵列添加设备 ####
|
||||
|
||||
@ -57,11 +55,11 @@
|
||||
|
||||
|
||||
|
||||
添加设备到 Raid 阵列
|
||||
*添加设备到 Raid 阵列*
|
||||
|
||||
#### 例2：把一个 RAID 设备标记为故障并从阵列中移除 ####
|
||||
|
||||
在从逻辑阵列中删除该设备前，这是强制性的一步，然后从机器中取出它 - 注意顺序（如果弄错了这些步骤，最终可能会造成实际设备的损害）：
|
||||
在从逻辑阵列中删除该设备前，这是强制性的步骤，然后才能从机器中取出它 - 注意顺序（如果弄错了这些步骤，最终可能会造成实际设备的损害）：
|
||||
|
||||
# mdadm --manage /dev/md0 --fail /dev/sdb1
|
||||
|
||||
@ -69,21 +67,23 @@
|
||||
|
||||
|
||||
|
||||
恢复和重建 raid 数据
|
||||
*恢复和重建 raid 数据*
|
||||
|
||||
一旦设备已被手动标记为故障，你就可以安全地从阵列中删除它：
|
||||
|
||||
# mdadm --manage /dev/md0 --remove /dev/sdb1
|
||||
|
||||
#### 例3：重新添加设备，这是阵列中已经移除的一部分 ####
|
||||
#### 例3：重新添加设备，来替代阵列中已经移除的设备 ####
|
||||
|
||||
到现在为止，我们有一个工作的 RAID 1 阵列，它包含了2个活动的设备：/dev/sdc1 和 /dev/sdd1。现在让我们试图重新添加 /dev/sdb1 到/dev/md0：
|
||||
到现在为止，我们有一个工作的 RAID 1 阵列，它包含了2个活动的设备：/dev/sdc1 和 /dev/sdd1。现在让我们试试重新添加 /dev/sdb1 到/dev/md0：
|
||||
|
||||
# mdadm --manage /dev/md0 --re-add /dev/sdb1
|
||||
|
||||
我们会碰到一个错误:
|
||||
|
||||
mdadm: --re-add 将 /dev/sdb1 添加到 /dev/md0 是不可能的，因为阵列中的磁盘已经达到了最大的数量。因此，我们有两个选择：a）将 /dev/sdb1 添加为备用的，如例1，或 b）从阵列中删除 /dev/sdd1 然后重新添加 /dev/sdb1。
|
||||
# mdadm: --re-add for /dev/sdb1 to /dev/md0 is not possible
|
||||
|
||||
因为阵列中的磁盘已经达到了最大的数量。因此，我们有两个选择：a）将 /dev/sdb1 添加为备用的，如例1；或 b）从阵列中删除 /dev/sdd1 然后重新添加 /dev/sdb1。
|
||||
|
||||
我们选择选项 b），先停止阵列然后重新启动：
|
||||
|
||||
@ -96,7 +96,7 @@ mdadm 能检测到新添加的设备并将其作为备用设备，当添加完
|
||||
|
||||
|
||||
|
||||
重建 Raid 的状态
|
||||
*重建 Raid 的状态*
|
||||
|
||||
#### 例4：使用特定磁盘更换 RAID 设备 ####
|
||||
|
||||
@ -106,19 +106,19 @@ mdadm 能检测到新添加的设备并将其作为备用设备，当添加完
|
||||
|
||||
|
||||
|
||||
更换 Raid 设备
|
||||
*更换 Raid 设备*
|
||||
|
||||
当磁盘通过 `--replace` 被标记为故障时，这将导致设备通过 `--with` 被添加到 RAID 中：
|
||||
这会导致 `--replace` 指定的设备被标记为故障，而 `--with`指定的设备添加到 RAID 中来替代它：
|
||||
|
||||
|
||||
|
||||
检查 Raid 重建状态
|
||||
*检查 Raid 重建状态*
|
||||
|
||||
#### 例5：标记 RAID 阵列为 ro 或 rw ####
|
||||
|
||||
创建阵列后，你必须在它上面创建一个文件系统并将其挂载到一个目录下才能使用它。你可能不知道，RAID 也可以被设置为 ro，然后它就只读了，或者设置为 rw，然后就能进行写入设备以及读取操作。
|
||||
创建阵列后，你必须在它上面创建一个文件系统并将其挂载到一个目录下才能使用它。你可能不知道，RAID 也可以被设置为 ro，使其只读；或者设置为 rw，就可以同时写入了。
|
||||
|
||||
为了标记该设备为 ro，首先需要将其卸载：
|
||||
要标记该设备为 ro，首先需要将其卸载：
|
||||
|
||||
# umount /mnt/raid1
|
||||
# mdadm --manage /dev/md0 --readonly
|
||||
@ -127,7 +127,7 @@ mdadm 能检测到新添加的设备并将其作为备用设备，当添加完
|
||||
|
||||
|
||||
|
||||
在 RAID 阵列上设置权限
|
||||
*在 RAID 阵列上设置权限*
|
||||
|
||||
要配置阵列允许写入操作需要使用 `--readwrite` 选项。请注意，在设置 rw 标志前，你需要先卸载设备并停止它：
|
||||
|
||||
@ -139,23 +139,24 @@ mdadm 能检测到新添加的设备并将其作为备用设备，当添加完
|
||||
|
||||
|
||||
|
||||
配置 Raid 允许读写操作
|
||||
*配置 Raid 允许读写操作*
|
||||
|
||||
### 总结 ###
|
||||
|
||||
在本系列中，我们已经解释了如何建立一个在企业环境中使用的软件RAID 阵列。如果你按照这些文章所提供的例子进行配置，在 Linux 中你会充分利用软件 RAID 的价值。
|
||||
在本系列中，我们已经解释了如何建立一个在企业环境中使用的软件 RAID 阵列。如果你按照这些文章所提供的例子进行配置，在 Linux 中你会充分领会到软件 RAID 的价值。
|
||||
|
||||
如果你碰巧任何问题或有建议，请随时使用下面的方式与我们联系。
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: http://www.tecmint.com/manage-software-raid-devices-in-linux-with-mdadm/
|
||||
|
||||
作者：[GABRIEL CÁNEPA][a]
|
||||
译者：[strugglingyouth](https://github.com/strugglingyouth)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
校对：[wxy](https://github.com/wxy)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
||||
[a]:http://www.tecmint.com/author/gacanepa/
|
||||
[1]:http://www.tecmint.com/understanding-raid-setup-in-linux/
|
||||
[2]:http://www.tecmint.com/recover-data-and-rebuild-failed-software-raid/
|
||||
[1]:https://linux.cn/article-6085-1.html
|
||||
[2]:https://linux.cn/article-6448-1.html
|
||||
@ -1,16 +1,17 @@
|
||||
RHCE 第二部分 - 如何进行包过滤、网络地址转换和设置内核运行时参数
|
||||
RHCE 系列（二）：如何进行包过滤、网络地址转换和设置内核运行时参数
|
||||
================================================================================
|
||||
正如第一部分（“[设置静态网络路由][1]”）承诺的，在这篇文章（RHCE 系列第二部分），我们首先介绍红帽企业版 Linux 7中包过滤和网络地址转换原理，然后再介绍某些条件发送变化或者需要激活时设置运行时内核参数以改变运行时内核行为。
|
||||
|
||||
正如第一部分（“[设置静态网络路由][1]”）提到的，在这篇文章（RHCE 系列第二部分），我们首先介绍红帽企业版 Linux 7（RHEL）中包过滤和网络地址转换（NAT）的原理，然后再介绍在某些条件发生变化或者需要变动时设置运行时内核参数以改变运行时内核行为。
|
||||
|
||||
|
||||
|
||||
RHCE 第二部分：网络包过滤
|
||||
*RHCE 第二部分：网络包过滤*
|
||||
|
||||
### RHEL 7 中的网络包过滤 ###
|
||||
|
||||
当我们讨论数据包过滤的时候，我们指防火墙读取每个尝试通过它的数据包的包头所进行的处理。然后，根据系统管理员之前定义的规则，通过采取所要求的动作过滤数据包。
|
||||
当我们讨论数据包过滤的时候，我们指防火墙读取每个试图通过它的数据包的包头所进行的处理。然后，根据系统管理员之前定义的规则，通过采取所要求的动作过滤数据包。
|
||||
|
||||
正如你可能知道的，从 RHEL 7 开始，管理防火墙的默认服务是 [firewalld][2]。类似 iptables，它和 Linux 内核的 netfilter 模块交互以便检查和操作网络数据包。不像 iptables，Firewalld 的更新可以立即生效，而不用中断活跃的连接 - 你甚至不需要重启服务。
|
||||
正如你可能知道的，从 RHEL 7 开始，管理防火墙的默认服务是 [firewalld][2]。类似 iptables，它和 Linux 内核的 netfilter 模块交互以便检查和操作网络数据包。但不像 iptables，Firewalld 的更新可以立即生效，而不用中断活跃的连接 - 你甚至不需要重启服务。
|
||||
|
||||
Firewalld 的另一个优势是它允许我们定义基于预配置服务名称的规则（之后会详细介绍）。
|
||||
|
||||
@ -18,27 +19,27 @@ Firewalld 的另一个优势是它允许我们定义基于预配置服务名称
|
||||
|
||||
|
||||
|
||||
静态路由网络示意图
|
||||
*静态路由网络示意图*
|
||||
|
||||
然而，你应该记得，由于还没有介绍包过滤，为了简化例子，我们停用了路由器 2号 的防火墙。现在让我们来看看如何可以使接收的数据包发送到目的地的特定服务或端口。
|
||||
然而，你应该记得，由于还没有介绍包过滤，为了简化例子，我们停用了2号路由器的防火墙。现在让我们来看看如何使接收的数据包发送到目的地的特定服务或端口。
|
||||
|
||||
首先，让我们添加一条永久规则允许从 enp0s3 (192.168.0.19) 到 enp0s8 (10.0.0.18) 的绑定流量：
|
||||
首先，让我们添加一条永久规则允许从 enp0s3 (192.168.0.19) 到 enp0s8 (10.0.0.18) 的入站流量：
|
||||
|
||||
# firewall-cmd --permanent --direct --add-rule ipv4 filter FORWARD 0 -i enp0s3 -o enp0s8 -j ACCEPT
|
||||
|
||||
上面的命令会把规则保存到 /etc/firewalld/direct.xml：
|
||||
上面的命令会把规则保存到 `/etc/firewalld/direct.xml` 中：
|
||||
|
||||
# cat /etc/firewalld/direct.xml
|
||||
|
||||
|
||||
|
||||
检查 Firewalld 保存的规则
|
||||
*检查 Firewalld 保存的规则*
|
||||
|
||||
然后启用规则使其立即生效：
|
||||
|
||||
# firewall-cmd --direct --add-rule ipv4 filter FORWARD 0 -i enp0s3 -o enp0s8 -j ACCEPT
|
||||
|
||||
现在你可以从 RHEL 7 中通过 telnet 登录到 web 服务器并再次运行 [tcpdump][3] 监视两台机器之间的 TCP 流量，这次路由器 2号已经启用了防火墙。
|
||||
现在你可以从 RHEL 7 中通过 telnet 到 web 服务器并再次运行 [tcpdump][3] 监视两台机器之间的 TCP 流量，这次2号路由器已经启用了防火墙。
|
||||
|
||||
# telnet 10.0.0.20 80
|
||||
# tcpdump -qnnvvv -i enp0s3 host 10.0.0.20
|
||||
@ -61,19 +62,19 @@ Firewalld 的另一个优势是它允许我们定义基于预配置服务名称
|
||||
|
||||
我强烈建议你看看 Fedora Project Wiki 中的 [Firewalld Rich Language][4] 文档更详细地了解关于富规则的内容。
|
||||
|
||||
### RHEL 7 中的网络地址转换 ###
|
||||
### RHEL 7 中的网络地址转换（NAT） ###
|
||||
|
||||
网络地址转换（NAT）是为专用网络中的一组计算机（也可能是其中的一台）分配一个独立的公共 IP 地址的过程。结果，在内部网络中仍然可以用它们自己的私有 IP 地址区别，但外部“看来”它们是一样的。
|
||||
网络地址转换（NAT）是为专用网络中的一组计算机（也可能是其中的一台）分配一个独立的公共 IP 地址的过程。这样，在内部网络中仍然可以用它们自己的私有 IP 地址来区别，但外部“看来”它们是一样的。
|
||||
|
||||
另外，网络地址转换使得内部网络中的计算机发送请求到外部资源（例如因特网）然后只有源系统能接收到对应的响应成为可能。
|
||||
另外，网络地址转换使得内部网络中的计算机发送请求到外部资源（例如因特网），然后只有源系统能接收到对应的响应成为可能。
|
||||
|
||||
现在让我们考虑下面的场景：
|
||||
|
||||
|
||||
|
||||
网络地址转换
|
||||
*网络地址转换*
|
||||
|
||||
在路由器 2 中，我们会把 enp0s3 接口移动到外部区域，enp0s8 到内部区域，伪装或者说 NAT 默认是启用的：
|
||||
在2号路由器中，我们会把 enp0s3 接口移动到外部区域（external），enp0s8 到内部区域（external），伪装（masquerading）或者说 NAT 默认是启用的：
|
||||
|
||||
# firewall-cmd --list-all --zone=external
|
||||
# firewall-cmd --change-interface=enp0s3 --zone=external
|
||||
@ -81,7 +82,7 @@ Firewalld 的另一个优势是它允许我们定义基于预配置服务名称
|
||||
# firewall-cmd --change-interface=enp0s8 --zone=internal
|
||||
# firewall-cmd --change-interface=enp0s8 --zone=internal --permanent
|
||||
|
||||
对于我们当前的设置，内部区域 - 以及和它一起启用的任何东西都是默认区域：
|
||||
对于我们当前的设置，内部区域（internal） - 以及和它一起启用的任何东西都是默认区域：
|
||||
|
||||
# firewall-cmd --set-default-zone=internal
|
||||
|
||||
@ -89,44 +90,44 @@ Firewalld 的另一个优势是它允许我们定义基于预配置服务名称
|
||||
|
||||
# firewall-cmd --reload
|
||||
|
||||
最后，在 web 服务器中添加路由器 2 为默认网关：
|
||||
最后，在 web 服务器中添加2号路由器为默认网关：
|
||||
|
||||
# ip route add default via 10.0.0.18
|
||||
|
||||
现在你会发现在 web 服务器中你可以 ping 路由器 1 和外部网站（例如 tecmint.com）：
|
||||
现在你会发现在 web 服务器中你可以 ping 1号路由器和外部网站（例如 tecmint.com）：
|
||||
|
||||
# ping -c 2 192.168.0.1
|
||||
# ping -c 2 tecmint.com
|
||||
|
||||
|
||||
|
||||
验证网络路由
|
||||
*验证网络路由*
|
||||
|
||||
### 在 RHEL 7 中设置内核运行时参数 ###
|
||||
|
||||
在 Linux 中，允许你更改、启用以及停用内核运行时参数，RHEL 也不例外。/proc/sys 接口允许你当操作条件发生变化时实时设置运行时参数以改变系统行为而不需太多麻烦。
|
||||
在 Linux 中，允许你更改、启用以及停用内核运行时参数，RHEL 也不例外。当操作条件发生变化时，`/proc/sys` 接口（sysctl）允许你实时设置运行时参数改变系统行为，而不需太多麻烦。
|
||||
|
||||
为了实现这个目的，会用内建的 echo shell 写 /proc/sys/<category\> 中的文件，其中 <category\> 很可能是以下目录中的一个：
|
||||
为了实现这个目的，会用 shell 内建的 echo 写 `/proc/sys/<category>` 中的文件，其中 `<category>` 一般是以下目录中的一个：
|
||||
|
||||
- dev: 连接到机器中的特定设备的参数。
|
||||
- fs: 文件系统配置（例如 quotas 和 inodes）。
|
||||
- kernel: 内核配置。
|
||||
- net: 网络配置。
|
||||
- vm: 内核虚拟内存的使用。
|
||||
- vm: 内核的虚拟内存的使用。
|
||||
|
||||
要显示所有当前可用值的列表，运行
|
||||
|
||||
# sysctl -a | less
|
||||
|
||||
在第一部分中，我们通过以下命令改变了 net.ipv4.ip_forward 参数的值以允许 Linux 机器作为一个路由器。
|
||||
在第一部分中，我们通过以下命令改变了 `net.ipv4.ip_forward` 参数的值以允许 Linux 机器作为一个路由器。
|
||||
|
||||
# echo 1 > /proc/sys/net/ipv4/ip_forward
|
||||
|
||||
另一个你可能想要设置的运行时参数是 kernel.sysrq，它会启用你键盘上的 Sysrq 键，以使系统更好的运行一些底层函数，例如如果由于某些原因冻结了后重启系统：
|
||||
另一个你可能想要设置的运行时参数是 `kernel.sysrq`，它会启用你键盘上的 `Sysrq` 键，以使系统更好的运行一些底层功能，例如如果由于某些原因冻结了后重启系统：
|
||||
|
||||
# echo 1 > /proc/sys/kernel/sysrq
|
||||
|
||||
要显示特定参数的值，可以按照下面方式使用 sysctl：
|
||||
要显示特定参数的值，可以按照下面方式使用 `sysctl`：
|
||||
|
||||
# sysctl <parameter.name>
|
||||
|
||||
@ -135,28 +136,29 @@ Firewalld 的另一个优势是它允许我们定义基于预配置服务名称
|
||||
# sysctl net.ipv4.ip_forward
|
||||
# sysctl kernel.sysrq
|
||||
|
||||
一些参数，例如上面提到的一个，只需要一个值，而其它一些（例如 fs.inode-state）要求多个值：
|
||||
有些参数，例如上面提到的某个，只需要一个值，而其它一些（例如 `fs.inode-state`）要求多个值：
|
||||
|
||||
|
||||
|
||||
查看内核参数
|
||||
*查看内核参数*
|
||||
|
||||
不管什么情况下，做任何更改之前你都需要阅读内核文档。
|
||||
|
||||
请注意系统重启后这些设置会丢失。要使这些更改永久生效，我们需要添加内容到 /etc/sysctl.d 目录的 .conf 文件，像下面这样：
|
||||
请注意系统重启后这些设置会丢失。要使这些更改永久生效，我们需要添加内容到 `/etc/sysctl.d` 目录的 .conf 文件，像下面这样：
|
||||
|
||||
# echo "net.ipv4.ip_forward = 1" > /etc/sysctl.d/10-forward.conf
|
||||
|
||||
（其中数字 10 表示相对同一个目录中其它文件的处理顺序）。
|
||||
|
||||
并用下面命令启用更改
|
||||
并用下面命令启用更改：
|
||||
|
||||
# sysctl -p /etc/sysctl.d/10-forward.conf
|
||||
|
||||
### 总结 ###
|
||||
|
||||
在这篇指南中我们解释了基本的包过滤、网络地址变换和在运行的系统中设置内核运行时参数并使重启后能持久化。我希望这些信息能对你有用，如往常一样，我们期望收到你的回复！
|
||||
别犹豫，在下面的表格中和我们分享你的疑问、评论和建议吧。
|
||||
|
||||
别犹豫，在下面的表单中和我们分享你的疑问、评论和建议吧。
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
@ -164,12 +166,12 @@ via: http://www.tecmint.com/perform-packet-filtering-network-address-translation
|
||||
|
||||
作者：[Gabriel Cánepa][a]
|
||||
译者：[ictlyh](https://github.com/ictlyh)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
校对：[wxy](https://github.com/wxy)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创翻译，[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
||||
[a]:http://www.tecmint.com/author/gacanepa/
|
||||
[1]:http://www.tecmint.com/how-to-setup-and-configure-static-network-routing-in-rhel/
|
||||
[1]:https://linux.cn/article-6451-1.html
|
||||
[2]:http://www.tecmint.com/firewalld-rules-for-centos-7/
|
||||
[3]:http://www.tecmint.com/12-tcpdump-commands-a-network-sniffer-tool/
|
||||
[4]:https://fedoraproject.org/wiki/Features/FirewalldRichLanguage
|
||||
@ -1,3 +1,5 @@
|
||||
martin translating...
|
||||
|
||||
Superclass: 15 of the world’s best living programmers
|
||||
================================================================================
|
||||
When developers discuss who the world’s top programmer is, these names tend to come up a lot.
|
||||
@ -386,4 +388,4 @@ via: http://www.itworld.com/article/2823547/enterprise-software/158256-superclas
|
||||
[131]:http://community.topcoder.com/tc?module=AlgoRank
|
||||
[132]:http://www.quora.com/Computer-Programming/Who-is-the-best-programmer-in-the-world-right-now/answer/Prateek-Joshi
|
||||
[133]:http://www.quora.com/Computer-Programming/Who-is-the-best-programmer-in-the-world-right-now/answer/Prateek-Joshi/comment/4720779
|
||||
[134]:http://www.quora.com/Computer-Programming/Who-is-the-best-programmer-in-the-world-right-now/answer/Prateek-Joshi/comment/4880549
|
||||
[134]:http://www.quora.com/Computer-Programming/Who-is-the-best-programmer-in-the-world-right-now/answer/Prateek-Joshi/comment/4880549
|
||||
|
||||
@ -1,38 +0,0 @@
|
||||
ictlyh Translating
|
||||
Red Hat CEO Optimistic on OpenStack Revenue Opportunity
|
||||
================================================================================
|
||||
Red Hat continues to accelerate its growth thanks to an evolving mix of platform and infrastructure technology revolving around Linux and the cloud. Red Hat announced its second quarter fiscal 2016 financial results on September 21, once again exceeding expectations.
|
||||
|
||||
|
||||
|
||||
For the quarter, Red Hat reported revenue of $504 million for a 13 percent year-over-year gain. Net Income was reported at $51 million, up from $47 Red Hatmillion in the second quarter of fiscal 2015. Looking forward, Red Hat provided some aggressive guidance for the coming quarter and the full year. For the third quarter, Red Hat provided guidance for revenue to be in the range of $519 million to $523 million, which is a 15 percent year-over-year gain.
|
||||
|
||||
On a full year basis, Red Hat's full year guidance is for fiscal 2016 revenue of $2.044 billion, for a 14 percent year-over-year gain.
|
||||
|
||||
Red Hat CFO Frank Calderoni commented during the earnings call that all of Red Hat's top 30 largest deals were approximately $1 million or more. He noted that Red Hat had four deals that were in excess of $5 million and one deal that was well over $10 million. As has been the case in recent years, cross selling across Red Hat products is strong with 65 percent of all deals including one or more components from Red Hat's group of application development and emerging technologies offerings.
|
||||
|
||||
"We expect the growing adoption of these technologies, like Middleware, the RHEL OpenStack platform, OpenShift, cloud management and storage, to continue to drive revenue growth," Calderoni said.
|
||||
|
||||
### OpenStack ###
|
||||
|
||||
During the earnings call, Red Hat CEO Jim Whitehurst was repeatedly asked about the revenue prospects for OpenStack. Whitehurst said that the recently released Red Hat OpenStack Platform 7.0 is a big jump forward thanks to the improved installer.
|
||||
|
||||
"It does a really good job of kind of identifying hardware and lighting it up," Whitehurst said. "Of course, that means there's a lot of work to do around certifying that hardware, making sure it lights up appropriately."
|
||||
|
||||
Whitehurst said that he's starting to see a lot more production application start to move to the OpenStack cloud. He cautioned however that it's still largely the early adopters moving to OpenStack in production and it isn't quite mainstream, yet.
|
||||
|
||||
From a competitive perspective, Whitehurst talked specifically about Microsoft, HP and Mirantis. In Whitehurst's view many organizations will continue to use multiple operating systems and if they choose Microsoft for one part, they are more likely to choose an open-source option,as the alternative option. Whitehurst said he doesn't see a lot of head-to-head competition against HP in cloud, but he does see Mirantis.
|
||||
|
||||
"We've had several wins or people who were moving away from Mirantis to RHEL," Whitehurst said.
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: http://www.serverwatch.com/server-news/red-hat-ceo-optimistic-on-openstack-revenue-opportunity.html
|
||||
|
||||
作者：[Sean Michael Kerner][a]
|
||||
译者：[译者ID](https://github.com/译者ID)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
||||
[a]:http://www.serverwatch.com/author/Sean-Michael-Kerner-101580.htm
|
||||
@ -0,0 +1,119 @@
|
||||
Mark Shuttleworth – The Man Behind Ubuntu Operating System
|
||||
================================================================================
|
||||
|
||||
|
||||
**Mark Richard Shuttleworth** is the founder of **Ubuntu** or the man behind the Debian as they call him. He was born in 1973 in Welkom, South Africa. He’s an entrepreneur and also space tourist who became later **1st citizen of independent African country who could travel to the space**.
|
||||
|
||||
Mark also founded **Thawte** in 1996, the Internet commerce security company, while he was studying finance and IT at University of Cape Town.
|
||||
|
||||
In 2000, Mark founded the HBD, as an investment company, and also he created the Shuttleworth Foundation in order to fund the innovative leaders in the society with combination of fellowships and some investments.
|
||||
|
||||
> “The mobile world is crucial to the future of the PC. This month, for example, it became clear that the traditional PC is shrinking in favor of tablets. So if we want to be relevant on the PC, we have to figure out how to be relevant in the mobile world first. Mobile is also interesting because there’s no pirated Windows market. So if you win a device to your OS, it stays on your OS. In the PC world, we are constantly competing with “free Windows”, which presents somewhat unique challenges. So our focus now is to establish a great story around Ubuntu and mobile form factors – the tablet and the phone – on which we can build deeper relationships with everyday consumers.”
|
||||
>
|
||||
> — Mark Shuttleworth
|
||||
|
||||
In 2002, he flew to International Space Station as member of their crew of Soyuz mission TM-34, after 1 year of training in the Star City, Russia. And after running campaign to promote the science, code, and mathematics to the aspiring astronauts and the other ambitious types at schools in SA, Mark founded the **Canonical Ltd**. and in 2013, he provided leadership for Ubuntu operating system for software development purposes.
|
||||
|
||||
Today, Shuttleworth holds dual citizenship of United Kingdom and South Africa currently lives on lovely Mallards botanical garden in Isle of Man, with 18 precocious ducks, equally his lovely girlfriend Claire, 2 black bitches and occasional itinerant sheep.
|
||||
|
||||
> “Computer is not a device anymore. It is an extension of your mind and your gateway to other people.”
|
||||
>
|
||||
> — Mark Shuttleworth
|
||||
|
||||
### Mark Shuttleworth’s Early life ###
|
||||
|
||||
As we mentioned above, Mark was born in Welkom, South Africa’s Orange Free State as son of surgeon and nursery-school teacher, Mark attended the school at Western Province Preparatory School where he became eventually the Head Boy in 1986, followed by 1 term at Rondebosch Boys’ High School, and later at Bishops/Diocesan College where he was again Head Boy in 1991.
|
||||
|
||||
Mark obtained the Bachelor of Business Science degree in the Finance and Information Systems at University of Cape Town, where he lived there in Smuts Hall. He became, as a student, involved in installations of the 1st residential Internet connections at his university.
|
||||
|
||||
> “There are many examples of companies and countries that have improved their competitiveness and efficiency by adopting open source strategies. The creation of skills through all levels is of fundamental importance to both companies and countries.”
|
||||
>
|
||||
> — Mark Shuttleworth
|
||||
|
||||
### Mark Shuttleworth’s Career ###
|
||||
|
||||
Mark founded Thawte in 1995, which was specialized in the digital certificates and Internet security, then he sold it to VeriSign in 1999, earning about $575 million at the time.
|
||||
|
||||
In 2000, Mark formed the HBD Venture Capital (Here be Dragons), the business incubator and venture capital provider. In 2004, he formed the Canonical Ltd., for promotion and commercial support of the free software development projects, especially Ubuntu operating system. In 2009, Mark stepped down as CEO of Canonical, Ltd.
|
||||
|
||||
> “In the early days of the DCC I preferred to let the proponents do their thing and then see how it all worked out in the end. Now we are pretty close to the end.”
|
||||
>
|
||||
> — Mark Shuttleworth
|
||||
|
||||
### Linux and FOSS with Mark Shuttleworth ###
|
||||
|
||||
In the late 1990s, Mark participated as one of developers of Debian operating system.
|
||||
|
||||
In 2001, Mark formed the Shuttleworth Foundation, It is non-profit organization dedicated to the social innovation that also funds free, educational, and open source software projects in South Africa, including Freedom Toaster.
|
||||
|
||||
In 2004, Mark returned to free software world by funding software development of Ubuntu, as it was Linux distribution based on Debian, throughout his company Canonical Ltd.
|
||||
|
||||
In 2005, Mark founded Ubuntu Foundation and made initial investment of 10 million dollars. In Ubuntu project, Mark is often referred to with tongue-in-cheek title “**SABDFL (Self-Appointed Benevolent Dictator for Life)**”. To come up with list of names of people in order to hire for the entire project, Mark took about six months of Debian mailing list archives with him during his travelling to Antarctica aboard icebreaker Kapitan Khlebnikov in 2004. In 2005, Mark purchased 65% stake of Impi Linux.
|
||||
|
||||
> “I urge telecommunications regulators to develop a commercial strategy for delivering effective access to the continent.”
|
||||
>
|
||||
> — Mark Shuttleworth
|
||||
|
||||
In 2006, it was announced that Shuttleworth became **first patron of KDE**, which was highest level of sponsorship available at the time. This patronship ended in 2012, with financial support together for Kubuntu, which was Ubuntu variant with KDE as a main desktop.
|
||||
|
||||
|
||||
|
||||
In 2009, Shuttleworth announced that, he would step down as the CEO of Canonical in order to focus more energy on partnership, product design, and the customers. Jane Silber, took on this job as the CEO at Canonical after he was the COO at Canonical since 2004.
|
||||
|
||||
In 2010, Mark received the honorary degree from Open University for that work.
|
||||
|
||||
In 2012, Mark and Kenneth Rogoff took part together in debate opposite Peter Thiel and Garry Kasparov at Oxford Union, this debate was entitled “**The Innovation Enigma**”.
|
||||
|
||||
In 2013, Mark and Ubuntu were awarded **Austrian anti-privacy Big Brother Award** for sending the local Ubuntu Unity Dash searches to the Canonical servers by default. One year earlier in 2012, Mark had defended the anonymization method that was used.
|
||||
|
||||
> “All the major PC companies now ship PC’s with Ubuntu pre-installed. So we have a very solid set of working engagements in the industry. But those PC companies are nervous to promote something new to PC buyers. If we can get PC buyers familiar with Ubuntu as a phone and tablet experience, then they may be more willing buy it on the PC too. Because no OS ever succeeded by emulating another OS. Android is great, but if we want to succeed we need to bring something new and better to market. We are all at risk of stagnating if we don’t pursue the future, vigorously. But if you pursue the future, you have to accept that not everybody will agree with your vision.”
|
||||
>
|
||||
> — Mark Shuttleworth
|
||||
|
||||
### Mark Shuttleworth’s Spaceflight ###
|
||||
|
||||
Mark gained worldwide fame in 2002 as a second self-funded space tourist and the first South African who could travel to the space. Flying through Space Adventures, Mark launched aboard Russian Soyuz TM-34 mission as spaceflight participant, and he paid approximately $20 million for that voyage. 2 days later, Soyuz spacecraft arrived at International Space Station, where Mark spent 8 days participating in the experiments related to the AIDS and the GENOME research. Later in 2002, Mark returned to the Earth on the Soyuz TM-33. To participate in that flight, Mark had to undergo 1 year of preparation and training, including 7 months spent in the Star City, Russia.
|
||||
|
||||
|
||||
|
||||
While in space, Mark had radio conversation with Nelson Mandela and another 14 year old South African girl, called Michelle Foster, who asked Mark to marry her. Of course Mark politely dodged that question, stating that he was much honored to this question before cunningly change the subject. The terminally ill Foster was also provided the opportunity to have conversation with Mark and Nelson Mandela by Reach for Dream foundation.
|
||||
|
||||
Upon returning, Mark traveled widely and also spoke about that spaceflight to schoolchildren around the world.
|
||||
|
||||
> “The raw numbers suggest that Ubuntu continues to grow in terms of actual users. And our partnerships – Dell, HP, Lenovo on the hardware front, and gaming companies like EA, Valve joining up on the software front – make me feel like we continue to lead where it matters.”
|
||||
>
|
||||
> — Mark Shuttleworth
|
||||
|
||||
### Mark Shuttleworth’s Transport ###
|
||||
|
||||
Mark has his private jet, Bombardier Global Express that is often referred to as Canonical One but it’s in fact owned through the HBD Venture Capital Company. The dragon depicted on side of the plane is Norman, HBD Venture Capital mascot.
|
||||
|
||||
### The Legal Clash with South African Reserve Bank ###
|
||||
|
||||
Upon the moving R2.5 billion in the capital from South Africa to Isle of Man, South African Reserve Bank imposed R250 million levy to release Mark’s assets. Mark appealed, and then after lengthy legal battle, Reserve Bank was ordered to repay Mark his R250 million, plus the interest. Mark announced that he would be donating that entire amount to trust that will be established in order to help others take cases to Constitutional Court.
|
||||
|
||||
> “The exit charge was not inconsistent with the Constitution. The dominant purpose of the exit charge was not to raise revenue but rather to regulate conduct by discouraging the export of capital to protect the domestic economy.”
|
||||
>
|
||||
> — Judge Dikgang Moseneke
|
||||
|
||||
In 2015, Constitutional Court of South Africa reversed and set-aside findings of lower courts, ruling that dominant purpose of the exit charge was in order to regulate conduct rather than for raising the revenue.
|
||||
|
||||
### Mark Shuttleworth’s likes ###
|
||||
|
||||
Cesária Évora, mp3s,Spring, Chelsea, finally seeing something obvious for first time, coming home, Sinatra, daydreaming, sundowners, flirting, d’Urberville, string theory, Linux, particle physics, Python, reincarnation, mig-29s, snow, travel, Mozilla, lime marmalade, body shots, the African bush, leopards, Rajasthan, Russian saunas, snowboarding, weightlessness, Iain m banks, broadband, Alastair Reynolds, fancy dress, skinny-dipping, flashes of insight, post-adrenaline euphoria, the inexplicable, convertibles, Clifton, country roads, international space station, machine learning, artificial intelligence, Wikipedia, Slashdot, kitesurfing, and Manx lanes.
|
||||
|
||||
### Shuttleworth’s dislikes ###
|
||||
|
||||
Admin, salary negotiations, legalese, and public speaking.
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: http://www.unixmen.com/mark-shuttleworth-man-behind-ubuntu-operating-system/
|
||||
|
||||
作者：[M.el Khamlichi][a]
|
||||
译者：[译者ID](https://github.com/译者ID)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
||||
[a]:http://www.unixmen.com/author/pirat9/
|
||||
@ -0,0 +1,68 @@
|
||||
Ubuntu 15.10, Codenamed Wily Werewolf, Review
|
||||
================================================================================
|
||||
|
||||
|
||||
The problem we have with reviewing Ubuntu on any occasion, is readers consistently expect to read of a revolutionary new release, every 6 months. If you’re expecting Ubuntu 15.10 to be just that, then you may want to click out of this review right now. It’s important to clarify that this is nothing negative towards 15.10 as a release, but it is a maintenance release and not a release which purports to introduce a great deal of new software.
|
||||
|
||||
With that opening disclaimer out of the way, let’s take a look at what 15.10 does offer.
|
||||
|
||||
### Linux kernel 4.2 ###
|
||||
|
||||
The biggest change you will find with Ubuntu 15.10 is the kernel branch has been upgraded to **Linux 4.2**.
|
||||
|
||||
This is long overdue for Ubuntu. It feels like it has been lagging behind other distributions by sticking with the 3.x branch of Linux for the entirety of the 15.04 cycle.
|
||||
|
||||
If you’re going to be installing Ubuntu 15.10 on new hardware, then you will benefit greatly from the Linux kernel upgrade to 4.x branch as there is loads of updates which directly improve performance on new hardware. Support for AMDGPU kernel DRM is included, which is a boon for owners of recent Radeon graphics cards. The latest iteration of the driver will reside alongside the current Radeon DRM drivers, which was already in the kernel in addition to the usual open-source driver offerings.
|
||||
|
||||
Support for Intel Broxton is also included in Linux 4.2, albeit Ubuntu 15.10 users are probably going to get nothing out of this update, yet it’s still worthy of a mention we think. There are also some erroneous updates for Skylake CPU’s. Finally, there is a host of code updates and fixes for Ext4 filesystems.
|
||||
|
||||
That pretty much rounds out the Linux kernel 4.2 updates. So what else is new? Let’s take a closer look at the software that you may be more familiar with and get more excited about.
|
||||
|
||||
### Software ###
|
||||
|
||||
LibreOffice has been upgraded to 5.0.1.2, a major update for LibreOffice users. Firefox on the version that we tested is sitting at 41.0.2. By the time you read this, it will most-likely be updated again and you may see a newer version be pushed out through the Ubuntu Repositories.
|
||||
|
||||
On the desktop front, a vanilla Ubuntu installation will see you running Unity 7.3.2 while GNOME sits at 3.8. On the KDE end, a Plasma 5 desktop will see you running version 5.4.2. For the alternative desktop-environments, XFCE has been upgraded to the latest revision, 4.12 while the version of MATE includes 1.10.
|
||||
|
||||
### User Experience/Screenshots ###
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
### Conclusion ###
|
||||
|
||||
Ubuntu 15.10 as a operating system for Review is pretty lackluster. There’s nothing new as such and there’s nothing we can really say that is going to change your opinion from its predecessor, 15.04. Therefore, we recommend you to upgrade either out of habit and according to your regular upgrade schedule rather than out of a specific necessity for a specific feature of this release. Because there is really nothing that could possibly differentiate it from the older, yet still very stable 15.04 release. But if you’re going to stick with 15.04 for a little longer, we do recommend that you look at [upgrading the kernel to the latest 4.2 branch][2]. It is worth it.
|
||||
|
||||
If you really want a reason to upgrade? Linux kernel 4.2 would be our sole reason for taking Ubuntu 15.10 into consideration.
|
||||
|
||||
### Looking Ahead ###
|
||||
|
||||
What we really look forward to is the release of Ubuntu 16.04. We have been promised over and over again for several releases that Mir will be the default display server included in Ubuntu. We still see releases pushed out that rely on X.org. It has resulted in us adopting a “yeah right” attitude as we have become accustomed to the usual delay announcements.
|
||||
|
||||
We are hopeful that Mir Developers can push out a working version in time for the release of 16.04 next year. As precaution though, we urge you to not get too excited because it may very well not happen.
|
||||
|
||||
It remains much the same with Unity 8. It’s most certainly a possibility, but we can’t guarantee that it will be included in 16.04, yet we remain hopeful.
|
||||
|
||||
As we’ve mentioned for this release, there’s nothing really ground-breaking with this release. In fact, it has been much the same story for the last couple of releases of Ubuntu Linux. It is in dire need of a distribution-wide reboot. Developers and Ubuntu users alike are positive that Mir and Unity 8 will be the two primary packages that may just provide the popular, yet ailing, distribution the reboot that it needs.
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: http://www.unixmen.com/ubuntu-15-10-codenamed-wily-werewolf-review/
|
||||
|
||||
作者：[Chris Jones][a]
|
||||
译者：[译者ID](https://github.com/译者ID)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
||||
[a]:http://www.unixmen.com/author/chris/
|
||||
[1]:http://www.unixmen.com/how-to-install-linux-kernel-4-2-3/
|
||||
@ -1,130 +0,0 @@
|
||||
Part 10: Setting Up “NTP (Network Time Protocol) Server” in RHEL/CentOS 7
|
||||
================================================================================
|
||||
Network Time Protocol – NTP- is a protocol which runs over port 123 UDP at Transport Layer and allows computers to synchronize time over networks for an accurate time. While time is passing by, computers internal clocks tend to drift which can lead to inconsistent time issues, especially on servers and clients logs files or if you want to replicate servers resources or databases.
|
||||
|
||||
|
||||
|
||||
NTP Server Installation in CentOS and RHEL 7
|
||||
|
||||
#### Requirements: ####
|
||||
|
||||
- [CentOS 7 Installation Procedure][1]
|
||||
- [RHEL 7 Installation Procedure][2]
|
||||
|
||||
#### Additional Requirements: ####
|
||||
|
||||
- [Register and Enbale RHEL 7 Subscription for Updates][3]
|
||||
- [Configure Static IP Address on CentOS/Rhel 7][4]
|
||||
- [Disable and Remove Unwanted Services in CentOS/RHEL 7][5]
|
||||
|
||||
This tutorial will demonstrate how you can install and configure NTP server on CentOS/RHEL 7 and automatically synchronize time with the closest geographically peers available for your server location by using NTP Public Pool Time Servers list.
|
||||
|
||||
#### Step 1: Install and configure NTP daemon ####
|
||||
|
||||
1. NTP server package is provided by default from official CentOS /RHEL 7 repositories and can be installed by issuing the following command.
|
||||
|
||||
# yum install ntp
|
||||
|
||||
|
||||
|
||||
Install NTP Server
|
||||
|
||||
2. After the server is installed, first go to official [NTP Public Pool Time Servers][6], choose your Continent area where the server physically is located, then search for your Country location and a list of NTP servers should appear.
|
||||
|
||||
|
||||
|
||||
NTP Pool Server
|
||||
|
||||
3. Then open NTP daemon main configuration file for editing, comment the default list of Public Servers from pool.ntp.org project and replace it with the list provided for your country like in the screenshot below.
|
||||
|
||||
|
||||
|
||||
Configure NTP Server
|
||||
|
||||
4. Further, you need to allow clients from your networks to synchronize time with this server. To accomplish this, add the following line to NTP configuration file, where restrict statement controls, what network is allowed to query and sync time – replace network IPs accordingly.
|
||||
|
||||
restrict 192.168.1.0 netmask 255.255.255.0 nomodify notrap
|
||||
|
||||
The nomodify notrap statements suggest that your clients are not allowed to configure the server or be used as peers for time sync.
|
||||
|
||||
5. If you need additional information for troubleshooting in case there are problems with your NTP daemon add a log file statement which will record all NTP server issues into one dedicated log file.
|
||||
|
||||
logfile /var/log/ntp.log
|
||||
|
||||
|
||||
|
||||
Enable NTP Logs
|
||||
|
||||
6. After you have edited the file with all configuration explained above save and close ntp.conf file. Your final configuration should look like in the screenshot below.
|
||||
|
||||
|
||||
|
||||
NTP Server Configuration
|
||||
|
||||
### Step 2: Add Firewall Rules and Start NTP Daemon ###
|
||||
|
||||
7. NTP service uses UDP port 123 on OSI transport layer (layer 4). It is designed particularly to resist the effects of variable latency (jitter). To open this port on RHEL/CentOS 7 run the following commands against Firewalld service.
|
||||
|
||||
# firewall-cmd --add-service=ntp --permanent
|
||||
# firewall-cmd --reload
|
||||
|
||||
|
||||
|
||||
Open NTP Port in Firewall
|
||||
|
||||
8. After you have opened Firewall port 123, start NTP server and make sure you enable it system-wide. Use the following commands to manage the service.
|
||||
|
||||
# systemctl start ntpd
|
||||
# systemctl enable ntpd
|
||||
# systemctl status ntpd
|
||||
|
||||
|
||||
|
||||
Start NTP Service
|
||||
|
||||
### Step 3: Verify Server Time Sync ###
|
||||
|
||||
9. After NTP daemon has been started, wait a few minutes for the server to synchronize time with its pool list servers, then run the following commands to verify NTP peers synchronization status and your system time.
|
||||
|
||||
# ntpq -p
|
||||
# date -R
|
||||
|
||||
|
||||
|
||||
Verify NTP Time Sync
|
||||
|
||||
10. If you want to query and synchronize against a pool of your choice use ntpdate command, followed by the server or servers addresses, as suggested in the following command line example.
|
||||
|
||||
# ntpdate -q 0.ro.pool.ntp.org 1.ro.pool.ntp.org
|
||||
|
||||
|
||||
|
||||
Synchronize NTP Time
|
||||
|
||||
### Step 4: Setup Windows NTP Client ###
|
||||
|
||||
11. If your windows machine is not a part of a Domain Controller you can configure Windows to synchronize time with your NTP server by going to Time from the right side of Taskbar -> Change Date and Time Settings -> Internet Time tab -> Change Settings -> Check Synchronize with an Internet time server -> put your server’s IP or FQDN on Server filed -> Update now -> OK.
|
||||
|
||||
|
||||
|
||||
Synchronize Windows Time with NTP
|
||||
|
||||
That’s all! Setting up a local NTP Server on your network ensures that all your servers and clients have the same time set in case of an Internet connectivity failure and they all are synchronized with each other.
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: http://www.tecmint.com/install-ntp-server-in-centos/
|
||||
|
||||
作者：[Matei Cezar][a]
|
||||
译者：[译者ID](https://github.com/译者ID)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
||||
[a]:http://www.tecmint.com/author/cezarmatei/
|
||||
[1]:http://www.tecmint.com/centos-7-installation/
|
||||
[2]:http://www.tecmint.com/redhat-enterprise-linux-7-installation/
|
||||
[3]:http://www.tecmint.com/enable-redhat-subscription-reposiories-and-updates-for-rhel-7/
|
||||
[4]:http://www.tecmint.com/configure-network-interface-in-rhel-centos-7-0/
|
||||
[5]:http://www.tecmint.com/remove-unwanted-services-in-centos-7/
|
||||
[6]:http://www.pool.ntp.org/en/
|
||||
@ -0,0 +1,37 @@
|
||||
红帽 CEO 对 OpenStack 收益表示乐观
|
||||
================================================================================
|
||||
得益于围绕 Linux 和云不断发展的平台和基础设施技术，红帽正在持续快速发展。红帽宣布在九月二十一日完成了 2016 财年第二季度的财务业绩，再次超过预期。
|
||||
|
||||
|
||||
|
||||
这一季度，红帽的收入为 5 亿 4 百万美元，和去年同比增长 13%。网络输入为 5 千 1 百万美元，超过 2015 年第二季度的 4 千 7 百万美元。展望未来，红帽为下一季度和全年提供了积极的目标。对于第三季度，红帽希望指导收益能在 5亿1千9百万美元和5亿2千3百万美元之间，和去年同期相比增长 15%。
|
||||
|
||||
对于 2016 财年，红帽的全年指导目标是 20亿4千4百万美元，和去年相比增长 14%。
|
||||
|
||||
红帽 CFO Frank Calderoni 在电话会议上指出，红帽最高的 30 个订单大概甚至超过 1 百万美元。其中有 4 个订单超过 5百万美元，还有一个超过1千万美元。从近几年的经验来看，红帽产品的交叉销售非常成功，全部订单中有超过 65% 的订单包括了一个或多个红帽应用和新兴技术产品组件。
|
||||
|
||||
Calderoni 说 “我们希望这些技术，例如中间件、RHEL OpenStack 平台、OpenShift、云管理和存储能持续推动收益增长。”
|
||||
|
||||
### OpenStack ###
|
||||
|
||||
在电话会议中，红帽 CEO Jim Whitehurst 多次问到 OpenStack 的收入前景。Whitehurst 说得益于安装程序的改进，最近发布的 Red Hat OpenStack Platform 7.0 向前垮了一大步。
|
||||
|
||||
Whitehurst 提到：“在识别硬件和使用方面它做的很好，当然，这也意味着在硬件识别并正确使用它们方便还有很多工作要做。”
|
||||
|
||||
Whitehurst 说他已经开始注意到很多的生产应用程序开始迁移到 OpenStack 云上来。他也警告说在产业化方面迁移到 OpenStack 大部分只是尝鲜，还并没有成为主流。
|
||||
|
||||
对于竞争对手， Whitehurst 尤其提到了微软、惠普和 Mirantis。在他看来，很多组织仍然会使用多种操作系统，如果他们其中一部分使用了微软，他们更倾向于开源方案作为替代选项。Whitehurst 说在云方面他还没有看到太多和惠普面对面的竞争，但和 Mirantis 则确实如此。
|
||||
|
||||
Whitehurst 说 “我们也有几次胜利，他们从 Mirantis 转到了 RHEL。”
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: http://www.serverwatch.com/server-news/red-hat-ceo-optimistic-on-openstack-revenue-opportunity.html
|
||||
|
||||
作者：[Sean Michael Kerner][a]
|
||||
译者：[ictlyh](http://mutouxiaogui.cn/blog)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
||||
[a]:http://www.serverwatch.com/author/Sean-Michael-Kerner-101580.htm
|
||||
@ -1,33 +1,34 @@
|
||||
ictlyh Translating
|
||||
Linux History: 24 Years Step by Step
|
||||
Linux 的历史：24 年，一步一个脚印
|
||||
================================================================================
|
||||
注：youtube 视频
|
||||
|
||||
<iframe width="660" height="371" src="https://www.youtube.com/embed/84cHeoEebJM?feature=oembed" frameborder="0" allowfullscreen></iframe>
|
||||
|
||||
### Pre-history ###
|
||||
### 史前 ###
|
||||
|
||||
Linux success would not be possible without [C programming language][1] and [GNU Project][2] – Environment of Linux.
|
||||
没有 [C 编程语言][1] and [GNU 项目][2] - Linux 环境，也就不可能有 Linux 的成功。
|
||||
|
||||
|
||||
|
||||
Ken Thompson and Dennis Ritchie
|
||||
|
||||
[Ken Thompson][1] and [Dennis Ritchie][2] was created the Unix Operation System in 1969-1970. Later was released the new [C programming language][3] – high-level and portable PL. Linux kernel written in C with some assembly code.
|
||||
Ken Thompson 和 Dennis Ritchie
|
||||
|
||||
[Ken Thompson][1] 和 [Dennis Ritchie][2] 在 1969-1970 创造了 Unix 操作系统。之后发布了新的 [C 编程语言][3] - 高级可移植编程语言。 Linux 内核用 C 和一些汇编代码写成。
|
||||
|
||||
|
||||
|
||||
|
||||
Richard Matthew Stallman
|
||||
|
||||
[Richard Matthew Stallman][4] started in 1984 the [GNU Project][5]. One of biggest goals — free Unix-like operation system and totally
|
||||
[Richard Matthew Stallman][4] 在 1984 年启动了 [GNU 项目][5]。最大的一个目标 - 完全自由的类-Unix 操作系统。
|
||||
|
||||
### 1991 – The Beginning ###
|
||||
### 1991 – 元年 ###
|
||||
|
||||
|
||||
|
||||
Linus Torvalds, 1991
|
||||
|
||||
[Linus Torvalds][5] begin Linux kernel development in Helsinki, Finland – witten programm for hes hardware – Intel 80386 CPU. Hi also use Minix and GNU C compiler. Here is historical message from Linus Torvalds to Minix newsgroup:
|
||||
[Linus Torvalds][5] 在芬兰赫尔辛基开始了 Linux 内核开发 - 为他的硬件 - Intel 30386 CPU 编写程序。他也使用 Minix 和 GNU C 编译器。下面是 Linus Torvalds 给 Minix 新闻组的历史消息：
|
||||
|
||||
> From: torvalds@klaava.Helsinki.FI (Linus Benedict Torvalds)
|
||||
> Newsgroups: comp.os.minix
|
||||
@ -54,41 +55,41 @@ Linus Torvalds, 1991
|
||||
>
|
||||
> Linus (torvalds@kruuna.helsinki.fi)
|
||||
|
||||
After this Linux has supported by worldwide volunteers and professional specialists. Name “Linux” was defined by Linus coworker Ari Lemmke – just named directory of project on University Server.
|
||||
从此之后，Linux 开始得到了世界范围志愿者和专业专家的支持。Linus 的合作者 Ari Lemmke 把它命名为 “Linux” - 大学服务器项目上的目录名称。
|
||||
|
||||
### 1992 ###
|
||||
|
||||
|
||||
|
||||
Version 0.12 of Linux Kernel released under GPLv2.
|
||||
在 GPLv2 协议下发布了 0.12 版 Linux 内核。
|
||||
|
||||
### 1993 ###
|
||||
|
||||
|
||||
|
||||
First release of Slackware – the oldest Linux Distro with the same leader – Patrick Volkerding. Linux kernel have ~100 Developers.
|
||||
第一次发布 Slackware（译者注：Slackware Linux 是一个高度技术性的，干净的发行版，只有少量非常有限的个人设置） – 相同主导者 Patrick Volkerding 最老的 Linux 发行版。Linux 内核有 100 多个开发者。
|
||||
|
||||
|
||||
|
||||
Debian
|
||||
|
||||
Debian – one of largest Linux-community also created in 1991.
|
||||
Debian – 1991 年创立了最大的 Linux 社区之一。
|
||||
|
||||
### 1994 ###
|
||||
|
||||
Linux 1.0 released and first GUI is available – thanks to XFree86 project.
|
||||
Linux 1.0 发布了，多亏了 XFree 86 项目，第一次有了 GUI。
|
||||
|
||||
|
||||
|
||||
Red Hat Linux
|
||||
|
||||
Released Red Hat Linux 1.0
|
||||
发布 Red Hat Linux 1.0
|
||||
|
||||
|
||||
|
||||
S.u.S.E Linux
|
||||
|
||||
and [S.u.S.E. Linux][6] 1.0.
|
||||
和 [S.u.S.E. Linux][6] 1.0.
|
||||
|
||||
### 1995 ###
|
||||
|
||||
@ -96,7 +97,7 @@ and [S.u.S.E. Linux][6] 1.0.
|
||||
|
||||
Red Hat Inc.
|
||||
|
||||
Bob Young and Marc Ewing merged their local business to [Red Hat Software][7]. Linux ported to many of hardware platforms.
|
||||
Bob Yound 和 Marc Ewing 合并他们的本地业务为 [Red Hat Software][7]。Linux 移植到了很多硬件平台。
|
||||
|
||||
### 1996 ###
|
||||
|
||||
@ -104,7 +105,7 @@ Bob Young and Marc Ewing merged their local business to [Red Hat Software][7]. L
|
||||
|
||||
### Tux ###
|
||||
|
||||
Tux Penguin – official mascot of Linux. Idea of Linus Torvalds – after visit to National Zoo & Aquarium in Canberra. Linux 2.0 released and support symmetric multiprocessing. Begin of KDE development.
|
||||
企鹅 Tux - Linux 官方吉祥物。Linus Torvalds 参观了堪培拉国家动物园和水族馆之后有了这个想法。发布了 Linux 2.0，支持对称多处理器。开始开发 KDE。
|
||||
|
||||
### 1997 ###
|
||||
|
||||
@ -112,33 +113,33 @@ Tux Penguin – official mascot of Linux. Idea of Linus Torvalds – after visit
|
||||
|
||||
Miguel de Icaza
|
||||
|
||||
Miguel de Icaza and Federico Mena begin development of GNOME – free desktop environment with application. Linus Torvalds win in Linux’s Trademark conflict and Linux becomes the registered trademark of Linus.
|
||||
Miguel de Icaza 和 Federico Mena 开始开发 GNOME - 自由桌面环境和应用程序。Linus Torvalds 赢得了 Linux 商标冲突，Linux 成为了 Linus 的注册商标。
|
||||
|
||||
### 1998 ###
|
||||
|
||||
|
||||
|
||||
The Cathedral and the Bazaar
|
||||
大教堂和集市
|
||||
|
||||
[The Cathedral and the Bazaar][8] essay by Eric S. Raymond is published – highly recommend to read. Linux support from big companies: IBM, Oracle, Compaq.
|
||||
Eric S. Raymond 出版了文章 [The Cathedral and the Bazaar][8]（大教堂和集市） - 非常推荐阅读。Linux 得到了大公司的支持： IBM、Oracle、康柏。
|
||||
|
||||
|
||||
|
||||
Mandrake Linux
|
||||
|
||||
First release of Mandrake Linux – Red Hat Linux-based distro with K Desktop Environment.
|
||||
首次发布 Mandrake Linux - 基于红帽 Linux 带 K 桌面环境的发行版。
|
||||
|
||||
### 1999 ###
|
||||
|
||||
|
||||
|
||||
First major KDE release.
|
||||
第一个主要的 KDE 发行版。
|
||||
|
||||
### 2000 ###
|
||||
|
||||
|
||||
|
||||
Dell support Linux – first big hardware vendor
|
||||
Dell 支持 Linux - 第一个大的硬件供应商。
|
||||
|
||||
### 2001 ###
|
||||
|
||||
@ -146,7 +147,7 @@ Dell support Linux – first big hardware vendor
|
||||
|
||||
Revolution OS
|
||||
|
||||
Documentary film “Revolution OS” – 20 years of GNU, Linux, Open Source, Free Software history with iterview of best hackers of Linux and Open Source World.
|
||||
纪录片 “Revolution OS”（译者注：操作系统革命） - GNU、Linux、开源、自由软件的 20 年历史，以及 Linux 和开源界最好骇客的采访。
|
||||
|
||||
### 2002 ###
|
||||
|
||||
@ -154,7 +155,7 @@ Documentary film “Revolution OS” – 20 years of GNU, Linux, Open Source, Fr
|
||||
|
||||
BitKeeper
|
||||
|
||||
Linux now use BitKeeper – proprietary software for distributed version control.
|
||||
Linux 开始使用 BitKeeper - 分布式版本控制专用软件。
|
||||
|
||||
### 2003 ###
|
||||
|
||||
@ -162,25 +163,25 @@ Linux now use BitKeeper – proprietary software for distributed version control
|
||||
|
||||
SUSE
|
||||
|
||||
Novell buy SuSE Linux AG for $210M. Since 2003 also started epic battle SCO Group vs IBM and Linux community for the Unix copyrights.
|
||||
Novell 用 210 美元购买了 SUSE Linux AG。2003 年也开始了 SCO 集团，IBM、以及 Linux 社区关于 Unix 版权的史诗般战役。
|
||||
|
||||
|
||||
|
||||
Fedora
|
||||
|
||||
First Release of Fedora Linux from Red Hat and Linux Community.
|
||||
红帽和 Linux 社区第一次发布了 Fedora Linux。
|
||||
|
||||
### 2004 ###
|
||||
|
||||
|
||||
|
||||
X.ORG Foundation
|
||||
X.ORG 基金会
|
||||
|
||||
The XFree86 team is dropped and join to [X.Org Foundation][9], development of X be faster.
|
||||
XFree86 解散了并加入到 [X.Org 基金会][9]， X 的开发更快了。
|
||||
|
||||
|
||||
|
||||
Ubuntu 4.10 – First Release
|
||||
Ubuntu 4.10 – 第一次发布
|
||||
|
||||
### 2005 ###
|
||||
|
||||
@ -188,21 +189,21 @@ Ubuntu 4.10 – First Release
|
||||
|
||||
openSUSE
|
||||
|
||||
Beginning of [openSUSE][10] – free version of enterprise Novell’s OS. OpenOffice.org started support of OpenDocument standards.
|
||||
开始了 [openSUSE][10] - 企业版 Novell’s OS 的免费版本。OpenOffice.org 开始支持 OpenDocument 标准。
|
||||
|
||||
### 2006 ###
|
||||
|
||||
|
||||
|
||||
New Linux distribution – Oracle Linux based on Red Hat Enterprise Linux. Microsoft and Novell begin cooperation in IT and both patents protection.
|
||||
新的 Linux 发行版 - 基于红帽企业版 Linux 的 Oracle Linux。微软和 Novell 开始在 IT 和专利保护方面进行合作。
|
||||
|
||||
### 2007 ###
|
||||
|
||||
|
||||
|
||||
Dell Linux Laptop
|
||||
Dell Linux 笔记本
|
||||
|
||||
First laptops with preinstalled Linux from Dell.
|
||||
Dell 发布了预安装 Linux 的笔记本。
|
||||
|
||||
### 2008 ###
|
||||
|
||||
@ -210,7 +211,7 @@ First laptops with preinstalled Linux from Dell.
|
||||
|
||||
KDE 4.0
|
||||
|
||||
KDE 4 released in non-stable condition and many users migrate to GNOME.
|
||||
在不稳定的情况下发布了 KDE 4，很多用户开始迁移到 GNOME。
|
||||
|
||||
### 2009 ###
|
||||
|
||||
@ -218,9 +219,9 @@ KDE 4 released in non-stable condition and many users migrate to GNOME.
|
||||
|
||||
Red Hat
|
||||
|
||||
Red Hat’s Linux-based success – $2.62 billion market capitalization.
|
||||
红帽 Linux 的成功 - 市值 2亿6千2百万美元。
|
||||
|
||||
In 2009 Microsoft sumbitted first patch to Linux kernel under GPLv2 license.
|
||||
2009 年微软第一次在 GPLv2 协议下向 Linux 内核提交了补丁。
|
||||
|
||||
### 2010 ###
|
||||
|
||||
@ -228,9 +229,9 @@ In 2009 Microsoft sumbitted first patch to Linux kernel under GPLv2 license.
|
||||
|
||||
Novell -> Attachmate
|
||||
|
||||
Novell was sold to The Attachmate Group, Inc. for $2.2 billion. SUSE and Novell – two independs products in new company.
|
||||
Novell 已 2亿2千万美元卖给了 Attachmate Group, Inc。在新公司 SUSE 和 Novell 成为了两款独立的产品。
|
||||
|
||||
First release of [systemd][11] and begin of Linux system revolution.
|
||||
第一次发布了 [systemd][11]，开始了 Linux 系统的革命。
|
||||
|
||||
### 2011 ###
|
||||
|
||||
@ -238,50 +239,50 @@ First release of [systemd][11] and begin of Linux system revolution.
|
||||
|
||||
Unity Desktop in 2011
|
||||
|
||||
Ubuntu Unity released – a lot of criticizm from users.
|
||||
发布了 Ubuntu Unity - 遭到很多用户的批评。
|
||||
|
||||
|
||||
|
||||
GNOME 3.0, 2011
|
||||
|
||||
GNOME 3.0 release – “unholy mess” by Linus Torvalds and also a lot of negative critics. Linux kernel 3.0 released.
|
||||
发布了 GNOME 3.0 - Linus Torvalds 评论为 “unholy mess” 以及很多负面评论。发布了 Linux 内核 3.0。
|
||||
|
||||
### 2012 ###
|
||||
|
||||
|
||||
|
||||
15 million lines of code
|
||||
1500 万行代码
|
||||
|
||||
Linux kernel have a 15 million lines of code. Microsoft is one of top Linux contributors.
|
||||
Linux 内核有 1500 万行代码。微软成为主要共享者之一。
|
||||
|
||||
### 2013 ###
|
||||
|
||||
|
||||
|
||||
Kali Linux 1.0 released – Debian-based Linux distro for penetration testing and digital forensics. Also in 2014 Centos with code developers joined to Red Hat Inc.
|
||||
发布了 Kali Linux 1.0 - 用户渗透测试和数字取证的基于 Debian 的 Linux 发行版。2014 年 CentOS 代码开发者加入到了红帽公司。
|
||||
|
||||
### 2014 ###
|
||||
|
||||
|
||||
|
||||
Lennart Poettering and Kay Sievers
|
||||
Lennart Poettering 和 Kay Sievers
|
||||
|
||||
systemd – default in Ubuntu and all top Linux distribution. Ubuntu have 22 000 000 users. Big Android progress – 75% of all mobile devices.
|
||||
systemd - Ubuntu 和所有主流 Linux 发行版的默认初始化程序。Ubuntu 有 2200 万用户。安卓的大进步 - 占了所有移动设备的 75%。
|
||||
|
||||
### 2015 ###
|
||||
|
||||
|
||||
|
||||
Linux kernel 4.0 released. Mandriva was liquidated, but have a lot of forks – Mageia is most popular.
|
||||
发布了 Linux 4.0。没有了 Mandriva（译者注：Mandriva 是目前全球最优秀的 Linux 发行版之一，稳居于 linux 排行榜第一梯队。2005年之前稳居 linux 排行榜 NO.1。它是目前最易用的 linux 发行版，也是众多国际级 linux 发行版中唯一一个默认即支持中文环境的 linux） - 但还有很多分支 - 其中最流行的一个是 Mageia。
|
||||
|
||||
Written from Linux with love.
|
||||
写于对 Linux 的热爱。
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://tlhp.cf/linux-history/
|
||||
|
||||
作者：[Pavlo Rudyi][a]
|
||||
译者：[译者ID](https://github.com/译者ID)
|
||||
译者：[ictlyh](http://mutouxiaogui.cn/blog)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
||||
@ -0,0 +1,130 @@
|
||||
第 10 部分：在 RHEL/CentOS 7 中设置 “NTP（网络时间协议） 服务器”
|
||||
================================================================================
|
||||
网络时间协议 - NTP - 是运行在传输层 123 号端口允许计算机通过网络同步准确时间的协议。随着时间的流逝，计算机内部时间会出现漂移，这会导致时间不一致问题，尤其是对于服务器和客户端日志文件，或者你想要备份服务器资源或数据库。
|
||||
|
||||
|
||||
|
||||
在 CentOS 和 RHEL 7 上安装 NTP 服务器
|
||||
|
||||
#### 要求： ####
|
||||
|
||||
- [CentOS 7 安装过程][1]
|
||||
- [RHEL 安装过程][2]
|
||||
|
||||
#### 额外要求： ####
|
||||
|
||||
- [注册并启用 RHEL 7 更新订阅][3]
|
||||
- [在 CentOS/RHCE 7 上配置静态 IP][4]
|
||||
- [在 CentOS/RHEL 7 上停用并移除不需要的服务][5]
|
||||
|
||||
这篇指南会告诉你如何在 CentOS/RHCE 7 上安装和配置 NTP 服务器，并使用 NTP 公共时间服务器池列表中和你服务器地理位置最近的可用节点中同步时间。
|
||||
|
||||
#### 步骤一：安装和配置 NTP 守护进程 ####
|
||||
|
||||
1. 官方 CentOS /RHEL 7 库默认提供 NTP 服务器安装包，可以通过使用下面的命令安装。
|
||||
|
||||
# yum install ntp
|
||||
|
||||
|
||||
|
||||
安装 NTP 服务器
|
||||
|
||||
2. 安装完服务器之后，首先到官方 [NTP 公共时间服务器池][6]，选择你服务器物理位置所在的洲，然后搜索你的国家位置，然后会出现 NTP 服务器列表。
|
||||
|
||||
|
||||
|
||||
NTP 服务器池
|
||||
|
||||
3. 然后打开编辑 NTP 守护进程主要配置文件，从 pool.ntp.org 中注释掉默认的公共服务器列表并用类似下面截图提供给你国家的列表替换。
|
||||
|
||||
|
||||
|
||||
配置 NTP 服务器
|
||||
|
||||
4. 下一步，你需要允许客户端从你的网络中和这台服务器同步时间。为了做到这点，添加下面一行到 NTP 配置文件，其中限制语句控制允许哪些网络查询和同步时间 - 根据需要替换网络 IP。
|
||||
|
||||
restrict 192.168.1.0 netmask 255.255.255.0 nomodify notrap
|
||||
|
||||
nomodify notrap 语句意味着不允许你的客户端配置服务器或者作为同步时间的节点。
|
||||
|
||||
5. 如果你需要额外的信息用于错误处理，以防你的 NTP 守护进程出现问题，添加一个 logfile 语句，用于记录所有 NTP 服务器问题到一个指定的日志文件。
|
||||
|
||||
logfile /var/log/ntp.log
|
||||
|
||||
|
||||
|
||||
启用 NTP 日志
|
||||
|
||||
6. 你编辑完所有上面解释的配置并保存关闭 ntp.conf 文件后，你最终的配置看起来像下面的截图。
|
||||
|
||||
|
||||
|
||||
NTP 服务器配置
|
||||
|
||||
### 步骤二：添加防火墙规则并启动 NTP 守护进程 ###
|
||||
|
||||
7. NTP 服务在传输层（第四层）使用 123 号 UDP 端口。它是针对限制可变延迟的影响特别设计的。要在 RHEL/CentOS 7 中开放这个端口，可以对 Firewalld 服务使用下面的命令。
|
||||
|
||||
# firewall-cmd --add-service=ntp --permanent
|
||||
# firewall-cmd --reload
|
||||
|
||||
|
||||
|
||||
在 Firewall 中开放 NTP 端口
|
||||
|
||||
8. 你在防火墙中开放了 123 号端口之后，启动 NTP 服务器并确保系统范围内可用。用下面的命令管理服务。
|
||||
|
||||
# systemctl start ntpd
|
||||
# systemctl enable ntpd
|
||||
# systemctl status ntpd
|
||||
|
||||
|
||||
|
||||
启动 NTP 服务
|
||||
|
||||
### 步骤三：验证服务器时间同步 ###
|
||||
|
||||
9. 启动了 NTP 守护进程后，用几分钟等服务器和它的服务器池列表同步时间，然后运行下面的命令验证 NTP 节点同步状态和你的系统时间。
|
||||
|
||||
# ntpq -p
|
||||
# date -R
|
||||
|
||||
|
||||
|
||||
验证 NTP 时间同步
|
||||
|
||||
10. 如果你想查询或者和你选择的服务器池同步，你可以使用 ntpdate 命令，后面跟服务器名或服务器地址，类似下面建议的命令行事例。
|
||||
|
||||
# ntpdate -q 0.ro.pool.ntp.org 1.ro.pool.ntp.org
|
||||
|
||||
|
||||
|
||||
同步 NTP 时间
|
||||
|
||||
### 步骤四：设置 Windows NTP 客户端 ###
|
||||
|
||||
11. 如果你的 windows 机器不是域名控制器的一部分，你可以配置 Windows 和你的 NTP服务器同步时间。在任务栏右边 -> 时间 -> 更改日期和时间设置 -> 网络时间标签 -> 更改设置 -> 和一个网络时间服务器检查同步 -> 在 Server 空格输入服务器 IP 或 FQDN -> 马上更新 -> OK。
|
||||
|
||||
|
||||
|
||||
和 NTP 同步 Windows 时间
|
||||
|
||||
就是这些。在你的网络中配置一个本地 NTP 服务器能确保你所有的服务器和客户端有相同的时间设置，以防出现网络连接失败，并且它们彼此都相互同步。
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: http://www.tecmint.com/install-ntp-server-in-centos/
|
||||
|
||||
作者：[Matei Cezar][a]
|
||||
译者：[ictlyh](http://motouxiaogui.cn/blog)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
||||
[a]:http://www.tecmint.com/author/cezarmatei/
|
||||
[1]:http://www.tecmint.com/centos-7-installation/
|
||||
[2]:http://www.tecmint.com/redhat-enterprise-linux-7-installation/
|
||||
[3]:http://www.tecmint.com/enable-redhat-subscription-reposiories-and-updates-for-rhel-7/
|
||||
[4]:http://www.tecmint.com/configure-network-interface-in-rhel-centos-7-0/
|
||||
[5]:http://www.tecmint.com/remove-unwanted-services-in-centos-7/
|
||||
[6]:http://www.pool.ntp.org/en/
|
||||
Loading…
Reference in New Issue
Block a user