mirror of
https://github.com/LCTT/TranslateProject.git
synced 2025-03-21 02:10:11 +08:00
Merge branch 'master' of https://github.com/LCTT/TranslateProject
This commit is contained in:
runningwater
commit
a6fcb37eee
83
README.md
83
README.md
@ -1,11 +1,11 @@
|
||||
简介
|
||||
-------------------------------
|
||||
|
||||
LCTT是Linux中国社区（[http://linux.cn/](http://linux.cn/)）的翻译组，负责从国外优秀媒体翻译Linux相关的技术、资讯、杂文等内容。
|
||||
LCTT是“Linux中国”（[http://linux.cn/](http://linux.cn/)）的翻译组，负责从国外优秀媒体翻译Linux相关的技术、资讯、杂文等内容。
|
||||
|
||||
LCTT已经拥有近百余名活跃成员，并欢迎更多的Linux志愿者加入我们的团队。
|
||||
|
||||
|
||||
|
||||
|
||||
LCTT的组成
|
||||
-------------------------------
|
||||
@ -18,11 +18,10 @@ LCTT的组成
|
||||
|
||||
**发布**，负责将校对后的文章，排版进行发布。
|
||||
|
||||
|
||||
加入我们
|
||||
-------------------------------
|
||||
|
||||
请首先加入翻译组的QQ群，群号是：198889102，加群时请说明是志愿者。加入后记得修改您的群名片为您的github的ID。
|
||||
请首先加入翻译组的QQ群，群号是：198889102，加群时请说明是“志愿者”。加入后记得修改您的群名片为您的github的ID。
|
||||
|
||||
加入的成员，请先阅读[WIKI 如何开始](https://github.com/LCTT/TranslateProject/wiki/01-如何开始)。
|
||||
|
||||
@ -39,62 +38,75 @@ LCTT的组成
|
||||
- CORE [carolinewuyan](https://github.com/carolinewuyan),
|
||||
- CORE [DeadFire](https://github.com/DeadFire),
|
||||
- CORE [geekpi](https://github.com/geekpi),
|
||||
- CORE [tinyeyeser](https://github.com/tinyeyeser),
|
||||
- CORE [vito-L](https://github.com/vito-L),
|
||||
- CORE [jasminepeng](https://github.com/jasminepeng),
|
||||
- CORE [willqian](https://github.com/willqian),
|
||||
- CORE [vizv](https://github.com/vizv),
|
||||
- CORE [GOLinux](https://github.com/GOLinux),
|
||||
- [luoxcat](https://github.com/Luoxcat),
|
||||
- CORE [reinoir](https://github.com/reinoir),
|
||||
- Senior [tinyeyeser](https://github.com/tinyeyeser),
|
||||
- Senior [vito-L](https://github.com/vito-L),
|
||||
- Senior [jasminepeng](https://github.com/jasminepeng),
|
||||
- Senior [willqian](https://github.com/willqian),
|
||||
- Senior [vizv](https://github.com/vizv),
|
||||
- [runningwater](https://github.com/runningwater),
|
||||
- [luoxcat](https://github.com/Luoxcat),
|
||||
- [bazz2](https://github.com/bazz2),
|
||||
- [Vic020](https://github.com/Vic020),
|
||||
- [flsf](https://github.com/flsf),
|
||||
- [alim0x](https://github.com/alim0x),
|
||||
- [KayGuoWhu](https://github.com/KayGuoWhu),
|
||||
- [zpl1025](https://github.com/zpl1025),
|
||||
- [blueabysm](https://github.com/blueabysm),
|
||||
- [flsf](https://github.com/flsf),
|
||||
- [crowner](https://github.com/crowner),
|
||||
- [Linux-pdz](https://github.com/Linux-pdz),
|
||||
- [KayGuoWhu](https://github.com/KayGuoWhu),
|
||||
- [Linchenguang](https://github.com/Linchenguang),
|
||||
- [woodboow](https://github.com/woodboow),
|
||||
- [zpl1025](https://github.com/zpl1025),
|
||||
- [yechunxiao19](https://github.com/yechunxiao19),
|
||||
- [blueabysm](https://github.com/blueabysm),
|
||||
- [linuhap](https://github.com/linuhap),
|
||||
- [2q1w2007](https://github.com/2q1w2007),
|
||||
- [yechunxiao19](https://github.com/yechunxiao19),
|
||||
- [woodboow](https://github.com/woodboow),
|
||||
- [su-kaiyao](https://github.com/su-kaiyao),
|
||||
- [scusjs](https://github.com/scusjs),
|
||||
- [hyaocuk](https://github.com/hyaocuk),
|
||||
- [theo-l](https://github.com/theo-l),
|
||||
- [NearTan](https://github.com/NearTan),
|
||||
- [l3b2w1](https://github.com/l3b2w1),
|
||||
- [ThomazL](https://github.com/ThomazL),
|
||||
- [MikeCoder](https://github.com/MikeCoder),
|
||||
- [shipsw](https://github.com/shipsw),
|
||||
- [boredivan](https://github.com/boredivan),
|
||||
- [ThomazL](https://github.com/ThomazL),
|
||||
- [theo-l](https://github.com/theo-l),
|
||||
- [jiajia9linuxer](https://github.com/jiajia9linuxer),
|
||||
- [SteveArcher](https://github.com/SteveArcher),
|
||||
- [l3b2w1](https://github.com/l3b2w1),
|
||||
- [NearTan](https://github.com/NearTan),
|
||||
- [shipsw](https://github.com/shipsw),
|
||||
- [disylee](https://github.com/disylee),
|
||||
- [Love-xuan](https://github.com/Love-xuan),
|
||||
- [boredivan](https://github.com/boredivan),
|
||||
- [cvsher](https://github.com/cvsher),
|
||||
- [owen-carter](https://github.com/owen-carter),
|
||||
- [JonathanKang](https://github.com/JonathanKang),
|
||||
- [tenght](https://github.com/tenght),
|
||||
- [icybreaker](https://github.com/icybreaker),
|
||||
- [liuaiping](https://github.com/liuaiping),
|
||||
- [tenght](https://github.com/tenght),
|
||||
- [rogetfan](https://github.com/rogetfan),
|
||||
- [nd0104](https://github.com/nd0104),
|
||||
- [whatever1992](https://github.com/whatever1992),
|
||||
- [2q1w2007](https://github.com/2q1w2007),
|
||||
- [disylee](https://github.com/disylee),
|
||||
- [SteveArcher](https://github.com/SteveArcher),
|
||||
- [JonathanKang](https://github.com/JonathanKang),
|
||||
- [zzlyzq](https://github.com/zzlyzq),
|
||||
- [FineFan](https://github.com/FineFan),
|
||||
- [ailurus1991](https://github.com/ailurus1991),
|
||||
- [lfzark](https://github.com/lfzark),
|
||||
- [CNprober](https://github.com/CNprober),
|
||||
- [213edu](https://github.com/213edu),
|
||||
- [johnhoow](https://github.com/johnhoow),
|
||||
- [yujianxuechuan](https://github.com/yujianxuechuan),
|
||||
- [ggaaooppeenngg](https://github.com/ggaaooppeenngg),
|
||||
- [zzlyzq](https://github.com/zzlyzq),
|
||||
- [ailurus1991](https://github.com/ailurus1991),
|
||||
- [FineFan](https://github.com/FineFan),
|
||||
- [tomatoKiller](https://github.com/tomatoKiller),
|
||||
- [stduolc](https://github.com/stduolc),
|
||||
- [Maclauring](https://github.com/Maclauring),
|
||||
- [Hao-Ding](https://github.com/Hao-Ding),
|
||||
- [small-Wood](https://github.com/small-Wood),
|
||||
- [zsJacky](https://github.com/zsJacky),
|
||||
- [Hao-Ding](https://github.com/Hao-Ding),
|
||||
- [luoyutiantang](https://github.com/luoyutiantang),
|
||||
- [small-Wood](https://github.com/small-Wood),
|
||||
- [CHINAANSHE](https://github.com/CHINAANSHE),
|
||||
- [ggaaooppeenngg](https://github.com/ggaaooppeenngg),
|
||||
- [guodongxiaren](https://github.com/guodongxiaren),
|
||||
- [cereuz](https://github.com/cereuz),
|
||||
- [lijhg](https://github.com/lijhg),
|
||||
|
||||
|
||||
（更新于2014/06/18）
|
||||
（更新于2014/09/09）
|
||||
|
||||
谢谢大家的支持！
|
||||
|
||||
@ -112,4 +124,5 @@ LCTT的组成
|
||||
* 2014/01/02 增加了Core Translators 成员: geekpi。
|
||||
* 2014/05/04 更换了新的QQ群：198889102
|
||||
* 2014/05/16 增加了Core Translators 成员: will.qian、vizv。
|
||||
* 2014/06/18 由于GOLinux令人惊叹的翻译速度和不错的翻译质量，升级为Core Translators 成员。
|
||||
* 2014/06/18 由于GOLinux令人惊叹的翻译速度和不错的翻译质量，升级为Core Translators 成员。
|
||||
* 2014/09/09 LCTT 一周年，做一年总结。并将曾任 CORE 的成员分组为 Senior，以表彰他们的贡献。
|
||||
80
lctt2014.md
Normal file
80
lctt2014.md
Normal file
@ -0,0 +1,80 @@
|
||||
LCTT 2014 ： LCTT 成立一年总结
|
||||
============================
|
||||
|
||||
### 缘起 ###
|
||||
|
||||
一年前，我因为开发 Linux 中国的微信公众号，想着在公众号里面提供 Linux 的 man 手册应该是个不错的主意，因此在网上遍寻中文 man 手册。虽然我之前也寻找过中文的 man 手册，知道颇多不全和错漏，但是这次仔细搜寻之下，却发现还远较我预计的还差。
|
||||
|
||||
无奈之下，只能先使用了英文版本作为 man 的内容，并因此萌发了组织一个翻译 man 手册的活动或组织的想法。说干就干，当时我就在 Linux 中国的 QQ 群里面发起了倡议，还真得到了大家响应。
|
||||
|
||||
于是，2013 年 9 月 10日，草草而就的 LCTT 就成立了，很快就创建了一个 QQ 群作为交流，并确定了名称为“Linux.CN Translate Team”，简称 LCTT。考虑到需要多人协作，几乎没有多想，就决定了采用 GITHUB 作为翻译平台——虽然现在看起来，GITHUB 作为主要工作平台，有利也有弊，但是，总体来说还是不错的。LCTT 就这样启动了。
|
||||
|
||||
### 发展 ###
|
||||
|
||||
次日，我们就组织起来了翻译，并初步拟定了翻译流程、分工之类的内容。
|
||||
|
||||
LCTT 草创，各种方面都没有经验，也出现过一些失误。比如说，开始时对于 GITHUB 以及 GIT，大部分人，包括我，都不是很熟悉，因此并未采用 Pull-Request 模式，而是共同控制的方式，也由于一些协调和经验的原因，出现过版本错误和回滚，甚至回滚得更乱。还有，初期还要求 LINUX 中国网站 的注册身份，但是后来发现这完全不必要。
|
||||
|
||||
本来成立 LCTT 的目标是为了 man 手册的翻译，但是经过研究，我发现翻译 man 手册还有一些困难：
|
||||
|
||||
1. man 手册是二进制的 groff 格式，因此生成和解析需要一些额外的过程，甚至需要一些特定的环境；
|
||||
2. man 手册对翻译的能力要求较高，并且应该对 man 手册所对应的命令有足够的了解，才能翻译得当，因为一字之差就可能导致很多误解。
|
||||
|
||||
所以，当时商量决定，先期启动普通的 Linux 方面、开源方面的文章翻译，以此来摸索翻译流程和锻炼协作，并作为翻译 man 手册的人员筛选环节。
|
||||
|
||||
我安排 Linux 中国站长，原本经常独自翻译发表来自国外文章的 DeadFire 来做选题。他负责将选题从英文的页面，转换成 Markdown 格式。我又找了朋友 jasminepeng 和 carolinewuyan 帮忙做校对，我自己则主要承担发布的工作。
|
||||
|
||||
初期，很快就涌现出了一些积极参与的人员，如 tinyeyeser、vito-L、boredivanivan等等，不一一列举了，他们不但积极参与翻译，而且还帮助撰写了第一批的翻译组 Wiki 文档，对引导新人起到了很大作用。
|
||||
|
||||
伴随着 LCTT 的逐步运作，一个月之后，我和大家感觉时间比较成熟了，就启动了 man 翻译计划。
|
||||
|
||||
### man 翻译计划的夭折 ###
|
||||
|
||||
_写下这个标题时，我也颇感觉惭愧的，这也算是我正视这个结果吧。不管怎么说，现在还是深夜，未过零点，我终究是在 LCTT 一周年之前正视了失败。_
|
||||
|
||||
其实，前面提到过，我检索过各种可以找到的中文 man 翻译项目的结果，但种种结果让人无法满意，因此我觉得，我应该能吸取其中的教训，为 Linux、为开源做点实事出来。
|
||||
|
||||
我总结的之前的 man 翻译项目失败的原因大概如下：
|
||||
|
||||
1. 缺乏足够的驱动力，翻译者无论从利益还是荣誉，都得不到鼓励，因此往往难以为继。
|
||||
2. 由于依赖个人热情，没有形成流动机制，因此，当某个人热情耗尽之后，就没有人继续接手维护。
|
||||
3. 翻译流程简单，没有形成初译、校对、发布等流程，无法保证质量，也没有保持同步更新的流程。
|
||||
|
||||
因此，我觉得，通过建立一个翻译的公益组织（即 LCTT）、建立翻译流程、翻译后保留翻译和校对等人员的署名，可以解决一些以上的问题。
|
||||
|
||||
但是，其实我还忽视了一点，翻译 man 手册，其实无论是环境还是流程，比较复杂，因此限制了参与者。参与门槛高，导致发展不能持续。
|
||||
|
||||
因此，实际上，man 翻译项目，在大概运作了一个月之后，就逐渐停滞下来了，虽然后期，willqian 独立完成了很多篇，但是总体来说，man 翻译项目算是失败了。
|
||||
|
||||
### 总结这一年 ###
|
||||
|
||||
抛开 man 翻译项目的失败不说，其实，LCTT 还是成果累累。
|
||||
|
||||
这一年，我们完成了 5820 次提交，发起了 1482 个 PR，翻译了 805 篇文章。
|
||||
|
||||
这一年，我们有了 98 个贡献者，得到了 162 个 fork。
|
||||
|
||||
我使用了一个工具，根据这一年来我们 LCTT 翻译项目的 git 日志，生成了一段[视频](http://img.linux.net.cn/static/video/lctt2014.mp4)。看着视频中如辛勤的工蜂一样忙忙碌碌的志愿者们；看着如穿花蝴蝶一样，承担了更多工作量的选题、校对们；看着归档时如同施展魔法一样，瞬间变出了一朵朵花，我感觉我们这一年是有收获的一年！
|
||||
|
||||
请大家观赏我们这一年： http://img.linux.net.cn/static/video/lctt2014.mp4 （213M，720p）
|
||||
|
||||
这是我用 kdenlive 合成配音的。虽然我的乐感很差，只能选择一首自己觉得还算配的音乐；虽然我根本不会用 kdenlive，连配音淡出都琢磨半天；虽然我编译用于生成这个视频的 gource 都花费了几个小时来解决问题；但是，看到这份视频，我为我们 LCTT 这一年来的工作感到骄傲。
|
||||
|
||||
### 感谢你们 ###
|
||||
|
||||
虽然很俗套，但是此刻，已经是 2014 年 9 月 10 日凌晨00:50了，我心情很激动，真心感谢所有的参与者、贡献者。几乎每个 LCTT 的成员我都知道，也有几个我特别熟悉；LCTT 的成员有新来的，也有逐渐淡出的，但是不论是那种，我都记得你们。
|
||||
|
||||
名单太长，我就不一一列举了： https://github.com/LCTT/TranslateProject/graphs/contributors
|
||||
|
||||
### 接下来 ###
|
||||
|
||||
我会说，man 计划我不会放弃么？
|
||||
|
||||
是的，man 计划是 LCTT 之所以发起的原因，也是 LCTT 能够持久发展的基础，而 man 翻译也是真正对国内的 Linux 、开源发展有实在意义的事情，所以，我不会放弃。
|
||||
|
||||
我会投入精力开发一个翻译平台，用于 man 项目的翻译、校对和发布，将复杂的翻译环境配置和使用方法隐藏在后面；并增加可视化的图表和进度显示，明了的体现翻译工作进展；对接 man7.org 的最新更新，保持 man 内容的及时更新等等。
|
||||
|
||||
期待 LCTT 的下一个年度的发展吧！
|
||||
|
||||
LCTT wxy
|
||||
2014 年 9 月 10 日
|
||||
@ -1,5 +1,5 @@
|
||||
|
||||
Linux有问必答——如何为sudo命令定义PATH环境变量
|
||||
Linux有问必答——如何为sudo命令定义PATH环境变量
|
||||
================================================================================
|
||||
>**问题**:我安装了一个程序到/usr/local/bin目录下，这个程序需要root权限才能执行，当我用sudo去执行它时，收到"sudo: XXXXX: command not found"的错误提示，不知道为什么/usr/local/bin没有被包含到PATH环境变量下面来，我该如何解决这个问题？
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
使用Linux命令行管理DigitalOcean VPS水滴
|
||||
================================================================================
|
||||
[DigitalOcean][1]是云VPS主机市场中最炙手可热的新生儿。虽然没有提供像Amazon之类一样的综合服务业务，DigitalOcean已经成为定位于中小型企业和开发者的基于Linux的最佳云VPS服务的强有力的竞争者，这都得归功于他们具有竞争力的价格和对用户友好的管理界面。
|
||||
[DigitalOcean][1]是云VPS主机市场中最炙手可热的新生儿。虽然没有提供像Amazon之类一样的综合服务业务，但DigitalOcean定位于中小型企业和开发者，已经成为基于Linux的最佳云VPS服务的强有力竞争者，这都得归功于它们具有竞争力的价格和用户友好的管理界面。
|
||||
|
||||
|
||||
|
||||
@ -20,13 +20,13 @@
|
||||
$ sudo yum install ruby-devel
|
||||
$ sudo gem install tugboat
|
||||
|
||||
要在CentOS上安装tugboat，首先[安装或升级到最新的Ruby][5]，因为在CentOS 6.5以及更早的版本上，默认的Ruby不满足拖船所需的最小版本（1.9及更高版本）。安装Ruby 1.9及更高版本后，请按如下方式安装tugboat。
|
||||
要在CentOS上安装tugboat，首先[安装或升级到最新的Ruby][5]，因为在CentOS 6.5以及更早的版本上，默认的Ruby不满足Tugboat所需的最小版本（1.9及更高版本）。安装Ruby 1.9及更高版本后，请按如下方式安装tugboat。
|
||||
|
||||
$ sudo gem install tugboat
|
||||
|
||||
### tugboat首次使用配置 ###
|
||||
|
||||
在安装完后，就该实行一次配置，配置涉及了授权tugboat访问DigitalOcean帐号。
|
||||
在安装完后，就该进行一次配置，其中包括授权tugboat访问DigitalOcean帐号。
|
||||
|
||||
转到[https://cloud.digitalocean.com/api_access][6]，并创建新的API密钥，记录客户ID和API密钥。
|
||||
|
||||
@ -36,11 +36,11 @@
|
||||
|
||||
$ tugboat authorize
|
||||
|
||||
在提示你输入客户ID和API密钥时，请输入。它会询问几个其它问题，目前你可以接受默认的回答。我们打算在今后自定义默认设置。
|
||||
在提示你输入客户ID和API密钥时，请输入。它会询问几个其它问题，目前你可以接受默认的回答。我们将会在后面自定义默认设置。
|
||||
|
||||
[][7]
|
||||
|
||||
现在，让我们自定义默认水滴设置，以反映你典型的使用状况。要那么做，首先检查水滴提供的可用的东西（如，可用的镜像、区域、大小）。
|
||||
现在，让我们自定义默认水滴设置，以反映你典型的使用状况。要做到这一点，首先检查水滴提供的可用设置项（如，可用的镜像、区域、大小）。
|
||||
|
||||
运行以下命令，它会列出可用的水滴镜像。选取使用一个默认镜像，并记录相关的ID。
|
||||
|
||||
@ -80,7 +80,7 @@
|
||||
private_networking: 'false'
|
||||
backups_enabled: 'false'
|
||||
|
||||
### 创建并添加SSH密钥到数字海洋 ###
|
||||
### 创建并添加SSH密钥到DigitalOcean ###
|
||||
|
||||
要访问水滴实例，一个安全的方式是通过[密钥验证][8]的SSH连接到该实例。
|
||||
|
||||
@ -104,7 +104,7 @@
|
||||
|
||||
ssh_key: '182710'
|
||||
|
||||
### 拖船的基本用法 ###
|
||||
### Tugboat的基本用法 ###
|
||||
|
||||
这里列出了tugboat命令行的一些基本使用情况。
|
||||
|
||||
@ -138,7 +138,7 @@
|
||||
|
||||
$ tugboat resize <name-of-droplet> -s <image-id>
|
||||
|
||||
如果你想要知道特定命令的更多选项，运行：
|
||||
如果你想要了解特定命令的更多选项，运行：
|
||||
|
||||
$ tugboat help <command>
|
||||
|
||||
@ -146,7 +146,7 @@
|
||||
|
||||
### 排障 ###
|
||||
|
||||
1. 当我运行tugboat命令时，它出错了，并出现以下错误。
|
||||
1. 当我运行tugboat命令时，它出现以下错误。
|
||||
|
||||
/usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in `gem_original_require': /usr/lib/ruby/gems/1.8/gems/tugboat-0.2.0/lib/tugboat/cli.rb:12: syntax error, unexpected ':', expecting kEND (SyntaxError)
|
||||
|
||||
@ -156,7 +156,7 @@ Tugboat要求Ruby 1.9及更高版本，你需要升级Ruby来解决该问题。
|
||||
|
||||
/usr/local/share/ruby/site_ruby/rubygems/core_ext/kernel_require.rb:55:in `require': cannot load such file -- json/pure (LoadError)
|
||||
|
||||
安装以下gem来修复该问题。
|
||||
安装以下gem来修复该问题。
|
||||
|
||||
$ sudo gem install json_pure
|
||||
|
||||
@ -166,7 +166,7 @@ via: http://xmodulo.com/2014/07/manage-digitalocean-vps-droplets-command-line-li
|
||||
|
||||
原文作者：[Dan Nanni][a]
|
||||
|
||||
译者：[GOLinux](https://github.com/GOLinux) 校对：[校对者ID](https://github.com/校对者ID)
|
||||
译者：[GOLinux](https://github.com/GOLinux) 校对：[Caroline](https://github.com/carolinewuyan)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创翻译，[Linux中国](http://linux.cn/) 荣誉推出
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
如何在Linux命令行下访问SoundCloud
|
||||
================================================================================
|
||||
如果你喜欢流媒体音乐和原创音乐，你不能错过[SoundCloud][1]。这家云流媒体服务总部设在德国，这对任何音乐爱好者都非常有名且完善。自然，作为一个Linux爱好者，你可能想知道如何在Linux中加入你对音乐的热情。作为一个解决方案，我建议你使用Soundcloud2000，**SoundCloud的命令行客户端**脱胎于[Music Hack Day Stockholm '13][2]。
|
||||
如果你喜欢流媒体音乐和原创音乐，你不能错过[SoundCloud][1]。这家云流媒体服务总部设在德国，这对任何音乐爱好者都非常有名，且功能完善。自然，作为一个Linux爱好者，你可能想知道如何在Linux中体现你对音乐的热情。作为一个解决方案，我建议你使用Soundcloud2000，这是一个脱胎于[Music Hack Day Stockholm '13][2]的**SoundCloud的命令行客户端**。
|
||||
|
||||
### 安装 ###
|
||||
|
||||
@ -43,24 +43,24 @@ Soundcloud2000非常容易使用。有些人甚至会说简单。我喜欢它的
|
||||
|
||||
|
||||
|
||||
这可能是Soundcloud2000的主要默认之一。而导航没有优化过，我寄予厚望的改善和支持的软件还是很年轻的。
|
||||
这可能是Soundcloud2000的主要缺陷之一。虽然导航没有优化过，但是我对这个很年轻的软件的改善和支持还是寄予厚望的。
|
||||
|
||||
### 红利 ###
|
||||
### 奖励 ###
|
||||
|
||||
另外一个额外的红利：如果你喜欢在终端上使用SoundCloud的想法，但不想安装任何额外的软件（也许你不能），我劝你去[cmd.fm][6]。该网站是一个伪装的SoundCloud，因为它隐藏在一个shell接口后。
|
||||
另外一个额外的奖励：如果你喜欢在终端上使用SoundCloud的想法，但不想安装任何额外的软件（也许你不能），我劝你去[cmd.fm][6]。该网站是一个伪装的SoundCloud，它隐藏在一个shell界面后。
|
||||
|
||||
[][7]
|
||||
|
||||
输入“help”可以得到命令列表，这比Soundcloud2000长很多。比如，我看到：
|
||||
|
||||
- _genres to list all genres
|
||||
- _play random to play a random track
|
||||
- _pause to pause the current track
|
||||
- _playlist new to make a new playlist
|
||||
- _loop to loop current track
|
||||
- _cinema to watch and ASCII version of Star Wars which completely blew my mind.
|
||||
- _genres 列出所有流派
|
||||
- _play random 随机播放
|
||||
- _pause 暂停播放
|
||||
- _playlist new 建立新的播放节目单
|
||||
- _loop 循环播放
|
||||
- _cinema 如同星球大战一样的字幕
|
||||
|
||||
它甚至支持通过tab键自动完成流派
|
||||
它甚至支持通过tab键自动补完流派名称
|
||||
|
||||
最后，Soundcloud2000的确是一个整洁的程序。我们可以原谅其目前的缺陷，因为它还年轻。我真的希望它会成长，并包含更多的功能（并从潜在的cmd.fm得到的灵感）。
|
||||
|
||||
@ -74,7 +74,7 @@ via: http://xmodulo.com/2014/07/access-soundcloud-command-line-linux.html
|
||||
|
||||
原文作者：[Adrien Brochard][a]
|
||||
|
||||
译者：[geekpi](https://github.com/geekpi) 校对：[校对者ID](https://github.com/校对者ID)
|
||||
译者：[geekpi](https://github.com/geekpi) 校对：[wxy](https://github.com/wxy)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创翻译，[Linux中国](http://linux.cn/) 荣誉推出
|
||||
|
||||
114
published/20140723 Top 10 Fun On The Command Line.md
Normal file
114
published/20140723 Top 10 Fun On The Command Line.md
Normal file
@ -0,0 +1,114 @@
|
||||
用命令行去发掘有趣的“前十”
|
||||
================================================================================
|
||||
|
||||
**如果你喜欢做‘排名前10’之类的列表但又有点不好意思这样说，那么告诉人们你热爱数据的探索。为了进一步打动他们，向他们解释你在命令行间的数据探索。但是不要告诉他们这其实很容易，以免你的好形象就这样被毁灭了哦！**
|
||||
|
||||
在这篇文章中，我将基于GNU/Linux工具和'单列表格'（也就是我所说的简单列表）来做一些数据探索。如若想在这里通过命令行查看更多的信息，请查看'man'页，或者在“注释”部分求解。
|
||||
|
||||
### 密码 ###
|
||||
|
||||
在第一个列表里探讨的是马克.伯内特2011著的关于[10000 个最常用的密码][1]汇编。这个列表是有序的、使用最频繁的，也是广为人知的阶乘“密码”的最常用来源之一，与“123456”并列排名第二。在这里，我把该列表放到一个名为“passwords”的文件中，并且使用head命令把排名前10的列出来了：
|
||||
|
||||
|
||||
|
||||
（伯内特解释他是如何收集这些密码的[这里][2]。你会注意到在列表中他把所有大写字母都转换成小写的。)
|
||||
|
||||
OK，所以'password'是伯内特列表的顶部。那么每个数字呢？
|
||||
|
||||
|
||||
|
||||
非常有趣的是！数字'1'出现在密码列表中的次数多于第二个最常用数字'2'的两倍，而且，除了0和9之外，这十个数字出现的次数以其数字顺序排列。而排名前10的字母呢？
|
||||
|
||||
|
||||
|
||||
在 passwords 文件中出现最频繁的字母依次是EARONISTLC，类似于EAIRTONSLC，这是至少[一个出版的表格][3]中提到的常用英文单词中出现的字频。这是否意味着，大部分密码其实是一些常见的英语单词呢，也许会参杂一些数字呢？
|
||||
|
||||
为了找到答案，我先把密码转换成一个纯字母的字符串列表，然后看看有多少字符串是可以在英语词典中找到的。
|
||||
|
||||
首先我将通过 **sed** 命令删除所有密码中的数字，然后删除所有的标点符号，再删除所有的空行。这将创建出一个纯字母的密码列表。然后我通过**sort** 和 **uniq**来修剪列表的排序，将重复项取出。（例如，'abc1234def'和'abc1!2!3!def!'都剔除剩下'abcdef'.) 。根据wc命令，我把1000个密码减至成8583个纯字母的字符串：
|
||||
|
||||
|
||||
|
||||
我经常使用一本便携式的英语字典，我通常会使用`usr/share/dict/american-english`，这个文件是来自Debian Linux的一个发行版本。它包含了99171个单词。我会先通过**tr**命令将这个词表转换为纯小写的，然后使用**sort** 和 **uniq**删除掉任何重复的条目排序（例如'A' 和 'a' 都将成为 'a'）。这样就将词表的数量减至97723项了：
|
||||
|
||||
|
||||
|
||||
我现在可以用comm命令及'-23'的参数来比较两个列表，并报告纯字母文件中而没有出现在字典中的单词：
|
||||
|
||||
|
||||
|
||||
总数是3137，所以至少有8583 -3137 = 5446个'核心'密码在伯纳特的纯小写字母列表中（大约63%）是简单的英语单词，或者是简单的单词附加一些数字或者标点符号。我之所以说“至少”，是因为在3137个字符串中有很大比例是只有经过轻微修改的纯英语单词、名称、或者在/usr/share字典中未能找到的名称修改而成的。在LA项中，例如，'labtec', 'ladyboy', 'lakeside', 'lalakers', 'lalala', 'laserjet', 'lasvegas', 'lavalamp' 和 'lawman'.
|
||||
|
||||
### 地名 ###
|
||||
|
||||
在之前的一篇[Linux Rain article][4]，我描述了如何建立一张37万项澳大利亚的地名表。有了它，我现在可以回答一些类似这样的关键问题“Round Hill是澳大利亚山脉中最流行的名字吗？”和“桑迪是沙滩之最，而岩溪峡谷呢？”
|
||||
|
||||
在地名表中地名字段的排名第2，所以这里有：
|
||||
|
||||
|
||||
|
||||
哇。我当时甚至没有关闭这个终端。（但是请注意到我是如何通过**\^string1\^string2**命令保存打印的内容。它重复着最后一个命令，但是用第2个字符串代替了第1个字符串。这是多么有用的BASH绝招！）
|
||||
|
||||
另一个亟待解决的问题是有多少地名有'Mile'在其中，例如'Six Mile Creek',而他们的排名又是如何：
|
||||
|
||||
|
||||
我在我的澳洲之旅发现有很多Dead Horse Creeks，因此有这些地名：
|
||||
|
||||
|
||||
|
||||
|
||||
### 种类 ###
|
||||
|
||||
第三个列表是探索我今年出版的1961-2010年期间澳大利亚新种类昆虫名。从这个列表中，我去掉所有“物种的绰号”，就是种群组合的第二部分，比如像智人（你和我）和西方蜜蜂（欧洲蜜蜂）。
|
||||
|
||||
（科技小贴士：这个昆虫表，可以从开发数据Zenodo库中[https://zenodo.org/record/10481][5]取得，包括亚种。在我的‘top 10’练习中，我首先分离出所有独特的种群组合，这样避免了重复的，例如蜜蜂iberica的亚种，以避免蜜蜂的绰号intermissa，等等。最后一个物种文件有18155个绰号。）
|
||||
|
||||
大多数人讲科学名称带玩笑式地用'-us'结局，如'Biggus buggus'。那么昆虫学家呢？有几个不错的，用命令行的方式获取字符串的最后2个字母，在这里我都会用到这2个：
|
||||
|
||||
|
||||
|
||||
耶！昆虫学家喜欢也‘-us’结尾。接下来，我不知道有多少物种是以我的家乡Tasmania州来命名的？（下面我想看看前100行，来确保我得到的所有'tasman'组合.)
|
||||
|
||||
|
||||
|
||||
那么昆士兰呢？
|
||||
|
||||
|
||||
|
||||
一般来说，昆虫物种名单中的前10名分别是什么呢？
|
||||
|
||||
|
||||
|
||||
嗯，除了明显的'australis'和'australiensis'，而地理方面的'occidentalis'（西部），另外昆虫学家创建7个在10个最流行列表中的绰号已经履行了其它昆虫学家的意愿。(绰号'commoni'是给澳大利亚蝴蝶和蛾专家Ian F.B. Common[1917-2006]的荣誉。)
|
||||
|
||||
### 演变 ###
|
||||
|
||||
上面的这些命令用在简单列表上。要从简单的列表变成文本块，那就再次需要我们的命令行朋友了。例如，我把澳大利亚参议院于2014年7月16日的[演讲][6]保存成文本文件hansard。将hansard分割成一个单词列表：
|
||||
|
||||
|
||||
|
||||
现在看看讲话中的单词使用频率：
|
||||
|
||||
|
||||
|
||||
### 即将推出... ###
|
||||
|
||||
从多列的表中做'top 10'等排名，需要更多些的命令行工具。我将会在未来的文章中证明他们的用处。
|
||||
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: http://thelinuxrain.com/articles/top-10-fun-on-the-command-line
|
||||
|
||||
原文作者：Bob Mesibov(Bob Mesibov is Tasmanian, retired and a keen Linux tinkerer.)
|
||||
|
||||
译者：[disylee](https://github.com/译者ID) 校对：[wxy](https://github.com/wxy)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创翻译，[Linux中国](http://linux.cn/) 荣誉推出
|
||||
|
||||
[1]:https://xato.net/passwords/more-top-worst-passwords/#.U8eD13AvDy0
|
||||
[2]:https://xato.net/passwords/how-i-collect-passwords/#.U8eEdnAvDy0
|
||||
[3]:http://www.rinkworks.com/words/letterfreq.shtml
|
||||
[4]:http://www.thelinuxrain.com/articles/building-a-gazetteer-table-from-kml-files
|
||||
[5]:https://zenodo.org/record/10481
|
||||
[6]:http://parlinfo.aph.gov.au/parlInfo/search/display/display.w3p;db=CHAMBER;id=chamber%2Fhansards%2F232fa1a8-d7e8-4b22-9018-1a99b5a96812%2F0025;query=Id%3A%22chamber%2Fhansards%2F232fa1a8-d7e8-4b22-9018-1a99b5a96812%2F0000%22
|
||||
@ -1,29 +1,30 @@
|
||||
如何创建Ubuntu信息端计算机
|
||||
如何创建Ubuntu 信息亭（kiosk）
|
||||
================================================================================
|
||||
|
||||
**Linux发行版可以作为全功能打包，也可以按需分解，驱动了从市内标示牌到市议会桌面系统在内的所有设备。**
|
||||
**Linux发行版可以作为全功能打包，也可以按需分解，它驱动了从市内标示牌到市议会桌面系统在内的所有设备。**
|
||||
|
||||
正是这种多样化，几乎可塑的质量，让Linux发行版，包括Ubuntu在内，在众多不同领域如此成功。
|
||||
### 信息端和单功能计算机 ###
|
||||
|
||||
Ubuntu更为流行的使用之一，是在**信息端类计算机**中。这些设备趋向于运行功能剥离的，或者功能有限的OS版本，只允许**一个单一应用运行**。
|
||||
### 信息亭和单功能计算机 ###
|
||||
|
||||
信息端计算机可以设置提供短暂的或者被动的访问，对于网吧或者对于任何要求只有特定功能——如网页浏览器——可以让用户访问的机器十分理想。
|
||||
Ubuntu更为流行的使用之一，是在**信息亭（kiosk）类计算机**中。这些设备趋向于运行功能剥离的，或者功能有限的OS版本，只允许**一个单一应用运行**。
|
||||
|
||||
信息亭计算机可以设置提供短时的或者被动的访问，适用于网吧或只能让用户访问特定功能时（如网页浏览器）。
|
||||
|
||||
### 构建Ubuntu信息端 ###
|
||||
|
||||
但你会怎样来创建这样一台计算机？好吧，保存你的Google。Linux开发者Oli Warner最近发布了两篇文章，介绍了使用Ubuntu 14.04和Google Chrome来创建单一功能的设备。
|
||||
但你会怎样来创建这样一台计算机？好吧，不用去Google了。Linux开发者Oli Warner最近发布了两篇文章，介绍了使用Ubuntu 14.04和Google Chrome来创建单一功能的设备。
|
||||
|
||||
他的第一篇指南从零开始，使用Ubuntu Server和少量的软件包来创建一个轻量级的X和Openbox的组合，开机启动Chrome。该安装需要最多2GB的磁盘空间和仅仅512MB的内存来运行。
|
||||
|
||||
- [从零开始构建信息端计算机][1]
|
||||
- [从零开始构建信息亭计算机][1]
|
||||
|
||||
第二篇教程反其道而行，一步一步介绍了将一个现存的Ubuntu桌面安装转变为一个更轻巧的单一功能的变形版本。
|
||||
|
||||
- [将Ubuntu转换成信息端计算机][2]
|
||||
- [将Ubuntu转换成信息亭计算机][2]
|
||||
|
||||
Neither guide is for the faint-hearted, but are simple enough for most intermediate-level users to follow. Follow the guides to get a functional setup, but don’t be afraid to strip out further packages and processes or double down on security, especially if intending to use an instance in a public space.
|
||||
两个指南都不是给那些胆小的新手的，而对于大多数中级水平的用户而言却是简单易行的。跟着指南来获得一次实用的安装体验，不要畏首畏尾，大胆去剥离一些深层次的包和进程，或者加固安全吧，特别是如果想要在公共空间中使用一个实例。
|
||||
|
||||
两个指南都不是给那些胆小的新手的，而对于大多数中级水平的用户而言却是简单易行的。跟着指南来获得一次实用的安装体验，不要畏首畏尾，大胆去剥离一些深层次的包和进程，或者加固安全吧，特别是如果想要在公共环境中使用时。
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
@ -31,7 +32,7 @@ via: http://www.omgubuntu.co.uk/2014/07/create-ubuntu-kiosk
|
||||
|
||||
作者：[Joey-Elijah Sneddon][a]
|
||||
译者：[GOLinux](https://github.com/GOLinux)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
校对：[wxy](https://github.com/wxy)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创翻译，[Linux中国](http://linux.cn/) 荣誉推出
|
||||
|
||||
@ -1,32 +1,32 @@
|
||||
Cheat - 一个给Linux初学者和管理员的终极命令行‘备忘单’
|
||||
Cheat—— 给Linux初学者和管理员一个终极命令行‘备忘单’
|
||||
==============================================================================================
|
||||
当你不确定你所运行的命令，尤其是那些使用了许多选项的复杂命令的时候，你怎么做？在这种情况下，我们使用man pages来获取帮助。还有一些其它的选择可能包括像‘**help**’，‘**whereis**’和‘**whatis**’这样的命令。但是所有的这些既有优点，也有缺点
|
||||
|
||||
当我们浏览**man pages**来查看选项和帮助的时候，man pages里面的描述实在太冗长了，我们无法在很短的时间里理解它的意思
|
||||
当你不确定你所运行的命令，尤其是那些使用了许多选项的复杂命令时，你会怎么做？在这种情况下，我们使用man pages来获取帮助。还有一些其它的选择可能包括像‘**help**’，‘**whereis**’和‘**whatis**’这样的命令。但是所有的这些既有优点，也有缺点。
|
||||
|
||||
当我们浏览**man pages**来查看选项和帮助的时候，里面的描述实在太冗长了，我们无法在短的时间里理解它的意思。
|
||||
|
||||
|
||||
Linux Man Pages
|
||||
|
||||
同样，‘**help**’命令可能不会给你想要的答案
|
||||
同样，‘**help**’命令可能也不会给你期待的答案。
|
||||
|
||||
|
||||
Help Command
|
||||
|
||||
‘**whereis**’命令几乎不给你任何信息，除了安装的二进制文件的位置（有些时候可能非常重要）
|
||||
‘**whereis**’命令几乎不给你任何信息，除了安装二进制文件的位置（有些时候可能是重要的）
|
||||
|
||||
|
||||
Whereis Command
|
||||
|
||||
‘**whatis**’命令给出一套很严格的答案---仅仅说出了所查询命令的作用，但，它并没有什么太大帮助。而且， 它从来不提及所查询命令所拥有的选项
|
||||
‘**whatis**’命令给出一套很严格的答案，它除了说出所查询命令的作用，并没有什么太大帮助。而且，它从来不说明可用的选项。
|
||||
|
||||
|
||||
Whatis Command
|
||||
|
||||
我们使用这些选项直到在困境中解决问题，但是现在来了一个交互式的备忘录应用程序‘**cheat**’，它将带领其余的命令查询命令
|
||||
直到在困难中解决问题前，我们已经使用了以上全部选项，但是现在来了一个交互式的备忘录应用程序‘**cheat**’，它将在其余的命令中脱颖而出。
|
||||
|
||||
### 什么是cheat? ###
|
||||
|
||||
**cheat**是在GNU通用公共许可证下，为Linux命令行使用者发行的交互式备忘单应用程序。它提供显示Linux命令使用案例，包括该命令所有的选项和简短但尚可理解的功能介绍
|
||||
**cheat**是在GNU通用公共许可证下，为Linux命令行用户发行的交互式备忘单应用程序。它提供显示Linux命令使用案例，包括该命令所有的选项和简短但尚可理解的功能。
|
||||
|
||||
|
||||
|
||||
@ -34,7 +34,7 @@ Cheat：提供简单命令选项
|
||||
|
||||
### 在Linux系统中安装‘Cheat’ ###
|
||||
|
||||
‘**Cheat**’有两个主要的依赖 - ‘**python**’ 和 ‘**pip**’，在安装‘**cheat**’之前，确保你的系统安装了python和pip
|
||||
‘**Cheat**’有两个主要的依赖——‘**python**’ 和 ‘**pip**’，在安装‘**cheat**’之前，确保你的系统安装了python和pip。
|
||||
|
||||
### Install Python ###
|
||||
|
||||
@ -46,29 +46,29 @@ Install Pip
|
||||
# apt-get install python-pip (基于Debian的系统)
|
||||
# yum install python-pip (基于小红帽的系统)
|
||||
|
||||
**Note**：pip是一个简单的安装替代，是一个有极大改进的Python第三方包安装器
|
||||
**Note**：pip是一个简单的安装替代，是一个有极大改进的Python第三方包安装器。
|
||||
|
||||
### 下载并安装Cheat ###
|
||||
|
||||
我们将通过Git下载‘Cheat’，确保你安装了‘git’包，如果没有最好安装下
|
||||
我们将通过Git下载‘Cheat’，确保你安装了‘git’包，如果没有最好安装一下。
|
||||
|
||||
# apt-get install git (基于Debian的系统)
|
||||
# yum install git (基于小红帽的系统)
|
||||
|
||||
接下来，通过运行下面的命令来安装所需要的python依赖包
|
||||
接下来，通过运行下面的命令来安装所需要的python依赖包。
|
||||
|
||||
# pip install docopt pygments
|
||||
|
||||
现在，clone cheat的[Git repository][1]
|
||||
现在，复制cheat的[Git库][1]
|
||||
|
||||
# git clone https://github.com/chrisallenlane/cheat.git
|
||||
|
||||
进入cheat目录，运行‘**setup.py**’（一个python脚本）
|
||||
进入cheat目录，运行‘**setup.py**’（一个python脚本）。
|
||||
|
||||
# cd cheat
|
||||
# python setup.py install
|
||||
|
||||
如果安装很顺利，你就能够看到安装在系统上的cheat版本了
|
||||
如果安装很顺利，你就能够看到安装在系统上的cheat版本了。
|
||||
|
||||
# cheat -v
|
||||
cheat 2.0.9
|
||||
@ -79,9 +79,9 @@ Install Pip
|
||||
|
||||
export EDITOR = /usr/bin/nano
|
||||
|
||||
你可以使用你喜欢的编辑器来替代‘**nano**’。保存文件然后退出，再次登录以确保修改生效
|
||||
你可以使用你喜欢的编辑器来替代‘**nano**’。保存文件然后退出，再次登录以确保修改生效。
|
||||
|
||||
接下来，添加cheat的自动补全特性，来确保不同解释器下命令行的自动补全。为了到达该功能要求，简单地将‘**cheat.bash**’脚本clone下来，然后复制到你系统正确的路径下
|
||||
接下来，添加cheat的自动补全特性，来确保不同解释器下命令行的自动补全。为了到达该功能要求，简单地将‘**cheat.bash**’脚本clone下来，然后复制到你系统正确的路径下。
|
||||
|
||||
# wget https://github.com/chrisallenlane/cheat/raw/master/cheat/autocompletion/cheat.bash
|
||||
# mv cheat.bash /etc/bash_completion.d/
|
||||
@ -90,15 +90,15 @@ Install Pip
|
||||
|
||||
- [Auto Completion Script for Various Shells][2]
|
||||
|
||||
不仅如此，如果需要的话，你也可以使用语法高亮。要想达到次功能，在你的‘**.bashrc**’文件中添加‘**CHEATCOLORS**’环境变量
|
||||
不仅如此，如果需要的话，你也可以使用语法高亮。要想做到这一点，在你的‘**.bashrc**’文件中添加‘**CHEATCOLORS**’环境变量。
|
||||
|
||||
export CHEATCOLOR=true
|
||||
|
||||
Cheat应用默认只提供最基本和最常用的命令。cheat备忘单的内容保存在**~/.cheat/.**目录里，我们可以手动在这个目录添加备忘单里面的内容，这样，我们的cheat应用将更强大
|
||||
Cheat应用默认只提供最基本和最常用的命令。cheat备忘单的内容保存在**~/.cheat/.**目录里，我们可以手动在这个目录添加备忘单里面的内容，这样，我们的cheat应用将更强大。
|
||||
|
||||
# cheat -xyz
|
||||
|
||||
这将打开xyz备忘单，如果没有的话就会创建一个。备忘单将使用**.bashrc**里设置的默认**编辑器**打开，默认编辑器就是上面内容所提及到的
|
||||
这将打开xyz备忘单，如果没有的话就会创建一个。备忘单将使用**.bashrc**里设置的默认**编辑器**打开，默认编辑器就是在上面**.bashrc**所设置的。
|
||||
|
||||
### 一些Cheat命令的使用 ###
|
||||
|
||||
@ -107,7 +107,7 @@ Cheat应用默认只提供最基本和最常用的命令。cheat备忘单的内
|
||||
|
||||
tar命令选项
|
||||
|
||||
除非在不同的地方咨询和核对后，我才使用**dd**命令，在此之前，无论我对这个命令多么的确定，我从不使用它。现在，事情就变得简单多了
|
||||
除非在不同的地方咨询和核对后，我才使用**dd**命令，在此之前，无论我对这个命令多么的肯定，我从不使用它。现在，事情就变得简单多了。
|
||||
|
||||
|
||||
dd命令选项
|
||||
@ -122,42 +122,42 @@ uname命令选择
|
||||
|
||||
ifconfig命令选项
|
||||
|
||||
‘top‘命令，一个对管理员和正常用户来说，最重要的命令之一
|
||||
‘top’命令，对管理员和普通用户来说，是最重要的命令之一。
|
||||
|
||||
|
||||
top命令选项
|
||||
|
||||
我们来骗骗cheat命令，如何（尽管别有意义）？得到可用命令的的列表，其实就是安装在你系统里的cheat备忘录
|
||||
我们来骗骗cheat命令，如何（尽管别有意义）？得到一个可用命令的列表，其实就是安装在你系统里的cheat备忘录。
|
||||
|
||||
|
||||
列出所有Linux命令
|
||||
|
||||
使用关键字搜索备忘单
|
||||
使用关键字搜索备忘单。
|
||||
|
||||
|
||||
搜索备忘单
|
||||
|
||||
来看看包含所有命令的内置备忘单
|
||||
来看看包含所有命令的内置备忘单。
|
||||
|
||||
$ cheat -d
|
||||
|
||||
/home/avi/.cheat
|
||||
/usr/local/lib/python2.7/dist-packages/cheat/cheatsheets
|
||||
|
||||
复制内置的备忘单到你的本地目录
|
||||
复制内置的备忘单到你的本地目录。
|
||||
|
||||
# cp /usr/local/lib/python2.7/dist-packages/cheat/cheatsheets/* /home/avi/.cheat/
|
||||
|
||||
### 结论 ###
|
||||
|
||||
这个有趣的工程在许多情况下担任救世主的角色，它给予你需要的信息，信息不冗余，不模糊，相反地，却击中要点。这是每个人都会需要的工具，很简单就能创建，安装，使用和理解，这个项目前途无量
|
||||
这个超棒的工具在许多情况下担任“救世主”的角色，它给予你需要的信息，信息不冗余，不模糊，相反地，却击中要点。这是每个人都会需要的工具，很简单就能创建、安装，使用和理解，这个工具前途无量。
|
||||
|
||||
这个Git仓库已经添加了一个精彩的**gag**，这里我不打算去解释它，而留给你去解释
|
||||
这个Git仓库已经添加了一个精彩的**gag**，这里我不打算去解释它，而留给各位来解释。
|
||||
|
||||
|
||||
Linux Gag
|
||||
|
||||
好了，文章就要结束了，我会带着下一个你们爱读的有趣文章回到这里的，在此之前，时刻关注Tecmint。别忘了在下面的评论部分给我们提供你们有价值的反馈
|
||||
好了，文章就要结束了，我会带着下一篇你们喜欢的有趣文章回到这里的，在此之前，要时刻关注我们。别忘了在下面的评论部分给我们留下您宝贵的反馈信息。
|
||||
|
||||
-------------------------------------------------------------------------------------------------------------------------------
|
||||
|
||||
@ -165,7 +165,7 @@ via: http://www.tecmint.com/cheat-command-line-cheat-sheet-for-linux-users/
|
||||
|
||||
作者：[Avishek Kumar][a]
|
||||
译者：[su-kaiyao](https://github.com/su-kaiyao)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
校对：[Caroline](https://github.com/carolinewuyan)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创翻译，[Linux中国](http://linux.cn/) 荣誉推出
|
||||
|
||||
@ -0,0 +1,214 @@
|
||||
KDE Plasma 5 —— 给尚未确定桌面环境的 Linux 用户指明道路
|
||||
================================================================================
|
||||
> 点评 ———— 新的KDE 5版本既满足了传统桌面环境的需求，也兼顾了多设备长期支持计划
|
||||
|
||||
KDE 项目终于发布了备受瞩目的 KDE 桌面环境的最新主版本 ———— KDE Plasma 5。
|
||||
|
||||
Plasma 5 站在了一场正在进行的未来 Linux 桌面环境的争夺战中间。
|
||||
|
||||
一方面，有着 GNOME 和 Unity 这样的新生桌面代表。二者均通过某种重要方法打破了传统桌面模式的垄断，并且都不只是满足于桌面型计算机，而将其界面延伸到了备受期待的新型平板电脑（[也许不久后就会面世][1]）。
|
||||
|
||||
另一方面，Linux 桌面环境，如 KDE、XFCE、LXDE、Mate 甚至 Cinnamon，都是桌面环境的另一种类型 ———— 自发布以来没有什么大的变化，继续向用户提供传统的桌面环境体验，但这并不能表明这些项目没有成长和进步。这些发行版全部持续更新，并且根据成熟桌面应有的模式进行了不断的调整。
|
||||
|
||||
|
||||
|
||||
Ubuntu 下的 Unity 桌面环境
|
||||
|
||||
|
||||
|
||||
GNOME 3 桌面环境
|
||||
|
||||
GNOME 和 Unity 暂时在这场正在进行的争夺战中赢得了最大的优势。二者均新颖非凡，固执并极端。有的 Linux 用户对他们情有所钟，也有的 Linux 用户对他们恨之入骨。这使得在 Linux 世界里，没有哪条关于这两个桌面环境的评论或帖子是轻松活泼的。同时两大 Linux 阵营之间的差异不仅仅关乎于你未来桌面的样子，更决定了未来计算机会如何运作。
|
||||
|
||||
GNOME 和 Unity 相信未来的计算机运作方式，是由多台设备同时运行着相同的软件互相合作而成的 ———— 因此这两个项目发行的新版桌面只朝着这个方向努力。这些新版桌面并不是真正意义上作为未来桌面打造的，而是同时囊括了现在意义上的桌面，以及会出现在未来设备上的桌面的混合桌面。而另一派 Linux 桌面环境似乎完全忽视了这些。
|
||||
|
||||
与闭源操作系统的世界不同 ———— 那里所有变化都遗传了下来，与之仿效还是以之为戒？Linux 世界正在这两种对立的观点中徘徊着。
|
||||
|
||||
对用户群体来说，这也许很令他们沮丧。试想你正在努力完成工作，但此时你必须完成一个会彻底改变你现有桌面环境的更新，陌生的工作方式使你不得不花费时间来学习。即便最好的情况是，当你曾经最喜爱的桌面环境更新得面目全非的时候，你选择迁移到了其他桌面去。但你长久以来的使用习惯以及那种熟悉的感觉，却再也无法找回了。
|
||||
|
||||
幸运的是，有一个简单的方法去避免这种糟糕的情况并为你找到合适的桌面。简而言之：你想被桌面牵制，还是想控制桌面？
|
||||
|
||||
如果你是第一派阵营的，并且乐于学习新的工作方式，那么 Unity 和 GNOME 3 将会是你最好的选择。如果你是后一派阵营的，XFCE、Cinnamon、Mate，还有许多其他的桌面环境，都将很好的满足你的需求。甚至如果你想尝试和 Unity 还有 GNOME 3 都不相同的新生桌面时，也有 Xmonad、Ratpoison 等其他非常小众的桌面环境供你选择。（说来惭愧，自从 Linus 说了“呃，嘿，这有个内核非常适合你的 GNU 操作系统”以来，Xmonad 可能是 Linux 里最好的东西了。）
|
||||
|
||||
|
||||
|
||||
KDE Plasma 5 的启动界面
|
||||
|
||||
那么对于犹豫不决的 Linux 用户呢，让他们随便选一种吗？他们喜欢传统桌面环境的带来体验，但也不想因此放弃新生桌面的菜单、快捷方式还有任务栏，同时他们还担心着平板电脑等其他问题，想着是否会有某个桌面能在所有设备上工作。假如你正在这么想，那么我的朋友，你绝对有必要尝试下 KDE 的最新版 Plasma 5。
|
||||
|
||||
KDE 正在尝试做其他 Linux 桌面都没有做过的事 ———— 向平板电脑及移动设备桌面前进的同时，继续向用户提供传统的、多功能的、高度定制化的桌面体验。
|
||||
|
||||
### KDE Plasma 5 与“通用”世界 ###
|
||||
|
||||
经历过 KDE 3.5 升级至 KDE 4 的用户似乎仍然避免任何有关 KDE 的重要更新，但对 KDE 粉丝而言，Plasma 5 还是带来了一些好消息。确实这是一个重要更新，没错，但这只是极少数情况下出现的例外（因此我得花费点时间来解释一下，因为你还不太了解）。
|
||||
|
||||
事实证明，难以置信且艰难万分的 KDE 4 更新确实为一个更加美好的未来打下了坚实的基础 ———— 我们现在刚刚抵达这美好的未来。
|
||||
|
||||
通过这次更新，KDE 核心今后出现变化的可能性大大减小。我们确实提及了正迈向平板电脑以及其他设备的一步，这令人难以置信，但不要害怕。KDE 似乎准备去做 GNOME 和 Unity 无法做到的事 ———— 在不改变传统桌面模式的前提下，移植到其他设备上去。换言之，这一版本极力避免了所有因某些新技术的出现而随意尝试所导致的混乱结果。
|
||||
|
||||
（说点其他的：如果你没记住也没关系，但你认同 Canonical 继续通过 Unity 的更新来实现桌面通用这件事吗？早在 Canonical 让用户测试 GNOME 2 菜单中的阴影棕色以调配出最佳效果时，KDE 就开始决定实施桌面统一计划了）
|
||||
|
||||
通过 KDE Frameworks 5、Qt5 还有其他一系列随同 Plasma 5 进行的更新，通用版本的 KDE 得以实现。KDE 将出现在任何需要它的地方。
|
||||
|
||||
因此当所有因素出现时，KDE 项目及其开发者打造出了全新的界面 ———— KDE 称这种新框架为“通用等离子壳层”（converged Plasma shell），在 Plasma 5 中作为支撑桌面环境的框架基础 ———— Plasma 5 桌面截至目前，是唯一的界面。KDE 计划打造出其他的界面，但针对 Plasma 5 的[官方声明][2]中提到“一个平板中心及用户体验媒体中心正在开发中”。
|
||||
|
||||
从这点来看，KDE 的通用版本和和 Ubuntu 所预想的并不相同；用户界面将基于设备和硬件进行改变。例如，当你在长椅上浏览网页的时候，你也许有台平板电脑正在管理着进行中的工作。然后你起身，走回办公室，连接无线键盘，平板电脑又变成了拥有键盘的友好操作界面。
|
||||
|
||||
这种情况下有些潜在的问题，部分 Win 8 用户也许已经习以为常了。比方说，假如键盘正在进行输入，而你仍然想通过触屏进行交互，会发生些什么？试想你正在操纵鼠标，但你同时却想活动活动手指。
|
||||
|
||||
我们提及这些并不是说 KDE 没有考虑过这些问题（希望他们已经考虑过了），而是指这个“通用”所有设备用户界面的想法将很难做到完美。并且 KDE 一直在做一件事 ———— 暗示用户这项计划的成功是遥遥无期的。
|
||||
|
||||
假如 KDE 能运行在平板设备上，那么用户将获得可以订制任何细节部分的体验。简单来说，会有一种方法让你决定当系统检测到键盘时进行什么操作，而不是让系统自己决定。
|
||||
|
||||
### Plasma 5 桌面 ###
|
||||
|
||||
KDE Plasma 5 是由 KDE 4 演化来的，而不是任何一种意义上的界面革新。
|
||||
|
||||
|
||||
|
||||
KDE Plasma 5 的桌面。
|
||||
|
||||
我们早就用这个版本了 ———— 早在不太稳定的测试期时就开始了，尽管大部分错误提示已图形化，而不仅仅是文字警告 ———— 截至目前已在虚拟机上运行了超过一个月的时间。我们已经在 Retina 屏的 MacBook Pro 上进行过了双重启动测试，并且验证了 KDE 在更旧的硬件，一台古老的东芝笔记本上，表现如何。测试 KDE Plasma 5 期间我们使用了 Kubuntu（虚拟机和东芝笔记本）以及新安装的 Arch Linux（MacBook 上的双重启动）。
|
||||
|
||||
如果你想试试 Plasma 5，最简单的方法是下载[KDE 的官方 Neon live CD][3]。这样可以使你得到在 Ubuntu 上运行的 Plasma。如果你想在一个已经安装了 Kubuntu 的操作系统上安装测试，你可以使用以下命令：
|
||||
|
||||
sudo add-apt-repository ppa:neon/kf5
|
||||
sudo apt-get update
|
||||
sudo apt-get install project-neon5-session project-neon5-utils project-neon5-konsole project-neon5-breeze project-neon5-plasma-workspace-wallpapers
|
||||
|
||||
重启你的机器，你将会在登录界面下找到启动 Neon 的新启动项。
|
||||
|
||||
当你安装完 Plasma 5 并且启动时，首先你将会注意到的是叫做 Breeze 全新 KDE 默认主题。
|
||||
|
||||
### Plasma 5 的全新外观 Breezy ###
|
||||
|
||||
Breezy 主题是 KDE 所要呈现出的一种现代化界面，同时“减少了工作区的视觉混乱”。也就是说，很长时间以来一直作为 KDE 默认外观一部分的，那种给人以忙碌混乱的感觉已经成为了过去。
|
||||
|
||||
|
||||
|
||||
KDE Plasma 5 的 Breeze 桌面主题最大程度上完善了开始菜单。每个标签下都有注释，方便搜索。
|
||||
|
||||
全部界面发生了极大的变化 ———— 更大的字体，更好的对比度，以及一种全新的平面布局，其“磨砂”外观有点类似并且介于 OS X Yosemite、Android L 还有 KDE 4.x 的风格。这并不是说 KDE 抄袭了苹果或者谷歌。这不可能是抄袭，因为 Plasma 5 和 Breeze 主题发布了很长时间之后苹果核谷歌那里才透漏出些许 Yosemite 还有 Android L 的信息出来。
|
||||
|
||||
当然，说 KDE 抄袭了任何产品都是不对的，从 Breeze 的视觉设计和整体审美性来看，其更偏向于长时间沉淀的作品。从这种角度看，它看起来很“现代化”，只要你把现代化定义为较多的尖锐元素，较少的纹理和轮廓，更多的半透感，以及单色图形。
|
||||
|
||||
KDE 的设计者将大量的工作放在了 Breeze 主题还有其外观上。这不仅仅是外观上的变化。Breeze 主题借由清爽的菜单、更有条理的通知中心以及全新的开始菜单，使 KDE 变得更加友好。
|
||||
|
||||
|
||||
|
||||
清爽、有条理的通知中心。
|
||||
|
||||
Breeze 出现了多少问题取决于你是否使用过它。KDE 更倾向于那些喜欢定制自己系统的用户，他们大概也喜欢定制主题。有件期待的事，有什么发行版会大幅修改默认 KDE 主题？ ———— 显然是 OpenSUSE ———— 将会提供一个比 Breeze 所提供的更高的开始菜单栏。
|
||||
|
||||
目前而言，大多数发行版应该不会直接过渡到 Breeze 上去，因为其仍处于测试阶段。而且巧合的是，Breeze 将会是你注意到 Plasma 5 不完美的第一个标志。开始菜单上有许多很棒的新图标了，但其他界面上却没有。并且作为 Kubuntu PPA 可用的最新更新，Breeze 并未使用新版的窗口装饰。新版窗口装饰是已经安装了的，但默认并未被使用。你可以去系统设置中打开该选项以获得更完整的，但也更有可能出 bug 的 Breeze 体验。
|
||||
|
||||
|
||||
|
||||
图片上半部分是默认的 Oxygen 窗口装饰，下半部分是最新的 Breeze 主题中的窗口装饰。
|
||||
|
||||
并非所有都是理想的，有时很难分辨什么是 bug 或者什么地方是不完善的，以及哪里的设计不够好。比如，Breeze 下有很多窗口的时候会呈半透明覆盖状，其中一些看起来非常好看。但某些时候，这会成为一种妨碍。堆叠窗口与覆盖预览之后的是什么，在后台时很难看到这些。可以通过将之拉至前台来解决问题，但这样一来则很难评价透明的意义在哪里。
|
||||
|
||||
|
||||
|
||||
透明... 意义何在？
|
||||
|
||||
是的，Breeze 主题仍然处于测试中，不仅仅是功能和设计；工作重点放在了真正 bug 还有缺陷上。同时我们还遇到了一些意料之外的情况，特别是关于屏幕刷新的问题。这些问题频繁发生，很长时间才引起我们的注意。窗口时常消失，并且有时菜单栏只显示一半。
|
||||
|
||||
Plasma 5 在我们的测试期间从未崩溃过，并且从未遗失任何数据。但注意 ———— 经常会有一些图像方面的小 bug 出现。我们建议你在稳定版发布前不要尝试进行更新。
|
||||
|
||||
### Plasma 的垂直菜单 ###
|
||||
|
||||
Breeze 给 Plasma 5 带来一种新外观，同时也带来了许多细节方面的变化。例如，窗口小部件和 ALT-TAB 窗口切换均呈现垂直显示，并且默认都具有相同的启动位置 ———— 当前屏幕的左侧。
|
||||
|
||||
|
||||
|
||||
ALT-TAB 窗口切换的默认外观。
|
||||
|
||||
共通性也许对于 KDE 的新特点是有利的，当需要帮助时所需资料会出现在屏幕的左侧，但这也许会对那些期待点其他东西的老用户感到失望。有些变化看上去不太合情理。
|
||||
|
||||
|
||||
窗口小部件。
|
||||
|
||||
KDE 项目称在像窗口小部件和窗口切换器等菜单中，垂直菜单将取代水平菜单，“提供更好的使用体验”。但并未提及会具体如何。发行文档称挪动窗口切换器至屏幕一端“使用户的注意力更加集中于应用和文档，以完成手头上的工作”。可是当你启用了窗口切换器，嗯，准备切换窗口时，你的注意力更可能是在不同的任务间而不是集中在某一个任务上面。
|
||||
|
||||
|
||||
|
||||
KDE 依旧偏向于提供不同选择。注意右侧的暗灰色选择条，那是拖动窗口时的阴影选项。
|
||||
|
||||
这就是 KDE，当然，不是 Unity；高度可定制化是其一大特色，而不是 bug。进入系统设置你可以调回旧版风格的窗口切换器，并且在 Plasma 5 中有 10 种不同的窗口切换器效果可供选择。如果默认风格并不是你最喜欢的，那么换一个吧。
|
||||
|
||||
### 告别 Nepomuk 语义桌面的时间，感谢长久以来支持着我们的粉丝 ###
|
||||
|
||||
如果你是 KDE 重度用户，并且经历了 KDE 的顶峰和低谷，并仍抱有期待，那么你肯定已经知道了 Plasma 5 中的最大看点。没错，KDE 替换了 Nepomuk 语义桌面，取而代之的是称作 Baloo 的新搜索引擎。
|
||||
|
||||
Nepomuk 语义桌面最初是一个由欧盟赞助的搜索项目，高调宣称其目的是创建一个“使用网络环境提供个性化服务的，基于本地的知识库管理(Networked Environment for Personalized, Ontology-based Management of Unified Knowledge)”。当项目被引用到 KDE 上的时候，Nepomuk 成为了一个更加通用的桌面搜索工具，在辉煌与疯狂之间徘徊着。
|
||||
|
||||
|
||||
|
||||
在 Plasma 5 中搜索文件。
|
||||
|
||||
Baloo 沿用了 Nepomuk 的大部分功能，全文字文件搜索和一种不可思议的文件衔接功能，比如，知晓与一个特定文件相关的其他文件并[予之改进][4]。实际上这使用于 Plasma 5 中的搜索功能，并且你可以在搜索栏的右边注意到两点：更快的速度以及每次索引更新时你的风扇并未发疯般狂转。
|
||||
|
||||
Baloo 大幅减少了搜索记录的资源，并且，根据 KDE 上的测试，其准确度更高了。我们不能保证后一点，因为我们从未在旧版 KDE 中使用大量搜索（参见风扇运转注释），但在计算精度上，Plasma 5 中的简单文件搜索达到了你使用 Ubuntu、OS X 等其他文件搜索方式的平均速度。涉及更复杂的搜索关系或复杂元数据的成功将更大程度上取决于你使用默认 KDE 应用的频率。比方说，如果你想利用基于 Baloo 的搜索引擎的优势进行涉及文件间关联的搜索时，你需要使用 Kontact 套件。
|
||||
|
||||
尽管这肯能会随着时间而改变，因为与 Nepomuk 相比另一个比较大的变化是新的、改进的开发者 API。搜索 API 意味着第三方应用可以配合 Plasma 5 中的语义搜索基础，并发挥默认应用所使用的相同工具的优势。
|
||||
|
||||
奇怪的是，其他可见的和 Baloo 具有相同任务量的搜索工具，其可见度与发掘性已经落后一步了。点燃 Plasma 5 的开始菜单 ———— KDE 对窗口开始菜单的回应 ———— 并且无法找到搜索栏。如果你仔细寻找，你将会找到一个非常小的提醒样式的“点击以进行搜索”，这是初版以来的第一步改变（没有你可以进行搜索的指示）。然而，可以发现这并不是一个专门的搜索框。
|
||||
|
||||
### Kickoff 开始菜单与他的新表弟 Kicker ###
|
||||
|
||||
KDE 提交的关于窗口开始菜单的答案一直是过度包装的、狭小空间内拥挤的视觉外观，但在 Breeze 主题中开始菜单开始变得清爽，并更具有视觉观赏性。
|
||||
|
||||
|
||||
|
||||
默认主题下的开始菜单。
|
||||
|
||||
如果这样对你的需求来说还是有点多，Plasma 5 提供了一个全新的、更加传统的菜单 ———— 称为 Kicker，基于原启动器。Kicker 所需完成的任务更少 ———— 它更接近于 XP 中的开始菜单，在需要提供扩展菜单的地方提供一种单一的、狭窄的面板 ———— 并且在你如果只是想启动应用或打开文件时，提供一种更加轻量级的选择。它也有一个非常显眼的搜索框。
|
||||
|
||||
|
||||
|
||||
另一个选择 ———— 全新的 Kicker 菜单。
|
||||
|
||||
菜单的另一侧得到了更新，变得更加清爽。最显著的变化是通知中心，减少了弹出次数，并且通过更好、更迅速方式来显示通知。
|
||||
|
||||
### OpenGL、QtQuick 以及 HiDPI 显示 ###
|
||||
|
||||
Plasma 5 完成了 KDE 至 Qt 5 和 QtQuick 的迁移，后者使用硬件加速的 OpenGL 场景图进行图形渲染。OpenGL 的大部分更新都和任何可用的 GPU 图形卸载有关。这意味着，如果你拥有被支持的硬件，Plasma 5 将利用现今强劲的 GPU 充分发挥显卡优势。
|
||||
|
||||
事实上，在最新的硬件上（例如我们测试所用的 MacBook 的 NVIDIA GeForce GT 显卡）Plasma 5 的反应速度很迅捷，远比其老版本要快。也许更令人印象深刻的是，即使把 Plasma 5 相比 KDE 4.x 在 GPU 上的优势去除，其反应速度仍然很快。也就是说，虽然在老旧硬件上运行仍然不是 KDE 的强项，但其表现与之前相比已有所改观。不过，如果你想在老旧硬件上得到更多支持，请务必使用 Xfce、LXDE 或者某些像 Openbox 那样简单的桌面环境吧。
|
||||
|
||||
有趣的是，弥补 Plasma 5 图形叠加的修改过后的框架也向 KDE 切换至 Wayland 显示服务协议提供了道路。尽管 KDE 并没有急着切换到 Wayland，但注意全面支持技术将在“某个未来版本”实现。
|
||||
|
||||
这一版本也声称改进了对 HDPI 显示的支持。然而，结合 GNOME 和 Unity 对 HDPI 的支持，实际经验是忧喜参半的。特别是字体渲染远不及 OS X 所提供的渲染平滑。对我来说，即使安装 了 Infinality 并进行调整，也从来没有出现令我满意的结果。我们仍然不确定问题是否是在安装过程中出现的，并且我们也未亲眼见到 HDPI 的新功能。或许，KDE 对于究竟是什么构成了 HDPI 支持有一个完全不同的定义。但愿问题是出在安装过程中。
|
||||
|
||||
### 有哪些缺陷 ###
|
||||
|
||||
在本文的前半部分，我们曾提到由 KDE 4 向 Plasma 5 的转变将不会像从 KDE 3 向 KDE 4 的转变那样艰难。对大多数人来说，这是真的，但是，对于某些人来说，也许会出现例外。
|
||||
|
||||
KDE 项目称这一版本的焦点已经“集中在了弥补核心工作流的工具上”，并表明“并不是所有 Plasma 4 系列中的功能都可以使用了”。这给那些经历了 KDE 3 向 KDE 4 转变的人敲响了警钟。
|
||||
|
||||
在测试期间，我们并未遇到任何性能上的差距或者功能上的显著缺失，除了提到：Breeze 主题的不完善、某些图形故障，以及某些可疑的设计方面的问题。也就是说，请查阅[已知问题列表][5]，特别是性能方面的警示。
|
||||
|
||||
同时我们在此建议在你完全迁移至 Plasma 5 之前请提前测试，以确保你所必需的都已具备。
|
||||
|
||||
### 结论 ###
|
||||
|
||||
KDE Plasma 5 版本缺乏使 Unity 和 GNOME 一跃成名的那种吸引人的代表性变化。与之相反，KDE 项目致力于改善其核心桌面体验。从任何意义上讲 Plasma 5 都不是完美的，但与 Unity 和 GNOME 不同，你可以随意改变那些你所不喜欢的地方。
|
||||
|
||||
这一版本最激动人心的地方在于 KDE 已经在完全没有弄乱现有桌面的情况下，为交互界面做出了大量铺垫。另一个好消息是速度方面的改善。如果你此前曾经尝试过 KDE 并觉得它过于“庞大”，那么你应该重新审视以下 Plasma 5 了。
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: http://arstechnica.com/information-technology/2014/08/kde-plasma-5-for-those-linux-users-undecided-on-the-kernels-future/
|
||||
|
||||
作者：Scott Gilbertson
|
||||
译者：[SteveArcher](https://github.com/SteveArcher)
|
||||
校对：[wxy](https://github.com/wxy)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创翻译，[Linux中国](http://linux.cn/) 荣誉推出
|
||||
|
||||
[1]:http://arstechnica.com/gadgets/2014/08/op-ed-tables-really-are-pcsbecause-theres-no-point-in-buying-new-ones/
|
||||
[2]:http://www.kde.org/announcements/plasma5.0/
|
||||
[3]:http://files.kde.org/snapshots/neon5-latest.iso.mirrorlist
|
||||
[4]:https://dot.kde.org/2014/02/24/kdes-next-generation-semantic-search
|
||||
[5]:https://community.kde.org/Plasma/5.0_Errata
|
||||
@ -0,0 +1,45 @@
|
||||
“林纳斯·托瓦兹是我的英雄”13岁的扎卡里杜邦说
|
||||
================================================================================
|
||||
|
||||
Zachary DuPon是一名6年级的学生，他马上年满13岁。他过去是Arch liunx的用户，并期待着尽快安装Gentoo Linux。
|
||||
|
||||
Zachary DuPon的故事是这样的-他的学校组织了一个活动，要求学生们给他们的英雄写一封信，大多数孩子写给社会名流，而Zachary DuPon写给了现代科技世界的“真”英雄-林纳斯·托瓦兹。
|
||||
|
||||
由于林纳斯在家工作，他没有透露自己的办公地点，Zach的信送到了Linux基金会，工作人员会在发送给林纳斯之前浏览全部的信件内容。当基金会看到了这封信，他们联系了扎克的学校，慷慨地邀请他做客LinuxCon，这样他就能见到他的英雄本人。
|
||||
|
||||
linux的执行董事长Jim Zemlin在主题小组讨论过后，引领Zach来到人群中。Zach见到了林纳斯并得到了linux之父签名的《linux圣经》；他也得到了林纳斯签名自传[《只为了好玩：一次偶然的革命》][1]
|
||||
|
||||
|
||||
林纳斯·托瓦兹为扎克里杜邦签名
|
||||
|
||||
|
||||
扎克里杜邦一家
|
||||
|
||||
|
||||
本文作者 Swapnil Bhartiya和扎克里杜邦
|
||||
|
||||
我不想失去这个机会，所以他们和林纳斯交谈一结束，我就走向这个家庭，安排了这次视频采访。我是一个两岁孩子的父亲，而作为一名父亲，我着实对Zach自信、清晰，明确的思想所感到惊讶。
|
||||
|
||||
我提供给你这次视屏采访的细节
|
||||
|
||||
- 他使用Arch linux。
|
||||
- 他打算一旦他擅长编程就做出自己的贡献。
|
||||
- 他没有提交任何漏洞报告，并且他认为他应该这样做。他也表示他没有发现任何漏洞。
|
||||
- 他对WINE没太大的兴趣。
|
||||
- 他喜欢KDE的原始桌面，但是它在他的网关机器上工作不是很好。
|
||||
- 他是一个装有XFCE桌面环境的Debian GNU/linux用户。
|
||||
|
||||
林纳斯也许是扎克的英雄，但是扎克是整个GNU/linux和自由软件社区的英雄，他不断地提醒我们，未来尽在我们掌握中。
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: http://www.themukt.com/2014/08/24/linus-torvalds-hero-says-13-years-old-zachary-dupont/
|
||||
|
||||
作者：[Swapnil Bhartiya][a]
|
||||
译者：[luoyutiantang](https://github.com/luoyutiantang)
|
||||
校对：[Caroline](https://github.com/carolinewuyan)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创翻译，[Linux中国](http://linux.cn/) 荣誉推出
|
||||
|
||||
[a]:http://www.themukt.com/author/swapnil_bhartiya/
|
||||
[1]:http://www.amazon.com/gp/product/0066620732/ref=as_li_tl?ie=UTF8&camp=1789&creative=9325&creativeASIN=0066620732&linkCode=as2&tag=muktware-20&linkId=HBKEBIFVZQC35GGK
|
||||
@ -0,0 +1,45 @@
|
||||
GIMP 2.8.12 发布了，来看看如何在Ubuntu上安装
|
||||
================================================================================
|
||||
**GIMP是深受欢迎的开源Photoshop替代软件，它的[新版本][1]现在可以下载了。**
|
||||
|
||||
|
||||
GIMP是一款免费的可替代Photoshop的软件
|
||||
|
||||
正如在GIMP 2.8.x 系列中的最新条目——[自2012年起开始发布][2]并着重介绍长期追求的“单窗口模式”——版本2.8.12并没有重新去做它而是继续改进。如其所说，软件并没有发现面向用户的新特点。
|
||||
|
||||
然而，开发人员修复了一批新的漏洞，旨在提高整体的稳定性，安全性以及这款著名软件的风格。
|
||||
|
||||
- 插件的笔刷大小不再变形。
|
||||
- .XCF 文件的加载更稳固。
|
||||
- 小部件的方向现在匹配界面语言（例如 RTL）。
|
||||
- script-fu-server 的安全性提高。
|
||||
|
||||
文档，帮助以及翻译的更新也包括在其中。想了解在版本 2.8.10 和 2.8.12 之间所有修复完整更改日志，可以看[GNOME Git日志][2]。
|
||||
|
||||
### 在Ubuntu上安装最新的GIMP ###
|
||||
|
||||
最新发布的源代码可以从官方网站上或者从[官方种子文件][3]下载。
|
||||
|
||||
在Ubuntu上呢？在Ubuntu 12.04 和14.04 LTS 上你可以通过添加[以下第三方PPA][4]软件源来安装GIMP 2.8.12：
|
||||
|
||||
sudo add-apt-repository ppa:otto-kesselgulasch/gimp
|
||||
|
||||
sudo apt-get update && sudo apt-get install gimp
|
||||
|
||||
在安装完成后，你可以从Unity Dash（或者类似途径）来启动GIMP 2.8.12。
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: http://www.omgubuntu.co.uk/2014/08/whats-new-in-gimp-2-8-12-plus-install-ubuntu
|
||||
|
||||
作者：[Joey-Elijah Sneddon][a]
|
||||
译者：[linuhap](https://github.com/linuhap)
|
||||
校对：[Caroline](https://github.com/carolinewuyan)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创翻译，[Linux中国](http://linux.cn/) 荣誉推出
|
||||
|
||||
[a]:https://plus.google.com/117485690627814051450/?rel=author
|
||||
[1]:http://www.omgubuntu.co.uk/2012/05/gimp-2-8-released
|
||||
[2]:https://git.gnome.org/browse/gimp/plain/NEWS?h=gimp-2-8
|
||||
[3]:http://download.gimp.org/pub/gimp/v2.8/gimp-2.8.12.tar.bz2.torrent
|
||||
[4]:https://launchpad.net/~otto-kesselgulasch/+archive/ubuntu/gimp
|
||||
@ -0,0 +1,55 @@
|
||||
Remarkable：Linux平台下一个新的MarkDown编辑器
|
||||
===
|
||||
|
||||
|
||||
|
||||
[Remarkable][1]是一个全新，免费，功能齐全的Linux发行版Markdown编辑器。它拥有许多特性，比如：在线预览，这让你的Markdown编辑变得更加容易。它是一个轻量级的编辑器，而且它还有一个简洁的用户界面(UI)。
|
||||
|
||||
下面是Remarkable的主要特性：
|
||||
|
||||
- 实时预览
|
||||
- 支持Github Markdown 语法
|
||||
- 支持导出为PDF和HTML
|
||||
- 自定义CSS
|
||||
- 语法高亮
|
||||
- 高度可定制
|
||||
- 字数实时计数
|
||||
- 键盘快捷键
|
||||
|
||||
|
||||
|
||||
你可以观看[这部YouTube视频][2]（请自备梯子:-]）了解Linux下的Remakable。
|
||||
|
||||
### 安装 ###
|
||||
|
||||
根据不同的Linux发行版本，Remarkable拥有许多可供使用的安装源，下面是不同Linux发行版以及它们对应的安装文件
|
||||
|
||||
#### Ubuntu / Linux Mint: ####
|
||||
|
||||
- [Dowbnload .DEB][3]
|
||||
|
||||
#### Fedora: ####
|
||||
|
||||
- [Download .RPM][4]
|
||||
|
||||
#### Arch Linux (AUR): ####
|
||||
|
||||
sudo yaourt -S remarkable
|
||||
|
||||
喜欢吗？
|
||||
|
||||
---
|
||||
|
||||
via: http://www.unixmen.com/remarkable-new-markdown-editor-linux/
|
||||
|
||||
作者：[Enock Seth Nyamador][a]
|
||||
译者：[su-kaiyao](https://github.com/su-kaiyao)
|
||||
校对：[Caroline](https://github.com/carolinewuyan)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创翻译，[Linux中国](http://linux.cn/) 荣誉推出
|
||||
|
||||
[a]:http://www.unixmen.com/author/seth/
|
||||
[1]:http://remarkableapp.net/
|
||||
[2]:https://www.youtube.com/watch?v=UpjAIcXti9s
|
||||
[3]:http://remarkableapp.net/files/remarkable_0.965_all.deb
|
||||
[4]:http://remarkableapp.net/files/remarkable-0.965.rpm
|
||||
@ -0,0 +1,72 @@
|
||||
Ubuntu壁纸大赛落幕，推荐八张我们喜欢的
|
||||
================================================================================
|
||||
|
||||
**盖上你的镜头，放下你的笔，拔掉手绘板的电源，从你的GIMP前离开，[Ubuntu 14.10 壁纸大赛][1] 现在结束了**
|
||||
|
||||
为 Ubuntu 发行版的配套的一年两次的社区壁纸大赛总是会带来人们的激动、热情和争议的讨论。*太单调了！太亮了！植物在哪里？ 你为什么没有猫？？！！* —— 他们总是这样吵吵。
|
||||
|
||||
随着终结时间的到来。。好吧，这就是最后期限了，现在不再接收任何新的提交了。
|
||||
|
||||
在接下来的一周，为了评选出最喜爱的作品，会由上一年获胜的艺术家组成的评委会将会对每一个作品进行筛选。**获胜的壁纸将会在2014年9月9日宣布**.
|
||||
|
||||
### 我们最喜爱的仅仅意味着：这是属于我们的。 ###
|
||||
|
||||
我们从[大约400张][2]中搜罗了一些我们最喜爱的，如同以往，这是一个非常苦难的任务，如此多的杰作，但我们的磁盘空间却如此的小...
|
||||
|
||||
**否认声明**：我们不属于评委会，我们也没有直接或间接影响评委会的决定。每个提交作品都会根据他们的价值进行判断和展示。
|
||||
|
||||
如果喜欢下列作品，你可以点击进入艺术家作者在Flickr上的主页
|
||||
|
||||
#### Glden leaves ####
|
||||
|
||||
[][3]
|
||||
|
||||
#### Reminiscent Rain ####
|
||||
|
||||
[][4]
|
||||
|
||||
#### Bamboo Mat ####
|
||||
|
||||
[][5]
|
||||
|
||||
#### LSC_0440 ####
|
||||
|
||||
[][6]
|
||||
|
||||
#### Ubuntu Wallpaper ####
|
||||
|
||||
[][7]
|
||||
|
||||
#### Ubur ####
|
||||
|
||||
[][8]
|
||||
|
||||
#### Abstract ####
|
||||
|
||||
[][9]
|
||||
|
||||
#### 500 ####
|
||||
|
||||
[][10]
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: http://www.omgubuntu.co.uk/2014/08/best-ubuntu-wallpaper-contest-entries-1410
|
||||
|
||||
作者：[Joey-Elijah Sneddon][a]
|
||||
译者：[lfzark](https://github.com/lfzark)
|
||||
校对：[wxy](https://github.com/wxy)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创翻译，[Linux中国](http://linux.cn/) 荣誉推出
|
||||
|
||||
[a]:https://plus.google.com/117485690627814051450/?rel=author
|
||||
[1]:http://www.omgubuntu.co.uk/2014/08/ubuntu-14-10-wallpaper-contest
|
||||
[2]:https://www.flickr.com/groups/1410wallpapersubmissions/
|
||||
[3]:https://www.flickr.com/photos/mauro_campanelli/14919901295
|
||||
[4]:https://www.flickr.com/photos/fixem/14858973848
|
||||
[5]:https://www.flickr.com/photos/havaxinhua/14222953450
|
||||
[6]:https://www.flickr.com/photos/laurentschenkel/14698997457
|
||||
[7]:https://www.flickr.com/photos/57135082@N05/14573905897
|
||||
[8]:https://www.flickr.com/photos/anomalous_saga/8423532123
|
||||
[9]:https://www.flickr.com/photos/el_nando/14969203701
|
||||
[10]:https://www.flickr.com/photos/e4v/14660376638
|
||||
@ -0,0 +1,37 @@
|
||||
Ubuntu文本检索神器——SearchMonkey
|
||||
================================================================================
|
||||
有时候，我们需要搜索包含有某些特定文本或单词的文件。如果你是个开发者或者程序员，经常会碰到这样的问题。现在，我们总是能够使用[Linux命令来查找包含有指定文本的所有文件][1]，但不是每个人都热衷于命令行。我见过那些优秀的程序员，他们更多的是依赖于图形化工具，而不是命令行。
|
||||
|
||||
如果你也更喜欢图形化工具，那么[SearchMonkey][2]对于你而言是个十分完美的应用。
|
||||
|
||||
### SearchMonkey是你的桌面搜索引擎 ###
|
||||
|
||||
SearchMonkey递归搜索目录，因此你可以在它工作的时候坐下放松一下。用户可以使用强大的正则表达式来搜索文件名和内容，这使得SearchMonky返回结果时更为精确。
|
||||
|
||||
此外，SearchMonkey不仅仅给你列出可能包含有你正在查找的内容的文件，它也高亮显示匹配的内容。
|
||||
|
||||
### 在Ubuntu 14.04中安装SearchMonkey ###
|
||||
|
||||
SearchMonkey可以在Ubuntu 14.04的软件仓库中找到，你只需要通过Ubuntu软件中心或者通过以下命令来安装：
|
||||
|
||||
sudo apt-get install searchmonkey
|
||||
|
||||
安装完毕后，你可以从Unity Dash中启动SearchMonkey。界面简明直观，易于使用。
|
||||
|
||||
|
||||
|
||||
SearchMonkey帮助你快速查找到你所需要的文件，不需要先构建一个驱动映射。每次搜索都是实时的，结果也会在找到后立即在上下文中显示！尤，其，它还是一个免费又开源的软件。
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: http://itsfoss.com/searchmonkey-search-text-files-linux/
|
||||
|
||||
作者：[Amit Asthana][a]
|
||||
译者：[GOLinux](https://github.com/GOLinux )
|
||||
校对：[Caroline](https://github.com/carolinewuyan)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创翻译，[Linux中国](http://linux.cn/) 荣誉推出
|
||||
|
||||
[a]:http://itsfoss.com/author/amit/
|
||||
[1]:http://www.computerandyou.net/2011/06/how-to-find-all-files-containing-specific-text-in-linux/
|
||||
[2]:http://searchmonkey.embeddediq.com/
|
||||
@ -1,15 +1,16 @@
|
||||
如何在Linux命令行下收听网络电台
|
||||
========================================================================
|
||||
对于系统管理员和Linux爱好者来说，我们花大量的时间在Linux屏幕前，但是你们知道网络/本地电台上的音乐可以极大的提高我们的生产力吗？不管你相信与否，在工作环境中有适当的声音，如音乐或者喋喋不休的声音都可以提高我们的创造力。如果你喜欢在音乐环境中工作，这个教程也许会对你有用。我将会向你展示**如何在命令行中收听潘多拉（Pandora）在线电台**（LCTT译注：Pandora Internet Radio是一个仅为美国、澳大利亚和新西兰提供自动音乐推荐的系统。详细介绍[Prandoea电台][1]）
|
||||
|
||||
正如你已经知道的，Pandora是最有名的在线电台服务之一，它包含无数的不同种类的免费音乐流，同时它还有一个强大的音乐推荐引擎。Pandora可以通过不同的方法访问，如：浏览器，桌面客户端或者手机Apps，开源社区还给出了另一种访问Pandora音乐服务的方法：Linux命令行。
|
||||
对于花大量时间在Linux屏幕前的系统管理员和Linux爱好者来说，网络/本地电台上的音乐可以极大提高生产力，你们知道吗？不管你们相信与否，，在工作环境中有适当的声音，如音乐或者闲聊声包围，都可以提高我们的创造力。如果你喜欢在音乐环境中工作，这个教程也许会对你有用。我将会向你展示**如何在命令行中收听潘多拉（Pandora）在线电台**（LCTT译注：Pandora Internet Radio是一个仅为美国、澳大利亚和新西兰提供自动音乐推荐的系统。详细介绍[Prandoea电台][1]）
|
||||
|
||||
[pianobar][2]是一个播放Pandora在线电台音乐的开源命令行音乐播放器。它有一个简单的人机接口，用于播放和管理音乐电台。同时还有其他包括歌曲评价，即将上线音乐列表，播放历史，自定义快捷键绑定，远程控制等功能。对于那些居住在不可访问Pandora音乐服务区域的用户（即美国、澳大利亚和新西兰以外的用户）。Pianobar还配置了代理服务的支持。
|
||||
正如你已经知道的，Pandora是最有名的在线电台服务之一，它包含无数的不同种类的免费音乐流，同时它还有一个强大的音乐推荐引擎。Pandora可以通过不同的方式访问，如：浏览器，桌面客户端或者手机Apps，开源社区还给出了另一种访问Pandora音乐服务的方法：Linux命令行。
|
||||
|
||||
[pianobar][2]是一个播放Pandora在线电台音乐的开源命令行音乐播放器。它有一个简单的终端接口，用于播放和管理音乐电台。同时还有其他包括歌曲评价，即将上线音乐列表，播放历史，自定义快捷键绑定，远程控制等功能。对于那些居住在不可访问Pandora音乐服务区域的用户（即美国、澳大利亚和新西兰以外的用户），Pianobar还配置了代理服务的支持。
|
||||
|
||||
###在Linux中安装Pianobar###
|
||||
在Debian或者其他Debian的衍生品，如Ubuntu或LinuxMint中，Pianobar是一个已经编译好的软件包，因此安装Pianobar只是简单的输入如下命令：
|
||||
|
||||
$ sudo apt-get install pianobar
|
||||
在Debian或者其他Debian的衍生品中，如Ubuntu或LinuxMint，Pianobar是一个已经编译好的软件包，因此安装Pianobar只是简单的输入如下命令：
|
||||
$ sudo apt-get install pianobar
|
||||
|
||||
在Fedora中，Pianobar并不包含在基础的软件库中。因此，你需要通过源代码编译安装Pianobar。整个安装过程会有点麻烦，但是下面的教程将会实现Pianobar在Frdora系统中编译安装。该教程在Fedora20版本中测试通过。
|
||||
|
||||
@ -31,7 +32,7 @@
|
||||
|
||||
>/usr/local/lib
|
||||
|
||||
重载所有的共享库
|
||||
重载所有的共享库
|
||||
|
||||
就这样，Pianobar已经在Fedora系统中安装完成。
|
||||
|
||||
@ -46,6 +47,7 @@ paniobar的基本用法是输入如下命令：
|
||||
|
||||
|
||||
按‘？’按键pianobar会列出一系列可用个命令，其中一些如下：
|
||||
|
||||
>- s: 更换电台
|
||||
- u: 查看即将上线音乐列表
|
||||
- h: 查看播放历史
|
||||
@ -61,8 +63,9 @@ paniobar的基本用法是输入如下命令：
|
||||
|
||||
|
||||
|
||||
###将Pianobar配置为自动登录###
|
||||
你可以再一个单独的配置文件中配置Pianobar的各项默认配置。例如：你可以将你的登录信息配置到配置文件中，这样你就不用每次都要手动输入。下面是如何创建一个配置文件的示例：
|
||||
###将Pianobar配置为自动安装###
|
||||
|
||||
你可以在一个单独的配置文件中配置Pianobar的各项默认配置。例如：你可以将你的登录信息放到配置文件中，这样你就不用每次都要手动输入。下面是如何创建一个配置文件的示例：
|
||||
|
||||
> $ mkdir -p ~/.config/pianobar
|
||||
|
||||
@ -93,7 +96,7 @@ paniobar的基本用法是输入如下命令：
|
||||
|
||||
###远程控制Pianobar###
|
||||
|
||||
Pianobar的另一个优秀的特性是支持远程控制，你可以通过命令管道（FIFO）为Pianobar的一个运行实例发送命令。下面是远程控制Pianobar的示例：
|
||||
Pianobar的另一个优秀特性是支持远程控制，你可以通过命令管道（FIFO）为Pianobar的一个运行实例发送命令。下面是远程控制Pianobar的示例：
|
||||
|
||||
首先在目录~/.config/pianobar下创建一个FIFO命令管道
|
||||
|
||||
@ -113,9 +116,9 @@ Pianobar的另一个优秀的特性是支持远程控制，你可以通过命令
|
||||
|
||||
当然，你希望为登录到主机X的SSH登录认证[启用秘钥认证][5]，这样你就不用每次都输入SSH密码。
|
||||
|
||||
当你想在[树莓PI][6]上设置一个可以远程控制的在线电台播放器时，Pianobar的远程控制特性将会让你非常方便的实现该需求。
|
||||
当你想在[树莓Pi][6]上设置一个可以远程控制的在线电台播放器时，Pianobar的远程控制特性将会让你非常方便地实现该需求。
|
||||
|
||||
希望你像我一样喜欢Pianobar，若有什么想法，请在评论中告诉我。
|
||||
希望你和我一样喜欢Pianobar，若有什么想法，请在评论中告诉我。
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
@ -123,7 +126,7 @@ via: http://xmodulo.com/2014/08/listen-to-internet-radio-command-line-linux.html
|
||||
|
||||
作者：[Dan Nanni][a]
|
||||
译者：[cvsher](https://github.com/cvsher)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
校对：[Caroline](https://github.com/carolinewuyan)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创翻译，[Linux中国](http://linux.cn/) 荣誉推出
|
||||
|
||||
@ -1,46 +0,0 @@
|
||||
linuhap翻译中
|
||||
GIMP 2.8.12 Released — Here’s How to Install it on Ubuntu
|
||||
================================================================================
|
||||
**A [new update][1] to the popular open-source Photoshop alternative The GIMP is now available for download.**
|
||||
|
||||
|
||||
GIMP is a Free Photoshop Alternative
|
||||
|
||||
As the latest entry in the GIMP 2.8.x series — [released back in 2012][2] and notable for introducing the long-sought ‘single window mode’ — version 2.8.12 continues to refine rather than reinvent. As such there are no new user-facing features to be found.
|
||||
|
||||
Instead, developers bring a fresh batch of bug fixes to the table aimed at improving the overall stability, security and style of the famous app.
|
||||
|
||||
- Brush sizes from plugins are no longer distorted
|
||||
- ‘More robust’ loading of .XCF files
|
||||
- Widget direction now matches interface language (e.g. RTL)
|
||||
- Security improvements to the script-fu-server
|
||||
|
||||
Documentation, help and translation updates are also included. For a complete change log of everything fixed between 2.8.10 and 2.8.12, see [the GNOME Git notes][2].
|
||||
|
||||
### Install Latest GIMP in Ubuntu ###
|
||||
|
||||
Source for the latest release can be downloaded from the official website or via [an official torrent][3].
|
||||
|
||||
On Ubuntu? You can install GIMP 2.8.12 in Ubuntu 12.04 LTS and 14.04 LTS by adding the [following third-party PPA][4] to Software Sources:
|
||||
|
||||
sudo add-apt-repository ppa:otto-kesselgulasch/gimp
|
||||
|
||||
sudo apt-get update && sudo apt-get install gimp
|
||||
|
||||
After installation has complete you can proceed to open GIMP 2.8.12 from the Unity Dash (or equivalent).
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: http://www.omgubuntu.co.uk/2014/08/whats-new-in-gimp-2-8-12-plus-install-ubuntu
|
||||
|
||||
作者：[Joey-Elijah Sneddon][a]
|
||||
译者：[译者ID](https://github.com/译者ID)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创翻译，[Linux中国](http://linux.cn/) 荣誉推出
|
||||
|
||||
[a]:https://plus.google.com/117485690627814051450/?rel=author
|
||||
[1]:http://www.omgubuntu.co.uk/2012/05/gimp-2-8-released
|
||||
[2]:https://git.gnome.org/browse/gimp/plain/NEWS?h=gimp-2-8
|
||||
[3]:http://download.gimp.org/pub/gimp/v2.8/gimp-2.8.12.tar.bz2.torrent
|
||||
[4]:https://launchpad.net/~otto-kesselgulasch/+archive/ubuntu/gimp
|
||||
@ -0,0 +1,37 @@
|
||||
LibreOffice 4.3.1 Has More than 100 Fixes and DOCX Embedded Objects Support
|
||||
================================================================================
|
||||
|
||||
LibreOffice selection menu
|
||||
|
||||
**The Document Foundation announces that the stable version of LibreOffice 4.3.1 has been released and is now available for download.**
|
||||
|
||||
The developers from The Document Foundation have released a new update for the 4.3 branch of LibreOffice and they have implemented quite a few fixes and other various changes. The development cycle for this latest update has been rather short and the devs managed to repair most of the issues that have been found.
|
||||
|
||||
LibreOffice 4.3.1 is just maintenance release, which means that the focus has been about the bugs found so far. Don't expect to find anything extraordinary, but you should upgrade the software nonetheless.
|
||||
|
||||
"The Document Foundation announces LibreOffice 4.3.1, the first minor release of LibreOffice 4.3 'fresh' family, with over 100 fixes (including patches for two CVEs, backported to LibreOffice 4.2.6-secfix, which is also available for download now)."
|
||||
|
||||
"All LibreOffice users are invited to update their installation as soon as possible to avoid security issues. This includes users who are running LibreOffice 4.2.6 as originally released on August, 5th 2014. LibreOffice 4.3.1 and LibreOffice 4.2.6 will be shown on stage at the LibreOffice Conference in Bern, from September 3 to September 5, with a large number of sessions about development, community, marketing and migrations," reads the announcement made by The Linux Foundation.
|
||||
|
||||
According to the changelog, editing the text search with expanded fields is now working properly, the static value array for OOXML chart is now handled correctly, bullets now have the color as the following text by default, ww8import no longer creates a pagedesc if a continuous section changes margins, the 0 font height is now handled just like outdev, it's now possible to import OLE objects in the header with background wrapping, the XLSX export of revisions has been fixed in order to get it to work in Excel, and borders around data labels are now supported.
|
||||
|
||||
Also, the table style for lastRow is now correctly applied, the rulers now have app-background by default, the graphics are now swapped in on DrawingML::WriteImage, the redundant 'Preferences' label has been removed in order to save some space, page breaks in tables are now ignored during the RTF import, some of the style hierarchy has been reworked, Data Statistics no longer crashes with any entry, DOCX embedded objects are now supported, and numerous other improvements have been made.
|
||||
|
||||
More details about this release can be found in the official [announcement][1].
|
||||
|
||||
- [Download LibreOffice 4.3.1 for Linux][2]
|
||||
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: http://news.softpedia.com/news/LibreOffice-4-3-1-Has-More-Than-100-Fixes-and-DOCX-Embedded-Objects-Support-456916.shtml
|
||||
|
||||
作者：[Silviu Stahie][a]
|
||||
译者：[译者ID](https://github.com/译者ID)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创翻译，[Linux中国](http://linux.cn/) 荣誉推出
|
||||
|
||||
[a]:http://news.softpedia.com/editors/browse/silviu-stahie
|
||||
[1]:http://blog.documentfoundation.org/2014/08/28/libreoffice-4-3-1-fresh-announced/
|
||||
[2]:http://www.libreoffice.org/download/libreoffice-fresh/
|
||||
@ -0,0 +1,26 @@
|
||||
Ubuntu Touch Now Has a Torrent Client in the Ubuntu Store
|
||||
================================================================================
|
||||
|
||||
|
||||
**The Ubuntu Touch platform is already the host of many interesting applications, and it looks like the developers have started to implement software that goes beyond what you might expect, like a torrent client for example.**
|
||||
|
||||
The app store for Ubuntu Touch has been growing steadily over the past few months and interesting applications are added all the time. Most of them are covering some of the basic needs of the operating system, but there are quite a few that go well beyond regular users’ needs.
|
||||
|
||||
A torrent client is not something that you will find on most phones. Android and Windows Phone already have this kind of apps and it looks like Ubuntu is now one of those platforms. Ubuntu developer [Alan Pope][1] posted a screenshot with a new application that's being developed for the Ubuntu platforms called DowNow.
|
||||
|
||||
This is a relatively new application and it's still under development. You can find the click package for DowNow 0.3 in Launchpad, if you want to take a closer look, or you can download from Ubuntu Software Center.
|
||||
|
||||
For now, the only supported devices are Nexus 4 and Nexus 7, if you want to test Ubuntu for phones, but that might change in the coming months.
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: http://news.softpedia.com/news/Ubuntu-Touch-Now-Has-a-Torrent-Clinent-in-the-Ubuntu-Store-457538.shtml
|
||||
|
||||
作者：[Silviu Stahie][a]
|
||||
译者：[译者ID](https://github.com/译者ID)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创翻译，[Linux中国](http://linux.cn/) 荣誉推出
|
||||
|
||||
[a]:http://news.softpedia.com/editors/browse/silviu-stahie
|
||||
[1]:https://plus.google.com/u/0/+AlanPope/posts/Ej3vKVxBum8
|
||||
@ -0,0 +1,37 @@
|
||||
Jelly Conky Adds Simple, Stylish Stats To Your Linux Desktop
|
||||
================================================================================
|
||||
**I treat Conky setups a bit like wallpapers: I’ll find one I love, only to change it the next week because I’m bored of it and want a change.**
|
||||
|
||||
Part of the impatience is fuelled by the ever-growing catalog of designs available. One of my most recent favourites is Jelly Conky.
|
||||
|
||||
|
||||
|
||||
Jelly Conky sports the minimal design many of the Conky’s we’ve highlighted recently have followed. It’s not trying to be a kitchen sink. It won’t win favour with those who need constant at-a-glance data on their HDD temperatures and IP addresses.
|
||||
|
||||
It comes with three distinct modes that can all add personality to an otherwise static background image:
|
||||
|
||||
- Clock
|
||||
- Clock plus date
|
||||
- Clock plus date and weather
|
||||
|
||||
Some people don’t understand the point of having a duplicate clock on show on the desktop. That’s understandable. For me, it’s more about form than function (though, personally, I find Conky clocks easier to see than the minuscule digits nestled in my upper panel).
|
||||
|
||||
Chances are if you have a home screen widget on Android with the time, you won’t mind having one on your desktop, either!
|
||||
|
||||
You can download Jelly Conky from the link below. The .zip archive contains a readme with instructions on how to install. For a guided walkthrough, [revisit one of our previous articles][1].
|
||||
|
||||
- [Download Jelly Conky on Deviant Art][2]
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: http://www.omgubuntu.co.uk/2014/09/jelly-conky-for-linux-desktop
|
||||
|
||||
作者：[Joey-Elijah Sneddon][a]
|
||||
译者：[译者ID](https://github.com/译者ID)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创翻译，[Linux中国](http://linux.cn/) 荣誉推出
|
||||
|
||||
[a]:https://plus.google.com/117485690627814051450/?rel=author
|
||||
[1]:http://www.omgubuntu.co.uk/2014/07/conky-circle-theme-nod-lg-quick-cover
|
||||
[2]:http://zagortenay333.deviantart.com/art/Jelly-Conky-442559003
|
||||
@ -0,0 +1,79 @@
|
||||
Meet the 12 Ubuntu 14.10 Wallpaper Contest Winners (So Far)
|
||||
================================================================================
|
||||
Get ready to glance over a group of images you’ll be seeing a whole lot more of in the coming months. Yes, the winners of the [Ubuntu 14.10 Wallpaper contest][1] have been unveiled.
|
||||
|
||||
Well, announced ‘sort of’. So far twelve backgrounds have been formally selected to ship on the Ubuntu 14.10 release.
|
||||
|
||||
Having sifted through an entry pool of almost 400 images the judging panel made up of April’s winning artists have chosen a visually varied and colourful collection. I know I say it every 6 months, but this one looks to be the best yet (and not just because one or two of [our own favourites made it in][2]!)
|
||||
|
||||
### Meet The Winners ###
|
||||
|
||||
You can see the current crop of selected images below. Emphasis is on current for now as, according to the contest organiser Iain Farrell, [**he is**][3] “…awaiting a couple from people but if they don’t come back to me we’ll have to go without!” .
|
||||
|
||||
|
||||
|
||||
Obligatory mascot wallpaper
|
||||
|
||||
|
||||
|
||||
‘Empty Space’ by Glenn Rayat
|
||||
|
||||
|
||||
|
||||
Sand & horses by M. Siewert
|
||||
|
||||
|
||||
|
||||
Golden Leaves
|
||||
|
||||
|
||||
|
||||
Life Nomadic by Sal’
|
||||
|
||||
|
||||
|
||||
‘xgu472hf2′ by Lariliikala
|
||||
|
||||
|
||||
|
||||
Rocky shore? Juan PL.
|
||||
|
||||
|
||||
|
||||
‘Warm Grasses’ by dcsearle.t21
|
||||
|
||||
|
||||
|
||||
Kronach Leuchtet by Brian Fox
|
||||
|
||||
|
||||
|
||||
Davor Dopar’s seascape
|
||||
|
||||
|
||||
|
||||
Music by Tomasino
|
||||
|
||||
|
||||
|
||||
Joel Heaps’ Sunny Autumn
|
||||
|
||||
We’ll update this post when/if any changes occur. You can grab a .zip archive of the entries for yourself [from Launchpad][4]. The full Utopic Wallpapers package, likely to include the ‘new’ default wallpaper, will be made available in the next day or two.
|
||||
|
||||
Let us know which of the designs are your favourites in the comments below — and do try to keep things positive!
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: http://www.omgubuntu.co.uk/2014/09/ubuntu-14-10-wallpaper-contest-winners
|
||||
|
||||
作者：[Joey-Elijah Sneddon][a]
|
||||
译者：[译者ID](https://github.com/译者ID)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创翻译，[Linux中国](http://linux.cn/) 荣誉推出
|
||||
|
||||
[a]:https://plus.google.com/117485690627814051450/?rel=author
|
||||
[1]:http://www.omgubuntu.co.uk/2014/08/ubuntu-14-10-wallpaper-contest
|
||||
[2]:http://www.omgubuntu.co.uk/2014/08/best-ubuntu-wallpaper-contest-entries-1410
|
||||
[3]:https://bugs.launchpad.net/ubuntu/+source/ubuntu-wallpapers/+bug/1354341/comments/2
|
||||
[4]:https://bugs.launchpad.net/ubuntu/+source/ubuntu-wallpapers/+bug/1354341/+attachment/4199899/+files/14.10%20images.zip
|
||||
@ -1,200 +0,0 @@
|
||||
[Translating by SteveArcher]
|
||||
KDE Plasma 5—For those Linux users undecided on the kernel’s future
|
||||
================================================================================
|
||||
> Review—new release straddles traditional desktop needs, long term multi-device plans.
|
||||
|
||||
Finally, the KDE project has released KDE Plasma 5, a major new version of the venerable K Desktop Environment.
|
||||
|
||||
Plasma 5 arrives in the middle of an ongoing debate about the future of the Linux desktop. On one hand there are the brand new desktop paradigms represented by GNOME and Unity. Both break from the traditional desktop model in significant ways, and both attempt to create interfaces that will work on the desktop and the much-anticipated, tablet-based future (which [may or may not ever arrive][1]).
|
||||
|
||||
Linux desktops like KDE, XFCE, LXDE, Mate, and even Cinnamon are the other side of the fence. None has re-invented itself too much. They continue to offer users a traditional desktop experience, which is not to say these projects aren't growing and refining. All of them continue to turn out incremental releases that fine tune what is a well-proven desktop model.
|
||||
|
||||
|
||||
Ubuntu's Unity desktop
|
||||
|
||||
|
||||
GNOME 3 desktop
|
||||
|
||||
GNOME and Unity end up getting the lion's share of attention in this ongoing debate. They're both new and different. They're both opinionated and polarizing. For every Linux user that loves them, there's another that loves to hate them. It makes for, if nothing else, lively comments and forum posts in the Linux world. But the difference between these two Linux camps is about more than just how your desktop looks and behaves. It's about what the future of computing looks like.
|
||||
|
||||
GNOME and Unity believe that the future of computing consists of multiple devices all running the same software—the new desktop these two create only makes sense within this vision. These new versions aren't really built as desktops for the future, but they include a hybrid desktop fallback mode for now and appear to believe in devices going forward. The other side of the Linux schism largely seems to ignore those.
|
||||
|
||||
And unlike the world of closed source OSes—where changes are handed down, like them or leave them—the Linux world is in the middle of a conversation about these two opposite ideas.
|
||||
|
||||
For users, it can be frustrating. The last thing you need when you're trying to get work done is an update that completely changes your desktop, forcing you to learn new ways of working. Even the best case scenario, moving to another desktop when your old favorite suddenly veers off in a new direction, usually means jettisoning years of muscle memory and familiarity.
|
||||
|
||||
Luckily, there's a simple way to navigate this mess and find the right desktop for you. Here it is in a nutshell: do you want to bend your will to your desktop or do you want to bend your desktop to your will?
|
||||
|
||||
If you fall in the first camp and don't mind learning new ways of working, Unity and GNOME 3 will be your best bets. If you fall in the latter camp, XFCE, Cinnamon, Mate, and a host of others will all likely prove a good fit. And even if you want to go non-traditional in a different direction from GNOME 3 and Unity, there's always Xmonad, Ratpoison, and others that very few Linux users will ever try. (This is a small shame, as Xmonad may be the best thing in Linux since Linus said, uh, hey, here's a kernel for your GNU system.)
|
||||
|
||||
|
||||
KDE Plasma 5's new boot screen.
|
||||
|
||||
So what about the undecided Linux users, all those people in the middle? You like the traditional desktop experience, and you're not ready to give up your menu and shortcuts for HUDs and other new tools. But at the same time, you're curious about tablets and other form factors, and you want something that will work across them all. You, my hypothetical friend, are an excellent candidate for the brand new KDE Plasma 5.
|
||||
|
||||
KDE is attempting to do something no other desktop in Linux has tried to date—move toward the tablet and mobile device future while still producing a desktop experience that's familiar, functional, and infinitely customizable.
|
||||
|
||||
### KDE Plasma 5 and the world of "convergence" ###
|
||||
|
||||
KDE users who made it through the transition from KDE 3.5 to 4 likely still flinch at the mention of a major upgrade to any part of KDE, but there's good news for KDE fans in Plasma 5. This is a major update, yes, but it comes with a handful of exceptions (which I'll get into in a minute because you'd never know it).
|
||||
|
||||
It turns out that the incredibly bumpy move to KDE 4 really did lay the groundwork for a better future—we are now in that future.
|
||||
|
||||
With this update, KDE is laying future groundwork in a less disruptive way. We're referring to an inevitable move to tablets and other form factors, but fear not. KDE seems poised to do what GNOME and Unity could not—branch out to other form factors without abandoning the traditional desktop. In other words, this release resisted the urge to mess with the tried and true just because something new is on the horizon.
|
||||
|
||||
(As a quick aside: You'd be forgiven for not remembering this, but the whole convergence thing that Canonical goes on about with each new Unity update? KDE started using the word "convergence" way back when Canonical was still running user tests to determine the optimal shade of brown for GNOME 2 menus.)
|
||||
|
||||
With KDE Frameworks 5, Qt5, and some other updates to the plumbing that come along with Plasma 5, KDE's version of convergence is here. It's simply under the hood where it belongs.
|
||||
|
||||
So while the components are there to allow the KDE project and its developers to build different interfaces—KDE calls these new frameworks the "converged Plasma shell," which is what loads up the desktop in Plasma 5—the Plasma 5 desktop is, thus far, the only interface. KDE plans to build out others, but the [official release announcement][2] for Plasma 5 says that "a tablet-centric and media center user experience are under development."
|
||||
|
||||
In this sense, KDE's vision of convergence is not unlike what Ubuntu envisions; the user interface will change based on the device and hardware. For example, you might have the "tablet-centric" interface that's in the works running while you're reading the Web on the couch. But get up, walk back to your office, connect to your wireless keyboard, and the interface shifts to something more keyboard-friendly.
|
||||
|
||||
This scenario has some potential problems, some of which Windows 8 users are likely already familiar with. For example, what will happen when a keyboard is plugged in, but you still want to interact with the screen via touch? What happens if you plug in a mouse, but you still want to scroll with your fingers?
|
||||
|
||||
We mention these small points not to say that KDE hasn't thought them through (here's hoping they have), but because this idea of "convergence" of adaptive user interfaces will be very difficult to get right. And one thing KDE has long had that gives users hope for the project's success is limitless configurability.
|
||||
|
||||
The hope for KDE on a tablet is that any user would be able to configure every last detail of the experience. Simply put, there would be a way for you to determine what you want to happen when a keyboard is detected rather than letting the OS determine it.
|
||||
|
||||
### The Plasma 5 desktop ###
|
||||
|
||||
KDE Plasma 5 is KDE 4 evolved rather than any kind of revolutionary new interface.
|
||||
|
||||
|
||||
The KDE Plasma 5 desktop.
|
||||
|
||||
We've been using this release—still not completely stable during testing, though most of the glitches have been graphical, not data threatening—for over a month now in virtual machines. We've been dual booting on a Retina MacBook Pro and, to see how well it holds up on older hardware, an aging, underpowered Toshiba laptop. KDE Plasma 5 was tested using Kubuntu (virtual machine and the Toshiba) and atop a fresh install of Arch Linux (dual boot MacBook).
|
||||
|
||||
If you'd like to try out Plasma 5, the simplest way is to grab the [Neon live CD available from KDE][3]. That will get you Plasma with Ubuntu under the hood. If you want to commit and test it on an existing Kubuntu install, here are the commands for that:
|
||||
|
||||
sudo add-apt-repository ppa:neon/kf5
|
||||
sudo apt-get update
|
||||
sudo apt-get install project-neon5-session project-neon5-utils project-neon5-konsole project-neon5-breeze project-neon5-plasma-workspace-wallpapers
|
||||
|
||||
Restart your machine and you should see a new option at the login screen offering to start up a Neon session.
|
||||
|
||||
Once you have Plasma 5 up and running, the first thing you'll notice is the new default KDE theme, known as Breeze.
|
||||
|
||||
### Plasma 5's Breezy new look ###
|
||||
|
||||
Breeze is what KDE refers to as a modernized interface, with "reduced visual clutter throughout the workspace." Sure enough, the busy, somewhat cluttered feel that has long been a part of the default KDE look is gone.
|
||||
|
||||
|
||||
The KDE Plasma 5 desktop's Breeze theme is most complete in the Kickoff menu. Note the type to search message.
|
||||
|
||||
The entire interface has been flattened out, with bigger fonts, better contrast, and a sort of flat, "frosted" look that's somewhere between OS X Yosemite, Android L, and KDE 4.x. That's not to say KDE ripped off Apple or Google. They couldn't have, since Plasma 5 and the Breeze theme were well on their way before Apple revealed Yosemite or Google announced Android L.
|
||||
|
||||
Still, while it would be incorrect to say KDE has ripped anyone off, Breeze's visual design and overall aesthetic are very much a product of its time. In that sense it looks "modern," so long as you define modern to mean lots of strong type, few textures or outlines, lots of translucency, and monochrome iconography.
|
||||
|
||||
KDE's designers have put a lot of work into Breeze and it shows. This isn't just a new coat of paint. Breeze makes KDE more approachable out of the box with cleaned up menus, a less cluttered notification center, and a revamped Kickoff start menu.
|
||||
|
||||
|
||||
A cleaner, less nagging notification center.
|
||||
|
||||
How much Breeze matters depends on whether or not you'll ever even use it. KDE tends to attract users that like customizing their systems, which, presumably, includes customizing the theme. One thing to look forward to is what distros that heavily customize the default KDE theme—notably OpenSUSE—will do now that Breeze provides a somewhat higher starting bar.
|
||||
|
||||
Currently, most distros will likely not jump on Breeze, since it is very much a work in progress. And coincidently, Breeze is where you'll notice some of the first signs of incompleteness in Plasma 5. While the Kickoff menu has some nice new icons, much of the rest of the interface does not. And as of the latest updates available in the Kubuntu ppa, Breeze does not use its new Window Decorations. The Window Decorations are installed, but they aren't turned on by default. You can head to the System Settings app and turn them on for a more complete, though possibly buggier, Breeze experience.
|
||||
|
||||
|
||||
Top is the default Oxygen Window Decorations, bottom the new Breeze theme.
|
||||
|
||||
Not everything is ideal, and sometimes it's hard to tell what's a bug or incomplete feature and what is just poorly designed. For example, there's quite a bit of window and overlay translucency in Breeze, some of which looks nice. At other times, this gets in the way. Stacked windows and preview overlays bleed into what's behind them and become hard to read in the background. Pulling them to the foreground solves the problem, but it's hard to say what the value of the transparency is in this case.
|
||||
|
||||
|
||||
Transparency... why?
|
||||
|
||||
So yes, Breeze is still a work in progress, and not just in terms of features and design; things are still being worked out in terms of genuine bugs and glitches. We have encountered some unexpected behavior accordingly, particularly with regard to screen redraws. Those happen frequently and slow enough to notice. Windows disappear at times, and the menu bar occasionally only draws half of itself.
|
||||
|
||||
Plasma 5 has never crashed during our testing, nor has it lost any data. But be warned—little visual glitches abound. We would suggest waiting for things to stabilize and for the distro of your choice to integrate it before jumping in with both feet.
|
||||
|
||||
### Plasma menus go vertical ###
|
||||
|
||||
Breeze gives Plasma 5 a new look, but there are also a number of changes in behavior. For example, both the widget explorer and the alt-tab window switcher are now vertically oriented and located in the same place by default—the far left side of the screen.
|
||||
|
||||
|
||||
The default look for the alt-tab switcher menu.
|
||||
|
||||
While that consistency is probably good for KDE newcomers, who need to learn to expect that various stuff will appear to the left of the screen, it can be a little frustrating for long-time users anticipating something else. Some of these changes seem somewhat arbitrary.
|
||||
|
||||
|
||||
The widget explorer menu.
|
||||
|
||||
The KDE project claims the shift to vertical instead of horizontal lists, in things like the widget explorer and window switcher, "provide better usability." It stops short of saying how exactly. The release docs claim that moving the window switcher to the side of the screen "shifts the user's focus towards the applications and documents, clearing the stage for the task at hand." But if you only call up the window switcher when you're, ahem, switching windows, then it seems more likely that the user is between tasks rather than involved in one.
|
||||
|
||||
|
||||
KDE still loves offering options. Notice the dark gray bar to the right that's an artifact (glitch) from dragging the window.
|
||||
|
||||
This is KDE, though, not Unity; infinite customization is a feature, not a bug. A trip to the System Settings will get your old style window switcher back, and there are some 10 different visual possibilities for the window switcher in Plasma 5. If the default is not to your liking, customize away.
|
||||
|
||||
### So long Nepomuk, thanks for all the spinning fans ###
|
||||
|
||||
If you're a heavy user of KDE's sometimes awesome, sometimes not, search features, this may be the biggest news in Plasma 5. It's true, KDE has ditched Nepomuk in favor of a new search engine known as Baloo.
|
||||
|
||||
Nepomuk started life as an EU-funded metadata search project, with the lofty-sounding goal of creating a "Networked Environment for Personalized, Ontology-based Management of Unified Knowledge." By the time it trickled down to the KDE project, Nepomuk became a somewhat more mundane desktop search tool that alternated between brilliant and maddening.
|
||||
|
||||
|
||||
Searching for files in Plasma 5.
|
||||
|
||||
Baloo takes much of what made Nepomuk great—namely, full text file search and an uncanny ability to pick up on relationships between files, for example, knowing that particular document is related to a contact—and [improves it][4]. Actually use the search features in Plasma 5 and you'll notice two things right off the bat: it's faster and your fan doesn't go haywire every time something new is indexed.
|
||||
|
||||
Baloo significantly reduces the resource footprint of searching and, according to KDE, is more accurate. We can't vouch for the latter, since we never used search much in older versions of KDE (see fan spinning comments), but in terms of accuracy, simple file searches in Plasma 5 are on par with what you'll find in Ubuntu, OS X, and elsewhere. The success of more complex searches involving relationships or complex metadata will vary depending on how much you use the default KDE apps. For example, you need to use the Kontact Suite if you want to take advantage of Baloo-based searches involving relationships between contacts and files.
|
||||
|
||||
That will likely change as time goes on, though, because another big change from Nepomuk is the new, improved developer API. The API for searching means third-party apps can tie in Plasma 5's Semantic Search infrastructure and take advantage of the same tools the default apps use.
|
||||
|
||||
Curiously, for something that has seen as much work as Baloo has, the visibility and discoverability of the search feature has taken a step backward. Fire up Plasma 5's Kickoff menu—KDE's answer to the Windows Start menu—and search is nowhere to be found. If you look closely, you'll see a tiny little reminder to "type to search," which is a step up from the first release (which had no indication that you could search). Still, this isn't as discoverable as a dedicated search box.
|
||||
|
||||
### Kickoff and its new cousin, Kicker ###
|
||||
|
||||
KDE's answer to the Windows Start button has always been overkill in these eyes, packing too much in too little space, but with Breeze the menu has been cleaned up a bit and feels less visually overwhelming.
|
||||
|
||||
|
||||
The Kickoff menu in the default theme.
|
||||
|
||||
If it's still a bit too much for your needs, Plasma 5 offers a new, more traditional menu-based launcher called Kicker. Kicker does less—it's much closer to the Start menu in XP, a single, narrower pane that offers expanding menus where needed—and makes a lightweight alternative if all you want to do is launch applications and files. It also has a very obvious search box.
|
||||
|
||||
|
||||
The new Kicker menu option.
|
||||
|
||||
The other side of the menu bar has been revamped and cleaned up a bit as well. The most notable change is the notification app, which seems to kick up fewer notifications and does a better job of displaying them and quickly getting them out of the way.
|
||||
|
||||
### OpenGL, QtQuick, and HiDPI Screens ###
|
||||
|
||||
Plasma 5 finishes up KDE's migration to Qt 5 and QtQuick, the latter of which uses a hardware-accelerated OpenGL scenegraph to render graphics. Most of what's new with OpenGL pertains to offloading graphics to any available GPU. That means, provided you've got the hardware for it, Plasma 5 can take full advantage of today's powerful GPUs.
|
||||
|
||||
Indeed, on newish hardware (our test MacBook's NVIDIA GeForce GT graphics card, for example) Plasma 5 is snappy, considerably snappier than its predecessor. Perhaps even more impressive, take away whatever GPU advantage Plasma 5 might gain over KDE 4.x systems, and it still feels faster. That is, running on older hardware still isn't KDE's strong point, but the story is better than it used to be. Still, if you're looking to get some extra mileage out of older hardware, stick with Xfce, LXDE or something even simpler like Openbox.
|
||||
|
||||
Interestingly, the revamped Frameworks that make up Plasma 5's graphics stack also pave the way for KDE to switch to the Wayland display server protocol. KDE doesn't seem to be in a hurry to make the switch to Wayland though, noting only that full support will be available in "a future release."
|
||||
|
||||
This release also claims improved support for HDPI displays. But, as with the HDPI support in GNOME and Unity, the actual experience is a very mixed bag. Font rendering in particular is nowhere near as smooth as what OS X offers. Even installing and fiddling with Infinality has never produced satisfactory results for me. We're still not sure if the problem is in setup, and we're not in fact seeing the new HDPI features. Or, possibly the KDE project just has a very different definition of what constitutes HDPI support. Hopefully it's the former.
|
||||
|
||||
### What's missing ###
|
||||
|
||||
Earlier in this review, we said that the transition from KDE 4 to the Plasma 5 desktop would not be as bumpy as the move from KDE 3.x to 4.x. For the most part, that's true, but, for some people, there may be exceptions.
|
||||
|
||||
The KDE project says the focus for this release has been "concentrated on tools that make up the central workflows" and notes that "not all features from the Plasma 4.x series are available yet." That might ring a bell for those who made it through the KDE 3 to 4 transition.
|
||||
|
||||
In testing, we didn't run across any noticeable gaps in functionality or obvious missing features, save what was mentioned: the incomplete Breeze theme, some graphical glitches, and some questionable design choices. That said, have a look at the [list of known issues][5], in particular the note about performance.
|
||||
|
||||
And we suggest trying Plasma 5 first to make sure all your must-haves are there before you jump in with both feet.
|
||||
|
||||
### Conclusion ###
|
||||
|
||||
KDE's Plasma 5 release lacks the attention-grabbing, paradigm-shifting changes that keep Unity and GNOME in the spotlight. Instead, the KDE project has been focused on improving its core desktop experience. Plasma 5 is not perfect by any means, but, unlike Unity and GNOME, it's easy to change the things you don't like.
|
||||
|
||||
What's perhaps most heartening about this release is that KDE has managed to get a lot of the groundwork done for alternate interfaces without messing with their desktop interface much at all. The speed improvements are also good news. If you've tried KDE in the past and found it too "heavy," you might want to give Plasma 5 a fresh look.
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: http://arstechnica.com/information-technology/2014/08/kde-plasma-5-for-those-linux-users-undecided-on-the-kernels-future/
|
||||
|
||||
作者：Scott Gilbertson
|
||||
译者：[译者ID](https://github.com/译者ID)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创翻译，[Linux中国](http://linux.cn/) 荣誉推出
|
||||
|
||||
[1]:http://arstechnica.com/gadgets/2014/08/op-ed-tables-really-are-pcsbecause-theres-no-point-in-buying-new-ones/
|
||||
[2]:http://www.kde.org/announcements/plasma5.0/
|
||||
[3]:http://files.kde.org/snapshots/neon5-latest.iso.mirrorlist
|
||||
[4]:https://dot.kde.org/2014/02/24/kdes-next-generation-semantic-search
|
||||
[5]:https://community.kde.org/Plasma/5.0_Errata
|
||||
23
sources/talk/20140902 Happy Birthday Email.md
Normal file
23
sources/talk/20140902 Happy Birthday Email.md
Normal file
@ -0,0 +1,23 @@
|
||||
Happy Birthday Email
|
||||
================================================================================
|
||||
**An Indian American had the brain to invent electronic mail without which we cannot figure out a single day in this era.**
|
||||
|
||||
|
||||
|
||||
30 August, email turned 32. Now we wonder how this fast and quick method of message transfer came into existence. The credit goes to an Indian American, Shiva Ayyadurai. Shiva developed a full-scale software of the interoffice mail system and it was named email.
|
||||
|
||||
He was officially acknowledged as the inventor of the computer programme on 30 August, 1982, by the US government. Born to Tamil family in Bombay, Shiva was just 14 years old when he invented the email system. He was studying at Livingston High School in New Jersey and he began working on this system for the University of Medicine and Dentistry of New Jersey. A copyright was given to the email system as no other way was known to protect software inventions at that time.
|
||||
|
||||
Ayyadurai got the idea of the email system from the way mail was transported internally in offices. He tried to make a copy of ‘Pneumatic Tube System’ which was mostly used to send interoffice mails across offices. This system used a physical network of tubes which used to transport typed mails to secretaries. Each secretary used to have inbox, outbox, drafts, carbon copy paper, folders, address book, paper clips or attachments etc. All these were used to create and process incoming and outgoing mails.
|
||||
|
||||
Shiva also took a note of the common templates like “To”, “From”, “Subject”, “Date”, “Body”, “CC”, “BCC” and so on. All these templates were incorporated in the version of the electronic mail too. Mail was written FORTRAN programming language and Shiva discovered an electronic version of the same. Shiva received many accolades for his extraordinary work and also won a Westinghouse Science Talent Search Award for high school seniors in 1981. Now Smithsonian Institution National Museum of American History (SINMAH) has the official US copyright for “Email”. But there is a controversy that not Ayyadurai but some other people have invented email.
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: http://www.efytimes.com/e1/fullnews.asp?edid=147170
|
||||
|
||||
作者：Sanchari Banerjee
|
||||
译者：[译者ID](https://github.com/译者ID)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创翻译，[Linux中国](http://linux.cn/) 荣誉推出
|
||||
116
sources/talk/20140902 The awesomely epic guide to KDE.md
Normal file
116
sources/talk/20140902 The awesomely epic guide to KDE.md
Normal file
@ -0,0 +1,116 @@
|
||||
The awesomely epic guide to KDE
|
||||
================================================================================
|
||||
**Everything you ever wanted to know about KDE (but were too afraid of the number of possible solutions to ask).**
|
||||
|
||||
Desktops on Linux. They’re a concept completely alien to users of other operating systems because they never having to think about them. Desktops must feel like the abstract idea of time to the Amondawa tribe, a thought that doesn’t have any use until you’re in a different environment. But here it is – on Linux you don’t have to use the graphical environment lurking beneath your mouse cursor. You can change it for something completely different. If you don’t like windows, switch to xmonad. If you like full-screen apps, try Gnome. And if you’re after the most powerful and configurable point-and-click desktop, there’s KDE.
|
||||
|
||||
KDE is wonderful, as they all are in their own way. But in our opinion, KDE in particular suffers from poor default configuration and a rather allusive learning curve. This is doubly frustrating, firstly because it has been quietly growing more brilliant over the last couple of years, and secondly, because KDE should be the first choice for users unhappy with their old desktop – in particular, Windows 8 users pining for an interface that makes sense.
|
||||
|
||||
But fear not. We’re going to use a decade’s worth of KDE firefighting to bring you the definitive guide to making KDE look good and function slightly more like how you might expect it to. We’re not going to look at KDE’s applications, other than perhaps Dolphin; we’re instead going to look at the functionality in the desktop environment itself. And while our guinea pig distribution is going to be Mageia, this guide will be equally applicable to any recent KDE desktop running from almost any distribution, so don’t let the default Mageia background put you off.
|
||||
|
||||
### Fonts ###
|
||||
|
||||
A great first target for getting your system looking good is its selection of fonts. It used to be the case that many of us would routinely copy fonts across from a Windows installation, getting the professional Ariel and Helvetica font rendering that was missing from Linux at the time. But thanks to generic quality fonts such as DejaVu and Nimbus Sans/Roman, this isn’t a problem any more. But it’s still worth finding a font you prefer, as there are now so many great alternatives to choose between.
|
||||
|
||||
The best source of free fonts we’ve found is [www.fontsquirrel.com][1] – it hosts the Roboto, Roboto Slab (Hello!) and Roboto Condensed (Hello!) typefaces used throughout our magazine, and also on the Nexus 5 smartphone (Roboto was developed for use in the Ice Cream Sandwich version of the Android mobile operating system).
|
||||
|
||||
TrueType fonts, with their **.ttf** file extensions, are incredibly easy to install from KDE. Download the zip file, right-click and select something from the Extract menu. Now all you need to do is drag a selection across the TrueType fonts you want to install and select ‘Install’ from the right-click Actions menu. KDE will take care of the rest.
|
||||
|
||||
Another brilliant thing about KDE is that you can change all the fonts at once. Open the System Settings panel and click on Application Appearances, followed by the fonts tab, and click on Adjust All Fonts. Now just select a font from the requester. Most KDE applications will update with your choice immediately, while other applications, such as Firefox, will require a restart. Either way, it’s a quick and effective way of experimenting with your desktop’s usability and appearance. We’d recommend either Open Sans or the thinner Aller fonts.
|
||||
|
||||
|
||||
Most distributions don’t include decent fonts. But KDE enables you to quickly install new ones and apply them to your desktop.
|
||||
|
||||
### Eye candy ###
|
||||
|
||||
One of KDE’s most secret features is that backgrounds can be dynamic. We don’t find much use for this when it comes to the desktops that tells us the weather outside the window, but we do like backgrounds that dynamically grab images from the internet. With most distributions you’ll need to install something for this to work. Just search for **plasma-wallpaper** in your distribution’s package manager. Our favourite is **plasma-wallpaper-potd**, as this installs easy access to update-able wallpaper images from a variety of sources.
|
||||
|
||||
Changing a desktop background is easy with KDE, but it’s not intuitive. Mageia, for example, defaults to using ‘Folder’ view, as this is closer to the traditional desktop where files from the Desktop folder in your home directory are displayed on the background, and the whole desktop works like a file manager. Right-click and select ‘Folder Settings’ if this is the view you’re using. Alternatively, KDE defaults to ‘Desktop’, where the background is clear apart from any widgets you add yourself, and files and folders are considered links to the sources. The menu item in this mode is labelled Desktop Settings. The View Configuration panel that changes the background is the same, however, and you need to make your changes in the Wallpaper drop-down menu. We’d recommend Picture Of The Day as the wallpaper, and the Astronomy Picture Of The Day as the image source.
|
||||
|
||||
Another default option we think is crazy is the blue glow that surrounds the active window. While every other desktop uses a slightly deeper drop-shadow, KDE’s active window looks like it’s bathed in radioactive light. The solution to this lies in the default theme, and this can be changed by going to KDE’s System Settings control panel and selecting Workspace Appearance. On the first page, which is labelled Window Decorations, you’ll find that Oxygen is nearly always selected, and it’s this theme that contains the option to change the blue glow. Just click on the Configure Decoration button, flip to the Shadows tab and disable Active Window Glow’. Alternatively, if you’d like active windows to have a more pronounced shadow, change the inner and outer colours to black.
|
||||
|
||||
You may have seen the option to download wallpapers, for example, from within a KDE window, and you can see this now by clicking on the Get New Decorations button. Themes are subjective, but our favourite combination is currently the Chrome window decoration (it looks identical to Google’s default theme for its browser) with the Aya desktop theme. The term ‘desktop theme’ is a bit of a misnomer, as it doesn’t encapsulate every setting as you might expect. Instead it controls how generic desktop elements are rendered. The most visible of these elements is the launch panel, and changing the desktop theme will usually have a dramatic effect on its appearance, but you’ll also notice a difference in the widgets system.
|
||||
|
||||
The final graphical flourish we’d suggest is to change the icon set that KDE uses. There’s nothing wrong with the default Oxygen set, but there are better options. Unfortunately, this is where the ‘Get New Themes’ download option often fails, probably because icon packages are large and can overwhelm the personal storage space often reserved for projects like these. We’d suggest going to [kde-look.org][2] and browsing its icon collections. Open up the Icons panel from KDE’s System Settings, click on the Icons tab followed by Install Theme File and point the requester at the location of the archive you just downloaded. KDE will take it from there and add the icon set to the list in the panel. Try Kotenza for a flat theme, or keep an eye on Nitrux development.
|
||||
|
||||
|
||||
Remove the blue glow and change a few of the display options, and KDE starts to look pretty good in our opinion.
|
||||
|
||||
### The panel ###
|
||||
|
||||
Our next target is going to be the panel at the bottom of the screen. This has become a little dated, especially if you’re using KDE on a large or high-resolution display, so our first suggestion is to re-scale and centre it for your screen. The key to moving screen components in KDE is making sure they’re unlocked, and this accomplished by right-clicking on the ‘plasma’ cashew in the top-right of the display where the current activity is listed. Only when widgets are unlocked can you re-size the panel, and even add new applications from the launch menu.
|
||||
|
||||
With widgets unlocked, click on the cashew on the side of the panel followed by More Settings and select Centre for panel alignment. With this enabled you can re-size the panel using the sliders on either side and the panel itself will always stay in the middle of your screen. Just pretend you’re working on indentation on a word processor and you’ll get the idea. You can also change its height when the sliders are visible by dragging the central height widget, and to the left of this, you can drag the panel to a different edge on your screen. The top edge works quite well, but many of KDE’s applets don’t work well when stacked vertically on the left or right edges of the display.
|
||||
|
||||
There are two different kinds of task manager applets that come with KDE. The default displays each running application as a title bar in the panel, but this takes up quite a bit of space. The alternative task manager displays only the icon of the application, which we think is much more useful. Mageia defaults to the icon version, but most others – and KDE itself – prefer the title bar applet. To change this, click on the cashew again and hover over the old applet so that the ‘X’ appears, then click on this ‘X’ to remove the applet from the panel. Now click on Add Widgets, find the two task managers and drag the icon version on to your panel. You can re-arrange any other applets in this mode by dragging them to the left and right.
|
||||
|
||||
By default, the Icon-Only task manager will only display icons for tasks running on the current desktop, which we think is counterintuitive, as it’s more convenient to see all of the applications you may have running and to quickly switch between whatever desktops on which they may be running with a simple click. To change this behaviour, right-click on the applet and select the Settings menu option and the Behaviour tab in the next window. Deselect ‘Only Show Tasks From The Current Desktop’, and perhaps ‘Only Show Tasks From The Current Activity’ if you use KDE’s activities.
|
||||
|
||||
Another alteration we like to make is to reconfigure the virtual desktops applet from showing four desktops as a 2×2, which doesn’t look too good on a small panel, to 4×1. This can be done by right-clicking on the applet, selecting Pager Settings and then clicking on the Virtual Desktops tabs and changing the number of rows to ‘1’.
|
||||
|
||||
Finally, there’s the launch menu. Mageia has switched this from the new style of application launcher to the old style originally seen in Microsoft Windows. We prefer the former because of its search field, but the two can be switched by right-clicking the icon and selecting the Switch To… menu option.
|
||||
|
||||
If you find the hover-select action of this mode annoying, where moving the mouse over one of the categories automatically selects it, you can disable it by right-clicking on the launcher, selecting Launcher Settings from the menu and disabling ‘Switch Tabs On Hover’ from the General settings page. It’s worth reiterating that many of these menu options are only available when widgets are unlocked, so don’t despair if you don’t see the correct menu entry at first.
|
||||
|
||||
> ### Activities ###
|
||||
>
|
||||
> No article on KDE would be complete without some discussion of what KDE calls Activities. In many ways, Activities are a solution waiting for a problem. They’re meta-virtual desktops that allow you to group desktop configuration and applications together. You may have an activity for photo editing, for example, or one for working and another for the internet. If you’ve got a touchscreen laptop, activities could be used to switch between an Android-style app launcher (the Search and Launch mode from the Desktop Settings panel), and the regular desktop mode. We use a single activity as a default for screenshots, for instance, while another activity switches everything to the file manager desktop mode. But the truth is that you have to understand what they are before you can find a way of using them.
|
||||
>
|
||||
> Some installations of KDE will include the Activity applet in the toolbar. Its red, blue and green dots can be clicked on to open the activity manager, or you can click on the Plasma cashew in the top-right and select Activities. This will open the bar at the bottom of the screen, which lists activities installed and primed on your system. Clicking on any will switch between them; as will pressing the meta key (usually the Windows key) and Tab.
|
||||
>
|
||||
> We’d suggest that finding a fast way to switch between activities, such as with a keyboard shortcut or with the Activity Bar widget is the key to using them more. With the Activity Manager open, clicking on Create Activity lets you either clone the current desktop, add a blank desktop or create a new activity from a list of templates. Clone works well if you want to add some default applications to the desktop for your current setup. To remove an activity, switch to another one and press the Stop and Delete buttons from the Activity Manager.
|
||||
|
||||
### Upgraded launch menu ###
|
||||
|
||||
You may want to look into replacing the default launch menu entirely. If you open the Add Widgets view, for instance, and search for menus, you’ll see several results. Our current favourite is called Application Launcher (QML). It provides the same kind of functionality as the default menu, but has a cleaner interface after you’ve enlarged the initial window. But if we’re being honest, we don’t use the launcher that much. We prefer to do most launching through KRunner, which is the seemingly simple requester that appears when you hold Alt+F2.
|
||||
|
||||
KRunner is better than the default launcher, because you can type this shortcut from anywhere, regardless of which applications are running or where your mouse is located. When you start to type the name of the application you want to run into KRunner, you’ll see the results filtered in real time beneath the entry field – press Enter to launch the top choice.
|
||||
|
||||
KRunner is capable of so much more. You can type in calculations like **=sin(90)**, for example, and see the result in real time. You can search Google with **gg**: or Wikipedia with **wp**: followed by the search terms, and add many other operations through installable modules. To make best use of this awesome KDE feature, make sure you’ve got the **plasma-addons** package installed, and search for **runner** on your distribution’s package manager. When you next launch KRunner and click on the tool icon to the left of the search bar, you’ll see a wide variety of plugins that can do all kinds of things with the text you type in. In classic KDE style, many don’t include instructions on how to use them, so here’s our breakdown of the most useful things you can do with KRunner:
|
||||
|
||||
|
||||
|
||||
### File management ###
|
||||
|
||||
File management may not be the most exciting subject in Linux, but it is one we all seem to spend a lot of time doing, whether that’s moving a download into a better folder, or copying photos from a camera. The old file manager, Konqueror, was one of the best reasons for using KDE in the first place, and while Konqueror has been superseded by Dolphin in KDE 4.x, it’s still knocking around – even if it is labelled a web browser.
|
||||
|
||||
If you open Konqueror and enter the URL as **file:/**, it turns back into that file manager of old, with many of its best features intact. You can click on the lower status bar, for example, and split the view vertically or horizontally, into other views. You can fill the view with proportionally sized blocks by selecting Preview File Size View from the right-click menu, and preview many other file types without ever leaving Konqueror.
|
||||
|
||||
Mageia uses a double-click for most options, whereas we prefer a single click. This can be changed from the System-Settings panel by opening Input Devices, clicking on Mouse and enabling ‘Single-click To Open Files And Folders’. If you’ve become used to Apple’s reverse scroll, you’ll also find an option here to reverse the scroll direction on Linux.
|
||||
|
||||
Konqueror is a great application, but it hasn’t been a focus of KDE development for a considerable period of time. Dolphin has replaced it, and while this is a much simplified file manager, it does inherit some of Konqueror’s best features. You can still split the view, for instance, albeit one only once, and only horizontally, from the toolbar. You can also view lots of metadata. Select the Details View and right-click on the column headings for the files, and you can add columns that list the word counts in text files, or an image’s size and orientation, or the artist, title and duration of an audio file, all from within the contents of the data. This is KDE’s semantic desktop in action, and it’s been growing in functionality for the last couple of years. Apple’s OS X, for example, has only just started pushing its ability to tag files and applications – we’ve been able to do this from KDE for a long time. We don’t know any other desktop that comes close to providing that level of control.
|
||||
|
||||
### Window management ###
|
||||
|
||||
KDE has a comprehensive set of windowing functions as well as graphical effects. They’re all part of the window manager, KWin, rather than the desktop, which is what we’ve been dealing with so far. It’s the window manager’s job to handle the positioning, moving and rendering of your windows, which is why they can be replaced without switching the whole desktop. You might want to try KWin on the RazorQt desktop, for example, to get the best of both the minimal environment RazorQt offers and the power of KDE’s window manager.
|
||||
|
||||
The easiest way to get to KWin’s configuration settings is to right-click on the title bar of any window (this is usually the most visible element of any window manager), and select Window Manager Settings from the More Actions menu.
|
||||
|
||||
The Task Switcher is the tool that appears when you press Alt+Tab, and continually pressing those two keys will switch between all running applications on the current desktop. You can also use cursor keys to move left and right through the list. These settings are mostly sensibly configured, but you may want to include All Other Desktops in the Filter Windows By section, as that will allow you to quickly switch to applications running on other desktops. We also like the Cover Switch visualisation rather than the Thumbnails view, and you can even configure the perceived distance of the windows by clicking on the toolbar icon.
|
||||
|
||||
The next page on the window manager control module handles what happens at the edges of your screen. At the very least, we prefer to enable Switch Desktop On Edge by selecting Only When Moving Windows from the drop-down list. This means that when you drag a window to one edge, the virtual desktop will switch beneath, effectively dragging the window on to a new virtual desktop.
|
||||
|
||||
The great thing about enabling this only for dragged windows is that it doesn’t interfere with KDE’s fantastic window snapping feature. When you drag a window close to the left or right edge, for instance, KDE displays a ghosted window where your window will snap to if you release the mouse. This is a great way of turning KDE into a tiling window manager, where you can easily have two windows split down the middle of the screen area. Moving a window into any of the corners will also give you the ability to neatly arrange your windows to occupy a quarter of the screen, which is ideal for large displays.
|
||||
|
||||
We also enable a mode similar to Mission Control on OS X when the cursor is in the region of the top-left corner of the screen. On the screen edge layout, click on the dot in the top-right of the screen (or any other point you’d prefer) and select Desktop Grid from the drop-down menu that appears. Now when you move to the top-right of your display, you’ll get an overview of all your virtual desktops, any of which can be chosen with a click.
|
||||
|
||||
Two pages down in the configuration module, there’s a page called Focus. This is an old idea where you can change whether a window becomes active when you click on it, or when you roll your mouse cursor over it. KDE adds another twist to this by providing a slider that progresses from click to a strict hover policy, where the window under the cursor always becomes active. We prefer to use one of the middle options – Focus Follows Mouse – as this chooses the most obvious window to activate for us without making too many mistakes, and it means we seldom click to focus. We also reduce the focus delay to 200ms, but this will depend on how you feel about the feature after using it for a while.
|
||||
|
||||
KDE has so many features, many of which only come to light when you start to use the desktop. It really is a case of developers often adding things and then telling no one. But we feel KDE is worth the effort, and unlikely some other desktops, is unlikely to change too much in the transition from 4.x to 5. That means the time you spend learning how to use KDE now is an investment. Dive in!.
|
||||
|
||||
|
||||
KDE visual effects (click for larger)
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: http://www.linuxvoice.com/desktops/
|
||||
|
||||
作者：[Ben Everard][a]
|
||||
译者：[译者ID](https://github.com/译者ID)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创翻译，[Linux中国](http://linux.cn/) 荣誉推出
|
||||
|
||||
[a]:http://www.linuxvoice.com/author/ben_everard/
|
||||
[1]:http://www.fontsquirrel.com/
|
||||
[2]:http://kde-look.org/
|
||||
92
sources/talk/20140904 Making MySQL Better at GitHub.md
Normal file
92
sources/talk/20140904 Making MySQL Better at GitHub.md
Normal file
@ -0,0 +1,92 @@
|
||||
Making MySQL Better at GitHub
|
||||
================================================================================
|
||||
> At GitHub we say, "it's not fully shipped until it's fast." We've talked before about some of the ways we keep our [frontend experience speedy][1], but that's only part of the story. Our MySQL database infrastructure dramatically affects the performance of GitHub.com. Here's a look at how our infrastructure team seamlessly conducted a major MySQL improvement last August and made GitHub even faster.
|
||||
|
||||
### The mission ###
|
||||
|
||||
Last year we moved the bulk of GitHub.com's infrastructure into a new datacenter with world-class hardware and networking. Since MySQL forms the foundation of our backend systems, we expected database performance to benefit tremendously from an improved setup. But creating a brand-new cluster with brand-new hardware in a new datacenter is no small task, so we had to plan and test carefully to ensure a smooth transition.
|
||||
|
||||
### Preparation ###
|
||||
|
||||
A major infrastructure change like this requires measurement and metrics gathering every step of the way. After installing base operating systems on our new machines, it was time to test out our new setup with various configurations. To get a realistic test workload, we used tcpdump to extract SELECT queries from the old cluster that was serving production and replayed them onto the new cluster.
|
||||
|
||||
MySQL tuning is very workload specific, and well-known configuration settings like innodb_buffer_pool_size often make the most difference in MySQL's performance. But on a major change like this, we wanted to make sure we covered everything, so we took a look at settings like innodb_thread_concurrency, innodb_io_capacity, and innodb_buffer_pool_instances, among others.
|
||||
|
||||
We were careful to only make one test configuration change at a time, and to run tests for at least 12 hours. We looked for query response time changes, stalls in queries per second, and signs of reduced concurrency. We observed the output of SHOW ENGINE INNODB STATUS, particularly the SEMAPHORES section, which provides information on work load contention.
|
||||
|
||||
Once we were relatively comfortable with configuration settings, we started migrating one of our largest tables onto an isolated cluster. This served as an early test of the process, gave us more space in the buffer pools of our core cluster and provided greater flexibility for failover and storage. This initial migration introduced an interesting application challenge, as we had to make sure we could maintain multiple connections and direct queries to the correct cluster.
|
||||
|
||||
In addition to all our raw hardware improvements, we also made process and topology improvements: we added delayed replicas, faster and more frequent backups, and more read replica capacity. These were all built out and ready for go-live day.
|
||||
|
||||
### Making a list; checking it twice ###
|
||||
|
||||
With millions of people using GitHub.com on a daily basis, we did not want to take any chances with the actual switchover. We came up with a thorough [checklist][2] before the transition:
|
||||
|
||||
|
||||
|
||||
We also planned a maintenance window and [announced it on our blog][3] to give our users plenty of notice.
|
||||
|
||||
### Migration day ###
|
||||
|
||||
At 5am Pacific Time on a Saturday, the migration team assembled online in chat and the process began:
|
||||
|
||||
|
||||
|
||||
We put the site in maintenance mode, made an announcement on Twitter, and set out to work through the list above:
|
||||
|
||||
|
||||
|
||||
**13 minutes** later, we were able to confirm operations of the new cluster:
|
||||
|
||||
|
||||
|
||||
Then we flipped GitHub.com out of maintenance mode, and let the world know that we were in the clear.
|
||||
|
||||
|
||||
|
||||
Lots of up front testing and preparation meant that we kept the work we needed on go-live day to a minimum.
|
||||
|
||||
### Measuring the final results ###
|
||||
|
||||
In the weeks following the migration, we closely monitored performance and response times on GitHub.com. We found that our cluster migration cut the average GitHub.com page load time by half and the 99th percentile by *two-thirds*:
|
||||
|
||||
|
||||
|
||||
### What we learned ###
|
||||
|
||||
#### Functional partitioning ####
|
||||
|
||||
During this process we decided that moving larger tables that mostly store historic data to separate cluster was a good way to free up disk and buffer pool space. This allowed us to leave more resources for our "hot" data, splitting some connection logic to enable the application to query multiple clusters. This proved to be a big win for us and we are working to reuse this pattern.
|
||||
|
||||
#### Always be testing ####
|
||||
|
||||
You can never do too much acceptance and regression testing for your application. Replicating data from the old cluster to the new cluster while running acceptance tests and replaying queries were invaluable for tracing out issues and preventing surprises during the migration.
|
||||
|
||||
#### The power of collaboration ####
|
||||
|
||||
Large changes to infrastructure like this mean a lot of people need to be involved, so pull requests functioned as our primary point of coordination as a team. We had people all over the world jumping in to help.
|
||||
|
||||
Deploy day team map:
|
||||
|
||||
<iframe width="620" height="420" frameborder="0" src="https://render.githubusercontent.com/view/geojson?url=https://gist.githubusercontent.com/anonymous/5fa29a7ccbd0101630da/raw/map.geojson"></iframe>
|
||||
|
||||
This created a workflow where we could open a pull request to try out changes, get real-time feedback, and see commits that fixed regressions or errors -- all without phone calls or face-to-face meetings. When everything has a URL that can provide context, it's easy to involve a diverse range of people and make it simple for them give feedback.
|
||||
|
||||
### One year later.. ###
|
||||
|
||||
A full year later, we are happy to call this migration a success — MySQL performance and reliability continue to meet our expectations. And as an added bonus, the new cluster enabled us to make further improvements towards greater availability and query response times. I'll be writing more about those improvements here soon.
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://github.com/blog/1880-making-mysql-better-at-github
|
||||
|
||||
作者：[samlambert][a]
|
||||
译者：[译者ID](https://github.com/译者ID)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创翻译，[Linux中国](http://linux.cn/) 荣誉推出
|
||||
|
||||
[a]:https://github.com/samlambert
|
||||
[1]:https://github.com/blog/1756-optimizing-large-selector-sets
|
||||
[2]:https://help.github.com/articles/writing-on-github#task-lists
|
||||
[3]:https://github.com/blog/1603-site-maintenance-august-31st-2013
|
||||
378
sources/talk/20140904 The Masked Avengers.md
Normal file
378
sources/talk/20140904 The Masked Avengers.md
Normal file
@ -0,0 +1,378 @@
|
||||
[Translating by SteveArcher]
|
||||
The Masked Avengers
|
||||
================================================================================
|
||||
> How Anonymous incited online vigilantism from Tunisia to Ferguson.
|
||||
|
||||
|
||||
|
||||
Anyone can join Anonymous simply by claiming affiliation. An anthropologist says that participants “remain subordinate to a focus on the epic win—and, especially, the lulz.”
|
||||
|
||||
Paper Sculpture by Jeff Nishinaka / Photograph by Scott Dunbar
|
||||
|
||||
----------
|
||||
|
||||
In the mid-nineteen-seventies, when Christopher Doyon was a child in rural Maine, he spent hours chatting with strangers on CB radio. His handle was Big Red, for his hair. Transmitters lined the walls of his bedroom, and he persuaded his father to attach two directional antennas to the roof of their house. CB radio was associated primarily with truck drivers, but Doyon and others used it to form the sort of virtual community that later appeared on the Internet, with self-selected nicknames, inside jokes, and an earnest desire to effect change.
|
||||
|
||||
Doyon’s mother died when he was a child, and he and his younger sister were reared by their father, who they both say was physically abusive. Doyon found solace, and a sense of purpose, in the CB-radio community. He and his friends took turns monitoring the local emergency channel. One friend’s father bought a bubble light and affixed it to the roof of his car; when the boys heard a distress call from a stranded motorist, he’d drive them to the side of the highway. There wasn’t much they could do beyond offering to call 911, but the adventure made them feel heroic.
|
||||
|
||||
Small and wiry, with a thick New England accent, Doyon was fascinated by “Star Trek” and Isaac Asimov novels. When he saw an ad in Popular Mechanics for a build-your-own personal-computer kit, he asked his grandmother to buy it for him, and he spent months figuring out how to put it together and hook it up to the Internet. Compared with the sparsely populated CB airwaves, online chat rooms were a revelation. “I just click a button, hit this guy’s name, and I’m talking to him,” Doyon recalled recently. “It was just breathtaking.”
|
||||
|
||||
At the age of fourteen, he ran away from home, and two years later he moved to Cambridge, Massachusetts, a hub of the emerging computer counterculture. The Tech Model Railroad Club, which had been founded thirty-four years earlier by train hobbyists at M.I.T., had evolved into “hackers”—the first group to popularize the term. Richard Stallman, a computer scientist who worked in M.I.T.’s Artificial Intelligence Laboratory at the time, says that these early hackers were more likely to pass around copies of “Gödel, Escher, Bach” than to incite technological warfare. “We didn’t have tenets,” Stallman said. “It wasn’t a movement. It was just a thing that people did to impress each other.” Some of their “hacks” were fun (coding video games); others were functional (improving computer-processing speeds); and some were pranks that took place in the real world (placing mock street signs near campus). Michael Patton, who helped run the T.M.R.C. in the seventies, told me that the original hackers had unwritten rules and that the first one was “Do no damage.”
|
||||
|
||||
In Cambridge, Doyon supported himself through odd jobs and panhandling, preferring the freedom of sleeping on park benches to the monotony of a regular job. In 1985, he and a half-dozen other activists formed an electronic “militia.” Echoing the Animal Liberation Front, they called themselves the Peoples Liberation Front. They adopted aliases: the founder, a towering middle-aged man who claimed to be a military veteran, called himself Commander Adama; Doyon went by Commander X. Inspired by the Merry Pranksters, they sold LSD at Grateful Dead shows and used some of the cash to outfit an old school bus with bullhorns, cameras, and battery chargers. They also rented a basement apartment in Cambridge, where Doyon occasionally slept.
|
||||
|
||||
Doyon was drawn to computers, but he was not an expert coder. In a series of conversations over the past year, he told me that he saw himself as an activist, in the radical tradition of Abbie Hoffman and Eldridge Cleaver; technology was merely his medium of dissent. In the eighties, students at Harvard and M.I.T. held rallies urging their schools to divest from South Africa. To help the protesters communicate over a secure channel, the P.L.F. built radio kits: mobile FM transmitters, retractable antennas, and microphones, all stuffed inside backpacks. Willard Johnson, an activist and a political scientist at M.I.T., said that hackers were not a transformative presence at rallies. “Most of our work was still done using a bullhorn,” he said.
|
||||
|
||||
In 1992, at a Grateful Dead concert in Indiana, Doyon sold three hundred hits of acid to an undercover narcotics agent. He was sentenced to twelve years in Pendleton Correctional Facility, of which he served five. While there, he developed an interest in religion and philosophy and took classes from Ball State University.
|
||||
|
||||
Netscape Navigator, the first commercial Web browser, was released in 1994, while Doyon was incarcerated. When he returned to Cambridge, the P.L.F. was still active, and their tools had a much wider reach. The change, Doyon recalls, “was gigantic—it was the difference between sending up smoke signals and being able to telegraph someone.” Hackers defaced an Indian military Web site with the words “Save Kashmir.” In Serbia, hackers took down an Albanian site. Stefan Wray, an early online activist, defended such tactics at an “anti-Columbus Day” rally in New York. “We see this as a form of electronic civil disobedience,” he told the crowd.
|
||||
|
||||
In 1999, the Recording Industry Association of America sued Napster, the file-sharing service, for copyright infringement. As a result, Napster was shut down in 2001. Doyon and other hackers disabled the R.I.A.A. site for a weekend, using a Distributed Denial of Service, or DDoS, attack, which floods a site with so much data that it slows down or crashes. Doyon defended his actions, employing the heightened rhetoric of other “hacktivists.” “We quickly came to understand that the battle to defend Napster was symbolic of the battle to preserve a free internet,” he later wrote.
|
||||
|
||||
One day in 2008, Doyon and Commander Adama met at the P.L.F.’s basement apartment in Cambridge. Adama showed Doyon the Web site of the Epilepsy Foundation, on which a link, instead of leading to a discussion forum, triggered a series of flashing colored lights. Some epileptics are sensitive to strobes; out of sheer malice, someone was trying to induce seizures in innocent people. There had been at least one victim already.
|
||||
|
||||
Doyon was incensed. He asked Adama who would do such a thing.
|
||||
|
||||
“Ever hear of a group called Anonymous?” Adama said.
|
||||
|
||||
----------
|
||||
|
||||
In 2003, Christopher Poole, a fifteen-year-old insomniac from New York City, launched 4chan, a discussion board where fans of anime could post photographs and snarky comments. The focus quickly widened to include many of the Internet’s earliest memes: LOLcats, Chocolate Rain, RickRolls. Users who did not enter a screen name were given the default handle Anonymous.
|
||||
|
||||
|
||||
|
||||
“I need to talk about my inner life.”
|
||||
|
||||
Poole hoped that anonymity would keep things irreverent. “We have no intention of partaking in intelligent discussions concerning foreign affairs,” he wrote on the site. One of the highest values within the 4chan community was the pursuit of “lulz,” a term derived from the acronym LOL. Lulz were often achieved by sharing puerile jokes or images, many of them pornographic or scatological. The most shocking of these were posted on a part of the site labelled /b/, whose users called themselves /b/tards. Doyon was aware of 4chan, but considered its users “a bunch of stupid little pranksters.” Around 2004, some people on /b/ started referring to “Anonymous” as an independent entity.
|
||||
|
||||
It was a new kind of hacker collective. “It’s not a group,” Mikko Hypponen, a leading computer-security researcher, told me—rather, it could be thought of as a shape-shifting subculture. Barrett Brown, a Texas journalist and a well-known champion of Anonymous, has described it as “a series of relationships.” There was no membership fee or initiation. Anyone who wanted to be a part of Anonymous—an Anon—could simply claim allegiance.
|
||||
|
||||
Despite 4chan’s focus on trivial topics, many Anons considered themselves crusaders for justice. They launched vigilante campaigns that were purposeful, if sometimes misguided. More than once, they posed as underage girls in order to entrap pedophiles, whose personal information they sent to the police. Other Anons were apolitical and sowed chaos for the lulz. One of them posted images on /b/ of what looked like pipe bombs; another threatened to blow up several football stadiums and was arrested by the F.B.I. In 2007, a local news affiliate in Los Angeles called Anonymous “an Internet hate machine.”
|
||||
|
||||
In January, 2008, Gawker Media posted a video in which Tom Cruise enthusiastically touted the benefits of Scientology. The video was copyright-protected, and the Church of Scientology sent a cease-and-desist letter to Gawker, asking that the video be removed. Anonymous viewed the church’s demands as attempts at censorship. “I think it’s time for /b/ to do something big,” someone posted on 4chan. “I’m talking about ‘hacking’ or ‘taking down’ the official Scientology Web site.” An Anon used YouTube to issue a “press release,” which included stock footage of storm clouds and a computerized voice-over. “We shall proceed to expel you from the Internet and systematically dismantle the Church of Scientology in its present form,” the voice said. “You have nowhere to hide.” Within a few weeks, the YouTube video had been viewed more than two million times.
|
||||
|
||||
Anonymous had outgrown 4chan. The hackers met in dedicated Internet Relay Chat channels, or I.R.C.s, to coördinate tactics. Using DDoS attacks, they caused the main Scientology Web site to crash intermittently for several days. Anons created a “Google bomb,” so that a search for “dangerous cult” would yield the main Scientology site at the top of the results page. Others sent hundreds of pizzas to Scientology centers in Europe, and overwhelmed the church’s Los Angeles headquarters with all-black faxes, draining the machines of ink. The Church of Scientology, an organization that reportedly has more than a billion dollars in assets, could withstand the depletion of its ink cartridges. But its leaders, who had also received death threats, contacted the F.B.I. to request an investigation into Anonymous.
|
||||
|
||||
On March 15, 2008, several thousand Anons marched past Scientology churches in more than a hundred cities, from London to Sydney. In keeping with the theme of anonymity, the organizers decided that all the protesters should wear versions of the same mask. After considering Batman, they settled on the Guy Fawkes mask worn in “V for Vendetta,” a dystopian movie from 2005. “It was available in every major city, in large quantities, for cheap,” Gregg Housh, one of the organizers of the protests and a well-known Anon, told me. The mask was a caricature of a man with rosy cheeks, a handlebar mustache, and a wide grin.
|
||||
|
||||
Anonymous did not “dismantle” the Church of Scientology. Still, the Tom Cruise video remained online. Anonymous had proved its tenacity. The collective adopted a bombastic slogan: “We are Legion. We do not forgive. We do not forget. Expect us.”
|
||||
|
||||
----------
|
||||
|
||||
In 2010, Doyon moved to Santa Cruz, California, to join a local movement called Peace Camp. Using wood that he stole from a lumberyard, he built a shack in the mountains. He borrowed WiFi from a nearby mansion, drew power from salvaged solar panels, and harvested marijuana, which he sold for cash.
|
||||
|
||||
At the time, the Peace Camp activists were sleeping on city property as a protest against a Santa Cruz anti-homelessness law that they considered extreme. Doyon appeared at Peace Camp meetings and offered to promote their cause online. He had an unkempt red beard and wore a floppy beige hat and quasi-military fatigues. Some of the activists called him Curbhugger Chris.
|
||||
|
||||
Kelley Landaker, a member of Peace Camp, spoke with Doyon several times about hacking. Doyon sometimes bragged about his technical aptitude, but Landaker, an expert programmer, was unimpressed. “He was more of a spokesman than a hands-on-the-keyboard type of person,” Landaker told me. But the movement needed a passionate leader more than it needed a coder. “He was very enthusiastic and very outspoken,” Robert Norse, also a member of Peace Camp, told me. “He created more media attention for the issue than anyone I’ve seen, and I’ve been doing this for twenty years.”
|
||||
|
||||
Commander Adama, Doyon’s superior in the P.L.F., who still lived in Cambridge and communicated with him via e-mail, had ordered Doyon to monitor Anonymous. Doyon’s brief was to observe their methods and to recruit members to the P.L.F. Recalling his revulsion at the Epilepsy Foundation hack, Doyon initially balked. Adama argued that the malicious hackers were a minority within Anonymous, and that the collective might inspire powerful new forms of activism. Doyon was skeptical. “The biggest movement in the world is going to come from 4chan?” he said. But, out of loyalty to the P.L.F., he obeyed Adama.
|
||||
|
||||
Doyon spent much of his time at the Santa Cruz Coffee Roasting Company, a café downtown, hunched over an Acer laptop. The main Anonymous I.R.C. did not require a password. Doyon logged in using the name PLF and followed along. Over time, he discovered back channels where smaller, more dedicated groups of Anons had dozens of overlapping conversations. To participate, you had to know the names of the back channels, which could be changed to deflect intruders. It was not a highly secure system, but it was adaptable. “These simultaneous cabals keep centralization from happening,” Gabriella Coleman, an anthropologist at McGill University, told me.
|
||||
|
||||
Some Anons proposed an action called Operation Payback. As the journalist Parmy Olson wrote in a 2012 book, “We Are Anonymous,” Operation Payback started as another campaign in support of file-sharing sites like the Pirate Bay, a successor to Napster, but the focus soon broadened to include political speech. In late 2010, at the behest of the State Department, several companies, including MasterCard, Visa, and PayPal, stopped facilitating donations to WikiLeaks, the vigilante organization that had released hundreds of thousands of diplomatic cables. In an online video, Anonymous called for revenge, promising to lash out at the companies that had impeded WikiLeaks. Doyon, attracted by the anti-corporate spirit of the project, decided to participate.
|
||||
|
||||
|
||||
|
||||
During Operation Payback, in early December, Anonymous directed new recruits, or noobs, to a flyer headed “How to Join the Fucking Hive,” in which participants were instructed to “FIX YOUR GODDAMN INTERNET. THIS IS VERY FUCKING IMPORTANT.” They were also asked to download Low Orbit Ion Cannon, an easy-to-use tool that is publicly available. Doyon downloaded the software and watched the chat rooms, waiting for a cue. When the signal came, thousands of Anons fired at once. Doyon entered a target URL—say, www.visa.com—and, in the upper-right corner, clicked a button that said “IMMA CHARGIN MAH LAZER.” (The operation also relied on more sophisticated hacking.) Over several days, Operation Payback disabled the home pages of Visa, MasterCard, and PayPal. In court filings, PayPal claimed that the attack had cost the company five and a half million dollars.
|
||||
|
||||
To Doyon, this was activism made tangible. In Cambridge, protesting against apartheid, he could not see immediate results; now, with the tap of a button, he could help sabotage a major corporation’s site. A banner headline on the Huffington Post read “MasterCard DOWN.” One gloating Anon tweeted, “There are some things WikiLeaks can’t do. For everything else, there’s Operation Payback.”
|
||||
|
||||
----------
|
||||
|
||||
In the fall of 2010, the Peace Camp protests ended. With slight concessions, the anti-homelessness law remained in effect. Doyon hoped to use the tactics of Anonymous to reinvigorate the movement. He recalls thinking, “I could wield Anonymous against this tiny little city government and they would just be fucking wrecked. Plan was we were finally going to solve this homelessness problem, once and for all.”
|
||||
|
||||
Joshua Covelli, a twenty-five-year-old Anon who went by the nickname Absolem, admired Doyon’s decisiveness. “Anonymous had been this clusterfuck of chaos,” Covelli told me. With Commander X, “there seemed to be a structure set up.” Covelli worked as a receptionist at a college in Fairborn, Ohio, and knew nothing about Santa Cruz politics. But when Doyon asked for help with Operation Peace Camp, Covelli e-mailed back immediately: “I’ve been waiting to join something like that my entire life.”
|
||||
|
||||
Doyon, under the name PLF, invited Covelli into a private I.R.C.:
|
||||
|
||||
> Absolem: Sorry to be so rude . . . Is PLF part of Anonymous or separate?
|
||||
>
|
||||
> Absolem: I was just asking because you all seem very organized in chat.
|
||||
>
|
||||
> PLF: You are not in the least rude. I am pleased to meet you. PLF is 22 year old hacker group originally from Boston. I started hacking in 81, not with computers but PBX (telephones).
|
||||
>
|
||||
> PLF: We are all older 40 or over. Some of us are former military or intelligence. One of us, Commander Adama is currently sought by an alphabet soup of cops and spooks and in hiding.
|
||||
>
|
||||
> Absolem: Wow that’s legit. I am really interested in helping this out in some way and Anonymous just seems too chaotic. I have some computer skills but very noob in hacking. I have some tools but no Idea how to use them.
|
||||
|
||||
With ritual solemnity, Doyon accepted Covelli’s request to join the P.L.F.:
|
||||
|
||||
> PLF: Encrypt the fuck out of all sensitive material that might incriminate you.
|
||||
>
|
||||
> PLF: Yep, work with any PLFer to get a message to me. Call me . . . Commander X for now.
|
||||
|
||||
In 2012, the Associated Press called Anonymous “a group of expert hackers”; Quinn Norton, in Wired, wrote that “Anonymous had figured out how to infiltrate anything,” resulting in “a wild string of brilliant hacks.” In fact some Anons are gifted coders, but the vast majority possess little technical skill. Coleman, the anthropologist, told me that only a fifth of Anons are hackers—the rest are “geeks and protesters.”
|
||||
|
||||
On December 16, 2010, Doyon, as Commander X, sent an e-mail to several reporters. “At exactly noon local time tomorrow, the Peoples Liberation Front and Anonymous will remove from the Internet the Web site of the Santa Cruz County government,” he wrote. “And exactly 30 minutes later, we will return it to normal function.”
|
||||
|
||||
The data-center staff for Santa Cruz County saw the warning and scrambled to prepare for the attack. They ran security scans on the servers and contacted A.T. & T., the county’s Internet provider, which suggested that they alert the F.B.I.
|
||||
|
||||
The next day, Doyon entered a Starbucks and booted up his laptop. Even for a surfing town, he was notably eccentric: a homeless-looking man wearing fatigues and typing furiously. Covelli met him in a private chat room.
|
||||
|
||||
> PLF: Go to Forum, sign in—and look at top right menu bar “chat.” Thats Ops for today. Thank you for standing with us.
|
||||
>
|
||||
> Absolem: Anything for PLF, sir.
|
||||
|
||||
They both opened DDoS software. Though only a handful of people were participating in Operation Peace Camp, Doyon gave orders as if he were addressing legions of troops:
|
||||
|
||||
> PLF: ATTENTION: Everyone who supports the PLF or considers us their friend—or who cares about defeating evil and protecting the innocent: Operation Peace Camp is LIVE and an action is underway. TARGET: www.co.santa-cruz.ca.us. Fire At Will. Repeat: FIRE!
|
||||
>
|
||||
> Absolem: got it, sir.
|
||||
|
||||
The data-center staff watched their servers, which showed a flurry of denial-of-service requests. Despite their best efforts, the site crashed. Twenty-five minutes later, Doyon decided that he had made his point. He typed “CEASE FIRE,” and the county’s site flickered back to life. (Despite the attack, the city’s anti-homelessness law did not change.)
|
||||
|
||||
Doyon hardly had time to celebrate before he grew anxious. “I got to leave,” he typed to Covelli. He fled to his shack in the mountains. Doyon was right to be wary: an F.B.I. agent had been snooping in the I.R.C. The F.B.I. obtained a warrant to search Doyon’s laptop.
|
||||
|
||||
A few weeks later, Doyon’s food ran out, and he returned to town. While he was at the Santa Cruz Coffee Roasting Company, two federal agents entered the shop. They brought him to the county police station. Doyon called Ed Frey, a lawyer and the founder of Peace Camp, who met him at the station. Doyon told Frey about his alter ego as Commander X.
|
||||
|
||||
Doyon was released, but the F.B.I. kept his laptop, which was full of incriminating evidence. Frey, a civil-rights lawyer who knew little about cybersecurity, drove Doyon back to his hillside encampment. “What are you going to do?” Frey asked.
|
||||
|
||||
|
||||
|
||||
“Zach is in the gifted-and-talented-and-you’re-not class.”
|
||||
|
||||
He spoke in cinematic terms. “Run like hell,” he said. “I will go underground, try to stay free as long as I can, and keep fighting the bastards any way possible.” Frey gave him two twenty-dollar bills and wished him luck.
|
||||
|
||||
----------
|
||||
|
||||
Doyon hitchhiked to San Francisco and stayed there for three months. He spent his days at Coffee to the People, a quirky café in the Haight-Ashbury district, where he would sit for hours in front of his computer, interrupted only by outdoor cigarette breaks.
|
||||
|
||||
In January, 2011, Doyon contacted Barrett Brown, the journalist and Anon. “What are we going to do next?” Doyon asked.
|
||||
|
||||
“Tunisia,” Brown said.
|
||||
|
||||
“Yeah, it’s a country in the Middle East,” Doyon said. “What about it?”
|
||||
|
||||
“We’re gonna take down its dictator,” Brown said.
|
||||
|
||||
“Oh, they have a dictator?” Doyon said.
|
||||
|
||||
A couple of days later, Operation Tunisia began. Doyon volunteered to spam Tunisian government e-mail addresses in an attempt to clog their servers. “I would take the text of the press release for that op and just keep sending it over and over again,” he said. “Sometimes, I was so busy that I would just put ‘fuck you’ and send it.” In one day, the Anons brought down the Web sites of the Tunisian Stock Exchange, the Ministry of Industry, the President, and the Prime Minister. They replaced the Web page of the President’s office with an image of a pirate ship and the message “Payback is a bitch, isn’t it?”
|
||||
|
||||
Doyon often spoke of his online battles as if he had just crawled out of a foxhole. “Dude, I turned black from doing it,” he told me. “My face, from all the smoke—it would cling to me. I would look up and I would literally be like a raccoon.” Most nights, he camped out in Golden Gate Park. “I would look at myself in the mirror and I’d be like, O.K., it’s been four days—maybe I should eat, bathe.”
|
||||
|
||||
Anonymous-affiliated operations continued to be announced on YouTube: Operation Libya, Operation Bahrain, Operation Morocco. As protesters filled Tahrir Square, Doyon participated in Operation Egypt. A Facebook page disseminated information, including links to a “care package” for protesters on the ground. The package, distributed through the file-sharing site Megaupload, contained encryption software and a primer on defending against tear gas. Later, when the Egyptian government disabled Internet and cellular networks within the country, Anonymous helped the protesters find alternative ways to get online.
|
||||
|
||||
In the summer of 2011, Doyon succeeded Adama as Supreme Commander of the P.L.F. Doyon recruited roughly half a dozen new members and attempted to position the P.L.F. as an élite squad within Anonymous. Covelli became one of his technical advisers. Another hacker, Crypt0nymous, made YouTube videos; others did research or assembled electronic care packages. Unlike Anonymous, the P.L.F. had a strict command structure. “X always called the shots on everything,” Covelli said. “It was his way or no way.” A hacker who founded a blog called AnonInsiders told me over encrypted chat that Doyon was willing to act unilaterally—a rare thing within Anonymous. “When we wanted to start an op, he didn’t mind if anyone would agree or not,” he said. “He would just write the press release by himself, list all the targets, open the I.R.C. channel, tell everyone to go in there, and start the DDoSing.”
|
||||
|
||||
Some Anons viewed the P.L.F. as a vanity project and Doyon as a laughingstock. “He’s known for his exaggeration,” Mustafa Al-Bassam, an Anon who went by Tflow, told me. Others, even those who disapproved of Doyon’s egotism, grudgingly acknowledged his importance to the Anonymous movement. “He walks that tough line of sometimes being effective and sometimes being in the way,” Gregg Housh said, adding that he and other prominent Anons had faced similar challenges.
|
||||
|
||||
Publicly, Anonymous persists in claiming to be non-hierarchical. In “We Are Legion,” a 2012 documentary about Anonymous by Brian Knappenberger, one activist uses the metaphor of a flock of birds, with various individuals taking turns drifting toward the front. Gabriella Coleman told me that, despite such claims, something resembling an informal leadership class did emerge within Anonymous. “The organizer is really important,” she said. “There are four or five individuals who are really good at it.” She counted Doyon among them. Still, Anons tend to rebel against institutional structure. In a forthcoming book about Anonymous, “Hacker, Hoaxer, Whistleblower, Spy,” Coleman writes that, among Anons, “personal identity and the individual remain subordinate to a focus on the epic win—and, especially, the lulz.”
|
||||
|
||||
Anons who seek individual attention are often dismissed as “egofags” or “namefags.” (Many Anons have yet to outgrow their penchant for offensive epithets.) “There are surprisingly few people who violate the rule” against attention-seeking, Coleman says. “Those who do, like X, are marginalized.” Last year, in an online discussion forum, a commenter wrote, “I stopped reading his BS when he started comparing himself to Batman.”
|
||||
|
||||
Peter Fein, an online activist known by the nickname n0pants, was among the many Anons who were put off by Doyon’s self-aggrandizing rhetoric. Fein browsed the P.L.F. Web site, which featured a coat of arms and a manifesto about the group’s “epic battle for the very soul of humanity.” Fein was dismayed to find that Doyon had registered the site using his real name, leaving himself and possibly other Anons vulnerable to prosecution. “I’m basically okay with people DDoSing,” Fein recalls telling Doyon over private chat. “But if you’re going to do it, you’ve got to cover your ass.”
|
||||
|
||||
On February 5, 2011, the Financial Times reported that Aaron Barr, the C.E.O. of a cybersecurity firm called HBGary Federal, had identified the “most senior” members of Anonymous. Barr’s research suggested that one of the top three was Commander X, a hacker based in California, who could “manage some significant firepower.” Barr contacted the F.B.I. and offered to share his work with them.
|
||||
|
||||
Like Fein, Barr had seen that the P.L.F. site was registered to Christopher Doyon at an address on Haight Street. Based on Facebook and I.R.C. activity, Barr concluded that Commander X was Benjamin Spock de Vries, an online activist who had lived near the Haight Street address. Barr approached de Vries on Facebook. “Please tell the folks there that I am not out to get you guys,” Barr wrote. “Just want the ‘leadership’ to know what my intent is.”
|
||||
|
||||
“ ‘Leadership’ lmao,” de Vries responded.
|
||||
|
||||
Days after the Financial Times story appeared, Anonymous struck back. HBGary Federal’s Web site was defaced. Barr’s personal Twitter account was hijacked, thousands of his e-mails were leaked online, and Anons released his address and other personal information—a punishment known as doxing. Barr resigned from HBGary Federal within the month.
|
||||
|
||||
----------
|
||||
|
||||
In April, 2011, Doyon left San Francisco and hitchhiked around the West, camping in parks at night and spending his days at Starbucks outlets. In his backpack he kept his laptop, his Guy Fawkes mask, and several packs of Pall Malls.
|
||||
|
||||
|
||||
|
||||
“This is what I learned during my summer at TED camp.”
|
||||
|
||||
He followed internal Anonymous news. That spring, six élite Anons, all of whom had been instrumental in deflecting Barr’s investigation, formed a group called Lulz Security, or LulzSec. As their name indicated, they felt that Anonymous had become too self-serious; they aimed to bring the lulz back. While Anonymous continued supporting Arab Spring protesters, LulzSec hacked the Web site of PBS and posted a fake story claiming that the late rapper Tupac Shakur was alive in New Zealand.
|
||||
|
||||
Anons often share text through the Web site Pastebin.com. On the site, LulzSec issued a statement that read, “It has come to our unfortunate attention that NATO and our good friend Barrack Osama-Llama 24th-century Obama have recently upped the stakes with regard to hacking. They now treat hacking as an act of war.” The loftier the target, the greater the lulz. On June 15th, LulzSec took credit for crashing the C.I.A.’s Web site, tweeting, “Tango down—cia.gov—for the lulz.”
|
||||
|
||||
On June 20, 2011, Ryan Cleary, a nineteen-year-old member of LulzSec, was arrested for the DDoS attacks on the C.I.A. site. The next month, F.B.I. agents arrested fourteen other hackers for DDoS attacks on PayPal seven months earlier. Each of the PayPal Fourteen, as they became known, faced fifteen years in prison and a five-hundred-thousand-dollar fine. They were charged with conspiracy and intentional damage to protected computers under the Computer Fraud and Abuse Act. (The law allows for wide prosecutorial discretion and was widely criticized after Aaron Swartz, an Internet activist who was facing thirty-five years in prison, committed suicide last year.)
|
||||
|
||||
A petition was circulated on behalf of Jake (Topiary) Davis, a member of LulzSec, who needed help paying his legal fees. Doyon entered an I.R.C. to promote Davis’s cause:
|
||||
|
||||
> CommanderX: Please sign the petition and help Topiary…
|
||||
>
|
||||
> toad: you are an attention whore
|
||||
>
|
||||
> toad: so you get attention
|
||||
>
|
||||
> CommanderX: Toad your an asshole.
|
||||
>
|
||||
> katanon: sigh
|
||||
|
||||
Doyon had grown increasingly brazen. He DDoS’ed the Web site of the Chamber of Commerce of Orlando, Florida, after activists there were arrested for feeding the homeless. He launched the attacks from public WiFi networks, using his personal laptop, without making much effort to cover his tracks. “That’s brave but stupid,” a senior member of the P.L.F. who asked to be called Kalli told me. “He didn’t seem to care if he was caught. He was a suicide hacker.”
|
||||
|
||||
Two months later, Doyon participated in a DDoS strike against San Francisco’s Bay Area Rapid Transit, protesting an incident in which a BART police officer had killed a homeless man named Charles Hill. Doyon appeared on the “CBS Evening News” to defend the action, his voice disguised and his face obscured by a bandanna. He compared DDoS attacks to civil disobedience. “It’s no different, really, than taking up seats at the Woolworth lunch counters,” he said. Bob Schieffer, the CBS anchor, snickered and said, “It’s not quite the civil-rights movement, as I see it.”
|
||||
|
||||
On September 22, 2011, in a coffee shop in Mountain View, California, Doyon was arrested and charged with causing intentional damage to a protected computer. He was detained for a week and released on bond. Two days later, against his lawyer’s advice, he called a press conference on the steps of the Santa Cruz County Courthouse. His hair in a ponytail, he wore dark sunglasses, a black pirate hat, and a camouflage bandanna around his neck.
|
||||
|
||||
In characteristically melodramatic fashion, Doyon revealed his identity. “I am Commander X,” he told reporters. He raised his fist. “I am immensely proud, and humbled to the core, to be a part of the idea called Anonymous.” He told a journalist, “All you need to be a world-class hacker is a computer and a cool pair of sunglasses. And the computer is optional.”
|
||||
|
||||
Kalli worried that Doyon was placing his ego above the safety of other Anons. “It’s the weakest link in the chain that ends up taking everyone down,” he told me. Josh Covelli, the Anon who had been eager to help Doyon with Operation Peace Camp, told me that his “jaw dropped” when he saw a video of Doyon’s press conference online. “The way he presented himself and the way he acted had become more unhinged,” Covelli said.
|
||||
|
||||
Three months later, Doyon’s pro-bono lawyer, Jay Leiderman, was in a federal court in San Jose. Leiderman had not heard from Doyon in a couple of weeks. “I’m inquiring as to whether there’s a reason for that,” the judge said. Leiderman had no answer. Doyon was absent from another hearing two weeks later. The prosecutor stated the obvious: “It appears as though the defendant has fled.”
|
||||
|
||||
----------
|
||||
|
||||
Operation Xport was the first Anonymous operation of its kind. The goal was to smuggle Doyon, now a fugitive wanted for two felonies, out of the country. The coördinators were Kalli and a veteran Anon who had met Doyon at an acid party in Cambridge during the eighties. A retired software executive, he was widely respected within Anonymous.
|
||||
|
||||
Doyon’s ultimate destination was the software executive’s house, deep in rural Canada. In December, 2011, he hitchhiked to San Francisco and made his way to an Occupy encampment downtown. He found his designated contact, who helped him get to a pizzeria in Oakland. At 2 A.M., Doyon, using the pizzeria’s WiFi, received a message on encrypted chat.
|
||||
|
||||
“Are you near a window?” the message read.
|
||||
|
||||
“Yeah,” Doyon typed.
|
||||
|
||||
“Look across the street. Do you see the green mailbox? In exactly fifteen minutes, go and stand next to that mailbox and set your backpack down, and lay your mask on top of it.”
|
||||
|
||||
For a few weeks, Doyon shuttled among safe houses in the Bay Area, following instructions through encrypted chat. Eventually, he took a Greyhound bus to Seattle, where he stayed with a friend of the software executive. The friend, a wealthy retiree, spent hours using Google Earth to help Doyon plot a route to Canada. They went to a camping-supplies store, and the friend spent fifteen hundred dollars on gear for Doyon, including hiking boots and a new backpack. Then he drove Doyon two hours north and dropped him off in a remote area, several hundred miles from the border, where Doyon met up with Amber Lyon.
|
||||
|
||||
Months earlier, Lyon, a broadcast journalist, had interviewed Doyon for a CNN segment about Anonymous. He liked her report, and they stayed in touch. Lyon asked to join Doyon on his escape, to shoot footage for a possible documentary. The software executive thought that it was “nuts” to take the risk, but Doyon invited her anyway. “I think he wanted to make himself a face of the movement,” Lyon told me. For four days, she filmed him as he hiked north, camping in the woods. “It wasn’t very organized,” Lyon recalls. “He was functionally homeless, so he just kind of wandered out of the country.”
|
||||
|
||||
|
||||
|
||||
“This is the barn where we keep our feelings. If a feeling comes to you, bring it out here and lock it up.”
|
||||
|
||||
On February 11, 2012, a press release appeared on Pastebin. “The PLF is delighted to announce that Commander X, aka Christopher Mark Doyon, has fled the jurisdiction of the USA and entered the relative safety of the nation of Canada,” it read. “The PLF calls upon the government of the USA to come to its senses and cease the harassment, surveillance—and arrest of not only Anonymous, but all activists.”
|
||||
|
||||
----------
|
||||
|
||||
In Canada, Doyon spent a few days with the software executive in a small house in the woods. In a chat with Barrett Brown, Doyon was effusive.
|
||||
|
||||
> BarrettBrown: you have enough safe houses, etc? . . .
|
||||
>
|
||||
> CommanderX: Yes I am good here, money and houses a plenty in Canada.
|
||||
>
|
||||
> CommanderX: Amber Lyon asked me on camera about you.
|
||||
>
|
||||
> CommanderX: I think you will like my reply, and fuck the trolls Barrett. I have always loved you and always will.
|
||||
>
|
||||
> CommanderX: :-)
|
||||
>
|
||||
> CommanderX: I told her you were a hero.
|
||||
>
|
||||
> BarrettBrown: you’re a hero . . .
|
||||
>
|
||||
> BarrettBrown: glad you’re safe for now
|
||||
>
|
||||
> BarrettBrown: let me know if you need anything
|
||||
>
|
||||
> CommanderX: I am, and if this works we can get others out to . . . .
|
||||
>
|
||||
> BarrettBrown: good, we’re going to need that
|
||||
|
||||
Ten days after Doyon’s escape, the Wall Street Journal reported that Keith Alexander, then the N.S.A. and U.S. Cyber Command director, had held classified meetings in the White House and elsewhere during which he expressed concern about Anonymous. Within two years, Alexander warned, the group might be capable of destabilizing national power grids. General Martin Dempsey, the chairman of the Joint Chiefs of Staff, told the Journal that an enemy of the U.S. “could give cyber malware capability to some fringe group,” adding, “We have to get after this.”
|
||||
|
||||
On March 8th, a briefing on cybersecurity was held for members of Congress at a Sensitive Compartmented Information Facility near the Capitol Building. Many of the country’s top security officials attended the briefing, including Alexander, Dempsey, Robert Mueller, the head of the F.B.I., and Janet Napolitano, the Secretary of Homeland Security. Attendees were shown a computer simulation of what a cyberattack on the Eastern Seaboard’s electrical supply might look like. Anonymous was not yet capable of mounting an attack on this scale, but security officials worried that they might join forces with other, more sophisticated groups. “As we were dealing with this ever-increasing presence on the Net and ever-increasing risk, the government nuts and bolts were still being worked out,” Napolitano told me. When discussing potential cybersecurity threats, she added, “We often used Anonymous as Exhibit A.”
|
||||
|
||||
Anonymous might be the most powerful nongovernmental hacking collective in the world. Even so, it has never demonstrated an ability or desire to damage any key elements of public infrastructure. To some cybersecurity experts, the dire warnings about Anonymous sounded like fearmongering. “There’s a big gap between declaring war on Orlando and pulling off a Stuxnet attack,” James Andrew Lewis, a senior fellow at the Center for Strategic and International Studies, told me, referring to the elaborate cyberstrike carried out by the U.S. and Israel against Iranian nuclear sites in 2007. Yochai Benkler, a professor at Harvard Law School, told me, “What we’ve seen is the use of drumbeating as justification for major defense spending of a form that would otherwise be hard to justify.”
|
||||
|
||||
Keith Alexander, who recently retired from the government, declined to comment for this story, as did representatives from the N.S.A., the F.B.I., the C.I.A., and the D.H.S. Although Anons have never seriously compromised government computer networks, they have a record of seeking revenge against individuals who anger them. Andy Purdy, the former head of the national-cybersecurity division of the D.H.S., told me that “a fear of retaliation,” both institutional and personal, prevents government representatives from speaking out against Anonymous. “Everyone is vulnerable,” he said.
|
||||
|
||||
----------
|
||||
|
||||
On March 6, 2012, Hector Xavier Monsegur, a key member of LulzSec with the screen name Sabu, was revealed to be an F.B.I. informant. In exchange for a reduced sentence, Monsegur had spent several months undercover, helping to gather evidence against other LulzSec members. The same day, five leading Anons were arrested and charged with several crimes, including computer conspiracy. An F.B.I. official told Fox News, “This is devastating to the organization. We’re chopping off the head of LulzSec.” Over the next ten months, Barrett Brown was indicted on seventeen federal charges, most of which were later dropped. (He will be sentenced in October.)
|
||||
|
||||
Doyon was distraught, but he continued to hack—and to seek attention. He appeared, masked, at a Toronto screening of a documentary about Anonymous. He gave an interview to a reporter from the National Post and boasted, without substantiation, “We have access to every classified database in the U.S. government. It’s a matter of when we leak the contents of those databases, not if.”
|
||||
|
||||
In January, 2013, after another Anon started an operation about the rape of a teen-age girl in Steubenville, Ohio, Doyon repurposed LocalLeaks, a site he had created two years earlier, as a clearinghouse for information about the rape. Like many Anonymous efforts, LocalLeaks was both influential and irresponsible. It was the first site to widely disseminate the twelve-minute video of a Steubenville High School graduate joking about the rape, which inflamed public outrage about the story. But the site also perpetuated several false rumors about the case and it failed to redact a court document, thus accidentally revealing the rape victim’s name. Doyon admitted to me that his strategy of releasing unexpurgated materials was controversial, but he recalled thinking, “We could either gut the Steubenville Files . . . or we could release everything we know, basically, with the caveat, Hey, you’ve got to trust us.”
|
||||
|
||||
In May, 2013, the Rustle League, a group of online trolls who often provoke Anonymous, hacked Doyon’s Twitter account. Shm00p, one of the leaders of Rustle League, told me, “We’re not trying to cause harm to the guy, but, just, the shit he was saying—it was comical to me.” The Rustle League implanted racist and anti-Semitic messages into Doyon’s account, such as a link to www.jewsdid911.org.
|
||||
|
||||
On August 27, 2013, Doyon posted a note announcing his retirement from Anonymous. “My entire life has been dedicated to fighting for justice and freedom,” he wrote. “ ‘Commander X’ may be invincible, but I am extremely ill from the exhaustion and stress of fighting in this epic global cyber war.” Reactions varied from compassion (“you deserve a rest”) to ridicule (“poor crazy old gnoll. Maybe he has some time for bathing now”). Covelli told me, “The persona has consumed him to the point where he can’t handle it anymore.”
|
||||
|
||||
|
||||
|
||||
August 17, 1998 “We still have Paris? Just thought I’d check.”
|
||||
|
||||
----------
|
||||
|
||||
The first Million Mask March took place on November 5, 2013. Several thousand people marched in support of Anonymous, in four hundred and fifty cities around the world. In a sign of how deeply Anonymous had penetrated popular culture, one protester in London removed his Guy Fawkes mask to reveal that he was the actor Russell Brand.
|
||||
|
||||
While I attended the rally in Washington, D.C., Doyon watched a livestream in Canada. I exchanged e-mails with him on my phone. “It is so surreal to sit here, sidelined and out of the game—and watch something that you helped create turn into this,” he wrote. “At least it all made a difference.”
|
||||
|
||||
We arranged a face-to-face meeting. Doyon insisted that I submit to elaborate plans made over encrypted chat. I was to fly to an airport several hours away, rent a car, drive to a remote location in Canada, and disable my phone.
|
||||
|
||||
I found him in a small, run-down apartment building in a quiet residential neighborhood. He wore a green Army-style jacket and a T-shirt featuring one of Anonymous’s logos: a black-suited man with a question mark instead of a face. The apartment was sparsely furnished and smelled of cigarette smoke. He discussed U.S. politics (“I have not voted in many elections—it’s all a rigged game”), militant Islam (“I believe that people in the Nigerian government essentially colluded to create a completely phony Al Qaeda affiliate called Boko Haram”), and his tenuous position within Anonymous (“These people who call themselves trolls are really just rotten, mean, evil people”).
|
||||
|
||||
Doyon had shaved his beard, and he looked gaunt. He told me that he was ill and that he rarely went outside. On his small desk were two laptops, a stack of books about Buddhism, and an overflowing ashtray. A Guy Fawkes mask hung on an otherwise bare yellow wall. He told me, “Underneath the whole X persona is a little old man who is in absolute agony at times.”
|
||||
|
||||
This past Christmas, the founder of the news site AnonInsiders visited him, bearing pie and cigarettes. Doyon asked the friend to succeed him as Supreme Commander of the P.L.F., offering “the keys to the kingdom”—all his passwords, as well as secret files relating to several Anonymous operations. The friend gently declined. “I have a life,” he told me.
|
||||
|
||||
----------
|
||||
|
||||
On August 9, 2014, at 5:09 P.M. local time, Kareem (Tef Poe) Jackson, a rapper and activist from Dellwood, Missouri, a suburb of St. Louis, tweeted about a crisis unfolding in a neighboring town. “Basically martial law is taking place in Ferguson all perimeters blocked coming and going,” he wrote. “National and international friends Help!!!” Five hours earlier in Ferguson, an unarmed eighteen-year-old African-American, Michael Brown, had been shot to death by a white police officer. The police claimed that Brown had reached for the officer’s gun. Brown’s friend Dorian Johnson, who was with him at the time, said that Brown’s only offense was refusing to leave the middle of the street.
|
||||
|
||||
Within two hours, Jackson received a reply from a Twitter account called CommanderXanon. “You can certainly expect us,” the message read. “See if you can get us some live streams going, that would be useful.” In recent weeks, Doyon, still in Canada, had come out of retirement. In June, two months before his fiftieth birthday, he quit smoking (“#hacktheaddiction #ecigaretteswork #old,” he later tweeted). The following month, after fighting broke out in Gaza, he tweeted in support of Anonymous’s Operation Save Gaza, a series of DDoS strikes against Israeli Web sites. Doyon found the events in Ferguson even more compelling. Despite his idiosyncrasies, he had a knack for being early to a cause.
|
||||
|
||||
“Start collecting URLs for cops, city government,” Doyon tweeted. Within ten minutes, he had created an I.R.C. channel. “Anonymous Operation Ferguson is engaged,” he tweeted. Only two people retweeted the message.
|
||||
|
||||
The next morning, Doyon posted a link to a rudimentary Web site, which included a message to the people of Ferguson—“You are not alone, we will support you in every way possible”—and an ultimatum to the police: “If you abuse, harass or harm in any way the protesters in Ferguson, we will take every Web based asset of your departments and governments off line. That is not a threat, it is a promise.” Doyon appealed to the most visible Anonymous Twitter account, YourAnonNews, which has 1.3 million followers. “Please support Operation Ferguson,” he wrote. A minute later, YourAnonNews complied. That day, the hashtag #OpFerguson was tweeted more than six thousand times.
|
||||
|
||||
The crisis became a top news story, and Anons rallied around Operation Ferguson. As with the Arab Spring operations, Anonymous sent electronic care packages to protesters on the ground, including a riot guide (“Pick up the gas emitter and lob it back at the police”) and printable Guy Fawkes masks. As Jackson and other protesters marched through Ferguson, the police attempted to subdue them with rubber bullets and tear gas. “It looked like a scene from a Bruce Willis movie,” Jackson told me. “Barack Obama hasn’t supported us to the degree Anonymous has,” he said. “It’s comforting to know that someone out there has your back.”
|
||||
|
||||
One site, www.opferguson.com, turned out to be a honeypot—a trap designed to collect the Internet Protocol addresses of visitors and turn them over to law-enforcement agencies. Some suspected Commander X of being a government informant. In the #OpFerguson I.R.C., someone named Sherlock wrote, “Everyone got me scared clicking links. Unless it’s from a name I’ve seen a lot, I just avoid them.”
|
||||
|
||||
Protesters in Ferguson asked the police to reveal the name of the officer who had shot Brown. Several times, Anons echoed this demand. Someone tweeted, “Ferguson police better release the shooter’s name before Anonymous does the work for them.” In a community meeting on August 12th, Jon Belmar, the Chief of the St. Louis Police Department, refused. “We do not do that until they’re charged with an offense,” he said.
|
||||
|
||||
In retaliation, a hacker with the handle TheAnonMessage tweeted a link to what he claimed was a two-hour audio file of a police radio scanner, recorded around the time of Brown’s death. TheAnonMessage also doxed Belmar, tweeting what he purported to be the police chief’s home address, phone number, and photographs of his family—one of his son sleeping on a couch, another of Belmar posing with his wife. “Nice photo, Jon,” TheAnonMessage tweeted. “Your wife actually looks good for her age. Have you had enough?” An hour later, TheAnonMessage threatened to dox Belmar’s daughter.
|
||||
|
||||
Richard Stallman, the first-generation hacker from M.I.T., told me that though he supports many of Anonymous’s causes, he considered these dox attacks reprehensible. Even internally, TheAnonMessage’s actions were divisive. “Why bother doxing people who weren’t involved?” one Anon asked over I.R.C., adding that threatening Belmar’s family was “beyond stupid.” But TheAnonMessage and other Anons continued to seek information that could be used in future dox attacks. The names of Ferguson Police Department employees were available online, and Anons scoured the Internet, trying to suss out which of the officers had killed Brown.
|
||||
|
||||
|
||||
|
||||
April 12, 1999“Which thing do I press?”
|
||||
|
||||
In the early morning of August 14th, a few Anons became convinced, based on Facebook photos and other disparate clues, that Brown’s shooter was a thirty-two-year-old man named Bryan Willman. According to a transcript of an I.R.C., one Anon posted a photo of Willman with a swollen face; another noted, “The shooter claimed to have been hit in the face.” Another user, Anonymous|11057, acknowledged that his suspicion of Willman involved “a leap of probably bad logic.” Still, he wrote, “i just can’t shake it. i really truly honestly and without a shred of hard evidence think it’s him.”
|
||||
|
||||
TheAnonMessage seemed amused by the conversation, writing, “#RIPBryanWillman.” Other Anons urged caution. “Please be sure,” Anonymous|2252 wrote. “It’s not just about a man’s life, Anon can easily be turned on by the public if something truly unjust comes of this.”
|
||||
|
||||
The debate went on for more than an hour. Several Anons pointed out that there was no way to confirm that Willman had ever been a Ferguson police officer.
|
||||
|
||||
> Anonymous|3549: @gs we still don’t have a confirmation that bry is even on PD
|
||||
>
|
||||
> Intangir: tensions are high enough right now where there is a slim chance someone might care enough to kill him
|
||||
>
|
||||
> Anonymous|11057: the only real way to get a confirmation would be an eyewitness report from the scene of the crime. otherwise it’s hearsay and shillery
|
||||
>
|
||||
> Anonymous|11057: the fastest way to eliminate a suspect is to call him a suspect . . . we are all terrified of being unjust, but the pegs keep fitting in the holes . . .
|
||||
|
||||
Many Anons remained uncomfortable with the idea of a dox. But around 7 A.M. a vote was taken. According to chat logs, of the eighty or so people in the I.R.C., fewer than ten participated. They decided to release Willman’s personal information.
|
||||
|
||||
> Anonymous|2252: is this going on twitter?
|
||||
>
|
||||
> anondepp: lol
|
||||
>
|
||||
> Anonymous|2252: via @theanonmessage ?
|
||||
>
|
||||
> TheAnonMessage: yup
|
||||
>
|
||||
> TheAnonMessage: just did
|
||||
>
|
||||
> anondepp: its up
|
||||
>
|
||||
> Anonymous|2252: shit
|
||||
>
|
||||
> TheAnonMessage: Lord in heaven…
|
||||
>
|
||||
> Anonymous|3549: . . .have mercy on our souls
|
||||
>
|
||||
> anondepp: lol
|
||||
|
||||
At 9:45 A.M., the St. Louis Police Department responded to TheAnonMessage. “Bryan Willman is not even an officer with Ferguson or St. Louis County PD,” the tweet read. “Do not release more info on this random citizen.” (The F.B.I. later opened an investigation into the hacking of police computers in Ferguson.) Twitter quickly suspended TheAnonMessage, but Willman’s name and address had been reported widely.
|
||||
|
||||
Willman is the head police dispatcher in St. Ann, a suburb west of Ferguson. When the St. Louis Police Department’s Intelligence Unit called to tell him that he had been named as the killer, Willman told me, “I thought it was the weirdest joke.” Within hours, he received hundreds of death threats on his social-media accounts. He stayed in his house for nearly a week, alone, under police protection. “I just want it all to go away,” he told me. He thinks that Anonymous has irreparably harmed his reputation. “I don’t see how they can ever think they can be trusted again,” he said.
|
||||
|
||||
“We are not perfect,” OpFerguson tweeted. “Anonymous makes mistakes, and we’ve made a few in the chaos of the past few days. For those, we apologize.” Though Doyon was not responsible for the errant dox attack, other Anons took the opportunity to shame him for having launched an operation that spiralled out of control. A Pastebin message, distributed by YourAnonNews, read, “You may notice contradictory tweets and information about #Ferguson and #OpFerguson from various Anonymous twitter accounts. Part of why there is dissension about this particular #op is that CommanderX is considered a ‘namefag/facefag’—a known entity who enjoys or at least doesn’t shun publicity—which is considered by most Anonymous to be bad form, for some probably fairly obvious reasons.”
|
||||
|
||||
On his personal Twitter account, Doyon denied any involvement with Op Ferguson and wrote, “I hate this shit. I don’t want drama and I don’t want to fight with people I thought were friends.” Within a couple of days, he was sounding hopeful again. He recently retweeted messages reading, “You call them rioters, we call them voices of the oppressed” and “Free Tibet.”
|
||||
|
||||
Doyon is still in hiding. Even Jay Leiderman, his attorney, does not know where he is. Leiderman says that, in addition to the charges in Santa Cruz, Doyon may face indictment for his role in the PayPal and Orlando attacks. If he is arrested and convicted on all counts, he could spend the rest of his life in prison. Following the example of Edward Snowden, he hopes to apply for asylum with the Russians. When we spoke, he used a lit cigarette to gesture around his apartment. “How is this better than a fucking jail cell? I never go out,” he said. “I will never speak with my family again. . . . It’s an incredibly high price to pay to do everything you can to keep people alive and free and informed.”
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: http://www.newyorker.com/magazine/2014/09/08/masked-avengers
|
||||
|
||||
作者：[David Kushner][a]
|
||||
译者：[译者ID](https://github.com/译者ID)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创翻译，[Linux中国](http://linux.cn/) 荣誉推出
|
||||
|
||||
[a]:http://www.newyorker.com/contributors/david-kushner
|
||||
@ -0,0 +1,103 @@
|
||||
Why Is Huffington Post Running A Multi-Part Series To Promote The Lies Of A Guy Who Pretended To Invent Email?
|
||||
================================================================================
|
||||
**from the that's-just-wrong dept**
|
||||
|
||||
I thought this story had ended a few years ago. Back in 2012, we wrote about how The Washington Post and some other big name media outlets were claiming that a guy named V.A. Shiva Ayyadurai had "invented email" in 1978. The problem was that [it wasn't even close to true][1] and relied on a number of total misconceptions about email, software and copyright law. Ayyadurai and some of his friends have continued to play up the claim that he "invented" email, but it simply was never true, and it's reaching a level that seems truly bizarre. Ayyadurai may have done some interesting things, but his continued false insistence that he invented email is reaching really questionable levels. And, now it's gone absolutely nutty, with the Huffington Post running [a multi-part series][2] (up to five separate articles so far -- all done in the past 10 days) all playing up misleading claims saying that Ayyadurai invented email, even though even a basic understanding of the history shows he did not.
|
||||
|
||||
Let's take care of the basics first, and then we'll dig in on what's going on here, because it's really quite ridiculous. First off, no one denies that V.A. Shiva Ayyadurai -- an apparently very bright 14-year-old at the time -- wrote an email software program for the University of Medicine and Dentistry of New Jersey (UMDNJ) in 1978. By all accounts, it was a perfectly decent email system that allowed the UMDNJ staff to send electronic messages. Further, no one doubts that, in 1981, Ayyadurai registered the copyright on his program, which was called EMAIL. The problems are that (1) email was invented long before 1978, (2) the copyright is merely on the specific software code, not the idea of email, and (3) while Ayyadurai may have independently recreated the basics of email (and even added a nice feature), none of his work was even remotely related to what later became the standards of email. What's most sickening about this is that as part of this new PR campaign, Ayyadurai is ridiculously arguing that the reason no one believes him isn't because he's simply wrong, but because they can't stand to believe that "a dark-skinned immigrant kid, 14 years old," invented email, and that it was done in "one of the poorest cities in the US" rather than at a famous university.
|
||||
|
||||
Again, that might make for a nice story line if there were some factual basis behind it, but there isn't. The history of email [is well-documented][3] from [multiple sources][4] and it began way, way before 1978. And while early versions were somewhat crude, by 1978 they had basically everything that Ayyadurai claims to have invented (it is entirely believable that Ayyadurai, as a bright kid, independently came up with the same ideas, but he was hardly the first). There was a messaging system called MAILBOX at MIT in 1965. You can read [all the details of it here][5], including source code. Ray Tomlinson is frequently credited with inventing the modern concept of email for the internet by establishing the @ symbol (in 1972) as a way of determining both the user and which computer to send the email to. By 1975, there were things like email folders (invented by Larry Roberts) and some other basic email apps. As is noted, by 1976 -- two years before Ayyadurai wrote his app -- email was *75% of all ARPANET traffic*.
|
||||
|
||||
So, let's get to the Huffington Post trying to whitewash all of this factual history out of existence.
|
||||
|
||||
It started on August 20th, with an article by Larry Weber, CEO of Racepoint Global, kicking off a supposed "series" called "The History of Email." Except that the series has little to do with the history of email at all. It's just about Ayyadurai writing his particular email program in 1978. Great story. Smart kid done good. Has nothing to do with the invention of email. Weber, though, calls it [The Boy Who Invented Email][6]. At this point, it should be worth questioning why Weber suddenly decided this was such an interesting story. If you don't know, Weber is one of PR's [biggest names][7], having built one of the most successful PR companies in history. It seems odd that he "just happened" to come across Ayyadurai's fake story and decided to help create a 5-part series about it. I have reached out to both Weber and the Huffington Post to ask if Weber has any financial relationship with Ayyadurai. As I publish this, neither has responded. The post will be updated if I hear from either. None of the posts in the series disclose any such relationship. Nor does the Huffington Post indicate that this is a "sponsored" post as far as I can tell.
|
||||
|
||||
The [second][8] and [third][9] articles in the series are both written by Leslie Michelson, the Director of High Performance and Research Computing at Rutgers Medical School (which took over UMDNJ a while back). More importantly, in 1978 he was the Director of the Laboratory Computer Network at UMDNJ, and apparently "challenged" Ayyadurai to create an electronic interoffice mail system. The [fourth article][10] in the series is by Robert Field, a technologist at Rutgers Medical School and, in 1978, a colleague of Ayyadurai at UMDNJ. See a pattern? Huffington Post also [interviewed Ayyadurai][11] for HuffPost Live in which he mostly attacks anyone who challenges his story, comparing himself to Philo T. Farnsworth -- except in that case, Farnsworth actually invented TV before anyone else. Ayyadurai did not do that with email. Apparently there are two more in this series that are still to come.
|
||||
|
||||
When you look at the collection of articles, they all repeat the same basic things: Ayyadurai did create an email system and "it was recognized by the federal government." This is misleading in the extreme. It's amusing how they all use the exact same language. Larry Weber claims:
|
||||
|
||||
> On August 30, 1982, **the US government officially recognized V.A. Shiva Ayyadurai as the inventor of email** by awarding him the first US Copyright for "Email," "Computer Program for Electronic Mail System," for his 1978 invention. This was awarded at a time when Copyright was the only way to protect software inventions.
|
||||
|
||||
Leslie Michaelson says:
|
||||
|
||||
> On August 30,1982, V.A. Shiva Ayyadurai **received official recognition as the inventor of email from the U.S. government**, for the work he had done in 1978.
|
||||
|
||||
Every article in the series includes this image of his copyright registration:
|
||||
|
||||
[][12]
|
||||
|
||||
Except, if you know anything about copyright, you know that what they're claiming is not at all true. The registration of copyrights is about as close to a rubber-stamping process as is possible. It has nothing to do with "inventions" at all, but is rather a copyright for the specific software program. Ayyadurai received a copyright on his email program and that's it. It has absolutely nothing to do with him being the inventor of email.
|
||||
|
||||
Microsoft holds a copyright on Windows, but no one claims it "invented" the glass things you look outside your building with. Hell, no one even claims that Microsoft invented windowing user interfaces, because it did not. The name of the program and the fact that you can copyright it does not make you the "inventor" of the concept behind it.
|
||||
|
||||
Weber, Ayyadurai and his friends try to counter the "it's a copyright, not a patent" claim with an incredibly misleading response. Here's Michelson:
|
||||
|
||||
> On August 30, 1982, Shiva was issued the first Copyright for "Email", "Computer Program for Electronic Mail System." At that time, Copyright was the equivalent of a patent, as there was no other way to protect software inventions. Only in 1980 was the Copyright Act of 1976 amended to protect software. Patent law had not even caught up to software in 1980
|
||||
|
||||
Copyright was not, and has never been "the equivalent of a patent." Copyright and patents are two very different things. Copyright protects specific expression. Patents protect inventions. That's why copyright protected only the specific code that Ayyadurai wrote, rather than the concept of email. While it's true that software wasn't considered patentable by many at the time, that doesn't, in any way, mean that a copyright on a particular piece of software was the equivalent in any way, to a patent at the time.
|
||||
|
||||
To further their argument, both Weber and Michelson include nearly identical, but slightly different, infographics on the history of email, which (of course) start in 1978 with Ayyadurai's work. According to those charts, email was barely even a thing outside of UMDNJ until 1985 when offline email readers come about. The infographic is the work of the impressive sounding International Center for Integrative Systems. What's left out is that the "[Founder and Chairman][13]" of the International Center for Integrative Systems happens to be... a guy named V.A. Shiva Ayyadurai. The same infographic tosses in a "milestone" in email in 1995, when "Echomail" launched. Doesn't sound familiar? Echomail was a company started by... V.A. Shiva Ayyadurai.
|
||||
|
||||
The rest of the articles seem to just focus on attacking those who actually were involved in the invention of email and who dared to speak out against Ayyadurai's claims. The story, which includes no actual support, is that the folks at BBN decided in the early 80s that email security was a big business opportunity and rewrote history. Whether or not BBN played up their role in the history of email is debatable, but none of that changes the fact that they (and many others) were using email, and had email software, long before Ayyadurai did anything. At no point do any of them address the long history of email systems long before Ayyadurai arrived on the scene. Instead, they just talk about this grand conspiracy theory, claiming (ridiculously) that if BBN were outed as not being the inventor of email (even though no one really claims the company was the inventor of email) it would harm its business. That makes no sense at all. First of all, BBN's history of work related to the internet is long and well-detailed (there's even a [fantastic book][14] about it). Even if it had nothing to do with email, it's other work is much more impressive. Second, the company is currently owned by defense contracting giant Raytheon. Does anyone honestly think Raytheon cares one way or the other who "invented email"?
|
||||
|
||||
All of their "debunking" claims rest entirely on a RAND report written by David Crocker in 1977, where they take two sentences totally out of context. Here's what Ayyadurai, Weber and their friends claim Crocker said:
|
||||
|
||||
> "At this time, no attempt is being made to emulate a full-scale, inter-organizational mail system. The fact that the system is intended for use in various organizational contexts and by users of differing expertise makes it almost impossible to build a system which responds to all users' needs."
|
||||
|
||||
It's telling that Ayyadurai and his friends never actually tell you the name of the report or link to it. Because actually reading what Crocker wrote would undermine their argument. The report is called "Framework and Functions of the 'MS' Personal Message System" and you can read it here. Not only do Ayyadurai and his friends take Crocker entirely out of context, the two sentences above are not even contiguous sentences. They're not even on the same page. The first sentence is on page 18 of the paper. And it just says that this particular implementation (the program called MS) is focused on certain facets, and for MS "no attempt is being made to emulate a full-scale inter-organization mail system" even though the entire point of the paper is how various email implementations are clearly replicating inter-organizational mail systems. The second sentence comes on page 21 (with lots in between) and just focuses on the fact that lots of users have very different requests and desires, and it's impossible to satisfy everyone -- and that it, alone, is beyond the scope of this project. He's not, as Ayyadurai implies, claiming that building an interoffice email system is impossible. He's claiming that creating a full system that satisfies absolutely everyone is impossible. However, he does make it clear that other components are being worked on, and when combined could create a more functional email system. Here's that part, back in context:
|
||||
|
||||
> To construct a fully-detailed and monolithic message processing environment requires a much larger effort than has been possible with MS. In addition, the fact that the system is intended for use in various organizational contexts and by users of differing expertise makes it almost impossible to build a system which responds to all users' needs. Consequently, important segments of a full message environment have received little or no attention and decisions have been made with the expectation that other Unix capabilities will be used to augment MS. For example, MS has fairly primitive data-base management filing and cataloging) facilities and message folders have been implemented in a way which allows them to be modified by programs, such as text editors, which access them directly, rather than through the message system.
|
||||
|
||||
From the actual source documents (which, again, Ayyadurai and his friends fail to link to and totally misrepresent), it's clear that all Crocker is saying is that no single system will satisfy everyone's current interests. He's not saying it's impossible to create an interoffice email system. He's just saying that lots of different people have lots of different needs for an interoffice email system, and for the team building MS, it would be too difficult to satisfy everyone's exact requests, so they're focusing on certain features, knowing others will add other components later. And, given that people are still working to improve upon email today, it seems that's still basically true.
|
||||
|
||||
Back to the rest of the paper, which actually does a tremendous job undermining basically all of Ayyadurai's claims (again, which suggests why no one names or links to the full paper) -- in the very first paragraph (again, this is prior to Ayyadurai doing anything) it talks about research for "computer software" for "electronic mail." Ooops. It goes on:
|
||||
|
||||
> This report describes the design of one such program--the "MS" message system. Early electronic mail systems have existed on the larger computers. MS incorporates and expands upon many of the functions and concepts of such systems within an integrated package...
|
||||
|
||||
In other words, the very paper that Ayyadurai and his friends insist prove that there was no email prior to 1978 talks in depth about a variety of email programs. Again, remember that this was written in 1977. This is not historical revisionism. It goes on:
|
||||
|
||||
> One of the earliest and most popular applications of the ARPANET computer communications network has been the transfer of text messages between people using different computers. This "electronic mail" capability was originally grafted onto existing informal facilities; however, they proved inadequate. A large network greatly expands the base of potential communicators; when coupled with the communication convenience of a message system, there results a considerable expansion to the list of features desired by users. Systems which have responded to these increased user needs have resided on medium- and large-scaled computers.
|
||||
|
||||
In other words, lots of folks are working on email systems. Ayyadurai tries to brush all those aside by saying that his actually included things like "folders." But again, Crocker's paper notes:
|
||||
|
||||
> Messages reside in file "folders" and may contain any number of fields, or "components."
|
||||
|
||||
It actually has a whole section on folders. It also shows some sample messages at the time, showing "to," "from," "cc," "subject," and "message" fields, showing that the very basics of interoffice mail (such as "cc" -- standing for carbon copy, which was a standard bit of interoffice mail) had already moved into email. Here's a screenshot (which you can click for a larger version):
|
||||
|
||||
[][15]
|
||||
|
||||
Ayyadurai has built up his entire reputation around the (entirely false) claim that he "invented" email. His bio, his Twitter feed and his website all position himself as having invented email. He didn't. It looks like he wrote an implementation of an email system in 1978, long after others were working on similar things. He may have added some nice features, including the "blind carbon copy/bcc" concept (Update: Nope, bcc was in a [1977 RFC][16]). He also appears to have potentially been ahead of others in making a full address book be a part of the email system. He may, in fact, be the first person who shortened "electronic mail" to "email" which is cool enough, and he'd have an interesting claim if that's all he claimed. Unfortunately, he's claiming much, much more than that. He's set up [an entire website][17] in which he accuses lots of folks, including Techdirt, of unfairly "attacking" him. He apparently believes that some of the attacks on him are [because][18] he spoke out against corruption in India. Or because people think only rich white people can invent stuff. None of that is accurate. There's a simple fact, and it's that Ayyadurai did not invent email.
|
||||
|
||||
He does not even attempt to counter any of the actual facts. The documents that are presented are misleading or out of context. He misrepresents what a copyright registration means. And his main "smoking gun," in support of his claim that people are trying to unfairly write him out of history, is presented in a misleading way, out of context, with two entirely separate sentences pushed together to pretend they say something they didn't.
|
||||
|
||||
He's clearly quite proud of the email software he wrote in 1978, and that's great. He should be. It may have made some incremental improvements on what else was already out there, but it is not inventing email. It's also entirely possible that he was wholly unaware of everything else that was out there. And, again, that's great. We've talked many times in the past about multiple people coming up with the same ideas around the same time. Ayyadurai should be quite proud of what he's done. But he's simply not telling the truth when he claims to have invented email. His website is full of accolades from the past, including his Westinghouse award (which is a prestigious award for high schoolers), his copyrights and his later patents. There are local newspaper clippings. That's all great. It reminds me of the folder my mother has on all the nice things that happened to me as a kid. But none of it means he invented email.
|
||||
|
||||
It's unclear why Huffington Post is publishing this ludicrous and disproven narrative. It's unclear why one of the biggest names in PR is involved in all of this, though you can take some guesses. But there are facts, and they include that "electronic mail" existed long before V.A. Shiva Ayyadurai wrote his program as a precocious teenager. Huffington Post is either not disclosing a paid-for series of posts (which would be a massive ethical breach) or they've been taken for a ride. Neither option speaks well of HuffPo and its journalistic integrity.
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://www.techdirt.com/articles/20140901/07280928386/huffpo-publishes-bizarre-misleading-factually-incorrect-multi-part-series-pretending-guy-invented-email-even-though-he-didnt.shtml
|
||||
|
||||
译者：[译者ID](https://github.com/译者ID)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创翻译，[Linux中国](http://linux.cn/) 荣誉推出
|
||||
|
||||
[1]:https://www.techdirt.com/articles/20120222/11132917842/how-guy-who-didnt-invent-email-got-memorialized-press-smithsonian-as-inventor-email.shtml
|
||||
[2]:http://www.huffingtonpost.com/news/the-history-of-email/
|
||||
[3]:http://www.nethistory.info/History%20of%20the%20Internet/email.html
|
||||
[4]:http://www.ir.bbn.com/~craig/email.pdf
|
||||
[5]:http://www.multicians.org/thvv/mail-history.html
|
||||
[6]:http://www.huffingtonpost.com/larry-weber/the-history-of-email-boy-who-invented-email_b_5690783.html
|
||||
[7]:http://en.wikipedia.org/wiki/Larry_Weber
|
||||
[8]:http://www.huffingtonpost.com/leslie-p-michelson/the-history-of-email-invention-of-email_b_5707913.html
|
||||
[9]:http://www.huffingtonpost.com/leslie-p-michelson/history-of-email-introduction_b_5726018.html
|
||||
[10]:http://www.huffingtonpost.com/robert-field/history-of-email-first-email-system_b_5722000.html
|
||||
[11]:http://www.huffingtonpost.com/2014/08/28/email-shiva-ayyadurai_n_5731606.html
|
||||
[12]:https://imgur.com/AscOfQh
|
||||
[13]:http://integrativesystems.org/board.asp
|
||||
[14]:http://www.amazon.com/gp/product/0684832674/ref=as_li_tl?ie=UTF8&camp=1789&creative=390957&creativeASIN=0684832674&linkCode=as2&tag=techdirtcom-20&linkId=OSP5B7BVSLAG5XNX
|
||||
[15]:https://imgur.com/KJW7BnA
|
||||
[16]:http://tools.ietf.org/html/rfc733
|
||||
[17]:http://www.inventorofemail.com/index.asp
|
||||
[18]:http://gizmodo.com/5888702/corruption-lies-and-death-threats-the-crazy-story-of-the-man-who-pretended-to-invent-email
|
||||
@ -0,0 +1,89 @@
|
||||
Drab Desktop? Try These 4 Beautiful Linux Icon Themes
|
||||
================================================================================
|
||||
**Ubuntu’s default icon theme [hasn’t changed much][1] in almost 5 years, save for the [odd new icon here and there][2]. If you’re tired of how it looks we’re going to show you a handful of gorgeous alternatives that will easily freshen things up.**
|
||||
|
||||
Do feel free to share links to your own favourite choices in the comments below.
|
||||
|
||||
### Captiva ###
|
||||
|
||||
|
||||
|
||||
Captiva icons, elementary folders and Moka GTK
|
||||
|
||||
Captiva is a relatively new icon theme that even the least bling-prone user can appreicate.
|
||||
|
||||
Made by DeviantArt user ~[bokehlicia][3], Captiva shuns the 2D flat look of many current icon themes for a softer, rounded look. The icons themselves have an almost material or textured look, with subtle drop shadows and a rich colour palette adding to the charm.
|
||||
|
||||
It doesn’t yet include a set of its own folder icons, and will fallback to using elementary (if available) or stock Ubuntu icons.
|
||||
|
||||
To install Captiva icons in Ubuntu 14.04 you can add the official PPA by opening a new Terminal window and enter the following commands:
|
||||
|
||||
sudo add-apt-repository ppa:captiva/ppa
|
||||
|
||||
sudo apt-get update && sudo apt-get install captiva-icon-theme
|
||||
|
||||
Or, if you’re not into software source cruft, by downloading the icon pack direct from the DeviantArt page. To install, extract the archive and move the resulting folder to the ‘.icons‘ directory in Home.
|
||||
|
||||
However you choose to install it, you’ll need to apply this (and every other theme on this list) using a utility like [Unity Tweak Tool][4].
|
||||
|
||||
- [Captiva Icon Theme on DeviantArt][5]
|
||||
|
||||
### Square Beam ###
|
||||
|
||||
|
||||
|
||||
Square Beam icon set with Orchis GTK
|
||||
|
||||
After something a bit angular? Check out Square Beam. It offers a more imposing visual statement than other sets on this list, with electric colours, harsh gradients and stark iconography. It claims to have more than 30,000 different icons (!) included (you’ll forgive me for not counting) so you should find very few gaps in its coverage.
|
||||
|
||||
- [Square Beam Icon Theme on GNOME-Look.org][6]
|
||||
|
||||
### Moka & Faba ###
|
||||
|
||||
|
||||
|
||||
Moka/Faba Mono Icons with Orchis GTK
|
||||
|
||||
The Moka icon suite needs little introduction. In fact, I’d wager a good number of you are already using it
|
||||
|
||||
With pastel colours, soft edges and simple icon artwork, Moka is a truly standout and comprehensive set of application icons. It’s best used with its sibling, Faba, which Moka will inherit so as to fill in all the system icons, folders, panel icons, etc. The combined result is…well, you’ve got eyes!
|
||||
|
||||
For full details on how to install on Ubuntu head over to the official project website, link below.
|
||||
|
||||
- [Download Moka and Faba Icon Themes][7]
|
||||
|
||||
### Compass ###
|
||||
|
||||
|
||||
|
||||
Compass Icon Theme with Numix Blue GTK
|
||||
|
||||
Last on our list, but by no means least, is Compass. This is a true adherent to the ’2D, two-tone’ UI design right now. It may not be as visually diverse as others on this list, but that’s the point. It’s consistent and uniform and all the better for it — just check out those folder icons!
|
||||
|
||||
It’s available to download and install manually through GNOME-Look (link below) or through the Nitrux Artwork PPA:
|
||||
|
||||
sudo add-apt-repository ppa:nitrux/nitrux-artwork
|
||||
|
||||
sudo apt-get update && sudo apt-get install compass-icon-theme
|
||||
|
||||
- [Compass Icon Theme on GNOME-Look.org][8]
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: http://www.omgubuntu.co.uk/2014/09/4-gorgeous-linux-icon-themes-download
|
||||
|
||||
作者：[Joey-Elijah Sneddon][a]
|
||||
译者：[译者ID](https://github.com/译者ID)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创翻译，[Linux中国](http://linux.cn/) 荣誉推出
|
||||
|
||||
[a]:https://plus.google.com/117485690627814051450/?rel=author
|
||||
[1]:http://www.omgubuntu.co.uk/2010/02/lucid-gets-new-icons-for-rhythmbox-ubuntuone-memenu-more
|
||||
[2]:http://www.omgubuntu.co.uk/2012/08/new-icon-theme-lands-in-lubuntu-12-10
|
||||
[3]:http://bokehlicia.deviantart.com/
|
||||
[4]:http://www.omgubuntu.co.uk/2014/06/unity-tweak-tool-0-7-development-download
|
||||
[5]:http://bokehlicia.deviantart.com/art/Captiva-Icon-Theme-479302805
|
||||
[6]:http://gnome-look.org/content/show.php/Square-Beam?content=165094
|
||||
[7]:http://mokaproject.com/moka-icon-theme/download/ubuntu/
|
||||
[8]:http://gnome-look.org/content/show.php/Compass?content=160629
|
||||
@ -0,0 +1,85 @@
|
||||
Why Do Some Old Programming Languages Never Die?
|
||||
================================================================================
|
||||
> We like what we already know.
|
||||
|
||||
|
||||
|
||||
Many of today’s most well-known programming languages are old enough to vote. PHP is 20. Python is 23. HTML is 21. Ruby and JavaScript are 19. C is a whopping 42 years old.
|
||||
|
||||
Nobody could have predicted this. Not even computer scientist [Brian Kernighan][1], co-author of the very first book on C, which is still being printed today. (The language itself was the work of Kernighan's [co-author Dennis Ritchie][2], who passed away in 2011.)
|
||||
|
||||
“I dimly recall a conversation early on with the editors, telling them that we’d sell something like 5,000 copies of the book,” Kernighan told me in a recent interview. “We managed to do better than that. I didn’t think students would still be using a version of it as a textbook in 2014.”
|
||||
|
||||
What’s especially remarkable about C's persistence is that Google developed a new language, Go, specifically to more efficiently solve the problems C solves now. Still, it’s hard for Kernighan to imagine something like Go outright killing C no matter how good it is.
|
||||
|
||||
“Most languages don’t die—or at least once they get to a certain level of acceptance they don’t die," he said. "C still solves certain problems better than anything else, so it sticks around.”
|
||||
|
||||
### Write What You Know ###
|
||||
|
||||
Why do some computer languages become more successful than others? Because developers choose to use them. That’s logical enough, but it gets tricky when you want to figure out why developers choose to use the languages they do.
|
||||
|
||||
Ari Rabkin and Leo Meyerovich are researchers from, respectively, Princeton and the University of California at Berkeley who devoted two years to answering just that question. Their resulting paper, [Empirical Analysis of Programming Language Adoption][3], describes their analysis of more than 200,000 Sourceforge projects and polling of more than 13,000 programmers.
|
||||
|
||||
Their main finding? Most of the time programmers choose programming languages they know.
|
||||
|
||||
“There are languages we use because we’ve always used them,” Rabkin told me. “For example, astronomers historically use IDL [Interactive Data Language] for their computer programs, not because it has special features for stars or anything, but because it has tremendous inertia. They have good programs they’ve built with it that they want to keep.”
|
||||
|
||||
In other words, it’s partly thanks to name recognition that established languages retain monumental staying power. Of course, that doesn’t mean popular languages don’t change. Rabkin noted that the C we use today is nothing like the language Kernighan first wrote about, which probably wouldn’t be fully compatible with a modern C compiler.
|
||||
|
||||
“There’s an old, relevant joke in which an engineer is asked which language he thinks people will be using in 30 years and he says, ‘I don’t know, but it’ll be called Fortran’,” Rabkin said. “Long-lived languages are not the same as how they were when they were designed in the '70s and '80s. People have mostly added things instead of removed because that doesn’t break backwards compatibility, but many features have been fixed.”
|
||||
|
||||
This backwards compatibility means that not only can programmers continue to use languages as they update programs, they also don’t need to go back and rewrite the oldest sections. That older ‘legacy code’ keeps languages around forever, but at a cost. As long as it’s there, people’s beliefs about a language will stick around, too.
|
||||
|
||||
### PHP: A Case Study Of A Long-Lived Language ###
|
||||
|
||||
Legacy code refers to programs—or portions of programs—written in outdated source code. Think, for instance, of key programming functions for a business or engineering project that are written in a language that no one supports. They still carry out their original purpose and are too difficult or expensive to rewrite in modern code, so they stick around, forcing programmers to turn handsprings to ensure they keep working even as other code changes around them.
|
||||
|
||||
Any language that's been around more than a few years has a legacy-code problem of some sort, and PHP is no exception. PHP is an interesting example because its legacy code is distinctly different from its modern code, in what proponents say—and critics admit—is a huge improvement.
|
||||
|
||||
Andi Gutmans is a co-inventor of the Zend Engine, the compiler that became standard by the time PHP4 came around. Gutmans said he and his partner originally wanted to improve PHP3, and were so successful that the original PHP inventor, Rasmus Lerdorf, joined their project. The result was a compiler for PHP4 and its successor, PHP5.
|
||||
|
||||
As a consequence, the PHP of today is quite different from its progenitor, the original PHP. Yet in Gutmans' view, the base of legacy code written in older PHP versions keeps alive old prejudices against the language—such as the notion that PHP is riddled with security holes, or that it can't "scale" to handle large computing tasks.
|
||||
|
||||
"People who criticize PHP are usually criticizing where it was in 1998,” he says. “These people are not up-to-date with where it is today. PHP today is a very mature ecosystem.”
|
||||
|
||||
Today, Gutmans says, the most important thing for him as a steward is to encouraging people to keep updating to the latest versions. “PHP is a big enough community now that you have big legacy code bases," he says. "But generally speaking, most of our communities are on PHP5.3 at minimum.”
|
||||
|
||||
The issue is that users never fully upgrade to the latest version of any language. It’s why many Python users are still using Python 2, released in 2000, instead of Python 3, released in 2008. Even after six years major users like Google still aren’t upgrading. There are a variety of reasons for this, but it made many developers wary about taking the plunge.
|
||||
|
||||
“Nothing ever dies," Rabkin says. "Any language with legacy code will last forever. Rewrites are expensive and if it’s not broke don’t fix it.”
|
||||
|
||||
### Developer Brains As Scarce Resources ###
|
||||
|
||||
Of course, developers aren’t choosing these languages merely to maintain pesky legacy code. Rabkin and Meyerovich found that when it comes to language preference, age is just a number. As Rabkin told me:
|
||||
|
||||
> A thing that really shocked us and that I think is important is that we grouped people by age and asked them how many languages they know. Our intuition was that it would gradually rise over time; it doesn’t. Twenty-five-year-olds and 45-year-olds all know about the same number of languages. This was constant through several rewordings of the question. Your chance of knowing a given language does not vary with your age.
|
||||
|
||||
In other words, it’s not just old developers who cling to the classics; young programmers are also discovering and adopting old languages for the first time. That could be because the languages have interesting libraries and features, or because the communities these developers are a part of have adopted the language as a group.
|
||||
|
||||
“There’s a fixed amount of programmer attention in the world,” said Rabkin. “If a language delivers enough distinctive value, people will learn it and use it. If the people you exchange code and knowledge with you share a language, you’ll want to learn it. So for example, as long as those libraries are Python libraries and community expertise is Python experience, Python will do well.”
|
||||
|
||||
Communities are a huge factor in how languages do, the researchers discovered. While there's not much difference between high level languages like Python and Ruby, for example, programmers are prone to develop strong feelings about the superiority of one over the other.
|
||||
|
||||
“Rails didn’t have to be written in Ruby, but since it was, it proves there were social factors at work,” Rabkin says. “For example, the thing that resurrected Objective-C is that the Apple engineering team said, ‘Let’s use this.’ They didn’t have to pick it.”
|
||||
|
||||
Through social influence and legacy code, our oldest and most popular computer languages have powerful inertia. How could Go surpass C? If the right people and companies say it ought to.
|
||||
|
||||
“It comes down to who is better at evangelizing a language,” says Rabkin.
|
||||
|
||||
Lead image by [Blake Patterson][4]
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: http://readwrite.com/2014/09/02/programming-language-coding-lifetime
|
||||
|
||||
作者：[Lauren Orsini][a]
|
||||
译者：[译者ID](https://github.com/译者ID)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创翻译，[Linux中国](http://linux.cn/) 荣誉推出
|
||||
|
||||
[a]:http://readwrite.com/author/lauren-orsini
|
||||
[1]:http://en.wikipedia.org/wiki/Brian_Kernighan
|
||||
[2]:http://en.wikipedia.org/wiki/Dennis_Ritchie
|
||||
[3]:http://asrabkin.bitbucket.org/papers/oopsla13.pdf
|
||||
[4]:https://www.flickr.com/photos/blakespot/2444037775/
|
||||
@ -0,0 +1,73 @@
|
||||
With Apple Watch Unveiled, Could an Ubuntu Smartwatch Be Next?
|
||||
================================================================================
|
||||
**Apple today confirmed its long-rumoured foray into the wearable computing market with the launch of ‘Apple Watch’.**
|
||||
|
||||
|
||||
|
||||
Ubuntu Smartwatch – good idea?
|
||||
|
||||
Backed by a robust set of features, hardware solutions and app partnerships, the wrist mounted device is being heralded by the company as “a new chapter in the relationship people have with technology.”
|
||||
|
||||
But does its arrival, and the uptick in consumer interest it will likely bring, mean Ubuntu should follow with a version of Ubuntu for smartwatches?
|
||||
|
||||
### Big Hand Is On Success ###
|
||||
|
||||
Apple joins the fast growing smart-watch sector at just about the right time. The boundaries of what a wrist-mounted computer can and should do are not yet set in stone. Bad design, poor user interfaces, and weak arguments for the usefulness of wearable technology to mainstream users has seen the hardware category remains sufficiently impressionable — a factor that has allowed Cupertino to take its time with the Apple Watch.
|
||||
|
||||
> ‘More than 22 million smartwatches will be sold this year, say analysts’
|
||||
|
||||
Sales of wearables, including fitness trackers, last year were just shy of 10 million units worldwide. This year the number of devices analysts expect to see shifted will pass 22 million — and that’s without the Apple Watch, which doesn’t hit retail until early 2015.
|
||||
|
||||
It’s easy to see where the growth is going to come from. The IFA 2014 tradeshow held in Berlin at the start of September played host to a swathe of new wearables from major OEMs, including Sony and ASUS. Most are running Google’s newly released Android Wear platform.
|
||||
|
||||
A more mature offering, Android Wear debunks the novelty argument often associated with the form factor to present a consistent and convincing user scenario. Though, as with the new Apple Watch, it is one tightly hinging on an existing smartphone ecosystem.
|
||||
|
||||
Whether it’s a use case a wrist-mounted version Ubuntu can match isn’t (yet) clear.
|
||||
|
||||
#### ‘No Plans for an Ubuntu Smartwatch’ ####
|
||||
|
||||
The versatility of the Ubuntu OS combined with the stringent vision for a multi-device and convergent future has already seen Canonical target smart TVs, tablets and smartphones. Mir, the company’s homegrown display server, was even created to power interfaces on screens of all sizes (though admittedly not 1.5″ ones!).
|
||||
|
||||
At the start of this year then-Canonical community manager Jono Bacon was asked whether there were plans for an Ubuntu watch. Offering his opinion on the subject, Bacon mused: “adding another form factor to the [ubuntu touch] roadmap would only slow things down”.
|
||||
|
||||
As the two year anniversary of the Ubuntu Phone announcement approaches, it’s hard not to agree with him.
|
||||
|
||||
### Tick, Tock, Hedge-Your-Bets O’Clock ###
|
||||
|
||||
But all hope is not lost. In a [press call a few months later][1] Ubuntu founder Mark Shuttleworth mentioned wearable technologies in the same breath as the company’s plans for TVs, tablets and smartphones, saying:
|
||||
|
||||
> “Ubuntu is really unique in that it has this beautiful design on the phone, but it’s also designed at the same time to feed all of those other ecosystems, from wearables to the PC.”
|
||||
|
||||
While far from concrete confirmation, it serves as a pointer; an optimistic hedge in that direction.
|
||||
|
||||
#### Not likely — and here’s why ####
|
||||
|
||||
Canonical is not averse to entering markets with entrenched monopolies. In fact, it’s in the DNA of the company — RHEL on servers, Windows on desktops, Android on smartphones…
|
||||
|
||||
Ubuntu for devices is built as such that it could be expended to and adapted to run on smaller screens, possible even those as small as a watch face. When the common code base is in place for phone, tablet, desktop and TV I’d be surprised if we didn’t see some sort of effort in this direction from the community.
|
||||
|
||||
But reason why I don’t think it’s likely to happen from Canonical’s side, at least not yet, is an echo of Jono Bacon’s personal thoughts earlier this year: time and effort.
|
||||
|
||||
Tim Cook said in his keynote: “*We didn’t take the iPhone and shrink the user interface and strap it on your wrist.*” It’s an obvious statement. Designing a UI and UX model for such a small screen; working through interaction methodologies; complimenting hardware and input models isn’t a simple task.
|
||||
|
||||
Wearable technology is still a nascent market. At this stage Canonical would be wasting development, design and business time in pursuing it. Any benefits would be outweighed by the loss in other, more pressing areas.
|
||||
|
||||
Playing the longer game, waiting it out to see where other efforts succeed and fail, is the harder route, but the one better suited to Ubuntu as it stands today. It’s better for Canonical to focus energies on existing products (which some argue are already arriving late) before throwing newer ones out ahead of them.
|
||||
|
||||
**For an idea of what an Ubuntu smartwatch could be like hit play on the following video which shows an interactive Unity themed skin for the Tizen powered Samsung Galaxy Gear smartwatch.**
|
||||
|
||||
注：youtube视频，发布的时候不行做个链接吧
|
||||
<iframe width="750" height="563" frameborder="0" allowfullscreen="" src="https://www.youtube.com/embed/8Zf5dktXzEs?feature=oembed"></iframe>
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: http://www.omgubuntu.co.uk/2014/09/ubuntu-smartwatch-apple-iwatch
|
||||
|
||||
作者：[Joey-Elijah Sneddon][a]
|
||||
译者：[译者ID](https://github.com/译者ID)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创翻译，[Linux中国](http://linux.cn/) 荣誉推出
|
||||
|
||||
[a]:https://plus.google.com/117485690627814051450/?rel=author
|
||||
[1]:http://www.omgubuntu.co.uk/2014/03/ubuntu-tablets-coming-year
|
||||
@ -1,90 +0,0 @@
|
||||
alim0x translating
|
||||
|
||||
The history of Android
|
||||
================================================================================
|
||||
|
||||
The main alarm screen, setting an alarm, the calculator, and the calculator advanced functions screen.
|
||||
Photo by Ron Amadeo
|
||||
|
||||
Android 0.9 gave us the first look at the Alarm and Calculator apps. The alarm app featured a plain analog clock with a scrolling list of alarms on the bottom. Rather than some kind of on/off switch, alarms were set with a checkbox. Alarms could be set to repeat at certain days of the week, and there was a whole list of selectable, unique alarm sounds.
|
||||
|
||||
The calculator was an all-black app with glossy, round buttons. Through the menu, it was possible to bring up an additional panel with advanced functions. Again consistency was not Google’s strong suit. The on-press highlight on the pi key was red—in the rest of Android 0.9, the on-press highlight was usually orange. In fact, everything used in the calculator was 100 percent custom artwork limited to only the calculator.
|
||||
|
||||
|
||||
Google Maps with the menu open and the new directions interface.
|
||||
Photo by Ron Amadeo
|
||||
|
||||
Google Maps actually worked in Android 0.9—the client could connect to the Google Maps server and pull down tiles. (For our images, remember that Google Maps is cloud based. Even the oldest of clients will still pull down modern map tiles, so ignore the actual map tiles pictured.) The Maps menu got the same all-gray treatment as the browser menu, and the zoom controls were the same as the browser too. The all-important "My Location" button finally arrived, meaning this version of Maps supported GPS location.
|
||||
|
||||
The directions interface was revamped. The weird speech bubbles with misaligned plus buttons were swapped out for a more communicative bookmark icon, the swap field button moved to the left, and the go button was now labeled "Route."
|
||||
|
||||
|
||||
The Google Maps layers selector, search history, and the now-broken street view mode.
|
||||
Photo by Ron Amadeo
|
||||
|
||||
"Layers" was renamed "Map Mode" and switched to a radio button list. Only one map type was available at a time—you couldn't see traffic on the satellite view, for instance. Buried in the menu was a hastily thrown together search history screen. History seemed like only a proof-of-concept, with giant, blurry search icons that rammed up against search terms on a transparent background.
|
||||
|
||||
Street View used to be a separate app (although it was never made available to the public), but in 0.9 it was integrated into Google Maps as a Map Mode. You could drag the little pegman around, and it would display a popup bubble showing the thumbnail for Street View. Tapping on the thumbnail would launch Street View for that area. At the time, Street View showed nothing other than a scrollable 360 degree image—there was no UI on the interface at all.
|
||||
|
||||
|
||||
Our first look at the Google Maps search interface. These shots show the search bar, the results in a list, the results in a map, and a business page.
|
||||
Photo by Ron Amadeo
|
||||
|
||||
Android 0.9 also gave us our first look at the texting app, called "Messaging." Like many early Android designs, Messaging wasn't sure if it should be a dark app or a light app. The first visible screen was the message list, a stark black void of nothingness that looked like it was built on top of the settings interface. After tapping on “New Message" or one of the existing conversations, though, you were taken to a white and blue scrolling list of text messages. The two connected screens couldn’t be more different.
|
||||
|
||||
|
||||
The SMS app’s chat window, attachment screen, chat list, and setting.
|
||||
Photo by Ron Amadeo
|
||||
|
||||
Messaging supported a range of attachments: you could tack on pictures, audio, or a slideshow to your message. Pictures and audio could be recorded on the fly or pulled from phone storage. Another odd UI choice was that Android already had an established icon for almost everything in the attach menu, but Messaging used all-custom art instead.
|
||||
|
||||
Messaging was one of the first apps to have its own settings screen. Users could request read and delivery reports and set download preferences.
|
||||
|
||||
|
||||
The slideshow creator. The right picture shows the menu options.
|
||||
Photo by Ron Amadeo
|
||||
|
||||
The "slideshow" option in attachments would actually launch a fully featured slideshow creator. You could add pictures, choose the slide order, add music, change the duration of each slide, and add text. This was complicated enough to have its own app icon, but amazingly it was buried in the menu of the SMS app. This was one of the few Android apps that was completely unusable in portrait mode—the only way to see the picture and the controls was in landscape. Strangely, it would still rotate to portrait, but the layout just became a train wreck.
|
||||
|
||||
|
||||
The Music player’s main navigation page, song list, album list, and “now playing" screen.
|
||||
Photo by Ron Amadeo
|
||||
|
||||
Android 0.9 was the first to bring a music app to Android. The primary screen was mostly just four big, chunky navigation buttons that would take you to each music view. At the bottom of the app was a "now playing" bar that only contained the track name, artist, and a play/pause button. The song list had only a bare minimum interface, only showing the song name, artist, album and runtime. Album art was the only hope of seeing any color in this app. It was displayed as a tiny thumbnail in the album view and as a big, quarter-screen image in the Now Playing view.
|
||||
|
||||
Like most parts of Android in this era, the interface may not have been much to look at, but the features were there. The Now Playing screen had a button for a playlist queue that allowed you to drag songs around, shuffle, repeat, search, and choose background audio.
|
||||
|
||||
|
||||
The “Pictures" all album view, individual album view, and a single picture view.
|
||||
Photo by Ron Amadeo
|
||||
|
||||
The photo gallery was simply called "Pictures." The initial view showed all your albums. The two default ones were "Camera" and a large unified album called "All pictures." The thumbnail for each album was made up of a 2x2 grid of pictures, and every picture got a thick, white frame.
|
||||
|
||||
The individual album view was about what you would expect: a scrolling grid of pictures. You couldn't swipe through individual pictures—large left and right arrows flanking the individual picture had to be tapped on to move through an album. There was no pinch-zoom either; you had to zoom in and out with buttons.
|
||||
|
||||
|
||||
Picture editing! These screenshots show an open menu, the “more" menu, cropping, and the settings.
|
||||
Photo by Ron Amadeo
|
||||
|
||||
"Pictures" looked simple until you hit the menu button and suddenly accessed a myriad of options. Pictures could be cropped, rotated, deleted, or set as a wallpaper or contact icon. Like the browser, all of this was accomplished through a clumsy double-menu system. But again, why do two related menus look completely different?
|
||||
|
||||
Android 0.9 came out a mere two months before the first commercial release of Android. That was just enough time for app developers to make sure their apps worked—and for Google to do some testing and bug squashing before the big release.
|
||||
|
||||
----------
|
||||
|
||||
|
||||
|
||||
[Ron Amadeo][a] / Ron is the Reviews Editor at Ars Technica, where he specializes in Android OS and Google products. He is always on the hunt for a new gadget and loves to rip things apart to see how they work.
|
||||
|
||||
[@RonAmadeo][t]
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: http://arstechnica.com/gadgets/2014/06/building-android-a-40000-word-history-of-googles-mobile-os/5/
|
||||
|
||||
译者：[译者ID](https://github.com/译者ID) 校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创翻译，[Linux中国](http://linux.cn/) 荣誉推出
|
||||
|
||||
[a]:http://arstechnica.com/author/ronamadeo
|
||||
[t]:https://twitter.com/RonAmadeo
|
||||
@ -1,38 +0,0 @@
|
||||
Linux FAQs with Answers--How to check the last time system was rebooted on Linux
|
||||
================================================================================
|
||||
> **Question**: Is there a way to quickly check how long a Linux system has been running? That is, how can I find out the last time a Linux system was rebooted?
|
||||
|
||||
There are several ways to find out the last system reboot time,
|
||||
|
||||
### Method One ###
|
||||
|
||||
The first method is to use last command.
|
||||
|
||||
$ last reboot
|
||||
|
||||
|
||||
|
||||
This command actually shows system uptime for the last few days. Originally the last command is designed to show login history of a particular user. In Linux, a special "pseudo user" named reboot automatically logs in to the system right after the system has rebooted. Thus by checking the login history of reboot user, you can check the last reboot time.
|
||||
|
||||
### Method Two ###
|
||||
|
||||
Another command to check the time of last system boot is to use who command with '-b' option.
|
||||
|
||||
$ who -b
|
||||
|
||||
### Method Three ###
|
||||
|
||||
You can also use uptime command to deduce last reboot time. The uptime command shows you the current time, as well as how long the system has been running. From this information, you can calculate the time when the system was last booted.
|
||||
|
||||
$ uptime
|
||||
|
||||
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: http://ask.xmodulo.com/check-last-time-system-rebooted-linux.html
|
||||
|
||||
译者：[译者ID](https://github.com/译者ID)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创翻译，[Linux中国](http://linux.cn/) 荣誉推出
|
||||
@ -1,49 +0,0 @@
|
||||
Linux FAQs with Answers--How to fix “X11 forwarding request failed on channel 0″
|
||||
================================================================================
|
||||
> **Question**: When I tried to SSH to a remote host with X11 forwarding option, I got "X11 forwarding request failed on channel 0" error after logging in. Why am I getting this error, and how can I fix this problem?
|
||||
|
||||
|
||||
|
||||
First of all, we assume that you already enabled [X11 forwarding over SSH][1] properly.
|
||||
|
||||
If you are getting "X11 forwarding request failed on channel 0" message upon SSH login, there could be several reasons. Solutions vary as well.
|
||||
|
||||
### Solution One ###
|
||||
|
||||
For security reason, OpenSSH server, by default, binds X11 forwarding server to the local loopback address, and sets the hostname in DISPLAY environment variable to "localhost". Under this setup, some X11 clients cannot handle X11 forwarding properly, which causes the reported error. To fix this problem, add the following line in /etc/ssh/sshd_config file, which will let X11 forwarding server bind on the wild card address.
|
||||
|
||||
$ sudo vi /etc/ssh/sshd_config
|
||||
|
||||
----------
|
||||
|
||||
X11Forwarding yes
|
||||
X11UseLocalhost no
|
||||
|
||||
Restart SSH server to activate the change:
|
||||
|
||||
$ sudo /etc/init.d/ssh restart (Debian 6, Ubuntu or Linux Mint)
|
||||
$ sudo systemctl restart ssh.service (Debian 7, CentOS/RHEL 7, Fedora)
|
||||
$ sudo service sshd restart (CentOS/RHEL 6)
|
||||
|
||||
### Solution Two ###
|
||||
|
||||
The broken X11 forwarding error may also happen if the remote host where SSH server is running has IPv6 disabled. To fix the error in this case, open /etc/ssh/sshd_config file, and uncomment "AddressFamily all" (if any). Then add the following line. This will force SSH server to use IPv4 only, but not IPv6.
|
||||
|
||||
$ sudo vi /etc/ssh/sshd_config
|
||||
|
||||
----------
|
||||
|
||||
AddressFamily inet
|
||||
|
||||
Again, restart SSH server to finalize the change.
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: http://ask.xmodulo.com/fix-broken-x11-forwarding-ssh.html
|
||||
|
||||
译者：[译者ID](https://github.com/译者ID)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创翻译，[Linux中国](http://linux.cn/) 荣誉推出
|
||||
|
||||
[1]:http://xmodulo.com/2012/11/how-to-enable-x11-forwarding-using-ssh.html
|
||||
@ -1,42 +0,0 @@
|
||||
Linux FAQs with Answers--How to set a static MAC address on VMware ESXi virtual machine
|
||||
================================================================================
|
||||
> **Question**: I want to assign a static MAC address to a virtual machine (VM) on VMware ESXi. However, when I attempt to start a VM with a static MAC address, the VM fails to start and throws an error "00:0c:29:1f:4a:ab is not an allowed static Ethernet address. It conflicts with VMware reserved MACs". How can I set a static MAC address on VMware ESXi VMs?
|
||||
|
||||
When you create a VM on VMware ESXi, each network interface of the VM is assigned a dynamically generated MAC address. If you want to change this default behavior and assign a static MAC address to your VM, here is how to do it.
|
||||
|
||||
|
||||
|
||||
As you can see above, VMware's vSphere GUI client already has a menu for setting a static MAC address for a VM. However, this GUI-based method only allows you to choose a static MAC address from **00:50:56:xx:xx:xx**, which is VMware-reserved MAC address range. If you attempt to set any arbitrary MAC address outside this MAC range, you will fail to launch the VM, and get the following error.
|
||||
|
||||
|
||||
|
||||
Then what if I want to assign any arbitrary MAC address to a VM?
|
||||
|
||||
Fortunately, there is a workaround to this limitation. The solution is, instead of using vSphere GUI client, editing .vmx file of your VM directly, after logging in to the ESXi host.
|
||||
|
||||
First, turn off the VM to which you want to assign a static MAC address.
|
||||
|
||||
[Enable SSH access to your ESXi host][1] if you haven't done it already. Then log in to the ESXi host via SSH.
|
||||
|
||||
Move to the directory where your VM's .vmx file is located:
|
||||
|
||||
# cd vmfs/volumes/datastore1/[name-of-vm]
|
||||
|
||||
Open .vmx file with a text editor, and add the following fields. Replace the MAC address field with your own.
|
||||
|
||||
ethernet0.addressType = "static"
|
||||
ethernet0.checkMACAddress = "false"
|
||||
ethernet0.address = "00:0c:29:1f:4b:ac"
|
||||
|
||||
Now you should be able to launch a VM with the static MAC address you defined in .vmx file.
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: http://ask.xmodulo.com/static-mac-address-vmware-esxi-virtual-machine.html
|
||||
|
||||
译者：[译者ID](https://github.com/译者ID)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创翻译，[Linux中国](http://linux.cn/) 荣誉推出
|
||||
|
||||
[1]:http://ask.xmodulo.com/enable-ssh-remote-access-vmware-esxi5.html
|
||||
Some files were not shown because too many files have changed in this diff Show More
Loading…
Reference in New Issue
Block a user