From e595943c1756a468212191dc44da0a0dade722a0 Mon Sep 17 00:00:00 2001 From: darksun Date: Wed, 21 Aug 2019 23:00:23 +0800 Subject: [PATCH 01/58] =?UTF-8?q?take=20a=20break:=2020180116=20Command=20?= =?UTF-8?q?Line=20Heroes-=20Season=201-=20OS=20Wars=5F2.md=20at=202019?= =?UTF-8?q?=E5=B9=B4=2008=E6=9C=88=2021=E6=97=A5=20=E6=98=9F=E6=9C=9F?= =?UTF-8?q?=E4=B8=89=2023:00:23=20HKT?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- ...80116 Command Line Heroes- Season 1- OS Wars_2.md | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/sources/talk/20180116 Command Line Heroes- Season 1- OS Wars_2.md b/sources/talk/20180116 Command Line Heroes- Season 1- OS Wars_2.md index 59747b4d40..1e674c1b0d 100644 --- a/sources/talk/20180116 Command Line Heroes- Season 1- OS Wars_2.md +++ b/sources/talk/20180116 Command Line Heroes- Season 1- OS Wars_2.md @@ -7,17 +7,17 @@ [#]: via: (https://www.redhat.com/en/command-line-heroes/season-1/os-wars-part-2-rise-of-linux) [#]: author: (redhat https://www.redhat.com) -Command Line Heroes: Season 1: OS Wars(Part2 Rise of Linux) +代码英雄: 第一季: 操作系统大战(第二部分 Linux 崛起) ====== -Saron Yitbarek: Is this thing on? Cue the epic Star Wars crawl, and, action. +Saron Yitbarek: 这玩意开着的吗? 让我们进一段史诗般的星球大战的开幕吧, 开始了. -Voice Actor: [00:00:30] Episode Two: Rise of Linux ® . The empire of Microsoft controls 90 % of desktop users . C omplete standardization of operating systems seems assured. However, the advent of the internet swerves the focus of the war from the desktop toward enterprise, where all businesses scramble to claim a server of their own. Meanwhile, an unlikely hero arises from amongst the band of open source rebels . Linus Torvalds, head strong, bespectacled, releases his Linux system free of charge. Microsoft reels — and regroups. +配音: [00:00:30] 第二集:Linux®的崛起。微软帝国控制着90%的桌面用户。操作系统的全面标准化似乎是板上钉钉的事了。然而，互联网的出现将战争的焦点从桌面转向了企业，在该领域，所有商业组织都争相构建自己的服务器。与此同时，一个不太可能的英雄出现在开源反叛组织中。绝顶聪明，头戴眼镜的Linus Torvalds免费发布了他的Linux系统。微软打了个趔趄-并且开始重组。 -Saron Yitbarek: [00:01:00] Oh, the nerd in me just loves that. So, where were we? Last time, Apple and Microsoft were trading blows, trying to dominate in a war over desktop users. By the end of e pisode o ne, we saw Microsoft claiming most of the prize. Soon, the entire landscape went through a seismic upheaval. That's all because of the rise of the internet and the army of developers that rose with it. The internet moves the battlefield from PC users in their home offices to giant business clients with hundreds of servers. +Saron Yitbarek: [00:01:00] 哦，我们书呆子就是喜欢那样。上一次我们讲到哪了?苹果和微软互相攻伐，试图在一场争夺桌面用户的战争中占据主导地位。在第一集的结尾，我们看到微软获得了大部分的市场份额。很快，由于互联网的兴起以及随之而来的开发者大军,整个市场都经历了一场地震。互联网将战场从在家庭和办公室中的个人电脑用户转移到拥有数百台服务器的大型商业客户中。 -[00:01:30] This is a huge resource shift. Not only does every company out there wanting to remain relevant suddenly have to pay for server space and get a website built — they also have to integrate software to track resources, monitor databases, et cetera, et cetera. You're going to need a lot of developers to help you with that. At least, back then you did. +[00:01:30] 这意味着巨量资源的迁移。突然间，所有相关企业不仅被迫为服务器空间和网站建设付费，而且还必须集成软件来进行资源跟踪和数据库监控等工作。你需要很多开发人员来帮助你。至少那时候大家都是这么做的。 -In p art t wo of the OS wars, we'll see how that enormous shift in priorities , and the work of a few open source rebels like Linus Torvalds and Richard Stallman , managed to strike fear in the heart of Microsoft, and an entire software industry. +在操作系统之战的第二部分，我们将看到优先级的巨大转变，以及像Linus Torvalds和Richard Stallman这样的开源叛逆者是如何成功地在微软和整个软件行业的核心地带引起恐惧的。 [00:02:00] I'm Saron Yitbarek and you're listening to Command Line Heroes, an original podcast from Red Hat. In each episode, we're bringing you stories about the people who transform technology from the command line up. From 62310a8a0bf91835b79398f9021f787a785f2ea3 Mon Sep 17 00:00:00 2001 From: darksun Date: Thu, 22 Aug 2019 18:15:33 +0800 Subject: [PATCH 02/58] =?UTF-8?q?take=20a=20break:=2020180116=20Command=20?= =?UTF-8?q?Line=20Heroes-=20Season=201-=20OS=20Wars=5F2.md=20at=202019?= =?UTF-8?q?=E5=B9=B4=2008=E6=9C=88=2022=E6=97=A5=20=E6=98=9F=E6=9C=9F?= =?UTF-8?q?=E5=9B=9B=2018:15:33=20HKT?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- ...ommand Line Heroes- Season 1- OS Wars_2.md | 32 +++++++++---------- 1 file changed, 16 insertions(+), 16 deletions(-) diff --git a/sources/talk/20180116 Command Line Heroes- Season 1- OS Wars_2.md b/sources/talk/20180116 Command Line Heroes- Season 1- OS Wars_2.md index 1e674c1b0d..ce6ace888d 100644 --- a/sources/talk/20180116 Command Line Heroes- Season 1- OS Wars_2.md +++ b/sources/talk/20180116 Command Line Heroes- Season 1- OS Wars_2.md @@ -11,7 +11,7 @@ ====== Saron Yitbarek: 这玩意开着的吗? 让我们进一段史诗般的星球大战的开幕吧, 开始了. -配音: [00:00:30] 第二集:Linux®的崛起。微软帝国控制着90%的桌面用户。操作系统的全面标准化似乎是板上钉钉的事了。然而，互联网的出现将战争的焦点从桌面转向了企业，在该领域，所有商业组织都争相构建自己的服务器。与此同时，一个不太可能的英雄出现在开源反叛组织中。绝顶聪明，头戴眼镜的Linus Torvalds免费发布了他的Linux系统。微软打了个趔趄-并且开始重组。 +配音: [00:00:30] 第二集:Linux®的崛起。微软帝国控制着90%的桌面用户。操作系统的全面标准化似乎是板上钉钉的事了。然而，互联网的出现将战争的焦点从桌面转向了企业，在该领域，所有商业组织都争相构建自己的服务器。与此同时，一个不太可能的英雄出现在开源反叛组织中。固执，戴着眼镜的Linus Torvalds免费发布了他的Linux系统。微软打了个趔趄-并且开始重组。 Saron Yitbarek: [00:01:00] 哦，我们书呆子就是喜欢那样。上一次我们讲到哪了?苹果和微软互相攻伐，试图在一场争夺桌面用户的战争中占据主导地位。在第一集的结尾，我们看到微软获得了大部分的市场份额。很快，由于互联网的兴起以及随之而来的开发者大军,整个市场都经历了一场地震。互联网将战场从在家庭和办公室中的个人电脑用户转移到拥有数百台服务器的大型商业客户中。 @@ -19,35 +19,35 @@ Saron Yitbarek: [00:01:00] 哦，我们书呆子就是喜欢那样。上一次 在操作系统之战的第二部分，我们将看到优先级的巨大转变，以及像Linus Torvalds和Richard Stallman这样的开源叛逆者是如何成功地在微软和整个软件行业的核心地带引起恐惧的。 -[00:02:00] I'm Saron Yitbarek and you're listening to Command Line Heroes, an original podcast from Red Hat. In each episode, we're bringing you stories about the people who transform technology from the command line up. +[00:02:00] 我是 Saron Yitbarek,您现在收听的是代码英雄，一款红帽公司原创的播客节目. 每一集,我们都会给您带来“从码开始”改变技术的人的故事. -[00:02:30] Okay. Imagine for a second that you're Microsoft in 1991. You're feeling pretty good, right? Pretty confident. Assured global domination feels nice. You've mastered the art of partnering with other businesses, but you're still pretty much cutting out the developers, programmers, and sys admins that are the real foot soldiers out there. There is this Finnish geek named Linus Torvalds. He and his team of open source programmers are starting to put out versions of Linux, this OS kernel that they're duct taping together. +[00:02:30] 好。假设你是1991年的微软。你自我感觉良好，对吧?满怀信心。确定全球主导的地位感觉不错。你已经掌握了与其他企业合作的艺术，但是仍然将大部分开发人员、程序员和系统管理员排除在联盟之外，而他们才是真正的步兵。这是出现了个叫Linus Torvalds的芬兰极客。他和他的开源程序员团队正在开始发布Linux，其操作系统内核是由他们一起编写出来的。 -[00:03:00] If you're Microsoft, frankly, you're not too concerned about Linux or even about open source in general, but eventually, the sheer size of Linux gets so big that it becomes impossible for Microsoft not to notice. The first version comes out in 1991 and it's got maybe 10,000 lines of code. A decade later, there will be three million lines of code. In case you're wondering, today it's at 20 million. +[00:03:00] 坦白地说，如果你是微软公司，你并不会太在意Linux，甚至是一般意义上的开源运动，但是最终，Linux的规模变得如此之大，以至于微软不可能不注意到。Linux第一个版本出现在1991年，当时大概有10000行代码。十年后，变成了300万行代码。如果你想知道，今天则是2000万行代码。 -[00:03:30] For a moment, let's stay in the early 90s. Linux hasn't yet become the behemoth we know now. It's just this strangely viral OS that's creeping across the planet, and the geeks and hackers of the world are falling in love with it. I was too young in those early days, but I sort of wish I'd been there. At that time, discovering Linux was like gaining access to a secret society. Programmers would share the Linux CD set with friends the same way other people would share mixtapes of underground music. +[00:03:30] 让我们停留在90年代初一会儿。那是Linux还没有成为我们现在所知道的庞然大物。只是这个奇怪的病毒式的操作系统正在这个星球上蔓延，全世界的极客和黑客都爱上了它。那时候我还太年轻，但依然希望加入他们。在那个时候，发现Linux就如同进入了一个秘密社会一样。程序员与朋友分享Linux CD集，就像其他人分享地下音乐混音带一样。 -Developer Tristram Oaten [00:03:40] tells the story of how he first encountered Linux when he was 16 years old. +Developer Tristram Oaten [00:03:40] 讲讲了你16岁时第一次接触Linux的故事吧。 -Tristram Oaten: [00:04:00] We went on a scuba diving holiday, my family and I, to Hurghada, which is on the Red Sea. Beautiful place, highly recommend it. The first day, I drank the tap water. Probably, my mom told me not to. I was really sick the whole week — didn't leave the hotel room. All I had with me was a laptop with a fresh install of Slackware Linux, this thing that I'd heard about and was giving it a try. There were no extra apps, just what came on the eight CDs. By necessity, all I had to do this whole week was to get to grips with this alien system. I read man pages, played around with the terminal. I remember not knowing the difference between a single dot, meaning the current directory, and two dots, meaning the previous directory. +Tristram Oaten: [00:04:00] 我和我的家人去了Red Sea上的Hurghada潜水度假。那是一个美丽的地方，强烈推荐。第一天，我喝了自来水。也许，我妈妈跟我说过不要这么做。我整个星期都病得很厉害，没有离开旅馆房间。当时我只带了一台新安装了Slackware Linux的笔记本电脑，我听说过这玩意并且正在尝试使用它。这台笔记本上没有额外的应用程序，只有8张cd。出于必要，整个星期我所做的就是去了解这个外星一般的系统。我阅读手册，摆弄着终端。我记得当时我甚至我不知道一个点(表示当前目录)和两个点(表示前一个目录)之间的区别。 -[00:04:30] I had no clue. I must have made so many mistakes, but slowly, over the course of this forcible solitude, I broke through this barrier and started to understand and figure out what this command line thing was all about. By the end of the holiday, I hadn't seen the pyramids, the Nile, or any Egyptian sites, but I had unlocked one of the wonders of the modern world. I'd unlocked Linux, and the rest is history. +[00:04:30] 我一点头绪都没有。犯过很多错误，但慢慢地，在这种强迫的孤独中，我突破了障碍，开始理解并明白命令行到底是怎么回事。假期结束时，我没有看过金字塔、尼罗河等任何埃及遗址，但我解锁了现代世界的一个奇迹。我解锁了Linux，接下来的事大家都知道了。 -Saron Yitbarek: You can hear some variation on that story from a lot of people. Getting access to that Linux command line was a transformative experience. +Saron Yitbarek: 你可以从很多人那里听到关于这个故事的不同说法。访问Linux命令行是一种革命性的体验。 -David Cantrell: This thing gave me the source code. I was like, "That's amazing." +David Cantrell: 它给了我源代码. 我当时的感觉是, "太神奇了." -Saron Yitbarek: We're at a 2017 Linux developers conference called Flock to Fedora. +Saron Yitbarek: 我们正在参加一个名为Flock to Fedora的2017年Linux开发者大会。 -David Cantrell: ... very appealing. I felt like I had more control over the system and it just drew me in more and more. From there, I guess, after my first Linux kernel compile in 1995, I was hooked, so, yeah. +David Cantrell: ... 非常有吸引力。我觉得我对这个系统有了更多的控制力，它越来越吸引我。我想，从那时起，1995年我第一次编译Linux内核时，我就迷上了它。 -Saron Yitbarek: Developers David Cantrell and Joe Brockmire. +Saron Yitbarek: 开发者 David Cantrell 与 Joe Brockmire. -Joe Brockmeier: I was going through the cheap software and found a four - CD set of Slackware Linux. It sounded really exciting and interesting so I took it home, installed it on a second computer, started playing with it, and really got excited about two things. One was, I was excited not to be running Windows, and I was excited by the open source nature of Linux. +Joe Brockmeier: 我寻遍了便宜软件最终找到一套四张CD的 Slackware Linux. 它看起来来非常令人兴奋而且很有趣，所以我把它带回家，安装在第二台电脑上，开始摆弄它，并为两件事情感到兴奋。一个是，我运行的不是Windows，另一个我Linux的开源特性。 -Saron Yitbarek: [00:06:00] That access to the command line was, in some ways, always there. Decades before open source really took off, there was always a desire to have complete control, at least among developers. Go way back to a time before the OS wars, before Apple and Microsoft were fighting over their GUIs. There were command line heroes then, too. Professor Paul Jones is the director of the online library ibiblio.org. He worked as a developer during those early days. +Saron Yitbarek: [00:06:00] 某种程度上来说，对命令行的访问总是存在的。在开源真正开始流行还要早几十年前，人们(至少在开发人员中是这样)总是希望能够做到完全控制。让我们回到操作系统大战之前的那个时代，在苹果和微软他们的GUI而战之前。那时也有代码英雄。保罗·琼斯(Paul Jones)教授(在线图书馆ibiblio.org负责人)在那个古老的时代，就是一名开发人员。 -Paul Jones: [00:07:00] The internet, by its nature, at that time, was less client server, totally, and more peer to peer. We're talking about, really, some sort of VAX to VAX, some sort of scientific workstation, the scientific workstation. That doesn't mean that client and server relationships and applications weren't there, but it does mean that the original design was to think of how to do peer - to - peer things, the opposite of what IBM had been doing, in which they had dumb terminals that had only enough intelligence to manage the user interface, but not enough intelligence to actually let you do anything in the terminal that would expose anything to it. +Paul Jones: [00:07:00] 从本质上讲，互联网在那个时候比较少是客户端-服务器架构的，而是更多是点对点架构的。讲真，当我们说，某种VAX到VAX，某科学工作站，科学工作站。这并不意味着没有客户端与服务端的关系以及没有应用程序,但这的确意味着,最初的设计是思考如何实现点对点,它与IBM一直在做的东西相对立. IBM给你的只有哑终端,这种终端只能让你管理用户界面,却无法让你像真正的终端一样为所欲为。 Saron Yitbarek: As popular as GUI was becoming among casual users, there was always a pull in the opposite direction for the engineers and developers. Before Linux in the 1970s and 80s, that resistance was there, with EMAX and GNU . W ith Stallman's free software foundation, certain folks were always begging for access to the command line, but it was Linux in the 1990s that delivered like no other. From f232f167c2126a9a791340c457b68d8677e35692 Mon Sep 17 00:00:00 2001 From: darksun Date: Fri, 23 Aug 2019 11:22:37 +0800 Subject: [PATCH 03/58] =?UTF-8?q?take=20a=20break:=2020180116=20Command=20?= =?UTF-8?q?Line=20Heroes-=20Season=201-=20OS=20Wars=5F2.md=20at=202019?= =?UTF-8?q?=E5=B9=B4=2008=E6=9C=88=2023=E6=97=A5=20=E6=98=9F=E6=9C=9F?= =?UTF-8?q?=E4=BA=94=2011:22:37=20HKT?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- ...ommand Line Heroes- Season 1- OS Wars_2.md | 28 +++++++++---------- 1 file changed, 14 insertions(+), 14 deletions(-) diff --git a/sources/talk/20180116 Command Line Heroes- Season 1- OS Wars_2.md b/sources/talk/20180116 Command Line Heroes- Season 1- OS Wars_2.md index ce6ace888d..0fba2329ef 100644 --- a/sources/talk/20180116 Command Line Heroes- Season 1- OS Wars_2.md +++ b/sources/talk/20180116 Command Line Heroes- Season 1- OS Wars_2.md @@ -49,33 +49,33 @@ Saron Yitbarek: [00:06:00] 某种程度上来说，对命令行的访问总是 Paul Jones: [00:07:00] 从本质上讲，互联网在那个时候比较少是客户端-服务器架构的，而是更多是点对点架构的。讲真，当我们说，某种VAX到VAX，某科学工作站，科学工作站。这并不意味着没有客户端与服务端的关系以及没有应用程序,但这的确意味着,最初的设计是思考如何实现点对点,它与IBM一直在做的东西相对立. IBM给你的只有哑终端,这种终端只能让你管理用户界面,却无法让你像真正的终端一样为所欲为。 -Saron Yitbarek: As popular as GUI was becoming among casual users, there was always a pull in the opposite direction for the engineers and developers. Before Linux in the 1970s and 80s, that resistance was there, with EMAX and GNU . W ith Stallman's free software foundation, certain folks were always begging for access to the command line, but it was Linux in the 1990s that delivered like no other. +Saron Yitbarek: 图形用户界面在普通用户中普及的同时，在工程师和开发人员中总是存在和一股相反的力量。早在20世纪70年代和80年代的Linux出现之前，这股力量就存在于EMAX和GNU中。有了斯托尔曼的自由软件基金会后，总有某些人想要使用命令行，但上世纪90年代的Linux的交付方式是独一无二的。 -[00:07:30] The early lovers of Linux and other open source software were pioneers. I'm standing on their shoulders. We all are. +[00:07:30] Linux和其他开源软件的早期爱好者是都是先驱。我正站在他们的肩膀上。我们都是。 -You're listening to Command Line Heroes, an original podcast from Red Hat. This is part two of the OS wars: Rise of Linux. +您现在收听的是代码英雄, 一款由红帽公司原创的播客. 这是操作系统大战的第二部分: Linux 崛起. -Steven Vaughan-Nichols: By 1998, things have changed. +Steven Vaughan-Nichols: 1998年的时候, 情况发生了变化. -Saron Yitbarek: Steven Vaughan-Nichols is a contributing editor at zdnet.com, and he's been writing for decades about the business side of technology. He describes how Linux slowly became more and more popular until the number of volunteer contributors was way larger than the number of Microsoft developers working on Windows. Linux never really went after Microsoft's desktop customers, though, and maybe that's why Microsoft ignored them at first. Where Linux did shine was in the server room. When businesses went online, each one required a unique programming solution for their needs. +Saron Yitbarek: Steven Vaughan-Nichols 是zdnet.com的特约编辑，他已经写了几十年关于技术商业方面的文章了。他将向我们讲述Linux是如何慢慢变得越来越流行，直到自愿贡献者的数量远远超过了在Windows上工作的微软开发人员的数量的。不过，Linux从来没有真正关注过微软的台式机客户，这也许就是微软最开始时忽略了Linux及其开发者的原因。Linux真正大放光彩的地方是在服务器机房。当企业开始线上业务时，每个企业都需要一个独特的编程解决方案来满足其需求。 -[00:08:30] Windows NT comes out in 1993 and it's competing with other server operating systems, but lots of developers are thinking, "Why am I going to buy an AIX box or a large windows box when I could set up a cheap Linux-based system with Apache?" Point is, Linux code started seeping into just about everything online. +[00:08:30] WindowsNT于1993年问世，当时它已经在与其他的服务器操作系统展开竞争了，但是许多开发人员都在想，“既然我可以通过Apache构建出基于Linux的廉价系统，那我为什么要购买AIX设备或大型Windows设备呢？”关键点在于，Linux代码已经开始渗透到几乎所有在线的东西中。 -Steven Vaughan-Nichols: [00:09:00] Microsoft realizes that Linux, quite to their surprise, is actually beginning to get some of the business, not so much on the desktop, but on business servers. As a result of that, they start a campaign, what we like to call FUD — fear, uncertainty and doubt — saying, "Oh this Linux stuff, it's really not that good. It's not very reliable. You can't trust it with anything." +Steven Vaughan-Nichols: [00:09:00] 令微软感到惊讶的是，它开始意识到，Linux实际上已经开始有一些商业应用，不是在桌面环境，而是在商业服务器上。因此，他们发起了一场运动，我们称之为FUD-恐惧、不确定和怀疑(fear,uncertainty和double).他们说，“哦，Linux这玩意，真的没有那么好。它不太可靠。你一点都不能相信它”。 -Saron Yitbarek: [00:09:30] That soft propaganda style attack goes on for a while. Microsoft wasn't the only one getting nervous about Linux, either. It was really a whole industry versus that weird new guy. For example, anyone with a stake in UNIX was likely to see Linux as a usurper. Famously, the SCO Group, which had produced a version of UNIX, waged lawsuits for over a decade to try and stop the spread of Linux. SCO ultimately failed and went bankrupt. Meanwhile, Microsoft kept searching for their opening. They were a company that needed to make a move. It just wasn't clear what that move was going to be. +Saron Yitbarek: [00:09:30] 这种软宣传式的攻击持续了一段时间。微软也不是唯一一个对Linux感到紧张的公司。这其实是整个行业在对抗这个奇怪新人的挑战。例如，任何与UNIX有利害关系的人都可能将Linux视为篡夺者。有一个案例很著名，那就是SCO组织(它发行过一种版本的UNIX)在过去10多年里发起一系列的诉讼，试图阻止Linux的传播。SCO最终失败而且破产了。与此同时，微软一直在寻找机会。他们势在必行。只不过目前还不清楚具体要怎么做。 -Steven Vaughan-Nichols: [00:10:30] What will make Microsoft really concerned about it is the next year, in 2000, IBM will announce that they will invest a billion dollars in Linux in 2001. Now, IBM is not really in the PC business anymore. They're not out yet, but they're going in that direction, but what they are doing is they see Linux as being the future of servers and mainframe computers, which, spoiler alert, IBM was correct. Linux is going to dominate the server world. +Steven Vaughan-Nichols: [00:10:30] 让微软真正担心的是，第二年，在2000年的时候，IBM宣布,他们将于2001年投资10亿美元在Linux上。现在，IBM已经不再涉足个人电脑业务。他们还没有走出去，但他们正朝着这个方向前进，他们将Linux视为服务器和大型计算机的未来，在这一点上，剧透警告，IBM是正确的。Linux将主宰服务器世界。 -Saron Yitbarek: This was no longer just about a bunch of hackers loving their Jedi-like control of the command line. This was about the money side working in Linux's favor in a major way. John "Mad Dog" Hall, the executive director of Linux International, has a story that explains why that was. We reached him by phone. +Saron Yitbarek: 这已经不再仅仅是一群黑客喜欢命令行的Jedi式的控制了。金钱的投入对Linux助力极大。Linux国际的执行董事John "Mad Dog" Hall有一个故事可以解释为什么会这样。我们通过电话与他取得了联系。 -John Hall: [00:11:30] A friend of mine named Dirk Holden [00:10:56] was a German systems administrator at Deutsche Bank in Germany, and he also worked in the graphics projects for the early days of the X Windows system for PCs. I visited him one day at the bank, and I said, "Dirk, you have 3,000 servers here at the bank and you use Linux. Why don't you use Microsoft NT?" He looked at me and he said, "Yes, I have 3,000 servers , and if I used Microsoft Windows NT, I would need 2,999 systems administrators." He says, "With Linux, I only need four." That was the perfect answer. +John Hall: [00:11:30] 我的一个朋友名叫Dirk Holden[00:10:56]，他是德国德意志银行的一名系统管理员，他也参与了个人电脑上早期X Windows系统的图形项目中的工作。有一天我去银行拜访他，我说:“Dirk，你银行里有3000台服务器，用的都是Linux。为什么不用Microsoft NT呢?”他看着我说:“是的，我有3000台服务器，如果使用微软的Windows NT系统，我需要2999名系统管理员。”他继续说道:“而使用Linux，我只需要四个。”这真是完美的答案。 -Saron Yitbarek: [00:12:00] The thing programmers are getting obsessed with also happens to be deeply attractive to big business. Some businesses were wary. The FUD was having an effect. They heard open source and thought, "Open. That doesn't sound solid. It's going to be chaotic, full of bugs," but as that bank manager pointed out, money has a funny way of convincing people to get over their hangups. Even little businesses, all of which needed websites, were coming on board. The cost of working with a cheap Linux system over some expensive proprietary option, there was really no comparison. If you were a shop hiring a pro to build your website, you wanted them to use Linux. +Saron Yitbarek: [00:12:00] 程序员们着迷的这些东西恰好对大公司也极具吸引力。但由于FUD的作用，一些企业对此持谨慎态度。他们听到开源，就想:"开源。这看起来不太可靠,很混乱，充满了BUG".但正如那位银行经理所指出的，金钱听过一种有趣的方式，说服人们克服困境。甚至那些需要网站的小公司也加入了Linux阵营。与一些昂贵的专有选择相比，使用一个廉价的Linux系统在成本上是无法比拟的。如果您是一家雇佣专业人员来构建网站的商店，那么您很定想让他们使用Linux。 -[00:12:30] Fast forward a few years. Linux runs everybody's website. Linux has conquered the server world, and then, along comes the smartphone. Apple and their iPhones take a sizeable share of the market, of course, and Microsoft hoped to get in on that, except, surprise, Linux was there, too, ready and raring to go. +[00:12:30] 让我们快进几年. Linux运行每个人的网站上。Linux已经征服了服务器世界，然后智能手机也随之诞生。当然，苹果和他们的iPhone占据了相当大的市场份额，而且微软页希望能进入这个市场，但令人惊讶的是，Linux也在那，已经做好准备了，迫不及待要大展拳脚。 -Author and journalist James Allworth. +作家兼记者 James Allworth. James Allworth: [00:13:00] There was certainly room for a second player, and that could well have been Microsoft, but for the fact of Android, which was fundamentally based on Linux, and because Android, famously acquired by Google, and now running a majority of the world's smartphones, Google built it on top of that. They were able to start with a very sophisticated operating system and a cost basis of zero. They managed to pull it off, and it ended up locking Microsoft out of the next generation of devices, by and large, at least from an operating system perspective. From 2f33d8a1fa3c77e84cfb452cb710058b09eacfa0 Mon Sep 17 00:00:00 2001 From: darksun Date: Fri, 23 Aug 2019 18:53:21 +0800 Subject: [PATCH 04/58] =?UTF-8?q?take=20a=20break:=2020180116=20Command=20?= =?UTF-8?q?Line=20Heroes-=20Season=201-=20OS=20Wars=5F2.md=20at=202019?= =?UTF-8?q?=E5=B9=B4=2008=E6=9C=88=2023=E6=97=A5=20=E6=98=9F=E6=9C=9F?= =?UTF-8?q?=E4=BA=94=2018:53:21=20HKT?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- ...ommand Line Heroes- Season 1- OS Wars_2.md | 36 +++++++++---------- 1 file changed, 18 insertions(+), 18 deletions(-) diff --git a/sources/talk/20180116 Command Line Heroes- Season 1- OS Wars_2.md b/sources/talk/20180116 Command Line Heroes- Season 1- OS Wars_2.md index 0fba2329ef..7fcbeb38d7 100644 --- a/sources/talk/20180116 Command Line Heroes- Season 1- OS Wars_2.md +++ b/sources/talk/20180116 Command Line Heroes- Season 1- OS Wars_2.md @@ -73,43 +73,43 @@ John Hall: [00:11:30] 我的一个朋友名叫Dirk Holden[00:10:56]，他是德 Saron Yitbarek: [00:12:00] 程序员们着迷的这些东西恰好对大公司也极具吸引力。但由于FUD的作用，一些企业对此持谨慎态度。他们听到开源，就想:"开源。这看起来不太可靠,很混乱，充满了BUG".但正如那位银行经理所指出的，金钱听过一种有趣的方式，说服人们克服困境。甚至那些需要网站的小公司也加入了Linux阵营。与一些昂贵的专有选择相比，使用一个廉价的Linux系统在成本上是无法比拟的。如果您是一家雇佣专业人员来构建网站的商店，那么您很定想让他们使用Linux。 -[00:12:30] 让我们快进几年. Linux运行每个人的网站上。Linux已经征服了服务器世界，然后智能手机也随之诞生。当然，苹果和他们的iPhone占据了相当大的市场份额，而且微软页希望能进入这个市场，但令人惊讶的是，Linux也在那，已经做好准备了，迫不及待要大展拳脚。 +[00:12:30] 让我们快进几年. Linux运行每个人的网站上。Linux已经征服了服务器世界，然后智能手机也随之诞生。当然，苹果和他们的iPhone占据了相当大的市场份额，而且微软也希望能进入这个市场，但令人惊讶的是，Linux也在那，已经做好准备了，迫不及待要大展拳脚。 作家兼记者 James Allworth. -James Allworth: [00:13:00] There was certainly room for a second player, and that could well have been Microsoft, but for the fact of Android, which was fundamentally based on Linux, and because Android, famously acquired by Google, and now running a majority of the world's smartphones, Google built it on top of that. They were able to start with a very sophisticated operating system and a cost basis of zero. They managed to pull it off, and it ended up locking Microsoft out of the next generation of devices, by and large, at least from an operating system perspective. +James Allworth: [00:13:00] 当然还有容纳第二个竞争者的空间，那本可以是微软，但是实际上却是Android，而Andrid基本上是基于Linux的. 众所周知,Android被谷歌所收购，现在运行在世界上大部分的智能手机上，谷歌在Linux的基础上创建了Android。Linux使他们能够以零成本从一个非常复杂的操作系统开始。他们成功地实现了这一目标，最终将微软挡在了下一代设备之外，至少从操作系统的角度来看是这样。 -Saron Yitbarek: [00:13:30] The ground was breaking up, big time, and Microsoft was in danger of falling into the cracks. John Gossman is the chief architect on the Azure team at Microsoft. He remembers the confusion that gripped the company at that time. +Saron Yitbarek: [00:13:30] 天崩地裂了，很大程度上，微软有被埋没的风险。John Gossman是微软Azure团队的首席架构师。他还记得当时困扰公司的困惑。 -John Gossman: [00:14:00] Like a lot of companies, Microsoft was very concerned about IP pollution. They thought that if you let developers use open source they would likely just copy and paste bits of code into some product and then some sort of a viral license might take effect that ... They were also very confused, I think, it was just culturally, a lot of companies, Microsoft included, were confused on the difference between what open source development meant and what the business model was. There was this idea that open source meant that all your software was free and people were never going to pay anything. +John Gossman: [00:14:00] 像许多公司一样，微软也非常担心知识产权污染。他们认为，如果允许开发人员使用开源代码，那么很可能只是复制并粘贴一些代码到某些产品中，就会让某种病毒式的许可证生效从而引发未知的风险…，我认为，这跟公司文化有关，很多公司，包括微软，都对开源开发的意义和商业模式之间的分歧感到困惑。有一种观点认为，开源意味着你所有的软件都是免费的，人们永远不会付钱。 -Saron Yitbarek: [00:14:30] Anybody invested in the old, proprietary model of software is going to feel threatened by what's happening here. When you threaten an enormous company like Microsoft, yeah, you can bet they're going to react. It makes sense they were pushing all that FUD — fear, uncertainty and doubt. At the time, an “ us versus them ” attitude was pretty much how business worked. If they'd been any other company, though, they might have kept that old grudge, that old thinking, but then, in 2013, everything changes. +Saron Yitbarek: [00:14:30] 任何投资于旧的、专有软件模型的人都会觉得这里发生的一切对他们构成了威胁。当你威胁到像微软这样的大公司时，是的，他们一定会做出反应。他们推动所有这些FUD(fear,uncertainty,doubt)-恐惧，不确定性和怀疑是有道理的。当时，商业运作的方式基本上就是相互竞争。不过，如果他们是其他公司的话(If they'd been any other company,看不懂什么意思)，他们可能还会怀恨在心，抱着旧有的想法，但到了2013年，一切都变了。 -[00:15:00] Microsoft's cloud computing service, Azure, goes online and, shockingly, it offers Linux virtual machines from day one. Steve Ballmer, the CEO who called Linux a cancer, he's out, and a new forward - thinking CEO, Satya Nadella, has been brought in. +[00:15:00] 微软的云计算服务Azure上线了，令人震惊的是，它从第一天开始就提供了Linux虚拟机。Steve Ballmer，这位把Linux称为癌症的首席执行官，已经离开了，代替他的是一位新的有远见的首席执行官Satya Nadella. -John Gossman: Satya has a different attitude. He's another generation. He's a generation younger than Paul and Bill and Steve were, and had a different perspective on open source. +John Gossman: Satya 有不同的看法. 他属于另一个世代. 比Paul , Bill 和 Steve 更年轻的世代 , 他对开源有不同的看法. -Saron Yitbarek: John Gossman, again, from Microsoft's Azure team. +Saron Yitbarek: John Gossman, 再说一次, 来自于 微软的Azure 团队. -John Gossman: [00:16:00] We added Linux support into Azure about four years ago, and that was for very pragmatic reasons. If you go to any enterprise customer, you will find that they are not trying to decide whether to use Windows or to use Linux or to use .net or to use Java TM . They made all those decisions a long time ago — about 15 years or so ago, there was some of this argument. Now, every company that I have ever seen has a mix of Linux and Java and Windows and .net and SQL Server and Oracle and MySQL — proprietary source code - based products and open source code products. +John Gossman: [00:16:00] 大约四年前，处于实际需要，我们在Azure中添加了Linux支持。如果访问任何一家企业客户，你都会发现他们并没有试图决定是使用Windows还是使用Linux、使用.net还是使用Java TM。他们在很久以前就做出了决定——大约15年前才有这样的一些争论。现在，我见过的每一家公司都混合了Linux和Java、Windows和.net、SQL Server、Oracle和MySQL——基于专有源代码的产品和开放源代码的产品。 -If you're going to operate a cloud and you're going to allow and enable those companies to run their businesses on the cloud, you simply cannot tell them, "You can use this software but you can't use this software." +如果你正在运维着一个云，允许这些公司在云上运行他们的业务，那么你就不能简单地告诉他们，“你可以使用这个软件，但你不能使用那个软件。” -Saron Yitbarek: [00:16:30] That's exactly the philosophy that Satya Nadella adopted. In the fall of 2014, he gets up on stage and he wants to get across one big, fat point. Microsoft loves Linux. He goes on to say that 20 % of Azure is already Linux and that Microsoft will always have first - class support for Linux distros. There's not even a whiff of that old antagonism toward open source. +Saron Yitbarek: [00:16:30] 这正是 Satya Nadella 采纳的哲学思想. 2014年秋季，他站在舞台上，希望传递一个重要信息。微软爱Linux。他接着说，Azure 20%的业务量已经是Linux了，微软将始终对Linux发行版提供一流的支持。没有哪怕一丝对开源的宿怨。 -To drive the point home, there's literally a giant sign behind them that reads, "Microsoft hearts Linux." Aww. For some of us, that turnaround was a bit of a shock, but really, it shouldn't have been. Here's Steven Levy, a tech journalist and author. +为了说明这一点，在他们的背后有一个巨大的标志，上面写着:“Microsoft hearts Linux”。哇哇哇。对我们中的一些人来说，这种转变有点令人震惊，但实际上，无需如此震惊。下面是Steven Levy,一名科技记者兼作家。 -Steven Levy: [00:17:30] When you're playing a football game and the turf becomes really slick, maybe you switch to a different kind of footwear in order to play on that turf. That's what they were doing. They can't deny reality and there are smart people there so they had to realize that this is the way the world is and put aside what they said earlier, even though they might be a little embarrassed at their earlier statements, but it would be crazy to let their statements about how horrible open source was earlier, affect their smart decisions now. +Steven Levy: [00:17:30] 当你在踢足球的时候，如果草坪变滑了，那么你也许会换一种不同的鞋子。他们当初就是这么做的。他们不能否认现实而且他们之间也有有聪明人,所以他们必须意识到,这就是世界的运行方式,不管他们早些时候说了什么,即使他们对之前的言论感到尴尬,但是让他们之前关于开源多么可怕的言论影响到现在明智的决策那才真的是疯了。 -Saron Yitbarek: [00:18:00] Microsoft swallowed its pride in a big way. You might remember that Apple, after years of splendid isolation, finally shifted toward a partnership with Microsoft. Now it was Microsoft's turn to do a 180. After years of battling the open source approach, they were reinventing themselves. It was change or perish. Steven Vaughan-Nichols. +Saron Yitbarek: [00:18:00] 微软低下了它高傲的头. 你可能还记得苹果公司, 经过多年的孤立无援, 最终转向与微软构建合作伙伴关系. 现在轮到微软进行180度转变了. 经过多年的与开源方法的战斗后，他们正在重塑自己。要么改变，要么死亡. Steven Vaughan-Nichols. -Steven Vaughan-Nichols: [00:18:30] Even a company the size of Microsoft simply can't compete with the thousands of open source developers working on all these other major projects , including Linux. They were very loath e to do so for a long time. The former Microsoft CEO, Steve Ballmer, hated Linux with a passion. Because of its GPL license, it was a cancer, but once Ballmer was finally shown the door, the new Microsoft leadership said, "This is like trying to order the tide to stop coming in. The tide is going to keep coming in. We should work with Linux, not against it." +Steven Vaughan-Nichols: [00:18:30] 即使是像微软这样规模的公司也无法与成千上万的开源开发者竞争，这些开发者开发这包括Linux在内的其他大项目。很长时间以来他们都不愿意这么做。前微软首席执行官史蒂夫·鲍尔默（SteveBallmer）对Linux深恶痛绝。由于它的GPL许可证，让Linux称为一种癌症，但一旦鲍尔默被扫地出门，新的微软领导层说，“这就好像试图命令潮流不要过来，但潮水依然会不断涌进来。我们应该与Linux合作，而不是与之对抗。” -Saron Yitbarek: [00:19:00] Really, one of the big wins in the history of online tech is the way Microsoft was able to make this pivot, when they finally decided to. Of course, older, hardcore Linux supporters were pretty skeptical when Microsoft showed up at the open source table. They weren't sure if they could embrace these guys, but, as Vaughan-Nichols points out, today's Microsoft simply is not your mom and dad's Microsoft. +Saron Tiebreak: [00:19:00] 真的，在线技术历史上最大的胜利之一就是微软能够做出这样的转变，当他们最终决定这么做的时候。当然，当微软出现在开源的桌子上时，老的、铁杆Linux支持者是相当怀疑的。他们不确定自己是否能接受这些家伙，但正如沃恩-尼科尔斯所指出的，今天的微软根本不是你父母的微软。事实上, 互联网技术历史上最大的胜利之一就是让微软最终做出如此转变. 当然，当微软出现在开源桌上时，老一代的、铁杆Linux支持者是相当怀疑的。他们不确定自己是否能接受这些家伙，但正如Vaughan-Nichols 所指出的，今天的微软已经不是你父母那一代时的微软了。 -Steven Vaughan-Nichols : [00:19:30] Microsoft 2017 is not Steve Ballmer's Microsoft, nor is it Bill Gates' Microsoft. It's an entirely different company with a very different approach and, again, once you start using open source, it's not like you can really pull back. Open source has devoured the entire technology world. People who have never heard of Linux as such, don't know it, but every time they're on Facebook , they're running Linux. Every time you do a Google search , you're running Linux. +Steven Vaughan-Nichols : [00:19:30] 2017年的微软既不是史蒂夫•鲍尔默(Steve Ballmer)的微软，也不是比尔•盖茨(Bill Gates)的微软。这是一家完全不同的公司，有着完全不同的方法，而且，开源软件一旦被放出，就无法被收回。开源已经吞噬了整个技术世界。从未听说过Linux的人可能对它并不了解，但是每次他们访问Facebook，他们都在运行Linux。每次执行谷歌搜索时，你都在运行Linux。 -[00:20:00] Every time you do anything with your Android phone , you're running Linux again. It literally is everywhere, and Microsoft can't stop that, and thinking that Microsoft can somehow take it all over, I think is naïve. +[00:20:00] 每次你用Android手机，你都在运行Linux。它确实无处不在，微软无法阻止它，我认为以为微软可以以某种方式接管它的想法，太天真了。 Saron Yitbarek: [00:20:30] Open source supporters might have been worrying about Microsoft coming in like a wolf in the flock, but the truth is, the very nature of open source software protects it from total domination. No single company can own Linux and control it in any specific way. Greg Kroah-Hartman is a fellow at the Linux Foundation. From 61075cd3b99379dbcaa37a23c6442d83d3197c8b Mon Sep 17 00:00:00 2001 From: darksun Date: Fri, 23 Aug 2019 19:15:43 +0800 Subject: [PATCH 05/58] =?UTF-8?q?take=20a=20break:=2020180116=20Command=20?= =?UTF-8?q?Line=20Heroes-=20Season=201-=20OS=20Wars=5F2.md=20at=202019?= =?UTF-8?q?=E5=B9=B4=2008=E6=9C=88=2023=E6=97=A5=20=E6=98=9F=E6=9C=9F?= =?UTF-8?q?=E4=BA=94=2019:15:43=20HKT?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- .../talk/20180116 Command Line Heroes- Season 1- OS Wars_2.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/sources/talk/20180116 Command Line Heroes- Season 1- OS Wars_2.md b/sources/talk/20180116 Command Line Heroes- Season 1- OS Wars_2.md index 7fcbeb38d7..fe598d2f3f 100644 --- a/sources/talk/20180116 Command Line Heroes- Season 1- OS Wars_2.md +++ b/sources/talk/20180116 Command Line Heroes- Season 1- OS Wars_2.md @@ -111,9 +111,9 @@ Steven Vaughan-Nichols : [00:19:30] 2017年的微软既不是史蒂夫•鲍尔 [00:20:00] 每次你用Android手机，你都在运行Linux。它确实无处不在，微软无法阻止它，我认为以为微软可以以某种方式接管它的想法，太天真了。 -Saron Yitbarek: [00:20:30] Open source supporters might have been worrying about Microsoft coming in like a wolf in the flock, but the truth is, the very nature of open source software protects it from total domination. No single company can own Linux and control it in any specific way. Greg Kroah-Hartman is a fellow at the Linux Foundation. +Saron Yitbarek: [00:20:30] 开源支持者可能一直担心微软会像混入羊群中的狼一样，但事实是，开源软件的本质保护了它无法被完全控制。没有一家公司能够拥有Linux并以某种特定的方式控制它。Greg Kroah-Hartman是Linux基金会的一名成员。 -Greg Kroah-Hartman: Every company and every individual contributes to Linux in a selfish manner. They're doing so because they want to solve a problem that they have, be it hardware isn't working , or they want to add a new feature to do something else , or want to take it in a direction that they'll build that they can use for their product. That's great, because then everybody benefits from that because they're releasing the code back, so that everybody can use it. It's because of that selfishness that all companies and all people have, everybody benefits. +Greg Kroah-Hartman: 每个公司和个人都以自私的方式为Linux做出贡献。他们之所以这样做是因为他们想要解决他们所面临的问题，可能是硬件无法工作，或者是他们想要添加一个新功能来做其他事情，又或者想在他们的产品中使用它。这很棒，因为他们会把代码贡献回去,此后每个人都会从中受益，这样每个人都可以用到这份代码。正是因为这种自私，所有的公司，所有的人，所有的人都能从中受益。 Saron Yitbarek: [00:21:30] Microsoft has realized that in the coming cloud wars, fighting Linux would be like going to war with, well, a cloud. Linux and open source aren't the enemy, they're the atmosphere. Today, Microsoft has joined the Linux Foundation as a platinum member. They became the number one contributor to open source on GitHub. In September, 2017, they even joined the Open Source Initiative. These days, Microsoft releases a lot of its code under open licenses. Microsoft's John Gossman describes what happened when they open sourced .net. At first, they didn't really think they'd get much back. From 997bc43e7478f9a4eeadf07143c4d77e64ede8d5 Mon Sep 17 00:00:00 2001 From: DarkSun Date: Sat, 24 Aug 2019 00:51:33 +0800 Subject: [PATCH 06/58] =?UTF-8?q?=E9=80=89=E9=A2=98:=2020190823=20Managing?= =?UTF-8?q?=20credentials=20with=20KeePassXC?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit sources/tech/20190823 Managing credentials with KeePassXC.md --- ...823 Managing credentials with KeePassXC.md | 122 ++++++++++++++++++ 1 file changed, 122 insertions(+) create mode 100644 sources/tech/20190823 Managing credentials with KeePassXC.md diff --git a/sources/tech/20190823 Managing credentials with KeePassXC.md b/sources/tech/20190823 Managing credentials with KeePassXC.md new file mode 100644 index 0000000000..9e48eceb3f --- /dev/null +++ b/sources/tech/20190823 Managing credentials with KeePassXC.md @@ -0,0 +1,122 @@ +[#]: collector: (lujun9972) +[#]: translator: ( ) +[#]: reviewer: ( ) +[#]: publisher: ( ) +[#]: url: ( ) +[#]: subject: (Managing credentials with KeePassXC) +[#]: via: (https://fedoramagazine.org/managing-credentials-with-keepassxc/) +[#]: author: (Marco Sarti https://fedoramagazine.org/author/msarti/) + +Managing credentials with KeePassXC +====== + +![][1] + +A [previous article][2] discussed password management tools that use server-side technology. These tools are very interesting and suitable for a cloud installation. +In this article we will talk about KeePassXC, a simple multi-platform open source software that uses a local file as a database. +The main advantage of this type of password management is simplicity. No server-side technology expertise is required and can therefore be used by any type of user. + +### Introducing KeePassXC + +KeePassXC is an open source cross platform password manager: its development started as a fork of KeePassX, a good product but with a not very active development. It saves the secrets in an encrypted database with AES algorithm using 256 bit key, this makes it reasonably safe to save the database in a cloud drive storage such as pCloud or Dropbox. + +In addition to the passwords, KeePassXC allows you to save various information and attachments in the encrypted wallet. It also has a valid password generator that helps the user to correctly manage his credentials. + +### Installation + +The program is available both in the standard Fedora repository and in the Flathub repository. Unfortunately the integration with the browser does not work with the application running in the sandbox, so I suggest to install the program via dnf: +``` + +``` + +sudo dnf install keepassxc +``` + +``` + +### Creating your wallet + +To create a new database there are two important steps: + + * Choose the encryption settings: the default settings are reasonably safe, increasing the transform rounds also increases the decryption time. + * Choose the master key and additional protections: the master key must be easy to remember (if you lose it your wallet is lost!) but strong enough, a passphrase with at least 4 random words can be a good choice. As additional protection you can choose a key file (remember: you must always have it available otherwise you cannot open the wallet) and / or a YubiKey hardware key. + + + +![][3] + +![][4] + +The database file will be saved to the file system. If you want to share with other computers / devices you can save it on a USB key or in a cloud storage like pCloud or Dropbox. Of course, if you choose a cloud storage, a particularly strong master password is recommended, better if accompanied by additional protection. + +### Creating your first entry + +Once the database has been created, you can start creating your first entry. For a web login specify a username, password and url in the Entry tab. Optionally you can specify an expiration date for the credentials based on your personal policy: also by pressing the button on the right the favicon of the site is downloaded and associated as an icon of the entry, this is a nice feature. + +![][5] + +![][6] + +KeePassXC also offers a good password / passphrase generator, you can choose length and complexity and check the degree of resistance to a brute force attack: + +![][7] + +### Browser integration + +KeePassXC has an extension available for all major browsers. The extension allows you to fill in the login information for all the entries whose URL is specified. + +Browser integration must be enabled on KeePassXC (Tools menu -> Settings) specifying which browsers you intend to use: + +![][8] + +Once the extension is installed, it is necessary to create a connection with the database. To do this, press the extension button and then the Connect button: if the database is open and unlocked the extension will create an association key and save it in the database, the key is unique to the browser so I suggest naming it appropriately : + +![][9] + +When you reach the login page specified in the Url field and the database is unlocked, the extension will offer you all the credentials you have associated with that page: + +![][10] + +In this way, browsing with KeePassXC running you will have your internet credentials available without necessarily saving them in the browser. + +### SSH agent integration + +Another interesting feature of KeePassXC is the integration with SSH. If you have ssh-agent running KeePassXC is able to interact and add the ssh keys that you have uploaded as attachments to your entries. + +First of all in the general settings (Tools menu -> Settings) you have to enable the ssh agent and restart the program: + +![][11] + +At this point it is required to upload your ssh key pair as an attachment to your entry. Then in the “SSH agent” tab select the private key in the attachment drop-down list, the public key will be populated automatically. Don’t forget to select the two checkboxes above to allow the key to be added to the agent when the database is opened / unlocked and removed when the database is closed / locked: + +![][12] + +Now with the database open and unlocked you can log in ssh using the keys saved in your wallet. + +The only limitation is in the maximum number of keys that can be added to the agent: ssh servers do not accept by default more than 5 login attempts, for security reasons it is not recommended to increase this value. + +-------------------------------------------------------------------------------- + +via: https://fedoramagazine.org/managing-credentials-with-keepassxc/ + +作者：[Marco Sarti][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://fedoramagazine.org/author/msarti/ +[b]: https://github.com/lujun9972 +[1]: https://fedoramagazine.org/wp-content/uploads/2019/08/keepassxc-816x345.png +[2]: https://fedoramagazine.org/manage-your-passwords-with-bitwarden-and-podman/ +[3]: https://fedoramagazine.org/wp-content/uploads/2019/08/Screenshot-from-2019-08-17-07-33-27.png +[4]: https://fedoramagazine.org/wp-content/uploads/2019/08/Screenshot-from-2019-08-17-07-48-21.png +[5]: https://fedoramagazine.org/wp-content/uploads/2019/08/Screenshot-from-2019-08-17-08-30-07.png +[6]: https://fedoramagazine.org/wp-content/uploads/2019/08/Screenshot-from-2019-08-17-08-43-11.png +[7]: https://fedoramagazine.org/wp-content/uploads/2019/08/Screenshot-from-2019-08-17-08-49-22.png +[8]: https://fedoramagazine.org/wp-content/uploads/2019/08/Screenshot-from-2019-08-17-09-48-09.png +[9]: https://fedoramagazine.org/wp-content/uploads/2019/08/Screenshot-from-2019-08-17-09-05-57.png +[10]: https://fedoramagazine.org/wp-content/uploads/2019/08/Screenshot-from-2019-08-17-09-13-29.png +[11]: https://fedoramagazine.org/wp-content/uploads/2019/08/Screenshot-from-2019-08-17-09-47-21.png +[12]: https://fedoramagazine.org/wp-content/uploads/2019/08/Screenshot-from-2019-08-17-09-46-35.png From 54d4dbab600e6d75744a67333f22287781b1f5a5 Mon Sep 17 00:00:00 2001 From: DarkSun Date: Sat, 24 Aug 2019 00:52:32 +0800 Subject: [PATCH 07/58] =?UTF-8?q?=E9=80=89=E9=A2=98:=2020190823=20The=20Li?= =?UTF-8?q?nux=20kernel:=20Top=205=20innovations?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit sources/tech/20190823 The Linux kernel- Top 5 innovations.md --- ...823 The Linux kernel- Top 5 innovations.md | 105 ++++++++++++++++++ 1 file changed, 105 insertions(+) create mode 100644 sources/tech/20190823 The Linux kernel- Top 5 innovations.md diff --git a/sources/tech/20190823 The Linux kernel- Top 5 innovations.md b/sources/tech/20190823 The Linux kernel- Top 5 innovations.md new file mode 100644 index 0000000000..95e35bc309 --- /dev/null +++ b/sources/tech/20190823 The Linux kernel- Top 5 innovations.md @@ -0,0 +1,105 @@ +[#]: collector: (lujun9972) +[#]: translator: ( ) +[#]: reviewer: ( ) +[#]: publisher: ( ) +[#]: url: ( ) +[#]: subject: (The Linux kernel: Top 5 innovations) +[#]: via: (https://opensource.com/article/19/8/linux-kernel-top-5-innovations) +[#]: author: (Seth Kenlon https://opensource.com/users/sethhttps://opensource.com/users/mhaydenhttps://opensource.com/users/mralexjuarez) + +The Linux kernel: Top 5 innovations +====== +Want to know what the actual (not buzzword) innovations are when it +comes to the Linux kernel? Read on. +![Penguin with green background][1] + +The word _innovation_ gets bandied about in the tech industry almost as much as _revolution_, so it can be difficult to differentiate hyperbole from something that’s actually exciting. The Linux kernel has been called innovative, but then again it’s also been called the biggest hack in modern computing, a monolith in a micro world. + +Setting aside marketing and modeling, Linux is arguably the most popular kernel of the open source world, and it’s introduced some real game-changers over its nearly 30-year life span. + +### Cgroups (2.6.24) + +Back in 2007, Paul Menage and Rohit Seth got the esoteric [_control groups_ (cgroups)][2] feature added to the kernel (the current implementation of cgroups is a rewrite by Tejun Heo.) This new technology was initially used as a way to ensure, essentially, quality of service for a specific set of tasks. + +For example, you could create a control group definition (cgroup) for all tasks associated with your web server, another cgroup for routine backups, and yet another for general operating system requirements. You could then control a percentage of resources for each cgroup, such that your OS and web server gets the bulk of system resources while your backup processes have access to whatever is left. + +What cgroups has become most famous for, though, is its role as the technology driving the cloud today: containers. In fact, cgroups were originally named [process containers][3]. It was no great surprise when they were adopted by projects like [LXC][4], [CoreOS][5], and Docker. + +The floodgates being opened, the term _containers_ justly became synonymous with Linux, and the concept of microservice-style cloud-based “apps” quickly became the norm. These days, it’s hard to get away from cgroups, they’re so prevalent. Every large-scale infrastructure (and probably your laptop, if you run Linux) takes advantage of cgroups in a meaningful way, making your computing experience more manageable and more flexible than ever. + +For example, you might already have installed [Flathub][6] or [Flatpak][7] on your computer, or maybe you’ve started using [Kubernetes][8] and/or [OpenShift][9] at work. Regardless, if the term “containers” is still hazy for you, you can gain a hands-on understanding of containers from [Behind the scenes with Linux containers][10]. + +### LKMM (4.17) + +In 2018, the hard work of Jade Alglave, Alan Stern, Andrea Parri, Luc Maranget, Paul McKenney, and several others, got merged into the mainline Linux kernel to provide formal memory models. The Linux Kernel Memory [Consistency] Model (LKMM) subsystem is a set of tools describing the Linux memory coherency model, as well as producing _litmus tests_ (**klitmus**, specifically) for testing. + +As systems become more complex in physical design (more CPU cores added, cache and RAM grow, and so on), the harder it is for them to know which address space is required by which CPU, and when. For example, if CPU0 needs to write data to a shared variable in memory, and CPU1 needs to read that value, then CPU0 must write before CPU1 attempts to read. Similarly, if values are written in one order to memory, then there’s an expectation that they are also read in that same order, regardless of which CPU or CPUs are doing the reading. + +Even on a single CPU, memory management requires a specific task order. A simple action such as **x = y** requires a CPU to load the value of **y** from memory, and then store that value in **x**. Placing the value stored in **y** into the **x** variable cannot occur _before_ the CPU has read the value from memory. There are also address dependencies: **x[n] = 6** requires that **n** is loaded before the CPU can store the value of six. + +LKMM helps identify and trace these memory patterns in code. It does this in part with a tool called **herd**, which defines the constraints imposed by a memory model (in the form of logical axioms), and then enumerates all possible outcomes consistent with these constraints. + +### Low-latency patch (2.6.38) + +Long ago, in the days before 2011, if you wanted to do "serious" [multimedia work on Linux][11], you had to obtain a low-latency kernel. This mostly applied to [audio recording][12] while adding lots of real-time effects (such as singing into a microphone and adding reverb, and hearing your voice in your headset with no noticeable delay). There were distributions, such as [Ubuntu Studio][13], that reliably provided such a kernel, so in practice it wasn't much of a hurdle, just a significant caveat when choosing your distribution as an artist. + +However, if you weren’t using Ubuntu Studio, or you had some need to update your kernel before your distribution got around to it, you had to go to the rt-patches web page, download the kernel patches, apply them to your kernel source code, compile, and install manually. + +And then, with the release of kernel version 2.6.38, this process was all over. The Linux kernel suddenly, as if by magic, had low-latency code (according to benchmarks, latency decreased by a factor of 10, at least) built-in by default. No more downloading patches, no more compiling. Everything just worked, and all because of a small 200-line patch implemented by Mike Galbraith. + +For open source multimedia artists the world over, it was a game-changer. Things got so good from 2011 on that in 2016, I challenged myself to [build a Digital Audio Workstation (DAW) on a Raspberry Pi v1 (model B)][14] and found that it worked surprisingly well. + +### RCU (2.5) + +RCU, or Read-Copy-Update, is a system defined in computer science that allows multiple processor threads to read from shared memory. It does this by deferring updates, but also marking them as updated, to ensure that the data’s consumers read the latest version. Effectively, this means that reads happen concurrently with updates. + +The typical RCU cycle is a little like this: + + 1. Remove pointers to data to prevent other readers from referencing it. + 2. Wait for readers to complete their critical processes. + 3. Reclaim the memory space. + + + +Dividing the update stage into removal and reclamation phases means the updater performs the removal immediately while deferring reclamation until all active readers are complete (either by blocking them or by registering a callback to be invoked upon completion). + +While the concept of read-copy-update was not invented for the Linux kernel, its implementation in Linux is a defining example of the technology. + +### Collaboration (0.01) + +The final answer to the question of what the Linux kernel innovated will always be, above all else, collaboration. Call it good timing, call it technical superiority, call it hackability, or just call it open source, but the Linux kernel and the many projects that it enabled is a glowing example of collaboration and cooperation. + +And it goes well beyond just the kernel. People from all walks of life have contributed to open source, arguably _because_ of the Linux kernel. The Linux was, and remains to this day, a major force of [Free Software][15], inspiring users to bring their code, art, ideas, or just themselves, to a global, productive, and diverse community of humans. + +### What’s your favorite innovation? + +This list is biased toward my own interests: containers, non-uniform memory access (NUMA), and multimedia. I’ve surely left your favorite kernel innovation off the list. Tell me about it in the comments! + +-------------------------------------------------------------------------------- + +via: https://opensource.com/article/19/8/linux-kernel-top-5-innovations + +作者：[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/sethhttps://opensource.com/users/mhaydenhttps://opensource.com/users/mralexjuarez +[b]: https://github.com/lujun9972 +[1]: https://opensource.com/sites/default/files/styles/image-full-size/public/lead-images/linux_penguin_green.png?itok=ENdVzW22 (Penguin with green background) +[2]: https://en.wikipedia.org/wiki/Cgroups +[3]: https://lkml.org/lkml/2006/10/20/251 +[4]: https://linuxcontainers.org +[5]: https://coreos.com/ +[6]: http://flathub.org +[7]: http://flatpak.org +[8]: http://kubernetes.io +[9]: https://www.redhat.com/sysadmin/learn-openshift-minishift +[10]: https://opensource.com/article/18/11/behind-scenes-linux-containers +[11]: http://slackermedia.info +[12]: https://opensource.com/article/17/6/qtractor-audio +[13]: http://ubuntustudio.org +[14]: https://opensource.com/life/16/3/make-music-raspberry-pi-milkytracker +[15]: http://fsf.org From 709488ce25c7f2d8aafdd50256b81985d2994627 Mon Sep 17 00:00:00 2001 From: DarkSun Date: Sat, 24 Aug 2019 00:52:46 +0800 Subject: [PATCH 08/58] =?UTF-8?q?=E9=80=89=E9=A2=98:=2020190823=20Dive=20i?= =?UTF-8?q?nto=20the=20life=20and=20legacy=20of=20Alan=20Turing:=205=20boo?= =?UTF-8?q?ks=20and=20more?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit sources/tech/20190823 Dive into the life and legacy of Alan Turing- 5 books and more.md --- ...legacy of Alan Turing- 5 books and more.md | 97 +++++++++++++++++++ 1 file changed, 97 insertions(+) create mode 100644 sources/tech/20190823 Dive into the life and legacy of Alan Turing- 5 books and more.md diff --git a/sources/tech/20190823 Dive into the life and legacy of Alan Turing- 5 books and more.md b/sources/tech/20190823 Dive into the life and legacy of Alan Turing- 5 books and more.md new file mode 100644 index 0000000000..92b6cfe2b2 --- /dev/null +++ b/sources/tech/20190823 Dive into the life and legacy of Alan Turing- 5 books and more.md @@ -0,0 +1,97 @@ +[#]: collector: (lujun9972) +[#]: translator: ( ) +[#]: reviewer: ( ) +[#]: publisher: ( ) +[#]: url: ( ) +[#]: subject: (Dive into the life and legacy of Alan Turing: 5 books and more) +[#]: via: (https://opensource.com/article/19/8/who-was-alan-turing) +[#]: author: (Joshua Allen Holm https://opensource.com/users/holmja) + +Dive into the life and legacy of Alan Turing: 5 books and more +====== +Turing's theories had a huge impact on the development of the field of +computer science. +![Fire fist breaking glass][1] + +Recently, Bank of England Governor, Mark Carney, [announced][2] that Alan Turning would be the new face on the UK£ 50 note. The name _Alan Turing_ should be familiar to anyone in open source communities: His theories had a huge impact on the development of the field of computer science, and his code-breaking work at [Bletchley Park][3] during World War II was the focus of the 2014 film, [_The Imitation Game_][4], which starred Benedict Cumberbatch as Alan Turing. + +Another well-known fact about Turing was his conviction for "gross indecency" because of his homosexuality, and the posthumous [apology][5] and [pardon][6] issued over more a half a decade after Turing’s death. + +But beyond all of this, who was Alan Turing? + +Here are five books and archival material that delve deeply into the life and legacy of Alan Turing. Collectively, these resources cover his life, both professional and personal, and work others have done to build upon Turing’s ideas. Individually, or collectively, these works allow the reader to learn who Alan Turing was beyond just a few well-known, broad-stroke themes. + +### Alan Turing: The Enigma + +![Alan Turing: The Enigma][7] + +One of the most expansive biographies of Alan Turing, [_Alan Turing: The Enigma_][8], by Andrew Hodges, states on its cover that it is the inspiration for the film _The Imitation Game_. Weighing in at over 750 pages, this is no quick read, but it covers much of Turing’s life. The only drawback is the fact that the first edition was published in 1983. Even the updated edition does not make use of information that has become declassified in the past few years. + +Despite that, if you only read one book from this list, _Alan Turing: The Enigma_ is still an excellent choice. Hodges’s work is the gold standard when it comes to Alan Turing biographies. + +### The Imitation Game: Alan Turing Decoded + +![The Imitation Game: Alan Turing Decoded][9] + +_[The Imitation Game: Alan Turing Decoded][10]_, by Jim Ottaviani and illustrated by Leland Purvis, presents the life of Alan Turing as a graphic novel. Well told and partnered with lovely artwork, this book covers all the major facets of Alan Turing’s life but lacks the depth of a biography like Hodges’. + +That is not to say that there is anything wrong or deficient with Ottaviani’s writing, just that the graphic novel form requires a more streamlined narrative. For anyone wanting a quick introduction to Turing, this graphic novel is the quickest way to read an overview of Turing’s life and works. + +### Prof: Alan Turing Decoded + +![Prof: Alan Turing Decoded][11] + +Written by Alan Turing’s nephew, Durmot Turing, _[Prof: Alan Turing Decoded][12]_ draws upon material from the family, plus declassified material that was not available when Hodges researched his book. This shorter biography provides a more personal look at Alan Turing’s life while still being scholarly. + +Dermot Turing does an excellent job of telling the story of Alan Turing the man, not the myth born from public perceptions based on various dramatic interpretations. _Prof: Alan Turing Decoded_ is an interesting biography owing to its use of letters from members of the Turing family, including Alan Turing himself. + +### The Turing Digital Archive + +Nothing beats archival materials for really learning about a subject. Biographers have done masterful jobs at turning primary sources about Alan Turing’s life into compelling biographies, but reading Turing’s own writings and exploring other material in [The Turing Digital Archive][13]—maintained by King’s College, Cambridge—provides a more intimate look at Turing’s life and works. This archive contains Turing’s scholar papers, personal correspondence, photographs, and more. The collection is well-organized and the site is easy to use, making it simple for anyone to conduct their own archival research about the life of Alan Turing. + +### Turing’s Cathedral + +![Turing’s Cathedral][14] + +In [_Turing’s Cathedral_][15], George Dyson explores the efforts by John von Neumann and his collaborators to construct a computer based on Alan Turing’s theory of a Universal Machine. John von Neumann made many, many contributions to computer science, which are also covered in this book, but the transition of Alan Turing’s Universal Machine from theory to practice is the facet that concerns readers wishing to learn more about Alan Turing’s legacy. + +_Turing’s Cathedral_ is the story of von Neumann constructing one of the earliest modern computers, but it is, like all modern computing, the story of Alan Turing’s influence on everything that developed from his theories. + +### Turing’s Vision: The Birth of Computer Science + +![Turing’s Vision: The Birth of Computer Science][16] + +[_Turing’s Vision: The Birth of Computer Science_][17], like its title states, explores the birth of the field of computer science. Full of diagrams and complex examples, this book might not be for everyone, but it does a masterful job of explaining computer science concepts and Turing’s place in the birth of the discipline. Chris Bernhardt does an excellent job of weaving together the biographical aspects with the technical, but the technical material can be very, very technical. There are mathematical proofs and other things that make this book a poor choice for the non-technical reader, but an excellent choice for someone with a background in computer science. + +For a very technical book, it is an enjoyable read. The biographical aspects are not as broad or as deep as pure biographies, but it is the synthesis of the biographical and the technical that make this book so interesting. + +-------------------------------------------------------------------------------- + +via: https://opensource.com/article/19/8/who-was-alan-turing + +作者：[Joshua Allen Holm][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/holmja +[b]: https://github.com/lujun9972 +[1]: https://opensource.com/sites/default/files/styles/image-full-size/public/lead-images/fire_fist_break_glass_smash_fail.jpg?itok=S6hQNLtB (Fire fist breaking glass) +[2]: https://www.bankofengland.co.uk/news/2019/july/50-pound-banknote-character-announcement +[3]: https://www.bletchleypark.org.uk/ +[4]: https://www.imdb.com/title/tt2084970/ +[5]: https://www.telegraph.co.uk/news/politics/gordon-brown/6170112/Gordon-Brown-Im-proud-to-say-sorry-to-a-real-war-hero.html +[6]: https://www.bbc.com/news/technology-25495315 +[7]: https://opensource.com/sites/default/files/uploads/alan_turing-_the_enigma_125.jpeg (Alan Turing: The Enigma) +[8]: https://press.princeton.edu/titles/10413.html +[9]: https://opensource.com/sites/default/files/uploads/the_imitation_game-_alan_turing_decoded_125.jpg (The Imitation Game: Alan Turing Decoded) +[10]: https://www.abramsbooks.com/product/imitation-game_9781419718939/ +[11]: https://opensource.com/sites/default/files/uploads/prof-_alan_turing_decoded_125.jpg (Prof: Alan Turing Decoded) +[12]: https://dermotturing.com/my-recent-books/alan-turing/ +[13]: http://www.turingarchive.org/ +[14]: https://opensource.com/sites/default/files/uploads/turing_s_cathedral_125.jpg (Turing’s Cathedral) +[15]: https://www.penguinrandomhouse.com/books/44425/turings-cathedral-by-george-dyson/9781400075997/ +[16]: https://opensource.com/sites/default/files/uploads/turing_s_vision-_the_birth_of_computer_science_125.jpg (Turing’s Vision: The Birth of Computer Science) +[17]: https://mitpress.mit.edu/books/turings-vision From ff1c9e4ca0cc5009c480cf99fbc06b999e808205 Mon Sep 17 00:00:00 2001 From: DarkSun Date: Sat, 24 Aug 2019 00:53:04 +0800 Subject: [PATCH 09/58] =?UTF-8?q?=E9=80=89=E9=A2=98:=2020190823=20The=20li?= =?UTF-8?q?fecycle=20of=20Linux=20kernel=20testing?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit sources/tech/20190823 The lifecycle of Linux kernel testing.md --- ...3 The lifecycle of Linux kernel testing.md | 78 +++++++++++++++++++ 1 file changed, 78 insertions(+) create mode 100644 sources/tech/20190823 The lifecycle of Linux kernel testing.md diff --git a/sources/tech/20190823 The lifecycle of Linux kernel testing.md b/sources/tech/20190823 The lifecycle of Linux kernel testing.md new file mode 100644 index 0000000000..65bab32536 --- /dev/null +++ b/sources/tech/20190823 The lifecycle of Linux kernel testing.md @@ -0,0 +1,78 @@ +[#]: collector: (lujun9972) +[#]: translator: ( ) +[#]: reviewer: ( ) +[#]: publisher: ( ) +[#]: url: ( ) +[#]: subject: (The lifecycle of Linux kernel testing) +[#]: via: (https://opensource.com/article/19/8/linux-kernel-testing) +[#]: author: (Major Hayden https://opensource.com/users/mhaydenhttps://opensource.com/users/mhaydenhttps://opensource.com/users/marcobravohttps://opensource.com/users/mhayden) + +The lifecycle of Linux kernel testing +====== +The Continuous Kernel Integration (CKI) project aims to prevent bugs +from entering the Linux kernel. +![arrows cycle symbol for failing faster][1] + +In _[Continuous integration testing for the Linux kernel][2]_, I wrote about the [Continuous Kernel Integration][3] (CKI) project and its mission to change how kernel developers and maintainers work. This article is a deep dive into some of the more technical aspects of the project and how all the pieces fit together. + +### It all starts with a change + +Every exciting feature, improvement, and bug in the kernel starts with a change proposed by a developer. These changes appear on myriad mailing lists for different kernel repositories. Some repositories focus on certain subsystems in the kernel, such as storage or networking, while others focus on broad aspects of the kernel. The CKI project springs into action when developers propose a change, or patchset, to the kernel or when a maintainer makes changes in the repository itself. + +The CKI project maintains triggers that monitor these patchsets and take action. Software projects such as [Patchwork][4] make this process much easier by collating multi-patch contributions into a single patch series. This series travels as a unit through the CKI system and allows for publishing a single report on the series. + +Other triggers watch the repository for changes. This occurs when kernel maintainers merge patchsets, revert patches, or create new tags. Testing these critical changes ensures that developers always have a solid baseline to use as a foundation for writing new patches. + +All of these changes make their way into a GitLab pipeline and pass through multiple stages and multiple systems. + +### Prepare the build + +Everything starts with getting the source ready for compile time. This requires cloning the repository, applying the patchset proposed by the developer, and generating a kernel config file. These config files have thousands of options that turn features on or off, and config files differ incredibly between different system architectures. For example, a fairly standard x86_64 system may have a ton of options available in its config file, but an s390x system (IBM zSeries mainframes) likely has much fewer options. Some options might make sense on that mainframe but they have no purpose on a consumer laptop. + +The kernel moves forward and transforms into a source artifact. The artifact contains the entire repository, with patches applied, and all kernel configuration files required for compiling. Upstream kernels move on as a tarball, while Red Hat kernels become a source RPM for the next step. + +### Piles of compiles + +Compiling the kernel turns the source code into something that a computer can boot up and use. The config file describes what to build, scripts in the kernel describe how to build it, and tools on the system (like GCC and glibc) do the building. This process takes a while to complete, but the CKI project needs it done quickly for four architectures: aarch64 (64-bit ARM), ppc64le (POWER), s390x (IBM zSeries), and x86_64. It's important that we compile kernels quickly so that we keep our backlog manageable and developers receive prompt feedback. + +Adding more CPUs provides plenty of speed improvements, but every system has its limits. The CKI project compiles kernels within containers in an OpenShift deployment; although OpenShift allows for tons of scalability, the deployment still has a finite number of CPUs available. The CKI team allocates 20 virtual CPUs for compiling each kernel. With four architectures involved, this balloons to 80 CPUs! + +Another speed increase comes from a tool called [ccache][5]. Kernel development moves quickly, but a large amount of the kernel remains unchanged even between multiple releases. The ccache tool caches the built objects (small pieces of the overall kernel) during the compile on a disk. When another kernel compile comes along later, ccache looks for unchanged pieces of the kernel that it saw before. Ccache pulls the cached object from the disk and reuses it. This allows for faster compiles and lower overall CPU usage. Kernels that took 20 minutes to compile now race to the finish line in less than a few minutes. + +### Testing time + +The kernel moves onto its last step: testing on real hardware. Each kernel boots up on its native architecture using Beaker, and myriad tests begin poking it to find problems. Some tests look for simple problems, such as issues with containers or error messages on boot-up. Other tests dive deep into various kernel subsystems to find regressions in system calls, memory allocation, and threading. + +Large testing frameworks, such as the [Linux Test Project][6] (LTP), contain tons of tests that look for troublesome regressions in the kernel. Some of these regressions could roll back critical security fixes, and there are tests to ensure those improvements remain in the kernel. + +One critical step remains when tests finish: reporting. Kernel developers and maintainers need a concise report that tells them exactly what worked, what did not work, and how to get more information. Each CKI report contains details about the source code used, the compile parameters, and the testing output. That information helps developers know where to begin looking to fix an issue. Also, it helps maintainers know when a patchset needs to be held for another look before a bug makes its way into their kernel repository. + +### Summary + +The CKI project team strives to prevent bugs from entering the Linux kernel by providing timely, automated feedback to kernel developers and maintainers. This work makes their job easier by finding the low-hanging fruit that leads to kernel bugs, security issues, and performance problems. + +* * * + +_To learn more, you can attend the [CKI Hackfest][7] on September 12-13 following the [Linux Plumbers Conference][8] September 9-11 in Lisbon, Portugal._ + +-------------------------------------------------------------------------------- + +via: https://opensource.com/article/19/8/linux-kernel-testing + +作者：[Major Hayden][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/mhaydenhttps://opensource.com/users/mhaydenhttps://opensource.com/users/marcobravohttps://opensource.com/users/mhayden +[b]: https://github.com/lujun9972 +[1]: https://opensource.com/sites/default/files/styles/image-full-size/public/lead-images/fail_progress_cycle_momentum_arrow.png?itok=q-ZFa_Eh (arrows cycle symbol for failing faster) +[2]: https://opensource.com/article/19/6/continuous-kernel-integration-linux +[3]: https://cki-project.org/ +[4]: https://github.com/getpatchwork/patchwork +[5]: https://ccache.dev/ +[6]: https://linux-test-project.github.io +[7]: https://cki-project.org/posts/hackfest-agenda/ +[8]: https://www.linuxplumbersconf.org/ From 95df1d8c5ac9f78d6824fcc8017d234d3a9e11be Mon Sep 17 00:00:00 2001 From: DarkSun Date: Sat, 24 Aug 2019 00:53:42 +0800 Subject: [PATCH 10/58] =?UTF-8?q?=E9=80=89=E9=A2=98:=2020190822=20Semicond?= =?UTF-8?q?uctor=20startup=20Cerebras=20Systems=20launches=20massive=20AI?= =?UTF-8?q?=20chip?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit sources/talk/20190822 Semiconductor startup Cerebras Systems launches massive AI chip.md --- ...rebras Systems launches massive AI chip.md | 57 +++++++++++++++++++ 1 file changed, 57 insertions(+) create mode 100644 sources/talk/20190822 Semiconductor startup Cerebras Systems launches massive AI chip.md diff --git a/sources/talk/20190822 Semiconductor startup Cerebras Systems launches massive AI chip.md b/sources/talk/20190822 Semiconductor startup Cerebras Systems launches massive AI chip.md new file mode 100644 index 0000000000..91685c8501 --- /dev/null +++ b/sources/talk/20190822 Semiconductor startup Cerebras Systems launches massive AI chip.md @@ -0,0 +1,57 @@ +[#]: collector: (lujun9972) +[#]: translator: ( ) +[#]: reviewer: ( ) +[#]: publisher: ( ) +[#]: url: ( ) +[#]: subject: (Semiconductor startup Cerebras Systems launches massive AI chip) +[#]: via: (https://www.networkworld.com/article/3433617/semiconductor-startup-cerebras-systems-launches-massive-ai-chip.html) +[#]: author: (Andy Patrizio https://www.networkworld.com/author/Andy-Patrizio/) + +Semiconductor startup Cerebras Systems launches massive AI chip +====== + +![Cerebras][1] + +There are a host of different AI-related solutions for the data center, ranging from add-in cards to dedicated servers, like the Nvidia DGX-2. But a startup called Cerebras Systems has its own server offering that relies on a single massive processor rather than a slew of small ones working in parallel. + +Cerebras has taken the wraps off its Wafer Scale Engine (WSE), an AI chip that measures 8.46x8.46 inches, making it almost the size of an iPad and more than 50 times larger than a CPU or GPU. A typical CPU or GPU is about the size of a postage stamp. + +[Now see how AI can boost data-center availability and efficiency.][2] + +Cerebras won’t sell the chips to ODMs due to the challenges of building and cooling such a massive chip. Instead, it will come as part of a complete server to be installed in data centers, which it says will start shipping in October. + +The logic behind the design is that AI requires huge amounts of data just to run a test and current technology, even GPUs, are not fast or powerful enough. So Cerebras supersized the chip. + +The numbers are just incredible. The company’s WSE chip has 1.2 trillion transistors, 400,000 computing cores and 18 gigabytes of memory. A typical PC processor has about 2 billion transistors, four to six cores and a few megabytes of cache memory. Even a high-end GPU has 21 billion transistors and a few thousand cores. + +The 400,000 cores on the WSE are connected via the Swarm communication fabric in a 2D mesh with 100 Pb/s of bandwidth. The WSE has 18 GB of on-chip memory, all accessible within a single clock cycle, and provides 9 PB/s memory bandwidth. This is 3000x more capacity and 10,000x greater bandwidth than the best Nvidia has to offer. More to the point it eliminates the need to move data in and out of memory to and from the CPU. + +“A vast array of programmable cores provides cluster-scale compute on a single chip. High-speed memory close to each core ensures that cores are always occupied doing calculations. And by connecting everything on-die, communication is many thousands of times faster than what is possible with off-chip technologies like InfiniBand,” the company said in a [blog post][3] announcing the processor. + +The cores are called Sparse Linear Algebra Cores, or SLA. They are optimized for the sparse linear algebra that is fundamental to neural network calculation. These cores are designed specifically for AI work. They are small and fast, contain no caches, and have eliminated other features and overheads that are needed in general purpose cores but play no useful role in a deep learning processor. + +The chip is the brainchild of Andrew Feldman, who created the SeaMicro high density Atom-based server a decade ago as an alternative to overpowered Xeons for doing simple tasks like file and print or serving LAMP stacks. Feldman is a character, one of the more interesting people [I’ve interviewed][4]. He definitely thinks outside the box. + +Feldman sold SeaMicro to AMD for $334 million in 2012, which turned out to be a colossal waste of money on AMD’s part, as the product shortly disappeared from the market. Since then he’s raised $100 million in VC money. + +Join the Network World communities on [Facebook][5] and [LinkedIn][6] to comment on topics that are top of mind. + +-------------------------------------------------------------------------------- + +via: https://www.networkworld.com/article/3433617/semiconductor-startup-cerebras-systems-launches-massive-ai-chip.html + +作者：[Andy Patrizio][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/Andy-Patrizio/ +[b]: https://github.com/lujun9972 +[1]: https://images.idgesg.net/images/article/2019/08/cerebras-wafer-scale-engine-100809084-large.jpg +[2]: https://www.networkworld.com/article/3274654/ai-boosts-data-center-availability-efficiency.html +[3]: https://www.cerebras.net/hello-world/ +[4]: https://www.serverwatch.com/news/article.php/3887471/SeaMicro-Launches-an-AtomPowered-Cloud-Computing-Server.htm +[5]: https://www.facebook.com/NetworkWorld/ +[6]: https://www.linkedin.com/company/network-world From 69c6826bf1fe674fcd9d11939dbacc815d3d0454 Mon Sep 17 00:00:00 2001 From: DarkSun Date: Sat, 24 Aug 2019 00:53:58 +0800 Subject: [PATCH 11/58] =?UTF-8?q?=E9=80=89=E9=A2=98:=2020190822=20Things?= =?UTF-8?q?=20You=20Didn't=20Know=20About=20GNU=20Readline?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit sources/talk/20190822 Things You Didn-t Know About GNU Readline.md --- ...ings You Didn-t Know About GNU Readline.md | 136 ++++++++++++++++++ 1 file changed, 136 insertions(+) create mode 100644 sources/talk/20190822 Things You Didn-t Know About GNU Readline.md diff --git a/sources/talk/20190822 Things You Didn-t Know About GNU Readline.md b/sources/talk/20190822 Things You Didn-t Know About GNU Readline.md new file mode 100644 index 0000000000..189f1152b9 --- /dev/null +++ b/sources/talk/20190822 Things You Didn-t Know About GNU Readline.md @@ -0,0 +1,136 @@ +[#]: collector: (lujun9972) +[#]: translator: ( ) +[#]: reviewer: ( ) +[#]: publisher: ( ) +[#]: url: ( ) +[#]: subject: (Things You Didn't Know About GNU Readline) +[#]: via: (https://twobithistory.org/2019/08/22/readline.html) +[#]: author: (Two-Bit History https://twobithistory.org) + +Things You Didn't Know About GNU Readline +====== + +I sometimes think of my computer as a very large house. I visit this house every day and know most of the rooms on the ground floor, but there are bedrooms I’ve never been in, closets I haven’t opened, nooks and crannies that I’ve never explored. I feel compelled to learn more about my computer the same way anyone would feel compelled to see a room they had never visited in their own home. + +GNU Readline is an unassuming little software library that I relied on for years without realizing that it was there. Tens of thousands of people probably use it every day without thinking about it. If you use the Bash shell, every time you auto-complete a filename, or move the cursor around within a single line of input text, or search through the history of your previous commands, you are using GNU Readline. When you do those same things while using the command-line interface to Postgres (`psql`), say, or the Ruby REPL (`irb`), you are again using GNU Readline. Lots of software depends on the GNU Readline library to implement functionality that users expect, but the functionality is so auxiliary and unobtrusive that I imagine few people stop to wonder where it comes from. + +GNU Readline was originally created in the 1980s by the Free Software Foundation. Today, it is an important if invisible part of everyone’s computing infrastructure, maintained by a single volunteer. + +### Feature Replete + +The GNU Readline library exists primarily to augment any command-line interface with a common set of keystrokes that allow you to move around within and edit a single line of input. If you press `Ctrl-A` at a Bash prompt, for example, that will jump your cursor to the very beginning of the line, while pressing `Ctrl-E` will jump it to the end. Another useful command is `Ctrl-U`, which will delete everything in the line before the cursor. + +For an embarrassingly long time, I moved around on the command line by repeatedly tapping arrow keys. For some reason, I never imagined that there was a faster way to do it. Of course, no programmer familiar with a text editor like Vim or Emacs would deign to punch arrow keys for long, so something like Readline was bound to be created. Using Readline, you can do much more than just jump around—you can edit your single line of text as if you were using a text editor. There are commands to delete words, transpose words, upcase words, copy and paste characters, etc. In fact, most of Readline’s keystrokes/shortcuts are based on Emacs. Readline is essentially Emacs for a single line of text. You can even record and replay macros. + +I have never used Emacs, so I find it hard to remember what all the different Readline commands are. But one thing about Readline that is really neat is that you can switch to using a Vim-based mode instead. To do this for Bash, you can use the `set` builtin. The following will tell Readline to use Vim-style commands for the current shell: + +``` +$ set -o vi +``` + +With this option enabled, you can delete words using `dw` and so on. The equivalent to `Ctrl-U` in the Emacs mode would be `d0`. + +I was excited to try this when I first learned about it, but I’ve found that it doesn’t work so well for me. I’m happy that this concession to Vim users exists, and you might have more luck with it than me, particularly if you haven’t already used Readline’s default command keystrokes. My problem is that, by the time I heard about the Vim-based interface, I had already learned several Readline keystrokes. Even with the Vim option enabled, I keep using the default keystrokes by mistake. Also, without some sort of indicator, Vim’s modal design is awkward here—it’s very easy to forget which mode you’re in. So I’m stuck at a local maximum using Vim as my text editor but Emacs-style Readline commands. I suspect a lot of other people are in the same position. + +If you feel, not unreasonably, that both Vim and Emacs’ keyboard command systems are bizarre and arcane, you can customize Readline’s key bindings and make them whatever you like. This is not hard to do. Readline reads a `~/.inputrc` file on startup that can be used to configure various options and key bindings. One thing I’ve done is reconfigured `Ctrl-K`. Normally it deletes from the cursor to the end of the line, but I rarely do that. So I’ve instead bound it so that pressing `Ctrl-K` deletes the whole line, regardless of where the cursor is. I’ve done that by adding the following to `~/.inputrc`: + +``` +Control-k: kill-whole-line +``` + +Each Readline command (the documentation refers to them as _functions_) has a name that you can associate with a key sequence this way. If you edit `~/.inputrc` in Vim, it turns out that Vim knows the filetype and will help you by highlighting valid function names but not invalid ones! + +Another thing you can do with `~/.inputrc` is create canned macros by mapping key sequences to input strings. [The Readline manual][1] gives one example that I think is especially useful. I often find myself wanting to save the output of a program to a file, which means that I often append something like `> output.txt` to Bash commands. To save some time, you could make this a Readline macro: + +``` +Control-o: "> output.txt" +``` + +Now, whenever you press `Ctrl-O`, you’ll see that `> output.txt` gets added after your cursor on the command line. Neat! + +But with macros you can do more than just create shortcuts for strings of text. The following entry in `~/.inputrc` means that, every time I press `Ctrl-J`, any text I already have on the line is surrounded by `$(` and `)`. The macro moves to the beginning of the line with `Ctrl-A`, adds `$(`, then moves to the end of the line with `Ctrl-E` and adds `)`: + +``` +Control-j: "\C-a$(\C-e)" +``` + +This might be useful if you often need the output of one command to use for another, such as in: + +``` +$ cd $(brew --prefix) +``` + +The `~/.inputrc` file also allows you to set different values for what the Readline manual calls _variables_. These enable or disable certain Readline behaviors. You can use these variables to change, for example, how Readline auto-completion works or how the Readline history search works. One variable I’d recommend turning on is the `revert-all-at-newline` variable, which by default is off. When the variable is off, if you pull a line from your command history using the reverse search feature, edit it, but then decide to search instead for another line, the edit you made is preserved in the history. I find this confusing because it leads to lines showing up in your Bash command history that you never actually ran. So add this to your `~/.inputrc`: + +``` +set revert-all-at-newline on +``` + +When you set options or key bindings using `~/.inputrc`, they apply wherever the Readline library is used. This includes Bash most obviously, but you’ll also get the benefit of your changes in other programs like `irb` and `psql` too! A Readline macro that inserts `SELECT * FROM` could be useful if you often use command-line interfaces to relational databases. + +### Chet Ramey + +GNU Readline is today maintained by Chet Ramey, a Senior Technology Architect at Case Western Reserve University. Ramey also maintains the Bash shell. Both projects were first authored by a Free Software Foundation employee named Brian Fox beginning in 1988. But Ramey has been the sole maintainer since around 1994. + +Ramey told me via email that Readline, far from being an original idea, was created to implement functionality prescribed by the POSIX specification, which in the late 1980s had just been created. Many earlier shells, including the Korn shell and at least one version of the Unix System V shell, included line editing functionality. The 1988 version of the Korn shell (`ksh88`) provided both Emacs-style and Vi/Vim-style editing modes. As far as I can tell from [the manual page][2], the Korn shell would decide which mode you wanted to use by looking at the `VISUAL` and `EDITOR` environment variables, which is pretty neat. The parts of POSIX that specified shell functionality were closely modeled on `ksh88`, so GNU Bash was going to have to implement a similarly flexible line-editing system to stay compliant. Hence Readline. + +When Ramey first got involved in Bash development, Readline was a single source file in the Bash project directory. It was really just a part of Bash. Over time, the Readline file slowly moved toward becoming an independent project, though it was not until 1994 (with the 2.0 release of Readline) that Readline became a separate library entirely. + +Readline is closely associated with Bash, and Ramey usually pairs Readline releases with Bash releases. But as I mentioned above, Readline is a library that can be used by any software implementing a command-line interface. And it’s really easy to use. This is a simple example, but here’s how you would you use Readline in your own C program. The string argument to the `readline()` function is the prompt that you want Readline to display to the user: + +``` +#include +#include +#include "readline/readline.h" + +int main(int argc, char** argv) +{ + char* line = readline("my-rl-example> "); + printf("You entered: \"%s\"\n", line); + + free(line); + + return 0; +} +``` + +Your program hands off control to Readline, which is responsible for getting a line of input from the user (in such a way that allows the user to do all the fancy line-editing things). Once the user has actually submitted the line, Readline returns it to you. I was able to compile the above by linking against the Readline library, which I apparently have somewhere in my library search path, by invoking the following: + +``` +$ gcc main.c -lreadline +``` + +The Readline API is much more extensive than that single function of course, and anyone using it can tweak all sorts of things about the library’s behavior. Library users can even add new functions that end users can configure via `~/.inputrc`, meaning that Readline is very easy to extend. But, as far as I can tell, even Bash ultimately calls the simple `readline()` function to get input just as in the example above, though there is a lot of configuration beforehand. (See [this line][3] in the source for GNU Bash, which seems to be where Bash hands off responsibility for getting input to Readline.) + +Ramey has now worked on Bash and Readline for well over a decade. He has never once been compensated for his work—he is and has always been a volunteer. Bash and Readline continue to be actively developed, though Ramey said that Readline changes much more slowly than Bash does. I asked Ramey what it was like being the sole maintainer of software that so many people use. He said that millions of people probably use Bash without realizing it (because every Apple device runs Bash), which makes him worry about how much disruption a breaking change might cause. But he’s slowly gotten used to the idea of all those people out there. He said that he continues to work on Bash and Readline because at this point he is deeply invested and because he simply likes to make useful software available to the world. + +_You can find more information about Chet Ramey at [his website][4]._ + +_If you enjoyed this post, more like it come out every four weeks! Follow [@TwoBitHistory][5] on Twitter or subscribe to the [RSS feed][6] to make sure you know when a new post is out._ + +_Previously on TwoBitHistory…_ + +> Please enjoy my long overdue new post, in which I use the story of the BBC Micro and the Computer Literacy Project as a springboard to complain about Codecademy. +> +> — TwoBitHistory (@TwoBitHistory) [March 31, 2019][7] + +-------------------------------------------------------------------------------- + +via: https://twobithistory.org/2019/08/22/readline.html + +作者：[Two-Bit History][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://twobithistory.org +[b]: https://github.com/lujun9972 +[1]: https://tiswww.case.edu/php/chet/readline/readline.html +[2]: https://web.archive.org/web/20151105130220/http://www2.research.att.com/sw/download/man/man1/ksh88.html +[3]: https://github.com/bminor/bash/blob/9f597fd10993313262cab400bf3c46ffb3f6fd1e/parse.y#L1487 +[4]: https://tiswww.case.edu/php/chet/ +[5]: https://twitter.com/TwoBitHistory +[6]: https://twobithistory.org/feed.xml +[7]: https://twitter.com/TwoBitHistory/status/1112492084383092738?ref_src=twsrc%5Etfw From 71c8ac078a8214d32ef8c94d7a35fec4d5b76d8b Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?=E9=83=91?= Date: Sat, 24 Aug 2019 08:37:44 +0800 Subject: [PATCH 12/58] Translated --- ...ustomize Xfce and Give it a Modern Look.md | 146 ------------------ ...ustomize Xfce and Give it a Modern Look.md | 145 +++++++++++++++++ 2 files changed, 145 insertions(+), 146 deletions(-) delete mode 100644 sources/tech/20180727 4 Ways to Customize Xfce and Give it a Modern Look.md create mode 100644 translated/tech/20180727 4 Ways to Customize Xfce and Give it a Modern Look.md diff --git a/sources/tech/20180727 4 Ways to Customize Xfce and Give it a Modern Look.md b/sources/tech/20180727 4 Ways to Customize Xfce and Give it a Modern Look.md deleted file mode 100644 index bd91604a7f..0000000000 --- a/sources/tech/20180727 4 Ways to Customize Xfce and Give it a Modern Look.md +++ /dev/null @@ -1,146 +0,0 @@ -Translating by robsean -4 Ways to Customize Xfce and Give it a Modern Look -====== -**Brief: Xfce is a great lightweight desktop environment with one drawback. It looks sort of old. But you don’t have to stick with the default looks. Let’s see various ways you can customize Xfce to give it a modern and beautiful look.** - -![Customize Xfce desktop envirnment][1] - -To start with, Xfce is one of the most [popular desktop environments][2]. Being a lightweight DE, you can run Xfce on very low resource and it still works great. This is one of the reasons why many [lightweight Linux distributions][3] use Xfce by default. - -Some people prefer it even on a high-end device stating its simplicity, easy of use and non-resource hungry nature as the main reasons. - -[Xfce][4] is in itself minimal and provides just what you need. The one thing that bothers is its look and feel which feel old. However, you can easily customize Xfce to look modern and beautiful without reaching the limit where a Unity/GNOME session eats up system resources. - -### 4 ways to Customize Xfce desktop - -Let’s see some of the ways by which we can improve the look and feel of your Xfce desktop environment. - -The default Xfce desktop environment looks something like this : - -![Xfce default screen][5] - -As you can see, the default Xfce desktop is kinda boring. We will use some themes, icon packs and change the default dock to make it look fresh and a bit revealing. - -#### 1. Change themes in Xfce - -The first thing we will do is pick up a theme from [xfce-look.org][6]. My favorite Xfce theme is [XFCE-D-PRO][7]. - -You can download the theme from [here][8] and extract it somewhere. - -You can copy this extracted file to **.theme** folder in your home directory. If the folder is not present by default, you can create one and the same goes for icons which needs a **.icons** folder in the home directory. - -Open **Settings > Appearance > Style** to select the theme, log out and login to see the change. Adwaita-dark from default is also a nice one. - -![Appearance Xfce][9] - -You can use any [good GTK theme][10] on Xfce. - -#### 2. Change icons in Xfce - -Xfce-look.org also provides icon themes which you can download, extract and put it in your home directory under **.icons** directory. Once you have added the icon theme in the .icons directory, go to **Settings > Appearance > Icons** to select that icon theme. - -![Moka icon theme][11] - -I have installed [Moka icon set][12] that looks awesome. - -![Moka theme][13] - -You can also refer to our list of [awesome icon themes][14]. - -##### **Optional: Installing themes through Synaptic** - -If you want to avoid the manual search and copying of the files, install Synaptic Manager in your system. You can look for some best themes over web and icon sets, and using synaptic manager you can search and install it. -``` -sudo apt-get install synaptic - -``` - -**Searching and installing theme/icons through Synaptic** - -Open synaptic and click on **Search**. Enter your desired theme, and it will display the list of matching items. Mark all the additional required changes and click on **Apply**. This will download the theme and then install it. - -![Arc Theme][15] - -Once done, you can open the **Appearance** option to select the desired theme. - -In my opinion, this is not the best way to install themes in Xfce. - -#### 3. Change wallpapers in Xfce - -Again, the default Xfce wallpaper is not bad at all. But you can change the wallpaper to something that matches with your icons and themes. - -To change wallpapers in Xfce, right click on the desktop and click on Desktop Settings. You can change the desktop background from your custom collection or the defaults one given. - -Right click on the desktop and click on **Desktop Settings**. Choose **Background** from the folder option, and choose any one of the default backgrounds or a custom one. - -![Changing desktop wallpapers][16] - -#### 4. Change the dock in Xfce - -The default dock is nice and pretty much does what it is for. But again, it looks a bit boring. - -![Docky][17] - -However, if you want your dock to be better and with a little more customization options, you can install another dock. - -Plank is one of the simplest and lightweight docks and is highly configurable. - -To install Plank use the command below: - -`sudo apt-get install plank` - -If Plank is not available in the default repository, you can install it from this PPA. -``` -sudo add-apt-repository ppa:ricotz/docky -sudo apt-get update -sudo apt-get install plank - -``` - -Before you use Plank, you should remove the default dock by right-clicking in it and under Panel Settings, clicking on delete. - -Once done, go to **Accessory > Plank** to launch Plank dock. - -![Plank][18] - -Plank picks up icons from the one you are using. So if you change the icon themes, you’ll see the change is reflected in the dock also. - -### Wrapping Up - -XFCE is a lightweight, fast and highly customizable. If you are limited on system resource, it serves good and you can easily customize it to look better. Here’s how my screen looks after applying these steps. - -![XFCE desktop][19] - -This is just with half an hour of effort. You can make it look much better with different themes/icons customization. Feel free to share your customized XFCE desktop screen in the comments and the combination of themes and icons you are using. - --------------------------------------------------------------------------------- - -via: https://itsfoss.com/customize-xfce/ - -作者：[Ambarish Kumar][a] -选题：[lujun9972](https://github.com/lujun9972) -译者：[译者ID](https://github.com/译者ID) -校对：[校对者ID](https://github.com/校对者ID) - -本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出 - -[a]:https://itsfoss.com/author/ambarish/ -[1]:https://4bds6hergc-flywheel.netdna-ssl.com/wp-content/uploads/2018/07/xfce-customization.jpeg -[2]:https://itsfoss.com/best-linux-desktop-environments/ -[3]:https://itsfoss.com/lightweight-linux-beginners/ -[4]:https://xfce.org/ -[5]:https://4bds6hergc-flywheel.netdna-ssl.com/wp-content/uploads/2018/06/1-1-800x410.jpg -[6]:http://xfce-look.org -[7]:https://www.xfce-look.org/p/1207818/XFCE-D-PRO -[8]:https://www.xfce-look.org/p/1207818/startdownload?file_id=1523730502&file_name=XFCE-D-PRO-1.6.tar.xz&file_type=application/x-xz&file_size=105328&url=https%3A%2F%2Fdl.opendesktop.org%2Fapi%2Ffiles%2Fdownloadfile%2Fid%2F1523730502%2Fs%2F6019b2b57a1452471eac6403ae1522da%2Ft%2F1529360682%2Fu%2F%2FXFCE-D-PRO-1.6.tar.xz -[9]:https://4bds6hergc-flywheel.netdna-ssl.com/wp-content/uploads/2018/07/4.jpg -[10]:https://itsfoss.com/best-gtk-themes/ -[11]:https://4bds6hergc-flywheel.netdna-ssl.com/wp-content/uploads/2018/07/6.jpg -[12]:https://snwh.org/moka -[13]:https://4bds6hergc-flywheel.netdna-ssl.com/wp-content/uploads/2018/07/11-800x547.jpg -[14]:https://itsfoss.com/best-icon-themes-ubuntu-16-04/ -[15]:https://4bds6hergc-flywheel.netdna-ssl.com/wp-content/uploads/2018/07/5-800x531.jpg -[16]:https://4bds6hergc-flywheel.netdna-ssl.com/wp-content/uploads/2018/07/7-800x546.jpg -[17]:https://4bds6hergc-flywheel.netdna-ssl.com/wp-content/uploads/2018/07/8.jpg -[18]:https://4bds6hergc-flywheel.netdna-ssl.com/wp-content/uploads/2018/07/9.jpg -[19]:https://4bds6hergc-flywheel.netdna-ssl.com/wp-content/uploads/2018/07/10-800x447.jpg diff --git a/translated/tech/20180727 4 Ways to Customize Xfce and Give it a Modern Look.md b/translated/tech/20180727 4 Ways to Customize Xfce and Give it a Modern Look.md new file mode 100644 index 0000000000..a16d7200be --- /dev/null +++ b/translated/tech/20180727 4 Ways to Customize Xfce and Give it a Modern Look.md @@ -0,0 +1,145 @@ +4 种方式来自定义 Xfce 来给它一个现代化外观 +====== +**简介: Xfce 是一个非常轻量的桌面环境，它有一个缺点。它看起来有点老旧。但是你没有必要坚持默认外观。让我们看看你可以自定义 Xfce 的各种各样的方法，来给让一个现代化的和漂亮的外观。** + +![Customize Xfce desktop envirnment][1] + +首先，Xfce 是最[受欢迎的桌面环境][2]之一。作为一个轻量级桌面环境，你可以在非常低的资源上运行 Xfce ，并且，它仍然很好工作。这是为什么很多[轻量级 Linux 发行版][3]默认使用 Xfce 的原因之一。 + +一些人甚至喜欢在高端设备上使用它，说明它的简单性、易用性和非资源匮乏性是主要原因。 + +[Xfce][4] 是自身很小，并只提供你需要的东西。令人烦恼的事是觉得它的外观和感觉很老了。然而，你可以简单地自定义 Xfce 来看起来现代化和漂亮，而不达到 Unity/GNOME 会话占用系统资源的极限。 + +### 4 种方式来自定义 Xfce 桌面 + +让我们看看一些方法，我们可以通过这些方法改善你的 Xfce 桌面环境的外观和感觉。 + +默认 Xfce 桌面环境看起来有些像这样： + +![Xfce default screen][5] + +如您所见，默认 Xfce 桌面有点没有趣味性。我们将使用主题，图标包以及更改默认 dock 来使它看起来新鲜和有一个惊艳。 + +#### 1. 在 Xfce 中更改主题 + +我们将做的第一件事是从 [xfce-look.org][6] 中找到一款主题。我最喜欢的 Xfce 主题是 [XFCE-D-PRO][7]。 + +你可以从[这里][8]下载主题，并提取到某处。 + +你可以复制提取出的这些主题文件到你 home 目录中的 **.theme** 文件夹。如果文件夹默认不存在，你可以创建一个 ，同样的道理，图标需要一个在 home 目录中的 **.icons** 文件夹。 + +打开 **设置 > 外观 > 样式** 来选择主题，注销并重新登录以查看更改。默认的 Adwaita-dark 也是极好的一个。 + +![Appearance Xfce][9] + +你可以在 Xfce 上使用一些[好的 GTK 主题][10]。 + +#### 2. 在 Xfce 中更改图标 + +Xfce-look.org 也提供你可以下载的图标主题，提取并放置图标到你的 home 目录中 **.icons** 目录。在你添加图标主题到 .icons 目录中后，转到 **设置 > 外观 > 图标** 来选择这个图标主题。 + +![Moka icon theme][11] + +我已经安装 [Moka 图标集][12] ，它看起来令人惊艳。 + +![Moka theme][13] + +你也可以参考我们[令人惊艳的图标主题][14]列表。 + +##### **可选: 通过 Synaptic 安装主题** + +如果你想避免手工搜索和复制文件，在你的系统中安装 Synaptic 软件包管理器。你可以通过网络和图标集来查找最佳的主题，使用 synaptic 软件包管理器，你可以搜索和安装主题。 +``` +sudo apt-get install synaptic + +``` + +**通过 Synaptic 搜索和安装主题/图标** + +打开 synaptic ，并在**搜索**上单击。输入你期望的主题，接下来，它将显示匹配主题的列表。标记使用附加依赖的更改，并在**应用**上单击。这些操作将下载主题和安装主题。 + +![Arc Theme][15] + +在安装后，你可以打开**外观**选项来选择期望的主题。 + +在我看来，这不是在 Xfce 中安装主题的最佳方法。 + +#### 3. 在 Xfce 中更改桌面背景 + +在强调一次，默认 Xfce 桌面背景也不错。但是你可以把桌面背景更改成与你的图标和主题相匹配的东西。 + +为在 Xfce 中更改桌面背景，在桌面上右击，并单击桌面设置。你可以从你自定义收藏品中或默认收藏品中给定一个来更改桌面背景。 + +在桌面上右击，并单击**桌面设置**。从文件夹选择中选择**背景**，并选择任意一个默认背景或自定义背景。 + +![Changing desktop wallpapers][16] + +#### 4. 在 Xfce 中更改 dock + +默认 dock 是极好的，为此它做的非常多。但是，再强调一次，它看来有点没有趣味性。 + +![Docky][17] + +不过，如果你想你的 dock 变得更好，并带有更多一点的自定义选项，你可以安装另一个 dock 。 + +Plank 是最简单和轻量以及高度可配置中一个。 + +为安装 Plank ，使用下面的命令： + +`sudo apt-get install plank` + +如果 Plank 在默认存储库中不可获得，你可以从这个 PPA 中安装它。 +``` +sudo add-apt-repository ppa:ricotz/docky +sudo apt-get update +sudo apt-get install plank + +``` + +在你使用 Plank 前，你应该通过右键单击移除默认的 dockby，并在面板设置下，单击删除。 + +在完成后，转到 **附件 > Plank** 来启动 Plank dock 。 + +![Plank][18] + +Plank 从你正在使用的图标中选取一个图标。因此，如果你更改图标主题，你也将在 dock 中看到相关的更改。 + +### 总结 + +XFCE 是一个轻量级，快速和高度可自定义的桌面环境。如果你的系统资源有限，它服务很好，并且你可以简单地自定义它来看起来更好。这是在应用这些步骤后，我的屏幕的外观。 + +![XFCE desktop][19] + +这只是半个小时的努力，你可以使用不同的主题/图标自定义使它看起来更好。可以随意在评论区分享你自定义的 XFCE 桌面屏幕，以及你正在使用的主题和图标组合。 + +-------------------------------------------------------------------------------- + +via: https://itsfoss.com/customize-xfce/ + +作者：[Ambarish Kumar][a] +选题：[lujun9972](https://github.com/lujun9972) +译者：[robsean](https://github.com/robsean) +校对：[校对者ID](https://github.com/校对者ID) + +本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出 + +[a]:https://itsfoss.com/author/ambarish/ +[1]:https://4bds6hergc-flywheel.netdna-ssl.com/wp-content/uploads/2018/07/xfce-customization.jpeg +[2]:https://itsfoss.com/best-linux-desktop-environments/ +[3]:https://itsfoss.com/lightweight-linux-beginners/ +[4]:https://xfce.org/ +[5]:https://4bds6hergc-flywheel.netdna-ssl.com/wp-content/uploads/2018/06/1-1-800x410.jpg +[6]:http://xfce-look.org +[7]:https://www.xfce-look.org/p/1207818/XFCE-D-PRO +[8]:https://www.xfce-look.org/p/1207818/startdownload?file_id=1523730502&file_name=XFCE-D-PRO-1.6.tar.xz&file_type=application/x-xz&file_size=105328&url=https%3A%2F%2Fdl.opendesktop.org%2Fapi%2Ffiles%2Fdownloadfile%2Fid%2F1523730502%2Fs%2F6019b2b57a1452471eac6403ae1522da%2Ft%2F1529360682%2Fu%2F%2FXFCE-D-PRO-1.6.tar.xz +[9]:https://4bds6hergc-flywheel.netdna-ssl.com/wp-content/uploads/2018/07/4.jpg +[10]:https://itsfoss.com/best-gtk-themes/ +[11]:https://4bds6hergc-flywheel.netdna-ssl.com/wp-content/uploads/2018/07/6.jpg +[12]:https://snwh.org/moka +[13]:https://4bds6hergc-flywheel.netdna-ssl.com/wp-content/uploads/2018/07/11-800x547.jpg +[14]:https://itsfoss.com/best-icon-themes-ubuntu-16-04/ +[15]:https://4bds6hergc-flywheel.netdna-ssl.com/wp-content/uploads/2018/07/5-800x531.jpg +[16]:https://4bds6hergc-flywheel.netdna-ssl.com/wp-content/uploads/2018/07/7-800x546.jpg +[17]:https://4bds6hergc-flywheel.netdna-ssl.com/wp-content/uploads/2018/07/8.jpg +[18]:https://4bds6hergc-flywheel.netdna-ssl.com/wp-content/uploads/2018/07/9.jpg +[19]:https://4bds6hergc-flywheel.netdna-ssl.com/wp-content/uploads/2018/07/10-800x447.jpg From b4067805497f8626e2ff5e55f1faa3d6d3bf3202 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?=E9=83=91?= Date: Sat, 24 Aug 2019 12:58:10 +0800 Subject: [PATCH 13/58] Translating (#15145) --- ...Upgrade Linux Mint 19.1 (Tessa) to Linux Mint 19.2 (Tina).md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/sources/tech/20190810 How to Upgrade Linux Mint 19.1 (Tessa) to Linux Mint 19.2 (Tina).md b/sources/tech/20190810 How to Upgrade Linux Mint 19.1 (Tessa) to Linux Mint 19.2 (Tina).md index d37a9fb301..cd5e3dac06 100644 --- a/sources/tech/20190810 How to Upgrade Linux Mint 19.1 (Tessa) to Linux Mint 19.2 (Tina).md +++ b/sources/tech/20190810 How to Upgrade Linux Mint 19.1 (Tessa) to Linux Mint 19.2 (Tina).md @@ -1,5 +1,5 @@ [#]: collector: (lujun9972) -[#]: translator: ( ) +[#]: translator: (robsean) [#]: reviewer: ( ) [#]: publisher: ( ) [#]: url: ( ) From f4d78a6f1158494184c61ce682f36e45a93c992f Mon Sep 17 00:00:00 2001 From: darksun Date: Sat, 24 Aug 2019 16:00:44 +0800 Subject: [PATCH 14/58] translate done: 20180116 Command Line Heroes- Season 1- OS Wars_2.md --- ...ommand Line Heroes- Season 1- OS Wars_2.md | 162 ------------------ ...ommand Line Heroes- Season 1- OS Wars_2.md | 162 ++++++++++++++++++ 2 files changed, 162 insertions(+), 162 deletions(-) delete mode 100644 sources/talk/20180116 Command Line Heroes- Season 1- OS Wars_2.md create mode 100644 translated/talk/20180116 Command Line Heroes- Season 1- OS Wars_2.md diff --git a/sources/talk/20180116 Command Line Heroes- Season 1- OS Wars_2.md b/sources/talk/20180116 Command Line Heroes- Season 1- OS Wars_2.md deleted file mode 100644 index fe598d2f3f..0000000000 --- a/sources/talk/20180116 Command Line Heroes- Season 1- OS Wars_2.md +++ /dev/null @@ -1,162 +0,0 @@ -[#]: collector: (lujun9972) -[#]: translator: (lujun9972) -[#]: reviewer: ( ) -[#]: publisher: ( ) -[#]: url: ( ) -[#]: subject: (Command Line Heroes: Season 1: OS Wars) -[#]: via: (https://www.redhat.com/en/command-line-heroes/season-1/os-wars-part-2-rise-of-linux) -[#]: author: (redhat https://www.redhat.com) - -代码英雄: 第一季: 操作系统大战(第二部分 Linux 崛起) -====== -Saron Yitbarek: 这玩意开着的吗? 让我们进一段史诗般的星球大战的开幕吧, 开始了. - -配音: [00:00:30] 第二集:Linux®的崛起。微软帝国控制着90%的桌面用户。操作系统的全面标准化似乎是板上钉钉的事了。然而，互联网的出现将战争的焦点从桌面转向了企业，在该领域，所有商业组织都争相构建自己的服务器。与此同时，一个不太可能的英雄出现在开源反叛组织中。固执，戴着眼镜的Linus Torvalds免费发布了他的Linux系统。微软打了个趔趄-并且开始重组。 - -Saron Yitbarek: [00:01:00] 哦，我们书呆子就是喜欢那样。上一次我们讲到哪了?苹果和微软互相攻伐，试图在一场争夺桌面用户的战争中占据主导地位。在第一集的结尾，我们看到微软获得了大部分的市场份额。很快，由于互联网的兴起以及随之而来的开发者大军,整个市场都经历了一场地震。互联网将战场从在家庭和办公室中的个人电脑用户转移到拥有数百台服务器的大型商业客户中。 - -[00:01:30] 这意味着巨量资源的迁移。突然间，所有相关企业不仅被迫为服务器空间和网站建设付费，而且还必须集成软件来进行资源跟踪和数据库监控等工作。你需要很多开发人员来帮助你。至少那时候大家都是这么做的。 - -在操作系统之战的第二部分，我们将看到优先级的巨大转变，以及像Linus Torvalds和Richard Stallman这样的开源叛逆者是如何成功地在微软和整个软件行业的核心地带引起恐惧的。 - -[00:02:00] 我是 Saron Yitbarek,您现在收听的是代码英雄，一款红帽公司原创的播客节目. 每一集,我们都会给您带来“从码开始”改变技术的人的故事. - -[00:02:30] 好。假设你是1991年的微软。你自我感觉良好，对吧?满怀信心。确定全球主导的地位感觉不错。你已经掌握了与其他企业合作的艺术，但是仍然将大部分开发人员、程序员和系统管理员排除在联盟之外，而他们才是真正的步兵。这是出现了个叫Linus Torvalds的芬兰极客。他和他的开源程序员团队正在开始发布Linux，其操作系统内核是由他们一起编写出来的。 - -[00:03:00] 坦白地说，如果你是微软公司，你并不会太在意Linux，甚至是一般意义上的开源运动，但是最终，Linux的规模变得如此之大，以至于微软不可能不注意到。Linux第一个版本出现在1991年，当时大概有10000行代码。十年后，变成了300万行代码。如果你想知道，今天则是2000万行代码。 - -[00:03:30] 让我们停留在90年代初一会儿。那是Linux还没有成为我们现在所知道的庞然大物。只是这个奇怪的病毒式的操作系统正在这个星球上蔓延，全世界的极客和黑客都爱上了它。那时候我还太年轻，但依然希望加入他们。在那个时候，发现Linux就如同进入了一个秘密社会一样。程序员与朋友分享Linux CD集，就像其他人分享地下音乐混音带一样。 - -Developer Tristram Oaten [00:03:40] 讲讲了你16岁时第一次接触Linux的故事吧。 - -Tristram Oaten: [00:04:00] 我和我的家人去了Red Sea上的Hurghada潜水度假。那是一个美丽的地方，强烈推荐。第一天，我喝了自来水。也许，我妈妈跟我说过不要这么做。我整个星期都病得很厉害，没有离开旅馆房间。当时我只带了一台新安装了Slackware Linux的笔记本电脑，我听说过这玩意并且正在尝试使用它。这台笔记本上没有额外的应用程序，只有8张cd。出于必要，整个星期我所做的就是去了解这个外星一般的系统。我阅读手册，摆弄着终端。我记得当时我甚至我不知道一个点(表示当前目录)和两个点(表示前一个目录)之间的区别。 - -[00:04:30] 我一点头绪都没有。犯过很多错误，但慢慢地，在这种强迫的孤独中，我突破了障碍，开始理解并明白命令行到底是怎么回事。假期结束时，我没有看过金字塔、尼罗河等任何埃及遗址，但我解锁了现代世界的一个奇迹。我解锁了Linux，接下来的事大家都知道了。 - -Saron Yitbarek: 你可以从很多人那里听到关于这个故事的不同说法。访问Linux命令行是一种革命性的体验。 - -David Cantrell: 它给了我源代码. 我当时的感觉是, "太神奇了." - -Saron Yitbarek: 我们正在参加一个名为Flock to Fedora的2017年Linux开发者大会。 - -David Cantrell: ... 非常有吸引力。我觉得我对这个系统有了更多的控制力，它越来越吸引我。我想，从那时起，1995年我第一次编译Linux内核时，我就迷上了它。 - -Saron Yitbarek: 开发者 David Cantrell 与 Joe Brockmire. - -Joe Brockmeier: 我寻遍了便宜软件最终找到一套四张CD的 Slackware Linux. 它看起来来非常令人兴奋而且很有趣，所以我把它带回家，安装在第二台电脑上，开始摆弄它，并为两件事情感到兴奋。一个是，我运行的不是Windows，另一个我Linux的开源特性。 - -Saron Yitbarek: [00:06:00] 某种程度上来说，对命令行的访问总是存在的。在开源真正开始流行还要早几十年前，人们(至少在开发人员中是这样)总是希望能够做到完全控制。让我们回到操作系统大战之前的那个时代，在苹果和微软他们的GUI而战之前。那时也有代码英雄。保罗·琼斯(Paul Jones)教授(在线图书馆ibiblio.org负责人)在那个古老的时代，就是一名开发人员。 - -Paul Jones: [00:07:00] 从本质上讲，互联网在那个时候比较少是客户端-服务器架构的，而是更多是点对点架构的。讲真，当我们说，某种VAX到VAX，某科学工作站，科学工作站。这并不意味着没有客户端与服务端的关系以及没有应用程序,但这的确意味着,最初的设计是思考如何实现点对点,它与IBM一直在做的东西相对立. IBM给你的只有哑终端,这种终端只能让你管理用户界面,却无法让你像真正的终端一样为所欲为。 - -Saron Yitbarek: 图形用户界面在普通用户中普及的同时，在工程师和开发人员中总是存在和一股相反的力量。早在20世纪70年代和80年代的Linux出现之前，这股力量就存在于EMAX和GNU中。有了斯托尔曼的自由软件基金会后，总有某些人想要使用命令行，但上世纪90年代的Linux的交付方式是独一无二的。 - -[00:07:30] Linux和其他开源软件的早期爱好者是都是先驱。我正站在他们的肩膀上。我们都是。 - -您现在收听的是代码英雄, 一款由红帽公司原创的播客. 这是操作系统大战的第二部分: Linux 崛起. - -Steven Vaughan-Nichols: 1998年的时候, 情况发生了变化. - -Saron Yitbarek: Steven Vaughan-Nichols 是zdnet.com的特约编辑，他已经写了几十年关于技术商业方面的文章了。他将向我们讲述Linux是如何慢慢变得越来越流行，直到自愿贡献者的数量远远超过了在Windows上工作的微软开发人员的数量的。不过，Linux从来没有真正关注过微软的台式机客户，这也许就是微软最开始时忽略了Linux及其开发者的原因。Linux真正大放光彩的地方是在服务器机房。当企业开始线上业务时，每个企业都需要一个独特的编程解决方案来满足其需求。 - -[00:08:30] WindowsNT于1993年问世，当时它已经在与其他的服务器操作系统展开竞争了，但是许多开发人员都在想，“既然我可以通过Apache构建出基于Linux的廉价系统，那我为什么要购买AIX设备或大型Windows设备呢？”关键点在于，Linux代码已经开始渗透到几乎所有在线的东西中。 - -Steven Vaughan-Nichols: [00:09:00] 令微软感到惊讶的是，它开始意识到，Linux实际上已经开始有一些商业应用，不是在桌面环境，而是在商业服务器上。因此，他们发起了一场运动，我们称之为FUD-恐惧、不确定和怀疑(fear,uncertainty和double).他们说，“哦，Linux这玩意，真的没有那么好。它不太可靠。你一点都不能相信它”。 - -Saron Yitbarek: [00:09:30] 这种软宣传式的攻击持续了一段时间。微软也不是唯一一个对Linux感到紧张的公司。这其实是整个行业在对抗这个奇怪新人的挑战。例如，任何与UNIX有利害关系的人都可能将Linux视为篡夺者。有一个案例很著名，那就是SCO组织(它发行过一种版本的UNIX)在过去10多年里发起一系列的诉讼，试图阻止Linux的传播。SCO最终失败而且破产了。与此同时，微软一直在寻找机会。他们势在必行。只不过目前还不清楚具体要怎么做。 - -Steven Vaughan-Nichols: [00:10:30] 让微软真正担心的是，第二年，在2000年的时候，IBM宣布,他们将于2001年投资10亿美元在Linux上。现在，IBM已经不再涉足个人电脑业务。他们还没有走出去，但他们正朝着这个方向前进，他们将Linux视为服务器和大型计算机的未来，在这一点上，剧透警告，IBM是正确的。Linux将主宰服务器世界。 - -Saron Yitbarek: 这已经不再仅仅是一群黑客喜欢命令行的Jedi式的控制了。金钱的投入对Linux助力极大。Linux国际的执行董事John "Mad Dog" Hall有一个故事可以解释为什么会这样。我们通过电话与他取得了联系。 - -John Hall: [00:11:30] 我的一个朋友名叫Dirk Holden[00:10:56]，他是德国德意志银行的一名系统管理员，他也参与了个人电脑上早期X Windows系统的图形项目中的工作。有一天我去银行拜访他，我说:“Dirk，你银行里有3000台服务器，用的都是Linux。为什么不用Microsoft NT呢?”他看着我说:“是的，我有3000台服务器，如果使用微软的Windows NT系统，我需要2999名系统管理员。”他继续说道:“而使用Linux，我只需要四个。”这真是完美的答案。 - -Saron Yitbarek: [00:12:00] 程序员们着迷的这些东西恰好对大公司也极具吸引力。但由于FUD的作用，一些企业对此持谨慎态度。他们听到开源，就想:"开源。这看起来不太可靠,很混乱，充满了BUG".但正如那位银行经理所指出的，金钱听过一种有趣的方式，说服人们克服困境。甚至那些需要网站的小公司也加入了Linux阵营。与一些昂贵的专有选择相比，使用一个廉价的Linux系统在成本上是无法比拟的。如果您是一家雇佣专业人员来构建网站的商店，那么您很定想让他们使用Linux。 - -[00:12:30] 让我们快进几年. Linux运行每个人的网站上。Linux已经征服了服务器世界，然后智能手机也随之诞生。当然，苹果和他们的iPhone占据了相当大的市场份额，而且微软也希望能进入这个市场，但令人惊讶的是，Linux也在那，已经做好准备了，迫不及待要大展拳脚。 - -作家兼记者 James Allworth. - -James Allworth: [00:13:00] 当然还有容纳第二个竞争者的空间，那本可以是微软，但是实际上却是Android，而Andrid基本上是基于Linux的. 众所周知,Android被谷歌所收购，现在运行在世界上大部分的智能手机上，谷歌在Linux的基础上创建了Android。Linux使他们能够以零成本从一个非常复杂的操作系统开始。他们成功地实现了这一目标，最终将微软挡在了下一代设备之外，至少从操作系统的角度来看是这样。 - -Saron Yitbarek: [00:13:30] 天崩地裂了，很大程度上，微软有被埋没的风险。John Gossman是微软Azure团队的首席架构师。他还记得当时困扰公司的困惑。 - -John Gossman: [00:14:00] 像许多公司一样，微软也非常担心知识产权污染。他们认为，如果允许开发人员使用开源代码，那么很可能只是复制并粘贴一些代码到某些产品中，就会让某种病毒式的许可证生效从而引发未知的风险…，我认为，这跟公司文化有关，很多公司，包括微软，都对开源开发的意义和商业模式之间的分歧感到困惑。有一种观点认为，开源意味着你所有的软件都是免费的，人们永远不会付钱。 - -Saron Yitbarek: [00:14:30] 任何投资于旧的、专有软件模型的人都会觉得这里发生的一切对他们构成了威胁。当你威胁到像微软这样的大公司时，是的，他们一定会做出反应。他们推动所有这些FUD(fear,uncertainty,doubt)-恐惧，不确定性和怀疑是有道理的。当时，商业运作的方式基本上就是相互竞争。不过，如果他们是其他公司的话(If they'd been any other company,看不懂什么意思)，他们可能还会怀恨在心，抱着旧有的想法，但到了2013年，一切都变了。 - -[00:15:00] 微软的云计算服务Azure上线了，令人震惊的是，它从第一天开始就提供了Linux虚拟机。Steve Ballmer，这位把Linux称为癌症的首席执行官，已经离开了，代替他的是一位新的有远见的首席执行官Satya Nadella. - -John Gossman: Satya 有不同的看法. 他属于另一个世代. 比Paul , Bill 和 Steve 更年轻的世代 , 他对开源有不同的看法. - -Saron Yitbarek: John Gossman, 再说一次, 来自于 微软的Azure 团队. - -John Gossman: [00:16:00] 大约四年前，处于实际需要，我们在Azure中添加了Linux支持。如果访问任何一家企业客户，你都会发现他们并没有试图决定是使用Windows还是使用Linux、使用.net还是使用Java TM。他们在很久以前就做出了决定——大约15年前才有这样的一些争论。现在，我见过的每一家公司都混合了Linux和Java、Windows和.net、SQL Server、Oracle和MySQL——基于专有源代码的产品和开放源代码的产品。 - -如果你正在运维着一个云，允许这些公司在云上运行他们的业务，那么你就不能简单地告诉他们，“你可以使用这个软件，但你不能使用那个软件。” - -Saron Yitbarek: [00:16:30] 这正是 Satya Nadella 采纳的哲学思想. 2014年秋季，他站在舞台上，希望传递一个重要信息。微软爱Linux。他接着说，Azure 20%的业务量已经是Linux了，微软将始终对Linux发行版提供一流的支持。没有哪怕一丝对开源的宿怨。 - -为了说明这一点，在他们的背后有一个巨大的标志，上面写着:“Microsoft hearts Linux”。哇哇哇。对我们中的一些人来说，这种转变有点令人震惊，但实际上，无需如此震惊。下面是Steven Levy,一名科技记者兼作家。 - -Steven Levy: [00:17:30] 当你在踢足球的时候，如果草坪变滑了，那么你也许会换一种不同的鞋子。他们当初就是这么做的。他们不能否认现实而且他们之间也有有聪明人,所以他们必须意识到,这就是世界的运行方式,不管他们早些时候说了什么,即使他们对之前的言论感到尴尬,但是让他们之前关于开源多么可怕的言论影响到现在明智的决策那才真的是疯了。 - -Saron Yitbarek: [00:18:00] 微软低下了它高傲的头. 你可能还记得苹果公司, 经过多年的孤立无援, 最终转向与微软构建合作伙伴关系. 现在轮到微软进行180度转变了. 经过多年的与开源方法的战斗后，他们正在重塑自己。要么改变，要么死亡. Steven Vaughan-Nichols. - -Steven Vaughan-Nichols: [00:18:30] 即使是像微软这样规模的公司也无法与成千上万的开源开发者竞争，这些开发者开发这包括Linux在内的其他大项目。很长时间以来他们都不愿意这么做。前微软首席执行官史蒂夫·鲍尔默（SteveBallmer）对Linux深恶痛绝。由于它的GPL许可证，让Linux称为一种癌症，但一旦鲍尔默被扫地出门，新的微软领导层说，“这就好像试图命令潮流不要过来，但潮水依然会不断涌进来。我们应该与Linux合作，而不是与之对抗。” - -Saron Tiebreak: [00:19:00] 真的，在线技术历史上最大的胜利之一就是微软能够做出这样的转变，当他们最终决定这么做的时候。当然，当微软出现在开源的桌子上时，老的、铁杆Linux支持者是相当怀疑的。他们不确定自己是否能接受这些家伙，但正如沃恩-尼科尔斯所指出的，今天的微软根本不是你父母的微软。事实上, 互联网技术历史上最大的胜利之一就是让微软最终做出如此转变. 当然，当微软出现在开源桌上时，老一代的、铁杆Linux支持者是相当怀疑的。他们不确定自己是否能接受这些家伙，但正如Vaughan-Nichols 所指出的，今天的微软已经不是你父母那一代时的微软了。 - -Steven Vaughan-Nichols : [00:19:30] 2017年的微软既不是史蒂夫•鲍尔默(Steve Ballmer)的微软，也不是比尔•盖茨(Bill Gates)的微软。这是一家完全不同的公司，有着完全不同的方法，而且，开源软件一旦被放出，就无法被收回。开源已经吞噬了整个技术世界。从未听说过Linux的人可能对它并不了解，但是每次他们访问Facebook，他们都在运行Linux。每次执行谷歌搜索时，你都在运行Linux。 - -[00:20:00] 每次你用Android手机，你都在运行Linux。它确实无处不在，微软无法阻止它，我认为以为微软可以以某种方式接管它的想法，太天真了。 - -Saron Yitbarek: [00:20:30] 开源支持者可能一直担心微软会像混入羊群中的狼一样，但事实是，开源软件的本质保护了它无法被完全控制。没有一家公司能够拥有Linux并以某种特定的方式控制它。Greg Kroah-Hartman是Linux基金会的一名成员。 - -Greg Kroah-Hartman: 每个公司和个人都以自私的方式为Linux做出贡献。他们之所以这样做是因为他们想要解决他们所面临的问题，可能是硬件无法工作，或者是他们想要添加一个新功能来做其他事情，又或者想在他们的产品中使用它。这很棒，因为他们会把代码贡献回去,此后每个人都会从中受益，这样每个人都可以用到这份代码。正是因为这种自私，所有的公司，所有的人，所有的人都能从中受益。 - -Saron Yitbarek: [00:21:30] Microsoft has realized that in the coming cloud wars, fighting Linux would be like going to war with, well, a cloud. Linux and open source aren't the enemy, they're the atmosphere. Today, Microsoft has joined the Linux Foundation as a platinum member. They became the number one contributor to open source on GitHub. In September, 2017, they even joined the Open Source Initiative. These days, Microsoft releases a lot of its code under open licenses. Microsoft's John Gossman describes what happened when they open sourced .net. At first, they didn't really think they'd get much back. - -John Gossman: [00:22:00] We didn't count on contributions from the community, and yet, three years in, over 50 per cent of the contributions to the .net framework libraries, now, are coming from outside of Microsoft. This includes big pieces of code. Samsung has contributed ARM support to .net. Intel and ARM and a couple other chip people have contributed code generation specific for their processors to the .net framework, as well as a surprising number of fixes, performance improvements , and stuff — from just individual contributors to the community. - -Saron Yitbarek: Up until a few years ago, the Microsoft we have today, this open Microsoft, would have been unthinkable. - -[00:23:00] I'm Saron Yitbarek, and this is Command Line Heroes. Okay, we've seen titanic battles for the love of millions of desktop users. We've seen open source software creep up behind the proprietary titans, and nab huge market share. We've seen fleets of command line heroes transform the programming landscape into the one handed down to people like me and you. Today, big business is absorbing open source software, and through it all, everybody is still borrowing from everybody. - -[00:23:30] In the tech wild west, it's always been that way. Apple gets inspired by Xerox, Microsoft gets inspired by Apple, Linux gets inspired by UNIX. Evolve, borrow, constantly grow. In David and Goliath terms, open source software is no longer a David, but, you know what? It's not even Goliath, either. Open source has transcended. It's become the battlefield that others fight on. As the open source approach becomes inevitable, new wars, wars that are fought in the cloud, wars that are fought on the open source battlefield, are ramping up. - -Here's author Steven Levy. - -Steven Levy: [00:24:00] Basically, right now, we have four or five companies, if you count Microsoft, that in various ways are fighting to be the platform for all we do, for artificial intelligence, say. You see wars between intelligent assistants, and guess what? Apple has an intelligent assistant, Siri. Microsoft has one, Cortana. Google has the Google Assistant. Samsung has an intelligent assistant. Amazon has one, Alexa. We see these battles shifting to different areas, there. Maybe, you could say, the hottest one is would be, whose AI platform is going to control all the stuff in our lives there, and those five companies are all competing for that. - -Saron Yitbarek: If you're looking for another rebel that's going to sneak up behind Facebook or Google or Amazon and blindside them the way Linux blindsided Microsoft, you might be looking a long time, because as author James Allworth points out, being a true rebel is only getting harder and harder. - -James Allworth: [00:25:30] Scale's always been an advantage but the nature of scale advantages are almost ... Whereas, I think previously they were more linear in nature, now it's more exponential in nature, and so, once you start to get out in front with something like this , it becomes harder and harder for a new player to come in and catch up. I think this is true of the internet era in general, whether it's scale like that or the importance and advantages that data bestow on an organization in terms of its ability to compete. Once you get out in front, you attract more customers, and then that gives you more data and that enables you to do an even better job, and then, why on earth would you want to go with the number two player, because they're so far behind? I think it's going to be no different in cloud. - -Saron Yitbarek: [00:26:00] This story began with singular heroes like Steve Jobs and Bill Gates, but the progress of technology has taken on a crowdsourced, organic feel. I think it's telling that our open source hero, Linus Torvalds, didn't even have a real plan when he first invented the Linux kernel. He was a brilliant , young developer for sure, but he was also like a single drop of water at the very front of a tidal wave. The revolution was inevitable. It's been estimated that for a proprietary company to create a Linux distribution in their old - fashioned , proprietary way, it would cost them well over $ 10 billion. That points to the power of open source. - -[00:26:30] In the end, it's not something that a proprietary model is going to compete with. Successful companies have to remain open. That's the big, ultimate lesson in all this. Something else to keep in mind: W hen we're wired together, our capacity to grow and build on what we've already accomplished becomes limitless. As big as these companies get, we don't have to sit around waiting for them to give us something better. Think about the new developer who learns to code for the sheer joy of creating, the mom who decides that if nobody's going to build what she needs, then she'll build it herself. - -Wherever tomorrow's great programmers come from, they're always going to have the capacity to build the next big thing, so long as there's access to the command line. - -[00:27:30] That's it for our two - part tale on the OS wars that shaped our digital lives. The struggle for dominance moved from the desktop to the server room, and ultimately into the cloud. Old enemies became unlikely allies, and a crowdsourced future left everything open . Listen, I know, there are a hundred other heroes we didn't have space for in this history trip, so drop us a line. Share your story. Redhat.com/commandlineheroes. I'm listening. - -We're spending the rest of the season learning what today's heroes are creating, and what battles they're going through to bring their creations to life. Come back for more tales — from the epic front lines of programming. We drop a new episode every two weeks. In a couple weeks' time, we bring you episode three: the Agile Revolution. - -[00:28:00] Command Line Heroes is an original podcast from Red Hat. To get new episodes delivered automatically for free, make sure to subscribe to the show. Just search for “ Command Line Heroes ” in Apple p odcast s , Spotify, Google Play, and pretty much everywhere else you can find podcasts. Then, hit “ subscribe ” so you will be the first to know when new episodes are available. - -I'm Saron Yitbarek. Thanks for listening. Keep on coding. - --------------------------------------------------------------------------------- - -via: https://www.redhat.com/en/command-line-heroes/season-1/os-wars-part-2-rise-of-linux - -作者：[redhat][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.redhat.com -[b]: https://github.com/lujun9972 diff --git a/translated/talk/20180116 Command Line Heroes- Season 1- OS Wars_2.md b/translated/talk/20180116 Command Line Heroes- Season 1- OS Wars_2.md new file mode 100644 index 0000000000..040a2d2836 --- /dev/null +++ b/translated/talk/20180116 Command Line Heroes- Season 1- OS Wars_2.md @@ -0,0 +1,162 @@ +[#]: collector: (lujun9972) +[#]: translator: (lujun9972) +[#]: reviewer: ( ) +[#]: publisher: ( ) +[#]: url: ( ) +[#]: subject: (Command Line Heroes: Season 1: OS Wars) +[#]: via: (https://www.redhat.com/en/command-line-heroes/season-1/os-wars-part-2-rise-of-linux) +[#]: author: (redhat https://www.redhat.com) + +代码英雄：第一季：操作系统大战(第二部分 Linux 崛起) +====== +Saron Yitbarek: 这玩意开着的吗？让我们进一段史诗般的星球大战的开幕吧，开始了。 + +配音：[00:00:30] 第二集 :Linux® 的崛起。微软帝国控制着 90% 的桌面用户。操作系统的全面标准化似乎是板上钉钉的事了。然而，互联网的出现将战争的焦点从桌面转向了企业，在该领域，所有商业组织都争相构建自己的服务器。与此同时，一个不太可能的英雄出现在开源反叛组织中。固执，戴着眼镜的 Linus Torvalds 免费发布了他的 Linux 系统。微软打了个趔趄-并且开始重组。 + +Saron Yitbarek: [00:01:00] 哦，我们书呆子就是喜欢那样。上一次我们讲到哪了？苹果和微软互相攻伐，试图在一场争夺桌面用户的战争中占据主导地位。在第一集的结尾，我们看到微软获得了大部分的市场份额。很快，由于互联网的兴起以及随之而来的开发者大军，整个市场都经历了一场地震。互联网将战场从在家庭和办公室中的个人电脑用户转移到拥有数百台服务器的大型商业客户中。 + +[00:01:30] 这意味着巨量资源的迁移。突然间，所有相关企业不仅被迫为服务器空间和网站建设付费，而且还必须集成软件来进行资源跟踪和数据库监控等工作。你需要很多开发人员来帮助你。至少那时候大家都是这么做的。 + +在操作系统之战的第二部分，我们将看到优先级的巨大转变，以及像 Linus Torvalds 和 Richard Stallman 这样的开源叛逆者是如何成功地在微软和整个软件行业的核心地带引起恐惧的。 + +[00:02:00] 我是 Saron Yitbarek，您现在收听的是代码英雄，一款红帽公司原创的播客节目。每一集，我们都会给您带来“从码开始”改变技术的人的故事。 + +[00:02:30] 好。假设你是 1991 年的微软。你自我感觉良好，对吧？满怀信心。确定全球主导的地位感觉不错。你已经掌握了与其他企业合作的艺术，但是仍然将大部分开发人员、程序员和系统管理员排除在联盟之外，而他们才是真正的步兵。这是出现了个叫 Linus Torvalds 的芬兰极客。他和他的开源程序员团队正在开始发布 Linux，其操作系统内核是由他们一起编写出来的。 + +[00:03:00] 坦白地说，如果你是微软公司，你并不会太在意 Linux，甚至是一般意义上的开源运动，但是最终，Linux 的规模变得如此之大，以至于微软不可能不注意到。Linux 第一个版本出现在 1991 年，当时大概有 10000 行代码。十年后，变成了 300 万行代码。如果你想知道，今天则是 2000 万行代码。 + +[00:03:30] 让我们停留在 90 年代初一会儿。那是 Linux 还没有成为我们现在所知道的庞然大物。只是这个奇怪的病毒式的操作系统正在这个星球上蔓延，全世界的极客和黑客都爱上了它。那时候我还太年轻，但依然希望加入他们。在那个时候，发现 Linux 就如同进入了一个秘密社会一样。程序员与朋友分享 Linux CD 集，就像其他人分享地下音乐混音带一样。 + +Developer Tristram Oaten [00:03:40] 讲讲了你 16 岁时第一次接触 Linux 的故事吧。 + +Tristram Oaten: [00:04:00] 我和我的家人去了 Red Sea 上的 Hurghada 潜水度假。那是一个美丽的地方，强烈推荐。第一天，我喝了自来水。也许，我妈妈跟我说过不要这么做。我整个星期都病得很厉害，没有离开旅馆房间。当时我只带了一台新安装了 Slackware Linux 的笔记本电脑，我听说过这玩意并且正在尝试使用它。这台笔记本上没有额外的应用程序，只有 8 张 cd。出于必要，整个星期我所做的就是去了解这个外星一般的系统。我阅读手册，摆弄着终端。我记得当时我甚至我不知道一个点(表示当前目录)和两个点(表示前一个目录)之间的区别。 + +[00:04:30] 我一点头绪都没有。犯过很多错误，但慢慢地，在这种强迫的孤独中，我突破了障碍，开始理解并明白命令行到底是怎么回事。假期结束时，我没有看过金字塔、尼罗河等任何埃及遗址，但我解锁了现代世界的一个奇迹。我解锁了 Linux，接下来的事大家都知道了。 + +Saron Yitbarek: 你可以从很多人那里听到关于这个故事的不同说法。访问 Linux 命令行是一种革命性的体验。 + +David Cantrell: 它给了我源代码。我当时的感觉是，"太神奇了。" + +Saron Yitbarek: 我们正在参加一个名为 Flock to Fedora 的 2017 年 Linux 开发者大会。 + +David Cantrell: .。. 非常有吸引力。我觉得我对这个系统有了更多的控制力，它越来越吸引我。我想，从那时起，1995 年我第一次编译 Linux 内核时，我就迷上了它。 + +Saron Yitbarek: 开发者 David Cantrell 与 Joe Brockmire。 + +Joe Brockmeier: 我寻遍了便宜软件最终找到一套四张 CD 的 Slackware Linux。它看起来来非常令人兴奋而且很有趣，所以我把它带回家，安装在第二台电脑上，开始摆弄它，并为两件事情感到兴奋。一个是，我运行的不是 Windows，另一个我 Linux 的开源特性。 + +Saron Yitbarek: [00:06:00] 某种程度上来说，对命令行的访问总是存在的。在开源真正开始流行还要早几十年前，人们(至少在开发人员中是这样)总是希望能够做到完全控制。让我们回到操作系统大战之前的那个时代，在苹果和微软他们的 GUI 而战之前。那时也有代码英雄。保罗·琼斯 (Paul Jones) 教授(在线图书馆 ibiblio.org 负责人)在那个古老的时代，就是一名开发人员。 + +Paul Jones: [00:07:00] 从本质上讲，互联网在那个时候比较少是客户端-服务器架构的，而是更多是点对点架构的。讲真，当我们说，某种 VAX 到 VAX，某科学工作站，科学工作站。这并不意味着没有客户端与服务端的关系以及没有应用程序，但这的确意味着，最初的设计是思考如何实现点对点，它与 IBM 一直在做的东西相对立。IBM 给你的只有哑终端，这种终端只能让你管理用户界面，却无法让你像真正的终端一样为所欲为。 + +Saron Yitbarek: 图形用户界面在普通用户中普及的同时，在工程师和开发人员中总是存在和一股相反的力量。早在 20 世纪 70 年代和 80 年代的 Linux 出现之前，这股力量就存在于 EMAX 和 GNU 中。有了斯托尔曼的自由软件基金会后，总有某些人想要使用命令行，但上世纪 90 年代的 Linux 的交付方式是独一无二的。 + +[00:07:30] Linux 和其他开源软件的早期爱好者是都是先驱。我正站在他们的肩膀上。我们都是。 + +您现在收听的是代码英雄，一款由红帽公司原创的播客。这是操作系统大战的第二部分：Linux 崛起。 + +Steven Vaughan-Nichols: 1998 年的时候，情况发生了变化。 + +Saron Yitbarek: Steven Vaughan-Nichols 是 zdnet.com 的特约编辑，他已经写了几十年关于技术商业方面的文章了。他将向我们讲述 Linux 是如何慢慢变得越来越流行，直到自愿贡献者的数量远远超过了在 Windows 上工作的微软开发人员的数量的。不过，Linux 从来没有真正关注过微软的台式机客户，这也许就是微软最开始时忽略了 Linux 及其开发者的原因。Linux 真正大放光彩的地方是在服务器机房。当企业开始线上业务时，每个企业都需要一个独特的编程解决方案来满足其需求。 + +[00:08:30] WindowsNT 于 1993 年问世，当时它已经在与其他的服务器操作系统展开竞争了，但是许多开发人员都在想，“既然我可以通过 Apache 构建出基于 Linux 的廉价系统，那我为什么要购买 AIX 设备或大型 Windows 设备呢？”关键点在于，Linux 代码已经开始渗透到几乎所有在线的东西中。 + +Steven Vaughan-Nichols: [00:09:00] 令微软感到惊讶的是，它开始意识到，Linux 实际上已经开始有一些商业应用，不是在桌面环境，而是在商业服务器上。因此，他们发起了一场运动，我们称之为 FUD- 恐惧、不确定和怀疑 (fear，uncertainty 和 double)。他们说，“哦，Linux 这玩意，真的没有那么好。它不太可靠。你一点都不能相信它”。 + +Saron Yitbarek: [00:09:30] 这种软宣传式的攻击持续了一段时间。微软也不是唯一一个对 Linux 感到紧张的公司。这其实是整个行业在对抗这个奇怪新人的挑战。例如，任何与 UNIX 有利害关系的人都可能将 Linux 视为篡夺者。有一个案例很著名，那就是 SCO 组织(它发行过一种版本的 UNIX) 在过去 10 多年里发起一系列的诉讼，试图阻止 Linux 的传播。SCO 最终失败而且破产了。与此同时，微软一直在寻找机会。他们势在必行。只不过目前还不清楚具体要怎么做。 + +Steven Vaughan-Nichols: [00:10:30] 让微软真正担心的是，第二年，在 2000 年的时候，IBM 宣布，他们将于 2001 年投资 10 亿美元在 Linux 上。现在，IBM 已经不再涉足个人电脑业务。他们还没有走出去，但他们正朝着这个方向前进，他们将 Linux 视为服务器和大型计算机的未来，在这一点上，剧透警告，IBM 是正确的。Linux 将主宰服务器世界。 + +Saron Yitbarek: 这已经不再仅仅是一群黑客喜欢命令行的 Jedi 式的控制了。金钱的投入对 Linux 助力极大。Linux 国际的执行董事 John "Mad Dog" Hall 有一个故事可以解释为什么会这样。我们通过电话与他取得了联系。 + +John Hall: [00:11:30] 我的一个朋友名叫 Dirk Holden[00:10:56]，他是德国德意志银行的一名系统管理员，他也参与了个人电脑上早期 X Windows 系统的图形项目中的工作。有一天我去银行拜访他，我说 :“Dirk，你银行里有 3000 台服务器，用的都是 Linux。为什么不用 Microsoft NT 呢？”他看着我说：“是的，我有 3000 台服务器，如果使用微软的 Windows NT 系统，我需要 2999 名系统管理员。”他继续说道：“而使用 Linux，我只需要四个。”这真是完美的答案。 + +Saron Yitbarek: [00:12:00] 程序员们着迷的这些东西恰好对大公司也极具吸引力。但由于 FUD 的作用，一些企业对此持谨慎态度。他们听到开源，就想："开源。这看起来不太可靠，很混乱，充满了 BUG"。但正如那位银行经理所指出的，金钱听过一种有趣的方式，说服人们克服困境。甚至那些需要网站的小公司也加入了 Linux 阵营。与一些昂贵的专有选择相比，使用一个廉价的 Linux 系统在成本上是无法比拟的。如果您是一家雇佣专业人员来构建网站的商店，那么您很定想让他们使用 Linux。 + +[00:12:30] 让我们快进几年。Linux 运行每个人的网站上。Linux 已经征服了服务器世界，然后智能手机也随之诞生。当然，苹果和他们的 iPhone 占据了相当大的市场份额，而且微软也希望能进入这个市场，但令人惊讶的是，Linux 也在那，已经做好准备了，迫不及待要大展拳脚。 + +作家兼记者 James Allworth。 + +James Allworth: [00:13:00] 当然还有容纳第二个竞争者的空间，那本可以是微软，但是实际上却是 Android，而 Andrid 基本上是基于 Linux 的。众所周知，Android 被谷歌所收购，现在运行在世界上大部分的智能手机上，谷歌在 Linux 的基础上创建了 Android。Linux 使他们能够以零成本从一个非常复杂的操作系统开始。他们成功地实现了这一目标，最终将微软挡在了下一代设备之外，至少从操作系统的角度来看是这样。 + +Saron Yitbarek: [00:13:30] 天崩地裂了，很大程度上，微软有被埋没的风险。John Gossman 是微软 Azure 团队的首席架构师。他还记得当时困扰公司的困惑。 + +John Gossman: [00:14:00] 像许多公司一样，微软也非常担心知识产权污染。他们认为，如果允许开发人员使用开源代码，那么很可能只是复制并粘贴一些代码到某些产品中，就会让某种病毒式的许可证生效从而引发未知的风险…，我认为，这跟公司文化有关，很多公司，包括微软，都对开源开发的意义和商业模式之间的分歧感到困惑。有一种观点认为，开源意味着你所有的软件都是免费的，人们永远不会付钱。 + +Saron Yitbarek: [00:14:30] 任何投资于旧的、专有软件模型的人都会觉得这里发生的一切对他们构成了威胁。当你威胁到像微软这样的大公司时，是的，他们一定会做出反应。他们推动所有这些 FUD(fear，uncertainty，doubt)- 恐惧，不确定性和怀疑是有道理的。当时，商业运作的方式基本上就是相互竞争。不过，如果他们是其他公司的话 (If they'd been any other company，看不懂什么意思)，他们可能还会怀恨在心，抱着旧有的想法，但到了 2013 年，一切都变了。 + +[00:15:00] 微软的云计算服务 Azure 上线了，令人震惊的是，它从第一天开始就提供了 Linux 虚拟机。Steve Ballmer，这位把 Linux 称为癌症的首席执行官，已经离开了，代替他的是一位新的有远见的首席执行官 Satya Nadella。 + +John Gossman: Satya 有不同的看法。他属于另一个世代。比 Paul，Bill 和 Steve 更年轻的世代，他对开源有不同的看法。 + +Saron Yitbarek: John Gossman，再说一次，来自于 微软的 Azure 团队。 + +John Gossman: [00:16:00] 大约四年前，处于实际需要，我们在 Azure 中添加了 Linux 支持。如果访问任何一家企业客户，你都会发现他们并没有试图决定是使用 Windows 还是使用 Linux、 使用 .net 还是使用 Java TM。他们在很久以前就做出了决定——大约 15 年前才有这样的一些争论。现在，我见过的每一家公司都混合了 Linux 和 Java、Windows 和 .net、SQL Server、Oracle 和 MySQL—— 基于专有源代码的产品和开放源代码的产品。 + +如果你正在运维着一个云，允许这些公司在云上运行他们的业务，那么你就不能简单地告诉他们，“你可以使用这个软件，但你不能使用那个软件。” + +Saron Yitbarek: [00:16:30] 这正是 Satya Nadella 采纳的哲学思想。2014 年秋季，他站在舞台上，希望传递一个重要信息。微软爱 Linux。他接着说，Azure 20% 的业务量已经是 Linux 了，微软将始终对 Linux 发行版提供一流的支持。没有哪怕一丝对开源的宿怨。 + +为了说明这一点，在他们的背后有一个巨大的标志，上面写着 :“Microsoft hearts Linux”。哇哇哇。对我们中的一些人来说，这种转变有点令人震惊，但实际上，无需如此震惊。下面是 Steven Levy，一名科技记者兼作家。 + +Steven Levy: [00:17:30] 当你在踢足球的时候，如果草坪变滑了，那么你也许会换一种不同的鞋子。他们当初就是这么做的。他们不能否认现实而且他们之间也有有聪明人，所以他们必须意识到，这就是世界的运行方式，不管他们早些时候说了什么，即使他们对之前的言论感到尴尬，但是让他们之前关于开源多么可怕的言论影响到现在明智的决策那才真的是疯了。 + +Saron Yitbarek: [00:18:00] 微软低下了它高傲的头。你可能还记得苹果公司，经过多年的孤立无援，最终转向与微软构建合作伙伴关系。现在轮到微软进行 180 度转变了。经过多年的与开源方法的战斗后，他们正在重塑自己。要么改变，要么死亡。Steven Vaughan-Nichols。 + +Steven Vaughan-Nichols: [00:18:30] 即使是像微软这样规模的公司也无法与成千上万的开源开发者竞争，这些开发者开发这包括 Linux 在内的其他大项目。很长时间以来他们都不愿意这么做。前微软首席执行官史蒂夫·鲍尔默 （SteveBallmer） 对 Linux 深恶痛绝。由于它的 GPL 许可证，让 Linux 称为一种癌症，但一旦鲍尔默被扫地出门，新的微软领导层说，“这就好像试图命令潮流不要过来，但潮水依然会不断涌进来。我们应该与 Linux 合作，而不是与之对抗。” + +Saron Tiebreak: [00:19:00] 真的，在线技术历史上最大的胜利之一就是微软能够做出这样的转变，当他们最终决定这么做的时候。当然，当微软出现在开源的桌子上时，老的、铁杆 Linux 支持者是相当怀疑的。他们不确定自己是否能接受这些家伙，但正如沃恩-尼科尔斯所指出的，今天的微软根本不是你父母的微软。事实上，互联网技术历史上最大的胜利之一就是让微软最终做出如此转变。当然，当微软出现在开源桌上时，老一代的、铁杆 Linux 支持者是相当怀疑的。他们不确定自己是否能接受这些家伙，但正如 Vaughan-Nichols 所指出的，今天的微软已经不是你父母那一代时的微软了。 + +Steven Vaughan-Nichols : [00:19:30] 2017 年的微软既不是史蒂夫•鲍尔默 (Steve Ballmer) 的微软，也不是比尔•盖茨 (Bill Gates) 的微软。这是一家完全不同的公司，有着完全不同的方法，而且，开源软件一旦被放出，就无法被收回。开源已经吞噬了整个技术世界。从未听说过 Linux 的人可能对它并不了解，但是每次他们访问 Facebook，他们都在运行 Linux。每次执行谷歌搜索时，你都在运行 Linux。 + +[00:20:00] 每次你用 Android 手机，你都在运行 Linux。它确实无处不在，微软无法阻止它，我认为以为微软可以以某种方式接管它的想法，太天真了。 + +Saron Yitbarek: [00:20:30] 开源支持者可能一直担心微软会像混入羊群中的狼一样，但事实是，开源软件的本质保护了它无法被完全控制。没有一家公司能够拥有 Linux 并以某种特定的方式控制它。Greg Kroah-Hartman 是 Linux 基金会的一名成员。 + +Greg Kroah-Hartman: 每个公司和个人都以自私的方式为 Linux 做出贡献。他们之所以这样做是因为他们想要解决他们所面临的问题，可能是硬件无法工作，或者是他们想要添加一个新功能来做其他事情，又或者想在他们的产品中使用它。这很棒，因为他们会把代码贡献回去，此后每个人都会从中受益，这样每个人都可以用到这份代码。正是因为这种自私，所有的公司，所有的人，所有的人都能从中受益。 + +Saron Yitbarek: [00:21:30] 微软已经意识到，在即将到来的云战争中，与 Linux 作战就像与空气作战一样。Linux 和开源不是敌人，它们是一种氛围。今天，微软以白金会员的身份加入了 Linux 基金会。他们成为 GitHub 开源项目的头号贡献者。2017 年 9 月，他们甚至加入了 Open Source Initiative 组织。现在，微软在开放许可下发布了很多代码。微软的 John Gossman 描述了他们开源 .net 时所发生的事情。起初，他们并不认为自己能得到什么回报。 + +John Gossman: [00:22:00] 我们本没有指望来自社区的贡献，然而，三年后，超过 50% 的对 .net 框架库的贡献来自于微软之外。这包括大量的代码。三星为 .net 提供了 ARM 支持。Intel 和 ARM 以及其他一些芯片厂商已经为 .net 框架贡献了特定于他们处理器的代码生成，以及数量惊人的修复、性能改进等等——既有单个贡献者也有社区。 + +Saron Yitbarek: 直到几年前，我们今天拥有的这个微软，这个开放的微软，还是不可想象的。 + +[00:23:00] 我是 Saron Yitbarek，这里是代码英雄。好吧，我们已经看到了为了赢得数百万桌面用户的爱而战的激烈场面。我们已经看到开源软件在私有巨头的背后悄然崛起，并攫取了巨大的市场份额。我们已经看到了一批批的代码英雄将编程领域变成了我你现在看到的这个样子。今天，大企业正在吸收开源软件，通过这一切，每个人都从他人那里受益。 + +[00:23:30] 在狂野的西方科技界，一贯如此。苹果受到施乐的启发，微软受到苹果的启发，Linux 受到 UNIX 的启发。进化，借鉴，不断成长。如果比喻成大卫和歌利亚(西方经典的以弱胜强战争中的两个主角)的话，开源软件不再是大卫，但是，你知道吗？它也不是歌利亚。开源已经超越了传统。它已经成为其他人战斗的战场。随着开源变得不可避免，新的战争，那些在云计算中进行的战争，那些在开源战场上进行的战争，都在增加。 + +这是 Steven Levy，他是一名作者。 + +Steven Levy: [00:24:00] 基本上，到目前为止，包括微软在内，我们有四到五家公司，正以各种方式努力把自己打造成为我们的工作平台，比如人工智能领域。你能看到智能助手之间的战争，你猜怎么着？苹果有一个智能助手，叫 Siri。微软有一个，叫 Cortana。谷歌有谷歌助手。三星也有一个智能助手。亚马逊也有一个，叫 Alexa。我们看到这些战斗遍布各地。也许，你可以说，最热门的人工智能平台将控制我们生活中所有的东西，而这五家公司就是在为此而争斗。 + +Saron Yitbarek: 现在很难再找到另一个反叛者，它就像 Linux 奇袭微软那样，偷偷潜入 Facebook、 谷歌或亚马逊，攻其不备。因为正如作家 James Allworth 所指出的，成为一个真正的反叛者者只会变得越来越难。 + +James Allworth: [00:25:30] 规模一直以来都是一种优势，但规模优势本质上……怎么说呢，我认为以前它们在本质上是线性的，现在它们在本质上是指数型的了，所以，一旦你开始以某种方法走在前面，另一个新玩家要想赶上来就变得越来越难了。我认为在互联网时代这大体来说来说是正确的，无论是因为规模，还是数据赋予组织的重要性和优势，就其竞争能力而言。一旦你走在前面，你就会吸引更多的客户，这就给了你更多的数据，让你能做得更好，这之后，客户还有什么理由选择排名第二的公司呢，难道是因为因为他们落后了这么远么？我认为在云的时代这个逻辑也不会有什么不同。 + +Saron Yitbarek: [00:26:00] 这个故事始于史蒂夫•乔布斯 (Steve Jobs) 和比尔•盖茨 (Bill Gates) 这样的非凡的英雄，但科技的进步已经呈现出一种众包、有机的感觉。我认为据说我们的开源英雄 Linus Torvalds 在第一次发明 Linux 内核时甚至没有一个真正的计划。他无疑是一位才华横溢的年轻开发者，但他也像潮汐前的一滴水一样。变革是不可避免的。据估计，对于一家私有专利公司来说，用他们老式的、专有的方式创建一个 Linux 发行版将花费他们超过 100 亿美元。这说明了开源的力量。 + +[00:26:30] 最后，这并不是一个专利模型所能与之竞争的东西。成功的公司必须保持开放。这是最大、最终极的教训。还有一点要记住：当我们连接在一起的时候，我们在已有基础上成长和建设的能力是无限的。不管这些公司有多大，我们都不必坐等他们给我们更好的东西。想想那些为了纯粹的创造乐趣而学习编码的新开发者，那些自己动手丰衣足食的人。 + +未来的优秀程序员无管来自何方，只要能够访问代码，他们就能构建下一个大项目。 + +[00:27:30] 以上就是我们关于操作系统战争的两个故事。这场战争塑造了我们的数字生活。争夺主导地位的斗争从桌面转移到了服务器室，最终进入了云计算领域。过去的敌人难以置信地变成了盟友，众包的未来让一切都变得开放。听着，我知道，在这段历史之旅中，还有很多英雄我们没有提到，所以给我们写信吧。分享你的故事。Redhat.com/commandlineheroes。我恭候佳音。 + +在本季剩下的时间里，我们将学习今天的英雄们在创造什么，以及他们要经历什么样的战斗才能将他们的创造变为现实。让我们从艰苦卓绝的编程一线回来看看更多的传奇故事吧。我们每两周放一集新的博客。几周后，我们将为您带来第三集：敏捷革命。 + +[00:28:00] 命令行英雄是一款红帽公司原创的播客。要想免费自动获得新一集的代码英雄，请订阅我们的节目。只要在苹果播客 、Spotify、 谷歌 Play，或其他应用中搜索“代码英雄”。然后点击“订阅”。这样你就会第一个知道什么时候有新剧集了。 + +我是 Saron Yitbarek。感谢收听。继续编码。 + +-------------------------------------------------------------------------------- + +via: https://www.redhat.com/en/command-line-heroes/season-1/os-wars-part-2-rise-of-linux + +作者：[redhat][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.redhat.com +[b]: https://github.com/lujun9972 From 77a15e6dd8a76d313959217291bcdc2081b05f01 Mon Sep 17 00:00:00 2001 From: darksun Date: Sat, 24 Aug 2019 18:01:08 +0800 Subject: [PATCH 15/58] =?UTF-8?q?=E9=80=89=E9=A2=98:=2020190729=20I=20Used?= =?UTF-8?q?=20The=20Web=20For=20A=20Day=20On=20A=2050=20MB=20Budget=20?= =?UTF-8?q?=E2=80=94=20Smashing=20Magazine?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit sources/talk/20190729 I Used The Web For A Day On A 50 MB Budget - Smashing Magazine.md --- ...y On A 50 MB Budget - Smashing Magazine.md | 538 ++++++++++++++++++ 1 file changed, 538 insertions(+) create mode 100644 sources/talk/20190729 I Used The Web For A Day On A 50 MB Budget - Smashing Magazine.md diff --git a/sources/talk/20190729 I Used The Web For A Day On A 50 MB Budget - Smashing Magazine.md b/sources/talk/20190729 I Used The Web For A Day On A 50 MB Budget - Smashing Magazine.md new file mode 100644 index 0000000000..b0a7f4a7e0 --- /dev/null +++ b/sources/talk/20190729 I Used The Web For A Day On A 50 MB Budget - Smashing Magazine.md @@ -0,0 +1,538 @@ +[#]: collector: (lujun9972) +[#]: translator: ( ) +[#]: reviewer: ( ) +[#]: publisher: ( ) +[#]: url: ( ) +[#]: subject: (I Used The Web For A Day On A 50 MB Budget — Smashing Magazine) +[#]: via: (https://www.smashingmagazine.com/2019/07/web-on-50mb-budget/) +[#]: author: (Chris Ashton https://www.smashingmagazine.com/author/chrisbashton) + +I Used The Web For A Day On A 50 MB Budget +====== + +Data can be prohibitively expensive, especially in developing countries. Chris Ashton puts himself in the shoes of someone on a tight data budget and offers practical tips for reducing our websites’ data footprint. + +This article is part of a series in which I attempt to use the web under various constraints, representing a given demographic of user. I hope to raise the profile of difficulties faced by real people, which are avoidable if we design and develop in a way that is sympathetic to their needs. + +Last time, I [navigated the web for a day using Internet Explorer 8][7]. This time, I browsed the web for a day on a 50 MB budget. + +### Why 50 MB? + +Many of us are lucky enough to be on mobile plans which allow several gigabytes of data transfer per month. Failing that, we are usually able to connect to home or public WiFi networks that are on fast broadband connections and have effectively unlimited data. + +But there are parts of the world where mobile data is prohibitively expensive, and where there is little or no broadband infrastructure. + +> People often buy data packages of just tens of megabytes at a time, making a gigabyte a relatively large and therefore expensive amount of data to buy. +> — Dan Howdle, consumer telecoms analyst at Cable.co.uk + +Just how expensive are we talking? + +#### The Cost Of Mobile Data + +A 2018 [study by cable.co.uk][8] found that Zimbabwe was the most expensive country in the world for mobile data, where 1 GB cost an average of $75.20, ranging from $12.50 to $138.46. The enormous range in price is due to smaller amounts of data being very expensive, getting proportionally cheaper the bigger the data plan you commit to. You can read the [study methodology][9] for more information. + +Zimbabwe is by no means a one-off. Equatorial Guinea, Saint Helena and the Falkland Islands are next in line, with 1 GB of data costing $65.83, $55.47 and $47.39 respectively. These countries generally have a combination of poor technical infrastructure and low adoption, meaning data is both costly to deliver and doesn’t have the economy of scale to drive costs down. + +Data is expensive in parts of Europe too. A gigabyte of data in Greece will set you back $32.71; in Switzerland, $20.22. For comparison, the same amount of data costs $6.66 in the UK, or $12.37 in the USA. On the other end of the scale, India is the cheapest place in the world for data, at an average cost of $0.26. Kyrgyzstan, Kazakhstan and Ukraine follow at $0.27, $0.49 and $0.51 per GB respectively. + +The speed of mobile networks, too, varies considerably between countries. Perhaps surprisingly, [users experience faster speeds over a mobile network than WiFi][10] in at least 30 countries worldwide, including Australia and France. South Korea has the [fastest mobile download speed][11], averaging 52.4 Mbps, but Iraq has the slowest, averaging 1.6 Mbps download and 0.7 Mbps upload. The USA ranks 40th in the world for mobile download speeds, at around 34 Mbps, and is [at risk of falling further behind][12] as the world moves towards 5G. + +As for mobile network connection type, 84.7% of user connections in the UK are on 4G, compared to 93% in the USA, and 97.5% in South Korea. This compares with less than 50% in Uzbekistan and less than 60% in Algeria, Ecuador, Nepal and Iraq. + +#### The Cost Of Broadband Data + +Meanwhile, a [study of the cost of broadband in 2018][13] shows that a broadband connection in Niger costs $263 ‘per megabit per month’. This metric is a little difficult to comprehend, so here’s an example: if the average cost of broadband packages in a country is $22, and the average download speed offered by the packages is 10 Mbps, then the cost ‘per megabit per month’ would be $2.20. + +It’s an interesting metric, and one that acknowledges that broadband speed is as important a factor as the data cap. A cost of $263 suggests a combination of extremely slow and extremely expensive broadband. For reference, the metric is $1.19 in the UK and $1.26 in the USA. + +What’s perhaps easier to comprehend is the average cost of a broadband package. Note that this study was looking for the cheapest broadband packages on offer, ignoring whether or not these packages had a data cap, so provides a useful ballpark figure rather than the cost of data per se. + +On package cost alone, Mauritania has the most expensive broadband in the world, at an average of $768.16 (a range of $307.26 to $1,368.72). This enormous cost includes building physical lines to the property, since few already exist in Mauritania. At 0.7 Mbps, Mauritania also has one of the slowest broadband networks in the world. + +[Taiwan has the fastest broadband in the world][14], at a mean speed of 85 Mbps. Yemen has the slowest, at 0.38 Mbps. But even countries with good established broadband infrastructure have so-called ‘not-spots’. The United Kingdom is ranked 34th out of 207 countries for broadband speed, but in July 2019 there was [still a school in the UK without broadband][15]. + +The average cost of a broadband package in the UK is $39.58, and in the USA is $67.69. The cheapest average in the world is Ukraine’s, at just $5, although the cheapest broadband deal of them all was found in Kyrgystan ($1.27 — against the country average of $108.22). + +Zimbabwe was the most costly country for mobile data, and the statistics aren’t much better for its broadband, with an average cost of $128.71 and a ‘per megabit per month’ cost of $6.89. + +#### Absolute Cost vs Cost In Real Terms + +All of the costs outlined so far are the absolute costs in USD, based on the exchange rates at the time of the study. These costs have [not been accounted for cost of living][16], meaning that for many countries the cost is actually far higher in real terms. + +I’m going to limit my browsing today to 50 MB, which in Zimbabwe would cost around $3.67 on a mobile data tariff. That may not sound like much, but teachers in Zimbabwe were striking this year because their [salaries had fallen to just $2.50 a day][17]. + +For comparison, $3.67 is around half the [$7.25 minimum wage in the USA][18]. As a Zimbabwean, I’d have to work for around a day and a half to earn the money to buy this 50MB data, compared to just half an hour in the USA. It’s not easy to compare cost of living between countries, but on wages alone the $3.67 cost of 50 MB of data in Zimbabwe would feel like $52 to an American on minimum wage. + +### Setting Up The Experiment + +I launched Chrome and opened the dev tools, where I throttled the network to a slow 3G connection. I wanted to simulate a slow connection like those experienced by users in Uzbekistan, to see what kind of experience websites would give me. I also throttled my CPU to simulate being on a lower end device. + +[![][19]][20]I opted to throttle my network to Slow 3G and my CPU to 6x slowdown. ([Large preview][20]) + +I installed [ModHeader][21] and set the [‘Save-Data’ header][22] to let websites know I want to minimise my data usage. This is also the header set by Chrome for Android’s ‘Lite mode’, which I’ll cover in more detail later. + +I downloaded [TripMode][23]; an application for Mac which gives you control over which apps on your Mac can access the internet. Any other application’s internet access is automatically blocked. + +You can enable/disable individual apps from connecting to the internet with TripMode. I enabled Chrome. ([Large preview][24]) + +How far do I predict my 50 MB budget will take me? With the [average weight of a web page being almost 1.7 MB][25], that suggests I’ve got around 29 pages in my budget, although probably a few more than that if I’m able to stay on the same sites and leverage browser caching. + +Throughout the experiment I will suggest performance tips to speed up the [first contentful paint][26] and perceived loading time of the page. Some of these tips may not affect the amount of data transferred directly, but do generally involve deferring the download of less important resources, which on slow connections may mean the resources are never downloaded and data is saved. + +### The Experiment + +Without any further ado, I loaded google.com, using 402 KB of my budget and spending $0.03 (around 1% of my Zimbabwe budget). + +[![402 KB transferred, 1.1 MB resources, 24 requests][27]][28]402 KB transferred, 1.1 MB resources, 24 requests. ([Large preview][28]) + +All in all, not a bad page size, but I wondered where those 24 network requests were coming from and whether or not the page could be made any lighter. + +#### Google Homepage — DOM + +[![][29]][30]Chrome devtools screenshot of the DOM, where I’ve expanded one inline `style` tag. ([Large preview][30]) + +Looking at the page markup, there are no external stylesheets — all of the CSS is inline. + +##### Performance Tip #1: Inline Critical CSS + +This is good for performance as it saves the browser having to make an additional network request in order to fetch an external stylesheet, so the styles can be parsed and applied immediately for the first contentful paint. There’s a trade-off to be made here, as external stylesheets can be cached but inline ones cannot (unless you [get clever with JavaScript][31]). + +The general advice is for your [critical styles][32] (anything [above-the-fold][33]) to be inline, and for the rest of your styling to be external and loaded asynchronously. Asynchronous loading of CSS can be achieved in [one remarkably clever line of HTML][34]: + +``` + +``` + +The devtools show a prettified version of the DOM. If you want to see what was actually downloaded to the browser, switch to the Sources tab and find the document. + +[![A wall of minified code.][35]][36]Switching to Sources and finding the index shows the ‘raw’ HTML that was delivered to the browser. What a mess! ([Large preview][36]) + +You can see there is a LOT of inline JavaScript here. It’s worth noting that it has been uglified rather than merely minified. + +##### Performance Tip #2: Minify And Uglify Your Assets + +Minification removes unnecessary spaces and characters, but uglification actually ‘mangles’ the code to be shorter. The tell-tale sign is that the code contains short, machine-generated variable names rather than untouched source code. This is good as it means the script is smaller and quicker to download. + +Even so, inline scripts look to be roughly 120 KB of the 210 KB page resource (about half the 60 KB gzipped size). In addition, there are five external JavaScript files amounting to 291 KB of the 402 KB downloaded: + +[![Network tab of DevTools showing the external javascript files][37]][38]Five external JavaScript files in the Network tab of the devtools. ([Large preview][38]) + +This means that JavaScript accounts for about 80 percent of the overall page weight. + +This isn’t useless JavaScript; Google has to have some in order to display suggestions as you type. But I suspect a lot of it is tracking code and advertising setup. + +For comparison, I disabled JavaScript and reloaded the page: + +[![DevTools showing only 5 network requests][39]][40]The disabled JS version of Google search was only 102 KB and had just 5 network requests. ([Large preview][40]) + +The JS-disabled version of Google search is just 102 KB, as opposed to 402 KB. Although Google can’t provide autosuggestions under these conditions, the site is still functional, and I’ve just cut my data usage down to a quarter of what it was. If I really did have to limit my data usage in the long term, one of the first things I’d do is disable JavaScript. [It’s not as bad as it sounds][41]. + +##### Performance Tip #3: Less Is More + +Inlining, uglifying and minifying assets is all well and good, but the best performance comes from not sending down the assets in the first place. + + * Before adding any new features, do you have a [performance budget][42] in place? + * Before adding JavaScript to your site, can your feature be accomplished using plain HTML? (For example, [HTML5 form validation][43]). + * Before pulling a large JavaScript or CSS library into your application, use something like [bundlephobia.com][44] to measure how big it is. Is the convenience worth the weight? Can you accomplish the same thing using vanilla code at a much smaller data size? + + + +#### Analysing The Resource Info + +There’s a lot to unpack here, so let’s get cracking. I’ve only got 50 MB to play with, so I’m going to milk every bit of this page load. Settle in for a short Chrome Devtools tutorial. + +402 KB transferred, but 1.1 MB of resources: what does that actually mean? + +It means 402 KB of content was actually downloaded, but in its compressed form (using a compression algorithm such as [gzip or brotli][45]). The browser then had to do some work to unpack it into something meaningful. The total size of the unpacked data is 1.1 MB. + +This unpacking isn’t free — [there are a few milliseconds of overhead in decompressing the resources][46]. But that’s a negligible overhead compared to sending 1.1MB down the wire. + +##### Performance Tip #4: Compress Text-based Assets + +As a general rule, always compress your assets, using something like gzip. But don’t use compression on your images and other binary files — you should optimize these in advance at source. Compression could actually end up [making them bigger][47]. + +And, if you can, [avoid compressing files that are 1500 bytes or smaller][47]. The smallest TCP packet size is 1500 bytes, so by compressing to, say, 800 bytes, you save nothing, as it’s still transmitted in the same byte packet. Again, the cost is negligible, but wastes some compression CPU time on the server and decompression CPU time on the client. + +Now back to the Network tab in Chrome: let’s dig into those priorities. Notice that resources have priority “Highest” to “Lowest” — these are the browser’s best guess as to what are the more important resources to download. The higher the priority, the sooner the browser will try to download the asset. + +##### Performance Tip #5: Give Resource Hints To The Browser + +The browser will guess at what the highest priority assets are, but you can [provide a resource hint][48] using the `` tag, instructing the browser to download the asset as soon as possible. It’s a good idea to preload fonts, logos and anything else that appears above the fold. + +Let’s talk about caching. I’m going to hold ALT and right-click to change my column headers to unlock some more juicy information. We’re going to check out Cache-Control. + +There are lots of interesting fields tucked away behind ALT. ([Large preview][49]) + +Cache-Control denotes whether or not a resource can be cached, how long it can be cached for, and what rules it should follow around [revalidating][50]. Setting proper cache values is crucial to keeping the data cost of repeat visits down. + +##### Performance Tip #6: Set cache-control Headers On All Cacheable Assets + +Note that the cache-control value begins with a directive of `public` or `private`, followed by an expiration value (e.g. `max-age=31536000`). What does the directive mean, and why the oddly specific `max-age` value? + +[![Screenshot of Google network tab with cache-control column visible][51]][52]A mixture of max-age values and public/private. ([Large preview][52]) + +The value `31536000` is the number of seconds there are in a year, and is the theoretical maximum value allowed by the cache-control specification. It is common to see this value applied to all static assets and effectively means “this resource isn’t going to change”. In practice, [no browser is going to cache for an entire year][53], but it will cache the asset for as long as makes sense. + +To explain the public/private directive, we must explain the two main caches that exist off the server. First, there is the traditional browser cache, where the resource is stored on the user’s machine (the ‘client’). And then there is the CDN cache, which sits between the client and the server; resources are cached at the CDN level to prevent the CDN from requesting the resource from the origin server over and over again. + +A `Cache-Control` directive of `public` allows the resource to be cached in both the client and the CDN. A value of `private` means only the client can cache it; the CDN is not supposed to. This latter value is typically used for pages or assets that exist behind authentication, where it is fine to be cached on the client but we wouldn’t want to leak private information by caching it in the CDN and delivering it to other users. + +[![Screenshot of Google logo cache-control setting: private, max-age=31536000][54]][55]A mixture of max-age values and public/private. ([Large preview][55]) + +One thing that got my attention was that the Google logo has a cache control of “private”. Other images on the page do have a public cache, and I don’t know why the logo would be treated any differently. If you have any ideas, let me know in the comments! + +I refreshed the page and most of the resources were served from cache, apart from the page itself, which as you’ve seen already is `private, max-age=0`, meaning it cannot be cached. This is normal for dynamic web pages where it is important that the user always gets the very latest page when they refresh. + +It was at this point I accidentally clicked on an ‘Explanation’ URL in the devtools, which took me to the [network analysis reference][56], costing me about 5 MB of my budget. Oops. + +### Google Dev Docs + +4.2 MB of this new 5 MB page was down to images; specifically SVGs. The weightiest of these was 186 KB, which isn’t particularly big — there were just so many of them, and they all downloaded at once. + +This is a loooong page. All the images downloaded on page load. ([Large preview][57]) + +That 5 MB page load was 10% of my budget for today. So far I’ve used 5.5 MB, including the no-JavaScript reload of the Google homepage, and spent $0.40. I didn’t even mean to open this page. + +What would have been a better user experience here? + +##### Performance Tip #7: Lazy-load Your Images + +Ordinarily, if I accidentally clicked on a link, I would hit the back button in my browser. I’d have received no benefit whatsoever from downloading those images — what a waste of 4.2 MB! + +Apart from video, where you generally know what you’re getting yourself into, images are by far the biggest culprit to data usage on the web. A [study of the world’s top 500 websites][58] found that images take up to 53% of the average page weight. “This means they have a big impact on page-loading times and subsequently overall performance”. + +Instead of downloading all of the images on page load, it is good practice to lazy-load the images so that only users who are engaged with the page pay the cost of downloading them. Users who choose not to scroll below the fold therefore don’t waste any unnecessary bandwidth downloading images they’ll never see. + +There’s a great [css-tricks.com guide to rolling out lazy-loading for images][59] which offers a good balance between those on good connections, those on poor connections, and those with JavaScript disabled. + +If this page had implemented lazy loading as per the guide above, each of the 38 SVGs would have been represented by a 1 KB placeholder image by default, and only loaded into view on scroll. + +##### Performance Tip #8: Use The Right Format For Your Images + +I thought that Google had missed a trick by not using [WebP][60], which is an image format that is 26% smaller in size compared to PNGs (with no loss in quality) and 25-34% smaller in size compared to JPEGs (and of a comparable quality). I thought I’d have a go at converting SVG to WebP. + +Converting to WebP did bring one of the SVGs down from 186 KB to just 65 KB, but actually, looking at the images side by side, the WebP came out grainy: + +[![Comparison of the two images][61]][62]The SVG (left) is noticeably crisper than the WebP (right). ([Large preview][62]) + +I then tried converting one of the PNGs to WebP, which is supposed to be lossless and should come out smaller. However, the WebP output was *heavier* (127 KB, from 109 KB)! + +[![Comparison of the two images][63]][64]The PNG (left) is a similar quality to the WebP (right) but is smaller at 109 KB compared to 127 KB. ([Large preview][64]) + +This surprised me. WebP isn’t necessarily the silver bullet we think it is, and even Google have neglected to use it on this page. + +So my advice would be: where possible, experiment with different image formats on a per-image basis. The format that keeps the best quality for the smallest size may not be the one you expect. + +Now back to the DOM. I came across this: + +Notice the `async` keyword on the Google analytics script? + +[![Screenshot of performance analysis output of devtools][65]][66]Google analytics has ‘low’ priority. ([Large preview][66]) + +Despite being one of the first things in the head of the document, this was given a low priority, as we’ve explicitly opted out of being a blocking request by using the `async` keyword. + +A blocking request is one that stops the rendering of the page. A `