mirror of
https://github.com/LCTT/TranslateProject.git
synced 2025-01-01 21:50:13 +08:00
littlebirdnest
GitHub
commit
640b335d04
@ -0,0 +1,175 @@
|
||||
[#]: subject: "Install Linux Mint with Windows 11 Dual Boot [Complete Guide]"
|
||||
[#]: via: "https://www.debugpoint.com/linux-mint-install-windows/"
|
||||
[#]: author: "Arindam https://www.debugpoint.com/author/admin1/"
|
||||
[#]: collector: "lkxed"
|
||||
[#]: translator: "gpchn"
|
||||
[#]: reviewer: "wxy"
|
||||
[#]: publisher: "wxy"
|
||||
[#]: url: "https://linux.cn/article-15073-1.html"
|
||||
|
||||
使用 Windows 11 双引导安装 Linux Mint
|
||||
======
|
||||
|
||||
|
||||
|
||||
> 将 Linux Mint 与 Windows 11（或 Windows 10）同时安装并制作双引导系统的完整指南。
|
||||
|
||||
如果你是新 Linux 用户，想在不删除 OEM 安装的 Windows 的情况下安装 Linux Mint，请遵循本指南。完成下面描述的步骤后，你应该拥有一个双引导系统，你可以在其中学习和在 Linux 系统中完成工作，而无需引导 Windows。
|
||||
|
||||
### 1、开始之前你需要什么？
|
||||
|
||||
启动到你的 Windows 系统并从官方网站下载 Linux Mint ISO 文件。 ISO 文件是 Linux Mint 的安装镜像，我们将在本指南中使用它。
|
||||
|
||||
在官网（图1），下载 Cinnamon 桌面版的 ISO（适合所有人）。
|
||||
|
||||
> **[下载链接][1]**
|
||||
|
||||
![图 1：从官网下载 Linux Mint][2]
|
||||
|
||||
下载后，将 U 盘插入你的系统。然后使用 Rufus 或 [Etcher][3] 将上面下载的 .ISO 文件写入该 USB 驱动器。
|
||||
|
||||
### 2、准备一个分区来安装 Linux Mint
|
||||
|
||||
正常情况下，Windows 笔记本电脑通常配备 C 盘和 D 盘。C 盘是安装 Windows 的地方。对于新的笔记本电脑，D 驱动器通常是空的（任何后续驱动器，如 E 等）。现在，你有两个选项可供选择：一是 **缩小 C 盘** 为额外的 Linux 安装腾出空间。第二个是**使用其他驱动器/分区**，例如 D 盘或 E盘。
|
||||
|
||||
选择你希望的方法。
|
||||
|
||||
如果你选择使用 D 盘或 E 盘用于 Linux 系统，请确保先禁用 BitLocker，然后再禁用现代 OEM 安装的 Windows 笔记本电脑附带的所有其他功能。
|
||||
|
||||
* 从开始菜单打开 Windows PowerShell 并键入以下命令（图 2）以禁用 BitLocker。根据你的目标驱动程序更改驱动器号（这里，我使用了驱动器 E）。
|
||||
|
||||
```
|
||||
manage-bde -off E
|
||||
```
|
||||
|
||||
![图 2：禁用 Windows 驱动器中的 BitLocker 以安装 Linux][4]
|
||||
|
||||
如果你选择缩小 C 盘（或任何其他驱动器），请从开始菜单打开“<ruby>磁盘管理<rt>Disk Management</rt></ruby>”，它将显示你的整个磁盘布局。
|
||||
|
||||
* 右键单击并在要缩小的驱动器上选择“<ruby>缩小卷<rt>Shrink Volume</rt></ruby>”（图 3），以便为 Linux Mint 腾出位置。
|
||||
|
||||
![图 3：磁盘分区中的压缩卷选项示例][5]
|
||||
|
||||
* 在下一个窗口中，在“<ruby>输入要缩小的空间量（以 MB 为单位）<rt>Enter the amount of space to shrink in MB</rt></ruby>”下以 MB 为单位提供你的分区大小（图 4）。显然，它应该小于或等于“<ruby>可用空间大小<rt>Size of available space</rt></ruby>”中提到的值。因此，对于 100 GB 的分区，给出 100*1024=102400 MB。
|
||||
* 完成后，单击“<ruby>缩小<rt>Shrink</rt></ruby>”。
|
||||
|
||||
![图 4：输入 Linux 分区的大小][6]
|
||||
|
||||
现在，你应该会看到一个“<ruby>未分配空间<rt>Unallocated Space</rt></ruby>”，如下所示（图 5）。右键单击它并选择“<ruby>新建简单卷<rt>New Simple Volume</rt></ruby>”。
|
||||
|
||||
![图 5：创建未分配空间][7]
|
||||
|
||||
* 此向导将使用文件系统准备和格式化分区。注意：你可以在 Windows 本身中或在 Linux Mint 安装期间执行此操作。Linux Mint 安装程序也为你提供了创建文件系统表和准备分区的选项，我建议你在这里做。
|
||||
* 在接下来的一系列屏幕中（图 6、7 和 8），以 MB 为单位给出分区大小，分配驱动器号（例如 D、E、F）和文件系统为 fat32。
|
||||
|
||||
![图 6：新建简单卷向导-page1][8]
|
||||
|
||||
![图 7：新建简单卷向导-page2][9]
|
||||
|
||||
![图 8：新建简单卷向导-page3][10]
|
||||
|
||||
* 最后，你应该会看到你的分区已准备好安装 Linux Mint。你应该在 Mint 安装期间按照以下步骤选择此选项。
|
||||
|
||||
![图 9：安装 Linux 的最终分区][11]
|
||||
|
||||
* 作为预防措施，**记下分区大小**（你刚刚在图 9 中作为示例创建的分区）以便在安装程序中快速识别它。
|
||||
|
||||
### 3、在 BIOS 中禁用安全启动
|
||||
|
||||
插入 USB 驱动器并重新启动系统。
|
||||
|
||||
* 开机时，反复按相应的功能键进入 BIOS。你的笔记本电脑型号的按键可能不同。下面是主要笔记本电脑品牌的参考。
|
||||
|
||||
| 笔记本厂商 | 进入 BIOS 的功能键 |
|
||||
| :- | :- |
|
||||
| 宏碁 | `F2` 或 `DEL` |
|
||||
| 华硕 | PC 使用 `F2`，主板是 `F2` 或 `DEL` |
|
||||
| 戴尔 | `F2` 或 `F12` |
|
||||
| 惠普 | `ESC` 或 `F10` |
|
||||
| Lenovo | `F2` 或 `Fn + F2` |
|
||||
| Lenovo（台式机） | F1` |
|
||||
| Lenovo（ThinkPad） | `Enter + F1` |
|
||||
| 微星 | `DEL` |
|
||||
| 微软 Surface 平板 | 按住音量增加键 |
|
||||
| ORIGIN PC | `F2` |
|
||||
| 三星 | `F2` |
|
||||
| 索尼 | `F1`、`F2` 或 `F3` |
|
||||
| 东芝 | `F2` |
|
||||
|
||||
* 你应该禁用 BIOS 安全设置并确保将启动设备优先级设置为 U 盘。
|
||||
* 然后按 `F10` 保存并退出。
|
||||
|
||||
### 4、安装 Linux Mint
|
||||
|
||||
如果一切顺利，你应该会看到一个安装 Linux Mint 的菜单。选择 “Start Linux Mint……” 选项。
|
||||
|
||||
![图 10：Linux Mint GRUB 菜单启动安装][12]
|
||||
|
||||
片刻之后，你应该会看到 Linux Mint Live 桌面。在桌面上，你应该会看到一个安装 Linux Mint 的图标以启动安装。
|
||||
|
||||
在下一组屏幕中，选择你的语言、键盘布局、选择安装多媒体编解码器并点击继续按钮。
|
||||
|
||||
在安装类型窗口中，选择 “<ruby>其他<rt>Something Else</rt></ruby>” 选项。
|
||||
|
||||
在下一个窗口（图 11）中，仔细选择以下内容：
|
||||
|
||||
![图11：选择 Windows 11 安装 Linux Mint 的目标分区][13]
|
||||
|
||||
* 在“<ruby>设备<rt>Device</rt></ruby>”下，选择刚刚创建的分区；你可以通过我之前提到的要记下的分区大小来识别它。
|
||||
* 然后点击“<ruby>更改<rt>Change</rt></ruby>”，在编辑分区窗口中，选择 Ext4 作为文件系统，选择格式化分区选项和挂载点为 `/`。
|
||||
* 单击“<ruby>确定<rt>OK</rt></ruby>”，然后为你的系统选择“<ruby>引导加载程序<rt> boot loader</rt></ruby>”；理想情况下，它应该是下拉列表中的第一个条目。
|
||||
* 仔细检查更改。因为一旦你点击立即安装，你的磁盘将被格式化，并且无法恢复。当你认为一切准备就绪，请单击“<ruby>立即安装<rt>Install Now</rt></ruby>”。
|
||||
|
||||
在以下屏幕中，选择你的位置，输入你的姓名并创建用于登录系统的用户 ID 和密码。安装应该开始（图 12）。
|
||||
|
||||
![图 12：安装中][14]
|
||||
|
||||
安装完成后（图 13），取出 U 盘并重新启动系统。
|
||||
|
||||
![图 13：安装完成][15]
|
||||
|
||||
如果一切顺利，在成功安装为双引导系统后，你应该会看到带有 Windows 11 和 Linux Mint 的 GRUB。
|
||||
|
||||
现在你可以使用 [Linux Mint][16] 并体验快速而出色的 Linux 发行版。
|
||||
|
||||
### 总结
|
||||
|
||||
在本教程中，我向你展示了如何在装有 OEM 的 Windows 的笔记本电脑或台式机中使用 Linux Mint 创建一个简单的双启动系统。这些步骤包括分区、创建可引导 USB、格式化和安装。
|
||||
|
||||
尽管上述说明适用于 Linux Mint 21 Vanessa；但是，它现在应该可以用于所有其他出色的 [Linux 发行版][17]。
|
||||
|
||||
如果你遵循本指南，请在下面的评论框中告诉我你的安装情况。
|
||||
|
||||
如果你成功了，欢迎来到自由世界！
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://www.debugpoint.com/linux-mint-install-windows/
|
||||
|
||||
作者：[Arindam][a]
|
||||
选题：[lkxed][b]
|
||||
译者：[gpchn](https://github.com/gpchn)
|
||||
校对：[wxy](https://github.com/wxy)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
||||
[a]: https://www.debugpoint.com/author/admin1/
|
||||
[b]: https://github.com/lkxed
|
||||
[1]: https://www.linuxmint.com/download.php
|
||||
[2]: https://www.debugpoint.com/wp-content/uploads/2022/09/Download-Linux-Mint-from-the-official-website.jpg
|
||||
[3]: https://www.debugpoint.com/etcher-bootable-usb-linux/
|
||||
[4]: https://www.debugpoint.com/wp-content/uploads/2022/09/Disable-BitLocker-in-Windows-Drives-to-install-Linux.jpg
|
||||
[5]: https://www.debugpoint.com/wp-content/uploads/2022/09/Example-of-Shrink-Volume-option-in-Disk-Partition-1024x453.jpg
|
||||
[6]: https://www.debugpoint.com/wp-content/uploads/2022/09/Enter-the-size-of-your-Linux-Partition.jpg
|
||||
[7]: https://www.debugpoint.com/wp-content/uploads/2022/09/Unallocated-space-is-created.jpg
|
||||
[8]: https://www.debugpoint.com/wp-content/uploads/2022/09/New-Simple-Volume-Wizard-page1.jpg
|
||||
[9]: https://www.debugpoint.com/wp-content/uploads/2022/09/New-Simple-Volume-Wizard-page2.jpg
|
||||
[10]: https://www.debugpoint.com/wp-content/uploads/2022/09/New-Simple-Volume-Wizard-page3.jpg
|
||||
[11]: https://www.debugpoint.com/wp-content/uploads/2022/09/Final-partition-for-installing-Linux.jpg
|
||||
[12]: https://www.debugpoint.com/wp-content/uploads/2022/09/Linux-Mint-GRUB-Menu-to-kick-off-installation.jpg
|
||||
[13]: https://www.debugpoint.com/wp-content/uploads/2022/09/Choose-the-target-partition-to-install-Linux-Mint-with-Windows-11.jpg
|
||||
[14]: https://www.debugpoint.com/wp-content/uploads/2022/09/Installation-is-in-progress.jpg
|
||||
[15]: https://www.debugpoint.com/wp-content/uploads/2022/09/Installation-is-complete.jpg
|
||||
[16]: https://www.debugpoint.com/linux-mint
|
||||
[17]: https://www.debugpoint.com/category/distributions
|
||||
[18]: https://www.debugpoint.com/install-java-17-ubuntu-mint/
|
||||
@ -3,46 +3,43 @@
|
||||
[#]: author: "Ankush Das https://news.itsfoss.com/author/ankush/"
|
||||
[#]: collector: "lkxed"
|
||||
[#]: translator: "littlebirdnest"
|
||||
[#]: reviewer: " "
|
||||
[#]: publisher: " "
|
||||
[#]: url: " "
|
||||
[#]: reviewer: "wxy"
|
||||
[#]: publisher: "wxy"
|
||||
[#]: url: "https://linux.cn/article-15069-1.html"
|
||||
|
||||
哇！基于 Rust 的 Redox OS 获得 390,000 美元的加密货币匿名捐赠
|
||||
======
|
||||
Redox OS 刚刚获得了大量匿名捐款。它将用于什么？令人兴奋的事情！
|
||||
|
||||
> Redox OS 刚刚获得了大量匿名捐款。它将用于什么？令人兴奋的事情！
|
||||
|
||||
![Wow! Rust-based Redox OS Gets an Anonymous Donation of $390,000 in Cryptocurrency][1]
|
||||
|
||||
[Redox OS][2] is a Unix-like operating system written in Rust.
|
||||
[Redox OS][2] 是一个用 Rust 编写的类 Unix 操作系统。
|
||||
|
||||
[Redox OS](https://www.redox-os.org/)是一个用 Rust 编写的类 Unix 操作系统。
|
||||
该项目由 Jeremy Soller 于 2015 年发起，他被公认为 [System76][3] 的首席工程师及[Pop!_OS][4] 的维护者。
|
||||
|
||||
该项目由 Jeremy Soller 于 2015 年发起，他被公认为 System76 的首席工程师[和](https://system76.com/)Pop [!_OS](https://pop.system76.com/)的维护者。
|
||||
我们还介绍了它今年早些时候的最后一个版本：[基于 Rust 的 Redox OS 0.7.0 推出增强硬件支持](https://news.itsfoss.com/redox-os-0-7-0-release/)。
|
||||
|
||||
我们还介绍了它今年早些时候的最后一个版本：
|
||||
|
||||
[基于 Rust 的 Redox OS 0.7.0 推出增强硬件支持](https://news.itsfoss.com/redox-os-0-7-0-release/)
|
||||
|
||||
虽然更新涉及允许它在更多硬件上启动的改进，但它可能不是大多数用户的日常驱动程序的替代品。
|
||||
虽然这些更新包括的改进可以让它在更多硬件上启动，但它可能不是大多数用户的日常驱动程序的替代品。
|
||||
|
||||
然而，这是一个令人兴奋的项目，值得关注。
|
||||
|
||||
**而在收到匿名捐款后，事情变得更加精彩**。
|
||||
|
||||
🤯刚刚有人向 Redux OS 的捐赠地址发送了**299 个以太坊**，相当于近**39 万美元**（加密货币市场涨跌互现）。
|
||||
🤯 刚刚有人向 Redux OS 的捐赠地址发送了 **299 个以太坊**，相当于近 **39 万美元**（加密货币市场涨跌不定）。
|
||||
|
||||
嗯，那是一大笔钱！
|
||||
|
||||
![A Video from YouTube][7]
|
||||
|
||||
根据杰里米的最后一条推文，他还没有立即决定如何处理它。
|
||||
根据 Jeremy 的最新推文，他还没有立即决定如何处理它。
|
||||
|
||||
> 一位匿名捐赠者刚刚向@redox_os捐赠地址发送了 299 Ether（相当于 393,000 美元） 。这个地址和交易都是公开的。我不知道如何处理这种规模的捐赠，但在进行一些研究后很快就会有更多细节。https://t.co/f3yBDghWSh
|
||||
> 一位匿名捐赠者刚刚向 @redox_os 捐赠地址发送了 299 以太（相当于 393,000 美元） 。这个地址和交易都是公开的。我不知道如何处理这种规模的捐赠，但在进行一些研究后很快就会有更多细节。https://t.co/f3yBDghWSh
|
||||
>
|
||||
|
||||
但是，对推文的回复给了我们一些很好的建议。
|
||||
|
||||
一些人建议将其捐赠给负责 Rust 语言的人，还有一些人建议用这笔钱来赞助学习 rust 和 OS 开发。
|
||||
一些人建议将其捐赠给负责 Rust 语言的人，还有一些人建议用这笔钱来赞助学习 Rust 和 OS 开发。
|
||||
|
||||
他肯定可以使用它来扩展 Redox OS 或其他任何需要该资源的东西。
|
||||
|
||||
@ -51,11 +48,10 @@ Redox OS 刚刚获得了大量匿名捐款。它将用于什么？令人兴奋
|
||||
或者，也许买一辆带有 Redox OS 标志的布加迪？好吧，一些推特用户对这一事件有过搞笑的回复！😂
|
||||
|
||||
> 这不是开源项目第一次收到大量的加密货币捐赠。Apache 软件基金会在 2018 年收到了价值 100 万美元的比特币。
|
||||
>
|
||||
|
||||
当 Jeremy 决定分享有关捐赠的更多细节以及他打算如何处理时，我将更新这篇文章。
|
||||
|
||||
💬 *您如何看待匿名捐赠给 Redox OS？如果你得到那笔捐款，你会怎么做？在下面的评论框中让我们知道您的想法。*
|
||||
💬 *你如何看待匿名捐赠给 Redox OS？如果你得到那笔捐款，你会怎么做？在下面的评论框中让我们知道你的想法。*
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
@ -63,8 +59,8 @@ via: https://news.itsfoss.com/redox-os-anonymous-donation/
|
||||
|
||||
作者：[Ankush Das][a]
|
||||
选题：[lkxed][b]
|
||||
译者：[littlebirdnest](https://github.com/译者ID)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
译者：[littlebirdnest](https://github.com/littlebirdnest)
|
||||
校对：[wxy](https://github.com/wxy)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
||||
@ -0,0 +1,213 @@
|
||||
[#]: subject: "GNOME 43: Top New Features and Release Wiki"
|
||||
[#]: via: "https://www.debugpoint.com/gnome-43/"
|
||||
[#]: author: "Arindam https://www.debugpoint.com/author/admin1/"
|
||||
[#]: collector: "lkxed"
|
||||
[#]: translator: "wxy"
|
||||
[#]: reviewer: "wxy"
|
||||
[#]: publisher: "wxy"
|
||||
[#]: url: "https://linux.cn/article-15071-1.html"
|
||||
|
||||
GNOME 43 发布，标志性的版本
|
||||
======
|
||||
|
||||
> 对 GNOME 43 桌面环境的各种功能的介绍，以及它给你的日常需求和工作流程带来的变化和影响。
|
||||
|
||||
![通过 GNOME OS 运行的 GNOME 43][1]
|
||||
|
||||
这篇文章总结了所有关于 GNOME 43 的必要信息，包括功能、发布时间表等等。GNOME 43 版本可能是自 GNOME 40 以来在功能和对你的工作流程影响最大的一个版本。
|
||||
|
||||
主要的变化包括更新的 Shell 和更快的性能，内含了 GTK4 和 libadwaita 的转换，翻新的文件应用和 Web 应用的奇妙变化。
|
||||
|
||||
所有这些必要的变化都是早该进行的，并将改变你在 GNOME 桌面上的传统工作流程，使你的工作效率更高。
|
||||
|
||||
### 时间表
|
||||
|
||||
GNOME 43 于 2022 年 9 月 21 日 [正式发布][2]。
|
||||
|
||||
* GNOME 43 测试版：2022 年 8 月 31 日
|
||||
* GNOME 43 候选版：2022 年 9 月 4 日
|
||||
* GNOME 43 最终版：2022 年 9 月 21 日
|
||||
|
||||
### GNOME 43 的功能
|
||||
|
||||
#### 1、核心 Shell 的变化
|
||||
|
||||
* 终于，得益于 Wayland 最近的工作，GNOME 有了对高分辨率的滚轮支持。所以，如果你有一个高分辨率的显示器，用一个高级的鼠标（比如罗技 MX Master 3）来滚动应该成为了一种享受。
|
||||
* 除了上述情况，GNOME 43 中的<ruby>直接扫描输出<rt>direct scanout</rt></ruby> 支持将有助于多显示器环境。
|
||||
* 服务器端的窗口装饰得到了基本的颜色支持。
|
||||
* Shell 还实现了一个功能，当焦点改变时，通知会消失，并不等待超时。
|
||||
* 和每个版本一样，你在整个桌面上会体验到更好的动画性能，改进了网格和概览导航以及关键的更新，这给你带来了顺滑的体验。
|
||||
|
||||
这些就是核心变化的关键总结。现在，让我们来谈谈快速设置。
|
||||
|
||||
#### 2、新的快速设置菜单
|
||||
|
||||
系统托盘中的快速设置完全改变了。快速设置项目和菜单现在采用药丸状的切换按钮，用鲜艳的颜色来显示系统中正在发生的事情。该菜单也是动态的，并支持层叠的菜单项目。此外，你可以在快速设置中选择音频设备。
|
||||
|
||||
这里有一个快速演示，更多的屏幕截图和文章，请阅读：[GNOME 43 快速设置][3]。
|
||||
|
||||
![GNOME 43 的快速设置演示][4]
|
||||
|
||||
#### 3. 文件应用
|
||||
|
||||
GNOME <ruby>文件应用<rt>Files</rt></ruby>在 GNOME 43 版本中增加了很多功能。这个应用程序的改进清单非常巨大。文件管理器是任何桌面环境中使用最多的应用程序。因此，文件应用中的变化对整个用户群的影响最大。
|
||||
|
||||
这是 GTK4 版的文件应用第一次亮相（它在 GNOME 42 发布时还没有准备好），它将会彻底改变你的工作流程。
|
||||
|
||||
我将尝试用一个简短的列表来解释其中的大部分内容。否则，这将是一篇冗长的文章。我将单独推送另一篇关于文件应用的功能的文章。
|
||||
|
||||
##### 自适应侧边栏
|
||||
|
||||
可以让你访问导航、收藏夹、网络驱动器等的文件应用侧边栏是响应式的。当文件应用窗口的大小达到一定程度时，它会 [自动隐藏][5] 自己。如果你工作时有很多打开的窗口，而且显示器较小，那么这是一个熟悉而方便的功能。
|
||||
|
||||
另一个令人兴奋的功能是，当侧边栏完全隐藏时，在左上方会出现一个图标，点击可使其可见。
|
||||
|
||||
![自动隐藏侧边栏的文件应用 43][6]
|
||||
|
||||
##### 徽章
|
||||
|
||||
很久以前，GNOME 中就有了徽章，后来它们消失了。因此，徽章在 GNOME 43 中以文件和目录旁边的小图标的形象卷土重来。这些图标代表着类型，如符号链接、只读等。此外，这些图标会根据你的主题改变它们的颜色，而且一个文件也可以有多个图标。
|
||||
|
||||
![GNOME 43 中的徽章][7]
|
||||
|
||||
##### 橡皮筋选择
|
||||
|
||||
接下来是期待已久的橡皮筋选择功能，它 [终于到来了][8]。现在你可以通过拖动选择机制来选择文件和文件夹。这是用户要求最多的功能之一。
|
||||
|
||||
![橡皮筋选择功能][9]
|
||||
|
||||
##### GtkColumnView 代替了 GtkTreeView
|
||||
|
||||
当你把鼠标放在列视图中的项目上时，你会看到一个焦点行，这是 GNOME 43 文件应用的另一个关键功能。但是它在 [树形视图不能显示][10]，可能计划在下一次迭代中实现。
|
||||
|
||||
![GtkColumnView 启用了焦点行][11]
|
||||
|
||||
##### 重新设计的属性窗口，具有交互式的权限和可执行文件检测功能
|
||||
|
||||
通过采用 GTK4，属性窗口 [完全改变了][12]。该窗口现在更加简洁，设计合理，只在需要的时候显示必要的项目。
|
||||
|
||||
此外，属性对话框可以确定文件类型并提供合适的选项。例如，如果你查看一个 Shell 脚本或文本文件的属性，你会得到一个选项，使其可执行。相反，图像文件的属性不会给你一个可执行的选项。
|
||||
|
||||
![智能属性窗口][13]
|
||||
|
||||
##### 标签式视图的改进
|
||||
|
||||
文件的标签式视图得到了一些 [额外的更新][14]。最值得注意的是，当拖动文件到标签时，可以适当地聚焦，在当前聚焦的标签之后创建标签，等等。
|
||||
|
||||
##### 重新设计的右键菜单
|
||||
|
||||
对文件或文件夹的主要右键菜单进行了分组。首先，打开选项被归入一个子菜单中。其次，复制/粘贴/剪切选项被合并到一个组中。最后，垃圾箱、重命名和压缩选项被归为一组。
|
||||
|
||||
此外，“<ruby>在终端打开<rt>Open in terminal</rt></ruby>”的选项对所有文件和文件夹都可用。然而，仍然缺失一个“创建新文件”的选项（这是我在这个版本中所期望的）。（LCTT 译者：预计 GNOME 44 文件应用将出现此功能）
|
||||
|
||||
![各种上下文菜单][15]
|
||||
|
||||
##### 其他变化
|
||||
|
||||
文件应用中其他醒目的变化是垃圾箱图标，以及其他位置（网络驱动器、磁盘）在右键菜单中有了属性菜单。
|
||||
|
||||
最后，文件应用的偏好窗口被重新设计，以显示更多的基本项目。重新设计后，普通用户可以很容易地找到适当的文件设置。
|
||||
|
||||
#### 4、Web 应用
|
||||
|
||||
让我们抽出一些时间来谈谈我们心爱的 Epiphany，又称 GNOME Web，是 GNOME 桌面上基于 WebKit 的原生网页浏览器。
|
||||
|
||||
这些更新早就应该开始了，并且终于从这个版本开始出现了。
|
||||
|
||||
首先，GNOME Web 现在支持 WebExtension API。它可以让你在网络中下载和安装火狐和谷歌浏览器的扩展。以下是做法：
|
||||
|
||||
* 从 Firefox 附加组件或谷歌 Chrome 扩展页面下载任何扩展文件（xpi 或 crx 文件）。
|
||||
* 点击汉堡菜单，选择<ruby>扩展程序<rt>Extensions</rt></ruby>。
|
||||
* 最后，点击<ruby>添加<rt>Add</rt></ruby>来安装它们。
|
||||
|
||||
WebExtension 的支持是使 Web 应用尽快可用的关键步骤。
|
||||
|
||||
其次，可以使用火狐浏览器同步选项，让你通过火狐浏览器账户登录 Web 应用，同步书签和其他浏览器项目。
|
||||
|
||||
![使用火狐账户登录 Web 应用][16]
|
||||
|
||||
Web 应用中其他值得注意的变化包括对 “查看源代码” 的支持、GTK4 的移植工作和一个更新的 PDF 库（PDF.js 2.13.216）。
|
||||
|
||||
Web 应用中仍然缺少的一个关键组件是 [通过 GStreamer 支持WebRTC][17]。一旦这个功能出现，它将是一个适合日常使用的浏览器。
|
||||
|
||||
希望有一天，我们都有一个体面的非火狐、非 Chromium 的替代浏览器。
|
||||
|
||||
#### 5、设置应用
|
||||
|
||||
在 <ruby>设置应用<rt>Settings</rt></ruby> 的窗口中，大部分改进和视觉微调在这个版本中出现。重要的变化包括警报中的 “狗叫声” 在经过长时间的 [有趣的对话][18] 后现在已经消失。
|
||||
|
||||
此外，引入了一个新的设备安全面板，日期和时间面板中的时区地图也修改了。
|
||||
|
||||
设置窗口的侧边栏也是响应式的，并为你提供自动隐藏功能，如上图所示的文件应用一样。
|
||||
|
||||
#### 6、软件应用
|
||||
|
||||
GNOME <ruby>软件应用<rt>Software</rt></ruby> 有两个关键的变化。这些变化使你可以在一个页面上查看应用程序的更多信息。
|
||||
|
||||
首先，一个新“该作者的其他应用程序”部分，为你提供了一个由当前应用程序的作者编写的应用程序列表。这有助于发现并告诉你应用作者有多受欢迎。
|
||||
|
||||
其次，GNOME 43 软件应用现在在一个单独的窗口中为你提供了 Flatpak 应用程序所需的详细权限列表。因此，你可以在安装它们之前确认该应用程序所需权限。
|
||||
|
||||
另一个关键的视觉变化是在应用程序概览主页面上新增了 “适用于 Fedora/任何发行版”部分，这需要配置。
|
||||
|
||||
![软件应用中的开发者的其他应用程序部分][19]
|
||||
|
||||
#### 7、气候变化墙纸
|
||||
|
||||
我不确定这个功能是否有了。因为我找不到它，但我听说过它。所以，我想我应该在这里提到它。
|
||||
|
||||
这个功能是，GNOME 43 带来了一张背景墙纸，显示了全球温度在几十年间是如何从 [海洋条纹][20] 上升的。该墙纸包含了垂直的彩色编码条，表示低和高的温度。我认为这是一个很好的提示，也是提高人们认识的努力。这是它在 GitLab 中的 [提交][21]。
|
||||
|
||||
此外，还有几张新的 [白天和黑夜][22] 的新鲜壁纸。
|
||||
|
||||
这就是我可以找到并总结的所有基本变化。除了这些，GNOME 43 还有大量的错误修复、性能改进和代码清理。
|
||||
|
||||
Fedora 37 将在发布时采用 GNOME 43，它的某些部分应该在 10 月发布的 Ubuntu 22.10 中出现。
|
||||
|
||||
### 总结
|
||||
|
||||
GNOME 43 是一个标志性的版本，因为它改变了几个基本的设计，影响了数百万用户的工作流程。快速设置的转变是非常棒的，而且早该如此了。此外，文件应用、Web 应用和设置应用的必要改变将提高你的工作效率。
|
||||
|
||||
此外，新功能的到来，同时保持了设计准则和美学的理念。一个好的用户界面需要一个深思熟虑的过程，而开发者在这个版本中做了完美的工作。
|
||||
|
||||
所以，差不多就是这样了。这就是 GNOME 43 的内容。如果你打算得到这个更新并想从 KDE 跳到 GNOME，请告诉我！
|
||||
|
||||
🗨️请在下面的评论区让我知道你最喜欢的功能。
|
||||
|
||||
举杯~
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://www.debugpoint.com/gnome-43/
|
||||
|
||||
作者：[Arindam][a]
|
||||
选题：[lkxed][b]
|
||||
译者：[wxy](https://github.com/wxy)
|
||||
校对：[wxy](https://github.com/wxy)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
||||
[a]: https://www.debugpoint.com/author/admin1/
|
||||
[b]: https://github.com/lkxed
|
||||
[1]: https://www.debugpoint.com/wp-content/uploads/2022/08/GNOME-43-Running-via-GNOME-OS.jpg
|
||||
[2]: https://debugpointnews.com/gnome-43-release/
|
||||
[3]: https://www.debugpoint.com/gnome-43-quick-settings/
|
||||
[4]: https://www.debugpoint.com/?attachment_id=10682
|
||||
[5]: https://gitlab.gnome.org/GNOME/nautilus/-/merge_requests/877
|
||||
[6]: https://www.debugpoint.com/?attachment_id=10684
|
||||
[7]: https://www.debugpoint.com/?attachment_id=10685
|
||||
[8]: https://gitlab.gnome.org/GNOME/nautilus/-/merge_requests/817
|
||||
[9]: https://www.debugpoint.com/wp-content/uploads/2022/08/Rubberband-Selection-Feature.gif
|
||||
[10]: https://gitlab.gnome.org/GNOME/nautilus/-/merge_requests/817
|
||||
[11]: https://www.debugpoint.com/wp-content/uploads/2022/08/GtkColumnView-enables-row-focus.gif
|
||||
[12]: https://gitlab.gnome.org/GNOME/nautilus/-/merge_requests/745
|
||||
[13]: https://www.debugpoint.com/wp-content/uploads/2022/08/Intelligent-properties-window.jpg
|
||||
[14]: https://gitlab.gnome.org/GNOME/nautilus/-/merge_requests/595
|
||||
[15]: https://www.debugpoint.com/?attachment_id=10689
|
||||
[16]: https://www.debugpoint.com/wp-content/uploads/2022/08/Login-to-Web-using-Firefox-account.jpg
|
||||
[17]: https://twitter.com/_philn_/status/1490391956970684422
|
||||
[18]: https://discourse.gnome.org/t/dog-barking-error-message-sound/9529/2
|
||||
[19]: https://www.debugpoint.com/wp-content/uploads/2022/08/Other-APPS-by-developer-section-in-Software.jpg
|
||||
[20]: https://showyourstripes.info/s/globe/
|
||||
[21]: https://gitlab.gnome.org/GNOME/gnome-backgrounds/-/commit/a142d5c88702112fae3b64a6d90d10488150d8c1
|
||||
[22]: https://www.debugpoint.com/custom-light-dark-wallpaper-gnome/
|
||||
@ -0,0 +1,39 @@
|
||||
[#]: subject: "Lawmakers Proposes A New Bill To Protect Open Source Software"
|
||||
[#]: via: "https://www.opensourceforu.com/2022/09/lawmakers-proposes-a-new-bill-to-protect-open-source-software/"
|
||||
[#]: author: "Laveesh Kocher https://www.opensourceforu.com/author/laveesh-kocher/"
|
||||
[#]: collector: "lkxed"
|
||||
[#]: translator: "littlebirdnest"
|
||||
[#]: reviewer: "wxy"
|
||||
[#]: publisher: "wxy"
|
||||
[#]: url: "https://linux.cn/article-15072-1.html"
|
||||
|
||||
美国立法者提出一项保护开源软件的新法案
|
||||
======
|
||||
|
||||
|
||||
|
||||
> 美国的《保护开源软件法案》将责成管理和预算办公室提供有关如何安全使用开源软件的说明。
|
||||
|
||||
美国立法者周四提出了一项要求，美国网络安全和基础设施安全局（CISA）需创建风险框架以提高开源软件安全性的措施。为了降低依赖开源代码的系统风险，各机构将利用该框架，CISA 将决定关键基础设施所有者和运营商是否也可以自愿使用它。
|
||||
|
||||
大多数系统依赖于免费提供的并由社区维护的开源软件来构建网站和应用程序；最大的用户之一是美国联邦政府。该立法由美国国土安全委员会主席兼高级成员、俄亥俄州共和党参议员 Sens. Rob Portman、R-Ohio 和 Gary Peters D-Mich 在一次听证会后提出，以回应在开源代码中发现的影响美国联邦系统和全球数百万其他系统的严重、广泛的 Log4j 漏洞。
|
||||
|
||||
“这一事件对联邦系统和关键基础设施公司——包括银行、医院和公用事业公司——构成了严重威胁，美国人每天都依赖这些公司提供基本服务，”彼得斯在公告中说。“这项明智的两党立法将有助于保护开源软件，并进一步加强我们的网络安全防御，防止网络犯罪分子和外国对手对全国网络发起的不断的攻击。”
|
||||
|
||||
这项《保护开源软件法》还要求美国管理和预算办公室为各机构发布关于保护开源软件的指南，在 CISA 网络安全咨询委员会中设立一个软件安全小组委员会，并要求 CISA 聘请开源软件专家协助处理网络事件。
|
||||
|
||||
在此之前，Peters 和 Portman 的提议已获得美国参议院一致通过并签署成为法律，以加强州和地方政府的网络防御，并迫使关键基础设施的所有者和运营商向 CISA 报告重大网络攻击和勒索软件付款。
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://www.opensourceforu.com/2022/09/lawmakers-proposes-a-new-bill-to-protect-open-source-software/
|
||||
|
||||
作者：[Laveesh Kocher][a]
|
||||
选题：[lkxed][b]
|
||||
译者：[littlebirdnest](https://github.com/littlebirdnest)
|
||||
校对：[wxy](https://github.com/wxy)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
||||
[a]: https://www.opensourceforu.com/author/laveesh-kocher/
|
||||
[b]: https://github.com/lkxed
|
||||
107
sources/news/20220924 UbuntuDDE Remix 22.04 LTS Released!.md
Normal file
107
sources/news/20220924 UbuntuDDE Remix 22.04 LTS Released!.md
Normal file
@ -0,0 +1,107 @@
|
||||
[#]: subject: "UbuntuDDE Remix 22.04 LTS Released!"
|
||||
[#]: via: "https://news.itsfoss.com/ubuntudde-remix-22-04-released/"
|
||||
[#]: author: "Sourav Rudra https://news.itsfoss.com/author/sourav/"
|
||||
[#]: collector: "lkxed"
|
||||
[#]: translator: " "
|
||||
[#]: reviewer: " "
|
||||
[#]: publisher: " "
|
||||
[#]: url: " "
|
||||
|
||||
UbuntuDDE Remix 22.04 LTS Released!
|
||||
======
|
||||
UbuntuDDE 22.04 LTS is here with Linux Kernel 5.15, DDE Store, and several upgrades.
|
||||
|
||||
![UbuntuDDE Remix 22.04 LTS Released!][1]
|
||||
|
||||
UbuntuDDE Remix is a distro that integrates the Deepin desktop environment on top of Ubuntu. Users who do not want to try Deepin distribution but like its user interface can try this out.
|
||||
|
||||
With [Ubuntu 22.04 LTS][2] as its base, it is a major upgrade.
|
||||
|
||||
Let us see what they have to offer.
|
||||
|
||||
### UbuntuDDE Remix 22.04: What's New?
|
||||
|
||||
UbuntuDDE Remix 22.04 uses Ubuntu 22.04 and Linux Kernel 5.15 as a solid base with the Deepin desktop environment, of course.
|
||||
|
||||
![ubuntudde remix 22.04 desktop][3]
|
||||
|
||||
They have added many new things to Ubuntu with this distro, such as a '**grand search bar**', upgraded versions of GTK-based applications, **new wallpapers**, the **DDE app store**, and more.
|
||||
|
||||
Let's look at some key changes UbuntuDDE Remix 22.04 brings to the table.
|
||||
|
||||
#### DDE Grand Search
|
||||
|
||||
![ubuntudde remix 22.04 grand search][4]
|
||||
|
||||
They call it the 'DDE Grand Search', which is a quick app launcher.
|
||||
|
||||
This enables users to search for anything quickly, whether apps, files, folders, or even a simple web search. It is activated by a keyboard shortcut (**Shift+Space bar**).
|
||||
|
||||
#### Linux Kernel 5.15
|
||||
|
||||
The distro also features Linux Kernel 5.15, which opens the doors to various features such as enhanced support for Intel Alder Lake CPUs, improvements to the NTFS3 drivers, improved Apple M1 support, and more.
|
||||
|
||||
We previously covered the highlights of this Linux Kernel release, you can check it out for more info:
|
||||
|
||||
[Linux Kernel 5.15 LTS Released! Brings Improved NTFS Driver to Linux][5]
|
||||
|
||||
#### New Installer Re-design
|
||||
|
||||
![ubuntudde remix 22.04 installer][7]
|
||||
|
||||
The installer on UbuntuDDE Remix seems to have taken a few pages from the book of the [QT installer framework][8], by providing QT-based styling in the Calamares installer with a very familiar layout going on with all the usual options for effortless installation of the distro.
|
||||
|
||||
#### New Wallpapers
|
||||
|
||||
![ubuntudde remix 22.04 new wallpapers][9]
|
||||
|
||||
The release also includes a host of new wallpapers to play around with.
|
||||
|
||||
#### 🛠️ Other Changes
|
||||
|
||||
You can expect the obvious Deepin applications and goodies that come with it. Some of the noteworthy mentions include:
|
||||
|
||||
* Pre-installed DDE App Store
|
||||
* LibreOffice 7.3.6.2
|
||||
* Regular software updates through OTA updates
|
||||
* Inclusion of upgraded DTK-based apps such as Deepin Music, Deepin Terminal, Boot Maker, System Monitor and more
|
||||
|
||||
### Download UbuntuDDE Remix 22.04
|
||||
|
||||
You can download the ISO file for UbuntuDDE Remix 22.04 by heading to its official [download page][10].
|
||||
|
||||
[UbuntuDDE Remix 22.04][11]
|
||||
|
||||
If you're looking for a live USB creation tool to install UbuntuDDE Remix, go through this guide to create one easily:
|
||||
|
||||
[Rufus for Linux? Here are the Best Live USB Creating Tools][12]
|
||||
|
||||
Note that it is not an official Ubuntu flavour (hence, "Remix") but it looks like something exciting to try with Deepin desktop on baord.
|
||||
|
||||
*💬 What do you think? Do you want to experience Deepin desktop on top of Ubuntu?*
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://news.itsfoss.com/ubuntudde-remix-22-04-released/
|
||||
|
||||
作者：[Sourav Rudra][a]
|
||||
选题：[lkxed][b]
|
||||
译者：[译者ID](https://github.com/译者ID)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
||||
[a]: https://news.itsfoss.com/author/sourav/
|
||||
[b]: https://github.com/lkxed
|
||||
[1]: https://news.itsfoss.com/content/images/size/w1200/2022/09/ubunturemixdde-22-04-lts.png
|
||||
[2]: https://news.itsfoss.com/ubuntu-22-04-release/
|
||||
[3]: https://news.itsfoss.com/content/images/2022/09/UbuntuDDE_Remix_22.04_Desktop.png
|
||||
[4]: https://news.itsfoss.com/content/images/2022/09/UbuntuDDE_Remix_22.04_Grand-Search.png
|
||||
[5]: https://news.itsfoss.com/linux-kernel-5-15-release/
|
||||
[7]: https://news.itsfoss.com/content/images/2022/09/UbuntuDDE_Remix_22.04_Installer.png
|
||||
[8]: https://doc.qt.io/qtinstallerframework/ifw-overview.html
|
||||
[9]: https://news.itsfoss.com/content/images/2022/09/UbuntuDDE_Remix_22.04_New_Wallpapers.png
|
||||
[10]: https://ubuntudde.com/download/
|
||||
[11]: https://bit.ly/ubuntudde-22-04-fosshost
|
||||
[12]: https://itsfoss.com/live-usb-creator-linux/
|
||||
[14]: https://www.humblebundle.com/books/linux-no-starch-press-books?partner=itsfoss
|
||||
@ -1,263 +0,0 @@
|
||||
[#]: collector: (lujun9972)
|
||||
[#]: translator: (aREversez)
|
||||
[#]: reviewer: ( )
|
||||
[#]: publisher: ( )
|
||||
[#]: url: ( )
|
||||
[#]: subject: (The Real Novelty of the ARPANET)
|
||||
[#]: via: (https://twobithistory.org/2021/02/07/arpanet.html)
|
||||
[#]: author: (Two-Bit History https://twobithistory.org)
|
||||
|
||||
The Real Novelty of the ARPANET
|
||||
======
|
||||
|
||||
If you run an image search for the word “ARPANET,” you will find lots of maps showing how the [government research network][1] expanded steadily across the country throughout the late ’60s and early ’70s. I’m guessing that most people reading or hearing about the ARPANET for the first time encounter one of these maps.
|
||||
|
||||
Obviously, the maps are interesting—it’s hard to believe that there were once so few networked computers that their locations could all be conveyed with what is really pretty lo-fi cartography. (We’re talking 1960s overhead projector diagrams here. You know the vibe.) But the problem with the maps, drawn as they are with bold lines stretching across the continent, is that they reinforce the idea that the ARPANET’s paramount achievement was connecting computers across the vast distances of the United States for the first time.
|
||||
|
||||
Today, the internet is a lifeline that keeps us tethered to each other even as an airborne virus has us all locked up indoors. So it’s easy to imagine that, if the ARPANET was the first draft of the internet, then surely the world that existed before it was entirely disconnected, since that’s where we’d be without the internet today, right? The ARPANET must have been a big deal because it connected people via computers when that hadn’t before been possible.
|
||||
|
||||
That view doesn’t get the history quite right. It also undersells what made the ARPANET such a breakthrough.
|
||||
|
||||
### The Debut
|
||||
|
||||
The Washington Hilton stands near the top of a small rise about a mile and a half northeast of the National Mall. Its two white-painted modern facades sweep out in broad semicircles like the wings of a bird. The New York Times, reporting on the hotel’s completion in 1965, remarked that the building looks “like a sea gull perched on a hilltop nest.”[1][2]
|
||||
|
||||
The hotel hides its most famous feature below ground. Underneath the driveway roundabout is an enormous ovoid event space known as the International Ballroom, which was for many years the largest pillar-less ballroom in DC. In 1967, the Doors played a concert there. In 1968, Jimi Hendrix also played a concert there. In 1972, a somewhat more sedate act took over the ballroom to put on the inaugural International Conference on Computing Communication, where a promising research project known as the ARPANET was demonstrated publicly for the first time.
|
||||
|
||||
The 1972 ICCC, which took place from October 24th to 26th, was attended by about 800 people.[2][3] It brought together all of the leading researchers in the nascent field of computer networking. According to internet pioneer Bob Kahn, “if somebody had dropped a bomb on the Washington Hilton, it would have destroyed almost all of the networking community in the US at that point.”[3][4]
|
||||
|
||||
Not all of the attendees were computer scientists, however. An advertisement for the conference claimed it would be “user-focused” and geared toward “lawyers, medical men, economists, and government men as well as engineers and communicators.”[4][5] Some of the conference’s sessions were highly technical, such as the session titled “Data Network Design Problems I” and its sequel session, “Data Network Design Problems II.” But most of the sessions were, as promised, focused on the potential social and economic impacts of computer networking. One session, eerily prescient today, sought to foster a discussion about how the legal system could act proactively “to safeguard the right of privacy in the computer data bank.”[5][6]
|
||||
|
||||
The ARPANET demonstration was intended as a side attraction of sorts for the attendees. Between sessions, which were held either in the International Ballroom or elsewhere on the lower level of the hotel, attendees were free to wander into the Georgetown Ballroom (a smaller ballroom/conference room down the hall from the big one),[6][7] where there were 40 terminals from a variety of manufacturers set up to access the ARPANET.[7][8] These terminals were dumb terminals—they only handled input and output and could do no computation on their own. (In fact, in 1972, it’s likely that all of these terminals were hardcopy terminals, i.e. teletype machines.) The terminals were all hooked up to a computer known as a Terminal Interface Message Processor or TIP, which sat on a raised platform in the middle of the room. The TIP was a kind of archaic router specially designed to connect dumb terminals to the ARPANET. Using the terminals and the TIP, the ICCC attendees could experiment with logging on and accessing some of the computers at the 29 host sites then comprising the ARPANET.[8][9]
|
||||
|
||||
To exhibit the network’s capabilities, researchers at the host sites across the country had collaborated to prepare 19 simple “scenarios” for users to experiment with. These scenarios were compiled into [a booklet][10] that was handed to conference attendees as they tentatively approached the maze of wiring and terminals.[9][11] The scenarios were meant to prove that the new technology worked but also that it was useful, because so far the ARPANET was “a highway system without cars,” and its Pentagon funders hoped that a public demonstration would excite more interest in the network.[10][12]
|
||||
|
||||
The scenarios thus showed off a diverse selection of the software that could be accessed over the ARPANET: There were programming language interpreters, one for a Lisp-based language at MIT and another for a numerical computing environment called Speakeasy hosted at UCLA; there were games, including a chess program and an implementation of Conway’s Game of Life; and—perhaps most popular among the conference attendees—there were several AI chat programs, including the famous ELIZA chat program developed at MIT by Joseph Weizenbaum.
|
||||
|
||||
The researchers who had prepared the scenarios were careful to list each command that users were expected to enter at their terminals. This was especially important because the sequence of commands used to connect to any given ARPANET host could vary depending on the host in question. To experiment with the AI chess program hosted on the MIT Artificial Intelligence Laboratory’s PDP-10 minicomputer, for instance, conference attendees were instructed to enter the following:
|
||||
|
||||
_`[LF]`, `[SP]`, and `[CR]` below stand for the line feed, space, and carriage return keys respectively. I’ve explained each command after `//`, but this syntax was not used for the annotations in the original._
|
||||
|
||||
```
|
||||
@r [LF] // Reset the TIP
|
||||
@e [SP] r [LF] // "Echo remote" setting, host echoes characters rather than TIP
|
||||
@L [SP] 134 [LF] // Connect to host number 134
|
||||
:login [SP] iccXXX [CR] // Login to the MIT AI Lab's system, where "XXX" should be user's initials
|
||||
:chess [CR] // Start chess program
|
||||
```
|
||||
|
||||
If conference attendees were successfully able to enter those commands, their reward was the opportunity to play around with some of the most cutting-edge chess software available at the time, where the layout of the board was represented like this:
|
||||
|
||||
```
|
||||
BR BN BB BQ BK BB BN BR
|
||||
BP BP BP BP ** BP BP BP
|
||||
-- ** -- ** -- ** -- **
|
||||
** -- ** -- BP -- ** --
|
||||
-- ** -- ** WP ** -- **
|
||||
** -- ** -- ** -- ** --
|
||||
WP WP WP WP -- WP WP WP
|
||||
WR WN WB WQ WK WB WN WR
|
||||
```
|
||||
|
||||
In contrast, to connect to UCLA’s IBM System/360 and run the Speakeasy numerical computing environment, conference attendees had to enter the following:
|
||||
|
||||
```
|
||||
@r [LF] // Reset the TIP
|
||||
@t [SP] o [SP] L [LF] // "Transmit on line feed" setting
|
||||
@i [SP] L [LF] // "Insert line feed" setting, i.e. send line feed with each carriage return
|
||||
@L [SP] 65 [LF] // Connect to host number 65
|
||||
tso // Connect to IBM Time-Sharing Option system
|
||||
logon [SP] icX [CR] // Log in with username, where "X" should be a freely chosen digit
|
||||
iccc [CR] // This is the password (so secure!)
|
||||
speakez [CR] // Start Speakeasy
|
||||
```
|
||||
|
||||
Successfully running that gauntlet gave attendees the power to multiply and transpose and do other operations on matrices as quickly as they could input them at their terminal:
|
||||
|
||||
```
|
||||
:+! a=m*transpose(m);a [CR]
|
||||
:+! eigenvals(a) [CR]
|
||||
```
|
||||
|
||||
Many of the attendees were impressed by the demonstration, but not for the reasons that we, from our present-day vantage point, might assume. The key piece of context hard to keep in mind today is that, in 1972, being able to use a computer remotely, even from a different city, was not new. Teletype devices had been used to talk to distant computers for decades already. Almost a full five years before the ICCC, Bill Gates was in a Seattle high school using a teletype to run his first BASIC programs on a General Electric computer housed elsewhere in the city. Merely logging in to a host computer and running a few commands or playing a text-based game was routine. The software on display here was pretty neat, but the two scenarios I’ve told you about so far could ostensibly have been experienced without going over the ARPANET.
|
||||
|
||||
Of course, something new was happening under the hood. The lawyers, policy-makers, and economists at the ICCC might have been enamored with the clever chess program and the chat bots, but the networking experts would have been more interested in two other scenarios that did a better job of demonstrating what the ARPANET project had achieved.
|
||||
|
||||
The first of these scenarios involved a program called `NETWRK` running on MIT’s ITS operating system. The `NETWRK` command was the entrypoint for several subcommands that could report various aspects of the ARPANET’s operating status. The `SURVEY` subcommand reported which hosts on the network were functioning and available (they all fit on a single list), while the `SUMMARY.OF.SURVEY` subcommand aggregated the results of past `SURVEY` runs to report an “up percentage” for each host as well as how long, on average, it took for each host to respond to messages. The output of the `SUMMARY.OF.SURVEY` subcommand was a table that looked like this:
|
||||
|
||||
```
|
||||
--HOST-- -#- -%-UP- -RESP-
|
||||
UCLA-NMC 001 097% 00.80
|
||||
SRI-ARC 002 068% 01.23
|
||||
UCSB-75 003 059% 00.63
|
||||
...
|
||||
```
|
||||
|
||||
The host number field, as you can see, has room for no more than three digits (ha!). Other `NETWRK` subcommands allowed users to look at summary of survey results over a longer historical period or to examine the log of survey results for a single host.
|
||||
|
||||
The second of these scenarios featured a piece of software called the SRI-ARC Online System being developed at Stanford. This was a fancy piece of software with lots of functionality (it was the software system that Douglas Engelbart demoed in the “Mother of All Demos”), but one of the many things it could do was make use of what was essentially a file hosting service run on the host at UC Santa Barbara. From a terminal at the Washington Hilton, conference attendees could copy a file created at Stanford onto the host at UCSB simply by running a `copy` command and answering a few of the computer’s questions:
|
||||
|
||||
_`[ESC]`, `[SP]`, and `[CR]` below stand for the escape, space, and carriage return keys respectively. The words in parentheses are prompts printed by the computer. The escape key is used to autocomplete the filename on the third line. The file being copied here is called `<system>sample.txt;1`, where the trailing one indicates the file’s version number and `<system>` indicates the directory. This was a convention for filenames used by the TENEX operating system._[11][13]
|
||||
|
||||
```
|
||||
@copy
|
||||
(TO/FROM UCSB) to
|
||||
(FILE) <system>sample [ESC] .TXT;1 [CR]
|
||||
(CREATE/REPLACE) create
|
||||
```
|
||||
|
||||
These two scenarios might not look all that different from the first two, but they were remarkable. They were remarkable because they made it clear that, on the ARPANET, humans could talk to computers but computers could also talk to _each other._ The `SURVEY` results collected at MIT weren’t collected by a human regularly logging in to each machine to check if it was up—they were collected by a program that knew how to talk to the other machines on the network. Likewise, the file transfer from Stanford to UCSB didn’t involve any humans sitting at terminals at either Stanford or UCSB—the user at a terminal in Washington DC was able to get the two computers to talk each other merely by invoking a piece of software. Even more, it didn’t matter which of the 40 terminals in the Ballroom you were sitting at, because you could view the MIT network monitoring statistics or store files at UCSB using any of the terminals with almost the same sequence of commands.
|
||||
|
||||
This is what was totally new about the ARPANET. The ICCC demonstration didn’t just involve a human communicating with a distant computer. It wasn’t just a demonstration of remote I/O. It was a demonstration of software remotely communicating with other software, something nobody had seen before.
|
||||
|
||||
To really appreciate why it was this aspect of the ARPANET project that was important and not the wires-across-the-country, physical connection thing that the host maps suggest (the wires were leased phone lines anyhow and were already there!), consider that, before the ARPANET project began in 1966, the ARPA offices in the Pentagon had a terminal room. Inside it were three terminals. Each connected to a different computer; one computer was at MIT, one was at UC Berkeley, and another was in Santa Monica.[12][14] It was convenient for the ARPA staff that they could use these three computers even from Washington DC. But what was inconvenient for them was that they had to buy and maintain terminals from three different manufacturers, remember three different login procedures, and familiarize themselves with three different computing environments in order to use the computers. The terminals might have been right next to each other, but they were merely extensions of the host computing systems on the other end of the wire and operated as differently as the computers did. Communicating with a distant computer was possible before the ARPANET; the problem was that the heterogeneity of computing systems limited how sophisticated the communication could be.
|
||||
|
||||
### Come Together, Right Now
|
||||
|
||||
So what I’m trying to drive home here is that there is an important distinction between statement A, “the ARPANET connected people in different locations via computers for the first time,” and statement B, “the ARPANET connected computer systems to each other for the first time.” That might seem like splitting hairs, but statement A elides some illuminating history in a way that statement B does not.
|
||||
|
||||
To begin with, the historian Joy Lisi Rankin has shown that people were socializing in cyberspace well before the ARPANET came along. In _A People’s History of Computing in the United States_, she describes several different digital communities that existed across the country on time-sharing networks prior to or apart from the ARPANET. These time-sharing networks were not, technically speaking, computer networks, since they consisted of a single mainframe computer running computations in a basement somewhere for many dumb terminals, like some portly chthonic creature with tentacles sprawling across the country. But they nevertheless enabled most of the social behavior now connoted by the word “network” in a post-Facebook world. For example, on the Kiewit Network, which was an extension of the Dartmouth Time-Sharing System to colleges and high schools across the Northeast, high school students collaboratively maintained a “gossip file” that allowed them to keep track of the exciting goings-on at other schools, “creating social connections from Connecticut to Maine.”[13][15] Meanwhile, women at Mount Holyoke College corresponded with men at Dartmouth over the network, perhaps to arrange dates or keep in touch with boyfriends.[14][16] This was all happening in the 1960s. Rankin argues that by ignoring these early time-sharing networks we impoverish our understanding of how American digital culture developed over the last 50 years, leaving room for a “Silicon Valley mythology” that credits everything to the individual genius of a select few founding fathers.
|
||||
|
||||
As for the ARPANET itself, if we recognize that the key challenge was connecting the computer _systems_ and not just the physical computers, then that might change what we choose to emphasize when we tell the story of the innovations that made the ARPANET possible. The ARPANET was the first ever packet-switched network, and lots of impressive engineering went into making that happen. I think it’s a mistake, though, to say that the ARPANET was a breakthrough because it was the first packet-switched network and then leave it at that. The ARPANET was meant to make it easier for computer scientists across the country to collaborate; that project was as much about figuring out how different operating systems and programs written in different languages would interface with each other than it was about figuring out how to efficiently ferry data back and forth between Massachusetts and California. So the ARPANET was the first packet-switched network, but it was also an amazing standards success story—something I find especially interesting given [how][17] [many][18] [times][19] I’ve written about failed standards on this blog.
|
||||
|
||||
Inventing the protocols for the ARPANET was an afterthought even at the time, so naturally the job fell to a group made up largely of graduate students. This group, later known as the Network Working Group, met for the first time at UC Santa Barbara in August of 1968.[15][20] There were 12 people present at that first meeting, most of whom were representatives from the four universities that were to be the first host sites on the ARPANET when the equipment was ready.[16][21] Steve Crocker, then a graduate student at UCLA, attended; he told me over a Zoom call that it was all young guys at that first meeting, and that Elmer Shapiro, who chaired the meeting, was probably the oldest one there at around 38. ARPA had not put anyone in charge of figuring out how the computers would communicate once they were connected, but it was obvious that some coordination was necessary. As the group continued to meet, Crocker kept expecting some “legitimate adult” with more experience and authority to fly out from the East Coast to take over, but that never happened. The Network Working Group had ARPA’s tacit approval—all those meetings involved lots of long road trips, and ARPA money covered the travel expenses—so they were it.[17][22]
|
||||
|
||||
The Network Working Group faced a huge challenge. Nobody had ever sat down to connect computer systems together in a general-purpose way; that flew against all of the assumptions that prevailed in computing in the late 1960s:
|
||||
|
||||
> The typical mainframe of the period behaved as if it were the only computer in the universe. There was no obvious or easy way to engage two diverse machines in even the minimal communication needed to move bits back and forth. You could connect machines, but once connected, what would they say to each other? In those days a computer interacted with devices that were attached to it, like a monarch communicating with his subjects. Everything connected to the main computer performed a specific task, and each peripheral device was presumed to be ready at all times for a fetch-my-slippers type command…. Computers were strictly designed for this kind of interaction; they send instructions to subordinate card readers, terminals, and tape units, and they initiate all dialogues. But if another device in effect tapped the computer on the shoulder with a signal and said, “Hi, I’m a computer too,” the receiving machine would be stumped.[18][23]
|
||||
|
||||
As a result, the Network Working Group’s progress was initially slow.[19][24] The group did not settle on an “official” specification for any protocol until June, 1970, nearly two years after the group’s first meeting.[20][25]
|
||||
|
||||
But by the time the ARPANET was to be shown off at the 1972 ICCC, all the key protocols were in place. A scenario like the chess scenario exercised many of them. When a user ran the command `@e r`, short for `@echo remote`, that instructed the TIP to make use of a facility in the new TELNET virtual teletype protocol to inform the remote host that it should echo the user’s input. When a user then ran the command `@L 134`, short for `@login 134`, that caused the TIP to invoke the Initial Connection Protocol with host 134, which in turn would cause the remote host to allocate all the necessary resources for the connection and drop the user into a TELNET session. (The file transfer scenario I described may well have made use of the File Transfer Protocol, though that protocol was only ready shortly before the conference.[21][26]) All of these protocols were known as “level three” protocols, and below them were the host-to-host protocol at level two (which defined the basic format for the messages the hosts should expect from each other), and the host-to-IMP protocol at level one (which defined how hosts communicated with the routing equipment they were linked to). Incredibly, the protocols all worked.
|
||||
|
||||
In my view, the Network Working Group was able to get everything together in time and just generally excel at its task because it adopted an open and informal approach to standardization, as exemplified by the famous Request for Comments (RFC) series of documents. These documents, originally circulated among the members of the Network Working Group by snail mail, were a way of keeping in touch between meetings and soliciting feedback to ideas. The “Request for Comments” framing was suggested by Steve Crocker, who authored the first RFC and supervised the RFC mailing list in the early years, in an attempt to emphasize the open-ended and collaborative nature of what the group was trying to do. That framing, and the availability of the documents themselves, made the protocol design process into a melting pot of contributions and riffs on other people’s contributions where the best ideas could emerge without anyone losing face. The RFC process was a smashing success and is still used to specify internet standards today, half a century later.
|
||||
|
||||
It’s this legacy of the Network Working Group that I think we should highlight when we talk about ARPANET’s impact. Though today one of the most magical things about the internet is that it can connect us with people on the other side of the planet, it’s only slightly facetious to say that that technology has been with us since the 19th century. Physical distance was conquered well before the ARPANET by the telegraph. The kind of distance conquered by the ARPANET was instead the logical distance between the operating systems, character codes, programming languages, and organizational policies employed at each host site. Implementing the first packet-switched network was of course a major feat of engineering that should also be mentioned, but the problem of agreeing on standards to connect computers that had never been designed to play nice with each other was the harder of the two big problems involved in building the ARPANET—and its solution was the most miraculous part of the ARPANET story.
|
||||
|
||||
In 1981, ARPA issued a “Completion Report” reviewing the first decade of the ARPANET’s history. In a section with the belabored title, “Technical Aspects of the Effort Which Were Successful and Aspects of the Effort Which Did Not Materialize as Originally Envisaged,” the authors wrote:
|
||||
|
||||
> Possibly the most difficult task undertaken in the development of the ARPANET was the attempt—which proved successful—to make a number of independent host computer systems of varying manufacture, and varying operating systems within a single manufactured type, communicate with each other despite their diverse characteristics.[22][27]
|
||||
|
||||
There you have it from no less a source than the federal government of the United States.
|
||||
|
||||
_If you enjoyed this post, more like it come out every four weeks! Follow [@TwoBitHistory][28] on Twitter or subscribe to the [RSS feed][29] to make sure you know when a new post is out._
|
||||
|
||||
_Previously on TwoBitHistory…_
|
||||
|
||||
> It's been too long, I know, but I finally got around to writing a new post. This one is about how REST APIs should really be known as FIOH APIs instead (Fuck It, Overload HTTP):<https://t.co/xjMZVZgsEz>
|
||||
>
|
||||
> — TwoBitHistory (@TwoBitHistory) [June 28, 2020][30]
|
||||
|
||||
1. “Hilton Hotel Opens in Capital Today.” _The New York Times_, 20 March 1965, <https://www.nytimes.com/1965/03/20/archives/hilton-hotel-opens-in-capital-today.html?searchResultPosition=1>. Accessed 7 Feb. 2021. [↩︎][31]
|
||||
|
||||
2. James Pelkey. _Entrepreneurial Capitalism and Innovation: A History of Computer Communications 1968-1988,_ Chapter 4, Section 12, 2007, <http://www.historyofcomputercommunications.info/Book/4/4.12-ICCC%20Demonstration71-72.html>. Accessed 7 Feb. 2021. [↩︎][32]
|
||||
|
||||
3. Katie Hafner and Matthew Lyon. _Where Wizards Stay Up Late: The Origins of the Internet_. New York, Simon & Schuster, 1996, p. 178. [↩︎][33]
|
||||
|
||||
4. “International Conference on Computer Communication.” _Computer_, vol. 5, no. 4, 1972, p. c2, <https://www.computer.org/csdl/magazine/co/1972/04/01641562/13rRUxNmPIA>. Accessed 7 Feb. 2021. [↩︎][34]
|
||||
|
||||
5. “Program for the International Conference on Computer Communication.” _The Papers of Clay T. Whitehead_, Box 42, <https://d3so5znv45ku4h.cloudfront.net/Box+042/013_Speech-International+Conference+on+Computer+Communications,+Washington,+DC,+October+24,+1972.pdf>. Accessed 7 Feb. 2021. [↩︎][35]
|
||||
|
||||
6. It’s actually not clear to me which room was used for the ARPANET demonstration. Lots of sources talk about a “ballroom,” but the Washington Hilton seems to consider the room with the name “Georgetown” more of a meeting room. So perhaps the demonstration was in the International Ballroom instead. But RFC 372 alludes to a booking of the “Georgetown Ballroom” for the demonstration. A floorplan of the Washington Hilton can be found [here][36]. [↩︎][37]
|
||||
|
||||
7. Hafner, p. 179. [↩︎][38]
|
||||
|
||||
8. ibid., p. 178. [↩︎][39]
|
||||
|
||||
9. Bob Metcalfe. “Scenarios for Using the ARPANET.” _Collections-Computer History Museum_, <https://www.computerhistory.org/collections/catalog/102784024>. Accessed 7 Feb. 2021. [↩︎][40]
|
||||
|
||||
10. Hafner, p. 176. [↩︎][41]
|
||||
|
||||
11. Robert H. Thomas. “Planning for ACCAT Remote Site Operations.” BBN Report No. 3677, October 1977, <https://apps.dtic.mil/sti/pdfs/ADA046366.pdf>. Accessed 7 Feb. 2021. [↩︎][42]
|
||||
|
||||
12. Hafner, p. 12. [↩︎][43]
|
||||
|
||||
13. Joy Lisi Rankin. _A People’s History of Computing in the United States_. Cambridge, MA, Harvard University Press, 2018, p. 84. [↩︎][44]
|
||||
|
||||
14. Rankin, p. 93. [↩︎][45]
|
||||
|
||||
15. Steve Crocker. Personal interview. 17 Dec. 2020. [↩︎][46]
|
||||
|
||||
16. Crocker sent me the minutes for this meeting. The document lists everyone who attended. [↩︎][47]
|
||||
|
||||
17. Steve Crocker. Personal interview. [↩︎][48]
|
||||
|
||||
18. Hafner, p. 146. [↩︎][49]
|
||||
|
||||
19. “Completion Report / A History of the ARPANET: The First Decade.” BBN Report No. 4799, April 1981, <https://walden-family.com/bbn/arpanet-completion-report.pdf>, p. II-13. [↩︎][50]
|
||||
|
||||
20. I’m referring here to RFC 54, “Official Protocol Proffering.” [↩︎][51]
|
||||
|
||||
21. Hafner, p. 175. [↩︎][52]
|
||||
|
||||
22. “Completion Report / A History of the ARPANET: The First Decade,” p. II-29. [↩︎][53]
|
||||
|
||||
|
||||
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://twobithistory.org/2021/02/07/arpanet.html
|
||||
|
||||
作者：[Two-Bit History][a]
|
||||
选题：[lujun9972][b]
|
||||
译者：[aREversez](https://github.com/aREversez)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
||||
[a]: https://twobithistory.org
|
||||
[b]: https://github.com/lujun9972
|
||||
[1]: https://en.wikipedia.org/wiki/ARPANET
|
||||
[2]: tmp.pnPpRrCI3S#fn:1
|
||||
[3]: tmp.pnPpRrCI3S#fn:2
|
||||
[4]: tmp.pnPpRrCI3S#fn:3
|
||||
[5]: tmp.pnPpRrCI3S#fn:4
|
||||
[6]: tmp.pnPpRrCI3S#fn:5
|
||||
[7]: tmp.pnPpRrCI3S#fn:6
|
||||
[8]: tmp.pnPpRrCI3S#fn:7
|
||||
[9]: tmp.pnPpRrCI3S#fn:8
|
||||
[10]: https://archive.computerhistory.org/resources/access/text/2019/07/102784024-05-001-acc.pdf
|
||||
[11]: tmp.pnPpRrCI3S#fn:9
|
||||
[12]: tmp.pnPpRrCI3S#fn:10
|
||||
[13]: tmp.pnPpRrCI3S#fn:11
|
||||
[14]: tmp.pnPpRrCI3S#fn:12
|
||||
[15]: tmp.pnPpRrCI3S#fn:13
|
||||
[16]: tmp.pnPpRrCI3S#fn:14
|
||||
[17]: https://twobithistory.org/2018/05/27/semantic-web.html
|
||||
[18]: https://twobithistory.org/2018/12/18/rss.html
|
||||
[19]: https://twobithistory.org/2020/01/05/foaf.html
|
||||
[20]: tmp.pnPpRrCI3S#fn:15
|
||||
[21]: tmp.pnPpRrCI3S#fn:16
|
||||
[22]: tmp.pnPpRrCI3S#fn:17
|
||||
[23]: tmp.pnPpRrCI3S#fn:18
|
||||
[24]: tmp.pnPpRrCI3S#fn:19
|
||||
[25]: tmp.pnPpRrCI3S#fn:20
|
||||
[26]: tmp.pnPpRrCI3S#fn:21
|
||||
[27]: tmp.pnPpRrCI3S#fn:22
|
||||
[28]: https://twitter.com/TwoBitHistory
|
||||
[29]: https://twobithistory.org/feed.xml
|
||||
[30]: https://twitter.com/TwoBitHistory/status/1277259930555363329?ref_src=twsrc%5Etfw
|
||||
[31]: tmp.pnPpRrCI3S#fnref:1
|
||||
[32]: tmp.pnPpRrCI3S#fnref:2
|
||||
[33]: tmp.pnPpRrCI3S#fnref:3
|
||||
[34]: tmp.pnPpRrCI3S#fnref:4
|
||||
[35]: tmp.pnPpRrCI3S#fnref:5
|
||||
[36]: https://www3.hilton.com/resources/media/hi/DCAWHHH/en_US/pdf/DCAWH.Floorplans.Apr25.pdf
|
||||
[37]: tmp.pnPpRrCI3S#fnref:6
|
||||
[38]: tmp.pnPpRrCI3S#fnref:7
|
||||
[39]: tmp.pnPpRrCI3S#fnref:8
|
||||
[40]: tmp.pnPpRrCI3S#fnref:9
|
||||
[41]: tmp.pnPpRrCI3S#fnref:10
|
||||
[42]: tmp.pnPpRrCI3S#fnref:11
|
||||
[43]: tmp.pnPpRrCI3S#fnref:12
|
||||
[44]: tmp.pnPpRrCI3S#fnref:13
|
||||
[45]: tmp.pnPpRrCI3S#fnref:14
|
||||
[46]: tmp.pnPpRrCI3S#fnref:15
|
||||
[47]: tmp.pnPpRrCI3S#fnref:16
|
||||
[48]: tmp.pnPpRrCI3S#fnref:17
|
||||
[49]: tmp.pnPpRrCI3S#fnref:18
|
||||
[50]: tmp.pnPpRrCI3S#fnref:19
|
||||
[51]: tmp.pnPpRrCI3S#fnref:20
|
||||
[52]: tmp.pnPpRrCI3S#fnref:21
|
||||
[53]: tmp.pnPpRrCI3S#fnref:22
|
||||
@ -1,67 +0,0 @@
|
||||
[#]: collector: (lujun9972)
|
||||
[#]: translator: (Veryzzj)
|
||||
[#]: reviewer: ( )
|
||||
[#]: publisher: ( )
|
||||
[#]: url: ( )
|
||||
[#]: subject: (How I prioritize tasks on my to-do list)
|
||||
[#]: via: (https://opensource.com/article/21/1/prioritize-tasks)
|
||||
[#]: author: (Kevin Sonney https://opensource.com/users/ksonney)
|
||||
|
||||
How I prioritize tasks on my to-do list
|
||||
======
|
||||
Use the Eisenhower Matrix to better organize and prioritize your to-do
|
||||
lists.
|
||||
![Team checklist and to dos][1]
|
||||
|
||||
In prior years, this annual series covered individual apps. This year, we are looking at all-in-one solutions in addition to strategies to help in 2021. Welcome to day 4 of 21 Days of Productivity in 2021. In this article, I'll examine a strategy for prioritizing tasks on a to-do list. To find the open source tool that suits your routine, check out [this list][2].
|
||||
|
||||
It is easy to add things to a task or to-do list. Almost too easy, really. And once on the list, the challenge becomes figuring out what to do first. Do we do the thing at the top of the list? Is the top of the list the most important thing? How do we figure out what the most important thing is?
|
||||
|
||||
![To-do list][3]
|
||||
|
||||
To-do. Today? Tomorrow? Who knows? (Kevin Sonney, [CC BY-SA 4.0][4])
|
||||
|
||||
[Much like email][5], we can prioritize tasks based on a couple of things, and this lets us figure out what needs to be done first and what can wait until later.
|
||||
|
||||
I use a method commonly known as the _Eisenhower Matrix_ since it was taken from a quote by US President Dwight D. Eisenhower. Draw a box split horizontally and vertically. Label the columns "Urgent" and "Not Urgent," and the rows "Important" and "Not Important."
|
||||
|
||||
![Eisenhower matrix][6]
|
||||
|
||||
An Eisenhower Matrix. (Kevin Sonney, [CC BY-SA 4.0][4])
|
||||
|
||||
You can typically put all of the things on a to-do list in one of the boxes. But how do we know what to put where? Urgency and importance are often subjective. So the first step is to decide what is important to you. My family (including my pets), my work, and my hobbies are all important. If something on my to-do list isn't related to those three things, I can immediately put it into the "Not Important" row.
|
||||
|
||||
Urgency is a little more cut and dry. Is it something that needs to be done today or tomorrow? Then it is probably "Urgent." Does it have a deadline that is approaching, but there are days/weeks/months until that time, or perhaps it doesn't have a deadline at all? Certainly "Not Urgent."
|
||||
|
||||
Now we can translate the boxes into priorities. "Urgent/Important" is the highest priority (i.e., Priority 1) and needs to be done first. "Not Urgent/Important" comes next (Priority 2), then "Urgent/Not Important" (Priority 3), and finally "Not Urgent/Not Important" (Priority 4 or no priority at all).
|
||||
|
||||
Notice that "Urgent/Not Important" is third, not second. This is because people spend a lot of time on things that are important because they are urgent, not because they are _actually_ important. When I look at these, I ask myself some questions. Are these tasks that need to be done by me specifically? Are these tasks I can ask other people to do? Are they important and urgent for someone else? Does that change their importance for me? Maybe they need to be re-classified, or perhaps they are things I can ask someone else to do and remove them from my list.
|
||||
|
||||
![After prioritizing][7]
|
||||
|
||||
After prioritizing. (Kevin Sonney, [CC BY-SA 4.0][4])
|
||||
|
||||
There is a single question to ask about the items in the "Not Urgent/Not Important" box, and that is "Do these need to even be on my list at all?" In all honesty, we often clog up our to-do lists with things that are not urgent or important, and we can remove them from our list altogether. I know it is hard to admit that "This is never going to get done," but after I accept that, it is a relief to take that item off my list and not worry about it anymore.
|
||||
|
||||
After all that, it is pretty easy to look at my list and say, "This is what I need to work on now," and get it done, which is what my to-do list is for: Providing guidance and focus to my day.
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://opensource.com/article/21/1/prioritize-tasks
|
||||
|
||||
作者：[Kevin Sonney][a]
|
||||
选题：[lujun9972][b]
|
||||
译者：[译者ID](https://github.com/译者ID)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
||||
[a]: https://opensource.com/users/ksonney
|
||||
[b]: https://github.com/lujun9972
|
||||
[1]: https://opensource.com/sites/default/files/styles/image-full-size/public/lead-images/todo_checklist_team_metrics_report.png?itok=oB5uQbzf (Team checklist and to dos)
|
||||
[2]: https://opensource.com/article/20/5/alternatives-list
|
||||
[3]: https://opensource.com/sites/default/files/pictures/to-do-list.png (To-do list)
|
||||
[4]: https://creativecommons.org/licenses/by-sa/4.0/
|
||||
[5]: https://opensource.com/article/21/1/email-rules
|
||||
[6]: https://opensource.com/sites/default/files/pictures/eisenhower-matrix.png (Eisenhower matrix)
|
||||
[7]: https://opensource.com/sites/default/files/pictures/after-prioritizing.png (After prioritizing)
|
||||
@ -1,180 +0,0 @@
|
||||
[#]: subject: "3 ways to use the Linux inxi command"
|
||||
[#]: via: "https://opensource.com/article/22/9/linux-inxi-command"
|
||||
[#]: author: "Don Watkins https://opensource.com/users/don-watkins"
|
||||
[#]: collector: "lkxed"
|
||||
[#]: translator: "geekpi"
|
||||
[#]: reviewer: " "
|
||||
[#]: publisher: " "
|
||||
[#]: url: " "
|
||||
|
||||
3 ways to use the Linux inxi command
|
||||
======
|
||||
I use inxi on Linux to check my laptop batter, CPU information, and even the weather.
|
||||
|
||||
![Coding on a computer][1]
|
||||
|
||||
I was looking for information about the health of my laptop battery when I stumbled upon `inxi`. It's a command line system information tool that provides a wealth of information about your Linux computer, whether it's a laptop, desktop, or server.
|
||||
|
||||
The `inxi` command is [licensed][2] with the GPLv3, and many Linux distributions include it. According to its Git repository: "inxi strives to support the widest range of operating systems and hardware, from the most simple consumer desktops, to the most advanced professional hardware and servers."
|
||||
|
||||
Documentation is robust, and the project maintains a complete [man page][3] online. Once installed, you can access the man page on your system with the `man inxi` command.
|
||||
|
||||
### Install inxi on Linux
|
||||
|
||||
Generally, you can install `inxi` from your distribution's software repository or app center. For example, on Fedora, CentOS, Mageia, or similar:
|
||||
|
||||
```
|
||||
$ sudo dnf install inxi
|
||||
```
|
||||
|
||||
On Debian, Elementary, Linux Mint, or similar:
|
||||
|
||||
```
|
||||
$ sudo apt install inxi
|
||||
```
|
||||
|
||||
You can find more information about installation options for your Linux distribution [here][4].
|
||||
|
||||
### 3 ways to use inxi on Linux
|
||||
|
||||
Once you install `inxi`, you can explore all its options. There are numerous options to help you learn more about your system. The most fundamental command provides a basic overview of your system:
|
||||
|
||||
```
|
||||
$ inxi -b
|
||||
System:
|
||||
Host: pop-os Kernel: 5.19.0-76051900-generic x86_64 bits: 64
|
||||
Desktop: GNOME 42.3.1 Distro: Pop!_OS 22.04 LTS
|
||||
Machine:
|
||||
Type: Laptop System: HP product: Dev One Notebook PC v: N/A
|
||||
serial: <superuser required>
|
||||
Mobo: HP model: 8A78 v: KBC Version 01.03 serial: <superuser required>
|
||||
UEFI: Insyde v: F.05 date: 06/14/2022
|
||||
Battery:
|
||||
ID-1: BATT charge: 50.6 Wh (96.9%) condition: 52.2/53.2 Wh (98.0%)
|
||||
CPU:
|
||||
Info: 8-core AMD Ryzen 7 PRO 5850U with Radeon Graphics [MT MCP]
|
||||
speed (MHz): avg: 915 min/max: 400/4507
|
||||
Graphics:
|
||||
Device-1: AMD Cezanne driver: amdgpu v: kernel
|
||||
Device-2: Quanta HP HD Camera type: USB driver: uvcvideo
|
||||
Display: x11 server: X.Org v: 1.21.1.3 driver: X: loaded: amdgpu,ati
|
||||
unloaded: fbdev,modesetting,radeon,vesa gpu: amdgpu
|
||||
resolution: 1920x1080~60Hz
|
||||
OpenGL:
|
||||
renderer: AMD RENOIR (LLVM 13.0.1 DRM 3.47 5.19.0-76051900-generic)
|
||||
v: 4.6 Mesa 22.0.5
|
||||
Network:
|
||||
Device-1: Realtek RTL8822CE 802.11ac PCIe Wireless Network Adapter
|
||||
driver: rtw_8822ce
|
||||
Drives:
|
||||
Local Storage: total: 953.87 GiB used: 75.44 GiB (7.9%)
|
||||
Info:
|
||||
Processes: 347 Uptime: 15m Memory: 14.96 GiB used: 2.91 GiB (19.4%)
|
||||
Shell: Bash inxi: 3.3.13
|
||||
```
|
||||
|
||||
### 1. Display battery status
|
||||
|
||||
You can check your battery health using the `-B` option. The result shows the system battery ID, charge condition, and other information:
|
||||
|
||||
```
|
||||
$ inxi -B
|
||||
Battery:
|
||||
ID-1: BATT charge: 44.3 Wh (85.2%) condition: 52.0/53.2 Wh (97.7%)
|
||||
```
|
||||
|
||||
### 2. Display CPU info
|
||||
|
||||
Find out more information about the CPU with the `-C` option:
|
||||
|
||||
```
|
||||
$ inxi -C
|
||||
CPU:
|
||||
Info: 8-core model: AMD Ryzen 7 PRO 5850U with Radeon Graphics bits: 64
|
||||
type: MT MCP cache: L2: 4 MiB
|
||||
Speed (MHz): avg: 400 min/max: 400/4507 cores: 1: 400 2: 400 3: 400
|
||||
4: 400 5: 400 6: 400 7: 400 8: 400 9: 400 10: 400 11: 400 12: 400 13: 400
|
||||
14: 400 15: 400 16: 400
|
||||
```
|
||||
|
||||
The output of `inxi` uses colored text by default. You can change that to improve readability, as needed, by using the "color switch."
|
||||
|
||||
The command option is `-c` followed by any number between 0 and 42 to suit your tastes.
|
||||
|
||||
```
|
||||
$ inxi -c 42
|
||||
```
|
||||
|
||||
Here is an example of a couple of different options using color 5 and then 7:
|
||||
|
||||
![inxi -c 5 command][5]
|
||||
|
||||
The software can show hardware temperature, fan speed, and other information about your system using the sensors in your Linux system. Enter `inxi -s` and read the result below:
|
||||
|
||||
![inxi -s][6]
|
||||
|
||||
### 3. Combine options
|
||||
|
||||
You can combine options for `inxi` to get complex output when supported. For example, `inxi -S` provides system information, and `-v` provides verbose output. Combining the two gives the following:
|
||||
|
||||
```
|
||||
$ inxi -S
|
||||
System:
|
||||
Host: pop-os Kernel: 5.19.0-76051900-generic x86_64 bits: 64
|
||||
Desktop: GNOME 42.3.1 Distro: Pop!_OS 22.04 LTS
|
||||
|
||||
$ inxi -Sv
|
||||
CPU: 8-core AMD Ryzen 7 PRO 5850U with Radeon Graphics (-MT MCP-)
|
||||
speed/min/max: 634/400/4507 MHz Kernel: 5.19.0-76051900-generic x86_64
|
||||
Up: 20m Mem: 3084.2/15318.5 MiB (20.1%) Storage: 953.87 GiB (7.9% used)
|
||||
Procs: 346 Shell: Bash inxi: 3.3.13
|
||||
```
|
||||
|
||||
### Bonus: Check the weather
|
||||
|
||||
Your computer isn't all `inxi` can gather information about. With the `-w` option, you can also get weather information for your locale:
|
||||
|
||||
```
|
||||
$ inxi -w
|
||||
Weather:
|
||||
Report: temperature: 14 C (57 F) conditions: Clear sky
|
||||
Locale: Wellington, G2, NZL
|
||||
current time: Tue 30 Aug 2022 16:28:14 (Pacific/Auckland)
|
||||
Source: WeatherBit.io
|
||||
```
|
||||
|
||||
You can get weather information for other areas of the world by specifying the city and country you want along with `-W` :
|
||||
|
||||
```
|
||||
$ inxi -W rome,italy
|
||||
Weather:
|
||||
Report: temperature: 20 C (68 F) conditions: Clear sky
|
||||
Locale: Rome, Italy current time: Tue 30 Aug 2022 06:29:52
|
||||
Source: WeatherBit.io
|
||||
```
|
||||
|
||||
### Wrap up
|
||||
|
||||
There are many great tools to gather information about your computer. I use different ones depending on the machine, the desktop, or my mood. What are your favorite system information tools?
|
||||
|
||||
Image by: (Don Watkins, CC BY-SA 4.0)
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://opensource.com/article/22/9/linux-inxi-command
|
||||
|
||||
作者：[Don Watkins][a]
|
||||
选题：[lkxed][b]
|
||||
译者：[译者ID](https://github.com/译者ID)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
||||
[a]: https://opensource.com/users/don-watkins
|
||||
[b]: https://github.com/lkxed
|
||||
[1]: https://opensource.com/sites/default/files/lead-images/code_computer_laptop_hack_work.png
|
||||
[2]: https://github.com/smxi/inxi/blob/master/LICENSE.txt
|
||||
[3]: https://smxi.org/docs/inxi-man.htm
|
||||
[4]: https://smxi.org/docs/inxi-installation.htm#inxi-repo-install
|
||||
[5]: https://opensource.com/sites/default/files/2022-09/inxi-c5.png
|
||||
[6]: https://opensource.com/sites/default/files/2022-09/inxi-s.png
|
||||
@ -2,7 +2,7 @@
|
||||
[#]: via: "https://www.debugpoint.com/4-simple-steps-clean-ubuntu-system-linux/"
|
||||
[#]: author: "Arindam https://www.debugpoint.com/author/admin1/"
|
||||
[#]: collector: "lkxed"
|
||||
[#]: translator: " "
|
||||
[#]: translator: "Donkey-Hao"
|
||||
[#]: reviewer: " "
|
||||
[#]: publisher: " "
|
||||
[#]: url: " "
|
||||
@ -157,7 +157,7 @@ via: https://www.debugpoint.com/4-simple-steps-clean-ubuntu-system-linux/
|
||||
|
||||
作者：[Arindam][a]
|
||||
选题：[lkxed][b]
|
||||
译者：[译者ID](https://github.com/译者ID)
|
||||
译者：[Donkey-Hao](https://github.com/Donkey-Hao)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
||||
@ -1,212 +0,0 @@
|
||||
[#]: subject: "GNOME 43: Top New Features and Release Wiki"
|
||||
[#]: via: "https://www.debugpoint.com/gnome-43/"
|
||||
[#]: author: "Arindam https://www.debugpoint.com/author/admin1/"
|
||||
[#]: collector: "lkxed"
|
||||
[#]: translator: " "
|
||||
[#]: reviewer: " "
|
||||
[#]: publisher: " "
|
||||
[#]: url: " "
|
||||
|
||||
GNOME 43: Top New Features and Release Wiki
|
||||
======
|
||||
An extensive feature analysis of the GNOME 43 desktop environment bringing impactful changes to your day-to-day needs and workflow.
|
||||
|
||||
![GNOME 43 Running via GNOME OS][1]
|
||||
|
||||
This article summarises all necessary information about GNOME 43, including features, release schedule and more. The GNOME 43 release is probably the most impactful release since the GNOME 40 in terms of the features and their impact on your workflow.
|
||||
|
||||
The feature includes updated and faster Shell performance, wrapping up GTK4 and libadwaita conversion, renovated Files and fantastic Web changes.
|
||||
|
||||
All these necessary changes were long overdue and will change your traditional workflow in the GNOME desktop to make you more productive.
|
||||
|
||||
### Schedule
|
||||
|
||||
GNOME 43 was [officially released][2] on September 21, 2022.
|
||||
|
||||
* GNOME 43 Beta: August 31, 2022 (Complete)
|
||||
* GNOME 43 RC: September 4, 2022 (Complete)
|
||||
* GNOME 43 final release: September 21, 2022
|
||||
|
||||
### GNOME 43: The Features
|
||||
|
||||
#### 1. Core Shell Changes
|
||||
|
||||
* Finally, the high-resolution scroll wheel support lands in GNOME thanks to recent work in Wayland. So, if you have a high-resolution display, scrolling with an advanced mouse (such as Logitech MX Master 3) should be a treat for you.
|
||||
* In addition to the above, the direct scanout support in GNOME 43 will help with multi-monitor setup situations.
|
||||
* The server-side decorations get essential colour support.
|
||||
* Shell also implemented a feature where the notifications get away when the focus changes, and it doesn’t wait for the timeout.
|
||||
* Like every release, you experience better animation performance across the desktop, improved grid and overview navigation and critical updates, which gives you a seamless experience.
|
||||
|
||||
So, that are the key summaries of the core changes. Now, let’s talk about the Quick settings.
|
||||
|
||||
#### 2. New Quick Settings Menu
|
||||
|
||||
The quick settings in the system tray are entirely changed. The quick settings items and menus now feature pill-shaped toggle buttons with vibrant colours to show what is happening in your system. The menu is also dynamic and makes way for cascading menu items. In addition, you can choose the audio devices in the quick settings.
|
||||
|
||||
Here’s a quick demo, and for additional screenshots and write-up – read our exclusive coverage: [GNOME 43 Quick settings][3].
|
||||
|
||||
![Quick Settings Demo in GNOME 43][4]
|
||||
|
||||
#### 3. Files
|
||||
|
||||
GNOME Files gets the most features in GNOME 43 release. The list of improvements in this application is enormous. The file manager is the most used app in any desktop environment. Hence the changes in Files are the most impactful across the user base.
|
||||
|
||||
For the first time, Files with GTK4 arrive (it was not ready during GNOME 42 release), and it will change your workflow for good.
|
||||
|
||||
I will try to explain most of them in a brief list. Otherwise, this will be a lengthy post. I will push out another separate article on the File features.
|
||||
|
||||
##### Adaptive sidebar
|
||||
|
||||
So the sidebar of Files which gives you access to navigations, favourites, network drives, etc. – is not responsive. And it [autohides][5] itself when Files window size reaches a point. A familiar and handy feature if you work with many open windows and have smaller displays.
|
||||
|
||||
Another exciting feature is that when the sidebar is wholly hidden, an icon appears at the left top for you to make it visible.
|
||||
|
||||
![Files 43 with autohide sidebar][6]
|
||||
|
||||
##### Emblems
|
||||
|
||||
We had the emblems in GNOME long back, and they went away. So, Emblems make a comeback with GNOME 43 with small icons beside the files and directories. These icons imply the type, such as symbolic link, read-only, etc. Moreover, the icons change their colour based on your theme, and multiple emblems are also available for a single file.
|
||||
|
||||
![Emblems in GNOME 43][7]
|
||||
|
||||
##### Rubberband Selection
|
||||
|
||||
Next up is the much-awaited rubberband selection feature, which [finally arrived][8]. Now you can select the files and folders by drag-selection mechanism. One of the most requested features from the users.
|
||||
|
||||
![Rubberband Selection Feature][9]
|
||||
|
||||
##### GtkColumnView replacing GtkTreeView
|
||||
|
||||
When you mouse over the items in the column view, you see a focused row which is another critical feature of Files in GNOME 43. But the [tree view could not make it][10] and probably planned for the next iteration.
|
||||
|
||||
![GtkColumnView enables row focus][11]
|
||||
|
||||
##### Redesigned properties window with interactive permission and executable detection
|
||||
|
||||
The properties window is [wholly changed][12], thanks to the adaptation of GTK4. The window is now much cleaner and well-designed, showing essential items only when required.
|
||||
|
||||
Furthermore, the properties dialog can determine the file type and provide suitable options. For example, if you view the properties of a shell script or text file, you will get an option to make it executable. In contrast, the properties of an image file do not give you an executable option.
|
||||
|
||||
![Intelligent properties window][13]
|
||||
|
||||
**Tabbed View improvements**
|
||||
|
||||
The tabbed view of Files gets some [additional updates][14]. The most noteworthy ones are the proper focus when dragging a file to tag, the creation of tabs after the current focussed tab and so on.
|
||||
|
||||
**Redesigned Right-click menu**
|
||||
|
||||
The primary right-click context menu on files or folders is restricted. Firstly, the OPEN option is clubbed under a submenu. Secondly, the copy/paste/cut options are consolidated in a group. And finally, the Trash, Rename and Compress options are grouped.
|
||||
|
||||
In addition, the Open in terminal option is available for all files and folders. However, create a new file option is still missing (which I expected in this release).
|
||||
|
||||
![Various Context Menu][15]
|
||||
|
||||
##### Other changes in Files
|
||||
|
||||
Other prominent changes in Files are the Trash icon, and other locations (network drive, disk) gets the properties option in right-click context menu.
|
||||
|
||||
Finally, the Files preference window was revamped to show you more essential items. The redesign makes it easy for the average user to find the proper Files settings.
|
||||
|
||||
#### 4. Web
|
||||
|
||||
Let’s spare some moments to talk about our beloved Epiphany, a.k.a. GNOME Web, the WebKit-based native web browser for the GNOME desktop.
|
||||
|
||||
The updates were long overdue and finally started landing from this release onwards.
|
||||
|
||||
First and foremost, GNOME Web now supports WebExtension API. It lets you download and install the Firefox and Google Chrome extensions inside the Web. Here’s how you can do it.
|
||||
|
||||
* Download any extension file (xpi or crx file) from Firefox Add-on or Google Chrome extension page.
|
||||
* Click on the hamburger menu and select Extensions.
|
||||
* Finally, click add to install them.
|
||||
|
||||
WebExtension support is a crucial step for making the Web usable soon.
|
||||
|
||||
Secondly, the Firefox Sync option is available, which lets you log in to the Web via a Firefox account to sync bookmarks and other browser items.
|
||||
|
||||
![Login to the Web using a Firefox account][16]
|
||||
|
||||
Other noteworthy changes in the Web include support for “view source”, GTK4 porting work and an updated PDF library (PDF.js 2.13.216).
|
||||
|
||||
One of the critical components which are still missing in Web is the [WebRTC support via GStreamer][17]. Once that feature arrives, it will be a decent browser for daily usage.
|
||||
|
||||
Hopefully, one day, we all have a decent alternative browser which is non-Firefox or non-Chromium.
|
||||
|
||||
#### 5. Settings
|
||||
|
||||
In the settings window, mostly improvements and visual fine-tuning arrive in this release. The important change includes the “Dog Bark” sound in Alert is gone now after a long and [interesting conversation][18].
|
||||
|
||||
In addition, a new device security panel is introduced, and the TImezone map in the Date & Time panel is revamped.
|
||||
|
||||
The settings sidebar is also responsive and gives you autohide features like the Files shown above.
|
||||
|
||||
#### 6. Software
|
||||
|
||||
Two crucial changes are coming to GNOME Software. These changes enable you to view more information on a single page for any application.
|
||||
|
||||
Firstly, a new section, “Other apps by Author”, gives you a list of apps by the author of the current app. This helps in discovery and tells you how popular the creator is.
|
||||
|
||||
Secondly, GNOME 43 Software now provides you with a detailed list of permission required by the Flatpak apps in a separate window. Hence, you can verify the app before you install them.
|
||||
|
||||
Another crucial visual change is a new “Available for Fedora/any distro” section on the application main overview page, which requires configuration.
|
||||
|
||||
![Other APPS by developer section in Software][19]
|
||||
|
||||
#### 7. Climate Change Wallpaper
|
||||
|
||||
I am not sure whether this feature landed. Because I could not find it, but I heard about it. So, I though I should mention it here.
|
||||
|
||||
The feature is that GNOME 43 brings a background wallpaper showing how the global temperature has risen over the decades from [ocean stripes][20]. The wallpaper contains vertical colour-coded bars denoting low and high temperatures. I think it’s a nice touch and an effort to raise awareness. Here’s the [commit][21] in GitLab.
|
||||
|
||||
In addition, a couple of new [“days and nights”][22] fresh wallpapers are available.
|
||||
|
||||
That’s all about the essential changes I could find and summarise here. Besides those, a vast list of bug fixes, performance improvements and code clean up lands in GNOME 43.
|
||||
|
||||
Fedora 37 will feature GNOME 43 when released, and some parts of it should be in Ubuntu 22.10, due in October.
|
||||
|
||||
### Wrapping Up
|
||||
|
||||
GNOME 43 is an iconic release because it changes several basic designs and impacts millions of users’ workflow. The quick settings transformation is fantastic and long overdue. In addition, the necessary changes in Files, Web and Settings will improve your productivity.
|
||||
|
||||
Furthermore, the new features arrive while keeping the design guideline and aesthetics in mind. A good user interface requires a well-thought-out process, and the devs did a perfect job in this release.
|
||||
|
||||
So, that’s pretty much it. That’s GNOME 43 for you. Let me know if you plan to get this update and want to hop from KDE to GNOME!
|
||||
|
||||
🗨️ Do let me know your favourite feature in the comment section below.
|
||||
|
||||
Cheers.
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://www.debugpoint.com/gnome-43/
|
||||
|
||||
作者：[Arindam][a]
|
||||
选题：[lkxed][b]
|
||||
译者：[译者ID](https://github.com/译者ID)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
||||
[a]: https://www.debugpoint.com/author/admin1/
|
||||
[b]: https://github.com/lkxed
|
||||
[1]: https://www.debugpoint.com/wp-content/uploads/2022/08/GNOME-43-Running-via-GNOME-OS.jpg
|
||||
[2]: https://debugpointnews.com/gnome-43-release/
|
||||
[3]: https://www.debugpoint.com/gnome-43-quick-settings/
|
||||
[4]: https://www.debugpoint.com/?attachment_id=10682
|
||||
[5]: https://gitlab.gnome.org/GNOME/nautilus/-/merge_requests/877
|
||||
[6]: https://www.debugpoint.com/?attachment_id=10684
|
||||
[7]: https://www.debugpoint.com/?attachment_id=10685
|
||||
[8]: https://gitlab.gnome.org/GNOME/nautilus/-/merge_requests/817
|
||||
[9]: https://www.debugpoint.com/wp-content/uploads/2022/08/Rubberband-Selection-Feature.gif
|
||||
[10]: https://gitlab.gnome.org/GNOME/nautilus/-/merge_requests/817
|
||||
[11]: https://www.debugpoint.com/wp-content/uploads/2022/08/GtkColumnView-enables-row-focus.gif
|
||||
[12]: https://gitlab.gnome.org/GNOME/nautilus/-/merge_requests/745
|
||||
[13]: https://www.debugpoint.com/wp-content/uploads/2022/08/Intelligent-properties-window.jpg
|
||||
[14]: https://gitlab.gnome.org/GNOME/nautilus/-/merge_requests/595
|
||||
[15]: https://www.debugpoint.com/?attachment_id=10689
|
||||
[16]: https://www.debugpoint.com/wp-content/uploads/2022/08/Login-to-Web-using-Firefox-account.jpg
|
||||
[17]: https://twitter.com/_philn_/status/1490391956970684422
|
||||
[18]: https://discourse.gnome.org/t/dog-barking-error-message-sound/9529/2
|
||||
[19]: https://www.debugpoint.com/wp-content/uploads/2022/08/Other-APPS-by-developer-section-in-Software.jpg
|
||||
[20]: https://showyourstripes.info/s/globe/
|
||||
[21]: https://gitlab.gnome.org/GNOME/gnome-backgrounds/-/commit/a142d5c88702112fae3b64a6d90d10488150d8c1
|
||||
[22]: https://www.debugpoint.com/custom-light-dark-wallpaper-gnome/
|
||||
@ -2,7 +2,7 @@
|
||||
[#]: via: "https://itsfoss.com/figma-alternatives/"
|
||||
[#]: author: "Ankush Das https://itsfoss.com/author/ankush/"
|
||||
[#]: collector: "lkxed"
|
||||
[#]: translator: " "
|
||||
[#]: translator: "geekpi"
|
||||
[#]: reviewer: " "
|
||||
[#]: publisher: " "
|
||||
[#]: url: " "
|
||||
|
||||
285
sources/tech/20220924 Drop your database for PostgreSQL.md
Normal file
285
sources/tech/20220924 Drop your database for PostgreSQL.md
Normal file
@ -0,0 +1,285 @@
|
||||
[#]: subject: "Drop your database for PostgreSQL"
|
||||
[#]: via: "https://opensource.com/article/22/9/drop-your-database-for-postgresql"
|
||||
[#]: author: "Seth Kenlon https://opensource.com/users/seth"
|
||||
[#]: collector: "lkxed"
|
||||
[#]: translator: " "
|
||||
[#]: reviewer: " "
|
||||
[#]: publisher: " "
|
||||
[#]: url: " "
|
||||
|
||||
Drop your database for PostgreSQL
|
||||
======
|
||||
Postgres is one of the most flexible databases available, and it's open source.
|
||||
|
||||
Databases are tools to store information in an organized but flexible way. A spreadsheet is essentially a database, but the constraints of a graphical application render most spreadsheet applications useless to programmers. With [Edge][3] and IoT devices becoming significant target platforms, developers need powerful but lightweight solutions for storing, processing, and querying large amounts of data. One of my favourite combinations is the PostgreSQL database and [Lua bindings][4], but the possibilities are endless. Whatever language you use, Postgres is a great choice for a database, but you need to know some basics before adopting it.
|
||||
|
||||
### Install Postgres
|
||||
|
||||
To install PostgreSQL on Linux, use your software repository. On Fedora, CentOS, Mageia, and similar:
|
||||
|
||||
```
|
||||
$ sudo dnf install postgresql postgresql-server
|
||||
```
|
||||
|
||||
On Debian, Linux Mint, Elementary, and similar:
|
||||
|
||||
```
|
||||
$ sudo apt install postgresql postgresql-contrib
|
||||
```
|
||||
|
||||
On macOS and Windows, download an installer from [postgresql.org][5].
|
||||
|
||||
### Setting up Postgres
|
||||
|
||||
Most distributions install the Postgres database without *starting* it, but provide you with a script or [systemd service][6] to help it start reliably. However, before you start PostgreSQL, you must create a database cluster.
|
||||
|
||||
#### Fedora
|
||||
|
||||
On Fedora, CentOS, or similar, there's a Postgres setup script provided in the Postgres package. Run this script for easy configuration:
|
||||
|
||||
```
|
||||
$ sudo /usr/bin/postgresql-setup --initdb
|
||||
[sudo] password:
|
||||
* Initializing database in '/var/lib/pgsql/data'
|
||||
* Initialized, logs are in /var/lib/pgsql/initdb_postgresql.log
|
||||
```
|
||||
|
||||
#### Debian
|
||||
|
||||
On Debian-based distributions, setup is performed automatically by `apt` during installation.
|
||||
|
||||
#### Everything else
|
||||
|
||||
Finally, if you're running something else, then you can just use the toolchain provided by Postgres itself. The `initdb` command creates a database cluster, but you must run it as the `postgres` user, an identity you may temporarily assume using `sudo` :
|
||||
|
||||
```
|
||||
$ sudo -u postgres \
|
||||
"initdb -D /var/lib/pgsql/data \
|
||||
--locale en_US.UTF-8 --auth md5 --pwprompt"
|
||||
```
|
||||
|
||||
### Start Postgres
|
||||
|
||||
Now that a cluster exists, start the Postgres server using either the command provided to you in the output of `initdb` or with systemd:
|
||||
|
||||
```
|
||||
$ sudo systemctl start postgresql
|
||||
```
|
||||
|
||||
### Creating a database user
|
||||
|
||||
To create a Postgres user, use the `createuser` command. The `postgres` user is the superuser of the Postgres install,
|
||||
|
||||
```
|
||||
$ sudo -u postgres createuser --interactive --password bogus
|
||||
Shall the new role be a superuser? (y/n) n
|
||||
Shall the new role be allowed to create databases? (y/n) y
|
||||
Shall the new role be allowed to create more new roles? (y/n) n
|
||||
Password:
|
||||
```
|
||||
|
||||
### Create a database
|
||||
|
||||
To create a new database, use the `createdb` command. In this example, I create the database `exampledb` and assign ownership of it to the user `bogus` :
|
||||
|
||||
```
|
||||
$ createdb exampledb --owner bogus
|
||||
```
|
||||
|
||||
### Interacting with PostgreSQL
|
||||
|
||||
You can interact with a PostgreSQL database using the `psql` command. This command provides an interactive shell so you can view and update your databases. To connect to a database, specify the user and database you want to use:
|
||||
|
||||
```
|
||||
$ psql --user bogus exampledb
|
||||
psql (XX.Y)
|
||||
Type "help" for help.
|
||||
|
||||
exampledb=>
|
||||
```
|
||||
|
||||
### Create a table
|
||||
|
||||
Databases contain tables, which can be visualized as a spreadsheet. There's a series of rows (called *records* in a database) and columns. The intersection of a row and a column is called a *field*.
|
||||
|
||||
The Structured Query Language (SQL) is named after what it provides: A method to inquire about the contents of a database in a predictable and consistent syntax to receive useful results.
|
||||
|
||||
Currently, your database is empty, devoid of any tables. You can create a table with the `CREATE` query. It's useful to combine this with the `IF NOT EXISTS` statement, which prevents PostgreSQL from clobbering an existing table.
|
||||
|
||||
Before you createa table, think about what kind of data (the "data type" in SQL terminology) you anticipate the table to contain. In this example, I create a table with one column for a unique identifier and one column for some arbitrary text up to nine characters.
|
||||
|
||||
```
|
||||
exampledb=> CREATE TABLE IF NOT EXISTS my_sample_table(
|
||||
exampledb(> id SERIAL,
|
||||
exampledb(> wordlist VARCHAR(9) NOT NULL
|
||||
);
|
||||
```
|
||||
|
||||
The `SERIAL` keyword isn't actually a data type. It's [special notation in PostgreSQL][7] that creates an auto-incrementing integer field. The `VARCHAR` keyword is a data type indicating a variable number of characters within a limit. In this code, I've specified a maximum of 9 characters. There are lots of data types in PostgreSQL, so refer to the project documentation for a list of options.
|
||||
|
||||
### Insert data
|
||||
|
||||
You can populate your new table with some sample data by using the `INSERT` SQL keyword:
|
||||
|
||||
```
|
||||
exampledb=> INSERT INTO my_sample_table (wordlist) VALUES ('Alice');
|
||||
INSERT 0 1
|
||||
```
|
||||
|
||||
Your data entry fails, should you attempt to put more than 9 characters into the `wordlist` field:
|
||||
|
||||
```
|
||||
exampledb=> INSERT INTO my_sample_table (WORDLIST) VALUES ('Alexandria');
|
||||
ERROR: VALUE too long FOR TYPE CHARACTER VARYING(9)
|
||||
```
|
||||
|
||||
### Alter a table or column
|
||||
|
||||
When you need to change a field definition, you use the `ALTER` SQL keyword. For instance, should you decide that a nine character limit for `wordlist`, you can increase its allowance by setting its data type:
|
||||
|
||||
```
|
||||
exampledb=> ALTER TABLE my_sample_table
|
||||
ALTER COLUMN wordlist SET DATA TYPE VARCHAR(10);
|
||||
ALTER TABLE
|
||||
exampledb=> INSERT INTO my_sample_table (WORDLIST) VALUES ('Alexandria');
|
||||
INSERT 0 1
|
||||
```
|
||||
|
||||
### View data in a table
|
||||
|
||||
SQL is a query language, so you view the contents of a database through queries. Queries can be simple, or it can involve joining complex relationships between several different tables. To see everything in a table, use the `SELECT` keyword on `*` (an asterisk is a wildcard):
|
||||
|
||||
```
|
||||
exampledb=> SELECT * FROM my_sample_table;
|
||||
id | wordlist
|
||||
\----+------------
|
||||
1 | Alice
|
||||
2 | Bob
|
||||
3 | Alexandria
|
||||
(3 ROWS)
|
||||
```
|
||||
|
||||
### More data
|
||||
|
||||
PostgreSQL can handle a lot of data, but as with any database the key to success is how you design your database for storage and what you do with the data once you've got it stored. A relatively large public data set can be found on [OECD.org][8], and using this you can try some advanced database techniques.
|
||||
|
||||
First, download the data as comma-separated values (CSV) and save the file as `land-cover.csv` in your `Downloads` folder.
|
||||
|
||||
Browse the data in a text editor or spreadsheet application to get an idea of what columns there are, and what kind of data each column contains. Look at the data carefully and keep an eye out for exceptions to an apparent rule. For instance, the `COU` column, containing a country code such as `AUS` for Australia and `GRC` for Greece, tends to be 3 characters until the oddity `BRIICS`.
|
||||
|
||||
Once you understand the data you're working with, you can prepare a Postgres database:
|
||||
|
||||
```
|
||||
$ createdb landcoverdb --owner bogus
|
||||
$ psql --user bogus landcoverdb
|
||||
landcoverdb=> create table land_cover(
|
||||
country_code varchar(6),
|
||||
country_name varchar(76),
|
||||
small_subnational_region_code varchar(5),
|
||||
small_subnational_region_name varchar(14),
|
||||
large_subnational_region_code varchar(17),
|
||||
large_subnational_region_name varchar(44),
|
||||
measure_code varchar(13),
|
||||
measure_name varchar(29),
|
||||
land_cover_class_code varchar(17),
|
||||
land_cover_class_name varchar(19),
|
||||
year_code integer,
|
||||
year_value integer,
|
||||
unit_code varchar(3),
|
||||
unit_name varchar(17),
|
||||
power_code integer,
|
||||
power_name varchar(9),
|
||||
reference_period_code varchar(1),
|
||||
reference_period_name varchar(1),
|
||||
value float(8),
|
||||
flag_codes varchar(1),
|
||||
flag_names varchar(1));
|
||||
```
|
||||
|
||||
### Importing data
|
||||
|
||||
Postgres can import CSV data directly using the special metacommand `\copy` :
|
||||
|
||||
```
|
||||
landcoverdb=> \copy land_cover from '~/land-cover.csv' with csv header delimiter ','
|
||||
COPY 22113
|
||||
```
|
||||
|
||||
That's 22,113 records imported. Seems like a good start!
|
||||
|
||||
### Querying data
|
||||
|
||||
A broad `SELECT` statement to see all columns of all 22,113 records is possible, and Postgres very nicely pipes the output to a screen pager so you can scroll through the output at a leisurely pace. However, using advanced SQL you can get some useful views of what's otherwise some pretty raw data.
|
||||
|
||||
```
|
||||
landcoverdb=> SELECT
|
||||
lcm.country_name,
|
||||
lcm.year_value,
|
||||
SUM(lcm.value) sum_value
|
||||
FROM land_cover lcm
|
||||
JOIN (
|
||||
SELECT
|
||||
country_name,
|
||||
large_subnational_region_name,
|
||||
small_subnational_region_name,
|
||||
MAX(year_value) max_year_value
|
||||
FROM land_cover
|
||||
GROUP BY country_name,
|
||||
large_subnational_region_name,
|
||||
small_subnational_region_name
|
||||
) AS lcmyv
|
||||
ON
|
||||
lcm.country_name = lcmyv.country_name AND
|
||||
lcm.large_subnational_region_name = lcmyv.large_subnational_region_name AND
|
||||
lcm.small_subnational_region_name = lcmyv.small_subnational_region_name AND
|
||||
lcm.year_value = lcmyv.max_year_value
|
||||
GROUP BY lcm.country_name,
|
||||
lcm.large_subnational_region_name,
|
||||
lcm.small_subnational_region_name,
|
||||
lcm.year_value
|
||||
ORDER BY country_name,
|
||||
year_value;
|
||||
```
|
||||
|
||||
Here's some sample output:
|
||||
|
||||
```
|
||||
\---------------+------------+------------
|
||||
Afghanistan | 2019 | 743.48425
|
||||
Albania | 2019 | 128.82532
|
||||
Algeria | 2019 | 2417.3281
|
||||
American Samoa | 2019 | 100.2007
|
||||
Andorra | 2019 | 100.45613
|
||||
Angola | 2019 | 1354.2192
|
||||
Anguilla | 2019 | 100.078514
|
||||
Antarctica | 2019 | 12561.907
|
||||
[...]
|
||||
```
|
||||
|
||||
SQL is a rich langauge, and so it's beyond the scope of this article. Read through the SQL code and see if you can modify it to provide a different set of data.
|
||||
|
||||
### Open database
|
||||
|
||||
PostgreSQL is one of the great open source databases. With it, you can design repositories for structured data, and then use SQL to view it in different ways so you can gain fresh perspectives on that data. Postgres integrates with many languages, including Python, Lua, Groovy, Java, and more, so regardless of your toolset, you can probably make use of this excellent database.
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://opensource.com/article/22/9/drop-your-database-for-postgresql
|
||||
|
||||
作者：[Seth Kenlon][a]
|
||||
选题：[lkxed][b]
|
||||
译者：[译者ID](https://github.com/译者ID)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
||||
[a]: https://opensource.com/users/seth
|
||||
[b]: https://github.com/lkxed
|
||||
[1]: https://opensource.com/sites/default/files/lead-images/lenovo-thinkpad-laptop-concentration-focus-windows-office.png
|
||||
[2]: https://creativecommons.org/licenses/by/3.0/us/
|
||||
[3]: https://www.redhat.com/en/topics/edge-computing/what-is-edge-computing?intcmp=7013a000002qLH8AAM
|
||||
[4]: https://github.com/arcapos/luapgsql
|
||||
[5]: https://www.postgresql.org/download/
|
||||
[6]: https://opensource.com/article/21/4/sysadmins-love-systemd
|
||||
[7]: https://www.postgresql.org/docs/current/datatype-numeric.html#DATATYPE-SERIAL
|
||||
[8]: https://stats.oecd.org/Index.aspx?DataSetCode=LAND_COVER
|
||||
@ -0,0 +1,105 @@
|
||||
[#]: subject: "Wolfi is a Linux Un(distro) Built for Software Supply Chain Security"
|
||||
[#]: via: "https://news.itsfoss.com/wolfi-linux-undistro/"
|
||||
[#]: author: "Ankush Das https://news.itsfoss.com/author/ankush/"
|
||||
[#]: collector: "lkxed"
|
||||
[#]: translator: " "
|
||||
[#]: reviewer: " "
|
||||
[#]: publisher: " "
|
||||
[#]: url: " "
|
||||
|
||||
Wolfi is a Linux Un(distro) Built for Software Supply Chain Security
|
||||
======
|
||||
Wolfi is a Linux undistro that focuses on resolving security issues with the software supply chain. Explore more here.
|
||||
|
||||
![Wolfi is a Linux Un(distro) Built for Software Supply Chain Security][1]
|
||||
|
||||
The software supply chain includes everything that goes into developing, building, storing, and running it and its dependencies.
|
||||
|
||||
As per the [State of the Software Supply Chain 2021 report][2], between 2020 and 2021 alone, attacks on the software supply chain increased by a shocking **650%**.
|
||||
|
||||
![][3]
|
||||
|
||||
That's a staggering percentage. 🤯
|
||||
|
||||
So, everyone in the industry, ranging from code platforms like [GitHub][4] to tech giants like Google, has been putting their best efforts into coming up with various initiatives to enhance the security of the software supply chain.
|
||||
|
||||
One of the examples include:
|
||||
|
||||
[Google Sponsors $1 Million to Fund Secure Open Source Program by The Linux Foundation][5]
|
||||
|
||||
📢 To join the efforts, [Chainguard][7], a security firm specializing in open-source software and cloud-native development, has introduced a **Linux distro designed to secure the software supply chain**.
|
||||
|
||||
💡 They call it an "**Undistro**" because it is not a full-fledged Linux distribution to run on bare metal.
|
||||
|
||||
Instead, it is a **container-focused Linux distribution**. So, let me tell you more about it.
|
||||
|
||||
### Wolfi: A Container-specific Linux Distribution
|
||||
|
||||
The world’s smallest Octopus is named Wolfi, which inspired them to use the same to represent minimalism to flexibility for this Linux distribution.
|
||||
|
||||
Wolfi aims to address issues with containers, which are mainly used to build and ship software.
|
||||
|
||||
Furthermore, Chainguard mentions that there are several issues with running containers; some include:
|
||||
|
||||
* Running vulnerable container images.
|
||||
* Distributions used in container lag behind upstream versions.
|
||||
* Container images include more software than needed, increasing the attack surface.
|
||||
* Not designed to meet compliance requirements or standards like [SLSA][8].
|
||||
|
||||
So, Wolfi is a distro that aims to solve these problems by being a solution **designed for container/cloud-native environments**while **minimizing dependencies** as much as possible.
|
||||
|
||||
It provides a secure foundation that reduces the effort/time to review and mitigate security vulnerabilities while increasing productivity.
|
||||
|
||||
Chainguard explains this as follows:
|
||||
|
||||
> Building a new, container-specific distribution offers the chance to vastly simplify things by dropping support for traditional distribution features that are now irrelevant (like packaging Linux itself!), and other things like SBOMs become simpler when we can build them in from the start. We can also embrace the immutable nature of containers and avoid package updates altogether, instead preferring to rebuild from scratch with new versions.
|
||||
|
||||
### Key Features of Wolfi
|
||||
|
||||
To achieve its purpose, Wolfi has a few key highlights for you to encourage using it:
|
||||
|
||||
* Provides a high-quality, build-time SBOM as standard for all packages.
|
||||
* Packages are designed to be granular and independent, to support minimal images.
|
||||
* Uses the proven and reliable APK package format.
|
||||
* Fully declarative and reproducible build system.
|
||||
* Designed to support glibc and musl.
|
||||
|
||||
If you are not familiar with the securing software supply chain, this might go over your head.
|
||||
|
||||
![Securing your software supply chain][11]
|
||||
|
||||
So, I suggest looking at [Wikipedia][12] to understand the terms. The video above should also help you learn more.
|
||||
|
||||
### Try Wolfi
|
||||
|
||||
To try Chainguard images using the Wolfi undistro, you can head to its [GitHub page][13] to find all the technical instructions.
|
||||
|
||||
[Try Wolfi][14]
|
||||
|
||||
💬 *What do you think about Wolfi? Do you think it will solve the problem of securing the software supply chain? Let us know your thoughts in the comments.*
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://news.itsfoss.com/wolfi-linux-undistro/
|
||||
|
||||
作者：[Ankush Das][a]
|
||||
选题：[lkxed][b]
|
||||
译者：[译者ID](https://github.com/译者ID)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
||||
[a]: https://news.itsfoss.com/author/ankush/
|
||||
[b]: https://github.com/lkxed
|
||||
[1]: https://news.itsfoss.com/content/images/size/w1200/2022/09/wolfi-distro-software-supply-chain-security.png
|
||||
[2]: https://www.sonatype.com/resources/state-of-the-software-supply-chain-2021
|
||||
[3]: https://news.itsfoss.com/content/images/2022/09/software-chain-attacks.jpg
|
||||
[4]: https://news.itsfoss.com/gitlab-open-source-tool-malicious-code/
|
||||
[5]: https://news.itsfoss.com/google-sos-sponsor/
|
||||
[7]: https://www.chainguard.dev/
|
||||
[8]: https://slsa.dev/
|
||||
[11]: https://youtu.be/Dg-hD4HHKT8
|
||||
[12]: https://en.wikipedia.org/wiki/Software_supply_chain
|
||||
[13]: https://github.com/chainguard-images/
|
||||
[14]: https://github.com/chainguard-images/
|
||||
[15]: https://www.humblebundle.com/books/linux-no-starch-press-books?partner=itsfoss
|
||||
@ -1,35 +0,0 @@
|
||||
[#]: subject: "Lawmakers Proposes A New Bill To Protect Open Source Software"
|
||||
[#]: via: "https://www.opensourceforu.com/2022/09/lawmakers-proposes-a-new-bill-to-protect-open-source-software/"
|
||||
[#]: author: "Laveesh Kocher https://www.opensourceforu.com/author/laveesh-kocher/"
|
||||
[#]: collector: "lkxed"
|
||||
[#]: translator: "littlebirdnest"
|
||||
[#]: reviewer: " "
|
||||
[#]: publisher: " "
|
||||
[#]: url: " "
|
||||
|
||||
立法者提出一项保护开源软件的新法案
|
||||
======
|
||||
*《保护开源软件法案》将责成管理和预算办公室提供有关如何安全使用开源软件的说明。*
|
||||
|
||||
立法者周四提出了一项要求网络安全和基础设施安全局创建风险框架以提高开源软件安全性的措施。为了降低依赖开源代码的系统的风险，机构将利用该框架，CISA 将决定关键基础设施所有者和运营商是否也可以自愿使用它。
|
||||
|
||||
大多数系统依赖于免费提供并由社区维护的开源软件来构建网站和应用程序；最大的用户之一是联邦政府。该立法由国土安全委员会主席兼高级成员、俄亥俄州共和党参议员 Sens. Rob Portman, R-Ohio 和 Gary Peters D-Mich。发现一系列传播广泛的Log4j漏洞影响联邦系统和全球数百万其他系统的开源代码中的漏洞。
|
||||
|
||||
“这一事件对联邦系统和关键基础设施公司——包括银行、医院和公用事业公司——构成了严重威胁，美国人每天都依赖这些公司提供基本服务，”彼得斯在公告中说。“这项常识性的两党立法将有助于保护开源软件，并进一步加强我们对网络犯罪分子和对全国网络发起不断攻击的外国对手的网络安全防御。”
|
||||
|
||||
《保护开源软件法》还要求管理和预算办公室为机构发布关于保护开源软件的指南，创建 CISA 网络安全咨询委员会的一个软件安全小组委员会，并要求 CISA 聘请开源软件专家协助网络事件。
|
||||
|
||||
在此之前，彼得斯和波特曼的提议已获得参议院一致通过并签署成为法律，以加强州和地方政府的网络防御，并迫使关键基础设施的所有者和运营商向 CISA 报告重大网络攻击和勒索软件付款。
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://www.opensourceforu.com/2022/09/lawmakers-proposes-a-new-bill-to-protect-open-source-software/
|
||||
|
||||
作者：[Laveesh Kocher][a]
|
||||
选题：[lkxed][b]
|
||||
译者：[littlebirdnest](https://github.com/译者ID)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
||||
[a]: https://www.opensourceforu.com/author/laveesh-kocher/
|
||||
[b]: https://github.com/lkxed
|
||||
255
translated/talk/20210207 The Real Novelty of the ARPANET.md
Normal file
255
translated/talk/20210207 The Real Novelty of the ARPANET.md
Normal file
@ -0,0 +1,255 @@
|
||||
[#]: collector: (lujun9972)
|
||||
[#]: translator: (aREversez)
|
||||
[#]: reviewer: ( )
|
||||
[#]: publisher: ( )
|
||||
[#]: url: ( )
|
||||
[#]: subject: (The Real Novelty of the ARPANET)
|
||||
[#]: via: (https://twobithistory.org/2021/02/07/arpanet.html)
|
||||
[#]: author: (Two-Bit History https://twobithistory.org)
|
||||
|
||||
ARPANET 的真正创新之处
|
||||
======
|
||||
|
||||
如果你在搜索引擎中输入“ARPANET”，搜索相关图片，你会看到许多地图的图片，上面是上世纪六十年代末七十年代初 [美国政府创建的研究网络][1]，该网络不断延伸扩展，横跨了整个美国。我猜很多人第一次了解到 ARPANET 的时候都看过这种地图。
|
||||
|
||||
可以说，这些地图很有意思，毕竟我们很难想象过去连接网络的计算机是那么少，就连如此低保真的图片都可以表示出美国全部机器的所在位置（这里的低保真指的是高射投影仪成像技术，而不是大家熟知的 lo-fi 氛围音乐）。不过，这些地图是有问题的。地图上加粗的线条连接着大陆各地，强化了人们的一种观念：ARPANET 最大的贡献就是首次将横跨美国东西两地的电脑连接了起来。
|
||||
|
||||
今天，即便是在病毒肆虐、人们困居家中的情况下，网络也能把我们联系起来，可谓是我们的生命线。所以，如果认为 ARPANET 是最早的互联网，那么在那之前世界必然相互隔绝，毕竟那时还没有今天的互联网，对吧？ARPANET 首次通过计算机将人们连接起来，一定是一件惊天动地的大事。
|
||||
|
||||
但是，这一观点却与历史事实不符，而且它也没有进一步解释 ARPANET 的重要性。
|
||||
|
||||
### 初露锋芒
|
||||
|
||||
华盛顿希尔顿酒店坐落于国家广场东北方向约 2.4 千米处的一座小山丘山顶附近。酒店左右两侧白色的现代化立面分别向外延展出半个圆形，活像一只飞鸟的双翼。1965 年，酒店竣工之后，纽约时报报道称这座建筑物就像“一只栖息在山顶巢穴上的海鸥”[1][2]。
|
||||
|
||||
不过，这家酒店最有名的特点却深藏在地下。在车道交汇处下方，有着一个巨大的蛋形活动场地，这就是人们熟知的国际宴会厅，多年来一直是华盛顿特区最大的无柱宴会厅。1967 年，大门乐队在此举办了一场音乐会。1968 年，“吉他之神”吉米·亨德里克斯也在此举办了一场音乐会。到了 1972 年，国际宴会厅隐去了以往的喧嚣，举办了首届国际计算机通信会议。在这场大会上，研究项目 ARPANET 首次公开亮相。
|
||||
|
||||
1972 年的国际计算机通信会议举办时间为 10 月 24-26 日，与会人数约八百人[2][3]。在这场大会上，计算机网络这一新兴领域的领袖人物齐聚一堂。因特网的先驱鲍勃·卡恩称，“如果有人在华盛顿希尔顿酒店上方丢了一颗炸弹，那么美国的整个网络研究领域将会毁于一旦”[3][4]。
|
||||
|
||||
当然，不是所有的与会人员都是计算机科学家。根据当时的宣传广告，这场大会将会聚焦用户，照顾到“律师、医务人员、经济学家、政府工作者、工程师以及通信员等从业人员”[4][5]。虽然大会的部分议题非常专业，比如“数据网络设计问题（一）”与“数据网络设计问题（二）”，但是正如宣传广告所承诺的，大部分会议的主要关注点还是计算机网络给经济社会带来的潜在影响。其中甚至有一场会议以惊人的先见之明探讨了如何积极利用法律制度“保护计算机数据库中的隐私权益”[5][6]。
|
||||
|
||||
展示 ARPANET 的目的在于尽可能地吸引与会者的关注。各场会议在国际宴会厅或酒店更下一层的其他地方举行，会议休息期间，与会者可以自由进入乔治敦宴会厅（在国际宴会厅走廊尽头的一个较小的宴会厅，也可以说是会议室）[6][7]，那里放置着 40 台由不同制造商生产的终端，用以访问 ARPANET [7][8]。这些终端属于哑终端，也就是说，只能用来输入命令、输出结果，本身无法进行计算。事实上，因为是 1972 年，所以这些终端可能都是硬拷贝终端，即电传打字机。哑终端与一台被称为“终端接口信息处理机”（TIP）的计算机相连接，后者放置在宴会厅中间的一个高台上。TIP 是早期的一种路由器，哑终端可通过 TIP 连接到 ARPANET。有了终端和 TIP，ICCC 与会者可以尝试登录和访问组成 ARPANET 的 29 个主机站的计算机 [8][9]。
|
||||
|
||||
为了展示网络的性能，美国全国各主机站的研究员们通力合作，准备了 19 个简易的“情景”，供用户测试使用。他们还出了 [一份小册子][10]，将这些情景收录其中。如果与会人员打算进入这个满是电线与哑终端的房间，就会得到这样一本小册子 [9][11]。通过这些情景，研究员不仅要证明网络这项新技术的可行性，还要证明其实用性，因为 ARPANET 那时还只是“一条没有汽车驶过的公路”。此外，来自国防部的投资者们也希望，公开展示 ARPANET 可以进一步激发人们对网络的兴趣 [10][12]。
|
||||
|
||||
因此，这些情景充分展示了在 ARPANET 网络上可以使用的软件的丰富性：有程序语言解释器，其中一个是麻省理工学院（MIT） Lisp 语言的解释器，另一个是加州大学洛杉矶分校的数值计算环境 Speakeasy 项目的解释器；还有一些游戏，包括国际象棋和 <ruby>康威生命游戏<rt>Conway's Game of Life</rt></ruby>；以及最受与会者欢迎的几个人工智能聊天程序，包括由 MIT 的计算机科学家约瑟夫·魏泽堡开发的著名聊天程序伊莉莎。
|
||||
|
||||
设置情景的研究人员小心翼翼地列出了他们想让用户在终端机上输入的每一条命令。这点很重要，因为用于连接 ARPANET 主机的命令序列可能会因为主机的不同而发生变化。比如，为了能在 MIT 人工智能实验室的 PDP-10 微型电脑上测试人工智能国际象棋程序，与会者需要按照指示输入以下命令：
|
||||
|
||||
在下方代码块中， _`[LF]`、`[SP]` 以及 `[CR]` 分别代表换行、空格以及回车键。我在每行的 `//` 符号后面都解释了当前一行命令的含义，不过当时的小册子本来是没有使用这一符号的。
|
||||
|
||||
```
|
||||
@r [LF] // 重置 TIP
|
||||
@e [SP] r [LF] // “远程回显”设置, 主机回显字符，TIP 不回显
|
||||
@L [SP] 134 [LF] // 连接 134 号主机
|
||||
:login [SP] iccXXX [CR] // 登录 MIT 人工智能实验室的系统，“XXX”代表用户名首字母缩写
|
||||
:chess [CR] // 启动国际象棋程序
|
||||
```
|
||||
|
||||
如果与会者输入了上述命令，那么他就可以体验当时最先进的国际象棋程序，其棋盘布局如下：
|
||||
|
||||
```
|
||||
BR BN BB BQ BK BB BN BR
|
||||
BP BP BP BP ** BP BP BP
|
||||
-- ** -- ** -- ** -- **
|
||||
** -- ** -- BP -- ** --
|
||||
-- ** -- ** WP ** -- **
|
||||
** -- ** -- ** -- ** --
|
||||
WP WP WP WP -- WP WP WP
|
||||
WR WN WB WQ WK WB WN WR
|
||||
```
|
||||
|
||||
与之不同的是，如果要连接加州大学洛杉矶分校的 IBM System/360 机器，运行 Speakeasy 数值计算环境，与会者需要输入以下命令：
|
||||
|
||||
```
|
||||
@r [LF] // 重置 TIP
|
||||
@t [SP] o [SP] L [LF] // “传递换行”设置
|
||||
@i [SP] L [LF] // “插入换行”设置，即回车时发送换行符。
|
||||
@L [SP] 65 [LF] // 连接 65 号主机
|
||||
tso // 连接 IBM 分时可选软件系统
|
||||
logon [SP] icX [CR] // 输入用户名，进行登录，“X”可为任意数字
|
||||
iccc [CR] // 输入密码（够安全！）
|
||||
speakez [CR] // 启动 Speakeasy
|
||||
```
|
||||
|
||||
输入上述命令后，与会者可以在终端中对矩阵进行乘法、转置以及其他运算，如下所示：
|
||||
|
||||
```
|
||||
:+! a=m*transpose(m);a [CR]
|
||||
:+! eigenvals(a) [CR]
|
||||
```
|
||||
|
||||
当时，这场演示给许多人都留下了深刻的印象，但原因并不是我们所想的那样，毕竟我们有的只是后见之明。今天的人们总是记不住，在 1972 年，即便身处两个不同的城市，远程登录使用计算机也已经不是一件新鲜事儿了。在那之前的数十年，电传打字机就已经用于与相隔很远的计算机传递信息了。在 ICCC 第一届大会之前，差不多整整五年，在西雅图的一所高中，比尔·盖茨使用电传打字机，在该市其他地方的通用电气计算机上运行了他的第一个 BASIC 程序。在当时，登录远程计算机，运行几行命令或者玩一些文字游戏，只不过是家常便饭。因此，虽说上文提到的软件的确很不错，但是即便没有 ARPANET，我刚刚介绍的两个情景勉强也是可以实现的。
|
||||
|
||||
当然，ARPANET 一定带来了新的东西。参加本次大会的律师、政治家与经济学家关注更多的可能是国际象棋游戏与聊天机器人，但是网络专家们可能对另外两个情景更感兴趣，因为它们将 ARPANET 的作用更好地展示了出来。
|
||||
|
||||
在其中一个情景下，MIT <ruby>非兼容分时系统<rt>ITS</rt></ruby> 上运行了一个名为 `NETWRK` 的程序。`NETWRK` 命令下有若干个子命令，输入这些子命令就能得到 ARPANET 各方面的运行状态。`SURVEY` 子命令可以列出 ARPANET 上面运行的主机与空闲的主机，放入一个列表中；`SUMMARY.OF.SURVEY` 子命令对 `SURVEY` 子命令的运行结果进行统计，得出每台主机的“正常运行比率”，以及每台主机响应消息的平均时间。`SUMMARY.OF.SURVEY` 子命令以表格的形式输出结果，如下所示：
|
||||
|
||||
```
|
||||
--HOST-- -#- -%-UP- -RESP-
|
||||
UCLA-NMC 001 097% 00.80
|
||||
SRI-ARC 002 068% 01.23
|
||||
UCSB-75 003 059% 00.63
|
||||
...
|
||||
```
|
||||
|
||||
可以看到，主机编号的占位不超过三个数字。其他 `NETWRK` 子命令能够查看较长时间内查询结果的概要，或者检查单个主机查询结果的日志。
|
||||
|
||||
第二个情景用到了斯坦福大学开发的一款软件——SRI-ARC 联机系统。这款软件功能齐全，非常优秀。美国发明家道格拉斯·恩格尔巴特在 <ruby>所有演示之母<rt>Mother of All Demos</rt></ruby> 上演示的正是 SRI-ARC 联机系统。这款软件可以在加州大学圣芭芭拉分校的主机上运行本质上属于文件托管的服务。使用华盛顿希尔顿酒店的终端，用户就可以将斯坦福大学主机上创建的文件复制到加州大学圣芭芭拉分校的主机上。操作也很简单，只需执行 `copy` 命令，然后回答计算机的下列问题：
|
||||
|
||||
_在下方的代码块中，`[ESC]`、`[SP]` 与 `[CR]` 分别代表退出、空格与回车键；圆括号中的文字是计算机打印出的提示信息；第三行中的退出键用于自动补全文件名。此处复制的文件是 `<system>sample.txt;1`，其中文件名末尾的数字 1 代表文件的版本号，`<system>` 表示文件路径。这种文件名是 TENEX 操作系统上面的惯用写法。_[11][13]
|
||||
|
||||
```
|
||||
@copy
|
||||
(TO/FROM UCSB) to
|
||||
(FILE) <system>sample [ESC] .TXT;1 [CR]
|
||||
(CREATE/REPLACE) create
|
||||
```
|
||||
|
||||
这两个情景看起来好像和最初提及的两个情景没有太大区别，但是此二者却意义非凡。因为它们证明了，在 ARPANET 上面，不仅人们可以与计算机进行交流，计算机与计算机也可以 _相互_ 交流。保存在 MIT 的 `SURVEY` 命令的结果并非由人类定期登录并检查每台机器的运行状态收集而来，而是由一款能在网络上与其他机器进行交流的软件收集得到的。同样的道理，在斯坦福大学与加州大学圣芭芭拉分校之间传输文件的情景下，也没有人守在两所大学的终端旁边，特区的终端用户仅仅使用了一款软件，就能让其他两地的计算机连接起来。此外，这一点无关乎你使用的是宴会厅里的哪一台电脑，因为只要输入同样的命令序列，就能在任意一台电脑上浏览 MIT 的网络监视数据，或者在加州大学圣芭芭拉分校的计算机上储存文件。
|
||||
|
||||
这才是 ARPANET 的全新之处。本次国际计算机通信会议演示的不仅仅是人与远程电脑之间的交互，也不仅仅是远程输入输出的操作，更是一个软件与其他软件之间的远程通讯，这一点才是史无前例的。
|
||||
|
||||
为什么这一点才是最重要的，而不是地图上画着的那些贯穿整个美国、实际连接起来的电线呢（这些线是租赁的电话线，而且它们以前就在那了！）？要知道，早在 1966 年 ARPANET 项目启动之前，美国国防部的高级研究计划署打造了一间终端室，里面有三台终端。三台终端分别连接着位于 MIT、加州大学伯克利分校以及圣塔莫尼卡三地的计算机 [12][14]。对于高级研究计划署的工作人员来说，即便他们身处华盛顿特区，使用这三台计算机也非常方便。不过，这其中也有不便之处：工作人员必须购买和维护来自三家不同制造商的终端，牢记三种不同的登录步骤，熟悉三种不同的计算环境。虽然这三台终端机可能就放在一起，但是它们只是电线另一端主机系统的延申，而且操作也和那些计算机一样各不相同。所以说，在 ARPANET 项目诞生之前，远程连接计算机进行通讯就已经实现了，但问题是不同的计算系统阻碍了通讯朝着更加先进复杂的方向发展。
|
||||
|
||||
### 此刻，集合起来
|
||||
|
||||
因此，我想说的是，说法一（ARPANET 首次通过计算机将不同地方的人们连接了起来）与说法二（ARPANET 首次将多个计算机系统彼此连接了起来）之间有着云泥之别。听起来似乎有些吹毛求疵，咬文嚼字，但是相较于说法二，说法一忽略了一些重要的历史发展阶段。
|
||||
|
||||
首先，历史学家乔伊·利西·兰金（Joy Lisi Rankin）指出，早在 ARPANET 诞生之前，人们就已经在网络空间中进行交流了。在《美国人民的计算机历史》（_A People’s History of Computing in the United States_）一书中，兰金介绍了多个覆盖全国的数字社区，这些社区运行在早于 ARPANET 的分时网络上面。从技术层面讲，分时网络并不属于计算机网络，因为它仅仅由一台大型主机构成。这种计算机放置在地下室中，为多台哑终端提供计算，颇像一只又黑又胖的奇怪生物，触手向外伸展着，遍及整个美国。不过，在分时网络时代，被后社交媒体时代称为“网络”的大部分社会行为应有尽有。例如，Kiewit 网络是达特茅斯分时系统的延申应用，服务于美国东北部的各个大学和高中。在 Kiewit 网络上，高中生们共同维护着一个“<ruby>八卦文件<rt>gossip file</rt></ruby>”，用来记录其他学校发生的趣闻趣事，“在康涅狄格州和缅因州之间建立起了社交联系” [13][15]。同时，曼荷莲女子学院的女生通过网络与达特茅斯学院的男生进行交流，或者是安排约会，或者是与男朋友保持联系 [14][16]。这些事实都发生在上世纪六十年代。兰金认为，如果忽视了早期的分时网络，我们对美国过去 50 年数字文化发展的认识必然是贫瘠的：我们眼里可能只有所谓的“<ruby>硅谷神话<rt>Silicon Valley mythology</rt></ruby>”，认为计算机领域的所有发展都要归功于少数的几位天才，或者说互联网科技巨头的创始人。
|
||||
|
||||
回到 ARPANET，如果我们能意识到真正的困难是计算机 _系统_ 的联通，而非机器本身的连接，那么在探讨 ARPANET 的创新点时，我们就会更加倾向于第二种说法。ARPANET 是第一个包交换网络，涉及到许多重要的技术应用。但是如果仅仅因为这项优势，就说它是一项突破，我觉得这种说法本身就是错的。ARPANET 旨在促进全美计算机科学家之间的合作，目的是要弄明白不同的操作系统与不同语言编写的软件如何配合使用，而非如何在麻省和加州之间实现高效的数据传输。因此，ARPANET 不仅是第一个包交换网络，它还是一项非常成功且优秀的标准。在我看来，后者更有意思，毕竟我在博客上曾经写过许多颇有瑕疵的标准：[语义网][17]、[RSS][18] 与 [FOAF ][19]。
|
||||
|
||||
ARPANET 项目初期没有考虑到网络协议，协议的制定是后来的事情了。因此，这项工作自然落到了主要由研究生组成的组织——<ruby>国际网络工作组<rt>Network Working Group</rt></ruby> 身上。该组织的首次会议于 1968 年在加州大学圣芭芭拉分校举办 [15][20]。当时只有 12 人参会，大部分都是来自上述四所大学的代表 [16][21]。来自加州大学洛杉矶分校的研究生史蒂夫·克罗克（Steve Crocker）参加了这场会议。他告诉我，工作组首次会议的参会者清一色都是年轻人，最年长的可能要数会议主席埃尔默·夏皮罗（Elmer Shapiro）了，他当年 38 岁左右。高级研究计划署没有安排负责研究计算机连接之后如何进行通信的人员，但是很明显它需要提供一定的协助。随着工作组会议的陆续开展，克罗克一直期望着更有经验与威望的“法定成年人”从东海岸飞过来接手这项工作，但是期望终究还是落空了。在高级研究计划署的默许之下，工作组举办了多场会议，其中包括很多长途旅行，差旅费由计划署报销，这些就是计划署给与工作组的全部协助了 [17][22]。
|
||||
|
||||
当时，国际网络工作组面临着巨大的挑战。组内成员都没有使用通用方式连接计算机系统的经验，而且这本来就与上世纪六十年代末计算机领域盛行的全部观点相悖：
|
||||
|
||||
> 那个时候的主机就像是全世界唯一的一台计算机。即便是最简短的交流会话，两台主机也无法轻易做到。并不是说机器没办法相互连接，只是连接之后，两台计算机又能做些什么呢？当时，计算机和与其相连的其他设备之间的通讯，就像帝王与群臣之间的对话一般。连接到主机的设备各自执行着自己的任务，每台外围设备都保持着常备不懈的状态，等待着上司的命令。当时的计算机就是严格按照这类交流需求设计出来的；它们向读卡器、终端与磁带机等下属设备发号施令，发起所有会话。但是，如果一台计算机拍了拍另一台计算机的肩膀，说道，“你好，我也是一台计算机”，那么另一台计算机可就傻眼了，什么也回答不上来 [18][23]。
|
||||
于是，工作组的最初进展比较缓慢 [19][24]。直到 1970 年 6 月，也就是首次会议将近两年之后，工作组才为网络协议选定了一套官方规范 [20][25]。
|
||||
|
||||
到了 1972 年，在国际计算机通信会议上展示 ARPANET 的时候，所有的协议已经准备到位了。会议期间，这些协议运用到了国际象棋等情景之中。用户运行 `@e r` 命令（`@echo remote` 命令的缩写形式），可以指示 TIP 使用新远程登录虚拟终端协议提供的服务，通知远程主机回显用户输入的内容。接着，用户运行 `@L 134` 命令（`@login 134` 命令的缩写形式），让 TIP 在 134 号主机上调用<ruby>初始连接协议<rt>Initial Connection Protocol</rt></ruby>，该协议指示远程主机分配出连接所需的全部必要资源，并将用户带入远程登录会话中。上述文件传输的情景也许用到了 <ruby>文件传输协议<rt>File Transfer Protocol</rt></ruby>，而该协议恰好是在大会举办前夕才刚刚完成的 [21][26]。所有这些协议都是“三层”协议，其下的第二层是主机到主机层协议，定义了主机之间可以相互发送和接收的信息的基本格式；第一层是主机到接口通信处理机协议，定义了主机如何与连接的远程设备进行通信。令人感到不可思议的是，这些协议都能正常运行。
|
||||
|
||||
在我看来，网络工作组之所以能够在大会举办之前做好万全的准备，顺利且出色地完成任务，在于他们采用了开放且非正式的标准化方法，其中一个典型的例子就是著名的 Request for Comments（RFC）系列文档。RFC 文档最初通过传统邮件供工作组成员进行传阅，让成员们在没有举办会议的时候也能保持联系，同时收集成员反馈，汇集各方智慧。RFC 框架是克罗克提出的，他写出了第一篇 RFC 文档，并在早期负责管理 RFC 的邮寄列表。他这样做是为了强调工作组开放协作的活动本质。有了这套框架以及触手可及的文档，ARPANET 的协议设计过程成了一个大熔炉，每个人都可以贡献出自己的力量，步步推进，精益求精，让最棒的想法脱颖而出，使得每一位贡献者都值得尊敬。总而言之，RFC 获得了巨大成功，并且直至今天，长达半个世纪之后，它依旧是网络标准的“说明书”。
|
||||
|
||||
因此，说起 ARPANET 的影响力，我认为不得不强调的一点正是工作组留下的这一成果。今天，互联网可以把世界各地的人们连接起来，这也是它最神奇的属性之一。不过如果说这项技术到了上世纪才开始使用，那可就有些滑稽可笑了。要知道，在 ARPANET 出现之前，人们就已经通过电报打破了现实距离的限制。而 ARPANET 打破的应该是各个主机站点因使用不同的操作系统、字符编码、程序语言以及组织策略而在逻辑层面产生的差异限制。当然，不得不提的是，将第一个包交换网络投入使用在技术方面绝对是一大壮举。不过，在建立 ARPANET 网络过程中遇到的两大难题中，更为复杂的一项则是制定统一的标准并用以连接原本无法相互协作的计算机。而这一难题的解决方案，也成了 ARPANET 整个建立与发展历史中最为神奇的一个章节。
|
||||
|
||||
1981 年，高级研究计划署发表了一份“完工报告”，回顾了 ARPANET 项目的第一个十年。在《付出收获了回报的技术方面以及付出未能实现最初设想的技术方面》这一冗长的小标题下，作者们写道：
|
||||
|
||||
> 或许，在 ARPANET 的开发过程中，最艰难的一项任务就是，尽管主机制造商各不相同，或者同一制造商下操作系统各不相同，我们仍需在众多的独立主机系统之间实现通讯交流。好在这项任务后来取得了成功 [22][27]。
|
||||
你可以从美国联邦政府获得相关信息。
|
||||
|
||||
_如果你喜欢这篇文章，欢迎关注推特 [@TwoBitHistory][28]，也可通过 [RSS feed][29] 订阅，获取最新文章。_
|
||||
|
||||
1. “Hilton Hotel Opens in Capital Today.” _The New York Times_, 20 March 1965, <https://www.nytimes.com/1965/03/20/archives/hilton-hotel-opens-in-capital-today.html?searchResultPosition=1>. Accessed 7 Feb. 2021. [↩︎][31]
|
||||
|
||||
2. James Pelkey. _Entrepreneurial Capitalism and Innovation: A History of Computer Communications 1968-1988,_ Chapter 4, Section 12, 2007, <http://www.historyofcomputercommunications.info/Book/4/4.12-ICCC%20Demonstration71-72.html>. Accessed 7 Feb. 2021. [↩︎][32]
|
||||
|
||||
3. Katie Hafner and Matthew Lyon. _Where Wizards Stay Up Late: The Origins of the Internet_. New York, Simon & Schuster, 1996, p. 178. [↩︎][33]
|
||||
|
||||
4. “International Conference on Computer Communication.” _Computer_, vol. 5, no. 4, 1972, p. c2, <https://www.computer.org/csdl/magazine/co/1972/04/01641562/13rRUxNmPIA>. Accessed 7 Feb. 2021. [↩︎][34]
|
||||
|
||||
5. “Program for the International Conference on Computer Communication.” _The Papers of Clay T. Whitehead_, Box 42, <https://d3so5znv45ku4h.cloudfront.net/Box+042/013_Speech-International+Conference+on+Computer+Communications,+Washington,+DC,+October+24,+1972.pdf>. Accessed 7 Feb. 2021. [↩︎][35]
|
||||
|
||||
6. 我其实并不清楚 ARPANET 是在哪个房间展示的。很多地方都提到了“宴会厅”，但是华盛顿希尔顿酒店更习惯于叫它“乔治敦”，而不是把它当成一间会议室。因此，或许这场展示是在国际宴会厅举办的。但是 RFC 372 号文件又提到了预定“乔治敦”作为展示场地一事。华盛顿希尔顿酒店的楼层平面图可以点击 [此处][36] 查看。 [↩︎][37]
|
||||
|
||||
7. Hafner, p. 179. [↩︎][38]
|
||||
|
||||
8. ibid., p. 178. [↩︎][39]
|
||||
|
||||
9. Bob Metcalfe. “Scenarios for Using the ARPANET.” _Collections-Computer History Museum_, <https://www.computerhistory.org/collections/catalog/102784024>. Accessed 7 Feb. 2021. [↩︎][40]
|
||||
|
||||
10. Hafner, p. 176. [↩︎][41]
|
||||
|
||||
11. Robert H. Thomas. “Planning for ACCAT Remote Site Operations.” BBN Report No. 3677, October 1977, <https://apps.dtic.mil/sti/pdfs/ADA046366.pdf>. Accessed 7 Feb. 2021. [↩︎][42]
|
||||
|
||||
12. Hafner, p. 12. [↩︎][43]
|
||||
|
||||
13. Joy Lisi Rankin. _A People’s History of Computing in the United States_. Cambridge, MA, Harvard University Press, 2018, p. 84. [↩︎][44]
|
||||
|
||||
14. Rankin, p. 93. [↩︎][45]
|
||||
|
||||
15. Steve Crocker. Personal interview. 17 Dec. 2020. [↩︎][46]
|
||||
|
||||
16. 克罗克将会议记录文件发给了我，文件列出了所有的参会者。[↩︎][47]
|
||||
|
||||
17. Steve Crocker. Personal interview. [↩︎][48]
|
||||
|
||||
18. Hafner, p. 146. [↩︎][49]
|
||||
|
||||
19. “Completion Report / A History of the ARPANET: The First Decade.” BBN Report No. 4799, April 1981, <https://walden-family.com/bbn/arpanet-completion-report.pdf>, p. II-13. [↩︎][50]
|
||||
|
||||
20. 这里我指的是 RFC 54 号文件中的“官方协议”。[↩︎][51]
|
||||
|
||||
21. Hafner, p. 175. [↩︎][52]
|
||||
|
||||
22. “Completion Report / A History of the ARPANET: The First Decade,” p. II-29. [↩︎][53]
|
||||
|
||||
|
||||
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://twobithistory.org/2021/02/07/arpanet.html
|
||||
|
||||
作者：[Two-Bit History][a]
|
||||
选题：[lujun9972][b]
|
||||
译者：[aREversez](https://github.com/aREversez)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
||||
[a]: https://twobithistory.org
|
||||
[b]: https://github.com/lujun9972
|
||||
[1]: https://en.wikipedia.org/wiki/ARPANET
|
||||
[2]: tmp.pnPpRrCI3S#fn:1
|
||||
[3]: tmp.pnPpRrCI3S#fn:2
|
||||
[4]: tmp.pnPpRrCI3S#fn:3
|
||||
[5]: tmp.pnPpRrCI3S#fn:4
|
||||
[6]: tmp.pnPpRrCI3S#fn:5
|
||||
[7]: tmp.pnPpRrCI3S#fn:6
|
||||
[8]: tmp.pnPpRrCI3S#fn:7
|
||||
[9]: tmp.pnPpRrCI3S#fn:8
|
||||
[10]: https://archive.computerhistory.org/resources/access/text/2019/07/102784024-05-001-acc.pdf
|
||||
[11]: tmp.pnPpRrCI3S#fn:9
|
||||
[12]: tmp.pnPpRrCI3S#fn:10
|
||||
[13]: tmp.pnPpRrCI3S#fn:11
|
||||
[14]: tmp.pnPpRrCI3S#fn:12
|
||||
[15]: tmp.pnPpRrCI3S#fn:13
|
||||
[16]: tmp.pnPpRrCI3S#fn:14
|
||||
[17]: https://twobithistory.org/2018/05/27/semantic-web.html
|
||||
[18]: https://twobithistory.org/2018/12/18/rss.html
|
||||
[19]: https://twobithistory.org/2020/01/05/foaf.html
|
||||
[20]: tmp.pnPpRrCI3S#fn:15
|
||||
[21]: tmp.pnPpRrCI3S#fn:16
|
||||
[22]: tmp.pnPpRrCI3S#fn:17
|
||||
[23]: tmp.pnPpRrCI3S#fn:18
|
||||
[24]: tmp.pnPpRrCI3S#fn:19
|
||||
[25]: tmp.pnPpRrCI3S#fn:20
|
||||
[26]: tmp.pnPpRrCI3S#fn:21
|
||||
[27]: tmp.pnPpRrCI3S#fn:22
|
||||
[28]: https://twitter.com/TwoBitHistory
|
||||
[29]: https://twobithistory.org/feed.xml
|
||||
[30]: https://twitter.com/TwoBitHistory/status/1277259930555363329?ref_src=twsrc%5Etfw
|
||||
[31]: tmp.pnPpRrCI3S#fnref:1
|
||||
[32]: tmp.pnPpRrCI3S#fnref:2
|
||||
[33]: tmp.pnPpRrCI3S#fnref:3
|
||||
[34]: tmp.pnPpRrCI3S#fnref:4
|
||||
[35]: tmp.pnPpRrCI3S#fnref:5
|
||||
[36]: https://www3.hilton.com/resources/media/hi/DCAWHHH/en_US/pdf/DCAWH.Floorplans.Apr25.pdf
|
||||
[37]: tmp.pnPpRrCI3S#fnref:6
|
||||
[38]: tmp.pnPpRrCI3S#fnref:7
|
||||
[39]: tmp.pnPpRrCI3S#fnref:8
|
||||
[40]: tmp.pnPpRrCI3S#fnref:9
|
||||
[41]: tmp.pnPpRrCI3S#fnref:10
|
||||
[42]: tmp.pnPpRrCI3S#fnref:11
|
||||
[43]: tmp.pnPpRrCI3S#fnref:12
|
||||
[44]: tmp.pnPpRrCI3S#fnref:13
|
||||
[45]: tmp.pnPpRrCI3S#fnref:14
|
||||
[46]: tmp.pnPpRrCI3S#fnref:15
|
||||
[47]: tmp.pnPpRrCI3S#fnref:16
|
||||
[48]: tmp.pnPpRrCI3S#fnref:17
|
||||
[49]: tmp.pnPpRrCI3S#fnref:18
|
||||
[50]: tmp.pnPpRrCI3S#fnref:19
|
||||
[51]: tmp.pnPpRrCI3S#fnref:20
|
||||
[52]: tmp.pnPpRrCI3S#fnref:21
|
||||
[53]: tmp.pnPpRrCI3S#fnref:22
|
||||
@ -0,0 +1,67 @@
|
||||
[#]: collector: "lujun9972"
|
||||
[#]: translator: "Veryzzj"
|
||||
[#]: reviewer: " "
|
||||
[#]: publisher: " "
|
||||
[#]: url: " "
|
||||
[#]: subject: "How I prioritize tasks on my to-do list"
|
||||
[#]: via: "https://opensource.com/article/21/1/prioritize-tasks"
|
||||
[#]: author: "Kevin Sonney https://opensource.com/users/ksonney"
|
||||
|
||||
如何确定待办事项上任务的优先级
|
||||
======
|
||||
|
||||
使用艾森豪威尔矩阵更好地安排你的待办事项的优先次序。
|
||||
![Team checklist and to dos][1]
|
||||
|
||||
在前几年，这个年度系列涵盖了单个应用程序。今年，除了策略之外，我们还将着眼于一体式解决方案，以在2021提供帮助。欢迎来到2021年“21天生产力”活动的第4天。在本文中，将研究一种在待办事项上确定任务优先级的策略。想要找到适合你日常工作的开源工具，请查看[此列表][2]。
|
||||
|
||||
把事情添加到任务或待办事项中很容易。几乎太容易了。而一旦列入清单，挑战就变成了弄清楚先做什么。我们要做清单首位的事情吗？清单首位的事情是最重要的吗？如何弄清楚最重要的事是什么？
|
||||
|
||||
![To-do list][3]
|
||||
|
||||
要做的事。今天？明天？谁知道呢？（Kevin Sonney, [CC BY-SA 4.0][4]）
|
||||
|
||||
[与电子邮件一样][5]，我们可以根据一些事情来确定任务的优先级，这可以让我们弄清楚什么事情需要先做，什么可以等到以后再做。
|
||||
|
||||
我使用一种被称为_艾森豪威尔矩阵_ 的方法，它取自美国总统 Dwight D. Eisenhower 的一句话。画一个水平和垂直分割的方框。在列上标明“紧急”和“不紧急”，在行上标明“重要”和“不重要”。
|
||||
|
||||
![Eisenhower matrix][6]
|
||||
|
||||
一个艾森豪威尔矩阵。（Kevin Sonney, [CC BY-SA 4.0][4]）
|
||||
|
||||
你可以把待办事项上的任务放在其中一个框里。但如何知道一个任务应该放在哪里？紧迫性和重要性往往是主观的。因此，第一步就是决定什么对你来说是重要的。我的家庭（包括宠物）、工作和爱好都很重要。如果待办事项上的东西与这三件事无关，我可以立即把它放到 “不重要”行。
|
||||
|
||||
紧迫性是一个比较简单的问题。一件事需要在今天或明天完成吗？那么它可能是“紧急的”。一件事是否有一个即将到来的最后期限，但离那个时间还有几天/几周/几个月，或者它根本就没有最后期限？当然是“不急的”。
|
||||
|
||||
现在我们可以将这些框转化为优先级。“紧急/重要”是最高优先级（即第一优先级），需要首先完成。接下来是“不紧急/重要”（优先级2），然后是“紧急/不重要”（优先级3），最后是“不紧急/不重要”（优先级4或根本没有优先级）。
|
||||
|
||||
请注意，"紧急/不重要 "是第三位，而不是第二位。这是因为，人们花了很多时间在那些看似重要的事情上，只是因为它们比较紧急，实际上这些事并不是重要的。当我看到这类事项时，我会问自己一些问题。 这些任务需要我具体完成吗？这些任务我可以要求其他人去做吗？它们对其他人来说是否重要和紧急？而这是否改变了它们对我的重要性？也许它们需要重新分类，或者我可以要求别人完成，并将它们从我的清单中删除。
|
||||
|
||||
![After prioritizing][7]
|
||||
|
||||
确定优先级后。 （Kevin Sonney, [CC BY-SA 4.0][4]）
|
||||
|
||||
对于”不紧急/不重要“框中的事项，有一个问题要问，那就是“这些事情到底需不需要放在我的清单上？”说实话，我们经常用那些不紧急或不重要的事情来填满待办事项清单，但其实完全可以将它们从清单上删除。我知道承认“这事永远不会完成”是很难的，但在接受这个事实后，把这个事情从清单上删除并且不用再为它担心，是一种解脱。
|
||||
|
||||
经过这一切，看着清单很容易说出：“这是我现在需要做的事情。“然后完成它。这就是待办事项的作用：为一天提供指导和重点。
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://opensource.com/article/21/1/prioritize-tasks
|
||||
|
||||
作者：[Kevin Sonney][a]
|
||||
选题：[lujun9972][b]
|
||||
译者：[Veryzzj](https://github.com/Veryzzj)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
||||
[a]: https://opensource.com/users/ksonney
|
||||
[b]: https://github.com/lujun9972
|
||||
[1]: https://opensource.com/sites/default/files/styles/image-full-size/public/lead-images/todo_checklist_team_metrics_report.png?itok=oB5uQbzf "Team checklist and to dos"
|
||||
[2]: https://opensource.com/article/20/5/alternatives-list
|
||||
[3]: https://opensource.com/sites/default/files/pictures/to-do-list.png "To-do list"
|
||||
[4]: https://creativecommons.org/licenses/by-sa/4.0/
|
||||
[5]: https://opensource.com/article/21/1/email-rules
|
||||
[6]: https://opensource.com/sites/default/files/pictures/eisenhower-matrix.png "Eisenhower matrix"
|
||||
[7]: https://opensource.com/sites/default/files/pictures/after-prioritizing.png "After prioritizing"
|
||||
@ -1,161 +0,0 @@
|
||||
[#]: subject: "Install Linux Mint with Windows 11 Dual Boot [Complete Guide]"
|
||||
[#]: via: "https://www.debugpoint.com/linux-mint-install-windows/"
|
||||
[#]: author: "Arindam https://www.debugpoint.com/author/admin1/"
|
||||
[#]: collector: "lkxed"
|
||||
[#]: translator: "gpchn"
|
||||
[#]: reviewer: " "
|
||||
[#]: publisher: " "
|
||||
[#]: url: " "
|
||||
|
||||
使用 Windows 11 双引导安装 Linux Mint [完整指南]
|
||||
======
|
||||
将 Linux Mint 与 Windows 11（或 Windows 10）同时安装并制作双引导系统的完整指南。
|
||||
|
||||
如果您是新的 Linux 用户，尝试在不删除 OEM 安装的 Windows 的情况下安装 Linux Mint，请遵循本指南。完成下面描述的步骤后，您应该拥有一个双引导系统，您可以在其中学习和在 Linux 系统中完成工作，而无需引导 Windows。
|
||||
|
||||
### 1. 开始之前您需要什么？
|
||||
|
||||
启动到您的 Windows 系统并从官方网站下载 Linux Mint ISO 文件。 ISO 文件是 Linux Mint 的安装映像，我们将在本指南中使用它。
|
||||
|
||||
* 在官网（图1），下载 Cinnamon 桌面版的 ISO（适合大家）。
|
||||
|
||||
* [下载链接][1]
|
||||
|
||||
![图1：从官网下载Linux Mint][2]
|
||||
|
||||
* 下载后，将 U 盘插入您的系统。然后使用 Rufus 或 [Etcher][3] 将上面下载的 .ISO 文件写入该 USB 驱动器。
|
||||
|
||||
### 2.准备一个分区来安装Linux Mint
|
||||
|
||||
理想情况下，Windows 笔记本电脑通常配备 C 盘和 D 盘。 C 盘是安装 Windows 的地方。对于新的笔记本电脑，D 驱动器通常是空的（任何后续驱动器，如 E 等）。现在，您有两个选项可供选择：一是**缩小 C 盘** 为额外的 Linux 安装腾出空间。第二个是**使用其他驱动器/分区**，例如 D 盘或 E盘。
|
||||
|
||||
选择您希望的方法。
|
||||
|
||||
* 如果您选择使用 D 盘或 E 盘进行 Linux 安装，请确保先禁用 BitLocker，然后再禁用现代 OEM 安装的 Windows 笔记本电脑附带的所有其他功能。 * 从开始菜单打开 Windows PowerShell 并键入以下命令（图 2）以禁用 BitLocker。根据您的目标驱动程序更改驱动器号（这里，我使用了驱动器 E）。
|
||||
|
||||
```
|
||||
manage-bde -off E
|
||||
```
|
||||
|
||||
![图2：禁用 Windows 驱动器中的 BitLocker 以安装 Linux][4]
|
||||
|
||||
* 现在，如果您选择缩小 C 盘（或任何其他驱动器），请从开始菜单打开“磁盘管理”，它将显示您的整个磁盘布局。
|
||||
* 右键单击并在要缩小的驱动器上选择“Shrink Volume”（图 3），以便为 Linux Mint 腾出位置。
|
||||
* 在下一个窗口中，在“输入要缩小的空间量（以 MB 为单位）”下以 MB 为单位提供您的分区大小（图 4）。显然，它应该小于或等于“可用空间大小”中提到的值。因此，对于 100 GB 的分区，给出 100*1024=102400 MB。
|
||||
* 完成后，单击收缩。
|
||||
|
||||
![磁盘分区中的压缩卷选项示例][5]
|
||||
|
||||
![图4：输入 Linux 分区的大小][6]
|
||||
|
||||
* 现在，您应该会看到一个“未分配空间”，如下所示（图 5）。右键单击它并选择“新建简单卷”。
|
||||
* 此向导将使用文件系统准备和格式化分区。注意：您可以在 Windows 本身中或在 Linux Mint 安装期间执行此操作。 Linux Mint 安装程序还为您提供了创建文件系统表和准备分区的选项。我建议您在这里做。
|
||||
* 在接下来的一系列屏幕中（图 6,7 和 8），以 MB 为单位给出分区大小，分配驱动器号（例如 D、E、F）和文件系统为 fat32。
|
||||
* 最后，您应该会看到您的分区已准备好安装 Linux Mint。您应该在 Mint 安装期间按照以下步骤选择此选项。
|
||||
* 作为预防措施，记下分区大小（您刚刚在图 9 中作为示例创建）以便在安装程序中快速识别它。
|
||||
|
||||
![图5：创建未分配空间][7]
|
||||
|
||||
![图6：新建简单卷向导-page1][8]
|
||||
|
||||
![图7：新建简单卷向导-page2][9]
|
||||
|
||||
![图8：新建简单卷向导-page3][10]
|
||||
|
||||
![图9：安装Linux的最终分区][11]
|
||||
|
||||
### 3. 在 BIOS 中禁用安全启动
|
||||
|
||||
* 插入 USB 驱动器并重新启动系统。
|
||||
* 开机时，反复按相应的功能键进入BIOS。您的笔记本电脑型号的密钥可能不同。这是主要笔记本电脑品牌的参考。
|
||||
* 您应该禁用安全 BIOS 并确保将启动设备优先级设置为 U 盘。
|
||||
* 然后按 F10 保存并退出。
|
||||
|
||||
| Laptop OEM | Function key to enter BIOS |
|
||||
| :- | :- |
|
||||
| Acer | F2 or DEL |
|
||||
| ASUS | F2 for all PCs, F2 or DEL for motherboards |
|
||||
| Dell | F2 or F12 |
|
||||
| HP | ESC or F10 |
|
||||
| Lenovo | F2 or Fn + F2 |
|
||||
| Lenovo (Desktops) | F1 |
|
||||
| Lenovo (ThinkPads) | Enter + F1. |
|
||||
| MSI | DEL for motherboards and PCs |
|
||||
| Microsoft Surface Tablets | Press and hold the volume up button. |
|
||||
| Origin PC | F2 |
|
||||
| Samsung | F2 |
|
||||
| Sony | F1, F2, or F3 |
|
||||
| Toshiba | F2 |
|
||||
|
||||
### 4. 安装 Linux Mint
|
||||
|
||||
如果一切顺利，您应该会看到一个安装 Linux Mint 的菜单。选择“启动 Linux Mint……”选项。
|
||||
|
||||
![图 10：Linux Mint GRUB 菜单启动安装][12]
|
||||
|
||||
* 片刻之后，您应该会看到 Linux Mint Live 桌面。在桌面上，您应该会看到一个安装 Linux Mint 的图标以启动安装。
|
||||
* 在下一组屏幕中，选择您的语言、键盘布局、选择安装多媒体编解码器并点击继续按钮。
|
||||
* 在安装类型窗口中，选择其他选项。
|
||||
* 在下一个窗口（图 11）中，仔细选择以下内容：
|
||||
* 在设备下，选择刚刚创建的分区；您可以通过我之前提到的要记下的尺寸来识别它。
|
||||
* 然后点击更改，在编辑分区窗口中，选择Ext4作为文件系统，选择格式化分区选项和挂载点为“/”。
|
||||
* 单击确定，然后为您的系统选择引导加载程序；理想情况下，它应该是下拉列表中的第一个条目。
|
||||
* 仔细检查更改。因为一旦您点击立即安装，您的磁盘将被格式化，并且无法恢复。当您认为一切准备就绪，请单击立即安装。
|
||||
|
||||
![图11：选择Windows 11安装Linux Mint的目标分区][13]
|
||||
|
||||
在以下屏幕中，选择您的位置，输入您的姓名并创建用于登录系统的用户 ID 和密码。安装应该开始（图 12）。
|
||||
|
||||
安装完成后（图 13），取出 U 盘并重新启动系统。
|
||||
|
||||
![图12：安装中][14]
|
||||
|
||||
![图13：安装完成][15]
|
||||
|
||||
如果一切顺利，在成功安装为双引导系统后，您应该会看到带有 Windows 11 和 Linux Mint 的 GRUB。
|
||||
|
||||
现在您可以继续使用 [Linux Mint][16] 并体验快速而出色的 Linux 发行版。
|
||||
|
||||
### 总结
|
||||
|
||||
在本教程中，我向您展示了如何在装有 OEM 的 Windows 的笔记本电脑或台式机中使用 Linux Mint 创建一个简单的双启动系统。这些步骤包括分区、创建可引导 USB、格式化和安装。
|
||||
|
||||
尽管上述说明适用于 Linux Mint 21 Vanessa；但是，它现在应该可以与所有其他出色的 [Linux 发行版][17] 一起正常工作。
|
||||
|
||||
如果您遵循本指南，请在下面的评论框中告诉我您的安装情况。
|
||||
|
||||
如果您成功了，欢迎来到自由！
|
||||
|
||||
[下一篇：如何在 Ubuntu 22.04、22.10、Linux Mint 21 中安装 Java 17][18]
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://www.debugpoint.com/linux-mint-install-windows/
|
||||
|
||||
作者：[Arindam][a]
|
||||
选题：[lkxed][b]
|
||||
译者：[gpchn](https://github.com/gpchn)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
||||
[a]: https://www.debugpoint.com/author/admin1/
|
||||
[b]: https://github.com/lkxed
|
||||
[1]: https://www.linuxmint.com/download.php
|
||||
[2]: https://www.debugpoint.com/wp-content/uploads/2022/09/Download-Linux-Mint-from-the-official-website.jpg
|
||||
[3]: https://www.debugpoint.com/etcher-bootable-usb-linux/
|
||||
[4]: https://www.debugpoint.com/wp-content/uploads/2022/09/Disable-BitLocker-in-Windows-Drives-to-install-Linux.jpg
|
||||
[5]: https://www.debugpoint.com/wp-content/uploads/2022/09/Example-of-Shrink-Volume-option-in-Disk-Partition-1024x453.jpg
|
||||
[6]: https://www.debugpoint.com/wp-content/uploads/2022/09/Enter-the-size-of-your-Linux-Partition.jpg
|
||||
[7]: https://www.debugpoint.com/wp-content/uploads/2022/09/Unallocated-space-is-created.jpg
|
||||
[8]: https://www.debugpoint.com/wp-content/uploads/2022/09/New-Simple-Volume-Wizard-page1.jpg
|
||||
[9]: https://www.debugpoint.com/wp-content/uploads/2022/09/New-Simple-Volume-Wizard-page2.jpg
|
||||
[10]: https://www.debugpoint.com/wp-content/uploads/2022/09/New-Simple-Volume-Wizard-page3.jpg
|
||||
[11]: https://www.debugpoint.com/wp-content/uploads/2022/09/Final-partition-for-installing-Linux.jpg
|
||||
[12]: https://www.debugpoint.com/wp-content/uploads/2022/09/Linux-Mint-GRUB-Menu-to-kick-off-installation.jpg
|
||||
[13]: https://www.debugpoint.com/wp-content/uploads/2022/09/Choose-the-target-partition-to-install-Linux-Mint-with-Windows-11.jpg
|
||||
[14]: https://www.debugpoint.com/wp-content/uploads/2022/09/Installation-is-in-progress.jpg
|
||||
[15]: https://www.debugpoint.com/wp-content/uploads/2022/09/Installation-is-complete.jpg
|
||||
[16]: https://www.debugpoint.com/linux-mint
|
||||
[17]: https://www.debugpoint.com/category/distributions
|
||||
[18]: https://www.debugpoint.com/install-java-17-ubuntu-mint/
|
||||
180
translated/tech/20220920 3 ways to use the Linux inxi command.md
Normal file
180
translated/tech/20220920 3 ways to use the Linux inxi command.md
Normal file
@ -0,0 +1,180 @@
|
||||
[#]: subject: "3 ways to use the Linux inxi command"
|
||||
[#]: via: "https://opensource.com/article/22/9/linux-inxi-command"
|
||||
[#]: author: "Don Watkins https://opensource.com/users/don-watkins"
|
||||
[#]: collector: "lkxed"
|
||||
[#]: translator: "geekpi"
|
||||
[#]: reviewer: " "
|
||||
[#]: publisher: " "
|
||||
[#]: url: " "
|
||||
|
||||
Linux inxi 命令的 3 种使用方法
|
||||
======
|
||||
我在 Linux 上使用 inxi 来检查我的笔记本电脑电池、CPU 信息，甚至天气。
|
||||
|
||||
![Coding on a computer][1]
|
||||
|
||||
当我在查询有关笔记本电脑电池健康状况的信息时，我偶然发现了 `inxi`。它是一个命令行系统信息工具，可提供有关你的 Linux 计算机（无论是笔记本电脑、台式机还是服务器）的大量信息。
|
||||
|
||||
`inxi` 命令使用 GPLv3 [许可][2]，许多 Linux 发行版都包含它。根据它的 Git 存储库：“inxi 努力支持最广泛的操作系统和硬件，从最简单的消费台式机到最先进的专业硬件和服务器。”
|
||||
|
||||
文档很完善，并且该项目在线维护了完整的[手册页][3]。安装后，你可以使用 `man inxi` 命令访问系统上的手册页。
|
||||
|
||||
### 在 Linux 上安装 inxi
|
||||
|
||||
通常，你可以从发行版的软件仓库或应用中心安装 `inxi`。例如，在 Fedora、CentOS、Mageia 或类似发行版上：
|
||||
|
||||
```
|
||||
$ sudo dnf install inxi
|
||||
```
|
||||
|
||||
在 Debian、Elementary、Linux Mint 或类似发行版上：
|
||||
|
||||
```
|
||||
$ sudo apt install inxi
|
||||
```
|
||||
|
||||
你可以在[此处][4]找到有关 Linux 发行版安装选项的更多信息。
|
||||
|
||||
### 在 Linux 上使用 inxi 的 3 种方法
|
||||
|
||||
当你安装了 `inxi`，你可以探索它的所有选项。有许多选项可帮助你了解有关系统的更多信息。最基本的命令提供了系统的基本概览：
|
||||
|
||||
```
|
||||
$ inxi -b
|
||||
System:
|
||||
Host: pop-os Kernel: 5.19.0-76051900-generic x86_64 bits: 64
|
||||
Desktop: GNOME 42.3.1 Distro: Pop!_OS 22.04 LTS
|
||||
Machine:
|
||||
Type: Laptop System: HP product: Dev One Notebook PC v: N/A
|
||||
serial: <superuser required>
|
||||
Mobo: HP model: 8A78 v: KBC Version 01.03 serial: <superuser required>
|
||||
UEFI: Insyde v: F.05 date: 06/14/2022
|
||||
Battery:
|
||||
ID-1: BATT charge: 50.6 Wh (96.9%) condition: 52.2/53.2 Wh (98.0%)
|
||||
CPU:
|
||||
Info: 8-core AMD Ryzen 7 PRO 5850U with Radeon Graphics [MT MCP]
|
||||
speed (MHz): avg: 915 min/max: 400/4507
|
||||
Graphics:
|
||||
Device-1: AMD Cezanne driver: amdgpu v: kernel
|
||||
Device-2: Quanta HP HD Camera type: USB driver: uvcvideo
|
||||
Display: x11 server: X.Org v: 1.21.1.3 driver: X: loaded: amdgpu,ati
|
||||
unloaded: fbdev,modesetting,radeon,vesa gpu: amdgpu
|
||||
resolution: 1920x1080~60Hz
|
||||
OpenGL:
|
||||
renderer: AMD RENOIR (LLVM 13.0.1 DRM 3.47 5.19.0-76051900-generic)
|
||||
v: 4.6 Mesa 22.0.5
|
||||
Network:
|
||||
Device-1: Realtek RTL8822CE 802.11ac PCIe Wireless Network Adapter
|
||||
driver: rtw_8822ce
|
||||
Drives:
|
||||
Local Storage: total: 953.87 GiB used: 75.44 GiB (7.9%)
|
||||
Info:
|
||||
Processes: 347 Uptime: 15m Memory: 14.96 GiB used: 2.91 GiB (19.4%)
|
||||
Shell: Bash inxi: 3.3.13
|
||||
```
|
||||
|
||||
### 1. 显示电池状态
|
||||
|
||||
你可以使用 `-B` 选项检查电池健康状况。结果显示系统电池 ID、充电情况和其他信息：
|
||||
|
||||
```
|
||||
$ inxi -B
|
||||
Battery:
|
||||
ID-1: BATT charge: 44.3 Wh (85.2%) condition: 52.0/53.2 Wh (97.7%)
|
||||
```
|
||||
|
||||
### 2. 显示 CPU 信息
|
||||
|
||||
使用 `-C` 选项了解有关 CPU 的更多信息：
|
||||
|
||||
```
|
||||
$ inxi -C
|
||||
CPU:
|
||||
Info: 8-core model: AMD Ryzen 7 PRO 5850U with Radeon Graphics bits: 64
|
||||
type: MT MCP cache: L2: 4 MiB
|
||||
Speed (MHz): avg: 400 min/max: 400/4507 cores: 1: 400 2: 400 3: 400
|
||||
4: 400 5: 400 6: 400 7: 400 8: 400 9: 400 10: 400 11: 400 12: 400 13: 400
|
||||
14: 400 15: 400 16: 400
|
||||
```
|
||||
|
||||
`inxi` 的输出默认使用彩色文本。你可以根据需要使用“颜色开关”进行更改以提高可读性。
|
||||
|
||||
命令选项是 `-c` 后跟 0 到 42 之间的任意数字以适合你的习惯。
|
||||
|
||||
```
|
||||
$ inxi -c 42
|
||||
```
|
||||
|
||||
以下是使用颜色 5 和 7 的几个不同选项的示例：
|
||||
|
||||
![inxi -c 5 command][5]
|
||||
|
||||
该软件可以使用 Linux 系统中的传感器显示硬件温度、风扇速度和有关系统的其他信息。输入 `inxi -s` 并读取以下结果：
|
||||
|
||||
![inxi -s][6]
|
||||
|
||||
### 3. 组合选项
|
||||
|
||||
如果支持，你可以组合 `inxi` 的选项以获得复杂的输出。例如，`inxi -S` 提供系统信息，`-v` 提供详细输出。将两者结合起来可以得到以下结果：
|
||||
|
||||
```
|
||||
$ inxi -S
|
||||
System:
|
||||
Host: pop-os Kernel: 5.19.0-76051900-generic x86_64 bits: 64
|
||||
Desktop: GNOME 42.3.1 Distro: Pop!_OS 22.04 LTS
|
||||
|
||||
$ inxi -Sv
|
||||
CPU: 8-core AMD Ryzen 7 PRO 5850U with Radeon Graphics (-MT MCP-)
|
||||
speed/min/max: 634/400/4507 MHz Kernel: 5.19.0-76051900-generic x86_64
|
||||
Up: 20m Mem: 3084.2/15318.5 MiB (20.1%) Storage: 953.87 GiB (7.9% used)
|
||||
Procs: 346 Shell: Bash inxi: 3.3.13
|
||||
```
|
||||
|
||||
### 额外功能：查看天气
|
||||
|
||||
`inxi` 可以收集到的信息并不只有你的电脑。使用 `-w` 选项，你还可以获取你所在地区的天气信息：
|
||||
|
||||
```
|
||||
$ inxi -w
|
||||
Weather:
|
||||
Report: temperature: 14 C (57 F) conditions: Clear sky
|
||||
Locale: Wellington, G2, NZL
|
||||
current time: Tue 30 Aug 2022 16:28:14 (Pacific/Auckland)
|
||||
Source: WeatherBit.io
|
||||
```
|
||||
|
||||
你可以通过指定你想要的城市和国家以及 `-W` 来获取世界其他地区的天气信息：
|
||||
|
||||
```
|
||||
$ inxi -W rome,italy
|
||||
Weather:
|
||||
Report: temperature: 20 C (68 F) conditions: Clear sky
|
||||
Locale: Rome, Italy current time: Tue 30 Aug 2022 06:29:52
|
||||
Source: WeatherBit.io
|
||||
```
|
||||
|
||||
### 总结
|
||||
|
||||
有许多很棒的工具可以收集有关你的计算机的信息。 我根据机器、桌面或我的心情使用不同的。 你最喜欢的系统信息工具是什么？
|
||||
|
||||
图片来源：（Don Watkins，CC BY-SA 4.0）
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://opensource.com/article/22/9/linux-inxi-command
|
||||
|
||||
作者：[Don Watkins][a]
|
||||
选题：[lkxed][b]
|
||||
译者：[geekpi](https://github.com/geekpi)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
||||
[a]: https://opensource.com/users/don-watkins
|
||||
[b]: https://github.com/lkxed
|
||||
[1]: https://opensource.com/sites/default/files/lead-images/code_computer_laptop_hack_work.png
|
||||
[2]: https://github.com/smxi/inxi/blob/master/LICENSE.txt
|
||||
[3]: https://smxi.org/docs/inxi-man.htm
|
||||
[4]: https://smxi.org/docs/inxi-installation.htm#inxi-repo-install
|
||||
[5]: https://opensource.com/sites/default/files/2022-09/inxi-c5.png
|
||||
[6]: https://opensource.com/sites/default/files/2022-09/inxi-s.png
|
||||
Loading…
Reference in New Issue
Block a user