開源日報 每天推薦一個 GitHub 優質開源項目和一篇精選英文科技或編程文章原文,堅持閱讀《開源日報》,保持每日學習的好習慣。
今日推薦開源項目:《命令速查 linux-command》
今日推薦英文原文:《5 Linux rookie mistakes》
開源日報第396期:《命令速查 linux-command》
今日推薦開源項目:《命令速查 linux-command》傳送門:GitHub鏈接
推薦理由:一個用於快速查找 Linux 命令行命令的項目。當然了這不僅僅是忘記命令時用來提示的工具,對於每一個命令它都給出了語法,說明,選項和一些實例,就算是用於在剛開始使用 Linux 時熟悉命令的教程也可以。畢竟 Linux 上可是有 540 多個命令,除了常用的基本命令之外,把它們一一記全實在是不太容易。
今日推薦英文原文:《5 Linux rookie mistakes》作者:Jen Wike Huger
原文鏈接:https://opensource.com/article/19/4/linux-rookie-mistakes
推薦理由:一些 Linux 新手可能會犯下的錯誤

5 Linux rookie mistakes

It’s smart to learn new skills throughout your life—it keeps your mind nimble and makes you more competitive in the job market. But some skills are harder to learn than others, especially those where small rookie mistakes can cost you a lot of time and trouble when you’re trying to fix them.

Take learning Linux, for example. If you’re used to working in a Windows or MacOS graphical interface, moving to Linux, with its unfamiliar commands typed into a terminal, can have a big learning curve. But the rewards are worth it, as the millions and millions of people who have gone before you have proven.

That said, the journey won’t be without pitfalls. We asked some of Linux enthusiasts to think back to when they first started using Linux and tell us about the biggest mistakes they made.

“Don’t go into [any sort of command line interface (CLI) work] with an expectation that commands work in rational or consistent ways, as that is likely to lead to frustration. This is not due to poor design choices—though it can feel like it when you’re banging your head against the proverbial desk—but instead reflects the fact that these systems have evolved and been added onto through generations of software and OS evolution. Go with the flow, write down or memorize the commands you need, and (try not to) get frustrated when things aren’t what you’d expect.” —Gina Likins

“As easy as it might be to just copy and paste commands to make the thing go, read the command first and at least have a general understanding of the actions that are about to be performed. Especially if there is a pipe command. Double especially if there is more than one. There are a lot of destructive commands that look innocuous until you realize what they can do (e.g., rm, dd), and you don’t want to accidentally destroy things. (Ask me how I know.)” —Katie McLaughlin

“Early on in my Linux journey, I wasn’t as aware of the importance of knowing where you are in the filesystem. I was deleting some file in what I thought was my home directory, and I entered sudo rm -rf * and deleted all of the boot files on my system. Now, I frequently use pwd to ensure that I am where I think I am before issuing such commands. Fortunately for me, I was able to boot my wounded laptop with a USB drive and recover my files.” —Don Watkins

“Do not reset permissions on the entire file system to 777 because you think ‘permissions are hard to understand’ and you want an application to have access to something.” —Matthew Helmke

“I was removing a package from my system, and I did not check what other packages it was dependent upon. I just let it remove whatever it wanted and ended up causing some of my important programs to crash and become unavailable.” —Kedar Vijay Kulkarni
下載開源日報APP:https://openingsource.org/2579/
加入我們:https://openingsource.org/about/join/
關注我們:https://openingsource.org/about/love/