mirror of
https://github.com/LCTT/TranslateProject.git
synced 2025-01-04 22:00:34 +08:00
Merge remote-tracking branch 'LCTT/master'
This commit is contained in:
Xingyu Wang
commit
93a518b082
@ -1,16 +1,18 @@
|
||||
[#]: collector: (lujun9972)
|
||||
[#]: translator: (chen-ni)
|
||||
[#]: reviewer: ( )
|
||||
[#]: publisher: ( )
|
||||
[#]: url: ( )
|
||||
[#]: reviewer: (wxy)
|
||||
[#]: publisher: (wxy)
|
||||
[#]: url: (https://linux.cn/article-11106-1.html)
|
||||
[#]: subject: (The innovation delusion)
|
||||
[#]: via: (https://opensource.com/open-organization/19/6/innovation-delusion)
|
||||
[#]: author: (Jim Whitehurst https://opensource.com/users/jwhitehurst/users/jwhitehurst/users/n8chz/users/dhdeans)
|
||||
|
||||
创新的幻觉
|
||||
======
|
||||
创新是一种混乱的过程，但是关于创新的故事却很有条理。我们不应该把两者搞混了。
|
||||
![gears and lightbulb to represent innovation][1]
|
||||
|
||||
> 创新是一种混乱的过程，但是关于创新的故事却很有条理。我们不应该把两者搞混了。
|
||||
|
||||
|
||||
|
||||
如果说 [传统的规划方法已经消亡了][2]，为什么这么多机构还在孜孜不倦地运用那些针对工业革命所设计的规划方法呢？
|
||||
|
||||
@ -44,11 +46,11 @@
|
||||
|
||||
### 开放（并且混乱的）创新
|
||||
|
||||
机构（特别是领导们）喜欢把成功说成是一件计划之内的事情 - 好像成功人士可以驾驭混乱，并且几乎可以预测未来。但是这些言论都是事后诸葛亮罢了，他们在讲述自己充满偶然性的经历的时候会刻意将无序的事情整理一番，对于毫无确定性的事情也会说“我们就是想要那么做的”。
|
||||
机构（特别是领导们）喜欢把成功说成是一件计划之内的事情 —— 好像成功人士可以驾驭混乱，并且几乎可以预测未来。但是这些言论都是事后诸葛亮罢了，他们在讲述自己充满偶然性的经历的时候会刻意将无序的事情整理一番，对于毫无确定性的事情也会说“我们就是想要那么做的”。
|
||||
|
||||
但是正如我前面说的，我们不应该相信这些故事是创新过程的真实还原，也不应该在这种错误的假设的基础之上去构建未来的方案或者实验。
|
||||
|
||||
试想有另一家摩托车制造商想要复制本田公司在超级幼兽上的成功，就逐字逐句地照搬波士顿咨询总结的故事。由于本田公司成功的 **故事** 听上去是如此有逻辑，并且是线性的，这家新公司也许会假定他们可以通过类似的程序得到同样的结果：制定目标、谋划行动，然后针对可预期的结果进行执行。但是我们知道本田公司并不是真的靠这种“制定、谋划、执行”的方式赢得他们的市场份额的。他们是通过灵活性和一点运气获得成功的 - 更像是“尝试、学习、修改”。
|
||||
试想有另一家摩托车制造商想要复制本田公司在超级幼兽上的成功，就逐字逐句地照搬波士顿咨询总结的故事。由于本田公司成功的 **故事** 听上去是如此有逻辑，并且是线性的，这家新公司也许会假定他们可以通过类似的程序得到同样的结果：制定目标、谋划行动，然后针对可预期的结果进行执行。但是我们知道本田公司并不是真的靠这种“制定、谋划、执行”的方式赢得他们的市场份额的。他们是通过灵活性和一点运气获得成功的 —— 更像是“尝试、学习、修改”。
|
||||
|
||||
当我们可以真正理解并且接受“创新过程是混乱的”这个事实的时候，我们就可以换种方式思考如何让我们的机构实现创新了。与其将资源浪费在预先制定的计划上，**强迫** 创新以一种线性时间线的方式发生，我们不如去构建一些开放并且敏捷的机构，可以 **在创新发生的时候做出及时的响应**。
|
||||
|
||||
@ -69,7 +71,7 @@ via: https://opensource.com/open-organization/19/6/innovation-delusion
|
||||
作者：[Jim Whitehurst][a]
|
||||
选题：[lujun9972][b]
|
||||
译者：[chen-ni](https://github.com/chen-ni)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
校对：[wxy](https://github.com/wxy)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
||||
@ -1,25 +1,26 @@
|
||||
[#]: collector: "lujun9972"
|
||||
[#]: translator: "zianglei"
|
||||
[#]: reviewer: " "
|
||||
[#]: publisher: " "
|
||||
[#]: url: " "
|
||||
[#]: reviewer: "wxy"
|
||||
[#]: publisher: "wxy"
|
||||
[#]: url: "https://linux.cn/article-11108-1.html"
|
||||
[#]: subject: "Make an RGB cube with Python and Scribus"
|
||||
[#]: via: "https://opensource.com/article/19/7/rgb-cube-python-scribus"
|
||||
[#]: author: "Greg Pittman https://opensource.com/users/greg-p/users/greg-p"
|
||||
|
||||
使用 Python 和 Scribus 创建一个 RGB 立方体
|
||||
======
|
||||
使用 Scribus 的 Python 脚本功能，开发一个显示 RGB 色谱的 3D 立方体。
|
||||
|
||||
> 使用 Scribus 的 Python 脚本编写器功能，开发一个显示 RGB 色谱的 3D 立方体。
|
||||
|
||||
![cubes coming together to create a larger cube][1]
|
||||
|
||||
当我决定这个夏天要玩色彩游戏时，我想到通常色彩都是在色轮上描绘的。这些色彩通常都是使用色素而不是光，并且你失去了任何对颜色亮度或光度变化的感觉。
|
||||
|
||||
作为色轮的替代，我想在立方体表面使用一系列图形来显示 RGB 频谱。色彩的 RGB 值将在具有 X-、Y-、Z- 轴的三位图形上展示。例如，一个平面将会保持 B（或蓝色）为 0，其余的坐标轴将显示当我将 R（红色）和 G （绿色）的值从 0 绘制到 255 时发生的情况。
|
||||
作为色轮的替代，我想在立方体表面使用一系列图形来显示 RGB 频谱。色彩的 RGB 值将在具有 X、Y、Z 轴的三维图形上展示。例如，一个平面将会保持 B（蓝色）为 0，其余的坐标轴将显示当我将 R（红色）和 G （绿色）的值从 0 绘制到 255 时发生的情况。
|
||||
|
||||
事实证明，使用 [Scribus][2] 及其 [Python 脚本编写器][3] 功能实现这一点并不困难。我可以创建 RGB 颜色，使矩形显示颜色，并以 2D 格式排列它们。我决定设置颜色值的间隔为 5，并让矩形一边测量 5 个点。因此，对于每个 2D 图形，我将使用大约 250 种颜色，立方体一边测量 250 个点，也就是 3.5 英寸。
|
||||
|
||||
我使用下面这段 Python 代码完成了绿 - 红图的任务
|
||||
事实证明，使用 [Scribus][2] 及其 [Python 脚本编写器][3] 功能实现这一点并不困难。我可以创建 RGB 颜色，使矩形显示颜色，并以 2D 格式排列它们。我决定设置颜色值的间隔为 5，并让矩形按 5 个点（pt）进行绘图。因此，对于每个 2D 图形，我将使用大约 250 种颜色，立方体的一个边有 250 个点（pt），也就是 3.5 英寸。
|
||||
|
||||
我使用下面这段 Python 代码完成了绿 - 红图的任务：
|
||||
|
||||
```python
|
||||
x = 300
|
||||
@ -44,11 +45,11 @@ if scribus.newDoc(scribus.PAPER_LETTER, (0,0,0,0),scribus.PORTRAIT, 1,
|
||||
y = y – 5
|
||||
```
|
||||
|
||||
这个脚本在 **300,300** 位置开始绘制图形，这个位置大约是一个美国信件大小的纸张的水平中心，大概是垂直方向从顶部到底的三分之一位置；这是图像的原点，然后它沿着 X 轴（绿色值）水平构建图形，然后返回到 Y 轴，向上走 5 个点，然后绘制下一条矩形线。
|
||||
这个脚本在 `300,300` 位置开始绘制图形，这个位置大约是一个美国信件大小的纸张的水平中心，大概是垂直方向从顶部到底的三分之一位置；这是图像的原点，然后它沿着 X 轴（绿色值）水平构建图形，然后返回到 Y 轴，向上移动 5 个点，然后绘制下一条矩形线。
|
||||
|
||||
![Red-Green graph][4]
|
||||
|
||||
这看起来很简单；我只需要调整一下数字就可以把立方体的另一边画出来。但这不仅仅是再画两个图，一个是蓝 - 绿色，另一个是红 - 蓝色的问题。我想创建一个展开的立方体，这样我就可以打印、剪开然后折叠它，创建一个 RGB 的 3D 视图。因此，下一部分（向下的页面）的原点（黑色的角落）需要在左上角，其水平方向是绿色，垂直方向是蓝色。
|
||||
这看起来很简单；我只需要调整一下数字就可以把立方体的另一面画出来。但这不仅仅是再画两个图，一个是蓝 - 绿色，另一个是红 - 蓝色的问题。我想创建一个展开的立方体，这样我就可以打印、剪开然后折叠它，创建一个 RGB 的 3D 视图。因此，下一部分（向下的页面）的原点（黑色的角落）需要在左上角，其水平方向是绿色，垂直方向是蓝色。
|
||||
|
||||
“调整数字”最终或多或少变成了试错，从而得到我想要的东西。在创建了第二个图之后，我需要第三个图，它是红 - 蓝色的，原点位于左上角，红色向左递增，蓝色向下递增。
|
||||
|
||||
@ -62,7 +63,7 @@ if scribus.newDoc(scribus.PAPER_LETTER, (0,0,0,0),scribus.PORTRAIT, 1,
|
||||
|
||||
![Second half of RGB cube][6]
|
||||
|
||||
现在，是时候轮到打印机了！在这里，你可以直观了解彩色打印机如何处理 RGB 颜色到 CMYK 颜色的转换以及打印颜色密集空间。
|
||||
现在，是时候轮到打印机了！在这里，你可以直观了解彩色打印机如何处理 RGB 颜色到 CMYK 颜色的转换以及打印颜色密集空间。
|
||||
|
||||
接下来，朋友们，是剪切粘贴时间！我可以用胶带，但我不想改变表面的外观，所以我在切割的时候在两边留下了一些空间，这样我就可以把它们粘在里面了。根据我的经验，在复印纸上打印会产生一些不需要的皱纹，所以在我的复印纸原型完成后，我把立方体打印在了更厚的纸上，表面是哑光的。
|
||||
|
||||
@ -74,8 +75,7 @@ if scribus.newDoc(scribus.PAPER_LETTER, (0,0,0,0),scribus.PORTRAIT, 1,
|
||||
|
||||
最后，我做这个项目很开心。如果您也想参与其中，这里有两个脚本。
|
||||
|
||||
这是前半部分 :
|
||||
|
||||
这是前半部分：
|
||||
|
||||
```python
|
||||
#!/usr/bin/env python
|
||||
@ -235,7 +235,7 @@ via: https://opensource.com/article/19/7/rgb-cube-python-scribus
|
||||
作者：[Greg Pittman][a]
|
||||
选题：[lujun9972][b]
|
||||
译者：[zianglei](https://github.com/zianglei)
|
||||
校对：[校对者 ID](https://github.com/ 校对者 ID)
|
||||
校对：[wxy](https://github.com/wxy)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux 中国](https://linux.cn/) 荣誉推出
|
||||
|
||||
@ -1,3 +1,5 @@
|
||||
bestony is translating.
|
||||
|
||||
Create a Clean-Code App with Kotlin Coroutines and Android Architecture Components
|
||||
============================================================
|
||||
|
||||
|
||||
@ -1,3 +1,4 @@
|
||||
ZhiW5217 is translating
|
||||
Top 10 Microsoft Visio Alternatives for Linux
|
||||
======
|
||||
**Brief: If you are looking for a good Visio viewer in Linux, here are some alternatives to Microsoft Visio that you can use in Linux.**
|
||||
|
||||
@ -1,3 +1,5 @@
|
||||
translating by zyk2290
|
||||
|
||||
Two great uses for the cp command: Bash shortcuts
|
||||
============================================================
|
||||
|
||||
|
||||
@ -1,149 +0,0 @@
|
||||
translating by qfzy1233
|
||||
|
||||
MX Linux: A Mid-Weight Distro Focused on Simplicity
|
||||
======
|
||||
|
||||
|
||||
There are so many distributions of Linux. Some of those distributions go a very long way to differentiate themselves. In other cases, the differences are so minimal, you wonder why anyone would have bothered reinventing that particular wheel. It’s that latter concern that had me wondering why [antiX][1] and [MEPIS][2] communities would come together to create yet another distribution—especially given that the results would be an Xfce edition of antiX, built by the MEPIS community.
|
||||
|
||||
Does building antiX with an Xfce desktop warrant its own distribution? After all, antiX claims to be a “fast, lightweight and easy to install systemd-free linux live CD distribution based on Debian Stable.” The antiX desktop of choice is [LXDE][3], which does certainly fit the bill for a lightweight desktop. So why retool antiX into another lightweight distribution, only this time with Xfce? Well, as anyone within the Linux community knows, variance adds flavor and a good lightweight distribution is a worthwhile endeavor (especially in preventing old hardware from making its way to the landfill). Of course, LXDE and Xfce aren’t quite in the same category. LXDE should be considered a true lightweight desktop, whereas Xfce should be considered more a mid-weight desktop. And that, my friends, is key to why MX Linux is an important iteration of antiX. A mid-weight distribution, built on Debian, that includes all the tools you need to get your work done.
|
||||
|
||||
But there’s something really keen within MX Linux—something directly borrowed from antiX—and that is the installation tool. When I first set up a VirtualBox VM to install MX Linux, I assumed the installation would be the typical, incredibly easy Linux installation I’d grown accustomed to. Much to my surprise, that antiX installer MX Linux uses could be a real game changer, especially for those on the fence about giving Linux a try.
|
||||
|
||||
So even before I began kicking the tires of MX Linux, I was impressed. Let’s take a look at what makes the installation of this distribution so special, and then finally have a go with the desktop.
|
||||
|
||||
You can download MX Linux 17.1 from [here][4]. The minimum system requirements are:
|
||||
|
||||
* A CD/DVD drive (and BIOS capable of booting from that drive), or a live USB (and BIOS capable of booting from USB)
|
||||
|
||||
* A modern i486 Intel or AMD processor
|
||||
|
||||
* 512 MB of RAM memory
|
||||
|
||||
* 5 GB free hard drive space
|
||||
|
||||
* A SoundBlaster, AC97 or HDA-compatible sound card
|
||||
|
||||
* For use as a LiveUSB, 4 GB free
|
||||
|
||||
|
||||
|
||||
|
||||
### Installation
|
||||
|
||||
Out of the gate, the MX Linux installer makes installing Linux a breeze. Although it may not be the most modern-looking installation tool, there’s little to second-guess. The heart of the installation begins with choosing the disks and selecting the installation type (Figure 1).
|
||||
|
||||
|
||||
![install][6]
|
||||
|
||||
Figure 1: One of the first installer screens for MX Linux.
|
||||
|
||||
[Used with permission][7]
|
||||
|
||||
The next important screen (Figure 2) requires you to set a computer name, domain, and (if necessary) a workgroup for MS Networking.
|
||||
|
||||
That ability to configure a workgroup is the first bit to really stand out. This is the first distribution I can remember that offers this option during installation. It also should clue you in that MX Linux offers the ability to share directories out of the box. It does, and it does so with aplomb. It’s not perfect, but it works without having to install any extra package (more on this in a bit).
|
||||
|
||||
The last important installation screen (that requires user-interaction) is the creation of the user account and root password (Figure 3).
|
||||
|
||||
|
||||
![user][9]
|
||||
|
||||
Figure 3: Setting up your user account details and the root user password.
|
||||
|
||||
[Used with permission][7]
|
||||
|
||||
Once you’ve taken care of this final screen, the installation will complete and ask you to reboot. Upon rebooting, you’ll be greeted with the login screen. Login and enjoy the MX Linux experience.
|
||||
|
||||
### Usage
|
||||
|
||||
The Xfce desktop is quite an easy interface to get up to speed with. The default places the panel on the left edge of the screen (Figure 4).
|
||||
|
||||
|
||||
![desktop ][11]
|
||||
|
||||
Figure 4: The default MX Linux desktop.
|
||||
|
||||
[Used with permission][7]
|
||||
|
||||
If you want to move the panel to a more traditional location, right click a blank spot on the panel and click Panel > Panel Preferences. In the resulting window (Figure 5), click the Mode drop-down to select from between Deskbar, Vertical, or Horizontal.
|
||||
|
||||
|
||||
![panel][13]
|
||||
|
||||
Figure 5: Configuring the MX Linux Panel.
|
||||
|
||||
[Used with permission][7]
|
||||
|
||||
The difference between the Deskbar and Vertical options is that, in the Deskbar mode, the panel is aligned vertically, just like in the vertical mode, but the plugins are laid out horizontally. This means you can create much wider panels (for widescreen layouts). If you opt for a horizontal layout, it will default to the top—you will have to then uncheck the Lock panel check box, click Close, and then (using the drag handle on the left edge of the panel) drag it to the bottom. You can then go back into the Panel Settings window and re-lock the panel.
|
||||
|
||||
Beyond that, using the Xfce desktop should be a no-brainer for nearly any experience level … it’s that easy. You’ll find software to cover productivity (LibreOffice, Orage Calendar, PDF-Shuffler), graphics (GIMP), communication (Firefox, Thunderbird, HexChat), multimedia (Clementine, guvcview, SMTube, VLC media player), and a number of tools specific to MX Linux (called MX Tools, that range from a live-USB drive creator, a network assistant, package installer, repo manager, live ISO snapshot creator, and more).
|
||||
|
||||
![sharing][15]
|
||||
|
||||
Figure 6: Sharing out a directory to your network.
|
||||
|
||||
[Used with permission][7]
|
||||
|
||||
### Samba
|
||||
|
||||
Let’s talk about sharing folders to your network. As I mentioned, you won’t have to install any extra packages to get this to function. You simply open up the file manager, right-click anywhere, and select Share a folder on your network. You will be prompted for the administrative password (set during installation). Upon successful authentication, the Samba Server Configuration Tool will open (Figure 6).
|
||||
|
||||
![sharing][17]
|
||||
|
||||
Figure 7: Configuring the share on MX Linux.
|
||||
|
||||
[Used with permission][7]
|
||||
|
||||
Click the + button and configure your share. You will be asked to locate the directory, give the share a name/description, and then decide if the share is writeable and visible (Figure 7).
|
||||
|
||||
When you click the Access tab, you have the choice between giving everyone access to the share or just specific users. Here’s where the problem arises. At this point, no users will be available for sharing. Why? They haven’t been added. In order to add them, there are two possibilities: From the command line or using the tool we already have open. Let’s take the obvious route. From the main window of the Samba Server Configuration Tool, click Preferences > Samba Users. In the resulting window, click Add user.
|
||||
|
||||
A new window will appear (Figure 8), where you need to select the user from the drop-down, enter a Windows username, and type/retype a password for the user.
|
||||
|
||||
![Samba][19]
|
||||
|
||||
Figure 8: Adding a user to Samba.
|
||||
|
||||
[Used with permission][7]
|
||||
|
||||
Once you’ve clicked OK, the user will be added and the share will be accessible, to that user, across your network. Creating Samba shares really can be that easy.
|
||||
|
||||
### The conclusion
|
||||
|
||||
MX Linux makes transitioning from just about any desktop operating system simple. Although some might find the desktop interface to be a bit less-than-modern, the distribution’s primary focus isn’t on beauty, but simplicity. To that end, MX Linux succeeds in stellar fashion. This flavor of Linux can make anyone feel right at home on Linux. Spin up this mid-weight distribution and see if it can’t serve as your daily driver.
|
||||
|
||||
Learn more about Linux through the free ["Introduction to Linux" ][20]course from The Linux Foundation and edX.
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://www.linux.com/learn/intro-to-linux/2018/4/mx-linux-mid-weight-distro-focused-simplicity
|
||||
|
||||
作者：[JACK WALLEN][a]
|
||||
译者：[译者ID](https://github.com/译者ID)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
选题：[lujun9972](https://github.com/lujun9972)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
||||
[a]:https://www.linux.com/users/jlwallen
|
||||
[1]:https://antixlinux.com/
|
||||
[2]:https://en.wikipedia.org/wiki/MEPIS
|
||||
[3]:https://lxde.org/
|
||||
[4]:https://mxlinux.org/download-links
|
||||
[5]:/files/images/mxlinux1jpg
|
||||
[6]:https://www.linux.com/sites/lcom/files/styles/rendered_file/public/mxlinux_1.jpg?itok=i9bNScjH (install)
|
||||
[7]:/licenses/category/used-permission
|
||||
[8]:/files/images/mxlinux3jpg
|
||||
[9]:https://www.linux.com/sites/lcom/files/styles/rendered_file/public/mxlinux_3.jpg?itok=ppf2l_bm (user)
|
||||
[10]:/files/images/mxlinux4jpg
|
||||
[11]:https://www.linux.com/sites/lcom/files/styles/rendered_file/public/mxlinux_4.jpg?itok=mS1eBy9m (desktop)
|
||||
[12]:/files/images/mxlinux5jpg
|
||||
[13]:https://www.linux.com/sites/lcom/files/styles/floated_images/public/mxlinux_5.jpg?itok=wsN1hviN (panel)
|
||||
[14]:/files/images/mxlinux6jpg
|
||||
[15]:https://www.linux.com/sites/lcom/files/styles/floated_images/public/mxlinux_6.jpg?itok=vw8mIp9T (sharing)
|
||||
[16]:/files/images/mxlinux7jpg
|
||||
[17]:https://www.linux.com/sites/lcom/files/styles/floated_images/public/mxlinux_7.jpg?itok=tRIWdcEk (sharing)
|
||||
[18]:/files/images/mxlinux8jpg
|
||||
[19]:https://www.linux.com/sites/lcom/files/styles/floated_images/public/mxlinux_8.jpg?itok=ZS6lhZN2 (Samba)
|
||||
[20]:https://training.linuxfoundation.org/linux-courses/system-administration-training/introduction-to-linux
|
||||
@ -1,5 +1,5 @@
|
||||
[#]: collector: (lujun9972)
|
||||
[#]: translator: ( )
|
||||
[#]: translator: (qfzy1233 )
|
||||
[#]: reviewer: ( )
|
||||
[#]: publisher: ( )
|
||||
[#]: url: ( )
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
[#]: collector: (lujun9972)
|
||||
[#]: translator: ( )
|
||||
[#]: translator: (Flowsnow)
|
||||
[#]: reviewer: ( )
|
||||
[#]: publisher: ( )
|
||||
[#]: url: ( )
|
||||
|
||||
@ -1,61 +0,0 @@
|
||||
[#]: collector: (lujun9972)
|
||||
[#]: translator: ( )
|
||||
[#]: reviewer: ( )
|
||||
[#]: publisher: ( )
|
||||
[#]: url: ( )
|
||||
[#]: subject: (Sysadmin vs SRE: What's the difference?)
|
||||
[#]: via: (https://opensource.com/article/19/7/sysadmins-vs-sres)
|
||||
[#]: author: (Vince Power https://opensource.com/users/vincepower/users/craig5/users/dawnparzych/users/penglish)
|
||||
|
||||
Sysadmin vs SRE: What's the difference?
|
||||
======
|
||||
Both sysadmins and site reliability engineers are valuable parts of any
|
||||
organization. Here's a look at each role differs.
|
||||
![People work on a computer server with devices][1]
|
||||
|
||||
In the IT world, there has always been a pull between generalist and specialist. The stereotypical sysadmin falls in the generalist category 99 times out of 100. The [site reliability engineer (SRE)][2] role is specialized, however, and grew out of the needs of one of the first companies to know real scale: Google. Ultimately, these two roles have the same goal for the applications whose infrastructure they operate: providing a good experience for the applications’ consumers. Yet, these roles have drastically different starting points.
|
||||
|
||||
### Sysadmins: Neutral good incarnate
|
||||
|
||||
Sysadmins typically grow into their position by starting as entry-level desktop and network support, and then over time acquiring the broad set of skills most sysadmins have in common. By that point, these sysadmins know all of the systems and applications they are responsible for. They know the app on server one needs to be restarted every other Tuesday, or the service on server nine will crash on Wednesday with no errors. They have fine-tuned their monitoring so it ignores what doesn’t matter, even that error that happens on the third Sunday of the month, despite the fact that it’s marked as fatal.
|
||||
|
||||
In short, sysadmins know how to feed and care for the servers that run the core of your business. These sysadmins have grown to use automation to handle routine tasks across all the servers they manage. They love templates, golden images, and standards, but are flexible enough to make a parameter change on just the one server that has an error, and then make a note regarding why that server is now uniquely configured.
|
||||
|
||||
Sysadmins are great, but they have a couple of quirks. The first being that you just do not get root access without divine intervention, and that any changes they make which were not their idea have to be documented as required by the application they are working with’s vendor, and then will still be double-checked.
|
||||
|
||||
The servers are their domain, and no one messes with their stuff.
|
||||
|
||||
### SREs: Thanos would be proud
|
||||
|
||||
As opposed to the path to becoming a sysadmin, SREs are as likely to come from a development background as a sysadmin background. The SRE position is closer to the lifecycle you find in an application development environment.
|
||||
|
||||
As an organization grows and introduces [DevOps][3] concepts like [continuous integration][4] and [continuous delivery][5] (CI/CD), there will often be a skills gap on how to run those immutable applications across multiple environments while having them scale to meet the business’s needs. This is the world of an SRE. Yes, a sysadmin can learn the additional tools, but at scale, this easily becomes a full-time position to keep up. A specialist makes sense.
|
||||
|
||||
SREs use concepts like [infrastructure-as-code][6] to produce templates, which are called to deploy the environment an application will run in, with the goal of every application and its environment being completely reproducible with the push of a button. So, app one on server one in system testing will have the exact same binaries that will be used on server fifteen in production, with the exception of environment-specific variables like passwords and database connection strings.
|
||||
|
||||
An SRE will also completely destroy an environment and rebuild it based on a configuration change. There is no emotional attachment to any system. Each system is just a number and is tagged and lifecycled accordingly, even to the point that routine server patching is done by redeploying the entire application stack.
|
||||
|
||||
### Conclusion
|
||||
|
||||
In certain situations, especially when operating in large DevOps-based environments, the specialized skills an SRE provides regarding how to handle any level of scale definitely offer an advantage. And every time they get stuck, they will seek out the help of their friendly neighborhood sysadmin—or [(BOFH)][7] on a bad day—for those well-honed troubleshooting skills, and the breadth of experiences which sysadmins rely on to provide value to any organization they are a part of.
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://opensource.com/article/19/7/sysadmins-vs-sres
|
||||
|
||||
作者：[Vince Power][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/vincepower/users/craig5/users/dawnparzych/users/penglish
|
||||
[b]: https://github.com/lujun9972
|
||||
[1]: https://opensource.com/sites/default/files/styles/image-full-size/public/lead-images/rh_003499_01_linux11x_cc.png?itok=XMDOouJR (People work on a computer server with devices)
|
||||
[2]: https://en.wikipedia.org/wiki/Site_Reliability_Engineering
|
||||
[3]: https://opensource.com/resources/devops
|
||||
[4]: https://en.wikipedia.org/wiki/Continuous_integration
|
||||
[5]: https://en.wikipedia.org/wiki/Continuous_delivery
|
||||
[6]: https://en.wikipedia.org/wiki/Infrastructure_as_code
|
||||
[7]: http://www.bofharchive.com/BOFH.html
|
||||
@ -1,5 +1,5 @@
|
||||
[#]: collector: (lujun9972)
|
||||
[#]: translator: ( )
|
||||
[#]: translator: (martin2011qi)
|
||||
[#]: reviewer: ( )
|
||||
[#]: publisher: ( )
|
||||
[#]: url: ( )
|
||||
|
||||
@ -0,0 +1,139 @@
|
||||
MX Linux: 一款专注于简洁性的发行版
|
||||
======
|
||||
|
||||
|
||||
Linux 有着如此多种的发型版。许多发行版为了使自己与众不同而做出了很多改变。另一方面，许多发行版之间的区别又是如此之小，你可能会问为什么有人还愿意不厌其烦的重复别人已经做过的工作呢？也正是基于这一疑惑，让我好奇为什么 [antiX][1] 和 [MEPIS][2]这两个社区要联合推出一个特殊的发行版，考虑到具体情况应该会是一个搭载 Xfce 桌面并基于 antiX 的版本，由 MEPIS 社区承担开发。
|
||||
|
||||
这一开发中的使用 Xfce 桌面的 antiX 系统是否会基于他之前的发行版呢？毕竟，antiX 旨在提供一个“快速、轻量级、易于安装的、支持linux live CD 且基于Debian Stable的发行版”。antiX 所搭载的桌面是 [LXDE][3]，能够极好的满足关于轻量化系统的相关要求和特性。那究竟是什么原因使得 antiX 决定构建另一个轻量化发行版呢，仅仅是因为这次换成了 Xfce 吗？好吧，Linux 社区中的任何人都知道，差异之处体现了不同版本的特性，一个好的轻量级发行版是值得一试的(特别是可以使得我们的旧硬件摆脱进入垃圾填埋场的宿命)。当然，LXDE 和 Xfce 并不完全属于同一类别。LXDE应该被认为是一个真正的轻量级桌面，而 Xfce 应该被认为是一个中等重量的桌面。朋友们，这就是为什么 MX Linux 是 antiX 的一个重要迭代的关键。一个基于Debian的中等体量的发行版，它包含你完成工作所需的所有工具。
|
||||
|
||||
但是在 MX linux 中有一些直接从 antiX 借用来的非常有用的东西—那就是安装工具。当我第一次设置VirtualBox 的虚拟机来安装 MX Linux 时，我认为安装将是我已经习惯的典型的、非常简单的Linux安装。令我非常惊讶的是，MX Linux 使用的 antiX 安装程序打破了以往的痛点，特别是对于那些对尝试 Linux 持观望态度的人来说。
|
||||
|
||||
因此，甚至在我开始尝试 MX Linux 之前，我就对它有了深刻的印象。让我们来看看是什么让这个发行版的安装如此特别，最后再来看看桌面。
|
||||
|
||||
你可以从[这里][4]下载 MX Linux 17.1。系统的最低要求是:
|
||||
|
||||
* CD/DVD驱动器(以及能够从该驱动器引导的BIOS)或活动USB(以及能够从USB引导的BIOS)
|
||||
|
||||
* 英特尔 i486 或 AMD 处理器
|
||||
|
||||
* 512 MB 内存
|
||||
|
||||
* 5 GB 硬盘空间
|
||||
|
||||
* 扬声器，AC97 或 HDA-compatible 声卡
|
||||
|
||||
* 作为一个 LiveUSB 使用，需要 4 GB 空间
|
||||
|
||||
### 安装
|
||||
|
||||
MX Linux安装程序使安装 Linux 变得轻而易举。虽然它可能不是外观最现代化的安装工具，但也已经差不多了。安装的要点是从选择磁盘和选择安装类型开始的(图1)。
|
||||
|
||||
![install][6]
|
||||
|
||||
图1:MX Linux 的安装程序截图之一。
|
||||
|
||||
[Used with permission][7]
|
||||
|
||||
下一个重要的界面(图2)要求你为MS网络设置一个计算机名称、域名和(如果需要的话)工作组。
|
||||
|
||||
配置工作组的能力是真正值得称赞的第一项。这是我记忆中第一款在安装期间提供此选项的发行版。它还应该提示你，MX Linux 提供了开箱即用共享目录的功能。它做到了，而且深藏功与名。它并不完美，但它可以在不需要安装任何额外包的情况下工作(稍后将详细介绍)。
|
||||
|
||||
最后一个重要的安装界面(需要用户交互)是创建用户帐户和 root 权限的密码(图3)。
|
||||
|
||||
![user][9]
|
||||
|
||||
图3:设置用户帐户详细信息和 root 用户密码。
|
||||
|
||||
[Used with permission][7]
|
||||
|
||||
最后一个界面设置完成后，安装将完成并要求重新启动。重启后，你将看到登录屏幕。登录并享受MX Linux 带来的体验。
|
||||
|
||||
### 使用
|
||||
|
||||
Xfce桌面是一个非常容易上手的界面。默认设置将面板位于屏幕的左边缘(图4)。
|
||||
|
||||
![desktop ][11]
|
||||
|
||||
图4: MX Linux 的默认桌面。
|
||||
|
||||
[Used with permission][7]
|
||||
|
||||
如果你想将面板移动到更传统的位置，右键单击面板上的空白点，然后单击面板>面板首选项。在生成的窗口中(图5)，单击样式下拉菜单，在桌面栏、垂直栏或水平栏之间进行选择你想要的模式。
|
||||
|
||||
![panel][13]
|
||||
|
||||
图5:配置 MX Linux 面板。
|
||||
|
||||
[Used with permission][7]
|
||||
|
||||
桌面栏和垂直选项的区别在于，在桌面栏模式下，面板垂直对齐，就像在垂直模式下一样，但是插件是水平放置的。这意味着你可以创建更宽的面板(用于宽屏布局)。如果选择水平布局，它将默在顶部，然后你必须取消锁定面板，单击关闭，然后(使用面板左侧边缘的拖动手柄)将其拖动到底部。你可以回到面板设置窗口并重新锁定面板。
|
||||
|
||||
除此之外，使用 Xfce 桌面对于任何级别的用户来说都是无需动脑筋的事情……就是这么简单。你会发现很多生产力代表的软件(LibreOffice, Orage日历,PDF-Shuffler)、图像软件(GIMP)、通信(Firefox,Thunderbird,HexChat),多媒体(Clementine、guvcview SMTube, VLC媒体播放器),和一些 MX Linux 专属的工具(称为MX工具,涵盖了 live-USB 驱动器制作工具,包管理工具,repo 管理工具,回购经理,live ISO 快照工具,等等)。
|
||||
|
||||
![sharing][15]
|
||||
|
||||
图6:向网络共享一个目录。
|
||||
[Used with permission][7]
|
||||
|
||||
### Samba
|
||||
|
||||
让我们讨论一下如何将文件夹共享到你的网络。正如我所提到的，你不需要安装任何额外的包就可以使其正常工作。只需打开文件管理器，右键单击任何位置，并选择网络上的共享文件夹。系统将提示你输入管理密码(已在安装期间设置)。验证成功之后，Samba服务器配置工具将打开(图6)。
|
||||
|
||||
![sharing][17]
|
||||
|
||||
图7：在MX Linux上配置共享。
|
||||
|
||||
[Used with permission][7]
|
||||
|
||||
单击+按钮并配置你的共享。你将被要求指定一个目录，为共享提供一个名称/描述，然后决定该共享是否可写且可见(图7)。
|
||||
|
||||
当你单击 Access 选项时，你可以选择是让每个人都访问共享，还是限于特定的用户。问题就出在这里。此时，没有用户可以共享。为什么？因为它们还没有被添加。，有两种方法可以把它们添加到共享:从命令行或使用我们已经打开的工具。让我们用一种更为简单的方法。在Samba服务器配置工具的主窗口中，单击Preferences > Samba Users。在弹出的窗口中，单击 Add user。
|
||||
|
||||
将出现一个新窗口(图8)，你需要从下拉框中选择用户，输入Windows用户名，并为用户键入/重新键入密码。
|
||||
|
||||
![Samba][19]
|
||||
|
||||
图8:向 Samba 添加用户。
|
||||
|
||||
[Used with permission][7]
|
||||
|
||||
一旦你单击确定，用户将被添加，并且基于你的网络的对用户的共享功能也随之启用。创建 Samba 共享从未变得如此容易。
|
||||
|
||||
### 结论
|
||||
|
||||
MX Linux 使任何从桌面操作系统转到 Linux 都变得非常简单。尽管有些人可能会觉得桌面界面不太现代，但发行版的主要关注点不是美观，而是简洁。为此，MX Linux 以出色的方式取得了成功。Linux 的这种特性可以让任何人在使用 Linux 的过程中感到宾至如归。尝试这一中等体量的发行版，看看它能否作为你的日常系统。
|
||||
|
||||
从Linux 基金会和 edX 的[“Linux入门”][20]课程了解更多关于Linux的知识。
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://www.linux.com/learn/intro-to-linux/2018/4/mx-linux-mid-weight-distro-focused-simplicity
|
||||
|
||||
作者：[JACK WALLEN][a]
|
||||
译者：[qfzy1233](https://github.com/qfzy1233)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
选题：[lujun9972](https://github.com/lujun9972)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
||||
[a]:https://www.linux.com/users/jlwallen
|
||||
[1]:https://antixlinux.com/
|
||||
[2]:https://en.wikipedia.org/wiki/MEPIS
|
||||
[3]:https://lxde.org/
|
||||
[4]:https://mxlinux.org/download-links
|
||||
[5]:/files/images/mxlinux1jpg
|
||||
[6]:https://www.linux.com/sites/lcom/files/styles/rendered_file/public/mxlinux_1.jpg?itok=i9bNScjH (install)
|
||||
[7]:/licenses/category/used-permission
|
||||
[8]:/files/images/mxlinux3jpg
|
||||
[9]:https://www.linux.com/sites/lcom/files/styles/rendered_file/public/mxlinux_3.jpg?itok=ppf2l_bm (user)
|
||||
[10]:/files/images/mxlinux4jpg
|
||||
[11]:https://www.linux.com/sites/lcom/files/styles/rendered_file/public/mxlinux_4.jpg?itok=mS1eBy9m (desktop)
|
||||
[12]:/files/images/mxlinux5jpg
|
||||
[13]:https://www.linux.com/sites/lcom/files/styles/floated_images/public/mxlinux_5.jpg?itok=wsN1hviN (panel)
|
||||
[14]:/files/images/mxlinux6jpg
|
||||
[15]:https://www.linux.com/sites/lcom/files/styles/floated_images/public/mxlinux_6.jpg?itok=vw8mIp9T (sharing)
|
||||
[16]:/files/images/mxlinux7jpg
|
||||
[17]:https://www.linux.com/sites/lcom/files/styles/floated_images/public/mxlinux_7.jpg?itok=tRIWdcEk (sharing)
|
||||
[18]:/files/images/mxlinux8jpg
|
||||
[19]:https://www.linux.com/sites/lcom/files/styles/floated_images/public/mxlinux_8.jpg?itok=ZS6lhZN2 (Samba)
|
||||
[20]:https://training.linuxfoundation.org/linux-courses/system-administration-training/introduction-to-linux
|
||||
@ -0,0 +1,60 @@
|
||||
[#]: collector: (lujun9972)
|
||||
[#]: translator: (vizv)
|
||||
[#]: reviewer: ( )
|
||||
[#]: publisher: ( )
|
||||
[#]: url: ( )
|
||||
[#]: subject: (Sysadmin vs SRE: What's the difference?)
|
||||
[#]: via: (https://opensource.com/article/19/7/sysadmins-vs-sres)
|
||||
[#]: author: (Vince Power https://opensource.com/users/vincepower/users/craig5/users/dawnparzych/users/penglish)
|
||||
|
||||
系统管理员与网站可靠性工程师对比：区别在那儿？
|
||||
======
|
||||
系统管理员和网站可靠性工程师（SRE，下同）对于任何组织来讲都很重要。本篇将介绍下两者的不同之处。
|
||||
![People work on a computer server with devices][1]
|
||||
|
||||
在 IT 行业，成为多面手或是专家的争议一直存在。99% 的传统系统管理员都被归到了多面手这类。[网站可靠性工程师][2]的角色则更加专精，并且其需求在如 Google 般有着一定规模的公司中不断增加。但总的来说这两者对于跑着应用的基础设施有着同样的目标：为应用的消费者提供良好的体验。然而两者的出发点却截然不同。
|
||||
|
||||
### 系统管理员：中立善良的化身
|
||||
|
||||
系统管理员一般都是从基础的桌面或网络支持成长过来的，并一路习得大多数系统管理员都会掌握的广泛的技能。此时这些系统管理员会对他们所负责的系统和应用了如指掌。他们会知道一号服务器上的应用每隔一个星期二就需要重启一次，或是九号服务器周三会静默的崩溃。他们会对服务器的监视作出微调以忽略无关紧要的信息，尽管那是个每月第三个周日都会显示的被标记为<ruby>致命<rt>fatal<rt></ruby>的错误信息。
|
||||
|
||||
总的来讲，系统管理员了解如何照料那些跑着你核心业务的服务器。这些系统管理员已经成长到开始使用自动化工具去处理所有归他们管的服务器上的例行任务。他们虽然喜欢使用模板、<ruby>黄金镜像<rt>golden images</rt></ruby>、以及标准，但同时也有着足够的灵活度去修改一个服务器上的参数以解决错误，并注释为什么那个服务器的配置与众不同。
|
||||
|
||||
尽管系统管理员很伟大，但他们也有着一些怪癖。其中一项就是没有他们神圣的授权你永远也获取不了系统的 root 访问权限，另一项则是任何不是他们的主意都在文档被记录为应用的提供者的要求，并仍然需要再次核对。
|
||||
|
||||
他们所管理的服务器是他们的地盘，没有人可以随意干涉。
|
||||
|
||||
### SRE：灭霸将为之自豪
|
||||
|
||||
与成为系统管理员的道路相反，从开发背景和从系统管理员背景成长为 SRE 的可能性相近。SRE 的职位出现的时长与应用开发环境的生命周期相近。
|
||||
|
||||
随着一个组织的发展而引入的类似于[持续集成][4]和[持续发布][5] (CI/CD) 的 [DevOps][3] 概念，通常会带来如何让这些<ruby>不可变<rt>immutable</rt></ruby>的应用部署到多个环境并随着业务需求进行扩展的技能空缺。着将是 SRE 的舞台。的确，一个系统管理员可以学习额外的工具，但大体上成为一个全职的职位更容易跟的上进度。在这里成为一个专家更说的通。
|
||||
|
||||
SRE 使用如<ruby>[代码即基础设施][6]<rt>infrastructure-as-code</rt></ruby>的概念去制作模板，然后调用它们来部署用以运行应用的环境，并以使用一键将每个应用和它们的环境完整重现作为目标。因此测试环境中一号服务器里的一号应用的二进制文件与生产环境中十五号服务器的完全一致，仅环境相关的变量如密码和数据库链接字串有所不同。
|
||||
|
||||
SRE 同时也在配置发生改变时完全摧毁一个环境并重新构建它。对于任何系统他们不带一点感情。每个系统只是个被打了标记和安排了生命周期的数字，甚至例行的服务器补丁也要重新部署整个<ruby>应用栈<rt>application stack</rt></ruby>
|
||||
|
||||
### 总结
|
||||
|
||||
对于一些情况，尤其是运维一些大型的基于 DevOps 的环境时，一个 SRE 所能提供的用于处理各种规模业务的专业技能当然更具优势。但每次他们在运气不好走入死胡同时都会去寻求友人系统管理员，或是 [(BOFH)][7] 那身经百战的故障排除技能和那些系统管理员用于给组织提供价值的丰富经验的帮助。
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://opensource.com/article/19/7/sysadmins-vs-sres
|
||||
|
||||
作者：[Vince Power][a]
|
||||
选题：[lujun9972][b]
|
||||
译者：[vizv](https://github.com/vizv)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
||||
[a]: https://opensource.com/users/vincepower/users/craig5/users/dawnparzych/users/penglish
|
||||
[b]: https://github.com/lujun9972
|
||||
[1]: https://opensource.com/sites/default/files/styles/image-full-size/public/lead-images/rh_003499_01_linux11x_cc.png?itok=XMDOouJR (People work on a computer server with devices)
|
||||
[2]: https://en.wikipedia.org/wiki/Site_Reliability_Engineering
|
||||
[3]: https://opensource.com/resources/devops
|
||||
[4]: https://en.wikipedia.org/wiki/Continuous_integration
|
||||
[5]: https://en.wikipedia.org/wiki/Continuous_delivery
|
||||
[6]: https://en.wikipedia.org/wiki/Infrastructure_as_code
|
||||
[7]: http://www.bofharchive.com/BOFH.html
|
||||
Loading…
Reference in New Issue
Block a user