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

20131014-5 选题

Browse Source
This commit is contained in:
DeadFire 2013-10-14 21:21:51 +08:00
parent 64b8891ef6
commit 5afb6f9fdf
4 changed files with 250 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

35
sources/Daily Ubuntu Tips–Things To Do After Installing Ubuntu.md Normal file
View File

@ -0,0 +1,35 @@
Daily Ubuntu Tips–Things To Do After Installing Ubuntu
================================================================================
Many users from Windows find themselves stuck when starting out with Ubuntu. It’s a completely different from Windows and getting confortable with it may not be the easiest thing at first. Ubuntu is way different from Windows. The commands, the layout of the file system and application names are all foreign to many. But heck, we’re here to help.
If you’re coming from Windows or Mac OS X and want to learn Ubuntu, you’re in the right place. We try to help new users get started with Ubuntu. Our slogan here is “**Tutorials for newbies**”, which is rightly so.
Most of our tutorials are not for pros. They are for people who are just starting out with Windows and Ubuntu. So, for all your Ubuntu needs, keep coming back.
Now, back to the topic. One of our readers asked us this question few days ago.
> What should you do first after installing Ubuntu?
Simple. When you first install Ubuntu, there are many things you may want to get started with. But the most important thing is to get it right. Don’t worry about the difficult things, those you’ll learn later.
Here are the first few things you’ll want do after installing Ubuntu. There might be more, but these are important.
- Update your system – The very first thing is to update your system. Updating allows you to install newer packages and install fixes for other programs. The commands below will show you how to properly update your system when using Ubuntu.
sudo apt-get update && sudo apt-get dist-upgrade && sudo apt-get autoremove
- Another thing to do right after installing Ubuntu is to run the below command. This command helps you install codecs or packages that were left out of Ubuntu for legal reasons. Ubuntu comes without these important programs and they are very useful. Without them you may not be able to listen to music, watch movies and do other things. So, if you installed Ubuntu and can’t play some DVDs or listen to music CDs, then run the commands below.
sudo apt-get install ubuntu-restricted-extras
The commands above are not the only commands you’ll run in Ubuntu, but they are few of the first you should run after installing Ubuntu. I hope this helps.
Enjoy!
--------------------------------------------------------------------------------
via: http://www.liberiangeek.net/2013/10/daily-ubuntu-tipsthings-to-do-after-installing-ubuntu/
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创翻译，[Linux中国](http://linux.cn/) 荣誉推出
译者：[译者ID](https://github.com/译者ID) 校对：[校对者ID](https://github.com/校对者ID)

48
sources/Install Rhythmbox 3.0 In Ubuntu 13.10 Or 13.04.md Normal file
View File

@ -0,0 +1,48 @@
Install Rhythmbox 3.0 In Ubuntu 13.10 Or 13.04
================================================================================
Rhythmbox 3.0 was released more than a month ago, bringing an improved user interface, Python 3 support for the plugins and more. Unfortunately, the new version didn't make it into Ubuntu 13.10, but there's a PPA you can use to install it (also available for Ubuntu 13.04).
![](http://dl.dropboxusercontent.com/u/1113424/img/rhythmbox-3.0.png)
Changes in Rhythmox 3.0:
- the plugins now use Python 3;
- new task progress display below the track list (used for various things including track transfers and import jobs);
- support for composer tags;
- restyled playback controls;
- restyled source list using symbolic icons;
- better introspection of everything;
- separate CBR and VBR encoding styles with different sets of exposed properties;
- playlist settings (browser visibility etc.) saved in playlists.xml;
- better use of RTL icons where appropriate;
- fixed IM status and ReplayGain plugins;
- many other bug fixes.
A complete Rhythmbox 3.0 changelog can be found [HERE][1].
## Install Rhythmbox 3.0 in Ubuntu 13.10 or 13.04 ##
![](http://dl.dropboxusercontent.com/u/1113424/img/rhythmbox-3.0_2.png)
*Rhythmbox 3.0 in Ubuntu 13.10 (Unity)*
Because Rhythmbox 3.0 uses Python3 for plugins instead of Python 2, **none of the plugins available in the Rhythmbox [third-party plugins PPA][2] will work**. You can get some of them to work by installing them manually (including the Equalizer plugin and the cool **[CoverArt browser][3]**) - for more info, see **[THIS][4]** article.
Rhythmbox 3.0 is available in an unofficial PPA maintained by Jacob Zimmermann, for Ubuntu 13.10 and 13.04 (and derivatives). **Add the PPA and install/upgrade Rhythmbox 3.0 using the following commands**:
sudo add-apt-repository ppa:jacob/media
sudo apt-get update
sudo apt-get install rhythmbox
--------------------------------------------------------------------------------
via: http://www.webupd8.org/2013/10/install-rhythmbox-30-in-ubuntu-1310-or.html
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创翻译，[Linux中国](http://linux.cn/) 荣誉推出
译者：[译者ID](https://github.com/译者ID) 校对：[校对者ID](https://github.com/校对者ID)
[1]:http://ftp.acc.umu.se/pub/GNOME/sources/rhythmbox/3.0/rhythmbox-3.0.news
[2]:http://www.webupd8.org/2012/08/rhythmbox-third-party-plugins-ubuntu-ppa.html
[3]:http://www.webupd8.org/2013/08/rhythmbox-coverart-browser-plugin-gets.html
[4]:http://xpressubuntu.wordpress.com/2013/10/06/how-to-install-rhythmbox-3-0-in-saucy/

79
sources/Linux Terminal--Seeing the unseen characters with cat!.md Normal file
View File

@ -0,0 +1,79 @@
Linux Terminal: Seeing the unseen characters with cat!
================================================================================
Sometimes a program or software don’t start for a syntax error, and if you check the files there is nothing wrong..apparently.
There are a lot of characters that usually are not printed if you use a normal text editor, but you can easily check if they are present with your terminal and the command cat.
As first thing let’s create a simple text file with these special characters, open a terminal and run the command:
printf 'testing\012\011\011testing\014\010\012more testing\012\011\000\013\000even more testing\012\011\011\011\012' > /tmp/testing.txt
Now if you open the file with an editor you’ll have different results.
A simple cat will show:
$ cat /tmp/testing.txt
testing
testing
more testing
even more testing
While if you open it with nano or vim you’ll see :
testing
testing^L^H
more testing
^@^K^@even more testing
Now we can see some options of cat to print special characters.
1) Use cat -T to display TAB characters as ^I
cat -T /tmp/testing.txt
testing
^I^Itesting
more testing
^I
even more testing
^I^I^I
2) Use cat -E to display $ at end of each line
$ cat -E /tmp/testing.txt
testing$
testing
$
more testing$
even more testing$
$
3) Use a simple cat -A to show up all the invisible characters:
$ cat -A /tmp/testing.txt
testing$
^I^Itesting^L^H$
more testing$
^I^@^K^@even more testing$
^I^I^I$
--------------------------------------------------------------------------------
via: http://linuxaria.com/pills/linux-terminal-seeing-the-unseen-characters-with-cat?lang=en#more-7645
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创翻译，[Linux中国](http://linux.cn/) 荣誉推出
译者：[译者ID](https://github.com/译者ID) 校对：[校对者ID](https://github.com/校对者ID)
[1]:
[2]:
[3]:
[4]:
[5]:
[6]:
[7]:
[8]:
[9]:
[10]:

88
sources/Mastering the “Kill” Command in Linux.md Normal file
View File

@ -0,0 +1,88 @@
Mastering the “Kill” Command in Linux
================================================================================
It doesn’t matter which operating system you are using, you will surely come across a misbehaving application that lock itself up and refuse to close. In Linux (and Mac), there is this “kill” command that you can use to terminate the application forcefully. In this tutorial, we will show you the various way you can make use of the “kill” command to terminate an application.
**Kill Commands and Signals**
When you execute a “kill” command, you are in fact sending a signal to the system to instruct it to terminate the misbehaving app. There is a total of 60 signals that you can use, but all you really need to know is SIGTERM (15) and SIGKILL (9).
You can view all the signals with the command:
kill -l
![](http://i1.wp.com/imagecdn5.maketecheasier.com/2013/10/kill-list-signal.png)
- SIGTERM – This signal requests a process to stop running. This signal can be ignored. The process is given time to gracefully shutdown. When a program gracefully shuts down, that means it is given time to save its progress and release resources. In other words, it is not forced to stop.
- SIGKILL – The SIGKILL signal forces the process to stop executing immediately. The program cannot ignore this signal. Unsaved progress will be lost.
The syntax for using “kill” is:
kill [signal or option] PID(s)
The default signal (when none is specified) is SIGTERM. When that doesn’t work, you can use the following to kill a process forcefully:
kill SIGKILL PID
or
kill -9 PID
where the “-9” flag refers to SIGKILL signal.
If you are not aware of the PID of the application, simply run the command:
ps ux
and it will display all the running applications together with its PID.
![](http://i1.wp.com/imagecdn5.maketecheasier.com/2013/10/kill-find-pid.png)
For example, to kill the Chrome app, I will run the command:
kill -9 3629
Do also note that you can kill multiple processes at the same time.
kill -9 PID1 PID2 PID 3
**PKill**
The “pkill” command allows the use of extended regular expression patterns and other matching criteria. Instead of using PID, you can now kill application by entering their process name. For example, to kill Firefox browser, just run the command:
pkill firefox
As it matches regular expression pattern, you can also enter partial name of the process, such as:
pkill fire
To avoid killing the wrong processes, you might want to do a “pgrep -l [process name]” to list the matching processes.
![](http://i0.wp.com/imagecdn5.maketecheasier.com/2013/10/kill-pgrep-command.png)
**Killall**
Killall uses the process name as well instead of PID, and it kills all instance of the process with the same name. For example, if you are running multiple instances of Firefox browser, you can kill them all with the command:
killall firefox
In Gnome, you can restart Nautilus by using the command:
killall nautilus
**xkill**
Xkill is a graphical way to kill an application. When you type “xkill” in the terminal, your mouse cursor will instantly become a “cross”. All you have to do is to click the “cross” at the misbehaving app and it will kill the application instantly. If you are keen, you can also add a [keyboard shortcut to activate the xkill][1] function.
**Conclusion**
When apps misbehave and cause the system to hang, it is very tempting to restart the computer and start the session all over again. With these “kill” commands, you will be able to better manage the misbehaving apps without them causing the system to crash. This is especially useful for a server when you don’t want a misbehaving process to bring the whole server down.
--------------------------------------------------------------------------------
via: http://www.maketecheasier.com/kill-command-in-linux/
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创翻译，[Linux中国](http://linux.cn/) 荣誉推出
译者：[译者ID](https://github.com/译者ID) 校对：[校对者ID](https://github.com/校对者ID)
[1]:http://www.maketecheasier.com/quick-tips/kill-unresponsive-application-in-ubuntu/