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

Merge branch 'master' of github.com:LCTT/TranslateProject

Browse Source
This commit is contained in:
Vic___ 2013-11-09 00:07:40 +08:00
commit f6d198a1ba
20 changed files with 1352 additions and 521 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

0
translated/10 Things To Do After Installing Ubuntu 13.10.md → published/10 Things To Do After Installing Ubuntu 13.10.md
View File

16
translated/CISCO Announce New Open Source H.264 Codec.md → published/CISCO Announce New Open Source H.264 Codec.md
View File

@ -1,14 +1,14 @@
思科宣布新的开源H.264编解码器
思科发布新的开源H.264编解码器
================================================================================
![](http://www.omgubuntu.co.uk/wp-content/uploads/2012/04/youtube.jpg)
*YouTube是众多使用H.264的网站之一*
**美国网络设备公司思科[宣布计划提供一个开源的H.264编解码器](1) - 也就是在WebRTC中播放电影就再也没有问题了。**
**美国网络设备公司思科[宣布它计划提供一个开源的H.264编解码器](1) - 也就是说以后在WebRTC中播放电影就再不会有问题了。**
尽管H.264广泛应用于HTML5视频流中，但是不是所有的浏览器和操作系统都可以利用H.264。
这是因为使用可以编码与解码H.264视频的编解码器需要向持有相关专利的MPEG LA组织支付高昂的使用费（也许不是巧合，[一些专利为思科所拥有](2)）。
此外，用于H.264的编解码器禁止随同像网页浏览器这样的开源软件一同分发。
@ -19,17 +19,17 @@
这家公司谈到，通过开源他们的H.264编解码器和为他们预编译的二进制文件提供免费下载，这将给像WebRTC这样的允许浏览器间实时通信的HTML5 API提供强大动力。
>‘思科并不是第一个去创建H.264开源实现的。。。’
>‘思科并不是第一个去创建H.264开源实现的...’
实际上，Mozilla[已经宣布](3)它计划在Firefox中支持思科的H.264二进制模块。
思科并不是第一个去创建H.264的开源实现的。GNU的libavcodec库已经包括了解码器和编码器，后者基于[x264](4)。但是思科提供的开源实现实有法律立足点的 - 而这正是其它的开源实现所缺乏的。这使得思科的解码器对象Mozilla这样的公司来说就非常有用咯，这可以使得它们无需担心法律问题。
思科并不是第一个去创建H.264的开源实现的。GNU的libavcodec库已经包括了解码器和编码器，后者基于[x264](4)。但是思科提供的开源实现是有法律支持的 - 而这正是其它的开源实现所缺乏的。这使得思科的解码器对象Mozilla这样的公司来说就非常有用，这可以使得它们无需担心法律问题。
然而，思科公司为何提供这样一个新编解码器的真相还不很清楚。
然而，思科公司为何提供这样一个新编解码器的原因还不很清楚。
思科将开源他们的H.264栈。这将随着预编译二进制模块一同可从他们的网站上免费下载。像Firefox这样的应用就可以在需要解码H.264视频的时候载入它（甚至可在需要的时候自动下载它）。
而于此同时，思科将要向MPEG LA组织支付专利费用，而这些费用也无法向使用它们模块的用户收取。对于直接由源代码进行编译的行为的限制也不清晰。尽管如此，随着代码下周在Github网站上进行托管，我们就可以获得更多信息。
于此同时，思科将要向MPEG LA组织支付专利费用，而这些费用却无法向使用它们模块的用户收取。对于直接由源代码进行编译的行为的限制也不清晰。尽管如此，随着代码在Github网站上进行托管，我们就可以获得更多信息。
###总结###
@ -41,7 +41,7 @@
via: http://www.omgubuntu.co.uk/2013/10/cisco-announce-open-source-h-264-codec
译者：[Linux-pdz](https://github.com/Linux-pdz) 校对：[校对者ID](https://github.com/校对者ID)
译者：[Linux-pdz](https://github.com/Linux-pdz) 校对：[wxy](https://github.com/wxy)
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创翻译，[Linux中国](http://linux.cn/) 荣誉推出

19
translated/Create And Manage Encrypted Folders in Linux With encfs.md → published/Create And Manage Encrypted Folders in Linux With encfs.md
View File

@ -1,6 +1,7 @@
Linux系统上用encfs创建和管理加密文件夹
================================================================================
如果你想使你计算机上的某些信息免于被窥视的话，这儿正是所到之地。保护信息的一种方法就是加密你的home目录，但是一旦你登陆系统后，你的home目录下的信息将暴露于外。过去，我已经写过关于怎样[在你的系统上使用Cryptkeeper来创建加密的文件夹][1]。Cryptkeeper是一个图形前端，后端是**encfs**。encfs允许你创建一个加密的文件夹，然后把它当作使用[FUSE][2]来实现的用户文件系统来挂载。在这篇教程里，我会教你怎么在Linux系统上的命令行下面使用encfs工具来创建和管理一个加密的文件夹。
如果你想使你计算机上的某些信息免于被窥视的话，可以看看这篇文字。保护信息的一种方法就是加密你的home目录，但是一旦你登录系统后，你的home目录下的信息将暴露于外。过去，我已经写过关于怎样[在你的系统上使用Cryptkeeper来创建加密的文件夹][1]。Cryptkeeper是一个图形前端，后端是 **encfs**。encfs允许你创建一个加密的文件夹，然后通过[FUSE][2]来挂载作为用户文件系统。在这篇教程里，我会教你怎么在Linux系统上的命令行下面使用encfs工具来创建和管理一个加密的文件夹。
![](http://tuxtweaks.com/wp-content/uploads/2013/10/encfs.png)
@ -12,11 +13,11 @@ Linux系统上用encfs创建和管理加密文件夹
### 用encfs创建加密文件夹 ###
一旦在系统中安装好了encfs后，你就能在home目录下创建一个加密的文件夹。在这个示例当中，我将会创建一个叫做tuxtweaks的加密文件夹，这通过终端窗口就可以实现。当创建一个新的文件夹的时候，你需要指定全路径名，当然也可以使用如下所示的标准快捷方式。
一旦在系统中安装好了encfs后，你就能在你的home目录下创建一个加密的文件夹。在这个示例当中，我将会创建一个叫做tuxtweaks的加密文件夹，这通过终端窗口就可以完成。当创建一个新的文件夹的时候，你需要指定全路径名，当然也可以使用如下所示的标准快捷方式。
encfs ~/.tuxtweaks ~/tuxtweaks
这会创建两个文件夹。第一个.**tuxtweaks**,它包含被加密的信息；第二个tuxtweaks,当你想要访问信息的时候，解密的版本信息将会挂载到下面。如果这些文件夹都不存在，系统将会提示询问是否创建它们。在提示下面键入‘**y**’以允许创建文件夹，然后你应该能看到如下所示的一些信息：
这会创建两个文件夹。第一个.**tuxtweaks**,它包含被加密的信息；第二个tuxtweaks，当你想要访问信息的时候，解密的版本信息将会挂载到下面。如果这些文件夹都不存在，系统将会提示询问是否创建它们。在提示下面键入‘**y**’以允许创建文件夹，然后你应该能看到如下所示的一些信息：
Creating new encrypted volume.
Please choose from one of the following options:
@ -26,7 +27,7 @@ Linux系统上用encfs创建和管理加密文件夹
如果你想要最高级别的加密文件夹的话，在提示符下输入**p**选项。否则只需敲击**[Enter]键**，就会以标准选项来创建新的加密文件夹。
之后，你将会看到新加密卷的参数列表及一些警告信息，随之提示符会让输入一个密码。确保不要忘记使用的密码，回为没有密码找回机制。在输入密码能以第二次输入校验通过后，新的文件夹会被创建出来，并自动挂载进文件系统，就可以开始使用了。
之后，你将会看到新加密卷的参数列表及一些警告信息，随之提示符会让输入一个密码。确保不要忘记使用的密码，因为没有密码找回机制。在输入密码并以第二次输入校验通过后，新的文件夹会被创建成功，并自动挂载进文件系统，可以开始使用了。
### 使用加密文件夹 ###
@ -38,11 +39,11 @@ Linux系统上用encfs创建和管理加密文件夹
### 卸载encfs创建的加密文件夹 ###
一旦你完成文件访问或者数据创建等操作，最好把加密文件夹卸载，以便里面的信息安全的隐藏掉。encfs自身不带有卸载的命令，一旦用它创建了用户文件系统，就可以利用FUSE包来处理卸载任务。下面我们会使用fusermount命令来卸载我们的加密文件夹。
一旦你完成文件访问或者数据创建等操作，最好把加密文件夹卸载，以便里面的信息安全的隐藏掉。encfs自身不带有卸载的命令，一旦用它创建了用户文件系统，就可以利用FUSE来处理卸载任务。下面我们会使用fusermount命令来卸载我们的加密文件夹。
fusermount -u ~/tuxtweaks
切换到home目录下，会看到tuxtweaks目录仍然存在，但进入文件夹，你会发现里面是空的。
切换到home目录下，会看到tuxtweaks目录仍然存在，但进入文件夹，你会发现里面是空的。（译注：因为tuxtweaks目录只是一个挂载点，真实的数据是以加密的方式存储在.tuxtweaks目录下的，）
### 挂载用encfs创建的加密文件夹 ###
@ -50,8 +51,8 @@ Linux系统上用encfs创建和管理加密文件夹
encfs ~/.tuxtweaks ~/tuxtweaks
### 使用 ###
### 用途 ###
我发现使用**encfs**加密文件夹来安全地存储财务信息非常便捷，比如纳税申报表以及用于存储日志列表凭据。这样我只需要记住我加密文件夹的密码，然后就可以进入访问记录有其他登录ID和密码的名单文件。
你会使用encfs来做什么呢？在评论中给我们分享吧。
@ -60,7 +61,7 @@ Linux系统上用encfs创建和管理加密文件夹
via: http://tuxtweaks.com/2013/10/encrypted-folders-linux-encfs/
译者：[runningwater](https://github.com/runningwater) 校对：[校对者ID](https://github.com/校对者ID)
译者：[runningwater](https://github.com/runningwater) 校对：[wxy](https://github.com/wxy)
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创翻译，[Linux中国](http://linux.cn/) 荣誉推出

6
translated/Game-editor Leadwerks 3.1 demoed as running on Ubuntu with native look & feel.md → published/Game-editor Leadwerks 3.1 demoed as running on Ubuntu with native look & feel.md
View File

@ -1,11 +1,11 @@
具有原生外观和感觉的游戏编辑器Leadwerks 3.1演示版亦可以在Ubuntu上运行
===
可在Ubuntu上运行的游戏编辑器Leadwerks 3.1
====================================
[Leadwerks][1]是一个多用途游戏开发应用，现在正在往Linux上移植以便于在Linux（Ubuntu）上开发原生游戏。
数月前，Leadwerks在kickstarter平台上发起了一个众筹项目，以便于集资给这个游戏创建工具增加Linux平台支持，项目目标包括成功达到预定的集资目标和放出leadwerks的beta版。
在它的官网上，Leadwerks的开发者[贴出了][2]一张有**leadwerks 3.1**运行在Ubuntu上的图片，图片显示它有着原生的外观和感觉，而且和桌面进行了恰当的集成，这些成就明显的推动了仍在开发中的leadwerks对于Ubuntu的可用性。这是Leadwerks真正正正运行在Ubuntu上的第一张截图！尽管仍然还有许多工作要做，但是看到它确实已经可以运行在Ubuntu上了，无论怎样，这真的是一个**大的里程碑**。我们使用GTK，所以Leadwerks的Linux版的外观和使用的感受和Linux原生应用一样。
在它的官网上，Leadwerks的开发者[贴出了][2]一张有 **leadwerks 3.1** 运行在Ubuntu上的图片。图片显示，它有着原生的外观和感觉，而且和桌面进行了恰当的集成，这些成就明显的推动了仍在开发中的leadwerks在Ubuntu上的可用性。这是Leadwerks真正运行在Ubuntu上的第一张截图！尽管仍然还有许多工作要做，但是看到它确实已经可以运行在Ubuntu上了，无论怎样，这真的是一个**大的里程碑**。我们使用GTK，所以Leadwerks的Linux版的外观和使用的感受和Linux原生应用一样。
![](http://iloveubuntu.net/pictures_me/leadwerks%20running%20on%20ubuntu.jpg)

296
published/Raspberry Pi--the Perfect Home Server.md Normal file
View File

@ -0,0 +1,296 @@
树莓派（Raspberry Pi）：完美的家用服务器
================================
自从树莓派发布后，所有在互联网上的网站为此激动人心的设备提供了很多有趣和具有挑战性的使用方法。虽然这些想法都很棒，但树莓派( **RPi** )最明显却又是最不吸引人的用处是：创建你的完美家用服务器。
如果你有几个不同的电脑需要同步和自动化备份，RPi可以做到。如果你想通过家中的任意屏幕来访问你的音乐和视频，RPi也能实现。也许你有一个或两个打印机，你想要简单与大家共享，树莓派在硬件和时间上用最小投资就能满足你的这些需求。
###树莓派的好处
低成本：35美元（约合242元RMB），B型的RPi接近一台完整的电脑，512M内存，100Mb以太网，SD卡插槽，2个USB接口，音频输出和HDMI或RCA视频输出。我知道HDMI电缆就比树莓派贵。
能源效率：硬件成本只是服务器费用的一部分，因为你需要考虑能源成本去不断运行设备。家用服务器所需要的服务不会占用太多CPU，大部分时间它都处于空闲状态，等待发挥功效。RPi's超低功率组件非常适合这个工作负载，这有助于降低你的电费消耗。我的一个B型的RPi加上外部硬盘消耗总共只有8瓦，然而用老式速龙代替的机器在闲置时消耗54瓦。假设10美分每千瓦一小时，这使得一个RPi每年的电费在7美元。一个基于速龙的机器是47美元。在不到一年的时间里，RPI基本上能够收回成本。
低噪音：因为RPi没有风扇和移动部件，在你最终配置中的唯一能生成噪音或明显热量的组件就是硬盘。如果你担心噪音，像[Silent PC Review][1]发烧友网站经常在他们的评论中涉及到噪声基准。我的体会是现代驱动器足够安静，要比其他的设备安静的多（如媒体中心，游戏机或其他电脑）。如果你家里没有为布线提供更多的灵活性选择，RPi的小尺寸、少量发热和低噪音也许让你走过它旁边都很难发现。
![](http://www.linuxjournal.com/files/linuxjournal.com/ufiles/imagecache/large-550px-centered/u1002061/11454f1.jpg)
图1,一个简洁高效的家用服务器
新机会：一个不怎么实际的好处是-简单快乐的尝试新事物！对我来说，这是我第一次真正工作在基于Debian的发行版，很可能也是许多Linux爱好者们第一次有机会尝试一个基于ARM的体系结构。
###布置硬件
对于一个家庭服务器来说，你将需要一个中等容量的SD闪存卡作为本地存储。它可以使用一个USB引导，但那会占用两个宝贵的USB插槽之一。闪存卡不需要很大容量，但是速度越快越好。我选择了一个名牌SD卡，8GB容量和CLASS 10的速度等级。对于备份和存储多媒体文件，一个有USB连接插槽的硬盘驱动器是必须的。我选择一个1.5TB的硬盘和一个Calvary EN-CAHDD-D 2-bay USB 2.0硬盘连接基座。这个连接基座有个功能，在RAID-0模式中连接两个硬盘，总有一天会有用的。最后，RPi不带电源线，但可以用大多数智能手机充电器所用的5v微型USB。看看RPi是否挑剔电源，我为电源已换了三个不同的微型USB手机充电器。我在这周内尝试了每一个，在任何一个上都没有问题。
###安装操作系统
安装RPi操作系统包括了许多方面的大量细节，但这里有一些家用特定服务器的安装提示，大致按需要的顺序讲述。
1）直接通过[http://www.raspberrypi.org/downloads][2]获取Raspbian "Wheezy"安装镜像，并复制到SD卡，用网站上已列出的步骤。
2）第一次引导RPi时，连接一个键盘、鼠标和显示器。在引导RPi之前别忘打开显示器，可以检测到正确的HDMI或混合输出端口。
3）RPi有一个很好的"raspi-config"屏幕，在第一次启动时你会看到。对于家庭服务器来说，以下选择将会有用：
- expand_rootfs：调整默认2GB OS镜像的大小，来填满闪存卡剩余的内存。
- change_pass：修改默认密码"raspberry"，但是，越安全的密码越好。
- 设置你的地点和时区。
- memory_split：给GPIU服务分配最少的内存（16M）尽可能为其他服务留下更多内存。
- SSH：别忘开启SSH服务。
- boot_behaviour：关闭“启动至桌面（boot to desktop）”（再次为你的其他服务节省内存）。
完成后，你将在出现 `pi@raspberrypi` 提示符下。安装脚本可以在任何时间通过 `sudo raspi-config` 重新运行。
还有一些其他配置，然后操作系统就可以用了。
1）一个静态IP让一切变得更容易，切换eth0的网络设置：
>> sudo nano -w /etc/network/interfaces
更改eth0的那行 `iface eth0 inet dhcp` ，如下所示（根据你的家庭网络设置修改）：
======/etc/network/interfaces======
...
iface eth0 inet static
address 192.168.1.10
netmask 255.255.255.0
gateway 192.168.1.1
...
======/etc/network/interfaces======
2）创建本地用户并加入到users组和sudo组：
>> sudo adduser YOURUSERIDHERE
>> sudo usermod -a -G users YOURUSERIDHERE
>> sudo usermod -a -G sudo YOURUSERIDHERE
3）更新系统确保所有的库是最新最好的：
>> sudo apt-get update; sudo apt-get upgrade
4）好了，准备重新启动吧！先关闭PI：
>> sudo /sbin/shutdown -h now
一旦关闭（注意RPi电路板上的绿色LED状态指示灯，可以知道什么时候完成关闭了），拔下显示器，键盘，鼠标和电源线。插入USB端口上的硬盘，然后插回电源重启RPi。
5）一旦RPi开启（这些绿色LED指示灯用来描述状态），你可以从远程网络上从任何其他机器ssh到RPi并完成所有的配置（更改以下命令里的IP为你的静态IP）：
>> ssh YOURUSERIDHERE@192.168.1.10
祝贺你，有了一个可以工作的树莓派！
###外设
第一件事是要连接外设。用dmesg来寻找你的存储设备，会发现——几乎可以肯定是/dev/sda。我喜欢使用自动挂载去挂载移动存储设备，这样更灵活，因为在启动时这些设备也许没有或者没准备好：
>> sudo apt-get install autofs
>> sudo nano -w /etc/auto.master
======/etc/auto.master======
...
/misc /etc/auto.misc
...
======/etc/auto.master======
>> sudo nano -w /etc/auto.misc
注意，我的外部存储设备是ext4格式，如果需要话可以在下面更改：
======/etc/auto.misc======
...
storage -fstype=ext4:/dev/sda1
...
======/etc/auto.misc======
>> sudo /etc/init.d/autofs restart
>> ls -lat /misc/storage
可选的，创建一个符号链接的短路径：
>> ln -s /misc/storage /storage
###备份仓库
在任何家庭服务器功能列表里面最重要的是提供坚如磐石的备份。对于RPi来说，这很简单而优美，在Linux中有丰富的网络共享选项：Samba/CIFS用于Windows机器，NFS用于基于UNIX的设备，并且甚至SFTP可以用于更多新的备份客户端，如deja-dup。由于RPi只有100MB以太网接口和USB上的存储设备，它没有非常快的传送速度。不过在另一方面，好的备份客户端是在后台自动运行的，所以你不会注意略微缓慢的传输速度。
我的家庭网络包括一台Windows 7电脑。对于它，我通过Samba在RPi's外部USB存储设备上导出一个备份目录。因为备份程序在Windows7基础版上不支持网络设备作为备份目标，我使用[SyncBack Free][3]去设置使其自动化，每日备份。
配置Samba是容易的。
1）安装samba和common-bin库（具有smbpasswd效用）
>> sudo apt-get install samba samba-common-bin
2）使用 `smbpasswd` 让你的本地ID能访问：
>> sudo smbpasswd -a YOURUSERIDHERE
3）编辑samba配置文件：
>> sudo nano -w /etc/samba/smb.conf
4）更改 `workgroup = WORKGROUP` 行以匹配你的Windows工作组名称。
5）注释掉或删除[homes]和[printers]共享。(打印机共享稍后将通过直接CUPS访问来完成。)
6）为Windows备份路径增加一个条目。这是我的示例，放置在该文件的底部：
======/etc/samba/smb.conf======
...
[win7pc]
comment=Backup for windows PC
path=/storage/win7pc
writeable=Yes
create mask=0777
directory mask=0777
browsable=Yes
public=Yes
valid users=YOURUSERIDHERE
...
======/etc/samba/smb.conf======
7）重启Samba使你的编辑生效：
>> sudo /etc/init.d/samba restart
8）从Windows机器文件资源管理器通过映射一个网络设备测试连通。
对Linux设备来说，设置和使用deja-dup非常简单。它被默认安装在我的Fedora 18和Ubuntu 12.10上。包的名称是“deja-dup”，程序名简单的称为“Backup（备份）”。虽然RPi很容易支持NFS导出，我发现使用deja-dup的SSH选项更容易，更方便，在RPi上它不需要额外服务的支持。指定一个deja-dup加密密码是一个好主意，除非你不在意一旦丢失了存储器，别人就可以拿走全部数据：
>> sudo mkdir /storage/linuxlaptop
>> sudo chown -R YOURUSERIDHERE:YOURUSERIDHERE /storage/linuxlaptop
从linux客户端启动备份程序，选择“SSH”作为备份位置，输入RPi的IP地址和你创建的存储位置。首次备份会很慢，但是以后的运行将只发送增量变化，速度更快。
![](http://www.linuxjournal.com/files/linuxjournal.com/ufiles/imagecache/medium-350px-centered/u1002061/11454f2.png)
图2,Deja-dup客户端设置
###多媒体服务器：DLNA
现在每个人的文件都已安全备份。让我们继续看些有趣的！一个DLNA服务器可以让你集中存储你的电影、音乐和图片。通过这个中心库，家中每一个屏幕的DLNA客户端都可以轻松重放此内容。
至少，这是一个宣称。事实是这样的，DNLA规格并不太确定一些重要的事情，如支持哪些格式或编码。每个客户端通常对于支持什么格式和服务器功能都有略微不同的想法。很多高功率的服务器也许能转码本地内容到移动设备支持的格式，但是在RPi上是不可能的，在即时转码上经常扰乱其他功能，如暂停，快进和倒带。一般情况下，高功率设备如PS3、Xbox和WD TV设备支持大多数格式，而无需任何转码。低端设备如智能TVs或Blu-ray播放器只支持更有限的编码列表。
对于RPi来说，最好的办法是支持你的主要的DLNA设备的标准编码，然后测试你的其他DLNA客户端。如果没有完美播放，在下一节的提示也许有帮助。在我的情况下，我的PlayStation 3充当DLNA客户端，PS3能够流畅播放经Handbrake制作后的.m4v文件。
对于RPi的DLNA服务器来说，Minidlna是个很好的选择。它已经在Raspbian发行版中，易于设置和使用最小服务资源运行：
>> sudo apt-get install minidlna
>> sudo nano -w /etc/minidlna.conf
这是我/etc/minidlna.conf文件的相关部分：
...
# I found keeping video + audio in different paths helpful
media_dir=V,/storage/dlna/video
media_dir=A,/storage/dlna/music
...
presentation_url=http://192.168.1.10:8200/
...
friendly_name=MyRPi
...
# Since I add new media infrequently, turning off
# inotify keeps minidlna for polling for
# content changes. It's simple enough to run
# sudo /etc/init.d/minidlna force-reload
# when new content is added.
inotify=no
一旦完成编辑，重启minidlna以加载新配置：
>> sudo /etc/init.d/minidlna force-reload
Minidlna能够为你的设备支持的电影提供电影海报缩略图（像PS3）。这让我能够更方便地在几十个电影文件中滚屏查找我想要的那个电影。我发现每个电影一个目录是最兼容的文件布局，只包含影片文件和缩略图，图像命名为“Cover.jpg”。使用像"MovieName.m4v"和"MovieName.jpg"的格式在PS3上工作的很好，但它不太适合VLC（除非你能让VLC uPNP插件首先查找服务器的话）。
通过PS3，你可以通过转到在XMB栏上的"Video"测试连通性。当视频列表向下翻页时，你以前设置的"friendly_name"应该是可见的，测试确保Minidlna是通过浏览器转到http://192.168.1.10:8200/。
###非DLNA设备的多媒体
当你让DNLA与你的一些设备一起工作时，你可能会发现有些设备并不适合它，所以多媒体计划B是个好主意。Nginx网站服务器有一个MP4插件尝试在旧式的HTTP连接上改善流媒体传输，但是浏览器回放的性能差别很大，在一部电影里快进也一直不工作。看起来多媒体共享或非 DLNA 设备的最低共同特性是使用传统Samba共享的访客只读访问。
这是/etc/samba/smb.conf的部分示例：
[dlna]
path=/storage/dlna
read only=yes
browsable=yes
public=yes
定义了共享设置后重启Samba（ `sudo /etc/init.d/samba restart` ），你可以开始测试你的客户端。
我用一个混合的编码m4v视频文件测试了以下客户端：
- Android 4.0.4手机："ES File Explorer"与"ES Media Player"（播放器附带安装）。
- Android 4.1.2平板电脑："ES File Explorer"与"ES Media Player"（播放器附带安装）。
- Linux设备：自动挂载：//192.168.1.10/dlna，然后使用VLC或MPlayer。
- Windows：挂载//192.168.1.10:/dlna，然后使用VLC。
所有设备都能几乎立即开始播放和快进没有延迟的情况。
###打印服务器
RPi运行CUPS相当不错，所以它容易共享一个较旧的没有本地网络接口的打印机。
安装你的打印机所需的CUPS和任何软件包。我需要hplip-cups，因为我有一个HP喷墨打印机：
>> sudo apt-get install cups hplip-cups
更新“Listen”行和增加 `Allow @LOCAL` 到位置指令，如下所示（你可以使用其他机器在你的LAN上去管理CUPS）：
======/etc/cups/cupsd.conf======
#Listen localhost:631 #Comment this out
Listen 192.168.1.10:631 #Add this line
...
<Location />
Order allow,deny
Allow @LOCAL
</Location>
# Restrict access to the admin pages...
<Location /admin>
Order allow,deny
Allow @LOCAL
</Location>
# Restrict access to configuration files...
<Location /admin/conf>
AuthType Default
Require user @SYSTEM
Order allow,deny
Allow @LOCAL
</Location>
======/etc/cups/cupsd.conf======
添加你的本地ID到lpadmin组就能管理CUPS：
>> sudo usermod -a -G lpadmin YOURUSERIDHERE
重启CUPS：
>> sudo /etc/init.d/cups restart
然后转到http://192.168.1.10:631/并点击 "Adding Printers and Classes"去设置你的打印机。我的打印机是自动发现的USB设备，所以，我只需点击“share”就可以。同样访问https://192.168.1.10:631/admin，确保检查“Share printers connected to this system（共享连接至这个系统的打印机）”。
完成后，你可以用通常的方式设置你的客户端。当我输入主机名，我的Linux客户端就能够自动发现打印机，并选择正确的驱动程序。在我的Windows7的机器上，一旦我选择“Network Printer（网络打印机）”，我必须点击“The printer that I want isn't listed（我想要的打印机未列出）”，选择“Select a shared printer by name（通过名称选择共享的打印机）”，然后从CUPS网络接口输入URL：http://192.168.1.10:631/printers/HP_J4500。
###结论
用最少的额外的硬件和配置，树莓派是高效、简洁的家用服务器。它能够花最小的硬件费用来为你的家庭环境带来由Linux提供的广泛企业服务。
--------------------------------------------------------------------------------
via: http://www.linuxjournal.com/content/raspberry-pi-perfect-home-server
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创翻译，[Linux中国](http://linux.cn/) 荣誉推出
译者：[Vito](https://github.com/vito-L) 校对：[Caroline](https://github.com/carolinewuyan)
[1]:http://www.silentpcreview.com/
[2]:http://www.raspberrypi.org/downloads
[3]:http://www.2brightsparks.com/freeware/freeware-hub.html

4
translated/Say Hello to Linux Kernel 4.0 and Say Goodbye to 3.x.md → published/Say Hello to Linux Kernel 4.0 and Say Goodbye to 3.x.md
View File

@ -2,8 +2,6 @@ Linux内核4.0就要来了！准备对3.x说再见吧！
================================================================================
**Linux Torvalds目前正在考虑尽快更换内核的版本号到4.0，新版本将主要专注于bug修复**
![](http://i1-news.softpedia-static.com/images/news2/Say-Hello-to-Linux-Kernel-4-0-and-Say-Goodbye-to-3-x-396734-2.jpg)
据Linux内核开发维护人员介绍，不远的将来，为了便于管理，Linux的内核版本号将从3.x跳到4.x。Linus Torvalds表示会尽快将其付诸实施。
他在Linux内核3.12的[声明][1]中说道：“我不希望我们再有类似2.x那样令人发狂的版本号经历，因此很快某个时候，我们将直接从3.x跳到4.x，这样版本号更短，更便于记忆。虽然目前暂时还未实现，但是我会尽快，可能最多一年左右吧，到时也许是3.19什么的，之后，就会是4.0。”
@ -20,7 +18,7 @@ Linus说，“之所以我提到‘4.0’，是因为如果我们用几乎一年
via: http://news.softpedia.com/news/Say-Hello-to-Linux-Kernel-4-0-and-Say-Goodbye-to-3-x-396734.shtml
译者：[Mr小眼儿](http://blog.csdn.net/tinyeyeser) 校对：[校对者ID](https://github.com/校对者ID)
译者：[Mr小眼儿](http://blog.csdn.net/tinyeyeser) 校对：[wxy](https://github.com/wxy)
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创翻译，[Linux中国](http://linux.cn/) 荣誉推出

53
published/Upgrade To Linux Kernel 3.11.6 In Ubuntu.md Normal file
View File

@ -0,0 +1,53 @@
在Ubuntu上升级到Linux内核3.11.6
================================================================================
Ubuntu 13.10已经发布，不过它的内核可不是最新的。当然坚持Ubuntu 13.10当前内核不是一件坏事。事实上。不特别建议升级超出你的Linux发行版的官方仓库测试过的特定版本。
但另一方面,如果你不害怕一再折腾Ubuntu，那么你可以试试升级到最新Ubuntu支持的Linux内核。你会发觉最新的内核总是有改善的、修补了漏洞和添加特性的.
所以，如果你的电脑有些运行不正常，那么更新Linux内核可能就能修复。但记住，当你升级时你也有可能导致系统崩溃。
如果你不再惧怕，和我一起永往直前吧，让我们开始升级Ubuntu Linux 内核到 3.11.6!!
首先，在你开始升级之前，请先备份你的数据，以防升级时出错无法恢复。小心行得万年船!!!
更多关于这个内核版本信息，[阅读更改日志][1]。
当你一切准备就绪，运行下列命令来升级你的机器并删除包括比当前更旧的内核在内的旧软件包。
sudo apt-get update && sudo apt-get dist-upgrade && sudo apt-get autoremove
然后，进到/tmp目录。
cd /tmp
接着，复制粘贴下列命令，按回车下载32位的Linux内核
wget http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.11.6-saucy/linux-headers-3.11.6-031106-generic_3.11.6-031106.201310181453_i386.deb http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.11.6-saucy/linux-headers-3.11.6-031106_3.11.6-031106.201310181453_all.deb http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.11.6-saucy/linux-image-3.11.6-031106-generic_3.11.6-031106.201310181453_i386.deb
对于64位Linux内核版本，则复制粘贴下行。
wget http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.11.6-saucy/linux-headers-3.11.6-031106-generic_3.11.6-031106.201310181453_amd64.deb http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.11.6-saucy/linux-headers-3.11.6-031106_3.11.6-031106.201310181453_all.deb http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.11.6-saucy/linux-image-3.11.6-031106-generic_3.11.6-031106.201310181453_amd64.deb
下载适合你的版本，运行下列命令，开始安装：
sudo dpkg -i *.deb
最后，运行下列命令升级Grub。
sudo update-grub2
就这样！重启你的电脑，完成升级!!
玩的开心!
--------------------------------------------------------------------------------
via: http://www.liberiangeek.net/2013/10/upgrade-linux-kernel-3-11-6-ubuntu/
译者：[Luoxcat](https://github.com/Luoxcat) 校对：[wxy](https://github.com/wxy)
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创翻译，[Linux中国](http://linux.cn/) 荣誉推出
[1]:https://www.kernel.org/pub/linux/kernel/v3.x/ChangeLog-3.11.6

18
translated/Using Wine to Play Games On Linux？ Here’s Why You Should Switch To Steam Right Now.markdown → published/Using Wine to Play Games On Linux？ Here’s Why You Should Switch To Steam Right Now.md
View File

@ -1,7 +1,9 @@
#使用Wine在Linux上玩游戏？这儿是一些你为什么应该立即转到Steam平台的理由#
还在使用Wine在Linux上玩游戏？别傻了，用Steam吧！
==================================
![](http://main.makeuseoflimited.netdna-cdn.com/wp-content/uploads/2012/12/steamforlinux.png)
在过去的几个月中，Steam平台受到了众人的关注。并不是因为它带来的游戏，而是由于它拓展支持了不同的操作系统。假如你好没有听说，那么我告诉你，官方宣布Steam计划支持Linux，而且已经持续改进他们的beta版Linux客户端。花不了多长时间，就可以让Steam的Linux客户端平稳下来，所以现在需要做的事情就只是把游戏移植到Linux上了。
在过去的几个月中，Steam平台受到了众人的关注。并不是因为它带来的游戏，而是由于它拓展支持了不同的操作系统。假如你还没有听说过，那么我告诉你，官方宣布Steam计划支持Linux，而且还在持续改进他们的beta版Linux客户端。花不了多长时间，就可以让Steam的Linux客户端平稳下来，所以现在需要做的事情就只是把游戏移植到Linux上了。
现在这项非常重要的服务已经可以在我们可爱的企鹅上使用，这儿还有好多理由指出你为什么应该至少考虑一下转换到Linux平台。
@ -9,25 +11,25 @@
我将以这个明显的优点作为开始 - 使用Steam玩游戏时，性能表现会好很多。当然，同使用Wine玩游戏相比，那就更加显得更加快速咯，因为游戏是原生运行的，无需兼容层。性能是玩游戏时最重要的因素之一，所以人们怎么可以错过这么一个显著的优点呢。
另外，我还注意到使用Steam玩游戏比在Windows上玩游戏还更加快速？同样的硬件同一款游戏，在linux上的表现比Windows上的表现还好。这一点别说比人，连我自己都没想到。
另外，我还注意到使用Steam玩游戏比在Windows上玩游戏还更加快速？同样的硬件同一款游戏，在linux上的表现比Windows上的表现还好。这一点别说别人，连我自己都没想到。
###兼容性###
![](http://main.makeuseoflimited.netdna-cdn.com/wp-content/uploads/2013/01/switch_steam_wine.jpg)
无论何时你购买一个游戏，你均无法保证你购买的游戏可以在Wine上良好运行。虽然有一个Wine兼容性数据库，上面列出了Wine兼容的应用和游戏，但是这只是通过告诉你那些你想购买但是有可能不兼容的应用或游戏从而节省你的金钱 。然而，使用Steam，那些支持Linux的所有游戏都可以保证兼容，不需要去询问任何兼容性问题。
无论何时你购买一个游戏，你都无法保证你购买的游戏可以在Wine上良好运行。虽然有一个Wine兼容性数据库，上面列出了Wine兼容的应用和游戏，但是这只是告诉你有哪些想购买但是有可能不兼容的应用或游戏，从而节省你的金钱。然而，使用Steam，那些支持Linux的所有游戏都可以保证兼容，不需要去询问任何兼容性问题。
###Steam的优点###
![](http://main.makeuseoflimited.netdna-cdn.com/wp-content/uploads/2013/01/switch_steam_window.jpg)
当然，转到Steam平台你就可以获得它所有的好处。这包括：偶尔的价格优惠（尤其是那些在售的游戏），完全在在线体验不在需要物理媒介，游戏和客户端 更新时你可以保持同步更新等。
当然，转到Steam平台你就可以获得它所有的好处。这包括：偶尔的价格优惠（尤其是那些在售的游戏），完全在线体验，不再需要物理介质，游戏和客户端更新时你可以保持同步更新等。
例如，若你在你的电脑上重装了系统，你只需打开Steam，坐在一旁休息，它就可以自动下载并安装所有你安装过的游戏。在Windows和Mac OS X上，人们非常喜欢Steam的这种运作方式，所以这是一个你购买游戏的好去处。
###让你的声音被听到###
###后排的朋友，让我听到你的声音！###
最后，转到Steam平台，你是在表明你的态度。若Steam对于Linux平台的努力无法引起你游戏的兴趣，那么我会感到非常惊讶。作为社区的一份子，我们需要对那些我们喜欢的项目 表示支持。转到Steam平台，不仅可以让Steam公司对于在Linux平台上的冒险值得，而且也告诉了其它人Linux完全可以作为游戏平台——只是由于历史的缘故，人们只是没有在这方面投入足够的时间和经历使其取得突破而已。
最后，转到Steam平台，你是在表明你的态度。若Steam对于Linux平台的努力无法引起你游戏的兴趣，那么我会感到非常惊讶。作为社区的一份子，我们需要对那些我们喜欢的项目表示支持。转到Steam平台，不仅可以让Steam公司觉得对于在Linux平台上的冒险值得，而且也告诉了其它人Linux完全可以作为游戏平台——只是由于历史的缘故，人们只是没有在这方面投入足够的时间和经历使其取得突破而已。
假如我们向人们展示使用Linux的人们也是喜欢玩游戏的，而且通过支持Linux是可以获得利润的，那么人们就可能更加乐意开发支持Linux的游戏。另外，我们都希望有更多的Linux原生游戏，难道不是吗？
@ -39,6 +41,6 @@
via: http://www.makeuseof.com/tag/using-wine-to-play-games-on-linux-heres-why-you-should-switch-to-steam-right-now/
译者：[Linux-pdz](https://github.com/Linux-pdz) 校对：[校对者ID](https://github.com/校对者ID)
译者：[Linux-pdz](https://github.com/Linux-pdz) 校对：[wxy](https://github.com/wxy)
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创翻译，[Linux中国](http://linux.cn/) 荣誉推出

5
sources/How to add kernel boot parameters via GRUB on Linux.md
View File

@ -1,3 +1,6 @@
**【晨光】翻译中**
How to add kernel boot parameters via GRUB on Linux
================================================================================
The Linux kernel can be supplied with various parameters during boot time or at run time. These parameters customize the default behavior of the kernel, or inform the kernel about hardware configuration. Kernel parameters can be changed at run time by modifying files in /proc or /sys, while certain kernel parameters need be passed to the kernel at boot time by a boot loader such as GRUB or LILO.
@ -50,4 +53,4 @@ via: http://xmodulo.com/2013/11/add-kernel-boot-parameters-via-grub-linux.html
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创翻译，[Linux中国](http://linux.cn/) 荣誉推出
[1]:http://www.flickr.com/photos/xmodulo/10618657834/
[1]:http://www.flickr.com/photos/xmodulo/10618657834/

98
sources/How to monitor system temperature on Linux.md Normal file
View File

@ -0,0 +1,98 @@
How to monitor system temperature on Linux
================================================================================
In most cases, you are not supposed to be worried about the temperature of your computer. Barring manufacturing defects, hardware is designed so that its temperature does not exceed maximum operating temperature. But even without any hardware fault, overheating can occur due to various software issues, e.g., buggy graphics card driver, misconfigured fan control program, malfunctioning CPU frequency scaling daemon, etc.
Overheating may become serious enough to cause permanent damage on your hardware. So watch out for any overheating issue in your system. Even better, have temperature monitoring system in place, so that you will be alerted if system temperature suddenly goes up.
In this tutorial, I will describe **how to monitor system temperature on Linux**.
There are several user space tools on Linux, which allow you to check and monitor temperature of various system components.
[lm-sensors][1] is a software tool that draws from hardware embedded sensors to monitor temperatures, voltage, humidity and fans. [hddtemp][2] is a tool that can measure the temperature of hard drives from [S.M.A.R.T.][3] readings. [psensor][4] is a graphical front-end for temperature monitoring, which visualizes temperature readings from CPUs, NVidia/ATI/AMD GPUs, hard disks, etc.
In the following, I will describe how to set up psensor to monitor the temperature of CPUs and hard drives.
### Install psensor on Linux Desktop ###
psensor can visualize system temperature based on the information obtained from other tools such as lm-sensors and hddtemp. Thus you need to install psensor along with those prerequisites.
To install psensor on Debian or Ubuntu:
$ sudo apt-get install lm-sensors hddtemp psensor
To install psensor on Fedora:
$ sudo yum install lm_sensors hddtemp
$ sudo yum install gcc gtk3-devel GConf2-devel lm_sensors-devel cppcheck libatasmart-devel libcurl-devel json-c-devel libmicrohttpd-devel help2man libnotify-devel libgtop2-devel make
$ wget http://wpitchoune.net/psensor/files/psensor-0.8.0.3.tar.gz
$ tar xvfvz psensor-0.8.0.3.tar.gz
$ cd psensor-0.8.0.3
$ ./configure
$ make
$ sudo make install
Due to the requirement for GTK3 libraries, psensor is not compatible with the GNOME 2 desktop of CentOS or RHEL 6.
### Configure psensor on Linux ###
Before launching psensor, you need to configure lm_sensors and hddtemp first.
#### lm_sensors configuration ####
To configure lm_sensors, run the following command. Choose YES to every question.
$ sudo sensors-detect
This command will probe for and detect embedded sensors in your hardware (including CPUs, memory controllers, I/O chips), and automatically determine which driver modules need to be loaded to check temperature on your system.
Once sensor probing is completed, you will be asked to add detected driver module(s) to /etc configuration, so they can be loaded automatically upon boot.
On Debian or Ubuntu, detected driver modules will be added to /etc/modules. On Fedora, the driver information will be added to /etc/sysconfig/lm_sensors.
Next, proceed to load necessary modules as follows.
On Ubuntu:
$ sudo service module-init-tools start
On Debian:
$ sudo /etc/init.d/kmod start
On Fedora:
$ sudo service lm_sensors start
#### hddtemp configuration ####
You also need to launch hddtemp which monitors the temperature of hard drives.
Run the following command to launch hddtemp as a daemon. Replace “/dev/sda” with the disk drive to monitor on your system.
$ sudo hddtemp -d /dev/sda
### Monitor System Temperature with psensor ###
To start monitoring temperature with psensor, simply run:
$ psensor
The psensor window will show a list of available sensors, and visualize temperature readings from these sensors. You can selectively enable or disable each sensor.
[![](http://farm8.staticflickr.com/7448/10719475225_f89b6f7191_z.jpg)][5]
Optionally, you can set an alarm level for each sensor, so that you can be notified when the temperature from a sensor exceeds a threshold.
--------------------------------------------------------------------------------
via: http://xmodulo.com/2013/11/monitor-system-temperature-linux.html
译者：[译者ID](https://github.com/译者ID) 校对：[校对者ID](https://github.com/校对者ID)
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创翻译，[Linux中国](http://linux.cn/) 荣誉推出
[1]:http://lm-sensors.org/
[2]:http://www.guzu.net/linux/hddtemp.php
[3]:http://en.wikipedia.org/wiki/S.M.A.R.T.
[4]:http://wpitchoune.net/blog/psensor/
[5]:http://www.flickr.com/photos/xmodulo/10719475225/

4
sources/How to set up web-based network traffic monitoring system on Linux.md
View File

@ -1,3 +1,5 @@
翻译中 by小眼儿
How to set up web-based network traffic monitoring system on Linux
================================================================================
When you are tasked with monitoring network traffic on the local network, you can consider many different options to do it, depending on the scale/traffic of the local network, monitoring platforms/interface, types of backend database, etc.
@ -119,4 +121,4 @@ via: http://xmodulo.com/2013/10/set-web-based-network-traffic-monitoring-linux.h
[7]:http://xmodulo.com/go/fedora_guide
[8]:http://www.flickr.com/photos/xmodulo/10487165303/
[9]:http://www.flickr.com/photos/xmodulo/10486988416/
[10]:http://www.flickr.com/photos/xmodulo/10486995114/
[10]:http://www.flickr.com/photos/xmodulo/10486995114/

447
sources/Linux Commands/Package Management Using YUM In Red Hat Linux.md Normal file
View File

@ -0,0 +1,447 @@
Package Management Using YUM In Red Hat Linux
================================================================================
![](http://linoxide.com/wp-content/uploads/2013/11/yum-package-install.png)
**Yum** is a utility provided in RHEL based systems to install,remove and search packages. It can do lot more than just installing and removing and that’s what I will demonstrate in this article.
Yum installs the package dependencies automatically, for example yum install httpd will install https apache server and it’s required dependencies automatically. Something that is not that easy while installing through rpm. with rpm you have to download all the required dependencies and then install accordingly.
The yum utility fetches the package information from a hosted repository (usually by the OS vendor). A repository is basically a collection of rpm’s that are supposed to work on a particular architecture. For example there would be a separate repository for 32 and 64 bit systems, and same goes with RHEL Version 5 and Version 6. You can host your local repository and configure yum to search,install packages from the local repository. In the following examples I will show you some other stuff we can do with yum rather than install and remove but for the sake of understanding I will use httpd package for exempts on my Amazon EC2 RHEL 6.4 server.
### Search package from repository ###
# yum search httpd
Loaded plugins: amazon-id, rhui-lb, security
=============================================== N/S Matched: httpd ==========
httpd.x86_64 : Apache HTTP Server
httpd-devel.i686 : Development interfaces for the Apache HTTP server
httpd-devel.x86_64 : Development interfaces for the Apache HTTP server
httpd-manual.noarch : Documentation for the Apache HTTP server
httpd-tools.x86_64 : Tools for use with the Apache HTTP Server
mod_dav_svn.x86_64 : Apache httpd module for Subversion server
mod_dnssd.x86_64 : An Apache HTTPD module which adds Zeroconf support
For a more detailed output use the below command:
# yum provides httpd
Loaded plugins: amazon-id, rhui-lb, security
httpd-2.2.15-26.el6.x86_64 : Apache HTTP Server
Repo : rhui-REGION-rhel-server-releases
Matched from:
**yum provides */httpd** Searches in yum packages to find the package that contains a httpd.
### Provide a list of all Package Groups. ###
# yum grouplist
The above command will show you the installed and available package group. You can install an individual package group with group install option. For example we will install package group PHP Support. This package group contains the required php packages.
# yum groupinstall PHP Support
Loaded plugins: amazon-id, downloadonly, rhui-lb, security
Setting up Group Process
Warning: Group Support does not exist.
Resolving Dependencies
–> Running transaction check
—> Package php.x86_64 0:5.3.3-23.el6_4 will be installed
–> Processing Dependency: php-common(x86-64) = 5.3.3-23.el6_4 for package: php-5.3.3-23.el6_4.x86_64
–> Processing Dependency: php-cli(x86-64) = 5.3.3-23.el6_4 for package: php-5.3.3-23.el6_4.x86_64
—> Package php-gd.x86_64 0:5.3.3-23.el6_4 will be installed
–> Processing Dependency: libXpm.so.4()(64bit) for package: php-gd-5.3.3-23.el6_4.x86_64
—> Package php-pdo.x86_64 0:5.3.3-23.el6_4 will be installed
—> Package php-pear.noarch 1:1.9.4-4.el6 will be installed
—> Package php-xml.x86_64 0:5.3.3-23.el6_4 will be installed
–> Running transaction check
—> Package libXpm.x86_64 0:3.5.10-2.el6 will be installed
—> Package php-cli.x86_64 0:5.3.3-23.el6_4 will be installed
—> Package php-common.x86_64 0:5.3.3-23.el6_4 will be installed
–> Finished Dependency Resolution
Dependencies Resolved
=====================================================================
Package Arch Version Repository Size
=====================================================================
Installing:
php x86_64 5.3.3-23.el6_4 rhui-REGION-rhel-server-releases 1.1 M
php-gd x86_64 5.3.3-23.el6_4 rhui-REGION-rhel-server-releases 106 k
php-pdo x86_64 5.3.3-23.el6_4 rhui-REGION-rhel-server-releases 75 k
php-pear noarch 1:1.9.4-4.el6 rhui-REGION-rhel-server-releases 393 k
php-xml x86_64 5.3.3-23.el6_4 rhui-REGION-rhel-server-releases 103 k
Installing for dependencies:
libXpm x86_64 3.5.10-2.el6 rhui-REGION-rhel-server-releases 51 k
php-cli x86_64 5.3.3-23.el6_4 rhui-REGION-rhel-server-releases 2.2 M
php-common x86_64 5.3.3-23.el6_4 rhui-REGION-rhel-server-releases 524 k
Transaction Summary
========================================================================
Install 8 Package(s)
Total download size: 4.5 M
Installed size: 16 M
Is this ok [y/N]: y
Downloading Packages:
(1/8): libXpm-3.5.10-2.el6.x86_64.rpm | 51 kB 00:00
(2/8): php-5.3.3-23.el6_4.x86_64.rpm | 1.1 MB 00:00
(3/8): php-cli-5.3.3-23.el6_4.x86_64.rpm | 2.2 MB 00:00
(4/8): php-common-5.3.3-23.el6_4.x86_64.rpm | 524 kB 00:00
(5/8): php-gd-5.3.3-23.el6_4.x86_64.rpm | 106 kB 00:00
(6/8): php-pdo-5.3.3-23.el6_4.x86_64.rpm | 75 kB 00:00
(7/8): php-pear-1.9.4-4.el6.noarch.rpm | 393 kB 00:00
(8/8): php-xml-5.3.3-23.el6_4.x86_64.rpm | 103 kB 00:00
———————————————————————-
Total 2.9 MB/s | 4.5 MB 00:01
Running rpm_check_debug
Running Transaction Test
Transaction Test Succeeded
Running Transaction
Installing : php-common-5.3.3-23.el6_4.x86_64 1/8
Installing : php-cli-5.3.3-23.el6_4.x86_64 2/8
Installing : libXpm-3.5.10-2.el6.x86_64 3/8
Installing : php-gd-5.3.3-23.el6_4.x86_64 4/8
Installing : 1:php-pear-1.9.4-4.el6.noarch 5/8
Installing : php-5.3.3-23.el6_4.x86_64 6/8
Installing : php-xml-5.3.3-23.el6_4.x86_64 7/8
Installing : php-pdo-5.3.3-23.el6_4.x86_64 8/8
Verifying : 1:php-pear-1.9.4-4.el6.noarch 1/8
Verifying : php-xml-5.3.3-23.el6_4.x86_64 2/8
Verifying : php-common-5.3.3-23.el6_4.x86_64 3/8
Verifying : libXpm-3.5.10-2.el6.x86_64 4/8
Verifying : php-cli-5.3.3-23.el6_4.x86_64 5/8
Verifying : php-5.3.3-23.el6_4.x86_64 6/8
Verifying : php-pdo-5.3.3-23.el6_4.x86_64 7/8
Verifying : php-gd-5.3.3-23.el6_4.x86_64 8/8
Installed:
php.x86_64 0:5.3.3-23.el6_4 php-gd.x86_64 0:5.3.3-23.el6_4 php-pdo.x86_64 0:5.3.3-23.el6_4
php-pear.noarch 1:1.9.4-4.el6 php-xml.x86_64 0:5.3.3-23.el6_4
Dependency Installed:
libXpm.x86_64 0:3.5.10-2.el6 php-cli.x86_64 0:5.3.3-23.el6_4 php-common.x86_64 0:5.3.3-23.el6_4
Complete!
### Install package using YUM ###
A package can be installed using yum install command as below:
# yum install httpd
Loaded plugins: amazon-id, rhui-lb, security
Setting up Install Process
Resolving Dependencies
–> Running transaction check
—> Package httpd.x86_64 0:2.2.15-29.el6_4 will be installed
–> Processing Dependency: httpd-tools = 2.2.15-29.el6_4 for package: httpd-2.2.15-29.el6_4.x86_64
–> Processing Dependency: apr-util-ldap for package: httpd-2.2.15-29.el6_4.x86_64
–> Processing Dependency: libaprutil-1.so.0()(64bit) for package: httpd-2.2.15-29.el6_4.x86_64
–> Processing Dependency: libapr-1.so.0()(64bit) for package: httpd-2.2.15-29.el6_4.x86_64
–> Running transaction check
—> Package apr.x86_64 0:1.3.9-5.el6_2 will be installed
—> Package apr-util.x86_64 0:1.3.9-3.el6_0.1 will be installed
—> Package apr-util-ldap.x86_64 0:1.3.9-3.el6_0.1 will be installed
—> Package httpd-tools.x86_64 0:2.2.15-29.el6_4 will be installed
–> Finished Dependency Resolution
Dependencies Resolved
=============================================================================
Package Arch Version Repository Size
=============================================================================
Installing:
httpd x86_64 2.2.15-29.el6_4 rhui-REGION-rhel-server-releases 821 k
Installing for dependencies:
apr x86_64 1.3.9-5.el6_2 rhui-REGION-rhel-server-releases 123 k
apr-util x86_64 1.3.9-3.el6_0.1 rhui-REGION-rhel-server-releases 87 k
apr-util-ldap x86_64 1.3.9-3.el6_0.1 rhui-REGION-rhel-server-releases 15 k
httpd-tools x86_64 2.2.15-29.el6_4 rhui-REGION-rhel-server-releases 73 k
Transaction Summary
==============================================================================
Install 5 Package(s)
Total download size: 1.1 M
Installed size: 3.6 M
Is this ok [y/N]: y
As you can see yum added additional packages with httpd installation. This is called the dependency resolution done by yum.
If you want yum not to prompt for the [y/N] option. Use **yum install -y httpd**
**Update an existing package using yum update command.**
# yum update httpd
Loaded plugins: amazon-id, rhui-lb, security
Setting up Update Process
No Packages marked for Update
That means the httpd package is the latest version in the yum’s repository.
**Update all packages on the server.**
# yum update
the above command will update all the packages including kernel package to the latest version that means your OS will be updated to the latest provided by RHEL.
### Download RPM without installing ###
Use yum to download RPM package from RHN or CentOS repository without installing it. You have to install a plugin for yum first to have yum download the rpm only. The utility name is yum-downloadonly and can be installed through yum as below:
# yum install yum-downloadonly
Loaded plugins: amazon-id, rhui-lb, security
Setting up Install Process
Resolving Dependencies
–> Running transaction check
—> Package yum-plugin-downloadonly.noarch 0:1.1.30-14.el6 will be installed
–> Finished Dependency Resolution
Dependencies Resolved
===========================================================================
Package Arch Version Repository Size
===========================================================================
Installing:
yum-plugin-downloadonly noarch 1.1.30-14.el6 rhui-REGION-rhel-server-releases 20 k
Transaction Summary
===========================================================================
Install 1 Package(s)
Total download size: 20 k
Installed size: 21 k
Is this ok [y/N]: y
Downloading Packages:
yum-plugin-downloadonly-1.1.30-14.el6.noarch.rpm | 20 kB 00:00
Running rpm_check_debug
Running Transaction Test
Transaction Test Succeeded
Running Transaction
Installing : yum-plugin-downloadonly-1.1.30-14.el6.noarch 1/1
Verifying : yum-plugin-downloadonly-1.1.30-14.el6.noarch 1/1
Installed:
yum-plugin-downloadonly.noarch 0:1.1.30-14.el6
Complete!
Now you can just download a package from repository without installing it by using this command:
# yum install httpd-devel –downloadonly
By default packages are downloaded to **/var/cache/yum/<arch\>** directory but you can download them a specified location by adding another option to yum command
# yum install httpd-devel –downloadonly –downloaddir=/opt
If you have a rpm of a package but you don’t have the dependencies and you do not know where to get that. you can still have yum to install that rpm and get the required dependencies from the repository. Let’s install the httpd-devel-2.2.15-29.el6_4.x86_64 RPM that we just downloaded.
# yum localinstall /opt/httpd-devel-2.2.15-29.el6_4.x86_64.rpm
Loaded plugins: amazon-id, downloadonly, rhui-lb, security
Setting up Local Package Process
Examining /opt/httpd-devel-2.2.15-29.el6_4.x86_64.rpm: httpd-devel-2.2.15-29.el6_4.x86_64
Marking /opt/httpd-devel-2.2.15-29.el6_4.x86_64.rpm to be installed
Resolving Dependencies
–> Running transaction check
—> Package httpd-devel.x86_64 0:2.2.15-29.el6_4 will be installed
–> Processing Dependency: apr-devel for package: httpd-devel-2.2.15-29.el6_4.x86_64
–> Processing Dependency: apr-util-devel for package: httpd-devel-2.2.15-29.el6_4.x86_64
–> Running transaction check
—> Package apr-devel.x86_64 0:1.3.9-5.el6_2 will be installed
—> Package apr-util-devel.x86_64 0:1.3.9-3.el6_0.1 will be installed
–> Processing Dependency: openldap-devel for package: apr-util-devel-1.3.9-3.el6_0.1.x86_64
–> Processing Dependency: expat-devel for package: apr-util-devel-1.3.9-3.el6_0.1.x86_64
–> Processing Dependency: db4-devel for package: apr-util-devel-1.3.9-3.el6_0.1.x86_64
–> Running transaction check
—> Package db4-devel.x86_64 0:4.7.25-18.el6_4 will be installed
–> Processing Dependency: db4-cxx = 4.7.25-18.el6_4 for package: db4-devel-4.7.25-18.el6_4.x86_64
–> Processing Dependency: db4 = 4.7.25-18.el6_4 for package: db4-devel-4.7.25-18.el6_4.x86_64
–> Processing Dependency: libdb_cxx-4.7.so()(64bit) for package: db4-devel-4.7.25-18.el6_4.x86_64
—> Package expat-devel.x86_64 0:2.0.1-11.el6_2 will be installed
—> Package openldap-devel.x86_64 0:2.4.23-32.el6_4.1 will be installed
–> Processing Dependency: cyrus-sasl-devel >= 2.1 for package: openldap-devel-2.4.23-32.el6_4.1.x86_64
–> Running transaction check
—> Package cyrus-sasl-devel.x86_64 0:2.1.23-13.el6_3.1 will be installed
—> Package db4.x86_64 0:4.7.25-17.el6 will be updated
–> Processing Dependency: db4 = 4.7.25-17.el6 for package: db4-utils-4.7.25-17.el6.x86_64
—> Package db4.x86_64 0:4.7.25-18.el6_4 will be an update
—> Package db4-cxx.x86_64 0:4.7.25-18.el6_4 will be installed
–> Running transaction check
—> Package db4-utils.x86_64 0:4.7.25-17.el6 will be updated
—> Package db4-utils.x86_64 0:4.7.25-18.el6_4 will be an update
–> Finished Dependency Resolution
Dependencies Resolved
=============================================================================
Package Arch Version Repository Size
=============================================================================
Installing:
httpd-devel x86_64 2.2.15-29.el6_4 /httpd-devel-2.2.15-29.el6_4.x86_64 526 k
Installing for dependencies:
apr-devel x86_64 1.3.9-5.el6_2 rhui-REGION-rhel-server-releases 176 k
apr-util-devel x86_64 1.3.9-3.el6_0.1 rhui-REGION-rhel-server-releases 69 k
cyrus-sasl-devel x86_64 2.1.23-13.el6_3.1 rhui-REGION-rhel-server-releases 302 k
db4-cxx x86_64 4.7.25-18.el6_4 rhui-REGION-rhel-server-releases 588 k
db4-devel x86_64 4.7.25-18.el6_4 rhui-REGION-rhel-server-releases 6.6 M
expat-devel x86_64 2.0.1-11.el6_2 rhui-REGION-rhel-server-releases 120 k
openldap-devel x86_64 2.4.23-32.el6_4.1 rhui-REGION-rhel-server-releases 1.1 M
Updating for dependencies:
db4 x86_64 4.7.25-18.el6_4 rhui-REGION-rhel-server-releases 563 k
db4-utils x86_64 4.7.25-18.el6_4 rhui-REGION-rhel-server-releases 130 k
Transaction Summary
=======================================================================
Install 8 Package(s)
Upgrade 2 Package(s)
Total size: 10 M
Is this ok [y/N]: y
Downloading Packages:
Running rpm_check_debug
Running Transaction Test
Transaction Test Succeeded
Running Transaction
Updating : db4-4.7.25-18.el6_4.x86_64 1/12
Installing : apr-devel-1.3.9-5.el6_2.x86_64 2/12
Installing : expat-devel-2.0.1-11.el6_2.x86_64 3/12
Installing : db4-cxx-4.7.25-18.el6_4.x86_64 4/12
Installing : db4-devel-4.7.25-18.el6_4.x86_64 5/12
Installing : cyrus-sasl-devel-2.1.23-13.el6_3.1.x86_64 6/12
Installing : openldap-devel-2.4.23-32.el6_4.1.x86_64 7/12
Installing : apr-util-devel-1.3.9-3.el6_0.1.x86_64 8/12
Installing : httpd-devel-2.2.15-29.el6_4.x86_64 9/12
Updating : db4-utils-4.7.25-18.el6_4.x86_64 10/12
Cleanup : db4-utils-4.7.25-17.el6.x86_64 11/12
Cleanup : db4-4.7.25-17.el6.x86_64 12/12
Verifying : apr-devel-1.3.9-5.el6_2.x86_64 1/12
Verifying : cyrus-sasl-devel-2.1.23-13.el6_3.1.x86_64 2/12
Verifying : apr-util-devel-1.3.9-3.el6_0.1.x86_64 3/12
Verifying : db4-cxx-4.7.25-18.el6_4.x86_64 4/12
Verifying : httpd-devel-2.2.15-29.el6_4.x86_64 5/12
Verifying : openldap-devel-2.4.23-32.el6_4.1.x86_64 6/12
Verifying : expat-devel-2.0.1-11.el6_2.x86_64 7/12
Verifying : db4-devel-4.7.25-18.el6_4.x86_64 8/12
Verifying : db4-4.7.25-18.el6_4.x86_64 9/12
Verifying : db4-utils-4.7.25-18.el6_4.x86_64 10/12
Verifying : db4-4.7.25-17.el6.x86_64 11/12
Verifying : db4-utils-4.7.25-17.el6.x86_64 12/12
Installed:
httpd-devel.x86_64 0:2.2.15-29.el6_4
Dependency Installed:
apr-devel.x86_64 0:1.3.9-5.el6_2 apr-util-devel.x86_64 0:1.3.9-3.el6_0.1
cyrus-sasl-devel.x86_64 0:2.1.23-13.el6_3.1 db4-cxx.x86_64 0:4.7.25-18.el6_4
db4-devel.x86_64 0:4.7.25-18.el6_4 expat-devel.x86_64 0:2.0.1-11.el6_2
openldap-devel.x86_64 0:2.4.23-32.el6_4.1
Dependency Updated:
db4.x86_64 0:4.7.25-18.el6_4 db4-utils.x86_64 0:4.7.25-18.el6_4
Complete!
### Removing packages using yum. ###
yum remove Remove a package.
# yum remove httpd
Failed to set locale, defaulting to C
Loaded plugins: amazon-id, downloadonly, rhui-lb, security
Setting up Remove Process
Resolving Dependencies
–> Running transaction check
—> Package httpd.x86_64 0:2.2.15-29.el6_4 will be erased
–> Processing Dependency: httpd-mmn = 20051115 for package: php-5.3.3-23.el6_4.x86_64
–> Processing Dependency: httpd = 2.2.15-29.el6_4 for package: httpd-devel-2.2.15-29.el6_4.x86_64
–> Running transaction check
—> Package httpd-devel.x86_64 0:2.2.15-29.el6_4 will be erased
—> Package php.x86_64 0:5.3.3-23.el6_4 will be erased
–> Finished Dependency Resolution
Dependencies Resolved
========================================================================
Package Arch Version Repository Size
========================================================================
Removing:
httpd x86_64 2.2.15-29.el6_4 @rhui-REGION-rhel-server-releases 2.9 M
Removing for dependencies:
httpd-devel x86_64 2.2.15-29.el6_4 @/httpd-devel-2.2.15-29.el6_4.x86_64 526 k
php x86_64 5.3.3-23.el6_4 @rhui-REGION-rhel-server-releases 3.5 M
Transaction Summary
==========================================================================
Remove 3 Package(s)
Installed size: 7.0 M
Is this ok [y/N]: y
Downloading Packages:
Running rpm_check_debug
Running Transaction Test
Transaction Test Succeeded
Running Transaction
Erasing : httpd-devel-2.2.15-29.el6_4.x86_64 1/3
Erasing : php-5.3.3-23.el6_4.x86_64 2/3
Erasing : httpd-2.2.15-29.el6_4.x86_64 3/3
Verifying : httpd-2.2.15-29.el6_4.x86_64 1/3
Verifying : httpd-devel-2.2.15-29.el6_4.x86_64 2/3
Verifying : php-5.3.3-23.el6_4.x86_64 3/3
Removed:
httpd.x86_64 0:2.2.15-29.el6_4
Dependency Removed:
httpd-devel.x86_64 0:2.2.15-29.el6_4 php.x86_64 0:5.3.3-23.el6_4
Complete!
### List all installed packages ###
If you want to list all the installed packages then you can use yum list installed command. This is useful in combination with grep or to check whether a specific package has been installed. This is similar to query installed packages with rpm -qa command.
# yum list installed
Loaded plugins: amazon-id, downloadonly, rhui-lb, security
Installed Packages
ConsoleKit.x86_64 0.4.1-3.el6 @koji-override-0/$releasever
ConsoleKit-libs.x86_64 0.4.1-3.el6 @koji-override-0/$releasever
MAKEDEV.x86_64 3.24-6.el6 @koji-override-0/$releasever
PyYAML.x86_64 3.10-3.1.el6 @koji-override-0/$releasever
Red_Hat_Enterprise_Linux-Release_Notes-6-en-US.noarch
4-2.el6 @koji-override-0/$releasever
SDL.x86_64 1.2.14-3.el6 @koji-override-0/$releasever
abrt.x86_64 2.0.8-15.el6 @koji-override-0/$releasever
abrt-addon-ccpp.x86_64 2.0.8-15.el6 @koji-override-0/$releasever
abrt-addon-kerneloops.x86_64 2.0.8-15.el6 @koji-override-0/$releasever
abrt-addon-python.x86_64 2.0.8-15.el6 @koji-override-0/$releasever
abrt-cli.x86_64 2.0.8-15.el6 @koji-override-0/$releasever
abrt-libs.x86_64 2.0.8-15.el6 @koji-override-0/$releasever
abrt-tui.x86_64 2.0.8-15.el6 @koji-override-0/$releasever
acl.x86_64 2.2.49-6.el6 @koji-override-0/$releasever
acpid.x86_64 1.0.10-2.1.el6 @koji-override-0/$releasever
aic94xx-firmware.noarch 30-2.el6 @koji-override-0/$releasever
.
.
Output Truncated.
### List the available repository from which packages are being queried, installed and updated. ###
# yum repolist
Loaded plugins: amazon-id, downloadonly, rhui-lb, security
repo id repo name status
rhui-REGION-client-config-server-6 Red Hat Update Infrastructure 2.0 Client Configuration Server 6 4
rhui-REGION-rhel-server-releases Red Hat Enterprise Linux Server 6 (RPMs) 10994
rhui-REGION-rhel-server-releases-optional Red Hat Enterprise Linux Server 6 Optional (RPMs) 6250
repolist: 17248
--------------------------------------------------------------------------------
via: http://linoxide.com/linux-command/package-management-yum-redhat-linux/
译者：[译者ID](https://github.com/译者ID) 校对：[校对者ID](https://github.com/校对者ID)
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创翻译，[Linux中国](http://linux.cn/) 荣誉推出

38
sources/Linux Desktop In The Enterprise--Ubuntu Vs. Windows.md Normal file
View File

@ -0,0 +1,38 @@
Linux Desktop In The Enterprise: Ubuntu Vs. Windows
================================================================================
The "year of the Linux desktop" has been prophesied by Linux supporters almost every year for the last decade. This was once a lofty goal in the Microsoft-dominated enterprise, but times are changing. Linux has grown into a formidable competitor in the smartphone and cloud computing markets, which has caught Microsoft off guard. More importantly, Google, IBM, Red Hat, Facebook, and Netflix have made huge investments into Linux innovations.
Now, with shrinking technology budgets and rising Microsoft licensing fees, it's time for IT to seriously consider desktop Linux deployment as an alternative to Windows. The timing for this couldn't be better: Windows 8.1 was just released, as was the latest version of Ubuntu, 13.10. Windows XP has just five months of support left, so companies need to make the switch to something new. Ubuntu may just have what companies need to support their desktop OS needs. I'll look at various considerations for making the Linux desktop switch, including training and support, as well as potential complications.
I know that Ubuntu has lost some of the favor it once enjoyed in the open source community. Canonical, the creators of Ubuntu, have made some unpopular choices, including changing the display manager -- the base component of the graphical interface in Linux-- to the internally developed Mir instead of Wayland. However, Ubuntu remains completely open source and offers the most painless install of any Linux distribution or even Windows version, for that matter. Canonical also offers paid support, which may be needed in enterprise environments.
There has always been the argument that end users will need retraining if they switch over to a new desktop interface. Microsoft's controversial decision to overhaul the familiar interface for Windows 8.1 now requires just as much training as switching to Linux. Ubuntu's Unity desktop has evolved into a user friendly interface that is arguably more easily understood by end users than Windows 8.1.
For example, compare how a user shuts down the system in each operating system. In all recent versions of Ubuntu, it starts with one click in the right corner of the screen, where the symbol for on-off is located. A menu drops down and one more click shuts down the machine. Windows 8.1 requires a right-click on the Start button, where a menu drops down allowing for a shutdown. This was a vast improvement over Windows 8, which required a trip to the charms bar, but still not as obvious as an icon located directly on the screen.
End-user training for applications is a less complex task nowadays, thanks to the Windows versions of many popular open source applications. Users may already be familiar with Firefox, LibreOffice, Pidgin, and VLC Media Player on Windows. Commercial applications used in business, such as Skype and Adobe Acrobat, function just like their Windows equivalents. Cloud-based applications such as Google Drive or Microsoft Office 365 work well on Ubuntu.
Legacy Windows applications can be accessed through the familiar Citrix client or open source RDP clients. Companies also can use open source virtualization products such as VirtualBox to run the most stubborn legacy Windows applications.
On the support front, many technicians will remember the earlier days of Linux when hardware support was extremely limited. That simply is not the case anymore.
Linux hardware support is oftentimes better than the latest versions of Windows. Many hardware vendors have been dropping driver support for newer versions of Windows. The open source drivers in Linux can be kept up to date by anyone in the developer community, so a lot of older hardware is fully supported in the latest versions of Ubuntu. This fact, plus Ubuntu's lower system requirements, will allow companies to extend the life of hardware once destined for the recycling bin.
While there are upsides to a Linux desktop replacement program, there are some potential difficulties companies should consider. While many technicians have already been using Linux or will be motivated by the prospect of learning new skills, there also will be technicians who have spent a lot of time developing a comfort level managing Windows and may be reluctant to embrace the change.
Citing salary trends is one way to address this potential issue. The salaries of positions with Linux skills requirements are rising at nearly double the rate of other technical professionals, according to Dice.
Companies under stringent compliance requirements may have difficulties switching over to Linux. For example, HIPAA requires encryption that meets FIPS-140-2 requirements. Most open source encryption projects do not have sponsors to get them through the NIST certification to meet this requirement. Open source may actually be more secure than proprietary software because of the number of people that have reviewed the source code, but surprisingly that doesn't matter in the world of compliance.
Businesses need to understand their compliance requirements and develop a plan for training IT staff before deciding to move forward with a full conversion. But overall, Ubuntu Linux has matured into a viable alternative to proprietary operating systems in the enterprise. The effort companies put into a Linux desktop replacement program will be worth the savings in licensing fees. Next year may finally be the “year of the Linux desktop.”
> Joseph Granneman has more than 20 years of technology experience, primarily focused in health care information technology. He is CIO for Rockford Orthopedic Associates in Rockford, Ill., and an active independent author, presenter and professor in the health care information technology and information security fields. Granneman has been active in many standards groups, including developing the early frameworks for Health Information Exchange as part of the Health Information Security and Privacy Security Working Group for Illinois. He was also a volunteer for the Certification Commission for Health Information Technology (CCHIT) Security Working Group, which developed the information security standards for ARRA certification of electronic medical records.
--------------------------------------------------------------------------------
via: http://www.networkcomputing.com/data-networking-management/linux-desktop-in-the-enterprise-ubuntu-v/240163564
译者：[译者ID](https://github.com/译者ID) 校对：[校对者ID](https://github.com/校对者ID)
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创翻译，[Linux中国](http://linux.cn/) 荣誉推出

142
sources/The Linux Kernel/14 The Linux Kernel--Configuring the Kernel Part 10.md
View File

@ -1,142 +0,0 @@
Translating-----------geekpi
14 The Linux Kernel: Configuring the Kernel Part 10
================================================================================
![](http://www.linux.org/attachments/slide-jpg.514/)
Wireless broadband devices that use the WiMAX protocol can be enabled (WiMAX Wireless Broadband support). This type of wireless connection usually works only if the connection service is provided by a service provider (this is the same concept as with 3G/4G). WiMAX stands for Worldwide Interoperability for Microwave Access. WiMAX is intended to be a replacement for DSL. Broadband refers to the wide bandwidth and transportation of numerous signals.
RF switches are used in many Wifi and Bluetooth cards (RF switch subsystem support). The “RF” stands for Radio Frequency. RF switches route high-frequency signals.
Input support for RF switches also exists in the kernel (RF switch input support).
The kernel can control and query radio transmitters (Generic rfkill regulator driver). Enabling this will make a device file (/dev/rfkill). This device file acts as an interface to such radio devices.
The Linux kernel supports the 9P2000 protocol (Plan 9 Resource Sharing Support (9P2000)). This network protocol is sometimes called Styx. Plan 9's windowing system (Rio) uses Styx the same way Linux's X11 uses Unix Network Sockets. Linux systems may use Styx on Styx networks. Plan 9 and Linux can use Styx on a network.
The "9P Virtio Transport" system provides transports to and from guest and host partitions on virtual systems.
RDMA transport is also supported by the kernel (9P RDMA Transport (Experimental)). RDMA stands for Remote Direct Memory Access. This is Plan 9's protocol for accessing memory from a remote computer.
The 9P system has debugging support like many of the other kernel components (Debug information).
"CAIF support" support can also be enabled in the kernel. CAIF stands for Communication CPU to Application CPU Interface. This is a MUX protocol that uses packets and is used with ST-Ericsson's modems. ST-Ericsson is the company that developed this protocol. Android and MeeGo phones use this protocol. (Yes, MeeGo and Android are Linux systems, and yes, I am talking about the popular Android by Google.) A MUX protocol is a multiplexing protocol. Multiplexing was mentioned in a previous article.
Next, cephlib can be added to the kernel which is used in the rados block devices (rbd) and the Ceph filesystem (Ceph core library). cephlib is the complete core library for Ceph. Ceph is a storage platform. CephFS (the Ceph filesystem) is a filesystem that runs on top of another. Usually, CephFS runs on top of EXT2, ZFS, XFS, or BTRFS. Rados devices are block storage units that use CephFS.
This debugging feature for ceph harms the kernels performance, so only use it if needed (Include file:line in ceph debug output).
The CONFIG_DNS_RESOLVER facility will perform DNS lookups when this feature is enabled (Use in-kernel support for DNS lookup).
Near Field Communication (NFC) devices are also supported by the Linux kernel (NFC subsystem support).
The NFC Controller Interface (NCI) should be enabled if the above feature is enabled (NCI protocol support). This allows the host and the NFC controller to communicate.
NFC devices that process HCI frames will need this next feature to be enabled (NFC HCI implementation).
Some HCI drivers need a SHDLC link layer (SHDLC link layer for HCI based NFC drivers). SHDLC is a protocol that checks integrity and manages the order of the HCI frames.
"NFC LLCP support" is usually enabled if NFC features (like the above) are enabled.
Next, there are some drivers for specific NFC devices. The first one is a "NXP PN533 USB driver".
The next NFC driver supports Texas Instrument's BT/FM/GPS/NFC devices (Texas Instruments NFC WiLink driver).
Next is the "NXP PN544 NFC driver".
The driver for Inside Secure microread NFC chips is also provided by the kernel (Inside Secure microread NFC driver).
Now, we will be moving on to various drivers that are not network related. First, we can allow a path to the uevent helper (path to uevent helper). Many computers today should not have this feature because one uevent helper is executed for every one fork a process possess. This can quickly consume resources.
On boot-up, the kernel will make a tmpfs/ramfs filesystem (Maintain a devtmpfs filesystem to mount at /dev). This offers the complete /dev/ directory system. Of the two filesystems (tmpfs and ramfs), ramfs is the most simple of the two. “tmpfs” stands for temporary filesystem and “ramfs” stands for ram filesystem.
The next setting is the code for the devtmpfs filesystem which is also mounted at /dev/ (Automount devtmpfs at /dev, after the kernel mounted the rootfs).
The following feature allows modules to be loaded into user space (Userspace firmware loading support).
To "Include in-kernel firmware blobs in kernel binary" (which will add proprietary firmware to the kernel) enable this feature.
Some binary proprietary drivers need to be used on boot-up. This feature allows such software to do so (External firmware blobs to build into the kernel binary). Some computers have boot devices that require special firmware that may only be proprietary binaries. Without this feature enabled, the system will not boot.
Enabling "Fallback user-helper invocation for firmware loading" allows user-helper (udev) to load firmware drivers as a fallback for the kernel fails to load firmware drivers. udev can load firmware that resides in a non-standard path for firmware.
The part of the kernel that manages drivers can produce debugging messages if permitted (Driver Core verbose debug messages).
Next, the devres.log file will be used if this feature is enabled (Managed device resources verbose debug messages). This is a debugging system for device resources.
This next feature makes a connection between the userspace and kernelspace via a netlink socket (Connector - unified userspace <-> kernelspace linker). This socket uses the netlink protocol. This is another example of a Linux system needing networking abilities even if the computer will never be on a physical network.
The userspace can be informed on process events via a socket (Report process events to userspace). Some reported events include ID changes, forks, and exit status. Some previously enabled kernel features may need this. It is best to follow what the configuration tool recommends.
Systems that use solid state drives will need MTD support (Memory Technology Device (MTD) support). MTD devices are solid state storage devices. Typical storage drivers are different than Solid State Drives (SSD). The standard routines used on magnetic storage units do not work on SSDs (read, write, and erase).
Most desktop computers have parallel ports (a connector with 25 holes), so they need this feature (Parallel port support). Parallel ports are used for printers and ZIP drives among many other less known uses. Parallel ports are the ports with twenty-five pins.
Enable this feature for IBM compatible computers (PC-style hardware). There are different types of computers. Besides IBM computers (which commonly run Windows), there are Apple computers. Linux runs on nearly every type of computer.
Linux also supports multi-IO PCI cards (Multi-IO cards (parallel and serial)). Multi-IO PCI cards have both parallel and serial ports. Serial ports send or receive one bit at a time.
This next feature allows the kernel to "Use FIFO/DMA if available". This is used on certain parallel port cards to speed up printing. FIFO stands for “First In, First Out”. DMA is Direct Memory Access as mentioned before.
The next feature is for probing Super-IO cards (SuperIO chipset support). These probes find the IRQ numbers, DMA channels, and other types of addresses/numbers of such devices. Super-IO is a type of integrated IO controller.
PCMCIA support for parallel ports can be enabled (Support for PCMCIA management for PC-style ports).
NOTE: For many of these features, it may be best to do what the configuration tool recommends unless you have a specific reason for not doing so. Usually, if you are cross-compiling or making a kernel for a broad range of computers, then you should be familiar with what you are wanting to support and make the choices accordingly.
Parallel ports on AX88796 network controllers need this support (AX88796 Parallel Port).
"IEEE 1284 transfer modes" allows Enhanced Parallel Port (EPP) and Enhanced Capability Port (ECP) on parallel ports and status readback for printers. Status readback is the retrieval of the printer's status.
"Plug and Play support" (PnP) should be enabled. This allows users to plugin devices while the system is still on and then immediately utilize them. Without this feature, users could not plugin a USB device, printer, or some other device without performing any special tasks. The system will manage the rest automatically.
Next, users can enable block devices (Block devices). This is a feature that should be enabled because block devices are very common.
Floppy disks are block devices that can be enabled (Normal floppy disk support).
IDE devices that connect to parallel ports are also supported (Parallel port IDE device support). Some external CD-ROM devices can connect via parallel ports.
External IDE storage units can also be connected to parallel ports (Parallel port IDE disks).
ATA Packet Interface (ATAPI) CD-ROM drives that connect to parallel ports will need this driver (Parallel port ATAPI CD-ROMs). ATAPI is an extension of the ATA protocol used in Parallel ATA (PATA) devices.
Other ATAPI disk devices can be plugged into the parallel ports (Parallel port ATAPI disks). This driver will support other disk types besides CD-ROMs.
The kernel also supports ATAPI tape devices that connect via the parallel ports (Parallel port ATAPI tapes).
There are many other ATAPI devices that can connect to the parallel ports. As a result, a generic driver was made to manage the other devices not supported by the previously mentioned drivers (Parallel port generic ATAPI devices).
IDE devices attached to the parallel ports need a special protocol for communication purposes. There are many such protocols, one of them being the "ATEN EH-100 protocol".
An alternate protocol for parallel IDE devices is the "MicroSolutions backpack (Series 5) protocol".
There is yet again another parallel IDE device protocol (DataStor Commuter protocol) and another (DataStor EP-2000 protocol) and another (FIT TD-2000 protocol).
Once again, there is another protocol, but this one is highly recommended for the newer CD-ROM and PD/CD devices that plug into parallel ports (FIT TD-3000 protocol).
This next protocol is mainly for parallel port devices made by SyQuest, Avatar, Imation, and HP (Shuttle EPAT/EPEZ protocol).
Imation SuperDisks need support for the Shuttle EP1284 chip (Support c7/c8 chips).
Some other parallel IDE protocols that can be enabled next include
Shuttle EPIA protocol
Freecom IQ ASIC-2 protocol - used by Maxell Superdisks
FreeCom power protocol
KingByte KBIC-951A/971A protocols
KT PHd protocol - used in by 2.5 inch external parallel port hard-drives.
OnSpec 90c20 protocol
OnSpec 90c26 protocol
NOTE: These protocols and support for plugging devices into the parallel port is meant to be like hotplugging devices just like USB devices are put in USB ports. USB and Firewire are still the most popular ports to use because of their size and speed. A parallel storage unit is larger than a USB flash drive because parallel ports are larger than USB ports.
Next, we have a driver for Micron PCIe Solid State Drives (Block Device Driver for Micron PCIe SSDs).
You may have guessed it – in the next article there is still more to configure.
--------------------------------------------------------------------------------
via: http://www.linux.org/threads/the-linux-kernel-configuring-the-kernel-part-10.4613/
译者：[译者ID](https://github.com/译者ID) 校对：[校对者ID](https://github.com/校对者ID)
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创翻译，[Linux中国](http://linux.cn/) 荣誉推出

2
sources/The Linux Kernel/15 The Linux Kernel--Configuring the Kernel Part 11.md
View File

@ -1,3 +1,5 @@
Translating-------------geekpi
15 The Linux Kernel: Configuring the Kernel Part 11
================================================================================
![](http://www.linux.org/attachments/slide-jpg.530/)

122
sources/The Linux Kernel/19 The Linux Kernel--Configuring the Kernel Part 15.md Normal file
View File

@ -0,0 +1,122 @@
19 The Linux Kernel: Configuring the Kernel Part 15
================================================================================
![](http://www.linux.org/attachments/slide-jpg.578/)
Aloha! In this article of the Linux kernel series, we are still configuring drivers for USB networking. Then, we will move on to input devices.
First, we can enable/disable the "Multi-purpose USB Networking Framework" which allows connecting laptops to desktop systems.
Next, the ASIX USB-to-Ethernet adapter driver can be enabled/disabled (ASIX AX88xxx Based USB 2.0 Ethernet Adapters).
Then, there is another ASIX adaptor driver (ASIX AX88179/178A USB 3.0/2.0 to Gigabit Ethernet).
NOTE: Generally, it is best to add adapter drivers as modules.
The Communication Device Class specification is offered in the driver (CDC Ethernet support (smart devices such as cable modems)). This specification is for USB modems. The Linux system recognizes this USB networking interface as an Ethernet interface and will be designated as "ethX" where "X" is the Ethernet device number.
Next is a specification similar to the above (CDC EEM support). CDC EEM stands for Communication Device Class Ethernet Emulation Model.
The CDC Network Control Model (NCM) also has a driver that offers the specification (CDC NCM support).
The driver providing the CDC MBIM (Mobile Broadband Interface Model) specification is also available for the Linux kernel (CDC MBIM support).
Next, there are several vendor/device specific drivers for various USB networking devices and chipsets.
After those, there is a generic driver for USB network devices that do not require any special drivers (Simple USB Network Links (CDC Ethernet subset)).
Again, there are some more drivers for device/vendor specific devices.
FUN FACT: Linux was used to make the special effects for the movie "Titanic" by James Cameron.
"CDC Phonet support" is for USB Nokia modems that use Phonet.
Now, we can move on to Wireless LAN drivers which use the 802.11 specification.
Mainly, there is a list of vendor/device specific drivers.
"SoftLED Support" controls the LEDs that are associated with the Wifi cards/devices.
Some chipsets support SDIO as seen by this driver (Atheros ath6kl SDIO support). SDIO is an extension of the Secure Digital specification for wireless SD cards. SDIO stands for Secure Digital Input/Output.
Kernel developers may also notice that some wireless devices can support QoS. QoS stands for Quality of Service. This feature gives network transmissions priority. Assume two sets of data need to be sent over a network. Only one can go first. QoS will send the most important data first.
FUN FACT: Technically, Linux is not an operating system. Linux is the kernel while GNU/Linux is the operating system.
The "Generic HDLC layer" is needed for WAN cards. HDLC stands for High-Level Data Link Control. This is a data link layer protocol.
Raw HDLC can be used with the "Raw HDLC support" driver enabled.
The "Raw HDLC Ethernet device support" driver allows the HDLC layer to emulate Ethernet.
The cHDLC driver offers a HDLC extension also called Cisco HDLC (Cisco HDLC support).
The Linux kernel also has a driver for "Frame Relay support" for HDLC. Frame Relay is a Layer 2 protocol.
HDLC can also support PPP (Synchronous Point-to-Point Protocol (PPP) support) and X.25 (X.25 protocol support).
Next, this driver offers Frame Relay the ability to use DLCI (Frame Relay DLCI support).
The "LAPB over Ethernet driver" creates a device file that permits the user to make a LAPB point-to-point connection to another computer via Ethernet. The device file is usually /dev/lapb0 for the first of such device.
X.25 frames can be sent over telephone lines with this driver (X.25 async driver). Specifically, this driver allows X.25 to use asynchronous serial lines.
A special driver is needed for ISA SBNI12-xx cards (Granch SBNI12 Leased Line adapter support). These cards are inexpensive substitutes for leased line modems.
The next driver allows parallel connections to carry scheduled traffic (Multiple line feature support). This allows the Linux system to more efficiently manage parallel connection on SBNI12 adapters. Some Linux users claim this driver doubles their speed. However, I have never tested this to know for myself.
Next, "IEEE 802.15.4 drivers" can be configured. This is for slow WAN devices. This is a standard that controls the media and physical layers of the wireless network. This specification uses different frequencies in different continents. For example, in Europe, such wireless devices will use the 868.0-868.6MHz frequency.
The first setting in this category is for a fake LR-WPAN driver (Fake LR-WPAN driver with several interconnected devices). LR-WPAN stand for Low-Rate Wireless Personal Area Network.
FUN FACT: Only about 2% of the current kernel was written by Linus Torvalds.
The vmxnet3 virtual Ethernet used by VMware requires this driver (VMware VMXNET3 ethernet driver). When making a kernel for a large number of users, it is best to enable this as a module because someone may want to use the Ethernet on VMware.
The Hyper-V virtual network needs this driver (Microsoft Hyper-V virtual network driver). You may be wondering if this is the same Hyper-V virtual network by Microsoft. It is and yes, Linux supports Hyper-V.
The digital telephone service, ISDN, is supported by this driver (ISDN support). ISDN stands for Integrated Services Digital Network. In France, ISDN is known as RNIS which stands for Réseau numérique à intégration de services. With an ISDN adapter, a computer can start and accept voice calls. This allows computers to be used as answering machines or some other telephone service device. ISDN can also carry video information.
Now, we can move on to input devices (Input device support). These are devices that give the computer information. Mice and keyboards are the most commonly used and known input devices. Scanners are another example of input devices.
First, there is a driver that supports various haptic/tactile feed-back devices (Support for memoryless force-feedback devices). For instance, many game controllers vibrate which is haptic/tactile feed-back.
Some input devices check on the status of the hardware (Polled input device skeleton). Such behavior requires this driver.
Input devices that use sparse keymaps need this driver (Sparse keymap support library). A keymap is the layout information for keyboards.
Next, this is another keymap (Matrix keymap support library).
NOTE: When making a kernel for a broad user group, include most or all input devices as modules because the developer usually does not know what type of devices the users may plugin to the computer.
FUN FACT: A Vanilla Kernel is a Linux kernel in its original, unchanged state.
The "Mouse interface" makes two different device files for the mouse. The two device files are /dev/input/mouseX and /dev/input/mice.
This next driver makes a psaux device file that is an alias to /dev/input/mice (Provide legacy /dev/psaux device). The psaux device file is /dev/psaux.
If the system has a digitizer, then the horizontal resolution needs to be set (Horizontal screen resolution) and then the vertical resolution (Vertical screen resolution). A digitizer is the type of touch-screen that supports touch-pens that allow users to draw. Other touch-screens cannot support such complex input.
The next driver supports joysticks and gamepads (Joystick interface). This driver creates the /dev/input/jsX files.
The "Event interface" driver allows input devices to be accessible via /dev/input/eventX.
The "Event debugging" driver outputs all input events to the system's log. Do not enable this for any reason other than debugging systems. Obviously, for performance reasons, but the main reason I recommend this be disabled is for security purposes. All key-presses are plainly logged including passwords.
Next, a list of various keyboard drivers are listed for configuration (Keyboards) followed by mouse drivers (Mice) and then joystick/gamepad drivers (Joysticks/Gamepads).
After that, various drivers for specific tablet hardware/vendors are listed (Tablets). After that is the driver list for "Touchscreens".
The last set of input device drivers is a list of miscellaneous drivers for specific hardware and vendors (Miscellaneous devices).
The next article of this series will discuss input ports. Do not forget to read the other articles of this series and this website. Mahalo!
**NOTE TO FANS: Thank you** for all of your kind emails telling me how much you all love these articles.
--------------------------------------------------------------------------------
via: http://www.linux.org/threads/the-linux-kernel-configuring-the-kernel-part-15.4793/
译者：[译者ID](https://github.com/译者ID) 校对：[校对者ID](https://github.com/校对者ID)
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创翻译，[Linux中国](http://linux.cn/) 荣誉推出

118
sources/The Linux Kernel/20 The Linux Kernel--Configuring the Kernel Part 16.md Normal file
View File

@ -0,0 +1,118 @@
20 The Linux Kernel: Configuring the Kernel Part 16
================================================================================
![](http://www.linux.org/attachments/slide-jpg.587/)
Welcome to the next Linux kernel article. In this article, we will discuss the input/output ports.
First, the "i8042 PC Keyboard controller" driver is needed for PS/2 mice and AT keyboards. Before USB, mice and keyboards used PS/2 ports which are circular ports. The AT keyboard is an 84-key IBM keyboard that uses the AT port. The AT port has five pins while the PS/2 port has six pins.
Input devices that use the COM port (sometime called RS232 serial port) will need this diver (Serial port line discipline). The COM port is a serial port meaning that one bit at a time is transferred.
The TravelMate notebooks need this special driver to use a mouse attached to the QuickPort (ct82c710 Aux port controller).
Parallel port adapters for PS/2 mice, AT keyboards, and XT keyboards use this driver (Parallel port keyboard adapter).
The "PS/2 driver library" is for PS/2 mice and AT keyboards.
"Raw access to serio ports" can be enabled to allow device files to be used as character devices.
Next, there is a driver for the "Altera UP PS/2 controller".
The PS/2 multiplexer also needs a driver (TQC PS/2 multiplexer).
The ARC FPGA platform needs special driver for PS/2 controllers (ARC PS/2 support).
NOTE: I want to make it clear that the PS/2 controllers that are discussed in this article are not Sony's game controllers for their PlayStation. This article is discussing the 6-pin mouse/keyboard ports. The controller is the card that holds the PS/2 ports.
The "Gameport support" driver offers support for the 15-pin gameport. Gameport was the 15-pin port used by many input gaming devices until the invention of the USB port.
The next driver is for gameports on ISA and PnP bus cards (Classic ISA and PnP gameport support). ISA stands for Industry Standard Architecture and was a parallel bus standard before PCI. PnP stands for Plug-and-Play and was a common standard before ISA.
"PDPI Lightning 4 gamecard support" provides a driver for a proprietary gamecard with gameports.
The SoundBlaster Audigy card is a proprietary gameport card (SB Live and Audigy gameport support).
The ForteMedia FM801 PCI audio controller has a gameport on the card (ForteMedia FM801 gameport support). This driver only supports the gameport.
Next, we can move on to "Character devices". Character devices transfer data character by character.
First, TTY can be enabled or disabled (Enable TTY). Removing TTY will save a lot of space, but TTY is needed for terminals and such. Unless you know what you are doing, do not disabled TTY.
NOTE TO MY FANS: If you know of a reason for disabling TTY, could you post the answer below and share with us. Mahalo!
Next, support for "Virtual terminals" can be enabled/disabled. Again, a lot of space can be saved, but virtual terminals are very important.
This next driver supports font mapping and Unicode translation (Enable character translations in console). This can be used to convert ASCII to Unicode.
Virtual terminals can be used as system consoles with this driver (Support for console on virtual terminal). A system console manages the logins and kernel messages/warnings.
Virtual terminals must channel through a console driver to interact with the physical terminal (Support for binding and unbinding console drivers). Before the virtual terminal can do so, the console driver must be loaded. When the virtual terminal is closed, the console terminal must be unloaded.
The next driver provides support for Unix98 PTY (Unix98 PTY support). This is Unix98 pseudo terminal.
FUN FACT: The Linux kernel allows a filesystem to be mount many times in many places at once.
Next, "Support multiple instances of devpts" can be supported. The devpts filesystem is for pseudo-terminal slaves.
Legacy support for PTY can also be enabled (Legacy (BSD) PTY support).
The max amount of legacy PTYs in use can be set (Maximum number of legacy PTY in use).
The next driver can be used to offer support to serial boards that the other drivers fail to support (Non-standard serial port support).
Next, there are some drivers for specific boards and cards.
The GSM MUX protocol is supported with this driver (GSM MUX line discipline support (EXPERIMENTAL)).
The next driver enables the kmem device file (/dev/kmem virtual device support). kmem is usually used for kernel debugging. kmem can be used to read certain kernel variables and states.
The Stallion cards have many serial ports on them (Stallion multiport serial support). This driver specifically supports this card.
Next, we can move on to drivers for serial devices. As stated before, serial devices transfer one bit at a time.
The first driver is for standard serial port support (8250/16550 and compatible serial support).
Plug-and-Play also exists for serial ports with this driver (8250/16550 PNP device support).
The following driver allows the serial ports to be used for connecting a terminal to be used as a console (Console on 8250/16550 and compatible serial port).
Some UART controllers support Direct Memory Access (DMA support for 16550 compatible UART controllers). UART stands for Universal Asynchronous Receiver/Transmitter. UART controllers convert serial to parallel and vice versa.
Next, this driver offers support for standard PCI serial devices (8250/16550 PCI device support).
16-bit PCMCIA serial devices are supported by this driver (8250/16550 PCMCIA device support). Remember, PCMCIA is a PC-card that is usually used in laptops.
The maximum number of supported serial ports can be set (Maximum number of 8250/16550 serial ports) and then the maximum that are registered during boot-up (Number of 8250/16550 serial ports to register at runtime).
For extended serial abilities like HUB6 support, enable this driver (Extended 8250/16550 serial driver options).
A special driver is needed to support more than four legacy serial ports (Support more than 4 legacy serial ports).
Serial interrupts can be shared when this driver is used (Support for sharing serial interrupts).
Serial port IRQs can be autodetected using this driver (Autodetect IRQ on standard ports).
RSA serial ports are also supported by the Linux kernel (Support RSA serial ports). RSA stands for Remote Supervisor Adapter. RSA is an IBM-specific hardware.
Next, there are various vendor/device specific divers.
This is a TTY driver that uses printk to output user messages (TTY driver to output user messages via printk). Printk (print kernel) is a special piece of software that usually prints the boot-up messages. Any string that is displayed by printk is usually put in the /var/log/messages file. The shell command "dmesg" displays all strings that were used by printk.
Next, we can enable/disable support for parallel printers (Parallel printer support).
The next driver allows a printer to be used as a console (Support for console on line printer). This means kernel messages will be literally printed at the printer. Normally when the word "print" was used in this article series, it meant putting data on the screen. This time, this literally means putting the data on paper.
The following driver makes the device files at /dev/parport/ (Support for user-space parallel port device drivers). This allows some processes to access.
Again, the Linux kernel has many features and drivers, so we will discuss more drivers in the next article. Mahalo!
NOTE TO FANS: We are getting close to the end of the configuration process. I still have a list of all of the suggested Linux kernel topics that many of you wanted to know about. Some of the topics include installing the kernel, managing modules, adding 3rd-party drivers, and all of the other very interesting suggestions and requests.
--------------------------------------------------------------------------------
via: http://www.linux.org/threads/the-linux-kernel-configuring-the-kernel-part-16.4835/
译者：[译者ID](https://github.com/译者ID) 校对：[校对者ID](https://github.com/校对者ID)
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创翻译，[Linux中国](http://linux.cn/) 荣誉推出

292
translated/Raspberry Pi--the Perfect Home Server.md
View File

@ -1,292 +0,0 @@
树莓派（Raspberry Pi）：完美的家用服务器
---
自从树莓派发布公告，所有在互联网上的网站为此激动人心的设备提供了很多有趣和具有挑战性的使用方法。虽然这些想法都很棒，树莓派( **RPi** )最明显却又是最不吸引人的用处是：创建你的完美家用服务器。
如果你有几个不同的电脑需要同步和自动化备份，RPI可以做到。如果你想通过家中的任意屏幕来访问你的音乐和视频，RPi也能实现。也有你有一个或两个打印机，你想要简单与大家共享，树莓派在硬件和时间上用最小投资就能满足你的这些需求。
**树莓派的好处**
低成本：35美元（约合242元RMB），RPi模型B接近一台完整的电脑，512M内存，100Mb以太网，SD卡插槽，2个USB接口，音频输出和HDMI或RCA视频输出。我见过的HDMI电缆花费高于树莓派。
能源效率：硬件成本只是服务器费用的一部分，因为你需要考虑能源成本去不断运行设备。家用服务器所需要的服务不会占用太多CPU，大部分时间它都处于空闲状态，等待发挥功效。RPi's超低功率组件非常适合这个工作负载，这有助于降低你的电费消耗。我的模型B单个加上外部硬盘消耗总共只有8瓦，然而用老式速龙代替的机器在闲置时消耗54瓦。假设10美分每千瓦一小时，这使得一个RPi每年的电费在7美元。一个基于速龙的机器是47美元。在不到一年的时间里，RPI基本上能够收回成本。
低噪音：因为RPi没有风扇和移动部件，在你最终配置中的唯一组件上生成噪音或任何明显热量的将在硬盘上。如果你担心噪音，像[Silent PC Review][1]发烧友网站经常在他们的评论中涉及到噪声基准。我的体会是现代驱动器足够安静，能够避免检测任何地方有其它程序在运行（如媒体中心，游戏控制台或其他电脑）。如果你家里没有为布线提供更多的灵活性选择，RPi's的小尺寸、最小热输出和低噪音排放量也许让它偷偷地“藏”在服务器中，这在过去是很难查出的。
![](https://github-camo.global.ssl.fastly.net/37922c152a6abd82b42ca0a965a311e8914fbb16/687474703a2f2f7777772e6c696e75786a6f75726e616c2e636f6d2f66696c65732f6c696e75786a6f75726e616c2e636f6d2f7566696c65732f696d61676563616368652f6c617267652d35353070782d63656e74657265642f75313030323036312f313134353466312e6a7067)
图1,一个简洁高效的家用服务器
新机会：一个不怎么实际的好处是-简单快乐的尝试新事物！对我来说，这是我第一次真正工作在基于Debian的发行版，很可能也是许多Linux爱好者们第一次有机会尝试一个基于ARM的体系结构。
**布置硬件**
对于一个家庭服务器来说，你将需要一个中等大小的SD闪存卡作为本地存储。它可以使用一个USB引导，但那会占用两个宝贵的USB插槽之一。闪存卡不需要很大，但是速度越快越好。我选择了一个名牌SD卡，8GB容量和10级速度等级。对于备份和存储多媒体文件，一个有USB连接插槽的硬盘驱动器是必须的。我选择一个1.5TB的硬盘和一个Calvary EN-CAHDD-D 2-bay USB 2.0硬盘连接插槽。这个连接插槽有个功能，在RAID-0模式中运行两个驱动器，总有一天会有用。最后，RPi不带电源线，但大多数智能手机充电器电源线所需的5v以上微型USB。看看RPi是否挑剔电源，我为电源已换了三个不同的微型USB手机充电器。我在这周内尝试了每一个，在任何一个上都没有问题。
**安装操作系统**
安装RPi操作系统包括了各个地方的大量细节，但这里有一些家用特定服务器的安装提示，大致按需要的顺序。
1）直接通过[http://www.raspberrypi.org/downloads][2]获取Raspbian "Wheezy"安装镜像，并复制到SD卡，用网站上已列出的步骤。
2）第一次引导RPi时，附加一个键盘，鼠标和显示器。在引导RPi之前别忘打开显示器，可以检测更正HDMI或合并输出端口。
3）RPi有一个很好的"raspi-config"屏幕，在第一次启动时你会看到。对于家庭服务器来说，以下选择将会有用：
- expand_rootfs：调整默认2GB OS镜像来填充闪存卡剩余的内存。
- change_pass：默认密码是"raspberry"，但是，越安全的密码越好。
- 设置你的地点和时区。
- memory_split：分配最小值尽可能为GPU服务留下更多空间。
- SSH：别忘开启SSH服务。
- boot_behaviour：关闭启动至桌面（再次为你的服务保存内存）。
完成后，你将在 `pi@raspberrypi` 提示符下。安装脚本可以在任何时间通过 `sudo raspi-config` 重新运行。
只是一些配置项，然后操作系统已经准备就绪。
1）一个静态IP让一切变得更容易，切换eth0的网络设置：
>>> sudo nano -w /etc/network/interfaces
更改eth0 `iface eth0 inet dhcp` 行，如下所示（更改以满足你的家庭网络设置）：
======/etc/network/interfaces======
...
iface eth0 inet static
address 192.168.1.10
netmask 255.255.255.0
gateway 192.168.1.1
...
======/etc/network/interfaces======
2）创建本地用户并加入到users组和sudo组：
>> sudo adduser YOURUSERIDHERE
>> sudo usermod -a -G users YOURUSERIDHERE
>> sudo usermod -a -G sudo YOURUSERIDHERE
3）更新系统确保所有的库是最新最好的：
>> sudo apt-get update; sudo apt-get upgrade
4）这里，准备从头开始吧！关闭PI：
>> sudo /sbin/shutdown -h now
一旦关闭（监控RPi电路板上的绿色LED状态指示灯，了解什么时候完成关闭），拔下显示器，键盘，鼠标和电源线。附加USB存储器，然后插回电源重启RPi。
5）一旦RPi开启（这些绿色LED指示灯就是状态提示线索），你可以从远程网络上从任何其他机器ssh到RPi并完成所有的配置（更改以下命令里的IP为你的静态IP）：
`>> ssh YOURUSERIDHERE@192.168.1.10`
祝贺你，有了一个工作中的树莓派！
**外围设备**
第一要务是要装入外围设备。用dmesg来寻找你的存储设备，会发现--几乎可以肯定是/dev/sda。我喜欢使用自动挂载去处理挂载远程存储设备，因为关于交换设备可能不存在或准备在启动时间更灵活：
>> sudo apt-get install autofs
>> sudo nano -w /etc/auto.master
======/etc/auto.master======
...
/misc /etc/auto.misc
...
======/etc/auto.master======
>> sudo nano -w /etc/auto.misc
注意，我的外部存储设备是ext4格式--如果需要，更改如下：
======/etc/auto.misc======
...
storage -fstype=ext4:/dev/sda1
...
======/etc/auto.misc======
>> sudo /etc/init.d/autofs restart
>> ls -lat /misc/storage
可选，创建一个符号链接至短路径：
>> ln -s /misc/storage /storage
**备份仓库**
在任何家庭服务器功能列表的顶端是提供坚如磐石的备份。RPi，这是漂亮而简单，在Linux中基于范围广泛的网络共享选项：Samba/CIFS用于Windows机器，NFS用于基于UNIX的设备并且甚至SFTP用于更多先进的备份客户端，像deja-dup。由于RPi只有100MB以太网和在USB上的存储设备，它没有非常快的传送速度。在其他方面，好的备份客户端在后台自动运行，所以它不会注意略微缓慢的传输速度。
我的家庭网络包括一台Windows7电脑。对于它，我通过Samba在RPi's外部USB存储设备上导出一个备份目录。因为备份程序在Windows7的基础版本不支持网络设备作为一个备份目标，我使用[SyncBack Free][3]去设置使其自动化，每日备份。
配置Samba是容易的。
1）安装samba和common-bin库（具有smbpasswd效用）
>> sudo apt-get install samba samba-common-bin
2）使用 `smbpasswd` 让你的本地ID能访问：
>> sudo smbpasswd -a YOURUSERIDHERE
3）编辑samba配置文件：
>> sudo nano -w /etc/samba/smb.conf
4)更改 `workgroup = WORKGROUP` 行去匹配你的Windows工作组名称。
5）注释掉或删除[homes]和[printers]共享。(打印机共享稍后将通过直接CUPS访问来完成。)
6）为Windows备份路径增加一个条目。这是我的示例，放置在该文件的底部：
======/etc/samba/smb.conf======
...
[win7pc]
comment=Backup for windows PC
path=/storage/win7pc
writeable=Yes
create mask=0777
directory mask=0777
browsable=Yes
public=Yes
valid users=YOURUSERIDHERE
...
======/etc/samba/smb.conf======
7）重启Samba使你的编辑生效：
>> sudo /etc/init.d/samba restart
8）从Windows机器文件资源管理器通过映射一个网络设备测试连通。
对Linux设备来说，设置和使用deja-dup非常简单。它被默认安装在我的Fedora 18和Ubuntu 12.10上。包的名称是“deja-dup”，前端简单的称为“Backup（备份）”。虽然RPi很容易支持NFS导出，我发现使用deja-dup的SSH选项更容易，更方便，在RPi上它消除了对额外服务的需要。指定一个deja-dup加密密码是一个好主意，除非你想让你全部的文件都丢失，一旦你的存储驱动器落入别人手中：
>> sudo mkdir /storage/linuxlaptop
>> sudo chown -R YOURUSERIDHERE:YOURUSERIDHERE /storage/linuxlaptop
从linux客户端启动备份程序，选择“SSH”作为备份位置，输入RPi's IP地址和你创建的存储位置。首次备份会很慢，但是未来运行将只发送增量变化，速度更快。
![](https://github-camo.global.ssl.fastly.net/08111990037d492b22d45de49816f5bc2b02933a/687474703a2f2f7777772e6c696e75786a6f75726e616c2e636f6d2f66696c65732f6c696e75786a6f75726e616c2e636f6d2f7566696c65732f696d61676563616368652f6d656469756d2d33353070782d63656e74657265642f75313030323036312f313134353466322e706e67)
图2,Deja-dup客户端设置
**多媒体服务器：DLNA**
现在每个人的文件都已安全备份。让我们继续看些有趣的！一个DLNA服务器将给你一个集中地去存储你的电影，音乐和图片。通过这个中心库，家中每一个屏幕的DLNA客户端都可以轻松重放此内容。
至少，这是承诺。事实是这样的，DNLA规格并不太确定一些重要的事情，如支持哪些格式或编码。每个客户端通常对于支持什么格式和服务器功能都有略微不同的想法。很多高功率服务器也许能转码本地内容到移动设备支持的格式，但是在RPi上是不可能的，在即时烧录转码上经常扰乱其他功能，如暂停，快进和倒带。一般情况下，高功率设备如PS3,Xbox和WD TV设备大多数格式无需任何转码。低端设备如智能TVs或Blu-ray播放器支持更多的编码限制列表。
对于RPi来说，最好的办法是简单的进行标准编码去支持你的初级DLNA设备，然后测试你的其他DLNA客户端。如果没有完美播放，在下一节提示中也许有帮助。在我的案例中，我的PlayStation 3充当DLNA客户端，PS3能够流畅播放经Handbrake制作后的.m4v文件。对于DLNA服务器Minidlna是个很好的选择。它已经在Raspbian发行版中，易于设置和使用最小服务资源运行：
>> sudo apt-get install minidlna
>> sudo nano -w /etc/minidlna.conf
这是我/etc/minidlna.conf文件的相关部分：
...
# I found keeping video + audio in different paths helpful
media_dir=V,/storage/dlna/video
media_dir=A,/storage/dlna/music
...
presentation_url=http://192.168.1.10:8200/
...
friendly_name=MyRPi
...
# Since I add new media infrequently, turning off
# inotify keeps minidlna for polling for
# content changes. It's simple enough to run
# sudo /etc/init.d/minidlna force-reload
# when new content is added.
inotify=no
一旦完成编辑，告诉minidlna重启并重新扫描内容：
>> sudo /etc/init.d/minidlna force-reload
Minidlna有能力为你的设备支持的电影提供电影海报缩略图（像PS3）。这让我能够更方便地在几十个电影文件中滚屏查找我想要的那个特定电影。我发现每个电影一个目录是最兼容的文件布局，只包含影片文件和缩略图，图像命名为“Cover.jpg”。使用像"MovieName.m4v"和"MovieName.jpg"的格式为PS3正常工作。但它破坏VLC（如果你能说服VLC uPNP插件首先查找服务器）。
通过PS3，你可以通过转到在XMB栏上的"Video"测试连通性。当视频向下滚动时，你以前设置的"friendly_name"应该是可见的，测试确保Minidlna是通过浏览器转到http://192.168.1.10:8200/。
**非DLNA设备的多媒体**
一旦你能够让DNLA与你的一些设备一起工作，你可能会发现有些设备并不适合它，所以多媒体计划B是个好主意。Nginx网站服务器有一个MP4插件尝试改善流传输plain-old HTTP，但是浏览器重放性能差别很大，快进在一部电影里也一贯不工作。看起来多媒体共享或非 DLNA 设备的最低共同特性是与访客共享好的传统Samba的只读访问。
这是/etc/samba/smb.conf的部分示例：
[dlna]
path=/storage/dlna
read only=yes
browsable=yes
public=yes
定义所占份额和重启Samba后（ `sudo /etc/init.d/samba restart` ），你可以开始测试你的客户端。
我测试了以下客户端与一个混合视频编码with Handbrake作为m4v文件：
- Android 4.0.4手机："ES File Explorer"与"ES Media Player"（播放器附带安装）。
- Android 4.1.2平板电脑："ES File Explorer"与"ES Media Player"（播放器附带安装）。
- Linux设备：自动挂载：//192.168.1.10/dlna，然后使用VLC或MPlayer。
- Windows：挂载//192.168.1.10:/dlna，然后使用VLC。
所有设备都能几乎立即开始播放和快进没有延迟的情况。
**打印服务器**
RPi运行CUPS相当不错，所以它易于共享一个较旧的没有本机网络功能的打印机。
安装你的打印机所需的CUPS和任何软件包。我需要hplip-cups，因为我也有HP喷墨打印机：
>> sudo apt-get install cups hplip-cups
更新“Listen”行和增加 `Allow @LOCAL` 到位置指令，如下所示（你可以使用其他机器在你的LAN上去管理CUPS）：
======/etc/cups/cupsd.conf======
#Listen localhost:631 #Comment this out
Listen 192.168.1.10:631 #Add this line
...
<Location />
Order allow,deny
Allow @LOCAL
</Location>
# Restrict access to the admin pages...
<Location /admin>
Order allow,deny
Allow @LOCAL
</Location>
# Restrict access to configuration files...
<Location /admin/conf>
AuthType Default
Require user @SYSTEM
Order allow,deny
Allow @LOCAL
</Location>
======/etc/cups/cupsd.conf======
添加你的本地ID到lpadmin组就能管理CUPS：
>> sudo usermod -a -G lpadmin YOURUSERIDHERE
重启CUPS：
>> sudo /etc/init.d/cups restart
然后转到http://192.168.1.10:631/并点击 "Adding Printers and Classes"去设置你的打印机。我的打印机是自动发现USB，所以，我只需点击“share”就可以。同样访问https://192.168.1.10:631/admin，确保检查“Share printers connected to this system（共享打印机连接至这个系统）”。
一旦你完成，你可以用通常的方式设置你的客户端。一旦我输入主机名，我的Linux客户端就能够自动发现打印机，并选择正确的打印设备。在我的Windows7的机器上，一旦我选择“Network Printer（网络打印机）”，我必须点击“The printer that I want isn't listed（我想要的打印机未列出）”，选择“Select a shared printer by name（通过名称选择共享的打印机）”，然后从CUPS网络接口输入URL：http://192.168.1.10:631/printers/HP_J4500。
**结论**
用最少的额外的硬件和配置，树莓派是高效、简洁的家用服务器。它能够花最小的硬件费用来为你的家庭环境带来由Linux提供的广泛企业服务。
--------------------------------------------------------------------------------
via: http://www.linuxjournal.com/content/raspberry-pi-perfect-home-server
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创翻译，[Linux中国](http://linux.cn/) 荣誉推出
译者：[Vito](https://github.com/vito-L) 校对：[Caroline](https://github.com/carolinewuyan)
[1]:http://www.silentpcreview.com/
[2]:http://www.raspberrypi.org/downloads
[3]:http://www.2brightsparks.com/freeware/freeware-hub.html

139
translated/The Linux Kernel/14 The Linux Kernel--Configuring the Kernel Part 10.md Normal file
View File

@ -0,0 +1,139 @@
戴文的Linux内核专题：14 配置内核 (10)
================================================================================
![](http://www.linux.org/attachments/slide-jpg.514/)
使用WiMAX协议的无线宽频设备可以启用这个(WiMAX Wireless Broadband support)。这个类型的无线连接通常需由服务供应商提供的连接服务才能工作(这与3G/4G的概念相同)。WiMAX代表"Worldwide Interoperability for Microwave Access"(微波存取全球互通)。WiMAX的目的是代替DSL。宽频指的是宽的带宽和大量信号的传输。
射频开关被用于许多Wifi和蓝牙卡中(RF switch subsystem support)。"RF"代表"Radio Frequency"。RF开关路由高频信号。
RF开关输入支持同样也在内核中支持(RF switch input support)。
内核可以控制并请求无线传输(Generic rfkill regulator driver)。启用这个生成一个设备文件(/dev/rfkill)。这个设备文件作为无线设备的接口。
Linux内核支持9P2000协议(Plan 9 Resource Sharing Support (9P2000))。这个网络协议有时称作Styx。Plan 9的窗口系统(Rio)的Styx和Linux的X11都使用Unix网络套接字。Linux系统可能使用Styx在Styx网络中。Plan 9和Linux可以在一个网络中使用Styx
"9P Virtio Transport"(9P 虚拟io传输)系统提供了在虚拟系统上客户机和主机分区间的传输。
内核同样支持RDMA传输(9P RDMA Transport (Experimental))。RDMA代表的是"Remote Direct Memory Access"(远程内存直接访问)。这个Plan9上访问远程计算机内存的协议。
9P系统与其他内核组件一样有调试特性(Debug information)。
"CAIF support"支持同样可以在内核中启用。CAIF代表" Communication CPU to Application CPU Interface"(通信CPU到应用CPU接口)。这是一个使用数据包的多路复用(MUX)协议并被用于ST-Ericsson(意法爱立信)调制解调器中。ST-Ericsson是开发这个协议的公司(是的，MeeGo和Android是Linux系统，并且我正在讨论Google的Andorid)。MUX协议就是多路复用(multiplexing)协议。多路复用在前面的文章中已经提到过。
下面，cephlib可以加入内核，它可以用于rados块设备(rbd)h和Ceph文件系统(Ceph核心库)(译注：Ceph是一种分布式文件系统)。cephlib是是Ceph的完整核心库。Ceph是存储平台。CephFs(Ceph文件系统)是运行在另外一个文件系统的顶部。通常，CephFs运行在EXT2、ZFS、XFS或者BTRFS上面。Rados设备是使用CephFs的块存储单元。
ceph的调试特性会损害内核性能，所以只在需要的时候启用(Include file:line in ceph debug output)。
当启用这个选项(Use in-kernel support for DNS lookup)，CONFIG_DNS_RESOLVER设施会执行DNS查询。
近场通信(Near Field Communication (NFC))设备在Linux内核中也被支持(NFC subsystem support)。
如果上面的特性被启用，那么NFC控制器接口(NFC Controller Interface (NCI))也应该启用(NCI protocol support)。这允许主机和NFC控制器相互通信。
NFC要处理HCI帧需要启用下面一个特性(NFC HCI implementation)。
一些HCI驱动需要一个SHDLC链路层(SHDLC link layer)(SHDLC link layer for HCI based NFC drivers)。SHDLC是检测完整性和管理HCI帧顺序的协议。
如果NFC特性启用了，那么通常也启用"NFC LLCP support"(就像上面那样)。
接下来有一些为特别的NFC设备的驱动。第一个是"NXP PN533 USB driver"。
下一个NFC驱动支持TI的BT/FM/GPS/NFC设备(Texas Instruments NFC WiLink driver)。
下面的是"NXP PN544 NFC driver"。
对于Inside Secure(译注：法国一家非接触半导体芯片厂商)生产的microread NFC芯片驱动同样在内核中支持(Inside Secure microread NFC driver)。
现在，我们将继续配置与网络无关的驱动。首先我们可以选择uevent帮助程序的路径(path to uevent helper)。如今许多计算机不在需要这个特性因为一个uevent帮助程序会在每次执行时fork一个进程处理。这回很快地消耗资源。
在启动时，内核会创建一个tmpfs/ramfs 文件系统(Maintain a devtmpfs filesystem to mount at /dev)。这个提供了完整的/dev目录系统。在这两个文件系统中(tmpfs和ramfs)，ramfs两者中最简单。"tmpfs"代表"temporary filesystem"(临时文件系统)，而"ramfs"代表"ram filesystem"(内存文件系统)。
下一个设置是devtmpfs文件系统的代码，它同样挂载在/dev下(Automount devtmpfs at /dev, after the kernel mounted the rootfs)。
下面的特性允许模块加载到用户空间(Userspace firmware loading support)。
为了"Include in-kernel firmware blobs in kernel binary"(译注：将固件编译进内核)(这会增加专有固件到内核中)，就启用这个特性。
一些二进制专有驱动需要在启动时使用。这个特性允许这类软件这么做(External firmware blobs to build into the kernel binary)。一些计算机有些引导设备需要只包含专有二进制文件的特殊固件。这个特性不启用，系统将无法引导。
启用"Fallback user-helper invocation for firmware loading"，允许user-helper(用户助手) (udev)作为内核加载固件驱动失败的后备手段加载固件。udev可以加载驻留在非标准路径的固件。
管理驱动的不跟内核如果被允许就可以生成调试信息(Driver Core verbose debug messages)。
下一步，如果启用这个特性(Managed device resources verbose debug messages)，devres.log文件就可以使用。这是一个用于设备资源的调试系统。
下面一个特性会通过netlink套接字生成一条用户空间和内核空间的连接(Connector - unified userspace <-> kernelspace linker)。这个套接字使用netlink协议。这是另外一个Linux系统即使在没有物理网络情况下仍需要网络特性的例子。
用户空间可以通过套接字得到进城时间的通知(Report process events to userspace)。一些报告事件包含了ID改变、fork、和退出状态。一些先前启用的内核特性可能需要这个。最好按配置工具建议的那样设置。
使用固态硬盘的系统需要MTD的支持(Memory Technology Device (MTD) support)。MTD设备是固态存储设备。典型的存储设备与固态硬盘(SSD)不同。用于磁盘单元的标准常规不适用于SSD(读、写、擦除)。
大多数会桌面电脑否有并口(一个有25个洞的连接器)，所以他们需要这个特性(Parallel port support)。并口在其他许多鲜为人知的应用中通常用于打印机和ZIP驱动器。并口有25针。
对IBM兼容计算机启用这个特性(PC-style hardware)。它们是不同类型的计算机。除了IBM计算机(通常运行Windows),还有苹果计算机。Linxu可以运行在几乎所有类型的计算机上。
Linux同样支持Multi-IO PCI卡(Multi-IO cards (parallel and serial))。Multi-IO PCI卡同时拥有并口和串口。串口每次发送或接收1位数据。
下一个特性允许内核"Use FIFO/DMA if available"。这用于特定的并口卡来加速打印。FIFO代表"First In, First Out"(先入先出)。DMA是先前提过的直接内存访问(Direct Memory Access)。
下面一个特性用于探测Super-IO卡(SuperIO chipset support)。这些探针会发信中断号、DMA通道和其他类型设备的地址/数量。Super-IO是一种集成IO控制器类型。
PCMCIA的并口支持可以启用(Support for PCMCIA management for PC-style ports)。
注意：对于许多特性来说，你最好按照配置工具的建议除非你有特别的理由不这么做。通常地，如果你是交叉编译或者编译一个通用内核，那么你应该熟悉你想要支持的并做出相应的选择。
在AX88796网络控制器的并口需要这个支持(AX88796 Parallel Port)。
"IEEE 1284 transfer modes"在并口上支持增强型并口(Enhanced Parallel Port (EPP))和增强功能口(Enhanced Capability Port (ECP))并支持打印机状态回读。状态回读是检索打印机的状态。
即插即用("Plug and Play support" (PnP))应该启用。这允许用户在系统开机状态下插入设备并能马上使用它们。没有这个特性，用户不能使用USB设备、打印机或者其他没有执行特殊任务的设备。系统会自动管理复位(译注：原文是 "The system will manage the rest automatically")。
下面，用户可以启用块设备(Block devices)。这是一个应该启用的特性，因为块设备很常见。
软驱也是可以启用的块设备(Normal floppy disk support)。
连接到并口的IDE设备也同样支持(Parallel port IDE device support)。一些外部CD-ROM设备也能通过并口连接。
外部IDE存储设备单元同样可以连接到并口(Parallel port IDE disks)。
连接到并口的ATA包接口(ATA Packet Interface (ATAPI)) CD-ROM需要这个驱动(Parallel port ATAPI CD-ROMs)。ATAPI是用于并行ATA(PATA)设备的ATA协议扩展。
还有一个ATAPI磁盘设备可以插到并口中(Parallel port ATAPI disks)。这个驱动会除了支持CD-ROM外还支持其他类型的磁盘。
内核同样支持通过并口连接ATAPI磁带设备(Parallel port ATAPI tapes)。
还有许多其他的ATAPI设备可以连接到并口中。结果就是，一个通用驱动被用于管理前面提到过的驱动不支持的设备(Parallel port generic ATAPI devices)。
连接到并口上的IDE设备需要一个特殊的协议用于通信。有很多这样的协议，其中一个是"ATEN EH-100 protocol"。
一个可选的用于并行IDE设备的协议是"MicroSolutions backpack (Series 5) protocol"。
这里仍有另外一个并口IDE设备协议(DataStor Commuter protocol)和另一个(DataStor EP-2000 protocol)还有(FIT TD-2000 protocol)。
再提一次，这里有另外一个协议，但是这个强烈建议用在更新的插在并口上的CD-ROM和PD/CD设备(FIT TD-3000 protocol)。
下面的协议主要用于SyQuest、Avatar、Imation和HP生产的并口设备(Shuttle EPAT/EPEZ protocol)。
Imation SuperDisks需要Shuttle EP1284芯片的支持(Support c7/c8 chips)。
一些其他的并行IDE协议可以启用，包括：
Shuttle EPIA protocol
Freecom IQ ASIC-2 protocol - (用于Maxell Superdisks)
FreeCom power protocol
KingByte KBIC-951A/971A protocols
KT PHd protocol - (用于2.5英寸外置并口硬盘)
OnSpec 90c20 protocol
OnSpec 90c26 protocol
注意：这些协议以及支持的插入并口的设备意味着这些都类似于热插拔设备,就像USB设备插入USB端口一样。USB和火线人仍旧是使用最流行的端口,因为它们的大小和速度。一个并口设备单元大于USB闪存因为并口大于USB端口。
下一步,我们有一个对于Micron PCIe的SSD驱动(Block Device Driver for Micron PCIe SSDs)。
你可能已经猜到了- 下面的文章会讨论更多的配置.
--------------------------------------------------------------------------------
via: http://www.linux.org/threads/the-linux-kernel-configuring-the-kernel-part-10.4613/
译者：[geekpi](https://github.com/geekpi) 校对：[校对者ID](https://github.com/校对者ID)
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创翻译，[Linux中国](http://linux.cn/) 荣誉推出

54
translated/Upgrade To Linux Kernel 3.11.6 In Ubuntu.md
View File

@ -1,54 +0,0 @@
Ubuntu 升级到Linux内核3.11.6
================================================================================
昨天已经发布了Ubuntu 13.10但是你可能仍然运行着Linux 3.11.0 内核.当然坚持Ubuntu 13.10 当前内核不是一件坏事.事实上,不建议升级超出你的Linux发行版的官方仓库测试的特定版本.
另一方面,如果你不害怕折腾再折腾Ubuntu那么你应该升级到最新Ubuntu支持的 Linux 内核.你会发觉,最新的内核总是有改善,漏洞修补和添加特性的.
所以,如果你的电脑有些运行不正常,那么更新Linux内核可能会被修复.但记住,当你升级时你也有可能导致崩溃.
如果你不再惧怕,和我一起永往直前吧,让我们开始升级Ubuntu Linux 内核到 3.11.6!!
首先,在你开始升级之前,请先备份你的数据,以防升级时出错无法恢复.小心不出大错!!!
更多关于这个内核版本信息,[阅读更改日志][1]
当你一切就绪,运行下列命令来升级你的机器并删除旧包,包括旧内核.
sudo apt-get update && sudo apt-get dist-upgrade && sudo apt-get autoremove
另外,进到/tmp目录.
cd /tmp
接着,复制粘贴下列命令,按回车下载32位的Linux内核
wget http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.11.6-saucy/linux-headers-3.11.6-031106-generic_3.11.6-031106.201310181453_i386.deb http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.11.6-saucy/linux-headers-3.11.6-031106_3.11.6-031106.201310181453_all.deb http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.11.6-saucy/linux-image-3.11.6-031106-generic_3.11.6-031106.201310181453_i386.deb
下载64位Linux 内核版本,复制粘贴下行.
wget http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.11.6-saucy/linux-headers-3.11.6-031106-generic_3.11.6-031106.201310181453_amd64.deb http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.11.6-saucy/linux-headers-3.11.6-031106_3.11.6-031106.201310181453_all.deb http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.11.6-saucy/linux-image-3.11.6-031106-generic_3.11.6-031106.201310181453_amd64.deb
下载适合的版本,运行下列命令,开始安装.
sudo dpkg -i *.deb
最后,运行下列命令升级Grub.
sudo update-grub2
就这样!重启你的电脑,完成升级!!
玩的开心!
--------------------------------------------------------------------------------
via: http://www.liberiangeek.net/2013/10/upgrade-linux-kernel-3-11-6-ubuntu/
译者：[Luoxcat](https://github.com/Luoxcat) 校对：[校对者ID](https://github.com/校对者ID)
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创翻译，[Linux中国](http://linux.cn/) 荣誉推出
[1]:https://www.kernel.org/pub/linux/kernel/v3.x/ChangeLog-3.11.6