20141222-2 选题

This commit is contained in:
DeadFire 2014-12-22 15:37:01 +08:00
parent 44d2576118
commit 17669ee7a2
3 changed files with 214 additions and 0 deletions

View File

@ -0,0 +1,44 @@
Linus Torvalds Launches Linux Kernel 3.19 RC1, One of the Biggest So Far
================================================================================
> new development cycle for Linux kernel has started
![](http://i1-news.softpedia-static.com/images/news2/Linus-Torvalds-Launches-Linux-kernel-3-19-RC1-One-of-the-Biggest-So-Far-468043-2.jpg)
**The first Linux kernel Release Candidate has been made available in the 3.19 branch and it looks like it's one of the biggest ones so far. Linux Torvalds surprised everyone with an early launch, but it's easy to understand why.**
The Linux kernel development cycle has been refreshed with a new released, 3.19. Given the fact that the 3.18 branch reached stable status just a couple of weeks ago, today's release was not completely unexpected. The holidays are coming and many of the developers and maintainers will probably take a break. Usually, a new RC is launched on a weekly basis, but users might see a slight delay this time.
There is no mention of the regression problem that was identified in Linux kernel 3.18, but it's pretty certain that they are still working to fix it. On the other hand, Linux did say that this is a very large released, in fact it's one of the biggest ones made until now. It's likely that many devs wanted to push their patches before the holidays, so the next RC should be a smaller.
### Linux kernel 3.19 RC1 marks the start of a new cycle ###
The size of the releases has been increasing, along with the frequency. The development cycle for the kernel usually takes about 8 to 10 weeks and it seldom happens to be more than that, which brings a nice predictability for the project.
"That said, maybe there aren't any real stragglers - and judging by the size of rc1, there really can't have been much. Not only do I think there are more commits than there were in linux-next, this is one of the bigger rc1's (at least by commits) historically. We've had bigger ones (3.10 and 3.15 both had large merge windows leading up to them), but this was definitely not a small merge window."
"In the 'big picture', this looks like a fairly normal release. About two thirds driver updates, with about half of the rest being architecture updates (and no, the new nios2 patches are not at all dominant, it's about half ARM, with the new nios2 support being less than 10% of the arch updates by lines overall)," [reads][1] the announcement made by Linus Torvalds.
More details about this RC can be found on the official mailing list.
#### Download Linux kernel 3.19 RC1 source package: ####
- [tar.xz (3.18.1 Stable)][3]File size: 77.2 MB
- [tar.xz (3.19 RC1 Unstable)][4]
It you want to test it, you will need to compile it yourself although it's advisable to not use a production machines.
--------------------------------------------------------------------------------
via: http://news.softpedia.com/news/Linus-Torvalds-Launches-Linux-kernel-3-19-RC1-One-of-the-Biggest-So-Far-468043.shtml
作者:[Silviu Stahie ][a]
译者:[译者ID](https://github.com/译者ID)
校对:[校对者ID](https://github.com/校对者ID)
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创翻译,[Linux中国](http://linux.cn/) 荣誉推出
[a]:http://news.softpedia.com/editors/browse/silviu-stahie
[1]:http://lkml.iu.edu/hypermail/linux/kernel/1412.2/02480.html
[2]:http://linux.softpedia.com/get/System/Operating-Systems/Kernels/Linux-Kernel-Development-8069.shtml
[3]:https://www.kernel.org/pub/linux/kernel/v3.x/linux-3.18.1.tar.xz
[4]:https://www.kernel.org/pub/linux/kernel/v3.x/testing/linux-3.19-rc1.tar.xz

View File

@ -0,0 +1,97 @@
A Great Tool To Show Linux Command Progress Like % , ETA
================================================================================
Coreutils Viewer (**cv**) is a simple program that can be used to show the progress of any of coreutils commands. It uses information from file descriptors to determine the progress of a command for example the cp command. The beauty of **cv** is that it can be used with other linux commands like watch and I/O redirection commands as you shall see. This allows you to use it in a script, or however you like, your imagination will be the limit.
### Installation ###
You can download the source files for cv from its [github repository here][1]. Once you have downloaded the zip file extract it and then change directory to the extracted folder.
The program dependencies is the **ncurses library**. If you have installed ncurses in your Linux box then installation of cv will be a breeze.
Compiling and installation can be done in two easy steps.
$ make
$ sudo make install
### Running cv ###
To run cv, just type it on the command line as other programs. If you did not make install and chose to run it from the current directory run the command as follows:
$ ./cv
Otherwise run the command as follows.
$ cv
If there are no coreutils commands running then the cv program will exit and tell you, no coreutils program is running.
![cv no command](http://blog.linoxide.com/wp-content/uploads/2014/11/cv-no-command.png)
To effectively use the program have one of the coreutils programs running on your system. In this case we shall use the command **cp**.
When copying a large file you can see the progress, shown as a percentage
![cv default](http://blog.linoxide.com/wp-content/uploads/2014/11/cv-default.png)
### Adding Options To cv ###
You can also add several option to the cv command just like other commands. One useful option is having to know the estimated time remaining for a copying operation or a move operation particularly for large files.
Adding the **-w** option will just do exactly that.
$ cv -w
![cv estimated throughput](http://blog.linoxide.com/wp-content/uploads/2014/11/cv-estimated-throughput.png)
Try adding more command options. Adding other options like this:
$ cv -wq
### cv And watch Command ###
watch is a program used to run a program periodically and then show the output. Sometimes you might want to see the commands as they are running without storing the data in a log file. In this case watch comes in handy to use with cv.
$ watch cv -qw
This command will show any running instances of coreutils commands. It will also show the progress and the ETA.
![cv and watch](http://blog.linoxide.com/wp-content/uploads/2014/11/cv-and-watch-e1416519384265.png)
### View Output In A Log File ###
As promised, with cv you can redirect its output to a log file. This is particularly useful when the command runs too fast to see anything meaningful.
To see the progress in a log file you can simply redirect the output as in the command below.
$ cv -w >> log.txt
To see the output of this command open the log file with your favourite text editor or with the cat command as follows:
$ cat log.txt
### Getting Help ###
If you get stuck anywhere you can always refer to the man page or the help option.
To get help use cv command with the **-h** option.
$ cv -h
If you need more detailed information then the man page would be a great place to visit.
$ man cv
However, to get the man page with the above command, ensure that you make install cv.
Yay! Now you have another great tool in your Linux toolbox.
--------------------------------------------------------------------------------
via: http://linoxide.com/linux-command/tool-show-command-progress/
作者:[Allan Mbugua][a]
译者:[译者ID](https://github.com/译者ID)
校对:[校对者ID](https://github.com/校对者ID)
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创翻译,[Linux中国](http://linux.cn/) 荣誉推出
[a]:http://linoxide.com/author/allan/
[1]:http://github.com/Xfennec/cv

View File

@ -0,0 +1,73 @@
How to Sync Time Properly with NTP Server in CentOS 7.x
================================================================================
**Chrony** is an open source and free application that helps you keep the system clock in sync with a NTP server, thus allowing you to keep the exact time. It consists of two programs chronyd and chronyc. chronyd is the daemon that runs in the background and adjusts the system clock which is running in the kernel to the time on a NTP server. It determines the rate at which the computer gains or loses time, and compensates for this. chronyc provides a user interface for monitoring the performance and configuring various settings. It can do so while running on the same computer as the chronyd instance it is controlling or a different remote computer.
Chrony comes installed by default on RHEL based operating systems like CentOS 7.
### Chrony configuration ###
When it starts Chrony will read the settings in /etc/chrony.conf configuration file. The most important settings on a CentOS 7 operating system are:
**server** - This can be used multiple times to add NTP server, it should be used in the format "server ". In general you can add as many server addresses as you wish.
Example:
server 0.centos.pool.ntp.org
server 3.europe.pool.ntp.org
**stratumweight** - The stratumweight directive sets how much distance should be added per stratum to the synchronization distance when chronyd selects the synchronization source from available sources. By default in CentOS it's 0, to makes chronyd ignore stratum when selecting the source
**driftfile** - One of the main activities of the chronyd program is to work out the rate at which the system clock gains or loses time relative to real time. Each time chronyd has a new value of gain/loss rate, it is desirable to record it in a file and this will allow it to compansate the system clock at the rate it was last restarted, even before it has a chance to obtain good estimate from the NTP server.
**rtcsync** - The rtcsync directive will enable a kernel mode where the system time is copied to the real time clock (RTC) every 11 minutes.
**allow / deny** - here you can specify a host, subnet, or network from which to allow or deny NTP connections to a machine acting as NTP server.
Examples:
allow 192.168.4.5
deny 192.168/16
**cmdallow / cmddeny** - same as allow only that you can specifiy witch IP address or host to have control command over chronyd
**bindcmdaddress** - this directive allows you to restrict the network interface to which chronyd will listen for command packets (issued by chronyc). This provides an additional level of access restriction above that available through cmddeny mechanism.
Example:
bindcmdaddress 127.0.0.1
bindcmdaddress ::1
**makestep** - normally chronyd will cause the system to gradually correct any time offset, by slowing down or speeding up the clock as required. In certain situations, the system clock may be so far adrift that this slewing process would take a very long time to correct the system clock. This directive forces chronyd to step system clock if the adjustment is larger than a threshold value, but only if there were no more clock updates since chronyd was started than a specified limit (a negative value can be used to disable the limit).
### Using chronyc ###
You can also change settings by running the chronyc command and then use one of the following commands:
**accheck** - Check whether NTP access is allowed on the speicif host
**activity** - This will display how many NTP sources are online/offline
![](http://blog.linoxide.com/wp-content/uploads/2014/10/chrony-activity.jpg)
**add server** - Add a new NTP server manually.
**clients** - Report on clients that have accessed the server
**delete** - Manually remove an NTP server or peer
**settime** - Manually set the daemon time
**tracking** - Display system time information
You can see the full list of commands by using the help command:
![](http://blog.linoxide.com/wp-content/uploads/2014/10/commands.jpg)
--------------------------------------------------------------------------------
via: http://linoxide.com/linux-command/chrony-time-sync/
作者:[Adrian Dinu][a]
译者:[译者ID](https://github.com/译者ID)
校对:[校对者ID](https://github.com/校对者ID)
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创翻译,[Linux中国](http://linux.cn/) 荣誉推出
[a]:http://linoxide.com/author/adriand/