mirror of
https://github.com/LCTT/TranslateProject.git
synced 2026-09-04 04:32:49 +08:00
Merge branch 'LCTT:master' into master
This commit is contained in:
Donkey
GitHub
@@ -1,94 +0,0 @@
|
||||
[#]: subject: "This Flutter-based Unofficial Software Center Might Replace Ubuntu's Official App"
|
||||
[#]: via: "https://news.itsfoss.com/unofficial-flutter-ubuntu-software/"
|
||||
[#]: author: "Sagar Sharma https://news.itsfoss.com/author/sagar/"
|
||||
[#]: collector: "lkxed"
|
||||
[#]: translator: " "
|
||||
[#]: reviewer: " "
|
||||
[#]: publisher: " "
|
||||
[#]: url: " "
|
||||
|
||||
This Flutter-based Unofficial Software Center Might Replace Ubuntu's Official App
|
||||
======
|
||||
Is Canonical planning to replace the Ubuntu software center with a flutter-based app? Maybe, or maybe not.
|
||||
|
||||
![This Flutter-based Unofficial Software Center Might Replace Ubuntu's Official App][1]
|
||||
|
||||
Ubuntu is often considered [one of the best distros for beginners][2], but the default software center (GNOME Software Center) needs more polishing to make it a pleasing experience.
|
||||
|
||||
Why? Well, it's slow and heavy on resources, so most users do not bother using it or just have a bad time with it.
|
||||
|
||||
Yes, it may have improved over the years, but it is still far from a good experience.
|
||||
|
||||
And it looks like contributors from Canonical, and others have teamed up together to work on with a lightweight, flutter-based alternative for the Ubuntu software center!
|
||||
|
||||
Hold on, it is **not an official replacement**. But, I wonder if it is meant to replace Ubuntu Software Center soon? 🤔
|
||||
|
||||
### 🆕 Ubuntu Software Made With Flutter
|
||||
|
||||
![ubuntu software built with flutter][3]
|
||||
|
||||
This implementation of Ubuntu software using Flutter aims to be lightweight, adaptive, and fast, providing a better user experience than the traditional one.
|
||||
|
||||
But the prime factor must be usability, right? Because in the end, you're just going to install the software. And, you want to do it quickly without any hassle.
|
||||
|
||||
When I tried it on my system, I noticed that there is a separate section for Snaps and Deb packages under "**My apps**":
|
||||
|
||||
![separate section for deb and snap packages in ubuntu software][4]
|
||||
|
||||
This should be convenient for dealing with different packages within a single app. After all, this is what I always wanted!
|
||||
|
||||
A unified experience to easily install/manage applications, too much to ask? 🤷
|
||||
|
||||
But what about the app info and installation page? Well, it has been redesigned for good with subtle animations to enhance the experience.
|
||||
|
||||
![app info section in unofficial ubuntu software][5]
|
||||
|
||||
And the adaptive layout works as a cherry on the cake. This is somewhat similar to what elementary OS 7 has in store for us:
|
||||
|
||||
[elementary OS 7 Gears Up to Add Responsive Apps and Port to GTK 4][6]
|
||||
|
||||
So, it looks like a thoughtful implementation for the future, right?
|
||||
|
||||
![adaptive layout in unofficial ubuntu software center][8]
|
||||
|
||||
### Is It Going to Replace Ubuntu Software?
|
||||
|
||||
While the project contributors mark it as an unofficial alternative to Ubuntu Software, I think it is more of an experiment gearing up as a replacement.
|
||||
|
||||
Considering [J-P Nurmi][9], *Senior Engineer @ Canonical* responsible for Flutter on Ubuntu is involved, this is going to be something exciting.
|
||||
|
||||
The only thing we can now do here is "predict". But, it looks like there are more chances of this being official, as things get better with the development.
|
||||
|
||||
**Want to try the flutter-based implementation?**
|
||||
|
||||
You can head to its [GitHub page][10] and follow the build instructions to get it running. Note that it is under heavy development as of now.
|
||||
|
||||
[Download Ubuntu Software][11]
|
||||
|
||||
It works pretty well for something that is in active development.
|
||||
|
||||
*💬 And I hope this replaces by the current software center. What do you think about that? Let me know your thoughts in the comments below!*
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://news.itsfoss.com/unofficial-flutter-ubuntu-software/
|
||||
|
||||
作者：[Sagar Sharma][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/sagar/
|
||||
[b]: https://github.com/lkxed
|
||||
[1]: https://news.itsfoss.com/content/images/size/w1200/2022/09/ubuntu-unofficial-flutter-store.jpg
|
||||
[2]: https://itsfoss.com/best-linux-beginners/
|
||||
[3]: https://news.itsfoss.com/content/images/2022/09/unofficial-ubuntu-software-1.png
|
||||
[4]: https://news.itsfoss.com/content/images/2022/09/snap-and-deb-section-1.png
|
||||
[5]: https://news.itsfoss.com/content/images/2022/09/kdenline-in-ubuntu-software.png
|
||||
[6]: https://news.itsfoss.com/elementary-os-7-dev-updates/
|
||||
[8]: https://news.itsfoss.com/content/images/2022/09/responsive-design-of-ubuntu-software.png
|
||||
[9]: https://twitter.com/jpnurmi
|
||||
[10]: https://github.com/ubuntu-flutter-community/software
|
||||
[11]: https://github.com/ubuntu-flutter-community/software
|
||||
@@ -1,86 +0,0 @@
|
||||
[#]: subject: "Penpot is a Solid Open-Source Figma Alternative to Look Out for!"
|
||||
[#]: via: "https://news.itsfoss.com/penpot-figma-alternative/"
|
||||
[#]: author: "Ankush Das https://news.itsfoss.com/author/ankush/"
|
||||
[#]: collector: "lkxed"
|
||||
[#]: translator: "zjsoftceo"
|
||||
[#]: reviewer: " "
|
||||
[#]: publisher: " "
|
||||
[#]: url: " "
|
||||
|
||||
Penpot is a Solid Open-Source Figma Alternative to Look Out for!
|
||||
======
|
||||
Penpot is a free and open-source solution as an alternative to Figma and similar design tools. What do you think?
|
||||
|
||||
![Penpot is a Solid Open-Source Figma Alternative to Look Out for!][1]
|
||||
|
||||
Adobe is acquiring the popular design tool [Figma][2] for a whopping **$20 billion**.
|
||||
|
||||
As usual, it is the big tech eliminating the competition by acquiring businesses. So, not entirely a piece of exciting news.
|
||||
|
||||
But, **what's exciting** is we came across a free and open-source design tool that gets its inspiration from Figma and does a few things better!
|
||||
|
||||
### Penpot: Free & Open-Source Design Tool in Development
|
||||
|
||||
![Penpot UI][3]
|
||||
|
||||
[Penpot][4] is an open-source project in active development. It is in its beta phase following its launch on [ProductHunt][5] nearly two years ago.
|
||||
|
||||
**Here's what makes Penpot interesting:**
|
||||
|
||||
* Free and open-source (of course).
|
||||
* Option to Self-host.
|
||||
* Cross-platform.
|
||||
* Using SVG as the native format.
|
||||
* Web-based.
|
||||
* Featuring industry-standard features (inspired by Figma).
|
||||
|
||||
You can watch its official video to know the basics of it:
|
||||
|
||||
![Penpot for Beginners][6]
|
||||
|
||||
The major highlight of Penpot is the use of SVG as its native format. With SVG files, you get compatibility with many vector graphics editing tools.
|
||||
|
||||
So you do not get locked down with a proprietary file format that can be accessed using a particular application.
|
||||
|
||||
Penpot gives you the absolute best of open standards.
|
||||
|
||||
The **CEO of Penpot,***Pablo Ruiz-Múzquiz*, mentions more about it:
|
||||
|
||||
So, using SVG as the native format has a lot of advantages!
|
||||
|
||||
At the moment, the project is in its beta stage and constantly improving with plenty of skilled contributors in the project.
|
||||
|
||||
**This can turn out to be the most useful open-source alternative to Figma, breaking out of big tech for design tools.**
|
||||
|
||||
You can self-host it or use the cloud app to test it out. Sign up at its official website to learn and experiment with it.
|
||||
|
||||
You can also check out its [GitHub page][7] to explore more.
|
||||
|
||||
[Penpot][8]
|
||||
|
||||
This also reminds me of [Akira][9], which aimed to be a native Linux app for UI and UX design. It is still in its early development stage, but such efforts are always appreciated when it involves Linux or the open-source initiative.
|
||||
|
||||
*💬 What do you think about Penpot as an open-source alternative to Figma?*
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://news.itsfoss.com/penpot-figma-alternative/
|
||||
|
||||
作者：[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/content/images/size/w1200/2022/09/penpot-opensource-figma-ft.jpg
|
||||
[2]: https://www.figma.com/
|
||||
[3]: https://news.itsfoss.com/content/images/2022/09/penpot-screenshot.jpg
|
||||
[4]: https://penpot.app/
|
||||
[5]: https://www.producthunt.com/products/penpot?utm_source=badge-featured&utm_medium=badge#penpot
|
||||
[6]: https://youtu.be/JozESuPcVpg
|
||||
[7]: https://github.com/penpot/penpot
|
||||
[8]: https://penpot.app/
|
||||
[9]: https://github.com/akiraux/Akira
|
||||
@@ -0,0 +1,52 @@
|
||||
[#]: subject: "AMD’s Open Source Vulkan Graphics Drivers Now Enable Ray Tracing"
|
||||
[#]: via: "https://www.opensourceforu.com/2022/09/amds-open-source-vulkan-graphics-drivers-now-enable-ray-tracing/"
|
||||
[#]: author: "Laveesh Kocher https://www.opensourceforu.com/author/laveesh-kocher/"
|
||||
[#]: collector: "lkxed"
|
||||
[#]: translator: " "
|
||||
[#]: reviewer: " "
|
||||
[#]: publisher: " "
|
||||
[#]: url: " "
|
||||
|
||||
AMD’s Open Source Vulkan Graphics Drivers Now Enable Ray Tracing
|
||||
======
|
||||
*Linux users of RDNA 2 GPUs can use the AMDVLK GPUOpen open source Vulkan driver from AMD.*
|
||||
|
||||
The AMDVLK GPUOpen graphics driver for its Radeon RX 6000 GPUs has improved support for 64-bit ray tracing over the past week. This covers RDNA 2 graphics-enabled APUs as well as desktop/mobility GPUs. Hardware ray tracing is now supported by all AMD Vulkan drivers on all platforms, including Mesa3D RADV, AMDVLK GPUOpen, and AMDGPU-PRO.
|
||||
|
||||
The foundation of the GPURT library is a C++ interface. Depending on its usage and dependencies, the public interface is split up into various header files. Users can learn more on the official GitHub website, which also includes a breakdown of the structure, about the RDNA 2 GPU Ray Tracing Library (GPURT). The most recent AMDVLK GPUOpen v-2022.Q3.4 information is provided below:
|
||||
|
||||
**Updates and new features**
|
||||
|
||||
* Expand Navi2x’s capability for 64-bit ray tracing.
|
||||
* Upgrade Vulkan Headers to version 1.3.225
|
||||
* Game performance optimization, including For Honor and Ashes of the Singularity
|
||||
|
||||
**Issues resolved so far**
|
||||
|
||||
* The dEQP-VK.api.copy and blit..resolve image.whole copy before resolving transfer has a new version CTS failure.
|
||||
* dEQP-VK.pipeline.creation cache control has a CTS warning.
|
||||
* Firefox corruption on Ubuntu 22.04
|
||||
* VulkanInfo crash with pipeline cache deactivated
|
||||
* RGP test kit failure on RX 6800
|
||||
|
||||
The new improvements include the GPU Ray Tracing Library, or GPURT, which will include the construct and sort processing for the Bounding Volume Hierarchy (BVH) seen in ray tracing utilising shaders like HLSL. This library will provide a standard library to improve graphics rendering and introduce more uniformity. DirectX 12 DXR will also work with the new library.
|
||||
|
||||
The description of the GPU Ray Tracing (GPURT) library reads as “a static library (source deliverable) that provides ray tracing-related functionalities for AMD drivers supporting DXR (DirectX 12) and the Vulkan® RT API.” The company’s Platform Abstraction Library is used to build the library (PAL).
|
||||
|
||||
The installation instructions for the most recent AMDVLK GPUOpen v-2022.Q3.4 upgrade are available here for users. Users should back up any relevant data before updating any software, hardware, or drivers in order to avoid losing crucial files. A lot of work has been put into getting the most recent Linux driver ready for AMD, Intel, and NVIDIA technologies, which were all launched in the first quarter of this year.
|
||||
|
||||
A lot of work has been put into getting the most recent Linux driver ready for AMD, Intel, and NVIDIA technologies, which were all launched in the first quarter of this year.
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://www.opensourceforu.com/2022/09/amds-open-source-vulkan-graphics-drivers-now-enable-ray-tracing/
|
||||
|
||||
作者：[Laveesh Kocher][a]
|
||||
选题：[lkxed][b]
|
||||
译者：[译者ID](https://github.com/译者ID)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
||||
[a]: https://www.opensourceforu.com/author/laveesh-kocher/
|
||||
[b]: https://github.com/lkxed
|
||||
@@ -0,0 +1,89 @@
|
||||
[#]: subject: "GNOME Files Introduces Most-Requested Feature: New File Menu"
|
||||
[#]: via: "https://www.debugpoint.com/gnome-files-new-file-document/"
|
||||
[#]: author: "Arindam https://www.debugpoint.com/author/admin1/"
|
||||
[#]: collector: "lkxed"
|
||||
[#]: translator: " "
|
||||
[#]: reviewer: " "
|
||||
[#]: publisher: " "
|
||||
[#]: url: " "
|
||||
|
||||
GNOME Files Introduces Most-Requested Feature: New File Menu
|
||||
======
|
||||
Here’s the “new file” feature in GNOME Files which gives you a new way of creating documents and files. Have a look.
|
||||
|
||||
No more tweaking in the backend. The most anticipated feature of creating a new document / new files via the context menu in Files (aka Nautilus) finally arrives.
|
||||
|
||||
Developed as part of the [Google Summer of Code 2022][1] (by Ignacy Kuchciński), the change was recently reviewed and merged into the main branch of Files.
|
||||
|
||||
### How it looks
|
||||
|
||||
When you right-click on the Files, the context menu has a new option, “New File”.
|
||||
|
||||
![New File Option in Files Context Menu][2]
|
||||
|
||||
The GNOME Files New File option launches an action window, as shown in the below image.
|
||||
|
||||
![GNOME Files New File Action Dialog][3]
|
||||
|
||||
A couple of things happen behind the scenes when it launches the above dialog box.
|
||||
|
||||
You are probably aware that you can create a “Template” folder with templates in your Home directory to easily access commonly used document types. So, Files checks whether you have a Template directory.
|
||||
|
||||
If a template directory with templates is present, you get a list of those document types to create a new document.
|
||||
|
||||
![GNOME Files New File Template Dialog (when some templates present)][4]
|
||||
|
||||
And if you don’t have any templates (which is likely), Files scans your system and shows a list of common file types based on the installed applications in your system.
|
||||
|
||||
For example, Text editor, LibreOffice document types – Spreadsheets, presentations, etc.
|
||||
|
||||
Some other things happen here. The file extension is selected by default when you choose a file type for a New document. That’s a protected label on the file name text box.
|
||||
|
||||
Moreover, if you don’t have any templates or any applications installed, then the Files New Document menu option is not shown at all!
|
||||
|
||||
### Future Roadmap
|
||||
|
||||
The developer also proposed a future enhancement of this feature, extending its functionality to a greater extent.
|
||||
|
||||
When no template is available, the dialog will look like the one below. It will allow you to create files by selecting the applications, including blank files.
|
||||
|
||||
In addition, you can directly launch Software to install some applications which can help you create those respective file types.
|
||||
|
||||
![Long term vision with additional features (Image Credit: GNOEM Team)][5]
|
||||
|
||||
Since this feature is more complex, it may be developed later. There is no timeline as of now.
|
||||
|
||||
### Is this available in Files 43 (via GNOME 43)?
|
||||
|
||||
However, this change requires some additional design review, in my opinion. I feel it’s not complete. For example, when you have templates, you can not create the standard document types (for text, LibreOffice docs) – those two dialog are mutually exclusive. Also, there are some minor bugs which I find.
|
||||
|
||||
Although the feature is [approved and merged][6] at the moment, it could not make it to the [GNOME 43][7] release candidate due to schedule conflicts.
|
||||
|
||||
Hopefully, you can get this in GNOME 44 release next year after a good round of review and testing.
|
||||
|
||||
### Wrapping Up
|
||||
|
||||
Overall, it’s an elegant feature, and I don’t think any other File manager has this advanced design today. Once this FIles New document feature is implemented entirely, it would a nice addition to its excellent set of features.
|
||||
|
||||
So, do you like this new design? Do let me know in the comment box.
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://www.debugpoint.com/gnome-files-new-file-document/
|
||||
|
||||
作者：[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://debugpointnews.com/gsoc-2022/
|
||||
[2]: https://www.debugpoint.com/wp-content/uploads/2022/09/New-File-Option-in-Files-Context-Menu.jpg
|
||||
[3]: https://www.debugpoint.com/wp-content/uploads/2022/09/GNOME-Files-New-Document-Action-Dialog.jpg
|
||||
[4]: https://www.debugpoint.com/wp-content/uploads/2022/09/GNOME-Files-New-Document-Template-Dialog.jpg
|
||||
[5]: https://www.debugpoint.com/wp-content/uploads/2022/09/Long-term-vision-with-additional-features.jpg
|
||||
[6]: https://gitlab.gnome.org/GNOME/nautilus/-/merge_requests/914
|
||||
[7]: https://www.debugpoint.com/gnome-43/
|
||||
@@ -0,0 +1,71 @@
|
||||
[#]: subject: "Loongson is Getting Ready for LoongArch Linux Laptops"
|
||||
[#]: via: "https://news.itsfoss.com/loongson-loongarch-linux-laptops/"
|
||||
[#]: author: "Ankush Das https://news.itsfoss.com/author/ankush/"
|
||||
[#]: collector: "lkxed"
|
||||
[#]: translator: " "
|
||||
[#]: reviewer: " "
|
||||
[#]: publisher: " "
|
||||
[#]: url: " "
|
||||
|
||||
Loongson is Getting Ready for LoongArch Linux Laptops
|
||||
======
|
||||
The Chinese manufacturer is working on a Linux laptop series based on LoongArch processors.
|
||||
|
||||
![Loongson is Getting Ready for LoongArch Linux Laptops][1]
|
||||
|
||||
Don't confuse it with Arch Linux :)
|
||||
|
||||
**LoongArch is a CPU architecture by Loongson Technology.**
|
||||
|
||||
Recently, Loongson added the initial support for LoongArch CPU architecture in [Linux Kernel 5.19][2].
|
||||
|
||||
If you are curious, **LoongArch has similar attributes to RISC-V**. You can also call it a new RISC ISA (Instruction Set Architecture).
|
||||
|
||||
Want more technical details? The Linux Kernel's [documentation][3] is your friend.
|
||||
|
||||
While it is not popular, a new CPU architecture support is always welcome and opens up various opportunities with new hardware.
|
||||
|
||||
### Chinese Manufacturer Gearing Up for Linux Laptops
|
||||
|
||||
It seems like Loongson Technology, the computer hardware manufacturer responsible for the LoongArch CPU architecture, is preparing new Linux laptops featuring the same.
|
||||
|
||||
![[LoongArch] Unbox THE NEWEST LOONGSON LAPTOP —— Loongson 3A5000][4]
|
||||
|
||||
**What this means**: You will soon get to see LoongArch laptops running Linux out-of-the-box.
|
||||
|
||||
Of course, considering it as a Chinese vendor, it is unlikely to be available everywhere. But you never know, right?
|
||||
|
||||
Lenovo and Huawei are some of the most prominent Chinese manufacturers producing Linux laptops. Considering the market for Linux laptops is not as crowded, Loongson coming up with its product offering sounds good.
|
||||
|
||||
[13 Places to Buy Linux Laptops in 2021][5]
|
||||
|
||||
**Loongson adding a driver to Linux:**They are adding code to the Linux Kernel, i.e., in the form of an ACPI-based "**loongson-laptop**" driver, as spotted by [Phoronix][7]. This could be a part of the upcoming [Linux 6.0 release][8].
|
||||
|
||||
The code addition also mentions that some are derived from Thinkpad's ACPI configuration, which should not be surprising.
|
||||
|
||||
**Joining the RISC-V race early**: Considering much hope for RISC-V computers as the next major leap in computing, I think Loongson wants to compete in that space, preparing its similar CPU architecture for the real world.
|
||||
|
||||
Loongson is not famous for its laptops or their performance in them. So, it will be interesting to see how it unfolds shortly.
|
||||
|
||||
💬 *What do you think about LoongArch Linux laptops? Let me know your thoughts in the comments.*
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://news.itsfoss.com/loongson-loongarch-linux-laptops/
|
||||
|
||||
作者：[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/content/images/size/w1200/2022/09/loongsoon-loongarch-linux-laptops.jpg
|
||||
[2]: https://news.itsfoss.com/linux-kernel-5-19-release/
|
||||
[3]: https://docs.kernel.org/loongarch/introduction.html
|
||||
[4]: https://youtu.be/a5KZRvSgzUc
|
||||
[5]: https://itsfoss.com/get-linux-laptops/
|
||||
[7]: https://www.phoronix.com/news/Loongson-LoongArch-Laptop-Prep
|
||||
[8]: https://news.itsfoss.com/linux-kernel-6-0-reveal/
|
||||
@@ -1,192 +0,0 @@
|
||||
[#]: subject: "20 Facts About Linus Torvalds, the Creator of Linux and Git"
|
||||
[#]: via: "https://itsfoss.com/linus-torvalds-facts/"
|
||||
[#]: author: "Abhishek Prakash https://itsfoss.com/"
|
||||
[#]: collector: "lkxed"
|
||||
[#]: translator: "gpchn"
|
||||
[#]: reviewer: " "
|
||||
[#]: publisher: " "
|
||||
[#]: url: " "
|
||||
|
||||
20 Facts About Linus Torvalds, the Creator of Linux and Git
|
||||
======
|
||||
*Brief: Some known, some lesser known – here are 20 facts about the Linus Torvalds, creator of the Linux kernel.*
|
||||
|
||||
![Linus Torvalds, creator of Linux and Git][1]
|
||||
|
||||
[Linus Torvalds][2], a Finnish student, developed a Unix-like operating system while he was doing his masters in the year 1991. Since then, it’s sparked a revolution: today it powers most of the web, many embedded devices and every one of the [top 500 supercomputers][3].
|
||||
|
||||
I’ve already written about some less known [facts about Linux][4]. This article is not about Linux. It’s about its creator, Linus Torvalds.
|
||||
|
||||
I learned a number of things about Torvalds by reading his biography [Just for Fun][5]. If you’re interested, you can [order a copy of the biography from Amazon][6]. (This is an [affiliate][7] link.)
|
||||
|
||||
### 20 Interesting facts about Linus Torvalds
|
||||
|
||||
You’ll probably already know some of these facts about Linus but the chances are that you’ll learn some new facts about him by reading this.
|
||||
|
||||
#### 1. Named after a Nobel prize winner
|
||||
|
||||
Linus Benedict Torvalds was born on December 28th 1969 in Helsinki. He comes from a family of journalists. His father [Nils Torvalds][11] is a Finnish politician and a likely candidate for president in future elections.
|
||||
|
||||
He was named after [Linus Pauling][12], a double Nobel prize winner in Chemistry and Peace.
|
||||
|
||||
#### 2. All the Torvalds in the world are relatives
|
||||
|
||||
While you may find several people with the name Linus, you won’t find many people with the name Torvalds – because the ‘correct’ spelling is actually Torvald (without the s). His grandfather changed his name from Torvald to Torvalds, adding an ‘s’ at the end. And thus the Torvalds dynasty (if I can call it that) began.
|
||||
|
||||
Since it’s such an unusual surname, there are hardly 30 Torvalds in the world and they’re all relatives, claims Linus Torvalds in his biography.
|
||||
|
||||
![Linus Torvalds with sister Sara Torvalds][13]
|
||||
|
||||
#### 3. Commodore Vic 20 was his first computer
|
||||
|
||||
At the age of 10, Linus started writing programs in BASIC on his maternal grandfather’s Commodore Vic 20. This is when he discovered his love for computers and programming.
|
||||
|
||||
#### 4. Second Lieutenant Linus Torvalds
|
||||
|
||||
Though he preferred to spend time on computers rather than in athletic activities, he had to attend compulsory military training. He held the rank of Second Lieutenant.
|
||||
|
||||
#### 5. He created Linux because he didn’t have money for UNIX
|
||||
|
||||
In early 1991, unhappy with [MS-DOS][14] and [MINIX][15], Torvalds wanted to buy a UNIX system. Luckily for us, he didn’t have enough money. So he decided to make his own clone of UNIX, from scratch.
|
||||
|
||||
#### 6. Linux could have been called Freax
|
||||
|
||||
In September ’91, Linus announced Linux (standing for ‘Linus’s MINIX’) and encouraged his colleagues to use its source code for wider distribution.
|
||||
|
||||
Linus thought that the name Linux was too egotistical. He wanted to change it to Freax (based on free, freak and MINIX), but his friend Lemmarke had already created a directory called Linux on his FTP server. And thus the name Linux continued.
|
||||
|
||||
#### 7. Linux was his main project at University
|
||||
|
||||
“Linux: A Portable Operating System” was the title of his thesis for his M.Sc.
|
||||
|
||||
#### 8. He married his student
|
||||
|
||||
In 1993, when he was teaching at the University of Helsinki, he gave the task of composing email as homework to the students. Yeah, composing emails were a big deal back then.
|
||||
|
||||
A female student named Tove Monni completed the task by sending him an email asking him out on a date. He accepted and three years later the first of their three daughters was born.
|
||||
|
||||
Shall I say he started the internet dating trend? Hmm … nah! Let’s leave it there ;)
|
||||
|
||||
![Linus Torvalds with his wife Tove Monni Torvalds][16]
|
||||
|
||||
#### 9. Linus has an asteroid named after him
|
||||
|
||||
He has numerous awards to his name, including an asteroid named [9793 Torvalds][17].
|
||||
|
||||
#### 10. Linus had to battle for the trademark of Linux
|
||||
|
||||
Linux is a trademark registered with Linus Torvalds. Torvalds didn’t care about the trademark initially, but in August 1994, a William R. Della Croce, Jr. registered the Linux trademark and started demanding royalties from Linux developers. Torvalds sued him in return and in 1997, the case was settled.
|
||||
|
||||
![Who is Linus Torvalds? Know about him in 2 minutes!][18]
|
||||
|
||||
#### 11. Steve Jobs wanted him to work on Apple’s macOS
|
||||
|
||||
In 2000, Apple’s founder [Steve Jobs invited him to work on Apple’s macOS][19]. Linus refused the lucrative offer and continued to work on the Linux kernel.
|
||||
|
||||
#### 12. Linus also created Git
|
||||
|
||||
Most people know Linus Torvalds for creating the Linux kernel. But he also created [Git][20], a version control system that is extensively used in software development worldwide.
|
||||
|
||||
Till 2005, (then) proprietary service [BitKeeper][21] was used for Linux kernel development. When Bitkeeper shut down its free service, Linus Torvalds created Git on his own because none of the other version control systems met his needs.
|
||||
|
||||
#### 13. Linus hardly codes these days
|
||||
|
||||
Though Linus works full time on the Linux kernel, he hardly writes any code for it anymore. In fact, most of the code in the Linux kernel is by contributors from around the world. He ensures that things go fine at each release with the help of kernel maintainers.
|
||||
|
||||
#### 14. Torvalds hates C++
|
||||
|
||||
Linus Torvalds has a strong [dislike for the C++ programming language][22]. He has been very vocal about it. He jokes that the Linux kernel compiles faster than a C++ program.
|
||||
|
||||
#### 15. Even Linus Torvalds found Linux difficult to install (you can feel good about yourself now)
|
||||
|
||||
A few years ago, Linus told that [he found Debian difficult to install][23]. He is [known to be using Fedora][24] on his main workstation.
|
||||
|
||||
#### 16. He loves scuba diving
|
||||
|
||||
Linus Torvalds loves scuba diving. He even created [Subsurface][25], a dive logging tool for scuba divers. You’ll be surprised that sometimes he even answers general questions on its forum.
|
||||
|
||||
![Linus Torvalds in Scuba Gear][26]
|
||||
|
||||
#### 17. The foul-mouthed Torvalds has improved his behavior
|
||||
|
||||
Torvalds is known for using [mild expletives][27] on the Linux kernel mailing list. This has been criticized by some in the industry. However, it would be difficult to criticize his banter of “[F**k you, NVIDIA][28]” as it prompted better support for the Linux kernel from NVIDIA.
|
||||
|
||||
In 2018, [Torvalds took a break from Linux kernel development to improve his behavior][29]. This was done just before he signed the controversial [code of conduct for Linux kernel developers][30].
|
||||
|
||||
![Linus Torvalds Middle finger to Nvidia : Fuck You Nvidia][31]
|
||||
|
||||
#### 18. He is too shy to speak in public
|
||||
|
||||
Linus doesn’t feel comfortable with public speaking. He doesn’t attend many events. And when he does, he prefers to sit down and be interviewed by the host. This is his favorite way of doing a public talk.
|
||||
|
||||
#### 19. Not a social media buff
|
||||
|
||||
[Google Plus][32] is the only social media platform he has used. He even spent some time [reviewing gadgets][33] there in his free time. Google Plus is now discontinued so he has no other social media accounts.
|
||||
|
||||
#### 20. Torvalds is settled in the USA
|
||||
|
||||
Linus moved to the US in 1997 and settled there with his wife Tove and their three daughters. He became a US citizen in 2010. At present, he works full-time on the Linux kernel as part of the [Linux Foundation][34].
|
||||
|
||||
It’s difficult to say what the net worth of Linus Torvalds is or how much Linus Torvalds earns because this information has never been made public.
|
||||
|
||||
![Tove and Linus Torvalds with their daughters Patricia, Daniela and Celeste][35]
|
||||
|
||||
Picture credit: [opensource.com][36]
|
||||
|
||||
If you’re interested in learning more about the early life of Linus Torvalds, I recommend reading his biography entitled [Just for Fun][37].
|
||||
|
||||
*Disclaimer: Some of the images here have been taken from the internet. I do not own the copyright to the images. I also do not intend to invade the privacy of the Torvalds family with this article.*
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://itsfoss.com/linus-torvalds-facts/
|
||||
|
||||
作者：[Abhishek Prakash][a]
|
||||
选题：[lkxed][b]
|
||||
译者：[译者ID](https://github.com/译者ID)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
||||
[a]: https://itsfoss.com/
|
||||
[b]: https://github.com/lkxed
|
||||
[1]: https://itsfoss.com/wp-content/uploads/2017/12/Linus-Torvalds-featured-800x450.png
|
||||
[2]: https://en.wikipedia.org/wiki/Linus_Torvalds
|
||||
[3]: https://itsfoss.com/linux-runs-top-supercomputers/
|
||||
[4]: https://itsfoss.com/facts-linux-kernel/
|
||||
[5]: https://www.amazon.com/dp/0066620732?tag=AAWP_PLACEHOLDER_TRACKING_ID
|
||||
[6]: https://www.amazon.com/dp/0066620732?tag=AAWP_PLACEHOLDER_TRACKING_ID
|
||||
[7]: https://itsfoss.com/affiliate-policy/
|
||||
[8]: https://www.amazon.com/dp/0066620732?tag=AAWP_PLACEHOLDER_TRACKING_ID
|
||||
[9]: https://www.amazon.com/dp/0066620732?tag=AAWP_PLACEHOLDER_TRACKING_ID
|
||||
[10]: https://www.amazon.com/dp/0066620732?tag=AAWP_PLACEHOLDER_TRACKING_ID
|
||||
[11]: https://en.wikipedia.org/wiki/Nils_Torvalds
|
||||
[12]: https://en.wikipedia.org/wiki/Linus_Pauling
|
||||
[13]: https://itsfoss.com/wp-content/uploads/2017/12/Linus_and_sara_Torvalds.jpg
|
||||
[14]: https://en.wikipedia.org/wiki/MS-DOS
|
||||
[15]: https://www.minix3.org/
|
||||
[16]: https://itsfoss.com/wp-content/uploads/2017/12/Linus_torvalds-wife-800x533.jpg
|
||||
[17]: http://enacademic.com/dic.nsf/enwiki/1928421
|
||||
[18]: https://youtu.be/eE-ovSOQK0Y
|
||||
[19]: https://www.macrumors.com/2012/03/22/steve-jobs-tried-to-hire-linux-creator-linus-torvalds-to-work-on-os-x/
|
||||
[20]: https://en.wikipedia.org/wiki/Git
|
||||
[21]: https://www.bitkeeper.org/
|
||||
[22]: https://lwn.net/Articles/249460/
|
||||
[23]: https://www.youtube.com/watch?v=qHGTs1NSB1s
|
||||
[24]: https://plus.google.com/+LinusTorvalds/posts/Wh3qTjMMbLC
|
||||
[25]: https://subsurface-divelog.org/
|
||||
[26]: https://itsfoss.com/wp-content/uploads/2017/12/Linus_Torvalds_in_SCUBA_gear.jpg
|
||||
[27]: https://www.theregister.co.uk/2016/08/26/linus_torvalds_calls_own_lawyers_nasty_festering_disease/
|
||||
[28]: https://www.youtube.com/watch?v=_36yNWw_07g
|
||||
[29]: https://itsfoss.com/torvalds-takes-a-break-from-linux/
|
||||
[30]: https://itsfoss.com/linux-code-of-conduct/
|
||||
[31]: https://itsfoss.com/wp-content/uploads/2012/09/Linus-Torvalds-Fuck-You-Nvidia.jpg
|
||||
[32]: https://plus.google.com/+LinusTorvalds
|
||||
[33]: https://plus.google.com/collection/4lfbIE
|
||||
[34]: https://www.linuxfoundation.org/
|
||||
[35]: https://itsfoss.com/wp-content/uploads/2017/12/patriciatorvalds.jpg
|
||||
[36]: https://opensource.com/life/15/8/patricia-torvalds-interview
|
||||
[37]: https://www.amazon.com/dp/0066620732?tag=AAWP_PLACEHOLDER_TRACKING_ID
|
||||
[38]: https://www.amazon.com/dp/0066620732?tag=AAWP_PLACEHOLDER_TRACKING_ID
|
||||
[39]: https://www.amazon.com/dp/0066620732?tag=AAWP_PLACEHOLDER_TRACKING_ID
|
||||
[40]: https://www.amazon.com/dp/0066620732?tag=AAWP_PLACEHOLDER_TRACKING_ID
|
||||
94
sources/talk/20220919 I got my first pull request merged!.md
Normal file
94
sources/talk/20220919 I got my first pull request merged!.md
Normal file
@@ -0,0 +1,94 @@
|
||||
[#]: subject: "I got my first pull request merged!"
|
||||
[#]: via: "https://opensource.com/article/22/9/first-pull-request-merged"
|
||||
[#]: author: "Oluwaseun https://opensource.com/users/jhhornn"
|
||||
[#]: collector: "lkxed"
|
||||
[#]: translator: " "
|
||||
[#]: reviewer: " "
|
||||
[#]: publisher: " "
|
||||
[#]: url: " "
|
||||
|
||||
I got my first pull request merged!
|
||||
======
|
||||
Experience the joy that contributing to open source brings.
|
||||
|
||||
![Dandelion zoomed in][1]
|
||||
|
||||
Image by: Photo by Rob Tiller, CC BY-SA 4.0
|
||||
|
||||
Words cannot express my joy when I got the notification about the merge below, and I owe it to my current engineering school, [AltSchool Africa][2].
|
||||
|
||||
![successful merge message][3]
|
||||
|
||||
Before this, I had been introduced to open source many times, told about its importance in the tech space, and even attended open source conferences (e.g., OSCAFest). I had all the instant excitement to start, but imposter syndrome set in on opening GitHub to create something.
|
||||
|
||||
Fast forward to Monday, the 8th of August, 2022, when I watched Bolaji's video on contributing to open source. I felt pumped again, but I wanted to apply what I learned, so I noted some steps.
|
||||
|
||||
The steps:
|
||||
|
||||
1. I made up my mind I was going to contribute to a project.
|
||||
2. I was focused on a site ([good first issue][4]) to pick my first project from, which I filtered to suit my skill level. I kept opening the next page till I found one.
|
||||
3. I made sure I was equipped with the required [Git and GitHub][5] knowledge to complete the project.
|
||||
|
||||
### The project
|
||||
|
||||
After long hours searching for projects, I finally found one titled, [Ensure no missing alt attributes][6]. I was to give descriptive alt values to images from the site. Alt values in images help to improve the accessibility of the site such that screen readers can provide a detailed description of the image to, say, a visually impaired person. Easy right? Yes, but if I didn't make up my mind to get the first contribution, I wouldn't find it, and open source would continue to be a myth to me.
|
||||
|
||||
I was still pumped until I discovered it was from [MDN][7]. Wait, MDN? As in Mozilla developer? Will they merge my contribution even with how seemingly easy it looks? [Imposter syndrome][8] set in.
|
||||
|
||||
Upon checking the issue, I saw that people were already contributing. I summoned my courage and started reading about it. Taking my time to read and understand the project and how I needed to approach the issue was another challenge I had to overcome.
|
||||
|
||||
The project is as easy as you try to understand it.
|
||||
|
||||
So, I picked two images to begin with. I gave alt values to them, committed my changes, then made a pull request. The time between when I made the pull request and when I got the approval mail was full of self-doubts. Should I close the pull request? This is MDN. Well, it's not coding... What if I don't get merged? I might never contribute again. All it took to clear all of the doubts were the emails I got from my reviewer below:
|
||||
|
||||
![Email of approved pull request][9]
|
||||
|
||||
![mail showing that pull request has been merged][10]
|
||||
|
||||
![congratulatory mail on contributing and merging of pull request][11]
|
||||
|
||||
I was indeed delighted, and this inspired me to check for more. It gave me the courage I needed to request additional issues to solve.
|
||||
|
||||
![Mail of issue assignment][12]
|
||||
|
||||
### Summary
|
||||
|
||||
A few lessons I'd love you to take home from this article are:
|
||||
|
||||
* Open source is for all. Do you see that typo on that site you just visited? You helping to correct it is a way of contributing.
|
||||
* No skillset is too small. A basic understanding of HTML was what I needed to contribute.
|
||||
* Only you can stop yourself from contributing.
|
||||
* The first contribution is all you need to get the ball rolling.
|
||||
|
||||
I hope you have been able to pick something from my story and apply it today. This is another space I'd like to keep contributing to, so see you in my next article, and happy open sourcing!
|
||||
|
||||
*[This article originally appeared on I got my first Pull Request merged! and is republished with permission.][13]*
|
||||
|
||||
Image by: (Awosise Oluwaseun, CC BY-SA 4.0)
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://opensource.com/article/22/9/first-pull-request-merged
|
||||
|
||||
作者：[Oluwaseun][a]
|
||||
选题：[lkxed][b]
|
||||
译者：[译者ID](https://github.com/译者ID)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
||||
[a]: https://opensource.com/users/jhhornn
|
||||
[b]: https://github.com/lkxed
|
||||
[1]: https://opensource.com/sites/default/files/dandelion_zoom.jpg
|
||||
[2]: https://www.altschoolafrica.com/
|
||||
[3]: https://opensource.com/sites/default/files/2022-09/successfulmerge.png
|
||||
[4]: https://goodfirstissues.com/
|
||||
[5]: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/getting-started/about-collaborative-development-models
|
||||
[6]: https://github.com/mdn/content/issues/19334
|
||||
[7]: https://developer.mozilla.org/en-US/
|
||||
[8]: https://opensource.com/article/20/9/imposter-syndrome
|
||||
[9]: https://opensource.com/sites/default/files/2022-09/approved.png
|
||||
[10]: https://opensource.com/sites/default/files/2022-09/merged_0.png
|
||||
[11]: https://opensource.com/sites/default/files/2022-09/thanks.png
|
||||
[12]: https://opensource.com/sites/default/files/2022-09/next.png
|
||||
[13]: https://dev.to/jhhornn/i-got-my-first-pull-request-merged-3ei9
|
||||
@@ -0,0 +1,85 @@
|
||||
[#]: subject: "Security buzzwords to avoid and what to say instead"
|
||||
[#]: via: "https://opensource.com/article/22/9/security-buzzword-alternatives"
|
||||
[#]: author: "Seth Kenlon https://opensource.com/users/seth"
|
||||
[#]: collector: "lkxed"
|
||||
[#]: translator: " "
|
||||
[#]: reviewer: " "
|
||||
[#]: publisher: " "
|
||||
[#]: url: " "
|
||||
|
||||
Security buzzwords to avoid and what to say instead
|
||||
======
|
||||
Consider these thoughtful approaches to define what security really means in your open source project.
|
||||
|
||||
![Lock][1]
|
||||
|
||||
Image by: JanBaby, via Pixabay CC0.
|
||||
|
||||
Technology is a little famous for coming up with "buzzwords." Other industries do it, too, of course. "Story-driven" and "rules light" tabletop games are a big thing right now, "deconstructed" burgers and burritos are a big deal in fine dining. The problem with buzzwords in tech, though, is that they potentially actually affect your life. When somebody calls an application "secure," to influence you to use their product, there's an implicit promise being made. "Secure" must mean that something's secure. It's safe for you to use and trust. The problem is, the word "secure" can actually refer to any number of things, and the tech industry often uses it as such a general term that it becomes meaningless.
|
||||
|
||||
Because "secure" can mean both so much and so little, it's important to use the word "secure" carefully. In fact, it's often best not to use the word at all, and instead, just say what you actually mean.
|
||||
|
||||
### When "secure" means encrypted
|
||||
|
||||
Sometimes "secure" is imprecise shorthand for *encrypted*. In this context, "secure" refers to some degree of difficulty for outside observers to eavesdrop on your data.
|
||||
|
||||
**Don't say this:** "This website is resilient and secure."
|
||||
|
||||
That sounds pretty good! You're probably imagining a website that has several options for 2-factor authentication, zero-knowledge data storage, and steadfast anonymity policies.
|
||||
|
||||
**Say this instead:** "This website has a 99% uptime guarantee, and its traffic is encrypted and verifiable with SSL."
|
||||
|
||||
Not only is the intent of the promise clear now, it also explains how "secure" is achieved (it uses SSL) and what the scope of "secure" is.
|
||||
|
||||
Note that there's explicitly no promise here about privacy or anonymity.
|
||||
|
||||
### When "secure" means restricted access
|
||||
|
||||
Sometimes the term "secure" refers to application or device access. Without clarification, "secure" could mean anything from the useless *security by obscurity* model, to a simple htaccess password, to biometric scanners.
|
||||
|
||||
**Don't say this:** "We've secured the system for your protection."
|
||||
|
||||
**Say this instead:** "Our system uses 2-factor authentication."
|
||||
|
||||
### When "secure" means data storage
|
||||
|
||||
The term "secure" can also refer to the way your data is stored on a server or a device.
|
||||
|
||||
**Don't say this:** "This device stores your data with security in mind."
|
||||
|
||||
**Say this instead:** "This device uses full disk encryption to protect your data."
|
||||
|
||||
When remote storage is involved, "secure" may instead refer to who has access to stored data.
|
||||
|
||||
**Don't say this:** "Your data is secure."
|
||||
|
||||
**Say this instead:** "Your data is encrypted using PGP, and only you have the private key."
|
||||
|
||||
### When "secure" means privacy
|
||||
|
||||
These days, the term "privacy" is almost as broad and imprecise as "security." On one hand, you might think that "secure" must mean "private," but that's true only when "secure" has been defined. Is something private because it has a password barrier to entry? Or is something private because it's been encrypted and only you have the keys? Or is it private because the vendor storing your data knows nothing about you (aside from an IP address?) It's not enough to declare "privacy" any more than it is to declare "security" without qualification.
|
||||
|
||||
**Don't say this:** "Your data is secure with us."
|
||||
|
||||
**Say this instead:** "Your data is encrypted with PGP, and only you have the private key. We require no personal data from you, and can only identify you by your IP address."
|
||||
|
||||
Some sites make claims about how long IP addresses are retained in logs, and promises about never surrendering data to authorities without warrants, and so on. Those are beyond the scope of technological "security," and have everything to do with trust, so don't confuse them for technical specifications.
|
||||
|
||||
### Say what you mean
|
||||
|
||||
Technology is a complex topic with a lot of potential for confusion. Communication is important, and while shorthand and jargon can be useful in some settings, generally it's better to be precise. When you're proud of the "security" of your project, don't generalize it with a broad term. Make it clear to others what you're doing to protect your users, and make it equally clear what you consider out of scope, and communicate these things often. "Security" is a great feature, but it's a broad one, so don't be afraid to brag about the specifics.
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://opensource.com/article/22/9/security-buzzword-alternatives
|
||||
|
||||
作者：[Seth Kenlon][a]
|
||||
选题：[lkxed][b]
|
||||
译者：[译者ID](https://github.com/译者ID)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
||||
[a]: https://opensource.com/users/seth
|
||||
[b]: https://github.com/lkxed
|
||||
[1]: https://opensource.com/sites/default/files/lead-images/security-lock-password.jpg
|
||||
@@ -1,140 +0,0 @@
|
||||
[#]: subject: "Connect to WiFi Using Terminal in Arch Linux and Other Distros"
|
||||
[#]: via: "https://www.debugpoint.com/connect-wifi-terminal-linux/"
|
||||
[#]: author: "Arindam https://www.debugpoint.com/author/admin1/"
|
||||
[#]: collector: "lkxed"
|
||||
[#]: translator: "geekpi"
|
||||
[#]: reviewer: " "
|
||||
[#]: publisher: " "
|
||||
[#]: url: " "
|
||||
|
||||
Connect to WiFi Using Terminal in Arch Linux and Other Distros
|
||||
======
|
||||
This quick guide explains the steps you need to set up and connect to WiFi using a terminal in Arch Linux and other distros.
|
||||
|
||||
This guide is ideal for those scenarios where you are stuck with a terminal without any GUI, and no other wired internet connectivity is available. These steps help you to manually detect the wireless card, and device and connect to the WiFi hotspot with password authentication via terminal.
|
||||
|
||||
This guide uses [iwd][1] (Net Wireless Daemon) to connect to WiFi via a terminal.
|
||||
|
||||
### Connect to WiFi Using Terminal in Arch Linux and Other Distros
|
||||
|
||||
#### 1. Setup iwd
|
||||
|
||||
The `iwd` package comes with three main modules:
|
||||
|
||||
**iwctl** : The wireless client**iwd**: The Daemon**iwmon** : Monitoring tool
|
||||
|
||||
On the terminal type –
|
||||
|
||||
```
|
||||
iwctl
|
||||
```
|
||||
|
||||
![iwctl Prompt][2]
|
||||
|
||||
If you get a command not found, then you need to download the package from [here][3].
|
||||
|
||||
So get help from any other system/laptop with an internet connection to download and install the package via mounting the USB.
|
||||
|
||||
Alternatively, if you have a USB dongle with the internet, then plugin that into your system. And install via the below commands.
|
||||
|
||||
The USB dongle should work out of the box in Arch and most Linux systems today to connect to the internet.
|
||||
|
||||
**Arch**
|
||||
|
||||
```
|
||||
pacman -S iwd
|
||||
```
|
||||
|
||||
**Debian, Ubuntu, and other similar distributions**
|
||||
|
||||
```
|
||||
sudo apt-get install iwd
|
||||
```
|
||||
|
||||
**Fedora**
|
||||
|
||||
```
|
||||
sudo dnf install iwd
|
||||
```
|
||||
|
||||
If you get an `iwctl` prompt (like below), then proceed to the next step.
|
||||
|
||||
#### 2. Configure
|
||||
|
||||
Run the below command to get your system’s **wireless device name**.
|
||||
|
||||
```
|
||||
device list
|
||||
```
|
||||
|
||||
![iwctl – device list][4]
|
||||
|
||||
To **get the list of WiFi networks**, run the below command. Replace `wlan0` with your device name on the below command and all the following commands.
|
||||
|
||||
```
|
||||
station wlan0 get-networks
|
||||
```
|
||||
|
||||
![iwctl – available networks][5]
|
||||
|
||||
The command gives you the list of available WiFi network with security type and signal strength.
|
||||
|
||||
#### Connect
|
||||
|
||||
To **connect to the WiFi networ**k, run the below command with the WiFi access point name from the above “get-networks” command.
|
||||
|
||||
```
|
||||
station wlan0 connect
|
||||
```
|
||||
|
||||
Enter your WiFi password when prompted.
|
||||
|
||||
![connect to WiFi using iwctl][6]
|
||||
|
||||
If all, goes well you should be connected to the internet.
|
||||
|
||||
### Usage Guides
|
||||
|
||||
* You can check the connection using a simple ping command as follows. The ping replies successful packet transfers for a stable connection.
|
||||
|
||||
```
|
||||
ping -c 3 google.com
|
||||
```
|
||||
|
||||
* You can also check the status of the connection using the below command.
|
||||
|
||||
```
|
||||
station wlan0 show
|
||||
```
|
||||
|
||||
* The iwd keeps the configuration file at `/var/lib/iwd` as a `.psk` file with your access point name.
|
||||
|
||||
* This file contains a hash file that is generated using the password and SSID of your WiFi network.
|
||||
|
||||
* Press `CTRL+D` to leave from the `iwctl` prompt.
|
||||
|
||||
### Wrapping Up
|
||||
|
||||
I hope this guide helps you to connect to the internet via the terminal. This helps when you have no other way to connect to WiFi. For example, if you are installing Arch Linux in a stand-alone system (not a VM), you need to connect to the internet to download packages via a terminal using `pacman`.
|
||||
|
||||
If you face any trouble, mention the error messages in the comment box below.
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://www.debugpoint.com/connect-wifi-terminal-linux/
|
||||
|
||||
作者：[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://wiki.archlinux.org/index.php/Iwd
|
||||
[2]: https://www.debugpoint.com/wp-content/uploads/2020/11/iwctl-Prompt.jpg
|
||||
[3]: https://www.archlinux.org/packages/?name=iwd
|
||||
[4]: https://www.debugpoint.com/wp-content/uploads/2020/11/iwctl-device-list-2.jpg
|
||||
[5]: https://www.debugpoint.com/wp-content/uploads/2020/11/iwctl-available-networks.jpg
|
||||
[6]: https://www.debugpoint.com/wp-content/uploads/2020/11/connect-to-WiFi-using-iwctl.jpg
|
||||
@@ -2,7 +2,7 @@
|
||||
[#]: via: "https://opensource.com/article/22/9/docker-desktop-colima"
|
||||
[#]: author: "Michael Anello https://opensource.com/users/ultimike"
|
||||
[#]: collector: "lkxed"
|
||||
[#]: translator: " "
|
||||
[#]: translator: "geekpi"
|
||||
[#]: reviewer: " "
|
||||
[#]: publisher: " "
|
||||
[#]: url: " "
|
||||
|
||||
@@ -0,0 +1,323 @@
|
||||
[#]: subject: "How To Find Default Gateway IP Address In Linux And Unix From Commandline"
|
||||
[#]: via: "https://ostechnix.com/find-default-gateway-linux/"
|
||||
[#]: author: "sk https://ostechnix.com/author/sk/"
|
||||
[#]: collector: "lkxed"
|
||||
[#]: translator: " "
|
||||
[#]: reviewer: " "
|
||||
[#]: publisher: " "
|
||||
[#]: url: " "
|
||||
|
||||
How To Find Default Gateway IP Address In Linux And Unix From Commandline
|
||||
======
|
||||
5 Ways To Find Gateway Or Router IP Address In Linux
|
||||
|
||||
A **gateway** is a node or a router that allows two or more hosts with different IP addresses to communicate with each other when connected to the same router. Without gateway, devices connected on the same router won’t be able to communicate with each other. To put this another way, the gateway acts as an access point to pass network data from a local network to a remote network. In this guide, we will see all the possible ways to **find default gateway in Linux** and **Unix** from commandline.
|
||||
|
||||
#### Contents
|
||||
|
||||
1. Find Default Gateway In Linux 2. 1. Find Default Gateway Using ip Command 3. 2. Display Default Gateway IP Address Using route Command 4. 3. View Gateway IP Address Using netstat Command 5. 4. Print Default Gateway IP Address Or Router IP Address Using routel Command 6. 5. Find Gateway From Ethernet Configuration Files
|
||||
7. Conclusion
|
||||
|
||||
### Find Default Gateway In Linux
|
||||
|
||||
There are various commandline tools are available to view the gateway IP address in Linux. The most commonly used tools are: **ip**, **ss**, and **netcat**. We will see how check the default gateway using each tool with examples.
|
||||
|
||||
#### 1. Find Default Gateway Using ip Command
|
||||
|
||||
The **ip** command is used to show and manipulate routing, network devices, interfaces and tunnels in Linux.
|
||||
|
||||
To find the default gateway or Router IP address, simply run:
|
||||
|
||||
```
|
||||
$ ip route
|
||||
```
|
||||
|
||||
Or,
|
||||
|
||||
```
|
||||
$ ip r
|
||||
```
|
||||
|
||||
Or,
|
||||
|
||||
```
|
||||
$ ip route show
|
||||
```
|
||||
|
||||
**Sample output:**
|
||||
|
||||
```
|
||||
default via 192.168.1.101 dev eth0 proto static metric 100
|
||||
172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown
|
||||
192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.20 metric 100
|
||||
```
|
||||
|
||||
Did you see the line **"default via 192.168.1.101"** in the above output? This is the default gateway. So my default gateway is **192.168.1.101**.
|
||||
|
||||
You can use **-4** with `ip route` command to **display the IPv4 gateway** only:
|
||||
|
||||
```
|
||||
$ ip -4 route
|
||||
```
|
||||
|
||||
And, use `-6` to **display the IPv6 gateway** only:
|
||||
|
||||
```
|
||||
$ ip -6 route
|
||||
```
|
||||
|
||||
As you noticed in the output, the IP address and the subnet details are also shown. If you want to display ONLY the default gateway and exclude all other details from the output, you can use `awk` command with `ip route` like below.
|
||||
|
||||
To find the default gateway IP address using `ip route` and `grep`, run:
|
||||
|
||||
To print Gateway IP address with `ip route` and `awk` commands, run:
|
||||
|
||||
```
|
||||
$ ip route | awk '/^default/{print $3}'
|
||||
```
|
||||
|
||||
Or,
|
||||
|
||||
```
|
||||
$ ip route show default | awk '{print $3}'
|
||||
```
|
||||
|
||||
This will list only the gateway.
|
||||
|
||||
**Sample output:**
|
||||
|
||||
```
|
||||
192.168.1.101
|
||||
```
|
||||
|
||||
![Find Default Gateway Using ip Command][1]
|
||||
|
||||
You can also use **[grep][2]** command with `ip route` to filter the default gateway.
|
||||
|
||||
```
|
||||
$ ip route | grep default
|
||||
default via 192.168.1.101 dev eth0 proto static metric 100
|
||||
```
|
||||
|
||||
The `ip route` is the recommended command to find the default gateway IP address in latest Linux distributions. However, some of you may still be using the legacy tools like **route** and `netstat`. Old habits die hard, right? The following sections explains how to determine the gateway in Linux using `route` and `netstat` commands.
|
||||
|
||||
#### 2. Display Default Gateway IP Address Using route Command
|
||||
|
||||
The **route** command is used to show and manipulate routing table in older Linux distributions, for example RHEL 6, CentOS 6.
|
||||
|
||||
If you're using those older Linux distributions, you can use the `route` command to display the default gateway.
|
||||
|
||||
Please note that the `route` tool is deprecated and replaced with `ip route` command in the latest Linux distributions. If you still want to use `route` for any reason, you need to install it.
|
||||
|
||||
First, we need to check which package provides `route` command. To do so, run the following command on your RHEL-based system:
|
||||
|
||||
```
|
||||
$ dnf provides route
|
||||
```
|
||||
|
||||
**Sample output:**
|
||||
|
||||
```
|
||||
net-tools-2.0-0.52.20160912git.el8.x86_64 : Basic networking tools
|
||||
Repo : @System
|
||||
Matched from:
|
||||
Filename : /usr/sbin/route
|
||||
|
||||
net-tools-2.0-0.52.20160912git.el8.x86_64 : Basic networking tools
|
||||
Repo : baseos
|
||||
Matched from:
|
||||
Filename : /usr/sbin/route
|
||||
```
|
||||
|
||||
As you can see in the above output, the net-tools package provides the `route` command. So, let us install it using command:
|
||||
|
||||
```
|
||||
$ sudo dnf install net-tools
|
||||
```
|
||||
|
||||
Now, run `route` command with `-n` flag to display the gateway IP address or router IP address in your Linux system:
|
||||
|
||||
```
|
||||
$ route -n
|
||||
```
|
||||
|
||||
**Sample output:**
|
||||
|
||||
```
|
||||
Kernel IP routing table
|
||||
Destination Gateway Genmask Flags Metric Ref Use Iface
|
||||
0.0.0.0 192.168.1.101 0.0.0.0 UG 100 0 0 eth0
|
||||
172.17.0.0 0.0.0.0 255.255.0.0 U 0 0 0 docker0
|
||||
192.168.1.0 0.0.0.0 255.255.255.0 U 100 0 0 eth0
|
||||
```
|
||||
|
||||
![Display Default Gateway IP Address Using route Command][3]
|
||||
|
||||
As you see in the above output, the gateway IP address is 192.168.1.101. You will also see the two letters **"UG"** under Flags section. The letter **"U"** indicates the interface is **UP** and **G** stands for Gateway.
|
||||
|
||||
#### 3. View Gateway IP Address Using netstat Command
|
||||
|
||||
**Netstat** prints information about the Linux networking subsystem. Using netstat tool, we can print network connections, routing tables, interface statistics, masquerade connections, and multicast memberships in Linux and Unix systems.
|
||||
|
||||
Netstat is part of net-tools package, so make sure you've installed it in your Linux system. The following commands install net-tools package in RHEL-based systems:
|
||||
|
||||
```
|
||||
$ sudo dnf install net-tools
|
||||
```
|
||||
|
||||
To print the default gateway IP address using `netstat` command, run:
|
||||
|
||||
```
|
||||
$ netstat -rn
|
||||
```
|
||||
|
||||
**Sample output:**
|
||||
|
||||
```
|
||||
Kernel IP routing table
|
||||
Destination Gateway Genmask Flags MSS Window irtt Iface
|
||||
0.0.0.0 192.168.1.101 0.0.0.0 UG 0 0 0 eth0
|
||||
172.17.0.0 0.0.0.0 255.255.0.0 U 0 0 0 docker0
|
||||
192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
|
||||
```
|
||||
|
||||
![View Gateway IP Address Using netstat Command][4]
|
||||
|
||||
The `netstat` command's output is same as `route` command's output. As per the above output, the gateway IP address is 192.168.1.101 and the UG stands the NIC associated to gateway is UP and G indicates Gateway,
|
||||
|
||||
Please note that `netstat` is also deprecated and it is recommended to use **"ss"** command instead of netstat.
|
||||
|
||||
#### 4. Print Default Gateway IP Address Or Router IP Address Using routel Command
|
||||
|
||||
The **routel** is a script to list routes with pretty output format. The routel script will list routes in a format that some might consider easier to interpret then the `ip route` list equivalent.
|
||||
|
||||
The routel script is also the part of net-tools package.
|
||||
|
||||
To print the default gateway or router IP address, run routel script without any flags like below:
|
||||
|
||||
```
|
||||
$ routel
|
||||
```
|
||||
|
||||
**Sample output:**
|
||||
|
||||
```
|
||||
target gateway source proto scope dev tbl
|
||||
default 192.168.1.101 static eth0
|
||||
172.17.0.0/ 16 172.17.0.1 kernel linkdocker0
|
||||
192.168.1.0/ 24 192.168.1.20 kernel link eth0
|
||||
127.0.0.0/ 8 local 127.0.0.1 kernel host lo local
|
||||
127.0.0.1 local 127.0.0.1 kernel host lo local
|
||||
127.255.255.255 broadcast 127.0.0.1 kernel link lo local
|
||||
172.17.0.1 local 172.17.0.1 kernel hostdocker0 local
|
||||
172.17.255.255 broadcast 172.17.0.1 kernel linkdocker0 local
|
||||
192.168.1.20 local 192.168.1.20 kernel host eth0 local
|
||||
192.168.1.255 broadcast 192.168.1.20 kernel link eth0 local
|
||||
::1 kernel lo
|
||||
::/ 96 unreachable lo
|
||||
::ffff:0.0.0.0/ 96 unreachable lo
|
||||
2002:a00::/ 24 unreachable lo
|
||||
2002:7f00::/ 24 unreachable lo
|
||||
2002:a9fe::/ 32 unreachable lo
|
||||
2002:ac10::/ 28 unreachable lo
|
||||
2002:c0a8::/ 32 unreachable lo
|
||||
2002:e000::/ 19 unreachable lo
|
||||
3ffe:ffff::/ 32 unreachable lo
|
||||
fe80::/ 64 kernel eth0
|
||||
::1 local kernel lo local
|
||||
fe80::d085:cff:fec7:c1c3 local kernel eth0 local
|
||||
```
|
||||
|
||||
![Print Default Gateway IP Address Or Router IP Address Using routel Command][5]
|
||||
|
||||
To print only the default gateway, run routel with `grep` like below:
|
||||
|
||||
```
|
||||
$ routel | grep default
|
||||
default 192.168.1.101 static eth0
|
||||
```
|
||||
|
||||
#### 5. Find Gateway From Ethernet Configuration Files
|
||||
|
||||
If you have **[configured static IP address in your Linux or Unix][6]** system, you can view the default gateway or router IP address by looking at the network configuration files.
|
||||
|
||||
In RPM-based systems like Fedora, RHEL, CentOS, AlmaLinux and Rocky Linux, the network interface card (shortly **NIC**) configuration are stored under **/etc/sysconfig/network-scripts/** directory.
|
||||
|
||||
Find the name of the network card:
|
||||
|
||||
```
|
||||
# ip link show
|
||||
```
|
||||
|
||||
**Sample output:**
|
||||
|
||||
```
|
||||
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
|
||||
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
|
||||
2: eth0@if5: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000
|
||||
link/ether d2:85:0c:c7:c1:c3 brd ff:ff:ff:ff:ff:ff link-netnsid 0
|
||||
```
|
||||
|
||||
The network card name is **eth0**. So let us open the network card configuration of this NIC card file:
|
||||
|
||||
```
|
||||
# cat /etc/sysconfig/network-scripts/ifcfg-eth0
|
||||
```
|
||||
|
||||
**Sample output:**
|
||||
|
||||
```
|
||||
DEVICE=eth0
|
||||
ONBOOT=yes
|
||||
UUID=eb6b6a7c-37f5-11ed-a59a-a0e70bdf3dfb
|
||||
BOOTPROTO=none
|
||||
IPADDR=192.168.1.20
|
||||
NETMASK=255.255.255.0
|
||||
GATEWAY=192.168.1.101
|
||||
DNS1=8.8.8.8
|
||||
```
|
||||
|
||||
As you see above, the gateway IP is `192.168.1.101`.
|
||||
|
||||
In Debian, Ubuntu and its derivatives, all network configuration files are stored under **/etc/network/** directory.
|
||||
|
||||
```
|
||||
$ cat /etc/network/interfaces
|
||||
```
|
||||
|
||||
**Sample output:**
|
||||
|
||||
```
|
||||
auto ens18
|
||||
iface ens18 inet static
|
||||
address 192.168.1.150
|
||||
netmask 255.255.255.0
|
||||
gateway 192.168.1.101
|
||||
dns-nameservers 8.8.8.8
|
||||
```
|
||||
|
||||
Please note that this method should work only if the IP address is configured manually. For DHCP-enabled network, you need to follow the previous 4 methods.
|
||||
|
||||
### Conclusion
|
||||
|
||||
In this guide, we listed 5 different ways to find default gateway in Linux and Unix operating systems. We also have included sample commands to display the gateway/router IP address in each method. Hope this helps.
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://ostechnix.com/find-default-gateway-linux/
|
||||
|
||||
作者：[sk][a]
|
||||
选题：[lkxed][b]
|
||||
译者：[译者ID](https://github.com/译者ID)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
||||
[a]: https://ostechnix.com/author/sk/
|
||||
[b]: https://github.com/lkxed
|
||||
[1]: https://ostechnix.com/wp-content/uploads/2022/09/Find-Default-Gateway-Using-ip-Command.png
|
||||
[2]: https://ostechnix.com/the-grep-command-tutorial-with-examples-for-beginners/
|
||||
[3]: https://ostechnix.com/wp-content/uploads/2022/09/Display-Default-Gateway-IP-Address-Using-route-Command.png
|
||||
[4]: https://ostechnix.com/wp-content/uploads/2022/09/View-Gateway-IP-Address-Using-netstat-Command.png
|
||||
[5]: https://ostechnix.com/wp-content/uploads/2022/09/Print-Default-Gateway-IP-Address-Or-Router-IP-Address-Using-routel-Command.png
|
||||
[6]: https://ostechnix.com/configure-static-ip-address-linux-unix/
|
||||
@@ -0,0 +1,190 @@
|
||||
[#]: subject: "How to Install Cockpit Web Console on Ubuntu 22.04"
|
||||
[#]: via: "https://www.linuxtechi.com/how-to-install-cockpit-on-ubuntu/"
|
||||
[#]: author: "Pradeep Kumar https://www.linuxtechi.com/author/pradeep/"
|
||||
[#]: collector: "lkxed"
|
||||
[#]: translator: " "
|
||||
[#]: reviewer: " "
|
||||
[#]: publisher: " "
|
||||
[#]: url: " "
|
||||
|
||||
How to Install Cockpit Web Console on Ubuntu 22.04
|
||||
======
|
||||
In this guide, we examine how to install Cockpit on Ubuntu 22.04 LTS (Jammy Jellyfish) step-by-step.
|
||||
|
||||
Cockpit is a free and opensource web-based graphical server management tool that allows administrators and Linux users to easily manage and configure their Linux servers/PCs from a browser. It targets new Linux users or those who want an easy way to manage their servers on a graphical interface without the hassle of working on the command-line.
|
||||
|
||||
Cockpit is easy to install and simple to use. At a glance, it allows you to perform the following tasks.
|
||||
|
||||
* Keep tabs of system metrics and performance
|
||||
* Create and manage users
|
||||
* Browse and search system logs
|
||||
* Inspect and interact with systemd-based services
|
||||
* Access the terminal and run commands
|
||||
* Inspect system’s hardware
|
||||
* Create and manage virtual machines
|
||||
* Upgrade software packages to their latest versions
|
||||
* Configure Firewall & and many more.
|
||||
|
||||
### 1) Update Local Package Index
|
||||
|
||||
To start off, log into your server and refresh the local package index as follows.
|
||||
|
||||
```
|
||||
$ sudo apt update
|
||||
```
|
||||
|
||||
### 2) Install Cockpit Web Console
|
||||
|
||||
The Cockpit web console packages are provided by the official Ubuntu repositories. You can verify this by running the following command.
|
||||
|
||||
```
|
||||
$ apt search cockpit
|
||||
```
|
||||
|
||||
So, install Cockpit using the APT package manager as shown.
|
||||
|
||||
```
|
||||
$ sudo apt install cockpit -y
|
||||
```
|
||||
|
||||
The command installs the Cockpit web console alongside other additional packages, libraries, and dependencies.
|
||||
|
||||
![Apt-Command-Install-Cockpit-Ubuntu-22-04][1]
|
||||
|
||||
Once installed, you can verify if cockpit is installed by running the following command:
|
||||
|
||||
```
|
||||
$ apt -qq list cockpit
|
||||
OR
|
||||
$ dpkg -l cockpit
|
||||
```
|
||||
|
||||
From the output below, we can see that Cockpit version 264-1 has been installed.
|
||||
|
||||
![Check-Cockpit-WebConsole-Version-Ubuntu][2]
|
||||
|
||||
In case, you planning to manage kvm virtual machines with cockpit then install following package
|
||||
|
||||
```
|
||||
$ sudo apt install cockpit-machines -y
|
||||
```
|
||||
|
||||
### 3) Install Cockpit Support for Podman
|
||||
|
||||
By default, Cockpit does not provide support for podman. If you wish to administer and manage podman containers using Cockpit, install the cockpit-podman package which provides support for podman.
|
||||
|
||||
```
|
||||
$ sudo apt install cockpit-podman y
|
||||
```
|
||||
|
||||
![Install-Cockpit-Podman-Support-Ubuntu-22-04][3]
|
||||
|
||||
### 4) Start Cockpit Web Console Service
|
||||
|
||||
Unlike other services or daemons, Cockpit does not start automatically once installed. Therefore, start the Cockpit systemd service as shown.
|
||||
|
||||
```
|
||||
$ sudo systemctl start cockpit
|
||||
```
|
||||
|
||||
Next, verify that the Cockpit service is running as follows.
|
||||
|
||||
```
|
||||
$ sudo systemctl status cockpit
|
||||
```
|
||||
|
||||
The output confirms that the Cockpit service is up and running.
|
||||
|
||||
![Cockpit-Service-Status-Ubuntu-22-04][4]
|
||||
|
||||
Cockpit listens on TCP port 9090. You can verify this is the case by running the following ss command.
|
||||
|
||||
```
|
||||
$ ss -tunlpe | grep cockpit
|
||||
```
|
||||
|
||||
![Socket-Connection-Cockpit-Ubuntu-22-04][5]
|
||||
|
||||
If the firewall is enabled on your Ubuntu 22.04 system, then allow 9090/tcp port so it’s web console can be accessed from outside
|
||||
|
||||
```
|
||||
$ sudo ufw allow 9090/tcp
|
||||
$ sudo ufw reload
|
||||
```
|
||||
|
||||
![Allow-cockpit-console-port-ubuntu-22-04][6]
|
||||
|
||||
### 5) Access Cockpit Web Console
|
||||
|
||||
Cockpit is now fully installed and the only thing remaining is to access it and use it to manage your server.
|
||||
|
||||
To access Cockpit Web console, browse the following address.
|
||||
|
||||
https://server-ip:9090
|
||||
|
||||
You will get a warning that the website you are accessing is not private and that you could fall victim to hackers. Do not fret, as this happens since the server is encrypted by a self-signed SSL certificate which is not recognized by CA.
|
||||
|
||||
To get around this issue, simply click ‘Advanced’
|
||||
|
||||
![Cockpit-WebConsole-URL-Ubuntu-22-04][7]
|
||||
|
||||
Then click on ‘Proceed to server-ip’ link.
|
||||
|
||||
![Accept-Certificate-Cockpit-WebConsole][8]
|
||||
|
||||
Thereafter, the following login page will appear. Be sure to provide your username and password and click ‘Log In’.
|
||||
|
||||
![Cockpit-Login-Page-Ubuntu-22-04][9]
|
||||
|
||||
This ushers you to the Cockpit dashboard. The ‘Overview’ page provides your system’s metrics at a glance. You will see details on CPU and memory usage, health status, and system information.
|
||||
|
||||
To perform the administrative task, click on ‘Turn on administrative access’, it will prompt you to enter your user’s password.
|
||||
|
||||
The left sidebar provides various options that you can view.
|
||||
|
||||
![Cockpit-Dashboard-Ubuntu-22-04][10]
|
||||
|
||||
For example, you can click on ‘Networking’ to view information about bandwidth statistics, network interfaces as well as network logs.
|
||||
|
||||
![View-Network-Statistics-from-Cockpit-WebConsole][11]
|
||||
|
||||
You can also click ‘Services’ to get information about all the system services.
|
||||
|
||||
![System-Services-Status-Cockpit-WebConsole-Ubuntu-22-04][12]
|
||||
|
||||
To view and install software updates, click on ‘Software Updates’
|
||||
|
||||
![Software-Updates-Cockpit-WebConsole-Ubuntu-22-04][13]
|
||||
|
||||
In my case all the software updates are already installed, that’s why I am getting the status as ‘System is up to date’
|
||||
|
||||
##### Conclusion
|
||||
|
||||
And that’s it. In this guide, we have successfully installed Cockpit on Ubuntu 22.04. All the best as you enjoy managing your system.
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://www.linuxtechi.com/how-to-install-cockpit-on-ubuntu/
|
||||
|
||||
作者：[Pradeep Kumar][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.linuxtechi.com/author/pradeep/
|
||||
[b]: https://github.com/lkxed
|
||||
[1]: https://www.linuxtechi.com/wp-content/uploads/2022/09/Apt-Command-Install-Cockpit-Ubuntu-22-04.png
|
||||
[2]: https://www.linuxtechi.com/wp-content/uploads/2022/09/Check-Cockpit-WebConsole-Version-Ubuntu.png
|
||||
[3]: https://www.linuxtechi.com/wp-content/uploads/2022/09/Install-Cockpit-Podman-Support-Ubuntu-22-04.png
|
||||
[4]: https://www.linuxtechi.com/wp-content/uploads/2022/09/Cockpit-Service-Status-Ubuntu-22-04.png
|
||||
[5]: https://www.linuxtechi.com/wp-content/uploads/2022/09/Socket-Connection-Cockpit-Ubuntu-22-04.png
|
||||
[6]: https://www.linuxtechi.com/wp-content/uploads/2022/09/Allow-cockpit-console-port-ubuntu-22-04.png
|
||||
[7]: https://www.linuxtechi.com/wp-content/uploads/2022/09/Cockpit-WebConsole-URL-Ubuntu-22-04.png
|
||||
[8]: https://www.linuxtechi.com/wp-content/uploads/2022/09/Accept-Certificate-Cockpit-WebConsole.png
|
||||
[9]: https://www.linuxtechi.com/wp-content/uploads/2022/09/Cockpit-Login-Page-Ubuntu-22-04.png
|
||||
[10]: https://www.linuxtechi.com/wp-content/uploads/2022/09/Cockpit-Dashboard-Ubuntu-22-04.png
|
||||
[11]: https://www.linuxtechi.com/wp-content/uploads/2022/09/View-Network-Statistics-from-Cockpit-WebConsole.png
|
||||
[12]: https://www.linuxtechi.com/wp-content/uploads/2022/09/System-Services-Status-Cockpit-WebConsole-Ubuntu-22-04.png
|
||||
[13]: https://www.linuxtechi.com/wp-content/uploads/2022/09/Software-Updates-Cockpit-WebConsole-Ubuntu-22-04.png
|
||||
185
sources/tech/20220919 PyLint- The good, the bad, and the ugly.md
Normal file
185
sources/tech/20220919 PyLint- The good, the bad, and the ugly.md
Normal file
@@ -0,0 +1,185 @@
|
||||
[#]: subject: "PyLint: The good, the bad, and the ugly"
|
||||
[#]: via: "https://opensource.com/article/22/9/pylint-good-bad-ugly"
|
||||
[#]: author: "Moshe Zadka https://opensource.com/users/moshez"
|
||||
[#]: collector: "lkxed"
|
||||
[#]: translator: " "
|
||||
[#]: reviewer: " "
|
||||
[#]: publisher: " "
|
||||
[#]: url: " "
|
||||
|
||||
PyLint: The good, the bad, and the ugly
|
||||
======
|
||||
Get the most out of PyLint.
|
||||
|
||||
![Python programming language logo with question marks][1]
|
||||
|
||||
Image by: Opensource.com
|
||||
|
||||
Hot take: PyLint is actually good!
|
||||
|
||||
"PyLint can save your life" is an exaggeration, but not as much as you might think! PyLint can keep you from really really hard to find and complicated bugs. At worst, it can save you the time of a test run. At best, it can help you avoid complicated production mistakes.
|
||||
|
||||
### The good
|
||||
|
||||
I'm embarrassed to say how common this can be. Naming tests is perpetually *weird*: Nothing cares about the name, and there's often not a natural name to be found. For instance, look at this code:
|
||||
|
||||
```
|
||||
def test_add_small():
|
||||
# Math, am I right?
|
||||
assert 1 + 1 == 3
|
||||
|
||||
def test_add_large():
|
||||
assert 5 + 6 == 11
|
||||
|
||||
def test_add_small():
|
||||
assert 1 + 10 == 11
|
||||
```
|
||||
|
||||
The test works:
|
||||
|
||||
```
|
||||
collected 2 items
|
||||
test.py ..
|
||||
2 passed
|
||||
```
|
||||
|
||||
In reality, these files can be hundreds of lines long, and the person adding the new test might not be aware of all the names. Unless someone is looking at test output carefully, everything looks fine.
|
||||
|
||||
Worst of all, the *addition of the overriding test*, the *breakage of the overridden test*, and the *problem that results in prod* might be separated by days, months, or even years.
|
||||
|
||||
### PyLint finds it
|
||||
|
||||
But like a good friend, PyLint is there for you.
|
||||
|
||||
```
|
||||
test.py:8:0: E0102: function already defined line 1
|
||||
(function-redefined)
|
||||
```
|
||||
|
||||
### The bad
|
||||
|
||||
Like a 90s sitcom, the more you get into PyLint, the more it becomes problematic. This is completely reasonable code for an inventory modeling program:
|
||||
|
||||
```
|
||||
"""Inventory abstractions"""
|
||||
|
||||
import attrs
|
||||
|
||||
@attrs.define
|
||||
class Laptop:
|
||||
"""A laptop"""
|
||||
ident: str
|
||||
cpu: str
|
||||
```
|
||||
|
||||
It seems that PyLint has opinions (probably formed in the 90s) and is not afraid to state them as facts:
|
||||
|
||||
```
|
||||
$ pylint laptop.py | sed -n '/^laptop/s/[^ ]*: //p'
|
||||
R0903: Too few public methods (0/2) (too-few-public-methods)
|
||||
```
|
||||
|
||||
### The ugly
|
||||
|
||||
Ever wanted to add your own unvetted opinion to a tool used by millions? PyLint has 12 million monthly downloads.
|
||||
|
||||
> "People will just disable the whole check if it's too picky." —PyLint issue 6987, July 3rd, 2022
|
||||
|
||||
The attitude it takes towards adding a test with potentially many false positives is...*"eh."*
|
||||
|
||||
### Making it work for you
|
||||
|
||||
PyLint is fine, but you need to interact with it carefully. Here are the three things I recommend to make PyLint work for you.
|
||||
|
||||
#### 1. Pin it
|
||||
|
||||
Pin the PyLint version you use to avoid any surprises!
|
||||
|
||||
In your `.toml` file:
|
||||
|
||||
```
|
||||
[project.optional-dependencies]
|
||||
pylint = ["pylint"]
|
||||
```
|
||||
|
||||
In your code:
|
||||
|
||||
```
|
||||
from unittest import mock
|
||||
```
|
||||
|
||||
This corresponds with code like this:
|
||||
|
||||
```
|
||||
# noxfile.py
|
||||
...
|
||||
@nox.session(python=VERSIONS[-1])
|
||||
def refresh_deps(session):
|
||||
"""Refresh the requirements-*.txt files"""
|
||||
session.install("pip-tools")
|
||||
for deps in [..., "pylint"]:
|
||||
session.run(
|
||||
"pip-compile",
|
||||
"--extra",
|
||||
deps,
|
||||
"pyproject.toml",
|
||||
"--output-file",
|
||||
f"requirements-{deps}.txt",
|
||||
)
|
||||
```
|
||||
|
||||
#### 2. Default deny
|
||||
|
||||
Disable all checks. Then enable ones that you think have a high value-to-false-positive ratio. (Not just false-negative-to-false-positive ratio!)
|
||||
|
||||
```
|
||||
# noxfile.py
|
||||
...
|
||||
@nox.session(python="3.10")
|
||||
def lint(session):
|
||||
files = ["src/", "noxfile.py"]
|
||||
session.install("-r", "requirements-pylint.txt")
|
||||
session.install("-e", ".")
|
||||
session.run(
|
||||
"pylint",
|
||||
"--disable=all",
|
||||
*(f"--enable={checker}" for checker in checkers)
|
||||
"src",
|
||||
)
|
||||
```
|
||||
|
||||
#### 3. Checkers
|
||||
|
||||
These are some of the ones I like. Enforce consistency in the project, avoid some obvious mistakes.
|
||||
|
||||
```
|
||||
checkers = [
|
||||
"missing-class-docstring",
|
||||
"missing-function-docstring",
|
||||
"missing-module-docstring",
|
||||
"function-redefined",
|
||||
]
|
||||
```
|
||||
|
||||
### Using PyLint
|
||||
|
||||
You can take just the good parts of PyLint. Run it in CI to keep consistency, and use the highest value checkers.
|
||||
|
||||
Lose the bad parts: Default deny checkers.
|
||||
|
||||
Avoid the ugly parts: Pin the version to avoid surprises.
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://opensource.com/article/22/9/pylint-good-bad-ugly
|
||||
|
||||
作者：[Moshe Zadka][a]
|
||||
选题：[lkxed][b]
|
||||
译者：[译者ID](https://github.com/译者ID)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
||||
[a]: https://opensource.com/users/moshez
|
||||
[b]: https://github.com/lkxed
|
||||
[1]: https://opensource.com/sites/default/files/lead-images/python_programming_question.png
|
||||
180
sources/tech/20220920 3 ways to use the Linux inxi command.md
Normal file
180
sources/tech/20220920 3 ways to use the Linux inxi command.md
Normal file
@@ -0,0 +1,180 @@
|
||||
[#]: subject: "3 ways to use the Linux inxi command"
|
||||
[#]: via: "https://opensource.com/article/22/9/linux-inxi-command"
|
||||
[#]: author: "Don Watkins https://opensource.com/users/don-watkins"
|
||||
[#]: collector: "lkxed"
|
||||
[#]: translator: " "
|
||||
[#]: reviewer: " "
|
||||
[#]: publisher: " "
|
||||
[#]: url: " "
|
||||
|
||||
3 ways to use the Linux inxi command
|
||||
======
|
||||
I use inxi on Linux to check my laptop batter, CPU information, and even the weather.
|
||||
|
||||
![Coding on a computer][1]
|
||||
|
||||
I was looking for information about the health of my laptop battery when I stumbled upon `inxi`. It's a command line system information tool that provides a wealth of information about your Linux computer, whether it's a laptop, desktop, or server.
|
||||
|
||||
The `inxi` command is [licensed][2] with the GPLv3, and many Linux distributions include it. According to its Git repository: "inxi strives to support the widest range of operating systems and hardware, from the most simple consumer desktops, to the most advanced professional hardware and servers."
|
||||
|
||||
Documentation is robust, and the project maintains a complete [man page][3] online. Once installed, you can access the man page on your system with the `man inxi` command.
|
||||
|
||||
### Install inxi on Linux
|
||||
|
||||
Generally, you can install `inxi` from your distribution's software repository or app center. For example, on Fedora, CentOS, Mageia, or similar:
|
||||
|
||||
```
|
||||
$ sudo dnf install inxi
|
||||
```
|
||||
|
||||
On Debian, Elementary, Linux Mint, or similar:
|
||||
|
||||
```
|
||||
$ sudo apt install inxi
|
||||
```
|
||||
|
||||
You can find more information about installation options for your Linux distribution [here][4].
|
||||
|
||||
### 3 ways to use inxi on Linux
|
||||
|
||||
Once you install `inxi`, you can explore all its options. There are numerous options to help you learn more about your system. The most fundamental command provides a basic overview of your system:
|
||||
|
||||
```
|
||||
$ inxi -b
|
||||
System:
|
||||
Host: pop-os Kernel: 5.19.0-76051900-generic x86_64 bits: 64
|
||||
Desktop: GNOME 42.3.1 Distro: Pop!_OS 22.04 LTS
|
||||
Machine:
|
||||
Type: Laptop System: HP product: Dev One Notebook PC v: N/A
|
||||
serial: <superuser required>
|
||||
Mobo: HP model: 8A78 v: KBC Version 01.03 serial: <superuser required>
|
||||
UEFI: Insyde v: F.05 date: 06/14/2022
|
||||
Battery:
|
||||
ID-1: BATT charge: 50.6 Wh (96.9%) condition: 52.2/53.2 Wh (98.0%)
|
||||
CPU:
|
||||
Info: 8-core AMD Ryzen 7 PRO 5850U with Radeon Graphics [MT MCP]
|
||||
speed (MHz): avg: 915 min/max: 400/4507
|
||||
Graphics:
|
||||
Device-1: AMD Cezanne driver: amdgpu v: kernel
|
||||
Device-2: Quanta HP HD Camera type: USB driver: uvcvideo
|
||||
Display: x11 server: X.Org v: 1.21.1.3 driver: X: loaded: amdgpu,ati
|
||||
unloaded: fbdev,modesetting,radeon,vesa gpu: amdgpu
|
||||
resolution: 1920x1080~60Hz
|
||||
OpenGL:
|
||||
renderer: AMD RENOIR (LLVM 13.0.1 DRM 3.47 5.19.0-76051900-generic)
|
||||
v: 4.6 Mesa 22.0.5
|
||||
Network:
|
||||
Device-1: Realtek RTL8822CE 802.11ac PCIe Wireless Network Adapter
|
||||
driver: rtw_8822ce
|
||||
Drives:
|
||||
Local Storage: total: 953.87 GiB used: 75.44 GiB (7.9%)
|
||||
Info:
|
||||
Processes: 347 Uptime: 15m Memory: 14.96 GiB used: 2.91 GiB (19.4%)
|
||||
Shell: Bash inxi: 3.3.13
|
||||
```
|
||||
|
||||
### 1. Display battery status
|
||||
|
||||
You can check your battery health using the `-B` option. The result shows the system battery ID, charge condition, and other information:
|
||||
|
||||
```
|
||||
$ inxi -B
|
||||
Battery:
|
||||
ID-1: BATT charge: 44.3 Wh (85.2%) condition: 52.0/53.2 Wh (97.7%)
|
||||
```
|
||||
|
||||
### 2. Display CPU info
|
||||
|
||||
Find out more information about the CPU with the `-C` option:
|
||||
|
||||
```
|
||||
$ inxi -C
|
||||
CPU:
|
||||
Info: 8-core model: AMD Ryzen 7 PRO 5850U with Radeon Graphics bits: 64
|
||||
type: MT MCP cache: L2: 4 MiB
|
||||
Speed (MHz): avg: 400 min/max: 400/4507 cores: 1: 400 2: 400 3: 400
|
||||
4: 400 5: 400 6: 400 7: 400 8: 400 9: 400 10: 400 11: 400 12: 400 13: 400
|
||||
14: 400 15: 400 16: 400
|
||||
```
|
||||
|
||||
The output of `inxi` uses colored text by default. You can change that to improve readability, as needed, by using the "color switch."
|
||||
|
||||
The command option is `-c` followed by any number between 0 and 42 to suit your tastes.
|
||||
|
||||
```
|
||||
$ inxi -c 42
|
||||
```
|
||||
|
||||
Here is an example of a couple of different options using color 5 and then 7:
|
||||
|
||||
![inxi -c 5 command][5]
|
||||
|
||||
The software can show hardware temperature, fan speed, and other information about your system using the sensors in your Linux system. Enter `inxi -s` and read the result below:
|
||||
|
||||
![inxi -s][6]
|
||||
|
||||
### 3. Combine options
|
||||
|
||||
You can combine options for `inxi` to get complex output when supported. For example, `inxi -S` provides system information, and `-v` provides verbose output. Combining the two gives the following:
|
||||
|
||||
```
|
||||
$ inxi -S
|
||||
System:
|
||||
Host: pop-os Kernel: 5.19.0-76051900-generic x86_64 bits: 64
|
||||
Desktop: GNOME 42.3.1 Distro: Pop!_OS 22.04 LTS
|
||||
|
||||
$ inxi -Sv
|
||||
CPU: 8-core AMD Ryzen 7 PRO 5850U with Radeon Graphics (-MT MCP-)
|
||||
speed/min/max: 634/400/4507 MHz Kernel: 5.19.0-76051900-generic x86_64
|
||||
Up: 20m Mem: 3084.2/15318.5 MiB (20.1%) Storage: 953.87 GiB (7.9% used)
|
||||
Procs: 346 Shell: Bash inxi: 3.3.13
|
||||
```
|
||||
|
||||
### Bonus: Check the weather
|
||||
|
||||
Your computer isn't all `inxi` can gather information about. With the `-w` option, you can also get weather information for your locale:
|
||||
|
||||
```
|
||||
$ inxi -w
|
||||
Weather:
|
||||
Report: temperature: 14 C (57 F) conditions: Clear sky
|
||||
Locale: Wellington, G2, NZL
|
||||
current time: Tue 30 Aug 2022 16:28:14 (Pacific/Auckland)
|
||||
Source: WeatherBit.io
|
||||
```
|
||||
|
||||
You can get weather information for other areas of the world by specifying the city and country you want along with `-W` :
|
||||
|
||||
```
|
||||
$ inxi -W rome,italy
|
||||
Weather:
|
||||
Report: temperature: 20 C (68 F) conditions: Clear sky
|
||||
Locale: Rome, Italy current time: Tue 30 Aug 2022 06:29:52
|
||||
Source: WeatherBit.io
|
||||
```
|
||||
|
||||
### Wrap up
|
||||
|
||||
There are many great tools to gather information about your computer. I use different ones depending on the machine, the desktop, or my mood. What are your favorite system information tools?
|
||||
|
||||
Image by: (Don Watkins, CC BY-SA 4.0)
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://opensource.com/article/22/9/linux-inxi-command
|
||||
|
||||
作者：[Don Watkins][a]
|
||||
选题：[lkxed][b]
|
||||
译者：[译者ID](https://github.com/译者ID)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
||||
[a]: https://opensource.com/users/don-watkins
|
||||
[b]: https://github.com/lkxed
|
||||
[1]: https://opensource.com/sites/default/files/lead-images/code_computer_laptop_hack_work.png
|
||||
[2]: https://github.com/smxi/inxi/blob/master/LICENSE.txt
|
||||
[3]: https://smxi.org/docs/inxi-man.htm
|
||||
[4]: https://smxi.org/docs/inxi-installation.htm#inxi-repo-install
|
||||
[5]: https://opensource.com/sites/default/files/2022-09/inxi-c5.png
|
||||
[6]: https://opensource.com/sites/default/files/2022-09/inxi-s.png
|
||||
@@ -0,0 +1,106 @@
|
||||
[#]: subject: "Atoms is a GUI Tool to Let You Manage Linux Chroot Environments Easily"
|
||||
[#]: via: "https://itsfoss.com/atoms-chroot-tool/"
|
||||
[#]: author: "Ankush Das https://itsfoss.com/author/ankush/"
|
||||
[#]: collector: "lkxed"
|
||||
[#]: translator: " "
|
||||
[#]: reviewer: " "
|
||||
[#]: publisher: " "
|
||||
[#]: url: " "
|
||||
|
||||
Atoms is a GUI Tool to Let You Manage Linux Chroot Environments Easily
|
||||
======
|
||||
A chroot environment provides you with isolation for testing in Linux. You do not need to take the hassle of creating a virtual machine. Instead, if you want to test an application or something else, create a chroot environment that allows you to select a different root directory.
|
||||
|
||||
So, with chroot, you get to test stuff without giving the application access to the rest of the system. Any application you install or anything you try gets confined to that directory and does not affect the functioning of your operating system.
|
||||
|
||||
Chroot has its perks, which is why it is a convenient way to test things for various users (especially system administrators).
|
||||
|
||||
Unfortunately, all of this works via the Linux terminal. What if you can have a graphical user interface to make things a little easy? That’s where “**Atoms**” comes in.
|
||||
|
||||
### Atoms: A GUI to Manage Linux Chroot(s)
|
||||
|
||||
![atoms][1]
|
||||
|
||||
Atoms is a GUI tool that makes it convenient to create and manage Linux chroot environments.
|
||||
|
||||
It also supports integration with [Distrobox][2]. So, you can also manage containers using Atoms.
|
||||
|
||||
However, the developers mention that this tool does not offer seamless integration with Podman, explaining its purpose: “*its purpose is only to allow the user to open a shell in a new environment, be it chroot or container.”*
|
||||
|
||||
If you are looking for such a thing, you might want to check out [pods][3].
|
||||
|
||||
### Features of Atoms
|
||||
|
||||
![atoms options][4]
|
||||
|
||||
Atoms is a straightforward GUI program that lets you create chroot environments for several supported Linux distributions.
|
||||
|
||||
Let me highlight the supported distros along with their functionalities offered:
|
||||
|
||||
* Browse files for the chroot(s) created.
|
||||
* Ability to choose mount points to expose.
|
||||
* Access to the console.
|
||||
* Supported Linux distros include Ubuntu, Alpine Linux, Fedora, Rocky Linux, Gentoo, AlmaLinux, OpenSUSE, Debian, and CentOS.
|
||||
|
||||
It is incredibly easy to use. Creating an atom from within the app is a one-click process.
|
||||
|
||||
All you have to do is name the atom, and select the Linux distribution from the list of available options (Ubuntu as the selection in the screenshot above). It downloads the image and sets up the chroot environment for you in a few minutes as shown below.
|
||||
|
||||
![atom config][5]
|
||||
|
||||
Once its done, you can access the options to launch the console to manage the chroot environment or customize/delete it.
|
||||
|
||||
![atoms option][6]
|
||||
|
||||
To access the console, head to the other tab menu. Pretty seamless experience, and works well, at least for Ubuntu that I tested.
|
||||
|
||||
![atoms console][7]
|
||||
|
||||
Additionally, you can detach the console to access it as a separate window.
|
||||
|
||||
![atoms detach console][8]
|
||||
|
||||
### Installing Atoms on Linux
|
||||
|
||||
You can install Atoms on any Linux distribution with the Flatpak package available on [Flathub][9]. Follow our [Flatpak guide][10] if you are new to Linux.
|
||||
|
||||
**Note:** The latest stable version **1.0.2** is only available via Flathub.
|
||||
|
||||
To explore its source code and other details, head to its [GitHub page][11].
|
||||
|
||||
### Conclusion
|
||||
|
||||
The Linux command line is powerful and you can do almost anything with the commands. But not everyone feels comfortable with it and thus tools like Atoms make it more convenient by providing a GUI.
|
||||
|
||||
And Atoms is not the only one of this kind. There is [Grub Customizer][12] that makes it easier to change [Grub][13] configuration which can be done with the command line.
|
||||
|
||||
I believe there are many more such tools out there.
|
||||
|
||||
*What do you think about using a GUI program like Atom to manage Chroot environments? Share your thoughts in the comments down below.*
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://itsfoss.com/atoms-chroot-tool/
|
||||
|
||||
作者：[Ankush Das][a]
|
||||
选题：[lkxed][b]
|
||||
译者：[译者ID](https://github.com/译者ID)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
||||
[a]: https://itsfoss.com/author/ankush/
|
||||
[b]: https://github.com/lkxed
|
||||
[1]: https://itsfoss.com/wp-content/uploads/2022/09/atoms.png
|
||||
[2]: https://itsfoss.com/distrobox/
|
||||
[3]: https://github.com/marhkb/pods
|
||||
[4]: https://itsfoss.com/wp-content/uploads/2022/09/atoms-options.png
|
||||
[5]: https://itsfoss.com/wp-content/uploads/2022/09/atom-config.png
|
||||
[6]: https://itsfoss.com/wp-content/uploads/2022/09/atoms-option.png
|
||||
[7]: https://itsfoss.com/wp-content/uploads/2022/09/atoms-console.png
|
||||
[8]: https://itsfoss.com/wp-content/uploads/2022/09/atoms-detach-console.png
|
||||
[9]: https://flathub.org/apps/details/pm.mirko.Atoms
|
||||
[10]: https://itsfoss.com/flatpak-guide/
|
||||
[11]: https://github.com/AtomsDevs/Atoms
|
||||
[12]: https://itsfoss.com/grub-customizer-ubuntu/
|
||||
[13]: https://itsfoss.com/what-is-grub/
|
||||
Reference in New Issue
Block a user