mirror of
https://github.com/LCTT/TranslateProject.git
synced 2024-12-26 21:30:55 +08:00
20131104-1 选题
This commit is contained in:
DeadFire
parent
4dcf04a3fd
commit
1f1188df0a
124
sources/12 Practical Examples of Linux grep Command.md
Normal file
124
sources/12 Practical Examples of Linux grep Command.md
Normal file
@ -0,0 +1,124 @@
|
||||
12 Practical Examples of Linux grep Command
|
||||
================================================================================
|
||||
Have you ever been confronted with the task of looking for a particular string or pattern in a file, yet have no idea where to start looking? Well then, here is **grep** to the rescue!
|
||||
|
||||
|
||||
|
||||
*12 Grep Command Examples*
|
||||
|
||||
**grep** is a powerful file pattern searcher that comes equipped on every distribution of **Linux**. If, for whatever reason, it is not installed on your system, you can easily install it via your package manager (**apt-get** on **Debian/Ubuntu** and **yum** on **RHEL/CentOS/Fedora**).
|
||||
|
||||
$ sudo apt-get install grep #Debian/Ubuntu
|
||||
|
||||
|
||||
$ sudo yum install grep #RHEL/CentOS/Fedora
|
||||
|
||||
I have found that the easiest way to get your feet wet with **grep** is to just dive right in and use some real world examples.
|
||||
|
||||
### 1. Search and Find Files ###
|
||||
|
||||
Let’s say that you have just installed a fresh copy of the new **Ubuntu** on your machine, and that you are going to give **Python** scripting a shot. You have been scouring the web looking for tutorials, but you see that there are two different versions of **Python** in use, and you don’t know which one was installed on your system by the **Ubuntu** installer, or if it installed any modules. Simply run this command:
|
||||
|
||||
$ sudo dpkg –l | grep –i python
|
||||
|
||||
#### Sample Output ####
|
||||
|
||||
ii python2.7 2.7.3-0ubuntu3.4 Interactive high-level object-oriented language (version 2.7)
|
||||
ii python2.7-minimal 2.7.3-0ubuntu3.4 Minimal subset of the Python language (version 2.7)
|
||||
ii python-openssl 0.12-1ubuntu2.1 Python wrapper around the OpenSSL library
|
||||
ii python-pam 0.4.2-12.2ubuntu4 A Python interface to the PAM library
|
||||
|
||||
First, we ran **dpkg –l**, which lists installed ***.deb** packages on your system. Second, we piped that output to **grep –i** python, which simple states “go to grep and filter out and return everything with ‘python’ in it.” The **–i** option is there to ignore-case, as **grep** is case-sensitive. Using the **–i** option is a good habit of getting into, unless of course you are trying to nail down a more specific search.
|
||||
|
||||
### 2. Search and Filter Files ###
|
||||
|
||||
The grep can also be used to search and filter within individual files or multiple files. Lets take this scenario:
|
||||
|
||||
You are having some trouble with your **Apache Web Server**, and you have reached out to one of the many awesome forums on the net asking for some help. The kind soul who replies to you has asked you to post the contents of your **/etc/apache2/sites-available/default-ssl** file. Wouldn’t it be easier for you, the guy helping you, and everyone reading it, if you could remove all of the commented lines? Well you can! Just run this:
|
||||
|
||||
$ sudo grep –v “#” /etc/apache2/sites-available/default-ssl
|
||||
|
||||
The **–v** option tells **grep** to invert its output, meaning that instead of printing matching lines, do the opposite and print all of the lines that don’t match the expression, in this case, the **#** commented lines.
|
||||
|
||||
### 3. Find all .mp3 Files Only ###
|
||||
|
||||
The **grep** can be very useful for filtering from **stdout**. For example, let’s say that you have an entire folder full of music files in a bunch of different formats. You want to find all of the ***.mp3** files from the artist **JayZ**, but you don’t want any of the remixed tracks. Using a **find command** with a couple of **grep** pipes will do the trick:
|
||||
|
||||
$ sudo find . –name “*.mp3” | grep –i JayZ | grep –vi “remix”
|
||||
|
||||
In this example, we are using find to print all of the files with a ***.mp3 extension**, piping it to **grep –i** to filter out and prints all files with the name “**JayZ**” and then another pipe to **grep –vi** which filters out and does not print all filenames with the string (in any case) “**remix**”.
|
||||
|
||||
- [35 Practical Examples of Linux Find Command][1]
|
||||
|
||||
### 4. Display Number of Lines Before or After Search String ###
|
||||
|
||||
Another couple of options are the –A and –B switches, which displays the matched line and number of lines either that come before or after the search string. While the man page gives a more detailed explanation, I find it easiest to remember the options as –A = after, and –B = before:
|
||||
|
||||
$ sudo ifconfig | grep –A 4 eth0
|
||||
$ sudo ifconfig | grep -B 2 UP
|
||||
|
||||
### 5. Prints Number of Lines Around Match ###
|
||||
|
||||
The grep’s **–C** option is similar, but instead of printing the lines that come either before or after the string, it prints the lines in either direction:
|
||||
|
||||
$ sudo ifconfig | grep –C 2 lo
|
||||
|
||||
### 6. Count Number of Matches ###
|
||||
|
||||
Similar to piping a **grep** string to word count (**wc** program) grep’s built-in option can perform the same for you:
|
||||
|
||||
$ sudo ifconfig | grep –c inet6
|
||||
|
||||
### 7. Search Files by Given String ###
|
||||
|
||||
The **–n** option for **grep** is very useful when debugging files during compile errors. It displays the line number in the file of the given search string:
|
||||
|
||||
$ sudo grep –n “main” setup..py
|
||||
|
||||
### 8. Search a string Recursively in all Directories ###
|
||||
|
||||
If you would like to search for a string in the current directory along with all of the subdirectories, you can specify the **–r** option to search recursively:
|
||||
|
||||
$ sudo grep –r “function” *
|
||||
|
||||
### 9. Searches for the entire pattern ###
|
||||
|
||||
Passing the **–w** option to grep searches for the entire pattern that is in the string. For example, using:
|
||||
|
||||
$ sudo ifconfig | grep –w “RUNNING”
|
||||
|
||||
Will print out the line containing the pattern in quotes. On the other hand, if you try:
|
||||
|
||||
$ sudo ifconfig | grep –w “RUN”
|
||||
|
||||
Nothing will be returned as we are not searching for a pattern, but an entire word.
|
||||
|
||||
### 10. Search a string in Gzipped Files ###
|
||||
|
||||
Deserving some mention are grep’s derivatives. The first is **zgrep**, which, similar to **zcat**, is for use on **gzipped** files. It takes the same options as **grep** and is used in the same way:
|
||||
|
||||
$ sudo zgrep –i error /var/log/syslog.2.gz
|
||||
|
||||
### 11. Match Regular Expression in Files ###
|
||||
|
||||
The **egrep** is another derivative that stands for “**Extended Global Regular Expression**”. It recognizes additional expression meta-characters such **at + ?** | and **()**. egrep is very useful for searching source files, and other pieces of code, should the need arise. It can be invoked from regular grep by specifying the **–E** option.
|
||||
|
||||
$ sudo grep –E
|
||||
|
||||
### 12. Search a Fixed Pattern String ###
|
||||
|
||||
The **fgrep** searches a file or list of files for a fixed pattern string. It is the same as **grep –F**. A common way of using **fgrep** is to pass a file of patterns to it:
|
||||
|
||||
$ sudo fgrep –f file_full_of_patterns.txt file_to_search.txt
|
||||
|
||||
This is just a starting point with **grep**, but as you are probably able to see, it is invaluable for a variety of purposes. Aside from the simple one line commands we have implemented, **grep** can be used to write powerful **cron** jobs, and robust **shell scripts**, for a start. Be creative, experiment with the options in the **man page**, and come up with **grep expressions** that serve your own purposes!
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: http://www.tecmint.com/12-practical-examples-of-linux-grep-command/
|
||||
|
||||
译者：[译者ID](https://github.com/译者ID) 校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创翻译，[Linux中国](http://linux.cn/) 荣誉推出
|
||||
|
||||
[1]:http://www.tecmint.com/35-practical-examples-of-linux-find-command/
|
||||
@ -0,0 +1,35 @@
|
||||
Daily Ubuntu Tips–Update To LibreOffice Latest In Ubuntu Via PPA
|
||||
================================================================================
|
||||
For every new Ubuntu you install, you’ll also have LibreOffice, the office productivity tool that allows you to create and manage documents. Most people are aware of Microsoft Word, Excel, PowerPoint and Outlook but few know about LibreOffice.
|
||||
|
||||
LibreOffice is made available by volunteers around the world and is backed by a charitable foundation. It is the primary office productivity tool in the Linux community and it’s free. It can be installed on Windows, Mac OS X and Linux computers.
|
||||
|
||||
Just today, a new release was made available to the public. Windows, Mac OS X and Linux users can go directly to the download page and download the latest release.
|
||||
|
||||
An advantage Ubuntu users have is they can add LibreOffice’s software repository to your their computer to install the latest releases. This is useful if you wish to quickly get every latest release when it’s made available.
|
||||
|
||||
The current release family of LibreOffice is 4.1. Every subsequent release will be available instantly in the 4.1 repository until a new mainline is launched which maybe version 4.2.
|
||||
|
||||
So, to always upgrade automatically in Ubuntu, add the software repository below.
|
||||
|
||||
sudo add-apt-repository ppa:libreoffice/ppa
|
||||
|
||||
Next, run the commands below to upgrade to the latest version LibreOffice.
|
||||
|
||||
sudo apt-get update && sudo apt-get dist-upgrade
|
||||
|
||||
That’s it. When you add the repository above and update your system, Ubuntu will automatically download and install LibreOffice latest releases.
|
||||
|
||||
Windows and Mac OS X users may upgrade directly from within the program suite or download it directly from the web.
|
||||
|
||||
|
||||
|
||||
Enjoy!
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: http://www.liberiangeek.net/2013/11/daily-ubuntu-tipsupdate-to-libreoffice-latest-in-ubuntu-via-ppa/
|
||||
|
||||
译者：[译者ID](https://github.com/译者ID) 校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创翻译，[Linux中国](http://linux.cn/) 荣誉推出
|
||||
@ -0,0 +1,33 @@
|
||||
KDE and Canonical Conflict Over Mir Finally Bursts into Open
|
||||
================================================================================
|
||||
The conflict that has been brewing between the KDE developers and Canonical has finally exploded in a flurry of statements which show just how many problems the Mir display server has caused.
|
||||
|
||||
KDE and Canonical, especially Mark Shuttleworth, have been friends for a long time. Once upon a time, back in 2006, Mark Shuttleworth was the first patron of KDE and people were uttering things like this:
|
||||
|
||||
“I have no doubt that you will do the right thing once you actually see the true potential that KDE4 could bring. You are a true visionary. The world needs more people like you,” said one of the members of the KDE community.
|
||||
|
||||
Seven years later, Canonical announces a new displayer server and everything that KDE, Kubuntu, and Canonical communities have built together goes out the window.
|
||||
|
||||
The war of declarations has culminated with [a post written by Mark Shuttleworth][1] in which he grouped all the people that have been criticizing the Mir display server, on purely political reasons in his opinion, into a virtual “Tea Party”. A lot of people took offense, especially a couple of prolific KDE developers who opposed Mir straight from the get-go.
|
||||
|
||||
KDE Plasma developers and president of KDE e.v, Aaron Seigo, challenged Mark Shuttleworth to a debate regarding the issue. [The founder of Canonical has ignored][2] his request, which prompted a second reaction which turned out to be a lot more acid that the first comments.
|
||||
|
||||
The second reaction came from one of the Kwin developers and maintainers, Martin Gräßlin, which has basically [said goodbye to the Ubuntu community][3]. The reactions to his Google+ post have been mixed and it promoted a reaction from the Ubuntu community manager, Jono Bacon.
|
||||
|
||||
“Open Source has been and will always be filled with very energetic discussion. In some cases this discussion blurs into the area of rudeness and disrespect. The difficulty is that everyone's definition of what is rude and disrespectful is different. Likewise, everyone's definition of good and bad conduct is different,” said Jono Bacon in his post.
|
||||
|
||||
He expressed his regret towards the decision of Martin Gräßlin, but he also pointed out the Ubuntu Code of Conduct 2.0, which has been broken so many times it's hard to keep count.
|
||||
|
||||
As it stands right now, KDE will never adopt Mir, Kubuntu will probably follow suite, and the days of this Ubuntu flavor are probably numbered.
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: http://news.softpedia.com/news/KDE-and-Canonical-Conflict-Over-Mir-Finally-Bursts-into-Open-396651.shtml
|
||||
|
||||
译者：[译者ID](https://github.com/译者ID) 校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创翻译，[Linux中国](http://linux.cn/) 荣誉推出
|
||||
|
||||
[1]:http://news.softpedia.com/news/Mark-Shuttleworth-Says-That-Mir-Opponents-Have-Formed-the-Open-Source-Tea-Party-392793.shtml
|
||||
[2]:http://news.softpedia.com/news/KDE-Developer-and-President-of-KDE-e-v-Upset-Because-Mark-Shuttleworth-Is-Ignoring-Him-396623.shtml
|
||||
[3]:http://news.softpedia.com/news/Major-KDE-Developer-Says-Goodbye-to-Ubuntu-396429.shtml
|
||||
Loading…
Reference in New Issue
Block a user