mirror of
https://github.com/LCTT/TranslateProject.git
synced 2025-03-21 02:10:11 +08:00
joeren
commit
18ac63aa1f
178
published/20140924 Unix----stat -- more than ls.md
Normal file
178
published/20140924 Unix----stat -- more than ls.md
Normal file
@ -0,0 +1,178 @@
|
||||
stat -- 获取比 ls 更多的信息
|
||||
================================================================================
|
||||
> 厌倦了 ls 命令，并且想查看更多有关你的文件的有趣的信息？ 试一试 stat！
|
||||
|
||||
|
||||
|
||||
ls 命令可能是每一个 Unix 使用者第一个学习的命令之一， 但它仅仅显示了 stat 命令能给出的信息的一小部分。
|
||||
|
||||
stat 命令从文件的索引节点获取信息。 正如你可能已经了解的那样， 每一个系统里的文件都存有三组日期和时间， 它们包括最近修改时间（即使用 ls -l 命令时显示的日期和时间）, 最近状态改变时间（包括对文件重命名）和最近访问时间。
|
||||
|
||||
使用长列表模式查看文件信息， 你会看到类似下面的内容：
|
||||
|
||||
$ ls -l trythis
|
||||
-rwx------ 1 shs unixdweebs 109 Nov 11 2013 trythis
|
||||
|
||||
使用 stat 命令， 你会看到下面这些：
|
||||
|
||||
$ stat trythis
|
||||
File: `trythis'
|
||||
Size: 109 Blocks: 8 IO Block: 262144 regular file
|
||||
Device: 18h/24d Inode: 12731691 Links: 1
|
||||
Access: (0700/-rwx------) Uid: ( 263/ shs) Gid: ( 100/ unixdweebs)
|
||||
Access: 2014-09-09 19:27:58.000000000 -0400
|
||||
Modify: 2013-11-11 08:40:10.000000000 -0500
|
||||
Change: 2013-11-11 08:40:10.000000000 -0500
|
||||
|
||||
在上面的情形中， 文件的状态改变和文件修改的日期/时间是相同的， 而访问时间则是相当近的时间。 我们还可以看到文件使用了 8 个块， 以及两种格式显示的文件权限 -- 八进制（0700）格式和 rwx 格式。 在第三行显示的索引节点是 12731681. 文件没有其它的硬链接（Links: 1）。 而且， 这个文件是一个常规文件。
|
||||
|
||||
把文件重命名， 你会看到状态改变时间发生变化。
|
||||
|
||||
这里的 ctime 信息， 最早设计用来存储文件的创建（create）日期和时间， 但后来不知道什么时候变为用来存储状态修改（change）时间。
|
||||
|
||||
$ mv trythis trythat
|
||||
$ stat trythat
|
||||
File: `trythat'
|
||||
Size: 109 Blocks: 8 IO Block: 262144 regular file
|
||||
Device: 18h/24d Inode: 12731691 Links: 1
|
||||
Access: (0700/-rwx------) Uid: ( 263/ shs) Gid: ( 100/ unixdweebs)
|
||||
Access: 2014-09-09 19:27:58.000000000 -0400
|
||||
Modify: 2013-11-11 08:40:10.000000000 -0500
|
||||
Change: 2014-09-21 12:46:22.000000000 -0400
|
||||
|
||||
改变文件的权限也会改变 ctime 域。
|
||||
|
||||
你也可以配合通配符来使用 stat 命令以列出一组文件的状态：
|
||||
|
||||
$ stat myfile*
|
||||
File: `myfile'
|
||||
Size: 20 Blocks: 8 IO Block: 262144 regular file
|
||||
Device: 18h/24d Inode: 12731803 Links: 1
|
||||
Access: (0640/-rw-r-----) Uid: ( 263/ shs) Gid: ( 100/ unixdweebs)
|
||||
Access: 2014-08-23 03:00:36.000000000 -0400
|
||||
Modify: 2014-08-22 12:02:12.000000000 -0400
|
||||
Change: 2014-08-22 12:02:12.000000000 -0400
|
||||
File: `myfile2'
|
||||
Size: 20 Blocks: 8 IO Block: 262144 regular file
|
||||
Device: 18h/24d Inode: 12731806 Links: 1
|
||||
Access: (0640/-rw-r-----) Uid: ( 263/ shs) Gid: ( 100/ unixdweebs)
|
||||
Access: 2014-08-23 03:00:36.000000000 -0400
|
||||
Modify: 2014-08-22 12:03:30.000000000 -0400
|
||||
Change: 2014-08-22 12:03:30.000000000 -0400
|
||||
File: `myfile3'
|
||||
Size: 40 Blocks: 8 IO Block: 262144 regular file
|
||||
Device: 18h/24d Inode: 12730533 Links: 1
|
||||
Access: (0640/-rw-r-----) Uid: ( 263/ shs) Gid: ( 100/ unixdweebs)
|
||||
Access: 2014-08-23 03:00:36.000000000 -0400
|
||||
Modify: 2014-08-22 12:03:59.000000000 -0400
|
||||
Change: 2014-08-22 12:03:59.000000000 -0400
|
||||
|
||||
如果我们喜欢的话， 我们也可以通过其他命令来获取这些信息。
|
||||
|
||||
向 ls -l 命令添加 "u" 选项， 你会看到下面的结果。 注意这个选项会显示最后访问时间， 而添加 "c" 选项则会显示状态改变时间（在本例中， 是我们重命名文件的时间）。
|
||||
|
||||
$ ls -lu trythat
|
||||
-rwx------ 1 shs unixdweebs 109 Sep 9 19:27 trythat
|
||||
$ ls -lc trythat
|
||||
-rwx------ 1 shs unixdweebs 109 Sep 21 12:46 trythat
|
||||
|
||||
stat 命令也可应用与文件夹。
|
||||
|
||||
在这个例子中， 我们可以看到有许多的链接。
|
||||
|
||||
$ stat bin
|
||||
File: `bin'
|
||||
Size: 12288 Blocks: 24 IO Block: 262144 directory
|
||||
Device: 18h/24d Inode: 15089714 Links: 9
|
||||
Access: (0700/drwx------) Uid: ( 263/ shs) Gid: ( 100/ unixdweebs)
|
||||
Access: 2014-09-21 03:00:45.000000000 -0400
|
||||
Modify: 2014-09-15 17:54:41.000000000 -0400
|
||||
Change: 2014-09-15 17:54:41.000000000 -0400
|
||||
|
||||
在这里， 我们还可以查看一个文件系统。
|
||||
|
||||
$ stat -f /dev/cciss/c0d0p2
|
||||
File: "/dev/cciss/c0d0p2"
|
||||
ID: 0 Namelen: 255 Type: tmpfs
|
||||
Block size: 4096Fundamental block size: 4096
|
||||
Blocks: Total: 259366 Free: 259337 Available: 259337
|
||||
Inodes: Total: 223834 Free: 223531
|
||||
|
||||
注意 Namelen （文件名长度）域， 如果文件名长于 255 个字符的话， 你会很幸运地在文件名处看到心形符号！
|
||||
|
||||
stat 命令还可以一次显示所有我们想要的信息。 下面的例子中， 我们只想查看文件类型， 然后是硬连接数。
|
||||
|
||||
$ stat --format=%F trythat
|
||||
regular file
|
||||
$ stat --format=%h trythat
|
||||
1
|
||||
|
||||
在下面的例子中， 我们查看了文件权限 -- 分别以两种可用的格式 -- 然后是文件的 SELinux 安全环境。最后，我们我们可以以从 Epoch 开始的秒数格式来查看文件访问时间。
|
||||
|
||||
$ stat --format=%a trythat
|
||||
700
|
||||
$ stat --format=%A trythat
|
||||
-rwx------
|
||||
$ stat --format=%C trythat
|
||||
(null)
|
||||
$ stat --format=%X bin
|
||||
1411282845
|
||||
|
||||
下面全部是可用的选项：
|
||||
|
||||
%a 八进制表示的访问权限
|
||||
%A 可读格式表示的访问权限
|
||||
%b 分配的块数（参见 %B）
|
||||
%B %b 参数显示的每个块的字节数
|
||||
%d 十进制表示的设备号
|
||||
%D 十六进制表示的设备号
|
||||
%f 十六进制表示的 Raw 模式
|
||||
%F 文件类型
|
||||
%g 属主的组 ID
|
||||
%G 属主的组名
|
||||
%h 硬连接数
|
||||
%i Inode 号
|
||||
%n 文件名
|
||||
%N 如果是符号链接，显示器所链接的文件名
|
||||
%o I/O 块大小
|
||||
%s 全部占用的字节大小
|
||||
%t 十六进制的主设备号
|
||||
%T 十六进制的副设备号
|
||||
%u 属主的用户 ID
|
||||
%U 属主的用户名
|
||||
%x 最后访问时间
|
||||
%X 最后访问时间，自 Epoch 开始的秒数
|
||||
%y 最后修改时间
|
||||
%Y 最后修改时间，自 Epoch 开始的秒数
|
||||
%z 最后改变时间
|
||||
%Z 最后改变时间，自 Epoch 开始的秒数
|
||||
|
||||
针对文件系统还有如下格式选项：
|
||||
|
||||
%a 普通用户可用的块数
|
||||
%b 文件系统的全部数据块数
|
||||
%c 文件系统的全部文件节点数
|
||||
%d 文件系统的可用文件节点数
|
||||
%f 文件系统的可用节点数
|
||||
%C SELinux 的安全上下文
|
||||
%i 十六进制表示的文件系统 ID
|
||||
%l 文件名的最大长度
|
||||
%n 文件系统的文件名
|
||||
%s 块大小（用于更快的传输）
|
||||
%S 基本块大小（用于块计数）
|
||||
%t 十六进制表示的文件系统类型
|
||||
%T 可读格式表示的文件系统类型
|
||||
|
||||
这些信息都可以得到，stat 命令也许可以帮你以稍微不同的角度来了解你的文件。
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: http://www.itworld.com/operating-systems/437351/unix-stat-more-ls
|
||||
|
||||
作者：[Sandra Henry-Stocker][a]
|
||||
译者：[wangjiezhe](https://github.com/wangjiezhe)
|
||||
校对：[wxy](https://github.com/wxy)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创翻译，[Linux中国](http://linux.cn/) 荣誉推出
|
||||
|
||||
[a]:http://www.itworld.com/sandra-henry-stocker
|
||||
@ -1,10 +1,10 @@
|
||||
Linux有问必答——如何检测并修复bash中的破壳漏洞
|
||||
Linux有问必答：如何检测并修复bash中的破壳漏洞
|
||||
================================================================================
|
||||
> **问题**：我想要知道我的Linux服务器是否存在bash破壳漏洞，以及如何来保护我的Linux服务器不受破壳漏洞侵袭。
|
||||
|
||||
2014年9月24日，一位名叫斯特凡·沙泽拉的安全研究者发现了一个名为“破壳”（也称为“bash门”或“Bash漏洞”）的bash漏洞。该漏洞如果被渗透，远程攻击者就可以在调用shell前通过在特别精心编制的环境中输出函数定义执行任何程序代码。然后，这些函数内的代码就可以在调用bash时立即执行。
|
||||
2014年9月24日，一位名叫斯特凡·沙泽拉的安全研究者发现了一个名为“破壳”（Shellshock，也称为“bash门”或“Bash漏洞”）的bash漏洞。该漏洞如果被渗透，远程攻击者就可以在调用shell前通过在特别精心编制的环境中输出函数定义执行任何程序代码。然后，这些函数内的代码就可以在调用bash时立即执行。
|
||||
|
||||
注意，破壳漏洞影响到bash版本1.14到4.3（当前版本）。虽然在写本文时还没有该漏洞权威而完整的修复方案，也尽管主要的Linux发行版（[Debian][1]，[Red Hat][2]，[CentOS][3]，[Ubuntu][4]和 [Novell/Suse][5]）已经发布了用于解决与此漏洞相关的补丁（[CVE-2014-6271][6]和[CVE-2014-7169][7]），并且建议尽快更新bash，并在随后数日内检查更新：
|
||||
注意，破壳漏洞影响到bash版本1.14到4.3（当前版本）。虽然在写本文时还没有该漏洞权威而完整的修复方案，也尽管主要的Linux发行版（[Debian][1]，[Red Hat][2]，[CentOS][3]，[Ubuntu][4]和 [Novell/Suse][5]）已经发布了用于部分解决与此漏洞相关的补丁（[CVE-2014-6271][6]和[CVE-2014-7169][7]），并且建议尽快更新bash，并在随后数日内检查更新（LCTT 译注，可能你看到这篇文章的时候，已经有了完善的解决方案）。
|
||||
|
||||
### 检测破壳漏洞 ###
|
||||
|
||||
@ -12,14 +12,13 @@ Linux有问必答——如何检测并修复bash中的破壳漏洞
|
||||
|
||||
$ env x='() { :;}; echo "Your bash version is vulnerable"' bash -c "echo This is a test"
|
||||
|
||||
（注：上面代码中echo "Your bash version is vulnerable"一句在发布时刷成红色）
|
||||
|
||||
如果你的Linux系统已经暴露给了破壳漏洞渗透，命令输出会像这样：
|
||||
|
||||
Your bash version is vulnerable
|
||||
This is a test
|
||||
|
||||
在上面的命令中，一个名为x的环境变量已经被设置可用于用户环境。就如我们所了解到的，它并没有赋值（是一个虚函数定义），后面跟了一个任意命令（红色）（注：red这个词在发布时刷成红色），该命令将在bash调用前执行。
|
||||
在上面的命令中，一个名为x的环境变量已经被设置可用于用户环境。就如我们所了解到的，它并没有赋值（是一个虚函数定义），后面跟了一个任意命令（红色），该命令将在bash调用前执行。
|
||||
|
||||
### 为破壳漏洞应用修复 ###
|
||||
|
||||
@ -62,7 +61,7 @@ CentOS:
|
||||
via: http://ask.xmodulo.com/detect-patch-shellshock-vulnerability-bash.html
|
||||
|
||||
译者：[GOLinux](https://github.com/GOLinux)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
校对：[wxy](https://github.com/wxy)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创翻译，[Linux中国](http://linux.cn/) 荣誉推出
|
||||
|
||||
@ -1,16 +1,16 @@
|
||||
Debian 7.7 发布了，带来了一些安全修复
|
||||
Debian 7.7 更新版发布
|
||||
================================================================================
|
||||
** Debian项目已经宣布Debian7.7 “Wheezy”发布并提供下载。这是常规维护更新，但它打包了很多重要的更新。**
|
||||
**Debian项目已经宣布Debian7.7 “Wheezy”发布并提供下载。这是常规维护更新，但它打包了很多重要的更新。**
|
||||
|
||||
|
||||
|
||||
Debian发行版可以得到常规主要的更新，但如果你已经安装了它且保持最新，你无需做任何额外的东西。开发者已经开发了一些重要的修复，因此它建议尽快升级。
|
||||
Debian在这个发行版里面包含了常规的主要更新，但如果你已经安装的 Debian 保持着不断最新就无需下载安装这个版本。开发者做了一些重要的修复，因此如果还没升级的话建议尽快升级。
|
||||
|
||||
“此次更新主要给稳定版修正安全问题，以及对一些严重问题的调整。安全建议已经另外发布且在其他地方引用。”
|
||||
“此次更新主要是给稳定版修正安全问题，以及对一些严重问题的调整。安全建议的公告已经另行发布了，请查阅。”
|
||||
|
||||
开发者在正式[公告][1]中指出：“请注意，此更新不构成Debian 7的新版本，只会更新部分包，没必要扔掉旧的wheezy CD或DVD，只要在安装后通过Debian镜像升级来升级那些过期的包就行“。
|
||||
开发者在正式[公告][1]中指出：“请注意，此更新并不是Debian 7的新版本，只是更新了部分包，没必要扔掉旧的wheezy CD或DVD，只要在安装后通过 Debian 镜像来升级那些过期的包就行“。
|
||||
|
||||
开发着已经升级了Bash包来修复一些重要的漏洞，在boot时登录SSH不再有效，并且还做了其他一些微调。
|
||||
开发者已经升级了 Bash 包来修复一些重要的漏洞，在启动时SSH登录不再有效，并且还做了其他一些微调。
|
||||
|
||||
要了解发布更多的细节请查看官方公告中的完整更新日志。
|
||||
|
||||
@ -26,7 +26,7 @@ via: http://news.softpedia.com/news/Debian-7-7-Is-Out-with-Security-Fixes-462647
|
||||
|
||||
作者：[Silviu Stahie][a]
|
||||
译者：[geekpi](https://github.com/geekpi)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
校对：[wxy](https://github.com/wxy)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创翻译，[Linux中国](http://linux.cn/) 荣誉推出
|
||||
|
||||
@ -1,15 +1,15 @@
|
||||
实用免费图片查看器
|
||||
Linux 下的免费图片查看器
|
||||
================================================================================
|
||||
|
||||
我最喜欢的谚语之一是“一图胜千言”。它指一张静态图片可以传递一个复杂的想法。图像相比文字而言可以迅速且更有效地描述大量信息。它们捕捉回忆，永不让你忘记你所想记住的东西，并且让它时常在你的记忆里刷新。
|
||||
|
||||
图片是互联网日常使用的一部分，并且对社交媒体互动尤其重要。一个好的图片查看器是任何操作系统必不可少的一个组成部分。
|
||||
|
||||
Linux 系统提供了一个大量开源实用小程序的集合，其中这些程序提供了从显而易见到异乎寻常的各种功能。正是由于这些工具的高质量和可供选择帮助 Linux 在生产环境中而脱颖而出，尤其是当谈到图片查看器时。Linux 有如此多的图像查看器可供选择，以至于让挑选变得困难。
|
||||
Linux 系统提供了一个大量开源实用小程序的集合，其中这些程序提供了从显而易见到异乎寻常的各种功能。正是由于这些工具的高质量和多样选择帮助 Linux 在生产环境中而脱颖而出，尤其是当谈到图片查看器时。Linux 有如此多的图像查看器可供选择，以至于让选择困难症患者无所适从~
|
||||
|
||||
一个不该包括在这个综述中但是值得一提的软件是 Fragment Image Viewer。它在专有许可证下发行（是的，我知道！），所以不会预先安装在 Ubuntu 上。 但它无疑看起来十分有趣！它是明日之星，尤其如果它的开发者们将它在开源许可证下发布的话。
|
||||
一个不该包括在这个综述中但是值得一提的软件是 Fragment Image Viewer。它在专有许可证下发行（是的，我知道！），所以不会预先安装在 Ubuntu 上。 但它无疑看起来十分有趣！要是它的开发者们将它在开源许可证下发布的话，它将是明日之星！
|
||||
|
||||
现在，让我们亲眼探究一下这 13 款图像查看器。除了一个例外，它们中每个都是在开源协议下发行。由于有很多信息要阐述，我将这些详细内容从当前单一网页综述剥离，但作为替代，我为每一款图片查看器提供了一个单独页面，具有软件的完整描述，产品特点的详细分析，一张软件工作中的截图，以及相关资源和评论的链接。
|
||||
现在，让我们亲眼探究一下这 13 款图像查看器。除了一个例外，它们中每个都是在开源协议下发行。由于有很多信息要阐述，我将这些详细内容从当前单一网页综述剥离，但作为替代，我为每一款图片查看器提供了一个单独页面，包括软件的完整描述，产品特点的详细分析，一张软件工作中的截图，以及相关资源和评论的链接。
|
||||
|
||||
### 图片查看器 ###
|
||||
|
||||
@ -32,7 +32,7 @@ Linux 系统提供了一个大量开源实用小程序的集合，其中这些
|
||||
via: http://www.linuxlinks.com/article/20141018070111434/ImageViewers.html
|
||||
|
||||
译者：[jabirus](https://github.com/jabirus)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
校对：[wxy](https://github.com/wxy)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创翻译，[Linux中国](http://linux.cn/) 荣誉推出
|
||||
|
||||
@ -1,3 +1,4 @@
|
||||
(translating by runningwater)
|
||||
UbuTricks 14.10.08
|
||||
================================================================================
|
||||
> An Ubuntu utility that allows you to install the latest versions of popular apps and games
|
||||
@ -44,7 +45,7 @@ Several versions of the Ubuntu Linux operating systems are supported, but if not
|
||||
via: http://linux.softpedia.com/get/Desktop-Environment/Tools/UbuTricks-103626.shtml
|
||||
|
||||
作者：[Marius Nestor][a]
|
||||
译者：[译者ID](https://github.com/译者ID)
|
||||
译者：[runningwater](https://github.com/runningwater)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创翻译，[Linux中国](http://linux.cn/) 荣誉推出
|
||||
|
||||
@ -1,96 +0,0 @@
|
||||
Translating by ZTinoZ
|
||||
7 Improvements The Linux Desktop Needs
|
||||
======================================
|
||||
|
||||
In the last fifteen years, the Linux desktop has gone from a collection of marginally adequate solutions to an unparalleled source of innovation and choice. Many of its standard features are either unavailable in Windows, or else available only as a proprietary extension. As a result, using Linux is increasingly not only a matter of principle, but of preference as well.
|
||||
|
||||
Yet, despite this progress, gaps remain. Some are missing features, others missing features, and still others pie-in-the sky extras that could be easily implemented to extend the desktop metaphor without straining users' tolerance of change.
|
||||
|
||||
For instance, here are 7 improvements that would benefit the Linux desktop:
|
||||
|
||||
### 7. Easy Email Encryption
|
||||
|
||||
These days, every email reader from Alpine to Thunderbird and Kmail include email encryption. However, documentation is often either non-existent or poor.
|
||||
|
||||
But, even if you understand the theory, the practice is difficult. Controls are generally scattered throughout the configuration menus and tabs, requiring a thorough search for all the settings that you require or want. Should you fail to set up encryption properly, usually you receive no feedback about why.
|
||||
|
||||
The closest to an easy process is [Enigmail][1], a Thunderbird extension that includes a setup wizard aimed at beginners. But you have to know about Enigmail to use it, and the menu it adds to the composition window buries the encryption option one level down and places it with other options guaranteed to mystify everyday users.
|
||||
|
||||
No matter what the desktop, the assumption is that, if you want encrypted email, you already understand it. Today, though, the constant media references to security and privacy have ensured that such an assumption no longer applies.
|
||||
|
||||
### 6. Thumbnails for Virtual Workspaces
|
||||
|
||||
Virtual workspaces offer more desktop space without requiring additional monitors. Yet, despite their usefulness, management of virtual workspaces hasn't changed in over a decade. On most desktops, you control them through a pager in which each workspace is represented by an unadorned rectangle that gives few indications of what might be on it except for its name or number -- or, in the case of Ubuntu's Unity, which workspace is currently active.
|
||||
|
||||
True, GNOME and Cinnamon do offer better views, but the usefulness of these views is limited by the fact that they require a change of screens. Nor is KDE's written list of contents, which is jarring in the primarily graphic-oriented desktop.
|
||||
|
||||
A less distracting solution might be mouseover thumbnails large enough for those with normal vision to see exactly what is on each workspace.
|
||||
|
||||
### 5. A Workable Menu
|
||||
|
||||
The modern desktop long ago outgrew the classic menu with its sub-menus cascading across the screen. Today, the average computer simply has too many applications to fit comfortably into such a format.
|
||||
|
||||
The trouble is, neither of the major alternatives is as convenient as the classic menu. Confining the menu into a single window is less than ideal, because you either have to endure truncated sub-menus or else continually resize the window with the mouse.
|
||||
|
||||
Yet the alternative of a full-screen menu is even worse. It means changing screens before you even begin to work, and relying on a search field that is only useful if you already know what applications are available -- in which case you are almost better off launching from the command line.
|
||||
|
||||
Frankly, I don't know what the solution might be. Maybe spinner racks, like those in OS X? All I can say for certain is that all alternatives for a modern menu make a carefully constructed set of icons on the desktop seem a more reasonable alternative.
|
||||
|
||||
### 4. A Professional, Affordable Video Editor
|
||||
|
||||
Over the years, Linux has slowly filled the gaps in productivity software. However, one category in which it is still lacking is in reasonably priced software for editing videos.
|
||||
|
||||
The problem is not that such free software is non-existent. After all, [Maya][2] is one of the industry standards for animation. The problem is that the software costs several thousand dollars.
|
||||
|
||||
At the opposite end of the spectrum are apps like Pitivi or Blender, whose functionality -- despite brave efforts by their developers -- remain basic. Progress happens, but far more slowly than anyone hopes for.
|
||||
|
||||
Although I have heard of indie directors using native Linux video editors, the reason I have heard of their efforts is usually because of their complaints. Others prefer to minimize the struggle and edit on other operating systems instead.
|
||||
|
||||
### 3. A Document Processor
|
||||
|
||||
At one extreme are users whose need for word processing is satisfied by Google Docs. At the other extreme are layout experts for whom Scribus is the only feasible app.
|
||||
|
||||
In-between are those like publishers and technical writers who produce long, text-oriented documents. This category of users is served by [Adobe FrameMaker][3] on Windows, and to some extent by LibreOffice Writer on Linux.
|
||||
|
||||
Unfortunately, these users are apparently not a priority in LibreOffice, Calligra Words, AbiWord, or any other office suite. Features that would provide for these users include:
|
||||
|
||||
- separate bibliographic databases for each file
|
||||
- tables that are treated like styles in the same way that paragraphs and characters are
|
||||
- page styles with persistent content other than headers or footers that would appear each time the style is used
|
||||
- storable formats for cross-references, so that the structure doesn't need to be recreated manually each time that it is needed
|
||||
|
||||
Whether LibreOffice or another application provides these features is irrelevant comparing to whether they are available. Without them, the Linux desktop is an imperfect place for a large class of potential users.
|
||||
2. Color-Coded Title Bars
|
||||
|
||||
Browser extensions have taught me how useful color coded tabs can be for workspaces. The titles of open tabs disappear when more than eight or nine or open, so the color is often the quickest visual guide to the relation between tabs.
|
||||
|
||||
The same system could be just as useful on the desktop. Better yet, the color coding might be preserved between sessions, allowing users to open all the apps needed for a specific task at the same time. So far, I know of no desktop with such a feature.
|
||||
|
||||
### 1. Icon Fences
|
||||
|
||||
For years, Stardock Systems has been selling a Windows extension called [Fences][4], which lets icons be grouped. You can name each group and move the icons in it together. In addition, you can assign which fence different types of files are automatically added to, and hide and arrange fences as needed.
|
||||
|
||||
In other words, fences automate the sort of arrangements that users make on their desktop all the time. Yet aside from one or two minor functions they share with KDE's Folder Views, fences remain completely unknown on Linux desktops. Perhaps the reason is that designers are focused on mobile devices as the source of ideas, and fences are decidedly a feature of the traditional workstation desktop.
|
||||
|
||||
### Personalized Lists
|
||||
|
||||
As I made this list, what struck me was how few of the improvements were general. Several of these improvement would appeal largely to specific audiences, and only one even implies the porting of a proprietary application. At least one is cosmetic rather than functional.
|
||||
|
||||
What this observation suggests is that, for the general user, Linux has very little left to add. As an all-purpose desktop, Linux arrive some years ago, and has been diversifying ever since, until today users can choose from over half a dozen major desktops.
|
||||
|
||||
None of that means, of course, that specialists wouldn't have other suggestions. In addition, changing needs can make improvements desirable that nobody once cared about. But it does mean that many items on a list of desirable improvements will be highly personal.
|
||||
|
||||
All of which raises the question: what other improvements do you think would benefit the desktop?
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: http://www.datamation.com/open-source/7-improvements-the-linux-desktop-needs-1.html
|
||||
|
||||
译者：[译者ID](https://github.com/译者ID) 校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创翻译，[Linux中国](http://linux.cn/) 荣誉推出
|
||||
|
||||
[1]:https://addons.mozilla.org/en-US/thunderbird/addon/enigmail/
|
||||
[2]:http://en.wikipedia.org/wiki/Autodesk_Maya
|
||||
[3]:http://www.adobe.com/products/framemaker.html
|
||||
[4]:http://www.stardock.com/products/fences/
|
||||
@ -1,8 +1,16 @@
|
||||
**Translating by jabirus...**
|
||||
|
||||
The People Who Support Linux: Hacking on Linux Since Age 16
|
||||
================================================================================
|
||||
|
||||
一个 Linux 支持者：从 16 岁开始在 Linux 上 hack
|
||||
================================================================================
|
||||
|
||||
|
||||
|
||||
Pretty much all of the projects in software developer [Yitao Li's GitHub repository][1] were developed on his Linux machine. None of them are necessarily Linux-specific, he says, but he uses Linux for “everything.”
|
||||
>Pretty much all of the projects in software developer [Yitao Li's GitHub repository][1] were developed on his Linux machine. None of them are necessarily Linux-specific, he says, but he uses Linux for “everything.”
|
||||
|
||||
在软件开发者[李逸韬的 GitHub 仓库][1]中，相当多的项目是在他的 Linux 机器上完成的。它们没有一个是必须特定需要 Linux 的，但李逸韬说他使用 Linux 来做”任何事情“。
|
||||
|
||||
For example: “coding / scripting, web browsing, web hosting, anything cloud-related, sending / receiving PGP signed emails, tweaking IP table rules, flashing OpenWrt image into routers, running one version of Linux kernel while compiling another version, doing research, doing homework (e.g., typing math equations in Tex), and many others...” Li said via email.
|
||||
|
||||
|
||||
131
sources/talk/20141022 FOSS and the Fear Factor.md
Normal file
131
sources/talk/20141022 FOSS and the Fear Factor.md
Normal file
@ -0,0 +1,131 @@
|
||||
FOSS and the Fear Factor
|
||||
================================================================================
|
||||
|
||||
|
||||
> "'Many eyes' is a complete and total myth," said SoylentNews' hairyfeet. "I bet my last dollar that if you looked at every.single.package. that makes up your most popular distros and then looked at how many have actually downloaded the source for those various packages, you'd find that there is less than 30 percent ... that are downloaded by anybody but the guys that actually maintain the things."
|
||||
|
||||
In a world that's been dominated for far too long by the [Systemd Inferno][1], Linux fans will have to be forgiven if they seize perhaps a bit too gleefully upon the scraps of cheerful news that come along on any given day.
|
||||
|
||||
Of course, for cheerful news, there's never any better place to look than the [Reglue][2] effort. Run by longtime Linux advocate and all-around-hero-for-kids Ken Starks, as alert readers [may recall][3], Reglue just last week launched a brand-new [fundraising effort][4] on Indiegogo to support its efforts over the coming year.
|
||||
|
||||
Since 2005, Reglue has placed more than 1,600 donated and then refurbished computers into the homes of financially disadvantaged kids in Central Texas. Over the next year, it aims to place 200 more, as well as paying for the first 90 days of Internet connection for each of them.
|
||||
|
||||
"As overused as the term is, the 'Digital Divide' is alive and well in some parts of America," Starks explained. "We will bridge that divide where we can."
|
||||
|
||||
How's that for a heaping helping of hope and inspiration?
|
||||
|
||||
### Windows as Attack Vector ###
|
||||
|
||||
|
||||
|
||||
Offering discouraged FOSS fans a bit of well-earned validation, meanwhile -- and perhaps even a bit of levity -- is the news that Russian hackers apparently have begun using Windows as a weapon against the rest of the world.
|
||||
|
||||
"Russian hackers use Windows against NATO" is the [headline][5] over at Fortune, making it plain for all the world to see that Windows isn't the bastion of security some might say it is.
|
||||
|
||||
The sarcasm is [knee-deep][6] in the comments section on Google+ over that one.
|
||||
|
||||
### 'Hackers Shake Confidence' ###
|
||||
|
||||
Of course, malicious hacking is no laughing matter, and the FOSS world has gotten a bitter taste of the effects for itself in recent months with the Heartbleed and Shellshock flaws, to name just two.
|
||||
|
||||
Has it been enough to scare Linux aficionados away?
|
||||
|
||||
That essentially is [the suggestion][7] over at Bloomberg, whose story, entitled "Hackers Shake Confidence in 1980s Free Software Idealism," has gotten more than a few FOSS fans' knickers in a twist.
|
||||
|
||||
### 'No Software Is Perfect' ###
|
||||
|
||||
"None of this has shaken my confidence in the slightest," asserted [Linux Rants][8] blogger Mike Stone down at the blogosphere's Broken Windows Lounge, for instance.
|
||||
|
||||
"I remember a time when you couldn't put a Windows machine on the network without firewall software or it would be infected with viruses/malware in seconds," he explained. "I don't recall the articles claiming that confidence had been shaken in Microsoft.
|
||||
|
||||
"The fact of the matter is that no software is perfect, not even FOSS, but it comes closer than the alternatives," Stone opined.
|
||||
|
||||
### 'My Faith Is Just Fine' ###
|
||||
|
||||
"It is hard to even begin to get into where the Bloomberg article fails," began consultant and [Slashdot][9] blogger Gerhard Mack.
|
||||
|
||||
"For one, decompilers have existed for ages and allow black hats to find flaws in proprietary software, so the black-hats can find problems but cannot admit they found them let alone fix them," Mack explained. "Secondly, it has been a long time since most open source was volunteer-written, and most contributions need to be paid.
|
||||
|
||||
"The author goes on to rip into people who use open source for not contributing monetarily, when most of the listed companies are already Linux Foundation members, so they are already contributing," he added.
|
||||
|
||||
In short, "my faith in open source is just fine, and no clickbait Bloomberg article will change that," Mack concluded.
|
||||
|
||||
### 'The Author Is Wrong' ###
|
||||
|
||||
"Clickbait" is also the term Google+ blogger Alessandro Ebersol chose to describe the Bloomberg account.
|
||||
|
||||
"I could not see the point the author was trying to make, except sensationalism and views," he told Linux Girl.
|
||||
|
||||
"The author is wrong," Ebersol charged. "He should educate himself on the topic. The flaws are results of lack of funding, and too many corporations taking advantage of free software and giving nothing back."
|
||||
|
||||
Moreover, "I still believe that a piece of code that can be studied and checked by many is far more secure than a piece made by a few," Google+ blogger Gonzalo Velasco C. chimed in.
|
||||
|
||||
"All the rumors that FLOSS is as weak as proprietary software are only [FUD][10] -- period," he said. "It is even more sad when it comes from private companies that drink in the FLOSS fountain."
|
||||
|
||||
### 'Source Helps Ensure Security' ###
|
||||
|
||||
Chris Travers, a [blogger][11] who works on the [LedgerSMB][12] project, had a similar view.
|
||||
|
||||
"I do think that having the source available helps ensure security for well-designed, well-maintained software," he began.
|
||||
|
||||
"Those of us who do development on such software must necessarily approach the security process under a different set of constraints than proprietary vendors do," Travers explained.
|
||||
|
||||
"Since our code changes are public, when we release a security fix this also provides effectively full disclosure," he said, "ensuring that the concerns for unpatched systems are higher than they would be for proprietary solutions absent full disclosure."
|
||||
|
||||
At the same time, "this disclosure cuts both ways, as software security vendors can use this to provide further testing and uncover more problems," Travers pointed out. "In the long run, this leads to more secure software, but in the short run it has security costs for users."
|
||||
|
||||
Bottom line: "If there is good communication with the community, if there is good software maintenance and if there is good design," he said, "then the software will be secure."
|
||||
|
||||
### 'Source Code Isn't Magic Fairy Dust' ###
|
||||
|
||||
SoylentNews blogger hairyfeet had a very different view.
|
||||
|
||||
"'Many eyes' is a complete and total myth," hairyfeet charged. "I bet my last dollar that if you looked at every.single.package. that makes up your most popular distros and then looked at how many have actually downloaded the source for those various packages, you'd find that there is less than 30 percent of the packages that are downloaded by anybody but the guys that actually maintain the things.
|
||||
|
||||
"How many people have done a code audit on Firefox? [LibreOffice][13]? Gimp? I bet you won't find a single one, because everybody ASSUMES that somebody else did it," he added.
|
||||
|
||||
"At the end of the day, Wall Street is finding out what guys like me have been saying for years: Source code isn't magic fairy dust that makes the bugs go away," hairyfeet observed.
|
||||
|
||||
### 'No One Actually Looked at It' ###
|
||||
|
||||
"The problem with [SSL][14] was that everyone assumed the code was good, but almost no one had actually looked at, so you never had the 'many eyeballs' making the bugs shallow," Google+ blogger Kevin O'Brien conceded.
|
||||
|
||||
Still, "I think the methodology and the idealism are separable," he suggested. "Open source is a way of writing software in which the value created for everyone is much greater than the value captured by any one entity, which is why it is so powerful.
|
||||
|
||||
"The idea that corporate contributions somehow sully the purity is a stupid idea," added O'Brien. "Corporate involvement is not inherently bad; what is bad is trying to lock other people out of the value created. Many companies handle this well, such as Red Hat."
|
||||
|
||||
### 'The Right Way to Do IT' ###
|
||||
|
||||
Last but not least, "my confidence in FLOSS is unshaken," blogger [Robert Pogson][15] declared.
|
||||
|
||||
"After all, I need software to run my computers, and as bad as some flaws are in FLOSS, that vulnerability pales into insignificance compared to the flaws in that other OS -- you know, the one that thinks images are executable and has so much complexity that no one, not even M$ with its $billions, can fix."
|
||||
|
||||
FOSS is "the right way to do IT," Pogson added. "The world can and does make its own software, and the world has more and better programmers than the big corporations.
|
||||
|
||||
"Those big corporations use FLOSS and should support FLOSS," he maintained, offering "thanks to the corporations who hire FLOSS programmers; sponsor websites, mirrors and projects; and who give back code -- the fuel in the FLOSS economy."
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: http://www.linuxinsider.com/story/FOSS-and-the-Fear-Factor-81221.html
|
||||
|
||||
作者：Katherine Noyes
|
||||
译者：[译者ID](https://github.com/译者ID)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创翻译，[Linux中国](http://linux.cn/) 荣誉推出
|
||||
|
||||
[1]:http://www.linuxinsider.com/perl/story/80980.html
|
||||
[2]:http://www.reglue.org/
|
||||
[3]:http://www.linuxinsider.com/story/78422.html
|
||||
[4]:https://www.indiegogo.com/projects/deleting-the-digital-divide-one-computer-at-a-time
|
||||
[5]:http://fortune.com/video/2014/10/14/russian-hackers-use-windows-against-nato/
|
||||
[6]:https://plus.google.com/+KatherineNoyes/posts/DQvRMekLHV4
|
||||
[7]:http://www.bloomberg.com/news/2014-10-14/hackers-shake-confidence-in-1980s-free-software-idealism.html
|
||||
[8]:http://linuxrants.com/
|
||||
[9]:http://slashdot.org/
|
||||
[10]:http://en.wikipedia.org/wiki/Fear,_uncertainty_and_doubt
|
||||
[11]:http://ledgersmbdev.blogspot.com/
|
||||
[12]:http://www.ledgersmb.org/
|
||||
[13]:http://www.libreoffice.org/
|
||||
[14]:http://en.wikipedia.org/wiki/Transport_Layer_Security
|
||||
[15]:http://mrpogson.com/
|
||||
@ -1,3 +1,5 @@
|
||||
su-kaiyao translating
|
||||
|
||||
How to create and use Python CGI scripts
|
||||
================================================================================
|
||||
Have you ever wanted to create a webpage or process user input from a web-based form using Python? These tasks can be accomplished through the use of Python CGI (Common Gateway Interface) scripts with an Apache web server. CGI scripts are called by a web server when a user requests a particular URL or interacts with the webpage (such as clicking a "Submit" button). After the CGI script is called and finishes executing, the output is used by the web server to create a webpage displayed to the user.
|
||||
@ -154,4 +156,4 @@ via: http://xmodulo.com/create-use-python-cgi-scripts.html
|
||||
|
||||
[a]:http://xmodulo.com/author/joshua
|
||||
[1]:http://httpd.apache.org/docs/2.2/howto/cgi.html
|
||||
[2]:https://docs.python.org/2/library/cgi.html#module-cgi
|
||||
[2]:https://docs.python.org/2/library/cgi.html#module-cgi
|
||||
|
||||
@ -0,0 +1,54 @@
|
||||
wangjiezhe translating...
|
||||
|
||||
Linux FAQs with Answers--How to change character encoding of a text file on Linux
|
||||
================================================================================
|
||||
> **Question**: I have an "iso-8859-1"-encoded subtitle file which shows broken characters on my Linux system, and I would like to change its text encoding to "utf-8" character set. In Linux, what is a good tool to convert character encoding in a text file?
|
||||
|
||||
As you already know, computers can only handle binary numbers at the lowest level - not characters. When a text file is saved, each character in that file is mapped to bits, and it is those "bits" that are actually stored on disk. When an application later opens that text file, each of those binary numbers are read and mapped back to the original characters that are understood by us human. This "save and open" process is best performed when all applications that need access to a text file "understand" its encoding, meaning the way binary numbers are mapped to characters, and thus can ensure a "round trip" of understandable data.
|
||||
|
||||
If different applications do not use the same encoding while dealing with a text file, non-readable characters will be shown wherever special characters are found in the original file. By special characters we mean those that are not part of the English alphabet, such as accented characters (e.g., ñ, á, ü).
|
||||
|
||||
The questions then become: 1) how can I know which character encoding a certain text file is using?, and 2) how can I convert it to some other encoding of my choosing?
|
||||
|
||||
### Step One ###
|
||||
|
||||
In order to find out the character encoding of a file, we will use a commad-line tool called file. Since the file command is a standard UNIX program, we can expect to find it in all modern Linux distros.
|
||||
|
||||
Run the following command:
|
||||
|
||||
$ file --mime-encoding filename
|
||||
|
||||
|
||||
|
||||
### Step Two ###
|
||||
|
||||
The next step is to check what kinds of text encodings are supported on your Linux system. For this, we will use a tool called iconv with the "-l" flag (lowercase L), which will list all the currently supported encodings.
|
||||
|
||||
$ iconv -l
|
||||
|
||||
The iconv utility is part of the the GNU libc libraries, so it is available in all Linux distributions out-of-the-box.
|
||||
|
||||
### Step Three ###
|
||||
|
||||
Once we have selected a target encoding among those supported on our Linux system, let's run the following command to perform the conversion:
|
||||
|
||||
$ iconv -f old_encoding -t new_encoding filename
|
||||
|
||||
For example, to convert iso-8859-1 to utf-8:
|
||||
|
||||
$ iconv -f iso-8859-1 -t utf-8 input.txt
|
||||
|
||||
|
||||
|
||||
Knowing how to use these tools together as we have demonstrated, you can for example fix a broken subtitle file:
|
||||
|
||||
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: http://ask.xmodulo.com/change-character-encoding-text-file-linux.html
|
||||
|
||||
译者：[wangjiezhe](https://github.com/wangjiezhe)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创翻译，[Linux中国](http://linux.cn/) 荣誉推出
|
||||
@ -0,0 +1,63 @@
|
||||
Linux FAQs with Answers--How to fix “sshd error: could not load host key”
|
||||
================================================================================
|
||||
> **Question**: When I try to SSH to a remote server, SSH client fails with "Connection closed by X.X.X.X". On the SSH server side, I see error messages: "sshd error: could not load host key." What is going on, and how can I fix this error?
|
||||
|
||||
The detailed symptom of this SSH connection error is as follows.
|
||||
|
||||
**SSH client side**: when you attempt to SSH to a remote host, you don't see login screen, and your SSH connection is closed right away with a message: "Connection closed by X.X.X.X"
|
||||
|
||||
**SSH server side**: in a system log, you see the following error messages (e.g., /var/log/auth.log on Debian/Ubuntu).
|
||||
|
||||
Oct 16 08:59:45 openstack sshd[1214]: error: Could not load host key: /etc/ssh/ssh_host_rsa_key
|
||||
Oct 16 08:59:45 openstack sshd[1214]: error: Could not load host key: /etc/ssh/ssh_host_dsa_key
|
||||
Oct 16 08:59:45 openstack sshd[1214]: error: Could not load host key: /etc/ssh/ssh_host_ecdsa_key
|
||||
Oct 16 08:59:45 openstack sshd[1214]: fatal: No supported key exchange algorithms [preauth]
|
||||
|
||||
The root cause of this problem is that sshd daemon somehow is not able to load SSH host keys.
|
||||
|
||||
When OpenSSH server is first installed on Linux system, SSH host keys should automatically be generated for subsequent use. If, however, key generation was not finished successfully, that can cause SSH login problems like this.
|
||||
|
||||
Let's check if SSH host keys are found where they should be.
|
||||
|
||||
$ ls -al /etc/ssh/ssh*key
|
||||
|
||||
|
||||
|
||||
If SSH host keys are not found there, or their size is all truncated to zero (like above), you need to regenerate SSH host keys from scratch.
|
||||
|
||||
### Regenerate SSH Host Keys ###
|
||||
|
||||
On Debian, Ubuntu or their derivatives, you can use dpkg-reconfigure tool to regenerate SSH host keys as follows.
|
||||
|
||||
$ sudo rm -r /etc/ssh/ssh*key
|
||||
$ sudo dpkg-reconfigure openssh-server
|
||||
|
||||
|
||||
|
||||
On CentOS, RHEL or Fedora, all you have to do is to restart sshd after removing existing (problematic) keys.
|
||||
|
||||
$ sudo rm -r /etc/ssh/ssh*key
|
||||
$ sudo systemctl restart sshd
|
||||
|
||||
An alternative way to regenerate SSH host keys is to manually generate them using ssh-keygen command.
|
||||
|
||||
$ sudo ssh-keygen -t rsa -f /etc/ssh/ssh_host_rsa_key
|
||||
$ sudo ssh-keygen -t dsa -f /etc/ssh/ssh_host_dsa_key
|
||||
$ sudo ssh-keygen -t ecdsa -f /etc/ssh/ssh_host_ecdsa_key
|
||||
|
||||
|
||||
|
||||
Once new SSH host keys are generated, make sure that they are found in /etc/ssh directory. There is no need to restart sshd at this point.
|
||||
|
||||
$ ls -al /etc/ssh/ssh*key
|
||||
|
||||
Now try to SSH again to the SSH server to see if the problem is gone.
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: http://ask.xmodulo.com/sshd-error-could-not-load-host-key.html
|
||||
|
||||
译者：[译者ID](https://github.com/译者ID)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创翻译，[Linux中国](http://linux.cn/) 荣誉推出
|
||||
@ -0,0 +1,96 @@
|
||||
Wine 1.7.29 (Development Version) Released – Install in RedHat and Debian Based Systems
|
||||
================================================================================
|
||||
**Wine**, a most popular and powerful open source application for Linux, that used to run Windows based applications and games on Linux Platform without any trouble.
|
||||
|
||||
|
||||
|
||||
Install Wine (Development Version) in Linux
|
||||
|
||||
WineHQ team, recently announced a new development version of **Wine 1.7.29**. This new development build arrives with a number of new important features and **44** bug fixes.
|
||||
|
||||
Wine team, keep releasing their development builds almost on weekly basis and adding numerous new features and fixes. Each new version brings support for new applications and games, making Wine a most popular and must have tool for every user, who want to run Windows based software in a Linux platform.
|
||||
|
||||
According to the changelog, following key features are added in this release:
|
||||
|
||||
- Added much improved shaping and BiDi mirroring in DirectWrite.
|
||||
- Few page fault handling problems have been udpated.
|
||||
- Included few more C runtime functions.
|
||||
- Various bug fixes.
|
||||
|
||||
For more in-depth details about this build can be found at the official [changelog][1] page.
|
||||
|
||||
This article guides you how to install most recent development version of **Wine 1.7.29** on **Red Hat** and **Debian** based systems such as CentOS, Fedora, Ubuntu, Linux Mint and other supported distributions.
|
||||
|
||||
### Installing Wine 1.7.29 Development Version in Linux ###
|
||||
|
||||
Unfortunately, there are no official Wine repository available for the **Red Hat** based systems and the only way to install Wine, is to compile it from source. To do this, you need to install some dependency packages such as gcc, flex, bison, libX11-devel freetype-devel and Development Tools, etc. These packages are must required to compile Wine from source. Let’s install them using following **YUM** command.
|
||||
|
||||
### On RedHat, Fedora and CentOS ###
|
||||
|
||||
# yum -y groupinstall 'Development Tools'
|
||||
# yum -y install flex bison libX11-devel freetype-devel
|
||||
|
||||
Next, download the latest development version of Wine (i.e. **1.7.29**) and extract the source tallball package using the following commands.
|
||||
|
||||
$ cd /tmp
|
||||
$ wget http://citylan.dl.sourceforge.net/project/wine/Source/wine-1.7.29.tar.bz2
|
||||
$ tar -xvf wine-1.7.29.tar.bz2 -C /tmp/
|
||||
|
||||
Now, it’s time to compile and build Wine installer using the following commands as normal user.
|
||||
|
||||
Note: The installation process might take up-to **15-20** minutes depending upon your internet and hardware speed, during installation it will ask you to enter **root** password.
|
||||
|
||||
#### On 32-Bit Systems ####
|
||||
|
||||
$ cd wine-1.7.29/
|
||||
$ ./tools/wineinstall
|
||||
|
||||
#### On 64-Bit Systems ####
|
||||
|
||||
$ cd wine-1.7.29/
|
||||
$ ./configure --enable-win64
|
||||
$ make
|
||||
# make install
|
||||
|
||||
### On Ubuntu, Debian and Linux Mint ###
|
||||
|
||||
Under **Ubuntu** based systems, you can easily install the latest development build of Wine using the official **PPA**. Open a terminal and run the following commands with sudo privileges.
|
||||
|
||||
$ sudo add-apt-repository ppa:ubuntu-wine/ppa
|
||||
$ sudo apt-get update
|
||||
$ sudo apt-get install wine 1.7 winetricks
|
||||
|
||||
**Note**: At the time of writing this article, available version was **1.7.26** and the new build not yet updated in official Wine Repository, but the above instructions will install **1.7.29** when they made available.
|
||||
|
||||
Once the installation completes successfully, you can install or run any windows based applications or games using wine as shown below.
|
||||
|
||||
$ wine notepad
|
||||
$ wine notepad.exe
|
||||
$ wine c:\\windows\\notepad.exe
|
||||
|
||||
**Note**: Please remember, this is a development build and cannot be installed or used on production systems. It is advised to use this version only for testing purpose.
|
||||
|
||||
If you’re looking for a most recent stable version of Wine, you can go through our following articles, that describes how to install most latest version on almost all Linux environments.
|
||||
|
||||
- [Install Wine 1.6.2 (Stable) in RHEL, CentOS and Fedora][2]
|
||||
- [Install Wine 1.6.2 (Stable) in Debian, Ubuntu and Mint][3]
|
||||
|
||||
### Reference Links ###
|
||||
|
||||
- [WineHQ Homepage][4]
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: http://www.tecmint.com/install-wine-in-linux/
|
||||
|
||||
作者：[Ravi Saive][a]
|
||||
译者：[译者ID](https://github.com/译者ID)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创翻译，[Linux中国](http://linux.cn/) 荣誉推出
|
||||
|
||||
[a]:http://www.tecmint.com/author/admin/
|
||||
[1]:http://www.winehq.org/announce/1.7.29
|
||||
[2]:http://www.tecmint.com/install-wine-in-rhel-centos-and-fedora/
|
||||
[3]:http://www.tecmint.com/install-wine-on-ubuntu-and-linux-mint/
|
||||
[4]:http://www.winehq.org/
|
||||
@ -0,0 +1,94 @@
|
||||
7个Linux桌面需要改善之处
|
||||
======================================
|
||||
|
||||
在过去的15年内，Linux桌面从一个还算凑合的边缘化解决方案集合发展到了一个空前的创新和选择源。它的标准特点中有许多是要么不适用于Windows系统，要么就只适合作为一个专有的扩展软件。因此，使用Linux愈发变得不仅是一个原则问题，也是一种偏好。
|
||||
|
||||
然而，尽管Linux桌面不停在进步，但是仍然存在差距。一些正在丢失它们的特点，一些已经丢失了，还有一些如同天上掉的馅饼般的附加设备能轻易地实现在不考虑用户对于改变的容忍度的情况下来扩展桌面。
|
||||
|
||||
比如说，以下是7个有利于Linux桌面发展的改善建议：
|
||||
|
||||
### 7. 简单的Email加密技术
|
||||
|
||||
如今，每个Email阅读器从Alpine到Thunderbird再到Kmail，都包括了Email加密技术。然而，文件编制通常是不存在或者非常劣质。
|
||||
|
||||
但是，即使你理论上看懂了，但是实践起来还是很困难的。控件通常分散在整个配置菜单和选项卡中，需要为所有你需要和想要的设置进行一次彻底的搜索。如果你未能进行适当的加密，你就收不到反馈。
|
||||
|
||||
最新的一个简易加密进程是 [Enigmail][1] ，一个包含面向初学者设置向导的Thunderbird扩展。但是你一定要知道怎么用Enigmail，而且菜单新增了合成窗口并把加密设置项添加了进去，如果把它弄到其它的设置里势必会使每个用户都难以理解。
|
||||
|
||||
无论桌面怎么样，假设如果你想接收加密过的Email，你就要先知道密码。可如今，不断有媒体涉及安全和隐私方面就已经确定了这样的假设不再适用。
|
||||
|
||||
### 6. 虚拟工作空间缩略图
|
||||
|
||||
虚拟工作空间提供了更多不需要额外监听的桌面空间。然而，尽管它们很实用，但是虚拟工作空间的管理并没有在过去十年发生改变。在大多数桌面上，你能通过每个工作空间上的pager程序（一个提供很少指示除了它的名字和数字的简单矩形框）来控制它们 -- 但是，在Ubuntu的统一实例中，工作空间目前来说还是很常用的。
|
||||
|
||||
确实，GNOME和Cinnamon能提供出不错的视图，但是它们的实用性受限于它们需要显示屏大小的事实和会与主要的图形化桌面发生冲突的KDE内容书面列表。
|
||||
|
||||
一个比较不错的解决方案应该是鼠标悬停在足够大的缩略图上来获取正常的视图，这样就精确地查看每个工作空间上的东西了。
|
||||
|
||||
### 5. 一个可操作的菜单
|
||||
|
||||
现代型桌面很久之前就已经舍弃搭配着子菜单的经典型菜单了。如今，一般的电脑都有太多的应用程序以至于不能适应这样的模式。
|
||||
|
||||
糟糕的是，没有什么主要的替代品能与经典型菜单一样方便。把菜单限制进一个单一的窗口，其效果是不理想的，因为你要么必须截掉子菜单要么就用鼠标不断地调整窗口。
|
||||
|
||||
但是全屏幕菜单的产品还要差，意思是你甚至要在开始工作之前就调整屏幕，并且依赖于仅仅可用的搜索框，当然如果你已经知道什么应用程序可用 -- 这种情况下你还不如直接用命令行。
|
||||
|
||||
坦白地说，我不知道拿什么来解决这个问题，OS X下的spinner racks吗？我可以肯定地说，所有现代型菜单产品在桌面上呈现出一个个精心构造的图标似乎更是一个合理的选择。
|
||||
|
||||
### 4. 一个专业的、实惠的视频编辑器
|
||||
|
||||
多年来，Linux已经慢慢地填充了软件生产力上的空白。然而即便如此，它仍然缺少价格合理的视频编辑软件。
|
||||
|
||||
问题不在于自由软件不存在。毕竟， [Maya][2] 是动画产业的标准之一，问题是在于这些软件的售价达数千美金。
|
||||
|
||||
另一边，是那些像Pitivi或者是Blender那样的免费软件, 它们的功能性 -- 尽管它们的开发者足够的努力 -- 一些基本功能仍然被保持着。虽然取得了进步，但还是和用户们所期望的相去甚远。
|
||||
|
||||
尽管我听说独立的部门使用的是原生态Linux视频编辑器，原因通常是因为他们抱怨其它编辑器不好，但其余的人更愿意减少麻烦从而在其它操作系统上对视频进行编辑。
|
||||
|
||||
### 3. 一个文档处理器
|
||||
|
||||
有一个极端是，那些需要进行文字处理的用户是由Google Docs负责，而另一个极端是对于那些布局设计的专家来说，Scribus是唯一比较可信的应用。
|
||||
|
||||
这两种极端之间还有一层，是那些比如那些生产长期的、面向文本的文件的出版商和作家。这类用户有些是由基于Windows的 [Adobe FrameMaker][3] 来服务, 有些则由基于Linux的LibreOffice Writer来服务。
|
||||
|
||||
不幸的是，这些用户显然不会优先考虑LibreOffice，Calligra Words， AbiWord或者是任何其它的办公套件。应该提供给用户的办公套件的特色功能包括：
|
||||
|
||||
- 为每个文件建立书目数据库。
|
||||
- 表格在样式上表格和段落与字符保持一致。
|
||||
- 带有持续性内容的页面样式，除了页眉和页脚，在每次样式要被使用的时候就会出现。
|
||||
- 交叉引用存储格式，以便不需要每次都手动创建。
|
||||
|
||||
无论是LibreOffice还是其它同类应用，提供这些特色功能与它们是否可用是不相干的。没有它们，Linux桌面对于一群潜在的用户来说就是个不完善的东西。
|
||||
|
||||
浏览器的扩展软件向我们展示了彩色编码标签对于工作空间的作用。开放标签的标题在开放程度超过八九成或完全开放的时候会消失，所以颜色通常是最快区分标签关系的方法。
|
||||
|
||||
系统也能和桌面一样实用。更好的是，彩色编码能保存在会话之间，在同一时间允许用户打开所有需要一个特点任务的应用。到目前为止，我知道没有任何一个桌面有这个特点。
|
||||
|
||||
### 2. 图标栏
|
||||
|
||||
多年以来，Stardock公司一直销售着一个名叫 [Fences][4] 的扩展软件,它用来分类和组织桌面上的图标，你能用它给每个组取名并且可以把每个图标都放在一起。另外，你可以指定不同的文件类型自动加入到一个组里，并且按个人需要来隐藏和整理。
|
||||
|
||||
换句话说，fences让用户整天在桌面上干的事情自动有序地分组排列。然而，除了一两个小功能，它们与KDE的文件夹视图差不多，fences在Linux桌面上仍然鲜有人使用。这也许是因为开发人员把专注于移动设备作为主要目标，使用fences无疑是传统工作站桌面的一大特征。
|
||||
|
||||
### 1. 个性化列表
|
||||
|
||||
由于我做过这种列表，让我震惊的是鲜有提出的改进得到了推广普及。 这些改进能吸引大量特定的用户，并且甚至只有一个意味着专有应用程序的进入端口，至少它肯定是花拳绣腿。
|
||||
|
||||
这一观察表明，对于普通用户来说，Linux能添加的功能已经所剩无几了。作为一个通用的桌面，Linux从几年前到现在都很多元化，直到今天用户都能从超过半打的主流桌面中选择出一个来使用。
|
||||
|
||||
当然这不意味着，一些专家就不会有其它意见。另外，没有人会关心不断变化的需求会不会使改进令人满意。但是它意味着这份充斥着改进建议的名单上的许多项目将会高度个人化。
|
||||
|
||||
所有这些都是为了抛砖引玉：你认为还有什么其它的对桌面有益的建议吗？
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: http://www.datamation.com/open-source/7-improvements-the-linux-desktop-needs-1.html
|
||||
|
||||
译者：[ZTinoZ](https://github.com/ZTinoZ) 校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创翻译，[Linux中国](http://linux.cn/) 荣誉推出
|
||||
|
||||
[1]:https://addons.mozilla.org/en-US/thunderbird/addon/enigmail/
|
||||
[2]:http://en.wikipedia.org/wiki/Autodesk_Maya
|
||||
[3]:http://www.adobe.com/products/framemaker.html
|
||||
[4]:http://www.stardock.com/products/fences/
|
||||
@ -1,130 +0,0 @@
|
||||
Unix: stat -- 获取比 ls 更多的信息
|
||||
================================================================================
|
||||
> 厌倦了 ls 命令, 并且想查看更多有关你的文件的有趣的信息? 试一试 stat!
|
||||
|
||||
|
||||
|
||||
ls 命令可能是每一个 Unix 使用者第一个学习的命令之一, 但它仅仅显示了 stat 命令能给出的信息的一小部分.
|
||||
|
||||
stat 命令从文件的索引节点获取信息. 正如你可能已经了解的那样, 每一个系统里的文件都存有三组日期和时间, 它们包括最近修改时间(即使用 ls -l 命令时显示的日期和时间), 最近状态改变时间(包括重命名文件)和最近访问时间.
|
||||
|
||||
使用长列表模式查看文件信息, 你会看到类似下面的内容:
|
||||
|
||||
$ ls -l trythis
|
||||
-rwx------ 1 shs unixdweebs 109 Nov 11 2013 trythis
|
||||
|
||||
使用 stat 命令, 你会看到下面这些:
|
||||
|
||||
$ stat trythis
|
||||
File: `trythis'
|
||||
Size: 109 Blocks: 8 IO Block: 262144 regular file
|
||||
Device: 18h/24d Inode: 12731691 Links: 1
|
||||
Access: (0700/-rwx------) Uid: ( 263/ shs) Gid: ( 100/ unixdweebs)
|
||||
Access: 2014-09-09 19:27:58.000000000 -0400
|
||||
Modify: 2013-11-11 08:40:10.000000000 -0500
|
||||
Change: 2013-11-11 08:40:10.000000000 -0500
|
||||
|
||||
在上面的情形中, 文件的状态改变和文件修改的日期/时间是相同的, 而访问时间则是相当近的时间. 我们还可以看到文件使用了 8 个块, 以及两种格式显示的文件权限 -- 八进制(0700)格式和 rwx 格式. 在第三行显示的索引节点是 12731681. 文件没有其它的硬链接(Links: 1). 而且, 这个文件是一个常规文件.
|
||||
|
||||
重命名文件, 你会看到状态改变时间发生变化.
|
||||
|
||||
这里的 ctime 信息, 最早设计用来存储文件的创建日期和时间, 但之前的某个时间变为用来存储状态修改时间.
|
||||
|
||||
$ mv trythis trythat
|
||||
$ stat trythat
|
||||
File: `trythat'
|
||||
Size: 109 Blocks: 8 IO Block: 262144 regular file
|
||||
Device: 18h/24d Inode: 12731691 Links: 1
|
||||
Access: (0700/-rwx------) Uid: ( 263/ shs) Gid: ( 100/ unixdweebs)
|
||||
Access: 2014-09-09 19:27:58.000000000 -0400
|
||||
Modify: 2013-11-11 08:40:10.000000000 -0500
|
||||
Change: 2014-09-21 12:46:22.000000000 -0400
|
||||
|
||||
改变文件的权限也会改变 ctime 域.
|
||||
|
||||
你也可以配合通配符来使用 stat 命令以列出一组文件的状态:
|
||||
|
||||
$ stat myfile*
|
||||
File: `myfile'
|
||||
Size: 20 Blocks: 8 IO Block: 262144 regular file
|
||||
Device: 18h/24d Inode: 12731803 Links: 1
|
||||
Access: (0640/-rw-r-----) Uid: ( 263/ shs) Gid: ( 100/ unixdweebs)
|
||||
Access: 2014-08-23 03:00:36.000000000 -0400
|
||||
Modify: 2014-08-22 12:02:12.000000000 -0400
|
||||
Change: 2014-08-22 12:02:12.000000000 -0400
|
||||
File: `myfile2'
|
||||
Size: 20 Blocks: 8 IO Block: 262144 regular file
|
||||
Device: 18h/24d Inode: 12731806 Links: 1
|
||||
Access: (0640/-rw-r-----) Uid: ( 263/ shs) Gid: ( 100/ unixdweebs)
|
||||
Access: 2014-08-23 03:00:36.000000000 -0400
|
||||
Modify: 2014-08-22 12:03:30.000000000 -0400
|
||||
Change: 2014-08-22 12:03:30.000000000 -0400
|
||||
File: `myfile3'
|
||||
Size: 40 Blocks: 8 IO Block: 262144 regular file
|
||||
Device: 18h/24d Inode: 12730533 Links: 1
|
||||
Access: (0640/-rw-r-----) Uid: ( 263/ shs) Gid: ( 100/ unixdweebs)
|
||||
Access: 2014-08-23 03:00:36.000000000 -0400
|
||||
Modify: 2014-08-22 12:03:59.000000000 -0400
|
||||
Change: 2014-08-22 12:03:59.000000000 -0400
|
||||
|
||||
如果我们喜欢的话, 我们也可以通过其他命令来获取这些信息.
|
||||
|
||||
向 ls -l 命令添加 "u" 选项, 你会获得下面的结果. 注意这个选项会显示最后访问时间, 而添加 "c" 选项则会显示状态改变时间(在本例中, 是我们重命名文件的时间).
|
||||
|
||||
$ ls -lu trythat
|
||||
-rwx------ 1 shs unixdweebs 109 Sep 9 19:27 trythat
|
||||
$ ls -lc trythat
|
||||
-rwx------ 1 shs unixdweebs 109 Sep 21 12:46 trythat
|
||||
|
||||
stat 命令也可应用与文件夹.
|
||||
|
||||
在这个例子中, 我们可以看到有许多的链接.
|
||||
|
||||
$ stat bin
|
||||
File: `bin'
|
||||
Size: 12288 Blocks: 24 IO Block: 262144 directory
|
||||
Device: 18h/24d Inode: 15089714 Links: 9
|
||||
Access: (0700/drwx------) Uid: ( 263/ shs) Gid: ( 100/ unixdweebs)
|
||||
Access: 2014-09-21 03:00:45.000000000 -0400
|
||||
Modify: 2014-09-15 17:54:41.000000000 -0400
|
||||
Change: 2014-09-15 17:54:41.000000000 -0400
|
||||
|
||||
在这里, 我们查看一个文件系统.
|
||||
|
||||
$ stat -f /dev/cciss/c0d0p2
|
||||
File: "/dev/cciss/c0d0p2"
|
||||
ID: 0 Namelen: 255 Type: tmpfs
|
||||
Block size: 4096Fundamental block size: 4096
|
||||
Blocks: Total: 259366 Free: 259337 Available: 259337
|
||||
Inodes: Total: 223834 Free: 223531
|
||||
|
||||
注意 Namelen (文件名长度)域, 如果文件名长于 255 个字符的话, 你会很幸运地在文件名处看到心形符号!
|
||||
|
||||
stat 命令还可以一次显示所有我们想要的信息. 下面的例子中, 我们只想查看文件类型, 然后是硬连接数.
|
||||
|
||||
$ stat --format=%F trythat
|
||||
regular file
|
||||
$ stat --format=%h trythat
|
||||
1
|
||||
|
||||
在下面的例子中, 我们查看了文件权限 -- 分别以两种可用的格式 -- 然后是文件的 SELinux 安全环境.
|
||||
|
||||
译者注: 原文到这里就结束了, 但很明显缺少结尾. 最后一段的例子可以分别用
|
||||
|
||||
$ stat --format=%a trythat
|
||||
$ stat --format=%A trythat
|
||||
$ stat --format=%C trythat
|
||||
|
||||
来实现.
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: http://www.itworld.com/operating-systems/437351/unix-stat-more-ls
|
||||
|
||||
作者：[Sandra Henry-Stocker][a]
|
||||
译者：[wangjiezhe](https://github.com/wangjiezhe)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创翻译，[Linux中国](http://linux.cn/) 荣誉推出
|
||||
|
||||
[a]:http://www.itworld.com/sandra-henry-stocker
|
||||
@ -0,0 +1,29 @@
|
||||
Linux 有问必答 -- 如何修复“fatal error: openssl/aes.h: No such file or directory”
|
||||
================================================================================
|
||||
> **Question**：我尝试在Linux编译一个程序，但是编译失败并报了一个错，“fatal error: openssl/aes.h: No such file or directory”。我该怎样安装要求的头文件并在我的Linux上解决这个问题？
|
||||
|
||||
fatal error: openssl/aes.h: No such file or directory
|
||||
|
||||
如果你在编译时遇到这个错误，这可能是下面的原因：你尝试编译的程序使用OpenSSL，但是需要和OpenSSL链接的文件（库和头文件）在你Linux平台上缺少。
|
||||
|
||||
要解决这个问题，你需要安装**OpenSSL 开发包**，这在所有的现代Linux发行版的标准软件仓库中都有。
|
||||
|
||||
要在Debian、Ubuntu或者其他衍生版上安装OpenSSL：
|
||||
|
||||
$ sudo apt-get install libssl-dev
|
||||
|
||||
要在Fedora、CentOS或者RHEL上安装OpenSSL开发包：
|
||||
|
||||
$ sudo yum install openssl-devel
|
||||
|
||||
安装完后，尝试重新编译程序。
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: http://ask.xmodulo.com/fix-fatal-error-openssl.html
|
||||
|
||||
作者：[作者名][a]
|
||||
译者：[geekpi](https://github.com/geekpi)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创翻译，[Linux中国](http://linux.cn/) 荣誉推出
|
||||
Loading…
Reference in New Issue
Block a user