mirror of
https://github.com/LCTT/TranslateProject.git
synced 2025-01-13 22:30:37 +08:00
commit
50322ef0d4
@ -125,4 +125,4 @@ LCTT的组成
|
||||
* 2014/05/04 更换了新的QQ群:198889102
|
||||
* 2014/05/16 增加了Core Translators 成员: will.qian、vizv。
|
||||
* 2014/06/18 由于GOLinux令人惊叹的翻译速度和不错的翻译质量,升级为Core Translators 成员。
|
||||
* 2014/09/09 LCTT 一周年,做一年总结。并将曾任 CORE 的成员分组为 Senior,以表彰他们的贡献。
|
||||
* 2014/09/09 LCTT 一周年,做一年[总结](http://linux.cn/article-3784-1.html)。并将曾任 CORE 的成员分组为 Senior,以表彰他们的贡献。
|
@ -9,7 +9,7 @@ LCTT 2014 : LCTT 成立一年总结
|
||||
|
||||
于是,2013 年 9 月 10日,草草而就的 LCTT 就成立了,很快就创建了一个 QQ 群作为交流,并确定了名称为“Linux.CN Translate Team”,简称 LCTT。考虑到需要多人协作,几乎没有多想,就决定了采用 GITHUB 作为翻译平台——虽然现在看起来,GITHUB 作为主要工作平台,有利也有弊,但是,总体来说还是不错的。LCTT 就这样启动了。
|
||||
|
||||
### 发展 ###
|
||||
### 发展 ###
|
||||
|
||||
次日,我们就组织起来了翻译,并初步拟定了翻译流程、分工之类的内容。
|
||||
|
||||
@ -76,5 +76,8 @@ _写下这个标题时,我也颇感觉惭愧的,这也算是我正视这个
|
||||
|
||||
期待 LCTT 的下一个年度的发展吧!
|
||||
|
||||
----
|
||||
|
||||
LCTT wxy
|
||||
|
||||
2014 年 9 月 10 日
|
@ -1,3 +1,5 @@
|
||||
CNprober translating..
|
||||
|
||||
Staying free – should GCC allow non-free plug ins?
|
||||
================================================================================
|
||||
> Arguments in favour of the use of non-free plug-ins in GCC have again been raised on GCC mailing-lists, but are trumped by the arguments for GCC as a vehicle for free software development
|
||||
|
@ -1,3 +1,5 @@
|
||||
CNprober translating...
|
||||
|
||||
Linux Administration: A Smart Career Choice
|
||||
================================================================================
|
||||
![](http://www.opensourceforu.com/wp-content/uploads/2014/04/linux.jpeg)
|
||||
|
@ -1,3 +1,4 @@
|
||||
(translating by runningwater)
|
||||
Why Do Some Old Programming Languages Never Die?
|
||||
================================================================================
|
||||
> We like what we already know.
|
||||
@ -73,7 +74,7 @@ Lead image by [Blake Patterson][4]
|
||||
via: http://readwrite.com/2014/09/02/programming-language-coding-lifetime
|
||||
|
||||
作者:[Lauren Orsini][a]
|
||||
译者:[译者ID](https://github.com/译者ID)
|
||||
译者:[runningwater](https://github.com/runningwater)
|
||||
校对:[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创翻译,[Linux中国](http://linux.cn/) 荣誉推出
|
||||
|
@ -1,3 +1,5 @@
|
||||
[su-kaiyao]翻译中
|
||||
|
||||
With Apple Watch Unveiled, Could an Ubuntu Smartwatch Be Next?
|
||||
================================================================================
|
||||
**Apple today confirmed its long-rumoured foray into the wearable computing market with the launch of ‘Apple Watch’.**
|
||||
@ -70,4 +72,4 @@ via: http://www.omgubuntu.co.uk/2014/09/ubuntu-smartwatch-apple-iwatch
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创翻译,[Linux中国](http://linux.cn/) 荣誉推出
|
||||
|
||||
[a]:https://plus.google.com/117485690627814051450/?rel=author
|
||||
[1]:http://www.omgubuntu.co.uk/2014/03/ubuntu-tablets-coming-year
|
||||
[1]:http://www.omgubuntu.co.uk/2014/03/ubuntu-tablets-coming-year
|
||||
|
@ -1,3 +1,5 @@
|
||||
alim0x translating
|
||||
|
||||
The history of Android
|
||||
================================================================================
|
||||
![The T-Mobile G1](http://cdn.arstechnica.net/wp-content/uploads/2014/04/t-mobile_g1.jpg)
|
||||
@ -70,4 +72,4 @@ via: http://arstechnica.com/gadgets/2014/06/building-android-a-40000-word-histor
|
||||
[6]:http://android-developers.blogspot.com/2008/08/android-market-user-driven-content.html
|
||||
[7]:http://arstechnica.com/gadgets/2012/02/path-addresses-privacy-controversy-but-social-apps-remain-a-risk-to-users/
|
||||
[a]:http://arstechnica.com/author/ronamadeo
|
||||
[t]:https://twitter.com/RonAmadeo
|
||||
[t]:https://twitter.com/RonAmadeo
|
||||
|
@ -1,79 +0,0 @@
|
||||
(translating by runningwater)
|
||||
How to manage a WiFi connection from the command line
|
||||
================================================================================
|
||||
Whenever you install a new Linux distribution on a computer, it is in general recommended that you connect to the internet via a wired connection. There are two main reasons for this: one, your wireless adapter may not have the right driver loaded; second, if you are installing from the command line, managing WiFi is scary. I always tried to avoid dealing with WiFi over the command line. But in the Linux world, there is no place for fear. If you do not know how to do something, that is the only reason you need to go ahead and learn it. So I forced myself to learn how to manage a WiFi connection from the command line on Linux.
|
||||
|
||||
There are of course multiple ways to connect to a WiFi from the command line. But for the sake of this post, and as an advice, I will try to use the most basic way: the one that uses programs and utilities included in the "default packages" of any distribution. Or at least I will try. An obvious reason for this choice is that the process can potentially be reproduced on any Linux computer. The downside is its relative complexity.
|
||||
|
||||
First, I will assume that you have the correct drivers loaded for your wireless LAN card. There is no way to start anything without that. And if you don't, you should take a look at the Wiki and documentation for your distribution.
|
||||
|
||||
Then you can check which interface supports wireless connections with the command
|
||||
|
||||
$ iwconfig
|
||||
|
||||
![](https://farm6.staticflickr.com/5578/14725621337_b174a3029c_z.jpg)
|
||||
|
||||
In general, the wireless interface is called wlan0. There are of course exceptions, but for the rest of this tutorial, I will call it that way.
|
||||
|
||||
Just in case, you should make sure that the interface is up with:
|
||||
|
||||
$ sudo ip link set wlan0 up
|
||||
|
||||
Once you know that your interface is operational, you should scan for nearby wireless networks with:
|
||||
|
||||
$ sudo iw dev wlan0 scan | less
|
||||
|
||||
![](https://farm4.staticflickr.com/3847/14909117931_e2f3d0feb0_z.jpg)
|
||||
|
||||
From the output, you can extract the name of the network (its SSID), its signal power, and which type of security it uses (e.g., WEP, WPA/WPA2). From there, the road splits into two: the nice and easy, and the slightly more complicated case.
|
||||
|
||||
If the network you want to connect to is not encrypted, you can connect straight to it with:
|
||||
|
||||
$ sudo iw dev wlan0 connect [network SSID]
|
||||
|
||||
If the network uses WEP encryption, it is also quite easy:
|
||||
|
||||
$ sudo iw dev wlan0 connect [network SSID] key 0:[WEP key]
|
||||
|
||||
But everything gets worse if the network uses WPA or WPA2 protocols. In this case, you have to use the utility called wpa_supplicant, which is not always included by default. You then have to modify the file at /etc/wpa_supplicant/wpa_supplicant.conf to add the lines:
|
||||
|
||||
network={
|
||||
ssid="[network ssid]"
|
||||
psk="[the passphrase]"
|
||||
priority=1
|
||||
}
|
||||
|
||||
I recommend that you append it at the end of the file, and make sure that the other configurations are commented out. Be careful that both the ssid and the passphrase are case sensitive. You can also technically put the name of the access point as the ssid, and wpa_supplicant will replace it with the proper ssid.
|
||||
|
||||
Once the configuration file is completed, launch this command in the background:
|
||||
|
||||
$ sudo wpa_supplicant -i wlan0 -c /etc/wpa_supplicant/wpa_supplicant.conf
|
||||
|
||||
Finally, whether you connected to an open or a secure network, you have to get an IP address. Simply use:
|
||||
|
||||
$ sudo dhcpcd wlan0
|
||||
|
||||
If everything goes well, you should get a brand new local IP via DHCP, and the process will fork in the background. If you want to be sure that you are connected, you can always check again with:
|
||||
|
||||
$ iwconfig
|
||||
|
||||
![](https://farm4.staticflickr.com/3904/14725573368_7110407db8_z.jpg)
|
||||
|
||||
To conclude, I think that getting over the first step is completely worth it. You never know when your GUI will be down, or when you cannot access a wired connection, so getting ready now seems very important. Also, as mentioned before, there are a lot of ways (e.g., NetworkManager, [wicd][1], [netcfg][2], [wifi][3]) to manage a wireless connection. If I try to stick to the most basic way, I know that in some cases, the utilities that I used may not even be available to you, and that you would have to download them prior to that. On the other side of the balance, there are some more advanced programs, which are definitely not included in the "default packages," which will greatly simplify the whole process. But as a general advice, it is good to stick to the basics at first.
|
||||
|
||||
What other ways would you recommend to connect via WiFi from the command line? Please let us know in the comments.
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: http://xmodulo.com/2014/08/manage-wifi-connection-command-line.html
|
||||
|
||||
作者:[Adrien Brochard][a]
|
||||
译者:[runningwater](https://github.com/runningwater)
|
||||
校对:[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创翻译,[Linux中国](http://linux.cn/) 荣誉推出
|
||||
|
||||
[a]:http://xmodulo.com/author/adrien
|
||||
[1]:http://wicd.sourceforge.net/
|
||||
[2]:https://www.archlinux.org/netcfg/
|
||||
[3]:https://github.com/rockymeza/wifi
|
@ -1,3 +1,4 @@
|
||||
(translating by szrlee)
|
||||
Awesome ! systemd Commands to Manage Linux System
|
||||
================================================================================
|
||||
Systemd is the new system and service manager for Linux. It is a replacement for init system and can manage system startup and services. It starts up and supervises the entire system. In article we are using [centos 7.0 installed with systemd 216 version][1] and the latest version is [available for download from freedesktop.org][2].
|
||||
@ -272,11 +273,11 @@ The systemd brings out the whole new approach to interacting with your operating
|
||||
via: http://linoxide.com/linux-command/linux-systemd-commands/
|
||||
|
||||
作者:[Raghu][a]
|
||||
译者:[译者ID](https://github.com/译者ID)
|
||||
译者:[szrlee](https://github.com/szrlee)
|
||||
校对:[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创翻译,[Linux中国](http://linux.cn/) 荣誉推出
|
||||
|
||||
[a]:http://linoxide.com/author/raghu/
|
||||
[1]:http://linoxide.com/linux-how-to/install-systemd-centos-redhat/
|
||||
[2]:http://www.freedesktop.org/software/systemd/
|
||||
[2]:http://www.freedesktop.org/software/systemd/
|
||||
|
@ -1,3 +1,4 @@
|
||||
translating by szrlee
|
||||
Colourful ! systemd vs sysVinit Linux Cheatsheet
|
||||
================================================================================
|
||||
**systemd** is the new init system, starting with Fedora and now adopted in many distributions like RedHat, Suse and Centos. Historically, most of us have been using traditional SysV init scripts normally residing in /etc/rc.d/init.d/. These scripts invoke a daemon binary which will then fork a background process. Even though shell scripts are very flexible, tasks like supervising processes and parallelized execution ordering are difficult to implement. With the introduction of systemd’s new-style daemons it is easier to supervise and control them at runtime and it simplifies their implementation.
|
||||
@ -13,11 +14,11 @@ There are a lot of new [systemd commands available on rhel / centos 7.0][1]注
|
||||
via: http://linoxide.com/linux-command/systemd-vs-sysvinit-cheatsheet/
|
||||
|
||||
作者:[Bobbin Zachariah][a]
|
||||
译者:[译者ID](https://github.com/译者ID)
|
||||
译者:[szrlee](https://github.com/szrlee)
|
||||
校对:[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创翻译,[Linux中国](http://linux.cn/) 荣誉推出
|
||||
|
||||
[a]:http://linoxide.com/author/bobbin/
|
||||
[1]:http://linoxide.com/linux-command/linux-systemd-commands/
|
||||
[2]:http://images.linoxide.com/systemd-vs-sysVinit-cheatsheet.pdf
|
||||
[2]:http://images.linoxide.com/systemd-vs-sysVinit-cheatsheet.pdf
|
||||
|
@ -0,0 +1,78 @@
|
||||
在命令行中管理 Wifi 连接
|
||||
================================================================================
|
||||
无论何时要安装一款新的 Linux 发行系统,一般的建议都是让您通过有线连接来接到互联网的。这主要的原因有两条:第一,您的无线网卡也许安装的驱动不正确而不能用;第二,如果您是从命令行中来安装系统的,管理 WiFi 就非常可怕。我总是试图避免在命令行中处理 WiFi 。但 Linux 的世界,应具有无所畏惧的精神。如果您不知道怎样操作,您需要继续往下来学习之,这就是写这篇文章的唯一原因。所以我强迫自己学习如何在命令行中管理 WiFi 连接。
|
||||
|
||||
通过命令行来设置连接到 WiFi 当然有很多种方法,但在这篇文章里,也是一个建议,我将会作用最基本的方法:那就是使用在任何发布版本中都有的包含在“默认包”里的程序和工具。或者我偏向于使用这一种方法。使用此方法显而易见的好处是这个操作过程能在任意有 Linux 系统的机器上复用。不好的一点是它相对来说比较复杂。
|
||||
|
||||
首先,我假设您们都已经正确安装了无线网卡的驱动程序。没有这前提,后续的一切都如镜花水月。如果您你机器确实没有正确安装上,您应该看看关于您的发布版本的维基和文档。
|
||||
|
||||
然后您就可以用如下命令来检查是哪一个接口来支持无线连接的
|
||||
|
||||
$ iwconfig
|
||||
|
||||
![](https://farm6.staticflickr.com/5578/14725621337_b174a3029c_z.jpg)
|
||||
|
||||
一般来说,无线接口都叫做 wlan0。当然也有例外的,但在这篇教程中我们将会一直用通用叫法。
|
||||
|
||||
以防万一,你得确认下以使此接口服务是启动着的:
|
||||
|
||||
$ sudo ip link set wlan0 up
|
||||
|
||||
一但确认了无线接口是工作着的,你就可以用如下命令来扫描附近的无线网络了:
|
||||
|
||||
$ sudo iw dev wlan0 scan | less
|
||||
|
||||
![](https://farm4.staticflickr.com/3847/14909117931_e2f3d0feb0_z.jpg)
|
||||
|
||||
根据扫描出的结果,可以得到网络的名字(它的 SSID),它的信息强度,以及它使用的是哪个安全加密的(如:WEP、WPA/WPA2)。从此时起,将会分成两条路线:情况很好的和容易的以及情况稍微复杂的。
|
||||
|
||||
如果您想连接的网络是没有加密的,您可以用下面的命令直接连接:
|
||||
|
||||
$ sudo iw dev wlan0 connect [network SSID]
|
||||
|
||||
如果网络是用 WEP 加密的,也非常容易:
|
||||
|
||||
$ sudo iw dev wlan0 connect [network SSID] key 0:[WEP key]
|
||||
|
||||
但网络使用的是 WPA 或 WPA2 协议的话,事情就不好办了。这种情况,您就得使用叫做 wpa_supplicant 的工具,它默认是没有启用的。需要修改 /etc/wpa_supplicant/wpa_supplicant.conf 文件,增加如下行:
|
||||
|
||||
network={
|
||||
ssid="[network ssid]"
|
||||
psk="[the passphrase]"
|
||||
priority=1
|
||||
}
|
||||
|
||||
我建议你在文件的末尾添加它,并确保其他配置都注释掉。要注意 SSID 和密码字串都是大小写敏感的。在技术上您也可以把接入点的名称当做是 SSID,使用 wpa_supplicant 工具的话会有合适的 SSID 来替代这个名字。
|
||||
|
||||
一旦配置文件修改完成后,在后台启动此命令:
|
||||
|
||||
$ sudo wpa_supplicant -i wlan0 -c /etc/wpa_supplicant/wpa_supplicant.conf
|
||||
|
||||
最后,无论是连到开放的网络还是加密的安全网络,您都得获取 IP 地址。简单地使用如下命令:
|
||||
|
||||
$ sudo dhcpcd wlan0
|
||||
|
||||
如果一切顺利的话,您应该已经通过 DHCP 获取到了一个全新的本地 IP,这个过程是在后台自动完成的。如果想确认下是否真正连接上的话,您可以再一次输入如下命令检查:
|
||||
|
||||
$ iwconfig
|
||||
|
||||
![](https://farm4.staticflickr.com/3904/14725573368_7110407db8_z.jpg)
|
||||
|
||||
最后,我认为多次重复第一步的检查操作是很有必要的。您永远不会知道什么时候您的图形用户界面挂了,或者是什么时候不能访问无线连接了,所以现在就准备着用命令来检测吧。还有,前面提到过的,有很多种方式(如 NetworkManager、[wicd][1]、[netcfg][2]、[wifi][3] 等等)来管理无线连接。我坚持使用最基本的方式,但在某些情况下,我使用的工具可能您还没有,所以您在之前就得先下载它们。另一方面,有很多高级的应用程序,他们确实是不包含在“默认包”里面的,使用它们会大大简化操作过程。但一般建议是开始的话最好从基本的来。
|
||||
|
||||
关于从命令行来管理连接 WiFi 您还有其他方式方法吗?请在评论中让我们知道。
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: http://xmodulo.com/2014/08/manage-wifi-connection-command-line.html
|
||||
|
||||
作者:[Adrien Brochard][a]
|
||||
译者:[runningwater](https://github.com/runningwater)
|
||||
校对:[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创翻译,[Linux中国](http://linux.cn/) 荣誉推出
|
||||
|
||||
[a]:http://xmodulo.com/author/adrien
|
||||
[1]:http://wicd.sourceforge.net/
|
||||
[2]:https://www.archlinux.org/netcfg/
|
||||
[3]:https://github.com/rockymeza/wifi
|
Loading…
Reference in New Issue
Block a user