document/TranslateProject
2
0
Fork 0
mirror of https://github.com/LCTT/TranslateProject.git synced 2025-03-21 02:10:11 +08:00
Code Issues Packages Projects Releases Wiki Activity

Merge branch 'master' of https://github.com/LCTT/TranslateProject into translating

Browse Source
This commit is contained in:
geekpi 2022-08-04 08:33:32 +08:00
commit 6a79436cf6
8 changed files with 409 additions and 532 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

61
translated/tech/20211109 relaying mail to multiple smarthosts with opensmtpd.md → published/20211109 relaying mail to multiple smarthosts with opensmtpd.md
View File

@ -3,63 +3,54 @@
[#]: author: "jao https://jao.io"
[#]: collector: "lujun9972"
[#]: translator: "geekpi"
[#]: reviewer: " "
[#]: publisher: " "
[#]: url: " "
[#]: reviewer: "wxy"
[#]: publisher: "wxy"
[#]: url: "https://linux.cn/article-14891-1.html"
使用 opensmtpd 将邮件中继到多个 smarthost
使用 OpenSMTPD 将邮件中继到多个 smarthost
======
我喜欢使用本地 smtp 守护进程从我的笔记本电脑发送电子邮件，因为这样我即使在断开连接的情况下也可以发送电子邮件，而且，即使是在网络正常的情况下，因为我不需要等待网络协议在远程 smarthost 上完成。哦，我还需要本地邮件发送。
![](https://img.linux.net.cn/data/attachment/album/202208/03/162813rc900xbgx3xggxxg.jpg)
多年来，我一直使用后缀来达到这些目的。它具有可接受的简单配置。但最近我开始喜欢 VPN（[mullvad][1]，如果你想知道的话），并且在 `/etc/resolv.conf` 更改时会感到困惑（例如，因为你在 postfix 的服务启动后启动了 VPN）。我找到了一个非常简单的替代方案：[OpenSMTPD][2]。
我喜欢使用本地 SMTP 守护进程从我的笔记本电脑发送电子邮件，因为这样我即使在断开连接的情况下也可以发送电子邮件，而且，即使是在网络正常的情况下，因为我不需要等待网络协议在远程 smarthost 上完成。哦，我还需要本地邮件投递。
假设我想在使用 [jao@gnu.org][3] 发送电子邮件时使用 SMTP 服务器 fencepost.gnu.org，而在我的 `From` 头中使用 [mail@jao.io][4] 或 [news@xmobar.org][5] 时使用 smtp.jao.io。OpenSMTPD 让你通过一个非常简单的配置文件 `/etc/smtpd.conf`[1][6] 来实现：
多年来，我一直使用 Postfix 来达到这些目的。它具有可接受的简单配置。但最近我开始喜欢 VPN（[mullvad][1]，如果你想知道的话），而在 `/etc/resolv.conf` 发生变化时会变得混乱（例如，你在 Postfix 的服务启动后才启动 VPN）。我找到了一个非常简单的替代方案：[OpenSMTPD][2]。
假设我想在使用 [jao@gnu.org][3] 发送电子邮件时使用 SMTP 服务器 fencepost.gnu.org，而在我的 `From` 头中使用 [mail@jao.io][4] 或 [news@xmobar.org][5] 时使用 smtp.jao.io。OpenSMTPD 让你通过一个非常简单的配置文件 `/etc/smtpd.conf` 来实现：
（这是我的 Debian 机器中的默认配置文件。另一个流行的替代方案是 `/etc/openstmpd.conf`）。
```
table aliases file:/etc/aliases
table secrets db:/etc/mail/secrets.db
table aliases file:/etc/aliases
table secrets db:/etc/mail/secrets.db
table sendergnu { jao@gnu.org }
table senderjao { mail@jao.io, news@xmobar.org }
table sendergnu { jao@gnu.org }
table senderjao { mail@jao.io, news@xmobar.org }
listen on localhost
listen on localhost
action "local" mbox alias <aliases>
action "relaygnu" relay host smtp+tls://gnu@fencepost.gnu.org:587 auth <secrets>
action "relayjao" relay host smtps://jao@smtp.jao.io:465 auth <secrets>
match for local action "local"
match for any from mail-from <sendergnu> action "relaygnu"
match for any from mail-from <senderjao> action "relaygan"
action "local" mbox alias <aliases>
action "relaygnu" relay host smtp+tls://gnu@fencepost.gnu.org:587 auth <secrets>
action "relayjao" relay host smtps://jao@smtp.jao.io:465 auth <secrets>
match for local action "local"
match for any from mail-from <sendergnu> action "relaygnu"
match for any from mail-from <senderjao> action "relaygan"
```
我们还为此配置了本地投递。这是完整的配置文件！唯一需要的另一件事是生成 `secrets.db` 文件，其中包含与键 `gnu` 和 `jao` 对应的用户和密码（这些只是任意名称）。为此，我们使用它们创建一个纯文本文件，使用形式为 `<key> <user>:<password>` 的条目：
```
gnu jao:my fencepost password
jao mail@jao.io:xxxxxxxxxxxxxxxxx
gnu jao:my fencepost password
jao mail@jao.io:xxxxxxxxxxxxxxxxx
```
`fencepost.gnu.org` 用户是 `jao`，`smtp.jao.io` 的用户是 `mail@jao.io`（你看，不需要转义空格或 ats）。然后我们使用程序 `makemap` 来创建密钥数据库：
```
makemap secrets && rm secrets
makemap secrets && rm secrets
```
### 脚注：
[1][7]
That's the default configuration file in my debian box; other popular alternative is `/etc/openstmpd.conf`.
这是我的 debian 机器中的默认配置文件。另一个流行的替代方案是 `/etc/openstmpd.conf`。
--------------------------------------------------------------------------------
via: https://jao.io/blog/2021-11-09-relaying-mail-to-multiple-smarthosts.html
@ -67,7 +58,7 @@ via: https://jao.io/blog/2021-11-09-relaying-mail-to-multiple-smarthosts.html
作者：[jao][a]
选题：[lujun9972][b]
译者：[geekpi](https://github.com/geekpi)
校对：[校对者ID](https://github.com/校对者ID)
校对：[wxy](https://github.com/wxy)
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出

93
published/20220802 Secure Boot Disabled- GNOME Will Soon Warn You About it.md Normal file
View File

@ -0,0 +1,93 @@
[#]: subject: "Secure Boot Disabled? GNOME Will Soon Warn You About it!"
[#]: via: "https://news.itsfoss.com/gnome-secure-boot-warning/"
[#]: author: "Anuj Sharma https://news.itsfoss.com/author/anuj/"
[#]: collector: "lujun9972"
[#]: translator: "wxy"
[#]: reviewer: "wxy"
[#]: publisher: "wxy"
[#]: url: "https://linux.cn/article-14892-1.html"
如果禁用了安全启动，GNOME 就会发出警告
======
> GNOME 正计划通知用户其固件安全状态，来保护不安全的硬件。
![](https://news.itsfoss.com/wp-content/uploads/2022/08/gnome-secure-boot-warning.jpg)
当你在支持 UEFI 的电脑上安装 Linux 时，你必须禁用“<ruby>安全启动<rt>Secure Boot</rt></ruby>”，因为启用该选项后，不能使用<ruby>现场 USB<rt>Live USB</rt></ruby> 启动。
一些主流的 Linux 发行版支持安全启动，但对于许多其他发行版（以及板载的 Nvidia 硬件）来说，它的设置仍然具有挑战性。
虽然一年又一年，情况似乎并没有改善，但总的来说，安全启动是一个必不可少的保护功能。
因此，正如 [Phoronix][1] 所发现的，为了方便和让用户意识到这一点，GNOME 和红帽的开发者正在努力在安全启动被禁用时通知（或警告）用户。
### 它有什么用？
UEFI/安全启动被批评为 DRM，因为它剥夺了用户的自由。开源社区的许多人仍然不赞同实施 UEFI/安全启动和 TPM，因为它带来了不便。这就催生了像 [Coreboot][2] 这样的项目在开源世界中蓬勃发展。
当然，如果你每天都用 Linux，我会建议你购买支持 Coreboot 的新硬件，这是一个不同的故事。
话虽如此，但可以肯定的是，安全启动是最简单的方法。
考虑到捆绑的专有固件，安全启动的安全性仍然值得商榷。但是，它是一个确保系统的固件安全的基本保护机制。
所以，开发者准备在启动闪屏（[Plymouth][3]）、GNOME 显示管理器（GDM）和 GNOME 控制中心显示警告。
![图片来源：GNOME 博客][4]
GNOME 的一位开发者在 [博客文章][5] 中分享了它的更多细节，同时给出了其中的一些屏幕截图。
![][6]
一位来自红帽的开发者在 [合并请求][7] 中提到。
> 安全启动被用来对付一些恶意软件试图感染系统的固件的安全威胁。用户可能会无意中禁用或软件可能会有意禁用安全启动。因此，配置不正确的话，系统就运行在一个不安全的平台上。如果启动闪屏能向用户提供一个警告，用户可以重新启动并重新配置他们的系统，或者立即寻求帮助。
所以，作为一个 GNOME 用户，当它进入 GNOME 43 的最终版本或任何未来的版本时，我乐于看到它所带来的变化。
如果你也想看看，你可以在 GNOME 控制中心的“<ruby>隐私<rt>Privacy</rt></ruby>”标签下的“<ruby>设备安全<rt>Device Security</rt></ruby>”部分找到这个选项，如下图所示，我的机器在 Arch Linux 上运行 GNOME 43 alpha。
![][8]
该菜单还可以显示 TPM、英特尔 BootGuard 和 IOMMU 保护的细节。
![][9]
看来我的系统并不像我想象的那么安全……但也许这就是这个功能的意义所在？
如果你只在你的 Linux 发行版上使用 UEFI 模式，并且为了方便而关闭了安全保护功能，这能让你意识到这一点吗？
有可能。但是，看看 Linux 发行版的状况和启用安全启动的问题。我不觉得这可能会是一个大问题。我们很快就会知道了。
### 如何禁用这个警告？
正如在 GNOME Gitlab 的 [合并请求][10] 中提到的，在你的内核参数中添加 `sb-check=false` 就可以禁用这些警告。
不过，作为终端用户，你不需要担心这个问题。
你对即将在 GNOME 43 或更高版本中增加的这个功能有什么看法？你对 UEFI/安全启动有什么看法？
--------------------------------------------------------------------------------
via: https://news.itsfoss.com/gnome-secure-boot-warning/
作者：[Anuj Sharma][a]
选题：[lujun9972][b]
译者：[wxy](https://github.com/wxy)
校对：[wxy](https://github.com/wxy)
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
[a]: https://news.itsfoss.com/author/anuj/
[b]: https://github.com/lujun9972
[1]: https://www.phoronix.com/news/GNOME-Secure-Boot-Warning
[2]: https://www.coreboot.org/
[3]: https://gitlab.freedesktop.org/plymouth
[4]: https://news.itsfoss.com/wp-content/uploads/2022/08/gnome-secure-boot-mockup.png
[5]: https://blogs.gnome.org/hughsie/2022/07/29/emulated-host-profiles-in-fwupd/
[6]: https://news.itsfoss.com/wp-content/uploads/2022/08/boot-security.png
[7]: https://gitlab.freedesktop.org/plymouth/plymouth/-/merge_requests/176
[8]: https://news.itsfoss.com/wp-content/uploads/2022/07/secure-boot-gnome.png
[9]: https://news.itsfoss.com/wp-content/uploads/2022/07/secure-boot-gnome1.png
[10]: https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/2333

142
sources/news/20220724 Wayland Core Protocol is Tailored Only for GNOME and That-s Not a Good Thing -Opinion.md
View File

@ -1,142 +0,0 @@
[#]: subject: "Wayland Core Protocol is Tailored Only for GNOME and That’s Not a Good Thing [Opinion]"
[#]: via: "https://news.itsfoss.com/wayland-core-protocol-issue/"
[#]: author: "Community https://news.itsfoss.com/author/team/"
[#]: collector: "lujun9972"
[#]: translator: " "
[#]: reviewer: " "
[#]: publisher: " "
[#]: url: " "
Wayland Core Protocol is Tailored Only for GNOME and That’s Not a Good Thing [Opinion]
======
Wayland is a display server system based on the idea of [protocols][1]. That means that there is no Wayland display server that clients need to talk to. Instead, Wayland defines a protocol for creating display servers. Any client application that is programmed to use this protocol can work on any display server(or compositor) that fully supports this protocol. It’s like the [world wide web protocols][2], where any website can work on any browser as long as the browser is completely supporting the web protocols. So you don’t create websites for specific browsers.
That also means that the functions defined in the protocol decide what applications (aka clients) can do &amp; what they can’t do. Returning to the example of the website, if the protocol doesn’t define necessary functions, it will limit the web developers. Take CSS as an example; if it wasn’t available in the web protocols, all websites would have looked the same and boring. So the protocol must include all necessary basics in a way that doesn’t limit developers to a few cases and uses.
When Wayland developers started defining the protocol, they had to decide what functionalities to include in the protocol. Their decision was to make the protocol as minimal as possible, and compositors shall create new protocols for their specific use cases if they desire to offer more functionality not included in the main protocol. The main protocol was called [Wayland Core protocol][3], and other protocols are called [protocol extensions][4]. All compositors are expected to support the core protocol, and they may not support other protocol extensions. That means that applications that depend on certain functionality defined in one of the protocol extensions will not work on all compositors.
All of the above is what Wayland developers intended for the Wayland world to be. Now let’s delve into more detail. How much is Wayland core protocol minimal? In other words, what determines what shall be in the core protocol and what shall not be? In this article, I’m going to give you an answer to this question based on my opinion, which is in turn based on a group of simple facts.
_**My opinion is that Wayland’s Core protocol is tailored only for GNOME needs.**_
I mean that the functionalities which exist in Wayland’s core protocol are the bare minimum required for GNOME desktop and apps to work on Wayland.
That’s bad (still in my opinion) because it’s simply not enough for other desktop environments and apps other than GNOME desktop and apps, as I will show you in this article.
### 1\. The core protocol requires that desktop visual components be drawn by the compositor
First, let’s explain something. In most desktop environments, desktop components (like dock, panel, wallpaper, desktop icons, etc.) are regular clients. For those components to work, they need certain functions to be implemented by the compositor; those functions include:
* Ability to move the window
* Ability to tell the compositor to not draw decorations around said windows.
* Ability to keep it above all windows(in case of the panel) or keep it below all windows (in case of the background).
* In addition to some other functionalities.
On X11, those were defined in the ICCCM specification, which allows X11 clients to tell the compositor to do any of the above. On Wayland, there is not anything in the core protocol that allows that. This means that desktop environment creators have to draw all these in the compositor.
GNOME is the only desktop that does that, while many other desktops (KDE, XFCE, Lxqt, etc.) draw their components outside the compositor (an exception to that is Cinnamon because it started as a fork of GNOME 3). The situation is even worse. Apps like [plank dock][5], [latte dock][6] and other independent desktop components can’t exist in Wayland. There are protocol extensions that fix that, and I will discuss them later.
In summary, the situation is:
* Desktop environments have to draw everything in the compositor.
* It’s impossible to create cross-desktop desktop components like Plank and Latte dock
### 2\. CSD is implementable, although clients can’t move their window
We have known before that the core protocol doesn’t define a way for clients to move their windows. So how is CSD implemented? Well, there is a [function in the protocol][7] that tells the compositor to start dragging the window. So instead of having a function for moving the window, which would had been useful in many cases, they resorted to having a function only helpful in implementing CSD.
### 3\. CSD is a must in Wayland core protocol
On X11, the situation was that apps expect to get decorated by the compositor (which is SSD) and if they wish to decorate themselves (by CSD) they tell the compositor to not draw its decorations. On Wayland, compositors are free to draw their decorations if they wish.
The problem is that there is no way (inside the core protocol) for apps to know whether they are being decorated or not. In other words, clients can’t tell the compositor whether they prefer CSD or SSD, which is problematic for both CSD and SSD (in theory). But in practice, GNOME decided not to decorate clients at all. So apps have to assume that they are not decorated due to GNOME’s decision, so they must go for CSD. Again, there is a protocol extension that fixes that; more on that later.
### To summarize
The above three facts regarding the core protocol in summary are:
1. Desktop components need to be drawn by the compositor
2. CSD is a must.
3. CSD is implementable, although clients can’t move their windows.
According to these 3 facts, I’ve concluded my opinion that Wayland’s core protocol is tailored only for GNOME needs.
What if you wanted some functionalities not available in the core protocol. Wayland or GNOME developers’ answer to this is Wayland’s protocol extensions. That simply means that compositors can offer extra functionality by creating new protocols. The problem with this approach is that means that some apps may work on some compositors and may not work on the rest of the compositors (that’s if it needs some of the protocol extensions). That may have resulted in severe fragmentation in theory, but the reality is less than worse thanks to the efforts of [wlroots project][8] and KDE.
### Wlroots has mostly saved the situation
[Wlroots][8] is a library created by [Sway compositor][9] developers. It enables developers to create Wayland/X11 compositors easily. Their main focus is Wayland. There are already many compositors available based on wlroots. What is interesting though is the protocol extensions that wlroots implement.
Wlroots has many protocol extensions, including:
* [LayerShell][10] protocol
* [xdg-decoration][11] protocol
The LayerShell protocol enables desktop components to be drawn outside the compositor. Which also makes it possible to create independent cross-desktop desktop components. Many projects utilize this protocol that you can explore in the following repositories:
* [nwg-shell][12]
* [wf-shell][13]
* [awesome-wayland][14]
Also, have a look at [GtkLayerShell library][15]. Which is a library for writing Gtk apps with LayerShell protocol.
Because LayerShell protocol is not a part of the core protocol apps using it work on wlroots based compositors and KDE, it’s not supported only on GNOME.
The second protocol is xdg-decoration protocol. Made by wlroots and KDE, it enables apps to choose between CSD and SSD.
These protocols work on wlroots compositor and KDE. The only obstacle preventing the unification of Linux desktop is GNOME. They have decided not to implement any of these protocol extensions. Which put all apps that use SSD in a situation where they have to use SSD in supporting environments and CSD in gnome. The people actually feeling the pain are toolkits developers. To give you more context, have a look at the “CSD initiative” started by Tobias Bernard from GNOME, and this blog post from Martin’s blog (kwin’s developer). Also, have a look at this issue. The situation is mostly solved by now, that Qt and Gtk draw CSD always on GNOME and utilize the xdg-decoration on other environments. However, in my opinion, that is not good because it makes the platform less standardized/unified for no good reason. After all, in the future, toolkits developers may decide to just go for CSD to avoid the pain.
### The root of all these problems
The root of all these is GNOME or Wayland developers’ decision to have the core as minimum as possible and require the creation of protocol extensions.
Imagine if the web worked in a similar way. That means that websites would not be able to target the standardized (minimal) protocols because they are not enough and will rely on protocols created by certain browsers. So websites would target specific browsers, not the core protocol. That would had been a nightmare, right? Well, that’s the current Wayland situation.
### What is the solution?
The solution, in my opinion, is to put all these protocol extensions in the core protocol, or that might not be necessary if GNOME implements the above protocols (Which is not likely to happen anytime soon.)
In simple words, GNOME is the root cause of the problem, and it can solve the problem if it decides to do so.
Author Info: This article has been contributed by It’s FOSS reader Hamza Algohary. Hamza is a computer engineering student and a Linux and open source enthusiast. He also develops apps for Linux desktop. You can find his work on [his GitHub profile][16].
_The views and opinions expressed are those of the authors and do not necessarily reflect the official policy or position of It’s FOSS._
--------------------------------------------------------------------------------
via: https://news.itsfoss.com/wayland-core-protocol-issue/
作者：[Community][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/team/
[b]: https://github.com/lujun9972
[1]: https://wayland.freedesktop.org/docs/html/ch04.html
[2]: https://www.w3.org/standards/
[3]: https://wayland.app/protocols/wayland
[4]: https://wayland.app/protocols/
[5]: https://github.com/ricotz/plank
[6]: https://github.com/KDE/latte-dock
[7]: https://wayland-book.com/xdg-shell-in-depth/interactive.html
[8]: https://gitlab.freedesktop.org/wlroots/wlroots
[9]: https://swaywm.org/
[10]: https://wayland.app/protocols/wlr-layer-shell-unstable-v1
[11]: https://wayland.app/protocols/xdg-decoration-unstable-v1
[12]: https://github.com/nwg-piotr/nwg-shell
[13]: https://github.com/WayfireWM/wf-shell
[14]: https://github.com/natpen/awesome-wayland
[15]: https://github.com/wmww/gtk-layer-shell
[16]: https://github.com/hamza-Algohary

42
sources/news/20220725 In light Of The Log4j Incident, Google Supports Calls For Better Open Source Security.md
View File

@ -1,42 +0,0 @@
[#]: subject: "In light Of The Log4j Incident, Google Supports Calls For Better Open Source Security"
[#]: via: "https://www.opensourceforu.com/2022/07/in-light-of-the-log4j-incident-google-supports-calls-for-better-open-source-security/"
[#]: author: "Laveesh Kocher https://www.opensourceforu.com/author/laveesh-kocher/"
[#]: collector: "lkxed"
[#]: translator: " "
[#]: reviewer: " "
[#]: publisher: " "
[#]: url: " "
In light Of The Log4j Incident, Google Supports Calls For Better Open Source Security
======
![google][1]
In response to recent recommendations from the US government to take action against risks connected to the Log4j vulnerability, Google said it supports the advisories and detailed its own defence strategy. In a recent assessment on the Log4j vulnerability, the U.S. Department of Homeland Security (DHS) asked the entire sector to band together and strengthen cybersecurity precautions, warning that it might remain undetected on unpatched endpoints for up to 10 years.
“We welcome the U.S. Government’s work to improve the nation’s cybersecurity, including through establishment of the CSRB to review incidents like log4j,” Google said in a [blog post][2].
The report, among other things, provided three recommendations for the industry’s future actions: promoting the adoption of best practises; improving the software ecosystem; and making long-term investments in digital security. Google stated that it will continue to make security a “cornerstone of our product strategy” and that it will share its internal frameworks and best practises with others in order to advance current security hygiene best practises.
In an effort to spur industry-wide discussion and advancement on the security and sustainability of the open-source ecosystem, the company stated “We partner closely with industry stakeholders to identify and address vulnerabilities in the ecosystem, and share best practises on how to address the latest security threats”.
When it comes to creating a better software environment, Google sees itself as a market leader, claiming that it promotes, instigates, and funds initiatives and programmes that allow everyone to participate in and contribute to the global open source ecosystem.
And lastly, Google has significant investment intentions for the future. It promised a $10 billion investment in cybersecurity last year that will span five years and include a $100 million investment in outside organisations like OpenSSF.
“We welcome the chance to participate in future review board processes, and look forward to working alongside others to continue to protect the nation’s software supply chain ecosystem,” the announcement concludes. “It’s clear that public and private sector stakeholders learned a great deal from log4j and the report provides an in-depth review of shared challenges and potential solutions. Now, we must act on those learnings to improve the security of the entire ecosystem.”
--------------------------------------------------------------------------------
via: https://www.opensourceforu.com/2022/07/in-light-of-the-log4j-incident-google-supports-calls-for-better-open-source-security/
作者：[Laveesh Kocher][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.opensourceforu.com/author/laveesh-kocher/
[b]: https://github.com/lkxed
[1]: https://www.opensourceforu.com/wp-content/uploads/2022/07/google-e1658741796206.jpg
[2]: https://cloud.google.com/blog/products/identity-security/google-supports-csrb-call-improve-open-source-security

124
sources/news/20220801 Linus Torvalds Uses Apple MacBook Hardware to Release Linux Kernel 5.19.md
View File

@ -1,124 +0,0 @@
[#]: subject: "Linus Torvalds Uses Apple MacBook Hardware to Release Linux Kernel 5.19"
[#]: via: "https://news.itsfoss.com/linux-kernel-5-19-release/"
[#]: author: "Jacob Crume https://news.itsfoss.com/author/jacob/"
[#]: collector: "lkxed"
[#]: translator: " "
[#]: reviewer: " "
[#]: publisher: " "
[#]: url: " "
Linus Torvalds Uses Apple MacBook Hardware to Release Linux Kernel 5.19
======
Linux Kernel 5.19 is introducing support for a new CPU architecture, along with improvements for next-gen components from Intel and AMD.
![linux kernel][1]
Three months after the [last kernel release][2], Linux Kernel 5.19 is finally here. This exciting release brings plenty of improvements to every aspect of the kernel and opens up opportunities with new hardware.
The most interesting part is that the Linux creator Linus Torvalds used an Apple MacBook, the Arm version, to announce this release.
Don’t get your pitchfork out just yet. Torvalds used [Asahi Linux][3], a project dedicated to adding Linux support to Apple’s Arm-based Silicon Macbooks.
> On a personal note, the most interesting part here is that I did the release (and am writing this) on an arm64 laptop. It’s something I’ve been waiting for for a *loong* time, and it’s finally reality, thanks to the Asahi team. We’ve had arm64 hardware around running Linux for a long time, but none of it has really been usable as a development platform until now.
That’s interesting. And this is the [third time][4] Torvalds used Apple hardware for Linux development.
### Linux Kernel 5.19: What’s New?
As with all previous releases, Linux Kernel 5.19 has a lot of technical changes. However, there are only a few major ones that will have a direct impact on users, so we will focus on those here.
If you are interested in all the low-level code changes, you can refer to the official changelog.
#### LoongArch CPU Architecture Support
Over the past few years, it has been interesting to see Chinese chip manufacturers attempt to catch up to Intel and AMD. One way they have tried to do this is by creating their architectures, which are generally compatible with existing architectures.
One of the more successful of these companies is **Loongson**. However, due to their new architecture, the software support for these CPUs was pretty limited.
Starting with this release, these CPUs have initial support (it won’t work for booting) and will likely soon have packages ported to them.
We should see more progress on this with Linux Kernel 5.20.
#### 32-bit RISC-V Apps on 64-bit RISC-V
As has been the case for the recent releases, Linux Kernel 5.19 greatly improves support for the open-source RISC-V architecture. This time, this comes in the form of allowing 32-bit RISC-V apps to run on 64-bit RISC-V systems.
Very few 32-bit RISC-V CPUs can run Linux, meaning very few Linux packages are designed for them. And those packages already have 64-bit counterparts.
Even if its usefulness is limited, it is good to see RISC-V being treated as a first-class architecture and getting more improvements to bring it closer to mainstream feasibility.
#### Improved Arc Alchemist Support
It’s no surprise that Intel’s initial Arc Alchemist GPU launch is a disaster so far, Linux Kernel 5.19 is the first release where you could assume these GPUs are usable on Linux.
This release finally brings compute support to the Linux kernel. It is somewhat surprising this code was not merged earlier, but at least the support exists now.
The other major Arc improvement is significantly better power management. This comes in the form of a small tweak in Linux’s PCIe subsystem that treats the Arc GPUs as unlimited, enabling PCI Express Active State Power Management in far more configurations.
In essence, this change means that the GPU can now be put into an extremely low power mode when not in use, yielding some significant power savings.
#### Improved ARM SoC Support
This release brings support to several new ARM SoCs. This time around, 7 new SoCs have been added to the list, specifically:
* Renesas RZ/G2UL (R9A07G043)
* Renesas RZ/V2M (R9A09G011)
* Renesas R-Car V4H (R8A779G0)
* Broadcom BCM47622
* Corstone1000
* Mediatek MT8195 (Kompanio 1200)
* NXP i.MXRT1050
In addition, Apple’s M1 chip also gained some improved support. This comes from a new driver for the on-chip NVMe controller. Now, users wanting to be able of NVMe storage on their Apple Silicon Macs are able to do so, thanks to the contribution by the Asahi Linux project.
#### Significantly Reduced Boot Times For Azure VMs
Azure users, you are in for a good improvement. Thanks to a contribution by Microsoft, Azure VMs using multiple GPUs can have as many as 3 minutes shaved off their boot times!
To achieve this, Microsoft changed their PCI Hyper-V driver to avoid setting “PCI_COMMAND_MEMORY”, which stops the driver sending/receiving heaps of unnecessary data from each GPU, saving around 14 seconds of boot time per GPU.
### Other Changes
In addition to the ones I mentioned above, Linux Kernel 5.19 also includes
* Raspberry Pi Sense Hat joystick driver
* Various BTRFS improvements
* New Intel IFS driver
* Intel Raptor Lake P graphics support.
* Alder lake improvements.
* Initial support for AMD RDNA3 graphics.
* Performance optimizations as reported by [Phoronix][5].
Overall, these changes make up for a pretty decent release. Although there aren’t any major changes, Linux Kernel 5.19 continues to build on the great work of the past few Linux releases.
### How to Install Linux Kernel 5.19?
If you are using Arch Linux or Fedora, you can easily upgrade shortly. But, if you are using other Linux distributions (Pop!_OS can be an exception to some extent), you may not receive an upgrade.
So, if you are feeling adventurous (and know what you are doing), you can find the newer kernel listed on [Linux Kernel Archives][6]. You can download the [tarball][7] to test it out.
However, we recommend waiting for your Linux distribution to push an update if you do not want to take any chances. It is best to stick to what’s being offered for your Linux distribution by default.
[Linux Kernel Archives][8]
--------------------------------------------------------------------------------
via: https://news.itsfoss.com/linux-kernel-5-19-release/
作者：[Jacob Crume][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/jacob/
[b]: https://github.com/lkxed
[1]: https://news.itsfoss.com/wp-content/uploads/2022/07/linux-kernel-5-19-released.jpg
[2]: https://news.itsfoss.com/linux-kernel-5-18-release/
[3]: https://news.itsfoss.com/asahi-linux-alpha/
[4]: https://lore.kernel.org/lkml/CAHk-=wgrz5BBk=rCz7W28Fj_o02s0Xi0OEQ3H1uQgOdFvHgx0w@mail.gmail.com/T/#u
[5]: https://www.phoronix.com/news/Linux-5.19-Features
[6]: https://www.kernel.org/
[7]: https://git.kernel.org/torvalds/t/linux-5.19.tar.gz
[8]: https://www.kernel.org/

189
sources/tech/20220719 Top 10 Features of Linux Mint 21 -Vanessa-.md
View File

@ -1,189 +0,0 @@
[#]: subject: "Top 10 Features of Linux Mint 21 “Vanessa”"
[#]: via: "https://www.debugpoint.com/linux-mint-21-features/"
[#]: author: "Arindam https://www.debugpoint.com/author/admin1/"
[#]: collector: "lkxed"
[#]: translator: "robsean"
[#]: reviewer: " "
[#]: publisher: " "
[#]: url: " "
Top 10 Features of Linux Mint 21 “Vanessa”
======
We round up the top features of the upcoming Linux Mint 21 “Vanessa”. Find out what’s in store for you.
![Linux Mint 21 Cinnamon Desktop][1]
Linux Mint 21 “Vanessa” is the 36th release of [Linux Mint][2], which carries a good list of features along with several usability improvements across the desktop. The features are scattered across the Cinnamon desktop, core changes, Xapps updates and more.
I have summarized all of them in this list of top features of Linux Mint 21.
### Top Features of Linux Mint 21 “Vanessa”
#### 1. Ubuntu 22.04 and associated updates
Perhaps the most crucial change is the base of Linux Mint 21, which is now based upon [Ubuntu 22.04 “Jammy Jellyfish”][3]. The last major release, i.e. Linux Mint 20 “Ulyana”, was based on Ubuntu 20.04 “Focal Fossa”, when released four years back. The state of the world in 2020 was utterly different, considering everything going on.
Hence, a lot of packages, version upgrades, and new performance improvements – all these under-the-hood updates come to Linux Mint 21. That includes the latest LTS [Linux Kernel 5.15][4], which brings further hardware lineup support, and toolchain updates for programming, development and networking.
#### 2. Major changes in the Timeshift backup tool
A few months back, the Mint team [announced][5] that they are taking over the development of the popular backup tool Timeshift and continuing its development as a “XApps”. So, this is a significant change. Why, may you ask?
Well, the developer of the Timeshift tool, Tony George, is busy with other projects. You may have heard about “[TeeJeeTech][6]” apps for Linux. It was created by Tony and had some cool apps. However, he doesn’t have the time to concentrate on Timeshift development and enhancement.
![Timeshift creating snapshot][7]
With that said, since Linux Mint now maintains it, some new features land in this release, such as Timeshift now determining how much disk space you need for the next backup in rsync mode (not in btrfs mode). In addition, it stops the backup process if it seems the disk space is less than 1 GB after the backup.
#### 3. WebP Support
WebP image is a reasonably new image format created by Google for the web. It beings better compression and reduced size while maintaining good quality than traditional JPEG or PNG images.
WebP support (view images, thumbnail or edit) in Linux Desktop requires some [additional installation][8] of packages. Looking at the popularity Linux Mint team brings out-of-the-box WebP support across the desktop apps and flavours.
That means Nemo file manager can show thumbnails of WebP images and view them in xviewer. The mint team always think about the end-user first because other distros are still behind on supporting WebP by default, such as Ubuntu, etc. Not only that, the new app [xapp-thumbnailers][9] now helps Nemo file manager to preview additional file types as well:
* ePub
* MP3 with Album Arts
* RAW Images
* AppImage
#### 4. Process Monitor
A small but handy tool called process monitor will give you a heads-up on what’s happening in your system. This little icon at the system tray shows up when your system is undergoing automatic updates or backup by TImeshift. In those situations, your system may become slow, and this nifty icon can show you why.
#### 5. Improved printing support
Linux Mint is well equipped for devices, and the printer supports it by default. This edition of Mint brings [Internet Printing Protocol (IPP)][10] for driverless printing and scanning.
In addition, HP’s driver, HPLIP’s latest edition (3.21.12), is also installed by default.
All these changes streamline printer and scanner usage. And users like you can enjoy effortless printing and scanning. It is such an essential aspect of a Linux distro, but it doesn’t work all the time. While [reviewing many distros][11], I found many fails to detect the printers or even print.
It’s good to see that the mint team contributed to this critical functionality.
#### 6. Window Animation updates
There are some considerable changes come in the Window and desktop animation effects. Firstly, the Effects settings for Windows and desktop are merged now. Earlier, there were separate sections which gave more granular control of the animations.
Here’s a side-by-side view.
![][12]
![][13]
Secondly, the mapping windows and desktop effects options are removed.
Third, a new control arrives to change the overall animation speed from slower to faster.
Finally, a global switch to disable or enable all the animation on the entire desktop gives you the option for more control.
I believe this is a well-designed dialog and advanced options for better clarity.
#### 7. Mutter rebase
Let’s talk about [Cinnamon desktop version 5.4][14], which comes with Linux Mint 21. It’s the latest Cinnamon release, and Mint is the first distro to bring it to the user (other than traditional Arch Linux folks, who got it [a little early][15]).
Finally, the team completed the rebase of Mutter into its window manager, Muffin in Cinnamon 5.4. Since Muffin was initially forked from Mutter, it was always lagging behind the upstream Mutter features, despite the backporting of changes. A significant amount of effort went to feature inclusion, bug fixes & clean up to make Muffin as close to the Mutter code base.
Hence, in the future, it is now easier to port back changes from Mutter upstream and clean things in Muffin as needed.
#### 8. Window manager and GTK Themes
With the changes in Muffin, the team also moved some of the display settings from gnome-control-center to cinnamon-control-center. In addition, the display configs from csd-xrandr moved into the Muffin window manager in Cinnamon 5.4. Apparently, you may not see any difference in the Display settings window. However, you may see some performance boost and fewer bugs or issues while scaling displays or in high-res windows.
Another critical change that the Mint team introduced via CInnamon 5.4 is the uniform render of GTK dialogs in apps. Earlier, if a GTK app used a header bar, then the dialog was a mix of CSD (client side decoration) and GTK themes.
Now with Cinnamon 5.4, all the windows are rendered using the GTK theme irrespective of their design. And with that, the legacy Metacity themes also dropped.
On a side note, I loved the Metacity, and its “legacy look” when [they were a thing][16] in the early days of GNOME.
#### 9. Package Management updates
Following the trends of Debian, KDE Plasma desktop, Linux Mint also protects your system from uninstalling critical dependent packages.
When you try to uninstall, Mint now checks the dependencies and whether critical desktop packages will be removed.
If found, you get an error message that stops you from going further.
On the other hand, when you successfully uninstall a package, it cleans up all the dependencies with it installed.
#### 10. Disable the Systemd OOMD (out-of-memory daemon) service
The “systemd-oomd” had some bad feedback recently since the Ubuntu 22.04 LTS release. Users across the web [reported][17] the sudden closing of applications (such as Firefox) without any warning or user intervention. Further investigation pointed to the “not so well” implementation of the systemd-oomd service.
In theory, the [systemd-oomd.service][18] monitors your system for out-of-memory situations, and it has the authority to kill any processes which consume more system resources. Ubuntu team did not communicate this with importance, which eventually led to an unpleasant user experience.
With that knowledge, Linux Mint 21 decides [not to feature][19] this service and disables it. Because the user base of Linux Mint is general users, students, etc., it would be a bad experience for users if apps closed unexpectedly.
![Systemd OOMD service is not enabled][20]
#### 11. Other Changes
Finally, let’s round up some tiny yet impactful changes to wrap up the Linux Mint 21 features.
* The default document reader app Xreader is now capable of minor annotation. This is a handy feature.
* The WebApp manager now brings custom browser parameters.
* Warpinator file transfer utility now shows you other sources on Windows, Android and iOS devices.
* Mint packages Firefox web browser as deb and not the Snap version, which defaults in Ubuntu 22.04 LTS. Thanks to Mint team, users need not worry about the [complex set of commands][21] to remove the Firefox Snap from Jammy.
![Firefox 102 in Linux Mint 21 – Exclusively packaged as deb executable][22]
* The bulk renamer app Thingy gets some UI improvements.
* The os-prober of GRUB2 is now available to detect all the operating systems in your hardware (handy for dual boot or more systems).
* The Bluetooth manager Blueman replaces Blueberry, bringing additional features for connecting and managing your Bluetooth devices.
* Finally, new wallpapers for your new desktop arrive in this release.
![New Wallpapers in Linux Mint 21][23]
### Things that are NOT changing
From a very high level, you might feel that most of the Linux Mint 21 remains the same as its predecessors. The default desktop looks and default wallpaper remains the same. Xfce and MATE desktop didn’t have any major releases. Hence they are precisely the same. In addition, the default icon theme, application menu, etc., may give you a similar feel to the entire desktop.
### Wrapping Up
Overall, a good set of features is beneficial for end users rather than being fancy gestures and stuff. For this very fact, Linux Mint is the best Linux distro today for beginners or end users. So, that concludes the feature highlights of Linux Mint 21.
The BETA testing is in progress, and there are a [few bugs reported][24]. The final release is due soon, within a few weeks from now.
You can download/update to Linux Mint 21 when released. Also, stay tuned for our detailed distro review of Linux Mint 21 after the official release.
What do you think about the new features of Linux mint 21? Is there any feature you expected but didn’t arrive in this release? Let’s discuss this in the comment box below.
--------------------------------------------------------------------------------
via: https://www.debugpoint.com/linux-mint-21-features/
作者：[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/07/Linux-Mint-21-Cinnamon-Desktop.jpg
[2]: https://www.debugpoint.com/linux-mint/
[3]: https://www.debugpoint.com/web-stories/ubuntu-22-04-review/
[4]: https://www.debugpoint.com/linux-kernel-5-15/
[5]: https://blog.linuxmint.com/?p=4323
[6]: https://teejeetech.com/
[7]: https://www.debugpoint.com/wp-content/uploads/2022/07/Timeshift-creating-snapshot.jpg
[8]: https://www.debugpoint.com/view-webp-ubuntu-linux/
[9]: https://github.com/linuxmint/xapp-thumbnailers
[10]: https://datatracker.ietf.org/doc/html/rfc8011
[11]: https://www.debugpoint.com/tag/linux-distro-review/
[12]: https://www.debugpoint.com/wp-content/uploads/2022/07/Effects-in-Linux-Mint-20.jpg
[13]: https://www.debugpoint.com/wp-content/uploads/2022/07/Effects-in-Linux-Mint-21.jpg
[14]: https://github.com/linuxmint/cinnamon-desktop/releases/tag/5.4.0
[15]: https://www.debugpoint.com/cinnamon-arch-linux-install/
[16]: https://www.debugpoint.com/gnome-classic-ubuntu-22-04/
[17]: https://askubuntu.com/questions/1404888/how-do-i-disable-the-systemd-oom-process-killer-in-ubuntu-22-04
[18]: https://www.freedesktop.org/software/systemd/man/systemd-oomd.service.html
[19]: https://debugpointnews.com/linux-mint-21-systemd-oom/
[20]: https://www.debugpoint.com/wp-content/uploads/2022/07/Systemd-OOMD-service-is-not-enabled.jpg
[21]: https://www.debugpoint.com/remove-firefox-snap-ubuntu/
[22]: https://www.debugpoint.com/wp-content/uploads/2022/07/Firefox-102-in-Linux-Mint-21-Exclusively-packaged-as-deb-executable.jpg
[23]: https://www.debugpoint.com/wp-content/uploads/2022/07/New-Wallpapers-in-Linux-Mint-21.jpg
[24]: https://github.com/linuxmint/mint21-beta/issues

100
sources/tech/20220802 Pandas- The Popular Python Library for Data Analysis and Data Science.md Normal file
View File

@ -0,0 +1,100 @@
[#]: subject: "Pandas: The Popular Python Library for Data Analysis and Data Science"
[#]: via: "https://www.opensourceforu.com/2022/08/pandas-the-popular-python-library-for-data-analysis-and-data-science/"
[#]: author: "Phani Kiran https://www.opensourceforu.com/author/phani-kiran/"
[#]: collector: "lkxed"
[#]: translator: " "
[#]: reviewer: " "
[#]: publisher: " "
[#]: url: " "
Pandas: The Popular Python Library for Data Analysis and Data Science
======
*Pandas is a popular Python library. This article describes a few features and functions available in this library, and encourages readers to use it for practical business problems.*
Pandas provides fundamental and high-level building blocks for practical, real world data analysis in Python. It is one of the most powerful and flexible open source tools for data analysis and manipulation, and provides data structures for modelling and manipulating tabular data (data in rows and columns).
Pandas has two primary data structures. The first is a ‘series’ data structure that helps to retrieve data from the array or dictionary of Python objects. Data can be retrieved either by position or by specifying the index name. The second is the ‘dataframes’ data structure to store data in rows and columns. Columns have column names and rows are accessed using indexes. Columns can have different types of data including lists, dictionaries, pandas series, another dataframe, NumPy arrays, etc.
### Processing various file types
Data is often available in various formats. It is imperative that the tool used for data analysis is able to provide a wide range of methods for handling it.
With Pandas, one can read various file types like CSV, JSON, XML, Parquet, SQL (see Table 1).
| | Write | Read |
| :- | :- | :- |
| CSV | to_csv | read_csv |
| JSON | to_json | Read_json |
| Parquet | to_parquet | read_parquet |
| SQL | to_sql | read_sql, read_sql_query, read_sql_table |
| XML | to_xml | read_xml |
### Data cleansing using Pandas
In real-world scenarios, data is often incomplete and includes bad data. It is sometimes duplicated. Also, data includes sensitive and confidential information, which needs to be masked. Pandas offers ways to handle bad data by using methods like cleaning, dropping, replacing, masking, etc.
a.  Empty rows can be removed with the *df.dropna(inplace=True)* operation.
b.  Empty values can be replaced with *df.fillna(<value>, inplace=True)*. We can specify the column name to be placed in a particular column.
c. You can mask the values for sensitive and non-public data for all items NOT satisfying the condition *my_list.where(my_list < 5)*. Masking of values satisfying the condition can be done with*my_list.mask(my_list < 5)*.
d. Duplicates can be dropped from a dataframe using:
```
df.drop_duplicates(‘<column>’, keep = False)
df.drop_duplicates(‘<column>’, keep = ‘first’)
df.drop_duplicates(‘<column>’, keep = ‘last’)
```
### Data analysis using Pandas
Table 2 lists the various functions in Pandas that perform data analysis as well as the syntax for usage. (Note: df stands for dataframe.)
| Function | Description | Syntax |
| :- | :- | :- |
| Head | Head() function returns the first five rows | df.head(x) |
| tail | tail() function returns the last five rows by default | df.tail(x) |
| Loc | Loc function returns a particular row. Slicing of the data is also possible | loc(x:y) |
| Groupby | Groups data on a particular column | groupby(‘<column>’) |
| Sum | Sum of values in a particular column | df[‘column’].sum() |
| Mean | Average of values in a particular column | df[‘column’]. mean() |
| Min | Minimum value in a particular column | df[‘column’].min() |
| Max | Maximum value in a particular column | df[‘column’].max() |
| Sort | Sorts dataframe in a column | df.sort_values([‘column’]) |
| Size | Rows * columns | df.size |
| Describe | Describes details of the dataframe | df.describe |
| Crosstab | Creates a frequency tabulation of rows and columns | pd.crosstab(df[‘column1’], df[‘column2’], margins = True) |
| Duplicated | Returns True or False based on duplicate values in Column1 and Column2 | df.duplicated([column1, ‘column2’]) |
### Advantages of Pandas
* It supports multi-index (hierarchical index) used for easy analysis of data having a large number of dimensions.
* It supports the creation of pivot tables, stack and unstack operations.
* Categorical data containing finite values can be processed with Pandas.
* It supports grouping and aggregations.
* Sorting can be explicitly disabled.
* It supports filtering at both row-level (gets the rows satisfying the filter condition) and column-level (selects only the required columns).
* Helps in reshaping of data sets. You can also transpose the values of the array and convert to a List. When you are processing data using Python, you can convert the Pandas dataframe to a multi-dimensional NumPy array; the values member variable is used for this.
* Supports label-oriented slicing of data.
### The disadvantages
The code and syntax of Pandas is different from Python, which leads to a steep learning curve for some users. Also, a few concepts like three dimensional data are better handled in other libraries like NumPy.
Pandas really elevates the data analysis process in an efficient manner. Its compatibility with other libraries makes it very conducive for use in various scenarios.
--------------------------------------------------------------------------------
via: https://www.opensourceforu.com/2022/08/pandas-the-popular-python-library-for-data-analysis-and-data-science/
作者：[Phani Kiran][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.opensourceforu.com/author/phani-kiran/
[b]: https://github.com/lkxed

190
translated/tech/20220719 Top 10 Features of Linux Mint 21 -Vanessa-.md Normal file
View File

@ -0,0 +1,190 @@
[#]: subject: "Top 10 Features of Linux Mint 21 “Vanessa”"
[#]: via: "https://www.debugpoint.com/linux-mint-21-features/"
[#]: author: "Arindam https://www.debugpoint.com/author/admin1/"
[#]: collector: "lkxed"
[#]: translator: "robsean"
[#]: reviewer: " "
[#]: publisher: " "
[#]: url: " "
Linux Mint 21 “Vanessa” 的 10 大顶级特色功能
======
我们总结了即将到来的 Linux Mint 21 “Vanessa” 的 10 大顶级特色功能。找出为你准备了什么。
![Linux Mint 21 Cinnamon Desktop][1]
Linux Mint 21 “Vanessa” 是 [Linux Mint][2] 的第 36 个发布版本，它带来了一份特色功能的列表和桌面上的一些有用改善。特色功能散落在 Cinnamon 桌面、内核更改、Xapps 更新等处。
我已经在这份 Linux Mint 21 顶级特色功能列表中总结出来了。
### Linux Mint 21 “Vanessa” 的顶级特色功能
#### 1. Ubuntu 22.04 及其相关更新
也许最重要的变化就是Linux Mint 21 的基础，它现在基于 [Ubuntu 22.04 “Jammy Jellyfish”][3] 。上一次的主要发布版本，例如 Linux Mint 20 “Ulyana” ，是基于四年前发布的 Ubuntu 20.04 “Focal Fossa” 。沧海桑田，2020 年的世界状态与现在完全不同。
因此，很对软件包、版本升级、新的性能改善 – 所有的这些底层更新都涉及到了 Linux Mint 21 。这包括最新的 LTS [Linux Kernel 5.15][4] ，这带来了更多硬件系列的支持、以及针对编程、开发和网络的工具链的更新。
#### 2. Timeshift 备份工具的主要变化
几个月前，Mint 开发组 [宣布][5] ：他们正在接管著名的备份工具 Timeshift 的开发，并将其继续开发为一个 “XApps” 。因此，这是一个重要的变化。为什么，你可能会询问？
好吧，Timeshift 工具的开发组，Tony George ，正忙于其它的项目。你可能听说过针对于 Linux 的 “[TeeJeeTech][6]” 应用程序。它是由 Tony 创建的，并且有一些很快的应用程序。因此，他没有足够多的时间来专注于 Timeshift 的开发和增强。
![Timeshift creating snapshot][7]
话虽如此，不过，现在有了 Linux Mint 来维护它，一些新的特色功能出现在这个发布版本之中，例如，Timeshift 现在可以在 rsync 模式 (而非 btrfs 模式) 下准确计算出下一次备份时所需要的磁盘空间。此外，如果它看到磁盘空间在备份后小于 1 GB ，它将会停止备份过程。
#### 3. WebP 支持
WebP 图像是谷歌针对网络创建的一种相当新的图像格式。It beings better compression and reduced size while maintaining good quality than traditional JPEG or PNG images.
在 Linux 桌面中支持 WebP (查看图像、缩略图或编辑) 需要一些 [额外安装][8] 的软件包。看着流行的 Linux Mint 开发组在桌面应用程序和衍生程序上带来开箱即用的 WebP 支持
这意味着，在 Nemo 文件管理器中可以显示 WebP 图像的缩略图，并可以在 xviewer 中查看它们。mint 开发组总是优先考虑最终用户的处境，这是因为其它的发行版仍然不默认支持 WebP ，例如 Ubuntu 等等。不仅如此，新的应用程序 [xapp-thumbnailers][9] 现在还能帮助 Nemo 文件管理器来预览文件类型：
* ePub
* 带有专辑封面的 MP3
* RAW 图像
* AppImage
#### 4. 进程监视器
一个名称为 <ruby>进程监视器<rt> process monitor</rt></ruby> 的小巧方便的工具，将会告知你，在你的系统中正在发生什么。在你的系统正在通过 Timeshift 来自动更新或备份时，在系统托盘处的这个小图标将会显示。在这些情况下，你的系统可能会变慢，这些漂亮的图标可以告诉你答案。
#### 5. 改善打印支持
Linux Mint 针对硬件设备配置了各种驱动程序，默认情况下就支持打印机。 这个版本的 Mint 带来 [<ruby>网络打印协议<rt>Internet Printing Protocol (IPP)</rt></ruby>][10] ，可以无线驱动打印机和扫描仪。
另外，也默认安装了 HP 的启动程序 HPLIP 的最新版本 (3.21.12) 。
所有的这些变化都提高了打印机和扫描仪的使用效率。像你这样的最终用户可以轻松地享受打印和扫描。它是一个 Linux 发行版的一个重要的方面，但是它并不是总是有效的。在 [评价很多发行版][11] 时，我发现很多发行版不能自动地检测出打印机，甚至不能使用打印机。
很高兴看到 mint 开发组贡献这个重要的功能。
#### 6. 窗口动画更新
在窗口和桌面动画效果中有一些相当大的变化。第一，现在合并了窗口和桌面的效果设置。先前，效果设置是一些单独的组区，可以对动画进行微观化的控制。
这里是并排对比视图。
![][12]
![][13]
第二，移除了映射窗口和桌面效果选项。
第三，带来一个新的控件，用于更改整体动画的快慢速度。
最后，一个禁用或启用在整个桌面上的所有动画的全局开关，给予你更多的控制选项。
我相信这是一个精心设计的对话框和一些更简洁清晰的高级选项。
#### 7. Mutter 重新构建
让我们讨论一下 [Cinnamon 桌面环境版本 5.4][14] ，它随 Linux Mint 21 而来。它是最新的 Cinnamon 发布版本，Mint 是第一个将其带给用户的的发行版 (而不是传统观念上的 Arch Linux 用户，他们要获取它还有 [一点早][15]) 。
最后，开发者对其窗口管理器 Mutter 完成了重新构建，在 Cinnamon 5.4 中是 Muffin 。即使有一些后期移植的变化，但是由于 Muffin 的原始版本是从 Mutter 复刻出来的，所以它总是落后于上游的 Mutter 特色功能。为使尽可能地接近 Mutter 代码基础。在包含的特色功能、错误修复及清理方面付出了大量的努力。
因此，在未来，在 Muffin 需要的时候很容易从 Mutter 上游移植回来和清理东西。
#### 8. 窗口管理器和 GTK 主题
伴随着 Muffin 的变化，开发组也将 gnomes 控制中心的一些显示设置移动到了 cinnamon 控制中心。此外，在 Cinnamon 5.4 中，也来自 csd-xrandr 的显示配置移动到了 Muffin 窗口管理器。很显然，你不可能在显示设置窗口中看任何的差异。不过，在缩放显示或在高分辨率窗口中时，你可能会看到一些性能的提升和更少的错误或重大问题。
另外一个重大的变化，Mint 开发组通过 Cinnamon 5.4 来尝试在应用程序中实现 GTK 窗口的统一渲染。先前，如果一个 GTK 应用程序使用一个标题栏，那么对话框会是一个 CSD (客户端样式) 和 GTK 主题的混合体.
现在随着 Cinnamon 5.4 的到来，使用的窗口都使用 GTK 主题进行渲染，而不再与它们的设计相关联。于是，传统的 Metacity 主题也被抛弃。
顺便说一句，我喜欢 Metacity 及其 “传统外观” ，在 GNOME 的早期时 [它们是一种东西][16] 。
#### 9. 软件包管理器更新
遵循 Debian、KDE Plasma 桌面的发展趋势，Linux Mint 也开始保护你的系统不会卸载重要的依赖关系软件包。
当你尝试卸载时，Mint 现在会检查依赖关系，并检查重要的桌面软件包是否将会被移除。
如果发现这种情况，你将会得到一条阻止你继续卸载软件包的错误信息。
在另一方面，当成功地卸载一个软件包时，它会清理所有与之同时安装的依赖关系软件包。
#### 10. 禁用 Systemd OOMD (内存溢出守护进程) 服务
自从 Ubuntu 22.04 LTS 发布以来，<ruby>系统内存溢出守护进程<rt>systemd-oomd</rt></ruby>” 有一些不好的反馈。访问网络的用户 [报告][17] ：在没有任何警告或用户交互干涉的情况下，会突然关闭应用程序 (例如 Firefox) 。进一步的调查指明是系统内存溢出守护进程服务的实现“不如预期的好”。
按照理论上来说，[systemd-oomd.service][18] 监视你的系统的内存溢出情况，并且它有权杀死任何多过消耗系统资源的进程。Ubuntu 开发组并没有重要地强调这一点，最后导致了不愉快的用户的体验。
有了这些经验，Linux Mint 21 决定 [不提供][19] 这种服务，并禁用它。因为 Linux Mint 的用户群体是普通用户、学生等等，如果应用程序意外关闭，对用户来说将是一种不好的体验。
![Systemd OOMD service is not enabled][20]
#### 11. 其它变化
最后，让我们归纳一些微小却富有冲击力的变化来总结 Linux Mint 21 特色功能。
* 默认文档阅读器应用程序 Xreader 现在能够进行少量的注释。这是一个很方便的特色功能。
* WebApp 管理器现在可以提供一些自定义的浏览器参数。
* Warpinator 文件传输器实用工具现在可以向你显示来自 Windows 、Android 和 iOS 设备上的其它的源文件。
* Mint 打包 Firefox 网络浏览器为 .deb 版本，而不是在 Ubuntu 22.04 LTS 中的默认 .Snap 版本。感谢 Mint 开发组，用户不必为卸载 Jammy 中的 Firefox 的 .Snap 版本的 [复杂命令集][21] 而忧心。
![Firefox 102 in Linux Mint 21 – Exclusively packaged as deb executable][22]
* 批量重命名应用程序 Thingy 获得一些用户界面上的改善。
* 操作系统侦察引导启动器 GRUB2 现在能够侦察出在你的硬件系统上所有的操作系统 (对双操作系统启动或多操作系统启动有用) 。
* 蓝牙管理器 Blueman 取代了 Blueberry ，为连接和管理你的蓝牙设备带来了其它的特色功能。
* 最后，为你的新桌面而准备的新壁纸也将在这个发布版本中到来。
![New Wallpapers in Linux Mint 21][23]
### 未变化的东西
从一个非常高的层次来看，你可能会觉着 Linux Mint 21 的绝大部分功能与先前的版本相同。默认桌面外观和默认壁纸保存相同。Xfce 和 MATE 桌面没有任何的重要功能的发布。因此，它们是完全一样的。此外，默认图标主题、应用程序菜单等等都可能会给你一种似曾相识燕归来的感觉。
### 总结
总体来说，最终用户需要的是一套完好的特色功能，而不是金玉其外败絮其中的东西。鉴如此，对初学者或最终用户来说，Linux Mint 是当今最好的 Linux 发行版。至此，Linux Mint 21 的特色功能就总结结束了.
正在进行 BETA 版本测试，这里有 [一些错误报告][24] 。最后的发布版本即将在未来几周内到来。
当发布后，你可以下载/更新到 Linux Mint 21 。此外，在官方发布后，也敬请期待我们对于 Linux Mint 21 的详细评价。
你认为 Linux mint 21 的新的特色功能怎么样？在这个发布版本中，是否有一些你所求而未得的特色功能？让我们在下面的评论区讨论这个问题。
--------------------------------------------------------------------------------
via: <https://www.debugpoint.com/linux-mint-21-features/>
作者：[Arindam][a]
选题：[lkxed][b]
译者：[robsean](https://github.com/robsean)
校对：[校对者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/07/Linux-Mint-21-Cinnamon-Desktop.jpg
[2]: https://www.debugpoint.com/linux-mint/
[3]: https://www.debugpoint.com/web-stories/ubuntu-22-04-review/
[4]: https://www.debugpoint.com/linux-kernel-5-15/
[5]: https://blog.linuxmint.com/?p=4323
[6]: https://teejeetech.com/
[7]: https://www.debugpoint.com/wp-content/uploads/2022/07/Timeshift-creating-snapshot.jpg
[8]: https://www.debugpoint.com/view-webp-ubuntu-linux/
[9]: https://github.com/linuxmint/xapp-thumbnailers
[10]: https://datatracker.ietf.org/doc/html/rfc8011
[11]: https://www.debugpoint.com/tag/linux-distro-review/
[12]: https://www.debugpoint.com/wp-content/uploads/2022/07/Effects-in-Linux-Mint-20.jpg
[13]: https://www.debugpoint.com/wp-content/uploads/2022/07/Effects-in-Linux-Mint-21.jpg
[14]: https://github.com/linuxmint/cinnamon-desktop/releases/tag/5.4.0
[15]: https://www.debugpoint.com/cinnamon-arch-linux-install/
[16]: https://www.debugpoint.com/gnome-classic-ubuntu-22-04/
[17]: https://askubuntu.com/questions/1404888/how-do-i-disable-the-systemd-oom-process-killer-in-ubuntu-22-04
[18]: https://www.freedesktop.org/software/systemd/man/systemd-oomd.service.html
[19]: https://debugpointnews.com/linux-mint-21-systemd-oom/
[20]: https://www.debugpoint.com/wp-content/uploads/2022/07/Systemd-OOMD-service-is-not-enabled.jpg
[21]: https://www.debugpoint.com/remove-firefox-snap-ubuntu/
[22]: https://www.debugpoint.com/wp-content/uploads/2022/07/Firefox-102-in-Linux-Mint-21-Exclusively-packaged-as-deb-executable.jpg
[23]: https://www.debugpoint.com/wp-content/uploads/2022/07/New-Wallpapers-in-Linux-Mint-21.jpg
[24]: https://github.com/linuxmint/mint21-beta/issues