mirror of
https://github.com/LCTT/TranslateProject.git
synced 2024-12-29 21:41:00 +08:00
20150115-1 选题
This commit is contained in:
DeadFire
parent
df75566eaf
commit
d7d9009a1a
@ -0,0 +1,33 @@
|
||||
Configure Mate Desktop With Mate Tweak
|
||||
================================================================================
|
||||
|
||||
|
||||
[Installing Mate Desktop in Ubuntu][1] is one thing but you might be wondering about how to **configure Mate Desktop**? Most of the desktop environments have their own tweaking tools. For example Unity has Unity Tweak Tool, GNOME has Gnome Tweak Tool, Elementary OS has Elementary Tweak Tool. Good news is that Mate Desktop too has its own configuration tweak tool, named [Mate Tweak][2].
|
||||
|
||||
Mate Tweak is a fork of [mintDesktop][3], a configuration tool for Linux Mint.
|
||||
|
||||
### Install Mate Tweak to configure Mate Desktop ###
|
||||
|
||||
Mate Tweak can be easily installed in Ubuntu and Ubuntu based system via its official PPA. Open a terminal and use the following commands:
|
||||
|
||||
sudo add-apt-repository ppa:ubuntu-mate-dev/ppa
|
||||
sudo apt-get update
|
||||
sudo apt-get install mate-tweak
|
||||
|
||||
You can control what shows on the desktop, buttons layout and other interface tweaks and windows behavior. Compare to Unity and Gnome tweak tools, Mate Tweak doesn’t have much to offer in terms of tweaking. For example you can still not [change themes][4] with it but at least it provides an easier way to change some configuration. I hope that it will have more features in near future.
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: http://itsfoss.com/configure-mate-desktop-mate-tweak/
|
||||
|
||||
作者：[Abhishek][a]
|
||||
译者：[译者ID](https://github.com/译者ID)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创翻译，[Linux中国](http://linux.cn/) 荣誉推出
|
||||
|
||||
[a]:http://itsfoss.com/author/Abhishek/
|
||||
[1]:http://itsfoss.com/install-mate-desktop-ubuntu-14-04/
|
||||
[2]:https://bitbucket.org/flexiondotorg/mate-tweak
|
||||
[3]:https://github.com/linuxmint/mintdesktop
|
||||
[4]:http://itsfoss.com/how-to-install-themes-in-ubuntu-13-10/
|
||||
@ -0,0 +1,92 @@
|
||||
How to Manage Network using nmcli Tool in RedHat / CentOS 7.x
|
||||
================================================================================
|
||||
A new feature of [**Red Hat Enterprise Linux 7**][1] and **CentOS 7** is that the default networking service is provided by **NetworkManager**, a dynamic network control and configuration daemon that attempts to keep network devices and connections up and active when they are available while still supporting the traditional ifcfg type configuration files. NetworkManager can be used with the following types of connections: Ethernet, VLANs, Bridges, Bonds, Teams, Wi-Fi, mobile broadband (such as cellular 3G), and IP-over-InfiniBand. For these connection types, NetworkManager can configure network aliases, IP addresses, static routes, DNS information, and VPN connections, as well as many connection-specific parameters.
|
||||
|
||||
The NetworkManager can be controlled with the command-line tool, nmcli.
|
||||
|
||||
### General nmcli usage ###
|
||||
|
||||
The general syntax for nmcli is:
|
||||
|
||||
# nmcli [ OPTIONS ] OBJECT { COMMAND | help }
|
||||
|
||||
One cool thing is that you can use the TAB key to complete actions when you write the command so if at any time you forget the syntax you can just press TAB to see a list of available options.
|
||||
|
||||
|
||||
|
||||
Some examples of general nmcli usage:
|
||||
|
||||
# nmcli general status
|
||||
|
||||
Will display the overall status of NetworkManager.
|
||||
|
||||
# nmcli connection show
|
||||
|
||||
Will display all connections.
|
||||
|
||||
# nmcli connection show -a
|
||||
|
||||
Will display only the active connections.
|
||||
|
||||
# nmcli device status
|
||||
|
||||
Will display a list of devices recognized by NetworkManager and their current state.
|
||||
|
||||
|
||||
|
||||
### Starting / stopping network interfaces ###
|
||||
|
||||
You can use the nmcli tool to start or stop network interfaces from the command line, this is the equivalent of up/down in ifconfig.
|
||||
To stop an interface use the following syntax:
|
||||
|
||||
# nmcli device disconnect eno16777736
|
||||
|
||||
To start it you can use this syntax:
|
||||
|
||||
# nmcli device connect eno16777736
|
||||
|
||||
### Adding an ethernet connection with static IP ###
|
||||
|
||||
To add a new ethernet connection with a static IP address you can use the following command:
|
||||
|
||||
# nmcli connection add type ethernet con-name NAME_OF_CONNECTION ifname interface-name ip4 IP_ADDRESS gw4 GW_ADDRESS
|
||||
|
||||
replacing the NAME_OF_CONNECTION with the name you wish to apply to the new connection, the IP_ADDRESS with the IP address you wish to use and the GW_ADDRESS with the gateway address you use (if you don't use a gateway you can omit this last part).
|
||||
|
||||
# nmcli connection add type ethernet con-name NEW ifname eno16777736 ip4 192.168.1.141 gw4 192.168.1.1
|
||||
|
||||
To set the DNS servers for this connection you can use the following command:
|
||||
|
||||
# nmcli connection modify NEW ipv4.dns "8.8.8.8 8.8.4.4"
|
||||
|
||||
To bring up the new Ethernet connection, issue a command as follows:
|
||||
|
||||
# nmcli connection up NEW ifname eno16777736
|
||||
|
||||
To view detailed information about the newly configured connection, issue a command as follows:
|
||||
|
||||
# nmcli -p connection show NEW
|
||||
|
||||
|
||||
|
||||
Adding a connection that will use DHCP
|
||||
|
||||
If you wish to add a new connection that will use DHCP to configure the interface IP address, gateway address and dns servers, all you have to do is omit the ip/gw address part of the command and Network Manager will use DHCP to get the configuration details.
|
||||
|
||||
For example, to create a DHCP configured connection profile named NEW_DHCP, on device
|
||||
eno16777736 you can use the following command:
|
||||
|
||||
# nmcli connection add type ethernet con-name NEW_DHCP ifname eno16777736
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: http://linoxide.com/linux-command/nmcli-tool-red-hat-centos-7/
|
||||
|
||||
作者：[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/
|
||||
[1]:https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/7.0_Release_Notes/
|
||||
@ -0,0 +1,56 @@
|
||||
Tips for Apache Migration From 2.2 to 2.4 on Ubuntu 14.04
|
||||
================================================================================
|
||||
If you do a distribution upgrade from **Ubuntu** 12.04 to 14.04, the upgrade will bring among other things an important update to **Apache**, from [version 2.2][1] to version 2.4. The update brings many improvements but it may cause some errors when used with the old configuration file from 2.2.
|
||||
|
||||
### Access control in Apache 2.4 Virtual Hosts ###
|
||||
|
||||
Starting with **Apache 2.4** authorization is applied in a way that is much more flexible then just a single check against a single data store like it was in 2.2. In the past it was tricky to figure how and in what order authorization is applied but with the introduction of authorization container directives such as and , the configuration also has control over when the authorization methods are called and what criteria determines when access is granted.
|
||||
|
||||
This is the point where most upgrades fail because of wrong configuration because in 2.2 access control based on IP address, hostname or other characteristic was done using the directives Order, Allow, Deny or Satisfy, but in 2.4 this is done with authorization checks using the new modules.
|
||||
|
||||
To be clear let's see some virtual host examples, this can be found in your /etc/apache2/sites-enabled/default or /etc/apache2/sites-enabled/YOUR_WEBSITE_NAME:
|
||||
|
||||
Old 2.2 virtual host configuration:
|
||||
|
||||
Order allow,deny
|
||||
Allow from all
|
||||
|
||||
New 2.4 virtual host configuration:
|
||||
|
||||
Require all granted
|
||||
|
||||
|
||||
|
||||
### .htaccess problems ###
|
||||
|
||||
If after the upgrade some settings don't work or you get redirect errors, check if those settings are in a .htaccess file. If settings in the .htaccess file are not used by Apache it's because in 2.4 AllowOverride directive is set to None by default, thus ignoring the .htaccess files. All you have to do is to either change or add the AllowOverride All directive to your site configuration file.
|
||||
|
||||
You also see the AllowOverride All directive set in the screenshot above.
|
||||
|
||||
### Missing config file or module ###
|
||||
|
||||
From my experience another problem during upgrades is that your configuration file includes an old module or configuration file that is no longer needed or supported in 2.4, you will get a clear warning that Apache can't include the respective file and all you have to do is go to your configuration file and remove the line that causes problem. Afterwards you can search or install a similar module.
|
||||
|
||||
### Other small changes you shound know about ###
|
||||
|
||||
There are a few other changes that you should consider, although they generally result in an warning and not an error:
|
||||
|
||||
- MaxClients has been renamed to MaxRequestWorkers, which describes more accurately what it does. For async MPMs, like event, the maximum number of clients is not equivalent than the number of worker threads. The old name is still supported.
|
||||
- The DefaultType directive no longer has any effect, other than to emit a warning if it's used with any value other than none. You need to use other configuration settings to replace it in 2.4.
|
||||
- EnableSendfile now defaults to Off.
|
||||
- FileETag now defaults to "MTime Size" (without INode).
|
||||
- KeepAlive only accepts values of On or Off. Previously, any value other than "Off" or "0" was treated as "On".
|
||||
- Directives AcceptMutex, LockFile, RewriteLock, SSLMutex, SSLStaplingMutex, and WatchdogMutexPath have been replaced with a single Mutex directive. You will need to evaluate any use of these removed directives in your 2.2 configuration to determine if they can just be deleted or will need to be replaced using Mutex.
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: http://linoxide.com/linux-how-to/apache-migration-2-2-to-2-4-ubuntu-14-04/
|
||||
|
||||
作者：[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/
|
||||
[1]:http://httpd.apache.org/docs/2.4/
|
||||
Loading…
Reference in New Issue
Block a user