mirror of
https://github.com/LCTT/TranslateProject.git
synced 2024-12-26 21:30:55 +08:00
Merge branch 'master' of https://github.com/LCTT/TranslateProject into translating
This commit is contained in:
commit
41244a61b5
@ -2,70 +2,73 @@
|
||||
[#]: via: "https://itsfoss.com/duckduckgo-easter-eggs/"
|
||||
[#]: author: "sreenath https://itsfoss.com/author/sreenath/"
|
||||
[#]: collector: "lkxed"
|
||||
[#]: translator: " "
|
||||
[#]: reviewer: " "
|
||||
[#]: publisher: " "
|
||||
[#]: url: " "
|
||||
[#]: translator: "TravinDreek"
|
||||
[#]: reviewer: "wxy"
|
||||
[#]: publisher: "wxy"
|
||||
[#]: url: "https://linux.cn/article-14696-1.html"
|
||||
|
||||
隐藏功能!在 DuckDuckGo 搜索引擎中,你可以做这 25 件有趣的事情
|
||||
======
|
||||
|
||||
![](https://img.linux.net.cn/data/attachment/album/202206/11/142806ebr5xtzgcwcr5955.jpg)
|
||||
|
||||
比起无处不在的 Google,[有些搜索引擎替代品更加尊重隐私][1],而 DuckDuckGo 就是其中之一。
|
||||
|
||||
最近,这个搜索引擎有了很大的改进,搜索一般网页十分顺畅。在搜索本地地点方面,则还远不及 Google。
|
||||
|
||||
不过,DuckDuckGo(其爱称为 DDG)有一些很酷的功能,大部分用户还没注意到。如果你是一位 DDG 狂热粉,你可能会喜欢用这些小技巧来提升你的搜索体验。
|
||||
不过,DuckDuckGo(简称为 DDG)有一些很酷的功能,大部分用户还没注意到。如果你是一位 DDG 狂热粉,你可能会喜欢用这些小技巧来提升你的搜索体验。
|
||||
|
||||
### 1. 跳转特定网页
|
||||
### 1、跳转到特定网页
|
||||
|
||||
在你最喜欢的网站名称前输入 ! 即可直接进入这个网站。则类似于 Google 的 “运气不错” 功能,但用 DDG 的话来说,这就叫 “叹号搜索”。
|
||||
在你最喜欢的网站名称前输入 `!` 即可直接进入这个网站。则类似于 Google 的 “运气不错” 功能,但用 DDG 的话来说,这就叫 “叹号搜索”。
|
||||
|
||||
网站有缩写,开始输入时便会提示。
|
||||
有一些网站有缩写形式,开始输入时便会提示。
|
||||
|
||||
![duckduckgo bang feature][2]
|
||||
|
||||
在网站名后面输入搜索词,就可以直接抵达那个网站的搜索结果处。
|
||||
|
||||
### 2. 文本转 ASCII
|
||||
### 2、文本转 ASCII
|
||||
|
||||
Figlet 是一个[有趣的 Linux 命令][3],可以将任意文本转换为漂亮的 ASCII 画格式。
|
||||
Figlet 是一个 [有趣的 Linux 命令][3],可以将任意文本转换为漂亮的 ASCII 画格式。
|
||||
|
||||
在任意搜索词前输入 **figlet**,就会显示 ASCII 输出。无需打开终端。
|
||||
在任意搜索词前输入 `figlet`,就会显示 ASCII 输出。无需打开终端。
|
||||
|
||||
![Figlet in DDG][4]
|
||||
|
||||
### 3. 检查社交媒体的状态
|
||||
### 3、检查社交媒体的状态
|
||||
|
||||
在某个人的 Twitter 名前加上 ‘@’,就会显示 TA 的状态(关注者等)。
|
||||
在某个人的 Twitter 名前加上 `@`,就会显示 TA 的状态(关注者等)。
|
||||
|
||||
![Itsfoss Twitter][5]
|
||||
|
||||
### 4. 生成强密码
|
||||
### 4、生成强密码
|
||||
|
||||
输入 ‘password’ 并加上需要的字符数,就可以生成一个独特的强密码。
|
||||
输入 `password` 并加上需要的字符数,就可以生成一个独特的强密码。
|
||||
|
||||
![Generating password in DuckDuckGo][6]
|
||||
|
||||
### 5. 生成随机密码短语
|
||||
### 5、生成随机密码短语
|
||||
|
||||
输入 ‘random passphrase’ 可生成一段密码短语,通常长度为 4 个词。
|
||||
输入 `random passphrase` 可生成一段密码短语,通常长度为 4 个词。
|
||||
|
||||
![Random Passphrase][7]
|
||||
|
||||
### 6. 获取一份速查表
|
||||
### 6、获取一份速查表
|
||||
|
||||
在需要看速查表的搜索词后面,可输入 cheatsheet。如果要搜索的东西有速查表,就会立即显示在搜索页面。
|
||||
在需要看速查表的搜索词后面,可输入 `cheatsheet`。如果要搜索的东西有速查表,就会立即显示在搜索页面。
|
||||
|
||||
![Vim Cheatsheet][8]
|
||||
|
||||
### 7. 通过色码获取颜色
|
||||
### 7、通过色码获取颜色
|
||||
|
||||
输入 ‘color’ 并加上你想查的颜色的十六进制码,便可显示这个颜色。
|
||||
输入 `color` 并加上你想查的颜色的十六进制码,便可显示这个颜色。
|
||||
|
||||
![Color][9]
|
||||
|
||||
### 8. 生成随机数
|
||||
### 8、生成随机数
|
||||
|
||||
搜索 ‘random number’ 会输出一个 0 到 1 之间的随机数。
|
||||
搜索 `random number` 会输出一个 0 到 1 之间的随机数。
|
||||
|
||||
![Random Number][10]
|
||||
|
||||
@ -73,113 +76,113 @@ Figlet 是一个[有趣的 Linux 命令][3],可以将任意文本转换为漂
|
||||
|
||||
![Random Number between 1 and 1000][11]
|
||||
|
||||
### 9. 转换为二进制等形式
|
||||
### 9、转换为二进制等形式
|
||||
|
||||
输入一个二进制数并加上 ‘binary’,可将其从二进制转换为十进制。
|
||||
输入一个二进制数并加上 `binary`,可将其从二进制转换为十进制。
|
||||
|
||||
![Binary to Decimal][12]
|
||||
|
||||
类似地,它也能用于十六禁止和八进制,但我不清楚它们的处理逻辑。
|
||||
类似地,它也能用于十六进制和八进制,但我不清楚它们的处理逻辑。
|
||||
|
||||
### 10. 寻找韵词
|
||||
### 10、寻找韵词
|
||||
|
||||
输入 ‘what rhymes with ’ 并带上要找同韵词的词语。作诗能力变强了,对吧?
|
||||
输入 `what rhymes with` 并带上要找同韵词的词语。作诗能力变强了,对吧?
|
||||
|
||||
![What rhymes with rain][13]
|
||||
|
||||
### 11. 获取拉马努金数、圆周率等常数
|
||||
### 11、获取拉马努金数、圆周率等常数
|
||||
|
||||
输入想获取数值的常数名,便可在搜索结果中看到它。
|
||||
|
||||
![Ramanujan Number][14]
|
||||
|
||||
### 12. 查询现在谁在太空中
|
||||
### 12、查询现在谁在太空中
|
||||
|
||||
输入 ‘people in space’ 获取当前在太空中的人员名单。同时还会显示他们在太空中居住的时间。
|
||||
输入 `people in space` 获取当前在太空中的人员名单。同时还会显示他们在太空中居住的时间。
|
||||
|
||||
![People in Space][15]
|
||||
|
||||
### 13. 查询网页是否无法访问
|
||||
### 13、查询网页是否无法访问
|
||||
|
||||
如果你想知道某个网站是你无法访问了,还是大家都无法访问了,只需在搜索词中输入 “is xyz.com down”。
|
||||
如果你想知道某个网站是你无法访问了,还是大家都无法访问了,只需在搜索词中输入 `is xyz.com down`。
|
||||
|
||||
![Is down?][16]
|
||||
|
||||
### 14. 获取特定话题的名言
|
||||
### 14、获取特定话题的名言
|
||||
|
||||
输入一个词并带上 quotes,就会显示与这个词相关的名言。
|
||||
输入一个词并带上 `quotes`,就会显示与这个词相关的名言。
|
||||
|
||||
![Get quotes in DDG][17]
|
||||
|
||||
### 15. 获取占位文本
|
||||
### 15、获取占位文本
|
||||
|
||||
搜索 ‘lorem ipsum’ 就可以获取 5 段占位文本。对 Web 开发者应该会有用。
|
||||
搜索 `lorem ipsum` 就可以获取 5 段占位文本。对 Web 开发者应该会有用。
|
||||
|
||||
![Lorem ipsum][18]
|
||||
|
||||
### 16. 获取任意月份的日历
|
||||
### 16、获取任意月份的日历
|
||||
|
||||
在年、月、日后面输入 calendar,就会为你显示该月份的交互式日历。
|
||||
在年、月、日后面输入 `calendar`,就会为你显示该月份的交互式日历。
|
||||
|
||||
![Calendar][19]
|
||||
|
||||
### 17. 生成二维码
|
||||
### 17、生成二维码
|
||||
|
||||
在文字、链接等后面输入 ‘qr’,就会生成对应的二维码。
|
||||
在文字、链接等后面输入 `qr`,就会生成对应的二维码。
|
||||
|
||||
![QRCode][20]
|
||||
|
||||
### 18. 获取一些 CSS 动画
|
||||
### 18、获取一些 CSS 动画
|
||||
|
||||
搜索 ‘css animations’ 以获取一些 CSS 动画例子。
|
||||
搜索 `css animations` 以获取一些 CSS 动画例子。
|
||||
|
||||
![CSS Animations][21]
|
||||
|
||||
### 19. 展开短链接
|
||||
### 19、展开短链接
|
||||
|
||||
如果有一个 Bitly 链接或其他短链接,但不确定它指向哪里,不必再跳转到充满垃圾信息的网页了,只需展开短链接,看看真正的网址。
|
||||
|
||||
在短链接后面输入关键词 expand,就会显示真正的目标 URL。
|
||||
在短链接后面输入关键词 `expand`,就会显示真正的目标 URL。
|
||||
|
||||
![Expand Link][22]
|
||||
|
||||
### 20. 获取特殊字符的 HTML 代码
|
||||
### 20、获取特殊字符的 HTML 代码
|
||||
|
||||
搜索 ‘html chars’,可以获取一份很长的列表,上面有 HTML 实体及其描述,按下后会在结果中显示更多信息。
|
||||
搜索 `html chars`,可以获取一份很长的列表,上面有 HTML 实体及其描述,按下后会在结果中显示更多信息。
|
||||
|
||||
![HTML Chars][23]
|
||||
|
||||
### 21. 我用这东西干啥?
|
||||
### 21、我用这东西干啥?
|
||||
|
||||
这功能没什么用。如果你输入 “why should I use this?” ,它就会在搜索结果顶部显示 “cause it's awesome”。显然,DuckDuckGo 在说他自己。
|
||||
这功能没什么用。如果你输入 `why should I use this?` ,它就会在搜索结果顶部显示 `cause it's awesome`。显然,DuckDuckGo 在说他自己。
|
||||
|
||||
![Why should I use this?][24]
|
||||
|
||||
### 22. 转换大小写
|
||||
### 22、转换大小写
|
||||
|
||||
大小写都可转换。lowercase <大写搜索词> 就会显示小写的结果
|
||||
大小写都可转换。`lowercase <大写搜索词>` 就会显示小写的结果
|
||||
|
||||
![Lowercase][25]
|
||||
|
||||
uppercase <小写搜索词> 就会显示大写的结果。
|
||||
`uppercase <小写搜索词>` 就会显示大写的结果。
|
||||
|
||||
![Uppercase][26]
|
||||
|
||||
### 23. 编码 URL
|
||||
### 23、编码 URL
|
||||
|
||||
搜索 ‘encode’ 并加上 URL,就会给出编码后的结果
|
||||
搜索 `encode` 并加上 URL,就会给出编码后的结果
|
||||
|
||||
![URL Encode][27]
|
||||
|
||||
### 24. Motherboard
|
||||
### 24、Motherboard
|
||||
|
||||
搜索 ‘Motherboard’就会看见左侧的 DuckDuckGo 的 logo 变了。它会显示选好的几个随机 logo。
|
||||
搜索 `Motherboard` 就会看见左侧的 DuckDuckGo 的 logo 变了。它会显示选好的几个随机 logo。
|
||||
|
||||
![Motherboard][28]
|
||||
|
||||
### 25. 获取 HTML 色码
|
||||
### 25、获取 HTML 色码
|
||||
|
||||
搜索 ‘color codes’ 便可获得一份颜色表。一样,这个功能多为 Web 开发者和设计师所用。
|
||||
搜索 `color codes` 便可获得一份颜色表。一样,这个功能多为 Web 开发者和设计师所用。
|
||||
|
||||
![Color Codes][29]
|
||||
|
||||
@ -196,7 +199,7 @@ via: https://itsfoss.com/duckduckgo-easter-eggs/
|
||||
作者:[sreenath][a]
|
||||
选题:[lkxed][b]
|
||||
译者:[Peaksol](https://github.com/TravinDreek)
|
||||
校对:[校对者ID](https://github.com/校对者ID)
|
||||
校对:[wxy](https://github.com/wxy)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译,[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
@ -3,45 +3,47 @@
|
||||
[#]: author: "James Kiarie https://www.linuxtechi.com/author/james/"
|
||||
[#]: collector: "lkxed"
|
||||
[#]: translator: "robsean"
|
||||
[#]: reviewer: " "
|
||||
[#]: publisher: " "
|
||||
[#]: url: " "
|
||||
[#]: reviewer: "wxy"
|
||||
[#]: publisher: "wxy"
|
||||
[#]: url: "https://linux.cn/article-14699-1.html"
|
||||
|
||||
如何双启动 Ubuntu 22.04 LTS 和 Windows 11
|
||||
======
|
||||
嗨,伙计们,在这篇指南中,我们将演示如何在 Windows 11 的旁侧配置 Ubuntu 22.04 LTS (Jammy Jellyfish) 的双启动设置
|
||||
|
||||
为使其能工作,你需要在你的计算机上安装 windows 11 。接下来,你将需要在你的硬盘驱动器上创建一个单独的分区,你将在此分区上安装 Ubuntu 22.04 。我们将包含这点知识,因此不要担心。
|
||||
![](https://img.linux.net.cn/data/attachment/album/202206/12/110546fff10ck07e2p0z2f.jpg)
|
||||
|
||||
##### 必要条件
|
||||
嗨,伙计们,在这篇指南中,我们将演示如何在 Windows 11 的之外配置 Ubuntu 22.04 LTS(Jammy Jellyfish)的双启动设置。
|
||||
|
||||
在设置双启动前,这些是你所需要的。
|
||||
为使其能工作,你需要在你的计算机上已经安装好了 Windows 11 。接下来,你将需要在你的硬盘驱动器上创建一个单独的分区,你将在此分区上安装 Ubuntu 22.04 。我们将包含这点知识,因此不要担心。
|
||||
|
||||
* 一个 Ubuntu 22.04 的可启动 USB 驱动器,你可以转到 [Ubuntu 22.04 下载页面][1] 来下载 Ubuntu 22.04 的 ISO 镜像文件。在 ISO 镜像文件到位后,抓取一个 16GB USB 驱动器,并使用 Rufus 应用程序来使其可启动。
|
||||
**前置条件:**
|
||||
|
||||
* 快速稳定的因特网连接
|
||||
在设置双启动前,这些是你所需要的:
|
||||
|
||||
* 一个 Ubuntu 22.04 的可启动 USB 驱动器,你可以转到 [Ubuntu 22.04 下载页面][1] 来下载 Ubuntu 22.04 的 ISO 镜像文件。在 ISO 镜像文件到位后,拿一个 16GB USB 驱动器,并使用 Rufus 应用程序来使其可启动。
|
||||
* 快速稳定的互联网连接
|
||||
|
||||
### 步骤 1、在你的硬盘驱动器上创建一个可用的分区
|
||||
|
||||
正如介绍中所提到的,我们首先需要在硬盘驱动器上创建一个单独的分区,我们将在其中安装 Ubuntu 22.04 。
|
||||
|
||||
因此,通过按下 **Windows + R** 组合键来打开磁盘管理器实用程序
|
||||
因此,通过按下 `Windows + R` 组合键来打开磁盘管理器实用程序。
|
||||
|
||||
在对话框中,输入 diskmgmt.msc ,并按下 <ruby>回车键<rt>ENTER</rt></ruby> 按键。
|
||||
在对话框中,输入 `diskmgmt.msc` ,并按下回车键。
|
||||
|
||||
![][2]
|
||||
|
||||
<ruby>磁盘管理<rt>disk management</rt></ruby>控制台将显示当前磁盘分区,如你将在下面所看到的一样。我们将通过压缩 ‘卷 E’ 来创建一个用于安装 Ubuntu 的分区。这在你的安装过程中可能有所不同,但是只需要跟着做,你就会理解其中的大体意思。
|
||||
<ruby>磁盘管理<rt>disk management</rt></ruby>控制台将显示当前磁盘分区,如你将在下面所看到的一样。我们将通过压缩 “卷 E” 来创建一个用于安装 Ubuntu 的分区。这在你的安装过程中可能有所不同,但是只需要跟着做,你就会理解其中的大体意思。
|
||||
|
||||
![][3]
|
||||
|
||||
因此,在你想要压缩的磁盘驱动器卷上右键,并在弹出的菜单中选择 <ruby>压缩卷<rt>Shrink</rt></ruby> 选项。
|
||||
因此,在你想要压缩的磁盘驱动器卷上点击鼠标右键,并在弹出的菜单中选择 <ruby>压缩卷<rt>Shrink</rt></ruby> 选项。
|
||||
|
||||
![][4]
|
||||
|
||||
一个弹出对话框将会出现,如下所示。具体指定压缩的控件大小(以 MB 为单位),并单 <ruby>压缩卷<rt>Shrink</rt></ruby> 。
|
||||
将会出现一个弹出对话框,如下所示。具体指定压缩的控件大小(以 MB 为单位),并单击 <ruby>压缩卷<rt>Shrink</rt></ruby> 。
|
||||
|
||||
这是指定给 Ubuntu 22.04 安装所用的空间.
|
||||
这是指定给 Ubuntu 22.04 安装所用的空间。
|
||||
|
||||
![][5]
|
||||
|
||||
@ -49,11 +51,11 @@
|
||||
|
||||
![][6]
|
||||
|
||||
随着可用空间的到来,现在将可启动 USB 媒介盘插入到你的 PC ,并重新启动你的系统。此外,要确保访问 BIOS 设置,并修改启动优先级,来使 USB 驱动器成为第一优先级。保存 BIOS 更改并继续启动。
|
||||
随着有了可用空间,现在将可启动 USB 驱动器插入到你的 PC ,并重新启动你的系统。此外,要确保访问 BIOS 设置,并修改启动优先级,来使 USB 驱动器成为第一优先级。保存 BIOS 更改并继续启动。
|
||||
|
||||
### 步骤 2、开始安装
|
||||
|
||||
在第一屏幕中,你将得到如图所示的 GRUB 菜单。选择第一个选项 <ruby>尝试或安装 Ubuntu<rt>Try or Install Ubuntu</rt></ruby> ,并按下 <ruby>回车键<rt>ENTER</rt></ruby> 按键。
|
||||
在第一个屏幕中,你将得到如图所示的 GRUB 菜单。选择第一个选项 <ruby>尝试或安装 Ubuntu<rt>Try or Install Ubuntu</rt></ruby> ,并按下 <ruby>回车键<rt>ENTER</rt></ruby> 按键。
|
||||
|
||||
![][7]
|
||||
|
||||
@ -69,7 +71,7 @@ Ubuntu 22.04 将开始加载,如下所示。这最多需要一分钟。
|
||||
|
||||
![][10]
|
||||
|
||||
在 <ruby>更新和其它软件<rt>Updates and Other Software</rt></ruby> 步骤中,选择 <ruby>正常安装<rt>Normal Installation</rt></ruby>以便安装 Ubuntu的 GUI 版本,通过勾选其它剩余选项来允许下载更新和安装第三方的针对于图像、WIFI 硬件和其它实用程序的软件包
|
||||
在 <ruby>更新和其它软件<rt>Updates and Other Software</rt></ruby> 步骤中,选择 <ruby>正常安装<rt>Normal Installation</rt></ruby> 以便安装 Ubuntu的 GUI 版本,通过勾选其它剩余选项来允许下载更新和安装第三方的针对于图像、WIFI 硬件和其它实用程序的软件包。
|
||||
|
||||
接下来,单击 <ruby>继续<rt>Continue</rt></ruby> 按钮。
|
||||
|
||||
@ -85,29 +87,29 @@ Ubuntu 22.04 将开始加载,如下所示。这最多需要一分钟。
|
||||
|
||||
针对 Ubuntu 22.04 ,我们将创建下面的分区:
|
||||
|
||||
* /boot – 1 GB
|
||||
* /home – 10 GB
|
||||
* / – 12 GB
|
||||
* Swap – 2 GB
|
||||
* EFI – 300 MB
|
||||
* `/boot` – 1 GB
|
||||
* `/home` – 10 GB
|
||||
* `/` – 12 GB
|
||||
* 交换分区 – 2 GB
|
||||
* EFI – 300 MB
|
||||
|
||||
为开始使用这些分区,单击 <ruby>可用空间<rt>Free Space</rt></ruby>分区下面的 [ + ] 符号。
|
||||
为开始使用这些分区,单击 <ruby>可用空间<rt>Free Space</rt></ruby>分区下面的 “+” 符号。
|
||||
|
||||
![][13]
|
||||
|
||||
如图显示填写 /boot 分区的详细信息,然后单击 <ruby>确定<rt>OK</rt></ruby> 按钮。
|
||||
如图显示填写 `/boot` 分区的详细信息,然后单击 <ruby>确定<rt>OK</rt></ruby> 按钮。
|
||||
|
||||
![][14]
|
||||
|
||||
接下来,具体指定 /home 分区,并单击 <ruby>确定<rt>OK</rt></ruby> 按钮。
|
||||
接下来,具体指定 `/home` 分区,并单击 <ruby>确定<rt>OK</rt></ruby> 按钮。
|
||||
|
||||
![][15]
|
||||
|
||||
接下来,定义 / ( root ) 分区,并单击 <ruby>确定<rt>OK</rt></ruby> 按钮。
|
||||
接下来,定义 `/`(根)分区,并单击 <ruby>确定<rt>OK</rt></ruby> 按钮。
|
||||
|
||||
![][16]
|
||||
|
||||
为定义 swap 空间,设置大小,并在 <ruby>使用为<rt>Use as</rt></ruby>:选项中选择 <ruby>交换区域<rt>Swap area</rt></ruby>。
|
||||
为定义交换空间,设置大小,并在 <ruby>使用为<rt>Use as</rt></ruby>:选项中选择 <ruby>交换区域<rt>Swap area</rt></ruby>。
|
||||
|
||||
![][17]
|
||||
|
||||
@ -115,7 +117,7 @@ Ubuntu 22.04 将开始加载,如下所示。这最多需要一分钟。
|
||||
|
||||
![][18]
|
||||
|
||||
下图是一份我们的分区表的分区摘要。
|
||||
下图是一份我们的分区表的分区摘要:
|
||||
|
||||
![][19]
|
||||
|
||||
@ -141,17 +143,17 @@ Ubuntu 22.04 将开始加载,如下所示。这最多需要一分钟。
|
||||
|
||||
![][24]
|
||||
|
||||
在这时,移除你的可启动 USB 驱动器,并按下 <ruby>回车键<rt>ENTER</rt></ruby> 按键。
|
||||
在这时,移除你的可启动 USB 驱动器,并按下回车键。
|
||||
|
||||
![][25]
|
||||
|
||||
在系统重新启动时,你将找到 Ubuntu 和 Windows 11 的所有选项。
|
||||
在系统重新启动时,你将找到包括 Ubuntu 和 Windows 11 在内的各种选项。
|
||||
|
||||
选择 ‘Ubuntu’ 来启动到你的新 Ubuntu 22.04 安装。为启动到 Windows 11,选择标有 <ruby>Windows 恢复环境<rt>Windows Recovery Environment</rt></ruby> 的条目。
|
||||
选择 “Ubuntu” 来启动到你的新 Ubuntu 22.04 安装。要启动到 Windows 11,请选择标有 <ruby>Windows 恢复环境<rt>Windows Recovery Environment</rt></ruby> 的条目。
|
||||
|
||||
![][26]
|
||||
|
||||
就这样。我们演示了如何双启动 Windows 11 和 Ubuntu 22.04.
|
||||
就这样。我们演示了如何双启动 Windows 11 和 Ubuntu 22.04。
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
@ -160,7 +162,7 @@ via: https://www.linuxtechi.com/dual-boot-ubuntu-22-04-and-windows-11/
|
||||
作者:[James Kiarie][a]
|
||||
选题:[lkxed][b]
|
||||
译者:[robsean](https://github.com/robsean)
|
||||
校对:[校对者ID](https://github.com/校对者ID)
|
||||
校对:[wxy](https://github.com/wxy)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译,[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
@ -3,19 +3,22 @@
|
||||
[#]: author: "Pradeep Kumar https://www.linuxtechi.com/author/pradeep/"
|
||||
[#]: collector: "lkxed"
|
||||
[#]: translator: "geekpi"
|
||||
[#]: reviewer: " "
|
||||
[#]: publisher: " "
|
||||
[#]: url: " "
|
||||
[#]: reviewer: "wxy"
|
||||
[#]: publisher: "wxy"
|
||||
[#]: url: "https://linux.cn/article-14697-1.html"
|
||||
|
||||
如何在 RHEL 9 上创建本地 Yum/DNF 仓库
|
||||
======
|
||||
你好,技术人员,最近红帽发布了最新的操作系统 RHEL 9,RHEL 9 满足了混合云的所有要求。它可以安装在物理服务器、虚拟机和容器镜像中。
|
||||
|
||||
当我们没有订阅的时候,想安装软件包来做 POC,那么设置本地的 yum 或 dnf 仓库将是很方便的。
|
||||
![](https://img.linux.net.cn/data/attachment/album/202206/11/164149y9zzm7kkxwsxgszw.jpg)
|
||||
|
||||
在本指南中,我们将介绍如何在 RHEL 9 上使用 DVD 或 ISO 文件一步一步地创建本地 yum/dnf 资源库。
|
||||
你好,技术兄弟,最近红帽发布了最新的操作系统 RHEL 9,RHEL 9 满足了混合云的所有要求。它可以安装在物理服务器、虚拟机和容器镜像中。
|
||||
|
||||
创建本地 yum/dnf 资源库的先决条件:
|
||||
当我们没有订阅的时候,想安装软件包来做实验,那么设置本地的 Yum 或 DNF 仓库将是很方便的。
|
||||
|
||||
在本指南中,我们将介绍如何在 RHEL 9 上使用 DVD 或 ISO 文件一步一步地创建本地 Yum/DNF 资源库。
|
||||
|
||||
创建本地 Yum/DNF 资源库的先决条件:
|
||||
|
||||
* 最小化安装 RHEL 9 系统
|
||||
* 具有管理权限的 sudo 用户
|
||||
@ -23,7 +26,7 @@
|
||||
|
||||
### 1)挂载 RHEL 9 ISO 文件或 DVD
|
||||
|
||||
我们假设 RHEL 9 iso 文件已经被复制到系统中。运行下面的挂载命令,将 ISO 文件挂载到 /opt/repo 文件夹。
|
||||
我们假设 RHEL 9 iso 文件已经被复制到系统中。运行下面的挂载命令,将 ISO 文件挂载到 `/opt/repo` 文件夹。
|
||||
|
||||
```
|
||||
$ sudo mkdir /var/repo
|
||||
@ -32,15 +35,15 @@ $ sudo mount -o loop rhel-baseos-9.0-x86_64-dvd.iso /var/repo/
|
||||
|
||||
![Mount-RHEL9-ISO-File-Command][1]
|
||||
|
||||
如果是 dvd,运行:
|
||||
如果是 DVD 光盘,运行:
|
||||
|
||||
```
|
||||
$ sudo mount /dev/sr0 /var/repo/
|
||||
```
|
||||
|
||||
### 2)在 “/etc/yum.repos.d/” 目录中创建仓库文件
|
||||
### 2)在 /etc/yum.repos.d/ 目录中创建仓库文件
|
||||
|
||||
在 /etc/yum.repos.d/ 目录下创建一个名为 “rhel9-local.repo” 的仓库文件,内容如下:
|
||||
在 `/etc/yum.repos.d/` 目录下创建一个名为 “rhel9-local.repo` 的仓库文件,内容如下:
|
||||
|
||||
```
|
||||
$ sudo vi /etc/yum.repos.d/rhel9-local.repo
|
||||
@ -65,9 +68,9 @@ gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-redhat-release
|
||||
|
||||
![RHEL8-Local-Repo-File][2]
|
||||
|
||||
### 3)刷新 yum/dnf 和订阅管理器的缓存
|
||||
### 3)刷新 Yum/DNF 和订阅管理器的缓存
|
||||
|
||||
执行以下命令来清理 yum 或 dnf 和订阅管理器的缓存。
|
||||
执行以下命令来清理 Yum 或 DNF 和订阅管理器的缓存。
|
||||
|
||||
```
|
||||
$ sudo dnf clean all
|
||||
@ -76,7 +79,7 @@ $ sudo subscription-manager clean
|
||||
|
||||
![DNF-Subscription-Manager-Clean][3]
|
||||
|
||||
在上面的输出中,我们得到一个警告信息 “This system is not registered with an entitlement”(系统没有注册权限)。所以,为了抑制这个警告信息,编辑文件 “/etc/yum/pluginconf.d/subscription-manager.conf”,将参数 “enabled=1” 改为 “enabled=0”。
|
||||
在上面的输出中,我们得到一个警告信息 `This system is not registered with an entitlement`(系统没有注册权限)。所以,为了抑制这个警告信息,编辑文件 `/etc/yum/pluginconf.d/subscription-manager.conf`,将参数 `enabled=1` 改为 `enabled=0`。
|
||||
|
||||
```
|
||||
$ sudo vi /etc/yum/pluginconf.d/subscription-manager.conf
|
||||
@ -98,7 +101,7 @@ $ sudo dnf repolist
|
||||
|
||||
![DNF-Repolist-RHEL-9][5]
|
||||
|
||||
现在,试试用 dnf 命令通过上面配置的本地仓库安装软件包。
|
||||
现在,试试用 `dnf` 命令通过上面配置的本地仓库安装软件包。
|
||||
|
||||
```
|
||||
$ sudo dnf install nfs-utils
|
||||
@ -110,7 +113,7 @@ $ sudo dnf install nfs-utils
|
||||
|
||||
![Package-Installation-Completion-RHEL9-DNF-Command][7]
|
||||
|
||||
完美,上述输出证实了 nfs-utils 包及其依赖项已经通过本地配置的 yum 或 dnf 仓库成功安装。
|
||||
完美,上述输出证实了 `nfs-utils` 包及其依赖项已经通过本地配置的 Yum 或 DNF 仓库成功安装。
|
||||
|
||||
这就是本指南的全部内容。我希望你觉得它有参考价值。请在下面的评论区发表你的疑问和反馈。
|
||||
|
||||
@ -121,7 +124,7 @@ via: https://www.linuxtechi.com/create-local-yum-dnf-repository-rhel/
|
||||
作者:[Pradeep Kumar][a]
|
||||
选题:[lkxed][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/) 荣誉推出
|
||||
|
@ -0,0 +1,82 @@
|
||||
[#]: subject: "6 Linux word processors you need to try"
|
||||
[#]: via: "https://opensource.com/article/22/6/word-processors-linux"
|
||||
[#]: author: "Don Watkins https://opensource.com/users/don-watkins"
|
||||
[#]: collector: "lkxed"
|
||||
[#]: translator: "duoluoxiaosheng"
|
||||
[#]: reviewer: "wxy"
|
||||
[#]: publisher: "wxy"
|
||||
[#]: url: "https://linux.cn/article-14693-1.html"
|
||||
|
||||
值得尝试的六款 Linux 文字处理程序
|
||||
======
|
||||
|
||||
> 选择一款最中意的文字处理程序把你的想法打印到纸上。
|
||||
|
||||
![](https://img.linux.net.cn/data/attachment/album/202206/10/120032h7jlo1ozm37fdyfv.jpg)
|
||||
|
||||
作家们总是在寻找更好的方法将他们的文字和想法以更好的方式呈现给他们的读者。我对文字处理程序最早的印象是在 Apple II 上使用 AppleWorks 和后来的 FrEDWriter,后者是一个创建于 1985 年的免费文字处理程序。这是我的学生们的标配,他们许多人来自没有钱购买专有软件的家庭。
|
||||
|
||||
### Abiword
|
||||
|
||||
在 20 世纪 90 年代时,我开始使用 Linux,寻找我可以使用的高质量的写作程序,并推荐给跟随我进入开源软件世界的学生们。我首先接触的文字处理程序是 [AbiWord][2]。AbiWord 来自西班牙语 Abierto,意思是“开放”。它最早发布于 1998 年,并且之后一直在升级。它使用 GPLv2 开源协议。它支持列表、缩进,字符格式等基本功能,支持 .doc、.html、.docx、.odt 等多种格式文件的导入和导出。
|
||||
|
||||
![Image of Abiword][3]
|
||||
|
||||
### Etherpad
|
||||
|
||||
[Etherpad][4] 是一个开源协作编辑项目。它可以让你像 Google Drive 那样实时编辑文档,主要的区别是它是完全开源的。据它的网站上介绍,你可以“与你的朋友、同学或同事一起写文章、新闻稿、待办事项,同时在同一个文件上工作”。其源代码可随时查看。Etherpad 采用 Apache 2.0 开源协议。你可以直接在线使用它,或者把它下载并 [安装][5] 到你的 Linux 电脑上。
|
||||
|
||||
### Cryptpad
|
||||
|
||||
[CryptPad][6] 是一个端到端加密的写作套件。使用 GPLv3 开源协议,并且源代码公开在 [GitHub][7] 上。它由 [Xwiki][8] 实验室开发。可替代 Google Drive,并且是自主托管的。根据其网站描述,“CryptPad 旨在实现协作办公。实时同步文档的更改。由于所有数据都已加密,因此该服务及其管理员无法查看正在编辑和存储的内容。” Cryptpad 为用户提供了 [丰富的文档][9]。
|
||||
|
||||
### Focuswriter
|
||||
|
||||
[FocusWriter][10] 是一个简单的免干扰的编辑器。它使用隐藏式界面,鼠标移动到屏幕边界时才显示界面。它使用 GPLv3 开源协议,并为 Linux 提供了 Flatpak 软件包,也为 [Ubuntu][11] 和 [Fedora][12] 提供了 DEB 和 RPM。下图是一个 FocusWriter 桌面的例子。这是一个非常简单直观的界面,菜单自动隐藏,当鼠标指向屏幕顶部或边缘时才会显示。文件默认保存为 .odt 格式,也支持纯文本、.docx 和富文本。
|
||||
|
||||
![Image of FocusWriter][13]
|
||||
|
||||
### LibreOffice Writer
|
||||
|
||||
[LibreOffice Writer][14] 是我最喜欢的,我已经使用了十多年了。它拥有我需要的所有特性,包括富文本格式化。它还拥有我见过的最多的导入、导出方式。类似于 [APA][15] 这样的问卷和出版模板它拥有十多种。我最喜欢的是它可以将文件导出为 PDF 和 epub。 LibreOffice Writer 是一个自由软件,使用 Mozilla 公开许可证(MPL)2.0 开源协议。其 [源代码][16] 由文档基金会提供。LibreOffice 支持大多数 Linux 发行版。同时它也提供 Flatpak、Snap 和 AppImage 软件包。另外,你也可以把它下载并安装到 MacOS 和 Windows 上。
|
||||
|
||||
![Image of LibreOffice work space][17]
|
||||
|
||||
### OpenOffice Writer
|
||||
|
||||
Apache [OpenOffice Writer][18] 是一个全功能的文字处理程序。它可以简单地用于备忘录,也可以复杂到足以编写你的第一本书。依据官网的描述,OpenOffice Writer 将文档自动保存为 .odt。它还支持将文档保存为 .doc、.docx、富文本和其他格式。OpenOffice Writer 使用 Apache 许可证 2.0 开源协议。源代码在 [GitHub][19] 上公开。
|
||||
|
||||
还有许多自由开源软件等着大家去发现。它们非常适合完成你的日常任务,你也可以为它们的发展做出贡献。你最喜欢的 Linux 文字处理器程序是什么呢?
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://opensource.com/article/22/6/word-processors-linux
|
||||
|
||||
作者:[Don Watkins][a]
|
||||
选题:[lkxed][b]
|
||||
译者:[duoluoxiaosheng](https://github.com/duoluoxiaosheng)
|
||||
校对:[wxy](https://github.com/wxy)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译,[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
||||
[a]: https://opensource.com/users/don-watkins
|
||||
[b]: https://github.com/lkxed
|
||||
[1]: https://opensource.com/sites/default/files/lead-images/typewriter-hands.jpg
|
||||
[2]: https://www.abisource.com/
|
||||
[3]: https://opensource.com/sites/default/files/2022-05/abiword.png
|
||||
[4]: https://etherpad.org/#
|
||||
[5]: https://github.com/ether/etherpad-lite#installation
|
||||
[6]: https://cryptpad.fr/what-is-cryptpad.html
|
||||
[7]: https://github.com/xwiki-labs/cryptpad
|
||||
[8]: https://github.com/xwiki-labs
|
||||
[9]: https://docs.cryptpad.fr/en/user_guide/index.html
|
||||
[10]: https://gottcode.org/focuswriter/
|
||||
[11]: https://packages.ubuntu.com/jammy/focuswriter
|
||||
[12]: https://src.fedoraproject.org/rpms/focuswriter
|
||||
[13]: https://opensource.com/sites/default/files/2022-05/focuswriter.png
|
||||
[14]: https://www.libreoffice.org/discover/writer/
|
||||
[15]: https://extensions.libreoffice.org/en/extensions/show/apa-style-paper-template
|
||||
[16]: https://www.libreoffice.org/about-us/source-code/
|
||||
[17]: https://opensource.com/sites/default/files/2022-05/Libreofficewriter.png
|
||||
[18]: https://www.openoffice.org/product/writer.html
|
||||
[19]: https://github.com/apache/openoffice
|
@ -3,15 +3,18 @@
|
||||
[#]: author: "Abhishek Prakash https://itsfoss.com/author/abhishek/"
|
||||
[#]: collector: "lkxed"
|
||||
[#]: translator: "geekpi"
|
||||
[#]: reviewer: " "
|
||||
[#]: publisher: " "
|
||||
[#]: url: " "
|
||||
[#]: reviewer: "wxy"
|
||||
[#]: publisher: "wxy"
|
||||
[#]: url: "https://linux.cn/article-14700-1.html"
|
||||
|
||||
Amberol 是一款外观漂亮的 Linux 音乐播放器,只播放音乐,不做其他事情
|
||||
======
|
||||
|
||||
![](https://img.linux.net.cn/data/attachment/album/202206/12/155846b0sbsvtt1et70ttf.jpg)
|
||||
|
||||
虽然音乐世界被流媒体服务所主导,但这并没有阻止开发者为桌面电脑创建音乐播放器。
|
||||
|
||||
最近,我发现了一个外观漂亮的新的 Linux 桌面音乐播放器。它名为 Amberol,我被它的美丽所震撼了。
|
||||
最近,我发现了一个外观漂亮的新的 Linux 桌面音乐播放器。它名为 Amberol,我被它的美丽所震撼。
|
||||
|
||||
![amberol music player interface][1]
|
||||
|
||||
@ -21,41 +24,41 @@ Amberol 是一款外观漂亮的 Linux 音乐播放器,只播放音乐,不
|
||||
|
||||
看起来不错是它所做的两件(或几件)事情中的一件。另一件事是播放音乐。
|
||||
|
||||
这就是它。[Amberol][2] 没有额外的花哨(和有用)的功能,如生成专辑封面、元数据编辑、歌词显示或播放列表和库管理。
|
||||
这就是它,[Amberol][2] 没有额外的花哨(和有用)的功能,如生成专辑封面、元数据编辑、歌词显示或播放列表和库管理。
|
||||
|
||||
这些功能也不像会在未来的版本中加入。Amberol 只想播放音乐。就是这样。
|
||||
这些功能也不像是会在未来的版本中加入。Amberol 只想播放音乐。就是这样。
|
||||
|
||||
#### 令人惊叹的用户界面
|
||||
|
||||
Amberol 和大多数新的 GNOME 应用一样,是用 Rust 和 GTK 编写的。
|
||||
|
||||
它有一个自适应的用户界面,可以根据你正在播放的专辑颜色来改变颜色。渐变效果给了它一个现代、时尚的外观,肯定会成为你的 Linux rice 截图的一部分。
|
||||
它有一个自适应的用户界面,可以根据你正在播放的专辑颜色来改变颜色。渐变效果给了它一个现代、时尚的外观,肯定会成为你的 Linux <ruby>美化<rt>Ricing</rt></ruby>截图的一部分。
|
||||
|
||||
![amberol music player][3]
|
||||
|
||||
由于 UI 没有传统的手柄和菜单,它给应用一个统一的外观。
|
||||
由于其 UI 没有传统的手柄和菜单,它给应用一个统一的外观。
|
||||
|
||||
#### 播放列表
|
||||
|
||||
它从你添加的文件夹中存在的文件自动生成一个播放列表。它显示在左手边的侧边栏。
|
||||
它会从你添加的文件夹中的文件自动生成一个播放列表,显示在左手边的侧边栏。
|
||||
|
||||
![amberol playlist][4]
|
||||
|
||||
你可以在左上角看到整个播放列表将播放多长时间的音乐。点击“勾选符号”,你可以选择歌曲,并从播放列表中删除它们。
|
||||
你可以在左上角看到整个播放列表将播放多长时间的音乐。点击“勾选”符号,你可以选择歌曲,并从播放列表中删除它们。
|
||||
|
||||
如果你愿意,你可以隐藏播放列表的侧边栏。
|
||||
如果你愿意,可以隐藏播放列表的侧边栏。
|
||||
|
||||
![amberol without playlist][5]
|
||||
|
||||
#### 音乐播放选项
|
||||
|
||||
你可以在界面上看到歌曲的进度。该播放器与键盘上的媒体控制按钮整合得很好。你可以用专用的媒体键播放/暂停和改变曲目(如果你的系统上有)。
|
||||
你可以在界面上看到歌曲的进度。该播放器与键盘上的媒体控制按钮整合得很好。你可以用专用的媒体键来播放、暂停和改变曲目(如果你的系统上有)。
|
||||
|
||||
Amberol 为你提供了一些播放音乐的选项。你可以打开随机播放功能,按随机顺序播放音乐。你也可以把一首歌放在重复的位置,一直播放,直到你厌倦它。
|
||||
Amberol 为你提供了一些播放音乐的选项。你可以打开随机播放功能,按随机顺序播放音乐。你也可以单曲循环,直到你厌倦它。
|
||||
|
||||
![amberol music playing options][6]
|
||||
|
||||
底部的手柄菜单让你可以选择添加文件或文件夹,并显示可用的键盘快捷方式。
|
||||
底部的汉堡菜单让你可以选择添加文件或文件夹,并显示可用的键盘快捷方式。
|
||||
|
||||
![amberol keyboard shortcuts][7]
|
||||
|
||||
@ -63,7 +66,7 @@ Amberol 为你提供了一些播放音乐的选项。你可以打开随机播放
|
||||
|
||||
### 在 Linux 上安装 Amberol
|
||||
|
||||
Amberol 是[以 Flatpak 形式提供][8]。请确保[你的系统已启用 Flatpak 支持][9]。
|
||||
Amberol 是 [以 Flatpak 形式提供的][8]。请确保 [你的系统已启用 Flatpak 支持][9]。
|
||||
|
||||
要安装 Amberol,请打开终端并使用以下命令:
|
||||
|
||||
@ -73,17 +76,17 @@ flatpak install flathub io.bassi.Amberol
|
||||
|
||||
安装完毕后,在菜单中搜索该应用,并点击启动。
|
||||
|
||||
第一次运行时,它会要求你添加音乐文件或文件夹。你也可以拖放文件。
|
||||
第一次运行时,它会要求你添加音乐文件或文件夹。你也可以拖放文件播放。
|
||||
|
||||
![amberol first run][10]
|
||||
|
||||
### 总结
|
||||
|
||||
就个人而言,我更喜欢流媒体服务,因为我没有一个很好的本地音乐收藏。但我知道有的人有/有大量的 CD 收藏,现在都保存在硬盘上。
|
||||
就个人而言,我更喜欢流媒体服务,因为我没有本机音乐珍藏。但我知道有的人有大量的 CD 收藏,现在都保存在硬盘上。
|
||||
|
||||
Amberol 是一个外观漂亮的应用,对于播放本地音乐来说,它足够好。最吸引人的是基于专辑封面的自适应用户界面。
|
||||
Amberol 是一个外观漂亮的应用,对于播放本机音乐来说,它足够好。最吸引人的是它基于专辑封面的自适应用户界面。
|
||||
|
||||
我请你试试它,并在评论区分享你的经验。
|
||||
请你试试它,并在评论区分享你的经验。
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
@ -92,7 +95,7 @@ via: https://itsfoss.com/amberol-music-player/
|
||||
作者:[Abhishek Prakash][a]
|
||||
选题:[lkxed][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/) 荣誉推出
|
||||
|
@ -0,0 +1,100 @@
|
||||
[#]: subject: "Linux Kernel 5.19 RC1 Released, Concluding ARM Generic Kernel Work"
|
||||
[#]: via: "https://www.debugpoint.com/2022/06/linux-kernel-5-19-rc1/"
|
||||
[#]: author: "Arindam https://www.debugpoint.com/author/admin1/"
|
||||
[#]: collector: "lkxed"
|
||||
[#]: translator: "Donkey-Hao"
|
||||
[#]: reviewer: "wxy"
|
||||
[#]: publisher: "wxy"
|
||||
[#]: url: "https://linux.cn/article-14692-1.html"
|
||||
|
||||
Linux 内核 5.19 RC1 发布,完成了 ARM 通用内核的工作
|
||||
======
|
||||
|
||||
![](https://img.linux.net.cn/data/attachment/album/202206/10/100401b0t82bd0ww0o2tgn.jpg)
|
||||
|
||||
> Linus Torvalds 发布了用来测试的 Linux 内核 5.19 RC1,带来了一些重大变化。
|
||||
|
||||
继上个月 [Linux 内核 5.18][1] 发布之后,Linus Torvalds 宣布了 Linux 内核 5.19 系列第一个候选版本。与此同时,Linux 内核 5.19 官方合并窗口关闭,这意味着除非是关键性的,否则不会再接受任何新功能。
|
||||
|
||||
简单看一下 Linux 内核 5.19 的新内容,会发现 CPU、GPU、网络、存储和核心模块都有常规的更新。此外,代码清理、淘汰过时硬件和对以后芯片组的持续支持是此版本的亮点。
|
||||
|
||||
在进一步介绍之前,让我们简单来看一下这些新特性。
|
||||
|
||||
### Linux 内核 5.19(RC1)的新特性
|
||||
|
||||
#### CPU
|
||||
|
||||
首先需要提及的是,Linux 内核 5.19 开始 [初步支持][2] 龙芯架构的 CPU 系列。龙芯由中国龙芯中科公司设计开发。龙芯架构的 CPU 是兼容 MIPS 架构的通用微处理器。不过虽然现在提供了支持,但是你仍不能在龙芯 CPU 上启动 Linux,因为一些代码还在审核中。希望在 5.20 版本中能够使用。
|
||||
|
||||
新的 [英特尔 IFS 驱动][4] 在该版本中落地,这有助于在部署前后发现硬件问题。它能够在早期阶段检测电路层面的 CPU 错误。
|
||||
|
||||
在前几个针对英特尔 CPU 的内核版本中一直在对电源管理和散热方面进行开发,[这个版本][5] 也不例外。首先,为 Raptor 和 Alder Lake 家族添加了英特尔 <ruby>运行时平均功率限制<rt>Run-Time Average Power Limiting</rt></ruby>(RAPL)的支持。其次,改进了 P-state 驱动以处理频率变化,并且基于 CPU 的缩放支持被添加到被动 devfreq 中。
|
||||
|
||||
虽然英特尔 CPU 主要是散热和电源管理方面的工作,但对 AMD CPU 系列来说有更多的性能更新。首先,计划在今年年底完成 ZMD Zen 4 CPU 的 <ruby>基于指令的采样<rt>Instruction-Based Sampling</rt></ruby>(IBS)模块引入了更多更新。此外,此版本引入了 PerfMonV2,提供了更多性能监视能力。
|
||||
|
||||
此外,该版本中移除了 a.out 支持。同样,过时的 Renesas H8/300 CPU 也被移除了。
|
||||
|
||||
#### 主要 ARM 更新
|
||||
|
||||
终于,主线 Linux 内核能够 [支持 ARM 多平台][7] 了。在 Linus 的 RC1 开场白中可以看到,这是该版本中的巨大改变!从 Linux 3.7 开始,跨越了十多年的工作,这是多么漫长的过程。
|
||||
|
||||
![Linux 内核 5.19 Rc1 发布公告提到了 ARM 变化][8]
|
||||
|
||||
#### 图形和存储升级
|
||||
|
||||
存储子系统在各种流行的文件系统中都有性能提升。最主要的变化包括苹果 M1 NVMe 控制器支持和对 XFS 文件系统的更好支持。此外,Btrfs、F2FS 以及 exFAT 文件系统也有增强。
|
||||
|
||||
在代码行数方面,有一个令人兴奋的指标是仅是图形驱动程序 Linux 内核 5.19 就增加了大约[50 万行代码][9]。它包括 AMD 的 RDNA、CDNA,英特尔的 Raptor Lake、DG2/Alchemist 等图形驱动更新。
|
||||
|
||||
#### 重要的网络变化
|
||||
|
||||
鉴于数据传输大幅增长,对 Big TCP 的支持有助于支持数据中心 400 GBit 级别的流量。它还可以在高性能网络环境中降低延迟。
|
||||
|
||||
继续改进了 <ruby>多路径 TCP<rt>Multi-Path TCP</rt></ruby>(MPTCP)。此外,高通 ath11k WiFi 驱动程序在此版本中添加了网络唤醒功能。同样增加了对瑞昱的 8852ce 芯片、联发科的 T700 调制解调器以及瑞萨科技的 RZ/V2M 的支持。
|
||||
|
||||
#### 其他值得注意的功能
|
||||
|
||||
首先,内核中著名的随机函数生成器(RNG)在此版本中 [继续][10] 改进。
|
||||
|
||||
其次,著名的新兴的 Framework 模块化笔记本电脑获得了此版本 Chrome OS EC 驱动支持。Framework 笔记本现在可以作为一个非 Chromebook 设备利用 ChromeOS 的嵌入式控制器。
|
||||
|
||||
此外,Wacom 绘画板以及其他相关设备也有众多更新。[包括][11] 对联想 Thinkpad TrackPoint II、谷歌 Whiskers Touchpad、联想 X12 TrackPoint 等设备支持的提升。
|
||||
|
||||
### Linux 内核 5.19 下载
|
||||
|
||||
如果你想要测试并尝试该候选版本,可以在 [这里][12] 下载。
|
||||
|
||||
预计在 2022 年 7 月左右最终版本发布前,将会有多个版本更迭。
|
||||
|
||||
参考自:[内核邮件列表][17]
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://www.debugpoint.com/2022/06/linux-kernel-5-19-rc1/
|
||||
|
||||
作者:[Arindam][a]
|
||||
选题:[lkxed][b]
|
||||
译者:[Donkey-Hao](https://github.com/Donkey-Hao)
|
||||
校对:[wxy](https://github.com/wxy)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译,[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
||||
[a]: https://www.debugpoint.com/author/admin1/
|
||||
[b]: https://github.com/lkxed
|
||||
[1]: https://www.debugpoint.com/2022/05/linux-kernel-5-18/
|
||||
[2]: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=c6f2f3e2c80e975804360665d973211e4d9390cb
|
||||
[3]: http://www.loongson.cn/
|
||||
[4]: https://lore.kernel.org/lkml/13e61c61-0d4b-5f48-6373-f056bf8b603f@redhat.com/
|
||||
[5]: https://lore.kernel.org/linux-acpi/CAJZ5v0hKBt3js65w18iKxzWoN5QuEc84_2xcM6paSv-ZHwe3Rw@mail.gmail.com/
|
||||
[6]: https://lore.kernel.org/lkml/You6yGPUttvBcg8s@gmail.com/
|
||||
[7]: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ecf0aa5317b0ad6bb015128a5b763c954fd58708
|
||||
[8]: https://www.debugpoint.com/wp-content/uploads/2022/06/Linux-Kernel-5.19-Rc1-release-announcement-mentions-ARM-changes.jpg
|
||||
[9]: https://lore.kernel.org/lkml/CAPM=9tw62EZfAm0PbiOPmMrpfR98QMFTWGEQcA34G4ap4xxNkA@mail.gmail.com/
|
||||
[10]: https://lore.kernel.org/lkml/20220522214457.37108-1-Jason@zx2c4.com/T/#u
|
||||
[11]: https://lore.kernel.org/lkml/nycvar.YFH.7.76.2205241107530.28985@cbobk.fhfr.pm/
|
||||
[12]: https://www.kernel.org/
|
||||
[13]: https://git.kernel.org/torvalds/t/linux-5.19-rc1.tar.gz
|
||||
[14]: https://git.kernel.org/torvalds/p/v5.19-rc1/v5.18
|
||||
[15]: https://git.kernel.org/torvalds/ds/v5.19-rc1/v5.18
|
||||
[16]: https://git.kernel.org/torvalds/h/v5.19-rc1
|
||||
[17]: https://lore.kernel.org/lkml/CAHk-=wgZt-YDSKfdyES2p6A_KJoG8DwQ0mb9CeS8jZYp+0Y2Rw@mail.gmail.com/T/#u
|
@ -0,0 +1,100 @@
|
||||
[#]: subject: "openSUSE Leap 15.4 Release Adds Leap Micro 5.2, Updated Desktop Environments, and More"
|
||||
[#]: via: "https://news.itsfoss.com/opensuse-leap-15-4-release/"
|
||||
[#]: author: "Ankush Das https://news.itsfoss.com/author/ankush/"
|
||||
[#]: collector: "lkxed"
|
||||
[#]: translator: "robsean"
|
||||
[#]: reviewer: "wxy"
|
||||
[#]: publisher: "wxy"
|
||||
[#]: url: "https://linux.cn/article-14695-1.html"
|
||||
|
||||
openSUSE Leap 15.4 发布版本添加了 Leap Micro 5.2、更新桌面环境等等
|
||||
======
|
||||
|
||||
> 为奋起直追 SUSE Linux Enterprise 的 SP 4 ,openSUSE Leap 15.4 到来了,带来了新的升级和极其重要的改善。
|
||||
|
||||
![opensuse 15.4][1]
|
||||
|
||||
即将到来的 openSUSE 小发布版本终于来了。如果你使用 openSUSE 作为你日常使用的桌面或服务器版本,你现在可能已经测试候选版本好几周了。
|
||||
|
||||
openSUSE Leap 15.4 的重点是软件包的更新,用以奋起直追 SUSE Linux Enterprise 的 SP 4 。因此,你将注意到一些弃用的软件包,以及可用于替换它们的新的升级。
|
||||
|
||||
当然,你应该有一些可用的软件包来确保兼容性。但是,大多数较旧的版本已经被移除。
|
||||
|
||||
### openSUSE Leap 15.4: 有什么新的变化?
|
||||
|
||||
为与最新的 SUSE Linux Enterprise(SLE)相适应,像 Python 2 和 KDE 4 一样的软件包已经被移除。你可以在这次的发布版本中找到较新的桌面环境。
|
||||
|
||||
此外,在容器和 AI/ML 用例方面,更新了 Podman、Containerd、Tensorflow 和 Grafana。
|
||||
|
||||
#### Leap Micro 5.2
|
||||
|
||||
Leap Micro 是针对容器和虚拟化工作负载定制的轻量级操作系统的最新版本。它也是 Leap 版的 [MicroOS][2],是 Tumbleweed 的一种变体,提供了自动管理和修补。
|
||||
|
||||
#### 桌面环境
|
||||
|
||||
Xfce 4.16 继续保留,但你可以找到主要功能的一些新补充,包括新图标和调色板。
|
||||
|
||||
Xfce 4.16 中的设置管理器也获得了视觉上的刷新。类似地,文件管理器(Thunar)也有一些改善,新的状态托盘插件的深色模式支持等等。
|
||||
|
||||
KDE 4 软件包已经被弃用,Plasma 5.24 LTS 已经作为长期支持版本中包含于其中。
|
||||
|
||||
要深入了解这些变化,你可以查看我们之前针对 [KDE Plasma 5.24 LTS][3] 的报道。总体来说,新的 KDE Plasma 体验应该会令桌面用户赞叹。
|
||||
|
||||
说到 GNOME,你可以发现包含在 openSUSE Leap 15.4 中的 GNOME 41 带来了一系列的改善和新的特色功能。了解更多关于 [GNOME 41][4] 的信息,你可以期待它的一些新的特色功能。
|
||||
|
||||
对于其它的可用的桌面环境来说,Leap 15.4 包括:
|
||||
|
||||
* MATE 桌面环境 1.26
|
||||
* Enlightenment 桌面环境0.25.3
|
||||
* 深度桌面环境 20.3
|
||||
|
||||
#### 弃用的软件包
|
||||
|
||||
移除了一些基础的软件包,包括 Python 2(生命终结)、Digikam、TensorFlow 1.x 和 Qt 4 等软件包。
|
||||
|
||||
在更新系统后,你可以使用 Qt 5 和 Plasma 5 。
|
||||
|
||||
#### 更新的软件包
|
||||
|
||||
很多重要的软件包在 Leap 15.4 中得到了更新,包含一些流行的软件包:
|
||||
|
||||
* TensorFlow 2.6.2
|
||||
* Podman 3.4.4
|
||||
* GNU Health 4.0
|
||||
* sudo 1.9.9
|
||||
* systemd 249.10
|
||||
* AppArmor 3.04
|
||||
* DNF 4.10.0
|
||||
* LibreOffice 7.2.5
|
||||
|
||||
因此,你应该会注意到一些针对服务器用户和桌面用户的各种应用程序的有用更新。很多多媒体应用程序,像 VLC、GNOME MPV 等,都得到了升级。
|
||||
|
||||
#### 其它改善
|
||||
|
||||
随着基本软件的更新和清理,你也可以找到一个由 SUSE 维护的较新的 Linux 内核 5.14.21。
|
||||
|
||||
更新后的内核对硬件的支持应该会有改善。
|
||||
|
||||
更多信息,你可以参考针对 [openSUSE Leap 15.4][5] 的发布版本说明。
|
||||
|
||||
> **[下载 openSUSE Leap 15.4][6]**
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://news.itsfoss.com/opensuse-leap-15-4-release/
|
||||
|
||||
作者:[Ankush Das][a]
|
||||
选题:[lkxed][b]
|
||||
译者:[robsean](https://github.com/robsean)
|
||||
校对:[wxy](https://github.com/wxy)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译,[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
||||
[a]: https://news.itsfoss.com/author/ankush/
|
||||
[b]: https://github.com/lkxed
|
||||
[1]: https://news.itsfoss.com/wp-content/uploads/2022/06/opensuse-leap-15-4.jpg
|
||||
[2]: https://microos.opensuse.org/
|
||||
[3]: https://news.itsfoss.com/kde-plasma-5-24-lts-release/
|
||||
[4]: https://news.itsfoss.com/gnome-41-release/
|
||||
[5]: https://doc.opensuse.org/release-notes/x86_64/openSUSE/Leap/15.4/#rnotes
|
||||
[6]: https://get.opensuse.org/leap/15.4/
|
@ -1,47 +0,0 @@
|
||||
[#]: subject: "OpenInfra Foundation Launches ‘directed funding’ To Support Open Source Projects"
|
||||
[#]: via: "https://www.opensourceforu.com/2022/06/openinfra-foundation-launches-directed-funding-to-support-open-source-projects/"
|
||||
[#]: author: "Laveesh Kocher https://www.opensourceforu.com/author/laveesh-kocher/"
|
||||
[#]: collector: "lkxed"
|
||||
[#]: translator: " "
|
||||
[#]: reviewer: " "
|
||||
[#]: publisher: " "
|
||||
[#]: url: " "
|
||||
|
||||
OpenInfra Foundation Launches ‘directed funding’ To Support Open Source Projects
|
||||
======
|
||||
![open-infra-berlin-event][1]
|
||||
|
||||
The OpenInfra Foundation, formerly known as the OpenStack Foundation until it expanded its scope beyond its flagship project a few years ago, announced today an intriguing new way for companies to fund open source projects within the foundation. Corporate members of open source foundations have traditionally supported the organisation by paying a membership fee, which the foundations then distribute as they see fit. The OpenInfra foundation is now launching a new ‘Directed Funding’ model that allows members to direct their funds directly to a project.
|
||||
|
||||
The foundation previously did not allow this because, as Bryce pointed out, it can create mixed incentives and a pay-for-play dynamic, which the organisation has always tried to avoid. However, there was a lot of interest in the community to support specific projects, which makes sense given that the foundation is now home to a wider variety of projects, but not every member is heavily invested in every project.
|
||||
|
||||
Bryce stated that the foundation’s leadership and board spent a significant amount of time considering how to reconcile the foundation’s core principles with this new model. As a result, the model tries to combine the best of the OpenStack/OpenInfra technical governance model, which has worked well over the last decade, with these new financial considerations.
|
||||
|
||||
Under this ‘directed funding’ model, each new project will have its own legal entity that will hold the project funding. To ensure that the new projects are legitimate, an OpenInfra Platinum member (currently nine, including Ant Group, Huawei, Meta, Microsoft, and Red Hat) must serve as the project’s sponsor, after which other organisations can join the project fund. If a sponsoring company is not already an OpenInfra member, it must become one. All of these funding members then form a project fund governing board, which decides on the fees for creating a budget. Meanwhile, the OpenInfra Foundation will provide these projects with community-building services.
|
||||
|
||||
This new model will, for the time being, only apply to new projects that join the foundation. Bryce and Collier noted that there may be some existing projects where the organisation could retroactively apply this new model, but that is not currently on the roadmap.
|
||||
|
||||
The OpenInfra foundation has added projects such as Kata Containers for increased container security, Airship for infrastructure lifecycle management, the Startling X edge compute stack, and the Zuul CI/CD platform since it expanded beyond OpenStack.
|
||||
|
||||
“The most important thing we’ve learned from each of these successful projects is that collaboration is key and the more breadth in the ecosystem of support the better,” said Thierry Carrez, general manager of the OpenInfra Foundation. “In fact, we’ve found that the most successful open source projects are funded by multiple companies, because they are able to combine their resources to achieve a much stronger rate of return.”
|
||||
|
||||
This new model is clearly a way for the OpenInfra Foundation to bring new projects — and new members — into the fold. Its models for managing open source projects in a multi-party ecosystem — both through the new directed funds and its more traditional approach — may not be suitable for every project, as the leadership team readily admits. Even if the OpenInfra Foundation only receives a small percentage of projects, the number of open-source projects is increasing as the demand for these sophisticated cloud infrastructure projects grows, all while they become more complex.
|
||||
|
||||
The Foundation also announced a couple of milestone releases for its various projects, including version 2.0 of Kata Containers, version 5.0 of Zuul, and the release of StarlingX 6.0.
|
||||
|
||||
“The Foundation celebrates its 10 anniversary this year, and as we look to our next decade of open infrastructure, we’re building momentum on what makes our model so successful: aligning companies and individuals who wish to work together, providing them with a framework and tools to effectively collaborate, and helping them invest their funds to best help the project they care about,” said Collier.
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://www.opensourceforu.com/2022/06/openinfra-foundation-launches-directed-funding-to-support-open-source-projects/
|
||||
|
||||
作者:[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/06/open-infra-berlin-event.png
|
@ -1,41 +0,0 @@
|
||||
[#]: subject: "Atom Text Editor Will Officially Be Terminated Later This Year"
|
||||
[#]: via: "https://www.opensourceforu.com/2022/06/atom-text-editor-will-officially-be-terminated-later-this-year/"
|
||||
[#]: author: "Laveesh Kocher https://www.opensourceforu.com/author/laveesh-kocher/"
|
||||
[#]: collector: "lkxed"
|
||||
[#]: translator: " "
|
||||
[#]: reviewer: " "
|
||||
[#]: publisher: " "
|
||||
[#]: url: " "
|
||||
|
||||
Atom Text Editor Will Officially Be Terminated Later This Year
|
||||
======
|
||||
![github-cover][1]
|
||||
|
||||
On December 15, Microsoft’s GitHub will shut down Atom, its open source text editor that inspired and influenced widely used commercial apps such as Microsoft Visual Studio Code, Slack, and GitHub Desktop. The social code company stated that it is doing so to focus on cloud-based software.
|
||||
|
||||
GitHub Codespaces is a cloud-hosted development environment with Visual Studio Code integration. When Microsoft acquired Github in June 2018, Nat Friedman, the CEO at the time, reassured the GitHub community that Atom was still alive and well.
|
||||
|
||||
Atom has come to a halt after four years of progress. Apart from maintenance and security updates, the project hasn’t seen significant feature development in several years, according to GitHub. Community involvement has declined during this time, and the business of locally installed software now appears less appealing than the potential recurring revenue, vendor lock-in, and information gathering enabled by cloud-based apps.
|
||||
|
||||
The Atom shell – a separate component for integrating with Chromium, Node.js, and native APIs – was renamed Electron (a cross-platform app framework based on web tech) in 2015, and Microsoft began working with GitHub on Atom and Electron and what would become Visual Studio Code.
|
||||
|
||||
That relationship has now followed the famous Microsoft model of embrace, extend, and extinguish, though Atom’s demise appears to be more like pushing dead weight out of a cloud-bound balloon than a strategically advantageous hit.
|
||||
|
||||
Atom’s influence should be felt through the Electron framework. Electron.js is still the foundation for apps such as Discord, Skype, Slack, Trello, and Visual Studio Code, among others. However, technology evolves. Microsoft previously stated that it intends to abandon Electron in Teams. Other cross-platform frameworks, such as Flutter, Tauri, and Microsoft’s recently announced.NET Multi-platform App UI (.NET MAUI), may gain traction as well.
|
||||
|
||||
Nonetheless, Atom is expected to operate past its December 15, 2022 decommissioning date. GitHub intends to archive the Atom repository, but the code is open source and available to anyone who wants to champion the project.
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://www.opensourceforu.com/2022/06/atom-text-editor-will-officially-be-terminated-later-this-year/
|
||||
|
||||
作者:[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/06/github-cover-e1654769639273.jpg
|
@ -1,83 +1,79 @@
|
||||
[#]: subject: (Learn the Lisp programming language in 2021)
|
||||
[#]: via: (https://opensource.com/article/21/5/learn-lisp)
|
||||
[#]: author: (Seth Kenlon https://opensource.com/users/seth)
|
||||
[#]: collector: (lujun9972)
|
||||
[#]: translator: ( )
|
||||
[#]: reviewer: ( )
|
||||
[#]: publisher: ( )
|
||||
[#]: url: ( )
|
||||
[#]: subject: "Learn the Lisp programming language in 2021"
|
||||
[#]: via: "https://opensource.com/article/21/5/learn-lisp"
|
||||
[#]: author: "Seth Kenlon https://opensource.com/users/seth"
|
||||
[#]: collector: "lkxed"
|
||||
[#]: translator: " "
|
||||
[#]: reviewer: " "
|
||||
[#]: publisher: " "
|
||||
[#]: url: " "
|
||||
|
||||
Learn the Lisp programming language in 2021
|
||||
Let's learn the Lisp programming language
|
||||
======
|
||||
A lot of Lisp code lurks inside big codebases, so it's smart to get
|
||||
familiar with the language.
|
||||
![Woman sitting in front of her laptop][1]
|
||||
A lot of Lisp code lurks inside big codebases, so it's smart to get familiar with the language.
|
||||
|
||||
![Women in tech and computing][1]
|
||||
|
||||
Image by: kris krüg
|
||||
|
||||
Lisp was invented in 1958, which makes it the second-oldest computer programming language. It has spawned several modern derivatives, including Common Lisp, Emacs Lisp (Elisp), Clojure, Racket, Scheme, Fennel, and GNU Guile.
|
||||
|
||||
People who love thinking about the design of programming languages often love Lisp because of how its syntax and data share the same structure: Lisp code is essentially a list of lists, and its name is an acronym for _LISt Processing_. People who love thinking about the aesthetics of programming languages often hate Lisp because of its frequent use of parentheses for scoping; in fact, it's a common joke that Lisp stands for _Lots of Irritating Superfluous Parentheses_.
|
||||
People who love thinking about the design of programming languages often love Lisp because of how its syntax and data share the same structure: Lisp code is essentially a list of lists, and its name is an acronym for *LISt Processing*. People who love thinking about the aesthetics of programming languages often hate Lisp because of its frequent use of parentheses for scoping; in fact, it's a common joke that Lisp stands for *Lots of Irritating Superfluous Parentheses*.
|
||||
|
||||
Whether you love or hate its design philosophies, Lisp is an interesting glimpse at the past and, thanks to Clojure and Guile, into the future. You might be surprised how much Lisp code there is lurking within big codebases in any given industry, so it's a good idea to have at least a passing familiarity with the language.
|
||||
|
||||
### Install Lisp
|
||||
|
||||
There are many implementations of Lisp. Popular open source versions include [SBCL][2] and [GNU Common Lisp][3] (GCL). You can install either of these with your distribution's package manager.
|
||||
There are many implementations of Lisp. Popular open source versions include [SBCL][2], [GNU Lisp][3], and [GNU Common Lisp][4] (GCL). You can install any of these with your distribution's package manager, but for this article I use `clisp`.
|
||||
|
||||
On Fedora Linux:
|
||||
|
||||
|
||||
```
|
||||
`$ sudo dnf install gcl`
|
||||
$ sudo dnf install clisp
|
||||
```
|
||||
|
||||
On Debian:
|
||||
|
||||
|
||||
```
|
||||
`$ sudo apt install gcl`
|
||||
$ sudo apt install clisp
|
||||
```
|
||||
|
||||
For macOS, you can use [MacPorts][4] or [Homebrew][5]:
|
||||
|
||||
For macOS, you can use [MacPorts][5] or [Homebrew][6]:
|
||||
|
||||
```
|
||||
`$ sudo port install gcl`
|
||||
$ sudo port install clisp
|
||||
```
|
||||
|
||||
For Windows, download a binary from [gnu.org/software/gcl][6].
|
||||
For Windows, you can either use [clisp on Cygwin][7] or download a GCL binary from [gnu.org/software/gcl][8].
|
||||
|
||||
For this article, I'm using GCL and its `clisp` command, but most of the principles apply to any Lisp.
|
||||
Even though I'm using the `clisp` command, most of the principles in this article apply to any Lisp. Should you choose to use a different Lisp implementation, the command to run Lisp code is different from what I use in this article (`gcl` or `sbcl` instead of `clisp`, for example) but everything else is the same.
|
||||
|
||||
### List processing
|
||||
|
||||
The basic unit of Lisp source code is an _expression_, which is written as a list. For instance, this is a list of an operator (`+`) and two integers (`1` and `2`):
|
||||
|
||||
The basic unit of Lisp source code is an *expression*, which is written as a list. For instance, this is a list of an operator (`+` ) and two integers (`1` and `2` ):
|
||||
|
||||
```
|
||||
`(+ 1 2)`
|
||||
(+ 1 2)
|
||||
```
|
||||
|
||||
It's also a Lisp expression, using a symbol (`+`) that evaluates to a function (addition) and two arguments (`1` and `2`). You can run this expression and others in an interactive Common Lisp environment called REPL (read-eval-print loop). If you're familiar with Python's IDLE, Lisp's REPL should feel somewhat familiar to you.
|
||||
It's also a Lisp expression, using a symbol (`+` ) that evaluates to a function (addition) and two arguments (`1` and `2` ). You can run this expression and others in an interactive Common Lisp environment called REPL (read-eval-print loop). If you're familiar with Python's IDLE, Lisp's REPL should feel somewhat familiar to you.
|
||||
|
||||
To launch a REPL, launch Common Lisp:
|
||||
|
||||
|
||||
```
|
||||
$ clisp
|
||||
[1]>
|
||||
[1]>
|
||||
```
|
||||
|
||||
At the REPL prompt, type a few expressions:
|
||||
|
||||
|
||||
```
|
||||
[1]> (+ 1 2)
|
||||
[1]> (+ 1 2)
|
||||
3
|
||||
[2]> (- 1 2)
|
||||
[2]> (- 1 2)
|
||||
-1
|
||||
[3]> (- 2 1)
|
||||
[3]> (- 2 1)
|
||||
1
|
||||
[4]> (+ 2 3 4)
|
||||
[4]> (+ 2 3 4)
|
||||
9
|
||||
```
|
||||
|
||||
@ -85,109 +81,100 @@ At the REPL prompt, type a few expressions:
|
||||
|
||||
Now that you know the basic structure of a Lisp expression, you can utilize Lisp functions in useful ways. The `print` function takes any argument you provide and displays it on your terminal, while the `pprint` function "pretty" prints it. There are other variations on the print function, but `pprint` is nice in REPL:
|
||||
|
||||
|
||||
```
|
||||
[1]> (pprint "hello world")
|
||||
[1]> (pprint "hello world")
|
||||
|
||||
"hello world"
|
||||
|
||||
[2]>
|
||||
[2]>
|
||||
```
|
||||
|
||||
You can create your own functions with `defun`. The `defun` function requires a name for your function and any parameters you want your function to accept:
|
||||
|
||||
|
||||
```
|
||||
[1]> (defun myprinter (s) (pprint s))
|
||||
[1]> (defun myprinter (s) (pprint s))
|
||||
MYPRINTER
|
||||
[2]> (myprinter "hello world")
|
||||
[2]> (myprinter "hello world")
|
||||
|
||||
"hello world"
|
||||
|
||||
[3]>
|
||||
[3]>
|
||||
```
|
||||
|
||||
### Variables
|
||||
|
||||
You can create variables in Lisp with `setf`:
|
||||
|
||||
You can create variables in Lisp with `setf` :
|
||||
|
||||
```
|
||||
[1]> (setf foo "hello world")
|
||||
[1]> (setf foo "hello world")
|
||||
"hello world"
|
||||
[2]> (pprint foo)
|
||||
[2]> (pprint foo)
|
||||
|
||||
"hello world"
|
||||
|
||||
[3]>
|
||||
[3]>
|
||||
```
|
||||
|
||||
You can nest expressions within expressions in a kind of pipeline. For instance, you can pretty print the contents of your variable after invoking the `string-upcase` function to convert its characters to uppercase:
|
||||
|
||||
|
||||
```
|
||||
[3]> (pprint (string-upcase foo))
|
||||
[3]> (pprint (string-upcase foo))
|
||||
|
||||
"HELLO WORLD"
|
||||
|
||||
[4]>
|
||||
[4]>
|
||||
```
|
||||
|
||||
Lisp is dynamically typed in the sense that you don't have to declare variable types when setting them. Lisp treats integers as integers by default:
|
||||
|
||||
|
||||
```
|
||||
[1]> (setf foo 2)
|
||||
[2]> (setf bar 3)
|
||||
[3]> (+ foo bar)
|
||||
[1]> (setf foo 2)
|
||||
[2]> (setf bar 3)
|
||||
[3]> (+ foo bar)
|
||||
5
|
||||
```
|
||||
|
||||
If you intend for an integer to be interpreted as a string, you can quote it:
|
||||
|
||||
|
||||
```
|
||||
[4]> (setf foo "2")
|
||||
"2"
|
||||
[5]> (setf bar "3")
|
||||
[4]> (setf foo "2")
|
||||
"2"
|
||||
[5]> (setf bar "3")
|
||||
"3"
|
||||
[6]> (+ foo bar)
|
||||
[6]> (+ foo bar)
|
||||
|
||||
*** - +: "2" is not a number
|
||||
The following restarts are available:
|
||||
USE-VALUE :R1 Input a value to be used instead.
|
||||
ABORT :R2 Abort main loop
|
||||
Break 1 [7]>
|
||||
Break 1 [7]>
|
||||
```
|
||||
|
||||
In this sample REPL session, both `foo` and `bar` are set to quoted numbers, so Lisp interprets them as strings. Math operators can't be used on strings, so REPL drops into a debugger mode. To get out of the debugger, press **Ctrl+D** on your keyboard.
|
||||
|
||||
You can do some introspection on objects using the `typep` function, which tests for a specific data type. The tokens `T` and `NIL` represent _True_ and _False_, respectively.
|
||||
|
||||
You can do some introspection on objects using the `typep` function, which tests for a specific data type. The tokens `T` and `NIL` represent *True* and *False*, respectively.
|
||||
|
||||
```
|
||||
[4]> (typep foo 'string)
|
||||
[4]> (typep foo 'string)
|
||||
NIL
|
||||
[5]> (typep foo 'integer)
|
||||
[5]> (typep foo 'integer)
|
||||
T
|
||||
```
|
||||
|
||||
The single quote (`'`) before `string` and `integer` prevents Lisp from (incorrectly) evaluating those keywords as variables:
|
||||
|
||||
The single quote (`'` ) before `string` and `integer` prevents Lisp from (incorrectly) evaluating those keywords as variables:
|
||||
|
||||
```
|
||||
[6]> (typep foo string)
|
||||
[6]> (typep foo string)
|
||||
*** - SYSTEM::READ-EVAL-PRINT: variable STRING has no value
|
||||
[...]
|
||||
```
|
||||
|
||||
It's a shorthand way to protect the terms, normally done with the `quote` function:
|
||||
|
||||
|
||||
```
|
||||
[7]> (typep foo (quote string))
|
||||
[7]> (typep foo (quote string))
|
||||
NIL
|
||||
[5]> (typep foo (quote integer))
|
||||
[5]> (typep foo (quote integer))
|
||||
T
|
||||
```
|
||||
|
||||
@ -195,19 +182,17 @@ T
|
||||
|
||||
Unsurprisingly, you can also create lists in Lisp:
|
||||
|
||||
|
||||
```
|
||||
[1]> (setf foo (list "hello" "world"))
|
||||
[1]> (setf foo (list "hello" "world"))
|
||||
("hello" "world")
|
||||
```
|
||||
|
||||
Lists can be indexed with the `nth` function:
|
||||
|
||||
|
||||
```
|
||||
[2]> (nth 0 foo)
|
||||
[2]> (nth 0 foo)
|
||||
"hello"
|
||||
[3]> (pprint (string-capitalize (nth 1 foo)))
|
||||
[3]> (pprint (string-capitalize (nth 1 foo)))
|
||||
|
||||
"World"
|
||||
```
|
||||
@ -216,19 +201,17 @@ Lists can be indexed with the `nth` function:
|
||||
|
||||
To end a REPL session, press **Ctrl+D** on your keyboard, or use the `quit` keyword in Lisp:
|
||||
|
||||
|
||||
```
|
||||
[99]> (quit)
|
||||
[99]> (quit)
|
||||
$
|
||||
```
|
||||
|
||||
### Scripting
|
||||
|
||||
Lisp can be compiled or used as an interpreted scripting language. The latter is probably the easiest option when you're starting, especially if you're already familiar with Python or [shell scripting][7].
|
||||
Lisp can be compiled or used as an interpreted scripting language. The latter is probably the easiest option when you're starting, especially if you're already familiar with Python or [shell scripting][9].
|
||||
|
||||
Here's a simple dice roller script written in GNU Common Lisp:
|
||||
|
||||
|
||||
```
|
||||
#!/usr/bin/clisp
|
||||
|
||||
@ -241,26 +224,24 @@ Here's a simple dice roller script written in GNU Common Lisp:
|
||||
(roller userput)
|
||||
```
|
||||
|
||||
The first line tells your [POSIX][8] terminal what executable to use to run the script.
|
||||
The first line tells your [POSIX][10] terminal what executable to use to run the script.
|
||||
|
||||
The `roller` function, created with `defun`, uses the `random` function to print a pseudo-random number up to, and not including, the zeroth item of the `num` list. The `num` list hasn't been created yet in the script, but the function doesn't get executed until it's called.
|
||||
|
||||
The next line assigns any argument provided to the script at launch time to a variable called `userput`. The `userput` variable is a list, and it's what becomes `num` once it's passed to the `roller` function.
|
||||
|
||||
The penultimate line of the script starts a _random seed_. This provides Lisp with enough entropy to generate a mostly random number.
|
||||
The penultimate line of the script starts a *random seed*. This provides Lisp with enough entropy to generate a mostly random number.
|
||||
|
||||
The final line invokes the custom `roller` function, providing the `userput` list as its sole argument.
|
||||
|
||||
Save the file as `dice.lisp` and mark it executable:
|
||||
|
||||
|
||||
```
|
||||
`$ chmod +x dice.lisp`
|
||||
$ chmod +x dice.lisp
|
||||
```
|
||||
|
||||
Finally, try running it, providing it with a maximum number from which to choose its random number:
|
||||
|
||||
|
||||
```
|
||||
$ ./dice.lisp 21
|
||||
|
||||
@ -275,9 +256,11 @@ $ ./dice.lisp 21
|
||||
|
||||
Not bad!
|
||||
|
||||
You may notice that your emulated die has a pontential value of 0, and never reaches the maximum number you provide to it as an argument. In other words, this script never rolls 20 on a 20-sided die (unless you count 0 as 20). There's a simple fix to this, and you only need the knowledge gained from this article to do it. Can you fix this bug?
|
||||
|
||||
### Learn Lisp
|
||||
|
||||
Whether you can imagine using Lisp as a utilitarian language for personal scripts, to advance your career, or just as a fun experiment, you can see some particularly inventive uses at the annual [Lisp Game Jam][9] (most submissions are open source, so you can view the code to learn from what you play).
|
||||
Whether you can imagine using Lisp as a utilitarian language for personal scripts, to advance your career, or just as a fun experiment, you can see some particularly inventive uses at the annual [Lisp Game Jam][11] (most submissions are open source, so you can view the code to learn from what you play).
|
||||
|
||||
Lisp is a fun and unique language with an ever-growing developer base and enough historic and emerging dialects to keep programmers from all disciplines happy.
|
||||
|
||||
@ -286,20 +269,22 @@ Lisp is a fun and unique language with an ever-growing developer base and enough
|
||||
via: https://opensource.com/article/21/5/learn-lisp
|
||||
|
||||
作者:[Seth Kenlon][a]
|
||||
选题:[lujun9972][b]
|
||||
选题:[lkxed][b]
|
||||
译者:[译者ID](https://github.com/译者ID)
|
||||
校对:[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译,[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
||||
[a]: https://opensource.com/users/seth
|
||||
[b]: https://github.com/lujun9972
|
||||
[1]: https://opensource.com/sites/default/files/styles/image-full-size/public/lead-images/OSDC_women_computing_4.png?itok=VGZO8CxT (Woman sitting in front of her laptop)
|
||||
[b]: https://github.com/lkxed
|
||||
[1]: https://opensource.com/sites/default/files/lead-images/OSDC_women_computing_4.png
|
||||
[2]: http://sbcl.org
|
||||
[3]: https://www.gnu.org/software/gcl/
|
||||
[4]: https://opensource.com/article/20/11/macports
|
||||
[5]: https://opensource.com/article/20/6/homebrew-linux
|
||||
[6]: http://mirror.lagoon.nc/gnu/gcl/binaries/stable
|
||||
[7]: https://opensource.com/article/20/4/bash-programming-guide
|
||||
[8]: https://opensource.com/article/19/7/what-posix-richard-stallman-explains
|
||||
[9]: https://itch.io/jam/spring-lisp-game-jam-2021
|
||||
[3]: http://clisp.org
|
||||
[4]: https://www.gnu.org/software/gcl/
|
||||
[5]: https://opensource.com/article/20/11/macports
|
||||
[6]: https://opensource.com/article/20/6/homebrew-linux
|
||||
[7]: https://cygwin.fandom.com/wiki/Clisp
|
||||
[8]: http://mirror.lagoon.nc/gnu/gcl/binaries/stable
|
||||
[9]: https://opensource.com/article/20/4/bash-programming-guide
|
||||
[10]: https://opensource.com/article/19/7/what-posix-richard-stallman-explains
|
||||
[11]: https://itch.io/jam/spring-lisp-game-jam-2021
|
||||
|
@ -1,273 +0,0 @@
|
||||
[#]: subject: "How To Boot Into Rescue Mode Or Emergency Mode In Ubuntu 22.04 / 20.04 / 18.04"
|
||||
[#]: via: "https://ostechnix.com/how-to-boot-into-rescue-mode-or-emergency-mode-in-ubuntu-18-04/"
|
||||
[#]: author: "sk https://ostechnix.com/author/sk/"
|
||||
[#]: collector: "lkxed"
|
||||
[#]: translator: "robsean"
|
||||
[#]: reviewer: " "
|
||||
[#]: publisher: " "
|
||||
[#]: url: " "
|
||||
|
||||
How To Boot Into Rescue Mode Or Emergency Mode In Ubuntu 22.04 / 20.04 / 18.04
|
||||
======
|
||||
This tutorial explains how to boot into **rescue mode** or **emergency mode**in Ubuntu 22.04, 20.04 and 18.04 LTS editions.
|
||||
|
||||
As you might already know, **Runlevels** are replaced with **Systemd targets** in many Linux distributions such as RHEL 7 / RHEL 8 and Ubuntu 16.04 LTS and newer versions. For more details about runlevels and systemd target, refer to [this guide][1].
|
||||
|
||||
This guide is specifically written for Ubuntu, however the steps given below should work on most Linux distributions that use **Systemd** as the default service manager.
|
||||
|
||||
Before getting into the topic, let us have a brief understanding about what is rescue mode and emergency mode and what is the purpose of these both modes.
|
||||
|
||||
### What Is Rescue Mode?
|
||||
|
||||
The **rescue mode** is equivalent to **single user mode** in Linux distributions that use **SysV** as the default service manager. In rescue mode, all local filesystems will be mounted, only some important services will be started. However, no normal services (E.g network services) won't be started.
|
||||
|
||||
The rescue mode is helpful in situations where the system can't boot normally. Also, we can perform some important rescue operations, such as [reset root password][2], in rescue mode.
|
||||
|
||||
### What Is Emergency Mode?
|
||||
|
||||
In contrast to the rescue mode, nothing is started in the **emergency mode**. No services are started, no mount points are mounted, no sockets are established, nothing. All you will have is just a **raw shell**. Emergency mode is suitable for debugging purposes.
|
||||
|
||||
First, we will see how to boot into rescue mode and emergency mode in Ubuntu 22.04 and 20.04 LTS distributions. The procedure for entering rescue mode in Ubuntu 22.04 and 20.04 LTS is exactly the same!
|
||||
|
||||
### Boot Into Rescue Mode In Ubuntu 22.04 / 20.04 LTS
|
||||
|
||||
We can boot into rescue mode in two ways.
|
||||
|
||||
#### Method 1
|
||||
|
||||
Power on your Ubuntu system. Hit the ESC key right after the BIOS logo disappears to display the Grub menu.
|
||||
|
||||
In the GRUB menu, choose the first entry and press **"e"** to edit it.
|
||||
|
||||
![GRUB Menu In Ubuntu 22.04 / 20.04 LTS][3]
|
||||
|
||||
Hit the DOWN arrow and find the line that starts with the word **"linux"** and add the following line at the end of it. To reach the end, just press **CTRL+e** or use the **END** key or **LEFT/RIGHT** arrows in your keyboard.
|
||||
|
||||
```
|
||||
systemd.unit=rescue.target
|
||||
```
|
||||
|
||||
![Edit Grub Boot Menu Entries To Enter Into Rescue Mode In Ubuntu 22.04 / 20.04 LTS][4]
|
||||
|
||||
After adding the above line, hit **Ctrl+x** or**F10** to boot into rescue mode.
|
||||
|
||||
After a few seconds, you will be landed in the rescue mode (single user mode) as root user. You will be prompted to press ENTER to enter the maintenance mode.
|
||||
|
||||
Here is how rescue mode looks like in Ubuntu 22.04 / 20.04 LTS systems:
|
||||
|
||||
![Boot Into Rescue Mode In Ubuntu 22.04 / 20.04 LTS][5]
|
||||
|
||||
Now do whatever you want to do in the rescue mode. You may need to mount the root (**/**) file system in read/write mode before doing any operations in rescue mode.
|
||||
|
||||
```
|
||||
mount -n -o remount,rw /
|
||||
```
|
||||
|
||||
![Mount Root File System In Read Write Mode In Ubuntu 22.04 / 20.04 LTS][6]
|
||||
|
||||
Once done, press **"Ctrl+d"** to boot into normal mode. Alternatively, you can type any one of the following commands to boot into normal mode.
|
||||
|
||||
```
|
||||
systemctl default
|
||||
```
|
||||
|
||||
Or,
|
||||
|
||||
```
|
||||
exit
|
||||
```
|
||||
|
||||
If you want to reboot the system instead of booting into normal mode, enter:
|
||||
|
||||
```
|
||||
systemctl reboot
|
||||
```
|
||||
|
||||
#### Method 2
|
||||
|
||||
In this method, you don't need to edit the grub boot menu entries.
|
||||
|
||||
Power on the system and choose **"Advanced options for Ubuntu"** from the Grub boot menu.
|
||||
|
||||
![Choose Advanced Options For Ubuntu From Grub Boot Menu][7]
|
||||
|
||||
Next, you will see the list of available Ubuntu versions with Kernel versions. Choose the **"Recovery mode"** in the grub boot menu in Ubuntu.
|
||||
|
||||
![Choose Recovery Mode In Grub Boot Menu In Ubuntu 22.04 / 20.04 LTS][8]
|
||||
|
||||
After a few seconds, you will see the Ubuntu recovery menu. From the recovery menu, choose **"Drop to root shell prompt"** option and hit the ENTER key.
|
||||
|
||||
![Enter Into Root Shell Prompt In Ubuntu 22.04 / 20.04 LTS][9]
|
||||
|
||||
Now you will be landed in the rescue mode.
|
||||
|
||||
![Ubuntu Maintenance Mode][10]
|
||||
|
||||
Mount the root (**/**) file system in read/write mode by entering the following command:
|
||||
|
||||
```
|
||||
mount -n -o remount,rw /
|
||||
```
|
||||
|
||||
![Mount Root File System In Read Write Mode In Ubuntu][11]
|
||||
|
||||
Do whatever you want to do in the rescue mode.
|
||||
|
||||
Once done, type exit to return back to the recovery menu.
|
||||
|
||||
```
|
||||
exit
|
||||
```
|
||||
|
||||
Finally, choose **"Resume normal boot"** option and hit the ENTER key.
|
||||
|
||||
![Boot Into Normal Mode In Ubuntu][12]
|
||||
|
||||
Press ENTER key again to exit recovery mode and continue booting into normal mode.
|
||||
|
||||
![Exit The Recovery Mode In Ubuntu][13]
|
||||
|
||||
If you don't want to boot into normal mode, type **"reboot"** and press ENTER from the maintenance mode to restart your system.
|
||||
|
||||
### Boot Into Emergency Mode In Ubuntu 22.04 / 20.04 LTS
|
||||
|
||||
When the GRUB boot menu appears, press **"e"** to edit it.
|
||||
|
||||
![GRUB Menu In Ubuntu 22.04 / 20.04 LTS][14]
|
||||
|
||||
Find the line that starts with the word **"linux"** and add the following line at the end of it.
|
||||
|
||||
```
|
||||
systemd.unit=emergency.target
|
||||
```
|
||||
|
||||
![Edit Grub Boot Menu Entries To Enter Into Emergency Mode In Ubuntu 22.04 / 20.04 LTS][15]
|
||||
|
||||
After adding the above line, hit **Ctrl+x** or**F10** to boot into emergency mode.
|
||||
|
||||
After a few seconds, you will be landed in the emergency mode as `root` user. You will be prompted to press ENTER to enter the maintenance mode.
|
||||
|
||||
Here is how emergency mode looks like in Ubuntu 22.04 / 20.04 LTS system:
|
||||
|
||||
![Boot Into Emergency Mode In Ubuntu 22.04 / 20.04 LTS][16]
|
||||
|
||||
Now do whatever you want to do in the emergency mode. You may need to mount the root (**/**) file system in read/write mode before doing any operations in this mode.
|
||||
|
||||
```
|
||||
mount -n -o remount,rw /
|
||||
```
|
||||
|
||||
Once done, press **"Ctrl+d"** to boot into normal mode. Alternatively, you can type any one of the following commands to boot into normal mode.
|
||||
|
||||
```
|
||||
systemctl default
|
||||
```
|
||||
|
||||
Or,
|
||||
|
||||
```
|
||||
exit
|
||||
```
|
||||
|
||||
If you want to reboot the system instead of booting into normal mode, enter:
|
||||
|
||||
```
|
||||
systemctl reboot
|
||||
```
|
||||
|
||||
### Boot Into Rescue Mode In Ubuntu 18.04 LTS
|
||||
|
||||
Boot your Ubuntu system. When the Grub menu appears, choose the first entry and press **e** to edit. (To reach the end, just press **CTRL+e** or use the END key or LEFT/RIGHT arrows in your keyboard):
|
||||
|
||||
![Grub Menu][17]
|
||||
|
||||
If you don't see the Grub menu, just hit ESC key right after the BIOS logo disappears.
|
||||
|
||||
Find the line that starts with word **"linux"**and add the following line at the end of that line (To reach the end, just press **CTRL+e** or use the END key or LEFT/RIGHT arrows in your keyboard):
|
||||
|
||||
```
|
||||
systemd.unit=rescue.target
|
||||
```
|
||||
|
||||
![Edit Grub Menu][18]
|
||||
|
||||
Once you added the above line, just press **CTRL+x** or **F10** to continue to boot into rescue mode. After a few seconds, you will be landed in the rescue mode (single user mode) as root user.
|
||||
|
||||
Here is how rescue mode looks like in Ubuntu 18.04 LTS server:
|
||||
|
||||
![Ubuntu Rescue Mode][19]
|
||||
|
||||
Next, type the following command to mount root (**/**) file system into read/write mode.
|
||||
|
||||
```
|
||||
mount -n -o remount,rw /
|
||||
```
|
||||
|
||||
### Boot Into Emergency Mode
|
||||
|
||||
Booting your Ubuntu into emergency is as same as above method. All you have to do is replace **"systemd.unit=rescue.target"** with **"systemd.unit=emergency.target"** when editing grub menu.
|
||||
|
||||
![Edit Grub Menu][20]
|
||||
|
||||
Once you added "systemd.unit=emergency.target", press **Ctrl+x** or **F10** to continue booting into emergency mode.
|
||||
|
||||
![Ubuntu Emergency Mode][21]
|
||||
|
||||
Finally, you can mount root filesystem into read/write mode with command:
|
||||
|
||||
```
|
||||
mount -n -o remount,rw /
|
||||
```
|
||||
|
||||
### Switch Between Rescue And Emergency Modes
|
||||
|
||||
If you are in rescue mode, you don't have to edit the grub boot entry as I mentioned above. Instead, just type the following command to switch to emergency mode instantly:
|
||||
|
||||
```
|
||||
systemctl emergency
|
||||
```
|
||||
|
||||
Similarly, to switch from emergency to rescue mode, type:
|
||||
|
||||
```
|
||||
systemctl rescue
|
||||
```
|
||||
|
||||
### Conclusion
|
||||
|
||||
You know now what is rescue and emergency modes and how to boot into those modes in Ubuntu 22.04, 20.04 and 18.04 LTS systems. Like I already mentioned, the steps provided here will work on many recent Linux versions that uses Systemd.
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://ostechnix.com/how-to-boot-into-rescue-mode-or-emergency-mode-in-ubuntu-18-04/
|
||||
|
||||
作者:[sk][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://ostechnix.com/author/sk/
|
||||
[b]: https://github.com/lkxed
|
||||
[1]: https://ostechnix.com/check-runlevel-linux/
|
||||
[2]: https://ostechnix.com/how-to-reset-or-recover-root-user-password-in-linux/
|
||||
[3]: https://ostechnix.com/wp-content/uploads/2022/05/GRUB-Menu-In-Ubuntu-22.04-LTS.png
|
||||
[4]: https://ostechnix.com/wp-content/uploads/2022/05/Edit-Grub-Boot-Menu-Entries-To-Enter-Into-Rescue-Mode-In-Ubuntu-22.04-LTS.png
|
||||
[5]: https://ostechnix.com/wp-content/uploads/2022/05/Boot-Into-Rescue-Mode-In-Ubuntu-22.04.png
|
||||
[6]: https://ostechnix.com/wp-content/uploads/2022/05/Mount-Root-File-System-In-Read-Write-Mode-In-Ubuntu.png
|
||||
[7]: https://ostechnix.com/wp-content/uploads/2022/05/Choose-Advanced-Options-For-Ubuntu-From-Grub-Boot-Menu.png
|
||||
[8]: https://ostechnix.com/wp-content/uploads/2022/05/Choose-Recovery-Mode-In-Grub-Boot-Menu-In-Ubuntu.png
|
||||
[9]: https://ostechnix.com/wp-content/uploads/2022/05/Enter-Into-Root-Shell-Prompt-In-Ubuntu.png
|
||||
[10]: https://ostechnix.com/wp-content/uploads/2022/05/Ubuntu-Maintenance-Mode.png
|
||||
[11]: https://ostechnix.com/wp-content/uploads/2022/05/Mount-Root-File-System-In-Read-Write-Mode-In-Ubuntu-1.png
|
||||
[12]: https://ostechnix.com/wp-content/uploads/2022/05/Boot-Into-Normal-Mode-In-Ubuntu.png
|
||||
[13]: https://ostechnix.com/wp-content/uploads/2022/05/Exit-The-Recovery-Mode-In-Ubuntu.png
|
||||
[14]: https://ostechnix.com/wp-content/uploads/2022/05/GRUB-Menu-In-Ubuntu-22.04-LTS.png
|
||||
[15]: https://ostechnix.com/wp-content/uploads/2022/05/Edit-Grub-Boot-Menu-Entries-To-Enter-Into-Emergency-Mode-In-Ubuntu.png
|
||||
[16]: https://ostechnix.com/wp-content/uploads/2018/12/Boot-Into-Emergency-Mode-In-Ubuntu-20.04-LTS.png
|
||||
[17]: https://ostechnix.com/wp-content/uploads/2018/12/Grub-menu.png
|
||||
[18]: https://ostechnix.com/wp-content/uploads/2018/12/Edit-grub-menu.png
|
||||
[19]: https://ostechnix.com/wp-content/uploads/2018/12/Ubuntu-rescue-mode.png
|
||||
[20]: https://ostechnix.com/wp-content/uploads/2018/12/emergency-mode.png
|
||||
[21]: https://ostechnix.com/wp-content/uploads/2018/12/emergency-mode-1.png
|
@ -1,155 +0,0 @@
|
||||
[#]: subject: "How Garbage Collection works inside a Java Virtual Machine"
|
||||
[#]: via: "https://opensource.com/article/22/6/garbage-collection-java-virtual-machine"
|
||||
[#]: author: "Jayashree Huttanagoudar https://opensource.com/users/jayashree-huttanagoudar"
|
||||
[#]: collector: "lkxed"
|
||||
[#]: translator: "lkxed"
|
||||
[#]: reviewer: " "
|
||||
[#]: publisher: " "
|
||||
[#]: url: " "
|
||||
|
||||
How Garbage Collection works inside a Java Virtual Machine
|
||||
======
|
||||
Understanding how Java handles memory isn't always necessary, but it can help you envision how the JVM deals with your variables and class instances.
|
||||
|
||||
![Coffee beans][1]
|
||||
|
||||
Image by: Pixabay. CC0.
|
||||
|
||||
Automatic Garbage Collection (GC) is one of the most important features that makes Java so popular. This article explains why GC is essential. It includes automatic and generational GC, how the Java Virtual Machine (JVM) divides heap memory, and finally, how GC works inside the JVM.
|
||||
|
||||
### Java memory allocation
|
||||
|
||||
Java memory is divided into four sections:
|
||||
|
||||
1. Heap: The memory for object instances is allocated in the heap. When the object declaration is made, there won't be any memory allocated in the heap. Instead, a reference is created for that object in the stack.
|
||||
2. Stack: This section allocates the memory for methods, local variables, and class instance variables.
|
||||
3. Code: Bytecode resides in this section.
|
||||
4. Static: Static data and methods are placed in this section.
|
||||
|
||||
### What is automatic Garbage Collection (GC)?
|
||||
|
||||
Automatic GC is a process in which the referenced and unreferenced objects in heap memory are identified, and then unreferenced objects are considered for deletion. The term *referenced objects* means some part of your program is using those objects. *Unreferenced objects* are not currently being used by the program.
|
||||
|
||||
Programming languages like C and C++ require manual allocation and deallocation of memory. This is automatically handled by GC in Java, although you can trigger GC manually with the `system.gc();` call in your code.
|
||||
|
||||
The fundamental steps of GC are:
|
||||
|
||||
#### 1. Mark used and unused objects
|
||||
|
||||
In this step, the used and unused objects are marked separately. This is a time-consuming process, as all objects in memory must be scanned to determine whether they're in use or not.
|
||||
|
||||
![Marking used and unused objects][2]
|
||||
|
||||
#### 2. Sweep/Delete objects
|
||||
|
||||
There are two variations of sweep and delete.
|
||||
|
||||
**Simple deletion**: Only unreferenced objects are removed. However, the memory allocation for new objects becomes difficult as the free space is scattered across available memory.
|
||||
|
||||
![Normal deleting process][3]
|
||||
|
||||
**Deletion with compaction**: Apart from deleting unreferenced objects, referenced objects are compacted. Memory allocation for new objects is relatively easy, and memory allocation performance is improved.
|
||||
|
||||
![Deletion with compacting][4]
|
||||
|
||||
### What is generational Garbage Collection (GC), and why is it needed?
|
||||
|
||||
As seen in the sweep and delete model, scanning all objects for memory reclamation from unused objects becomes difficult once the objects keep growing. An experimental study shows that most objects created during the program execution are short-lived.
|
||||
|
||||
The existence of short-lived objects can be used to improve the performance of GC. For that, the JVM divides the memory into different generations. Next, it categorizes the objects based on these memory generations and performs the GC accordingly. This approach is known as *generational GC*.
|
||||
|
||||
### Heap memory generations and the generational Garbage Collection (GC) process
|
||||
|
||||
To improve the performance of the GC mark and sweep steps, the JVM divides the heap memory into three generations:
|
||||
|
||||
* Young Generation
|
||||
* Old Generation
|
||||
* Permanent Generation
|
||||
|
||||
![Hotspot heap structure][5]
|
||||
|
||||
Here is a description of each generation and its key features.
|
||||
|
||||
#### Young Generation
|
||||
|
||||
All created objects are present here. The young generation is further divided into:
|
||||
|
||||
1. Eden: All newly created objects are allocated with the memory here.
|
||||
2. Survivor space (S0 and S1): After surviving one GC, the live objects are moved to one of these survivor spaces.
|
||||
|
||||
![Object allocation][6]
|
||||
|
||||
The generational GC that happens in the Young Generation is known as *Minor GC*. All Minor GC cycles are "Stop the World" events that cause the other applications to pause until it completes the GC cycle. This is why Minor GC cycles are faster.
|
||||
|
||||
To summarize: Eden space has all newly created objects. Once Eden is full, the first Minor GC cycle is triggered.
|
||||
|
||||
![Filling Eden space][7]
|
||||
|
||||
Minor GC: The live and dead objects are marked during this cycle. The live objects are moved to survivor space S0. Once all live objects are moved to S0, the unreferenced objects are deleted.
|
||||
|
||||
![Copying referenced objects][8]
|
||||
|
||||
The age of objects in S0 is 1 because they have survived one Minor GC. Now Eden and S1 are empty.
|
||||
|
||||
Once cleared, the Eden space is again filled with new live objects. As time elapses, some objects in Eden and S0 become dead (unreferenced), and Eden's space is full again, triggering the Minor GC.
|
||||
|
||||
![Object aging][9]
|
||||
|
||||
This time the dead and live objects in Eden and S0 are marked. The live objects from Eden are moved to S1 with an age increment of 1. The live objects from S0 are also moved to S1 with an age increment of 2 (because they've now survived two Minor GCs). At this point, S0 and Eden are empty. After every Minor GC, Eden and one of the survivor spaces are empty.
|
||||
|
||||
The same cycle of creating new objects in Eden continues. When the next Minor GC occurs, Eden and S1 are cleared by moving the aged objects to S0. The survivor spaces switch after every Minor GC.
|
||||
|
||||
![Additional aging][10]
|
||||
|
||||
This process continues until the age of one of the surviving objects reaches a certain threshold, at which point it is moved to the so-called the Old Generation with a process called *promotion*.
|
||||
|
||||
Further, the `-Xmn` flag sets the Young Generation size.
|
||||
|
||||
### Old Generation (Tenured Generation)
|
||||
|
||||
This generation contains the objects that have survived several Minor GCs and aged to reach an expected threshold.
|
||||
|
||||
![Promotion][11]
|
||||
|
||||
In the example diagram above, the threshold is 8. The GC in the Old Generation is known as a *Major GC*. Use the flags `-Xms` and `-Xmx` to set the initial and maximum size of the heap memory.
|
||||
|
||||
### Permanent Generation
|
||||
|
||||
The Permanent Generation space stores metadata related to library classes and methods of an application, J2SE, and what's in use by the JVM itself. The JVM populates this data at runtime based on which classes and methods are in use. Once the JVM finds the unused classes, they are unloaded or collected, making space for used classes.
|
||||
|
||||
Use the flags `-XX:PermGen` and `-XX:MaxPermGen` to set the initial and maximum size of the Permanent Generation.
|
||||
|
||||
#### Metaspace
|
||||
|
||||
Metaspace was introduced in Java 8u and replaced PermGen. The advantage of this is automatic resizing, which avoids OutOfMemory errors.
|
||||
|
||||
### Wrap up
|
||||
|
||||
This article discusses the various memory generations of JVM and how they are helpful for automatic generational Garbage Collection (GC). Understanding how Java handles memory isn't always necessary, but it can help you envision how the JVM deals with your variables and class instances. This understanding allows you to plan and troubleshoot your code and comprehend potential limitations inherent in a specific platform.
|
||||
|
||||
Image by: (Jayashree Huttanagoudar, CC BY-SA 4.0)
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://opensource.com/article/22/6/garbage-collection-java-virtual-machine
|
||||
|
||||
作者:[Jayashree Huttanagoudar][a]
|
||||
选题:[lkxed][b]
|
||||
译者:[译者ID](https://github.com/译者ID)
|
||||
校对:[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译,[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
||||
[a]: https://opensource.com/users/jayashree-huttanagoudar
|
||||
[b]: https://github.com/lkxed
|
||||
[1]: https://opensource.com/sites/default/files/lead-images/java-coffee-beans.jpg
|
||||
[2]: https://opensource.com/sites/default/files/2022-06/1Marking.png
|
||||
[3]: https://opensource.com/sites/default/files/2022-06/2NormalDeletion.png
|
||||
[4]: https://opensource.com/sites/default/files/2022-06/3DeletionwithCompacting.png
|
||||
[5]: https://opensource.com/sites/default/files/2022-06/4Hotspot.png
|
||||
[6]: https://opensource.com/sites/default/files/2022-06/5ObjAllocation.png
|
||||
[7]: https://opensource.com/sites/default/files/2022-06/6FillingEden.png
|
||||
[8]: https://opensource.com/sites/default/files/2022-06/7CopyingRefdObjs.png
|
||||
[9]: https://opensource.com/sites/default/files/2022-06/8ObjAging.png
|
||||
[10]: https://opensource.com/sites/default/files/2022-06/9AddlAging.png
|
||||
[11]: https://opensource.com/sites/default/files/2022-06/10Promotion.png
|
374
sources/tech/20220610 Handling maps in Groovy vs Java.md
Normal file
374
sources/tech/20220610 Handling maps in Groovy vs Java.md
Normal file
@ -0,0 +1,374 @@
|
||||
[#]: subject: "Handling maps in Groovy vs Java"
|
||||
[#]: via: "https://opensource.com/article/22/6/maps-groovy-vs-java"
|
||||
[#]: author: "Chris Hermansen https://opensource.com/users/clhermansen"
|
||||
[#]: collector: "lkxed"
|
||||
[#]: translator: " "
|
||||
[#]: reviewer: " "
|
||||
[#]: publisher: " "
|
||||
[#]: url: " "
|
||||
|
||||
Handling maps in Groovy vs Java
|
||||
======
|
||||
Discover the differences in map handling between Groovy and Java with this hands-on demo.
|
||||
|
||||
![women programming][1]
|
||||
|
||||
Image by: WOCinTech Chat. Modified by Opensource.com. CC BY-SA 4.0
|
||||
|
||||
Java is a great programming language, but sometimes I want a Java-like language that's just a bit more flexible and compact. That's when I opt for [Groovy][2].
|
||||
|
||||
In a recent article, I reviewed some of the differences between [creating and initializing maps in Groovy][3] and doing the same thing in Java. In brief, Groovy has a concise syntax for setting up maps and accessing map entries compared to the effort necessary in Java.
|
||||
|
||||
This article will delve into more differences in map handling between Groovy and Java. For that purpose, I will use the [sample table of employees][4] used for demoing the JavaScript DataTables library. To follow along, start by making sure you have recent versions of Groovy and Java installed on your computer.
|
||||
|
||||
### Install Java and Groovy
|
||||
|
||||
Groovy is based on Java and requires a Java installation as well. A recent and/or decent version of Java and Groovy might already be in your Linux distribution's repositories, or you can download and install Groovy from the [Apache Groovy website][5]. A good option for Linux users is [SDKMan][6], which can be used to get multiple versions of Java, Groovy, and many other related tools. For this article, I'm using SDK's releases of:
|
||||
|
||||
* Java: version 11.0.12-open of OpenJDK 11
|
||||
* Groovy: version 3.0.8.
|
||||
|
||||
### Back to the problem: maps
|
||||
|
||||
First, in my experience, maps and lists (or at least arrays) often end up in the same program. For example, processing an input file is very similar to passing over a list; often, I do that when I want to categorize data encountered in the input file (or list), storing some kind of value in lookup tables, which are just maps.
|
||||
|
||||
Second, Java 8 introduced the whole Streams functionality and lambdas (or anonymous functions). In my experience, converting input data (or lists) into maps often involves using Java Streams. Moreover, Java Streams are at their most flexible when dealing with streams of typed objects, providing grouping and accumulation facilities out of the box.
|
||||
|
||||
### Employee list processing in Java
|
||||
|
||||
Here's a concrete example based on those fictitious employee records. Below is a Java program that defines an Employee class to hold the employee information, builds a list of Employee instances, and processes that list in a few different ways:
|
||||
|
||||
```
|
||||
1 import java.lang.*;
|
||||
2 import java.util.Arrays;
|
||||
|
||||
3 import java.util.Locale;
|
||||
4 import java.time.format.DateTimeFormatter;
|
||||
5 import java.time.LocalDate;
|
||||
6 import java.time.format.DateTimeParseException;
|
||||
7 import java.text.NumberFormat;
|
||||
8 import java.text.ParseException;
|
||||
|
||||
9 import java.util.stream.Collectors;
|
||||
|
||||
10 public class Test31 {
|
||||
|
||||
11 static public void main(String args[]) {
|
||||
|
||||
12 var employeeList = Arrays.asList(
|
||||
13 new Employee("Tiger Nixon", "System Architect",
|
||||
14 "Edinburgh", "5421", "2011/04/25", "$320,800"),
|
||||
15 new Employee("Garrett Winters", "Accountant",
|
||||
6 "Tokyo", "8422", "2011/07/25", "$170,750"),
|
||||
...
|
||||
|
||||
81 new Employee("Martena Mccray", "Post-Sales support",
|
||||
82 "Edinburgh", "8240", "2011/03/09", "$324,050"),
|
||||
83 new Employee("Unity Butler", "Marketing Designer",
|
||||
84 "San Francisco", "5384", "2009/12/09", "$85,675")
|
||||
85 );
|
||||
|
||||
86 // calculate the average salary across the entire company
|
||||
|
||||
87 var companyAvgSal = employeeList.
|
||||
88 stream().
|
||||
89 collect(Collectors.averagingDouble(Employee::getSalary));
|
||||
90 System.out.println("company avg salary = " + companyAvgSal);
|
||||
|
||||
91 // calculate the average salary for each location,
|
||||
92 // compare to the company average
|
||||
|
||||
93 var locationAvgSal = employeeList.
|
||||
94 stream().
|
||||
95 collect(Collectors.groupingBy((Employee e) ->
|
||||
96 e.getLocation(),
|
||||
97 Collectors.averagingDouble(Employee::getSalary)));
|
||||
98 locationAvgSal.forEach((k,v) ->
|
||||
99 System.out.println(k + " avg salary = " + v +
|
||||
100 "; diff from avg company salary = " +
|
||||
101 (v - companyAvgSal)));
|
||||
|
||||
102 // show the employees in Edinburgh approach #1
|
||||
|
||||
103 System.out.print("employee(s) in Edinburgh (approach #1):");
|
||||
104 var employeesInEdinburgh = employeeList.
|
||||
105 stream().
|
||||
106 filter(e -> e.getLocation().equals("Edinburgh")).
|
||||
107 collect(Collectors.toList());
|
||||
108 employeesInEdinburgh.
|
||||
109 forEach(e ->
|
||||
110 System.out.print(" " + e.getSurname() + "," +
|
||||
111 e.getGivenName()));
|
||||
112 System.out.println();
|
||||
|
||||
|
||||
113 // group employees by location
|
||||
|
||||
114 var employeesByLocation = employeeList.
|
||||
115 stream().
|
||||
116 collect(Collectors.groupingBy(Employee::getLocation));
|
||||
|
||||
117 // show the employees in Edinburgh approach #2
|
||||
|
||||
118 System.out.print("employee(s) in Edinburgh (approach #2):");
|
||||
119 employeesByLocation.get("Edinburgh").
|
||||
120 forEach(e ->
|
||||
121 System.out.print(" " + e.getSurname() + "," +
|
||||
122 e.getGivenName()));
|
||||
123 System.out.println();
|
||||
|
||||
124 }
|
||||
125 }
|
||||
|
||||
126 class Employee {
|
||||
127 private String surname;
|
||||
128 private String givenName;
|
||||
129 private String role;
|
||||
130 private String location;
|
||||
131 private int extension;
|
||||
132 private LocalDate hired;
|
||||
133 private double salary;
|
||||
|
||||
134 public Employee(String fullName, String role, String location,
|
||||
135 String extension, String hired, String salary) {
|
||||
136 var nn = fullName.split(" ");
|
||||
137 if (nn.length > 1) {
|
||||
138 this.surname = nn[1];
|
||||
139 this.givenName = nn[0];
|
||||
140 } else {
|
||||
141 this.surname = nn[0];
|
||||
142 this.givenName = "";
|
||||
143 }
|
||||
144 this.role = role;
|
||||
145 this.location = location;
|
||||
146 try {
|
||||
147 this.extension = Integer.parseInt(extension);
|
||||
148 } catch (NumberFormatException nfe) {
|
||||
149 this.extension = 0;
|
||||
150 }
|
||||
151 try {
|
||||
152 this.hired = LocalDate.parse(hired,
|
||||
153 DateTimeFormatter.ofPattern("yyyy/MM/dd"));
|
||||
154 } catch (DateTimeParseException dtpe) {
|
||||
155 this.hired = LocalDate.EPOCH;
|
||||
156 }
|
||||
157 try {
|
||||
158 this.salary = NumberFormat.getCurrencyInstance(Locale.US).
|
||||
159 parse(salary).doubleValue();
|
||||
160 } catch (ParseException pe) {
|
||||
161 this.salary = 0d;
|
||||
162 }
|
||||
163 }
|
||||
|
||||
164 public String getSurname() { return this.surname; }
|
||||
165 public String getGivenName() { return this.givenName; }
|
||||
166 public String getLocation() { return this.location; }
|
||||
167 public int getExtension() { return this.extension; }
|
||||
168 public LocalDate getHired() { return this.hired; }
|
||||
169 public double getSalary() { return this.salary; }
|
||||
170 }
|
||||
```
|
||||
|
||||
Wow, that's a lot of code for a simple demo program! I'll go through it in chunks first.
|
||||
|
||||
Starting at the end, lines 126 through 170 define the `Employee` class used to store employee data. The most important thing to mention here is that the fields of the employee record are of different types, and in Java that generally leads to defining this type of class. You could make this code a bit more compact by using [Project Lombok's @Data][7] annotation to automatically generate the getters (and setters) for the `Employee` class. In more recent versions of Java, I can declare these sorts of things as a record rather than a class, since the whole point is to store data. Storing the data as a list of `Employee` instances facilitates the use of Java streams.
|
||||
|
||||
Lines 12 through 85 create the list of `Employee` instances, so now you've already dealt with 119 of 170 lines.
|
||||
|
||||
There are nine lines of import statements up front. Interestingly, there are no map-related imports! This is partly because I'm using stream methods that yield maps as their results, and partly because I'm using the `var` keyword to declare variables, so the type is inferred by the compiler.
|
||||
|
||||
The interesting parts of the above code happen in lines 86 through 123.
|
||||
|
||||
In lines 87-90, I convert `employeeList` into a stream (line 88) and then use `collect()` to apply the `Collectors.averagingDouble()` method to the `Employee::getSalary` (line 89) method to calculate the average salary across the whole company. This is pure functional list processing; no maps are involved.
|
||||
|
||||
In lines 93-101, I convert `employeeList` into a stream again. I then use the `Collectors.groupingBy()` method to create a map whose keys are employee locations, returned by `e.getLocation()`, and whose values are the average salary for each location, returned by `Collectors.averagingDouble()` again applied to the `Employee::getSalary` method applied to each employee in the location subset, rather than the entire company. That is, the `groupingBy()` method creates subsets by location, which are then averaged. Lines 98-101 use `forEach()` to step through the map entries printing location, average salary, and the difference between the location averages and company average.
|
||||
|
||||
Now, suppose you wanted to look at just those employees located in Edinburgh. One way to accomplish this is shown in lines 103-112, where I use the stream `filter()` method to create a list of only those employees based in Edinburgh and the `forEach()` method to print their names. No maps here, either.
|
||||
|
||||
Another way to solve this problem is shown in lines 113-123. In this method, I create a map where each entry holds a list of employees by location. First, in lines 113-116, I use the `groupingBy()` method to produce the map I want with keys of employee locations whose values are sublists of employees at that location. Then, in lines 117-123, I use the `forEach()` method to print out the sublist of names of employees at the Edinburgh location.
|
||||
|
||||
When we compile and run the above, the output is:
|
||||
|
||||
```
|
||||
company avg salary = 292082.5
|
||||
San Francisco avg salary = 284703.125; diff from avg company salary = -7379.375
|
||||
New York avg salary = 410158.3333333333; diff from avg company salary = 118075.83333333331
|
||||
Singapore avg salary = 357650.0; diff from avg company salary = 65567.5
|
||||
Tokyo avg salary = 206087.5; diff from avg company salary = -85995.0
|
||||
London avg salary = 322476.25; diff from avg company salary = 30393.75
|
||||
Edinburgh avg salary = 261940.7142857143; diff from avg company salary = -30141.78571428571
|
||||
Sydney avg salary = 90500.0; diff from avg company salary = -201582.5
|
||||
employee(s) in Edinburgh (approach #1): Nixon,Tiger Kelly,Cedric Frost,Sonya Flynn,Quinn Rios,Dai Joyce,Gavin Mccray,Martena
|
||||
employee(s) in Edinburgh (approach #2): Nixon,Tiger Kelly,Cedric Frost,Sonya Flynn,Quinn Rios,Dai Joyce,Gavin Mccray,Martena
|
||||
```
|
||||
|
||||
### Employee list processing in Groovy
|
||||
|
||||
Groovy has always provided enhanced facilities for processing lists and maps, partly by extending the Java Collections library and partly by providing closures, which are somewhat like lambdas.
|
||||
|
||||
One outcome of this is that maps in Groovy can easily be used with different types of values. As a result, you can't be pushed into making the auxiliary Employee class; instead, you can just use a map. Let's examine a Groovy version of the same functionality:
|
||||
|
||||
```
|
||||
1 import java.util.Locale
|
||||
2 import java.time.format.DateTimeFormatter
|
||||
3 import java.time.LocalDate
|
||||
4 import java.time.format.DateTimeParseException
|
||||
5 import java.text.NumberFormat
|
||||
6 import java.text.ParseException
|
||||
|
||||
7 def employeeList = [
|
||||
8 ["Tiger Nixon", "System Architect", "Edinburgh",
|
||||
9 "5421", "2011/04/25", "\$320,800"],
|
||||
10 ["Garrett Winters", "Accountant", "Tokyo",
|
||||
11 "8422", "2011/07/25", "\$170,750"],
|
||||
|
||||
...
|
||||
|
||||
76 ["Martena Mccray", "Post-Sales support", "Edinburgh",
|
||||
77 "8240", "2011/03/09", "\$324,050"],
|
||||
78 ["Unity Butler", "Marketing Designer", "San Francisco",
|
||||
79 "5384", "2009/12/09", "\$85,675"]
|
||||
80 ].collect { ef ->
|
||||
81 def surname, givenName, role, location, extension, hired, salary
|
||||
82 def nn = ef[0].split(" ")
|
||||
83 if (nn.length > 1) {
|
||||
84 surname = nn[1]
|
||||
85 givenName = nn[0]
|
||||
86 } else {
|
||||
87 surname = nn[0]
|
||||
88 givenName = ""
|
||||
89 }
|
||||
90 role = ef[1]
|
||||
91 location = ef[2]
|
||||
92 try {
|
||||
93 extension = Integer.parseInt(ef[3]);
|
||||
94 } catch (NumberFormatException nfe) {
|
||||
95 extension = 0;
|
||||
96 }
|
||||
97 try {
|
||||
98 hired = LocalDate.parse(ef[4],
|
||||
99 DateTimeFormatter.ofPattern("yyyy/MM/dd"));
|
||||
100 } catch (DateTimeParseException dtpe) {
|
||||
101 hired = LocalDate.EPOCH;
|
||||
102 }
|
||||
103 try {
|
||||
104 salary = NumberFormat.getCurrencyInstance(Locale.US).
|
||||
105 parse(ef[5]).doubleValue();
|
||||
106 } catch (ParseException pe) {
|
||||
107 salary = 0d;
|
||||
108 }
|
||||
109 [surname: surname, givenName: givenName, role: role,
|
||||
110 location: location, extension: extension, hired: hired, salary: salary]
|
||||
111 }
|
||||
|
||||
112 // calculate the average salary across the entire company
|
||||
|
||||
113 def companyAvgSal = employeeList.average { e -> e.salary }
|
||||
114 println "company avg salary = " + companyAvgSal
|
||||
|
||||
115 // calculate the average salary for each location,
|
||||
116 // compare to the company average
|
||||
|
||||
117 def locationAvgSal = employeeList.groupBy { e ->
|
||||
118 e.location
|
||||
119 }.collectEntries { l, el ->
|
||||
120 [l, el.average { e -> e.salary }]
|
||||
121 }
|
||||
122 locationAvgSal.each { l, a ->
|
||||
123 println l + " avg salary = " + a +
|
||||
124 "; diff from avg company salary = " + (a - companyAvgSal)
|
||||
125 }
|
||||
|
||||
126 // show the employees in Edinburgh approach #1
|
||||
|
||||
127 print "employee(s) in Edinburgh (approach #1):"
|
||||
128 def employeesInEdinburgh = employeeList.findAll { e ->
|
||||
129 e.location == "Edinburgh"
|
||||
130 }
|
||||
131 employeesInEdinburgh.each { e ->
|
||||
132 print " " + e.surname + "," + e.givenName
|
||||
133 }
|
||||
134 println()
|
||||
|
||||
135 // group employees by location
|
||||
|
||||
136 def employeesByLocation = employeeList.groupBy { e ->
|
||||
137 e.location
|
||||
138 }
|
||||
|
||||
139 // show the employees in Edinburgh approach #2
|
||||
|
||||
140 print "employee(s) in Edinburgh (approach #1):"
|
||||
141 employeesByLocation["Edinburgh"].each { e ->
|
||||
142 print " " + e.surname + "," + e.givenName
|
||||
143 }
|
||||
144 println()
|
||||
```
|
||||
|
||||
Because I am just writing a script here, I don't need to put the program body inside a method inside a class; Groovy handles that for us.
|
||||
|
||||
In lines 1-6, I still need to import the classes needed for the data parsing. Groovy imports quite a bit of useful stuff by default, including `java.lang.*` and `java.util.*`.
|
||||
|
||||
In lines 7-90, I use Groovy's syntactic support for lists as comma-separated values bracketed by `[` and `]`. In this case, there is a list of lists; each sublist is the employee data. Notice that you need the `\` in front of the `$` in the salary field. This is because a `$` occurring inside a string surrounded by double quotes indicates the presence of a field whose value is to be interpolated into the string. An alternative would be to use single quotes.
|
||||
|
||||
But I don't want to work with a list of lists; I would rather have a list of maps analogous to the list of Employee class instances in the Java version. I use the Groovy Collection`.collect()` method in lines 90-111 to take apart each sublist of employee data and convert it into a map. The collect method takes a Groovy Closure argument, and the syntax for creating a closure surrounds the code with `{` and `}` and lists the parameters as `a, b, c ->` in a manner similar to Java's lambdas. Most of the code looks quite similar to the constructor method in the Java Employee class, except that there are items in the sublist rather than arguments to the constructor. However, the last two lines—
|
||||
|
||||
```
|
||||
[surname: surname, givenName: givenName, role: role,
|
||||
|
||||
location: location, extension: extension, hired: hired, salary: salary]
|
||||
```
|
||||
|
||||
—create a map with keys `surname`, `givenName`, `role`, `location`, `extension`, `hired`, and `salary`. And, since this is the last line of the closure, the value returned to the caller is this map. No need for a return statement. No need to quote these key values; Groovy assumes they are strings. In fact, if they were variables, you would need to put them in parentheses to indicate the need to evaluate them. The value assigned to each key appears on its right side. Note that this is a map whose values are of different types: The first four are `String`, then `int`, `LocalDate`, and `double`. It would have been possible to define the sublists with elements of those different types, but I chose to take this approach because the data would often be read in as string values from a text file.
|
||||
|
||||
The interesting bits appear in lines 112-144. I've kept the same kind of processing steps as in the Java version.
|
||||
|
||||
In lines 112-114, I use the Groovy Collection `average()` method, which like `collect()` takes a Closure argument, here iterating over the list of employee maps and picking out the `salary` value. Note that using these methods on the Collection class means you don't have to learn how to transform lists, maps, or some other element to streams and then learn the stream methods to handle your calculations, as in Java. For those who like Java Streams, they are available in newer Groovy versions.
|
||||
|
||||
In lines 115-125, I calculate the average salary by location. First, in lines 117-119, I transform `employeeList`, which is a list of maps, into a map, using the Collection`groupBy()` method, whose keys are the location values and whose values are linked sublists of the employee maps pertaining to that location. Then I process those map entries with the `collectEntries()` method, using the `average()` method to compute the average salary for each location.
|
||||
|
||||
Note that `collectEntries()` passes each key (location) and value (employee sublist at that location) into the closure (the `l, el ->` string) and expects a two-element list of key (location) and value (average salary at that location) to be returned, converting those into map entries. Once I have the map of average salaries by location, `locationAvgSal`, I can print it out using the Collection `each()` method, which also takes a closure. When `each()` is applied to a map, it passes in the key (location) and value (average salary) in the same way as `collectEntries()`.
|
||||
|
||||
In lines 126-134, I filter the `employeeList` to get a sublist of `employeesInEdinburgh`, using the `findAll()` method, which is analogous to the Java Streams `filter()` method. And again, I use the `each()` method to print out the sublist of employees in Edinburgh.
|
||||
|
||||
In lines 135-144, I take the alternative approach of grouping the `employeeList` into a map of employee sublists at each location, `employeesByLocation`. Then in lines 139-144, I select the employee sublist at Edinburgh, using the expression `employeesByLocation[“Edinburgh”]` and the `each()` method to print out the sublist of employee names at that location.
|
||||
|
||||
### Why I often prefer Groovy
|
||||
|
||||
Maybe it's just my familiarity with Groovy, built up over the last 12 years or so, but I feel more comfortable with the Groovy approach to enhancing Collection with all these methods that take a closure as an argument, rather than the Java approach of converting the list, map, or whatever is at hand to a stream and then using streams, lambdas, and data classes to handle the processing steps. I seem to spend a lot more time with the Java equivalents before I get something working.
|
||||
|
||||
I'm also a huge fan of strong static typing and parameterized types, such as `Map,employee>` `,employee>` as found in Java. However, on a day-to-day basis, I find that the more relaxed approach of lists and maps accommodating different types does a better job of supporting me in the real world of data without requiring a lot of extra code. Dynamic typing can definitely come back to bite the programmer. Still, even knowing that I can turn static type checking on in Groovy, I bet I haven't done so more than a handful of times. Maybe my appreciation for Groovy comes from my work, which usually involves bashing a bunch of data into shape and then analyzing it; I'm certainly not your average developer. So is Groovy really a more Pythonic Java? Food for thought.
|
||||
|
||||
I would love to see in both Java and Groovy a few more facilities like `average()` and `averagingDouble()`. Two-argument versions to produce weighted averages and statistical methods beyond averaging—like median, standard deviation, and so forth—would also be helpful. [Tabnine][8] offers interesting suggestions on implementing some of these.
|
||||
|
||||
### Groovy resources
|
||||
|
||||
The [Apache Groovy site][9] has a lot of great documentation. Other good sources include the reference page for [Groovy enhancements to the Java Collection class][10], the more tutorial-like introduction to [working with collections][11], and [Mr. Haki][12]. The [Baeldung site][13] provides a lot of helpful how-tos in Java and Groovy. And a really great reason to learn Groovy is to learn [Grails][14], a wonderfully productive full-stack web framework built on top of excellent components like Hibernate, Spring Boot, and Micronaut.
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://opensource.com/article/22/6/maps-groovy-vs-java
|
||||
|
||||
作者:[Chris Hermansen][a]
|
||||
选题:[lkxed][b]
|
||||
译者:[译者ID](https://github.com/译者ID)
|
||||
校对:[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译,[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
||||
[a]: https://opensource.com/users/clhermansen
|
||||
[b]: https://github.com/lkxed
|
||||
[1]: https://opensource.com/sites/default/files/lead-images/collab-team-pair-programming-code-keyboard2.png
|
||||
[2]: https://groovy-lang.org/
|
||||
[3]: https://opensource.com/article/22/3/maps-groovy-vs-java
|
||||
[4]: https://datatables.net/
|
||||
[5]: https://groovy.apache.org/download.html
|
||||
[6]: https://opensource.com/article/22/3/manage-java-versions-sdkman
|
||||
[7]: https://projectlombok.org/features/Data
|
||||
[8]: https://www.tabnine.com/code/java/methods/java.util.stream.Collectors/averagingDouble
|
||||
[9]: https://groovy-lang.org/
|
||||
[10]: https://docs.groovy-lang.org/latest/html/groovy-jdk/java/util/Collection.html
|
||||
[11]: https://groovy-lang.org/groovy-dev-kit.html#_working_with_collections
|
||||
[12]: https://blog.mrhaki.com/
|
||||
[13]: https://www.baeldung.com/
|
||||
[14]: https://grails.org/
|
@ -0,0 +1,113 @@
|
||||
[#]: subject: "Manage Flatpak Permission Using Flatseal"
|
||||
[#]: via: "https://www.debugpoint.com/2022/06/manage-flatpak-permission-flatseal/"
|
||||
[#]: author: "Arindam https://www.debugpoint.com/author/admin1/"
|
||||
[#]: collector: "lkxed"
|
||||
[#]: translator: " "
|
||||
[#]: reviewer: " "
|
||||
[#]: publisher: " "
|
||||
[#]: url: " "
|
||||
|
||||
Manage Flatpak Permission Using Flatseal
|
||||
======
|
||||
Learn how to manage Flatpak permission using the Flatseal app, which gives you a friendly GUI and additional features.
|
||||
|
||||
Installing applications can be challenging in Linux from a new user standpoint. The primary reason is there are so many [Linux distributions][1]. And you need different installation methods or instructions for various Linux distributions. It can be overwhelming for some users. In addition, it’s also difficult for developers to create separate packages and builds for different distributions.
|
||||
|
||||
### Flatpak solved this problem. How?
|
||||
|
||||
It uses container tech so that the same application executable runs similarly on all Linux platforms. For example, one single executable can run in Ubuntu, Fedora, OpenSUSE, Arch Linux and many others.
|
||||
|
||||
Moreover, the developers also spend fewer efforts on packaging the same app for different platforms. And they can concentrate on the app features rather than the distributions or deployments.
|
||||
|
||||
In addition, Flatpak apps also get updates instantly, and you get the newest version as soon as it’s available.
|
||||
|
||||
All these benefits also open up an important question. What is the permission a Flatpak app needs? How do you manage them easily? For example, one app may require only network access, not disk space. Or another may have access to take screenshots, but it might not be required at all.
|
||||
|
||||
So, it is essential to review the permission of a Flatpak app. This is similar to your Android or iOS app permission.
|
||||
|
||||
Finally, even if you are a new user, it’s not that difficult to manage and review the permissions, thanks to the graphical app – Flatseal.
|
||||
|
||||
### What is Flatseal?
|
||||
|
||||
Flatseal is a Flatpak application which gives you a friendly user interface to view and change permissions of all the Flatpak apps in your system.
|
||||
|
||||
It is an excellent little app with an easy-to-use toggle button for each of the permission sections per application. Here’s how it looks (Figure 1).
|
||||
|
||||
![Figure 1 – Flatseal App][2]
|
||||
|
||||
### How do you use Flatseal to manage Flatpak Permission?
|
||||
|
||||
When opening the Flatseal app, it should list all the Flatpak apps at the left navigation bar. And once you select one application, it shows the available permission settings in the main window at the right.
|
||||
|
||||
Now, for each Flatpak permission control, the current value is shown in the toggle switch. If the permission is in use, it should be set. Otherwise, it should be greyed out.
|
||||
|
||||
First, to set permission, you must navigate to your system’s application. Then, you can enable or disable any respective control from the permission list.
|
||||
|
||||
Second, if you want to set a global control that applies to all the Flatpak in your system, you can choose “All Applications” at the left-top and apply the global setting (Figure 2).
|
||||
|
||||
![Figure 2: Manage Flatpak Permission using Flatseal][3]
|
||||
|
||||
It’s super easy. Isn’t it?
|
||||
|
||||
### Example of Managing Flatpak Permission using Flatseal
|
||||
|
||||
Let’s take an example.
|
||||
|
||||
In my system, I have the above Flatpak installed (Figure 2). Let’s pick the Telegram Desktop app. Currently, the Telegram desktop does not have permission to access any home directory or user files (Figure 3).
|
||||
|
||||
![Figure 3: Telegram Desktop Flatpak App does not have permission to the home folders][4]
|
||||
|
||||
Now, if I want to permit all user files and any specific folder (e.g. /home/Downloads), you can give it by turning the enable switch on. See the Figure 4 below.
|
||||
|
||||
![Figure 4: Permission changed of Telegram Desktop to give access to folders][5]
|
||||
|
||||
Similarly, you can enable or disable the permission you want. Under the hood, Flatseal performs the internal Flatpak commands to achieve this.
|
||||
|
||||
For example, the above scenario may translate to the following command.
|
||||
|
||||
```
|
||||
flatpak override org.telegram.desktop --filesystem=/home/Downloads
|
||||
```
|
||||
|
||||
And to remove:
|
||||
|
||||
```
|
||||
flatpak override org.telegram.desktop --nofilesystem=/home/Downloads
|
||||
```
|
||||
|
||||
There is also another cool feature of Flatseal which shows a small alert icon beside the user-specific permission changes (See Figure 4).
|
||||
|
||||
### Can I install Flatseal in all Linux distributions?
|
||||
|
||||
Yes, you can install [Flatseal][6] in all Linux Distributions as Flatpak. You can set up your system using [this guide][7] and run the following command to install. Or, [click here][8] to launch the system-specific installer directly.
|
||||
|
||||
```
|
||||
flatpak install flathub com.github.tchx84.Flatseal
|
||||
```
|
||||
|
||||
### Closing Notes
|
||||
|
||||
I hope the above guide to managing Flatpak permission is easy enough for you to understand and start with Flatpak. It’s super easy to control and far easier to use. Also, you may want to visit our more Flatpak [guide here][9].
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://www.debugpoint.com/2022/06/manage-flatpak-permission-flatseal/
|
||||
|
||||
作者:[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/category/distributions
|
||||
[2]: https://www.debugpoint.com/wp-content/uploads/2022/06/Flatseal-App.jpg
|
||||
[3]: https://www.debugpoint.com/wp-content/uploads/2022/06/Manage-Flatpak-Permission-using-Flatseal.jpg
|
||||
[4]: https://www.debugpoint.com/wp-content/uploads/2022/06/Telegram-Desktop-Flatpak-App-does-not-have-permission-to-the-home-folders.jpg
|
||||
[5]: https://www.debugpoint.com/wp-content/uploads/2022/06/Permission-changed-of-Telegram-Desktop-to-give-access-to-folders.jpg
|
||||
[6]: https://flathub.org/apps/details/com.github.tchx84.Flatseal
|
||||
[7]: https://flatpak.org/setup/
|
||||
[8]: https://dl.flathub.org/repo/appstream/com.github.tchx84.Flatseal.flatpakref
|
||||
[9]: https://www.debugpoint.com/tag/flatpak/
|
@ -0,0 +1,181 @@
|
||||
[#]: subject: "Run Windows Apps And Games Using WineZGUI On Linux"
|
||||
[#]: via: "https://ostechnix.com/winezgui-run-windows-apps-and-games-on-linux/"
|
||||
[#]: author: "sk https://ostechnix.com/author/sk/"
|
||||
[#]: collector: "lkxed"
|
||||
[#]: translator: " "
|
||||
[#]: reviewer: " "
|
||||
[#]: publisher: " "
|
||||
[#]: url: " "
|
||||
|
||||
Run Windows Apps And Games Using WineZGUI On Linux
|
||||
======
|
||||
WineZGUI - A Wine GUI Frontend Using Zenity
|
||||
|
||||
A while ago we wrote about **[Bottles][1]**, an opensource graphical application easily to run Windows software and Games on Linux operating systems. Today, we will discuss about a similar interesting project. Say hello to **WineZGUI**, a Wine GUI frontend to **[run windows apps and games with wine on Linux][2]**.
|
||||
|
||||
#### Contents
|
||||
|
||||
1. What Is WineZGUI?
|
||||
2. Bottles Vs WineZGUI
|
||||
3. How To Install WineZGUI In Linux
|
||||
4. Run Windows Apps And Games With WineZGUI In Linux
|
||||
5. Conclusion
|
||||
|
||||
### What Is WineZGUI?
|
||||
|
||||
WineZGUI is a collection of Bash scripts that allows you to easily manage wine prefixes and provides easier wine gaming experience on Linux using **Zenity**.
|
||||
|
||||
Using WineZGUI, we can directly launch the Windows exe files or games from File manager without installing them.
|
||||
|
||||
WineZGUI creates shortcut for each application or game for easier access and also creates separate prefixes for each exe binary file.
|
||||
|
||||
When you launch a Windows exe file with WineZGUI, it will prompt you whether to use the default wine prefix or create a new one. The default prefix is `~/.local/share/winezgui/default`.
|
||||
|
||||
If you choose to create a new prefix for the windows binary or exe, WineZGUI will try to extract the product name and icon from the exe file and it creates a desktop shortcut.
|
||||
|
||||
When you launch the same exe or binary file later, it will recommend you to run it with the associated prefix earlier.
|
||||
|
||||
To put this layman terms, WineZGUI is simply a Wine and winetricks simple GUI for official vanilla wine. Wine prefix setup is automatic when we launch an exe to play a game.
|
||||
|
||||
You simply open an exe and it creates a prefix and a desktop shortcut with name and icon extracted from that exe.
|
||||
|
||||
It uses **exiftool** and **icotool** utilities to extract the name and icon respectively. Either you can open an exe to launch that game from existing prefix, or use desktop shortcut.
|
||||
|
||||
WineZGUI is a shell script that is freely hosted in GitHub. You can grab the source code, improve it, fix bugs and add features.
|
||||
|
||||
### Bottles Vs WineZGUI
|
||||
|
||||
You might wonder how does WineZGUI compare with Bottles. There is a subtle difference between these applications though.
|
||||
|
||||
**Bottles is prefix oriented** and **runner oriented**. Meaning - Bottles first creates a prefix then use different exe files with it. Bottles does not remember exe's prefix. Bottles uses different runners.
|
||||
|
||||
**WineZGUI is exe oriented**. It uses exe to create one prefix for that exe only. Next time we open an exe, it will ask whether to launch with existing exe prefix.
|
||||
|
||||
WineZGUI does not offer advanced features like **bottles** or **[lutris][3]** do, like runners, online installers, etc.
|
||||
|
||||
### How To Install WineZGUI In Linux
|
||||
|
||||
Make sure you have installed the necessary prerequisites for WineZGUI.
|
||||
|
||||
**Debian/Ubuntu:**
|
||||
|
||||
```
|
||||
$ sudo dpkg --add-architecture i386
|
||||
$ sudo apt install zenity wine winetricks libimage-exiftool-perl icoutils gnome-terminal
|
||||
```
|
||||
|
||||
**Fedora:**
|
||||
|
||||
```
|
||||
$ sudo dnf install zenity wine winetricks perl-Image-ExifTool icoutils gnome-terminal
|
||||
```
|
||||
|
||||
The officially recommended way to install WineZGUI is by using **[Flatpak][4]**.
|
||||
|
||||
After installing Flatpak, run the following commands one by one to install WineZGUI in Linux.
|
||||
|
||||
```
|
||||
$ flatpak --user remote-add --if-not-exists flathub https://flathub.org/repo/flathub.flatpakrepo
|
||||
```
|
||||
|
||||
```
|
||||
$ flatpak --user -y install flathub org.winehq.Wine/x86_64/stable-21.08
|
||||
```
|
||||
|
||||
```
|
||||
$ wget https://github.com/fastrizwaan/WineZGUI-Releases/releases/download/WineZGUI-0.4_20220608/io.github.WineZGUI_0_4_20220608.flatpak
|
||||
```
|
||||
|
||||
```
|
||||
$ flatpak --user -y install io.github.WineZGUI_0_4_20220608.flatpak
|
||||
```
|
||||
|
||||
### Run Windows Apps And Games With WineZGUI In Linux
|
||||
|
||||
Launch WineZGUI from Dash or Menu.
|
||||
|
||||
![Launch WineZGUI][5]
|
||||
|
||||
This is how the default interface of WineZGUI looks like.
|
||||
|
||||
![WineZGUI Interface][6]
|
||||
|
||||
As you can see in the above screenshot, WineZGUI interface is very simple and easy to understand. From the main window, you can,
|
||||
|
||||
* Open an EXE file,
|
||||
* Open Winetricks GUI and CLI,
|
||||
* Launch Wine configuration,
|
||||
* Launch explorer,
|
||||
* Open BASH shell,
|
||||
* Kill all apps/games including WineZGUI interface,
|
||||
* Delete wine prefix,
|
||||
* View installed WineZGUI version.
|
||||
|
||||
For the purpose of the demonstration, I am going to open an .exe file.
|
||||
|
||||
In the next window, choose the EXE file to run. In my case, it is WinRAR.
|
||||
|
||||
![Choose The EXE File To Run][7]
|
||||
|
||||
Next, whether you want to run the EXE file with default prefix or create a new prefix. I choose default prefix.
|
||||
|
||||
![Run WinRAR With Default Prefix][8]
|
||||
|
||||
A few seconds later, the WinRAR setup wizard will appear. Click Install to continue.
|
||||
|
||||
![Install WinRAR In Linux][9]
|
||||
|
||||
Click OK to complete the WinRAR installation.
|
||||
|
||||
![Complete WinRAR Installation][10]
|
||||
|
||||
Click "Run WinRAR" to launch it.
|
||||
|
||||
![Run WinRAR][11]
|
||||
|
||||
Here is WinRAR running in my Fedora 36 desktop!
|
||||
|
||||
![WinRAR Is Running In Fedora Using Wine][12]
|
||||
|
||||
### Conclusion
|
||||
|
||||
WineZGUI is a newcomer to the club. If you're looking for an easier way to run Windows apps and games using Wine on a Linux desktop, WineZGUI might be a good choice.
|
||||
|
||||
With the help of WineZGUI, the users have an option to create a wine prefix right at same folder as the `.exe` and creating a relatively-linked `.desktop` entry to automatically do so.
|
||||
|
||||
The reason being that it's easier to back up and delete a game along with the wine prefix, and having it generate a `.desktop` would make it resilient to being moved and transferred.
|
||||
|
||||
A cool use-case would be to setup using the app, then share the wine prefix to your friend and others who just want a working wine prefix with all the dependencies, saves, etc.
|
||||
|
||||
Give it a try and let us know what do you think about this project in the comment section below.
|
||||
|
||||
**Resource:**
|
||||
|
||||
* [WineZGUI GitHub Repository][13]
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://ostechnix.com/winezgui-run-windows-apps-and-games-on-linux/
|
||||
|
||||
作者:[sk][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://ostechnix.com/author/sk/
|
||||
[b]: https://github.com/lkxed
|
||||
[1]: https://ostechnix.com/run-windows-software-on-linux-with-bottles/
|
||||
[2]: https://ostechnix.com/run-windows-games-softwares-ubuntu-16-04/
|
||||
[3]: https://ostechnix.com/manage-games-using-lutris-linux/
|
||||
[4]: https://ostechnix.com/how-to-install-and-use-flatpak-in-linux/
|
||||
[5]: https://ostechnix.com/wp-content/uploads/2022/06/Launch-WineZGUI.png
|
||||
[6]: https://ostechnix.com/wp-content/uploads/2022/06/WineZGUI-Interface.png
|
||||
[7]: https://ostechnix.com/wp-content/uploads/2022/06/Choose-The-EXE-File-To-Run.png
|
||||
[8]: https://ostechnix.com/wp-content/uploads/2022/06/Run-WinRAR-With-Default-Prefix.png
|
||||
[9]: https://ostechnix.com/wp-content/uploads/2022/06/Install-WinRAR-In-Linux.png
|
||||
[10]: https://ostechnix.com/wp-content/uploads/2022/06/Complete-WinRAR-Installation.png
|
||||
[11]: https://ostechnix.com/wp-content/uploads/2022/06/Run-WinRAR.png
|
||||
[12]: https://ostechnix.com/wp-content/uploads/2022/06/WinRAR-Is-Running-In-Fedora-Using-Wine.png
|
||||
[13]: https://github.com/fastrizwaan/WineZGUI
|
@ -0,0 +1,144 @@
|
||||
[#]: subject: "Don’t Be Afraid of Linux Terminal. Embrace it."
|
||||
[#]: via: "https://itsfoss.com/love-thy-terminal/"
|
||||
[#]: author: "Ankush Das https://itsfoss.com/author/ankush/"
|
||||
[#]: collector: "lkxed"
|
||||
[#]: translator: " "
|
||||
[#]: reviewer: " "
|
||||
[#]: publisher: " "
|
||||
[#]: url: " "
|
||||
|
||||
Don’t Be Afraid of Linux Terminal. Embrace it.
|
||||
======
|
||||
Most of our focus goes into avoiding the Linux terminal, at least, for new users comfortable with Graphical User Interfaces (GUIs).
|
||||
|
||||
While it is good to make things easy and convenient, there are a few reasons why you should not be afraid of dipping your toes into the Linux terminal.
|
||||
|
||||
Here, I shall highlight some of them to encourage you to try a few things in the terminal that should help you eventually.
|
||||
|
||||
### 1. Quick Access to Information on Commands
|
||||
|
||||
![quick info terminal][1]
|
||||
|
||||
At times, you may need to use a command in the terminal to perform something. Sure, you can just copy-paste without knowing what it actually does.
|
||||
|
||||
But, what if you are interested to know a bit more about the command?
|
||||
|
||||
Well, you just need to type in:
|
||||
|
||||
```
|
||||
man <command you intend to learn>
|
||||
```
|
||||
|
||||
For instance: man apt
|
||||
|
||||
It will give you all the essential details right on the same screen, without needing an internet connection or scouring the web to find out what it does. You save time, you get to know stuff.
|
||||
|
||||
And, that makes things convenient, giving you more confidence in using the terminal.
|
||||
|
||||
These are often referred to as “man pages”. You can read one of our resources to[learn about man pages on Linux][2].
|
||||
|
||||
Thanks to the terminal.
|
||||
|
||||
### 2. Troubleshooting Problems
|
||||
|
||||
![troubleshoting illustration][3]
|
||||
|
||||
When you search for a fix on the internet, most of the solutions provide you with commands to get it fixed.
|
||||
|
||||
Hence, one of the best use-cases of the terminal is to resolve several system issues quite easily. You will have to be careful here, because
|
||||
|
||||
While there are things that you can tweak around with GUI programs, the majority of the easy fixes go through the terminal.
|
||||
|
||||
Considering we have several [troubleshooting guides][4] on our portal, some examples include:
|
||||
|
||||
* [Checking network adapter manufacturer][5]
|
||||
* [Fixing long shutdown time][6]
|
||||
* [Fix no Wi-Fi with broadcom adapters][7]
|
||||
|
||||
### 3. Easily Work With a Remote Server
|
||||
|
||||
![remote server illustration][8]
|
||||
|
||||
You will end up accessing the command line (or the terminal) to access a remote server and perform various operations, including file transfers.
|
||||
|
||||
Compared to a GUI method for a remote server, you minimize bandwidth issues and ensure that you get to perform anything you need faster using the Linux terminal.
|
||||
|
||||
There are also options to open a GUI program on the remote server via the terminal. Even if it is slow, the terminal gives you plenty of abilities to interact comfortably with a remote server.
|
||||
|
||||
### 4. Resource Efficient
|
||||
|
||||
It does not matter whether you use one of the [best Linux distributions][9], a Linux terminal is always resource-efficient and consumes the least amount of memory.
|
||||
|
||||
If you are low on resources or may have a graphics driver conflict with a GUI program, you can always rely on the Linux terminal.
|
||||
|
||||
This should help you through critical tasks without taking much system resources.
|
||||
|
||||
### 5. Fast
|
||||
|
||||
![fast illustration][10]
|
||||
|
||||
Not just limited to the memory usage, but you can get things done faster with a terminal over a GUI, you know?
|
||||
|
||||
Some tasks you can try include installing an application, launching a program, performing complex file operations, and more.
|
||||
|
||||
### 6. Stable and Reliable Command-line Programs
|
||||
|
||||
Compared to GUI programs, terminal programs are stable and more reliable. Why?
|
||||
|
||||
Fewer factors influence the program with crashes/bugs when it comes to a terminal.
|
||||
|
||||
While the terminal tools could be unintuitive, they are often built for servers in mind. So, the tools do not receive frequent experience breaking updates and do not quickly fail to work.
|
||||
|
||||
### 7. More Tools for CLI
|
||||
|
||||
We do not have a GUI program for everything on Linux. However, there are several [CLI tools][11] to perform a wide range of operations, some fun and critical tasks as well.
|
||||
|
||||
You need to get something done; chances are, you will find a command-line tool for it.
|
||||
|
||||
### 8. Various Terminal Emulators to Try
|
||||
|
||||
![variety illustration][12]
|
||||
|
||||
While you should not have any trouble with the default terminal emulator installed on your Linux distribution, you have plenty of other options.
|
||||
|
||||
If you prefer a different look, more advanced features, or tailored for a specific use, you can look at some of the [best terminal emulators][13] available.
|
||||
|
||||
If you thought using the terminal was boring, you must try some of them.
|
||||
|
||||
### Wrapping Up
|
||||
|
||||
Personally, I feared the terminal when I was a new Linux user. But, as I got comfortable with it for small tasks, I got to realize the perks mentioned above.
|
||||
|
||||
You do not need to use the terminal over GUI for everything. Nevertheless, it is good to prefer the terminal for a few things because you might save your time, and get things done faster, and in a hassle-free manner.
|
||||
|
||||
Abhishek has written an [excellent guide on various small things that make you get more comfortable with the Linux terminal][14].
|
||||
|
||||
*What do you think are the benefits of a terminal over a GUI? What are your reasons to prefer the terminal? Let me know your thoughts in the comments section below.*
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://itsfoss.com/love-thy-terminal/
|
||||
|
||||
作者:[Ankush Das][a]
|
||||
选题:[lkxed][b]
|
||||
译者:[译者ID](https://github.com/译者ID)
|
||||
校对:[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译,[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
||||
[a]: https://itsfoss.com/author/ankush/
|
||||
[b]: https://github.com/lkxed
|
||||
[1]: https://itsfoss.com/wp-content/uploads/2022/06/quick-info-terminal.png
|
||||
[2]: https://itsfoss.com/linux-man-page-guide/
|
||||
[3]: https://itsfoss.com/wp-content/uploads/2022/06/troubleshoting-illustration.jpg
|
||||
[4]: https://itsfoss.com/tag/troubleshoot/
|
||||
[5]: https://itsfoss.com/find-network-adapter-ubuntu-linux/
|
||||
[6]: https://itsfoss.com/long-shutdown-linux/
|
||||
[7]: https://itsfoss.com/fix-no-wireless-network-ubuntu/
|
||||
[8]: https://itsfoss.com/wp-content/uploads/2022/06/remote-server-illustration.jpg
|
||||
[9]: https://itsfoss.com/best-linux-distributions/
|
||||
[10]: https://itsfoss.com/wp-content/uploads/2022/06/fast-illustration.jpg
|
||||
[11]: https://itsfoss.com/tag/cli-tools/
|
||||
[12]: https://itsfoss.com/wp-content/uploads/2022/06/variety-illustration.jpg
|
||||
[13]: https://itsfoss.com/linux-terminal-emulators/
|
||||
[14]: https://itsfoss.com/basic-terminal-tips-ubuntu/
|
@ -0,0 +1,151 @@
|
||||
[#]: subject: "LibreOffice 7.4: Top New Features and Release Details"
|
||||
[#]: via: "https://www.debugpoint.com/2022/06/libreoffice-7-4/"
|
||||
[#]: author: "Arindam https://www.debugpoint.com/author/admin1/"
|
||||
[#]: collector: "lkxed"
|
||||
[#]: translator: " "
|
||||
[#]: reviewer: " "
|
||||
[#]: publisher: " "
|
||||
[#]: url: " "
|
||||
|
||||
LibreOffice 7.4: Top New Features and Release Details
|
||||
======
|
||||
This post contains the top new features of LibreOffice 7.4 (upcoming) across Writer, Calc, Impress and other core modules.
|
||||
|
||||
**This post contains the top new features of LibreOffice 7.4 (upcoming) across Writer, Calc, Impress and other core modules.**
|
||||
|
||||
The LibreOffice team improves the famous free and open-source office product with each iteration. Perhaps the only stable and well-managed open-source project as a replacement to Microsoft Office.
|
||||
|
||||
The LibreOffice 7.4 version (planned in August), bringing regular updates to core modules including Calc, Writer and Impress with features and enhancements. Furthermore, in this release, the compatibility with Microsoft Office improved with changes to the core filters and platform updates.
|
||||
|
||||
Before we round up the new features, here’s a tentative schedule for LibreOffice 7.4:
|
||||
|
||||
### Schedule
|
||||
|
||||
| Milestone | Release Date |
|
||||
| :- | :- |
|
||||
| Alpha 1 | May 9, 2022 – May 15, 2022 |
|
||||
| Feature Freeze | Jun 6, 2022 – Jun 12, 2022 |
|
||||
| Beta 1 | Jun 6, 2022 – Jun 12, 2022 |
|
||||
| RC1 | Jul 4, 2022 – Jul 10, 2022 |
|
||||
| RC2 | Jul 25, 2022 – Jul 31, 2022 |
|
||||
| RC3 | Aug 8, 2022 – Aug 14, 2022 |
|
||||
| Release 7.4 | Aug 15, 2022 – Aug 21, 2022 |
|
||||
|
||||
### LibreOffice 7.4 Features
|
||||
|
||||
#### Calc
|
||||
|
||||
First and foremost, the most crucial change coming in 7.4 is the support of 16k columns in LibreOffice Calc. It was available in earlier LibreOffice 7.3 but hidden as an experimental option. Finally, it is open to support 16384 columns, i.e. up to XFD. Additional columns are going to help several high-volume data work.
|
||||
|
||||
![LibreOffice 7.4 Calc now supports 16k columns.][1]
|
||||
|
||||
Second, the Autosum button gets the following [additional functions][2] to improve productivity and save time.
|
||||
|
||||
* COUNTA
|
||||
* PRODUCT
|
||||
* STDEV
|
||||
* STDEVP
|
||||
* VAR
|
||||
* VARP
|
||||
|
||||
![Additional options in Autosum button][3]
|
||||
|
||||
Moreover, the height of the formula bar is now part of the *.ods files. Hence, you can see the height retained after saving the file and opening it. Earlier, it was being reset to the default height. It is one of the small changes but has a more significant impact on heavy Calc users.
|
||||
|
||||
![Height of Calc Formula bar][4]
|
||||
|
||||
In addition, a new menu option `Sheet > Navigate > Go to Sheet` shows an entire new dialog which is similar to the Writer’s Go to Page.
|
||||
|
||||
#### Writer
|
||||
|
||||
Firstly, the hyphenation settings get three new options. You can now specify the size of the hyphenation zone, minimum word length and ability to stop hyphenating the last word.
|
||||
|
||||
![New Hyphenation settings][5]
|
||||
|
||||
*Image credit: LibreOffice Team*
|
||||
|
||||
Secondly, the menu item Tools > Update > Update now updates the preview of all OLE objects. Also, if you are importing a DOCX file in LibreOffice 7.4, the paragraph borders bring more clarity. In addition, the import also improves the Rich text and checkbox contents inside the text box for DOCX imports. Moreover, Write 7.4 now supports clearing breaks from Word files improving layout consistency.
|
||||
|
||||
Secondly, the menu item `Tools > Update > Update all` now updates the preview of all OLE objects.
|
||||
|
||||
Also, if you are importing a DOCX file in LibreOffice 7.4, the paragraph borders bring more clarity. In addition, the import also improves the Rich text and checkbox contents inside the text box for DOCX imports.
|
||||
|
||||
Moreover, Writer 7.4 now supports clearing breaks from Word files improving layout consistency.
|
||||
|
||||
#### Impress
|
||||
|
||||
The significant change in Impress is a new Theme tab in the Slide properties for the master slide. It contains several accent colour options which control all the sildes in your presentation. It will be a really neat feature in this version.
|
||||
|
||||
![New Theme option in Slide Master Properties][6]
|
||||
|
||||
### Common Updates (across all modules)
|
||||
|
||||
Firstly, the most important change as a standard feature is LibreOffice now supports WEBP images officially. You can directly export and import WebP images across Writer, Calc, Draw etc. Now you do not need additional software to convert WEBP images, especially in Linux systems.
|
||||
|
||||
Moreover, the support for Windows compressed enhanced meta file (EMZ/WMZ) also lands in this release.
|
||||
|
||||
![New WEBP Image Support][7]
|
||||
|
||||
Secondly, the Fille > Recent Documents can remember the state of the last opened document, whether it was read-only or editable.
|
||||
|
||||
The 3D shapes lighting gets some bug fixes and corrections corresponding to the ODF specifications.
|
||||
|
||||
### Performance Updates
|
||||
|
||||
A bunch of performance boosts also makes this an important release of LibreOffice. Here’s a quick recap of the performance boosts.
|
||||
|
||||
* [The Text Layout performance gets around a 60% boost][8]
|
||||
* [Calc formula re-calculation][9]
|
||||
* Improved performance of [VLOOKUP][10], COUNTIF and SUMIF
|
||||
* [And CSV file import][11]
|
||||
|
||||
That’s not all. LibreOffice 7.4 also brings a huge set of filters (export and import) for Microsoft Office 365 file types, extended PDF export options (such as a sign) via command line, updated language support and API changes.
|
||||
|
||||
### Download LibreOffice 7.4 for Testing
|
||||
|
||||
You can download the development version of LibreOffice 7.4 using the respective links and help to test.
|
||||
|
||||
* [RPM Package for Fedora and related distributions][12]
|
||||
* [DEB packages for Ubuntu, Linux Mint and others][13]
|
||||
* [Windows 10, 11 – 64-bit][14]
|
||||
* [macOS 64 bit][15]
|
||||
* [Mac OS X – ARM and Apple SIlicon, M1][16]
|
||||
|
||||
If you need assistance, you can refer to our [guide here][17] to install the development version in Linux. Make sure to report any issues or bugs in the [official bug tracker.][18]
|
||||
|
||||
LibreOffice 7.4 is planned for release between Aug 15, 2022, and Aug 21, 2022.
|
||||
|
||||
*[Via Release Notes][19]*
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://www.debugpoint.com/2022/06/libreoffice-7-4/
|
||||
|
||||
作者:[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/06/LibreOffice-7.4-Calc-now-supports-16k-columns.jpg
|
||||
[2]: https://bugs.documentfoundation.org/show_bug.cgi?id=139602
|
||||
[3]: https://www.debugpoint.com/wp-content/uploads/2022/06/Additional-formula-in-Autosum-tool.jpg
|
||||
[4]: https://www.debugpoint.com/wp-content/uploads/2022/06/Height-of-Calc-Formula-bar.jpg
|
||||
[5]: https://www.debugpoint.com/wp-content/uploads/2022/06/New-Hyphenation-settings.jpg
|
||||
[6]: https://www.debugpoint.com/wp-content/uploads/2022/06/New-Theme-option-in-Slide-Master-Properties.jpg
|
||||
[7]: https://www.debugpoint.com/wp-content/uploads/2022/06/New-WEBP-Image-Support.jpg
|
||||
[8]: http://llunak.blogspot.com/2022/04/improving-text-layout-performance.html
|
||||
[9]: https://bugs.documentfoundation.org/show_bug.cgi?id=119083
|
||||
[10]: https://bugs.documentfoundation.org/show_bug.cgi?id=146546
|
||||
[11]: https://bugs.documentfoundation.org/show_bug.cgi?id=94677
|
||||
[12]: https://www.libreoffice.org/download/download/?type=rpm-x86_64&version=7.4.0&lang=en-US
|
||||
[13]: https://www.libreoffice.org/download/download/?type=deb-x86_64&version=7.4.0&lang=en-US
|
||||
[14]: https://www.libreoffice.org/download/download/?type=win-x86_64&version=7.4.0&lang=en-US
|
||||
[15]: https://www.libreoffice.org/download/download/?type=mac-x86_64&version=7.4.0&lang=en-US
|
||||
[16]: https://www.libreoffice.org/download/download/?type=mac-aarch64&version=7.4.0&lang=en-US
|
||||
[17]: https://www.debugpoint.com/2022/06/install-latest-libreoffice-ubuntu-linux/
|
||||
[18]: https://bugs.documentfoundation.org/
|
||||
[19]: https://wiki.documentfoundation.org/ReleaseNotes/7.4
|
@ -1,103 +0,0 @@
|
||||
[#]: subject: "Linux Kernel 5.19 系列第一个候选版本(RC1)发布,包含 ARM 通用工作"
|
||||
[#]: via: "https://www.debugpoint.com/2022/06/linux-kernel-5-19-rc1/"
|
||||
[#]: author: "Arindam https://www.debugpoint.com/author/admin1/"
|
||||
[#]: collector: "lkxed"
|
||||
[#]: translator: " Donkey-Hao "
|
||||
[#]: reviewer: " "
|
||||
[#]: publisher: " "
|
||||
[#]: url: " "
|
||||
|
||||
Linux Kernel 5.19 系列第一个候选版本(RC1)发布,包含 ARM 通用工作
|
||||
======
|
||||
Linus Torvalds 发布了 Linux Kernel 5.19 RC1 进行测试,带来了重大变化。
|
||||
|
||||
继上个月 [Linux Kernel 5.18][1] 发布之后,Linus Torvalds 宣布 Linux Kernel 5.19 系列第一个候选版本可用。同时,Linux Kernel 5.19 官方合并窗口关闭,这意味着只有很关键的特性才会被接受。
|
||||
|
||||
简要介绍一下 Linux Kernel 5.19 的项目,会发现 CPU、GPU、网络、存储和核心模块会定期更新。 此外,代码清理、淘汰过时硬件和对以后芯片组的持续支持是此版本的亮点。
|
||||
|
||||
让我们简单来看一下这些新特性。
|
||||
|
||||
### Linux Kernel 5.19(RC1) 的新特性
|
||||
|
||||
#### 处理器
|
||||
|
||||
最重要的是,Linux Kernel 5.19 开始对龙芯架构 CPU 的 [初步支持][2]。龙芯由中国龙芯中科公司设计开发。龙芯架构下的 CPU 是通用 MIPS 架构兼容微处理器。尽管现在提供了支持,但是你仍不能在龙芯 CPU 上启动 Linux 因为一些代码还在审核中。希望在 5.20 版本中能够使用。
|
||||
|
||||
|
||||
[Intel IFS 驱动 ][4] 在该版本中落地,这有助于在部署前后发现硬件问题。它能够在早期发现 CPU 关键部分的错误。
|
||||
|
||||
|
||||
电源管理和散热工作在英特尔 CPU 的最后几个内核版本中继续进行。 在 [这个版本][5] 也不例外。首先,为 Raptor 和 Alder Lake 家族添加了英特尔运行时平均功率限制(RAPL)的支持。其次,为了处理频率变化升级了 P-state 驱动,并且基于 CPU 的缩放支持被添加到被动的 devfreq 中。
|
||||
|
||||
|
||||
虽然散热和供电主导着英特尔 CPU ,但 AMD 看到了自己 CPU 系列更多的性能更新。首先,计划在今年年底完成 ZMD Zen 4 CPUs 的 Instruction-Based Sampling (IBS) 模块的很多更新。此外,此版本引入了 PerfMonV2 ,提供了更多性能监视能力。
|
||||
|
||||
此外,该版本中移除了 a.out 支持。同样,过时的 Renesas H8/300 CPU 也被移除了。
|
||||
#### 主要 ARM 更新
|
||||
|
||||
最后,主线 Linux Kernel 能够 [支持多个 ARM 平台][7]。在 Linus 的 RC1 开场白中可以看到,这是此版本中的巨大改变!从 Linux 3.7 开始跨越了十多年的工作,这是多么漫长的过程。
|
||||
|
||||
![Linux Kernel 5.19 Rc1 发布公告提到了 ARM 更改][8]
|
||||
|
||||
#### 图像和存储升级
|
||||
|
||||
存储子系统实现了跨越流行文件系统的性能提升。最主要的变化包括苹果 M1 NVMe 控制器支持和对 XFS 文件系统的更好支持。此外,提升了 Btrfs , F2FS 以及 exFAT 文件系统。
|
||||
|
||||
关于 LOC 有一个令人兴奋的指标是仅图像驱动程序, Linux Kernel 5.19 增加了大约[50 万行代码][9] 。包括 AMD RDNA, CDNA, 英特尔的 Raptor Lake, DG2/Alchemist 等图形架构更新。
|
||||
|
||||
#### 重要的网络变化
|
||||
|
||||
鉴于数据传输大幅增长,对 Big TCP 的支持有助于数据中心流量达到 400 GBit 的范围。它还可以在高性能网络环境中降低延迟。
|
||||
|
||||
继续改进了 Multi-Path TCP (MPTCP) 。此外,高通 ath11k WiFi 驱动程序在此版本中添加了网络唤醒功能。同样增加了对瑞昱的 8852ce 芯片,联发科的 T700 调制解调器以及瑞萨科技的 RZ/V2M 的支持。
|
||||
|
||||
#### 其他值得注意的功能
|
||||
|
||||
首先,内核中著名的随机函数生成器在此版本中 [继续][10] 改进。
|
||||
|
||||
其次,著名的初创公司 Framework 模块化笔记本电脑获得了此版本 Chrome OS EC 驱动支持。 Framework 笔记本现在可以利用 ChromeOS 的嵌入式控制器作为 non-Chromebook 设备。
|
||||
|
||||
此外, Wacom 绘画板以及其他相关设备也有众多更新。 [包括][11] 对联想 Thinkpad TrackPoint II, 谷歌 Whiskers Touchpad, 联想 X12 TrackPoint 等设备支持的提升。
|
||||
|
||||
### Linux Kernel 5.19 下载
|
||||
|
||||
如果你想要测试并尝试该候选版本,可以在 [这里][12] 下载。或者参考下面的链接。
|
||||
|
||||
| - | - | - | - | - | - | - | - | - |
|
||||
| :- | :- | :- | :- | :- | :- | :- | :- | :- |
|
||||
| mainline: | 5.19-rc1 | 2022-06-06 | [tarball][13] | | [patch][14] | | [view diff][15] | [browse][16] |
|
||||
|
||||
预计在2022年7月左右最终版本发布前,将会有多个版本更迭。
|
||||
|
||||
*[Kernel 邮件列表.][17]*
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://www.debugpoint.com/2022/06/linux-kernel-5-19-rc1/
|
||||
|
||||
作者:[Arindam][a]
|
||||
选题:[lkxed][b]
|
||||
译者:[Donkey-Hao](https://github.com/Donkey-Hao)
|
||||
校对:[校对者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/2022/05/linux-kernel-5-18/
|
||||
[2]: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=c6f2f3e2c80e975804360665d973211e4d9390cb
|
||||
[3]: http://www.loongson.cn/
|
||||
[4]: https://lore.kernel.org/lkml/13e61c61-0d4b-5f48-6373-f056bf8b603f@redhat.com/
|
||||
[5]: https://lore.kernel.org/linux-acpi/CAJZ5v0hKBt3js65w18iKxzWoN5QuEc84_2xcM6paSv-ZHwe3Rw@mail.gmail.com/
|
||||
[6]: https://lore.kernel.org/lkml/You6yGPUttvBcg8s@gmail.com/
|
||||
[7]: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ecf0aa5317b0ad6bb015128a5b763c954fd58708
|
||||
[8]: https://www.debugpoint.com/wp-content/uploads/2022/06/Linux-Kernel-5.19-Rc1-release-announcement-mentions-ARM-changes.jpg
|
||||
[9]: https://lore.kernel.org/lkml/CAPM=9tw62EZfAm0PbiOPmMrpfR98QMFTWGEQcA34G4ap4xxNkA@mail.gmail.com/
|
||||
[10]: https://lore.kernel.org/lkml/20220522214457.37108-1-Jason@zx2c4.com/T/#u
|
||||
[11]: https://lore.kernel.org/lkml/nycvar.YFH.7.76.2205241107530.28985@cbobk.fhfr.pm/
|
||||
[12]: https://www.kernel.org/
|
||||
[13]: https://git.kernel.org/torvalds/t/linux-5.19-rc1.tar.gz
|
||||
[14]: https://git.kernel.org/torvalds/p/v5.19-rc1/v5.18
|
||||
[15]: https://git.kernel.org/torvalds/ds/v5.19-rc1/v5.18
|
||||
[16]: https://git.kernel.org/torvalds/h/v5.19-rc1
|
||||
[17]: https://lore.kernel.org/lkml/CAHk-=wgZt-YDSKfdyES2p6A_KJoG8DwQ0mb9CeS8jZYp+0Y2Rw@mail.gmail.com/T/#u
|
@ -0,0 +1,47 @@
|
||||
[#]: subject: "OpenInfra Foundation Launches ‘directed funding’ To Support Open Source Projects"
|
||||
[#]: via: "https://www.opensourceforu.com/2022/06/openinfra-foundation-launches-directed-funding-to-support-open-source-projects/"
|
||||
[#]: author: "Laveesh Kocher https://www.opensourceforu.com/author/laveesh-kocher/"
|
||||
[#]: collector: "lkxed"
|
||||
[#]: translator: "lkxed"
|
||||
[#]: reviewer: " "
|
||||
[#]: publisher: " "
|
||||
[#]: url: " "
|
||||
|
||||
OpenInfra 基金会启动“定向资助”以支持开源项目
|
||||
======
|
||||
![OpenInfra][1]
|
||||
|
||||
OpenInfra 基金会的前身为 OpenStack 基金会,几年前它将范围扩展到其旗舰项目之外,于是改了名字。今天(2022 年 6 月 7 日),它宣布了一种有趣的新方式,以供公司在基金会内资助开源项目。一般来说,开源基金会的企业成员通过支付会员费来支持该组织,然后基金会按照他们认为合适的方式分发这些费用。OpenInfra 基金会现在推出了一种新的“定向资助”模式,允许成员将他们的资金直接用于项目。
|
||||
|
||||
此前,基金会并不允许这样做,因为正如 Bryce 指出的那样,它可能会产生混合激励和付费游戏动态,而该组织一直试图避免这种情况。然而,社区对支持特定项目有很大的兴趣,这是有道理的,因为该基金会现在拥有更多种类的项目,但并不是每个成员都对每个项目进行了投入了大量精力。
|
||||
|
||||
Bryce 表示,基金会的领导层和董事会,花费了大量时间来考虑,如何使基金会的核心原则与这种新模式相协调。因此,该模型试图将过去十年运行良好的 OpenStack/OpenInfra 技术治理模型的优点,与这些新的财务考虑相结合。
|
||||
|
||||
在这种“定向资助”模式下,每个新项目都将拥有自己的法人实体来持有项目资金。为确保新项目的合法性,OpenInfra Platinum 会员(目前为 9 家,包括蚂蚁集团、华为、Meta、微软和红帽)必须担任项目的发起人,之后其他组织才能加入项目基金。如果赞助公司还不是 OpenInfra 成员,则必须成为其中的成员。然后,所有这些资助成员组成一个项目基金管理委员会,决定创建预算的费用。与此同时,OpenInfra 基金会将为这些项目提供社区建设服务。
|
||||
|
||||
这种新模式暂时只适用于加入基金会的新项目。Bryce 和 Collier 指出,组织可能会在一些现有项目中追溯应用这种新模式,但这个考虑目前不在路线图上。
|
||||
|
||||
自从将范围扩展到 OpenStack 之后,OpenInfra 基金会增加了一些新项目,例如用于提高容器安全性的 Kata Containers、用于基础设施生命周期管理的 Airship、Startling X 边缘计算堆栈以及 Zuul CI/CD 平台。
|
||||
|
||||
“我们从每个成功的项目中学到的最重要的一点是,协作是关键,支持生态系统的范围越广越好,” OpenInfra 基金会总经理 Thierry Carrez 说,“事实上,我们发现最成功的开源项目是由多家公司资助的,因为他们能够整合资源以实现更高的回报率。”
|
||||
|
||||
这种新模式显然是 OpenInfra 基金会引入新项目和新成员的一种方式。正如领导团队欣然承认的那样,其在多方生态系统中管理开源项目的模型 —— 无论是通过新的定向资金还是更传统的方法 —— 可能并不适合每个项目。即使 OpenInfra 基金会只收到一小部分项目,随着对这些复杂云基础设施项目需求的增长,开源项目的数量也在增加,同时它们也变得更加复杂。
|
||||
|
||||
基金会还宣布了其各个项目的几个里程碑版本,包括 Kata Containers 2.0 版、Zuul 5.0 版和 StarlingX 6.0 的发布。
|
||||
|
||||
Collier 说:“基金会今年庆祝成立 10 周年,在展望下一个十年的开放基础设施之际,我们正在推动我们的模型如此成功的关键,那就是:将希望合作的公司和个人联合起来,为他们提供一个框架和有效协作的工具,并帮助他们投资资金以最好地帮助他们关心的项目。”
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://www.opensourceforu.com/2022/06/openinfra-foundation-launches-directed-funding-to-support-open-source-projects/
|
||||
|
||||
作者:[Laveesh Kocher][a]
|
||||
选题:[lkxed][b]
|
||||
译者:[lkxed](https://github.com/lkxed)
|
||||
校对:[校对者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/06/open-infra-berlin-event.png
|
@ -0,0 +1,86 @@
|
||||
[#]: subject: "Cloudflare Has Something New to Replace Annoying CAPTCHAs on the Internet"
|
||||
[#]: via: "https://news.itsfoss.com/cloudflare-pat/"
|
||||
[#]: author: "Jacob Crume https://news.itsfoss.com/author/jacob/"
|
||||
[#]: collector: "lkxed"
|
||||
[#]: translator: "lkxed"
|
||||
[#]: reviewer: " "
|
||||
[#]: publisher: " "
|
||||
[#]: url: " "
|
||||
|
||||
Cloudflare 有了一个新东西,它可以替代互联网上烦人的验证码
|
||||
======
|
||||
不想通过正确输入 <ruby>验证码<rt>CAPTCHA</rt></ruby> 来证明自己是个人类吗?Cloudflare 可能有了一个解决方案。
|
||||
|
||||
![Cloudflare][1]
|
||||
|
||||
互联网服务巨头 Cloudflare(在 6 月 9 日)[刚刚宣布了][2] <ruby>私有访问令牌<rt>Private Access Tokens</rt></ruby> 功能。这项功能旨在减少你在网络上看到的验证码数量,同时改善你的隐私。
|
||||
|
||||
你可能已经发现,验证码在移动设备上是一种可怕的体验。通常,它们会最终会占据整个屏幕,有时甚至也无法完成。
|
||||
|
||||
作为替代方案,网站可以选择收集唯一识别数据,以证明你是人类。当然,从隐私的角度来看,这种做法是很糟糕的。如果这么做,许多重视隐私的公司都几乎无法避免 <ruby>僵尸攻击<rt>bot attacks</rt></ruby>。
|
||||
|
||||
幸运的是,私有访问令牌(PATs)的发布将改变这一点。
|
||||
|
||||
### 私有访问令牌会产生什么影响?
|
||||
|
||||
简而言之,私有访问令牌能够做到下面这些事:
|
||||
|
||||
* 在支持设备上减少验证码数量
|
||||
* 增强用户隐私
|
||||
* 允许网站所有者确保访问者来自真实设备
|
||||
|
||||
然而,深入观察,我们可以看到私有访问令牌的影响力远不止于此。若使用传统的验证码,就有多个实体可以访问你的数据。
|
||||
|
||||
首先,你正在访问的网站知道你的 IP 地址和你正在访问的 URL。当然,这些数据是建立连接所需的最低要求。此外,对于更高级的功能,网站还会发送一些用户代理数据,还好这些数据并不是唯一可识别的。
|
||||
|
||||
然而,另一方,也就是验证码提供者,却可以收集更多的数据。与你要访问的网站一样,它也知道你的 IP 地址、用户代理数据和你访问的 URL。不幸的是,除此之外,他们还会收集其他数据,例如你的设备信息和交互数据。如果把这些信息,与你之前完成验证码的时间联系起来,你就会惊讶的发现,他们可以建立一个非常详细的属于你的个人资料。
|
||||
|
||||
幸运的是,有了 Cloudflare 的私有访问令牌,你就可以完全绕过验证码,从而阻止验证码提供者收集此类数据。
|
||||
|
||||
### 私有访问令牌是如何工作的?
|
||||
|
||||
![][3]
|
||||
|
||||
验证码的理念是集中尽可能多的数据,私人访问令牌则恰恰相反,它将数据去中心化,因此任何一方都无法唯一识别你。在你提到数据共享之前,Cloudflare 就已经特别指出了,数据不会在各方之间共享。
|
||||
|
||||
当你访问使用 Cloudflare 和私人访问令牌的网站的时候,共有三方将处理你的数据的不同部分。
|
||||
|
||||
1. 网站。它只会知道你的 IP、URL 和用户代理,这也是建立连接所必需的。
|
||||
2. 你的设备制造商。他们只会知道那些用于验证设备是否真实所需的设备数据,而不会知道你正在访问哪个网站,或你的 IP 地址是什么。验证了你的设备后,他们将生成一个令牌,该令牌将发送到 Cloudflare。
|
||||
3. Cloudflare。他们将收到这个令牌,令牌中不包含你的任何设备数据,只有制造商对它是正品的“保证”。他们知道的唯一其他数据,就是你正在访问的网站,同样,这是为你提供内容所必需的。
|
||||
|
||||
通过这种方式,Cloudflare 无需接触你的数据,就可以对“你是一个人”充满信心。
|
||||
|
||||
### 支持的操作系统:没有 Linux?
|
||||
|
||||
你可能已经意识到,私人访问令牌需要特定的操作系统功能才能工作。目前,它们仅存在于苹果最新的操作系统上,即 iOS 和 iPadOS 16,以及 macOS Ventura。这是因为苹果的操作系统只在有限的硬件上运行,设备验证会更加容易。
|
||||
|
||||
另一方面,Linux 是一种通用操作系统,旨在在各种硬件上运行。因此,我认为,在可预见的未来,它都不会支持私人访问令牌。
|
||||
|
||||
回到苹果,我想到私人访问令牌也可能导致消费者维修设备的权利出现一些问题。例如,如果我用第三方的非正品电池更换了老旧的 iPhone 原装电池,私人访问令牌系统会特殊对待这种情况吗?
|
||||
|
||||
如果是 Linux 手机呢?这些制造商,如 Pine64 和 Purism,可能没有支持这样一个系统的基础设施。是否可以在这些上使用私人访问令牌呢?
|
||||
|
||||
Cloudflare 在 [公告帖][4] 中提到:
|
||||
|
||||
> 我们正在积极努力让其他客户和设备制造商也使用私人访问令牌框架。每当新客户开始使用它时,从该客户进入你网站的流量将自动开始要求令牌,你的访问者将自动看到更少的验证码。
|
||||
|
||||
因此,我们希望看到它被更多的设备和操作系统采用。你如何看待 Cloudflare 的私人访问令牌呢?在下面的评论中发表你的看法吧!
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://news.itsfoss.com/cloudflare-pat/
|
||||
|
||||
作者:[Jacob Crume][a]
|
||||
选题:[lkxed][b]
|
||||
译者:[lkxed](https://github.com/lkxed)
|
||||
校对:[校对者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/06/cloudflare-private-access-tokens.jpg
|
||||
[2]: https://blog.cloudflare.com/eliminating-captchas-on-iphones-and-macs-using-new-standard/
|
||||
[3]: https://news.itsfoss.com/wp-content/uploads/2022/06/PAT-Data-transfer-chart-1024x650.png
|
||||
[4]: https://blog.cloudflare.com/eliminating-captchas-on-iphones-and-macs-using-new-standard/
|
@ -1,99 +0,0 @@
|
||||
[#]: subject: "openSUSE Leap 15.4 Release Adds Leap Micro 5.2, Updated Desktop Environments, and More"
|
||||
[#]: via: "https://news.itsfoss.com/opensuse-leap-15-4-release/"
|
||||
[#]: author: "Ankush Das https://news.itsfoss.com/author/ankush/"
|
||||
[#]: collector: "lkxed"
|
||||
[#]: translator: "robsean"
|
||||
[#]: reviewer: " "
|
||||
[#]: publisher: " "
|
||||
[#]: url: " "
|
||||
|
||||
openSUSE Leap 15.4 发布版本添加了 Leap Micro 5.2、更新桌面环境等等
|
||||
======
|
||||
为奋起直追 SUSE Linux Enterprise 的 Service Pack 4 ,openSUSE Leap 15.4 到来了,带来了新的升级和极其重要的改善。
|
||||
|
||||
![opensuse 15.4][1]
|
||||
|
||||
即将到来的 openSUSE 小发布版本终于要来了。如果你使用 OpenSUSE 作为你日常驱动的桌面或服务器版本,你现在可能已经测试候选版本好几周了。
|
||||
|
||||
openSUSE Leap 15.4 专注于软件包的更新,用以奋起直追 SUSE Linux Enterprise 的 Service Pack 4 。因此,你将注意到一些弃用的软件包,以及可用于替换它们的新的升级。
|
||||
|
||||
当然,你应该有一些可用的软件包来确保兼容性。但是,大多数较旧的版本已经被移除。
|
||||
|
||||
### openSUSE Leap 15.4: 有什么新的变化?
|
||||
|
||||
为与最新的 SUSE Linux Enterprise (SLE) 相适应,像 Python 2 和 KDE 4 一样的软件包已经被移除。你可以在这次的发布版本中找到较新的桌面环境。
|
||||
|
||||
此外,在容器和 AI/ML 用例方面,更新 podman、containerd、Tensorflow 和 Grafana。
|
||||
|
||||
#### Leap Micro 5.2
|
||||
|
||||
Leap Micro 是针对容器和虚拟化工作负载定制的轻量级操作系统的最新版本。它也是一个针对 leap 的 [MicroOS][2] 的新作品,它是 Tumbleweed 的一种变体, 提供自动地管理和修补。
|
||||
|
||||
#### 桌面环境
|
||||
|
||||
Xfce 4.16 继续保留,但是你可以找到下一个主要版本中的一些的特色功能,包括新图标和调色板。
|
||||
|
||||
在 Xfce 4.16 中的设置管理器也获得了视觉上的刷新。类似地,文件管理器 (Thunar) 也有一些改善,暗黑模式支持一个新的状态托盘插件等等。
|
||||
|
||||
KDE 4 软件包已经被弃用,Plasma 5.24 LTS 已经包含在一个 LTS 发布版本中。
|
||||
|
||||
为探索这些更改,你可以查看我们针对 [KDE Plasma 5.24 LTS][3] 的原始的新闻报道。总得来说,新的 KDE Plasma 体验应该会令桌面用户赞叹。
|
||||
|
||||
当它来到 GNOME 时,你可以发现包含在 openSUSE Leap 15.4 中的 GNOME 41 带来了一系列的改善和新的特色功能。了解更多关于 [GNOME 41][4] 的信息来知道你可以期待哪些新的特色功能。
|
||||
|
||||
对于其它的可用的桌面环境来说,Leap 15.4 包括:
|
||||
|
||||
* MATE 桌面环境 1.26
|
||||
* Enlightenment 桌面环境0.25.3
|
||||
* <ruby>深度<rt>Deepin</rt></ruby> 桌面环境 20.3
|
||||
|
||||
#### 弃用的软件包
|
||||
|
||||
一些极其重要的软件包已经被移除,包括 python 2 (生命终结)、digika、tensorflow 1.x 和 Qt 4 等软件包。
|
||||
|
||||
在更新系统后,你将找到可用的 Qt 5 和 Plasma 5 。
|
||||
|
||||
#### 更新的软件包
|
||||
|
||||
针对 Leap 15.4 更新了很多重要的软件包, 包含一些流行的软件包:
|
||||
|
||||
* TensorFlow 2.6.2
|
||||
* podman 3.4.4
|
||||
* GNU Health 4.0
|
||||
* sudo 1.9.9
|
||||
* systemd 249.10
|
||||
* AppArmor 3.04
|
||||
* DNF 4.10.0
|
||||
* LibreOffice 7.2.5
|
||||
|
||||
因此,你应该会注意到一些有用的针对服务器用户和桌面用户的各种各样的应用程序的更新的升级。很多多媒体应用程序,像 VLC、GNOME MPV 等,都接受到了升级。
|
||||
|
||||
#### 其它改善
|
||||
|
||||
随着极其重要的软件的更新和清理,你也可以找到一个较新的由 SUSE 维护的 Linux 内核 5.14.21 版本。
|
||||
|
||||
随着内核的更新,硬件的支持也会带来改善。
|
||||
|
||||
更多信息,你可以参考针对 [openSUSE Leap 15.4][5] 的发布版本说明。
|
||||
|
||||
[下载 openSUSE Leap 15.4][6]
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://news.itsfoss.com/opensuse-leap-15-4-release/
|
||||
|
||||
作者:[Ankush Das][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://news.itsfoss.com/author/ankush/
|
||||
[b]: https://github.com/lkxed
|
||||
[1]: https://news.itsfoss.com/wp-content/uploads/2022/06/opensuse-leap-15-4.jpg
|
||||
[2]: https://microos.opensuse.org/
|
||||
[3]: https://news.itsfoss.com/kde-plasma-5-24-lts-release/
|
||||
[4]: https://news.itsfoss.com/gnome-41-release/
|
||||
[5]: https://doc.opensuse.org/release-notes/x86_64/openSUSE/Leap/15.4/#rnotes
|
||||
[6]: https://get.opensuse.org/leap/15.4/
|
@ -0,0 +1,273 @@
|
||||
[#]: subject: "How To Boot Into Rescue Mode Or Emergency Mode In Ubuntu 22.04 / 20.04 / 18.04"
|
||||
[#]: via: "https://ostechnix.com/how-to-boot-into-rescue-mode-or-emergency-mode-in-ubuntu-18-04/"
|
||||
[#]: author: "sk https://ostechnix.com/author/sk/"
|
||||
[#]: collector: "lkxed"
|
||||
[#]: translator: "robsean"
|
||||
[#]: reviewer: " "
|
||||
[#]: publisher: " "
|
||||
[#]: url: " "
|
||||
|
||||
如何在 Ubuntu 22.04 / 20.04 / 18.04 中启动到 <ruby>救援<rt>Rescue</rt></ruby> 模式 或 <ruby>紧急<rt>Emergency</rt></ruby> 模式
|
||||
======
|
||||
这篇教程将介绍如何在 Ubuntu 22.04、20.04 和 18.04 LTS 版本中启动到 <ruby>救援<rt>Rescue</rt></ruby> 模式 或 <ruby>紧急<rt>Emergency</rt></ruby> 模式。
|
||||
|
||||
你可能已经知道,在 Linux 发行版中 **<ruby>运行等级<rt>Runlevels</rt></ruby>** 已经被 **<ruby>系统目标<rt>Systemd targets</rt></ruby>** 所替代,例如, RHEL 7 、RHEL 8 、Ubuntu 16.04 LTS 及其更新的版本。更多关于 <ruby>运行等级<rt>Runlevels</rt></ruby> 和 <ruby>系统目标<rt>Systemd targets</rt></ruby> 的信息,参考 [这篇指南][1] 。
|
||||
|
||||
这篇指南是针对 Ubuntu 编写的,但是,下面所给的步骤应该也适用于大多数使用 **Systemd** 作为默认服务管理器的 Linux 发行版。
|
||||
|
||||
在进入主题前,让我们简单的理解:什么是 <ruby>救援<rt>rescue</rt></ruby> 模式 和 <ruby>紧急<rt>Emergency</rt></ruby> 模式,以及这两种模式的目的是什么。
|
||||
|
||||
### 什么是 <ruby>救援<rt>rescue</rt></ruby> 模式?
|
||||
|
||||
在 Linux 发行版中,<ruby>救援<rt>rescue</rt></ruby> 模式 等效于 <ruby>单用户<rt>single user</rt></ruby> 模式,它使用 **SysV** 作为默认的服务器管理器。在 <ruby>救援<rt>rescue</rt></ruby> 模式 中,将挂载所有的本地文件系统,将仅启动一些重要的服务。但是,不会启动一般的服务 (例如,网络服务)。
|
||||
|
||||
<ruby>救援<rt>rescue</rt></ruby> 模式 在不能正常启动系统的情况下是很有用的。此外,我们可以在 <ruby>救援<rt>rescue</rt></ruby> 模式 下执行一些重要的 <ruby>救援<rt>rescue</rt></ruby> 操作,例如,[重新设置 root 密码][2] 。
|
||||
|
||||
### 什么是 <ruby>紧急<rt>Emergency</rt></ruby> 模式?
|
||||
|
||||
与 <ruby>救援<rt>rescue</rt></ruby> 模式相比, 在 <ruby>紧急<rt>Emergency</rt></ruby> 模式中,不会启动任何的东西。不会启动服务,不会挂载挂载点,不会建立套接字,什么都不会启动。你将所拥有的只是一个 **原始的 shell** 。<ruby>紧急<rt>Emergency</rt></ruby> 模式适用于调试目的。
|
||||
|
||||
首先,我们将看到如何在 Ubuntu 22.04 和 20.04 LTS 发行版中启动到 <ruby>救援<rt>Rescue</rt></ruby> 模式 或 <ruby>紧急<rt>Emergency</rt></ruby> 模式。在 Ubuntu 22.04 和 20.04 LTS 中进入 <ruby>救援<rt>rescue</rt></ruby> 模式 的过程是完全相同的!
|
||||
|
||||
### 在 Ubuntu 22.04 / 20.04 LTS 中启动到 <ruby>救援<rt>rescue</rt></ruby> 模式
|
||||
|
||||
我们可以使用两种方法来启动到 <ruby>救援<rt>rescue</rt></ruby> 模式。
|
||||
|
||||
#### 方法 1
|
||||
|
||||
打开你的 Ubuntu 系统。在 BIOS 徽标出现后,按下 ESC 按键来显示 GRUB 菜单。
|
||||
|
||||
在 GRUB 菜单中,选择第一项,并按下 **"e"** 按键来编辑它。
|
||||
|
||||
![GRUB Menu In Ubuntu 22.04 / 20.04 LTS][3]
|
||||
|
||||
按下 **下箭头** 按键,并找到以单词 **"linux"** 开头的一行代码,并在其结尾处添加下面的一行代码。为到达其结尾处,只需要按下 **CTRL+e** 组合键,或使用你键盘上的 **END** 按键或 **左箭头/右箭头** 按键。
|
||||
|
||||
```
|
||||
systemd.unit=rescue.target
|
||||
```
|
||||
|
||||
![Edit Grub Boot Menu Entries To Enter Into Rescue Mode In Ubuntu 22.04 / 20.04 LTS][4]
|
||||
|
||||
在添加上面的代码行后,按下 **Ctrl+x** 组合键 或按下 **F10** 按键来启动到 <ruby>救援<rt>rescue</rt></ruby> 模式.
|
||||
|
||||
数秒后,你将作为 root 用户来登陆到 <ruby>救援<rt>rescue</rt></ruby> 模式 (<ruby>单用户<rt>single user</rt></ruby> 模式) 。将会提示你按下 <ruby>回车<rt>ENTER</rt></ruby> 按键来进入维护模式。
|
||||
|
||||
下图是 Ubuntu 22.04 / 20.04 LTS 系统的 <ruby>救援<rt>rescue</rt></ruby> 模式 的样子:
|
||||
|
||||
![Boot Into Rescue Mode In Ubuntu 22.04 / 20.04 LTS][5]
|
||||
|
||||
现在,在 <ruby>救援<rt>rescue</rt></ruby> 模式 中做你想做的任何事。在 <ruby>救援<rt>rescue</rt></ruby> 模式 中,在你执行任何操作前,你可能需要以 读/写 模式 的方式来挂载 root (**/**) 文件系统。
|
||||
|
||||
```
|
||||
mount -n -o remount,rw /
|
||||
```
|
||||
|
||||
![Mount Root File System In Read Write Mode In Ubuntu 22.04 / 20.04 LTS][6]
|
||||
|
||||
在完成后,按下 **"Ctrl+d"** 组合键来启动到正常模式。或者,你可以输入下面的任意一个命令来启动到正常模式。
|
||||
|
||||
```
|
||||
systemctl default
|
||||
```
|
||||
|
||||
或者,
|
||||
|
||||
```
|
||||
exit
|
||||
```
|
||||
|
||||
如果你想重新启动系统,而不是启动到正常的模式,输入:
|
||||
|
||||
```
|
||||
systemctl reboot
|
||||
```
|
||||
|
||||
#### 方法 2
|
||||
|
||||
在这种方法中,你不需要编辑 GRUB 启动菜单项目。
|
||||
|
||||
打开系统电源,并从 GRUB 启动菜单中选择 <ruby>Ubuntu 高级选项<rt>Advanced options for Ubuntu</rt></ruby>。
|
||||
|
||||
![Choose Advanced Options For Ubuntu From Grub Boot Menu][7]
|
||||
|
||||
接下来,你将看到一个带有内核版本的可用的 Ubuntu 版本的列表。在 Ubuntu 中的 GRUB 启动菜单中选择 <ruby>恢复<rt>Recovery</rt></ruby> 模式。
|
||||
|
||||
![Choose Recovery Mode In Grub Boot Menu In Ubuntu 22.04 / 20.04 LTS][8]
|
||||
|
||||
数秒后,你将看到 Ubuntu 的 <ruby>恢复<rt>Recovery</rt></ruby> 菜单。从 <ruby>恢复<rt>Recovery</rt></ruby> 菜单中,选择 **<ruby>进入 root 的 shell 提示符<rt>Drop to root shell prompt</rt></ruby>** 选项 ,并按下 <ruby>回车<rt>ENTER</rt></ruby> 按键。
|
||||
|
||||
![Enter Into Root Shell Prompt In Ubuntu 22.04 / 20.04 LTS][9]
|
||||
|
||||
现在,你将登陆到 <ruby>救援<rt>rescue</rt></ruby> 模式。
|
||||
|
||||
![Ubuntu Maintenance Mode][10]
|
||||
|
||||
通过输入下面的命令来 以 读/写 模式的方式 来挂载 root (**/**) 文件系统:
|
||||
|
||||
```
|
||||
mount -n -o remount,rw /
|
||||
```
|
||||
|
||||
![Mount Root File System In Read Write Mode In Ubuntu][11]
|
||||
|
||||
在 <ruby>救援<rt>rescue</rt></ruby> 模式 中做你想做的任何事。
|
||||
|
||||
在完成后,输入 **exit** 来返回到 <ruby>恢复<rt>Recovery</rt></ruby> 菜单。
|
||||
|
||||
```
|
||||
exit
|
||||
```
|
||||
|
||||
最后,选择 **<ruby>救援正常启动<rt>Resume normal boot</rt></ruby>** 选项,并按下 <ruby>回车<rt>ENTER</rt></ruby> 按键。
|
||||
|
||||
![Boot Into Normal Mode In Ubuntu][12]
|
||||
|
||||
再次按下 <ruby>回车<rt>ENTER</rt></ruby> 按键来退出 <ruby>恢复<rt>Recovery</rt></ruby> 模式,并继续启动到正常模式。
|
||||
|
||||
![Exit The Recovery Mode In Ubuntu][13]
|
||||
|
||||
如果你不想启动到正常模式,输入 **reboot** 并从维护模式中按下 <ruby>回车<rt>ENTER</rt></ruby> 按键来重新启动你的系统。
|
||||
|
||||
### 在 Ubuntu 22.04 / 20.04 LTS 中启动到 <ruby>紧急<rt>Emergency</rt></ruby> 模式
|
||||
|
||||
当 GRUB 菜单出现时,按下 **"e"** 按键来编辑它。
|
||||
|
||||
![GRUB Menu In Ubuntu 22.04 / 20.04 LTS][14]
|
||||
|
||||
找到以单词 **"linux"** 开头的一行代码,并在其结尾处添加下面的一行代码。
|
||||
|
||||
```
|
||||
systemd.unit=emergency.target
|
||||
```
|
||||
|
||||
![Edit Grub Boot Menu Entries To Enter Into Emergency Mode In Ubuntu 22.04 / 20.04 LTS][15]
|
||||
|
||||
在添加上面的代码行后,按下 **Ctrl+x** 组合键,或按下 **F10** 按键来启动到 <ruby>紧急<rt>Emergency</rt></ruby> 模式。
|
||||
|
||||
数秒后,你将作为 `root` 用户来登陆到 <ruby>紧急<rt>Emergency</rt></ruby> 模式。将会提示你按下 <ruby>回车<rt>ENTER</rt></ruby> 按键来进入维护模式。
|
||||
|
||||
下图是 Ubuntu 22.04 / 20.04 LTS 系统的 <ruby>紧急<rt>Emergency</rt></ruby> 模式 的样子:
|
||||
|
||||
![Boot Into Emergency Mode In Ubuntu 22.04 / 20.04 LTS][16]
|
||||
|
||||
现在,在 <ruby>紧急<rt>Emergency</rt></ruby> 模式 中做你想做的任何事。在 <ruby>紧急<rt>Emergency</rt></ruby> 模式 中,在你执行任何操作前,你可能需要以 读/写 模式 的方式来挂载 root (**/**) 文件系统。
|
||||
|
||||
```
|
||||
mount -n -o remount,rw /
|
||||
```
|
||||
|
||||
在完成后,按下 **"Ctrl+d"** 组合键来启动到正常模式。或者,你可以输入下面的任意一个命令来启动到正常模式。
|
||||
|
||||
```
|
||||
systemctl default
|
||||
```
|
||||
|
||||
或者,
|
||||
|
||||
```
|
||||
exit
|
||||
```
|
||||
|
||||
如果你想重新启动系统,而不是启动到正常的模式,输入:
|
||||
|
||||
```
|
||||
systemctl reboot
|
||||
```
|
||||
|
||||
### 在 Ubuntu 18.04 LTS 中启动到 <ruby>救援<rt>rescue</rt></ruby> 模式
|
||||
|
||||
启动你的 Ubuntu 系统。当 GRUB 菜单出现时,选择第一项并按下按键 **"e"** 来编辑。(为到达其结尾处,只需要按下 **CTRL+e** 组合键,或使用你键盘上的 **END** 按键或 **左箭头/右箭头** 按键):
|
||||
|
||||
![Grub Menu][17]
|
||||
|
||||
如果你没有看到 GRUB 菜单,只需要在 BIOS 徽标出现后,按下 ESC 按键来显示 GRUB 菜单。
|
||||
|
||||
找到以单词 **"linux"** 开头的一行代码,并在其结尾处添加下面的一行代码 (为到达其结尾处,只需要按下 **CTRL+e** 组合键,或使用你键盘上的 **END** 按键或 **左箭头/右箭头** 按键):
|
||||
|
||||
```
|
||||
systemd.unit=rescue.target
|
||||
```
|
||||
|
||||
![Edit Grub Menu][18]
|
||||
|
||||
在添加上面的代码行后,只需要按下 **Ctrl+x** 组合键,或按下 **F10** 按键来启动到 <ruby>救援<rt>rescue</rt></ruby> 模式。数秒后,你将作为 `root` 用户来登陆到 <ruby>救援<rt>rescue</rt></ruby> 模式 (<ruby>单用户<rt>single user</rt></ruby> 模式) 。
|
||||
|
||||
下图是 Ubuntu 18.04 LTS 服务器 系统的 <ruby>救援<rt>rescue</rt></ruby> 模式 的样子:
|
||||
|
||||
![Ubuntu Rescue Mode][19]
|
||||
|
||||
接下来,输入下面的命令来挂载 root (**/**) 文件系统为 读/写 模式。
|
||||
|
||||
```
|
||||
mount -n -o remount,rw /
|
||||
```
|
||||
|
||||
### 启动到 <ruby>紧急<rt>Emergency</rt></ruby> 模式
|
||||
|
||||
启动你的 Ubuntu 到 <ruby>紧急<rt>Emergency</rt></ruby> 模式 基本与上述方法相同。你所需要做的全部工作是,在编辑 GRUB 菜单时,将 **"systemd.unit=rescue.target"** 替换为 **"systemd.unit=emergency.target"** 。
|
||||
|
||||
![Edit Grub Menu][20]
|
||||
|
||||
在你添加 "systemd.unit=emergency.target" 后,按下 **Ctrl+x** 组合键,或按下 **F10** 按键来启动到 <ruby>紧急<rt>Emergency</rt></ruby> 模式。
|
||||
|
||||
![Ubuntu Emergency Mode][21]
|
||||
|
||||
最后,你可以使用下面的命令来以 读/写 模式的方式 来挂载 root (**/**) 文件系统:
|
||||
|
||||
```
|
||||
mount -n -o remount,rw /
|
||||
```
|
||||
|
||||
### 在 <ruby>救援<rt>rescue</rt></ruby> 模式 和 <ruby>紧急<rt>Emergency</rt></ruby> 模式 之间切换
|
||||
|
||||
如果你正在 <ruby>救援<rt>rescue</rt></ruby> 模式 中,你不必像我上述提到的那样来编辑 GRUB 的菜单启动项。相反,你只想要输入下面的命令来立刻切换到 <ruby>紧急<rt>Emergency</rt></ruby> 模式:
|
||||
|
||||
```
|
||||
systemctl emergency
|
||||
```
|
||||
|
||||
同样,为从 <ruby>紧急<rt>Emergency</rt></ruby> 模式 切换到 <ruby>救援<rt>rescue</rt></ruby> 模式,输入:
|
||||
|
||||
```
|
||||
systemctl rescue
|
||||
```
|
||||
|
||||
### 总结
|
||||
|
||||
现在,你知道了什么是 <ruby>救援<rt>Rescue</rt></ruby> 模式 和 <ruby>紧急<rt>Emergency</rt></ruby> 模式,以及如何在 Ubuntu 22.04 、20.04 和 18.04 LTS 系统中启动到这些模式。 正如我已经提到的,在这里提供的这些步骤应该也适用于大多数当前使用 **Systemd** 作为默认服务管理器的 Linux 发行版。
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://ostechnix.com/how-to-boot-into-rescue-mode-or-emergency-mode-in-ubuntu-18-04/
|
||||
|
||||
作者:[sk][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://ostechnix.com/author/sk/
|
||||
[b]: https://github.com/lkxed
|
||||
[1]: https://ostechnix.com/check-runlevel-linux/
|
||||
[2]: https://ostechnix.com/how-to-reset-or-recover-root-user-password-in-linux/
|
||||
[3]: https://ostechnix.com/wp-content/uploads/2022/05/GRUB-Menu-In-Ubuntu-22.04-LTS.png
|
||||
[4]: https://ostechnix.com/wp-content/uploads/2022/05/Edit-Grub-Boot-Menu-Entries-To-Enter-Into-Rescue-Mode-In-Ubuntu-22.04-LTS.png
|
||||
[5]: https://ostechnix.com/wp-content/uploads/2022/05/Boot-Into-Rescue-Mode-In-Ubuntu-22.04.png
|
||||
[6]: https://ostechnix.com/wp-content/uploads/2022/05/Mount-Root-File-System-In-Read-Write-Mode-In-Ubuntu.png
|
||||
[7]: https://ostechnix.com/wp-content/uploads/2022/05/Choose-Advanced-Options-For-Ubuntu-From-Grub-Boot-Menu.png
|
||||
[8]: https://ostechnix.com/wp-content/uploads/2022/05/Choose-Recovery-Mode-In-Grub-Boot-Menu-In-Ubuntu.png
|
||||
[9]: https://ostechnix.com/wp-content/uploads/2022/05/Enter-Into-Root-Shell-Prompt-In-Ubuntu.png
|
||||
[10]: https://ostechnix.com/wp-content/uploads/2022/05/Ubuntu-Maintenance-Mode.png
|
||||
[11]: https://ostechnix.com/wp-content/uploads/2022/05/Mount-Root-File-System-In-Read-Write-Mode-In-Ubuntu-1.png
|
||||
[12]: https://ostechnix.com/wp-content/uploads/2022/05/Boot-Into-Normal-Mode-In-Ubuntu.png
|
||||
[13]: https://ostechnix.com/wp-content/uploads/2022/05/Exit-The-Recovery-Mode-In-Ubuntu.png
|
||||
[14]: https://ostechnix.com/wp-content/uploads/2022/05/GRUB-Menu-In-Ubuntu-22.04-LTS.png
|
||||
[15]: https://ostechnix.com/wp-content/uploads/2022/05/Edit-Grub-Boot-Menu-Entries-To-Enter-Into-Emergency-Mode-In-Ubuntu.png
|
||||
[16]: https://ostechnix.com/wp-content/uploads/2018/12/Boot-Into-Emergency-Mode-In-Ubuntu-20.04-LTS.png
|
||||
[17]: https://ostechnix.com/wp-content/uploads/2018/12/Grub-menu.png
|
||||
[18]: https://ostechnix.com/wp-content/uploads/2018/12/Edit-grub-menu.png
|
||||
[19]: https://ostechnix.com/wp-content/uploads/2018/12/Ubuntu-rescue-mode.png
|
||||
[20]: https://ostechnix.com/wp-content/uploads/2018/12/emergency-mode.png
|
||||
[21]: https://ostechnix.com/wp-content/uploads/2018/12/emergency-mode-1.png
|
@ -1,88 +0,0 @@
|
||||
[#]: subject: "6 Linux word processors you need to try"
|
||||
[#]: via: "https://opensource.com/article/22/6/word-processors-linux"
|
||||
[#]: author: "Don Watkins https://opensource.com/users/don-watkins"
|
||||
[#]: collector: "lkxed"
|
||||
[#]: translator: "duoluoxiaosheng"
|
||||
[#]: reviewer: " "
|
||||
[#]: publisher: " "
|
||||
[#]: url: " "
|
||||
|
||||
6 Linux word processors you need to try
|
||||
======
|
||||
值得尝试的六款Linux文字处理程序
|
||||
======
|
||||
|
||||
选择一款最中意的文字处理程序把你的想法打印到纸上。
|
||||
|
||||
![Typewriter with hands][1]
|
||||
|
||||
Image by: rawpixel.com. CC0.
|
||||
|
||||
作家们总是在寻找更好的方法将他们的文字和想法以更好的方式呈现给他们的读者。我对文字处理程序最早的印象是在 Apple II 上使用 AppleWorks 和 FrEDWriter,一个1985年的免费的文字处理程序。这是我的学生的标配,他们中的许多人来自没有钱购买专用软件的家庭。
|
||||
|
||||
### Abiword
|
||||
|
||||
在20世纪90年代时,我开始使用 Linux, 我开始寻找高质量的写作程序,以推荐给在开源软件世界跟随我的学生。我首先接触的文字处理程序是 [AbiWord][2]。 AbiWord 来自西班牙语 Abierto,是打开的意思。最早发布于1998年,并且之后一直在升级。使用 GPLv2 开源协议。支持列表,缩进,字符格式等基本功能。支持比如 ".doc", ".html", ".docx", ".odt" 等多种格式文件的导入和导出。
|
||||
|
||||
![Image of Abiword][3]
|
||||
|
||||
### Etherpad
|
||||
|
||||
[Etherpad][4] 是一个开源项目。它可以让您像 Google Drive 那样实时编辑文档。它完全开源。据它的网站上介绍,您可以用它来写文章,新闻稿和待办清单,还可以和您的朋友,同学或者同事一起同时编辑同一个文档。源代码可查看。Etherpad 采用 Apache 2.0 开源协议。您可以直接在线使用它,或者把它下载并[安装][5]到您的 Linux 电脑上。
|
||||
|
||||
### Cryptpad
|
||||
|
||||
[CryptPad][6] 是一个端到端加密的写作套件。使用 GPLv3 开源协议,并且源代码在 [GitHub][7] 上公开。 由 [Xwiki][8] 实验室开发。可替代 Google Drive 并且自主托管。根据网站描述 “CryptPad 旨在实现协作办公。实时同步文档的更改。由于所有数据都已加密,因此服务及其管理员无法查看正在编辑和存储的内容。” Cryptpad 为用户提供了[丰富的文档][9]。
|
||||
|
||||
### Focuswriter
|
||||
|
||||
[FocusWriter][10] 是一个简单的免干扰的编辑器。它使用隐藏的界面,鼠标移动到屏幕边界时可以显示。使用 GPLv3 开源协议并提供 Linux 通用软件安装包(Flatpak),比如 [Ubuntu][11] 的 DEB 和 [Fedora][12] 的 RPM。这是一个 FocusWriter 桌面的例子。 一个非常简单直观的界面,菜单自动隐藏,鼠标指向屏幕顶部或边缘时才显示。文件默认保存为 ".odt" 格式,也支持纯文本, ".docx",和富文本。
|
||||
|
||||
![Image of FocusWriter][13]
|
||||
|
||||
### LibreOffice Writer
|
||||
|
||||
[LibreOffice Writer][14]是我最喜欢的。我已经使用了十多年了。他拥有我需要的富文本的所有特性。他还拥有我见过的最大的导入导出列表。类似 [APA][15]这样的问卷和出版模板它拥有十多种。最喜欢它的是他可以将文件导出为 PDF 和 “epub”。 LibreOffice Writer 是一个免费软件,使用 Mozilla Public Liceense 2.0 开源协议。 [源代码][16]由 Document Foundation 提供。LibreOffice 支持大多数 Linux 发行版。 同时它也提供 Flatpak,Snap 和 AppImage。另外,您也可以把它下载并安装到 MacOs 和 Windows 上。
|
||||
|
||||
![Image of LibreOffice work space][17]
|
||||
|
||||
### OpenOffice Writer
|
||||
|
||||
Apache [OpenOffice Writer][18] 是一个全功能点文字处理程序。作为一个备忘录来说它足够简单,但对于编写你的第一本书来说它又足够复杂。依据官网的描述,OpenOffice Writer 将文档自动保存为 “open document format”. 它还支持将文档保存为 ".doc", ".docx", 富文本和其他格式。OpenOffice Writer 使用 Apache License 2.0 开源协议。源代码在 [GitHub][19] 上公开。
|
||||
|
||||
这里还有许多免费的开源软件等着大家去发现。它们非常适合完成您的日常任务,您也可以为它们的发展做出贡献。您最喜欢的 Linux 文字处理器程序是什么呢?
|
||||
|
||||
Image by: (Don Watkins, CC BY-SA 4.0)
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://opensource.com/article/22/6/word-processors-linux
|
||||
|
||||
作者:[Don Watkins][a]
|
||||
选题:[lkxed][b]
|
||||
译者:[duoluoxiaosheng](https://github.com/duoluoxiaosheng)
|
||||
校对:[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译,[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
||||
[a]: https://opensource.com/users/don-watkins
|
||||
[b]: https://github.com/lkxed
|
||||
[1]: https://opensource.com/sites/default/files/lead-images/typewriter-hands.jpg
|
||||
[2]: https://www.abisource.com/
|
||||
[3]: https://opensource.com/sites/default/files/2022-05/abiword.png
|
||||
[4]: https://etherpad.org/#
|
||||
[5]: https://github.com/ether/etherpad-lite#installation
|
||||
[6]: https://cryptpad.fr/what-is-cryptpad.html
|
||||
[7]: https://github.com/xwiki-labs/cryptpad
|
||||
[8]: https://github.com/xwiki-labs
|
||||
[9]: https://docs.cryptpad.fr/en/user_guide/index.html
|
||||
[10]: https://gottcode.org/focuswriter/
|
||||
[11]: https://packages.ubuntu.com/jammy/focuswriter
|
||||
[12]: https://src.fedoraproject.org/rpms/focuswriter
|
||||
[13]: https://opensource.com/sites/default/files/2022-05/focuswriter.png
|
||||
[14]: https://www.libreoffice.org/discover/writer/
|
||||
[15]: https://extensions.libreoffice.org/en/extensions/show/apa-style-paper-template
|
||||
[16]: https://www.libreoffice.org/about-us/source-code/
|
||||
[17]: https://opensource.com/sites/default/files/2022-05/Libreofficewriter.png
|
||||
[18]: https://www.openoffice.org/product/writer.html
|
||||
[19]: https://github.com/apache/openoffice
|
@ -0,0 +1,157 @@
|
||||
[#]: subject: "How Garbage Collection works inside a Java Virtual Machine"
|
||||
[#]: via: "https://opensource.com/article/22/6/garbage-collection-java-virtual-machine"
|
||||
[#]: author: "Jayashree Huttanagoudar https://opensource.com/users/jayashree-huttanagoudar"
|
||||
[#]: collector: "lkxed"
|
||||
[#]: translator: "lkxed"
|
||||
[#]: reviewer: " "
|
||||
[#]: publisher: " "
|
||||
[#]: url: " "
|
||||
|
||||
JVM 垃圾回收的工作原理
|
||||
======
|
||||
对于程序员来说,掌握 Java 的内存管理机制并不是必须的,但它能够帮助你更好地理解 JVM 是如何处理程序中的变量和类实例的。
|
||||
|
||||
![咖啡豆][1]
|
||||
|
||||
图源:Pixabay. CC0.
|
||||
|
||||
Java 之所以能够如此流行,自动 <ruby>垃圾回收<rt>Garbage Collection</rt></ruby>(GC)功不可没,它也是 Java 最重要的几个特性之一。在这篇文章中,我将说明为什么垃圾回收如此重要。本文的主要内容为:自动的分代垃圾回收、JVM 划分内存的依据,以及 JVM 垃圾回收的工作原理。
|
||||
|
||||
### Java 内存分配
|
||||
|
||||
Java 程序的内存空间被划分为以下四个区域:
|
||||
|
||||
1. 堆区(Heap):对象实例就是在这个区域分配的。不过,当我们声明一个对象时,堆中不会有任何内存分配发生,只是在栈中创建了一个对象的引用而已。
|
||||
2. 栈区(Stack):方法、局部变量和类的实例变量就是在这个区域分配的。
|
||||
3. 代码区(Code):这个区域存放了程序的字节码。
|
||||
4. 静态区(Static):这个区域存放了程序的静态数据和静态方法。
|
||||
|
||||
### 什么是自动垃圾回收?
|
||||
|
||||
自动垃圾回收是这样一个过程:首先,堆中的所有对象会被分类为“被引用的”和“未被引用的”;接着,“未被引用的对象”就会被做上标记,以待之后删除。其中,“被引用的对象”是指程序中的某一部分仍在使用的对象,“未被引用的对象”是指目前没有正在被使用的对象。
|
||||
|
||||
许多编程语言,例如 C 和 C++,都需要程序员手动管理内存的分配和释放。在 Java 中,这一过程是通过垃圾回收机制来自动完成的(尽管你也可以在代码中调用 `system.gc();` 来手动触发垃圾回收)。
|
||||
|
||||
垃圾回收的基本步骤如下:
|
||||
|
||||
#### 1. 标记已使用和未使用的对象
|
||||
|
||||
在这一步骤中,已使用和未使用的对象会被分别做上标记。这是一个及其耗时的过程,因为需要扫描内存中的所有对象,才能够确定它们是否正在被使用。
|
||||
|
||||
![标记已使用和未使用的对象][2]
|
||||
|
||||
#### 2. 扫描/删除对象
|
||||
|
||||
有两种不同的扫描和删除算法:
|
||||
|
||||
**简单删除(标记清除)**:它的过程很简单,我们只需要删除未被引用的对象即可。但是,后续给新对象分配内存就会变得很困难了,因为可用空间被分割成了一块块碎片。
|
||||
|
||||
![标记清除的过程][3]
|
||||
|
||||
**删除压缩(标记整理)**:除了会删除未被引用的对象,我们还会压缩被引用的对象(未被删除的对象)。这样以来,新对象的内存分配就相对容易了,并且内存分配的效率也有了提升。
|
||||
|
||||
![标记整理的过程][4]
|
||||
|
||||
### 什么是分代垃圾回收,为什么需要它?
|
||||
|
||||
正如我们在“扫描删除”模型中所看到的,一旦对象不断增长,我们就很难扫描所有未使用的对象以回收内存。不过,有一项实验性研究指出,在程序执行期间创建的大多数对象,它们的存活时间都很短。
|
||||
|
||||
既然大多数对象的存活时间都很短,那么我们就可以利用这个事实,从而提升垃圾回收的效率。该怎么做呢?首先,JVM 将内存划分为不同的“代”。接着,它将所有的对象都分类到这些内存“代”中,然后对这些“代”分别执行垃圾回收。这就是“分代垃圾回收”。
|
||||
|
||||
### 堆内存的“代”和分代垃圾回收过程
|
||||
|
||||
为了提升垃圾回收中的“标记清除”的效率,JVM 将对内存划分成以下三个“代”:
|
||||
|
||||
* 年轻代
|
||||
* 老年代
|
||||
* 永久代
|
||||
|
||||
![Hotspot 堆内存结构][5]
|
||||
|
||||
下面我将介绍每个“代”及其主要特征。
|
||||
|
||||
#### 年轻代
|
||||
|
||||
所有创建不久的对象都存放在这里。年轻代被进一步分为以下两个区域:
|
||||
|
||||
1. 伊甸区(Eden):所有新创建的对象都在此处分配内存。
|
||||
2. 幸存者区(Survivor,分为 S0 和 S1):经历过一次垃圾回收后,仍然存活的对象会被移动到两个幸存者区中的一个。
|
||||
|
||||
![对象分配][6]
|
||||
|
||||
在年轻代发生的分代垃圾回收被称为 “Minor GC”。Minor GC 过程中的每个阶段都是“<ruby>停止世界<rt>Stop The World</rt></ruby>”(STW)的,这会导致其他应用程序暂停运行,直到垃圾回收结束。这也是 Minor GC 更快的原因。
|
||||
|
||||
一句话总结:伊甸区存放了所有新创建的对象,当它的可用空间被耗尽,第一次垃圾回收就会被触发。
|
||||
|
||||
![填充伊甸区][7]
|
||||
|
||||
Minor GC:在该垃圾回收过程中,所有存活和死亡的对象都会被做上标记。其中,存活对象会被移动到 S0 幸存者区。当所有存活对象都被移动到了 S0,未被引用的对象就会被删除。
|
||||
|
||||
![拷贝被引用的对象][8]
|
||||
|
||||
S0 中的对象年龄为 1,因为它们挺过了一次 Minor GC。此时,伊甸区和 S1 都是空的。
|
||||
|
||||
每当完成清理后,伊甸区就会再次接受新的存活对象。随着时间的推移,伊甸区和 S0 中的某些对象被宣判死亡(不再被引用),并且伊甸区的可用空间也再次耗尽(填满了),那么 Minor GC 又将再次被触发。
|
||||
|
||||
![对象年龄增长][9]
|
||||
|
||||
这一次,伊甸区和 S0 中的死亡和存活的对象会被做上标记。其中,伊甸区的存活对象会被移动到 S1,并且年龄增加至 1。S0 中的存活对象也会被移动到 S1,并且年龄增加至 2(因为它们挺过了两次 Minor GC)。此时,伊甸区和 S0 又是空的了。每次 Minor GC 之后,伊甸区和两个幸存者区中的一个都会是空的。
|
||||
|
||||
新对象总是在伊甸区被创建,周而复始。当下一次垃圾回收发生时,伊甸区和 S1 都会被清理,它们中的存活对象会被移动到 S0 区。每次 Minor GC 之后,这两个幸存者区(S0 和 S1)就会交换一次。
|
||||
|
||||
![额外年龄增长][10]
|
||||
|
||||
这个过程会一直进行下去,直到某个存活对象的年龄达到了某个阈值,然后它就会被移动到一个叫做“老年代”的地方,这是通过一个叫做“晋升”的过程来完成的。
|
||||
|
||||
使用 `-Xmn` 选项可以设置年轻代的大小。
|
||||
|
||||
### 老年代
|
||||
|
||||
这个区域存放着那些挺过了许多次 Minor GC,并且达到了某个年龄阈值的对象。
|
||||
|
||||
![晋升][11]
|
||||
|
||||
在上面这个示例图表中,晋升的年龄阈值为 8。在老年代发生的垃圾回收被称为 “Major GC”。
|
||||
|
||||
使用 `-Xms` 和 `-Xmx` 选项可以分别设置堆内存大小的初始值和最大值。(LCTT 译注:结合上面的 `-Xmn` 选项,就可以间接设置老年代的大小了。)
|
||||
|
||||
### 永久代
|
||||
|
||||
永久代存放着一些元数据,它们与应用程序、Java 标准环境以及 JVM 自用的库类及其方法相关。JVM 会在运行时,用到了什么类和方法,就会填充相应的数据。当 JVM 发现有未使用的类,就会卸载或是回收它们,从而为正在使用的类腾出空间。
|
||||
|
||||
使用 `-XX:PermGen` 和 `-XX:MaxPerGen` 选项可以分别设置永久代大小的初始值和最大值。
|
||||
|
||||
#### 元空间
|
||||
|
||||
Java 8 引入了元空间,并用它替换了永久代。这么做的好处是自动调整大小,避免了 <ruby>内存不足<rt>OutOfMemory</rt></ruby>(OOM)错误。
|
||||
|
||||
### 总结
|
||||
|
||||
本文讨论了各种不同的 JVM 内存“代”,以及它们是如何在分代垃圾回收算法中起作用的。对于程序员来说,掌握 Java 的内存管理机制并不是必须的,但它能够帮助你更好地理解 JVM 处理程序中的变量和类实例的方式。这种理解使你能够规划和排除代码故障,并理解特定平台固有的潜在限制。
|
||||
|
||||
正文配图来自:Jayashree Huttanagoudar,CC BY-SA 4.0
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://opensource.com/article/22/6/garbage-collection-java-virtual-machine
|
||||
|
||||
作者:[Jayashree Huttanagoudar][a]
|
||||
选题:[lkxed][b]
|
||||
译者:[lkxed](https://github.com/lkxed)
|
||||
校对:[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译,[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
||||
[a]: https://opensource.com/users/jayashree-huttanagoudar
|
||||
[b]: https://github.com/lkxed
|
||||
[1]: https://opensource.com/sites/default/files/lead-images/java-coffee-beans.jpg
|
||||
[2]: https://opensource.com/sites/default/files/2022-06/1Marking.png
|
||||
[3]: https://opensource.com/sites/default/files/2022-06/2NormalDeletion.png
|
||||
[4]: https://opensource.com/sites/default/files/2022-06/3DeletionwithCompacting.png
|
||||
[5]: https://opensource.com/sites/default/files/2022-06/4Hotspot.png
|
||||
[6]: https://opensource.com/sites/default/files/2022-06/5ObjAllocation.png
|
||||
[7]: https://opensource.com/sites/default/files/2022-06/6FillingEden.png
|
||||
[8]: https://opensource.com/sites/default/files/2022-06/7CopyingRefdObjs.png
|
||||
[9]: https://opensource.com/sites/default/files/2022-06/8ObjAging.png
|
||||
[10]: https://opensource.com/sites/default/files/2022-06/9AddlAging.png
|
||||
[11]: https://opensource.com/sites/default/files/2022-06/10Promotion.png
|
Loading…
Reference in New Issue
Block a user