mirror of
https://github.com/LCTT/TranslateProject.git
synced 2025-01-13 22:30:37 +08:00
Merge branch 'LCTT/master'
This commit is contained in:
Xingyu Wang
commit
db5d5cca82
140
published/20190111 Top 5 Linux Distributions for Productivity.md
Normal file
140
published/20190111 Top 5 Linux Distributions for Productivity.md
Normal file
@ -0,0 +1,140 @@
|
||||
[#]: collector: "lujun9972"
|
||||
[#]: translator: "qfzy1233"
|
||||
[#]: reviewer: "wxy"
|
||||
[#]: publisher: "wxy"
|
||||
[#]: url: "https://linux.cn/article-11028-1.html"
|
||||
[#]: subject: "Top 5 Linux Distributions for Productivity"
|
||||
[#]: via: "https://www.linux.com/blog/learn/2019/1/top-5-linux-distributions-productivity"
|
||||
[#]: author: "Jack Wallen https://www.linux.com/users/jlwallen"
|
||||
|
||||
5 个最具生产力的 Linux 发行版
|
||||
======
|
||||
|
||||
> 如果你正在寻找一个适合开发工作的完美环境，我敢说你找不到比 Pop!_OS 更好的选择。
|
||||
|
||||
|
||||
|
||||
必须承认的是，这样的一个热门话题其实很难被总结的话题。为什么呢？首先，Linux 在就是一种有生产力的操作系统。由于它极强的可靠性和稳定的平台，使得完成工作变得很容易。其次为了衡量工作的效率，你需要考虑到哪项工作需要得到生产力方面的助推。是日常办公？开发类工作？学校事务？数据挖掘？或者是人力资源？你可以看到这个问题有多复杂。
|
||||
|
||||
然而，这并不意味着某些发行版无法更好地配置将底层操作系统呈现为一个有效的平台来完成工作。恰恰相反，许多发行版在偏离生产力这条道路上越走越远，所以你不会意识到你自己处在工作的窘境中，而是继续挖掘自己的潜力在工期结束之前拼命赶上进度。这些 Linux 发行版可以帮助你化繁为简，因此或许可以减少你工作流程中的痛点。
|
||||
|
||||
让我们来看一下这些发行版并为你找出适合你的最佳选择。为了更具条理，我按照生产力诉求把它们分成了几类。这项任务本身也是一种挑战，因为每个人在生产力提升上的需要是千差万别的。然而，我所关注的是下列的几项：
|
||||
|
||||
* 常规：适于那些只需要有效地完成多项工作的人。
|
||||
* 设计：适于那些从事设计创造和图像处理的人。
|
||||
* 开发：适于那些使用 Linux 桌面发行版来进行编程工作的人。
|
||||
* 运维：适于那些需要一个发行版来促进其执行系统管理任务的人。
|
||||
* 教育：适于那些需要桌面发行版可以助力他们在教育领域更高效的人。
|
||||
|
||||
诚然，有很多很多类别的发行版可供挑选，其中的很多可能用起来十分得心应手，但这五种或许是你最为需要的。
|
||||
|
||||
### 常规
|
||||
|
||||
对于常规的生产力诉求来说，你不会找到比 [Ubuntu][1] 更为高效的了。在这个类别中首推 Ubuntu 最主要的原因是因为它实现了桌面操作系统、软件、服务的无缝集成。你可能会问为什么我不选择同类别的 Linux Mint 呢？因为 Ubuntu 现在默认的的桌面环境为 GNOME 桌面，而它拥有 GNOME 许多扩展程序的优势的加成（图 1）。
|
||||
|
||||
![GNOME Clipboard][3]
|
||||
|
||||
*图 1：运行中的 GNOME 桌面的剪切板管理工具。*
|
||||
|
||||
这些扩展程序在提升生产力方面做了很多努力（所以 Ubuntu 比 Linux Mint 获得了更多的认可）。但是 Ubuntu 不仅仅是装了一个普通的 GNOME 桌面。事实上，他们致力于将它改进的更为轻量化、更为高效、以及用户友好度更高、开箱即用。总而言之，由于 Ubuntu 正确的融合了多种特性，开箱即用，完善的软件支持（仅对工作方面而言），这些特性使它几乎成为了生产力领域最为完美的一个平台。
|
||||
|
||||
不管你是要写一篇文档，制作一张电子表格，写一个新的软件，开发公司的网站，设计商用的图形，管理一个服务器或是网络，抑或是在你的公司内从事人力资源管理工作，Ubuntu 都可以满足你的需求。Ubuntu 桌面发行版也并不要求你耗费很大的精力才能开始开始开展工作……它直接就能使用（并且工作的十分优秀）。最后，得益于它是基于 Debian 的，使得在 Ubuntu 上安装第三方的软件十分简便。
|
||||
|
||||
很难不支持这一发行版独占生产力发行版列表的鳌头，尽管 Ubuntu 几乎已经成为几乎所有“某某类顶级发行版”列表的榜首。
|
||||
|
||||
### 设计
|
||||
|
||||
如果你正在寻求提升你的平面设计效率，你不能错过 [Fedora 设计套件][5]。这一 Fedora 衍生版是由负责 Fedora 相关的艺术作品的团队亲自操刀制作的。虽然其默认选择的应用程序并不是一个庞大的工具集合，但它所包含的工具都是创建和处理图像专用的。
|
||||
|
||||
有了 GIMP、Inkscape、Darktable、Krita、Entangle、Blender、Pitivi、Scribus 等应用程序（图 2），你可以找到完成图像编辑工作所需要的一切。但是 Fedora 设计套件并不仅限于此。这个桌面平台还包括一堆教程，涵盖了许多已安装的应用程序。对于任何想要尽可能提高效率的人来说，这将是一些非常有用的信息。不过，我要说的是，GNOME 收藏夹中的教程并没有超乎[此页中][6]链接的内容。
|
||||
|
||||
![Fedora Design Suite Favorites][8]
|
||||
|
||||
*图 2：Fedora 设计套件收藏夹菜单包含了许多工具，可以让你用于图形设计。*
|
||||
|
||||
那些使用数码相机的用户肯定会喜欢 Entangle 应用程序，它可以让你在电脑上控制单反相机。
|
||||
|
||||
### 开发
|
||||
|
||||
几乎所有的 Linux 发行版都是程序员的绝佳平台。然而，有一种特定的发行版脱颖而出，并超越了其他发行版，它将是你见过的用于编程类最有效率的工具之一。这个操作系统来自 [System76][9]（LCTT 译注：一家美国的计算机制造商），名为 [Pop!\_OS][10]。Pop!\_OS 是专门为创作者定制的，但不是针对艺术类。相反，Pop!\_OS 面向专门从事开发、编程和软件制作的程序员。如果你需要一个既能完美的胜任开发工作又包含符合使用习惯的桌面操作系统的开发环境，Pop!\_OS 将会是你的不二选择。（图 3）
|
||||
|
||||
可能会让你感到惊讶（考虑到这个操作系统是多么“年轻”）的是 Pop!\_OS 也是你将使用的基于 GNOME 平台的最稳定系统的之一。这意味着 Pop!\_OS 不只是为创作者和创客准备的，也是为任何想要一个可靠的操作系统的人准备的。你可以下载针对你的硬件的专门 ISO 文件，这一点是许多用户十分欣赏的。如果你有英特尔硬件，[下载][10] Intel 或 AMD 的版本。如果你的显卡是 NVIDIA，请下载该特定版本。不管怎样，你肯定会得到针对不同平台进行特殊定制的稳定版本。
|
||||
|
||||
![Pop!_OS][12]
|
||||
|
||||
*图 3：装有 GNOME 桌面的 Pop!_OS 一览。*
|
||||
|
||||
有趣的是，在 Pop!\_OS 中，你不会找到太多预装的开发工具。你也不会找到 IDE 或许多其他开发工具。但是，你可以在 Pop 商店中中找到所需的所有开发工具。
|
||||
|
||||
### 运维
|
||||
|
||||
如果你正在寻找适合系统管理的最具生产力的发行版，[Debian][13] 将会是你的不二之选。为什么这么说呢？因为 Debian 不仅仅拥有无与伦比的可靠性，它也是众多能从苦海中将你解救出来的最好的一个发行版。Debian 是易用性和无限可能性的完美结合。最重要的是，因为它是许多其他发行版的基础，所以可以打赌，如果你需要一个任务的管理工具，那么它一定支持 Debian 系统。当然，我们讨论的是一般的系统管理任务，这意味着大多数时候你需要使用终端窗口 SSH 连接到服务器（图 4），或者在浏览器上使用网络上基于 web 的 GUI 工具。既然如此为什么还要使用一个增加复杂性的桌面呢（比如 Fedora 中的 SELinux 或 openSUSE 中的 YaST）呢？所以，应选择更为简洁易用的那一种。
|
||||
|
||||
![Debian][15]
|
||||
|
||||
*图 4：在 Debian 系统上通过 SSH 连接到远程服务器。*
|
||||
|
||||
你可以选择你想要的不同的桌面（包括 GNOME、Xfce、KDE、Cinnamon、MATE、LXDE），可以确保你所使用的桌面外观最适合你的工作习惯。
|
||||
|
||||
### 教育
|
||||
|
||||
如果你是一名老师或学生，抑或是其他从事与教育相关工作的人士，你需要适当的工具来提高生产力。之前，有 Edubuntu 这样的版本。这一版本位列教育类相关发行版排名的前列。然而，自从 Ubuntu 14.04 版之后这一发行版就再也没有更新。还好，现在有一款基于 openSUSE 的新的以教育为基础的发行版有望夺摘得桂冠。这一改版叫做 [openSUSE:Education-Li-f-e][16]（Li-f-e：Linux For Education - 图 5），它基于 openSUSE Leap 42.1 （所以它可能稍微有一点过时）。
|
||||
|
||||
openSUSE:Education-Li-f-e 包含了以下工具：
|
||||
|
||||
* Brain Workshop（大脑工坊）：一种基于 dual n-back 模式的大脑训练软件（LCTT 译注：dual n-back 训练是一种科学的智力训练方法，可以改善人的工作记忆和流体智力）
|
||||
* GCompris：一种针对青少年的教育软件包
|
||||
* gElemental：一款元素周期表查看工具
|
||||
* iGNUit：一款通用的记忆卡片工具
|
||||
* Little Wizard：基于 Pascal 语言的少儿编程开发环境
|
||||
* Stellarium：天文模拟器
|
||||
* TuxMath：数学入门游戏
|
||||
* TuxPaint：一款少儿绘画软件
|
||||
* TuxType：一款为少儿准备的打字入门软件
|
||||
* wxMaxima：一个跨平台的计算机代数系统
|
||||
* Inkscape：矢量图形编辑软件
|
||||
* GIMP：图像处理软件（LCTT 译注：被誉为 Linux 上的 PhotoShop）
|
||||
* Pencil：GUI 模型制作工具
|
||||
* Hugin：全景照片拼接及 HDR 效果混合软件
|
||||
|
||||
|
||||
![Education][18]
|
||||
|
||||
*图 5：openSUSE:Education-Li-f-e 发行版拥有大量的工具可以帮你在学校中变得更为高效。*
|
||||
|
||||
同时还集成在 openSUSE:Education-Li-f-e 中的还有 [KIWI-LTSP Server][19] 。KIWI-LTSP 服务器是一个灵活的、经济高效的解决方案，旨在使全世界的学校、企业和组织能够轻松地安装和部署桌面工作站。虽然这可能不会直接帮助学生变得更具生产力，但它肯定会使教育机构在部署供学生使用的桌面时更有效率。有关配置 KIWI-LTSP 的更多信息，请查看 openSUSE [KIWI-LTSP 快速入门指南][20]。
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://www.linux.com/blog/learn/2019/1/top-5-linux-distributions-productivity
|
||||
|
||||
作者：[Jack Wallen][a]
|
||||
选题：[lujun9972][b]
|
||||
译者：[qfzy1233](https://github.com/qfzy1233)
|
||||
校对：[wxy](https://github.com/wxy)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
||||
[a]: https://www.linux.com/users/jlwallen
|
||||
[b]: https://github.com/lujun9972
|
||||
[1]: https://www.ubuntu.com/
|
||||
[2]: /files/images/productivity1jpg
|
||||
[3]: https://www.linux.com/sites/lcom/files/styles/rendered_file/public/productivity_1.jpg?itok=yxez3X1w "GNOME Clipboard"
|
||||
[4]: /licenses/category/used-permission
|
||||
[5]: https://labs.fedoraproject.org/en/design-suite/
|
||||
[6]: https://fedoraproject.org/wiki/Design_Suite/Tutorials
|
||||
[7]: /files/images/productivity2jpg
|
||||
[8]: https://www.linux.com/sites/lcom/files/styles/rendered_file/public/productivity_2.jpg?itok=ke0b8qyH "Fedora Design Suite Favorites"
|
||||
[9]: https://system76.com/
|
||||
[10]: https://system76.com/pop
|
||||
[11]: /files/images/productivity3jpg-0
|
||||
[12]: https://www.linux.com/sites/lcom/files/styles/rendered_file/public/productivity_3_0.jpg?itok=8UkCUfsD "Pop!_OS"
|
||||
[13]: https://www.debian.org/
|
||||
[14]: /files/images/productivity4jpg
|
||||
[15]: https://www.linux.com/sites/lcom/files/styles/rendered_file/public/productivity_4.jpg?itok=c9yD3Xw2 "Debian"
|
||||
[16]: https://en.opensuse.org/openSUSE:Education-Li-f-e
|
||||
[17]: /files/images/productivity5jpg
|
||||
[18]: https://www.linux.com/sites/lcom/files/styles/rendered_file/public/productivity_5.jpg?itok=oAFtV8nT "Education"
|
||||
[19]: https://en.opensuse.org/Portal:KIWI-LTSP
|
||||
[20]: https://en.opensuse.org/SDB:KIWI-LTSP_quick_start
|
||||
[21]: https://training.linuxfoundation.org/linux-courses/system-administration-training/introduction-to-linux
|
||||
@ -1,30 +1,30 @@
|
||||
[#]: collector: (lujun9972)
|
||||
[#]: translator: (murphyzhao)
|
||||
[#]: reviewer: ( )
|
||||
[#]: publisher: ( )
|
||||
[#]: url: ( )
|
||||
[#]: reviewer: (wxy)
|
||||
[#]: publisher: (wxy)
|
||||
[#]: url: (https://linux.cn/article-11027-1.html)
|
||||
[#]: subject: (Applications for writing Markdown)
|
||||
[#]: via: (https://fedoramagazine.org/applications-for-writing-markdown/)
|
||||
[#]: author: (Ryan Lerch https://fedoramagazine.org/author/ryanlerch/)
|
||||
|
||||
撰写 Markdown 的软件
|
||||
三个在 Fedora 平台上撰写 Markdown 的软件
|
||||
======
|
||||
|
||||
![][1]
|
||||
|
||||
Markdown 是一种轻量级标记语言，添加格式后，以纯文本格式查看时依然保持可读性。Markdown（和 Markdown 衍生物）被广泛用作 GitHub 和 pagure 等服务上文档标记的主要形式。根据设计，可以在文本编辑器中轻松创建和编辑 Markdown，但是，有许多编辑器可以提供 Markdown 标记的格式化预览，或提供 markdown 语法高亮显示。
|
||||
Markdown 是一种轻量级标记语言，可以在添加格式后以纯文本格式查看时依然保持可读性。Markdown（和 Markdown 衍生物）被广泛用作 GitHub 和 pagure 等服务上格式化文档的主要形式。根据其设计，可以在文本编辑器中轻松创建和编辑 Markdown，但是，有许多编辑器可以提供 Markdown 标记的格式化预览，或提供 Markdown 语法高亮显示。
|
||||
|
||||
本文介绍了针对 Fedora 平台的 3 个桌面应用程序，以帮助编辑 Markdown。
|
||||
|
||||
### UberWriter
|
||||
|
||||
[UberWriter][2] 是一个小巧的 Markdown 编辑器和预览器，允许您编辑文本，并预览渲染的文档。
|
||||
[UberWriter][2] 是一个小巧的 Markdown 编辑器和预览器，允许你以文本方式编辑，并预览渲染的文档。
|
||||
|
||||
![][3]
|
||||
|
||||
编辑器本身具有内置的内联预览，因此标记为粗体的文本以粗体显示。编辑器还提供图像、公式、脚注等标记的内联预览。按住 Ctrl 键单击其中的一个标记可以即时预览要显示的元素。
|
||||
该编辑器本身具有内置的内联预览，因此标记为粗体的文本以粗体显示。编辑器还提供图像、公式、脚注等标记的内联预览。按住 `Ctrl` 键单击其中的一个标记可以即时预览要显示的元素。
|
||||
|
||||
除了编辑器功能外，UberWriter 还具有全屏模式和聚焦模式，有助于最大限度地减少干扰。焦点模式将以灰色显示除当前段落以外的所有内容，以帮助您专注于文档中当前元素。
|
||||
除了编辑器功能外，UberWriter 还具有全屏模式和聚焦模式，有助于最大限度地减少干扰。焦点模式将以灰色显示除当前段落以外的所有内容，以帮助你专注于文档中当前元素。
|
||||
|
||||
从第三方 Flathub 存储库安装 UberWriter 到 Fedora 平台。在将系统[设置为从 Flathub 安装][4]后，可以直接从 Software 应用程序中安装它。
|
||||
|
||||
@ -34,13 +34,13 @@ Marker 是一个 Markdown 编辑器，它提供了一个简单的文本编辑器
|
||||
|
||||
![][5]
|
||||
|
||||
此外，Marker 允许您以各种格式导出文档，包括 HTML、PDF 和开放文档格式（ODF）。
|
||||
此外，Marker 允许你以各种格式导出文档，包括 HTML、PDF 和开放文档格式（ODF）。
|
||||
|
||||
从第三方 Flathub 存储库安装 Marker 到 Fedora 平台。在将系统[设置为从 Flathub 安装][4]后，可以直接从 Software 应用程序中安装它。
|
||||
|
||||
### Ghostwriter
|
||||
|
||||
以前的编辑更专注于最小的用户体验，Ghostwriter 提供了更多的功能和选项。Ghostwriter 提供了一个文本编辑器，当您以 Markdown 格式书写时，编辑器将 Markdown 部分样式化。粗体标记文本显示为粗体，标题标记显示为较大的字体，以帮助编写 Markdown 标记。
|
||||
以前的编辑更专注于最小的用户体验，Ghostwriter 提供了更多的功能和选项。Ghostwriter 提供了一个文本编辑器，当你以 Markdown 格式书写时，编辑器将 Markdown 部分样式化。粗体标记文本显示为粗体，标题标记显示为较大的字体，以帮助编写 Markdown 标记。
|
||||
|
||||
![][6]
|
||||
|
||||
@ -60,8 +60,8 @@ via: https://fedoramagazine.org/applications-for-writing-markdown/
|
||||
|
||||
作者：[Ryan Lerch][a]
|
||||
选题：[lujun9972][b]
|
||||
译者：[译者ID](https://github.com/译者ID)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
译者：[murphyzhao](https://github.com/murphyzhao)
|
||||
校对：[wxy](https://github.com/wxy)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
||||
@ -1,8 +1,8 @@
|
||||
[#]: collector: (lujun9972)
|
||||
[#]: translator: (geekpi)
|
||||
[#]: reviewer: ( )
|
||||
[#]: publisher: ( )
|
||||
[#]: url: ( )
|
||||
[#]: reviewer: (wxy)
|
||||
[#]: publisher: (wxy)
|
||||
[#]: url: (https://linux.cn/article-11031-1.html)
|
||||
[#]: subject: (Using i3 with multiple monitors)
|
||||
[#]: via: (https://fedoramagazine.org/using-i3-with-multiple-monitors/)
|
||||
[#]: author: (Adam Šamalík https://fedoramagazine.org/author/asamalik/)
|
||||
@ -12,13 +12,13 @@
|
||||
|
||||
![][1]
|
||||
|
||||
你在 Linux 工作站上使用多个显示器吗？一次看到很多东西可能是有益的。但在我们的工作中通常有比实际显示器更多的窗口 - 这是一件好事，因为一次看到太多东西可能会分散注意力。因此能够切换我们在单个显示器上看到的内容似乎很重要。
|
||||
你在 Linux 工作站上使用多个显示器吗？一次看到很多东西可能是有益的。但在我们的工作中通常有比实际显示器更多的窗口 —— 这是一件好事，因为一次看到太多东西可能会分散注意力。因此能够切换我们在单个显示器上看到的内容似乎很重要。
|
||||
|
||||
让我们来谈谈 i3，它是一个流行的平铺窗口管理器，可以与多个显示器配合使用。并且有许多其他窗口管理器没有的便利功能，它能够独立地在各个显示器上切换工作区。
|
||||
让我们来看看 i3，它是一个流行的平铺窗口管理器，可以与多个显示器配合使用。并且有许多其他窗口管理器没有的便利功能，它能够独立地在各个显示器上切换工作区。
|
||||
|
||||
### 快速介绍 i3
|
||||
|
||||
大约三年前，[Fedora Magazine 已经写了一篇关于 i3 的文章][2]。这是有史以来最受欢迎的文章之一！虽然情况并非总是如此，但 i3 非常稳定，而且这篇文章如今也很准确。所以，这次不会重复太多，本篇只涵盖了让 i3 启动和运行，如果你是 i3 的新手，想要了解更多基础知识的话，欢迎你继续阅读。
|
||||
大约三年前，[Fedora Magazine 已经写了一篇关于 i3 的文章][2]。这是有史以来最受欢迎的文章之一！虽然情况并非总是如此，但 i3 非常稳定，而且那篇文章如今也很准确。所以，这次不会重复太多内容，本篇只涵盖了让 i3 启动和运行的极少内容，如果你是 i3 的新手，想要了解更多基础知识的话，欢迎你继续阅读。
|
||||
|
||||
要在系统上安装 i3，请运行以下命令：
|
||||
|
||||
@ -28,7 +28,7 @@ $ sudo dnf install i3
|
||||
|
||||
完成后，注销，然后在登录屏幕上选择 i3 作为窗口管理器，然后重新登录。
|
||||
|
||||
当你第一次运行 i3 时，系统会询问你是否要继续进行自动配置 - 在此处回答是。之后，你将被要求选择 “mod 键”。如果你在这里不确定，只需接受默认值，即将 Windows/Super 键设置为 mod 键。你将主要使用此键用于窗口管理器中的快捷方式。
|
||||
当你第一次运行 i3 时，系统会询问你是否要继续进行自动配置 —— 在此处回答是。之后，你将被要求选择 “mod 键”。如果你不确定，只需接受默认值，即将 Windows/Super 键设置为 mod 键。你将主要使用此键用于窗口管理器中的快捷方式。
|
||||
|
||||
此时，你应该在底部看到一个小条和一个空白屏幕。我们来看看一些基本的快捷方式。
|
||||
|
||||
@ -72,7 +72,7 @@ $mod + shift + q
|
||||
|
||||
还有更多的快捷方式，但这些足够让你开始使用 i3。
|
||||
|
||||
要退出 i3（退出登录）按：
|
||||
要退出 i3（并退出登录）按：
|
||||
|
||||
```
|
||||
$mod + shift + e
|
||||
@ -84,9 +84,9 @@ $mod + shift + e
|
||||
|
||||
现在我们已经启动并运行了 i3，让我们把所有这些屏幕都用到！
|
||||
|
||||
为此，我们需要使用命令行，因为 i3 非常轻量级，并且没有 gui 来管理其他屏幕。如果这听起来很难也不用担心，它实际上非常简单！
|
||||
为此，我们需要使用命令行，因为 i3 非常轻量级，并且没有 GUI 来管理其他屏幕。如果这听起来很难也不用担心，它实际上非常简单！
|
||||
|
||||
我们将使用的命令称为 xrandr。如果你的系统上没有 xrandr，请运行以下命令安装：
|
||||
我们将使用的命令称为 `xrandr`。如果你的系统上没有 `xrandr`，请运行以下命令安装：
|
||||
|
||||
```
|
||||
$ sudo dnf install xrandr
|
||||
@ -98,7 +98,7 @@ $ sudo dnf install xrandr
|
||||
$ xrandr
|
||||
```
|
||||
|
||||
输出列出了所有可用输出，并通过显示支持的分辨率指示哪些输出连接了屏幕（通过电缆连接的显示器）。好消息是，我们不需要关心使它们工作的分辨率。
|
||||
输出列出了所有可用输出设备，并通过显示支持的分辨率指示哪些输出连接了屏幕（通过电缆连接的显示器）。好消息是，我们不需要关心使它们工作的分辨率。
|
||||
|
||||
这个例子显示了笔记本电脑的主屏幕（名为 eDP1），以及连接到 HDMI-2 输出的第二个显示器，它位于笔记本电脑的右侧。要打开它，请运行以下命令：
|
||||
|
||||
@ -108,7 +108,7 @@ $ xrandr --output HDMI-2 --auto --right-of eDP1
|
||||
|
||||
就是这样！你的屏幕现已激活。
|
||||
|
||||
![Second screen active. The commands shown on this screenshot are slightly different than in the article, as they set a smaller resolution to make the screenshots more readable.][3]
|
||||
![第二个屏幕激活。截屏上显示命令与文章中略有不同，它设置了更小的分辨率以使截屏适合阅读][3]
|
||||
|
||||
### 在多个屏幕上管理工作区
|
||||
|
||||
@ -122,11 +122,11 @@ $mod + NUMBER
|
||||
|
||||
你可以独立切换各个显示器上的工作区！
|
||||
|
||||
![Workspace 2 on the left screen, workspace 4 on the right screen.][4]
|
||||
![工作空间 2 在左侧屏幕，工作空间 4 在右侧屏幕][4]
|
||||
|
||||
![Left screen switched to workspace 3, right screen still showing workspace 4.][5]
|
||||
![左侧屏幕切换为工作空间 3，右侧屏幕仍为工作空间 4][5]
|
||||
|
||||
![Right screen switched to workspace 4, left screen still showing workspace 3.][6]
|
||||
![右侧屏幕切换为工作空间 5，左侧屏幕仍为空间空间 3][6]
|
||||
|
||||
### 在显示器之间移动工作区
|
||||
|
||||
@ -138,7 +138,7 @@ $mod + shift + NUMBER
|
||||
|
||||
我们也可以将工作区移动到不同的屏幕。但是，此操作没有默认快捷方式，因此我们必须先创建它。
|
||||
|
||||
要创建自定义快捷方式，你需要在你选择的文本编辑器中打开配置文件（本文使用 _vim_）：
|
||||
要创建自定义快捷方式，你需要在你选择的文本编辑器中打开配置文件（本文使用 `vim`）：
|
||||
|
||||
```
|
||||
$ vim ~/.config/i3/config
|
||||
@ -163,9 +163,9 @@ $mod + shift + r
|
||||
$mod + p
|
||||
```
|
||||
|
||||
![Workspace 2 with Firefox on the left screen][7]
|
||||
![打开火狐浏览器的工作空间 2 在左侧][7]
|
||||
|
||||
![Workspace 2 with Firefox moved to the second screen][8]
|
||||
![打开火狐浏览器的工作空间 2 移动到第二个屏幕][8]
|
||||
|
||||
就是这些了！享受你的新多显示器体验，并了解更多 i3，欢迎阅读 Fedora Magazine 上之前关于 i3 的文章，或者查看官方 i3 文档。
|
||||
|
||||
@ -176,7 +176,7 @@ via: https://fedoramagazine.org/using-i3-with-multiple-monitors/
|
||||
作者：[Adam Šamalík][a]
|
||||
选题：[lujun9972][b]
|
||||
译者：[geekpi](https://github.com/geekpi)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
校对：[wxy](https://github.com/wxy)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
||||
@ -1,106 +0,0 @@
|
||||
[#]: collector: (lujun9972)
|
||||
[#]: translator: (hopefully2333)
|
||||
[#]: reviewer: ( )
|
||||
[#]: publisher: ( )
|
||||
[#]: url: ( )
|
||||
[#]: subject: (Cisco to buy IoT security, management firm Sentryo)
|
||||
[#]: via: (https://www.networkworld.com/article/3400847/cisco-to-buy-iot-security-management-firm-sentryo.html)
|
||||
[#]: author: (Michael Cooney https://www.networkworld.com/author/Michael-Cooney/)
|
||||
|
||||
Cisco to buy IoT security, management firm Sentryo
|
||||
======
|
||||
Buying Sentryo will give Cisco support for anomaly and real-time threat detection for the industrial internet of things.
|
||||
![IDG Worldwide][1]
|
||||
|
||||
Looking to expand its IoT security and management offerings Cisco plans to acquire [Sentryo][2], a company based in France that offers anomaly detection and real-time threat detection for Industrial Internet of Things ([IIoT][3]) networks.
|
||||
|
||||
Founded in 2014 Sentryo products include ICS CyberVision – an asset inventory, network monitoring and threat intelligence platform – and CyberVision network edge sensors, which analyze network flows.
|
||||
|
||||
**More on IoT:**
|
||||
|
||||
* [What is the IoT? How the internet of things works][4]
|
||||
* [What is edge computing and how it’s changing the network][5]
|
||||
* [Most powerful Internet of Things companies][6]
|
||||
* [10 Hot IoT startups to watch][7]
|
||||
* [The 6 ways to make money in IoT][8]
|
||||
* [What is digital twin technology? [and why it matters]][9]
|
||||
* [Blockchain, service-centric networking key to IoT success][10]
|
||||
* [Getting grounded in IoT networking and security][11]
|
||||
* [Building IoT-ready networks must become a priority][12]
|
||||
* [What is the Industrial IoT? [And why the stakes are so high]][13]
|
||||
|
||||
|
||||
|
||||
“We have incorporated Sentryo’s edge sensor and our industrial networking hardware with Cisco’s IOx application framework,” wrote Rob Salvagno, Cisco vice president of Corporate Development and Cisco Investments in a [blog][14] about the proposed buy.
|
||||
|
||||
“We believe that connectivity is foundational to IoT projects and by unleashing the power of the network we can dramatically improve operational efficiencies and uncover new business opportunities. With the addition of Sentryo, Cisco can offer control systems engineers deeper visibility into assets to optimize, detect anomalies and secure their networks.”
|
||||
|
||||
Gartner [wrote][15] of Sentryo’s system: “ICS CyberVision product provides visibility into its customers'' OT networks in way all OT users will understand, not just technical IT staff. With the increased focus of both hackers and regulators on industrial control systems, it is vital to have the right visibility of an organization’s OT. Many OT networks not only are geographically dispersed, but also are complex and consist of hundreds of thousands of components.”
|
||||
|
||||
Sentryo's ICS CyberVision lets enterprises ensure continuity, resilience and safety of their industrial operations while preventing possible cyberattacks, said [Nandini Natarajan][16] , industry analyst at Frost & Sullivan. "It automatically profiles assets and communication flows using a unique 'universal OT language' in the form of tags, which describe in plain text what each asset is doing. ICS CyberVision gives anyone immediate insights into an asset's role and behaviors; it offers many different analytic views leveraging artificial intelligence algorithms to let users deep-dive into the vast amount of data a typical industrial control system can generate. Sentryo makes it easy to see important or relevant information."
|
||||
|
||||
In addition, Sentryo's platform uses deep packet inspection (DPI) to extract information from communications among industrial assets, Natarajan said. This DPI engine is deployed through an edge-computing architecture that can run either on Sentryo sensor appliances or on network equipment that is already installed. Thus, Sentryo can embed visibility and cybersecurity features in the industrial network rather than deploying an out-of-band monitoring network, Natarajan said.
|
||||
|
||||
**[[Prepare to become a Certified Information Security Systems Professional with this comprehensive online course from PluralSight. Now offering a 10-day free trial!][17] ]**
|
||||
|
||||
Sentryo’s technology will broaden [Cisco’s][18] overarching IoT plan. In January it [launched][19] a family of switches, software, developer tools and blueprints to meld IoT and industrial networking with [intent-based networking][20] (IBN) and classic IT security, monitoring and application-development support.
|
||||
|
||||
The new platforms can be managed by Cisco’s DNA Center, and Cisco IoT Field Network Director, letting customers fuse their IoT and industrial-network control with their business IT world.
|
||||
|
||||
DNA Center is Cisco’s central management tool for enterprise networks, featuring automation capabilities, assurance setting, fabric provisioning and policy-based segmentation. It is also at the center of the company’s IBN initiative offering customers the ability to automatically implement network and policy changes on the fly and ensure data delivery. The IoT Field Network Director is software that manages multiservice networks of Cisco industrial, connected grid routers and endpoints.
|
||||
|
||||
Liz Centoni, senior vice president and general manager of Cisco's IoT business group said the company expects the [Sentryo technology to help][21] IoT customers in a number of ways:
|
||||
|
||||
Network-enabled, passive DPI capabilities to discover IoT and OT assets, and establish communication patterns between devices and systems. Sentryo’s sensor is natively deployable on Cisco’s IOx framework and can be built into the industrial network these devices run on instead of adding additional hardware.
|
||||
|
||||
As device identification and communication patterns are created, Cisco will integrate this with DNA Center and Identity Services Engine(ISE) to allow customers to easily define segmentation policy. This integration will allow OT teams to leverage IT security teams’ expertise to secure their environments without risk to the operational processes.
|
||||
|
||||
With these IoT devices lacking modern embedded software and security capabilities, segmentation will be the key technology to allow communication from operational assets to the rightful systems, and reduce risk of cyber security incidents like we saw with [WannaCry][22] and [Norsk Hydro][23].
|
||||
|
||||
According to [Crunchbase][24], Sentryo has $3.5M in estimated revenue annually and it competes most closely with Cymmetria, Team8, and Indegy. The acquisition is expected to close before the end of Cisco’s Q1 Fiscal Year 2020 -- October 26, 2019. Financial details of the acquisition were not detailed.
|
||||
|
||||
Sentryo is Cisco’s second acquisition this year. It bought Singularity for its network analytics technology in January. In 2018 Cisco bought six companies including Duo security software.
|
||||
|
||||
** **
|
||||
|
||||
Join the Network World communities on [Facebook][25] and [LinkedIn][26] to comment on topics that are top of mind.
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://www.networkworld.com/article/3400847/cisco-to-buy-iot-security-management-firm-sentryo.html
|
||||
|
||||
作者：[Michael Cooney][a]
|
||||
选题：[lujun9972][b]
|
||||
译者：[译者ID](https://github.com/译者ID)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
||||
[a]: https://www.networkworld.com/author/Michael-Cooney/
|
||||
[b]: https://github.com/lujun9972
|
||||
[1]: https://images.idgesg.net/images/article/2018/09/nwan_019_iiot-100771131-large.jpg
|
||||
[2]: https://www.sentryo.net/
|
||||
[3]: https://www.networkworld.com/article/3243928/what-is-the-industrial-iot-and-why-the-stakes-are-so-high.html
|
||||
[4]: https://www.networkworld.com/article/3207535/internet-of-things/what-is-the-iot-how-the-internet-of-things-works.html
|
||||
[5]: https://www.networkworld.com/article/3224893/internet-of-things/what-is-edge-computing-and-how-it-s-changing-the-network.html
|
||||
[6]: https://www.networkworld.com/article/2287045/internet-of-things/wireless-153629-10-most-powerful-internet-of-things-companies.html
|
||||
[7]: https://www.networkworld.com/article/3270961/internet-of-things/10-hot-iot-startups-to-watch.html
|
||||
[8]: https://www.networkworld.com/article/3279346/internet-of-things/the-6-ways-to-make-money-in-iot.html
|
||||
[9]: https://www.networkworld.com/article/3280225/internet-of-things/what-is-digital-twin-technology-and-why-it-matters.html
|
||||
[10]: https://www.networkworld.com/article/3276313/internet-of-things/blockchain-service-centric-networking-key-to-iot-success.html
|
||||
[11]: https://www.networkworld.com/article/3269736/internet-of-things/getting-grounded-in-iot-networking-and-security.html
|
||||
[12]: https://www.networkworld.com/article/3276304/internet-of-things/building-iot-ready-networks-must-become-a-priority.html
|
||||
[13]: https://www.networkworld.com/article/3243928/internet-of-things/what-is-the-industrial-iot-and-why-the-stakes-are-so-high.html
|
||||
[14]: https://blogs.cisco.com/news/cisco-industrial-iot-news
|
||||
[15]: https://www.globenewswire.com/news-release/2018/06/28/1531119/0/en/Sentryo-Named-a-Cool-Vendor-by-Gartner.html
|
||||
[16]: https://www.linkedin.com/pulse/industrial-internet-things-iiot-decoded-nandini-natarajan/
|
||||
[17]: https://pluralsight.pxf.io/c/321564/424552/7490?u=https%3A%2F%2Fwww.pluralsight.com%2Fpaths%2Fcertified-information-systems-security-professional-cisspr
|
||||
[18]: https://www.cisco.com/c/dam/en_us/solutions/iot/ihs-report.pdf
|
||||
[19]: https://www.networkworld.com/article/3336454/cisco-goes-after-industrial-iot.html
|
||||
[20]: https://www.networkworld.com/article/3202699/what-is-intent-based-networking.html
|
||||
[21]: https://blogs.cisco.com/news/securing-the-internet-of-things-cisco-announces-intent-to-acquire-sentryo
|
||||
[22]: https://blogs.cisco.com/security/talos/wannacry
|
||||
[23]: https://www.securityweek.com/norsk-hydro-may-have-lost-40m-first-week-after-cyberattack
|
||||
[24]: https://www.crunchbase.com/organization/sentryo#section-web-traffic-by-similarweb
|
||||
[25]: https://www.facebook.com/NetworkWorld/
|
||||
[26]: https://www.linkedin.com/company/network-world
|
||||
@ -1,92 +0,0 @@
|
||||
[#]: collector: (lujun9972)
|
||||
[#]: translator: (wahailin)
|
||||
[#]: reviewer: ( )
|
||||
[#]: publisher: ( )
|
||||
[#]: url: ( )
|
||||
[#]: subject: (Raspberry Pi 4 is here!)
|
||||
[#]: via: (https://opensource.com/article/19/6/raspberry-pi-4)
|
||||
[#]: author: (Ben Nuttall https://opensource.com/users/bennuttall)
|
||||
|
||||
Raspberry Pi 4 is here!
|
||||
======
|
||||
A new version of the $35 computer features a 1.5GHz Arm chip and support
|
||||
for dual-HDMI 4K displays, Gigabit Ethernet, and much more.
|
||||
![Raspberry Pi 4 board][1]
|
||||
|
||||
The latest version of the Raspberry Pi—Raspberry Pi 4—was released today, earlier than anticipated, featuring a new 1.5GHz Arm chip and VideoCore GPU with some brand new additions: dual-HDMI 4K display output; USB3 ports; Gigabit Ethernet; and multiple RAM options up to 4GB.
|
||||
|
||||
![Raspberry Pi 4 case][2]
|
||||
|
||||
The Raspberry Pi 4 is a very powerful single-board computer and starts at the usual price of $35. That gets you the standard 1GB RAM, or you can pay $45 for the 2GB model or $55 for the 4GB model—premium-priced models are a first for Raspberry Pi.
|
||||
|
||||
The specs at-a-glance:
|
||||
|
||||
* 64-bit BCM2711 quad-core A72 CPU @ 1.5GHz
|
||||
* VideoCore VI GPU
|
||||
* Gigabit Ethernet port
|
||||
* 1GB, 2GB, or 4GB LPDDR4 RAM
|
||||
* Two Micro-HDMI ports
|
||||
* Two USB3 ports
|
||||
* Two USB2 ports
|
||||
* Dual-band (2.4GHz and 5GHz) WiFi
|
||||
* Bluetooth 5.0
|
||||
* USB Type C power port
|
||||
* CSI camera interface
|
||||
* DSI display interface
|
||||
* MicroSD card slot
|
||||
* Power-over-Ethernet pins
|
||||
* Full compatibility with all previous Raspberry Pi models
|
||||
|
||||
|
||||
|
||||
### USB and networking
|
||||
|
||||
The Raspberry Pi 4 has the benefit of having USB3; it's powered by a USB Type C cable and provides two USB3 ports and two USB2 ports. You can now connect USB3 hard drives and other peripherals and get faster connectivity.
|
||||
|
||||
![Raspberry Pi 4 USBs][3]
|
||||
|
||||
The BCM2835-based chip in Raspberry Pi 1 to 3 provided just one native USB port and no Ethernet, so a USB hub on the board provided more USB ports and an Ethernet port. The 3B+ added a dedicated LAN chip, which gave it Gigabit Ethernet, but this was limited to USB2 speeds. The Pi 4 has dedicated Gigabit Ethernet, and because it's no longer throttled over USB, its networking speeds are much faster.
|
||||
|
||||
The Pi 4 takes advantage of the technology built into the 3B+ that made it the first single-board computer with dual-band WiFi. This means you can connect to both 2.4GHz and 5GHz networks.
|
||||
|
||||
### Displays
|
||||
|
||||
When the first Raspberry Pi launched, the balance of its CPU and GPU performance was tipped heavily in favor of the GPU. The VideoCore IV was a very powerful graphics processor, capable of full-HD 1080p multimedia, which is why the Pi has always been popular as a home media center. The Pi 2 rebalanced things somewhat and brought the CPU in line, taking the Pi from a single-core to a quad-core Arm chip. The Pi 4 takes both factors a big step forward. The new VideoCore VI GPU gives the Pi 4K video and allows two displays via the board's two Micro-HDMI ports (selected to keep the board the same size), so you'll need an adapter or a Micro-to-full HDMI cable to use an HDMI monitor.
|
||||
|
||||
Dual displays are a godsend when you need more screen real estate to keep eye contact with multiple windows—if you're programming you might have your code on one screen and the website or app you're building; your database; your web browser; your emails, or anything else on the other. For the first time, development on Raspberry Pi won't be limited to a single monitor. It's also handy if you want to build a Pi-based project with different things on different screens.
|
||||
|
||||
The Pi also has a Display Serial Interface (DSI) port to drive another special display—not another monitor per se, but the official Raspberry Pi touch screen display connected via a flex cable.
|
||||
|
||||
### Raspbian Buster
|
||||
|
||||
This Raspberry Pi 4's launch coincides with a major Debian release, and the fact the new Pi supports OpenGL ES 3 means it makes sense for any software developed for the Pi 4 to target Raspbian Buster. Buster brings a few user interface tweaks and a whole host of software upgrades, including Python 3.7.
|
||||
|
||||
![Raspbian Buster][4]
|
||||
|
||||
### Open source graphics drivers
|
||||
|
||||
Over the last five years, Eric Anholt has been working to write open source graphics drivers for the Raspberry Pi. Now, Raspbian can use this driver to deliver accelerated web browsing, desktop graphics, and 3D applications on the Pi. This replaces a large chunk of closed-source code that was previously required. Huge thanks to Eric and Broadcom for this effort.
|
||||
|
||||
Previously, the Raspberry Pi 4 was expected to be yet another year away, but the chip design turned out to be ready for production much earlier than anticipated, so here it is!
|
||||
|
||||
* * *
|
||||
|
||||
_The Raspberry Pi 4 is on sale now. Which model will you opt for? Let us know your plans in the comments!_
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://opensource.com/article/19/6/raspberry-pi-4
|
||||
|
||||
作者：[Ben Nuttall][a]
|
||||
选题：[lujun9972][b]
|
||||
译者：[译者ID](https://github.com/译者ID)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
||||
[a]: https://opensource.com/users/bennuttall
|
||||
[b]: https://github.com/lujun9972
|
||||
[1]: https://opensource.com/sites/default/files/styles/image-full-size/public/lead-images/raspberry-pi-4_lead.jpg?itok=2bkk43om (Raspberry Pi 4 board)
|
||||
[2]: https://opensource.com/sites/default/files/uploads/raspberry-pi-4-case.jpg (Raspberry Pi 4 case)
|
||||
[3]: https://opensource.com/sites/default/files/uploads/raspberry-pi-4-usb.jpg (Raspberry Pi 4 USBs)
|
||||
[4]: https://opensource.com/sites/default/files/uploads/raspbian-buster.png (Raspbian Buster)
|
||||
@ -0,0 +1,95 @@
|
||||
[#]: collector: (lujun9972)
|
||||
[#]: translator: ( )
|
||||
[#]: reviewer: ( )
|
||||
[#]: publisher: ( )
|
||||
[#]: url: ( )
|
||||
[#]: subject: (FreeDOS turns 25 years old: An origin story)
|
||||
[#]: via: (https://opensource.com/article/19/6/freedos-anniversary)
|
||||
[#]: author: (Jim Hall https://opensource.com/users/jim-hall)
|
||||
|
||||
FreeDOS turns 25 years old: An origin story
|
||||
======
|
||||
The operating system's history is a great example of the open source
|
||||
software model: developers working together to create something.
|
||||
![FreeDOS fish logo and command prompt on computer][1]
|
||||
|
||||
June 29 marks the 25th anniversary of [FreeDOS][2]. That's a major milestone for any open source software project, and I'm proud of the work that we've done on it over the past quarter century. I'm also proud of how we built FreeDOS because it is a great example of how the open source software model works.
|
||||
|
||||
For its time, MS-DOS was a powerful operating system. I'd used DOS for years, ever since my parents replaced our aging Apple II computer with a newer IBM machine. MS-DOS provided a flexible command line, which I quite liked and that came in handy to manipulate my files. Over the years, I learned how to write my own utilities in C to expand its command-line capabilities even further.
|
||||
|
||||
Around 1994, Microsoft announced that its next planned version of Windows would do away with MS-DOS. But I liked DOS. Even though I had started migrating to Linux, I still booted into MS-DOS to run applications that Linux didn't have yet.
|
||||
|
||||
I figured that if we wanted to keep DOS, we would need to write our own. And that's how FreeDOS was born.
|
||||
|
||||
On June 29, 1994, I made a small announcement about my idea to the comp.os.msdos.apps newsgroup on Usenet.
|
||||
|
||||
> ANNOUNCEMENT OF PD-DOS PROJECT:
|
||||
> A few months ago, I posted articles relating to starting a public domain version of DOS. The general support for this at the time was strong, and many people agreed with the statement, "start writing!" So, I have…
|
||||
>
|
||||
> Announcing the first effort to produce a PD-DOS. I have written up a "manifest" describing the goals of such a project and an outline of the work, as well as a "task list" that shows exactly what needs to be written. I'll post those here, and let discussion follow.
|
||||
|
||||
While I announced the project as PD-DOS (for "public domain," although the abbreviation was meant to mimic IBM's "PC-DOS"), we soon changed the name to Free-DOS and later FreeDOS.
|
||||
|
||||
I started working on it right away. First, I shared the utilities I had written to expand the DOS command line. Many of them reproduced MS-DOS features, including CLS, DATE, DEL, FIND, HELP, and MORE. Some added new features to DOS that I borrowed from Unix, such as TEE and TRCH (a simple implementation of Unix's tr). I contributed over a dozen FreeDOS utilities
|
||||
|
||||
By sharing my utilities, I gave other developers a starting point. And by sharing my source code under the [GNU General Public License][3] (GNU GPL), I implicitly allowed others to add new features and fix bugs.
|
||||
|
||||
Other developers who saw FreeDOS taking shape contacted me and wanted to help. Tim Norman was one of the first; Tim volunteered to write a command shell (COMMAND.COM, later named FreeCOM). Others contributed utilities that replicated or expanded the DOS command line.
|
||||
|
||||
We released our first alpha version as soon as possible. Less than three months after announcing FreeDOS, we had an Alpha 1 distribution that collected our utilities. By the time we released Alpha 5, FreeDOS boasted over 60 utilities. And FreeDOS included features never imagined in MS-DOS, including internet connectivity via a PPP dial-up driver and dual-monitor support using a primary VGA monitor and a secondary Hercules Mono monitor.
|
||||
|
||||
New developers joined the project, and we welcomed them. By October 1998, FreeDOS had a working kernel, thanks to Pat Villani. FreeDOS also sported a host of new features that brought not just parity with MS-DOS but surpassed MS-DOS, including ANSI support and a print spooler that resembled Unix lpr.
|
||||
|
||||
You may be familiar with other milestones. We crept our way towards the 1.0 label, finally releasing FreeDOS 1.0 in September 2006, FreeDOS 1.1 in January 2012, and FreeDOS 1.2 in December 2016. MS-DOS stopped being a moving target long ago, so we didn't need to update as frequently after the 1.0 release.
|
||||
|
||||
Today, FreeDOS is a very modern DOS. We've moved beyond "classic DOS," and now FreeDOS features lots of development tools such as compilers, assemblers, and debuggers. We have lots of editors beyond the plain DOS Edit editor, including Fed, Pico, TDE, and versions of Emacs and Vi. FreeDOS supports networking and even provides a simple graphical web browser (Dillo). And we have tons of new utilities, including many that will make Linux users feel at home.
|
||||
|
||||
FreeDOS got where it is because developers worked together to create something. In the spirit of open source software, we contributed to each other's work by fixing bugs and adding new features. We treated our users as co-developers; we always found ways to include people, whether they were writing code or writing documentation. And we made decisions through consensus based on merit. If that sounds familiar, it's because those are the core values of open source software: transparency, collaboration, release early and often, meritocracy, and community. That's the [open source way][4]!
|
||||
|
||||
I encourage you to download FreeDOS 1.2 and give it a try.
|
||||
|
||||
### More resources
|
||||
|
||||
* [FreeDOS website][2]
|
||||
* [FreeDOS wiki][5]
|
||||
* [Download FreeDOS 1.2][6]
|
||||
* [Free ebooks about FreeDOS][7]
|
||||
* [A gentle introduction to FreeDOS][8]
|
||||
* [The origin and evolution of FreeDOS][9]
|
||||
* [4 cool facts you should know about FreeDOS][10]
|
||||
* [How to upgrade your system BIOS using FreeDOS][11]
|
||||
* [Celebrating 24 years of FreeDOS: Useful commands cheat sheet][12]
|
||||
* [How to run DOS programs in Linux][13]
|
||||
* [Keeping DOS alive and kicking with open source][14]
|
||||
* [Running DOS on the Raspberry Pi][15]
|
||||
|
||||
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://opensource.com/article/19/6/freedos-anniversary
|
||||
|
||||
作者：[Jim Hall][a]
|
||||
选题：[lujun9972][b]
|
||||
译者：[译者ID](https://github.com/译者ID)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
||||
[a]: https://opensource.com/users/jim-hall
|
||||
[b]: https://github.com/lujun9972
|
||||
[1]: https://opensource.com/sites/default/files/styles/image-full-size/public/lead-images/freedos-fish-laptop-color.png?itok=vfv_Lpph (FreeDOS fish logo and command prompt on computer)
|
||||
[2]: https://www.freedos.org/
|
||||
[3]: https://www.gnu.org/licenses/licenses.en.html
|
||||
[4]: https://opensource.com/open-source-way
|
||||
[5]: http://wiki.freedos.org/
|
||||
[6]: https://www.freedos.org/download/
|
||||
[7]: https://www.freedos.org/ebook/
|
||||
[8]: https://opensource.com/article/18/4/gentle-introduction-freedos
|
||||
[9]: https://opensource.com/article/17/10/freedos
|
||||
[10]: https://opensource.com/article/17/6/freedos-still-cool-today
|
||||
[11]: https://opensource.com/article/17/6/upgrade-bios-freedos
|
||||
[12]: https://opensource.com/article/18/6/freedos-commands-cheat-sheet
|
||||
[13]: https://opensource.com/article/17/10/run-dos-applications-linux
|
||||
[14]: https://opensource.com/life/16/9/interview-jim-hall-freedos
|
||||
[15]: https://opensource.com/article/18/3/can-you-run-dos-raspberry-pi
|
||||
@ -1,198 +0,0 @@
|
||||
Translating by MjSeven
|
||||
|
||||
Manage your workstation with Ansible: Configure desktop settings
|
||||
======
|
||||
|
||||
|
||||
|
||||
In the [first article][1] of this series on using Ansible to configure a workstation, we set up a repository and configured a few basic things. In the [second part][2], we automated Ansible to apply settings automatically when changes are made to our repository. In this third (and final) article, we'll use Ansible to configure GNOME desktop settings.
|
||||
|
||||
This configuration will work only on newer distributions (such as Ubuntu 18.04, which I'll use in my examples). Older versions of Ubuntu will not work, as they ship with a version of `python-psutils` that is too old for Ansible's `dconf` module to work properly. If you're using a newer version of your Linux distribution, you should have no issues.
|
||||
|
||||
Before you begin, make sure you've worked through parts one and two of this series, as part three builds upon that groundwork. If you haven't already, download the GitHub repository you've been using in those first two articles. We'll add a few more features to it.
|
||||
|
||||
### Set a wallpaper and lock screen
|
||||
|
||||
First, we'll create a taskbook to hold our GNOME settings. In the root of the repository, you should have a file named `local.yml`. Add the following line to it:
|
||||
```
|
||||
- include: tasks/gnome.yml
|
||||
|
||||
```
|
||||
|
||||
The entire file should now look like this:
|
||||
```
|
||||
- hosts: localhost
|
||||
|
||||
become: true
|
||||
|
||||
pre_tasks:
|
||||
|
||||
- name: update repositories
|
||||
|
||||
apt: update_cache=yes
|
||||
|
||||
changed_when: False
|
||||
|
||||
|
||||
|
||||
tasks:
|
||||
|
||||
- include: tasks/users.yml
|
||||
|
||||
- include: tasks/cron.yml
|
||||
|
||||
- include: tasks/packages.yml
|
||||
|
||||
- include: tasks/gnome.yml
|
||||
|
||||
```
|
||||
|
||||
Basically, this added a reference to a file named `gnome.yml` that will be stored in the `tasks` directory inside the repository. We haven't created this file yet, so let's do that now. Create `gnome.yml` file in the `tasks` directory, and place the following content inside:
|
||||
```
|
||||
- name: Install python-psutil package
|
||||
|
||||
apt: name=python-psutil
|
||||
|
||||
|
||||
|
||||
- name: Copy wallpaper file
|
||||
|
||||
copy: src=files/wallpaper.jpg dest=/home/jay/.wallpaper.jpg owner=jay group=jay mode=600
|
||||
|
||||
|
||||
|
||||
- name: Set GNOME Wallpaper
|
||||
|
||||
become_user: jay
|
||||
|
||||
dconf: key="/org/gnome/desktop/background/picture-uri" value="'file:///home/jay/.wallpaper.jpg'"
|
||||
|
||||
```
|
||||
|
||||
Note that this code refers to my username (`jay`) several times, so make sure to replace every occurrence of `jay` with the username you use on your machine. Also, if you're not using Ubuntu 18.04 (as I am), you'll have to change the `apt` line to match the package manager for your chosen distribution and to confirm the name of the `python-psutil` package for your distribution, as it may be different.
|
||||
|
||||
`wallpaper.jpg` inside the `files` directory. This file must exist or the Ansible configuration will fail. Inside the `tasks` directory, create a subdirectory named `files`. Find a wallpaper image you like, name it `wallpaper.jpg`, and place it inside the `files` directory. If the file is a PNG image instead of a JPG, change the file extension in both the code and in the repository. If you're not feeling creative, I have an example wallpaper file in the
|
||||
|
||||
In the example tasks, I referred to a file namedinside thedirectory. This file must exist or the Ansible configuration will fail. Inside thedirectory, create a subdirectory named. Find a wallpaper image you like, name it, and place it inside thedirectory. If the file is a PNG image instead of a JPG, change the file extension in both the code and in the repository. If you're not feeling creative, I have an example wallpaper file in the [GitHub repository][3] for this article series that you can use.
|
||||
|
||||
Once you've made all these changes, commit everything to your GitHub repository, and push those changes. To recap, you should've completed the following:
|
||||
|
||||
* Modified the `local.yml` file to refer to the `tasks/gnome.yml` playbook
|
||||
* Created the `tasks/gnome.yml` playbook with the content mentioned above
|
||||
* Created a `files` directory inside the `tasks` directory, with an image file named `wallpaper.jpg` (or whatever you chose to call it).
|
||||
|
||||
|
||||
|
||||
Once you've completed those steps and pushed your changes back to the repository, the configuration should be automatically applied during its next scheduled run. (You may recall that we automated this in the previous article.) If you're in a hurry, you can apply the configuration immediately with the following command:
|
||||
```
|
||||
sudo ansible-pull -U https://github.com/<github_user>/ansible.git
|
||||
|
||||
```
|
||||
|
||||
If everything ran correctly, you should see your new wallpaper.
|
||||
|
||||
Let's take a moment to go through what the new GNOME taskbook does. First, we added a play to install the `python-psutil` package. If we don't add this, we can't use the `dconf` module, since it requires this package to be installed before we can modify GNOME settings. Next, we used the `copy` module to copy the wallpaper file to our `home` directory, and we named the resulting file starting with a period to hide it. If you'd prefer not to have this file in the root of your `home` directory, you can always instruct this section to copy it somewhere else—it will still work as long as you refer to it at the correct place. In the next play, we used the `dconf` module to change GNOME settings. In this case, we adjusted the `/org/gnome/desktop/background/picture-uri` key and set it equal to `file:///home/jay/.wallpaper.jpg`. Note the quotes in this section of the playbook—you must always use two single-quotes in `dconf` values, and you must also include double-quotes if the value is a string.
|
||||
|
||||
Now, let's take our configuration a step further and apply a background to the lock screen. Here's the GNOME taskbook again, but with two additional plays added:
|
||||
```
|
||||
- name: Install python-psutil package
|
||||
|
||||
apt: name=python-psutil
|
||||
|
||||
|
||||
|
||||
- name: Copy wallpaper file
|
||||
|
||||
copy: src=files/wallpaper.jpg dest=/home/jay/.wallpaper.jpg owner=jay group=jay mode=600
|
||||
|
||||
|
||||
|
||||
- name: Set GNOME wallpaper
|
||||
|
||||
dconf: key="/org/gnome/desktop/background/picture-uri" value="'file:///home/jay/.wallpaper.jpg'"
|
||||
|
||||
|
||||
|
||||
- name: Copy lockscreenfile
|
||||
|
||||
copy: src=files/lockscreen.jpg dest=/home/jay/.lockscreen.jpg owner=jay group=jay mode=600
|
||||
|
||||
|
||||
|
||||
- name: Set lock screen background
|
||||
|
||||
become_user: jay
|
||||
|
||||
dconf: key="/org/gnome/desktop/screensaver/picture-uri" value="'file:///home/jay/.lockscreen.jpg'"
|
||||
|
||||
```
|
||||
|
||||
As you can see, we're pretty much doing the same thing as we did with the wallpaper. We added two additional tasks, one to copy the lock screen image and place it in our `home` directory, and another to apply the setting to GNOME so it will be used. Again, be sure to change your username from `jay` and also name your desired lock screen picture `lockscreen.jpg` and copy it to the `files` directory. Once you've committed these changes to your repository, the new lock screen should be applied during the next scheduled Ansible run.
|
||||
|
||||
### Apply a new desktop theme
|
||||
|
||||
Setting the wallpaper and lock screen background is cool and all, but let's go even further and apply a desktop theme. First, let's add an instruction to our taskbook to install the package for the `arc` theme. Add the following code to the beginning of the GNOME taskbook:
|
||||
```
|
||||
- name: Install arc theme
|
||||
|
||||
apt: name=arc-theme
|
||||
|
||||
```
|
||||
|
||||
Then, at the bottom, add the following play:
|
||||
```
|
||||
- name: Set GTK theme
|
||||
|
||||
become_user: jay
|
||||
|
||||
dconf: key="/org/gnome/desktop/interface/gtk-theme" value="'Arc'"
|
||||
|
||||
```
|
||||
|
||||
Did you see GNOME's GTK theme change right before your eyes? We added a play to install the `arc-theme` package via the `apt` module and another play to apply this theme to GNOME.
|
||||
|
||||
### Make other customizations
|
||||
|
||||
Now that you've changed some GNOME settings, feel free to add additional customizations on your own. Any setting you can tweak in GNOME can be automated this way; setting the wallpapers and the theme were just a few examples. You may be wondering how to find the settings that you want to change. Here's a trick that works for me.
|
||||
|
||||
First, take a snapshot of ALL your current `dconf` settings by running the following command on the machine you're managing:
|
||||
```
|
||||
dconf dump / > before.txt
|
||||
|
||||
```
|
||||
|
||||
This command exports all your current changes to a file named `before.txt`. Next, manually change the setting you want to automate, and capture the `dconf` settings again:
|
||||
```
|
||||
dconf dump / > after.txt
|
||||
|
||||
```
|
||||
|
||||
Now, you can use the `diff` command to see what's different between the two files:
|
||||
```
|
||||
diff before.txt after.txt
|
||||
|
||||
```
|
||||
|
||||
This should give you a list of keys that changed. While it's true that changing settings manually defeats the purpose of automation, what you're essentially doing is capturing the keys that change when you update your preferred settings, which then allows you to create Ansible plays to modify those settings so you'll never need to touch those settings again. If you ever need to restore your machine, your Ansible repository will take care of each and every one of your customizations. If you have multiple machines, or even a fleet of workstations, you only have to manually make the change once, and all other workstations will have the new settings applied and be completely in sync.
|
||||
|
||||
### Wrapping up
|
||||
|
||||
If you've followed along with this series, you should know how to set up Ansible to automate your workstation. These examples offer a useful baseline, and you can use the syntax and examples to make additional customizations. As you go along, you can continue to add new modifications, which will make your Ansible configuration grow over time.
|
||||
|
||||
I've used Ansible in this way to automate everything, including my user account and password; configuration files for Vim, tmux, etc.; desktop packages; SSH settings; SSH keys; and basically everything I could ever want to customize. Using this series as a starting point will pave the way for you to completely automate your workstations.
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://opensource.com/article/18/5/manage-your-workstation-ansible-part-3
|
||||
|
||||
作者：[Jay LaCroix][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/jlacroix
|
||||
[1]:https://opensource.com/article/18/3/manage-workstation-ansible
|
||||
[2]:https://opensource.com/article/18/3/manage-your-workstation-configuration-ansible-part-2
|
||||
[3]:https://github.com/jlacroix82/ansible_article.git
|
||||
@ -1,268 +0,0 @@
|
||||
[#]: collector: (lujun9972)
|
||||
[#]: translator: (chen-ni)
|
||||
[#]: reviewer: ( )
|
||||
[#]: publisher: ( )
|
||||
[#]: url: ( )
|
||||
[#]: subject: (5 tiny Linux distros to try before you die)
|
||||
[#]: via: (https://opensource.com/article/19/6/linux-distros-to-try)
|
||||
[#]: author: (Seth Kenlon https://opensource.com/users/seth/users/marcobravo)
|
||||
|
||||
5 tiny Linux distros to try before you die
|
||||
======
|
||||
Resurrect an ancient machine, boot a broken system, or ensure a safe
|
||||
public computing session with these tiny Linux distros.
|
||||
![Hand putting a Linux file folder into a drawer][1]
|
||||
|
||||
There are plenty of Linux distributions out there to choose from when you're deciding what to run on a daily basis, yet some are so small that they get little notice. But tiny Linux distributions are powerful innovations: having an entire operating system drive a computer with less than 1GB of storage and half as much RAM is the ultimate software hack.
|
||||
|
||||
Tiny distros have many uses, such as:
|
||||
|
||||
* Save old and slow computers from the rubbish bin. Reject planned obsolescence and use computers until they fall apart, not just until they start to feel slow.
|
||||
* Boot broken or corrupted systems from a thumb drive to recover data or repair boot partitions.
|
||||
* Ensure a safe and private environment when on a public computer. If you boot a public computer in a hotel lobby or a library from a thumb drive, you'll know your operating environment is secure.
|
||||
|
||||
|
||||
|
||||
There are plenty of lightweight distributions out there, like [Lubuntu][2], [Peppermint OS][3], and [Bodhi][4], but there's something special about the truly tiny. Here are five tiny distros you owe it to yourself to try.
|
||||
|
||||
### Tiny Core
|
||||
|
||||
![Tiny Core Linux][5]
|
||||
|
||||
At 11MB for a text console and 16MB for a GUI, [Tiny Core Linux][6] is almost impossibly small. I dug through my collection of old thumb drives; the smallest one was 128MB, which is still eight times the size of Tiny Core's image.
|
||||
|
||||
By default, Tiny Core includes the base OS, assuming you have an Ethernet connection to the internet so you can install only the applications you need. It's such an extremely efficient model that it doesn't even include an application to install the OS (although you can download it from the Tiny Core repository when you're ready to install).
|
||||
|
||||
I've run Tiny Core from a 128MB thumb drive on a system with 512MB RAM, and the performance was excellent, as you might expect from an OS that takes only 16MB. Performance slows only when browsing the internet in a web browser, but the blame lies with the complexity of most modern websites more than Tiny Core.
|
||||
|
||||
Without a GUI, Tiny Core runs well on a mere 64MB of RAM.
|
||||
|
||||
#### Installation
|
||||
|
||||
[Download Tiny Core][7] and write it to a thumb drive with **dd** or [Etcher][8].
|
||||
|
||||
Installing Tiny Core is easy, once you download the **tc-install** or **tc-install-GUI** application using the **Apps** icon in the launcher bar at the bottom of the screen.
|
||||
|
||||
![Tiny Core installer][9]
|
||||
|
||||
You have several options to install Tiny Core. You can install it to a thumb drive formatted as a Linux drive (this requires your computer to allow booting from a USB drive, which is common in most modern PCs but was less common for older ones), to a Microsoft FAT thumb drive (a hack for PCs that don't normally boot from USB drives), or even to a directory in an existing Linux partition.
|
||||
|
||||
The installation is quick, and when you finish, you can reboot your computer and boot into your Tiny Core Linux OS.
|
||||
|
||||
#### Applications
|
||||
|
||||
Since it comes with little more than a text editor and a terminal, the first thing you should do is install some applications. The **Apps** icon in the bottom launcher bar displays all the Tiny Core packages available to you. The **Apps** repository also includes important drivers, so it's useful when you're looking to get a WiFi card or a printer working.
|
||||
|
||||
When installing a new application or utility, you can choose between having the package load into Tiny Core at boot time or on demand. Choosing to load a package at boot makes it available to you immediately and still available after a reboot (as you would expect). Choosing to load it on demand means the package is available after Tiny Core downloads the package, but after a reboot, it won't be loaded into memory. This may keep your boot time fast and Tiny Core's footprint in RAM tiny, but it also means the package data isn't loaded into memory until you use it for the first time each session.
|
||||
|
||||
The application selection is a good mix between user-centric apps, like office and graphics applications, and server-centric, such as [Samba][10] and web servers.
|
||||
|
||||
Of course, once you start adding applications to Tiny Core, it becomes less tiny. Even the **Tiny Core Plus** image, which includes all WiFi drivers, on the Tiny Core website is only about 100MB, so "less tiny" is likely still well under 256MB or so.
|
||||
|
||||
#### Bottom line
|
||||
|
||||
Tiny Core is ideal for old computers with few resources, network boot images, and anyone who values applications over the OS. Tiny Core is a great weekend project: build the OS you want from 16MB until you have just as much of an OS as you need.
|
||||
|
||||
### SliTaz
|
||||
|
||||
![SliTaz Linux][11]
|
||||
|
||||
The [SliTaz Linux][12] image is about 51MB, about four times the size of Tiny Core, with an impressive collection of drivers and applications included. In fact, if you didn't know better, you might think you booted into a 1GB Ubuntu image because everything you'd expect from a basic starter image is there: text editor, web browser, paint program, spreadsheet application, and so on.
|
||||
|
||||
I've run SliTaz from a 128MB thumb drive on a system with 512MB RAM, and the performance was excellent. Performance slows when browsing heavy websites, but the included lightweight [Midori][13] browser keeps most sites loading quickly.
|
||||
|
||||
At boot time, you can choose to run SliTaz without a GUI; it runs nicely on a mere 64MB of RAM.
|
||||
|
||||
#### Installation
|
||||
|
||||
There are many download options for SliTaz because its developers and community provide many variations for potential system limitations. For instance, there's a low RAM version for systems with as little as 24MB RAM, a version with Firefox instead of Midori, a version with no extra applications, and so on.
|
||||
|
||||
If you're overwhelmed by options and just want to try it out, [download the rolling release][14]. This version is roughly 50MB and is updated weekly. If you fall in love with SliTaz, you can choose a download that's better for your needs—if the rolling release proves to be _too_ fresh for you.
|
||||
|
||||
Once you've downloaded your choice of SliTaz image, write it to a thumb drive with **dd** or [Etcher][8] and reboot.
|
||||
|
||||
Installing SliTaz to a thumb drive or hard drive is done through the **TazPanel** application. It guides you through partitioning your disk (as needed) and installs SliTaz to the destination you choose.
|
||||
|
||||
![SliTaz installer][15]
|
||||
|
||||
#### Applications
|
||||
|
||||
The **TazPanel** application is SliTaz's control center. If you're a fan of OpenSUSE or Mageia (née Mandrake), you might find TazPanel familiar, at least in concept: it's a single application that provides access to system configuration, hardware detection, user and group management, system updates, and application installation.
|
||||
|
||||
Available applications satisfy most basic requirements, meaning if you're not picky about which application you use to accomplish a task, then SliTaz's repositories probably have something for you. If you have specific requirements (GIMP 2.10 instead of GIMP 2.8, for instance), then you'll have to learn how to generate SliTaz packages. The good news is that the **tazpkg** command can convert from several packaging formats, including:
|
||||
|
||||
* Debian packages (.deb, .udeb)
|
||||
* RPM packages (.rpm)
|
||||
* Slackware packages (.tgz)
|
||||
* Puppy packages (.sfs, .pet)
|
||||
* NuTyX packages (.cards.tar.xz)
|
||||
* Arch and Alpine Linux packages (.apk, .pkg.tar.gz, .pkg.tar.xz)
|
||||
* OpenWrt packages (.ipk, .opk)
|
||||
* Paldo packages (.tar.bz2)
|
||||
* Void packages (.xbps)
|
||||
* Tiny Core packages (.tce, .tcel, .tcem, .tcz)
|
||||
|
||||
|
||||
|
||||
#### Bottom line
|
||||
|
||||
SliTaz is a fast, small Linux distribution with a centralized control panel that makes it easy to learn. Because its packaging tools can convert from other Linux packaging formats, its application selection is theoretically vast, making it easy for you to design your work environment with all your favorite tools. SliTaz is small but lethal, just like its arachnid logo.
|
||||
|
||||
### Porteus
|
||||
|
||||
![Porteus Linux][16]
|
||||
|
||||
[Porteus][17] offers a few desktop options, with the smallest image around 270MB and the largest 350MB. That makes it one of the largest of tiny Linux images, but most of that space is dedicated to ensuring a smooth Linux desktop experience, to the point that you'll likely forget you're using a live distribution. Installing Porteus to an SSD drive or loading it to RAM during boot results in such a flawlessly smooth environment that you won't believe your OS occupies less space than half a CD-ROM.
|
||||
|
||||
Porteus is tiny in the sense that its base image is comparatively small, but depending on the desktop you choose, it can easily require up to 1GB of RAM to run. While other tiny Linux distributions tend to capitalize on minimalist applications to preserve space and resources, Porteus expects you to use it as you would any other distribution. Install all your favorite apps and drivers and forget you're running on a tiny, compressed root filesystem.
|
||||
|
||||
#### Installation
|
||||
|
||||
Download Porteus from your [closest Porteus mirror][18], choosing from MATE, LXQT, LXDE, OpenBox, XFCE, Cinnamon, or KDE, depending upon your preference. If you have no preference, the MATE or KDE desktop are both good at balancing image size with a familiar-feeling desktop experience.
|
||||
|
||||
![Porteus installer][19]
|
||||
|
||||
opensource.com
|
||||
|
||||
You can install Porteus to a thumb drive or an internal hard drive using the instructions in the [official installation guide][20]. The process is similar either way and results in a compressed root filesystem that never changes. It's a stable and contained filesystem upon which you overlay your changes as you use it. When you reboot, changes you make and applications you install are loaded into memory, so your environment is just as you left it.
|
||||
|
||||
#### Applications
|
||||
|
||||
Applications are called "modules" in Porteus lingo and are available from the [Unified Slackware Package Manager][21] (USM), which draws from five different Slackware repositories, meaning you have plenty of applications to choose from.
|
||||
|
||||
#### Bottom line
|
||||
|
||||
Porteus is a full Linux experience with a fraction of the space usually required. It's an excellent portable Linux distribution with lots of desktop options and lots of applications.
|
||||
|
||||
### Bodhi Linux
|
||||
|
||||
![Bodhi Linux][22]
|
||||
|
||||
[Bodhi Linux][4] might not look tiny at first glance, with an ISO image of 740MB, but once it's installed, you'll be amazed at just how tiny it is. Bodhi runs smoothly on only 512MB of RAM but looks and feels like the desktop of tomorrow. Bodhi uses the [Enlightenment][23] desktop, a beautiful user interface that's lovingly crafted to be both small and powerful.
|
||||
|
||||
Bodhi doesn't just use Enlightenment, though, it adds to it. Bodhi's configuration applications and system setting panels are custom interfaces to Enlightenment's sometimes overwhelming array of options. Bodhi makes some sane default choices for you and provides a subset of options. If you're a die-hard Enlightenment user, Bodhi's interpretation might not be pure enough for you, but for many users, Bodhi brings focus to the Enlightenment desktop.
|
||||
|
||||
#### Installation
|
||||
|
||||
[Download Bodhi Linux][24], write it to a thumb drive with **dd** or [Etcher][8], and reboot.
|
||||
|
||||
The Bodhi installer is available from the **Applications** menu in the **Preferences** category. The installation application is **Ubiquity**, so the process is the same as installing Ubuntu. If you've never installed Ubuntu, don't worry; it's one of the easiest to install.
|
||||
|
||||
![Bodhi installer][25]
|
||||
|
||||
#### Applications
|
||||
|
||||
Bodhi is based on the latest long term support (LTS) Ubuntu Linux release, so your available software knows almost no bounds. If it's available for Ubuntu Linux, Bohdi has access to it.
|
||||
|
||||
#### Bottom line
|
||||
|
||||
Bodhi Linux is a step down from the size of a typical Ubuntu install and a step up from many other minimalist Ubuntu environments because it uses Enlightenment. If you're looking for a Linux distribution that runs lighter than most without resorting to overlay filesystems and application modules, then Bodhi is the distribution for you.
|
||||
|
||||
### Puppy Linux
|
||||
|
||||
![Puppy Linux][26]
|
||||
|
||||
Before there was Tiny Core or SliTaz or [AntiX][27] or Porteus, there was [Puppy Linux][28]. One of the original tiny Linux distributions, Puppy has endured for a decade and a half as a reliable, bootable OS for old computers and new users alike.
|
||||
|
||||
Upon first boot, Puppy does its best to guide the user through any necessary steps to ensure everything works as expected. It's a lot of windows to wade through, but once you get through it all, you know without a doubt what works and what doesn't before you choose whether to install.
|
||||
|
||||
Puppy is almost 300MB and failed to work on anything under 1GB RAM in my tests, so it's not exactly the tiniest Linux available. However, it's still a great, under-1GB operating system, and of the OSes in that category, it's one of the very friendliest.
|
||||
|
||||
#### Installation
|
||||
|
||||
[Download Puppy Linux][29] and write it to a thumb drive with **dd** or [Etcher][8] or burn it to a CD or DVD, then reboot.
|
||||
|
||||
![Puppy installer][30]
|
||||
|
||||
Puppy can install onto nearly anything that accepts data. The installer application, available from the top launcher bar, is called **Puppy Installer**, and it manages installing Puppy and applications for Puppy.
|
||||
|
||||
Puppy Installer steps you through the process of installing the OS onto whatever media you have available. Puppy can boot from a thumb drive, an optical disc, a hard drive, and even an SD card. I've used Puppy on a computer with no hard drive whatsoever, no working optical drive, and no option to boot from USB. Because Puppy can write your configuration options to just about anything, I was able to use it with persistent data storage to an external device.
|
||||
|
||||
#### Applications
|
||||
|
||||
The **Puppy Installer** application is also used to install apps onto Puppy. Because Puppy is based on Ubuntu, there aren't likely to be any Linux packages missing from its repositories, and if there are, you can probably use a [Flatpak][31].
|
||||
|
||||
#### Bottom line
|
||||
|
||||
Puppy is the original tiny Linux. While it's not the tiniest any more, it's by far the easiest.
|
||||
|
||||
### Bonus: Silverblue
|
||||
|
||||
![SilverBlue, not tiny, but tiny-adjacent][32]
|
||||
|
||||
The concept of tiny Linux has changed over the years. Long ago, a tiny Linux distribution was something you downloaded onto a CD-R and ran from your optical drive while saving changes to external media. Later, it was something you ran from a thumb drive with dedicated space for persistent changes. Now it's all of those things plus the ability to install to internal drives or directories.
|
||||
|
||||
What no one expected was for Linux to kick off the craze for containers, in which applications are self-contained Linux systems running in a para-virtualized environment. What was once a niche hobby for people who either loved to optimize disk space or who loved to resurrect ancient computers quickly became a salient requirement for developers who wanted to develop containers without adding too much overhead to their applications. All the work put into the minimalist, ephemeral Linux distributions suddenly paid off in an unexpected way.
|
||||
|
||||
With the concept of what a root filesystem looks like, the Fedora Project's [Silverblue][33] experiment is an effort to create an immutable OS. It's an operating system that never changes and instead gets updates and application installs in the form of, essentially, containers.
|
||||
|
||||
Silverblue at 2.1GB is by no means a tiny Linux distribution, but in many ways, it's a child of the tiny Linux and container movements.
|
||||
|
||||
#### Installation
|
||||
|
||||
[Download Silverblue][34] and write it to a thumb drive with **dd** or [Etcher][8] or burn it to a CD or DVD, then reboot.
|
||||
|
||||
After booting into Silverblue, install it to an internal hard drive using [Anaconda][35], the standard, friendly Fedora Linux installer.
|
||||
|
||||
![Anaconda installer][36]
|
||||
|
||||
#### Applications
|
||||
|
||||
Silverblue doesn't install applications in the traditional sense; instead, it runs containers over the top of its base OS. Specifically, it uses Flatpaks for GUI applications and [Toolbox][37] for commands.
|
||||
|
||||
Because Flatpaks aren't nearly as common as traditional Fedora RPM packages, Silverblue also provides **package layering**, a way to convert Fedora RPM packages to Silverblue.
|
||||
|
||||
#### Bottom line
|
||||
|
||||
Silverblue could be a fun experiment testing out emerging technology, or it could be the future of the desktop OS. It's tiny only in the sense that its root filesystem remains the same size regardless of updates and applications added onto it, but it's worth looking at to see where the strange obsession with tiny distributions has delivered the Linux community and industry. Don't forget to tip your hat to the 11MB pioneers on your way out.
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://opensource.com/article/19/6/linux-distros-to-try
|
||||
|
||||
作者：[Seth Kenlon][a]
|
||||
选题：[lujun9972][b]
|
||||
译者：[译者ID](https://github.com/译者ID)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
||||
[a]: https://opensource.com/users/seth/users/marcobravo
|
||||
[b]: https://github.com/lujun9972
|
||||
[1]: https://opensource.com/sites/default/files/styles/image-full-size/public/lead-images/yearbook-haff-rx-linux-file-lead_0.png?itok=-i0NNfDC (Hand putting a Linux file folder into a drawer)
|
||||
[2]: http://lubuntu.net
|
||||
[3]: http://peppermintos.com
|
||||
[4]: https://www.bodhilinux.com/
|
||||
[5]: https://opensource.com/sites/default/files/uploads/tinycore.jpg (Tiny Core Linux)
|
||||
[6]: http://tinycorelinux.net/
|
||||
[7]: http://tinycorelinux.net/welcome.html
|
||||
[8]: https://www.balena.io/etcher/
|
||||
[9]: https://opensource.com/sites/default/files/uploads/tc-install-gui.png (Tiny Core installer)
|
||||
[10]: https://www.samba.org/
|
||||
[11]: https://opensource.com/sites/default/files/uploads/slitaz.jpg (SliTaz Linux)
|
||||
[12]: http://www.slitaz.org/en/
|
||||
[13]: https://github.com/midori-browser/core
|
||||
[14]: http://slitaz.org/en/get/#rolling
|
||||
[15]: https://opensource.com/sites/default/files/uploads/slitaz-install.jpg (SliTaz installer)
|
||||
[16]: https://opensource.com/sites/default/files/uploads/porteus.jpg (Porteus Linux)
|
||||
[17]: http://www.porteus.org/
|
||||
[18]: http://porteus.org/porteus-mirrors.txt
|
||||
[19]: https://opensource.com/sites/default/files/images/porteus-installer.png (Porteus installer)
|
||||
[20]: http://www.porteus.org/component/content/article/26-tutorials/general-info-tutorials/114-official-porteus-installation-guide.html
|
||||
[21]: http://www.porteus.org/tutorials/9-modules/149-usm.html
|
||||
[22]: https://opensource.com/sites/default/files/uploads/bodhi.jpg (Bodhi Linux)
|
||||
[23]: https://www.enlightenment.org/
|
||||
[24]: https://www.bodhilinux.com/download
|
||||
[25]: https://opensource.com/sites/default/files/uploads/bodhi-install.jpg (Bodhi installer)
|
||||
[26]: https://opensource.com/sites/default/files/uploads/puppy.jpg (Puppy Linux)
|
||||
[27]: https://antixlinux.com/
|
||||
[28]: http://puppylinux.com/
|
||||
[29]: http://puppylinux.com/index.html#download
|
||||
[30]: https://opensource.com/sites/default/files/uploads/puppy-install.jpg (Puppy installer)
|
||||
[31]: https://docs.fedoraproject.org/en-US/fedora-silverblue/getting-started/#flatpak
|
||||
[32]: https://opensource.com/sites/default/files/uploads/silverblue.jpg (SilverBlue, not tiny, but tiny-adjacent)
|
||||
[33]: https://silverblue.fedoraproject.org/
|
||||
[34]: https://silverblue.fedoraproject.org/download
|
||||
[35]: https://fedoraproject.org/wiki/Anaconda
|
||||
[36]: https://opensource.com/sites/default/files/uploads/silverblue-install.jpg (Anaconda installer)
|
||||
[37]: https://docs.fedoraproject.org/en-US/fedora-silverblue/toolbox/
|
||||
@ -1,5 +1,5 @@
|
||||
[#]: collector: (lujun9972)
|
||||
[#]: translator: ( )
|
||||
[#]: translator: (chen-ni)
|
||||
[#]: reviewer: ( )
|
||||
[#]: publisher: ( )
|
||||
[#]: url: ( )
|
||||
|
||||
209
sources/tech/20190628 How to Install and Use R on Ubuntu.md
Normal file
209
sources/tech/20190628 How to Install and Use R on Ubuntu.md
Normal file
@ -0,0 +1,209 @@
|
||||
[#]: collector: (lujun9972)
|
||||
[#]: translator: ( )
|
||||
[#]: reviewer: ( )
|
||||
[#]: publisher: ( )
|
||||
[#]: url: ( )
|
||||
[#]: subject: (How to Install and Use R on Ubuntu)
|
||||
[#]: via: (https://itsfoss.com/install-r-ubuntu/)
|
||||
[#]: author: (Sergiu https://itsfoss.com/author/sergiu/)
|
||||
|
||||
How to Install and Use R on Ubuntu
|
||||
======
|
||||
|
||||
_**Brief: This tutorial teaches you to install R on Ubuntu. You’ll also learn how to run your first R program in Ubuntu using various methods.**_
|
||||
|
||||
[R][1], together with Python, is the most commonly used programming language for statistical computing and graphics, making it easy to work with data. With the growing interest in data analysis, data visualization, data science (the machine learning craze), it is now more popular than ever and is a great tool for anyone looking to dive into this fields.
|
||||
|
||||
The good thing about R is that its syntax is pretty straight-forward and you can find many tutorials/guides on how R is used in the real world.
|
||||
|
||||
In this article, I’ll cover how to install R on Ubuntu Linux. I’ll also show you how to run your first R program in Linux.
|
||||
|
||||
![][2]
|
||||
|
||||
### Installing R on Ubuntu
|
||||
|
||||
**R** is included in the Ubuntu repositories. It can be easily installed using:
|
||||
|
||||
```
|
||||
sudo apt install r-base
|
||||
```
|
||||
|
||||
Do note that this may install a slightly older version. At the time of writing this article, Ubuntu offers version 3.4 whereas the latest is version 3.6.
|
||||
|
||||
_I advise sticking with whichever version Ubuntu provides unless you must use the newer version._
|
||||
|
||||
In order to get the latest version (or any specific version for that matter), you must use **[CRAN][3]** (The Comprehensive R Archive Network). This is a list of mirrors for downloading the latest version of R. Click on the next section to learn how to install the latest version of R on Ubuntu.
|
||||
|
||||
**How to install latest R version 3.6 on Ubuntu (click to expand)**
|
||||
|
||||
To get the R version 3.6, you need to add the mirror to your sources list. I have simplified it for you in this command:
|
||||
|
||||
```
|
||||
sudo add-apt-repository "deb https://cloud.r-project.org/bin/linux/ubuntu $(lsb_release -cs)-cran35/"
|
||||
```
|
||||
|
||||
Now you should add the key for the repository:
|
||||
|
||||
```
|
||||
sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys E298A3A825C0D65DFD57CBB651716619E084DAB9
|
||||
```
|
||||
|
||||
And then update the repository information and install R:
|
||||
|
||||
```
|
||||
sudo apt update
|
||||
sudo apt install r-base
|
||||
```
|
||||
|
||||
That’s it.
|
||||
|
||||
[][4]
|
||||
|
||||
Suggested read How to Create a Bootable Windows 10 USB in Linux
|
||||
|
||||
### Using R programming on Ubuntu
|
||||
|
||||
R has more than one use. I’ll go over several methods you can use to run R programs.
|
||||
|
||||
#### Interactive Mode in R
|
||||
|
||||
After having installed **R**, you can run the console using:
|
||||
|
||||
```
|
||||
R
|
||||
```
|
||||
|
||||
This should open up the interactive mode:
|
||||
|
||||
![R Interactive Mode][5]
|
||||
|
||||
This R console is very similar to the **Python** and **Haskell** interactive prompts. You can enter any **R** command and you can do basic mathematical computations. For example:
|
||||
|
||||
```
|
||||
> 20+40
|
||||
[1] 60
|
||||
|
||||
> print ("Hello World!")
|
||||
[1] "Hello World!"
|
||||
```
|
||||
|
||||
You could test plotting too:
|
||||
|
||||
![R Plotting][6]
|
||||
|
||||
You can **quit** using **q()** or pressing **CTRL+c**. When doing so, you will be asked if you want to save a workspace ****image; a workspace ****is an environment for created variables.
|
||||
|
||||
#### Running R program with Rscript
|
||||
|
||||
The second way to run R programs is in directly on the Linux command line. You can do so using **RScript**, a utility included with **r-base**.
|
||||
|
||||
First, you have to save your R program to a file using your [favorite code editor on Linux][7]. The file extension should be .r.
|
||||
|
||||
This is my sample R program printing “Hello World”. I have saved it in a file name hello.r.
|
||||
|
||||
```
|
||||
print("Hello World!")
|
||||
a <- rnorm(100)
|
||||
plot(a)
|
||||
```
|
||||
|
||||
To run the R program, use the command like this:
|
||||
|
||||
```
|
||||
Rscript hello.r
|
||||
```
|
||||
|
||||
You should get back the output:
|
||||
|
||||
```
|
||||
[1] "Hello World!"
|
||||
```
|
||||
|
||||
The plot is going to be saved in the working directory, to a file named **Rplots.pdf**:
|
||||
|
||||
![Rplots.pdf][8]
|
||||
|
||||
**Note:** _**Rscript**_ _doesn’t load the_ _**methods**_ _package by default. Make sure to [load it explicitly][9] in your script_.
|
||||
|
||||
#### Run R scripts with RStudio in Ubuntu
|
||||
|
||||
The most common way to use **R** is using [RStudio][10], a great cross-platform open source IDE. You can [install it using deb file in Ubuntu][11]. Download the deb file from the link below. You’ll have to scroll down a bit to locate the DEB files for Ubuntu.
|
||||
|
||||
[Download RStudio for Ubuntu][12]
|
||||
|
||||
Once you download the DEB file, just double click on it to install it.
|
||||
|
||||
Once installed, search for it in the menu and start it. The home window of the application should pop up:
|
||||
|
||||
![RStudio Home][13]
|
||||
|
||||
Here you have a working console, just like the one you got in the terminal with the **R** command.
|
||||
|
||||
[][14]
|
||||
|
||||
Suggested read Setting Up Python Environments In Linux and Unix Systems
|
||||
|
||||
To create a file, in the top bar click on **File** and select **New File > Rscript** (or **CTRL+Shift+n)**:
|
||||
|
||||
![RStudio New File][15]
|
||||
|
||||
Press **CTRL+s** to save the file and choose a location and a name it:
|
||||
|
||||
![RStudio Save File][16]
|
||||
|
||||
After doing so, click on **Session > Set Working Directory > To Source File Location** to change the working directory to the location of your script:
|
||||
|
||||
![RStudio Working Directory][17]
|
||||
|
||||
You are now ready to go! Write in your code and click run. You should be able to see output both in the console and in the plotting window:
|
||||
|
||||
![RStudio Run][18]
|
||||
|
||||
**Wrapping Up**
|
||||
|
||||
In this article, I showed you step by step how to get started using the **R** programming language on an Ubuntu system. I covered several ways you can go about this: **R console** – useful for testing, **Rscript** – for the terminal lover, **RStudio** – the IDE for your needs.
|
||||
|
||||
Whether you are willing to get into data science or simply love statistics, **R** is a good addition to your programming arsenal, being the perfect tool for analyzing data.
|
||||
|
||||
If you are absolutely new to R, let me recommend you this excellent book that will teach you fundamentals of R. It’s available on Amazon Kindle.
|
||||
|
||||
Preview | Product | Price |
|
||||
---|---|---|---
|
||||
![Learn R in a Day][19] ![Learn R in a Day][19] | [Learn R in a Day][20] | | [Buy on Amazon][21]
|
||||
|
||||
Do you use **R**? Are you just getting into it? Let us know more about how and why you use or want to learn to use **R**!
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://itsfoss.com/install-r-ubuntu/
|
||||
|
||||
作者：[Sergiu][a]
|
||||
选题：[lujun9972][b]
|
||||
译者：[译者ID](https://github.com/译者ID)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
||||
[a]: https://itsfoss.com/author/sergiu/
|
||||
[b]: https://github.com/lujun9972
|
||||
[1]: https://www.r-project.org/
|
||||
[2]: https://i2.wp.com/itsfoss.com/wp-content/uploads/2019/06/install-r-on-ubuntu.jpg?resize=800%2C450&ssl=1
|
||||
[3]: https://cran.r-project.org/
|
||||
[4]: https://itsfoss.com/bootable-windows-usb-linux/
|
||||
[5]: https://i1.wp.com/itsfoss.com/wp-content/uploads/2019/06/r_interactive_mode.png?fit=800%2C516&ssl=1
|
||||
[6]: https://i0.wp.com/itsfoss.com/wp-content/uploads/2019/06/r_plotting.jpg?fit=800%2C434&ssl=1
|
||||
[7]: https://itsfoss.com/best-modern-open-source-code-editors-for-linux/
|
||||
[8]: https://i1.wp.com/itsfoss.com/wp-content/uploads/2019/06/rplots_pdf.png?fit=800%2C539&ssl=1
|
||||
[9]: https://www.dummies.com/programming/r/how-to-install-load-and-unload-packages-in-r/
|
||||
[10]: https://www.rstudio.com/
|
||||
[11]: https://itsfoss.com/install-deb-files-ubuntu/
|
||||
[12]: https://www.rstudio.com/products/rstudio/download/#download
|
||||
[13]: https://i1.wp.com/itsfoss.com/wp-content/uploads/2019/06/rstudio_home.jpg?fit=800%2C603&ssl=1
|
||||
[14]: https://itsfoss.com/python-setup-linux/
|
||||
[15]: https://i0.wp.com/itsfoss.com/wp-content/uploads/2019/06/rstudio_new_file.png?fit=800%2C392&ssl=1
|
||||
[16]: https://i1.wp.com/itsfoss.com/wp-content/uploads/2019/06/rstudio_save_file.png?fit=800%2C258&ssl=1
|
||||
[17]: https://i0.wp.com/itsfoss.com/wp-content/uploads/2019/06/rstudio_working_directory.png?fit=800%2C394&ssl=1
|
||||
[18]: https://i0.wp.com/itsfoss.com/wp-content/uploads/2019/06/rstudio_run.jpg?fit=800%2C626&ssl=1
|
||||
[19]: https://i1.wp.com/images-na.ssl-images-amazon.com/images/I/51oIJTbUlnL._SL160_.jpg?ssl=1
|
||||
[20]: https://www.amazon.com/Learn-R-Day-Steven-Murray-ebook/dp/B00GC2LKOK?SubscriptionId=AKIAJ3N3QBK3ZHDGU54Q&tag=chmod7mediate-20&linkCode=xm2&camp=2025&creative=165953&creativeASIN=B00GC2LKOK (Learn R in a Day)
|
||||
[21]: https://www.amazon.com/Learn-R-Day-Steven-Murray-ebook/dp/B00GC2LKOK?SubscriptionId=AKIAJ3N3QBK3ZHDGU54Q&tag=chmod7mediate-20&linkCode=xm2&camp=2025&creative=165953&creativeASIN=B00GC2LKOK (Buy on Amazon)
|
||||
@ -0,0 +1,106 @@
|
||||
[#]: collector: (lujun9972)
|
||||
[#]: translator: (hopefully2333)
|
||||
[#]: reviewer: ( )
|
||||
[#]: publisher: ( )
|
||||
[#]: url: ( )
|
||||
[#]: subject: (Cisco to buy IoT security, management firm Sentryo)
|
||||
[#]: via: (https://www.networkworld.com/article/3400847/cisco-to-buy-iot-security-management-firm-sentryo.html)
|
||||
[#]: author: (Michael Cooney https://www.networkworld.com/author/Michael-Cooney/)
|
||||
|
||||
思科收购了物联网安全管理公司 Sentryo
|
||||
======
|
||||
买下 Sentryo 将给思科在工业互联网的异常和实时威胁检测两方面予以支持。
|
||||
![IDG Worldwide][1]
|
||||
|
||||
为了扩展自己的物联网安全管理产品，思科计划收购 Sentryo，这是一家位于法国的公司，Sentryo 为工业互联网提供异常检测和实时威胁检测。
|
||||
|
||||
Sentryo 成立于 2014 年，产品包括 ICS CyberVision - 一种用于资产库存、网络监控和威胁情报的平台 - 以及 CyberVision 网络边界传感器，这用于分析网络流量。
|
||||
|
||||
**更多关于物联网的信息：**
|
||||
|
||||
* [什么是物联网？物联网如何运行？][4]
|
||||
* [什么是边缘计算，这会如何改变我们的网络？][5]
|
||||
* [最强的物联网公司][6]
|
||||
* [10 个值得关注的热门物联网创业公司][7]
|
||||
* [在物联网领域赚钱的六种方法][8]
|
||||
* [什么是数字双胞胎技术？ [以及它为什么重要]][9]
|
||||
* [区块链，以服务为中心的网络是物联网成功的关键][10]
|
||||
* [物联网的网络和安全作为基础][11]
|
||||
* [构建完整的物联网网络必须优先完成][12]
|
||||
* [什么是工业互联网？ [为什么风险如此之高]][13]
|
||||
|
||||
|
||||
|
||||
“我们通过思科的 IOx 应用框架将 Sentryo 的边缘传感器和我们的工业网络硬件相结合”，思科企业发展和思科投资的副总裁 Rob Salvagno 在一篇关于计划收购的博客中写道。
|
||||
|
||||
“我们相信连接是物联网项目的基础，通过释放网络的力量，我们可以大大提高运作的效率并发现新的商业机会。随着 Sentryo 的加入，思科可以为系统控制工程师提供更加深入的资产可见度，以此来对系统进行优化，检测异常并保护他们的网络”
|
||||
|
||||
Gartner 对 Sentryo 的系统写道：“ICS CyberVision 这个产品为它的客户提供了可见性”所有的 OT 用户都将了解 OT 网络，而不仅仅是 IT 技术人员。随着黑客和监管机构越来越关注工业控制系统，一个组织的 OT 拥有完整的可见性是至关重要的一件事。很多的 OT 网络不仅在地理上位置分散，而且也很复杂，由成千上万的组件组成
|
||||
|
||||
Frost & Sullivan 的工业分析师 Nandini Natarajan 表示，Sentryo 的 ICS CyberVision 让企业能够确保其工业运作的连续性、动态弹性和安全性，并以此预防可能的网络攻击。“它将在标签的表单中使用一种独特的 ‘通用 OT 语言’ 来自动描述资产和通信流程，它会用纯文本的方式描述每个资产在做什么。ICS CyberVision 可以让任何人都能立刻查看一台设备的类别和行为；它利用人工智能算法提供很多不同的分析视图，来让用户深入了解到一个典型的工业控制系统可以产生多么庞大的数据。Sentryo 可以轻松查看重要或相关的信息”
|
||||
|
||||
Natarajan 表示，除此之外，Sentryo 的平台使用深度数据包检测（DPI）从工业设备之间的通信数据包里提取信息。DPI 引擎通过边缘计算架构进行部署，它可以运行在 Sentryo 传感器设备上，也可以在已经安装好的网络设备上运行。因此，Sentryo 可以将可见性和网络安全特性嵌入进工业网络中，而非部署带外监控网络。
|
||||
|
||||
**[[好消息！好消息！通过 PluralSight 的综合在线课程，成为一名光荣的认证信息安全系统专家，现在免费提供 10 天试用！走过路过不要错过！][17] ]**
|
||||
|
||||
Sentryo 的技术将扩大思科在物联网上的总体计划。在今年一月，思科推出了一整套的交换机、软件、开发工具和蓝图，这些东西将用于把物联网、基于意图联网的工业网络、传统信息安全、传统信息监控、应用开发支持融为一体。
|
||||
|
||||
这个新平台可以通过思科的 DNA 中心进行管理，让客户能将他们的物联网、工业网络控制和他们的商业 IT 世界融为一体。
|
||||
|
||||
DNA 中心是思科用于企业网络的中央管理工具，具有自动化、确保设置、结构配置、基于策略进行分割的功能。它也是公司 IBN 计划的核心，用于主动向客户提供动态自动化完成网络和策略变更的能力，并在这个过程中确保数据的交付。物联网领域网络的主管是软件，这个软件管理思科工业、连接的网格路由器、终端这多个业务的网络。
|
||||
|
||||
思科物联网业务部的高级副总裁兼总经理 Liz Centoni 表示，公司希望 Sentryo 的技术能以多种方式帮助物联网客户：
|
||||
|
||||
支持网络的被动 DPI 功能，这用于发现 IOT 和 OT 设备，并且在设备和系统之间建立起通信模式。Sentryo 的传感器可以在思科的 IOx 框架里进行本地部署，并且可以内置到这些设备运行的工业网络中，而不是添加额外的硬件。
|
||||
|
||||
随着设备识别和通信模式的建立，思科将把 DNA 中心和身份识别服务引擎（ISE）集成到一起，以便客户能够很轻松地定义分割策略。这种集成将使 OT 团队能够利用 IT 安全团队的专业知识来保护他们的环境，而不会对运营的流程造成风险。
|
||||
|
||||
这些物联网设备缺乏现代嵌入式软件和安全功能，网络分段将成为允许运作设备向合法系统进行通信的关键技术，并降低像我们看见的 WannaCry 和 Norsk Hydro 那样网络安全事件的风险。
|
||||
|
||||
据 Crunchbase 称，Sentryo 的每年预计收入为 350 万美元，与 Cymmetria，Team8，和 Indegy 的竞争最为激烈。此次收购预期将在思科 2020 财年的第一季度 - 2019 年 10 月 26 日 - 结束前完成。思科并未详细披露此次收购的财务细节。
|
||||
|
||||
Sentryo 是思科今年的第二次收购。思科在今年一月收购了 Singularity，这是为了这家公司的网络分析技术。在 2018 年，思科收购了包含 Duo security software 在内的 6 家公司。
|
||||
|
||||
** **
|
||||
|
||||
加入 Facebook 和 LinkedIn 上的网络世界社区，评论最重要的主题。
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://www.networkworld.com/article/3400847/cisco-to-buy-iot-security-management-firm-sentryo.html
|
||||
|
||||
作者：[Michael Cooney][a]
|
||||
选题：[lujun9972][b]
|
||||
译者：[hopefully2333](https://github.com/hopefully2333)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
||||
[a]: https://www.networkworld.com/author/Michael-Cooney/
|
||||
[b]: https://github.com/lujun9972
|
||||
[1]: https://images.idgesg.net/images/article/2018/09/nwan_019_iiot-100771131-large.jpg
|
||||
[2]: https://www.sentryo.net/
|
||||
[3]: https://www.networkworld.com/article/3243928/what-is-the-industrial-iot-and-why-the-stakes-are-so-high.html
|
||||
[4]: https://www.networkworld.com/article/3207535/internet-of-things/what-is-the-iot-how-the-internet-of-things-works.html
|
||||
[5]: https://www.networkworld.com/article/3224893/internet-of-things/what-is-edge-computing-and-how-it-s-changing-the-network.html
|
||||
[6]: https://www.networkworld.com/article/2287045/internet-of-things/wireless-153629-10-most-powerful-internet-of-things-companies.html
|
||||
[7]: https://www.networkworld.com/article/3270961/internet-of-things/10-hot-iot-startups-to-watch.html
|
||||
[8]: https://www.networkworld.com/article/3279346/internet-of-things/the-6-ways-to-make-money-in-iot.html
|
||||
[9]: https://www.networkworld.com/article/3280225/internet-of-things/what-is-digital-twin-technology-and-why-it-matters.html
|
||||
[10]: https://www.networkworld.com/article/3276313/internet-of-things/blockchain-service-centric-networking-key-to-iot-success.html
|
||||
[11]: https://www.networkworld.com/article/3269736/internet-of-things/getting-grounded-in-iot-networking-and-security.html
|
||||
[12]: https://www.networkworld.com/article/3276304/internet-of-things/building-iot-ready-networks-must-become-a-priority.html
|
||||
[13]: https://www.networkworld.com/article/3243928/internet-of-things/what-is-the-industrial-iot-and-why-the-stakes-are-so-high.html
|
||||
[14]: https://blogs.cisco.com/news/cisco-industrial-iot-news
|
||||
[15]: https://www.globenewswire.com/news-release/2018/06/28/1531119/0/en/Sentryo-Named-a-Cool-Vendor-by-Gartner.html
|
||||
[16]: https://www.linkedin.com/pulse/industrial-internet-things-iiot-decoded-nandini-natarajan/
|
||||
[17]: https://pluralsight.pxf.io/c/321564/424552/7490?u=https%3A%2F%2Fwww.pluralsight.com%2Fpaths%2Fcertified-information-systems-security-professional-cisspr
|
||||
[18]: https://www.cisco.com/c/dam/en_us/solutions/iot/ihs-report.pdf
|
||||
[19]: https://www.networkworld.com/article/3336454/cisco-goes-after-industrial-iot.html
|
||||
[20]: https://www.networkworld.com/article/3202699/what-is-intent-based-networking.html
|
||||
[21]: https://blogs.cisco.com/news/securing-the-internet-of-things-cisco-announces-intent-to-acquire-sentryo
|
||||
[22]: https://blogs.cisco.com/security/talos/wannacry
|
||||
[23]: https://www.securityweek.com/norsk-hydro-may-have-lost-40m-first-week-after-cyberattack
|
||||
[24]: https://www.crunchbase.com/organization/sentryo#section-web-traffic-by-similarweb
|
||||
[25]: https://www.facebook.com/NetworkWorld/
|
||||
[26]: https://www.linkedin.com/company/network-world
|
||||
95
translated/news/20190624 Raspberry Pi 4 is here.md
Normal file
95
translated/news/20190624 Raspberry Pi 4 is here.md
Normal file
@ -0,0 +1,95 @@
|
||||
[#]: collector: (lujun9972)
|
||||
[#]: translator: (wahailin)
|
||||
[#]: reviewer: ( )
|
||||
[#]: publisher: ( )
|
||||
[#]: url: ( )
|
||||
[#]: subject: (Raspberry Pi 4 is here!)
|
||||
[#]: via: (https://opensource.com/article/19/6/raspberry-pi-4)
|
||||
[#]: author: (Ben Nuttall https://opensource.com/users/bennuttall)
|
||||
|
||||
树莓派 4 来袭！
|
||||
======
|
||||
售价 35 美元起的新一代树莓派计算机，装载了 1.5 GHz 的 Arm 芯片，并支持双 HDMI 4K 显示，全吞吐量千兆以太网，以及更多新特性。
|
||||
|
||||
![Raspberry Pi 4 board][1]
|
||||
|
||||
树莓派的最新版本树莓派 4 代，已于近日（北京时间 6 月 24 日）发布，这早于此前预期。树莓派 4 装载了 1.5 GHz 的 Arm 芯片和 VideoCore GPU，支持双 4K 显示输出，并引入了 USB 3 接口和全吞吐量千兆以太网，以及最高可达 4G 的多个可选 RAM 配置。
|
||||
|
||||
![Raspberry Pi 4 case][2]
|
||||
|
||||
树莓派 4 是非常强大的单板计算机，其起始售价依然是 35 美元。起始版的 RAM 配置为 1G，2G RAM 配置的树莓派售价为 45 美元，顶配 4G RAM 的树莓派售价为 55 美元，采用这种差异化定价对树莓派尚属首次。
|
||||
|
||||
树莓派 4 的详细配置如下：
|
||||
|
||||
* 1.5 GHz 4 核心 64 位博通 BCM2711 A72 CPU
|
||||
* VideoCore VI GPU
|
||||
* 千兆以太网端口
|
||||
* 1GB/2GB/4GB LPDDR4 SDRAM 内存
|
||||
* 双 Micro-HDMI 接口
|
||||
* 两个 USB 3 接口
|
||||
* 两个 USB 2 接口
|
||||
* 双频（2.4 GHz 和 5 GHz）无线网络
|
||||
* 蓝牙 5.0
|
||||
* USB Type C 电源接口
|
||||
* CSI 摄像头接口
|
||||
* DSI 显示接口
|
||||
* MicroSD 卡槽
|
||||
* PoE（以太网供电）供电针
|
||||
* 完全兼容早期的树莓派产品
|
||||
|
||||
|
||||
|
||||
### USB 接口和网络
|
||||
|
||||
树莓派 4 板载了更高速率的 USB 3 接口；它通过 Type C 接口供电，并提供两个 USB 3 接口和两个 USB 2 接口。USB 3 接口可以为连接的硬盘和其它外部设备提供更高的速率。
|
||||
|
||||
|
||||
![Raspberry Pi 4 USBs][3]
|
||||
|
||||
基于 BCM2835 的树莓派 1 到 3 代的芯片只有一个本地 USB 接口，并且没有以太网接口，因而需要使用板子的 USB 集线器给出更多的 USB 接口和以太网接口。树莓派 3B+ 增加了一个专用的局域网（LAN）芯片，装载了千兆以太网，但它受到 USB 2 速率的限制。树莓派 4 板载了专门的千兆以太网，并且由于它不再收到 USB 速率的限制，网络速度要快得多。
|
||||
|
||||
|
||||
树莓派 4 采用了 3B+ 中已有的技术，这项技术使得树莓派 3B+ 成为了第一个带有双频无线网络的单板计算机，即可以同时连接 2.4 GHz 和 5 GHz 频率的网络。
|
||||
|
||||
### 显示
|
||||
|
||||
设计第一代树莓派时，其 CPU 和 GPU 性能的平衡大大偏向于 GPU。VideoCore IV 是一个非常强大的图形处理器，支持全高清 1080 p 多媒体的处理，这就是为什么树莓派一直作为家庭媒体中心而广受欢迎的原因。树莓派 2 代在某种程度上进行了权衡修改，并将 CPU 的性能进行提升，将树莓派从单核发展成四核 ARM 芯片。而树莓派 4 代将 CPU 和 GPU 的性能都进行了大幅提升。新的 VideoCore VI GPU 支持 4K 视频，并允许通过板子的两个 Micro HDMI 端口（板子特意保持了和旧有型号相同的尺寸）进行双显示输出，这里要用一个适配器或 Micro HDMI 转 full HDMI 的转换线连接到 HDMI 屏幕。
|
||||
|
||||
当你需要同时浏览多个窗口时，需要用到更多的物理显示屏，双显示的好处在此时就得到了绝佳体现。如果你正在编程，你可能会在其中一个屏幕上编写代码，构建网站或应用，而在另一个屏幕上查看数据库、Web 浏览器、电子邮件或其他内容。这是树莓派首次可以不必将开发局限在一台显示器上，从而可以让你在需要时，在不同的屏幕上构建具有不同内容的基于树莓派的项目。
|
||||
|
||||
|
||||
树莓派还有一个显示器串行接口（DSI)，用于驱动另一个特殊的显示-这里并非指另一个监视器本身，而是通过一根挠性电缆连接的官方树莓派触摸屏显示器。
|
||||
|
||||
### Raspbian Buster
|
||||
|
||||
树莓派 4 发布后，紧接着更新了基于 Debian 的系统 Raspbian Buster，而新的树莓派对 OpenGL ES 3 的支持，使我们在 Raspbian Buster 上为树莓派 4 开发任意软件成为可能。 Buster 对界面进行了一些调整，并对很多软件进行了升级，其中包括 Python3.7。
|
||||
|
||||
![Raspbian Buster][4]
|
||||
|
||||
### 开源图形驱动程序
|
||||
|
||||
在过去的五年中，Eric Anholt 一直致力于为树莓派编写开源图形驱动程序。现在，Raspbian 可以使用这个驱动程序加速树莓派上的 Web 浏览、桌面图形和 3D 应用，这取代了以前需要的大量封闭源代码。非常感谢 Eric 和 博通 的贡献。
|
||||
|
||||
按之前预计，树莓派 4 将于明年完成，但由于芯片设计比预期更早投入生产，树莓派 4 因而可以提早到现在发布。
|
||||
|
||||
* * *
|
||||
|
||||
树莓派 4 已经开始发售，你会选择哪个型号呢？在评论中说出你的想法吧。
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://opensource.com/article/19/6/raspberry-pi-4
|
||||
|
||||
作者：[Ben Nuttall][a]
|
||||
选题：[lujun9972][b]
|
||||
译者：[wahailin](https://github.com/wahailin)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
||||
[a]: https://opensource.com/users/bennuttall
|
||||
[b]: https://github.com/lujun9972
|
||||
[1]: https://opensource.com/sites/default/files/styles/image-full-size/public/lead-images/raspberry-pi-4_lead.jpg?itok=2bkk43om (Raspberry Pi 4 board)
|
||||
[2]: https://opensource.com/sites/default/files/uploads/raspberry-pi-4-case.jpg (Raspberry Pi 4 case)
|
||||
[3]: https://opensource.com/sites/default/files/uploads/raspberry-pi-4-usb.jpg (Raspberry Pi 4 USBs)
|
||||
[4]: https://opensource.com/sites/default/files/uploads/raspbian-buster.png (Raspbian Buster)
|
||||
@ -0,0 +1,193 @@
|
||||
使用 Ansible 管理工作站：配置桌面设置
|
||||
======
|
||||
|
||||
|
||||
|
||||
在本系列关于使用 Ansible 配置工作站的[第一篇文章][1]中，我们设置了一个仓库并配置了一些基本的东西。在[第二篇文章][2]中，我们配置了 Ansible 以使其在对仓库进行更改时自动应用设置。在第三篇（也是最后一篇）文章中，我们将使用 Ansible 配置 GNOME 桌面设置。
|
||||
|
||||
此配置只适用于较新的发行版（例如我将在示例中使用的 Ubuntu 18.04）。较旧版本的 Ubuntu 将无法运行，因为它们附带了一个老版本的 `python-psutils`，对于 Ansible 的 `dconf` 模块无法正常工作。如果你使用的是较新版本的 Linux 发行版，则应该没有问题。
|
||||
|
||||
在开始之前，确保你已经完成了本系列的第一部分和第二部分，因为第三部分建立在此基础之上的。如果还没有，下载前两篇文章中一直使用的 GitHub 仓库，我们将为其添加更多功能。
|
||||
|
||||
### 设置壁纸和锁屏
|
||||
|
||||
首先，我们将创建一个任务手册来保存我们的 GNOME 设置。在仓库的根目录中，应该有一个名为 `local.yml` 的文件，添加以下行：
|
||||
```
|
||||
- include: tasks/gnome.yml
|
||||
|
||||
```
|
||||
|
||||
整个文件应如下所示：
|
||||
```
|
||||
- hosts: localhost
|
||||
|
||||
become: true
|
||||
|
||||
pre_tasks:
|
||||
|
||||
- name: update repositories
|
||||
|
||||
apt: update_cache=yes
|
||||
|
||||
changed_when: False
|
||||
|
||||
|
||||
|
||||
tasks:
|
||||
|
||||
- include: tasks/users.yml
|
||||
|
||||
- include: tasks/cron.yml
|
||||
|
||||
- include: tasks/packages.yml
|
||||
|
||||
- include: tasks/gnome.yml
|
||||
|
||||
```
|
||||
|
||||
基本上，这添加了对名为 `gnome.yml` 文件的引用，它将存储在仓库内的 `tasks` 目录中。我们还没有创建这个文件，现在就来创建它。在 `tasks` 目录中创建 `gnome.yml` 文件，并将以下内容放入：
|
||||
```
|
||||
- name: Install python-psutil package
|
||||
|
||||
apt: name=python-psutil
|
||||
|
||||
|
||||
- name: Copy wallpaper file
|
||||
|
||||
copy: src=files/wallpaper.jpg dest=/home/jay/.wallpaper.jpg owner=jay group=jay mode=600
|
||||
|
||||
|
||||
|
||||
- name: Set GNOME Wallpaper
|
||||
|
||||
become_user: jay
|
||||
|
||||
dconf: key="/org/gnome/desktop/background/picture-uri" value="'file:///home/jay/.wallpaper.jpg'"
|
||||
|
||||
```
|
||||
|
||||
注意，此代码多次引用我的用户名（`jay`），因此确保使用你机器上的用户名替换每次出现的 `jay`。另外，如果你没有像我一样使用 Ubuntu 18.04，你将不得不更改 `apt` 一行来匹配你所选择的发行版的包管理器，并确认 `python-psutil` 包的名称，因为它可能有所不同。
|
||||
|
||||
|
||||
在示例任务中，我引用了 `file` 目录下的 `wallpaper.jpg` 文件，此文件必须存在，否则 Ansible 配置将失败。在 `tasks` 目录中，创建一个名为 `files` 的子目录。找到你喜欢的壁纸图片，将其命名为 `wallpaper.jpg`，然后把它放在 `files` 目录中。如果文件是 PNG 图像而不是 JPG，在代码和仓库中更改文件扩展名。如果你觉得没有创意，我在 [GitHub 仓库][3] 中有一个示例壁纸文件，你可以使用它。
|
||||
|
||||
完成所有这些更改后，将内容提交到 GitHub 仓库，并推送这些更改。总结一下，你应该完成以下工作：
|
||||
|
||||
* 修改 `local.yml` 文件以引用 `tasks/gnome.yml`
|
||||
* 使用上面提到的内容创建 `tasks/gnome.yml`
|
||||
* 在 `tasks` 目录中创建一个 `files` 目录，其中有一个名为 `wallpaper.jpg` 的图像文件（或者你选择的任何名称）。
|
||||
|
||||
|
||||
完成这些步骤并将更改推送到仓库后，配置应该在下次计划运行期间自动应用。（你可能还记得我们在上一篇文章中对此进行了自动化。）如果你赶时间，可以使用以下命令立即应用配置：
|
||||
```
|
||||
sudo ansible-pull -U https://github.com/<github_user>/ansible.git
|
||||
|
||||
```
|
||||
|
||||
如果一切正常，你应该可以看到你的新壁纸。
|
||||
|
||||
让我们花一点时间来了解新 GNOME 任务手册的功能。首先，我们添加了一个计划来安装 `python-psutil` 包。如果不添加它，我们就不能使用 `dconf` 模块，因为它需要在修改 GNOME 设置之前安装这个包。接下来，我们使用 `copy` 模块将壁纸文件复制到我们的 `home` 目录，并将生成的文件命名为以点开头的隐藏文件。如果你不希望此文件放在 `home` 目录的根目录中，你可以随时指示此部分将其复制到其它位置 - 只要你在正确的位置引用它，它仍然可以工作。在下一个计划中，我们使用 `dconf` 模块来更改 GNOME 设置。在这种情况下，我们调整了 `/org/gnome/desktop/background/picture-uri` 键并将其设置为 `file:///home/jay/.wallpaper.jpg`。注意本节中的引号 - 你必须在 `dconf` 值中使用两个单引号，如果值是一个字符串，还必须包含双引号。
|
||||
|
||||
现在，让我们进一步进行配置，并将背景应用于锁屏。这是 GNOME 任务手册，但增加了两个额外的计划：
|
||||
```
|
||||
- name: Install python-psutil package
|
||||
|
||||
apt: name=python-psutil
|
||||
|
||||
|
||||
|
||||
- name: Copy wallpaper file
|
||||
|
||||
copy: src=files/wallpaper.jpg dest=/home/jay/.wallpaper.jpg owner=jay group=jay mode=600
|
||||
|
||||
|
||||
|
||||
- name: Set GNOME wallpaper
|
||||
|
||||
dconf: key="/org/gnome/desktop/background/picture-uri" value="'file:///home/jay/.wallpaper.jpg'"
|
||||
|
||||
|
||||
|
||||
- name: Copy lockscreenfile
|
||||
|
||||
copy: src=files/lockscreen.jpg dest=/home/jay/.lockscreen.jpg owner=jay group=jay mode=600
|
||||
|
||||
|
||||
|
||||
- name: Set lock screen background
|
||||
|
||||
become_user: jay
|
||||
|
||||
dconf: key="/org/gnome/desktop/screensaver/picture-uri" value="'file:///home/jay/.lockscreen.jpg'"
|
||||
|
||||
```
|
||||
|
||||
正如你所看到的，我们做的事情和设置壁纸时差不多。我们添加了两个额外的任务，一个是复制锁屏图像并将其放在我们的 `home` 目录中，另一个是将设置应用于 GNOME 以便使用它。同样，确保将 `jay` 更改为你的用户名，并命名你想要的锁屏图片 `lockscreen.jpg`，并将其复制到 `files` 目录。将这些更改提交到仓库后，在下一次计划的 Ansible 运行期间就会应用新的锁屏。
|
||||
|
||||
### 应用新的桌面主题
|
||||
|
||||
设置壁纸和锁屏背景很酷，但是让我们更进一步来应用桌面主题。首先，让我们在我们的任务手册中添加一条指令来安装 `arc` 主题的包。将以下代码添加到 GNOME 任务手册的开头：
|
||||
```
|
||||
- name: Install arc theme
|
||||
|
||||
apt: name=arc-theme
|
||||
|
||||
```
|
||||
|
||||
然后，在底部，添加以下任务：
|
||||
```
|
||||
- name: Set GTK theme
|
||||
|
||||
become_user: jay
|
||||
|
||||
dconf: key="/org/gnome/desktop/interface/gtk-theme" value="'Arc'"
|
||||
|
||||
```
|
||||
|
||||
你看到 GNOME 的 GTK 主题在你眼前变化了吗？我们添加了一个任务来通过 `apt` 模块安装 `arc-theme` 包，另一个任务将这个主题应用到 GNOME。
|
||||
|
||||
### 进行其它定制
|
||||
|
||||
既然你已经更改了一些 GNOME 设置，你可以随意添加其它定制。你在 GNOME 中调整的任何设置都可以通过这种方式自动完成，设置壁纸和主题只是几个例子。你可能想知道如何找到要更改的设置，以下一个适合我的技巧。
|
||||
|
||||
首先，通过在你管理的计算机上运行以下命令，获取所有当前 `dconf` 设置的快照：
|
||||
```
|
||||
dconf dump / > before.txt
|
||||
|
||||
```
|
||||
|
||||
此命令将所有当前更改导出到名为 `before.txt` 的文件中。接下来，手动更改要自动化的设置，并再次获取 `dconf` 设置：
|
||||
```
|
||||
dconf dump / > after.txt
|
||||
|
||||
```
|
||||
|
||||
现在，你可以使用 `diff` 命令查看两个文件之间的不同之处：
|
||||
```
|
||||
diff before.txt after.txt
|
||||
|
||||
```
|
||||
|
||||
这应该会给你一个已更改键的列表。虽然手动更改设置确实违背了自动化的目的，但你实际上正在做的是获取更新首选设置时更改的键，这允许你创建 Ansible 任务以修改这些设置，这样你就再也不需要碰这些设置了。如果你需要还原机器，Ansible 仓库将负责你的每个定制。如果你有多台计算机，甚至是一组工作站，则只需手动进行一次更改，所有其他工作站都将应用新设置并完全同步。
|
||||
|
||||
### 最后
|
||||
|
||||
如果你已经阅读完本系列文章，你应该知道如何设置 Ansible 来自动化工作站。这些示例提供了一个有用的基线，你可以使用语法和示例进行其他定制。随着你的前进，你可以继续添加新的修改，这将使你的 Ansible 配置一直增长。
|
||||
|
||||
我已经用 Ansible 以这种方式自动化了一切，包括我的用户帐户和密码、Vim、tmux 等配置文件、桌面包、SSH 设置、SSH 密钥，基本上我想要自定义的一切都使用了。以本系列文章作为起点，将为你实现工作站的完全自动化铺平道路。
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://opensource.com/article/18/5/manage-your-workstation-ansible-part-3
|
||||
|
||||
作者：[Jay LaCroix][a]
|
||||
选题：[lujun9972](https://github.com/lujun9972 )
|
||||
译者：[MjSeven](https://github.com/MjSeven)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
||||
[a]:https://opensource.com/users/jlacroix
|
||||
[1]:https://opensource.com/article/18/3/manage-workstation-ansible
|
||||
[2]:https://opensource.com/article/18/3/manage-your-workstation-configuration-ansible-part-2
|
||||
[3]:https://github.com/jlacroix82/ansible_article.git
|
||||
@ -1,169 +0,0 @@
|
||||
[#]: collector: "lujun9972"
|
||||
[#]: translator: "qfzy1233"
|
||||
[#]: reviewer: " "
|
||||
[#]: publisher: " "
|
||||
[#]: url: " "
|
||||
[#]: subject: "Top 5 Linux Distributions for Productivity"
|
||||
[#]: via: "https://www.linux.com/blog/learn/2019/1/top-5-linux-distributions-productivity"
|
||||
[#]: author: "Jack Wallen https://www.linux.com/users/jlwallen"
|
||||
|
||||
五个最具生产力的 Linux 发行版
|
||||
======
|
||||
|
||||
|
||||
|
||||
必须承认的是，这样一个热门的话题其实很难被总结出来。为什么呢？首先，Linux 在设计层面就是一种有生产力的操作系统。由于它极强的可靠性和稳定的平台，使得工作的开展变得简易化。其次为了衡量工作的效率，你需要考虑到哪项工作需要得到生产力方面的助推。是普通办公？开发类工作？学校事务？数据挖掘？或者是人力资源？你可以看到这一问题变得复杂起来了。
|
||||
|
||||
然而，这并不意味着那些基于推动底层操作系统成为更为高效平台的发行版们可以在配置和呈现方面做的更好。恰恰相反，许多发行版在偏离生产力这条道路上越走越远，所以你不会意识到你自己处在工作的窘境中，而是继续挖掘自己的潜力在工期结束之前拼命赶上进度。这些 Linux 发行版可以帮助你化繁为简，因此或许可以减少你工作流程中的痛点。
|
||||
|
||||
让我们来看一下这些发行版并为你找出适合你的最佳选择。为了更具条理，我按照生产力诉求把他们分成了几类。这项任务本身也是一种挑战，因为每个人在生产力提升上的需要是千差万别的。然而，我所关注的是下列的几项：
|
||||
|
||||
* 普通生产力: 适于从事复杂工作并希望提升工作效率。
|
||||
|
||||
* 平面设计: 适于从事设计创造和图像处理的人们。
|
||||
|
||||
* 开发: 适于那些使用 Linux 桌面发行版来进行编程工作。
|
||||
|
||||
* 管理人员: 适于那些需要某些版本来促进一体化的管理任务的人员。
|
||||
|
||||
* 教育: 适于那些需要桌面发行版可以助力他们在教育领域更创造力的人们。
|
||||
|
||||
|
||||
诚然，有很多很多类别的发行版可供挑选，其中的很多可能用起来十分得心应手，但这五种或许是你最为需要的。
|
||||
|
||||
|
||||
### 普通生产力
|
||||
|
||||
对普通的生产力诉求来说，你不会找到比 [Ubuntu][1] 更为高效的了。在这个类别中首推 Ubuntu 最基础的原因是因为它实现了桌面操作系统、软件、服务的无缝集成。你可能会问为什么我不选择同类别的 Linux Mint 呢？因为 Ubuntu 现在默认的的桌面环境为 GNOME 桌面，而它拥有 GNOME 许多扩展程序的优势的加成（图 1）。
|
||||
|
||||
|
||||
![GNOME Clipboard][3]
|
||||
|
||||
图 1：运行中的 GNOME 桌面的剪切板管理工具。
|
||||
|
||||
[经许可使用][4]
|
||||
|
||||
这些扩展程序在提升生产力方面做了很多努力(所以 Ubuntu 比 Linux Mint 获得了更多的认可)。但是 Ubuntu 不仅仅支持 vanilla 版本的 GNOME 桌面。事实上，他们致力于将它改进的更为轻量化、更为高效、以及用户友好度更高、开箱即用。总而言之，由于 Ubuntu 正确的融合了多种特性，开箱即用，完善的软件支持（仅对工作方面而言），这些特性使它几乎成为了生产力领域最为完美的一个平台。
|
||||
|
||||
不管你是要写一篇文档，制作一张电子表格，写一个新的软件，开啊公司的网站，设计商用的图形，管理一个服务器或是网络，抑或是在你的公司内从事人力资源管理工作， Ubuntu 都可以满足你的需求。Ubuntu 桌面发行版也并不要求你耗费很大的精力才能开始开始开展工作…他只是纯粹的工作（并且十分优秀）。最后，得益于 Debian 的基础，使得 Ubuntu 上安装第三方的软件十分简便。
|
||||
|
||||
很难反对这一特殊的发行版在生产力发行版列表中独占鳌头，尽管 Ubuntu 几乎已经成为几乎所有“顶级发行版”列表的榜首。
|
||||
|
||||
### 平面设计
|
||||
|
||||
如果你正在寻求提升你的平面设计效率，你不能错过[Fedora设计套件][5]。这一 Fedora 的衍生版是由负责 Fedora 艺术类项目的团队亲自操刀制作的。虽然默认选择的应用程序并不是一个庞大的工具集合，但它所包含的工具都是创建和处理图像专用的。
|
||||
|
||||
有了GIMP、Inkscape、Darktable、Krita、Entangle、Blender、Pitivi、Scribus等应用程序(图 2)，您将发现完成图像编辑工作所需要的一切都已经准备好了，而且准备得很好。但是Fedora设计套件并不仅限于此。这个桌面平台还包括一堆教程，涵盖了许多已安装的应用程序。对于任何想要尽可能提高效率的人来说，这将是一些非常有用的信息。不过，我要说的是，GNOME Favorites中的教程不过是[此页][6]链接的内容。
|
||||
|
||||
![Fedora Design Suite Favorites][8]
|
||||
|
||||
图 2: Fedora Design Suite Favorites菜单包含了许多工具，可以让您用于图形设计。
|
||||
|
||||
[经许可使用][4]
|
||||
|
||||
那些使用数码相机的用户肯定会喜欢Entangle应用程序，它可以让你在电脑上上控制单反相机。
|
||||
|
||||
### 开发人员
|
||||
|
||||
几乎所有的Linux发行版对于程序员来说都是很好的编程平台。然而，有一种特定的发行版脱颖而出，并超越了其他发行版，它将是您见过的用于编程类最有效率的工具之一。这个操作系统来自[System76][9]（译注：一家美国的计算机制造商），名为[Pop!_OS][10]。Pop!_OS是专门为创作者定制的，但不是针对艺术类。相反,Pop!_OS面向专门从事开发、编程和软件制作的程序员。如果您需要一个既能完美的胜任开发平台又包含桌面操作系统的开发环境，Pop!_OS 将会是您的不二选择。 (图 3)
|
||||
|
||||
可能会让您感到惊讶(考虑到这个操作系统是多么“年轻”)的是Pop!_OS也是您使用过的基于 GNOME平台的最稳定系统的之一。这意味着 Pop!_OS 不只是为创造者和制造者准备的，也是为任何想要一个可靠的操作系统的人准备的。你可以下载针对你的硬件的专门 ISO 文件，这一点是许多用户十分欣赏的。如果你有英特尔硬件,[下载][10]Intel或AMD的版本。如果您的显卡是NVIDIA，请下载该特定版本。不管怎样，您肯定会得到针对不同平台进行特殊定制的稳定的版本。
|
||||
|
||||
![Pop!_OS][12]
|
||||
|
||||
图 3: 装有 GNOME 桌面的 Pop!_OS 一览。
|
||||
|
||||
[经许可使用][4]
|
||||
|
||||
有趣的是，在 Pop!_OS 中，您不会找到太多预装的开发工具。你也不会找到IDE或许多其他开发工具。但是，您可以在Pop 商店中中找到所需的所有开发工具。
|
||||
|
||||
### 管理人员
|
||||
|
||||
如果你正在寻找适合管理领域的最生产力的发行版本，[Debian][13]将会是你的不二之选。为什么这么说呢？因为 Debian 不仅仅拥有无与伦比的可靠性，它也是众多能从苦海中将你解救出来的最好的一个版本。Debian是易用性和无限可能性的完美结合。最重要的是，因为它是许多其他发行版的基础，所以可以打赌的是，如果您需要一个任务的管理工具，那么它一定支持 Debian 系统。当然，我们讨论的是一般管理任务，这意味着大多数时候您需要使用终端窗口 SSH 连接到服务器(图4)，或者在浏览器上使用网络上基于web的GUI工具。既然如此为什么还要使用一个复杂的桌面呢(比如Fedora中的SELinux或openSUSE中的YaST)呢?所以,应选择更为简洁易用的那一种。
|
||||
![Debian][15]
|
||||
|
||||
图 4: 在 Debian 系统上通过SSH 连接到远程服务器。
|
||||
|
||||
[经授权使用][4]
|
||||
|
||||
你可以选择你想要的不同的桌面（包括GNOME, Xfce, KDE, Cinnamon, MATE, LXDE），确保你所使用的桌面外观最适合你的工作习惯。
|
||||
|
||||
### 教育
|
||||
|
||||
如果你是一名老师或者学生，抑或是其他从事与教育相关工作的人士，你需要适当的工具来变得更具创造力。之前，有 Edubuntu 这样的版本。这一版本位列教育类相关发行版排名的前列。然而，自从 Ubuntu 14.04 版之后这一发行版就再也没有更新。还好，现在有一款基于 openSUSE 的新的以教育为基础的发行版有望夺摘得桂冠。这一改版叫做 [openSUSE:Education-Li-f-e][16] (Linux For Education - 图 5), 它基于 openSUSE Leap 42.1 （所以它可能稍微有一点过时）。
|
||||
|
||||
openSUSE:Education-Li-f-e 包含了一下工具：
|
||||
|
||||
* Brain Workshop（大脑工坊） - 一种基于 dual n-back 模式的大脑训练软件（译注：dual n-back 训练是一种科学的智力训练方法，可以改善人的工作记忆和流体智力）
|
||||
|
||||
* GCompris - 一种针对青少年的教育软件包
|
||||
|
||||
* gElemental - 一款元素周期表查看工具
|
||||
|
||||
* iGNUit - 一款通用的记忆卡片工具
|
||||
|
||||
* Little Wizard - 基于 Pascal 语言的少儿编程开发环境
|
||||
|
||||
* Stellarium - 天文模拟器
|
||||
|
||||
* TuxMath - 数学入门游戏
|
||||
|
||||
* TuxPaint - 一款少儿绘画软件
|
||||
|
||||
* TuxType - 一款为少儿准备的打字入门软件
|
||||
|
||||
* wxMaxima - 一个跨平台的计算机代数系统
|
||||
|
||||
* Inkscape - 矢量图形编辑软件
|
||||
|
||||
* GIMP - 图像处理软件（译注：被誉为 Linux 上的 PhotoShop）
|
||||
|
||||
* Pencil - GUI 模型制作工具
|
||||
|
||||
* Hugin - 全景照片拼接及 HDR 效果混合软件
|
||||
|
||||
|
||||
![Education][18]
|
||||
|
||||
图 5: openSUSE:Education-Li-f-e 发行版拥有大量的工具可以帮你在学校中变得更为高效。
|
||||
|
||||
[经许可使用][4]
|
||||
|
||||
同时还集成在 openSUSE:Education-Li-f-e 中的还有 [KIWI-LTSP Server][19] 。Also included with openSUSE:Education-Li-f-e is the [KIWI-LTSP Server][19]. KIWI-LTSP KIWI-LTSP服务器是一个灵活的、成本有效的解决方案，旨在使全世界的学校、企业和组织能够轻松地安装和部署桌面工作站。虽然这可能不会直接帮助学生变得更具创造力，但它肯定会使教育机构在部署供学生使用的桌面时更有效率。有关配置 KIWI-LTSP 的更多信息，请查看openSUSE [KIWI-LTSP quick start guide][20].
|
||||
|
||||
通过 Linux 基金会和 edX 的免费["入门介绍"][21]课程来了解更多关于 Linux 的知识。
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://www.linux.com/blog/learn/2019/1/top-5-linux-distributions-productivity
|
||||
|
||||
作者：[Jack Wallen][a]
|
||||
选题：[lujun9972][b]
|
||||
译者：[qfzy1233](https://github.com/译者ID)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
||||
[a]: https://www.linux.com/users/jlwallen
|
||||
[b]: https://github.com/lujun9972
|
||||
[1]: https://www.ubuntu.com/
|
||||
[2]: /files/images/productivity1jpg
|
||||
[3]: https://www.linux.com/sites/lcom/files/styles/rendered_file/public/productivity_1.jpg?itok=yxez3X1w "GNOME Clipboard"
|
||||
[4]: /licenses/category/used-permission
|
||||
[5]: https://labs.fedoraproject.org/en/design-suite/
|
||||
[6]: https://fedoraproject.org/wiki/Design_Suite/Tutorials
|
||||
[7]: /files/images/productivity2jpg
|
||||
[8]: https://www.linux.com/sites/lcom/files/styles/rendered_file/public/productivity_2.jpg?itok=ke0b8qyH "Fedora Design Suite Favorites"
|
||||
[9]: https://system76.com/
|
||||
[10]: https://system76.com/pop
|
||||
[11]: /files/images/productivity3jpg-0
|
||||
[12]: https://www.linux.com/sites/lcom/files/styles/rendered_file/public/productivity_3_0.jpg?itok=8UkCUfsD "Pop!_OS"
|
||||
[13]: https://www.debian.org/
|
||||
[14]: /files/images/productivity4jpg
|
||||
[15]: https://www.linux.com/sites/lcom/files/styles/rendered_file/public/productivity_4.jpg?itok=c9yD3Xw2 "Debian"
|
||||
[16]: https://en.opensuse.org/openSUSE:Education-Li-f-e
|
||||
[17]: /files/images/productivity5jpg
|
||||
[18]: https://www.linux.com/sites/lcom/files/styles/rendered_file/public/productivity_5.jpg?itok=oAFtV8nT "Education"
|
||||
[19]: https://en.opensuse.org/Portal:KIWI-LTSP
|
||||
[20]: https://en.opensuse.org/SDB:KIWI-LTSP_quick_start
|
||||
[21]: https://training.linuxfoundation.org/linux-courses/system-administration-training/introduction-to-linux
|
||||
@ -0,0 +1,262 @@
|
||||
[#]: collector: (lujun9972)
|
||||
[#]: translator: (chen-ni)
|
||||
[#]: reviewer: ( )
|
||||
[#]: publisher: ( )
|
||||
[#]: url: ( )
|
||||
[#]: subject: (5 tiny Linux distros to try before you die)
|
||||
[#]: via: (https://opensource.com/article/19/6/linux-distros-to-try)
|
||||
[#]: author: (Seth Kenlon https://opensource.com/users/seth/users/marcobravo)
|
||||
|
||||
5 个不容错过的微型 Linux 发行版
|
||||
======
|
||||
这些微型 Linux 发行版可以让你的老爷机复活、启动一个损坏的系统，或者是确保在公共电脑上进行安全的操作。
|
||||
![Hand putting a Linux file folder into a drawer][1]
|
||||
|
||||
可供日常使用的 Linux 发行版比比皆是，不过其中有一些发行版常常被我们忽视，因为它们实在是太小了。但这些微型 Linux 发行版其实是一种非常强大的创新：使用一套完整的操作系统驱动一台只有不到 1 GB 存储空间和 512 MB 内存的计算机，真的是终极的黑客作风。
|
||||
|
||||
微型发行版的用法有很多种，比如说：
|
||||
|
||||
* 从垃圾桶边挽救回那些又老又慢的电脑。你可以继续使用那些本来已经计划报废的机器，直到它们彻底解体（而不是在刚开始感觉有点儿慢的时候就扔掉）。
|
||||
* 使用 U盘 启动一个损坏的系统来恢复数据或者修复启动分区。
|
||||
* 确保在安全和隐私的操作环境下使用公共电脑。如果使用 U盘 启动酒店大厅或者图书馆里的一台公共电脑，你是可以确定操作环境是安全的。
|
||||
|
||||
轻量级发行版有很多种，比如说 [Lubuntu][2]、[Peppermint OS][3] 和 [Bodhi][4]，但是那些真正微型的发行版又有一些独到之处。下面就是你不容错过的五个微型发行版：
|
||||
|
||||
### Tiny Core
|
||||
|
||||
![Tiny Core Linux][5]
|
||||
|
||||
[Tiny Core Linux][6] 小得近乎不可思议：终端版本只有 11 MB，图形界面版本只有 16 MB。我翻了一下之前收集的旧 U盘，最小的一个是 128 MB 的，也有 Tiny Core 镜像文件的八倍之大呢。
|
||||
|
||||
Tiny Core 默认包括只包括了基础操作系统，你需要通过以太网下载需要的应用程序。由于设计得极端精简，甚至安装完整操作系统的应用程序都没有被包含在内（不过需要的话可以从 Tiny Core 的软件仓库下载）。
|
||||
|
||||
我使用过一个 128 MB 的 U盘 在一台只有 512 MB 内存的机器上运行了 Tiny Core，对于一个只有 16 MB 的操作系统来说，效果算是非常棒了。只有在使用网页浏览器的时候速度才会变慢，但这主要是由于大部分现代网站太过复杂，而不是 Tiny Core 的问题。
|
||||
|
||||
如果不使用图形界面，运行 Tiny Core 就只需要 64 MB 的内存了。
|
||||
|
||||
#### 安装
|
||||
|
||||
[下载 Tiny Core][7] 并使用 **dd** 或者 [Etcher][8] 写入 U盘。
|
||||
|
||||
你只需要点击屏幕底部启动栏上的 **Apps** 图标下载 **tc-install** 或者 **tc-install-GUI** 应用，就可以轻松安装 Tiny Core了。
|
||||
|
||||
![Tiny Core installer][9]
|
||||
|
||||
安装 Tiny Core 有几种不同的方式。你可以把它安装在一个格式化为 Linux 驱动的 U盘 里（这要求你的电脑支持使用 USB 驱动启动。大多数现代电脑都支持，但是在老一些的电脑上不太常见），或者安装在微软 FAT 文件系统的 U盘 里（这对于大多数不支持从 USB 驱动启动的电脑来说非常管用），或者甚至安装在一个现有 Linux 分区的一个文件夹里。
|
||||
|
||||
安装过程非常快，完成之后就可以重启计算机，进入到 Tiny Core Linux 系统中啦。
|
||||
|
||||
#### 应用程序
|
||||
|
||||
由于系统自带程序基本上只有一个文本编辑器和一个终端，你所要做的第一件事情就应该是安装一些应用程序。底部启动栏上的 **Apps** 图标展示了 Tiny Core 提供的所有软件包。**Apps** 软件仓库同时包含了一些重要的驱动程序，对于使用 WiFi 网卡或者是打印机等等都很有帮助。
|
||||
|
||||
在安装一个新的应用程序或者实用程序的时候，你可以选择在 Tiny Core 启动的时候就加载软件包，或者是需要的时候才加载。如果选择启动时加载，那么不仅该软件立即就可以使用，并且（不出所料地）下次重启之后也依然可用；如果选择需要时加载，那么在软件包下载完成之后仍然可以马上使用，但是重启之后就不会被自动加载到内存中了。这样可以保持很快的开机速度，并且只占用很少的内存，但同时也意味着每次开机之后，该应用的软件包只有在第一次被使用的时候才会被加载到内存中。
|
||||
|
||||
可供选择的应用程序同时包括像 office 和图像应用之类的用户端应用，以及像 [Samba][10] 和网站服务器这种的服务端应用。
|
||||
|
||||
当然了，随着你在 Tiny Core 上添加的应用程序越来越多，它就不那么“微型”了。不过在 Tiny Core 的网站上我们可以看到，即使是包括了所有 WiFi 驱动程序的 **Tiny Core Plus** 镜像文件也只有大约 100 MB，所以“不那么微型”也仍然很可能比 256 MB 要小很多。
|
||||
|
||||
#### 结论
|
||||
|
||||
Tiny Core 非常适合性能不佳的老爷机、用来通过网络启动的镜像文件，以及任何更看重应用而不是操作系统的人。Tiny Core 可以作为一个很好的周末工程来实践：从 16 MB 开始一步步搭建操作系统，直到你感觉这个操作系统已经足够满足你的需求了。
|
||||
|
||||
### SliTaz
|
||||
|
||||
![SliTaz Linux][11]
|
||||
|
||||
[SliTaz Linux][12] 的镜像文件有大约 51 MB 大小，差不多是 Tiny Core 的四倍，但是包含一整套出色的驱动程序和应用程序。事实上，如果事先不知道的话，你可能会以为是通过一个 1 GB 的 Ubuntu 镜像启动的，因为能想到的任何一个基本启动镜像应该有的东西都在这儿：文本编辑器、网页浏览器、绘画工具、表格工具等等。
|
||||
|
||||
我使用过一个 128 MB 的 U盘 在一个 512 MB 内存的机器上运行了 SliTaz，效果非常不错。浏览复杂网站的时候性能会下降，但是系统包含的轻量级浏览器 [Midori][13] 可以快速加载绝大多数网站。
|
||||
|
||||
你可以在启动的时候选择进入没有图形界面的 SliTaz，这样在仅仅只有 64 MB 的机器上也可以很好地运行。
|
||||
|
||||
#### 安装
|
||||
|
||||
可供下载的 SliTaz 有很多种，因为它的开发者和社区针对可能存在的限制提供了非常多的版本。比如说，有一种低内存版本可以在只有 24 MB 内存的机器上运行；有一种版本使用 Firefox 而不是 Midori；还有一种版本没有包含额外的应用程序，等等。
|
||||
|
||||
如果你挑花了眼，只想赶紧选择一个版本尝试一下的话，那就 [下载滚动发布版本吧][14]。这个版本有差不多 50 MB 大小，每周都会更新。如果你爱上了 SliTaz，而滚动发布版本又更新得 *过快* 了的话，可以再选择一个更符合你需求的版本。
|
||||
|
||||
下载好你选择的 SliTaz 镜像文件之后，你就可以用 **dd** 或者 [Etcher][8] 将它写入 U盘，然后重启。
|
||||
|
||||
将 SliTaz 安装在 U盘 或者硬盘上需要通过 **TazPanel** 这个应用程序来实现。它会引导你对硬盘进行需要的分区，然后将 SliTaz 安装在你选择的地方。
|
||||
|
||||
![SliTaz installer][15]
|
||||
|
||||
#### 应用程序
|
||||
|
||||
SliTaz 的控制中心是 **TazPanel** 这个应用程序。如果你喜欢 OpenSUSE 或者 Mageia (最初被称为 Mandrake)，那 TazPanel 对你来说应该不会陌生（至少在核心思想上）：包括系统设置、硬件监测、用户和用户组的管理、系统升级、安装应用程序在内的这些功能，都在这一个应用程序内实现。
|
||||
|
||||
SliTaz 提供的应用程序可以满足大多数基本需求，如果你不是非常在意完成某一项任务必须使用哪一个应用程序的话，那么在 SliTaz 的软件仓库里应该可以找到你想要的应用。如果你有一些特别的需求（比如说想要使用 GIMP 2.10 而不是 GIMP 2.8），那么就需要学习如何生成 SliTaz 软件包了。好消息是，**tazpkg** 命令支持从好几种软件包格式转换过来，包括：
|
||||
|
||||
* Debian 软件包 (.deb, .udeb)
|
||||
* RPM 软件包 (.rpm)
|
||||
* Slackware 软件包 (.tgz)
|
||||
* Puppy 软件包 (.sfs, .pet)
|
||||
* NuTyX 软件包 (.cards.tar.xz)
|
||||
* Arch 和 Alpine Linux 软件包 (.apk, .pkg.tar.gz, .pkg.tar.xz)
|
||||
* OpenWrt 软件包 (.ipk, .opk)
|
||||
* Paldo 软件包 (.tar.bz2)
|
||||
* Void 软件包 (.xbps)
|
||||
* Tiny Core 软件包 (.tce, .tcel, .tcem, .tcz)
|
||||
|
||||
#### 结论
|
||||
|
||||
SliTaz 是一个快速而小巧的 Linux 发行版，并且非常容易上手（因为有一个中心化的控制面板）。由于它的软件包工具支持从其它格式的 Linux 软件包转换成自己的格式，它的应用程序理论上来说是非常丰富的，你可以很容易地使用喜欢的工具搭建自己的工作环境。SliTaz 很小，但是也非常具有杀伤力，正如它的蜘蛛 logo 所暗示的那样。
|
||||
|
||||
### Porteus
|
||||
|
||||
![Porteus Linux][16]
|
||||
|
||||
[Porteus][17] 提供了不同的桌面环境可供选择，最小的镜像文件大约在 270 MB 左右，最大的有 350 MB。它是微型 Linux 中镜像文件最大的一个，但是这些额外的空间都被用来确保一个非常顺畅的 Linux 桌面环境的体验，以至于你很可能会忘了自己是在使用一个 live 版本。如果将 Porteus 安装到 SSD 或者是在启动的时候加载到内存里的话，你就会得到一个如此天衣无缝地顺畅的环境，以至于不会相信你的操作系统所占用的空间只有不到半个 CD-ROM 的大小。
|
||||
|
||||
Porteus 的基础镜像文件相对来说比较小，因此被称为是“微型”，但是根据你选择的桌面环境版本，Porteus 有可能会需要 1 GB 之多的内存才可以运行。尽管其它微型 Linux 发行版倾向于通过精简应用程序来节约空间和资源，Porteus 却希望你像普通发行版一样来使用它。忘掉你是在使用一个微型的压缩根文件系统，尽情安装所有你喜欢的应用程序吧。
|
||||
|
||||
#### 安装
|
||||
|
||||
可以在 [离你最近的 Porteus 镜像网站][18] 上下载 Porteus，并且从 MATE、LXQT、LXDE、OpenBox、XFCE、Cinnamon 或者 KDE 里选择自己喜欢的桌面环境。如果没有特殊偏好，MATE 或者是 KDE 桌面都是不错的选择，他们可以提供熟悉的桌面环境体验，并且镜像文件又不至于太大。
|
||||
|
||||
![Porteus installer][19]
|
||||
|
||||
你可以根据 [官方的安装指南][20] 将 Porteus 安装到一个 U盘 或者是内部硬盘里。这两种方式非常相似，都会使用一个不能被改变的压缩根文件系统。这是一种稳定的、受限制的文件系统，会根据你的使用被修改。你所做的变更和安装的应用程序在重启的时候都会被加载到内存里，从而还原你关机前的使用环境。
|
||||
|
||||
#### 应用程序
|
||||
|
||||
应用程序在 Porteus 里被称为“模块”，由 [Slackware 软件包统一管理器][21]（USM）提供。USM 的资源涵盖五个不同的 Slackware 软件仓库，所以可供选择的应用还是很丰富的。
|
||||
|
||||
#### 结论
|
||||
|
||||
Porteus 可以提供完整的 Linux 使用体验，却只使用了正常 Linux 所需要空间的一小部分。这是一个配备了很多种可供选择的桌面环境和很多应用程序的出色的便携式 Linux 发行版。
|
||||
|
||||
### Bodhi Linux
|
||||
|
||||
![Bodhi Linux][22]
|
||||
|
||||
[Bodhi Linux][4] 的 ISO 镜像文件有 740 MB 大小，初看之下并不是很“微型”，不过一旦安装完成之后，你就会惊讶于它是多么微型了。Bodhi 在 512 MB 大小的内存上也可以顺畅运行，并且它的桌面环境看起来就像是来自未来一样。Bodhi 使用的是 [Enlightenment][23] 桌面，这是一个精心制作的优美的用户界面，小巧而强悍。
|
||||
|
||||
不过 Bodhi 并不只是简单地使用 Enlightenment，而是在此基础上增色不少。Bodhi 在配置型应用程序和系统设置面板上都进行了界面处理，避免了 Enlightenment 有时显得过于繁复的选项。Bodhi 替你做了一些很好的默认选择，并且只显示全部选项的一部分。如果你是一个 Enlightenment 狂热分子，那么 Bodhi 这样的做法对你来说可能显得不是很纯粹，但是对于大多数用户来说，Bodhi 这样做可以让人更加专注于 Enlightenment 桌面本身。
|
||||
|
||||
#### 安装
|
||||
|
||||
[下载 Bodhi Linux][24]，通过 **dd** 或者 [Etcher][8] 写入 U盘，然后重启。
|
||||
|
||||
Bodhi 安装器可以在 **设置** 页面的 **应用程序** 菜单里找到。安装程序用的是 **Ubiquity**，所以整个过程和安装 Ubuntu 是一样的。如果你没有安装过 Ubuntu 也不必担心，因为这是最好安装的发行版之一了。
|
||||
|
||||
![Bodhi installer][25]
|
||||
|
||||
#### 应用程序
|
||||
|
||||
Bodhi 是基于最新的 Ubuntu 长期维护发布版的，所以可供使用的应用程序简直数不胜数。只要是在 Ubuntu 上可以使用的应用，Bohdi 上就同样可以找到。
|
||||
|
||||
#### 结论
|
||||
|
||||
Bodhi Linux 相比一个标准的 Ubuntu 来说要小不少，但是相比其它微型 Ubuntu 环境来说又好一些（因为使用了 Enlightenment）。如果你在找一个比大多数发行版更轻量的 Linux 发行版，但是又不想使用 OverlayFS 或者是应用程序模块的话，那么 Bodhi 就是一个不错的选择了。
|
||||
|
||||
### Puppy Linux
|
||||
|
||||
![Puppy Linux][26]
|
||||
|
||||
早在 Tiny Core、SliTaz、[AntiX][27] 或者是 Porteus 诞生之前，就已经有 [Puppy Linux][28] 了。作为最早的微型 Linux 发行版之一，Puppy 已经历经了十五年风霜，并且无论是对于老爷机还是新用户来说始终都是一个可靠的、可启动的操作系统。
|
||||
|
||||
为了保证正常运行，Puppy 会在第一次启动之后引导用户完成必要的设置步骤。整个过程涉及很多个窗口，但是一旦完成，你就会对一切功能了如指掌，然后再决定是否需要安装。
|
||||
|
||||
Puppy 有几乎 300 MB 大小，并且在我测试的 1 GB 内存的机器上并不能正常运行，所以它并不是一个特别微型的 Linux 发行版。尽管如此，它仍然是一个非常棒的 1 GB 以下的操作系统，并且在该类系统里算是非常友好的一个。
|
||||
|
||||
#### 安装
|
||||
|
||||
[下载 Puppy Linux][29]，然后通过 **dd** or [Etcher][8] 写入 U盘，或者是刻录到 CD 或者 DVD 里，然后重启。
|
||||
|
||||
![Puppy installer][30]
|
||||
|
||||
Puppy 几乎可以安装在支持任何一种数据格式的载体上。你可以在顶部启动栏里找到 **Puppy Installer** 安装程序，这个程序负责安装 Puppy 以及 Puppy 的应用程序。
|
||||
|
||||
Puppy 安装器会一步步引导你将系统安装在你提供的任何一种媒介上。Puppy 可以从 U盘、光盘、硬盘，或者甚至是 SD 卡上启动。我曾经在一台没有硬盘、光驱出了故障，并且也无法从 USB 启动的计算机上成功运行了 Puppy。由于 Puppy 支持在任何载体上写入你的配置选项，我甚至可以在一个拥有永久数据存储的外部设备上使用它。
|
||||
|
||||
#### 应用程序
|
||||
|
||||
**Puppy 安装器** 这个应用同样被用来在 Puppy 上安装应用。由于 Puppy 是基于 Ubuntu 的，它的软件仓库几乎不会缺少任何一个 Linux 软件包，并且如果真的出现了这种情况的话，你也可以使用 [Flatpak][31]。
|
||||
|
||||
#### 结论
|
||||
|
||||
Puppy 是最早的微型 Linux。尽管它已经不是最微型的了，却是目前最易用的一个。
|
||||
|
||||
### 附赠：Silverblue
|
||||
|
||||
![SilverBlue, not tiny, but tiny-adjacent][32]
|
||||
|
||||
微型 Linux 这个概念是随着时间不断变化的。很久以前，微型 Linux 发行版意味着需要下载到 CD-R 里，从光驱启动，然后将修改写入外部媒介中。后来，你可以从 U盘 启动它，并且有专门用来记录永久修改的空间。现在的微型 Linux 不仅支持上面两种方法，还可以被直接安装在内部驱动或者文件夹里。
|
||||
|
||||
大家都没有想到 Linux 开创了容器的热潮 —— 容器里应用程序是在半虚拟化的环境中运行的一套独立的 Linux 系统。曾经只是属于喜欢优化硬盘空间或者重新利用老爷机的人们的小众爱好，很快成为了那些想要开发容器但又不想在应用程序上添加太多负载的人的强烈需求。那些在极简化的、不起眼的 Linux 发行版上所付出的辛苦，一夜之间以一种意想不到的方式得到了回报。
|
||||
|
||||
立足于根文件系统这个概念，Fedora 项目发起的 [Silverblue][33] 试验旨在创造一个不可修改的操作系统。该操作系统主要通过容器的形式来更新系统以及安装应用，系统本身永远不会改变。
|
||||
|
||||
2.1 GB 的 Silverblue 可不是一个微型 Linux 发行版，但是从某种程度上来说，它是微型 Linux 和容器运动的产物。
|
||||
|
||||
#### 安装
|
||||
|
||||
[下载 Silverblue][34]，然后通过 **dd** or [Etcher][8] 写入 U盘，或者是刻录到 CD 或者 DVD 里，然后重启。
|
||||
|
||||
启动到 Silverblue 之后，使用 [Anaconda][35]（标准的、友好的 Fedora 安装器）将它安装在一个内部硬盘里。
|
||||
|
||||
![Anaconda installer][36]
|
||||
|
||||
#### 应用程序
|
||||
|
||||
Silverblue 安装应用的方式和传统意义上不同：它是在基础操作系统之上运行容器。具体来说，它使用 Flatpaks 运行 GUI 应用程序，使用 [Toolbox][37] 运行命令。
|
||||
|
||||
由于 Flatpaks 并非像传统的 Fedora RPM 软件包一样常见，Silverblue 也提供了一种可以将 Fedora RPM 软件包转换成 Silverblue 形式的方法：**package layering**。
|
||||
|
||||
#### 结论
|
||||
|
||||
Silverblue 可能是一个用来尝试前沿科技的有趣实验，或者也可能是桌面操作系统的未来。它之所以被称为微型，只是因为根文件系统的大小不会随着系统升级或者安装应用而改变。不过，透过 Silverblue 来看看对微型 Linux 的迷恋在带领着 Linux 社区和行业往哪个方向走，也是一件挺有意思的事情。对了，走之前不要忘了向 11 MB 大小的微型 Linux 先驱们脱帽致敬。
|
||||
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://opensource.com/article/19/6/linux-distros-to-try
|
||||
|
||||
作者：[Seth Kenlon][a]
|
||||
选题：[lujun9972][b]
|
||||
译者：[chen-ni](https://github.com/chen-ni)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
||||
[a]: https://opensource.com/users/seth/users/marcobravo
|
||||
[b]: https://github.com/lujun9972
|
||||
[1]: https://opensource.com/sites/default/files/styles/image-full-size/public/lead-images/yearbook-haff-rx-linux-file-lead_0.png?itok=-i0NNfDC (Hand putting a Linux file folder into a drawer)
|
||||
[2]: http://lubuntu.net
|
||||
[3]: http://peppermintos.com
|
||||
[4]: https://www.bodhilinux.com/
|
||||
[5]: https://opensource.com/sites/default/files/uploads/tinycore.jpg (Tiny Core Linux)
|
||||
[6]: http://tinycorelinux.net/
|
||||
[7]: http://tinycorelinux.net/welcome.html
|
||||
[8]: https://www.balena.io/etcher/
|
||||
[9]: https://opensource.com/sites/default/files/uploads/tc-install-gui.png (Tiny Core installer)
|
||||
[10]: https://www.samba.org/
|
||||
[11]: https://opensource.com/sites/default/files/uploads/slitaz.jpg (SliTaz Linux)
|
||||
[12]: http://www.slitaz.org/en/
|
||||
[13]: https://github.com/midori-browser/core
|
||||
[14]: http://slitaz.org/en/get/#rolling
|
||||
[15]: https://opensource.com/sites/default/files/uploads/slitaz-install.jpg (SliTaz installer)
|
||||
[16]: https://opensource.com/sites/default/files/uploads/porteus.jpg (Porteus Linux)
|
||||
[17]: http://www.porteus.org/
|
||||
[18]: http://porteus.org/porteus-mirrors.txt
|
||||
[19]: https://opensource.com/sites/default/files/images/porteus-installer.png (Porteus installer)
|
||||
[20]: http://www.porteus.org/component/content/article/26-tutorials/general-info-tutorials/114-official-porteus-installation-guide.html
|
||||
[21]: http://www.porteus.org/tutorials/9-modules/149-usm.html
|
||||
[22]: https://opensource.com/sites/default/files/uploads/bodhi.jpg (Bodhi Linux)
|
||||
[23]: https://www.enlightenment.org/
|
||||
[24]: https://www.bodhilinux.com/download
|
||||
[25]: https://opensource.com/sites/default/files/uploads/bodhi-install.jpg (Bodhi installer)
|
||||
[26]: https://opensource.com/sites/default/files/uploads/puppy.jpg (Puppy Linux)
|
||||
[27]: https://antixlinux.com/
|
||||
[28]: http://puppylinux.com/
|
||||
[29]: http://puppylinux.com/index.html#download
|
||||
[30]: https://opensource.com/sites/default/files/uploads/puppy-install.jpg (Puppy installer)
|
||||
[31]: https://docs.fedoraproject.org/en-US/fedora-silverblue/getting-started/#flatpak
|
||||
[32]: https://opensource.com/sites/default/files/uploads/silverblue.jpg (SilverBlue, not tiny, but tiny-adjacent)
|
||||
[33]: https://silverblue.fedoraproject.org/
|
||||
[34]: https://silverblue.fedoraproject.org/download
|
||||
[35]: https://fedoraproject.org/wiki/Anaconda
|
||||
[36]: https://opensource.com/sites/default/files/uploads/silverblue-install.jpg (Anaconda installer)
|
||||
[37]: https://docs.fedoraproject.org/en-US/fedora-silverblue/toolbox/
|
||||
Loading…
Reference in New Issue
Block a user