mirror of
https://github.com/LCTT/TranslateProject.git
synced 2024-12-26 21:30:55 +08:00
beamrolling
GitHub
commit
e4592f4faf
@ -2,7 +2,7 @@
|
||||
[#]: via: "https://news.itsfoss.com/onlyoffice-7-1-release/"
|
||||
[#]: author: "Jacob Crume https://news.itsfoss.com/author/jacob/"
|
||||
[#]: collector: "lkxed"
|
||||
[#]: translator: " "
|
||||
[#]: translator: "PeterPan0106"
|
||||
[#]: reviewer: " "
|
||||
[#]: publisher: " "
|
||||
[#]: url: " "
|
||||
@ -125,7 +125,7 @@ via: https://news.itsfoss.com/onlyoffice-7-1-release/
|
||||
|
||||
作者：[Jacob Crume][a]
|
||||
选题：[lkxed][b]
|
||||
译者：[译者ID](https://github.com/译者ID)
|
||||
译者：[PeterPan0106](https://github.com/PeterPan0106)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
||||
@ -1,62 +0,0 @@
|
||||
[#]: subject: "FSF Does Not Accept Debian as a Free Distribution. Here’s Why!"
|
||||
[#]: via: "https://news.itsfoss.com/fsf-does-not-consider-debian-a-free-distribution/"
|
||||
[#]: author: "Abhishek https://news.itsfoss.com/author/root/"
|
||||
[#]: collector: "lkxed"
|
||||
[#]: translator: " "
|
||||
[#]: reviewer: " "
|
||||
[#]: publisher: " "
|
||||
[#]: url: " "
|
||||
|
||||
FSF Does Not Accept Debian as a Free Distribution. Here’s Why!
|
||||
======
|
||||
![Why FSF doesn't consider Debian a free distribution][1]
|
||||
|
||||
The Debian Project develops a free GNU/Linux distribution that respects the freedom of its users. It’s not uncommon for software, the source code of which is distributed under this or that free license, to contain non-free components. In this case, the software is cleaned before being released into Debian. The Free Software Foundation (FSF), in turn, maintains a [list of free GNU/Linux distributions][2], but oddly enough, Debian is not there. The fact is that Debian does not meet some criteria for getting on this list and we have to figure out which ones. But first, you need to understand how all this intellectual work is justified. In other words, why bother trying to get on some lists and this one in particular?
|
||||
|
||||
Stefano Zacchiroli, who used to be the leader of the Debian Project from 2010 to 2013, once voiced several reasons why Debian should have got the FSF to obtain the status of free distribution. One of these reasons, which Stefano called “external review”, I especially liked. The fact is that Debian has criteria and quality standards that software must meet to become part of the distribution, but no one except the Debian developers themselves controls this process. If the distribution had been included in that cherished list, the FSF would have been keeping a close eye on the fate of Debian with moderate criticism. Excellent motivation, I believe. If you also think so, then let’s now have a look at the reasons why the FSF considers Debian as not free enough.
|
||||
|
||||
### Debian Social Contract
|
||||
|
||||
Along with the list of free GNU/Linux distributions, the FSF maintains a list of GNU/Linux distributions that have been rejected a free status for one reason or another. For each distribution in this list, there is a comment with a brief argument for refusal. From the comment on Debian, it becomes clear that the main source of disagreement between the FSF and the Debian Project in the interpretation of the phrase “free distribution” is a document known as the Debian Social Contract.
|
||||
|
||||
The Debian Social Contract has five points. To answer the main question, we need only two of them – the first and the fifth, so they will be given below, and the others are omitted. Check out the full version of the contract [here][3].
|
||||
|
||||
The first point says: «**Debian will remain 100% free**. We provide the guidelines that we use to determine if a work is “free” in the document entitled “The Debian Free Software Guidelines”. We promise that the Debian system and all its components will be free according to these guidelines. We will support people who create or use both free and non-free works on Debian. We will never make the system require the use of a non-free component.»
|
||||
|
||||
At the same time, the fifth point reads: «**Works that do not meet our free software standards**. We acknowledge that some of our users require the use of works that do not conform to the Debian Free Software Guidelines. We have created “contrib” and “non-free” areas in our archive for these works. The packages in these areas are not part of the Debian system, although they have been configured for use with Debian. We encourage CD manufacturers to read the licenses of the packages in these areas and determine if they can distribute the packages on their CDs. Thus, although non-free works are not a part of Debian, we support their use and provide infrastructure for non-free packages (such as our bug tracking system and mailing lists).»
|
||||
|
||||
Although the contract states that the distribution will remain 100% free, it allows sections of the official archive that may contain non-free software or free software that depends on some non-free components. Formally, the software in these sections, according to the same contract, is not part of Debian, but the FSF is haunted by this since these sections make it much easier to install non-free software on a system.
|
||||
|
||||
Until 2011, the FSF had reasonable grounds not to consider Debian free – the distribution was shipped with a Linux kernel uncleaned from binary blobs. But since the February 2011 release of Squeeze to this day, Debian has included the free Linux kernel. Thus, simplifying the installation of non-free software is the main reason why the FSF cannot recognize Debian as free distribution, and until 2016 this was the only reason I knew, but in early 2016 something went wrong…
|
||||
|
||||
### Wait… what’s Firefox doing here?
|
||||
|
||||
For a long time, Debian included a browser called Iceweasel, which was nothing more than a rebrand of the Firefox browser. The rebranding was carried out for two reasons. First, the browser logo and name are trademarks of the Mozilla Foundation, and the provision of non-free software contradicts the DFSG. Second, by including the browser in the distribution, the Debian developers had to comply with the requirements of the Mozilla Foundation, which prohibits the delivery of a modified version of the browser under the name Firefox. Thus, the developers had to change the name, because they constantly make changes to the browser code to fix bugs and eliminate vulnerabilities. But at the beginning of 2016 Debian was lucky to have a modified browser that does not fall under the above restrictions and can retain the original name and logo. On the one hand, this is a recognition of merit and a demonstration of trust in Debian. On the other hand, the software, obviously uncleaned from non-free components, is now a part of the distribution. If by this time Debian had been included in the list of free GNU/Linux distributions, the Free Software Foundation wouldn’t have hesitated to point this out.
|
||||
|
||||
### Conclusion
|
||||
|
||||
Freedom in the digital world is as important as freedom in the real world. In this article, I tried to reveal one of the most important features of Debian – developing distribution with regard to the freedom of its users. Developers spend extra time cleaning up non-free components from software, and dozens of distributions for which Debian is the technology base inherit its work, and with it, a piece of freedom.
|
||||
|
||||
Also, I wanted to share a simple observation that freedom is not as straightforward as it might seem at first glance, and it is quite natural to enquire what is really free and what is not. Debian cannot be called a free GNU/Linux distribution now because of the presence of Firefox in it. But from 2011, when Debian finally began cleaning the kernel along with other components of the distribution, and until 2016, when Firefox became part of the distribution, the Free Software Foundation did not consider the distribution to be free for purely ideological reasons: Debian greatly simplifies the installation of non-free software… Now it’s your turn to weigh up all the arguments and decide whether to consider the GNU/Linux distribution as free or not.
|
||||
|
||||
Good luck! And stay as free as possible.
|
||||
|
||||
Written by Evgeny Golyshev for [Cusdeb.com][4]
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://news.itsfoss.com/fsf-does-not-consider-debian-a-free-distribution/
|
||||
|
||||
作者：[Abhishek][a]
|
||||
选题：[lkxed][b]
|
||||
译者：[译者ID](https://github.com/译者ID)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
||||
[a]: https://news.itsfoss.com/author/root/
|
||||
[b]: https://github.com/lkxed
|
||||
[1]: https://news.itsfoss.com/wp-content/uploads/2022/05/why-fsf-doesnt-consider-debian-a-free-software-1200-%C3%97-675px.png
|
||||
[2]: https://gnu.org/distros/free-distros.en.html
|
||||
[3]: https://debian.org/social_contract
|
||||
[4]: https://wiki.cusdeb.com/Essays:Why_the_FSF_does_not_consider_Debian_as_a_free_distribution/en
|
||||
@ -0,0 +1,130 @@
|
||||
[#]: subject: "Linux Kernel 5.18 Released with Graphics Driver Changes and New Hardware Support"
|
||||
[#]: via: "https://news.itsfoss.com/linux-kernel-5-18-release/"
|
||||
[#]: author: "Ankush Das https://news.itsfoss.com/author/ankush/"
|
||||
[#]: collector: "lkxed"
|
||||
[#]: translator: " "
|
||||
[#]: reviewer: " "
|
||||
[#]: publisher: " "
|
||||
[#]: url: " "
|
||||
|
||||
Linux Kernel 5.18 Released with Graphics Driver Changes and New Hardware Support
|
||||
======
|
||||
The latest Linux Kernel 5.18 is now available as per the expected schedule without any delays. The release includes support for new hardware, and some core changes.
|
||||
|
||||
![Linux kernel 5.18 release][1]
|
||||
|
||||
[Linux Kernel 5.17][2] came loaded with support for next-gen hardware, including improvements for the Steam Deck.
|
||||
|
||||
Not to forget, every Linux Kernel release is technically exciting, and Linux Kernel 5.18 is no exception.
|
||||
|
||||
### Linux Kernel 5.18: What’s New?
|
||||
|
||||
This time around, we get to see improved support for Razer hardware, Apple Magic keyboard, AMD graphics, and numerous networking, core, and security changes.
|
||||
|
||||
#### A New Razer Driver
|
||||
|
||||
When it comes to gaming gears, the hardware support in Linux needs serious upgrades.
|
||||
|
||||
Yes, there are useful workarounds with open-source drivers. But, that’s not always the solution for every user.
|
||||
|
||||
As spotted by [Phoronix][3], a new Razer HID driver comes with Linux Kernel 5.18, which focuses on Razer BlackWidow keyboards fixing the macro key handling.
|
||||
|
||||
#### AMDGPU FreeSync Video Mode Enabled by Default
|
||||
|
||||
![][4]
|
||||
|
||||
While the support for FreeSync video was good enough, it was a temporary solution to improve the user experience with FreeSync monitors.
|
||||
|
||||
Now, with Linux Kernel 5.18, the FreeSync video mode is enabled by default ([changelog][5]). You do not have to do anything from your side to enable it with supported monitors.
|
||||
|
||||
#### Graphics Driver Updates
|
||||
|
||||
In addition to the improvements to the AMDGPU driver, you also get updates preparing for future hardware.
|
||||
|
||||
There have been changes to support higher DisplayPort rates as well.
|
||||
|
||||
#### Switch from C89 to C11 (GNU11)
|
||||
|
||||
![][6]
|
||||
|
||||
The C programming used for the Linux Kernel was limited to the old C89 standard, which lacked certain features for the current requirements.
|
||||
|
||||
So, C11 was decided to replace it considering the current compiler version requirement i.e. GCC 5.1 sounds perfectly fine with it.
|
||||
|
||||
#### Networking Tweaks
|
||||
|
||||
Linux Kernel 5.18 adds support for new wireless hardware, including MediaTek MT7916, MT7921U, and Broadcom BCM43454/6.
|
||||
|
||||
![][7]
|
||||
|
||||
When it comes to mobile solutions, support for Intel M.2 WWAN card has also been added.
|
||||
|
||||
The Realtek W89 driver now supports AP mode, 6 GHz band, and adds a hardware scan feature.
|
||||
|
||||
Several other improvements have been made to configure IPv6, and handle various protocols, including performance optimizations.
|
||||
|
||||
#### USB Improvements
|
||||
|
||||
Xen USB driver is being hardened against malicious hosts, and the USB DWC3 driver received improvements to support more hardware types.
|
||||
|
||||
You can find various other refinements in the [commit log][8].
|
||||
|
||||
#### Enhanced Apple Keyboard and Tablet Support
|
||||
|
||||
![][9]
|
||||
|
||||
Advancements were made to improve the experience with Apple Magic Keyboards, including the first-generation models.
|
||||
|
||||
Some of the fixes included correcting function-key mapping, keyboard backlight events, and the ability to report the battery level for the 2021 Magic Keyboard model when connected via USB.
|
||||
|
||||
Linux Kernel 5.18 improves input handling and makes things reliable when it comes to tablets.
|
||||
|
||||
You can find changes for new hardware, touchscreens, and other stuff in the related [commit][10].
|
||||
|
||||
#### New ARM Chip Support (Tesla FSD, Raspberry Pi Zero 2 W)
|
||||
|
||||
![][11]
|
||||
|
||||
Tesla’s full self-driving SoC is now supported with Linux Kernel 5.18. Samsung engineers made it possible to upstream into the Linux Kernel.
|
||||
|
||||
Other interesting chip additions include Qualcomm Snapdragon 625/632, and Samsung Exynos 850/7885.
|
||||
|
||||
You also find the support for Raspberry Pi Zero 2 W with Linux Kernel 5.18. In addition to the new entrants, old hardware/boards were removed as well. You can explore the [commit l][12]og to know more.
|
||||
|
||||
You can refer to the [official changelog][13] and Linus Torvald’s announcement to explore more details.
|
||||
|
||||
### How to Install Linux Kernel 5.18?
|
||||
|
||||
You should find the newer kernel listed on [Linux Kernel Archives][14]. So, you can download the [tarball][15] to test it out. Or, you can follow our [Linux Kernel upgrade guide][16] for help.
|
||||
|
||||
If you want to avoid compiling it yourself, you should wait for a few weeks for Linux distributions to push it to the repositories.
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://news.itsfoss.com/linux-kernel-5-18-release/
|
||||
|
||||
作者：[Ankush Das][a]
|
||||
选题：[lkxed][b]
|
||||
译者：[译者ID](https://github.com/译者ID)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
||||
[a]: https://news.itsfoss.com/author/ankush/
|
||||
[b]: https://github.com/lkxed
|
||||
[1]: https://news.itsfoss.com/wp-content/uploads/2022/05/kernel-5-18-release.png
|
||||
[2]: https://news.itsfoss.com/linux-kernel-5-17-release/
|
||||
[3]: https://www.phoronix.com/scan.php?page=news_item&px=Linux-5.18-HID
|
||||
[4]: https://news.itsfoss.com/wp-content/uploads/2022/05/amd-linux-5-18-1024x576.jpg
|
||||
[5]: https://lists.freedesktop.org/archives/amd-gfx/2022-February/075262.html
|
||||
[6]: https://news.itsfoss.com/wp-content/uploads/2022/05/c-linux-5-18-1024x576.jpg
|
||||
[7]: https://news.itsfoss.com/wp-content/uploads/2022/05/networking-linux-5-18-1024x576.jpg
|
||||
[8]: https://lore.kernel.org/lkml/Yj7vGtn8fILavjyL@kroah.com/
|
||||
[9]: https://news.itsfoss.com/wp-content/uploads/2022/05/apple-linux-5-18-1024x576.jpg
|
||||
[10]: https://lore.kernel.org/lkml/nycvar.YFH.7.76.2203231015060.24795@cbobk.fhfr.pm/
|
||||
[11]: https://news.itsfoss.com/wp-content/uploads/2022/05/arm-linux-5-18-1024x576.jpg
|
||||
[12]: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=baaa68a9796ef2cadfe5caaf4c730412eda0f31c
|
||||
[13]: https://lore.kernel.org/lkml/CAHk-=wjiqyoH6qntYvYTjR1F2L-pHtgX9esZMRS13iktCOJ1zA@mail.gmail.com/T/#u
|
||||
[14]: https://www.kernel.org/
|
||||
[15]: https://git.kernel.org/torvalds/t/linux-5.16.tar.gz
|
||||
[16]: https://itsfoss.com/upgrade-linux-kernel-ubuntu/
|
||||
@ -1,182 +0,0 @@
|
||||
[#]: collector: (lujun9972)
|
||||
[#]: translator: (CoWave-Fall)
|
||||
[#]: reviewer: ( )
|
||||
[#]: publisher: ( )
|
||||
[#]: url: ( )
|
||||
[#]: subject: (31 open source text editors you need to try)
|
||||
[#]: via: (https://opensource.com/article/21/2/open-source-text-editors)
|
||||
[#]: author: (Seth Kenlon https://opensource.com/users/seth)
|
||||
|
||||
31 open source text editors you need to try
|
||||
======
|
||||
Looking for a new text editor? Here are 31 options to consider.
|
||||
![open source button on keyboard][1]
|
||||
|
||||
Computers are text-based, so the more things you do with them, the more you find yourself needing a text-editing application. And the more time you spend in a text editor, the more likely you are to demand more from whatever you use.
|
||||
|
||||
If you're looking for a good text editor, you'll find that Linux has plenty to offer. Whether you want to work in the terminal, on your desktop, or in the cloud, you can literally try a different editor every day for a month (or one a month for almost three years) in your relentless search for the perfect typing experience.
|
||||
|
||||
### Vim-like editors
|
||||
|
||||
![][2]
|
||||
|
||||
* [Vi][3] ships with every Linux, BSD, Solaris, and macOS installation. It's the quintessential Unix text editor, with its unique combination of editing modes and super-efficient single-key shortcuts. The original Vi editor was an application written by Bill Joy, creator of the C shell. Modern incarnations of Vi, most notably Vim, have added many features, including multiple levels of undo, better navigation while in insert mode, line folding, syntax highlighting, plugin support, and much more. It takes practice (it even has its own tutor application, vimtutor.)
|
||||
* [Kakoune][4] is a Vim-inspired application with a familiar, minimalistic interface, short keyboard shortcuts, and separate editing and insert modes. It looks and feels a lot like Vi at first, but with its own unique style, both in design and function. As a special bonus, it features an implementation of the Clippy interface.
|
||||
|
||||
|
||||
|
||||
### emacs editors
|
||||
|
||||
![][5]
|
||||
|
||||
* The original free emacs, and one of the first official applications of the GNU project that started the Free Software movement, [GNU Emacs][6] is a wildly popular text editor. It's great for sysadmins, developers, and everyday users alike, with loads of features and seemingly endless extensions. Once you start using Emacs, you might find it difficult to think of a reason to close it because it's just that versatile!
|
||||
* If you like Emacs but find GNU Emacs too bloated, then you might like [Jove][7]. Jove is a terminal-based emacs editor. It's easy to use, but if you're new to emacsen (the plural of emacs), Jove is also easy to learn, thanks to the teachjove command.
|
||||
* Another lightweight emacs editor, [Jed][8] is a simple incarnation of a macro-based workflow. One thing that sets it apart from other editors is its use of [S-Lang][9], a C-like scripting language providing extensibility options to developers more comfortable with C than with Lisp.
|
||||
|
||||
|
||||
|
||||
### Interactive editors
|
||||
|
||||
![][10]
|
||||
|
||||
* [GNU nano][11] takes a bold stance on terminal-based text editing: it provides a menu. Yes, this humble editor takes a cue from GUI editors by telling the user exactly which key they need to press to perform a specific function. This is a refreshing take on user experience, so it's no wonder that it's nano, not Vi, that's set as the default editor for "user-friendly" distributions.
|
||||
* [JOE][12] is based on an old text-editing application called WordStar. If you're not familiar with Wordstar, JOE can also mimic Emacs or GNU nano. By default, it's a good compromise between something relatively mysterious like Emacs or Vi and the always-on verbosity of GNU Nano (for example, it tells you how to activate an onscreen help display, but it's not on by default).
|
||||
* The excellent [e3][13] application is a tiny text editor with five built-in keyboard shortcut schemes to emulate Emacs, Vi, nano, NEdit, and WordStar. In other words, no matter what terminal-based editor you are used to, you're likely to feel right at home with e3.
|
||||
|
||||
|
||||
|
||||
### ed and more
|
||||
|
||||
* The [ed][14] line editor is part of the [POSIX][15] and Open Group's standard definition of a Unix-based operating system. You can count on it being installed on nearly every Linux or Unix system you'll ever encounter. It's tiny, terse, and tip-top.
|
||||
* Building upon ed, the [Sed][16] stream editor is popular both for its functionality and its syntax. Most Linux users learn at least one sed command when searching for the easiest and fastest way to update a line in a config file, but it's worth taking a closer look. Sed is a powerful command with lots of useful subcommands. Get to know it better, and you may find yourself open text editor applications a lot less frequently.
|
||||
* You don't always need a text editor to edit text. The [heredoc][17] (or Here Doc) system, available in any POSIX terminal, allows you to type text directly into your open terminal and then pipes what you type into a text file. It's not the most robust editing experience, but it is versatile and always available.
|
||||
|
||||
|
||||
|
||||
### Minimalist editors
|
||||
|
||||
![][18]
|
||||
|
||||
If your idea of a good text editor is a word processor except without all the processing, you're probably looking for one of these classics. These editors let you write and edit text with minimal interference and minimal assistance. What features they do offer are often centered around markup, Markdown, or code. Some have names that follow a certain pattern:
|
||||
|
||||
* [Gedit][19] from the GNOME team
|
||||
* [medit][20] for a classic GNOME feel
|
||||
* [Xedit][21] uses only the most basic X11 libraries
|
||||
* [jEdit][22] for Java aficionados
|
||||
|
||||
|
||||
|
||||
A similar experience is available for KDE users:
|
||||
|
||||
* [Kate][23] is an unassuming editor with all the features you need.
|
||||
* [KWrite][24] hides a ton of useful features in a deceptively simple, easy-to-use interface.
|
||||
|
||||
|
||||
|
||||
And there are a few for other platforms:
|
||||
|
||||
* [Notepad++][25] is a popular Windows application, while Notepadqq takes a similar approach for Linux.
|
||||
* [Pe][26] is for Haiku OS (the reincarnation of that quirky child of the '90s, BeOS).
|
||||
* [FeatherPad][27] is a basic editor for Linux but with some support for macOS and Haiku. If you're a Qt hacker looking to port code, take a look!
|
||||
|
||||
|
||||
|
||||
### IDEs
|
||||
|
||||
![][28]
|
||||
|
||||
There's quite a crossover between text editors and integrated development environments (IDEs). The latter really is just the former with lots of code-specific features added on. If you use an IDE regularly, you might find an XML or Markdown editor lurking in your extension manager:
|
||||
|
||||
* [NetBeans][29] is a handy text editor for Java users.
|
||||
* [Eclipse][30] offers a robust editing suite with lots of extensions to give you the tools you need.
|
||||
|
||||
|
||||
|
||||
### Cloud-based editors
|
||||
|
||||
![][31]
|
||||
|
||||
Working in the cloud? You can write there too, you know.
|
||||
|
||||
* [Etherpad][32] is a text editor app that runs on the web. There are free and independent instances for you to use, or you can set up your own.
|
||||
* [Nextcloud][33] has a thriving app scene and includes both a built-in text editor and a third-party Markdown editor with live preview.
|
||||
|
||||
|
||||
|
||||
### Newer editors
|
||||
|
||||
![][34]
|
||||
|
||||
Everybody has an idea about what makes a text editor perfect. For that reason, new editors are released each year. Some reimplement classic old ideas in a new and exciting way, some have unique takes on the user experience, and some focus on specific needs.
|
||||
|
||||
* [Atom][35] is an all-purpose modern text editor from GitHub featuring lots of extensions and Git integration.
|
||||
* [Brackets][36] is an editor from Adobe for web developers.
|
||||
* [Focuswriter][37] seeks to help you focus on writing with helpful features like a distraction-free fullscreen mode, optional typewriter sound effects, and beautiful configuration options.
|
||||
* [Howl][38] is a progressive, dynamic editor based on Lua and Moonscript.
|
||||
* [Norka][39] and [KJots][40] mimic a notebook with each document representing a "page" in your "binder." You can take individual pages out of your notebook through export functions.
|
||||
|
||||
|
||||
|
||||
### DIY editor
|
||||
|
||||
![][41]
|
||||
|
||||
As the saying does _NOT_ go: Why use somebody else's application when you can write your own? Linux has over 30 text editors available, so probably the last thing it really needs is another one. Then again, part of the fun of open source is the ability to experiment.
|
||||
|
||||
If you're looking for an excuse to learn how to program, making your own text editor is a great way to get started. You can achieve the basics in about 100 lines of code, and the more you use it, the more you'll be inspired to learn more so you can make improvements. Ready to get started? Go and [create your own text editor][42].
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://opensource.com/article/21/2/open-source-text-editors
|
||||
|
||||
作者：[Seth Kenlon][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/seth
|
||||
[b]: https://github.com/lujun9972
|
||||
[1]: https://opensource.com/sites/default/files/styles/image-full-size/public/lead-images/button_push_open_keyboard_file_organize.png?itok=KlAsk1gx (open source button on keyboard)
|
||||
[2]: https://opensource.com/sites/default/files/kakoune-screenshot.png
|
||||
[3]: https://opensource.com/article/20/12/vi-text-editor
|
||||
[4]: https://opensource.com/article/20/12/kakoune
|
||||
[5]: https://opensource.com/sites/default/files/jed.png
|
||||
[6]: https://opensource.com/article/20/12/emacs
|
||||
[7]: https://opensource.com/article/20/12/jove-emacs
|
||||
[8]: https://opensource.com/article/20/12/jed
|
||||
[9]: https://www.jedsoft.org/slang
|
||||
[10]: https://opensource.com/sites/default/files/uploads/nano-31_days-nano-opensource.png
|
||||
[11]: https://opensource.com/article/20/12/gnu-nano
|
||||
[12]: https://opensource.com/article/20/12/31-days-text-editors-joe
|
||||
[13]: https://opensource.com/article/20/12/e3-linux
|
||||
[14]: https://opensource.com/article/20/12/gnu-ed
|
||||
[15]: https://opensource.com/article/19/7/what-posix-richard-stallman-explains
|
||||
[16]: https://opensource.com/article/20/12/sed
|
||||
[17]: https://opensource.com/article/20/12/heredoc
|
||||
[18]: https://opensource.com/sites/default/files/uploads/gedit-31_days_gedit-opensource.jpg
|
||||
[19]: https://opensource.com/article/20/12/gedit
|
||||
[20]: https://opensource.com/article/20/12/medit
|
||||
[21]: https://opensource.com/article/20/12/xedit
|
||||
[22]: https://opensource.com/article/20/12/jedit
|
||||
[23]: https://opensource.com/article/20/12/kate-text-editor
|
||||
[24]: https://opensource.com/article/20/12/kwrite-kde-plasma
|
||||
[25]: https://opensource.com/article/20/12/notepad-text-editor
|
||||
[26]: https://opensource.com/article/20/12/31-days-text-editors-pe
|
||||
[27]: https://opensource.com/article/20/12/featherpad
|
||||
[28]: https://opensource.com/sites/default/files/uploads/eclipse-31_days-eclipse-opensource.png
|
||||
[29]: https://opensource.com/article/20/12/netbeans
|
||||
[30]: https://opensource.com/article/20/12/eclipse
|
||||
[31]: https://opensource.com/sites/default/files/uploads/etherpad_0.jpg
|
||||
[32]: https://opensource.com/article/20/12/etherpad
|
||||
[33]: https://opensource.com/article/20/12/31-days-text-editors-nextcloud-markdown-editor
|
||||
[34]: https://opensource.com/sites/default/files/uploads/atom-31_days-atom-opensource.png
|
||||
[35]: https://opensource.com/article/20/12/atom
|
||||
[36]: https://opensource.com/article/20/12/brackets
|
||||
[37]: https://opensource.com/article/20/12/focuswriter
|
||||
[38]: https://opensource.com/article/20/12/howl
|
||||
[39]: https://opensource.com/article/20/12/norka
|
||||
[40]: https://opensource.com/article/20/12/kjots
|
||||
[41]: https://opensource.com/sites/default/files/uploads/this-time-its-personal-31_days_yourself-opensource.png
|
||||
[42]: https://opensource.com/article/20/12/31-days-text-editors-one-you-write-yourself
|
||||
@ -2,7 +2,7 @@
|
||||
[#]: via: "https://itsfoss.com/install-vs-code-extensions/"
|
||||
[#]: author: "Pratham Patel https://itsfoss.com/author/pratham/"
|
||||
[#]: collector: "lujun9972"
|
||||
[#]: translator: " "
|
||||
[#]: translator: "CoWave-Fall"
|
||||
[#]: reviewer: " "
|
||||
[#]: publisher: " "
|
||||
[#]: url: " "
|
||||
|
||||
@ -1,58 +0,0 @@
|
||||
[#]: subject: "Five common mistakes when using automation"
|
||||
[#]: via: "https://fedoramagazine.org/five-common-mistakes-when-using-automation/"
|
||||
[#]: author: "Gary Scarborough https://fedoramagazine.org/author/gscarbor/"
|
||||
[#]: collector: "lujun9972"
|
||||
[#]: translator: "geekpi"
|
||||
[#]: reviewer: " "
|
||||
[#]: publisher: " "
|
||||
[#]: url: " "
|
||||
|
||||
Five common mistakes when using automation
|
||||
======
|
||||
|
||||
![][1]
|
||||
|
||||
Background image from ["Modern Times" (1936)][2], [United Artists][3], Public domain, via Wikimedia Commons
|
||||
|
||||
As automation expands to cover more aspects of IT, more administrators are learning automation skills and applying them to ease their workload. Automation can ease the burden of repetitive tasks and add a level of conformity to infrastructure. But when IT workers deploy automation, there are common mistakes that can wreak havoc on infrastructures large and small. Five common mistakes are typically seen in automation deployments.
|
||||
|
||||
### Lack of testing
|
||||
|
||||
A beginner’s mistake that is commonly made is that automation scripts are not thoroughly tested. A simple shell script can have adverse affects on a server due to typos or logic errors. Multiply that mistake by the number of servers in your infrastructure, and you can have a big mess to clean up. Always test your automation scripts before deploying in large scale.
|
||||
|
||||
### Unexpected server load
|
||||
|
||||
The second mistake that frequently occurs is not predicting the system load the script may put on other resources. Running a script that downloads a file or installs a package from a repository may be fine when the target is a dozen servers. Scripts are often run against hundreds or thousands of servers. This load can bring supporting services to a stand still or crash them entirely. Don’t forget to consider end point impact or set a reasonable concurrency rate.
|
||||
|
||||
### Run away scripts
|
||||
|
||||
One use of automation tools is to ensure compliance to standard settings. Automation can make it easy to ensure that every server in a group has exactly the same settings. Problems may arise if a server in that group needs to be altered from that baseline, and the administrator is not aware of the compliance standard. Unneeded and unwanted services can be installed and enabled leading to possible security concerns.
|
||||
|
||||
### Lack of documentation
|
||||
|
||||
A constant duty for administrators should be to document their work. Companies can have frequent new employees in IT departments due to contracts ending or promotions or regular employee turnover. It is also not uncommon for work groups within a company to be siloed from each other. For these reasons it is important to document what automation is in place. Unlike user run scripts, automation may continue long after the person who created it leaves the group. Administrators can find themselves facing strange behaviors in their infrastructure from automation left unchecked.
|
||||
|
||||
### Lack of experience
|
||||
|
||||
The last mistake on the list is when administrators do not know enough about the systems they are automating. Too often admins are hired to work positions where they do not have adequate training and no one to learn from. This has been especially relevant since COVID when companies are struggling to fill vacancies. Admins are then forced to deal with infrastructure they didn’t set up and may not fully understand. This can lead to very inefficient scripts that waste resources or misconfigured servers.
|
||||
|
||||
### Conclusion
|
||||
|
||||
More and more admins are learning automation to help them in their everyday tasks. As a result, automation is being applied to more areas of technology. Hopefully this list will help prevent new users from making these mistakes and urge seasoned admins to re-evaluate their IT strategies. Automation is meant to ease the burden of repetitive tasks, not cause more work for the end user.
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://fedoramagazine.org/five-common-mistakes-when-using-automation/
|
||||
|
||||
作者：[Gary Scarborough][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://fedoramagazine.org/author/gscarbor/
|
||||
[b]: https://github.com/lujun9972
|
||||
[1]: https://fedoramagazine.org/wp-content/uploads/2022/05/modern-times-816x345.jpg
|
||||
[2]: https://en.wikipedia.org/wiki/Modern_Times_(film)
|
||||
[3]: https://commons.wikimedia.org/wiki/File:Chaplin_-_Modern_Times.jpg
|
||||
@ -2,7 +2,7 @@
|
||||
[#]: via: "https://www.debugpoint.com/2022/05/customize-gnome-42-look-1/"
|
||||
[#]: author: "Arindam https://www.debugpoint.com/author/admin1/"
|
||||
[#]: collector: "lkxed"
|
||||
[#]: translator: " "
|
||||
[#]: translator: "geekpi"
|
||||
[#]: reviewer: " "
|
||||
[#]: publisher: " "
|
||||
[#]: url: " "
|
||||
|
||||
@ -0,0 +1,141 @@
|
||||
[#]: subject: "Ultramarine Linux: Ultimate Fedora Spin with Budgie, Cutefish and Pantheon"
|
||||
[#]: via: "https://www.debugpoint.com/2022/05/ultramarine-linux-36/"
|
||||
[#]: author: "Arindam https://www.debugpoint.com/author/admin1/"
|
||||
[#]: collector: "lkxed"
|
||||
[#]: translator: " "
|
||||
[#]: reviewer: " "
|
||||
[#]: publisher: " "
|
||||
[#]: url: " "
|
||||
|
||||
Ultramarine Linux: Ultimate Fedora Spin with Budgie, Cutefish and Pantheon
|
||||
======
|
||||
A review of Ultramarine Linux features some unique desktop environments out-of-the-box with a Fedora base.
|
||||
|
||||
Ultramarine Linux is a Fedora-based distribution which offers Budgie, Cutefish, Pantheon and GNOME desktop environments. This distro gives you an out-of-the-box experience with all these desktop favours with under-the-hood tweaks and packages. In addition, it pre-loads several packages (RPM Fusion, etc.) for Fedora, which you usually do as a post-install[tweak][1].
|
||||
|
||||
On top of that, Ultramarine Linux also brings several packages from its [own copr repo][2] for package distribution.
|
||||
|
||||
### Ultramarine Linux Review (version 36)
|
||||
|
||||
#### What does it offer?
|
||||
|
||||
In a nutshell, Ultramarine Linux built itself on the Fedora Linux base. In addition, it gives you four desktop flavours – Budgie (flagship), Cutefish, Pantheon (of elementary OS) and GNOME desktop. The pre-loaded applications are typical as same as Fedora. Moreover, the application list changes based on your desktop environment of choice.
|
||||
|
||||
As it is based on Fedora Linux, you get to experience the latest and greatest of technology such as Linux Kernel, audio and video tech, latest file system improvements, programming environment, etc.
|
||||
|
||||
The distro is a unique combination of the latest tech with the beautiful desktops.
|
||||
|
||||
#### Installation
|
||||
|
||||
![Ultramarine uses Anaconda Installer][3]
|
||||
|
||||
The distro brings separate ISO files for different desktop environments. From the installer, you can not choose the desktop environment. You need to download the one which you prefer.
|
||||
|
||||
In a way, it is a good approach because isolating different ISO help to keep the ISO size in a range of ~2 GB.
|
||||
|
||||
It uses the same Fedora’s Anaconda installer, which is easy to use. During the test, I could not find any problem while downloading the ISO or installing it. All went super-smooth.
|
||||
|
||||
#### Desktop Flavours – the selling point
|
||||
|
||||
This review is based on the latest Ultramarine Linux 36 (Rhode Island) based on the recently released [Fedora 36][4]. With version 36, you get the [Linux Kernel 5.17][5] and the latest applications and packages.
|
||||
|
||||
##### Pantheon Flavour
|
||||
|
||||
![Ultramarine Linux with Pantheon Desktop][6]
|
||||
|
||||
The Pantheon desktop is surprisingly stable in Ultramarine Linux. When using, you may not feel sometimes it is elementary OS. But obviously, it is not.
|
||||
|
||||
The team also included the elementaryOS AppCenter, which gives you access to a massive list of software and apps. Moreover, the Fedora system updates and upgrades are also possible from AppCenter itself. In addition to Fedora base, you get the elementaryOS File manager, text editor and system settings in Ultramarine Linux.
|
||||
|
||||
![AppCenter works well with Fedora base][7]
|
||||
|
||||
##### Budgie Flavour
|
||||
|
||||
![Ultramarine Linux with Budgie Desktop][8]
|
||||
|
||||
The Budgie desktop is the flagship offering of Ultramarine Linux and gives you a stock Budgie desktop experience. On top of the base applications and packages from Fedora Linux, the Budgie flavour brings Budgie Control Center and Budgie Desktop settings to tweak your desktop. The Budgie is blazing fast and should be a choice for you if you want it to be a productive desktop.
|
||||
|
||||
This version 36 also includes the branding related changes for Fedora 37 as the [Budgie team is working on a Fedora spin][9].
|
||||
|
||||
##### Cutefish Flavour
|
||||
|
||||
![Ultramarine Linux – Cutefish desktop flavour][10]
|
||||
|
||||
A while back, when we [reviewed][11] the Cutefish desktop. Firstly, the Cutefish desktop is a new desktop environment created from the ground up with a vision to look beautiful while being productive. It comes with a native dark mode, a built-in global menu, and many unique features that you can read in our detailed review. Perhaps the Ultramarine is the first distro with Fedora, which provides a Cutefish desktop as an option.
|
||||
|
||||
Second, the team integrated the Cutefish flavour with Fedora in an organized way to give you this nice desktop with applications such as Cutefish’s file manager, terminal and settings window.
|
||||
|
||||
System upgrade/update Cutefish flavour uses GNOME Software similar to the Budgie flavour to install and uninstall applications.
|
||||
|
||||
##### GNOME Flavour
|
||||
|
||||
Finally, the GNOME version is similar to the Fedora workstation edition. It’s almost identical in terms of GNOME Shell and native application versions. The only difference is the RPM fusion, as reviewed below.
|
||||
|
||||
#### Applications and Differences with stock Fedora Linux
|
||||
|
||||
Firstly, the base applications are installed in all the above-stated desktop environments. Essential applications such as Firefox, LibreOffice, and system monitors are all installed by default in this distro. Other than that, the default shell is [ZSH with a Starship theme][12], which definitely improves productivity over the bash shell.
|
||||
|
||||
Secondly, the critical addition or difference from the stock Fedora version is that Ultramarine Linux includes the RPM Fusion repo by default. The RPM Fusion repo is a collection of packages or software available as a community project. They are not included in the official Fedora distribution because of their proprietary nature.
|
||||
|
||||
![Ultramarine packages RPM Fusion by default][13]
|
||||
|
||||
The Ultramarine Linux brings all the RPM Fusions types – free, non-free, free-tainted and non-free trained. So, from a general user standpoint, you need not worry about [adding RPM Fusion separately][14] to install extra media playback codecs or such apps.
|
||||
|
||||
The distro follows a release cadence based on Fedora Linux. So, in general, you get the updates within a month or so after an official Fedora release.
|
||||
|
||||
#### Performance
|
||||
|
||||
During our test, the performance is impressive in both virtual machines and physical systems. All the above desktop flavours have fantastic desktop responsiveness and an overall good impression while using them.
|
||||
|
||||
For example, Pantheon, which is a little resource heavy, uses 1.3 GB of RAM, and the CPU is on average 2% in an idle state. It uses 1.8 GB of RAM with a little higher CPU of around 4% based on the applications you are running in a hefty workload mode. We tested it during the heavy workload phase using text editor, Firefox, LibreOffice calc, image viewer, and two sessions of terminal applications.
|
||||
|
||||
![Idle state performance while using the Pantheon version][15]
|
||||
|
||||
![Heavy workload performance while using the Pantheon version][16]
|
||||
|
||||
Furthermore, I think the other desktop flavours would also be in a similar performance metric.
|
||||
|
||||
I think the performance is excellent, considering it’s based on optimized Fedora. You can efficiently run this distro in the moderately newer hardware (perhaps Intel i3 and above with good RAM capacity).
|
||||
|
||||
### Closing Notes
|
||||
|
||||
To summarize the Ultramarine Linux 36 review, I believe it’s one of the coolest Fedora spins with some beautiful desktop environments. The vision of this distro is perfect and has a good user base. One of the plus points is the Pantheon desktop which many users like, and you get it with Fedora without manual installation. An underrated distro, in my opinion, needs more love from the community.
|
||||
|
||||
If you like this Linux distribution and believe in its offerings, you should head to their community pages ([Twitter][17], [Discord][18]) for contributions/donations. The project needs some contributors as it’s a small member team.
|
||||
|
||||
You can download Ultramarine Linux from the[official website][19].
|
||||
|
||||
Finally, in the comment box below, let me know your opinion about this distro.
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://www.debugpoint.com/2022/05/ultramarine-linux-36/
|
||||
|
||||
作者：[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/2022/05/10-things-to-do-fedora-36-after-install/
|
||||
[2]: https://copr.fedorainfracloud.org/coprs/cappyishihara/ultramarine/
|
||||
[3]: https://www.debugpoint.com/wp-content/uploads/2022/05/Ultramarine-uses-Anaconda-Installer.jpg
|
||||
[4]: https://www.debugpoint.com/2022/05/fedora-36-features/
|
||||
[5]: https://www.debugpoint.com/2022/03/linux-kernel-5-17/
|
||||
[6]: https://www.debugpoint.com/wp-content/uploads/2022/05/Ultramine-Linux-with-Pantheon-Desktop.jpg
|
||||
[7]: https://www.debugpoint.com/wp-content/uploads/2022/05/AppCenter-works-well-with-Fedora-base.jpg
|
||||
[8]: https://www.debugpoint.com/wp-content/uploads/2022/05/Ultramine-Linux-with-Budgie-Desktop.jpg
|
||||
[9]: https://debugpointnews.com/fedora-budgie-fudgie/
|
||||
[10]: https://www.debugpoint.com/wp-content/uploads/2022/05/Ultramarine-Linux-Cutefosh-desktop-flavour.jpg
|
||||
[11]: https://www.debugpoint.com/2021/11/cutefish-os-review-2021/
|
||||
[12]: https://www.debugpoint.com/2021/10/install-use-zsh/
|
||||
[13]: https://www.debugpoint.com/wp-content/uploads/2022/05/Ultramarine-packages-RPM-Fusion-by-default.jpg
|
||||
[14]: https://www.debugpoint.com/2020/07/enable-rpm-fusion-fedora-rhel-centos/
|
||||
[15]: https://www.debugpoint.com/wp-content/uploads/2022/05/Idle-state-performance-while-using-Pantheon-version.jpg
|
||||
[16]: https://www.debugpoint.com/wp-content/uploads/2022/05/Heavy-workload-performance-while-using-Pantheon-version.jpg
|
||||
[17]: https://twitter.com/UltramarineProj
|
||||
[18]: https://discord.gg/bUuQasHdrF
|
||||
[19]: https://ultramarine-linux.org/download
|
||||
@ -0,0 +1,62 @@
|
||||
[#]: subject: "FSF Does Not Accept Debian as a Free Distribution. Here’s Why!"
|
||||
[#]: via: "https://news.itsfoss.com/fsf-does-not-consider-debian-a-free-distribution/"
|
||||
[#]: author: "Abhishek https://news.itsfoss.com/author/root/"
|
||||
[#]: collector: "lkxed"
|
||||
[#]: translator: "Chao-zhi"
|
||||
[#]: reviewer: " "
|
||||
[#]: publisher: " "
|
||||
[#]: url: " "
|
||||
|
||||
自由软件基金会为什么不认为 Debian 是一种自由发行版？
|
||||
======
|
||||
![Why FSF doesn't consider Debian a free distribution][1]
|
||||
|
||||
Debian 项目开发了一个尊重用户自由的 GNU/Linux 发行版。它的 non-free 软件源中拥有许多根据各式各样的自由许可证分发的软件。这些软件真正被发布到 Debian 之前会进行清理。而自由软件基金会 (Free Software Foundation, FSF) 维护着一份[自由的 GNU/Linux 发行版列表](2)，但奇怪的是，Debian 并不在这个列表中。事实是 Debian 不符合进入此列表的某些标准，我们很想知道到底不满足哪些标准。但首先，我们需要了解所有这些劳心劳力的工作是如何得到证明的。换句话说，为什么要费心尝试进入一些名单，尤其是这个名单？
|
||||
|
||||
曾于 2010 年至 2013 年担任 Debian 项目负责人的 Stefano Zacchiroli 曾表示 Debian 应该获得 FSF 的承认以维护它自由发行版的地位的几个原因。其中一个原因，Stefano 称之为“外部审查”，我特别赞同。事实是 Debian 的软件应当满足一些标准和质量水平才能成为发行版的一部分，但除了 Debian 开发人员自己之外没有人控制这个过程。如果该发行版被包含在这份珍贵的清单中，那么 FSF 将密切关注 Debian 的命运，并给予适度的批评。我相信这是很好的动力。如果你也这么认为，那么现在让我们看看 FSF 认为 Debian 不够自由的原因。
|
||||
|
||||
### Debian 社会契约
|
||||
|
||||
除了自由的 GNU/Linux 发行版列表之外，FSF 还维护着一份 GNU/Linux 发行版的列表，这些发行版由于某种原因被拒绝为自由状态。对于此列表中的每个发行版，都有一个带有拒绝的简短论据的评论。从对 Debian 的评论中可以清楚地看出，FSF 和 Debian 项目在对“自由分发”一词的解释上产生分歧的主要根源是一份被称为 Debian 社会契约的文件。
|
||||
|
||||
Debian 社会契约有五点。要回答主要问题，我们只需要关注其中两个点——即第一个和第五个，其他的省略。在[此处](3)查看合同的完整版本。
|
||||
|
||||
第一点说：« **Debian 将保持 100% 自由**。我们在标题为“Debian 自由软件指南”的文档中提供了用于确定作品是否“自由”的指南。我们承诺根据这些指南，Debian 系统及其所有组件将是自由的。我们将支持在 Debian 上创建或使用自由和非自由作品的人。我们永远不会让系统需要使用非自由组件。»
|
||||
|
||||
同时，第五点写道：« **不符合我们自由软件标准的作品**。我们承认我们的一些用户需要使用不符合 Debian 自由软件指南的作品。我们在我们的档案中为这些作品创建了“free”和“non-free”区域。这些区域中的软件包不是 Debian 系统的一部分，尽管它们已被配置为与 Debian 一起使用。我们鼓励 CD 制造商阅读这些区域的软件包许可证，并确定他们是否可以在其 CD 上分发这些软件包。因此，尽管非自由作品不是 Debian 的一部分，但我们支持它们的使用并为非自由软件包提供基础设施（例如我们的错误跟踪系统和邮件列表）。»
|
||||
|
||||
尽管合同规定分发将保持 100% 自由，但它允许官方存档的部分可能包含非自由软件或依赖于某些非自由组件的自由软件。形式上，根据同一份合同，这些部分中的软件不是 Debian 的一部分，但 FSF 对此感到困扰，因为这些部分使在系统上安装非自由软件变得更加容易。
|
||||
|
||||
2011 年时，FSF 有合理的理由不考虑 Debian 自由版——该发行版附带了一个未清除二进制 blob 的 Linux 内核。但自 2011 年 2 月发布的 Squeeze 至今，Debian 已经包含了完全自由的 Linux 内核。因此，简化非自由软件的安装是 FSF 无法将 Debian 识别为自由发行版的主要原因，直到 2016 年这是我知道的唯一原因，但在 2016 年初出现了问题……
|
||||
|
||||
### 等等…… 关 Firefox 什么事？
|
||||
|
||||
很长一段时间，Debian 都包含一个名为 Iceweasel 的浏览器，它只不过是 Firefox 浏览器的更名。进行品牌重塑有两个原因。首先，浏览器标志和名称是 Mozilla 基金会的商标，提供非自由软件与 DFSG 相抵触。其次，通过在发行版中包含浏览器，Debian 开发人员必须遵守 Mozilla 基金会的要求，该基金会禁止以 Firefox 的名义交付浏览器的修改版本。因此，开发人员不得不更改名称，因为他们不断更改浏览器代码以修复错误并消除漏洞。但在 2016 年初，Debian 有幸拥有一款经过修改的浏览器，不受上述限制，可以保留原来的名称和徽标。一方面，这是对 Debian 修改的认可，也是对 Debian 信任的体现。另一方面，该软件显然没有从非自由组件中清除，现在已成为发行版的一部分。如果此时 Debian 已被列入免费 GNU/Linux 发行版列表，那么自由软件基金会会毫不犹豫地指出这一点。
|
||||
|
||||
### 结论
|
||||
|
||||
数字世界中的自由与现实世界中的自由同样重要。在这篇文章中，我试图揭示 Debian 最重要的特性之一——开发与用户自由相关的发行版。开发人员花费额外的时间从软件中清理非自由组件，并且以 Debian 为技术基础的数十个发行版继承了它的工作，并由此获得了一部分自由。
|
||||
|
||||
另外，我想分享一个简单的观察，即自由并不像乍看起来那么简单，人们自然会去追问什么是真正的自由和什么不是。由于 Firefox 的存在，Debian 现在不能被称为自由的 GNU/Linux 发行版。但从 2011 年，当 Debian 终于开始清理内核以及发行版的其他组件时，直到 2016 年 Firefox 成为发行版的一部分，自由软件基金会出于纯粹的意识形态原因并不认为该发行版是自由的：原因是 Debian 大大简化了非自由软件的安装……现在轮到你权衡所有的争论并决定是否将 GNU/Linux 发行版视为自由的了。
|
||||
|
||||
祝你好运！并尽可能保持自由。
|
||||
|
||||
由 Evgeny Golyshev 为 [Cusdeb.com](4) 撰写
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://news.itsfoss.com/fsf-does-not-consider-debian-a-free-distribution/
|
||||
|
||||
作者：[Abhishek][a]
|
||||
选题：[lkxed][b]
|
||||
译者：[Chao-zhi](https://github.com/Chao-zhi)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
||||
[a]: https://news.itsfoss.com/author/root/
|
||||
[b]: https://github.com/lkxed
|
||||
[1]: https://news.itsfoss.com/wp-content/uploads/2022/05/why-fsf-doesnt-consider-debian-a-free-software-1200-%C3%97-675px.png
|
||||
[2]: https://gnu.org/distros/free-distros.en.html
|
||||
[3]: https://debian.org/social_contract
|
||||
[4]: https://wiki.cusdeb.com/Essays:Why_the_FSF_does_not_consider_Debian_as_a_free_distribution/en
|
||||
@ -0,0 +1,181 @@
|
||||
[#]: collector: (lujun9972)
|
||||
[#]: translator: (CoWave-Fall)
|
||||
[#]: reviewer: ( )
|
||||
[#]: publisher: ( )
|
||||
[#]: url: ( )
|
||||
[#]: subject: (31 open source text editors you need to try)
|
||||
[#]: via: (https://opensource.com/article/21/2/open-source-text-editors)
|
||||
[#]: author: (Seth Kenlon https://opensource.com/users/seth)
|
||||
|
||||
您可以尝试的 31 个开源文本编辑器
|
||||
======
|
||||
|
||||
正在寻找新的文本编辑器？ 这里有 31 个选项可供您考虑。
|
||||
![open source button on keyboard][1]
|
||||
|
||||
计算机是基于文本的，因此您使用它们做的事情越多，您可能就越需要文本编辑应用程序。 您在文本编辑器上花费的时间越多，您就越有可能对您您使用的编辑器提出更多的要求。
|
||||
|
||||
如果您正在寻找一个好的文本编辑器，您会发现 Linux 可以提供很多。 无论您是想在终端、桌面还是在云端工作，您都可以试一试。您可以每天一款编辑器，连续着试一个月（或每月试一个，能够试三年）。坚持不懈，您终将找到适合您的完美的编辑器。
|
||||
|
||||
### 与 Vim 相似的编辑器
|
||||
|
||||
![][2]
|
||||
|
||||
* [Vi][3] 通常随着 Linux 各发行版、BSD、Solaris 和 macOS 一起安装。 它是典型的 Unix 文本编辑器，具有编辑模式和超高效的单键快捷键二者的独特组合。 最初的 Vi 编辑器由 Bill Joy 编写（他也是 C shell 的作者）。 Vi 的现代版本，尤其是 Vim，增加了许多特性，包括多级撤消、在插入模式下更好的导航、折叠行、语法高亮、插件支持等等。但它需要学习如何使用（它甚至有自己的教程程序，vimtutor）。
|
||||
* [Kakoune][4] 是一个受 Vim 启发的应用程序，它具有熟悉的简约界面、短键盘快捷键以及独立的编辑和插入模式。 乍一看，它的外观和感觉很像 Vi，但它在设计和功能上有自己独特的风格。 它有一个小彩蛋：具有 Clippy 接口的实现。
|
||||
|
||||
|
||||
|
||||
### emacs 编辑器
|
||||
|
||||
![][5]
|
||||
|
||||
* 从最初的免费 emacs 开始，发展到 GNU 项目（自由软件运动的发起者）的第一批官方应用程序，[GNU Emacs][6] 是一个广受欢迎的文本编辑器。 它非常适合系统管理员、开发人员和日常用户的使用，具有大量功能和近乎无穷无尽的扩展。 一旦您开始使用 Emacs，您可能会发现很难想出一个理由来关闭它，因为它能做的事情非常多！
|
||||
* 如果您喜欢 Emacs 但觉得 GNU Emacs 过于臃肿，那么您可以试试 [Jove][7]。 Jove 是一个基于终端的 emacs 编辑器。 它很容易使用，但是如果您是使用 emacs 一类编辑器的新手，那么 Jove 也是很容易学习的，这要归功于 teajove 命令。
|
||||
* 另一个轻量级的 emacs 编辑器是 [Jed][8]。它的工作流程基于宏。 它与其他编辑器的不同之处在于它使用了 [S-Lang][9]，这是一种类似 C 的脚本语言，它为使用 C 而不是使用 Lisp 的开发人员提供了可扩展的选项。
|
||||
|
||||
|
||||
|
||||
### 交互式编辑器
|
||||
|
||||
![][10]
|
||||
|
||||
* [GNU nano][11] 对基于终端的文本编辑采取了大胆的立场：它提供了一个菜单。是的，这个不起眼的编辑器从 GUI 编辑器那里得到了提示，它告诉用户他们需要按哪个键来执行特定的功能。这是一种令人耳目一新的用户体验，所以难怪 nano 被设置为“用户友好”发行版的默认编辑器，而不是 Vi。
|
||||
* [JOE][12] 基于一个名为 WordStar 的旧文本编辑应用程序。如果您不熟悉 Wordstar，JOE 也可以模仿 Emacs 或 GNU nano。默认情况下，它是介于 Emacs 或 Vi 等相对神秘的编辑器和 GNU Nano 永远在线的冗长信息之间的一个很好的折衷方案（例如，它告诉您如何激活屏幕帮助显示，但默认情况下不启用）。
|
||||
* [e3][13] 是一个优秀的小型文本编辑器，具有五个内置的键盘快捷键方案来模拟 Emacs、Vi、nano、NEdit 和 WordStar。换句话说，无论您习惯使用哪种基于终端的编辑器，您都可能对 e3 感到宾至如归。
|
||||
|
||||
### ed 和更多像 ed 一样的编辑器
|
||||
|
||||
* [ed][14] 行编辑器是 [POSIX][15] 和 Open Group 对基于 Unix 的操作系统的标准定义的一部分。它安装在您遇到的几乎所有 Linux 或 Unix 系统上。它小巧、简洁、一流。
|
||||
* 基于 ed，[Sed][16] 流编辑器因其功能和语法而广受欢迎。大多数 Linux 用户在搜索更新配置文件中的行的最简单和最快的方法时至少会学习一个 sed 命令，但值得仔细研究一下。 Sed 是一个强大的命令，包含许多有用的子命令。更好地了解它，您可能会发现自己打开文本编辑器应用程序的频率要低得多。
|
||||
* 您并不总是需要文本编辑器来编辑文本。 [heredoc][17]（或 Here Doc）系统可在任何 POSIX 终端中使用，允许您直接在打开的终端中输入文本，然后将输入的内容通过管道传输到文本文件中。这不是最强大的编辑体验，但它用途广泛且始终可用。
|
||||
|
||||
|
||||
|
||||
### 极简风格的编辑器
|
||||
|
||||
![][18]
|
||||
|
||||
如果您对一个好的文本编辑器的想法是一个文字处理器（除了没有所有的处理功能）的话，您可能正在寻找这些经典。这些编辑器可让您以最少的干扰和最少的帮助写作和编辑文本。它们提供的功能通常以标记、Markdown 或代码为中心。有些名称遵循某种模式：
|
||||
|
||||
* [Gedit][19] 来自 GNOME 团队；
|
||||
* [medit][20] 有经典的 GNOME 手感；
|
||||
* [Xedit][21] 仅使用最基本的 X11 库；
|
||||
* [jEdit][22] 适用于 Java 爱好者。
|
||||
|
||||
|
||||
|
||||
KDE 用户也类似：
|
||||
|
||||
* [Kate][23] 是一款低调的编辑器，拥有您需要的几乎所有功能；
|
||||
* [KWrite][24] 在看似简单易用的界面中隐藏了大量有用的功能。
|
||||
|
||||
|
||||
|
||||
还有一些适用于其他平台：
|
||||
|
||||
* [Notepad++][25] 是一种流行的 Windows 应用程序，而 Notepadqq 对 Linux 采用了类似的方法；
|
||||
* [Pe][26] 适用于 Haiku OS（90 年代那个古怪的孩子 BeOS 的转世）；
|
||||
* [FeatherPad][27] 是适用于 Linux 的基本编辑器，但对 macOS 和 Haiku 有一些支持。如果您是一名希望移植代码的 Qt 骇客，请务必看一看！
|
||||
|
||||
|
||||
|
||||
### 集成开发环境（IDE）
|
||||
|
||||
![][28]
|
||||
|
||||
文本编辑器和集成开发环境 (IDE) 之间存在相当大的相同之处。 后者实际上只是前者加上许多对于特定代码的添加的功能。 如果您经常使用 IDE，您可能会在扩展管理器中发现一个 XML 或 Markdown 编辑器：
|
||||
|
||||
* [NetBeans][29] 是一个方便 Java 用户的文本编辑器。
|
||||
* [Eclipse][30] 提供了一个强大的编辑套件，其中包含许多扩展，可为您提供所需的工具。
|
||||
|
||||
|
||||
|
||||
### 云端编辑器
|
||||
|
||||
![][31]
|
||||
|
||||
在云端写作？ 当然，您也可以在那里写。
|
||||
|
||||
* [Etherpad][32] 是在网上运行的文本编辑器应用程序。 有独立免费的实例供您使用，或者您也·可以设置自己的实例。
|
||||
* [Nextcloud][33] 拥有蓬勃发展的应用场景，包括内置文本编辑器和具有实时预览功能的第三方 Markdown 编辑器。
|
||||
|
||||
|
||||
|
||||
### 较新的编辑器
|
||||
|
||||
![][34]
|
||||
|
||||
每个人都会有让文本编辑器变得更完美的想法。 因此，几乎每年都会发布新的编辑器。 有些以一种新的、令人兴奋的方式重新实现经典的旧想法，有些对用户体验有独特的看法，还有些则专注于特定的需求。
|
||||
|
||||
* [Atom][35] 是来自 GitHub 的多功能的现代文本编辑器，具有许多扩展和 Git 集成。
|
||||
* [Brackets][36] 是 Adobe 为 Web 开发人员提供的编辑器。
|
||||
* [Focuswriter][37] 旨在通过无干扰全屏模式、可选的打字机音效和精美的配置选项等有用功能帮助您专注于写作。
|
||||
* [Howl][38] 是一个基于 Lua 和 Moonscript 的渐进式动态编辑器。
|
||||
* [Norka][39] 和 [KJots][40] 模仿笔记本，每个文档代表“活页夹”中的“页面”。 您可以通过导出功能从笔记本中取出单个页面。
|
||||
|
||||
|
||||
|
||||
### 自己制作编辑器
|
||||
|
||||
![][41]
|
||||
|
||||
俗话说得好：既然可以编写自己的应用程序，为什么要使用别人的（虽然其实没有这句俗语）？虽然 Linux 有超过 30 个常用的文本编辑器，但是再说一次，开源的一部分乐趣在于能够亲手进行实验。
|
||||
|
||||
如果您正在寻找学习编程的理由，那么制作自己的文本编辑器是一个很好的入门方法。 您可以在大约 100 行代码中实现基础知识，并且您使用它的次数越多，您可能就越会受到启发，进而去学习更多内容，从而进行改进。 准备好开始了吗？ 来吧，去[创建您自己的文本编辑器][42]。
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://opensource.com/article/21/2/open-source-text-editors
|
||||
|
||||
作者：[Seth Kenlon][a]
|
||||
选题：[lujun9972][b]
|
||||
译者：[CoWave-Fall](https://github.com/CoWave-Fall)
|
||||
校对：[校对者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/button_push_open_keyboard_file_organize.png?itok=KlAsk1gx (open source button on keyboard)
|
||||
[2]: https://opensource.com/sites/default/files/kakoune-screenshot.png
|
||||
[3]: https://opensource.com/article/20/12/vi-text-editor
|
||||
[4]: https://opensource.com/article/20/12/kakoune
|
||||
[5]: https://opensource.com/sites/default/files/jed.png
|
||||
[6]: https://opensource.com/article/20/12/emacs
|
||||
[7]: https://opensource.com/article/20/12/jove-emacs
|
||||
[8]: https://opensource.com/article/20/12/jed
|
||||
[9]: https://www.jedsoft.org/slang
|
||||
[10]: https://opensource.com/sites/default/files/uploads/nano-31_days-nano-opensource.png
|
||||
[11]: https://opensource.com/article/20/12/gnu-nano
|
||||
[12]: https://opensource.com/article/20/12/31-days-text-editors-joe
|
||||
[13]: https://opensource.com/article/20/12/e3-linux
|
||||
[14]: https://opensource.com/article/20/12/gnu-ed
|
||||
[15]: https://opensource.com/article/19/7/what-posix-richard-stallman-explains
|
||||
[16]: https://opensource.com/article/20/12/sed
|
||||
[17]: https://opensource.com/article/20/12/heredoc
|
||||
[18]: https://opensource.com/sites/default/files/uploads/gedit-31_days_gedit-opensource.jpg
|
||||
[19]: https://opensource.com/article/20/12/gedit
|
||||
[20]: https://opensource.com/article/20/12/medit
|
||||
[21]: https://opensource.com/article/20/12/xedit
|
||||
[22]: https://opensource.com/article/20/12/jedit
|
||||
[23]: https://opensource.com/article/20/12/kate-text-editor
|
||||
[24]: https://opensource.com/article/20/12/kwrite-kde-plasma
|
||||
[25]: https://opensource.com/article/20/12/notepad-text-editor
|
||||
[26]: https://opensource.com/article/20/12/31-days-text-editors-pe
|
||||
[27]: https://opensource.com/article/20/12/featherpad
|
||||
[28]: https://opensource.com/sites/default/files/uploads/eclipse-31_days-eclipse-opensource.png
|
||||
[29]: https://opensource.com/article/20/12/netbeans
|
||||
[30]: https://opensource.com/article/20/12/eclipse
|
||||
[31]: https://opensource.com/sites/default/files/uploads/etherpad_0.jpg
|
||||
[32]: https://opensource.com/article/20/12/etherpad
|
||||
[33]: https://opensource.com/article/20/12/31-days-text-editors-nextcloud-markdown-editor
|
||||
[34]: https://opensource.com/sites/default/files/uploads/atom-31_days-atom-opensource.png
|
||||
[35]: https://opensource.com/article/20/12/atom
|
||||
[36]: https://opensource.com/article/20/12/brackets
|
||||
[37]: https://opensource.com/article/20/12/focuswriter
|
||||
[38]: https://opensource.com/article/20/12/howl
|
||||
[39]: https://opensource.com/article/20/12/norka
|
||||
[40]: https://opensource.com/article/20/12/kjots
|
||||
[41]: https://opensource.com/sites/default/files/uploads/this-time-its-personal-31_days_yourself-opensource.png
|
||||
[42]: https://opensource.com/article/20/12/31-days-text-editors-one-you-write-yourself
|
||||
@ -7,17 +7,17 @@
|
||||
[#]: publisher: " "
|
||||
[#]: url: " "
|
||||
|
||||
如何在 Ubuntu 22.04 LTS 中安装 Classic GNOME Flashback
|
||||
Ubuntu 22.04 LTS 中安装经典 GNOME Flashback 指南
|
||||
======
|
||||
关于如何在最新的 UBUNTU 22.04 LTS 中安装旧的 Classic GNOME Flashback 的快速指南。
|
||||
关于如何在最新的 UBUNTU 22.04 LTS 中安装旧的经典 GNOME Flashback 的快速指南。
|
||||
|
||||
[GNOME Flashback][1]（又名 classic GNOME）是旧 GNOME 3 shell 的一个分支，它使用早期 GNOME 2 技术的布局和原则。它的速度快如闪电，并且在设计上占用的 CPU 和系统资源非常少。因此，它非常适合可以追溯到几十年前的旧硬件。
|
||||
[GNOME Flashback][1]（又名 classic GNOME）是旧 GNOME 3 shell 的一个分支，它使用早期 GNOME 2 技术的布局和原则。它的速度快如闪电，并且在设计上非常轻量级。因此，它非常适合几十年前的老旧硬件。
|
||||
|
||||
随着带有现代 GNOME 42 的 [Ubuntu 22.04 LTS][2] 的发布，有必要寻找消耗很少系统资源的桌面环境选项。
|
||||
随着带有现代 GNOME 42 的 [Ubuntu 22.04 LTS][2] 的发布，有必要寻找轻量级的桌面环境选项。
|
||||
|
||||
此外，GNOME Flashback 很容易安装在现代 Ubuntu Linux 中，你仍然可以享受 Ubuntu 性能而不必担心 GNOME 42、GTK4、libadwaita 和其他东西。
|
||||
|
||||
### 在 Ubuntu 22.04 LTS 中下载并安装 Classic GNOME Flashback
|
||||
### 在 Ubuntu 22.04 LTS 中下载并安装经典 GNOME Flashback
|
||||
|
||||
按照以下步骤在 Ubuntu 22.04 LTS 中下载并安装经典 GNOME Flashback（Metacity）。
|
||||
|
||||
@ -43,7 +43,7 @@
|
||||
|
||||
### 经典 GNOME Flashback 的特点
|
||||
|
||||
首先，当你登录时，你将体验到传统的 GNOME 技术，该技术已被证明具有良好的生产力并且比今天的技术快得多。
|
||||
首先，当你登录时，你将体验到经典的 GNOME 技术，该技术已被证明具有良好的生产力并且比今天的技术快得多。
|
||||
|
||||
在顶部有旧版面板，左侧是应用菜单，而系统托盘位于桌面的右上方。应用程序菜单显示所有已安装的应用和软件快捷方式，你可以在工作流程中轻松浏览。
|
||||
|
||||
@ -61,7 +61,7 @@
|
||||
|
||||
![Add to panel widgets][3]
|
||||
|
||||
### GNOME Classic 的性能
|
||||
### 经典 GNOME 的性能
|
||||
|
||||
首先，磁盘空间占用极小，即仅安装 61 MB。我的测试使用了大约 28% 的内存，其中大部分被其他进程占用。猜猜是谁？是的，是 snap-store 又名 Ubuntu 软件。
|
||||
|
||||
@ -69,11 +69,11 @@
|
||||
|
||||
![Performance of GNOME Classic in Ubuntu 22.04][3]
|
||||
|
||||
此外，假设你将其与同样使用相同技术的 Ubuntu MATE 进行比较。在这种情况下，它比 MATE 更轻量，因为你不需要任何额外的 MATE 应用及其用于通知、主题和其他补充资源的本机包。
|
||||
此外，假设你将其与同样使用相同技术的 Ubuntu MATE 进行比较。在这种情况下，它比 MATE 更轻量，因为你不需要任何额外的 MATE 应用及其用于通知、主题和其他附加资源的软件包。
|
||||
|
||||
### 结束语
|
||||
|
||||
我希望本指南在你决定在 Ubuntu 22.04 LTS Jammy Jellyfish 中安装 GNOME Classic 之前帮助你获得必要的信息。
|
||||
我希望本指南在你决定在 Ubuntu 22.04 LTS Jammy Jellyfish 中安装经典 GNOME 之前帮助你获得必要的信息。
|
||||
|
||||
* * *
|
||||
|
||||
|
||||
@ -0,0 +1,58 @@
|
||||
[#]: subject: "Five common mistakes when using automation"
|
||||
[#]: via: "https://fedoramagazine.org/five-common-mistakes-when-using-automation/"
|
||||
[#]: author: "Gary Scarborough https://fedoramagazine.org/author/gscarbor/"
|
||||
[#]: collector: "lujun9972"
|
||||
[#]: translator: "geekpi"
|
||||
[#]: reviewer: " "
|
||||
[#]: publisher: " "
|
||||
[#]: url: " "
|
||||
|
||||
使用自动化时的五个常见错误
|
||||
======
|
||||
|
||||
![][1]
|
||||
|
||||
背景图片来自 [“Modern Times”（1936）][2]，[United Artists][3]，公共领域，通过 Wikimedia Commons
|
||||
|
||||
随着自动化扩展到涵盖 IT 的更多方面，越来越多的管理员正在学习自动化技能并应用它们来减轻他们的工作量。自动化可以减轻重复性任务的负担，并为基础设施增加一定程度的一致性。但是，当 IT 工作人员部署自动化时，会出现可能对大大小小的基础设施造成严重破坏的常见错误。在自动化部署中通常会出现五个常见错误。
|
||||
|
||||
### 缺乏测试
|
||||
|
||||
初学者常犯的错误是自动化脚本没有经过全面测试。由于拼写错误或逻辑错误，简单的 shell 脚本可能会对服务器产生不利影响。将该错误乘以基础架构中的服务器数量，你可能会遇到一大堆问题需要清理。在大规模部署之前始终测试你的自动化脚本。
|
||||
|
||||
### 意外的服务器负载
|
||||
|
||||
经常发生的第二个错误是没有预测脚本可能对其他资源施加的系统负载。当目标是十几个服务器时，运行从仓库下载文件或安装包的脚本可能没问题。脚本通常在成百上千台服务器上运行。这种负载可以使支持服务停止或完全崩溃。不要忘记考虑端点影响或设置合理的并发率。
|
||||
|
||||
### 离开脚本
|
||||
|
||||
自动化工具的一种用途是确保符合标准设置。自动化可以轻松确保组中的每台服务器都具有完全相同的设置。如果该组中的服务器需要根据该基线进行更改，同时管理员不了解合规标准，那么可能会出现问题。安装和启用不需要和不想要的服务，从而导致可能的安全问题。
|
||||
|
||||
### 缺乏文档
|
||||
|
||||
管理员的一项固定职责应该是记录他们的工作。由于合同到期、升职或定期员工流动，公司可能会在 IT 部门频繁招聘新员工。公司内的工作组相互隔离也很常见。由于这些原因，重要的是记录哪些自动化已经到位。与用户运行脚本不同，自动化可能会在创建它的人离开组之后继续很长时间。管理员可能会发现自己在其基础设施中面临着来自自动化未经检查的奇怪行为。
|
||||
|
||||
### 缺乏经验
|
||||
|
||||
列表中的最后一个错误是管理员对他们正在自动化的系统不够了解。管理员经常被雇用到他们没有接受过足够培训且没有人可以学习的职位上工作。自 COVID 以来，当公司努力填补空缺时，这一点尤其重要。然后管理员被迫处理他们没有设置并且可能不完全理解的基础设施。这可能会导致非常低效的脚本浪费资源或配置错误的服务器。
|
||||
|
||||
### 结论
|
||||
|
||||
越来越多的管理员正在学习自动化来帮助他们完成日常任务。因此，自动化正被应用于更多的技术领域。希望此列表将有助于防止新用户犯这些错误，并敦促经验丰富的管理员重新评估他们的 IT 策略。自动化旨在减轻重复性任务的负担，而不是为最终用户带来更多工作。
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://fedoramagazine.org/five-common-mistakes-when-using-automation/
|
||||
|
||||
作者：[Gary Scarborough][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://fedoramagazine.org/author/gscarbor/
|
||||
[b]: https://github.com/lujun9972
|
||||
[1]: https://fedoramagazine.org/wp-content/uploads/2022/05/modern-times-816x345.jpg
|
||||
[2]: https://en.wikipedia.org/wiki/Modern_Times_(film)
|
||||
[3]: https://commons.wikimedia.org/wiki/File:Chaplin_-_Modern_Times.jpg
|
||||
Loading…
Reference in New Issue
Block a user