mirror of
https://github.com/LCTT/TranslateProject.git
synced 2025-01-16 22:42:21 +08:00
Merge remote-tracking branch 'LCTT/master'
This commit is contained in:
wxy
commit
2af66526bf
@ -0,0 +1,177 @@
|
||||
如何在 Linux 中查找最大的 10 个文件
|
||||
======
|
||||
|
||||
当系统的磁盘空间不足时，您可能会使用 `df`、`du` 或 `ncdu` 命令进行检查，但这些命令只会显示当前目录的文件，并不会显示整个系统范围的文件。
|
||||
|
||||
您得花费大量的时间才能用上述命令获取系统中最大的文件，因为要进入到每个目录重复运行上述命令。
|
||||
|
||||
这种方法比较麻烦，也并不恰当。
|
||||
|
||||
如果是这样，那么该如何在 Linux 中找到最大的 10 个文件呢？
|
||||
|
||||
我在谷歌上搜索了很久，却没发现类似的文章，我反而看到了很多关于列出当前目录中最大的 10 个文件的文章。所以，我希望这篇文章对那些有类似需求的人有所帮助。
|
||||
|
||||
本教程中，我们将教您如何使用以下四种方法在 Linux 系统中查找最大的前 10 个文件。
|
||||
|
||||
### 方法 1
|
||||
|
||||
在 Linux 中没有特定的命令可以直接执行此操作，因此我们需要将多个命令结合使用。
|
||||
|
||||
```
|
||||
# find / -type f -print0 | xargs -0 du -h | sort -rh | head -n 10
|
||||
|
||||
1.4G /swapfile
|
||||
1.1G /home/magi/ubuntu-17.04-desktop-amd64.iso
|
||||
564M /home/magi/.gdfuse/magi/cache/0B5nso_FPaZFqTFU0XzkzUlJUZzA
|
||||
378M /home/magi/.gdfuse/magi/cache/0B5nso_FPaZFqeldzUmhPeC03Zm8
|
||||
377M /home/magi/.gdfuse/magi/cache/0B5nso_FPaZFqRGd4V0VrOXM4YVU
|
||||
100M /usr/lib/x86_64-linux-gnu/libOxideQtCore.so.0
|
||||
93M /usr/lib/firefox/libxul.so
|
||||
84M /var/lib/snapd/snaps/core_3604.snap
|
||||
84M /var/lib/snapd/snaps/core_3440.snap
|
||||
84M /var/lib/snapd/snaps/core_3247.snap
|
||||
```
|
||||
|
||||
详解：
|
||||
|
||||
- `find`：在目录结构中搜索文件的命令
|
||||
- `/`：在整个系统（从根目录开始）中查找
|
||||
- `-type`：指定文件类型
|
||||
- `f`：普通文件
|
||||
- `-print0`：在标准输出显示完整的文件名，其后跟一个空字符（null）
|
||||
- `|`：控制操作符，将一条命令的输出传递给下一个命令以供进一步处理
|
||||
- `xargs`：将标准输入转换成命令行参数的命令
|
||||
- `-0`：以空字符（null）而不是空白字符（LCTT 译者注：即空格、制表符和换行）来分割记录
|
||||
- `du -h`：以可读格式计算磁盘空间使用情况的命令
|
||||
- `sort`：对文本文件进行排序的命令
|
||||
- `-r`：反转结果
|
||||
- `-h`：用可读格式打印输出
|
||||
- `head`：输出文件开头部分的命令
|
||||
- `n -10`：打印前 10 个文件
|
||||
|
||||
### 方法 2
|
||||
|
||||
这是查找 Linux 系统中最大的前 10 个文件的另一种方法。我们依然使用多个命令共同完成这个任务。
|
||||
|
||||
```
|
||||
# find / -type f -exec du -Sh {} + | sort -rh | head -n 10
|
||||
|
||||
1.4G /swapfile
|
||||
1.1G /home/magi/ubuntu-17.04-desktop-amd64.iso
|
||||
564M /home/magi/.gdfuse/magi/cache/0B5nso_FPaZFqTFU0XzkzUlJUZzA
|
||||
378M /home/magi/.gdfuse/magi/cache/0B5nso_FPaZFqeldzUmhPeC03Zm8
|
||||
377M /home/magi/.gdfuse/magi/cache/0B5nso_FPaZFqRGd4V0VrOXM4YVU
|
||||
100M /usr/lib/x86_64-linux-gnu/libOxideQtCore.so.0
|
||||
93M /usr/lib/firefox/libxul.so
|
||||
84M /var/lib/snapd/snaps/core_3604.snap
|
||||
84M /var/lib/snapd/snaps/core_3440.snap
|
||||
84M /var/lib/snapd/snaps/core_3247.snap
|
||||
```
|
||||
|
||||
详解：
|
||||
|
||||
- `find`：在目录结构中搜索文件的命令
|
||||
- `/`：在整个系统（从根目录开始）中查找
|
||||
- `-type`：指定文件类型
|
||||
- `f`：普通文件
|
||||
- `-exec`：在所选文件上运行指定命令
|
||||
- `du`：计算文件占用的磁盘空间的命令
|
||||
- `-S`：不包含子目录的大小
|
||||
- `-h`：以可读格式打印
|
||||
- `{}`：递归地查找目录，统计每个文件占用的磁盘空间
|
||||
- `|`：控制操作符，将一条命令的输出传递给下一个命令以供进一步处理
|
||||
- `sort`：对文本文件进行按行排序的命令
|
||||
- `-r`：反转结果
|
||||
- `-h`：用可读格式打印输出
|
||||
- `head`：输出文件开头部分的命令
|
||||
- `n -10`：打印前 10 个文件
|
||||
|
||||
### 方法 3
|
||||
|
||||
这里介绍另一种在 Linux 系统中搜索最大的前 10 个文件的方法。
|
||||
|
||||
```
|
||||
# find / -type f -print0 | xargs -0 du | sort -n | tail -10 | cut -f2 | xargs -I{} du -sh {}
|
||||
|
||||
84M /var/lib/snapd/snaps/core_3247.snap
|
||||
84M /var/lib/snapd/snaps/core_3440.snap
|
||||
84M /var/lib/snapd/snaps/core_3604.snap
|
||||
93M /usr/lib/firefox/libxul.so
|
||||
100M /usr/lib/x86_64-linux-gnu/libOxideQtCore.so.0
|
||||
377M /home/magi/.gdfuse/magi/cache/0B5nso_FPaZFqRGd4V0VrOXM4YVU
|
||||
378M /home/magi/.gdfuse/magi/cache/0B5nso_FPaZFqeldzUmhPeC03Zm8
|
||||
564M /home/magi/.gdfuse/magi/cache/0B5nso_FPaZFqTFU0XzkzUlJUZzA
|
||||
1.1G /home/magi/ubuntu-17.04-desktop-amd64.iso
|
||||
1.4G /swapfile
|
||||
```
|
||||
|
||||
详解：
|
||||
|
||||
- `find`：在目录结构中搜索文件的命令
|
||||
- `/`：在整个系统（从根目录开始）中查找
|
||||
- `-type`：指定文件类型
|
||||
- `f`：普通文件
|
||||
- `-print0`：输出完整的文件名，其后跟一个空字符（null）
|
||||
- `|`：控制操作符，将一条命令的输出传递给下一个命令以供进一步处理
|
||||
- `xargs`：将标准输入转换成命令行参数的命令
|
||||
- `-0`：以空字符（null）而不是空白字符来分割记录
|
||||
- `du`：计算文件占用的磁盘空间的命令
|
||||
- `sort`：对文本文件进行按行排序的命令
|
||||
- `-n`：根据数字大小进行比较
|
||||
- `tail -10`：输出文件结尾部分的命令（最后 10 个文件）
|
||||
- `cut`：从每行删除特定部分的命令
|
||||
- `-f2`：只选择特定字段值
|
||||
- `-I{}`：将初始参数中出现的每个替换字符串都替换为从标准输入读取的名称
|
||||
- `-s`：仅显示每个参数的总和
|
||||
- `-h`：用可读格式打印输出
|
||||
- `{}`：递归地查找目录，统计每个文件占用的磁盘空间
|
||||
|
||||
### 方法 4
|
||||
|
||||
还有一种在 Linux 系统中查找最大的前 10 个文件的方法。
|
||||
|
||||
```
|
||||
# find / -type f -ls | sort -k 7 -r -n | head -10 | column -t | awk '{print $7,$11}'
|
||||
|
||||
1494845440 /swapfile
|
||||
1085984380 /home/magi/ubuntu-17.04-desktop-amd64.iso
|
||||
591003648 /home/magi/.gdfuse/magi/cache/0B5nso_FPaZFqTFU0XzkzUlJUZzA
|
||||
395770383 /home/magi/.gdfuse/magi/cache/0B5nso_FPaZFqeldzUmhPeC03Zm8
|
||||
394891761 /home/magi/.gdfuse/magi/cache/0B5nso_FPaZFqRGd4V0VrOXM4YVU
|
||||
103999072 /usr/lib/x86_64-linux-gnu/libOxideQtCore.so.0
|
||||
97356256 /usr/lib/firefox/libxul.so
|
||||
87896064 /var/lib/snapd/snaps/core_3604.snap
|
||||
87793664 /var/lib/snapd/snaps/core_3440.snap
|
||||
87089152 /var/lib/snapd/snaps/core_3247.snap
|
||||
```
|
||||
|
||||
详解：
|
||||
|
||||
- `find`：在目录结构中搜索文件的命令
|
||||
- `/`：在整个系统（从根目录开始）中查找
|
||||
- `-type`：指定文件类型
|
||||
- `f`：普通文件
|
||||
- `-ls`：在标准输出中以 `ls -dils` 的格式列出当前文件
|
||||
- `|`：控制操作符，将一条命令的输出传递给下一个命令以供进一步处理
|
||||
- `sort`：对文本文件进行按行排序的命令
|
||||
- `-k`：按指定列进行排序
|
||||
- `-r`：反转结果
|
||||
- `-n`：根据数字大小进行比较
|
||||
- `head`：输出文件开头部分的命令
|
||||
- `-10`：打印前 10 个文件
|
||||
- `column`：将其输入格式化为多列的命令
|
||||
- `-t`：确定输入包含的列数并创建一个表
|
||||
- `awk`：模式扫描和处理语言
|
||||
- `'{print $7,$11}'`：只打印指定的列
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://www.2daygeek.com/how-to-find-search-check-print-top-10-largest-biggest-files-in-linux/
|
||||
|
||||
作者：[Magesh Maruthamuthu][a]
|
||||
译者：[jessie-pang](https://github.com/jessie-pang)
|
||||
校对：[wxy](https://github.com/wxy)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
||||
[a]:https://www.2daygeek.com/author/magesh/
|
||||
107
published/20180201 How I coined the term open source.md
Normal file
107
published/20180201 How I coined the term open source.md
Normal file
@ -0,0 +1,107 @@
|
||||
我是如何创造“开源”这个词的
|
||||
============================================================
|
||||
|
||||
|
||||
> Christine Peterson 最终公开讲述了二十年前那决定命运的一天。
|
||||
|
||||
|
||||
|
||||
图片来自: opensource.com
|
||||
|
||||
2 月 3 日是术语“<ruby>[开源软件][6]<rt>open source software</rt></ruby>”创立 20 周年的纪念日。由于开源软件渐受欢迎，并且为这个时代强有力的重要变革提供了动力，我们仔细反思了它的初生到崛起。
|
||||
|
||||
我是 “开源软件” 这个词的始作俑者，它是我在<ruby>前瞻协会<rt>Foresight Institute</rt></ruby>担任执行董事时提出的。我不像其它人是个软件开发者，所以感谢 Linux 程序员 Todd Anderson 对这个术语的支持并将它提交小组讨论。
|
||||
|
||||
这是我对于它如何想到的，如何提出的，以及后续影响的记叙。当然，还有一些有关该术语的其它记叙，例如 Eric Raymond 和 Richard Stallman 写的，而我的，则写于 2006 年 1 月 2 日。
|
||||
|
||||
但直到今天，我才公诸于世。
|
||||
|
||||
* * *
|
||||
|
||||
推行术语“开源软件”是特别为了让新手和商业人士更加理解这个领域，对它的推广被认为对于更广泛的用户社区很有必要。早期的称呼“<ruby>自由软件<rt>free software</rt></ruby>”不适用并非是因为含有政治意义，而是对于新手来说会误导关注于价格。所以需要一个关注于关键的源代码，而且不会让新用户混淆概念的术语。第一个在正确时间出现并且满足这些要求的术语被迅速接受了：<ruby>开源<rt>open source</rt></ruby>。
|
||||
|
||||
这个术语很长一段时间被用在“情报”（即间谍活动）活动中，但据我所知，确实在 1998 年以前软件领域从未使用过该术语。下面这个就是讲述了术语“开源软件”如何流行起来，并且变成了一项产业和一场运动名称的故事。
|
||||
|
||||
### 计算机安全会议
|
||||
|
||||
在 1997 年的晚些时候，<ruby>前瞻协会<rt>Foresight Institute</rt></ruby>开始举办周会讨论计算机安全问题。这个协会是一个非盈利性智库，它专注于纳米技术和人工智能，而二者的安全性及可靠性取决于软件安全。我们确定了自由软件是一个改进软件安全可靠性且具有发展前景的方法，并将寻找推动它的方式。 对自由软件的兴趣开始在编程社区外开始增长，而且越来越清晰，一个改变世界的机会正在来临。然而，该怎么做我们并不清楚，因为我们当时正在摸索中。
|
||||
|
||||
在这些会议中，由于“容易混淆”的因素，我们讨论了采用一个新术语的必要性。观点主要如下：对于那些新接触“自由软件”的人会把 “free” 当成了价格上的 “免费” 。老资格的成员们开始解释，通常像下面所说的：“我们指的是 ‘freedom’ 中的自由，而不是‘免费啤酒’的免费。”在这一点上，关于软件方面的讨论就会变成了关于酒精饮料价格的讨论。问题不在于解释不了它的含义 —— 问题在于重要概念的术语不应该使新手们感到困惑。所以需要一个更清晰的术语。自由软件一词并没有政治上的问题；问题在于这个术语不能对新人清晰表明其概念。
|
||||
|
||||
### 开放的网景
|
||||
|
||||
1998 年 2 月 2 日，Eric Raymond 访问网景公司，并与它一起计划采用自由软件风格的许可证发布其浏览器的源代码。我们那晚在前瞻协会位于<ruby>罗斯阿尔托斯<rt>Los Altos</rt></ruby>的办公室开会，商讨并完善了我们的计划。除了 Eric 和我，积极参与者还有 Brian Behlendorf、Michael Tiemann、Todd Anderson、Mark S. Miller 和 Ka-Ping Yee。但在那次会议上，这一领域仍然被描述成“自由软件”，或者用 Brian 的话说， 叫“可获得源代码的” 软件。
|
||||
|
||||
在这个镇上，Eric 把前瞻协会作为行动的大本营。他访问行程期间，他接到了网景的法律和市场部门人员的电话。当他聊完后，我要求和他们（一男一女，可能是 Mitchell Baker）通电话，以便我告诉他们一个新的术语的必要性。他们原则上立即同意了，但我们在具体术语上并未达成一致。
|
||||
|
||||
在那周的会议中，我始终专注于起一个更好的名字并提出了 “开源软件”一词。 虽然不太理想，但我觉得足够好了。我找到至少四个人征求意见：Eric Drexler、Mark Miller 以及 Todd Anderson 都喜欢它，而一个从事市场公关的朋友觉得术语 “open” 被滥用了，并且觉得我们能找到一个更好。理论上他是对的，可我想不出更好的了，所以我想试着先推广它。事后想起来，我应该直接向 Eric Raymond 提议，但在那时我并不是很了解他，所以我采取了间接的策略。
|
||||
|
||||
Todd 强烈同意需要一个新的术语，并提供协助推广它。这很有帮助，因为作为一个非编程人员，我在自由软件社区的影响力很弱。我从事的纳米技术教育是一个加分项，但不足以让我在自由软件问题上非常得到重视。而作为一个 Linux 程序员，Todd 的话更容易被倾听。
|
||||
|
||||
### 关键性会议
|
||||
|
||||
那周稍晚时候，1998 年的 2 月 5 日，一伙人在 VA Research 进行头脑风暴商量对策。与会者除了 Eric Raymond、Todd 和我之外，还有 Larry Augustin、Sam Ockman，和 Jon Hall （“maddog”）通过电话参与。
|
||||
|
||||
会议的主要议题是推广策略，特别是要联系的公司。 我几乎没说什么，但是一直在寻找机会介绍提议的术语。我觉得我直接说“你们这些技术人员应当开始使用我的新术语了。”没有什么用。大多数与会者不认识我，而且据我所知，他们可能甚至不同意现在就迫切需要一个新术语。
|
||||
|
||||
幸运的是，Todd 一直留心着。他没有主张社区应该用哪个特定的术语，而是面对社区这些固执的人间接地做了一些事。他仅仅是在其它话题中使用了那个术语 —— 把它放进对话里看看会发生什么。我很紧张，期待得到回应，但是起初什么也没有。讨论继续进行原来的话题。似乎只有他和我注意了这个术语的使用。
|
||||
|
||||
不仅如此——模因演化（LCTT 译注：人类学术语）在起作用。几分钟后，另一个人使用了这个术语，显然没有注意到，而在继续进行话题讨论。Todd 和我用眼角互觑了一下：是的，我们都注意到发生了什么。我很激动——它或许有用！但我保持了安静：我在小组中仍然地位不高。可能有些人都奇怪为什么 Eric 会邀请我。
|
||||
|
||||
临近会议尾声，可能是 Todd 或 Eric，明确提出了[术语问题][8]。Maddog 提及了一个早期的术语“可自由分发的”，和一个新的术语“合作开发的”。Eric 列出了“自由软件”、“开源软件”和“软件源”作为主要选项。Todd 提议使用“开源”，然后 Eric 支持了他。我没说太多，就让 Todd 和 Eric（轻松、非正式地）就“开源”这个名字达成了共识。显然对于大多数与会者，改名并不是在这讨论的最重要议题；那只是一个次要的相关议题。从我的会议记录中看只有大约 10% 的内容是术语的。
|
||||
|
||||
但是我很高兴。在那有许多社区的关键领导人，并且他们喜欢这新名字，或者至少没反对。这是一个好的信号。可能我帮不上什么忙； Eric Raymond 更适合宣传新的名称，而且他也这么做了。Bruce Perens 立即表示支持，帮助建立了 [Opensource.org][9] 并在新术语的宣传中发挥了重要作用。
|
||||
|
||||
为了让这个名字获得认同，Tim O'Reilly 同意在代表社区的多个项目中积极使用它，这是很必要，甚至是非常值得的。并且在官方即将发布的 Netscape Navigator（网景浏览器）代码中也使用了此术语。 到二月底， O'Reilly & Associates 还有网景公司（Netscape） 已经开始使用新术语。
|
||||
|
||||
### 名字的宣传
|
||||
|
||||
在那之后的一段时间，这条术语由 Eric Raymond 向媒体推广，由 Tim O'Reilly 向商业推广，并由二人向编程社区推广，它似乎传播的相当快。
|
||||
|
||||
1998 年 4 月 17 日，Tim O'Reilly 召集了该领域的一些重要领袖的峰会，宣布为第一次 “[自由软件峰会][10]” ，在 4 月14 日之后，它又被称作首届 “[开源峰会][11]”。
|
||||
|
||||
这几个月对于开源来说是相当激动人心的。似乎每周都有一个新公司宣布加入计划。读 Slashdot（LCTT 译注：科技资讯网站）已经成了一个必需操作，甚至对于那些像我一样只能外围地参与者亦是如此。我坚信新术语能对快速传播到商业很有帮助，能被公众广泛使用。
|
||||
|
||||
尽管在谷歌搜索一下表明“开源”比“自由软件”出现的更多，但后者仍然有大量的使用，在和偏爱它的人们沟通的时候我们应该包容。
|
||||
|
||||
### 快乐的感觉
|
||||
|
||||
当 Eric Raymond 写的有关术语更改的[早期声明][12]被发布在了<ruby>开源促进会<rt>Open Source Initiative</rt></ruby>的网站上时，我被列在 VA 头脑风暴会议的名单上，但并不是作为术语的创始人。这是我自己的失误，我没告诉 Eric 细节。我的想法就是让它过去吧，我呆在幕后就好，但是 Todd 不这样认为。他认为我总有一天会为被称作“开源软件”这个名词的创造者而高兴。他向 Eric 解释了这个情况，Eric 及时更新了网站。
|
||||
|
||||
想出这个短语只是一个小贡献，但是我很感激那些把它归功于我的人。每次我听到它（现在经常听到了），它都给我些许的感动。
|
||||
|
||||
说服社区的巨大功劳要归功于 Eric Raymond 和 Tim O'Reilly，是他们让这一切成为可能。感谢他们对我的归功，并感谢 Todd Anderson 所做的一切。以上内容并非完整的开源一词的历史，让我对很多没有提及的关键人士表示歉意。那些寻求更完整讲述的人应该参考本文和网上其他地方的链接。
|
||||
|
||||
### 关于作者
|
||||
|
||||
[][13]
|
||||
|
||||
Christine Peterson 撰写、举办讲座，并向媒体介绍未来强大的技术，特别是在纳米技术，人工智能和长寿方面。她是纳米科技公益组织前瞻协会的共同创始人和前任主席。前瞻协会向公众、技术团体和政策制定者提供未来强大的技术的教育以及告诉它是如何引导他们的长期影响。她服务于[机器智能][2]咨询委员会……[更多关于 Christine Peterson][3]
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://opensource.com/article/18/2/coining-term-open-source-software
|
||||
|
||||
作者：[Christine Peterson][a]
|
||||
译者：[fuzheng1998](https://github.com/fuzheng1998)
|
||||
校对：[wxy](https://github.com/wxy)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
||||
[a]:https://opensource.com/users/christine-peterson
|
||||
[1]:https://opensource.com/article/18/2/coining-term-open-source-software?rate=HFz31Mwyy6f09l9uhm5T_OFJEmUuAwpI61FY-fSo3Gc
|
||||
[2]:http://intelligence.org/
|
||||
[3]:https://opensource.com/users/christine-peterson
|
||||
[4]:https://opensource.com/users/christine-peterson
|
||||
[5]:https://opensource.com/user/206091/feed
|
||||
[6]:https://opensource.com/resources/what-open-source
|
||||
[7]:https://opensource.org/osd
|
||||
[8]:https://wiki2.org/en/Alternative_terms_for_free_software
|
||||
[9]:https://opensource.org/
|
||||
[10]:http://www.oreilly.com/pub/pr/636
|
||||
[11]:http://www.oreilly.com/pub/pr/796
|
||||
[12]:https://ipfs.io/ipfs/QmXoypizjW3WknFiJnKLwHCnL72vedxjQkDDP1mXWo6uco/wiki/Alternative_terms_for_free_software.html
|
||||
[13]:https://opensource.com/users/christine-peterson
|
||||
[14]:https://opensource.com/users/christine-peterson
|
||||
[15]:https://opensource.com/users/christine-peterson
|
||||
[16]:https://opensource.com/article/18/2/coining-term-open-source-software#comments
|
||||
@ -1,3 +1,4 @@
|
||||
gongqi0632 translating
|
||||
Lessons Learned from Growing an Open Source Project Too Fast
|
||||
======
|
||||
![open source project][1]
|
||||
|
||||
@ -1,106 +0,0 @@
|
||||
translating---geekpi
|
||||
|
||||
Caffeinated 6.828: Exercise: Shell
|
||||
======
|
||||
|
||||
This assignment will make you more familiar with the Unix system call interface and the shell by implementing several features in a small shell. You can do this assignment on any operating system that supports the Unix API (a Linux Athena machine, your laptop with Linux or Mac OS, etc.). Please submit your shell to the the [submission web site][1] at any time before the first lecture.
|
||||
|
||||
While you shouldn't be shy about emailing the [staff mailing list][2] if you get stuck or don't understand something in this exercise, we do expect you to be able to handle this level of C programming on your own for the rest of the class. If you're not very familiar with C, consider this a quick check to see how familiar you are. Again, do feel encouraged to ask us for help if you have any questions.
|
||||
|
||||
Download the [skeleton][3] of the xv6 shell, and look it over. The skeleton shell contains two main parts: parsing shell commands and implementing them. The parser recognizes only simple shell commands such as the following:
|
||||
```
|
||||
ls > y
|
||||
cat < y | sort | uniq | wc > y1
|
||||
cat y1
|
||||
rm y1
|
||||
ls | sort | uniq | wc
|
||||
rm y
|
||||
|
||||
```
|
||||
|
||||
Cut and paste these commands into a file `t.sh`
|
||||
|
||||
You can compile the skeleton shell as follows:
|
||||
```
|
||||
$ gcc sh.c
|
||||
|
||||
```
|
||||
|
||||
which produces a file named `a.out`, which you can run:
|
||||
```
|
||||
$ ./a.out < t.sh
|
||||
|
||||
```
|
||||
|
||||
This execution will panic because you have not implemented several features. In the rest of this assignment you will implement those features.
|
||||
|
||||
### Executing simple commands
|
||||
|
||||
Implement simple commands, such as:
|
||||
```
|
||||
$ ls
|
||||
|
||||
```
|
||||
|
||||
The parser already builds an `execcmd` for you, so the only code you have to write is for the ' ' case in `runcmd`. To test that you can run "ls". You might find it useful to look at the manual page for `exec`; type `man 3 exec`.
|
||||
|
||||
You do not have to implement quoting (i.e., treating the text between double-quotes as a single argument).
|
||||
|
||||
### I/O redirection
|
||||
|
||||
Implement I/O redirection commands so that you can run:
|
||||
```
|
||||
echo "6.828 is cool" > x.txt
|
||||
cat < x.txt
|
||||
|
||||
```
|
||||
|
||||
The parser already recognizes '>' and '<', and builds a `redircmd` for you, so your job is just filling out the missing code in `runcmd` for those symbols. Make sure your implementation runs correctly with the above test input. You might find the man pages for `open` (`man 2 open`) and `close` useful.
|
||||
|
||||
Note that this shell will not process quotes in the same way that `bash`, `tcsh`, `zsh` or other UNIX shells will, and your sample file `x.txt` is expected to contain the quotes.
|
||||
|
||||
### Implement pipes
|
||||
|
||||
Implement pipes so that you can run command pipelines such as:
|
||||
```
|
||||
$ ls | sort | uniq | wc
|
||||
|
||||
```
|
||||
|
||||
The parser already recognizes "|", and builds a `pipecmd` for you, so the only code you must write is for the '|' case in `runcmd`. Test that you can run the above pipeline. You might find the man pages for `pipe`, `fork`, `close`, and `dup` useful.
|
||||
|
||||
Now you should be able the following command correctly:
|
||||
```
|
||||
$ ./a.out < t.sh
|
||||
|
||||
```
|
||||
|
||||
Don't forget to submit your solution to the [submission web site][1], with or without challenge solutions.
|
||||
|
||||
### Challenge exercises
|
||||
|
||||
If you'd like to experiment more, you can add any feature of your choice to your shell. You might try one of the following suggestions:
|
||||
|
||||
* Implement lists of commands, separated by `;`
|
||||
* Implement subshells by implementing `(` and `)`
|
||||
* Implement running commands in the background by supporting `&` and `wait`
|
||||
* Implement quoting of arguments
|
||||
|
||||
|
||||
|
||||
All of these require making changing to the parser and the `runcmd` function.
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://sipb.mit.edu/iap/6.828/lab/shell/
|
||||
|
||||
作者：[mit][a]
|
||||
译者：[译者ID](https://github.com/译者ID)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
||||
[a]:https://sipb.mit.edu
|
||||
[1]:https://exokernel.scripts.mit.edu/submit/
|
||||
[2]:mailto:sipb-iap-6.828@mit.edu
|
||||
[3]:https://sipb.mit.edu/iap/6.828/files/sh.c
|
||||
@ -1,255 +0,0 @@
|
||||
Translating by MjSeven
|
||||
|
||||
Oh My Fish! Make Your Shell Beautiful
|
||||
======
|
||||
|
||||
|
||||
A few days ago, we discussed how to [**install** **Fish shell**][1], a robust, fully-usable shell that ships with many cool features out of the box such as autosuggestions, built-in search functionality, syntax highlighting, web based configuration and a lot more. Today, we are going to discuss how to make our Fish shell beautiful and elegant using **Oh My Fish** (shortly **omf** ). It is a Fishshell framework that allows you to install packages which extend or modify the look and feel of your shell. It is easy to use, fast and extensible. Using omf, you can easily install themes that enriches the look of your shell and install plugins to tweak your fish shell as per your wish.
|
||||
|
||||
#### Install Oh My Fish
|
||||
|
||||
Installing omf is not a big deal. All you have to do is just run the following command in your fish shell.
|
||||
```
|
||||
curl -L https://get.oh-my.fish | fish
|
||||
```
|
||||
|
||||
![][3]
|
||||
|
||||
Once the installation has completed, you will see the the prompt has automatically changed as shown in the above picture. Also, you will notice that the current time on the right of the shell window.
|
||||
|
||||
That's it. Let us go ahead and tweak our fish shell.
|
||||
|
||||
#### Now, Let Us Make Our Fish Shell Beautiful
|
||||
|
||||
To list all installed packages, run:
|
||||
```
|
||||
omf list
|
||||
```
|
||||
|
||||
This command will display both the installed themes and plugins. Please note that a package can be either a theme or plugin. Installing packages means installing themes or plugins.
|
||||
|
||||
All official and community supported packages (both plugins and themes) are hosted in the [**main Omf repository**][4]. In this repository, you can see a whole bunch of repositories that contains a lot of plugins and themes.
|
||||
|
||||
Now let us see the list of available and installed themes. To do so, run:
|
||||
```
|
||||
omf theme
|
||||
```
|
||||
|
||||
[![][2]][5]
|
||||
|
||||
As you can see, we have only one installed theme, which is default, and a whole bunch of available themes. You can preview all available themes [**here**][6] before installing it. This page contains all theme details, features, a sample screenshot of each theme and which theme is suitable for whom.
|
||||
|
||||
**Installing a new theme**
|
||||
|
||||
Allow me to install a theme, for example **clearance theme - **a minimalist fish shell theme for people who use git a lot. To do so, run:
|
||||
```
|
||||
omf install clearance
|
||||
```
|
||||
|
||||
[![][2]][7]
|
||||
|
||||
As you see in the above picture, the look of fish prompt has changed immediately after installing the new theme.
|
||||
|
||||
Let me browse through the file system and see how it looks like.
|
||||
|
||||
[![][2]][8]
|
||||
|
||||
Not bad! It is really simple theme. It distinguishes the current working directory, folders and files with different color. As you may notice, it also displays the current working directory on top of the prompt. Currently, **clearance** is my default theme.
|
||||
|
||||
**Changing theme**
|
||||
|
||||
Like I already said, the theme will be applied immediately after installing it. If you have more than one themes, you can switch to a different theme using the following command:
|
||||
```
|
||||
omf theme <theme-name>
|
||||
```
|
||||
|
||||
Example:
|
||||
```
|
||||
omf theme agnoster
|
||||
```
|
||||
|
||||
Now I am using "agnoster" theme. Here is how agnoster theme changed the look of my shell.
|
||||
|
||||
[![][2]][9]
|
||||
|
||||
**Installing Plugins**
|
||||
|
||||
For instance, I am going to install weather plugin. To do so, just run:
|
||||
```
|
||||
omf install weather
|
||||
```
|
||||
|
||||
The weather plugin depends on [jq][10]. So, you might need to install jq as well. It is mostly available in the default repositories of any Linux distro. So, you can install it using the default package manager. For example, the following command will install jq in Arch Linux and its variants.
|
||||
```
|
||||
sudo pacman -S jq
|
||||
```
|
||||
|
||||
Now, check your weather from your fish shell using command:
|
||||
```
|
||||
weather
|
||||
```
|
||||
|
||||
[![][2]][11]
|
||||
|
||||
**Searching packages**
|
||||
|
||||
To search for a theme or plugin, do:
|
||||
```
|
||||
omf search <search_string>
|
||||
```
|
||||
|
||||
Example:
|
||||
```
|
||||
omf search nvm
|
||||
```
|
||||
|
||||
To limit the search to themes, use **-t** flag.
|
||||
```
|
||||
omf search -t chain
|
||||
```
|
||||
|
||||
This command will only search for themes that contains the string "chain".
|
||||
|
||||
To limit the search to plugins, use **-p** flag.
|
||||
```
|
||||
omf search -p emacs
|
||||
```
|
||||
|
||||
**Updating packages**
|
||||
|
||||
To update only the core (omf itself), run:
|
||||
```
|
||||
omf update omf
|
||||
```
|
||||
|
||||
If it is up-to-date, you would see the following output:
|
||||
```
|
||||
Oh My Fish is up to date.
|
||||
You are now using Oh My Fish version 6.
|
||||
Updating https://github.com/oh-my-fish/packages-main master... Done!
|
||||
```
|
||||
|
||||
To update all packages:
|
||||
```
|
||||
omf update
|
||||
```
|
||||
|
||||
To selectively update packages, just include the packages names as shown below.
|
||||
```
|
||||
omf update clearance agnoster
|
||||
```
|
||||
|
||||
**Displaying information about a package**
|
||||
|
||||
When you want to know the information about a theme or plugin, use this command:
|
||||
```
|
||||
omf describe clearance
|
||||
```
|
||||
|
||||
This command will show the information about a package.
|
||||
```
|
||||
Package: clearance
|
||||
Description: A minimalist fish shell theme for people who use git
|
||||
Repository: https://github.com/oh-my-fish/theme-clearance
|
||||
Maintainer:
|
||||
```
|
||||
|
||||
**Removing packages**
|
||||
|
||||
To remove a package, for example emacs, run:
|
||||
```
|
||||
omf remove emacs
|
||||
```
|
||||
|
||||
**Managing Repositories**
|
||||
|
||||
By default, the official repository is added automatically when you install Oh My Fish. This repository contains all packages built by the developers. To manage user-installed package repositories, use this command:
|
||||
```
|
||||
omf repositories [list|add|remove]
|
||||
```
|
||||
|
||||
To list installed repositories, run:
|
||||
```
|
||||
omf repositories list
|
||||
```
|
||||
|
||||
To add a repository:
|
||||
```
|
||||
omf repositories add <URL>
|
||||
```
|
||||
|
||||
Example:
|
||||
```
|
||||
omf repositories add https://github.com/ostechnix/theme-sk
|
||||
```
|
||||
|
||||
To remove a repository:
|
||||
```
|
||||
omf repositories remove <repository-name>
|
||||
```
|
||||
|
||||
**Troubleshooting Oh My Fish**
|
||||
|
||||
Omf is smart enough to help you if things went wrong. It will list what to do to fix an issue. For example, I removed and installed clearance package and got file conflicting error. Luckily, Oh My Fish instructed me what to do before continuing. So, I simply ran the following to know how to fix the error:
|
||||
```
|
||||
omf doctor
|
||||
```
|
||||
|
||||
And fixed the issued the error by running the following command:
|
||||
```
|
||||
rm ~/.config/fish/functions/fish_prompt.fish
|
||||
```
|
||||
|
||||
[![][2]][12]
|
||||
|
||||
Whenever you ran into a problem, just run 'omf doctor' command and try all suggested workarounds.
|
||||
|
||||
**Getting help**
|
||||
|
||||
To display help section, run:
|
||||
```
|
||||
omf -h
|
||||
```
|
||||
|
||||
Or,
|
||||
```
|
||||
omf --help
|
||||
```
|
||||
|
||||
**Uninstalling Oh My Fish**
|
||||
|
||||
To uninstall Oh My Fish, run this command:
|
||||
```
|
||||
omf destroy
|
||||
```
|
||||
|
||||
Go ahead and start customizing your fish shell. For more details, refer the project's GitHub page.
|
||||
|
||||
That's all for now folks. I will be soon here with another interesting guide. Until then, stay tuned with OSTechNix!
|
||||
|
||||
Cheers!
|
||||
|
||||
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
via: https://www.ostechnix.com/oh-fish-make-shell-beautiful/
|
||||
|
||||
作者：[SK][a]
|
||||
译者：[译者ID](https://github.com/译者ID)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
||||
[a]:https://www.ostechnix.com/author/sk/
|
||||
[1]:https://www.ostechnix.com/install-fish-friendly-interactive-shell-linux/
|
||||
[2]:data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7
|
||||
[3]:http://www.ostechnix.com/wp-content/uploads/2017/12/Oh-My-Fish-1-1.png ()
|
||||
[4]:https://github.com/oh-my-fish
|
||||
[5]:http://www.ostechnix.com/wp-content/uploads/2017/12/Oh-My-Fish-5.png ()
|
||||
[6]:https://github.com/oh-my-fish/oh-my-fish/blob/master/docs/Themes.md
|
||||
[7]:http://www.ostechnix.com/wp-content/uploads/2017/12/Oh-My-Fish-3.png ()
|
||||
[8]:http://www.ostechnix.com/wp-content/uploads/2017/12/Oh-My-Fish-4.png ()
|
||||
[9]:http://www.ostechnix.com/wp-content/uploads/2017/12/Oh-My-Fish-6.png ()
|
||||
[10]:https://stedolan.github.io/jq/
|
||||
[11]:http://www.ostechnix.com/wp-content/uploads/2017/12/Oh-My-Fish-7.png ()
|
||||
[12]:http://www.ostechnix.com/wp-content/uploads/2017/12/Oh-My-Fish-8.png ()
|
||||
@ -1,3 +1,5 @@
|
||||
translating---geekpi
|
||||
|
||||
4 command line note-taking applications for Linux
|
||||
======
|
||||
|
||||
|
||||
270
sources/tech/20180326 Working with calendars on Linux.md
Normal file
270
sources/tech/20180326 Working with calendars on Linux.md
Normal file
@ -0,0 +1,270 @@
|
||||
Working with calendars on Linux
|
||||
======
|
||||
|
||||
|
||||
Linux systems can provide more help with your schedule than just reminding you what day today is. You have a lot of options for displaying calendars — some that are likely to prove helpful and others that just might boggle your mind.
|
||||
|
||||
### date
|
||||
|
||||
To begin, you probably know that you can show the current date with the **date** command.
|
||||
```
|
||||
$ date
|
||||
Mon Mar 26 08:01:41 EDT 2018
|
||||
|
||||
```
|
||||
|
||||
### cal and ncal
|
||||
|
||||
You can show the entire month with the **cal** command. With no arguments, cal displays the current month and, by default, highlights the current day by reversing the foreground and background colors.
|
||||
```
|
||||
$ cal
|
||||
March 2018
|
||||
Su Mo Tu We Th Fr Sa
|
||||
1 2 3
|
||||
4 5 6 7 8 9 10
|
||||
11 12 13 14 15 16 17
|
||||
18 19 20 21 22 23 24
|
||||
25 26 27 28 29 30 31
|
||||
|
||||
```
|
||||
|
||||
If you want to display the current month in a “sideways” format, you can use the **ncal** command.
|
||||
```
|
||||
$ ncal
|
||||
March 2018
|
||||
Su 4 11 18 25
|
||||
Mo 5 12 19 26
|
||||
Tu 6 13 20 27
|
||||
We 7 14 21 28
|
||||
Th 1 8 15 22 29
|
||||
Fr 2 9 16 23 30
|
||||
Sa 3 10 17 24 31
|
||||
|
||||
```
|
||||
|
||||
That command can be especially useful if, for example, you just want to see the dates for some particular day of the week.
|
||||
```
|
||||
$ ncal | grep Th
|
||||
Th 1 8 15 22 29
|
||||
|
||||
```
|
||||
|
||||
The ncal command can also display the entire year in the "sideways" format. Just provide the year along with the command.
|
||||
```
|
||||
$ ncal 2018
|
||||
2018
|
||||
January February March April
|
||||
Su 7 14 21 28 4 11 18 25 4 11 18 25 1 8 15 22 29
|
||||
Mo 1 8 15 22 29 5 12 19 26 5 12 19 26 2 9 16 23 30
|
||||
Tu 2 9 16 23 30 6 13 20 27 6 13 20 27 3 10 17 24
|
||||
We 3 10 17 24 31 7 14 21 28 7 14 21 28 4 11 18 25
|
||||
Th 4 11 18 25 1 8 15 22 1 8 15 22 29 5 12 19 26
|
||||
Fr 5 12 19 26 2 9 16 23 2 9 16 23 30 6 13 20 27
|
||||
Sa 6 13 20 27 3 10 17 24 3 10 17 24 31 7 14 21 28
|
||||
...
|
||||
|
||||
```
|
||||
|
||||
You can also display the entire year with **cal**. Just remember that you need all four digits for the year. If you type "cal 18", you'll get a calendar year for 18 AD, not 2018.
|
||||
```
|
||||
$ cal 2018
|
||||
2018
|
||||
January February March
|
||||
Su Mo Tu We Th Fr Sa Su Mo Tu We Th Fr Sa Su Mo Tu We Th Fr Sa
|
||||
1 2 3 4 5 6 1 2 3 1 2 3
|
||||
7 8 9 10 11 12 13 4 5 6 7 8 9 10 4 5 6 7 8 9 10
|
||||
14 15 16 17 18 19 20 11 12 13 14 15 16 17 11 12 13 14 15 16 17
|
||||
21 22 23 24 25 26 27 18 19 20 21 22 23 24 18 19 20 21 22 23 24
|
||||
28 29 30 31 25 26 27 28 25 26 27 28 29 30 31
|
||||
|
||||
|
||||
April May June
|
||||
Su Mo Tu We Th Fr Sa Su Mo Tu We Th Fr Sa Su Mo Tu We Th Fr Sa
|
||||
1 2 3 4 5 6 7 1 2 3 4 5 1 2
|
||||
8 9 10 11 12 13 14 6 7 8 9 10 11 12 3 4 5 6 7 8 9
|
||||
15 16 17 18 19 20 21 13 14 15 16 17 18 19 10 11 12 13 14 15 16
|
||||
22 23 24 25 26 27 28 20 21 22 23 24 25 26 17 18 19 20 21 22 23
|
||||
29 30 27 28 29 30 31 24 25 26 27 28 29 30
|
||||
|
||||
|
||||
July August September
|
||||
Su Mo Tu We Th Fr Sa Su Mo Tu We Th Fr Sa Su Mo Tu We Th Fr Sa
|
||||
1 2 3 4 5 6 7 1 2 3 4 1
|
||||
8 9 10 11 12 13 14 5 6 7 8 9 10 11 2 3 4 5 6 7 8
|
||||
15 16 17 18 19 20 21 12 13 14 15 16 17 18 9 10 11 12 13 14 15
|
||||
22 23 24 25 26 27 28 19 20 21 22 23 24 25 16 17 18 19 20 21 22
|
||||
29 30 31 26 27 28 29 30 31 23 24 25 26 27 28 29
|
||||
30
|
||||
|
||||
October November December
|
||||
Su Mo Tu We Th Fr Sa Su Mo Tu We Th Fr Sa Su Mo Tu We Th Fr Sa
|
||||
1 2 3 4 5 6 1 2 3 1
|
||||
7 8 9 10 11 12 13 4 5 6 7 8 9 10 2 3 4 5 6 7 8
|
||||
14 15 16 17 18 19 20 11 12 13 14 15 16 17 9 10 11 12 13 14 15
|
||||
21 22 23 24 25 26 27 18 19 20 21 22 23 24 16 17 18 19 20 21 22
|
||||
28 29 30 31 25 26 27 28 29 30 23 24 25 26 27 28 29
|
||||
30 31
|
||||
|
||||
```
|
||||
|
||||
For a particular year and month, use the -d option win a command like this.
|
||||
```
|
||||
$ cal -d 1949-03
|
||||
March 1949
|
||||
Su Mo Tu We Th Fr Sa
|
||||
1 2 3 4 5
|
||||
6 7 8 9 10 11 12
|
||||
13 14 15 16 17 18 19
|
||||
20 21 22 23 24 25 26
|
||||
27 28 29 30 31
|
||||
|
||||
```
|
||||
|
||||
Another potentially useful calendaring option is the **cal** command’s -j option. Let's take a look at what that shows you.
|
||||
```
|
||||
$ cal -j
|
||||
March 2018
|
||||
Su Mo Tu We Th Fr Sa
|
||||
60 61 62
|
||||
63 64 65 66 67 68 69
|
||||
70 71 72 73 74 75 76
|
||||
77 78 79 80 81 82 83
|
||||
84 85 86 87 88 89 90
|
||||
|
||||
```
|
||||
|
||||
"What???" you might be asking. OK, that -j option is displaying Julian dates — the numeric day of the year that runs from 1 to 365 most years. So, 1 is January 1st and 32 is February 1st. The command **cal -j 2018** will show you the entire year, ending like this:
|
||||
```
|
||||
$ cal -j 2018 | tail -9
|
||||
|
||||
November December
|
||||
Su Mo Tu We Th Fr Sa Su Mo Tu We Th Fr Sa
|
||||
305 306 307 335
|
||||
308 309 310 311 312 313 314 336 337 338 339 340 341 342
|
||||
315 316 317 318 319 320 321 343 344 345 346 347 348 349
|
||||
322 323 324 325 326 327 328 350 351 352 353 354 355 356
|
||||
329 330 331 332 333 334 357 358 359 360 361 362 363
|
||||
364 365
|
||||
|
||||
```
|
||||
|
||||
This kind of display might help remind you of how many days have gone by since you made that New Year's resolution that you haven't yet acted on.
|
||||
|
||||
Run a similar command for 2020, and you’ll note that it’s a leap year.
|
||||
```
|
||||
$ cal -j 2020 | tail -9
|
||||
|
||||
November December
|
||||
Su Mo Tu We Th Fr Sa Su Mo Tu We Th Fr Sa
|
||||
306 307 308 309 310 311 312 336 337 338 339 340
|
||||
313 314 315 316 317 318 319 341 342 343 344 345 346 347
|
||||
320 321 322 323 324 325 326 348 349 350 351 352 353 354
|
||||
327 328 329 330 331 332 333 355 356 357 358 359 360 361
|
||||
334 335 362 363 364 365 366
|
||||
|
||||
```
|
||||
|
||||
### calendar
|
||||
|
||||
Another interesting and potentially overwhelming command can inform you about holidays. This command has a lot of options, but let’s just say that you’d like to see a list of upcoming holidays and noteworthy days. The calendar's **-l** option allows you to select how many days you want to see beyond today, so 0 means "today only".
|
||||
```
|
||||
$ calendar -l 0
|
||||
Mar 26 Benjamin Thompson born, 1753, Count Rumford; physicist
|
||||
Mar 26 David Packard died, 1996; age of 83
|
||||
Mar 26 Popeye statue unveiled, Crystal City TX Spinach Festival, 1937
|
||||
Mar 26 Independence Day in Bangladesh
|
||||
Mar 26 Prince Jonah Kuhio Kalanianaole Day in Hawaii
|
||||
Mar 26* Seward's Day in Alaska (last Monday)
|
||||
Mar 26 Emerson, Lake, and Palmer record "Pictures at an Exhibition" live, 1971
|
||||
Mar 26 Ludwig van Beethoven dies in Vienna, Austria, 1827
|
||||
Mar 26 Bonne fête aux Lara !
|
||||
Mar 26 Aujourd'hui, c'est la St(e) Ludger.
|
||||
Mar 26 N'oubliez pas les Larissa !
|
||||
Mar 26 Ludwig van Beethoven in Wien gestorben, 1827
|
||||
Mar 26 Emánuel
|
||||
|
||||
```
|
||||
|
||||
For most of us, that's a bit more celebrating than we can manage in a single day. If you're seeing something like this, you can blame it on your **calendar.all** file that's telling the system what international calendars you'd like to include. You can, of course, pare this down by removing some of the lines in this file that include other files. The lines look like these:
|
||||
```
|
||||
#include <calendar.world>
|
||||
#include <calendar.argentina>
|
||||
#include <calendar.australia>
|
||||
#include <calendar.belgium>
|
||||
#include <calendar.birthday>
|
||||
#include <calendar.christian>
|
||||
#include <calendar.computer>
|
||||
|
||||
```
|
||||
|
||||
Say we cut our display down to world calendars only by removing all but the first #include line shown above. We'd then see this:
|
||||
```
|
||||
$ calendar -l 0
|
||||
Mar 26 Benjamin Thompson born, 1753, Count Rumford; physicist
|
||||
Mar 26 David Packard died, 1996; age of 83
|
||||
Mar 26 Popeye statue unveiled, Crystal City TX Spinach Festival, 1937
|
||||
Mar 26 Independence Day in Bangladesh
|
||||
Mar 26 Prince Jonah Kuhio Kalanianaole Day in Hawaii
|
||||
Mar 26* Seward's Day in Alaska (last Monday)
|
||||
Mar 26 Emerson, Lake, and Palmer record "Pictures at an Exhibition" live, 1971
|
||||
Mar 26 Ludwig van Beethoven dies in Vienna, Austria, 1827
|
||||
|
||||
```
|
||||
|
||||
Clearly, the world calendar's special days are quite numerous. A display like this could, however, keep you from forgetting the all-important Popeye statue unveiling day and its role in observing the "spinach capital of the world."
|
||||
|
||||
A more useful calendaring choice might be to put work-related calendars in a special file and use that calendar in the calendar.all file to determine what events you will see when you run the command.
|
||||
```
|
||||
$ cat /usr/share/calendar/calendar.all
|
||||
/*
|
||||
* International and national calendar files
|
||||
*
|
||||
* This is the calendar master file. In the standard setup, it is
|
||||
* included by /etc/calendar/default, so you can make any system-wide
|
||||
* changes there and they will be kept when you upgrade. If you want
|
||||
* to edit this file, copy it into /etc/calendar/calendar.all and
|
||||
* edit it there.
|
||||
*
|
||||
*/
|
||||
|
||||
#ifndef _calendar_all_
|
||||
#define _calendar_all_
|
||||
|
||||
#include <calendar.usholiday>
|
||||
#include <calendar.work> <==
|
||||
|
||||
#endif /bin /boot /dev /etc /home /lib /lib64 /lost+found /media /mnt /opt /proc /root /run /sbin /srv /sys /tmp /usr /var !_calendar_all_ */
|
||||
|
||||
```
|
||||
|
||||
The format for calendar files is very simple — mm/dd for the date, a tab, and the event's description.
|
||||
```
|
||||
$ cat calendar.work
|
||||
03/26 Describe how the cal and calendar commands work
|
||||
03/27 Throw a party!
|
||||
|
||||
```
|
||||
|
||||
### notes and nostalgia
|
||||
|
||||
Note that the calendar command might not be available for all Linux distributions. You might have to remember the Popeye statue unveiling day on your own.
|
||||
|
||||
And in case you're wondering, you can display a calendar as far ahead as the year 9999 — even for the prophetic [2525][1].
|
||||
|
||||
Join the Network World communities on [Facebook][2] and [LinkedIn][3] to comment on topics that are top of mind.
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://www.networkworld.com/article/3265752/linux/working-with-calendars-on-linux.html
|
||||
|
||||
作者：[Sandra Henry-Stocker][a]
|
||||
译者：[译者ID](https://github.com/译者ID)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
选题：[lujun9972](https://github.com/lujun9972)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
||||
[a]:https://www.networkworld.com/author/Sandra-Henry_Stocker/
|
||||
[1]:https://www.youtube.com/watch?v=izQB2-Kmiic
|
||||
[2]:https://www.facebook.com/NetworkWorld/
|
||||
[3]:https://www.linkedin.com/company/network-world
|
||||
@ -0,0 +1,185 @@
|
||||
Do continuous deployment with Github and Python
|
||||
======
|
||||
|
||||
|
||||
Developers can create many useful services using Github’s webhooks. From triggering a CI job on a Jenkins instance to provisioning machines in the cloud, the possibilities are almost limitless. This tutorial shows how to use Python and the Flask framework to build a simple continuous deployment service.
|
||||
|
||||
The continuous deployment service in this example is a simple Flask application with a REST endpoint that will receive Github’s webhook requests. After validating each request to check that it comes from the correct Github repository, the service pulls changes to the local copy of the repository. That way every time a new commit is pushed to the remote Github repository, the local repository is automatically updated.
|
||||
|
||||
### Flask web service
|
||||
|
||||
It is easy to build a small web service with Flask. Here’s a look at the project structure.
|
||||
```
|
||||
├── app
|
||||
│ ├── __init__.py
|
||||
│ └── webhooks.py
|
||||
├── requirements.txt
|
||||
└── wsgi.py
|
||||
|
||||
```
|
||||
|
||||
First, create the application. The application code goes under the app directory.
|
||||
|
||||
Two files ( __init__.py and webhooks.py) compose the Flask application. The former has the code needed to create the Flask application and add configuration to it. The latter has the endpoints logic. This is where the app receives the data from the Github request.
|
||||
|
||||
Here is the app/__init__.py content:
|
||||
```
|
||||
import os
|
||||
from flask import Flask
|
||||
|
||||
from .webhooks import webhook
|
||||
|
||||
def create_app():
|
||||
""" Create, configure and return the Flask application """
|
||||
|
||||
app = Flask(__name__)
|
||||
app.config['GITHUB_SECRET'] = os.environ.get('GITHUB_SECRET')
|
||||
app.config['REPO_PATH'] = os.environ.get('REPO_PATH')
|
||||
app.register_blueprint(webhook)
|
||||
|
||||
return(app)
|
||||
|
||||
```
|
||||
|
||||
The function creates two configuration variables:
|
||||
|
||||
* **GITHUB_SECRET** holds a secret passphrase, used to authenticate the Github requests.
|
||||
* **REPO_PATH** holds the path of the repository to automatically update.
|
||||
|
||||
|
||||
|
||||
This code uses [Flask Blueprints][1] to organize the application endpoints. Using blueprints allows logical grouping of APIs, making applications easier to maintain. It is generally considered a good practice.
|
||||
|
||||
Here is the content of app/webhooks.py:
|
||||
```
|
||||
import hmac
|
||||
from flask import request, Blueprint, jsonify, current_app
|
||||
from git import Repo
|
||||
|
||||
webhook = Blueprint('webhook', __name__, url_prefix='')
|
||||
|
||||
@webhook.route('/github', methods=['POST'])
|
||||
def handle_github_hook():
|
||||
""" Entry point for github webhook """
|
||||
|
||||
signature = request.headers.get('X-Hub-Signature')
|
||||
sha, signature = signature.split('=')
|
||||
|
||||
secret = str.encode(current_app.config.get('GITHUB_SECRET'))
|
||||
|
||||
hashhex = hmac.new(secret, request.data, digestmod='sha1').hexdigest()
|
||||
if hmac.compare_digest(hashhex, signature):
|
||||
repo = Repo(current_app.config.get('REPO_PATH'))
|
||||
origin = repo.remotes.origin
|
||||
origin.pull('--rebase')
|
||||
|
||||
commit = request.json['after'][0:6]
|
||||
print('Repository updated with commit {}'.format(commit))
|
||||
return jsonify({}), 200
|
||||
|
||||
```
|
||||
|
||||
First the code creates a new Blueprint webhook. Then it adds a new endpoint to the Blueprint using a Flask route. This route will be called by any POST request on the /github URL endpoint.
|
||||
|
||||
#### Verifying the request
|
||||
|
||||
When the service receives a request on this endpoint, it must first verify that the request comes from Github and from the correct repository. Github gives a signature in the request header X-Hub-Signature. This signature is generated using a secret (GITHUB_SECRET), the [HMAC][2] hex digest of the request body, and then hashed using the sha1 hash function.
|
||||
|
||||
To verify the request the service needs to calculate locally the signature and compare it to the signature received in the request header. This is done by the hmac.compare_digest function.
|
||||
|
||||
#### Custom hook logic
|
||||
|
||||
After validating the request, it can now be processd. This tutorial uses the [GitPython][3] module to interface with a git repository. From the GitPython module the Repo object is used to access the remote repository called origin. The service pulls the latest changes locally from the origin repository, also using the –rebase option to avoid issues with merges.
|
||||
|
||||
A debug print statement displays the short commit hash received from the request body. This example shows how to use the request body. For more details about the data available in the body, check [github’s documentation][4].
|
||||
|
||||
Finally the service returns a empty JSON string and a 200 status code. This tells Github’s webhook server the request was received.
|
||||
|
||||
### Deploying the service
|
||||
|
||||
To run the service, this example uses the [gunicorn][5] web server. First install the service dependencies. On a supported Fedora server, use this command with [sudo][6]:
|
||||
```
|
||||
sudo dnf install python3-gunicorn python3-flask python3-GitPython
|
||||
|
||||
```
|
||||
|
||||
Now edit the wsgi.py file used by gunicorn to run the service:
|
||||
```
|
||||
from app import create_app
|
||||
|
||||
application = create_app()
|
||||
|
||||
```
|
||||
|
||||
To deploy this service, clone this git [repository][7] or use your own git repository with this command:
|
||||
```
|
||||
git clone https://github.com/cverna/github_hook_deployment.git /opt/
|
||||
|
||||
```
|
||||
|
||||
The next step is to configure the environment variables needed by the service. Run these commands:
|
||||
```
|
||||
export GITHUB_SECRET=asecretpassphraseusebygithubwebhook
|
||||
export REPO_PATH=/opt/github_hook_deployment/
|
||||
|
||||
```
|
||||
|
||||
This tutorial uses the webhook service Github repository, but you could use a different repository if you wish. Finally, start the webserver with these commands:
|
||||
```
|
||||
cd /opt/github_hook_deployment/
|
||||
gunicorn --bind 0.0.0.0 wsgi:application --reload
|
||||
|
||||
```
|
||||
|
||||
These options bind the web server to the 0.0.0.0 ip address, meaning it will accept requests coming from any host. The –reload option ensures the web server restarts when the code changes. This is where the continuous deployment magic happens. Every Github request received pulls the latest change in the repository, and gunicorn detects these changes and automatically restarts the application.
|
||||
|
||||
**Note: **In order to receive the requests from github, the web service must be deployed on a server with a public IP address. An easy way to do this is to use your favorite cloud provider such as DigitalOcean, AWS, Linode, etc.
|
||||
|
||||
### Configure Github
|
||||
|
||||
The last part of this tutorial configures Github to send the webhook request to the web service. This is key to continuous deployment.
|
||||
|
||||
From your Github repository settings, select the Webhook menu and click on Add Webhook. Enter the following information:
|
||||
|
||||
* **Payload URL:** The URL of the service, for example <http://public\_ip\_address:8000/github>
|
||||
* **Content type:** Select application/json
|
||||
* **Secret:** The **GITHUB_SECRET** environment variable defined earlier
|
||||
|
||||
|
||||
|
||||
Then click the Add Webhook button.
|
||||
|
||||
![][8]
|
||||
|
||||
Github will now send a request to the service every time a push event happens on this repository.
|
||||
|
||||
### Conclusion
|
||||
|
||||
This tutorial has shown you how to write a Flask based web service that receives requests from a Github webhook and does continuous deployment. You should now be able to build your own useful services using this tutorial as a starting base.
|
||||
|
||||
#### Like this:
|
||||
|
||||
Like
|
||||
|
||||
Loading...
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://fedoramagazine.org/continuous-deployment-github-python/
|
||||
|
||||
作者：[Author Archive;Author Website;Clément Verna][a]
|
||||
译者：[译者ID](https://github.com/译者ID)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
选题：[lujun9972](https://github.com/lujun9972)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
||||
[a]:https://fedoramagazine.org
|
||||
[1]:http://flask.pocoo.org/docs/0.12/blueprints/
|
||||
[2]:https://en.wikipedia.org/wiki/HMAC
|
||||
[3]:https://gitpython.readthedocs.io/en/stable/index.html
|
||||
[4]:https://developer.github.com/v3/activity/events/types/#webhook-payload-example-26
|
||||
[5]:http://gunicorn.org/
|
||||
[6]:https://fedoramagazine.org/howto-use-sudo/
|
||||
[7]:https://github.com/cverna/github_hook_deployment.git
|
||||
[8]:https://fedoramagazine.org/wp-content/uploads/2018/03/Screenshot-2018-3-26-cverna-github_hook_deployment1.png
|
||||
@ -1,104 +0,0 @@
|
||||
[fuzheng1998 translating]
|
||||
我是如何创造“开源”这个词的
|
||||
============================================================
|
||||
|
||||
### Christine Peterson 最终公开讲述了二十年前那决定命运的一天。
|
||||
|
||||
|
||||
图片来自: opensource.com
|
||||
|
||||
几天后, 2 月 3 日, 术语“[开源软件][6]”创立 20 周年的纪念日即将到来。由于开源软件渐受欢迎并且为这个时代强有力的重要变革提供动力，我们仔细反思了它的初生到崛起。
|
||||
|
||||
我是 “开源软件” 这个词的始作俑者，它是我在前瞻技术协会（Foresight Institute）担任执行董事时想出的。并非向上面的一个程序开发者一样，我感谢 Linux 程序员 Todd Anderson 对这个术语的支持并将它提交小组讨论。
|
||||
|
||||
这是我对于它如何想到的，如何提出的，以及后续影响的记叙。当然，还有一些有关该术语的记叙，例如 Eric Raymond 和 Richard Stallman 写的，而我的，则写于 2006 年 1 月 2 日。
|
||||
|
||||
直到今天，它终于公诸于世。
|
||||
|
||||
* * *
|
||||
|
||||
推行术语“开源软件”是特地为了这个领域让新手和商业人士更加易懂，它的推广被认为对于更大的用户社区很有必要。早期称号的问题是，“自由软件” 并非有政治含义，但是那对于新手来说貌似对于价格的关注令人感到心烦意乱。一个术语需要聚焦于关键的源代码而且不会被立即把概念跟那些新东西混淆。一个恰好想出并且满足这些要求的第一个术语被快速接受：开源（open source）。
|
||||
|
||||
这个术语很长一段时间被用在“情报”（即间谍活动）的背景下，但据我所知，1998 年以前软件领域使用该术语尚未得到证实。下面这个就是讲述了术语“开源软件”如何流行起来并且变成了一项产业和一场运动名称的故事。
|
||||
|
||||
### 计算机安全会议
|
||||
|
||||
在 1997 年的晚些时候，为期一周的会议将被在前瞻技术协会（Foresight Insttitue) 举行来讨论计算机安全问题。这个协会是一个非盈利性智库，它专注于纳米技术和人工智能，并且认为软件安全是二者的安全性以及可靠性的核心。我们在那确定了自由软件是一个改进软件安全可靠性且具有发展前景的方法并将寻找推动它的方式。 对自由软件的兴趣开始在编程社区外开始增长，而且越来越清晰，一个改变世界的机会正在来临。然而，该怎么做我们并不清楚，因为我们当时正在摸索中。
|
||||
|
||||
在这些会议中，我们讨论了一些由于使人迷惑不解的因素而采用一个新术语的必要性。观点主要有以下：对于那些新接触“自由软件”的人把 "free" 当成了价格上的 “免费” 。老资格的成员们开始解释，通常像下面所说的：“我们的意思是自由的，而不是免费啤酒上的。"在这个点子上，一个软件方面的讨论变成了一个关于酒精价格的讨论。问题不在于解释不了含义——问题是重要概念的名称不应该使新手们感到困惑。所以需要一个更清晰的术语了。关于自由软件术语并没有政治上的问题；问题是缺乏对新概念的认识。
|
||||
|
||||
### 网景发布
|
||||
|
||||
1998 年 2 月 2 日，Eric Raymond 抵达访问网景并与它一起计划采用免费软件样式的许可证发布浏览器代码。我们那晚在前瞻位于罗斯阿尔托斯（Los Altos）的办公室制定了策略并改进了我们的要旨。除了 Eric 和我，活跃的参与者还有 Brian Behlendorf，Michael Tiemann，Todd Anderson，Mark S. Miller and Ka-Ping Yee。但在那次会议上，这个领域仍然被描述成“自由软件”，或者用 Brian 的话说， 叫“可获得源代码的” 软件。
|
||||
|
||||
在这个镇上，Eric 把前瞻协会（Foresight） 作为行动的大本营。他一开始访问行程，他就被几个网景法律和市场部门的员工通电话。当他挂电话后，我被要求带着电话跟他们——一男一女，可能是 Mitchell Baker——这样我才能谈论对于新术语的需求。他们原则上是立即同意了，但详细条款并未达成协议。
|
||||
|
||||
在那周的会议中，我仍然专注于起一个更好的名字并提出术语 “开源软件”。 虽然那不是完美的，但我觉得足够好了。我依靠至少另外四个人运营这个项目：Eric Drexler、Mark Miller，以及 Todd Anderson 和他这样的人，然而一个从事市场公关的朋友觉得术语 “open” 被滥用了并且相信我们能做更好再说。理论上它是对的，可我想不出更好的了，所以我想尝试并推广它。 事后一想我应该直接向 Eric Raymond 提案，但在那时我并不是很了解他，所以我采取了间接的策略。
|
||||
|
||||
Todd 强烈同意需要新的术语并提供协助推广它。这很有帮助，因为作为一个非编程人员，我在自由软件社区的影响力很弱。我从事的纳米技术是一个加分项，但不足以让我认真地接受自由软件问题的工作。作为一个Linux程序员，Todd 将会更仔细地聆听它。
|
||||
|
||||
### 关键的会议
|
||||
|
||||
那周之后，1998 年的 2 月 5 日，一伙人在 VA research 进行头脑风暴商量对策。与会者——除了 Eric Raymond，Todd和我之外，还有 Larry Augustin，Sam Ockman，还有 Jon“maddog”Hall 的电话。
|
||||
|
||||
会议的主要议题是推广策略，特别是要接洽的公司。 我几乎没说什么，而是在寻找机会推广已经提交讨论的术语。我觉得突然脱口而出那句话没什么用，“你们技术人员应当开始讨论我的新术语了。”他们大多数与会者不认识我，而且据我所知，他们可能甚至不同意对新术语的急切需求，或者是某种渴望。
|
||||
|
||||
幸运的是，Todd 是明智的。他没有主张社区应该用哪个特定的术语，而是间接地做了一些事——一件和社区里有强烈意愿的人做的明智之举。他简单地在其他话题中使用那个术语——把他放进对话里看看会发生什么。我警觉起来，希望得到一个答复，但是起初什么也没有。讨论继续进行原来的话题。似乎只有他和我注意了术语的使用。
|
||||
|
||||
不仅如此——模因演化（人类学术语）在起作用。几分钟后，另一个人明显地，没有提醒地，在仍然进行话题讨论而没说术语的情况下，用了这个术语。Todd 和我面面相觑对视：是的我们都注意到了发生的事。我很激动——它起作用了！但我保持了安静：我在小组中仍然地位不高。可能有些人都奇怪为什么 Eric 会最终邀请我。
|
||||
|
||||
临近会议尾声，可能是 Todd or Eric，[术语问题][8] 被明确提出。Maddog 提及了一个早期的术语“可自由分发的，和一个新的术语“合作开发的”。Eric 列出了“自由软件”、“开源软件”，并把 "自由软件源" 作为一个主要选项。Todd宣传 “开源” 模型，然后Eric 支持了他。我什么也没说，让 Todd 和 Eric 共同促进开源名字达成共识。对于大多数与会者，他们很清楚改名不是在这讨论的最重要议题；那只是一个次要的相关议题。 我在会议中只有大约10%的说明放在了术语问答中。
|
||||
|
||||
但是我很高兴。在那有许多社区的关键领导人，并且他们喜欢这新名字，或者至少没反对。这是一个好的信号信号。可能我帮不上什么忙； Eric Raymond 被相当好地放在了一个宣传模因的好位子上，而且他的确做到了。立即签约参加行动，帮助建立 [Opensource.org][9] 并在新术语的宣传中发挥重要作用。
|
||||
|
||||
对于这个成功的名字，那很必要，甚至是相当渴望， 因此 Tim O'Reilly 同意以社区的名义在公司积极使用它。在官方即将发布的 the Netscape Navigator（网景浏览器）代码中的术语使用也为此帮了忙。 到二月底， O'Reilly & Associates 还有网景公司（Netscape） 已经开始使用新术语。
|
||||
|
||||
### 名字的诞生
|
||||
|
||||
在那之后的一段时间，这条术语由 Eric Raymond 向媒体推广，由 Tim O'Reilly 向商业推广，并由二人向编程社区推广，那似乎传播的相当快。
|
||||
|
||||
1998 年 4 月 17 日, Tim O'Reilly 提前宣布首届 “[自由软件峰会][10]” ，在 4 月14 日之前，它以首届 “[开源峰会][11]” 被提及。
|
||||
|
||||
这几个月对于开源来说是相当激动人心的。似乎每周都有一个新公司宣布加入计划。读 Slashdot（科技资讯网站）已经成了一个必需操作, 甚至对于那些像我一样只能外围地参与者亦是如此。我坚信新术语能对快速传播到商业很有帮助，能被公众广泛使用。
|
||||
|
||||
尽管快捷的谷歌搜索表明“开源”比“自由软件”出现的更多，但后者仍然有大量的使用，特别是和偏爱它的人们沟通的时候。
|
||||
|
||||
### 一丝快感
|
||||
|
||||
当一个被 Eric Raymond 写的有关修改术语的早期的陈述被发布在了开放源代码促进会的网站上时，我上了 VA 头脑风暴会议的名单，但并不是作为一个术语的创始人。这是我自己的错，我没告诉 Eric 细节。我当时一时冲动只想让它表决通过然后我只是呆在后台，但是 Todd 不这样认为。他认为我总有一天将作为“开源软件”这个名词的创造者而感到高兴。他向 Eric 解释了这个情况，Eric 及时更新了它的网站。
|
||||
|
||||
想出这个短语只是一个小贡献，但是我得承认我十分感激那些把它归功于我的人。每次我听到它，它都给我些许激动的喜悦，到现在也时常感受到。
|
||||
|
||||
说服团队的大功劳归功于 Eric Raymond 和 Tim O'Reilly，这是他们搞定的。感谢他们对我的评价，并感谢 Todd Anderson 在整个过程中的角色。以上内容并非完整的开源历史记录，对很多没有无名人士表示歉意。那些寻求更完整讲述的人应该参考本文和网上其他地方的链接。
|
||||
|
||||
### 关于作者
|
||||
|
||||
[][13] Christine Peterson - Christine Peterson 撰写，举办讲座，并向媒体介绍未来强大的技术，特别是纳米技术，人工智能和长寿。她是著名的纳米科技公共利益集团的创始人和过去的前瞻技术协会主席。前瞻向公众、技术团体和政策制定者提供未来强大的技术的教育以及告诉它是如何引导他们的长期影响。她服务于 [机器智能 ][2]咨询委员会……[更多关于 Christine Peterson][3][关于我][4]
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://opensource.com/article/18/2/coining-term-open-source-software
|
||||
|
||||
作者：[ Christine Peterson][a]
|
||||
译者：[fuzheng1998](https://github.com/fuzheng1998)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
||||
[a]:https://opensource.com/users/christine-peterson
|
||||
[1]:https://opensource.com/article/18/2/coining-term-open-source-software?rate=HFz31Mwyy6f09l9uhm5T_OFJEmUuAwpI61FY-fSo3Gc
|
||||
[2]:http://intelligence.org/
|
||||
[3]:https://opensource.com/users/christine-peterson
|
||||
[4]:https://opensource.com/users/christine-peterson
|
||||
[5]:https://opensource.com/user/206091/feed
|
||||
[6]:https://opensource.com/resources/what-open-source
|
||||
[7]:https://opensource.org/osd
|
||||
[8]:https://wiki2.org/en/Alternative_terms_for_free_software
|
||||
[9]:https://opensource.org/
|
||||
[10]:http://www.oreilly.com/pub/pr/636
|
||||
[11]:http://www.oreilly.com/pub/pr/796
|
||||
[12]:https://ipfs.io/ipfs/QmXoypizjW3WknFiJnKLwHCnL72vedxjQkDDP1mXWo6uco/wiki/Alternative_terms_for_free_software.html
|
||||
[13]:https://opensource.com/users/christine-peterson
|
||||
[14]:https://opensource.com/users/christine-peterson
|
||||
[15]:https://opensource.com/users/christine-peterson
|
||||
[16]:https://opensource.com/article/18/2/coining-term-open-source-software#comments
|
||||
105
translated/tech/20140107 Caffeinated 6.828- Exercise- Shell.md
Normal file
105
translated/tech/20140107 Caffeinated 6.828- Exercise- Shell.md
Normal file
@ -0,0 +1,105 @@
|
||||
Caffeinated 6.828：练习 shell
|
||||
======
|
||||
|
||||
通过在 shell 中实现多项功能，该作业将使你更加熟悉 Unix 系统调用接口和 shell。你可以在支持 Unix API 的任何操作系统（一台 Linux Athena 机器、装有 Linux 或 Mac OS 的笔记本电脑等）上完成此作业。请在第一次上课前将你的 shell 提交到[网站][1]。
|
||||
|
||||
如果你在练习中遇到困难或不理解某些内容时，你不要害羞给[员工邮件列表][2]发送邮件，但我们确实希望全班的人能够自行处理这级别的 C 编程。如果你对 C 不是很熟悉，可以认为这个是你对 C 熟悉程度的检查。再说一次，如果你有任何问题，鼓励你向我们寻求帮助。
|
||||
|
||||
下载 xv6 shell 的[框架][3]，然后查看它。框架 shell 包含两个主要部分：解析 shell 命令并实现它们。解析器只能识别简单的 shell 命令，如下所示：
|
||||
```
|
||||
ls > y
|
||||
cat < y | sort | uniq | wc > y1
|
||||
cat y1
|
||||
rm y1
|
||||
ls | sort | uniq | wc
|
||||
rm y
|
||||
|
||||
```
|
||||
|
||||
将这些命令剪切并粘贴到 `t.sh `中。
|
||||
|
||||
你可以按如下方式编译框架 shell：
|
||||
```
|
||||
$ gcc sh.c
|
||||
|
||||
```
|
||||
|
||||
它会生成一个名为 `a.out` 的文件，你可以运行它：
|
||||
```
|
||||
$ ./a.out < t.sh
|
||||
|
||||
```
|
||||
|
||||
执行会崩溃，因为你还没有实现几个功能。在本作业的其余部分中，你将实现这些功能。
|
||||
|
||||
### 执行简单的命令
|
||||
|
||||
实现简单的命令，例如：
|
||||
```
|
||||
$ ls
|
||||
|
||||
```
|
||||
|
||||
解析器已经为你构建了一个 `execcmd`，所以你唯一需要编写的代码是 `runcmd` 中的 case ' '。要测试你可以运行 “ls”。你可能会发现查看 `exec` 的手册页是很有用的。输入 `man 3 exec`。
|
||||
|
||||
你不必实现引用（即将双引号之间的文本视为单个参数）。
|
||||
|
||||
### I/O 重定向
|
||||
|
||||
实现 I/O 重定向命令，这样你可以运行：
|
||||
```
|
||||
echo "6.828 is cool" > x.txt
|
||||
cat < x.txt
|
||||
|
||||
```
|
||||
|
||||
解析器已经识别出 '>' 和 '<'，并且为你构建了一个 `redircmd`，所以你的工作就是在 `runcmd` 中为这些符号填写缺少的代码。确保你的实现在上面的测试输入中正确运行。你可能会发现 `open`（`man 2 open`） 和 `close` 的 man 手册页很有用。
|
||||
|
||||
请注意，此 shell 不会像 `bash`、`tcsh`、`zsh` 或其他 UNIX shell 那样处理引号，并且你的示例文件 `x.txt` 预计包含引号。
|
||||
|
||||
### 实现管道
|
||||
|
||||
实现管道，这样你可以运行命令管道，例如：
|
||||
```
|
||||
$ ls | sort | uniq | wc
|
||||
|
||||
```
|
||||
|
||||
解析器已经识别出 “|”，并且为你构建了一个 `pipecmd`，所以你必须编写的唯一代码是 `runcmd` 中的 case '|'。测试你可以运行上面的管道。你可能会发现 `pipe`、`fork`、`close` 和 `dup` 的 man 手册页很有用。
|
||||
|
||||
现在你应该可以正确地使用以下命令：
|
||||
|
||||
```
|
||||
$ ./a.out < t.sh
|
||||
|
||||
```
|
||||
|
||||
无论是否完成挑战任务，不要忘记将你的答案提交给[网站][1]。
|
||||
|
||||
### 挑战练习
|
||||
|
||||
如果你想进一步尝试，可以将所选的任何功能添加到你的 shell。你可以尝试以下建议之一：
|
||||
|
||||
* 实现由 `;` 分隔的命令列表
|
||||
* 通过实现 `(` 和 `)` 来实现子 shell
|
||||
* 通过支持 `＆` 和 `wait` 在后台执行命令
|
||||
* 实现参数引用
|
||||
|
||||
|
||||
|
||||
所有这些都需要改变解析器和 `runcmd` 函数。
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://sipb.mit.edu/iap/6.828/lab/shell/
|
||||
|
||||
作者：[mit][a]
|
||||
译者：[geekpi](https://github.com/geekpi)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
||||
[a]:https://sipb.mit.edu
|
||||
[1]:https://exokernel.scripts.mit.edu/submit/
|
||||
[2]:mailto:sipb-iap-6.828@mit.edu
|
||||
[3]:https://sipb.mit.edu/iap/6.828/files/sh.c
|
||||
@ -0,0 +1,253 @@
|
||||
Oh My Fish! 让你的 Shell 漂亮起来
|
||||
=====
|
||||
|
||||
|
||||
|
||||
几天前，我们讨论了如何 [**安装** **Fish shell**][1]，一个健壮的，完全可用的 shell，带有许多很酷的功能，如自动建议，内置搜索功能，语法高亮显示，基于 web 配置等等。今天，我们将讨论如何使用 **Oh My Fish** (简称 **omf** ) 让我们的 Fish shell 变得漂亮且优雅。它是一个 Fishshell 框架，允许你安装扩展或更改 shell 外观的软件包。它简单易用，快速可扩展。使用 omf，你可以根据你的想法，很容易地安装主题，丰富你的外观和安装插件来调整你的 fish shell。
|
||||
|
||||
#### 安装 Oh My Fish
|
||||
|
||||
安装 omf 很简单。你要做的只是在你的 fish shell 中运行下面的命令。
|
||||
```
|
||||
curl -L https://get.oh-my.fish | fish
|
||||
```
|
||||
|
||||
![][3]
|
||||
|
||||
一旦安装完成，你将看到提示已经自动更改，如上图所所示。另外，你会注意到当前时间在 shell 窗口的右边。
|
||||
|
||||
就是这样。让我们继续并调整我们的 fish shell。
|
||||
|
||||
#### 现在，让我们将 Fish Shell 变漂亮
|
||||
|
||||
列出所有的安装包，运行：
|
||||
```
|
||||
omf list
|
||||
```
|
||||
|
||||
这条命令将显示已安装的主题和插件。请注意，包可以是主题或插件。安装包意味着安装主题和插件。
|
||||
|
||||
所有官方和社区支持的包（包括插件和主题）都托管在 [**Omf 主仓库**][4] 中。在这个主仓库中，你可以看到大量的仓库，其中包含大量的插件和主题。
|
||||
|
||||
现在让我们看一下可用的和已安装的主题列表。为此，运行：
|
||||
```
|
||||
omf theme
|
||||
```
|
||||
|
||||
![][5]
|
||||
|
||||
如你所见，我们只有一个已安装的主题，这是默认的，但是还有大量可用的主题。在安装之前，你在[**这里**][6]可以预览所有可用的主题。这个页面包含了所有的主题细节，特性，每个主题的截图示例，以及哪个主题适合谁。
|
||||
|
||||
**安装一个新主题**
|
||||
|
||||
请允许我安装一个主题，例如 **clearance theme - **一个极简的 fish shell 主题，供那些经常使用 git 的人使用。为此，运行：
|
||||
```
|
||||
omf install clearance
|
||||
```
|
||||
|
||||
![][7]
|
||||
|
||||
如上图所示，在安装新主题后，fish 的提示立即发生了变化。
|
||||
|
||||
让我浏览一下系统文件，看看它如何显示。
|
||||
|
||||
![][8]
|
||||
|
||||
看起来不坏！这是一个非常简单的主题。它将当前工作目录，文件夹和文件以不同的颜色区分开来。你可能会注意到，它还会在提示符的顶部显示当前工作目录。现在，**clearance** 是我的默认主题。
|
||||
|
||||
**改变主题**
|
||||
|
||||
就像我之前说的一样，这个主题在安装后被立即应用。如果你有多个主题，你可以使用以下命令切换到另一个不同的主题：
|
||||
```
|
||||
omf theme <theme-name>
|
||||
```
|
||||
|
||||
例如：
|
||||
```
|
||||
omf theme agnoster
|
||||
```
|
||||
|
||||
现在我正在使用 "agnoster" 主题。 agnoster 就是这样改变了我 shell 的外观。
|
||||
|
||||
![][9]
|
||||
|
||||
**安装插件**
|
||||
|
||||
例如，我想安装一个天气插件。为此，，只要运行：
|
||||
```
|
||||
omf install weather
|
||||
```
|
||||
|
||||
天气插件依赖于 [jq][10]（LCTT 译注：jq 是一个轻量级且灵活的命令行JSON处理器）。所以，你可能也需要安装 jq。它通常在 Linux 发行版的默认仓库中存在。因此，你可以使用默认的包管理器来安装它。例如，以下命令将在 Arch Linux 及其衍生版中安装 jq。
|
||||
```
|
||||
sudo pacman -S jq
|
||||
```
|
||||
|
||||
现在，在 fish shell 中使用以下命令查看天气：
|
||||
```
|
||||
weather
|
||||
```
|
||||
|
||||
![][11]
|
||||
|
||||
**寻找包**
|
||||
|
||||
要搜索主题或插件，请执行以下操作：
|
||||
```
|
||||
omf search <search_string>
|
||||
```
|
||||
|
||||
例如：
|
||||
```
|
||||
omf search nvm
|
||||
```
|
||||
|
||||
为了限制搜索的主题范围，使用 **-t** 选项。
|
||||
```
|
||||
omf search -t chain
|
||||
```
|
||||
|
||||
这条命令只会搜索主题名字中包含 "chain" 的主题。
|
||||
|
||||
为了限制搜索的插件范围，使用 **-p** 选项。
|
||||
```
|
||||
omf search -p emacs
|
||||
```
|
||||
|
||||
**更新包**
|
||||
|
||||
要仅更新核心功能（omf 本身），运行：
|
||||
```
|
||||
omf update omf
|
||||
```
|
||||
|
||||
如果是最新的，你会看到以下输出：
|
||||
```
|
||||
Oh My Fish is up to date.
|
||||
You are now using Oh My Fish version 6.
|
||||
Updating https://github.com/oh-my-fish/packages-main master... Done!
|
||||
```
|
||||
|
||||
更新所有包：
|
||||
```
|
||||
omf update
|
||||
```
|
||||
|
||||
要有选择地更新软件包，只需包含如下所示的包名称：
|
||||
```
|
||||
omf update clearance agnoster
|
||||
```
|
||||
|
||||
**显示关于包的信息**
|
||||
|
||||
当你想知道关于一个主题或插件的信息时，使用以下命令：
|
||||
```
|
||||
omf describe clearance
|
||||
```
|
||||
|
||||
这条命令将显示关于包的信息。
|
||||
```
|
||||
Package: clearance
|
||||
Description: A minimalist fish shell theme for people who use git
|
||||
Repository: https://github.com/oh-my-fish/theme-clearance
|
||||
Maintainer:
|
||||
```
|
||||
|
||||
**移除包**
|
||||
|
||||
移除一个包，例如 emacs，运行：
|
||||
```
|
||||
omf remove emacs
|
||||
```
|
||||
|
||||
**管理仓库**
|
||||
|
||||
默认情况下，当你安装了 Oh My Fish 时，会自动添加官方仓库。这个仓库包含了开发人员构建的所有包。要管理用户安装的仓库包，使用这条命令：
|
||||
```
|
||||
omf repositories [list|add|remove]
|
||||
```
|
||||
|
||||
列出所有安装的仓库，运行：
|
||||
```
|
||||
omf repositories list
|
||||
```
|
||||
|
||||
添加一个仓库：
|
||||
```
|
||||
omf repositories add <URL>
|
||||
```
|
||||
|
||||
例如：
|
||||
```
|
||||
omf repositories add https://github.com/ostechnix/theme-sk
|
||||
```
|
||||
|
||||
移除一个仓库：
|
||||
```
|
||||
omf repositories remove <repository-name>
|
||||
```
|
||||
|
||||
**Troubleshooting Oh My Fish**
|
||||
|
||||
如果出现了错误，omf 足够聪明来帮助你，它可以列出解决问题的方法。例如，我删除并安装了 clearance 包（这句不太理解，希望校正者注意），得到了文件冲突的错误。幸运的是，在继续之前，Oh My Fish 会指示我该怎么做。因此，我只是简单地运行了以下代码来了解如何修正错误。
|
||||
```
|
||||
omf doctor
|
||||
```
|
||||
|
||||
通过运行以下命令来解决错误：
|
||||
```
|
||||
rm ~/.config/fish/functions/fish_prompt.fish
|
||||
```
|
||||
|
||||
![][12]
|
||||
|
||||
无论你何时遇到问题，只要运行 'omf doctor' 命令，并尝试所有的建议方法。
|
||||
|
||||
**获取帮助**
|
||||
|
||||
显示帮助部分，运行：
|
||||
```
|
||||
omf -h
|
||||
```
|
||||
|
||||
或者
|
||||
```
|
||||
omf --help
|
||||
```
|
||||
|
||||
**卸载 Oh My Fish**
|
||||
|
||||
卸载 Oh My Fish，运行以下命令：
|
||||
```
|
||||
omf destroy
|
||||
```
|
||||
|
||||
继续前进，开始自定义你的 fish shell。获取更多细节，请参考项目的 GitHub 页面。
|
||||
|
||||
这就是全部了。我很快将会在这里开始另一个有趣的指导。在此之前，请继续关注 OSTechNix!
|
||||
|
||||
干杯！
|
||||
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
via: https://www.ostechnix.com/oh-fish-make-shell-beautiful/
|
||||
|
||||
作者：[SK][a]
|
||||
译者：[译者ID](https://github.com/译者ID)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
||||
[a]:https://www.ostechnix.com/author/sk/
|
||||
[1]:https://www.ostechnix.com/install-fish-friendly-interactive-shell-linux/
|
||||
[2]:data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7
|
||||
[3]:http://www.ostechnix.com/wp-content/uploads/2017/12/Oh-My-Fish-1-1.png()
|
||||
[4]:https://github.com/oh-my-fish
|
||||
[5]:http://www.ostechnix.com/wp-content/uploads/2017/12/Oh-My-Fish-5.png()
|
||||
[6]:https://github.com/oh-my-fish/oh-my-fish/blob/master/docs/Themes.md
|
||||
[7]:http://www.ostechnix.com/wp-content/uploads/2017/12/Oh-My-Fish-3.png()
|
||||
[8]:http://www.ostechnix.com/wp-content/uploads/2017/12/Oh-My-Fish-4.png()
|
||||
[9]:http://www.ostechnix.com/wp-content/uploads/2017/12/Oh-My-Fish-6.png()
|
||||
[10]:https://stedolan.github.io/jq/
|
||||
[11]:http://www.ostechnix.com/wp-content/uploads/2017/12/Oh-My-Fish-7.png()
|
||||
[12]:http://www.ostechnix.com/wp-content/uploads/2017/12/Oh-My-Fish-8.png()
|
||||
@ -1,241 +0,0 @@
|
||||
如何查找 Linux 中最大的 10 个文件
|
||||
======
|
||||
|
||||
|
||||
当系统的磁盘空间不足时，您可能更愿意使用 `df`、`du` 或 `ncdu` 命令进行检查，但这些命令只会显示当前目录的文件，并不会显示整个系统范围的文件。
|
||||
|
||||
您得花费大量的时间才能用上述命令获取系统中最大的文件，因为要进入到每个目录重复运行上述命令。
|
||||
|
||||
这个方法比较麻烦，也并不恰当。
|
||||
|
||||
如果是这样，那么该如何在 Linux 中找到最大的 10 个文件呢？
|
||||
|
||||
我在谷歌上搜索了很久，却没发现类似的文章，我反而看到了很多关于列出当前目录中最大的 10 个文件的文章。所以，我希望这篇文章对那些有类似需求的人有所帮助。
|
||||
|
||||
本教程中，我们将教您如何使用以下四种方法在 Linux 系统中查找最大的前 10 个文件。
|
||||
|
||||
### 方法 1：
|
||||
|
||||
在 Linux 中没有特定的命令可以直接执行此操作，因此我们需要将多个命令结合使用。
|
||||
|
||||
```
|
||||
# find / -type f -print0 | xargs -0 du -h | sort -rh | head -n 10
|
||||
|
||||
1.4G /swapfile
|
||||
1.1G /home/magi/ubuntu-17.04-desktop-amd64.iso
|
||||
564M /home/magi/.gdfuse/magi/cache/0B5nso_FPaZFqTFU0XzkzUlJUZzA
|
||||
378M /home/magi/.gdfuse/magi/cache/0B5nso_FPaZFqeldzUmhPeC03Zm8
|
||||
377M /home/magi/.gdfuse/magi/cache/0B5nso_FPaZFqRGd4V0VrOXM4YVU
|
||||
100M /usr/lib/x86_64-linux-gnu/libOxideQtCore.so.0
|
||||
93M /usr/lib/firefox/libxul.so
|
||||
84M /var/lib/snapd/snaps/core_3604.snap
|
||||
84M /var/lib/snapd/snaps/core_3440.snap
|
||||
84M /var/lib/snapd/snaps/core_3247.snap
|
||||
|
||||
```
|
||||
|
||||
**详解：**
|
||||
|
||||
**`find`**：在目录结构中搜索文件的命令
|
||||
|
||||
**`/`**：在整个系统（从根目录开始）中查找
|
||||
|
||||
**`-type`**：指定文件类型
|
||||
|
||||
**`f`**：普通文件
|
||||
|
||||
**`-print0`**：输出完整的文件名，其后跟一个空字符
|
||||
|
||||
**`|`**：控制操作符，将一条命令的输出传递给下一个命令以供进一步处理
|
||||
|
||||
**`xargs`**：将标准输入转换成命令行参数的命令
|
||||
|
||||
**`-0`**：以空字符（null）而不是空白字符（whitespace）（LCTT 译者注：即空格、制表符和换行）来分割记录
|
||||
|
||||
**`du -h`**：以可读格式计算磁盘空间使用情况的命令
|
||||
|
||||
**`sort`**：对文本文件进行排序的命令
|
||||
|
||||
**`-r`**：反转结果
|
||||
|
||||
**`-h`**：用可读格式打印输出
|
||||
|
||||
**`head`**：输出文件开头部分的命令
|
||||
|
||||
**`n -10`**：打印前 10 个文件
|
||||
|
||||
### 方法 2：
|
||||
|
||||
这是查找 Linux 系统中最大的前 10 个文件的另一种方法。我们依然使用多个命令共同完成这个任务。
|
||||
|
||||
```
|
||||
# find / -type f -exec du -Sh {} + | sort -rh | head -n 10
|
||||
|
||||
1.4G /swapfile
|
||||
1.1G /home/magi/ubuntu-17.04-desktop-amd64.iso
|
||||
564M /home/magi/.gdfuse/magi/cache/0B5nso_FPaZFqTFU0XzkzUlJUZzA
|
||||
378M /home/magi/.gdfuse/magi/cache/0B5nso_FPaZFqeldzUmhPeC03Zm8
|
||||
377M /home/magi/.gdfuse/magi/cache/0B5nso_FPaZFqRGd4V0VrOXM4YVU
|
||||
100M /usr/lib/x86_64-linux-gnu/libOxideQtCore.so.0
|
||||
93M /usr/lib/firefox/libxul.so
|
||||
84M /var/lib/snapd/snaps/core_3604.snap
|
||||
84M /var/lib/snapd/snaps/core_3440.snap
|
||||
84M /var/lib/snapd/snaps/core_3247.snap
|
||||
|
||||
```
|
||||
|
||||
**详解：**
|
||||
|
||||
**`find`**：在目录结构中搜索文件的命令
|
||||
|
||||
**`/`**：在整个系统（从根目录开始）中查找
|
||||
|
||||
**`-type`**：指定文件类型
|
||||
|
||||
**`f`**：普通文件
|
||||
|
||||
**`-exec`**：在所选文件上运行指定命令
|
||||
|
||||
**`du`**：计算文件占用的磁盘空间的命令
|
||||
|
||||
**`-S`**：不包含子目录的大小
|
||||
|
||||
**`-h`**：以可读格式打印
|
||||
|
||||
**`{}`**：递归地查找目录，统计每个文件占用的磁盘空间
|
||||
|
||||
**`|`**：控制操作符，将一条命令的输出传递给下一个命令以供进一步处理
|
||||
|
||||
**`sort`**：对文本文件进行按行排序的命令
|
||||
|
||||
**`-r`**：反转结果
|
||||
|
||||
**`-h`**：用可读格式打印输出
|
||||
|
||||
**`head`**：输出文件开头部分的命令
|
||||
|
||||
**`n -10`**：打印前 10 个文件
|
||||
|
||||
### 方法 3：
|
||||
|
||||
这里介绍另一种方法，在 Linux 系统中搜索最大的前 10 个文件。
|
||||
|
||||
```
|
||||
# find / -type f -print0 | xargs -0 du | sort -n | tail -10 | cut -f2 | xargs -I{} du -sh {}
|
||||
|
||||
84M /var/lib/snapd/snaps/core_3247.snap
|
||||
84M /var/lib/snapd/snaps/core_3440.snap
|
||||
84M /var/lib/snapd/snaps/core_3604.snap
|
||||
93M /usr/lib/firefox/libxul.so
|
||||
100M /usr/lib/x86_64-linux-gnu/libOxideQtCore.so.0
|
||||
377M /home/magi/.gdfuse/magi/cache/0B5nso_FPaZFqRGd4V0VrOXM4YVU
|
||||
378M /home/magi/.gdfuse/magi/cache/0B5nso_FPaZFqeldzUmhPeC03Zm8
|
||||
564M /home/magi/.gdfuse/magi/cache/0B5nso_FPaZFqTFU0XzkzUlJUZzA
|
||||
1.1G /home/magi/ubuntu-17.04-desktop-amd64.iso
|
||||
1.4G /swapfile
|
||||
|
||||
```
|
||||
|
||||
**详解：**
|
||||
|
||||
**`find`**：在目录结构中搜索文件的命令
|
||||
|
||||
**`/`**：在整个系统（从根目录开始）中查找
|
||||
|
||||
**`-type`**：指定文件类型
|
||||
|
||||
**`f`**：普通文件
|
||||
|
||||
**`-print0`**：输出完整的文件名，其后跟一个空字符
|
||||
|
||||
**`|`**：控制操作符，将一条命令的输出传递给下一个命令以供进一步处理
|
||||
|
||||
**`xargs`**：将标准输入转换成命令行参数的命令
|
||||
|
||||
**`-0`**：以空字符（null）而不是空白字符（whitespace）来分割记录
|
||||
|
||||
**`du`**：计算文件占用的磁盘空间的命令
|
||||
|
||||
**`sort`**：对文本文件进行按行排序的命令
|
||||
|
||||
**`-n`**：根据数字大小进行比较
|
||||
|
||||
**`tail -10`**：输出文件结尾部分的命令（最后 10 个文件）
|
||||
|
||||
**`cut`**：从每行删除特定部分的命令
|
||||
|
||||
**`-f2`**：只选择特定字段值
|
||||
|
||||
**`-I{}`**：将初始参数中出现的每个替换字符串都替换为从标准输入读取的名称
|
||||
|
||||
**`-s`**：仅显示每个参数的总和
|
||||
|
||||
**`-h`**：用可读格式打印输出
|
||||
|
||||
**`{}`**：递归地查找目录，统计每个文件占用的磁盘空间
|
||||
|
||||
### 方法 4：
|
||||
|
||||
还有一种在 Linux 系统中查找最大的前 10 个文件的方法。
|
||||
|
||||
```
|
||||
# find / -type f -ls | sort -k 7 -r -n | head -10 | column -t | awk '{print $7,$11}'
|
||||
|
||||
1494845440 /swapfile
|
||||
1085984380 /home/magi/ubuntu-17.04-desktop-amd64.iso
|
||||
591003648 /home/magi/.gdfuse/magi/cache/0B5nso_FPaZFqTFU0XzkzUlJUZzA
|
||||
395770383 /home/magi/.gdfuse/magi/cache/0B5nso_FPaZFqeldzUmhPeC03Zm8
|
||||
394891761 /home/magi/.gdfuse/magi/cache/0B5nso_FPaZFqRGd4V0VrOXM4YVU
|
||||
103999072 /usr/lib/x86_64-linux-gnu/libOxideQtCore.so.0
|
||||
97356256 /usr/lib/firefox/libxul.so
|
||||
87896064 /var/lib/snapd/snaps/core_3604.snap
|
||||
87793664 /var/lib/snapd/snaps/core_3440.snap
|
||||
87089152 /var/lib/snapd/snaps/core_3247.snap
|
||||
|
||||
```
|
||||
|
||||
**详解：**
|
||||
|
||||
**`find`**：在目录结构中搜索文件的命令
|
||||
|
||||
**`/`**：在整个系统（从根目录开始）中查找
|
||||
|
||||
**`-type`**：指定文件类型
|
||||
|
||||
**`f`**：普通文件
|
||||
|
||||
**`-ls`**：在标准输出中以 `ls -dils` 的格式列出当前文件
|
||||
|
||||
**`|`**：控制操作符，将一条命令的输出传递给下一个命令以供进一步处理
|
||||
|
||||
**`sort`**：对文本文件进行按行排序的命令
|
||||
|
||||
**`-k`**：按指定列进行排序
|
||||
|
||||
**`-r`**：反转结果
|
||||
|
||||
**`-n`**：根据数字大小进行比较
|
||||
|
||||
**`head`**：输出文件开头部分的命令
|
||||
|
||||
**`-10`**：打印前 10 个文件
|
||||
|
||||
**`column`**：将其输入格式化为多列的命令
|
||||
|
||||
**`-t`**：确定输入包含的列数并创建一个表
|
||||
|
||||
**`awk`**：样式扫描和处理语言
|
||||
|
||||
**`'{print $7,$11}'`**：只打印指定的列
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://www.2daygeek.com/how-to-find-search-check-print-top-10-largest-biggest-files-in-linux/
|
||||
|
||||
作者：[Magesh Maruthamuthu][a]
|
||||
译者：[jessie-pang](https://github.com/jessie-pang)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
||||
[a]:https://www.2daygeek.com/author/magesh/
|
||||
Loading…
Reference in New Issue
Block a user