mirror of
https://github.com/LCTT/TranslateProject.git
synced 2025-03-21 02:10:11 +08:00
Merge branch 'LCTT:master' into master
This commit is contained in:
六开箱
GitHub
commit
4b8fdde8fd
@ -3,43 +3,44 @@
|
||||
[#]: author: "Arindam https://www.debugpoint.com/author/admin1/"
|
||||
[#]: collector: "lujun9972"
|
||||
[#]: translator: "hwlife"
|
||||
[#]: reviewer: " "
|
||||
[#]: publisher: " "
|
||||
[#]: url: " "
|
||||
[#]: reviewer: "wxy"
|
||||
[#]: publisher: "wxy"
|
||||
[#]: url: "https://linux.cn/article-14444-1.html"
|
||||
|
||||
用archinstall自动化脚本安装Arch Linux [完全指南]
|
||||
用 archinstall 自动化脚本安装 Arch Linux
|
||||
======
|
||||
在这篇指南中，我们解释了使用自动化脚本 archinstall 安装 ArchLinux 的超级容易的方法。
|
||||
适合初学者到高级用户。
|
||||
|
||||
对许多新用户来说，安装 ArchLinux 仍然是一件头疼的事情。它需要命令行，Linux系统的内部工作机制包括启动引导过程，内核和 Grub 概念等大量的知识。对许多人来说并不知道这些知识。但是新用户仍然想要安装和体验 ArchLinux 。
|
||||
|
||||
|
||||
我个人感觉在计算机年代，操作系统的安装应该是简单的事情。对于最终用户安装系统应该尽可能的简单。毕竟，所有操作系统的存在只有一个目的 － 帮助最终用户执行某些任务并协助他们。
|
||||
> 在这篇指南中，我们解释了使用自动化脚本 `archinstall` 安装 Arch Linux 的超级容易的方法。适合初学者到高级用户。
|
||||
|
||||
对许多新用户来说，安装 Arch Linux 仍然是一件头疼的事情。它需要命令行，以及包括启动引导过程、内核和 Grub 概念在内的 Linux 系统的内部工作机制等大量的知识。对许多人来说并不知道这些知识。但是新用户仍然想要安装和体验 Arch Linux 。
|
||||
|
||||
我个人感觉在计算机年代，操作系统的安装应该是简单的事情。对于最终用户安装系统应该尽可能的简单。毕竟，所有操作系统的存在只有一个目的 —— 帮助最终用户执行某些任务并协助他们。
|
||||
|
||||
### archinstall 自动化脚本是什么？
|
||||
|
||||
也就是说，不久前我们讨论过在裸机上安装 ArchLinux 。从那以后，ArchLinux团队想出了一个叫做 [archinstall][1] 自动化和交互脚本。如今用这个脚本安装 ArchLinux 是一件容易的事情，任何人都能够完成。
|
||||
话说，不久前我们讨论过在裸机上安装 Arch Linux。从那以后，Arch Linux 团队弄出来了一个叫做 [archinstall][1] 自动化和交互脚本。如今用这个脚本安装 Arch Linux 是一件容易的事情，任何人都能够完成。
|
||||
|
||||
这就导致我们使用这个叫做 archinstall 的自动化脚本，于是就有了 ArchLinux 安装指南的打算。
|
||||
这就让我们有了使用这个叫做 `archinstall` 的自动化脚本撰写这篇 Arch Linux 安装指南的打算。
|
||||
|
||||
让我们开始吧。
|
||||
|
||||
### 使用 archinstall 脚本安装 Arch Linux 的指南
|
||||
|
||||
我将这个指南分为三个部分。第一部分是下载 Arch Linux的 .ISO 文件，创建一个磁盘引导分区。第二部分是实际安装，最后是用一个实例桌面来最终配置。
|
||||
|
||||
我将这个指南分为三个部分。第一部分是下载 Arch Linux 的 .ISO 文件，创建一个磁盘引导分区。第二部分是实际安装，最后是用一个示例桌面来完成配置。
|
||||
|
||||
#### 第一部分：下载 .ISO 文件
|
||||
|
||||
访问以下链接。下载 Arch Linux 的 .ISO 文件。你能够用一个直接的 HTTP 地址下载或者使用种子/磁力链接下载文件。
|
||||
|
||||
[Download Arch Linux][2]
|
||||
> [下载 Arch Linux][2]
|
||||
|
||||
一旦下载完成，用 [Etcher][3] 或者其他的工具创建一个可启动的U盘。
|
||||
一旦下载完成，用 [Etcher][3] 或者其他的工具创建一个可启动的 U 盘。
|
||||
|
||||
完成以后，插入U盘并且重启计算机。
|
||||
完成以后，插入 U 盘并且重启计算机。
|
||||
|
||||
你开始下一部分之前，确定你连接了互联网。一般来说，如果你是有线网，那就很好。如果你在 Arch 就要通过命令行 – [遵从本指南][4] 配置 Wi-Fi。只要确保你已经连接到互联网就行。
|
||||
你开始下一部分之前，确定你连接了互联网。一般来说，如果你是有线网，那就很好。如果你在 Arch 就要通过命令行配置 Wi-Fi，请 [遵从此指南][4]。只要确保你已经连接到互联网就行。
|
||||
|
||||
#### 第二部分：使用 archinstall 安装
|
||||
|
||||
@ -47,75 +48,64 @@
|
||||
|
||||
![First prompt for archinstall][5]
|
||||
|
||||
这个命令将会验证网络连接是否连接到 Arch Linxu 的镜像。一旦完成，一系列问题(像这样)将会弹出。你需要做的将是阅读和回复。
|
||||
这个命令将会验证网络连接是否连接到 Arch Linux 的镜像站点。一旦完成，就会弹出一系列（像这样的）问题。你需要做的将是阅读和回复。
|
||||
|
||||
所以，对这个指南来说，我给出了让你开始的最基础和最容易的一种方法。如果你足够自信，你也可以尝试其他选择。但是我建议遵循以下概述的基本选择，下次你在尝试其他的选择。
|
||||
|
||||
够公平吧？OK。
|
||||
|
||||
因此，第一个问题是键盘布局类型。通过两个字节国家特定布局代码来显示。你也可以键入它们或者输入它们边上的数字。对于美国-英语来说，我键入 us 。
|
||||
因此，第一个问题是键盘布局类型。通过两个字节国家特定布局代码来显示。你也可以键入它们或者输入它们边上的数字。对于美国-英语来说，我键入 `us` 。
|
||||
|
||||
![Keyboard Type – archinstall][6]
|
||||
|
||||
下一步是键盘语言，我键入数字 65 选择美国。
|
||||
|
||||
下一步是键盘语言，我键入数字 `65` 选择美国。
|
||||
|
||||
![Keyboard Language – archinstall][7]
|
||||
|
||||
下一个是硬盘驱动器部分。这个脚本自动探测你的目标系统的可用驱动器。举个例子，在以下图片中，它显示 17GB /dev/vda 是一个主要的块设备。这就是我要安装系统的地方。不要跳过这个步骤。
|
||||
下一个是硬盘驱动器部分。这个脚本自动探测你的目标系统的可用驱动器。举个例子，在以下图片中，它显示 17GB `/dev/vda` 是一个主要的块设备。这就是我要安装系统的地方。不要跳过这个步骤。
|
||||
|
||||
[][8]
|
||||
在这个指南中，我键入数字 `2` 选中 `/dev/vda` 块设备。请根据你们每人的系统键入相应的数字。
|
||||
|
||||
另见 ：怎样在 Arch Linux上安装 Cinnamon 桌面
|
||||
|
||||
在这个指南中，我键入数字 2 选中 /dev/vda 块设备。然后，根据你们每人的系统键入相应的数字。
|
||||
|
||||
一旦你做完这步，你应该在设置这个设备的边上看到一个双箭头 >> 。如果你已经选中它，按下回车键进入下一步。
|
||||
一旦你做完这步，你应该在设置这个设备的边上看到一个双箭头 `>>`。如果你已经选中它，按下回车键进入下一步。
|
||||
|
||||
![Choose Block Device -1][9]
|
||||
|
||||
![Choose Block Device -2][10]
|
||||
|
||||
在下一个选项中，你要小心。这个脚本问是否你想清除设备然后进行自动分区。否则你要手动分区硬盘驱动器。为了简单起见，我选择 0 选项。
|
||||
在下一个选项中，你要非常小心。这个脚本问是否你想清除设备然后进行自动分区。否则你要手动分区硬盘驱动器。为了简单起见，我选择选项 `0`。
|
||||
|
||||
![Select partition option – archinstall][11]
|
||||
|
||||
在下组问题中，如下图所示。更多的是文件系统类型，主机名，根用户密码，等等。按照屏幕上的操作。便于帮助你，我已经在下表中加入了用于本指南的问题和答案。
|
||||
|
||||
在下面一组问题中，如下图所示。更多的是文件系统类型、主机名、root 用户密码，等等。按照屏幕上的操作。便于帮助你，我已经在下表中加入了用于本指南的问题和答案。
|
||||
|
||||
问题 | 选项
|
||||
---|---
|
||||
问题 | 选项
|
||||
选择主要的文件系统 | ext4
|
||||
你想用 zram 作为交换分区吗？| n
|
||||
键入磁盘加密密码 |保留为空直接按下回车
|
||||
选择主要的文件系统 | `ext4`
|
||||
你想用 zram 作为交换分区吗？| `n`
|
||||
键入磁盘加密密码 | 保留为空直接按下回车
|
||||
主机名或计算机名 | 键入你要键入的名字
|
||||
键入根密码 | 键入你要键入的密码
|
||||
键入程序预配置文件名 –
|
||||
0 – 桌面
|
||||
1 – 最小化
|
||||
2 – 服务器
|
||||
3 – xorg | 选择 3 – xorg
|
||||
键入 root 密码 | 键入你要键入的密码
|
||||
键入程序预配置文件名：0 – 桌面；1 – 最小化；2 – 服务器；3 – xorg | 选择 `3` xorg
|
||||
安装显卡驱动 | 根据你的系统选择数字。否则缺省不选按下回车键
|
||||
安装声卡驱动| 选择 pulseaudio
|
||||
安装声卡驱动 | 选择 `pulseaudio`
|
||||
|
||||
![Various options in archinstall -1][12]
|
||||
|
||||
在选择内核，选择linux的下个问题里。这个脚本将要为你安装你额外添加的软件包 - 像 firefox ，nano ，等等。
|
||||
在选择内核的下个问题里，选择 `linux`。这个脚本将要为你安装你额外添加的软件包，像 firefox、nano ，等等。
|
||||
|
||||
用 NetworkManager 选择网络接口，并且为时区选择缺省选项。
|
||||
用 NetworkManager 选择网络接口，并且为时区选择缺省选项。
|
||||
|
||||
![Various options in archinstall -2][13]
|
||||
|
||||
就是这样。一旦你已经完成上述步骤，这个脚本将会生成并且等待你按下回车开始安装过程。
|
||||
就是这样。一旦你已经完成上述步骤，这个脚本将会生成，并且等待你按下回车开始安装过程。
|
||||
|
||||
![archinstall starts downloading packages][14]
|
||||
|
||||
等待直到步骤完成。这将花一些时间下载安装所有软件包，这依赖你的系统和网络连接速度。有时 Arch 镜像是慢的，所以等待直到它完成。
|
||||
等待直到这一步骤完成。这将花一些时间下载安装所有软件包，这依赖你的系统和网络连接速度。有时 Arch 镜像是缓慢的，所以等待直到它完成。
|
||||
|
||||
#### 第三部分 - 安装桌面环境
|
||||
|
||||
当你用以上方法安装完基本系统以后，你可以安装像 GNOME，KDE Plasma，MATE，Xfce 等额外的桌面环境。我们在以下页面中为它们每个都提供了安装指南。你可以访问你选择的桌面环境安装页面并且直接跳到这些页面底部提取安装桌面环境的命令。
|
||||
当你用以上方法安装完基本系统以后，你可以安装像 GNOME、KDE Plasma、MATE、Xfce 等额外的桌面环境。我们在以下页面中为它们每个都提供了安装指南。你可以访问你选择的桌面环境安装页面，并且直接跳到这些页面底部提取安装桌面环境的命令。
|
||||
|
||||
* [Xfce][15]
|
||||
* [GNOME][16]
|
||||
@ -123,44 +113,30 @@
|
||||
* [Cinnamon][8]
|
||||
* [LXQt][18]
|
||||
|
||||
|
||||
举个例子，如果你想要安装 GNOME 桌面基本套件，你可以简单的运行以下命令来安装。
|
||||
|
||||
|
||||
```
|
||||
|
||||
sudo pacman -S --needed gnome gnome-tweaks nautilus-sendto gnome-nettool gnome-usage gnome multi-writer adwaita-icon-theme chrome-gnome-shell xdg-user-dirs-gtk fwupd arc-gtk-theme seahosrse gdm firefox gedit
|
||||
|
||||
sudo pacman -S --needed gnome gnome-tweaks nautilus-sendto gnome-nettool gnome-usage gnome multi-writer adwaita-icon-theme chrome-gnome-shell xdg-user-dirs-gtk fwupd arc-gtk-theme seahosrse gdm firefox gedit
|
||||
```
|
||||
|
||||
```
|
||||
|
||||
systemctl enable gdm
|
||||
|
||||
systemctl enable gdm
|
||||
```
|
||||
|
||||
```
|
||||
|
||||
systemctl enable NetworkManager
|
||||
|
||||
systemctl enable NetworkManager
|
||||
```
|
||||
|
||||
一旦你完成了以上这些，键入 reboot 重启。
|
||||
一旦你完成了以上这些，键入 `reboot` 重启。
|
||||
|
||||
恭喜你。你已经使用这个指南和厉害的 archinstall 脚本安装完成了 Arch Linux。
|
||||
恭喜你。你已经使用这个指南通过厉害的 `archinstall` 脚本安装完成了 Arch Linux。
|
||||
|
||||
### 结语
|
||||
|
||||
我相信，这是团队开发的令人印象深刻的脚本之一。并且确实增加了使用 Arch Linux 的用户基数和覆盖范围。
|
||||
我相信，这是由该团队开发的令人印象深刻的脚本之一。并且确实增加了使用 Arch Linux 的用户基数和覆盖范围。
|
||||
|
||||
使用这个脚本有什么问题吗？在下方评论让我知道。
|
||||
|
||||
* * *
|
||||
|
||||
我们带来了最新的技术，软件新闻和重大事件。可以通过 [Telegram][19], [Twitter][20], [YouTube][21], 和 [Facebook][22] 与我们保持联系，不要错过一个更新！
|
||||
|
||||
##### 也要读
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://www.debugpoint.com/2022/01/archinstall-guide/
|
||||
@ -168,7 +144,7 @@ via: https://www.debugpoint.com/2022/01/archinstall-guide/
|
||||
作者：[Arindam][a]
|
||||
选题：[lujun9972][b]
|
||||
译者：[hwlife](https://github.com/hwlife)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
校对：[wxy](https://github.com/wxy)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
||||
@ -0,0 +1,117 @@
|
||||
[#]: subject: "Nautilus File Manager Looks Amazing with GTK4 and Libadwaita – A Deep Dive"
|
||||
[#]: via: "https://www.debugpoint.com/2022/03/gnome-files-43/"
|
||||
[#]: author: "Arindam https://www.debugpoint.com/author/admin1/"
|
||||
[#]: collector: "lujun9972"
|
||||
[#]: translator: "geekpi"
|
||||
[#]: reviewer: "wxy"
|
||||
[#]: publisher: "wxy"
|
||||
[#]: url: "https://linux.cn/article-14442-1.html"
|
||||
|
||||
GTK4 和 Libadwaita 让 GNOME 43 的文件管理器看起来很出色
|
||||
======
|
||||
|
||||
|
||||
|
||||
> 我们测试了 GNOME “<ruby>文件<rt>Files</rt></ruby>” v43 的开发版本，在这里将向你深入披露其外观、功能和性能的细节。
|
||||
|
||||
GNOME <ruby>文件<rt>Files</rt></ruby>（以前的 Nautilus）也许是当今 GNOME 生态空间中使用最多的桌面应用。而且，自其首次发布以来，它从未接受过什么大修，而其他的 GNOME 应用乃至桌面本身都转移到了一个较新的技术栈。
|
||||
|
||||
现在一切都变了。GNOME 开发者正在为整个桌面和 “文件” 采用 GTK4 和 libadwaita。
|
||||
|
||||
GNOME “文件” v43 将在 2022 年晚些时候与 GNOME 43 一起发布，必将令人印象深刻。这个急需的 [重制][1] 带来了原生的深色模式、很棒的 UI 以及出色的 libadwaita 触控和 GTK4 性能提升。
|
||||
|
||||
### GNOME “文件” v43
|
||||
|
||||
我们安装了 GNOME “文件” v43 的 Flatpak 开发版本，下面是我们的发现。
|
||||
|
||||
第一印象，你应该注意到漂亮的 UI 触控，这要感谢 Libadwaita。关闭按钮是漂亮的圆形，而地址栏、选择高亮和整个文件窗口都有适当的间距和圆角。
|
||||
|
||||
所有的组件都没有出现边框高亮线。
|
||||
|
||||
下面是 v43（左）和 v42（右）的深浅模式的快速比较。
|
||||
|
||||
![GNOME Files 43 and 42 – Light Mode Comparison][2]
|
||||
|
||||
![GNOME Files 43 and 42 – Dark Mode Comparison][3]
|
||||
|
||||
地址栏的文件夹分隔符保持不变。然而，字体却有了些许润色。地址栏的上下文菜单改变了，“<ruby>在终端打开<rt>Open in Terminal</rt></ruby>”选项没有了。取而代之的是 “<ruby>在其它应用中打开<rt>Open in Other application</rt></ruby>” 菜单。引入了一个新的选项 “<ruby>创建链接<rt>Create Link</rt></ruby>”。我想许多用户会怀念 “在终端打开” 的选项。
|
||||
|
||||
> 3/3 更新（感谢 Rashid）：“在终端打开” 选项是 Nautilus 扩展包的一部分。因此，Flatpak 构建版不能“看到”它。因此，它本身并没有被删除。
|
||||
|
||||
![New option in address bar menu][4]
|
||||
|
||||
另一个重要的变化是你应该注意到两个主工具条菜单：a）视图按钮和 b）汉堡主菜单。这些上下文菜单项显示了菜单项及键盘快捷键。这也使它们看起来更显眼一些。
|
||||
|
||||
![The Hamburger menu now have keyboard shortcuts][5]
|
||||
|
||||
文件夹的上下文菜单现在有一个向上的小箭头，指向从它弹出的文件夹。文件夹的右键上下文菜单以组为单位组织得很好。例如，打开动作是分组的，而剪切、复制、粘贴在上下文菜单中以横杠的形式明显分开。
|
||||
|
||||
![Context Menu for folder changes][6]
|
||||
|
||||
我还注意到一个新的选项 “<ruby>粘贴到该文件夹<rt>Paste into the folder</rt></ruby>”，这个很好。
|
||||
|
||||
Nautilus 搜索几乎与 “文件” v42 相同，只是在 “文件” v43 中你可以通过创建日期/时间搜索。
|
||||
|
||||
~~然而，我注意到一个令人兴奋的变化。上下文菜单中的文件关联的应用名称被删除了。例如，如果你今天试图在 “文件” v42 中打开一个文本文件，它在上下文菜单中显示与之相关的应用名称。在 “文件” v43 中，它只显示 “打开”。我觉得这种改变是不必要的。之前的情况更好。~~
|
||||
|
||||
> 3/3 更新（感谢 Rashid）：当我在试用 v43 的沙盒 Flatpak 版本时，它并没有看到系统关联。所以，这不是一个变化。但是，我又想知道，如果有人试图真正使用 Flatpak 版本怎么办。
|
||||
|
||||
![A subtle change in context menu for file association][7]
|
||||
|
||||
所以，这就是我在这个应用的新 GTK4 版本中发现的整体变化。但它看起来不错？不是吗。此外，如果你是直接从 Ubuntu 20.04 LTS 来的，其中包含 “文件” 3.38，那么也许你的体验会是“哇”！如果你将 “文件” v43 与 “文件” v3.38 进行比较，大部分区域都发生了变化。对于这些用户来说，这将是一个相当不错的体验。
|
||||
|
||||
你应该记住，v43 仍在开发中，因此在未来最终发布时，可能会发生变化。
|
||||
|
||||
### 愿望清单
|
||||
|
||||
如果比较各种 Linux 文件管理器，其他的文件管理器的选项远多于今天的 GNOME “文件”。
|
||||
|
||||
是这样的。
|
||||
|
||||
例如，Nemo 或 Dolphin - 这两个最好的文件管理器在各方面都胜过 “文件”。比较一下功能，GNOME “文件” 没有一些流行的功能：
|
||||
|
||||
* 双面板或分割视图
|
||||
* 从上下文菜单中打开一个根文件夹是困难的
|
||||
* 一个用于文件夹浏览的向上箭头
|
||||
* 没有从上下文菜单中创建一个新文件（文本、电子表格等）的选项
|
||||
* 更多的排序和搜索功能
|
||||
|
||||
我们希望这些功能能尽快出现在 GNOME “文件” 中。
|
||||
|
||||
### 何时能用
|
||||
|
||||
如上所述，这个版本的 GNOME “文件” 将与 GNOME 43 一起提供。因此，从 Linux 发行计划的角度来看，你应该在 2022 年 10 月的 Ubuntu 22.10 和今年晚些时候的 Fedora 37 上拥有它。
|
||||
|
||||
不幸的是，[Ubuntu 22.04 LTS][9]（Jammy Jellyfish）和带有 [GNOME 42][10] 的 [Fedora 36][11] 将不会有 GNOME “文件” 43。主要原因是时间表不匹配，而且它是要移植到 GTK4 和彻底测试的复杂应用之一。然而，大部分上述的内部功能仍然会在 “文件” 42 中。但它可能缺少漂亮的 UI 变化和主题。
|
||||
|
||||
尽管如此，我相信这个流行的文件管理器看起来不错，当它发布时，用户应该会很兴奋地使用它。让我知道你对 GNOME “文件” 43 的新变化的看法，请在下面的评论框中留言。
|
||||
|
||||
加油！
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://www.debugpoint.com/2022/03/gnome-files-43/
|
||||
|
||||
作者：[Arindam][a]
|
||||
选题：[lujun9972][b]
|
||||
译者：[geekpi](https://github.com/geekpi)
|
||||
校对：[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/lujun9972
|
||||
[1]: https://gitlab.gnome.org/GNOME/nautilus
|
||||
[2]: https://www.debugpoint.com/wp-content/uploads/2022/03/GNOME-Files-43-and-42-Light-Mode-Comparison-1024x502.jpg
|
||||
[3]: https://www.debugpoint.com/wp-content/uploads/2022/03/GNOME-Files-43-and-42-Dark-Mode-Comparison-1024x493.jpg
|
||||
[4]: https://www.debugpoint.com/wp-content/uploads/2022/03/New-option-in-address-bar-menu-1024x267.jpg
|
||||
[5]: https://www.debugpoint.com/wp-content/uploads/2022/03/The-Hamburger-menu-now-have-keyboard-shortcuts-1024x331.jpg
|
||||
[6]: https://www.debugpoint.com/wp-content/uploads/2022/03/Context-Menu-for-folder-changes-1024x560.jpg
|
||||
[7]: https://www.debugpoint.com/wp-content/uploads/2022/03/A-subtle-change-in-context-menu-for-file-association-1024x524.jpg
|
||||
[9]: https://www.debugpoint.com/2022/01/ubuntu-22-04-lts/
|
||||
[10]: https://www.debugpoint.com/2021/12/gnome-42/
|
||||
[11]: https://www.debugpoint.com/2022/02/fedora-36/
|
||||
[12]: https://t.me/debugpoint
|
||||
[13]: https://twitter.com/DebugPoint
|
||||
[14]: https://www.youtube.com/c/debugpoint?sub_confirmation=1
|
||||
[15]: https://facebook.com/DebugPoint
|
||||
@ -1,96 +0,0 @@
|
||||
[#]: subject: "Xfce Terminal 1.0.0 is a Feature-Packed Major Upgrade After a Year"
|
||||
[#]: via: "https://news.itsfoss.com/xfce-terminal-1-0-0-release/"
|
||||
[#]: author: "Jacob Crume https://news.itsfoss.com/author/jacob/"
|
||||
[#]: collector: "lujun9972"
|
||||
[#]: translator: "geelpi"
|
||||
[#]: reviewer: " "
|
||||
[#]: publisher: " "
|
||||
[#]: url: " "
|
||||
|
||||
Xfce Terminal 1.0.0 is a Feature-Packed Major Upgrade After a Year
|
||||
======
|
||||
|
||||
The popular terminal emulator found on almost all Xfce-powered distributions, Xfce Terminal has just released its first major upgrade under a new maintainer (and a new versioning scheme).
|
||||
|
||||
Let us take a look at some highlights of the release.
|
||||
|
||||
### New Maintainer & Versioning Scheme
|
||||
|
||||
Igor Zakharov was leading the development from 2016 until 2020. Unfortunately, it was left unmaintained in 2021 when the new maintainer, [Sergios][1] Anestis Kefalidis (also a developer of Thunar file manager), took over the responsibility.
|
||||
|
||||
And, since Sergios took over the project, the versioning scheme has changed. After consultation with the community, Thunar’s old versioning scheme was adopted.
|
||||
|
||||
For instance, version 1.1.x will be the development release, and 1.2.0 will be the next major upgrade.
|
||||
|
||||
Now, with the release of Xfce Terminal 1.0.0, a number of exciting new features have been packed in.
|
||||
|
||||
### New Features
|
||||
|
||||
Some new features in Xfce Terminal 1.0.0 include:
|
||||
|
||||
* Improved customization options
|
||||
* Overlay scrollbar support
|
||||
* Command-line option improvements
|
||||
* More use of XfceTitledDialog
|
||||
|
||||
|
||||
|
||||
#### Better Customization Options
|
||||
|
||||
As with many application updates these days, Xfce Terminal 1.0.0 includes plenty of new customization options. Perhaps my favorite, the image background feature now has a ‘Fill’ style option. This is accompanied by the ability to temporarily disable the unsafe paste dialog, which has also been revamped.
|
||||
|
||||
Finally, XFCE Terminal has also become one of the first apps to support the new XFCE shortcuts editor. As a result, users no longer need to dive into configuration files, instead of being given a simple UI to use.
|
||||
|
||||
![][2]
|
||||
|
||||
With so many new customization options, I’m sure many people would be happy with a release containing just these. But alas! The developer has managed to squeeze in yet more exciting new features, the next of which is the improved command-line arguments.
|
||||
|
||||
#### Better Command Line Arguments
|
||||
|
||||
With this release, ‘–tab’ and ‘–window’ command line arguments have been fixed to be more intuitive. This fixes a rather [longstanding bug][3] in XFCE Terminal that has been known for almost 6 years.
|
||||
|
||||
Despite the long wait, it has now been fixed. Better late than never, eh?
|
||||
|
||||
Anyway, it is always great to see bugs squashed with every new release, and this trend continues here.
|
||||
|
||||
#### More Use Of Xfce-Specific Widgets
|
||||
|
||||
Although I’m sure many users will probably see this as a downgrade, XFCE Terminal’s use of more XFCE-specific widgets brings numerous advantages. While it does mean more dependencies for non-XFCE users, it means better integration with XFCE.
|
||||
|
||||
It is safe to say that most of the Xfce terminal users stick to the same desktop environment. So, this change should result in greater consistency and UX improvements.
|
||||
|
||||
#### Other Changes
|
||||
|
||||
Other changes in this release include:
|
||||
|
||||
* ‘Scrolling on ouput’ preference improvements
|
||||
* Right-click behavior customization options
|
||||
* Code reworking for a smaller codebase
|
||||
|
||||
|
||||
|
||||
For a full list of features, feel free to refer to the [release notes][4]. The release notes also mention future plans for the next major release, v1.2.0.
|
||||
|
||||
### Wrapping Up
|
||||
|
||||
Overall, Xfce Terminal 1.0.0 is looking to be a great release and goes to show the dedication of its new maintainer.
|
||||
|
||||
If you want to try Xfce Terminal 1.0.0, it should be landing in your distribution’s repositories in the following weeks, if not already.
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://news.itsfoss.com/xfce-terminal-1-0-0-release/
|
||||
|
||||
作者：[Jacob Crume][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://news.itsfoss.com/author/jacob/
|
||||
[b]: https://github.com/lujun9972
|
||||
[1]: https://www.youtube.com/channel/UCu8-J-XWcXQhoCopBiJ5-uw/videos
|
||||
[2]: data:image/svg+xml;base64,PHN2ZyBoZWlnaHQ9IjUwOSIgd2lkdGg9Ijc4MCIgeG1sbnM9Imh0dHA6Ly93d3cudzMub3JnLzIwMDAvc3ZnIiB2ZXJzaW9uPSIxLjEiLz4=
|
||||
[3]: https://bugzilla.xfce.org/show_bug.cgi?id=12926
|
||||
[4]: http://users.uoa.gr/~sdi1800073/sources/xfce_blog12.html
|
||||
@ -0,0 +1,101 @@
|
||||
[#]: subject: "Vivaldi 5.2 Adds a Reading List Panel & New Privacy Statistics Bar"
|
||||
[#]: via: "https://news.itsfoss.com/vivaldi-5-2-release/"
|
||||
[#]: author: "Ankush Das https://news.itsfoss.com/author/ankush/"
|
||||
[#]: collector: "lujun9972"
|
||||
[#]: translator: " "
|
||||
[#]: reviewer: " "
|
||||
[#]: publisher: " "
|
||||
[#]: url: " "
|
||||
|
||||
Vivaldi 5.2 Adds a Reading List Panel & New Privacy Statistics Bar
|
||||
======
|
||||
|
||||
Vivaldi has been an excellent choice for users looking to get more out of their browsing experience.
|
||||
|
||||
Even though it isn’t completely FOSS (UI is proprietary, the rest is open-source), it is a viable alternative for Linux users dabbling with multiple tabs and wanting more features in their arsenal.
|
||||
|
||||
In fact, it is [one of the best options for Linux users][1] now.
|
||||
|
||||
Now, Vivaldi 5.2 adds more useful upgrades that can make it a compelling alternative to your current choice of browser.
|
||||
|
||||
### Vivaldi 5.2: What’s New?
|
||||
|
||||
Vivaldi 5.2 steps up the game with a new reading panel, and a separate privacy statistics bar.
|
||||
|
||||
The Android version also received some exciting upgrades, let us take a look at them.
|
||||
|
||||
Here’s more about it:
|
||||
|
||||
#### Reading List Panel
|
||||
|
||||
![][2]
|
||||
|
||||
Vivaldi’s side panel already features loads of options, including email, RSS, calendar, etc.
|
||||
|
||||
Now, the reading list that has been existing in the address bar (save the page to read later) is now available in the side panel.
|
||||
|
||||
With its entry on the side panel, it becomes more accessible than ever. So, you do not need to switch away from your current task, and still be able to check/explore the reading list when you want.
|
||||
|
||||
You can watch the feature in action here:
|
||||
|
||||
![][3]
|
||||
|
||||
You get to manage the list, search and organize it right from the side panel.
|
||||
|
||||
Quick commands can be used to save any page to the reading list. Not to forget, you can also sync your reading list with your mobile (Android) or any other devices connected.
|
||||
|
||||
#### Privacy Statistics Bar
|
||||
|
||||
![][2]
|
||||
|
||||
While Vivaldi already had the built-in protection to block trackers, you did not get to know about them properly.
|
||||
|
||||
With the new statistics bar, you get to see the collective tracking information about all the trackers blocked during your browsing session.
|
||||
|
||||
Most users may not need to bother with it. However, looking at the stats can give you an overview of what tracker is more prevalent and gain insights about them.
|
||||
|
||||
You can also check it out in action here:
|
||||
|
||||
![][4]
|
||||
|
||||
#### Other Improvements
|
||||
|
||||
In addition to the privacy statistics bar, you also have a few new additions like:
|
||||
|
||||
* [Qwant][5] search engine is now available as one of the default search engine selections.
|
||||
* Improved drag/drop of tabs.
|
||||
* Improvements to Vivaldi Mail, Calendar, and the Feed Reader.
|
||||
|
||||
|
||||
|
||||
For more information, you can refer to the [official release announcement][6].
|
||||
|
||||
### Download Vivaldi 5.2
|
||||
|
||||
You can grab the latest release package (deb/rpm) from its official site to install it.
|
||||
|
||||
[Download Vivaldi 5.2][7]
|
||||
|
||||
If you have already [installed Vivaldi on Linux][8] using their repo, you should find it in the software updates soon, if not already.
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://news.itsfoss.com/vivaldi-5-2-release/
|
||||
|
||||
作者：[Ankush Das][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://news.itsfoss.com/author/ankush/
|
||||
[b]: https://github.com/lujun9972
|
||||
[1]: https://itsfoss.com/best-browsers-ubuntu-linux/
|
||||
[2]: data:image/svg+xml;base64,PHN2ZyBoZWlnaHQ9IjU3NiIgd2lkdGg9IjEwMjQiIHhtbG5zPSJodHRwOi8vd3d3LnczLm9yZy8yMDAwL3N2ZyIgdmVyc2lvbj0iMS4xIi8+
|
||||
[3]: https://i.ytimg.com/vi/hhGQUO8u9iQ/hqdefault.jpg
|
||||
[4]: https://i.ytimg.com/vi/MAY5s_MpnxY/hqdefault.jpg
|
||||
[5]: https://www.qwant.com/
|
||||
[6]: https://vivaldi.com/press/vivaldi-adds-a-reading-list-panel-shows-statistics-on-blocked-trackers-and-ads/
|
||||
[7]: https://vivaldi.com/download/
|
||||
[8]: https://itsfoss.com/install-vivaldi-ubuntu-linux/
|
||||
@ -2,7 +2,7 @@
|
||||
[#]: via: "https://www.debugpoint.com/2022/04/end-of-elementary-os/"
|
||||
[#]: author: "Arindam https://www.debugpoint.com/author/admin1/"
|
||||
[#]: collector: "lujun9972"
|
||||
[#]: translator: " "
|
||||
[#]: translator: "hwlife"
|
||||
[#]: reviewer: " "
|
||||
[#]: publisher: " "
|
||||
[#]: url: " "
|
||||
|
||||
@ -0,0 +1,97 @@
|
||||
[#]: subject: "Xubuntu 22.04 LTS – New Features and Release Details"
|
||||
[#]: via: "https://www.debugpoint.com/2022/04/xubuntu-22-04-lts/"
|
||||
[#]: author: "Arindam https://www.debugpoint.com/author/admin1/"
|
||||
[#]: collector: "lujun9972"
|
||||
[#]: translator: " "
|
||||
[#]: reviewer: " "
|
||||
[#]: publisher: " "
|
||||
[#]: url: " "
|
||||
|
||||
Xubuntu 22.04 LTS – New Features and Release Details
|
||||
======
|
||||
A LIST OF NEW FEATURES IN XUBUNTU 22.04 LTS (JAMMY JELLYFISH) AND
|
||||
ADDITIONAL INFORMATION ABOUT THE RELEASE.
|
||||
![Xubuntu 22.04 Desktop][1]
|
||||
|
||||
### Xubuntu 22.04 LTS – New Features
|
||||
|
||||
Xubuntu 22.04 LTS is powered by Linux Kernel 5.15 and underlying packages from Ubuntu 22.04 LTS. In addition to that, the default desktop environment version is Xfce 4.16. The Xfce desktop environment did not see any significant release since its release in Dec 2020.
|
||||
|
||||
Even so the Xfce desktop version 4.16 remained as the Xubuntu 21.10 (last release), and the desktop components and native applications get some improvements and bug fixes.
|
||||
|
||||
Perhaps the vital work in this release is the initial support for GTK4 and libhandy in the Greybird theme (via version 3.23.1). That means the GTK4 apps from the GNOME ecosystem look good in Xubuntu with their theme.
|
||||
|
||||
### Application Updates
|
||||
|
||||
The default file manager Thunar 4.16.10 adds several performance improvements, including regression fixes, translation updates and under the hood changes. Although while scanning the changelog, I could not find anything substantial to report which is visible to the user. But if you are interested, you can read the NEWS file in detail [here][2].
|
||||
|
||||
In fact, Thunar is now under development with Xfce 4.17, which contains some exciting changes. But unfortunately, we all need to wait for that in the short term release because it’s too early to feature those in a long term version.
|
||||
|
||||
Apart from that, Xfce Terminal remains in 0.8.10 in this release. Similar to Thunar, Xfce Terminal 1.0.0 major updates won’t be available in this LTS release.
|
||||
|
||||
[][3]
|
||||
|
||||
SEE ALSO: Pop OS 22.04 LTS - New Features and Release Updates
|
||||
|
||||
Besides these two, other desktop components remain with their last stable version with Xfce Panel 4.16.3, Xfce window manager 4.16.1 and Xfce Desktop 4.16. It is worth mentioning that Xfce is still working on the GTK4 transition, and not much clarity is available on the schedule.
|
||||
|
||||
Furthermore, the native applications see their version bumped to the latest stable iteration. But one significant change is Firefox executable is now a Snap version in Xubuntu 22.04 following Ubuntu. So, ideally, users would not feel any difference but may face some issues with extensions and other utilities due to its sandbox nature.
|
||||
|
||||
In addition to that, Xubuntu 22.04 expects a few nice wallpapers from the community contest, including a default one. The results are pending. However, you can find out some exciting submissions on [this page][4].
|
||||
|
||||
### Summary and Download
|
||||
|
||||
To sum up, major core frameworks, apps and their versions are down below.
|
||||
|
||||
* GNOME 42
|
||||
* GTK 3.24.32
|
||||
* MATE 1.26
|
||||
* Xfce 4.16
|
||||
* Firefox 99
|
||||
* Thunderbird 91.8
|
||||
* Atril Document Viewer 1.26
|
||||
* Engrampa Archive Manager 1.26
|
||||
* Ristretto Image Viewer 0.12.2
|
||||
* LibreOffice 7.3.x
|
||||
* Catfish 4.16.3
|
||||
* Mousepad 0.5.8
|
||||
|
||||
|
||||
|
||||
Finally, to download the BETA version of Xubuntu 22.04, refer to the link below to the ISO file. You can try to install on a virtual machine or try it in a physical system.
|
||||
|
||||
* [xubuntu-22.04-beta-desktop-amd64.iso][5]
|
||||
* [Other download options include torrents, checksums][6]
|
||||
|
||||
|
||||
|
||||
_Via [official changelog][7]_
|
||||
|
||||
* * *
|
||||
|
||||
We bring the latest tech, software news and stuff that matters. Stay in touch via [Telegram][8], [Twitter][9], [YouTube][10], and [Facebook][11] and never miss an update!
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://www.debugpoint.com/2022/04/xubuntu-22-04-lts/
|
||||
|
||||
作者：[Arindam][a]
|
||||
选题：[lujun9972][b]
|
||||
译者：[译者ID](https://github.com/译者ID)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
||||
[a]: https://www.debugpoint.com/author/admin1/
|
||||
[b]: https://github.com/lujun9972
|
||||
[1]: https://www.debugpoint.com/wp-content/uploads/2022/04/Xubuntu-22.04-Desktop-1024x575.jpg
|
||||
[2]: https://archive.xfce.org/src/xfce/thunar/4.16/
|
||||
[3]: https://www.debugpoint.com/2022/04/pop-os-22-04-lts/
|
||||
[4]: https://contest.xubuntu.org/wallpaper_contest/xubuntu-22-04-community-wallpaper-contest/?action=view
|
||||
[5]: https://cdimage.ubuntu.com/xubuntu/releases/22.04/beta/xubuntu-22.04-beta-desktop-amd64.iso
|
||||
[6]: https://cdimage.ubuntu.com/xubuntu/releases/22.04/beta/
|
||||
[7]: https://wiki.xubuntu.org/releases/22.04/release-notes
|
||||
[8]: https://t.me/debugpoint
|
||||
[9]: https://twitter.com/DebugPoint
|
||||
[10]: https://www.youtube.com/c/debugpoint?sub_confirmation=1
|
||||
[11]: https://facebook.com/DebugPoint
|
||||
@ -7,26 +7,25 @@
|
||||
[#]: via: (https://opensource.com/article/20/9/systemd-startup-configuration)
|
||||
[#]: author: (David Both https://opensource.com/users/dboth)
|
||||
|
||||
Analyze Linux startup performance
|
||||
分析 Linux 启动性能
|
||||
======
|
||||
Use systemd-analyze to get insights and solve problems with Linux
|
||||
startup performance.
|
||||
用 systemd-analyze 查看 Linux 启动性能或者解决一些问题
|
||||
|
||||
![Magnifying glass on code][1]
|
||||
|
||||
Part of the system administrator's job is to analyze the performance of systems and to find and resolve problems that cause poor performance and long startup times. Sysadmins also need to check other aspects of systemd configuration and usage.
|
||||
|
||||
The systemd init system provides the `systemd-analyze` tool that can help uncover performance problems and other important systemd information. In a previous article, [_Analyzing systemd calendar and timespans_][2], I used `systemd-analyze` to analyze timestamps and timespans in systemd timers, but this tool has many other uses, some of which I will explore in this article.
|
||||
系统管理员的一部分工作就是分析系统性能，去发现并解决引起性能不佳、长时间启动系统的问题。系统维护者也需要去检查系统配置和使用等。
|
||||
|
||||
### Startup overview
|
||||
systemd 初始化系统提供了 systemd-analyze 工具，帮助查看性能和其他重要的 systemd 信息。在以前的文章 分析 [_systemd 日历和时间间隔_][2] 里，我用了 systemd-analyze 去分析 systemd 里的时间戳和时间间隔，但是这个工具有很多其他用法，这个文章里我再揭示一些。
|
||||
|
||||
The Linux startup sequence is a good place to begin exploring because many `systemd-analyze` tool functions are targeted at startup. But first, it is important to understand the difference between boot and startup. The boot sequence starts with the BIOS power-on self test (POST) and ends when the kernel is finished loading and takes control of the host system, which is the beginning of startup and the point when the systemd journal begins.
|
||||
（译者注： systemd 是目前主流Linux release 采用的系统管理； boot 翻译为启动，startup 翻译为起动）
|
||||
|
||||
In the second article in this series, [_Understanding systemd at startup on Linux_][3], I discuss startup in a bit more detail with respect to what happens and in what sequence. In this article, I want to examine the startup sequence to look at the amount of time it takes to go through startup and which tasks take the most time.
|
||||
|
||||
The results I'll show below are from my primary workstation, which is much more interesting than a virtual machine's results. This workstation consists of an ASUS TUF X299 Mark 2 motherboard, an Intel i9-7960X CPU with 16 cores and 32 CPUs (threads), and 64GB of RAM. Some of the commands below can be run by a non-root user, but I will use root in this article to prevent having to switch between users.
|
||||
|
||||
There are several options for examining the startup sequence. The simplest form of the `systemd-analyze` command displays an overview of the amount of time spent in each of the main sections of startup, the kernel startup, loading and running `initrd` (i.e., initial ramdisk, a temporary system image that is used to initialize some hardware and mount the `/` [root] filesystem), and userspace (where all the programs and daemons required to bring the host up to a usable state are loaded). If no subcommand is passed to the command, `systemd-analyze time` is implied:
|
||||
### 总览
|
||||
|
||||
LINUX 起动顺序是值得学习关注的地方，因为 systemd-analyze 工具很多功能聚焦在起动 startup 过程。但是首先，要理解启动 boot 和起动 startup 。启动从 BIOS 加电自检（POST）开始，装载和控制主机系统结束，然后是起动 startup ，systemd 日志开始。
|
||||
这个系列的第二篇文章， [_理解LINUX起动 systemd_][3]，我讨论了起动 startup 的一点顺序上的细节，文章里，我试图解释起动 startup 顺序时间总进程和大部分时间花费在哪里。
|
||||
我的主工作站比虚拟机的结果更有意义。工作站组成是ASUS TUF X299 Mark 2 主板，Intel i9-7960X cpu （16核 32线程），64G内存。一些命令非超级用户可以使用，但是我在这篇文章里使用了超级用户避免在用户之间切换。
|
||||
检查起动过程有几个选项，最简单的是从 systemd-analyze 命令显示起动的几个主要分段耗费的时间汇总，内核起动，装载运行 initrd （初始ramdisk，一个临时系统镜像用来初始化一些硬件，挂载 / 根文件系统），还有用户空间 （所有的程序和后台进程需要主机起动到一个可用的状态）。如果没有子命令传递给命令， systemd-analyze time 是这样的：
|
||||
|
||||
```
|
||||
[root@david ~]$ systemd-analyze
|
||||
@ -34,18 +33,17 @@ Startup finished in 53.921s (firmware) + 2.643s (loader) + 2.236s (kernel) + 4.3
|
||||
graphical.target reached after 10.071s in userspace
|
||||
[root@david ~]#
|
||||
```
|
||||
特别要注意的 BIOS 花费了接近54秒，这是一个非同寻常的时间段，基本上所有的物理硬件系统都要使用 BIOS。
|
||||
|
||||
The most notable data in this output is the amount of time spent in firmware (BIOS): almost 54 seconds. This is an extraordinary amount of time, and none of my other physical systems take anywhere near as long to get through BIOS.
|
||||
我的System76 Oryx Pro笔记本在BIOS只花了8.506秒，我家里所有的系统都在10秒以内。在线搜索一阵之后，我发现这个主板（译者注：作者的主工作站主板）因为不同寻常的 BIOS 启动时间著名，我的主板从不“启动”，总是挂掉，我需要关机再开机，BIOS报错，按 F1 进入 BIO S设置，选择要启动的驱动器完成启动，多出的时间就是这样用掉的。
|
||||
|
||||
My System76 Oryx Pro laptop spends only 8.506 seconds in BIOS, and all of my home-built systems take a bit less than 10 seconds. After some online searches, I found that this motherboard is known for its inordinately long BIOS boot time. My motherboard never "just boots." It always hangs, and I need to do a power off/on cycle, and then BIOS starts with an error, and I need to press F1 to enter BIOS configuration, from where I can select the boot drive and finish the boot. This is where the extra time comes from.
|
||||
不是所有主机显示固件数据（译者注：固件启动中无法使用 systemd）。用Intel 9代或者更高的处理器就感觉不科学。尽管那不是正确的。（译者注：更高代的 cpu 启动时间更短，因为优化的 BIOS ）
|
||||
|
||||
Not all hosts show firmware data. My unscientific experiments lead me to believe that this data is shown only for Intel generation 9 processors or above. But that could be incorrect.
|
||||
总结关于启动起动是非常有趣的，同时提供了很好的（虽然有限）的信息，仍然有很多关于起动的信息，就像下面我将描述的一样。
|
||||
|
||||
This overview of the boot startup process is interesting and provides good (though limited) information, but there is much more information available about startup, as I'll describe below.
|
||||
### 指定火炬
|
||||
|
||||
### Assigning blame
|
||||
|
||||
You can use `systemd-analyze blame` to discover which systemd units take the most time to initialize. The results are displayed in order by the amount of time they take to initialize, from most to least:
|
||||
你可以用 systemd-analyze blame 去发现初始化每个 systemd 单元用掉的时间，结果按照初始化时间长短排序，从多到少：
|
||||
|
||||
|
||||
```
|
||||
@ -64,14 +62,16 @@ You can use `systemd-analyze blame` to discover which systemd units take the mos
|
||||
396ms initrd-switch-root.service
|
||||
<SNIP – removed lots of entries with increasingly small times>
|
||||
```
|
||||
注：删去了好多时间不长的条目
|
||||
|
||||
Because many of these services start in parallel, the numbers may add up to significantly more than the total given by `systemd-analyze time` for everything after the BIOS. All of these are small numbers, so I cannot find any significant savings here.
|
||||
因为很多服务是并行开始的，在 BIOS 之后所有单元加在一起的总数超过了 systemd-analyze time 汇总数。很多都是小数，不能显著的节省时间。
|
||||
|
||||
The data from this command can provide indications about which services you might consider to improve boot times. Services that are not used can be disabled. There does not appear to be any single service that is taking an excessively long time during this startup sequence. You may see different results for each boot and startup.
|
||||
这个命令提供的数据显明了提升启动时间的办法。无用的服务禁止（disable）掉。在起动序列中花掉很多时间的单一服务呈现明显。每次启动起动你可以看到不同结果。（译者注：并行起动服务的原因）
|
||||
|
||||
### Critical chains
|
||||
### 严格链
|
||||
|
||||
Like the critical path in project management, a _critical chain_ shows the time-critical chain of events that take place during startup. These are the systemd units you want to look at if startup is slow, as they are the ones that would cause delays. This tool does not display all the units that start, only those in this critical chain of events:
|
||||
项目管理中有个严格链，（译者注：systemd可以定义服务间严格依赖，构成严格链）在起动中可以通过查看一个严格链与时间相关的事件。
|
||||
有一些systemd单元起动中很慢，可能因为依赖严格链影响的，工具没有从开始显示所有单元，仅仅是有严格限制关系的事件。（译者注：相当于最短路径。并不显示依赖但不在严格链上的服务单元）
|
||||
|
||||
|
||||
```
|
||||
@ -108,11 +108,11 @@ graphical.target @10.071s
|
||||
[root@david ~]#
|
||||
```
|
||||
|
||||
The numbers preceded with `@` show the absolute number of seconds since startup began when the unit becomes active. The numbers preceded by `+` show the amount of time it takes for the unit to start.
|
||||
@后面的秒数数字是从起动开始到单元激活的时间，+后面是单元开始花费的时间。
|
||||
|
||||
### System state
|
||||
### 系统状态
|
||||
|
||||
Sometimes you need to determine the system's current state. The `systemd-analyze dump` command dumps a _massive_ amount of data about the current system state. It starts with a list of the primary boot timestamps, a list of each systemd unit, and a complete description of the state of each:
|
||||
有时候你需要决定系统的当前状态， systemd-analyze dump 命令挖显出当前系统状态的一堆数据。有主要的启动时间戳，一个每个 systemd 单元的列表，和一个每个完整的详细描述：
|
||||
|
||||
|
||||
```
|
||||
@ -149,38 +149,39 @@ Timestamp initrd-units-load-finish: Wed 2020-08-26 12:33:38 EDT
|
||||
<SNIP – Deleted a bazillion lines of output>
|
||||
```
|
||||
|
||||
On my main workstation, this command generated a stream of 49,680 lines and about 1.66MB. This command is very fast, so you don't need to wait for the results.
|
||||
注：删掉了很多输出行
|
||||
|
||||
I do like the wealth of detail provided for the various connected devices, such as storage. Each systemd unit has a section with details such as modes for various runtimes, cache, and log directories, the command line used to start the unit, the process ID (PID), the start timestamp, as well as memory and file limits.
|
||||
在我的主工作站，这个命令生成了49680行大概1.66MB，命令很快，你不需要等待。
|
||||
|
||||
The man page for `systemd-analyze` shows the `systemd-analyze --user dump` option, which is intended to display information about the internal state of the user manager. This fails for me, and internet searches indicate that there may be a problem with it. In systemd, `--user` instances are used to manage and control the resources for the hierarchy of processes belonging to each user. The processes for each user are part of a control group, which I'll cover in a future article.
|
||||
我喜欢多种连接设备的规格细节，例如存储。每个 systemd 单元有一节例如模块的多种运行时、缓存、日志目录、单元开始命令、PID、开始时间戳、内存和文件限制。
|
||||
|
||||
### Analytic graphs
|
||||
systemd-analyze 的 man 帮助手册里展示了 systemd-analyze --user dump 选项，显示用户管理器的内部状态。但是我失败了，互联网搜索之后表明机器有一些问题。在 systemd 里， --user 实例用来管理和控制处理器给每个用户的资源。处理能力按分给每个用户的控制组 control group（译者注：系统管理一个特性）分配，我回头再写。
|
||||
|
||||
Most pointy-haired-bosses (PHBs) and many good managers find pretty graphs easier to read and understand than the text-based system performance data I usually prefer. Sometimes, though, even I like a good graph, and `systemd-analyze` provides the capability to display boot/startup data in an [SVG][4] vector graphics chart.
|
||||
### 分析图表
|
||||
|
||||
The following command generates a vector graphics file that displays the events that take place during boot and startup. It only takes a few seconds to generate this file:
|
||||
很多尖头老板( pointy-haired-bosses )和好的经理人发现好的图表特别容易阅读理解，比我经常看的文本类系统性能数据好。看，我喜欢好图表，systemd-analyze 提供了显示启动/起动数据用 [SVG][4] 向量图表。
|
||||
|
||||
下面的命令生成一个向量图文件来显示在启动起动之间发生的事件。生成这个文件只需要几秒：
|
||||
|
||||
```
|
||||
`[root@david ~]# systemd-analyze plot > /tmp/bootup.svg`
|
||||
```
|
||||
|
||||
This command creates an SVG, which is a text file that defines a series of graphic vectors that applications, including Image Viewer, Ristretto, Okular, Eye of Mate, LibreOffice Draw, and others, use to generate a graph. These applications process SVG files to create an image.
|
||||
这个命令创建了 SVG，SVG是一个定义图向量应用的文本文件，包括Image Viewer、Ristretto、 Okular、 Eye of Mate、 LibreOffice Draw、和其他，(译者注：这些是文档应用）用来生成图。这些应用可以处理 SVG 来创建一个图像。
|
||||
|
||||
I used LibreOffice Draw to render a graph. The graph is huge, and you need to zoom in considerably to make out any detail. Here is a small portion of it:
|
||||
我用 LibreOffice Draw（译者注：一个办公文档软件）去渲染一幅图。图很大，你需要放大来看细节。这里放的比较小：
|
||||
|
||||
![The bootup.svg file displayed in LibreOffice Draw.][5]
|
||||
|
||||
(David Both, [CC BY-SA 4.0][6])
|
||||
|
||||
The bootup sequence is to the left of the zero (0) on the timeline in the graph, and the startup sequence is to the right of zero. This small portion shows the kernel, `initrd`, and the processes `initrd` started.
|
||||
启动起始是图上左面的时间线0，起动序列在0的右面。这个小图显示了内核、initrd、和initrd处理开启。
|
||||
|
||||
This graph shows at a glance what started when, how long it took to start up, and the major dependencies. The critical path is highlighted in red.
|
||||
这个图显示了谁什么时候开始，持续了多久，和主要的依赖。严格路径是红色高亮的。
|
||||
|
||||
Another command that generates graphical output is `systemd-analyze plot`. It generates textual dependency graph descriptions in [DOT][7] format. The resulting data stream is then piped through the `dot` utility, which is part of a family of programs that can be used to generate vector graphic files from various types of data. These SVG files can also be processed by the tools listed above.
|
||||
另外一个生成图片输出的命令是 systemd-analyze plot，它生成了[DOT][7] 格式纹理依赖图。结果数据流通过 dot 工具管道，这是一族用来生成向量图文件多种类型数据的程序。这些 SVG 文件也能被上面列出的工具处理。
|
||||
|
||||
First, generate the file. This took almost nine minutes on my primary workstation:
|
||||
首先，生成文件，在我的主工作站花了9分钟：
|
||||
|
||||
|
||||
```
|
||||
@ -197,15 +198,17 @@ sys 0m0.070s
|
||||
[root@david ~]#
|
||||
```
|
||||
|
||||
I won't reproduce the output here because the resulting graph is pretty much spaghetti. But you should try it and view the result to see what I mean.
|
||||
我不想重新生成输出了，因为比意大利面还好。但是你应该试试看看我想让你看到的结果。
|
||||
|
||||
### Conditionals
|
||||
### 条件
|
||||
|
||||
One of the more interesting, yet somewhat generic, capabilities I discovered while reading the `systemd-analyze(1)` man page is the `condition` subcommand. (Yes—I do read the man pages, and it is amazing what I have learned this way!) This `condition` subcommand can be used to test the conditions and asserts that can be used in systemd unit files.
|
||||
我不想重新生成输出了，因为比意大利面还好。但是你应该试试看看我想让你看到的结果。
|
||||
|
||||
It can also be used in scripts to evaluate one or more conditions—it returns a zero (0) if all are met or a one (1) if any condition is not met. In either case, it also spews text about its findings.
|
||||
很多有意思的，也有些普遍的，当我读 systemd-analyze man 帮助时发现 condition 子命令 （是的，我读了man帮助手册，我就是这样学习的）。这个 condition 子命令能用来测试条件和断言 systemd 单元文件。
|
||||
|
||||
The example below, from the man page, is a bit complex. It tests for a kernel version between 4.0 and 5.1, that the host is running on AC power, that the system architecture is anything but ARM, and that the directory `/etc/os-release` exists. I added the `echo $?` statement to print the return code.
|
||||
把它放到程序里评估一个或者多个条件成立是否返回 0 值，或者条件没有成立返回 1。 在其他情况，它根据调查结果吐出文本。
|
||||
|
||||
下面的例子，来自man帮助手册，稍微有点复杂。它测试了内核版本是不是在 4.0 和 5.1，主机使 用AC power，系统结构不是 arm，并且它的目录 /etc/os-release 是否存在。我加了 echo $? 来打印返回值。
|
||||
|
||||
|
||||
```
|
||||
@ -226,11 +229,11 @@ Conditions succeeded.
|
||||
[root@david ~]#
|
||||
```
|
||||
|
||||
The list of conditions and asserts starts around line 600 on the `systemd.unit(5)` man page.
|
||||
条件和断言在 systemd.unit(5) man帮助手册的大概 600 行。
|
||||
|
||||
### Listing configuration files
|
||||
### 罗列配置文件
|
||||
|
||||
The `systemd-analyze` tool provides a way to send the contents of various configuration files to `STDOUT`, as shown here. The base directory is `/etc/`:
|
||||
systemd-analyze 工具可以发送多种配置文件内容去标准输出，像这儿展示的，基础根目录是 /etc/:
|
||||
|
||||
|
||||
```
|
||||
@ -254,7 +257,7 @@ Alias=display-manager.service
|
||||
[root@david ~]#
|
||||
```
|
||||
|
||||
This is a lot of typing to do nothing more than a standard `cat` command does. I find the next command a tiny bit helpful. It can search out files with the specified pattern within the standard systemd locations:
|
||||
这和标准的 cat 命令做的差不多。我发现另外一条小有帮助的命令，它能在标准的 systemd 所在的位置搜索模式匹配的内容：
|
||||
|
||||
|
||||
```
|
||||
@ -298,22 +301,22 @@ WantedBy=multi-user.target
|
||||
[root@david ~]#
|
||||
```
|
||||
|
||||
Both of these commands preface the contents of each file with a comment line containing the file's full path and name.
|
||||
这些命令为每个文件提供了包含文件的全路径和文件名的注释行。
|
||||
|
||||
### Unit file verification
|
||||
### 单元文件检查
|
||||
|
||||
After creating a new unit file, it can be helpful to verify that its syntax is correct. This is what the `verify` subcommand does. It can list directives that are spelled incorrectly and call out missing service units:
|
||||
当创建了一个新的单元文件，利用 verify 子命令帮助检查语法是否正确。它能指出来不正确的拼写和呼叫错误服务单元的指导。
|
||||
|
||||
|
||||
```
|
||||
`[root@david ~]# systemd-analyze verify /etc/systemd/system/backup.service`
|
||||
```
|
||||
|
||||
Adhering to the Unix/Linux philosophy that "silence is golden," a lack of output messages means that there are no errors in the scanned file.
|
||||
Unix/Linux 的反馈宗旨是“沉默是金”，没有输出意味着扫描文件没有错。
|
||||
|
||||
### Security
|
||||
### 安全
|
||||
|
||||
The `security` subcommand checks the security level of specified services. It only works on service units and not on other types of unit files:
|
||||
security 子命令检查指定服务的安全级别。只能针对服务单元，其他类型的单元文件不可用：
|
||||
|
||||
|
||||
```
|
||||
@ -340,30 +343,27 @@ The `security` subcommand checks the security level of specified services. It on
|
||||
lines 34-81/81 (END)
|
||||
```
|
||||
|
||||
Yes, the emoji is part of the output. But, of course, many services need pretty much complete access to everything in order to do their work. I ran this program against several services, including my own backup service; the results may differ, but the bottom line seems to be mostly the same.
|
||||
是的，哭脸（emoji）是输出。但是当然，很多服务的工作比美观更重要。我列举了一些服务，包括我自己的备份服务，结果可能不同，但是最下面一行看起来是一样的。
|
||||
这个工具对于在严格的安全环境检查和修复用户空间服务单元是很有用的。我不认为我们的大多数都能用到它。
|
||||
|
||||
This tool would be very useful for checking and fixing userspace service units in security-critical environments. I don't think it has much to offer for most of us.
|
||||
### 最后总结
|
||||
|
||||
### Final thoughts
|
||||
强有力的工具（sysmted-analyze）提供了一些有意思和迷人的有益的选项。这篇文章阐述了用 systemd-analyze 来分析 systemd Linux内部起动性能。它同样能分析 systemd 的其他方面。
|
||||
工具的某部分是限制使用的，有些被遗漏。但是大多数对于起动和其他 systemd 功能的问题解决提供了很好的结果。
|
||||
|
||||
This powerful tool offers some interesting and amazingly useful options. Much of what this article explores is about using `systemd-analyze` to provide insights into Linux's startup performance using systemd. It can also analyze other aspects of systemd.
|
||||
### 资源
|
||||
|
||||
Some of these tools are of limited use, and a couple should be forgotten completely. But most can be used to good effect when resolving problems with startup and other systemd functions.
|
||||
互联网上关于 systemd 有很多信息，但是很多过于简洁，迟钝，甚至误导。这篇文章中提到的额外的资源，是列在下面的关于 systemd 起动的更细节更可信的web页面。我罗列了自从我开始这个系列的文章影响我研究的内容。
|
||||
|
||||
### Resources
|
||||
|
||||
There is a great deal of information about systemd available on the internet, but much is terse, obtuse, or even misleading. In addition to the resources mentioned in this article, the following webpages offer more detailed and reliable information about systemd startup. This list has grown since I started this series of articles to reflect the research I have done.
|
||||
|
||||
* The [systemd.unit(5) manual page][9] contains a nice list of unit file sections and their configuration options along with concise descriptions of each.
|
||||
* The Fedora Project has a good, practical [guide to systemd][10]. It has pretty much everything you need to know in order to configure, manage, and maintain a Fedora computer using systemd.
|
||||
* The Fedora Project also has a good [cheat sheet][11] that cross-references the old SystemV commands to comparable systemd ones.
|
||||
* Red Hat documentation contains a good description of the [Unit file structure][12] as well as other important information.
|
||||
* For detailed technical information about systemd and the reasons for creating it, check out Freedesktop.org's [description of systemd][13].
|
||||
* [Linux.com][14]'s "More systemd fun" offers more advanced systemd [information and tips][15].
|
||||
* The [systemd.unit(5) 手册页面][9] 包含了非常棒的每个都是丰富细节描述的一些单元文件节段和它们的配置文件选项。
|
||||
* The Fedora 项目有一个好的练习 [systemd 指导][10]. 它指导了你用 Fedora systemd 要知道的设置，管理，维护。
|
||||
* The Fedora 项目还有一个好的 [备忘录][11] 兼容交叉了老的 SystemV 命令和 systemd 以及比较。
|
||||
* Red Hat 文档包含了一个详细的描述 [单元文件结构][12] 和其他一样重要的信息。
|
||||
* 关于systemd技术细节和创建的原因，可以去 Freedesktop.org's [ systemd 详述][13].
|
||||
* [Linux.com][14]的 "更多 systemd 乐趣" 提供了很多高级的 systemd [信息和提示][15].
|
||||
|
||||
|
||||
|
||||
There is also a series of deeply technical articles for Linux sysadmins by Lennart Poettering, the designer and primary developer of systemd. These articles were written between April 2010 and September 2011, but they are just as relevant now as they were then. Much of everything else good that has been written about systemd and its ecosystem is based on these papers.
|
||||
下面是 systemd 设计者和主要开发者 Lennart Poettering 关于 Linux 系统管理员的深度技术文档，这些文章尽管写于2010年4月到2011年9月，现在看也是非常适应时宜的。其他很棒的 systemd 相关的体系都基于这些设计。
|
||||
|
||||
* [Rethinking PID 1][16]
|
||||
* [systemd for Administrators, Part I][17]
|
||||
@ -386,7 +386,7 @@ via: https://opensource.com/article/20/9/systemd-startup-configuration
|
||||
|
||||
作者：[David Both][a]
|
||||
选题：[lujun9972][b]
|
||||
译者：[译者ID](https://github.com/译者ID)
|
||||
译者：[jiamn](https://github.com/jiamn)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
||||
@ -1,117 +0,0 @@
|
||||
[#]: subject: "Nautilus File Manager Looks Amazing with GTK4 and Libadwaita – A Deep Dive"
|
||||
[#]: via: "https://www.debugpoint.com/2022/03/gnome-files-43/"
|
||||
[#]: author: "Arindam https://www.debugpoint.com/author/admin1/"
|
||||
[#]: collector: "lujun9972"
|
||||
[#]: translator: "geekpi"
|
||||
[#]: reviewer: " "
|
||||
[#]: publisher: " "
|
||||
[#]: url: " "
|
||||
|
||||
使用 GTK4 和 Libadwaita 让 Nautilus 文件管理器看起来很出色 - 深入研究
|
||||
======
|
||||
我们测试了 GNOME Files v43 的开发版本，并向你介绍了其外观、功能和性能的细节。
|
||||
|
||||
GNOME Files（以前的 Nautilus）也许是当今 GNOME 生态空间中使用最多的桌面应用。而且，自其首次发布以来，它从未接受过什么大修，而其他的 GNOME 应用和桌面本身都转移到了一个较新的技术栈。
|
||||
|
||||
现在一切都变了。GNOME 开发者正在为整个桌面和 Files 采用 GTK4 和 libadwaita。
|
||||
|
||||
GNOME Files v43，将在 2022 年晚些时候与 GNOME 43 一起发布，将令人印象深刻。这个急需的[重做][1]带来了原生的深色模式，出色的 UI 以及出色的 libadwaita 触控和 GTK4 性能提升。
|
||||
|
||||
### GNOME Files 43
|
||||
|
||||
我们安装了 GNOME Files 43 的 Flatpak 开发版本，下面是我们的发现。
|
||||
|
||||
第一眼，你应该注意到漂亮的 UI 触控，这要感谢 Libadwaita。关闭按钮是漂亮的圆形，而地址栏、选择高亮器和整个文件窗口都有适当的间距和圆角。
|
||||
|
||||
所有的组件都没有出现边框高亮线。
|
||||
|
||||
下面是 v43（左）和 v42（右）的深浅模式的快速比较。
|
||||
|
||||
![GNOME Files 43 and 42 – Light Mode Comparison][2]
|
||||
|
||||
![GNOME Files 43 and 42 – Dark Mode Comparison][3]
|
||||
|
||||
地址栏的文件夹分隔符保持不变。然而，字体却有了些许润色。地址栏的上下文菜单改变了。这个选项没有了。取而代之的是 **Open in Other application** 菜单。一个新的选项 **Create Link** 被引入。我想许多用户会怀念在终端打开的选项。
|
||||
|
||||
![New option in address bar menu][4]
|
||||
|
||||
另一个重要的变化是你应该注意到两个主要的工具条菜单：a）视图按钮和 b）主设置菜单。这些上下文菜单项显示键盘快捷键以及菜单项。 这也使它们看起来更加突出。
|
||||
|
||||
![The Hamburger menu now have keyboard shortcuts][5]
|
||||
|
||||
文件夹的上下文菜单现在有一个向上的小箭头，指向从它弹出的文件夹。文件夹的右键上下文菜单以组为单位组织得很好。例如，打开动作是分组的，而剪切、复制、粘贴在上下文菜单中以横杠的形式明显分开。
|
||||
|
||||
![Context Menu for folder changes][6]
|
||||
|
||||
我还注意到一个新的选项 “Paste into the folder”，这个很好。
|
||||
|
||||
Nautilus 搜索几乎与 Files 42 相同，只是在 Files 43 中你可以通过创建日期/时间搜索。
|
||||
|
||||
然而，我注意到一个令人兴奋的变化。上下文菜单中的文件关联的应用名称被移除。例如，如果你今天试图在 Files 42 中打开一个文本文件，它在上下文菜单中显示与之相关的应用名称。在 Files 43 中，它只显示 “Open”。我觉得这种改变是不必要的。之前的情况更好。
|
||||
|
||||
![A subtle change in context menu for file association][7]
|
||||
|
||||
所以，这就是我在这个应用的新 GTK4 版本中发现的整体变化。但它看起来不错？不是吗。此外，如果你是直接从 Ubuntu 20.04 LTS 来的，其中包含 Files 3.38，那么也许你的体验会是“哇”。如果你将 Files 43 与 Files 3.38 进行比较，大部分的部分都发生了变化。对于这些用户来说，这将是一个相当不错的体验。
|
||||
|
||||
You should remember version 43 is still in development so that things may change in the coming days in the final shipment.
|
||||
|
||||
### 愿望清单
|
||||
|
||||
如果我比较各种 Linux 文件管理器，其他的选择远远多于今天的 GNOME Files。
|
||||
|
||||
我同意。
|
||||
|
||||
例如，Nemo 或 Dolphin - 这两个最好的文件管理器在各方面都胜过 Files。比较一下功能，GNOME Files 没有一些流行的功能：
|
||||
|
||||
* 双面板或分割视图
|
||||
* 从上下文菜单中打开一个根文件夹是困难的
|
||||
* 一个用于文件夹浏览的向上箭头
|
||||
* 没有从上下文菜单中创建一个新文件（文本、电子表格等）的选项
|
||||
* 更多的排序和搜索功能
|
||||
|
||||
|
||||
|
||||
我们希望这些功能能尽快出现在 GNOME Files 中。
|
||||
|
||||
### 何时能用
|
||||
|
||||
如上所述，这个版本的 GNOME Files 将与 GNOME 43 一起提供。因此，从Linux 发行计划的角度来看，你应该在 2022 年 10 月周期的 Ubuntu 22.10 和今年晚些时候的 Fedora 37 上拥有它。
|
||||
|
||||
不幸的是，[Ubuntu 22.04 LTS][9]（Jammy Jellyfish）和带 [GNOME 42][10] 的 [Fedora 36][11] 将不会有 GNOME Files 43。主要原因是时间表不匹配，而且它是要移植到 GTK4 和彻底测试的复杂应用之一。然而，大部分上述的内部功能仍然会在 Files 42 中。但它可能缺少漂亮的 UI 变化和主题。
|
||||
|
||||
尽管如此，我相信这个流行的文件管理器看起来不错，当它发布时，用户应该会很兴奋地使用它。让我知道你对 GNOME Files 43 的新变化的看法，请在下面的评论框中留言。
|
||||
|
||||
祝贺你。
|
||||
|
||||
* * *
|
||||
|
||||
我们带来最新的技术、软件新闻和重要的东西。通过 [Telegram][12]、[Twitter][13]、[YouTube][14] 和 [Facebook][15] 保持联系，不要错过任何更新！
|
||||
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://www.debugpoint.com/2022/03/gnome-files-43/
|
||||
|
||||
作者：[Arindam][a]
|
||||
选题：[lujun9972][b]
|
||||
译者：[geekpi](https://github.com/geekpi)
|
||||
校对：[校对者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/lujun9972
|
||||
[1]: https://gitlab.gnome.org/GNOME/nautilus
|
||||
[2]: https://www.debugpoint.com/wp-content/uploads/2022/03/GNOME-Files-43-and-42-Light-Mode-Comparison-1024x502.jpg
|
||||
[3]: https://www.debugpoint.com/wp-content/uploads/2022/03/GNOME-Files-43-and-42-Dark-Mode-Comparison-1024x493.jpg
|
||||
[4]: https://www.debugpoint.com/wp-content/uploads/2022/03/New-option-in-address-bar-menu-1024x267.jpg
|
||||
[5]: https://www.debugpoint.com/wp-content/uploads/2022/03/The-Hamburger-menu-now-have-keyboard-shortcuts-1024x331.jpg
|
||||
[6]: https://www.debugpoint.com/wp-content/uploads/2022/03/Context-Menu-for-folder-changes-1024x560.jpg
|
||||
[7]: https://www.debugpoint.com/wp-content/uploads/2022/03/A-subtle-change-in-context-menu-for-file-association-1024x524.jpg
|
||||
[9]: https://www.debugpoint.com/2022/01/ubuntu-22-04-lts/
|
||||
[10]: https://www.debugpoint.com/2021/12/gnome-42/
|
||||
[11]: https://www.debugpoint.com/2022/02/fedora-36/
|
||||
[12]: https://t.me/debugpoint
|
||||
[13]: https://twitter.com/DebugPoint
|
||||
[14]: https://www.youtube.com/c/debugpoint?sub_confirmation=1
|
||||
[15]: https://facebook.com/DebugPoint
|
||||
@ -0,0 +1,95 @@
|
||||
[#]: subject: "Xfce Terminal 1.0.0 is a Feature-Packed Major Upgrade After a Year"
|
||||
[#]: via: "https://news.itsfoss.com/xfce-terminal-1-0-0-release/"
|
||||
[#]: author: "Jacob Crume https://news.itsfoss.com/author/jacob/"
|
||||
[#]: collector: "lujun9972"
|
||||
[#]: translator: "geekpi"
|
||||
[#]: reviewer: " "
|
||||
[#]: publisher: " "
|
||||
[#]: url: " "
|
||||
|
||||
Xfce Terminal 1.0.0 是时隔一年后的一次功能丰富的重大升级
|
||||
======
|
||||
|
||||
作为几乎所有 Xfce 发行版上流行的终端模拟器，Xfce Terminal 刚刚在新的维护者（和新的版本计划）下发布了它的第一次重大升级。
|
||||
|
||||
让我们来看看这个版本的一些亮点。
|
||||
|
||||
### 新的维护者和版本管理方案
|
||||
|
||||
Igor Zakharov 从 2016 年到 2020 年一直在领导开发工作。不幸的是，在 2021 年，当新的维护者 [Sergios][1] Anestis Kefalidis（也是 Thunar 文件管理器的开发者）接手后，它就没有被维护了。
|
||||
|
||||
而且，自从 Sergios 接管了这个项目后，版本管理方案也发生了变化。经过与社区的协商，Thunar 的旧版本计划被采用。
|
||||
|
||||
例如，1.1.x 版本将是开发版本，而 1.2.0 版本将是下一个主要升级版本。
|
||||
|
||||
现在，随着 Xfce Terminal 1.0.0 的发布，一些令人兴奋的新特性已经被纳入。
|
||||
|
||||
### 新特性
|
||||
|
||||
Xfce Terminal 1.0.0 的一些新特性包括：
|
||||
|
||||
* 改进了自定义选项
|
||||
* 支持叠加滚动条
|
||||
* 命令行选项的改进
|
||||
* 更多使用 XfceTitledDialog
|
||||
|
||||
|
||||
|
||||
#### 更好的自定义选项
|
||||
|
||||
和现在许多应用的更新一样，Xfce Terminal 1.0.0 包括大量新的自定义选项。也许我最喜欢的是，图像背景功能现在有一个“填充”风格选项。伴随着这一点的是暂时禁用不安全的粘贴对话框的能力，它也被改造了。
|
||||
|
||||
最后，XFCE Terminal 也成为首批支持新的 XFCE 快捷键编辑器的应用之一。因此，用户不再需要潜心研究配置文件，而是有了一个简单的 UI 来使用。
|
||||
|
||||
![][2]
|
||||
|
||||
有了这么多新的定制选项，我相信很多人都会对一个只包含这些的版本感到满意。但可惜的是! 开发者设法加入了更多令人兴奋的新功能，其中下一个是改进的命令行参数。
|
||||
|
||||
#### 更好的命令行参数
|
||||
|
||||
在这个版本中，“-tab” 和 “-window” 命令行参数已经被修复，变得更加直观。这修复了 XFCE Terminal 中一个[长期存在的 bug][3]，它已经存在了近 6 年。
|
||||
|
||||
尽管等待了很久，但现在它已经被修复了。迟到总比不到好，是吧？
|
||||
|
||||
不管怎么说，看到每一个新版本的 bug 被修复总是很好的，这个趋势在这里继续。
|
||||
|
||||
#### 更多使用 Xfce 专用的小工具
|
||||
|
||||
虽然我相信很多用户可能会认为这是一个降级，但 XFCE Terminal 使用更多的 XFCE 专用小工具带来了很多好处。虽然这确实意味着对非 XFCE 用户有更多的依赖性，但它意味着与 XFCE 更好的整合。
|
||||
|
||||
可以说，大多数的 Xfce Terminal 用户都坚持使用同一个桌面环境。所以，这种改变应该会带来更大的一致性和用户体验的改善。
|
||||
|
||||
#### 其他变化
|
||||
|
||||
这个版本的其他变化包括：
|
||||
|
||||
* “输出滚动”偏好的改进
|
||||
* 右键点击行为的自定义选项
|
||||
* 为缩小代码库而进行的代码重做
|
||||
|
||||
|
||||
关于完整的功能列表，请随时参考[发布说明][4]。发布说明中还提到了下一个主要版本的未来计划，即 v1.2.0。
|
||||
|
||||
### 总结
|
||||
|
||||
总的来说，Xfce Terminal 1.0.0 看起来是一个很好的版本，也说明了其新的维护者的奉献精神。
|
||||
|
||||
如果你想试试 Xfce Terminal 1.0.0，它应该会在接下来的几周内进入你的发行库，如果还没有的话。
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://news.itsfoss.com/xfce-terminal-1-0-0-release/
|
||||
|
||||
作者：[Jacob Crume][a]
|
||||
选题：[lujun9972][b]
|
||||
译者：[geekpi](https://github.com/geekpi)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
||||
[a]: https://news.itsfoss.com/author/jacob/
|
||||
[b]: https://github.com/lujun9972
|
||||
[1]: https://www.youtube.com/channel/UCu8-J-XWcXQhoCopBiJ5-uw/videos
|
||||
[2]: data:image/svg+xml;base64,PHN2ZyBoZWlnaHQ9IjUwOSIgd2lkdGg9Ijc4MCIgeG1sbnM9Imh0dHA6Ly93d3cudzMub3JnLzIwMDAvc3ZnIiB2ZXJzaW9uPSIxLjEiLz4=
|
||||
[3]: https://bugzilla.xfce.org/show_bug.cgi?id=12926
|
||||
[4]: http://users.uoa.gr/~sdi1800073/sources/xfce_blog12.html
|
||||
Loading…
Reference in New Issue
Block a user