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

Merge remote-tracking branch 'LCTT/master'

Browse Source
This commit is contained in:
Xingyu Wang 2020-04-28 15:01:37 +08:00
commit cc496c213e
10 changed files with 908 additions and 104 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

54
translated/tech/20200422 Things You Should Know About Ubuntu 20.04.md → published/20200422 Things You Should Know About Ubuntu 20.04.md
View File

@ -1,8 +1,8 @@
[#]: collector: (lujun9972)
[#]: translator: (geekpi)
[#]: reviewer: ( )
[#]: publisher: ( )
[#]: url: ( )
[#]: reviewer: (wxy)
[#]: publisher: (wxy)
[#]: url: (https://linux.cn/article-12158-1.html)
[#]: subject: (Things You Should Know About Ubuntu 20.04)
[#]: via: (https://itsfoss.com/ubuntu-20-04-faq/)
[#]: author: (Abhishek Prakash https://itsfoss.com/author/abhishek/)
@ -10,13 +10,11 @@
关于 Ubuntu 20.04 你应该了解的事情
======
[Ubuntu 20.04][1] 即将发布，你可能对升级、安装等有一些问题和疑问。
[Ubuntu 20.04][1] 已经发布，你可能对升级、安装等有一些问题和疑问。
我在各种社交媒体渠道上主持了一些问答环节，回答像你这样的读者的疑虑。
我在各种社交媒体渠道上主持了一些问答环节，回答像你这样的读者的疑虑。我将列出这些关于 Ubuntu 20.04 的常见问题，并给出答案。我希望它能帮助你消除你的疑虑。如果你仍有问题，请随时在下面的评论栏提问。
我将列出这些关于Ubuntu 20.04的常见问题，并给出答案。我希望它能帮助你消除你的疑虑。如果你仍有问题，请随时在下面的评论栏提问。
### Ubuntu 20.04： 已回复的问题
### Ubuntu 20.04：已回复的问题
![][2]
@ -28,25 +26,25 @@ Ubuntu 20.04 LTS 于 2020 年 4 月 23 日发布。所有变种，如 Kubuntu、
#### Ubuntu 20.04 的系统要求是什么？
对于默认的 GNOME 版本，应至少具有 4GB 的内存、2 GHz 双核处理器和至少 25GB 的磁盘空间。
对于默认的 GNOME 版本，应至少具有 4GB 的内存、2GHz 双核处理器和至少 25GB 的磁盘空间。
其他 [Ubuntu 变种][3]可能有不同的系统要求。
#### 我可以在 32 位系统上使用 Ubuntu 20.04 吗？
完全不行。你不能在 32 位系统上使用 Ubuntu 20.04。即使你使用的是 32 位 Ubuntu 18.04，也不能升级到 Ubuntu 20.04。过去几年有 32 位的系统 ISO。
完全不行。你不能在 32 位系统上使用 Ubuntu 20.04。即使你使用的是 32 位 Ubuntu 18.04，也不能升级到 Ubuntu 20.04。32 位的系统 ISO 是以前用的。
![Error while upgrading 32-bit Ubuntu 18.04 to Ubuntu 20.04][4]
#### 我可以在Ubuntu 20.04上使用 Wine 吗？
#### 我可以在 Ubuntu 20.04 上使用 Wine 吗？
是的，你仍然可以在 Ubuntu 20.04 上使用 Wine，因为仍然有 32 位库，来用于 Wine 和 [Steam Play][5] 所需的软件包。
是的，你仍然可以在 Ubuntu 20.04 上使用 Wine，因为仍然用于 Wine 和 [Steam Play][5] 软件包所需的 32 位库。
#### 我需要购买 Ubuntu 20.04 或许可证？
不，Ubuntu 是完全免费使用的。你不必像在 Windows 中那样购买许可证密钥或激活 Ubuntu。
不，Ubuntu 完全可以免费使用。你不必像在 Windows 中那样购买许可证密钥或激活 Ubuntu。
Ubuntu 的下载页会请求你捐赠一些资金，如果你想捐赠一些钱来帮助开发这个系统，这完全取决于你。
Ubuntu 的下载页会请求你捐赠一些资金，如果你想为开发这个强大的操作系统捐钱，由你自己决定。
#### GNOME 版本是什么？
@ -54,21 +52,23 @@ Ubuntu 20.04 有 GNOME 3.36。
#### Ubuntu 20.04 的性能是否优于 Ubuntu 18.04？
是的，在几个方面。Ubuntu 20.04 安装速度更快，甚至加速更快。我在 4:40 的视频中展示了性能比较。
是的，在几个方面。Ubuntu 20.04 系统速度更快，甚至超快。我在下面这个视频的 4:40 处展示了性能对比。
在 GNOME 3.36 中，滚动、窗口动画和其他 UI 元素更加流畅，并提供了更流畅的体验。
- [video](https://img.linux.net.cn/static/video/Top%207%20Best%20Features%20You%27ll%20Love%20in%20Ubuntu%2020.04-lpq8pm_xkSE.mp4)
在 GNOME 3.36 中，滚动、窗口动画和其他 UI 元素更加流畅，提供了更流畅的体验。
#### Ubuntu 20.04 将支持多长时间？
它是一个长期支持 （LTS） 版本，与任何 LTS 版本一样，它将在五年内得到支持。这意味着 Ubuntu 20.04 将在 2025 年 4 月之前获得安全和维护更新。
它是一个长期支持（LTS）版本，与任何 LTS 版本一样，它将在五年内得到支持。这意味着 Ubuntu 20.04 将在 2025 年 4 月之前获得安全和维护更新。
#### 升级到 Ubuntu 20.04 时，是否会丢失数据？
你可以从 Ubuntu 19.10 或 Ubuntu 18.04 升级到 Ubuntu 20.04。你无需创建 live USB 并从中安装。你所需要的是一个良好的互联网连接，来下载约1.5GB 的数据。
你可以从 Ubuntu 19.10 或 Ubuntu 18.04 升级到 Ubuntu 20.04。你无需创建 live USB 并从中安装。你所需要的是一个良好的互联网连接，来下载约 1.5GB 的数据。
从现有系统升级不会破坏你的文件。你应该会有所有文件，并且大多数现有软件应具有相同的版本或升级后的版本。
从现有系统升级不会破坏你的文件。你应该会留有所有文件，并且大多数现有软件应具有相同的版本或升级后的版本。
如果你使用了某些第三方工具或[其他 PPA][6]，升级过程将禁用它们。如果 Ubuntu 20.04 适合这些其他存储库，那么可以再次启用它们。
如果你使用了某些第三方工具或[其他 PPA][6]，升级过程将禁用它们。如果 Ubuntu 20.04 可以使用这些其他存储库，那么可以再次启用它们。
升级大约需要一个小时，重启后，你将登录到新版本。
@ -78,21 +78,21 @@ Ubuntu 20.04 有 GNOME 3.36。
![][7]
如果你正在使用 Ubuntu 19.10 并有正确的更新设置（如前面部分所述），那么应在 Ubuntu 18.04 后的几天内通知你升级到 Ubuntu 20.04。
如果你正在使用 Ubuntu 19.10 并有正确的更新设置（如前面部分所述），那么应在发布后的几天内通知你升级到 Ubuntu 20.04。
对于 Ubuntu 18.04 用户，可能需要几周时间才能正式通知他们 Ubuntu 18.04 可用。可能，你可能会在第一个点版本 Ubuntu 20.04.1 后获得提示。
对于 Ubuntu 18.04 用户，可能需要几周时间才能正式通知他们 Ubuntu 20.04 可用。可能，你可能会在第一个点版本 Ubuntu 20.04.1 后获得提示。
#### 如果我升级到 Ubuntu 20.04，我可以降级到 19.10 或 18.04 吗？
不行。虽然升级到新版本很容易，但无法选择降级。 如果你想回到 Ubuntu 18.04，你将重新[安装 Ubuntu18.04][8]。
不行。虽然升级到新版本很容易，但无法选择降级。如果你想回到 Ubuntu 18.04，你需要重新[安装 Ubuntu 18.04][8]。
#### 我使用的是 Ubuntu 18.04 LTS。我应该升级到 Ubuntu 20.04 LTS 吗？
这取决于你。如果你对 Ubuntu 20.04 中的新功能印象深刻，并希望上手尝试，那么你应该升级。
如果你想要一个更稳定的系统，我建议等待第一个点版本 Ubuntu 20.04.1，新版本将有 bug 修复。20.04.1 通常在 Ubuntu 20.04 发布后大约两个月到来。
如果你想要一个更稳定的系统，我建议等待第一个点版本 Ubuntu 20.04.1，新版本会有 bug 修复。20.04.1 通常在 Ubuntu 20.04 发布后大约两个月到来。
其他情况下，我建议尽早升级到 Ubuntu 20.04。Ubuntu 20.04 具有更新的内核、性能改进，尤其是仓库中有更新版本的软件。
无论是那种情况，我都建议你或早或晚升级到 Ubuntu 20.04。Ubuntu 20.04 具有更新的内核、性能改进，尤其是仓库中有更新版本的软件。
在外部磁盘上进行备份，并且有良好的互联网连接，升级不应成为问题。
@ -113,13 +113,13 @@ via: https://itsfoss.com/ubuntu-20-04-faq/
作者：[Abhishek Prakash][a]
选题：[lujun9972][b]
译者：[geekpi](https://github.com/geekpi)
校对：[校对者ID](https://github.com/校对者ID)
校对：[wxy](https://github.com/wxy)
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
[a]: https://itsfoss.com/author/abhishek/
[b]: https://github.com/lujun9972
[1]: https://itsfoss.com/ubuntu-20-04-release-features/
[1]: https://linux.cn/article-12142-1.html
[2]: https://i1.wp.com/itsfoss.com/wp-content/uploads/2020/04/ubuntu_20_04_faq.jpg?ssl=1
[3]: https://itsfoss.com/which-ubuntu-install/
[4]: https://i0.wp.com/itsfoss.com/wp-content/uploads/2020/04/ubuntu-32-bit.jpg?ssl=1

81
sources/talk/20200427 Comparing subscription, pay-per-bug, and consulting software business models.md Normal file
View File

@ -0,0 +1,81 @@
[#]: collector: (lujun9972)
[#]: translator: ( )
[#]: reviewer: ( )
[#]: publisher: ( )
[#]: url: ( )
[#]: subject: (Comparing subscription, pay-per-bug, and consulting software business models)
[#]: via: (https://opensource.com/article/20/4/open-source-business)
[#]: author: (Jos Poortvliet https://opensource.com/users/jospoortvliet)
Comparing subscription, pay-per-bug, and consulting software business models
======
Learn how NextCloud achieves business revenue that is one-third
consulting and two-thirds subscription.
![A chair in a field.][1]
At FOSS Backstage this year, I hosted a discussion on open source models and shared why I think subscriptions are a great way to support open source products.
### Picking a business model
The company I co-founded, Nextcloud, only offers its services to customers on a (per user) subscription model. Some customers ask us during the sales conversation why they cannot just get access to our engineers on an hourly basis as they get from third party consultants: pay for the bug fix or support case, and be done?
When we discussed how to build our new company in 2016 during our very first "[hackweek][2]," our business model was an important conversation. The team discussed different approaches, and we decided to go for a subscription model. Such a model felt more in line with our mission and principles to [create a great product and run a trustworthy company.][3]
Why? While hourly rates seem like an easy way to get a quick fix for a problem, getting paid for fixing issues creates an incentive to create more buggy software, which of course, was not how we want to run our business.
Let's look a bit deeper at the choices.
### Subscription
As a customer, you want the most reliable software. And when (not if, when) things go wrong, you want them fixed as quickly as possible. Our company offers customers a subscription to our services. Such a subscription includes direct and unlimited access to our engineers the moment you run into a problem. These two points are very important. It means that a customer has the certainty of having the very best resources at their fingertips at the moment they need them, and as much as they need them, in a way that only the original software vendor can deliver.
For that, they pay a fee that scales with the number of users.
### Pay-per-bug
What if, instead, you could pay per issue fixed? In a way, this choice is similar to insurance. Indeed, when you need cold medicine once a year, the cost of a health insurance policy with a monthly premium seems prohibitive. But when a car accident crushes your spine and your medical costs skyrocket, not having to sell your house makes up for that premium and then some.
There is also the bigger picture: The incentives potentially created by a pay-per-bug model. It is a simple, albeit cynical calculation: If we got paid per bug we fix for customers, leaving more bugs in our product would increase our income. Now we're not saying every company offering product consulting by the hour is extorting their customers, merely that this backward incentive exists, even when most moral businesses would not give in to it.
Conversely, now that we offer insurance, we lower our support costs by building a better product, just like art insurance providers do what they can to ensure the art kept at their customers' exhibition is secure to keep their costs low. Our support team deeply cares about how our customers use our product: a better setup and good security practices not only make happier customers; it saves them time.
Or, in other words, it helps maximize the ROI or TEI the customer gains from deploying Nextcloud.
That is what we'd call a win-win and a business model an open source company can be proud of.
### Consulting
Now I discuss this business model regularly with others, and I invariably get told: "You might be right, but most of my customers only want to pay for the bugs we fix, or for features. Consulting is our main source of income! And I have no illusions about changing that."
Yes, that's an issue. We open source folk honestly have a sales and marketing issue. And yes, you might think that, as a marketing guy, I just see everything as a nail I can hit with my communications hammer. But really, communication is core to the issue—how you communicate your value—which, in turn, requires you to be aware of your value.
Recently, I had some challenging discussions with users on our forums who were upset that our engineers had not fixed their issues quickly enough. These users were clearly business users, and giving free support on GitHub obviously isn't exactly a great advertisement for the need for a subscription. So some abuse was thrown our way, and I took the hit. When complaining about it all to a fellow entrepreneurial friend of mine, he remarked: "Isn't that good news? They were frustrated and angry because clearly, you have something to offer, they need it, and are annoyed that they are forced to pay you for it. A good place to be in if you want to sell something!" Right he was, of course.
The lesson I want to share with this anecdote is: You have something to offer. Your current customers will certainly be upset if you tell them that, going forward, they can only get your services under a subscription. But the angrier they are, the more you know they _need_ you, and you should persist!
But moving to subscription from consulting requires a great deal of discipline, including saying "no" often. We have hard, internal rules, and one of these is that sales can only sell consulting valued at up to 50% of the subscription value, and only for deals greater than $10,000.
But it has worked. The breakdown of our business revenue is now about one-third consulting and two-thirds subscription. Engineering hours for consulting work are not the limiting factor for expanding our customer base; sales and sales engineering is. We doubled our order intake last year and plan to do the same this year.
### Bottomline: Sustainability
For us, a better product and more sustainable business follows from the subscription model. It also benefits software engineers, who prefer to build a better product and spend less time on debugging issues with customers. A pay-by-the-hour model, with all the time tracking and incentive to keep customers dependent, does not work for us.
What has your experience been? Tell us in the comments.
--------------------------------------------------------------------------------
via: https://opensource.com/article/20/4/open-source-business
作者：[Jos Poortvliet][a]
选题：[lujun9972][b]
译者：[译者ID](https://github.com/译者ID)
校对：[校对者ID](https://github.com/校对者ID)
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
[a]: https://opensource.com/users/jospoortvliet
[b]: https://github.com/lujun9972
[1]: https://opensource.com/sites/default/files/styles/image-full-size/public/lead-images/BIZ_WorkInPublic_4618517_1110_CS_A.png?itok=RwVrWArk (A chair in a field.)
[2]: https://nextcloud.com/blog/invitation-to-our-hackweek-in-stuttgart/
[3]: https://nextcloud.com/blog/the-nextcloud-mission-and-principles/

85
sources/talk/20200427 DevOps vs. Agile- Do they have anything in common.md Normal file
View File

@ -0,0 +1,85 @@
[#]: collector: (lujun9972)
[#]: translator: ( )
[#]: reviewer: ( )
[#]: publisher: ( )
[#]: url: ( )
[#]: subject: (DevOps vs. Agile: Do they have anything in common?)
[#]: via: (https://opensource.com/article/20/4/devops-vs-agile-common)
[#]: author: (Taz Brown https://opensource.com/users/heronthecli)
DevOps vs. Agile: Do they have anything in common?
======
Agile and DevOps have many differences, yet they both seek to address
complexity, improve quality, and innovate around software design.
![Women in tech boardroom][1]
The topic of DevOps vs. Agile is almost like debating iPhone vs. Android—everyone has an opinion, and emotions can become heated, especially if people disagree.
After writing _[DevOps v. Agile: What's the difference?][2]_ and reading the comments on the article, I wanted to add some more thoughts—including how some of my thinking has changed on the topic.
My perspective comes from where I am now but also where I have been. I used to be a systems administrator and infrastructure engineer, and now I am a senior scrum master with a major utility company in Missouri. (I actually was a scrum master before I was an admin or engineer, but I digress.)
My team consists of six frontend software engineers and IT programmer analysts, a business analyst, two product owners, and me. Recently, we learned that management wants our team to become a [DevSecOps][3] team, so our core scrum team is working with a DevSecOps team that is helping us make the transition. No one is naive to the fact that this will not be easy, but the DevSecOps team's experience gives us confidence that we can succeed.
Our team's manager recently hired a senior software engineer who will drive the DevSecOps goal. As a scrum master, I will continue to focus on continuous improvement. The team is fairly young, so they don't have expansive work experience, but they are smart and driven, and there is much room for greatness. In addition, our entire organization is going through an Agile transformation, so most people are new to all things Agile, including the [Agile Manifesto][4] and the [Five Scrum Values][5].
![Spray paint on a container][6]
Kyle Glenn on Unsplash
### Agile, Scrum, DevOps, and more
There is a clear relationship between DevOps and Agile. Agile is the methodology, Scrum is the framework, and DevOps falls under the agile [umbrella][7] along with kanban, lean, large-scale Scrum, Extreme Programming, Crystal, and more. For example, our Scrum team is an Agile team that will operate as a DevSecOps team.
Neither DevOps nor Agile is about the tools. Rather, both are about the [mindset and culture][8]. When it is done right, teams think and act differently and achieve greater results, including faster software delivery, continuous integration (CI), continuous delivery (CD), continuous improvement, working software, faster solutions, more collaboration, and fewer silos. Additional results are seen in quality testing, better automation, and improved systems, processes, and practices.
#### Common concepts
Some of the Agile concepts they have in common are associated with the Agile Manifesto; the most familiar of the 12 principles are the first four:
* Individual and interactions over processes and tools
* Working software over comprehensive documentation
* Customer collaboration over contract negotiations
* Responding to change over following a plan
Some of the DevOps concepts they have in common are the CI/CD pipeline, optimizing software delivery and quality, a culture of innovation, service-level objectives and indicators (SLOs and SLIs), collaboration across teams, and automation.
#### DevOps and Agile benefits
DevOps speeds up things between developers and operations. Furthermore, even though DevOps isn't about the tools, the fact that the dev and ops teams use the same tech stack creates a shared language and empathy between the two. Our Scrum team uses Jira to track all bugs, enhancements, and team performance. Common DevOps tools are Jenkins, AWS, SonarQube, GitHub, Splunk, and Ansible. While the tools differ from team to team, the mindset and culture should be common across all.
DevOps also creates less division between dev and ops and a sense of understanding of what it's like to walk in each other's shoes because now they function as one.
Agile teams continuously deliver often and fast, adapting incrementally along the way. Working in two-week sprints appears to be the sweet spot for most software- or product-delivery teams. Agile teams may utilize DevOps principles in their work (e.g., implementing a CI/CD pipeline), and dev teams that work with ops are likely to work in the same two-week increments.
DevOps traditionally leads to continuous deployment, delivery, and integration. Teamwork is integrated; problems and failures are jointly owned by development, operations, and other entities, such as quality assurance (QA), testing, automation, etc.
### Summing up
I believe that Agile and DevOps breathe the same air, with many concepts and theories crossing between them.
While I have no doubts that there will be counter opinions and even some sharply worded disagreements with my opinions, I think we would all agree that Agile and DevOps seek to address complexity, improve quality, and innovate around software design.
--------------------------------------------------------------------------------
via: https://opensource.com/article/20/4/devops-vs-agile-common
作者：[Taz Brown][a]
选题：[lujun9972][b]
译者：[译者ID](https://github.com/译者ID)
校对：[校对者ID](https://github.com/校对者ID)
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
[a]: https://opensource.com/users/heronthecli
[b]: https://github.com/lujun9972
[1]: https://opensource.com/sites/default/files/styles/image-full-size/public/lead-images/christina-wocintechchat-com-rg1y72ekw6o-unsplash_1.jpg?itok=MoIv8HlK (Women in tech boardroom)
[2]: https://opensource.com/article/20/2/devops-vs-agile
[3]: https://opensource.com/article/19/1/what-devsecops
[4]: https://agilemanifesto.org/
[5]: https://www.scrumalliance.org/about-scrum/values
[6]: https://opensource.com/sites/default/files/uploads/roomtogrow_kyleglenn.jpg (Spray paint on a container)
[7]: https://opensource.com/article/20/4/kanban-devops
[8]: https://opensource.com/article/19/5/values-devops-mindset

2
sources/tech/20200317 Create Stunning Pixel Art With Free and Open Source Editor Pixelorama.md
View File

@ -1,5 +1,5 @@
[#]: collector: (lujun9972)
[#]: translator: ( )
[#]: translator: (geekpi)
[#]: reviewer: ( )
[#]: publisher: ( )
[#]: url: ( )

76
sources/tech/20200425 What Happened to IPv5- Why there is IPv4, IPv6 but no IPv5.md
View File

@ -1,76 +0,0 @@
[#]: collector: (lujun9972)
[#]: translator: (geekpi)
[#]: reviewer: ( )
[#]: publisher: ( )
[#]: url: ( )
[#]: subject: (What Happened to IPv5? Why there is IPv4, IPv6 but no IPv5?)
[#]: via: (https://itsfoss.com/what-happened-to-ipv5/)
[#]: author: (John Paul https://itsfoss.com/author/john/)
What Happened to IPv5? Why there is IPv4, IPv6 but no IPv5?
======
If you have spent any amount of time in the world of the internet, you should have heard about the IPv4 and IPv6 protocols that our computers use every day.
One question that you might be asking is: Why there is no IPv5? Why IPv6 came after IPv4 and not IPv5? Was there ever a IPv5 and if yes, whatever happened to IPv5?
The answer is yes, there was an IPv5…sort of. Let me quickly explain a few things around it.
### The early history of the internet
![ARPA Logical Map in 1977 | Image courtesy: Wikipedia][1]
In the late 1960s, the US Department of Defense’s [Advanced Research Projects Agency][2] (ARPA) started a [project][3] to link computers across the country. The initial goal was to create a networked system of all of the ARPA-funded computers across the country.
Since this was the first time a network of this scale was put together, they were also creating the technology and hardware as they went. One of the first things they worked was an internet protocol (IP) named [Transmission Control Protocol][4] (TCP). This protocol “reliable, ordered, and error-checked delivery of a stream of octets (bytes) between applications running on hosts communicating via an IP network”. Basically, it made sure data got where it needed to go safely.
Originally, TCP was designed to be [“a host-level, end-to-end protocol and a packaging and routing protocol”][5]. However, they realized that they needed to split the protocol to make it more manageable. It was decided that IP would handle packaging and routing.
By this time TCP had gone through three versions, so the new protocol became known as IPv4.
### The birth of IPv5
IPv5 started life under a different name: Internet Stream Protocol (or ST). It was created to experiment with streaming voice and video [“by Apple, NeXT, and Sun Microsystems”][6].
This new protocol was capable of “transferring data packets on specific frequencies while maintaining communication”.
### So what happened to IPv5?
![][7]
IPv5 was never accepted as an official internet protocol. This was mainly due to the 32-bit limitation.
IPV5 used the same addressing system as IPv4. Each address was made up of four sets of numbers between 0 and 255. This limited the number of possible addresses to [4.3 billion][6].
In the early 1970s, that might have seemed like more than the world would ever need. However, the explosive growth of the Internet proved that idea wrong. In 2011, the world officially ran out of the IPv4 addresses.
In the 1990s, a new project was started to work on the next generation of internet protocol (IPng). This led to the 128-bit IPv6. An IPv6 address contains a [“series of eight 4-character hexadecimal numbers”][6] that can contain numbers from 0 to 9 and letters from A to F. Unlike IPv4, IPv6 had trillions of possible addresses, so we should be safe for a while.
Meanwhile, IPv5 laid the groundwork for the voice-over-IP technology that we use to communicate all over the world today. **So, I guess in some small way, you could say that IPv5 still survives to this day**.
I hope you liked this anecdote about internet history. You may read some other [trivia article about Linux and tech in general][8].
If you found this article interesting, please take a minute to share it on social media, Hacker News or [Reddit][9].
--------------------------------------------------------------------------------
via: https://itsfoss.com/what-happened-to-ipv5/
作者：[John Paul][a]
选题：[lujun9972][b]
译者：[译者ID](https://github.com/译者ID)
校对：[校对者ID](https://github.com/校对者ID)
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
[a]: https://itsfoss.com/author/john/
[b]: https://github.com/lujun9972
[1]: https://i1.wp.com/itsfoss.com/wp-content/uploads/2020/04/Arpa_internet.png?fit=800%2C573&ssl=1
[2]: https://en.wikipedia.org/wiki/DARPA
[3]: https://en.wikipedia.org/wiki/ARPANET
[4]: https://en.wikipedia.org/wiki/Transmission_Control_Protocol
[5]: https://fcw.com/articles/2006/07/31/what-ever-happened-to-ipv5.aspx
[6]: https://www.lifewire.com/what-happened-to-ipv5-3971327
[7]: https://i0.wp.com/itsfoss.com/wp-content/uploads/2020/04/what-happened-to-ipv5.png?ssl=1
[8]: https://itsfoss.com/category/story/
[9]: https://reddit.com/r/linuxusersgroup

175
sources/tech/20200426 6 tips for securing your WordPress website.md Normal file
View File

@ -0,0 +1,175 @@
[#]: collector: (lujun9972)
[#]: translator: ( )
[#]: reviewer: ( )
[#]: publisher: ( )
[#]: url: ( )
[#]: subject: (6 tips for securing your WordPress website)
[#]: via: (https://opensource.com/article/20/4/wordpress-security)
[#]: author: (Lucy Carney https://opensource.com/users/lucy-carney)
6 tips for securing your WordPress website
======
Even beginners can—and should—take these steps to protect their
WordPress sites against cyberattacks.
![A lock on the side of a building][1]
Already powering over 30% of the internet, WordPress is the fastest-growing content management system (CMS) in the world—and it's not hard to see why. With tons of customization available through coding and plugins, top-notch SEO, and a supreme reputation for blogging, WordPress has certainly earned its popularity.
However, with popularity comes other, less appealing attention. WordPress is a common target for intruders, malware, and cyberattacks—in fact, WordPress accounted for around [90% of hacked CMS platforms][2] in 2019.
Whether you're a first-time WordPress user or an experienced developer, there are important steps you can take to protect your WordPress website. The following six key tips will get you started.
### 1\. Choose reliable hosting
Hosting is the unseen foundation of all websites—without it, you can't publish your site online. But hosting does much more than simply host your site. It's also responsible for site speed, performance, and security.
The first thing to do is to check if a host includes SSL security in its plans.
SSL is an essential security feature for all websites, whether you're running a small blog or a large online store. You'll need a more [advanced SSL certificate][3] if you're accepting payments, but for most sites, the basic free SSL should be fine.
Other security features to look out for include:
* Frequent, automatic offsite backups
* Malware and antivirus scanning and removal
* Distributed denial of service (DDoS) protection
* Real-time network monitoring
* Advanced firewall protection
In addition to these digital security features, it's worth thinking about your hosting provider's _physical_ security measures as well. These include limiting access to data centers with security guards, CCTV, and two-factor or biometric authentication.
### 2\. Use security plugins
One of the best—and easiest—ways of protecting your website's security is to install a security plugin, such as [Sucuri][4], which is an open source, GPLv2 licensed project. Security plugins are vitally important because they automate security, which means you can focus on running your site rather than committing all your time to fighting off online threats.
These plugins detect and block malicious attacks and alert you about any issues that require your attention. In short, they constantly work in the background to protect your site, meaning you don't have to stay awake 24/7 to fight off hackers, bugs, and other digital nasties.
A good security plugin will provide all the essential security features you need for free, but some advanced features require a paid subscription. For example, you'll need to pay if you want to unlock [Sucuri's website firewall][5]. Enabling a web application firewall (WAF) blocks common threats and adds an extra layer of security to your site, so it's a good idea to look for this feature when choosing a security plugin.
### 3\. Choose trustworthy plugins and themes
The joy of WordPress is that it is open source, so anyone and everyone can pitch in with themes and plugins that they've developed. This can also pose problems when it comes to picking a high-quality theme or plugin.
It serves to be cautious when picking a free theme or plugin, as some are poorly designed—or worse, may hide malicious code.
To avoid this, always source free themes and plugins from reputable sources, such as the WordPress library. Always read reviews and research the developer to see if they've built any other programs.
Outdated or poorly designed themes and plugins can leave "backdoors" open for attackers or bugs to get into your site, which is why it pays to be careful in your choices. However, you should also be wary of nulled or cracked themes. These are premium themes that have been compromised by hackers and are for sale illegally. You might buy a nulled theme believing that it's all above-board—only to have your site damaged by hidden malicious code.
To avoid nulled themes, don't get drawn in by discounted prices, and always stick to reputable stores, such as the official [WordPress directory][6]. If you're looking elsewhere, stick to large and trusted stores, such as [Themify][7], a theme and plugin store that has been running since 2010. Themify ensures all its WordPress themes pass the [Google Mobile-Friendly][8] test and are open source under the [GNU General Public License][9].
### 4\. Run regular updates
It's a fundamental WordPress rule: _always keep your site up to date._ However, it's a rule not everyone sticks to—in fact, only [43% of WordPress sites][10] are running the latest version.
The problem is that when your site becomes outdated, it becomes susceptible to glitches, bugs, intrusions, and crashes because it falls behind on security and performance fixes. Outdated sites can't fix bugs the same way as updated sites can, and attackers can tell which sites are outdated. This means they can search for the most vulnerable sites and attack accordingly.
This is why you should always run your site on the latest version of WordPress. And in order to keep your security at its strongest, you must update your plugins and themes as well as your core WordPress software.
If you choose a managed WordPress hosting plan, you might find that your provider will check and run updates for you—be clear whether your host offers software _and_ plugin updates. If not, you can install an open source plugin manager, such as the GPLv2-licensed [Easy Updates Manager plugin][11], as an alternative.
### 5\. Strengthen your logins
Aside from creating a secure WordPress website through carefully choosing your theme and installing security plugins, you also need to safeguard against unauthorized access through logins.
#### Password protection
The first and simplest way to strengthen your login security is to change your password—especially if you're using an [easily guessed phrase][12] such as "123456" or "qwerty."
Instead, try to use a long passphrase rather than a password, as they are harder to crack. The best way is to use a series of unrelated words strung together that you find easy to remember.
Here are some other tips:
* Never reuse passwords
* Don't include obvious words such as family members' names or your favorite football team
* Never share your login details with anyone
* Include capitals and numbers to add complexity to your passphrase
* Don't write down or store your login details anywhere
* Use a [password manager][13]
#### Change your login URL
It's a good idea to change your default login web address from the standard format: yourdomain.com/wp-admin. This is because hackers know this is the default URL, so you risk brute-force attacks by not changing it.
To avoid this, change the URL to something different. Use an open source plugin such as the GPLv2-licensed [WPS Hide Login][14] for safe, quick, and easy customization.
#### Apply two-factor authentication
For extra protection against unauthorized logins and brute-force attacks, you should add two-factor authentication. This means that even if someone _does_ get access to your login details, they'll need a code that's sent directly to your phone to gain access to your WordPress site's admin.
Adding two-factor authentication is pretty easy. Simply install yet another plugin—this time, search the WordPress Plugin Directory for "two-factor authentication," and select the plugin you want. One option is [Two Factor][15], a popular GPLv2 licensed project that has over 10,000 active installations.
#### Limit login attempts
WordPress tries to be helpful by letting you guess your login details as many times as you like. However, this is also helpful to hackers trying to gain unauthorized access to your WordPress site to release malicious code.
To combat brute-force attacks, install a plugin that limits login attempts and set how many guesses you want to allow.
### 6\. Disable file editing
This isn't such a beginner-friendly step, so don't attempt it unless you're a confident coder—and always back up your site first!
That said, disabling file editing _is_ an important measure if you're really serious about protecting your WordPress website. If you don't hide your files, it means anyone can edit your theme and plugin code straight from the admin area—which is dangerous if an intruder gets in.
To deny unauthorized access, go to your **wp-config.php** file and enter:
```
<Files wp-config.php>
order allow,deny
deny from all
</Files>
```
Or, to remove the theme and plugin editing options from your WordPress admin area completely, edit your **wp-config.php** file by adding:
```
`define( 'DISALLOW_FILE_EDIT', true );`
```
Once you've saved and reloaded the file, the plugin and theme editors will disappear from your menus within the WordPress admin area, stopping anyone from editing your theme or plugin code—including you**.** Should you need to restore access to your theme and plugin code, just delete the code you added to your **wp-config.php** file when you disabled editing.
Whether you block unauthorized access or totally disable file editing, it's important to take action to protect your site's code. Otherwise, it's easy for unwelcome visitors to edit your files and add new code. This means an attacker could use the editor to gather data from your WordPress site or even use your site to launch attacks on others.
For an easier way of hiding your files, you can use a security plugin that will do it for you, such as Sucuri.
### WordPress security recap
WordPress is an excellent open source platform that should be enjoyed by beginners and developers alike without the fear of becoming a victim of an attack. Sadly, these threats aren't going anywhere anytime soon, so it's vital to stay on top of your site's security.
Using the measures outlined above, you can create a stronger, more secure level of protection for your WordPress site and ensure a much more enjoyable experience for yourself.
Staying secure is an ongoing commitment rather than a one-time checklist, so be sure to revisit these steps regularly and stay alert when building and using your CMS.
--------------------------------------------------------------------------------
via: https://opensource.com/article/20/4/wordpress-security
作者：[Lucy Carney][a]
选题：[lujun9972][b]
译者：[译者ID](https://github.com/译者ID)
校对：[校对者ID](https://github.com/校对者ID)
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
[a]: https://opensource.com/users/lucy-carney
[b]: https://github.com/lujun9972
[1]: https://opensource.com/sites/default/files/styles/image-full-size/public/lead-images/BUSINESS_3reasons.png?itok=k6F3-BqA (A lock on the side of a building)
[2]: https://cyberforces.com/en/wordpress-most-hacked-cms
[3]: https://opensource.com/article/19/11/internet-security-tls-ssl-certificate-authority
[4]: https://wordpress.org/plugins/sucuri-scanner/
[5]: https://sucuri.net/website-firewall/
[6]: https://wordpress.org/themes/
[7]: https://themify.me/
[8]: https://developers.google.com/search/mobile-sites/
[9]: http://www.gnu.org/licenses/gpl.html
[10]: https://wordpress.org/about/stats/
[11]: https://wordpress.org/plugins/stops-core-theme-and-plugin-updates/
[12]: https://www.forbes.com/sites/kateoflahertyuk/2019/04/21/these-are-the-worlds-most-hacked-passwords-is-yours-on-the-list/#4f157c2f289c
[13]: https://opensource.com/article/16/12/password-managers
[14]: https://wordpress.org/plugins/wps-hide-login/
[15]: https://en-gb.wordpress.org/plugins/two-factor/

209
sources/tech/20200427 How to secure your Linux email services with SSL-TLS.md Normal file
View File

@ -0,0 +1,209 @@
[#]: collector: (lujun9972)
[#]: translator: ( )
[#]: reviewer: ( )
[#]: publisher: ( )
[#]: url: ( )
[#]: subject: (How to secure your Linux email services with SSL/TLS)
[#]: via: (https://opensource.com/article/20/4/securing-linux-email)
[#]: author: (Marc Skinner https://opensource.com/users/marc-skinner)
How to secure your Linux email services with SSL/TLS
======
Protect your Linux email services by understanding security
certificates.
![email or newsletters via inbox and browser][1]
Traditionally, email services send data in an unprotected way—whether you are sending emails via SMTP or receiving them via IMAP or POP, the defaults are in cleartext. With more online applications enforcing encryption and the general consensus to protect your data, it's best to secure your email services with a Secure Sockets Layer/Transport Layer Security (SSL/TLS) security certificate.
First, a quick review of email services and protocols. Email is sent via a service called Simple Mail Transport Protocol (SMTP) using TCP port 25. This protocol sends emails from server to server based on DNS mail exchanger (MX) record lookups. Once an email is on the email server, it is retrieved using one of two services: Internet Message Access Protocol (IMAP) using port TCP 143, or Post Office Protocol (POP3) using port TCP 110. All of these services, by default, send your email and authentication to/from these services in plain text—thus, it's very unprotected!
To protect the email data and authentication, these services have added a security feature in which they can utilize an SSL/TLS certificate to wrap the data flow and communication with encryption. How SSL/TLS encryption secures information is beyond the scope of this article, but [Bryant Son's internet security article][2] covers it in great detail. At a high level, SSL/TLS encryption is a public/private encryption algorithm.
By adding these security features into the services, they can listen on new TCP ports:
Service | Default TCP Port | SSL/TLS Port
---|---|---
SMTP | 25 | 587
IMAP | 143 | 993
POP3 | 110 | 995
### Generate SSL/TLS certificates
SSL/TLS certificates can be generated for free using tools like [OpenSSL][3], or they can be purchased for a range of prices from public certificate authorities (CAs). In the past, generating your own certificate was easy and worked in most cases, but with the increasing demand for better security, most email clients don't trust self-generated SSL/TLS certificates without a manual exception.
If your use case is private or for testing, then saving money with a self-generated certificate makes sense. But if you're rolling this out to a large group or have paying customers, then you're better served by purchasing a certificate from a public, trusted company that sells them.
In either case, the process to start requesting a new certificate is to use the OpenSSL tooling on your Linux system to create a certificate signing request (CSR):
```
`$ openssl req -new -newkey rsa:2048 -nodes -keyout mail.mydomain.key -out mail.mydomain.csr`
```
This command will create a new CSR and private key at the same time for the service you are trying to secure. The process will ask you a number of questions associated with the certificate: location details, server fully qualified domain name (FQDN), email contact information, etc. Once you have filled out the information, the key and CSR will be generated.
#### If you generate your own certificate
If you want to generate your own certificate, you must create your own [root CA][4] before issuing the CSR command above. You can create your own root CA with:
```
`$ openssl genrsa -des3 -out myCA.key 2048`
```
It will prompt you to add a passphrase. Please give it a secure passphrase and don't lose it—this is your private root CA key, and as the name states, it's the root of all trust in your certificates.
Next, generate the root CA certificate:
```
`$ openssl req -x509 -new -nodes -key myCA.key -sha256 -days 1825 -out myCA.pem`
```
After answering a few more questions, you will generate a root CA certificate with a five-year lifespan.
Using the CSR file from the steps above, you can request a new certificate to be generated and signed by the root CA you just created:
```
`$ openssl x509 -req -in mail.mydomain.csr -CA myCA.pem -CAkey myCA.key -CAcreateserial -out mail.mydomain.pem -days 1825 -sha256`
```
Enter your private root CA key passphrase to create and sign the certificate.
Now you have the two files needed to configure your email services for enhanced security: the private key file, **mail.mydomain.key**, and the public certificate file, **mail.mydomain.pem**.
#### If you purchase a certificate
If you purchase a certificate from a vendor, it will ask you to upload that CSR to its system, as it is used as the input to generate the SSL/TLS certificate. The certificate will be accessible as a file (such as **mail.mydomain.pem**). Many SSL vendors also require you to download an intermediate certificate. If this is the case, you must combine the two certificate files into one, so the email service can process them both in combination. You can combine your certificate with a third-party intermediate certificate with:
```
`$ cat mail.mydomain.pem gd_bundle-g2-g1.crt > mail.mydomain.pem`
```
Notice that the output's file extension is **.pem**, which stands for Privacy-Enhanced Mail.
Now you have the two files you need to configure your email services for enhanced security: the private key file, **mail.mydomain.key**, and the public combined certificate file, **mail.mydomain.pem**.
### Create a safe directory for your files
Whether you created your own key or bought one from a vendor, create a safe, root-owned directory for the two files you created above. An example workflow to create a safe play would be:
```
$ mkdir /etc/pki/tls
$ chown root:root /etc/pki/tls
$ chmod 700 /etc/pki/tls
```
Make sure to set the permissions on your files after you copy them into **/etc/pki/tls** with:
```
`$ chmod 600 /etc/pki/tls/*`
```
### Configure your SMTP and IMAP services
Next, configure both the SMTP and the IMAP services to use the new security certificates. The programs used in this example for SMTP and IMAP are **postfix** and **dovecot**.
Edit ***/_****etc****_/*****postfix/main.cf** in your preferred text editor. Add the following lines:
```
smtpd_use_tls = yes
smtpd_tls_cert_file = /etc/pki/tls/mail.mydomain.pem
smtpd_tls_key_file = /etc/pki/tls/mail.mydomain.key
```
### Customize your config
The following options allow you to disable/enable different ciphers, protocols, etc.:
```
smtpd_tls_eecdh_grade = strong
smtpd_tls_protocols= !SSLv2, !SSLv3, !TLSv1, !TLSv1.1
smtpd_tls_mandatory_protocols= !SSLv2, !SSLv3, !TLSv1, !TLSv1.1
smtpd_tls_mandatory_ciphers = high
smtpd_tls_security_level=may
smtpd_tls_ciphers = high
tls_preempt_cipherlist = yes
smtpd_tls_mandatory_exclude_ciphers = aNULL, MD5 , DES, ADH, RC4, PSD, SRP, 3DES, eNULL
smtpd_tls_exclude_ciphers = aNULL, MD5 , DES, ADH, RC4, PSD, SRP, 3DES, eNULL
smtp_tls_mandatory_protocols = !SSLv2, !SSLv3, !TLSv1, !TLSv1.1
smtp_tls_protocols = !SSLv2, !SSLv3, !TLSv1, !TLSv1.1
```
Edit **/etc/dovecot/dovecot.conf** by adding these three lines:
```
ssl = required
ssl_cert = </etc/pki/tls/mail.mydomain.pem
ssl_key = </etc/pki/tls/mail.mydomain.key
```
Add the following options to disable/enable different ciphers, protocols, and more (I'll leave understanding and considering these up to you):
```
ssl_cipher_list = EECDH+ECDSA+AESGCM:EECDH+aRSA+AESGCM:EECDH+ECDSA+SHA384:EECDH+ECDSA+SHA256:EECDH+aRSA+SHA384:EECDH+aRSA+SHA256:EECDH+aRSA+RC4:EECDH:EDH+aRSA:ALL:!aNULL:!eNULL:!LOW:!3DES:!MD5:!EXP:!PSK:!SRP:!DSS:!RC4:!SSLv2
ssl_prefer_server_ciphers = yes
ssl_protocols = !SSLv2 !SSLv3 !TLSv1 !TLSv1.1
ssl_min_protocol = TLSv1.2
```
### Set context for SELinux
If your Linux distribution has SELinux enabled, set the correct SELinux context for your new certificate files.
For Postfix SELinux:
```
`$ chcon -u system_u -t cert_t mail.mydomain.*`
```
For Dovecot SELinux:
```
`$ chcon -u system_u -t dovecot_cert_t mail.mydomain.*`
```
Restart both services and connect with your updated email client configurations. Some email clients will auto-detect the new port numbers; others will require you to update them.
### Test your setup
Quickly test from the command line with **openssl** and the **s_client** plugin:
```
$ openssl s_client -connect mail.mydomain.com:993
$ openssl s_client -starttls imap -connect mail.mydomain.com:143
$ openssl s_client -starttls smtp -connect mail.mydomain.com:587
```
These test commands will show a plethora of data about the connection, certificate, cipher, session, and protocol you're using. This is not only a good way to validate that the new configuration is working but also to confirm you're using the appropriate certificate and security settings you defined in the **postfix** or **dovecot** configuration files.
Stay secure!
--------------------------------------------------------------------------------
via: https://opensource.com/article/20/4/securing-linux-email
作者：[Marc Skinner][a]
选题：[lujun9972][b]
译者：[译者ID](https://github.com/译者ID)
校对：[校对者ID](https://github.com/校对者ID)
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
[a]: https://opensource.com/users/marc-skinner
[b]: https://github.com/lujun9972
[1]: https://opensource.com/sites/default/files/styles/image-full-size/public/lead-images/newsletter_email_mail_web_browser.jpg?itok=Lo91H9UH (email or newsletters via inbox and browser)
[2]: https://opensource.com/article/19/11/internet-security-tls-ssl-certificate-authority
[3]: https://www.openssl.org/
[4]: https://en.wikipedia.org/wiki/Root_certificate

154
sources/tech/20200428 Lubuntu 20.04 Review- Lightweight, Minimalistic, Polished.md Normal file
View File

@ -0,0 +1,154 @@
[#]: collector: (lujun9972)
[#]: translator: ( )
[#]: reviewer: ( )
[#]: publisher: ( )
[#]: url: ( )
[#]: subject: (Lubuntu 20.04 Review: Lightweight, Minimalistic, Polished)
[#]: via: (https://itsfoss.com/lubuntu-20-04-review/)
[#]: author: (Dimitrios Savvopoulos https://itsfoss.com/author/dimitrios/)
Lubuntu 20.04 Review: Lightweight, Minimalistic, Polished
======
_**Lubuntu 20.04 LTS is significantly different than its previous LTS version. It is aiming to give you a more polished experience rather than just focusing on older computer. Read more about it as I review Lubuntu 20.04.**_
### Lubuntu 20.04 Review: First LTS release with LXQt
I have been using Lubuntu 20.04 from a few days before the release. I usually dwell in Arch world with Manjaro and Cinnamon desktop so using Lubuntu was a pleasant change for me.
Here’s what I have noticed and felt about Lubuntu 20.04.
#### Bye bye LXDE, Hello LXQt!
For a long time, [Lubuntu][1] relied on [LXDE][2] to provide a lightweight Linux experience. It now uses LXQt desktop environment.
[LXDE][3] is based on GTK (the libraries used by GNOME) and more specifically on GTK+ 2 which is dated in 2020. Dissatisfied with GTK+ 3, LXDE developer Hong Jen Yee decided to port the entire desktop to Qt (the libraries used by KDE). LXDE, the Qt port of it, and the [Razor-qt][4] project were combined to form [LXQt][5]. Although today, LXDE and LXQt coexist as separate projects.
Since LXDE developer itself is focusing on LXQt, it makes no sense for Lubuntu to stick with a desktop environment that had its last stable release more than three years ago.
Lubuntu 18.04 is the last version of with [LXDE][3]. Fortunately it’s a long term support edition. It will be supported officially by Lubuntu team till 2021.
![][6]
#### Not exclusively for older machines
As the definition of “older machine” has changed in 2020 Lubuntu 18.04 is the last 32bit version. Nowadays even a 10 year old machine comes with at least 2 gigabytes of ram and a dual-core 64bit processor.
As per that, [Lubuntu Team will no longer provide minimum system requirements and will no longer primarily focus on older hardware][7]. Although LXQt is still a lightweight, classic yet polished and feature rich desktop environment.
The First Lubuntu release with LXQt was 18.10, giving the developers three standard releases to perfect the LXQt desktop before the Lubuntu 20.04 LTS release, which is a good development strategy.
#### Not the regular Ubiquity, Lubuntu 20.04 uses Calamares installer
![Lubuntu 20.04 Calamares Installer][8]
A fresh installation begins with the new [Calamares][9] installer, in place of the Ubiquity installer that other [official Ubuntu flavors][10] use.
The whole process is done in approximately 10 minutes, slightly faster than the previous Lubuntu releases.
As the .iso comes with the essential applications pre-installed you can get your system fully configured pretty fast too.
#### No upgrade from Lubuntu 18.04 to Lubuntu 20.04
Normally, you can [upgrade Ubuntu from one LTS to another LTS release][11]. But Lubuntu team advises not to upgrade from Lubuntu 18.04 to 20.04. They recommend a fresh install and rightly so.
Lubuntu 18.04 used LXDE desktop while 20.04 uses LXQt. Due to the extensive changes in the desktop environments, upgrading to 20.04 from 18.04 will result in a broken system.
#### **More KDE and Qt applications**
![][12]
Here are some of the applications that are available by default in this new release and as I can see, not all of them are lightweight and most of them are Qt-based.
Even the software center used is KDE’s Discover instead of Ubuntu’s GNOME software center.
* Ark – archive manager
* Bluedevil – bluetooth connector
* Discover Software Center – package management system
* FeatherPad – text editor
* FireFox – web browser
* K3b – CD/DVD burner
* Kcalc – calculator
* KDE partition manager – partition manager
* LibreOffice – Office suite (Qt interface version)
* LXimage-Qt – image viewer and screenshot tool
* Muon – package manager
* Noblenote – note taker
* PCManFM-Qt – File manager
* Qlipper – clipboard manager
* qPDFview – PDF viewer
* PulseAudio – audio controller
* Qtransmission – bittorrent client (Qt interface version)
* Quassel – IRC client
* ScreenGrab – Screenshot creator
* Skanlite – scanning
* Startup Disk Creator – USB boot disk maker
* Trojita – email client
* VLC – media player
* [MPV video player][13]
#### Testing Lubuntu 20.04 LTS
Boot times on the LXQt version of Lubuntu are under a minute, booting from an SSD though.
LXQt currently requires slightly more memory than the Gtk+ v2-based LXDE, but the alternative Gtk+ v3 toolkit would also have required more memory.
After a reboot the system runs approximately at a very low of 340 MB for the modern standards, 100 MB more than LXDE.
![htop running on Lubuntu 20.04][14]
LXQt is not only for users with an older hardware but also for those who are seeking a simple and classic experience at their new machine.
The desktop layout looks similar to KDE’s Plasma desktop, don’t you think?
![Lubuntu 20.04 Desktop][15]
There’s an application menu in the lower-left corner, a taskbar for pinned and active applications, and a system tray in the lower-right corner.
Lubuntu in its LXQt version can be easily customized and everything is in the menu under preferences, with most key items under LXQt Settings.
It is worth-mentioning that LXQt uses the popular [Openbox window manager][16] by default.
Like the last three releases, 20.04 LTS comes with a default dark theme Lubuntu Arc, but it is quick and easy to change it if it doesn’t suit your taste.
In daily use, Lubuntu 20.04 has proven to me completely trouble-free as every Ubuntu flavour in fact.
#### Conclusion
Lubuntu team has successfully made the transition to a modern, still lightweight and minimal desktop environment. LXDE looks like abandoned and it is a good thing to move away to an active project.
I hope that Lubuntu 20.04 makes you as much enthusiastic as I am, and if so don’t hesitate to let me know at the comments below. Stay tuned!
--------------------------------------------------------------------------------
via: https://itsfoss.com/lubuntu-20-04-review/
作者：[Dimitrios Savvopoulos][a]
选题：[lujun9972][b]
译者：[译者ID](https://github.com/译者ID)
校对：[校对者ID](https://github.com/校对者ID)
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
[a]: https://itsfoss.com/author/dimitrios/
[b]: https://github.com/lujun9972
[1]: https://lubuntu.me/
[2]: https://github.com/lxde
[3]: https://lxde.org/
[4]: https://web.archive.org/web/20160220061334/http://razor-qt.org/
[5]: https://lxqt.org/
[6]: https://i1.wp.com/itsfoss.com/wp-content/uploads/2020/04/Lubuntu-20-04-review.jpg?ssl=1
[7]: https://itsfoss.com/lubuntu-no-more-old-distro/
[8]: https://i2.wp.com/itsfoss.com/wp-content/uploads/2020/04/lubuntu-20-04-installer.jpg?ssl=1
[9]: https://calamares.io/
[10]: https://itsfoss.com/which-ubuntu-install/
[11]: https://itsfoss.com/upgrade-ubuntu-version/
[12]: https://i2.wp.com/itsfoss.com/wp-content/uploads/2020/04/Lubuntu-20.04.gif?ssl=1
[13]: https://itsfoss.com/mpv-video-player/
[14]: https://i2.wp.com/itsfoss.com/wp-content/uploads/2020/04/htop.jpg?fit=800%2C629&ssl=1
[15]: https://i2.wp.com/itsfoss.com/wp-content/uploads/2020/04/Lubuntu-20.04-desktop.jpg?fit=800%2C450&ssl=1
[16]: https://en.wikipedia.org/wiki/Openbox

100
sources/tech/20200428 Using Files and Folders on Desktop Screen in Ubuntu.md Normal file
View File

@ -0,0 +1,100 @@
[#]: collector: (lujun9972)
[#]: translator: ( )
[#]: reviewer: ( )
[#]: publisher: ( )
[#]: url: ( )
[#]: subject: (Using Files and Folders on Desktop Screen in Ubuntu)
[#]: via: (https://itsfoss.com/add-files-on-desktop-ubuntu/)
[#]: author: (Abhishek Prakash https://itsfoss.com/author/abhishek/)
Using Files and Folders on Desktop Screen in Ubuntu
======
_**This beginner tutorial discusses a few difficulties you may face while adding files and folders on the desktop screen on Ubuntu.**_
I know a few people who are habitual of putting all the important/frequently used files on the desktop screen for quick access.
![][1]
I am not a fan of a cluttered desktop screen but I can imagine that it might actually be helpful to some people.
For the past few releases, it has been difficult to add files on the desktop screen in Ubuntu’s default GNOME desktop. It’s not really Ubuntu’s fault.
The [GNOME][2] developers thinks that there is no place for icons and files on the desktop screen. There is no need of putting files on the desktop when you can easily search for it in the menu. And that’s part true.
This is why the newer version of [GNOME’s File Manager Nautilus][3] doesn’t support icons and files on the desktop very well.
That said, it’s not impossible to add files and folders on the desktop. Let me show you how you can still use it.
### Adding files and folders on the desktop screen in Ubuntu
![][4]
I am using Ubuntu 20.04 in this tutorial. The steps may or may not vary for other Ubuntu versions.
#### Add the files and folders to the “Desktop folder”
If you open the file manager, you should see an entry called Desktop in the left sidebar or in the folders list. This folder represents your desktop screen (in a way).
![Desktop folder can be used to add files to the desktop screen][5]
Anything you add to this folder will be reflected on the desktop screen.
![Anything added to the Desktop folder will be reflected on the desktop screen][6]
If you delete files from this ‘Desktop folder’, it will be removed from the desktop screen as well.
#### Drag and drop files to desktop screen doesn’t work
Now, if you try to drag and drop files from the file manager on the desktop, it won’t work. It’s not a bug, it’s a feature that irks a lot of people.
A workaround would be to open two instances of the file manager. Open Desktop folder in one of them and then drag and drop files to this folder and they will be added on the desktop.
I know that’s not ideal but you don’t have a lot of choices here.
#### You cannot use Ctrl+C and Ctrl+V to copy-paste on the desktop, use the right click menu
To add salt to injury, you cannot use Ctrl+V the famous keyboard shortcut to paste files on the desktop screen.
But you can still use the right click context menu and select Paste from there to put the copied files on the desktop. You can even create new folders this way.
![Right click menu can be used for copy-pasting files to desktop][7]
Does it make sense? Not to me but that’s how it is in Ubuntu 20.04.
#### You cannot delete files and folder using the Delete key, use the right click menu again
What’s worse is that you cannot use the delete key or shift delete key to remove files from the desktop screen. But you can still right click on the files or folders and select “Move to trash” to delete the file.
![Delete files from desktop using right click][8]
Alright, so now you know that at least there is a way to add files on the desktop with some restrictions. But it doesn’t end here unfortunately.
You cannot search for files with their names on the desktop screen. Normally, if you start typing ‘abc’, files starting with ‘abc’ are highlighted. You don’t get it here.
I don’t know why so many restrictions have been put on adding files on the desktop. Thankfully, I don’t use it a lot otherwise I have been way too frustrated.
If interested, you may read about [adding application shortcut on the desktop in Ubuntu][9] as well.
--------------------------------------------------------------------------------
via: https://itsfoss.com/add-files-on-desktop-ubuntu/
作者：[Abhishek Prakash][a]
选题：[lujun9972][b]
译者：[译者ID](https://github.com/译者ID)
校对：[校对者ID](https://github.com/校对者ID)
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
[a]: https://itsfoss.com/author/abhishek/
[b]: https://github.com/lujun9972
[1]: https://i0.wp.com/itsfoss.com/wp-content/uploads/2020/04/files-on-desktop-ubuntu.jpg?ssl=1
[2]: https://www.gnome.org/
[3]: https://wiki.gnome.org/Apps/Files
[4]: https://i2.wp.com/itsfoss.com/wp-content/uploads/2020/04/adding-files-desktop-ubuntu.png?ssl=1
[5]: https://i1.wp.com/itsfoss.com/wp-content/uploads/2020/04/desktop-folder-ubuntu.png?ssl=1
[6]: https://i0.wp.com/itsfoss.com/wp-content/uploads/2020/04/adding-files-desktop-screen-ubuntu.jpg?ssl=1
[7]: https://i1.wp.com/itsfoss.com/wp-content/uploads/2020/04/adding-new-files-ubuntu-desktop.jpg?ssl=1
[8]: https://i2.wp.com/itsfoss.com/wp-content/uploads/2020/04/delete-files-from-desktop-ubuntu.jpg?ssl=1
[9]: https://itsfoss.com/ubuntu-desktop-shortcut/

76
translated/tech/20200425 What Happened to IPv5- Why there is IPv4, IPv6 but no IPv5.md Normal file
View File

@ -0,0 +1,76 @@
[#]: collector: (lujun9972)
[#]: translator: (geekpi)
[#]: reviewer: ( )
[#]: publisher: ( )
[#]: url: ( )
[#]: subject: (What Happened to IPv5? Why there is IPv4, IPv6 but no IPv5?)
[#]: via: (https://itsfoss.com/what-happened-to-ipv5/)
[#]: author: (John Paul https://itsfoss.com/author/john/)
IPv5 发生了什么？为什么有 IPv4、IPv6 但没有 IPv5？
======
如果你花过很多时间在互联网上，那么你应该已经听说过计算机每天使用的 IPv4 和 IPv6 协议。
你可能会问的一个问题是：为什么没有 IPv5？为什么 IPv6 在 IPv4 之后而不是 IPv5 之后出现？是否有 IPv5，如果是，那么 IPv5 发生了什么？
答案是肯定的，曾经有一个 IPv5。让我解释一下这里发生的事。
### 互联网的早期历史
![ARPA Logical Map in 1977 | Image courtesy: Wikipedia][1]
在 1960 年代后期，美国国防部的[高级研究计划局][2] （ARPA） 发起了一个[项目][3]来连接全国的计算机。最初的目标是创建一个由全国 ARPA 资助的所有计算机组成的网络系统。
由于这是第一次将如此规模的网络整合在一起，因此他们也在不断发展自己的技术和硬件。他们的第一件工作是名为[传输控制协议][4] （TCP） 的互联网协议 （IP）。该协议“可靠、有序、并会对通过 IP 网络传输的八进制（字节）流错误检测”。基本上，它确保数据安全到达。
最初，TCP 被设计为[“主机级别的端到端协议以及打包和路由协议”][5]。但是，他们意识到他们需要拆分协议以使其更易于管理。于是决定由 IP 处理打包和路由。
那时，TCP 已经经历了三个版本，因此新协议被称为 IPv4。
### IPv5 的诞生
IPv5 以不同的名称开始使用：互联网流协议（或 ST）。它是[由 Apple、NeXT 和 Sun Microsystems][6] 创建用于实验流式传输语音和视频。
该新协议能够“在保持通信的同时在特定频率上传输数据包”。
### 那么 IPv5 发生了什么？
![][7]
IPv5 从未被接受为正式的互联网协议。这主要是由于 32 位限制。
IPV5 使用与 IPv4 相同的寻址系统。每个地址由 0 到 255 之间的四组数字组成。这将可能的地址数量限制为 [43 亿][6]。
在 1970 年代初，这似乎比全世界所需要的还要多。但是，互联网的爆炸性增长证明了这一想法是错误的。2011年，世界正式耗尽了 IPv4 地址。
在 1990 年代，一个新项目开始致力于下一代互联网协议 （IPng）。这导致了 128 位的 IPv6。IPv6 地址包含 [“8 组 4 字符的十六进制数字”][6]，它可以包含从 0 到 9 的数字和从 A 到 F 的字母。与 IPv4 不同，IPv6 拥有数万亿个可能的地址，因此我们应该能安全一阵子。
同时，IPv5 奠定了 VoIP 的基础，而该技术已被我们用于当今世界范围内的通信。**因此，我想往小了说，你可以说 IPv5 仍然可以保留到了今天**。
希望你喜欢有关互联网历史的轶事。你可以阅读其他[关于 Linux 和技术的琐事文章] [8]。
如果你觉得这篇文章有趣，请花一点时间在社交媒体、Hacker News 或 [Reddit][9] 上分享它。
--------------------------------------------------------------------------------
via: https://itsfoss.com/what-happened-to-ipv5/
作者：[John Paul][a]
选题：[lujun9972][b]
译者：[geekpi](https://github.com/geekpi)
校对：[校对者ID](https://github.com/校对者ID)
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
[a]: https://itsfoss.com/author/john/
[b]: https://github.com/lujun9972
[1]: https://i1.wp.com/itsfoss.com/wp-content/uploads/2020/04/Arpa_internet.png?fit=800%2C573&ssl=1
[2]: https://en.wikipedia.org/wiki/DARPA
[3]: https://en.wikipedia.org/wiki/ARPANET
[4]: https://en.wikipedia.org/wiki/Transmission_Control_Protocol
[5]: https://fcw.com/articles/2006/07/31/what-ever-happened-to-ipv5.aspx
[6]: https://www.lifewire.com/what-happened-to-ipv5-3971327
[7]: https://i0.wp.com/itsfoss.com/wp-content/uploads/2020/04/what-happened-to-ipv5.png?ssl=1
[8]: https://itsfoss.com/category/story/
[9]: https://reddit.com/r/linuxusersgroup