mirror of
https://github.com/LCTT/TranslateProject.git
synced 2025-01-28 23:20:10 +08:00
Merge remote-tracking branch 'LCTT/master'
This commit is contained in:
Xingyu Wang
commit
fcac6ba458
@ -0,0 +1,207 @@
|
||||
[#]: collector: (lujun9972)
|
||||
[#]: translator: (geekpi)
|
||||
[#]: reviewer: (wxy)
|
||||
[#]: publisher: (wxy)
|
||||
[#]: url: (https://linux.cn/article-11720-1.html)
|
||||
[#]: subject: (Build a retro Apple desktop with the Linux MLVWM)
|
||||
[#]: via: (https://opensource.com/article/19/12/linux-mlvwm-desktop)
|
||||
[#]: author: (Seth Kenlon https://opensource.com/users/seth)
|
||||
|
||||
使用 Linux MLVWM 打造复古苹果桌面
|
||||
======
|
||||
|
||||
> 本文是 24 天 Linux 桌面特别系列的一部分。如果老式的苹果电脑是用开源 POSIX 构建的呢？你可以通过构建 Macintosh 式的虚拟窗口管理器来实现。
|
||||
|
||||
![Person typing on a 1980's computer][1]
|
||||
|
||||
想象一下穿越到另一段平行历史，Apple II GS 和 MacOS 7 是基于开源 [POSIX][2] 构建的，它使用了与现代 Linux 相同的所有惯例，例如纯文本配置文件和模块化系统设计。这样的操作系统将为其用户带来什么？你可以使用 [Macintosh 式的虚拟窗口管理器（MLVWM）][3]来回答这些问题（甚至更多！）。
|
||||
|
||||
![MLVWM running on Slackware 14.2][4]
|
||||
|
||||
### 安装 MLVWM
|
||||
|
||||
MLVWM 安装并不容易，并且可能不在你的发行版软件仓库中。如果你有时间理解翻译不佳的 README 文件，编辑一些配置文件，收集并调整一些旧的 .xpm 图片，编辑一两个 Xorg 选项，那么你就可以体验 MLVWM。不管怎么说，这是一个新奇的窗口管理器，其最新版本可以追溯到 2000 年。
|
||||
|
||||
要编译 MLVWM，你必须安装 imake，它提供了 `xmkmf` 命令。你可以从发行版的软件仓库中安装 imake，也可以直接从 [Freedesktop.org][5] 获得。假设你已经有 `xmkmf` 命令，请进入包含 MLVWM 源码的目录，然后运行以下命令进行构建：
|
||||
|
||||
```
|
||||
$ xmkmf -a
|
||||
$ make
|
||||
```
|
||||
|
||||
构建后，编译后的 `mlvwm` 二进制文件位于 `mlvwm` 目录中。将其移动到[你的 PATH][6] 的任何位置：
|
||||
|
||||
```
|
||||
$ mv mlvwm/mlvwm /usr/local/bin/
|
||||
```
|
||||
|
||||
#### 编辑配置文件
|
||||
|
||||
现在已经安装好 MLVWM，但是如果不调整几个配置文件并仔细放好所需的图像文件，它将无法正确启动。示例配置文件位于你下载的源代码的 `sample_rc` 目录中。将文件 `Mlvwm-Netscape` 和 `Mlvwm-Xterm` 复制到你的主目录：
|
||||
|
||||
```
|
||||
$ cp sample_rc/Mlvwm-{Netscape,Xterm} $HOME
|
||||
```
|
||||
|
||||
将 `Mlvwmrc` 改名为 `$HOME/.mlvwmrc`（是的，即使示例文件的名称看似是大写字母，但你也必须使用小写的 “m”）：
|
||||
|
||||
```
|
||||
$ cp sample_rc/Mlvwmrc $HOME/.mlvwmrc
|
||||
```
|
||||
|
||||
打开 `.mlwmrc` 并找到第 54-55 行，它们定义了 MLVWM 在菜单和 UI 中使用的像素图的路径（`IconPath`）：
|
||||
|
||||
```
|
||||
# Set icon search path. It needs before "Style".
|
||||
IconPath /usr/local/include/X11/pixmaps:/home2/tak/bin/pixmap
|
||||
```
|
||||
|
||||
调整路径以匹配你填充图像的路径（我建议使用 `$HOME/.local/share/pixmaps`）。MLVWM 不提供像素图，因此需要你提供构建桌面所需图标。
|
||||
|
||||
即使你有位于系统其他位置的像素图（例如 `/usr/share/pixmaps`），也要这样做，因为你需要调整像素图的大小，你可能也不想在系统范围内执行此操作。
|
||||
|
||||
```
|
||||
# Set icon search path. It needs before "Style".
|
||||
IconPath /home/seth/.local/share/pixmaps
|
||||
```
|
||||
|
||||
#### 选择像素图
|
||||
|
||||
你已将 `.local/share/pixmaps` 目录定义为像素图源路径，但是该目录和图像均不存在。创建目录：
|
||||
|
||||
```
|
||||
$ mkdir -p $HOME/.local/share/pixmaps
|
||||
```
|
||||
|
||||
现在，配置文件将图像分配给菜单项和 UI 元素，但是系统中不存在这些图像。要解决此问题，请通读配置文件并找到每个 .xpm 图像。对于配置中列出的每个图像，将具有相同文件名的图像（或更改配置文件中的文件名）添加到你的 IconPath 目录。
|
||||
|
||||
`.mlvwmrc` 文件的注释很好，因此你可以大致了解要编辑的内容。无论如何，这只是第一步。你可以随时回来更改桌面外观。
|
||||
|
||||
这有些例子。
|
||||
|
||||
此代码块设置屏幕左上角的图标：
|
||||
|
||||
```
|
||||
# Register the menu
|
||||
Menu Apple, Icon label1.xpm, Stick
|
||||
```
|
||||
|
||||
`label1.xpm` 图像实际上在源代码的 `pixmap` 目录中，但我更喜欢使用来自 `/usr/share/pixmaps` 的 `Penguin.xpm`（在 Slackware 上）。无论使用什么，都必须将自定义像素图放在 `~/.local/share/pixmaps` 中，并在配置中更改像素图的名称，或者重命名像素图以匹配配置文件中当前的名称。
|
||||
|
||||
此代码块定义了左侧菜单中列出的应用：
|
||||
|
||||
```
|
||||
"About this Workstation..." NonSelect, Gray, Action About
|
||||
"" NonSelect
|
||||
"Terminal" Icon mini-display.xpm, Action Exec "kterm" exec kterm -ls
|
||||
"Editor" Action Exec "mule" exec mule, Icon mini-edit.xpm
|
||||
"calculator" Action Exec "xcal" exec xcalc, Icon mini-calc.xpm
|
||||
END
|
||||
```
|
||||
|
||||
通过遵循与配置文件中相同的语法，你可以自定义像素图并将自己的应用添加到菜单中（例如，我将 `mule` 更改为 `emacs`）。这是你在 MLVWM GUI 中打开应用的入口，因此请列出你要快速访问的所有内容。你可能还希望包括指向 `/usr/share/applications` 文件夹的快捷方式。
|
||||
|
||||
```
|
||||
"Applications" Icon Penguin.xpm, Action Exec "thunar /usr/share/applications" exec thunar /usr/share/applications
|
||||
```
|
||||
|
||||
完成编辑配置文件并将自己的图像添加到 IconPath 目录后，必须将所有像素图的大小都调整为大约 16x16 像素。（MLVWM 的默认设置不一致，因此存在变化空间。）你可以使用 ImageMagick 进行批量操作：
|
||||
|
||||
```
|
||||
$ for i in ~/.local/share/mlvwm-pixmaps/*xpm ; do convert -resize '16x16^' $i; done
|
||||
```
|
||||
|
||||
### 启动 MLVWM
|
||||
|
||||
最简单的运行 MLVWM 的方式是让 Xorg 完成大部分工作。首先，你必须创建一个 `$HOME/.xinitrc` 文件。我从 Slackware 复制了这个，它也是从 Xorg 拿来的：
|
||||
|
||||
```
|
||||
#!/bin/sh
|
||||
# $XConsortium: xinitrc.cpp,v 1.4 91/08/22 11:41:34 rws Exp $
|
||||
|
||||
userresources=$HOME/.Xresources
|
||||
usermodmap=$HOME/.Xmodmap
|
||||
sysresources=/etc/X11/xinit/.Xresources
|
||||
sysmodmap=/etc/X11/xinit/.Xmodmap
|
||||
|
||||
# merge in defaults and keymaps
|
||||
|
||||
if [ -f $sysresources ]; then
|
||||
xrdb -merge $sysresources
|
||||
fi
|
||||
|
||||
if [ -f $sysmodmap ]; then
|
||||
xmodmap $sysmodmap
|
||||
fi
|
||||
|
||||
if [ -f $userresources ]; then
|
||||
xrdb -merge $userresources
|
||||
fi
|
||||
|
||||
if [ -f $usermodmap ]; then
|
||||
xmodmap $usermodmap
|
||||
fi
|
||||
|
||||
# Start the window manager:
|
||||
if [ -z "$DESKTOP_SESSION" -a -x /usr/bin/ck-launch-session ]; then
|
||||
exec ck-launch-session /usr/local/bin/mlvwm
|
||||
else
|
||||
exec /usr/local/bin/mlvwm
|
||||
fi
|
||||
```
|
||||
|
||||
根据此文件，`startx` 命令的默认操作是启动 MLVWM。但是，你的发行版可能对于图形服务器启动（或被终止以重新启动）时会发生的情况有其他做法，因此此文件可能对你没有什么帮助。在许多发行版上，你可以添加 .desktop 文件到 `/usr/share/xsessions` 中，以将其列在 GDM 或 KDM 菜单中，因此创建名为 `mlvwm.desktop` 的文件并输入：
|
||||
|
||||
```
|
||||
[Desktop Entry]
|
||||
Name=Mlvwm
|
||||
Comment=Macintosh-like virtual window manager
|
||||
Exec=/usr/local/bin/mlvwm
|
||||
TryExec=ck-launch-session /usr/local/bin/mlvwm
|
||||
Type=Application
|
||||
```
|
||||
|
||||
从桌面会话注销并重新登录到 MLVWM。默认情况下，会话管理器（KDM、GDM 或 LightDM，具体取决于你的设置）将继续登录到以前的桌面，因此在登录之前必须覆盖它。
|
||||
|
||||
对于 GDM：
|
||||
|
||||
![][7]
|
||||
|
||||
对于 SDDM：
|
||||
|
||||
![][8]
|
||||
|
||||
#### 强制启动
|
||||
|
||||
如果 MLVWM 无法启动，请尝试安装 XDM，这是一个轻量级会话管理器，它不会查询 `/usr/share/xsessions` 的内容，而是执行经过身份验证用户的所有 `.xinitrc` 操作。
|
||||
|
||||
![MLVWM][9]
|
||||
|
||||
### 打造自己的复古苹果
|
||||
|
||||
MLVWM 桌面未经打磨、不完美、模仿到位且充满乐趣。你看到的许多菜单项都是未实现的，但你可以使它们变得活跃且有意义。
|
||||
|
||||
这是一次让你时光倒流、改变历史，让老式苹果系列电脑成为开源堡垒的机会。成为一名修正主义者，设计你自己的复古苹果桌面，最重要的是，它有乐趣。
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://opensource.com/article/19/12/linux-mlvwm-desktop
|
||||
|
||||
作者：[Seth Kenlon][a]
|
||||
选题：[lujun9972][b]
|
||||
译者：[geekpi](https://github.com/geekpi)
|
||||
校对：[wxy](https://github.com/wxy)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
||||
[a]: https://opensource.com/users/seth
|
||||
[b]: https://github.com/lujun9972
|
||||
[1]: https://opensource.com/sites/default/files/styles/image-full-size/public/lead-images/1980s-computer-yearbook.png?itok=eGOYEKK- (Person typing on a 1980's computer)
|
||||
[2]: https://opensource.com/article/19/7/what-posix-richard-stallman-explains
|
||||
[3]: http://www2u.biglobe.ne.jp/~y-miyata/mlvwm.html
|
||||
[4]: https://opensource.com/sites/default/files/uploads/advent-mlvwm-file.jpg (MLVWM running on Slackware 14.2)
|
||||
[5]: http://cgit.freedesktop.org/xorg/util/imake
|
||||
[6]: https://opensource.com/article/17/6/set-path-linux
|
||||
[7]: https://opensource.com/sites/default/files/advent-gdm_2.jpg
|
||||
[8]: https://opensource.com/sites/default/files/advent-kdm_1.jpg
|
||||
[9]: https://opensource.com/sites/default/files/uploads/advent-mlvwm-chess.jpg (MLVWM)
|
||||
@ -1,22 +1,24 @@
|
||||
[#]: collector: (lujun9972)
|
||||
[#]: translator: (chen-ni)
|
||||
[#]: reviewer: ( )
|
||||
[#]: publisher: ( )
|
||||
[#]: url: ( )
|
||||
[#]: reviewer: (wxy)
|
||||
[#]: publisher: (wxy)
|
||||
[#]: url: (https://linux.cn/article-11721-1.html)
|
||||
[#]: subject: (How tracking pixels work)
|
||||
[#]: via: (https://jvns.ca/blog/how-tracking-pixels-work/)
|
||||
[#]: author: (Julia Evans https://jvns.ca/)
|
||||
|
||||
追踪像素是如何工作的？
|
||||
网络广告商的像素追踪是如何工作的？
|
||||
======
|
||||
|
||||
昨天，我和一名记者谈到了一个问题：广告商是如何在互联网上对人们进行追踪的？我们津津有味地查看了 Firefox 的开发者工具（虽然我不是一个互联网隐私专家，但至少还会使用开发者工具中的“network”标签页），从中我终于弄明白追踪像素在实际中是如何工作的了。
|
||||
|
||||
|
||||
昨天，我和一名记者谈到了一个问题：广告商是如何在互联网上对人们进行追踪的？我们津津有味地查看了 Firefox 的开发者工具（虽然我不是一个互联网隐私专家，但至少还会使用开发者工具中的“network”标签页），从中我终于弄明白<ruby>像素追踪<rt>tracking pixels</rt></ruby>在实际中是如何工作的了。
|
||||
|
||||
### 问题：Facebook 怎么知道你逛了 Old Navy？
|
||||
|
||||
我时常听人们说起这种有些诡异的上网经历：你在线上浏览了一个商品，一天之后，竟然看到了同一款靴子（或者是别的什么你当时浏览的商品）的广告。这就是所谓的“再营销”，但它到底是如何实现的呢？
|
||||
|
||||
在本文中，我们来进行一个小实验，看看 Facebook 究竟是怎么知道你在线上浏览了什么商品的。这里使用 Facebook 作为示例，只是因为很容易找到投放了 Facebook 追踪像素的网站；其实，几乎所有互联网广告公司都会使用类似的追踪技术。
|
||||
在本文中，我们来进行一个小实验，看看 Facebook 究竟是怎么知道你在线上浏览了什么商品的。这里使用 Facebook 作为示例，只是因为很容易找到使用了 Facebook 像素追踪技术的网站；其实，几乎所有互联网广告公司都会使用类似的追踪技术。
|
||||
|
||||
### 准备：允许第三方追踪器，同时关闭广告拦截器
|
||||
|
||||
@ -24,16 +26,20 @@
|
||||
|
||||
首先，我将隐私设置从默认设置（[截图][1]）修改为允许第三方追踪器的个性化设置（[截图][2]），然后禁用了一些平时运行的隐私保护扩展。
|
||||
|
||||
### 追踪像素：关键不在于 gif，而在于请求参数
|
||||
![截图][1]
|
||||
|
||||
追踪像素是网站用来追踪你的一个 1x1 大小的 gif。就其本身而言，一个小小的 1x1 gif 显然起不到什么作用。那么，追踪像素到底是如何进行追踪的？其中涉及两个方面：
|
||||
![截图][2]
|
||||
|
||||
1. 通过使用追踪像素上的**请求参数**，网站可以添加额外的信息，比如你正在访问的页面。这样一来，请求的就不是 `https://www.facebook.com/tr/`（这个链接是一个 44 字节大小的 1x1 gif），而是 `https://www.facebook.com/tr/?the_website_you're_on`。（邮件营销人员会使用类似的技巧，通过为追踪像素指定一个独特的 URL，弄清楚你是否打开了某一封邮件。）
|
||||
2. 在发送该请求的同时，还发送了相应的 cookie。这样一来广告商就可以知道，访问 oldnavy.com 的这个人和在同一台电脑上使用 Facebook 的是同一个人。
|
||||
### 像素追踪：关键不在于 gif，而在于请求参数
|
||||
|
||||
### Old Navy 网站上的 Facebook 追踪像素
|
||||
像素追踪是网站用来追踪你的一个 1x1 大小的 gif。就其本身而言，一个小小的 1x1 gif 显然起不到什么作用。那么，像素追踪到底是如何进行追踪的？其中涉及两个方面：
|
||||
|
||||
为了对此进行验证，我在 Old Navy（GAP 旗下的一个服装品牌）网站上浏览了一个商品，相应的URL是 [https://oldnavy.gap.com/browse/product.do?pid=504753002&cid=1125694&pcid=1135640&vid=1&grid=pds_0_109_1][3]（这是一件“男款短绒格子花呢大衣”）。
|
||||
1. 通过使用像素追踪上的**请求参数**，网站可以添加额外的信息，比如你正在访问的页面。这样一来，请求的就不是 `https://www.facebook.com/tr/`（这个链接是一个 44 字节大小的 1x1 gif），而是 `https://www.facebook.com/tr/?the_website_you're_on`。（邮件营销人员会使用类似的技巧，通过为像素追踪指定一个独特的 URL，弄清楚你是否打开了某一封邮件。）
|
||||
2. 在发送该请求的同时，还发送了相应的 cookie。这样一来广告商就可以知道，访问 oldnavy.com 的这个人和在同一台电脑上使用 Facebook 的是同一个人。
|
||||
|
||||
### Old Navy 网站上的 Facebook 像素追踪
|
||||
|
||||
为了对此进行验证，我在 Old Navy（GAP 旗下的一个服装品牌）网站上浏览了一个商品，相应的 URL 是 `https://oldnavy.gap.com/browse/product.do?pid=504753002&cid=1125694&pcid=1135640&vid=1&grid=pds_0_109_1`（这是一件“男款短绒格子花呢大衣”）。
|
||||
|
||||
在我浏览这个商品的同时，页面上运行的 Javascript（用的应该是[这段代码][4]）向 facebook.com 发送了一个请求。在开发者工具中，该请求看上去是这样的：（我屏蔽了大部分 cookie 值，因为其中有一些是我的登录 cookie）
|
||||
|
||||
@ -41,14 +47,23 @@
|
||||
|
||||
下面对其进行拆解分析：
|
||||
|
||||
1. 我的浏览器向 ` https://www.facebook.com/tr/?id=937725046402747&ev=PageView&dl=https%3A%2F%2Foldnavy.gap.com%2Fbrowse%2Fproduct.do%3Fpid%3D504753002%26cid%3D1125694%26pcid%3Dxxxxxx0%26vid%3D1%26grid%3Dpds_0_109_1%23pdp-page-content&rl=https%3A%2F%2Foldnavy.gap.com%2Fbrowse%2Fcategory.do%3Fcid%3D1135640%26mlink%3D5155%2Cm_mts_a&if=false&ts=1576684838096&sw=1920&sh=1080&v=2.9.15&r=stable&a=tmtealium&ec=0&o=30&fbp=fb.1.1576684798512.1946041422&it=15xxxxxxxxxx4&coo=false&rqm=GET` 发送了一个请求；
|
||||
2. 与该请求同时发送的，还有一个名为 `fr` 的 cookie，取值为 `10oGXEcKfGekg67iy.AWVdJq5MG3VLYaNjz4MTNRaU1zg.Bd-kxt.KU.F36.0.0.Bd-kx6.`（估计是我的 Facebook 广告追踪 ID）
|
||||
1. 我的浏览器向如下 URL 发送了一个请求；
|
||||
|
||||
在所发送的追踪像素查询字符串里，有三个值得注意的地方：
|
||||
```
|
||||
https://www.facebook.com/tr/?id=937725046402747&ev=PageView&dl=https%3A%2F%2Foldnavy.gap.com%2Fbrowse%2Fproduct.do%3Fpid%3D504753002%26cid%3D1125694%26pcid%3Dxxxxxx0%26vid%3D1%26grid%3Dpds_0_109_1%23pdp-page-content&rl=https%3A%2F%2Foldnavy.gap.com%2Fbrowse%2Fcategory.do%3Fcid%3D1135640%26mlink%3D5155%2Cm_mts_a&if=false&ts=1576684838096&sw=1920&sh=1080&v=2.9.15&r=stable&a=tmtealium&ec=0&o=30&fbp=fb.1.1576684798512.1946041422&it=15xxxxxxxxxx4&coo=false&rqm=GET
|
||||
```
|
||||
2. 与该请求同时发送的，还有一个名为 `fr` 的 cookie，取值为
|
||||
|
||||
* 我当前访问的页面：[https://oldnavy.gap.com/browse/product.do?pid=504753002&cid=1125694&pcid=1135640&vid=1&grid=pds_0_109_1#pdp-page-content][6]
|
||||
* 引导我来到当前页面的上一级页面：[https://oldnavy.gap.com/browse/category.do?cid=1135640&mlink=5155,m_mts_a][7]；
|
||||
* 作为我的身份标识的 cookie：`10oGXEcKfGekg67iy.AWVdJq5MG3VLYaNjz4MTNRaU1zg.Bd-kxt.KU.F36.0.0.Bd-kx6.`
|
||||
```
|
||||
10oGXEcKfGekg67iy.AWVdJq5MG3VLYaNjz4MTNRaU1zg.Bd-kxt.KU.F36.0.0.Bd-kx6.
|
||||
```
|
||||
（估计是我的 Facebook 广告追踪 ID）
|
||||
|
||||
在所发送的像素追踪查询字符串里，有三个值得注意的地方：
|
||||
|
||||
* 我当前访问的页面：`https://oldnavy.gap.com/browse/product.do?pid=504753002&cid=1125694&pcid=1135640&vid=1&grid=pds_0_109_1#pdp-page-content`
|
||||
* 引导我来到当前页面的上一级页面：`https://oldnavy.gap.com/browse/category.do?cid=1135640&mlink=5155,m_mts_a`；
|
||||
* 作为我的身份标识的 cookie：`10oGXEcKfGekg67iy.AWVdJq5MG3VLYaNjz4MTNRaU1zg.Bd-kxt.KU.F36.0.0.Bd-kx6.`
|
||||
|
||||
### 下面来逛逛 Facebook！
|
||||
|
||||
@ -60,11 +75,11 @@
|
||||
|
||||
Facebook 用来追踪我访问了哪些网站的 cookie，属于所谓的“第三方 cookie”，因为 Old Navy 的网站使用它为一个第三方（即 facebook.com）确认我的身份。这和用来维持登录状态的“第一方 cookie”有所不同。
|
||||
|
||||
Safari 和 Firefox 默认都会拦截许多第三方 cookie（所以需要更改 Firefox 的隐私设置，才能够进行这个实验），而 Chrome 目前并不进行拦截（很可能是因为 Chrome 的所有者正是一个广告公司）。
|
||||
Safari 和 Firefox 默认都会拦截许多第三方 cookie（所以需要更改 Firefox 的隐私设置，才能够进行这个实验），而 Chrome 目前并不进行拦截（很可能是因为 Chrome 的所有者正是一个广告公司）。（LCTT 译注：Chrome 可以设置阻拦）
|
||||
|
||||
### 网站上的追踪像素有很多
|
||||
### 网站上的像素追踪有很多
|
||||
|
||||
如我所料，网站上的追踪像素有 **很多**。比如，wrangler.com 在我的浏览器里加载了来自不同域的 19 个不同的追踪像素。wrangler.com 上的追踪像素分别来自：`ct.pinterest.com`、`af.monetate.net`、`csm.va.us.criteo.net`、`google-analytics.com`、`dpm.demdex.net`、`google.ca`、`a.tribalfusion.com`、`data.photorank.me`、`stats.g.doubleclick.net`、`vfcorp.dl.sc.omtrdc.net`、`ib.adnxs.com`、`idsync.rlcdn.com`、`p.brsrvr.com`，以及`adservice.google.com`。
|
||||
如我所料，网站上的像素追踪有 **很多**。比如，wrangler.com 在我的浏览器里加载了来自不同域的 19 个不同的像素追踪。wrangler.com 上的像素追踪分别来自：`ct.pinterest.com`、`af.monetate.net`、`csm.va.us.criteo.net`、`google-analytics.com`、`dpm.demdex.net`、`google.ca`、`a.tribalfusion.com`、`data.photorank.me`、`stats.g.doubleclick.net`、`vfcorp.dl.sc.omtrdc.net`、`ib.adnxs.com`、`idsync.rlcdn.com`、`p.brsrvr.com`，以及 `adservice.google.com`。
|
||||
|
||||
Firefox 贴心地指出，如果使用 Firefox 的标准隐私设置，其中的大部分追踪器都会被拦截：
|
||||
|
||||
@ -72,13 +87,13 @@ Firefox 贴心地指出，如果使用 Firefox 的标准隐私设置，其中的
|
||||
|
||||
### 浏览器的重要性
|
||||
|
||||
浏览器之所以如此重要，是因为你的浏览器最终决定了发送你的什么信息、发送到哪些网站。Old Navy 网站上的 Javascript 可以请求你的浏览器向 Facebook 发送关于你的追踪信息，但浏览器可以拒绝执行。浏览器的决定可以是：“哈，我知道 facebook.com/tr/ 是一个追踪像素，我不想让我的用户被追踪，所以我不会发送这个请求”。
|
||||
浏览器之所以如此重要，是因为你的浏览器最终决定了发送你的什么信息、发送到哪些网站。Old Navy 网站上的 Javascript 可以请求你的浏览器向 Facebook 发送关于你的追踪信息，但浏览器可以拒绝执行。浏览器的决定可以是：“哈，我知道 facebook.com/tr/ 是一个像素追踪，我不想让我的用户被追踪，所以我不会发送这个请求”。
|
||||
|
||||
浏览器还可以允许用户对上述行为进行配置，方法包括更改浏览器设置，以及安装浏览器扩展（所以才会有如此多的隐私保护扩展）。
|
||||
|
||||
### 摸清其中原理，实为一件趣事
|
||||
|
||||
在我看来，弄清楚 cookie / 追踪像素是怎么用于对你进行追踪的，实在是一件趣事（尽管显得有点阴险）。我之前大概明白其中的道理，但是并没有亲自查看过追踪像素上的 cookie，也没有看过发送的查询参数上究竟包含什么样的信息。
|
||||
在我看来，弄清楚 cookie/像素追踪是怎么用于对你进行追踪的，实在是一件趣事（尽管有点吓人）。我之前大概明白其中的道理，但是并没有亲自查看过像素追踪上的 cookie，也没有看过发送的查询参数上究竟包含什么样的信息。
|
||||
|
||||
当然，明白了其中的原理，也就更容易降低被追踪的概率了。
|
||||
|
||||
@ -86,9 +101,9 @@ Firefox 贴心地指出，如果使用 Firefox 的标准隐私设置，其中的
|
||||
|
||||
为了尽量避免在互联网上被追踪，我采取了几种简单的措施:
|
||||
|
||||
* 安装一个广告拦截器（比如 ublock origin 之类）。广告拦截器可以针对许多追踪器的域进行拦截。
|
||||
* 使用目前默认隐私保护强度更高的 Firefox/Safari，而不是 Chrome。
|
||||
* 使用 [Facebook Container][9] 这个 Firefox 扩展。该扩展针对 Facebook 进一步采取了防止追踪的措施。
|
||||
* 安装一个广告拦截器（比如 ublock origin 之类）。广告拦截器可以针对许多追踪器的域进行拦截。
|
||||
* 使用目前默认隐私保护强度更高的 Firefox/Safari，而不是 Chrome。
|
||||
* 使用 [Facebook Container][9] 这个 Firefox 扩展。该扩展针对 Facebook 进一步采取了防止追踪的措施。
|
||||
|
||||
虽然在互联网上被追踪的方式还有很多（尤其是在使用手机应用的时候，因为在这种情况下，你没有和像对浏览器一样的控制程度），但是能够理解这种追踪方法的工作原理，稍微减少一些被追踪的可能性，也总归是一件好事。
|
||||
|
||||
@ -98,8 +113,8 @@ via: https://jvns.ca/blog/how-tracking-pixels-work/
|
||||
|
||||
作者：[Julia Evans][a]
|
||||
选题：[lujun9972][b]
|
||||
译者：[译者ID](https://github.com/chen-ni)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
译者：[chen-ni](https://github.com/chen-ni)
|
||||
校对：[wxy](https://github.com/wxy)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
||||
@ -1,8 +1,8 @@
|
||||
[#]: collector: (lujun9972)
|
||||
[#]: translator: (geekpi)
|
||||
[#]: reviewer: ( )
|
||||
[#]: publisher: ( )
|
||||
[#]: url: ( )
|
||||
[#]: reviewer: (wxy)
|
||||
[#]: publisher: (wxy)
|
||||
[#]: url: (https://linux.cn/article-11722-1.html)
|
||||
[#]: subject: (How to Start, Stop & Restart Services in Ubuntu and Other Linux Distributions)
|
||||
[#]: via: (https://itsfoss.com/start-stop-restart-services-linux/)
|
||||
[#]: author: (Sergiu https://itsfoss.com/author/sergiu/)
|
||||
@ -10,37 +10,33 @@
|
||||
如何在 Ubuntu 和其他 Linux 发行版中启动、停止和重启服务
|
||||
======
|
||||
|
||||
服务是必不可少的后台进程，它通常随系统启动，并在关机时关闭。
|
||||
|
||||
|
||||
如果你是系统管理员，那么你会定期处理服务。
|
||||
|
||||
如果你是普通桌面用户，你可能会遇到需要重启服务的情况，例如[安装 Barrier 来用于在计算机之间共享鼠标和键盘][1]。或[在使用 ufw 设置防火墙][2]时。
|
||||
服务是必不可少的后台进程，它通常随系统启动，并在关机时关闭。如果你是系统管理员，那么你会定期处理服务。如果你是普通桌面用户，你可能会遇到需要重启服务的情况，例如[安装 Barrier 来用于在计算机之间共享鼠标和键盘][1]。或[在使用 ufw 设置防火墙][2]时。
|
||||
|
||||
今天，我将向你展示两种管理服务的方式。你将学习在 Ubuntu 或任何其他 Linux 发行版中启动、停止和重启服务。
|
||||
|
||||
systemd 与 init
|
||||
> systemd 与 init
|
||||
>
|
||||
> 如今，Ubuntu 和许多其他发行版都使用 systemd 而不是旧的 init。
|
||||
>
|
||||
> 在 systemd 中，可以使用 `systemctl` 命令管理服务。
|
||||
>
|
||||
> 在 init 中，你可以使用 `service` 命令管理服务。
|
||||
>
|
||||
> 你会注意到，即使你的 Linux 系统使用 systemd，它仍然可以使用 `service` 命令（与 init 系统一起使用的）。这是因为 `service` 命令实际上已重定向到 `systemctl`。systemd 引入了向后兼容性，因为系统管理员们习惯使用 `service` 命令。
|
||||
>
|
||||
> 在本教程中，我将同时展示 `systemctl` 和 `service` 命令。
|
||||
|
||||
如今，Ubuntu 和许多其他发行版都使用 systemd 而不是旧的 init。
|
||||
|
||||
在 systemd 中，可以使用 systemctl 命令管理服务。
|
||||
|
||||
在 init 中，你可以使用 service 命令管理服务。
|
||||
|
||||
你会注意到，即使你的 Linux 系统使用 systemd，它仍然可以使用 service 命令（为了与 init 系统一起使用）。这是因为 service 命令实际上已重定向到 systemctl。systemd 引入了向后兼容性，因为系统管理员们习惯使用 service 命令。
|
||||
|
||||
在本教程中，我将同时展示 systemctl 和 service 命令。
|
||||
|
||||
_我的是 Ubuntu 18.04，但其他版本的过程也一样_。
|
||||
我用的是 Ubuntu 18.04，但其他版本的过程也一样。
|
||||
|
||||
### 方法 1：使用 systemd 在 Linux 中管理服务
|
||||
|
||||
我从 systemd 开始，因为它被广泛接受。
|
||||
|
||||
#### 1\. 列出所有服务
|
||||
#### 1、列出所有服务
|
||||
|
||||
为了管理服务，你首先需要知道系统上有哪些服务可用。
|
||||
|
||||
你可以使用 systemd 命令列出 Linux 系统上的所有服务：
|
||||
为了管理服务，你首先需要知道系统上有哪些服务可用。你可以使用 systemd 的命令列出 Linux 系统上的所有服务：
|
||||
|
||||
```
|
||||
systemctl list-unit-files --type service -all
|
||||
@ -48,9 +44,9 @@ systemctl list-unit-files --type service -all
|
||||
|
||||
![systemctl list-unit-files][3]
|
||||
|
||||
此命令将输出所有服务的状态。服务状态有启用、禁用、屏蔽（在取消掩码之前处于非活动状态）、静态和已生成。
|
||||
此命令将输出所有服务的状态。服务状态有<ruby>启用<rt>enabled</rt></ruby>、<ruby>禁用<rt>disabled</rt></ruby>、<ruby>屏蔽<rt>masked</rt></ruby>（在取消屏蔽之前处于非活动状态）、<ruby>静态<rt>static</rt></ruby>和<ruby>已生成<rt>generated</rt></ruby>。
|
||||
|
||||
与 [grep 命令][4] 结合，你可以**仅显示正在运行的服务**：
|
||||
与 [grep 命令][4] 结合，你可以仅显示正在运行的服务：
|
||||
|
||||
```
|
||||
sudo systemctl | grep running
|
||||
@ -60,9 +56,9 @@ sudo systemctl | grep running
|
||||
|
||||
现在，你知道了如何引用所有不同的服务，你可以开始主动管理它们。
|
||||
|
||||
**注意：** 命令中的 **<service-name>** 应该用你想管理的服务名代替。（比如：network-manager、ufw 等）
|
||||
**注意：** 下列命令中的 `<service-name>` 应该用你想管理的服务名代替。（比如：network-manager、ufw 等）
|
||||
|
||||
#### 2\. 启动服务
|
||||
#### 2、启动服务
|
||||
|
||||
要在 Linux 中启动服务，你只需使用它的名字：
|
||||
|
||||
@ -70,15 +66,15 @@ sudo systemctl | grep running
|
||||
systemctl start <service-name>
|
||||
```
|
||||
|
||||
#### 3\. 停止服务
|
||||
#### 3、停止服务
|
||||
|
||||
要停止 systemd 服务，可以使用 systemctl 命令的 stop 选项：
|
||||
要停止 systemd 服务，可以使用 `systemctl` 命令的 `stop` 选项：
|
||||
|
||||
```
|
||||
systemctl stop <service-name>
|
||||
```
|
||||
|
||||
#### 4\. 重启服务
|
||||
#### 4、重启服务
|
||||
|
||||
要重启 systemd 服务，可以使用：
|
||||
|
||||
@ -86,7 +82,7 @@ systemctl stop <service-name>
|
||||
systemctl restart <service-name>
|
||||
```
|
||||
|
||||
#### 5\. 检查服务状态
|
||||
#### 5、检查服务状态
|
||||
|
||||
你可以通过打印服务状态来确认你已经成功执行特定操作：
|
||||
|
||||
@ -104,7 +100,7 @@ systemctl status <service-name>
|
||||
|
||||
init 的命令和 systemd 的一样简单。
|
||||
|
||||
#### 1\. 列出所有服务
|
||||
#### 1、列出所有服务
|
||||
|
||||
要列出所有 Linux 服务，使用：
|
||||
|
||||
@ -114,9 +110,9 @@ service --status-all
|
||||
|
||||
![service –status-all][7]
|
||||
|
||||
前面的 **[ – ]** 代表**禁用**，**[ + ]** 代表**启用**。
|
||||
前面的 `[ – ]` 代表**禁用**，`[ + ]` 代表**启用**。
|
||||
|
||||
#### 2\. 启动服务
|
||||
#### 2、启动服务
|
||||
|
||||
要在 Ubuntu 和其他发行版中启动服务，使用命令：
|
||||
|
||||
@ -124,7 +120,7 @@ service --status-all
|
||||
service <service-name> start
|
||||
```
|
||||
|
||||
#### 3\. 停止服务
|
||||
#### 3、停止服务
|
||||
|
||||
停止服务同样简单。
|
||||
|
||||
@ -132,7 +128,7 @@ service <service-name> start
|
||||
service <service-name> stop
|
||||
```
|
||||
|
||||
#### 4\. 重启服务
|
||||
#### 4、重启服务
|
||||
|
||||
如果你想重启服务，命令是：
|
||||
|
||||
@ -140,9 +136,9 @@ service <service-name> stop
|
||||
service <service-name> restart
|
||||
```
|
||||
|
||||
#### 5\. 检查服务状态
|
||||
#### 5、检查服务状态
|
||||
|
||||
此外，要检查是否达到了预期的结果，你可以输出服务**状态**：
|
||||
此外，要检查是否达到了预期的结果，你可以输出服务状态：
|
||||
|
||||
```
|
||||
service <service-name> status
|
||||
@ -152,9 +148,9 @@ service <service-name> status
|
||||
|
||||
![service status][8]
|
||||
|
||||
最重要的是，这将告诉你某项服务是否处于活跃状态（**正在运行**）。
|
||||
最重要的是，这将告诉你某项服务是否处于活跃状态（正在运行）。
|
||||
|
||||
**总结**
|
||||
### 总结
|
||||
|
||||
今天，我详细介绍了两种在 Ubuntu 或任何其他 Linux 系统上管理服务的非常简单的方法。 希望本文对你有所帮助。
|
||||
|
||||
@ -167,7 +163,7 @@ via: https://itsfoss.com/start-stop-restart-services-linux/
|
||||
作者：[Sergiu][a]
|
||||
选题：[lujun9972][b]
|
||||
译者：[geekpi](https://github.com/geekpi)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
校对：[wxy](https://github.com/wxy)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
||||
@ -1,91 +0,0 @@
|
||||
[#]: collector: (lujun9972)
|
||||
[#]: translator: (Morisun029)
|
||||
[#]: reviewer: ( )
|
||||
[#]: publisher: ( )
|
||||
[#]: url: ( )
|
||||
[#]: subject: (5 interview questions every Kubernetes job candidate should know)
|
||||
[#]: via: (https://opensource.com/article/19/12/kubernetes-interview-questions)
|
||||
[#]: author: (Jessica Repka https://opensource.com/users/jrepka)
|
||||
|
||||
5 interview questions every Kubernetes job candidate should know
|
||||
======
|
||||
If you're interviewing people for Kubernetes-related roles, here's what
|
||||
to ask and why it matters.
|
||||
![Pair programming][1]
|
||||
|
||||
Job interviews are hard for people on both sides of the table, but I've discovered that interviewing candidates for Kubernetes-related jobs has seemed especially hard lately. Why, you ask? For one thing, it's hard to find someone who can answer some of my questions. Also, it has been hard to confirm whether they have the right experience, regardless of their answers to my questions.
|
||||
|
||||
I'll skip over my musings on that topic and get to some questions that you should ask of any job candidate who would be working with [Kubernetes][2].
|
||||
|
||||
### What is Kubernetes?
|
||||
|
||||
I've always found this question to be one of the best ones to ask in interviews. I always hear, "I work with Kubernetes," but when I ask, "what is it?" I never get a confident answer.
|
||||
|
||||
My favorite answer is from [Chris Short][3]: "Just an API with some YAML files."
|
||||
|
||||
While he is not wrong, I'll give you a more detailed version. Kubernetes is a portable container orchestration tool that is used to automate the tasks of managing, monitoring, scaling, and deploying containerized applications.
|
||||
|
||||
I've found that "an orchestration tool for deploying containerized applications" is probably as good as you're going to get as an answer, which in my opinion is good enough. While many believe Kubernetes adds a great deal more, overall, it offers many APIs to add to this core feature: container orchestration.
|
||||
|
||||
In my opinion, this is one of the best questions you can ask in an interview, as it at least proves whether the candidate knows what Kubernetes is.
|
||||
|
||||
### What is the difference between a Kubernetes node and a pod?
|
||||
|
||||
This question reveals a great first look at the complexity of Kubernetes. It shifts the conversation to an architectural overview and can lead to many interesting follow-up details. It has also been explained incorrectly to me an innumerable amount of times.
|
||||
|
||||
A [node][4] is the worker machine. This machine can be a virtual machine (VM) or a physical machine, depending on whether you are running on a hypervisor or on bare metal. The node contains services to run containers, including the kubelet, kube-proxy, and container runtime.
|
||||
|
||||
A [pod][5] includes (1) one or more containers (2) with shared network (3) and storage (4) and the specification on how to run the containers deployed together. All four of these details are important. For bonus points, an applicant could mention that, technically, a pod is the smallest deployable unit Kubernetes can create and manage—not a container.
|
||||
|
||||
The best short answer I've received for this question is: "The node is the worker, and the pod is the thing the containers are in." The distinction matters. Most of a Kubernetes administrator's job depends on knowing when to deploy what, and nodes can be very, very expensive, depending on where they are run. I wouldn't want someone deploying nodes over and over when what they needed to do was deploy a bunch of pods.
|
||||
|
||||
### What is kubectl? (And how do you pronounce it?)
|
||||
|
||||
This question is one of my higher priority questions, but it may not be relevant for you and your team. In my organization, we don't use a graphical interface to manage our Kubernetes environments, which means command-line actions are all we do.
|
||||
|
||||
So what is [kubectl][6]? It is the command-line interface to Kubernetes. You can get and set anything from there, from gathering logs and events to editing deployments and secrets. It's always helpful to pop in a random question about how to use this tool to test the interviewee's familiarity with kubectl.
|
||||
|
||||
How do you pronounce it? Well, that's up to you (there's a big disagreement on the matter), but I will gladly point you to this great video presentation by my friend [Waldo][7].
|
||||
|
||||
### What is a namespace?
|
||||
|
||||
I haven't received an answer to this question on multiple interviews. I am not sure that namespaces are used as often in other environments as they are in the organization I work in. I'll give a short answer here: a namespace is a virtual cluster in a pod. This abstraction is what enables you to keep several virtual clusters in various environments for isolation purposes.
|
||||
|
||||
### What is a container?
|
||||
|
||||
It always helps to know what is being deployed in your pod, because what's a deployment without knowing what you're deploying in it? A container is a standard unit of software that packages up code and all its dependencies. Two optional secondary answers I have received and am OK with include: a) a slimmed-down image of an OS and b) an application running in a limited OS environment. Bonus points if you can name orchestration software that uses containers other than [Docker][8], like your favorite public cloud's container service.
|
||||
|
||||
### Other questions
|
||||
|
||||
If you're wondering why I didn't add more to this list of questions, I have an easy answer for you: these are the minimum set of things _you_ should know when you are asking candidates interview questions. The next set of questions should come from a large list of questions based on your specific team, environment, and organization. As you think through these, try to find interesting questions about how technology interacts with each other to see how people think through infrastructure challenges. Think about recent challenges your team had (outages), ask to walk through deployments step-by-step, or about strategies to improve something your team actively wants to improve (like a reduction to deployment time). The less abstract the questions, the more your asking about skills that will actually matter after the interview.
|
||||
|
||||
**[Read more: [How to prepare for a Kubernetes job interview]][9]**
|
||||
|
||||
No two environments will be the same, and this also applies when you are interviewing people. I mix up questions in every interview. I also have a small environment I can use to test interviewees. I always find that answering the questions is the easiest part, and doing the work is the real test you need to give.
|
||||
|
||||
My last bit of advice for anyone giving interviews: If you meet someone who has potential but none of the experience, give them a chance to prove themselves. I wouldn't have the knowledge and experience I have today if someone hadn't seen the potential of what I could do and given me an opportunity.
|
||||
|
||||
What are other important questions to ask interviewees about Kubernetes? Please add your list in the comments.
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://opensource.com/article/19/12/kubernetes-interview-questions
|
||||
|
||||
作者：[Jessica Repka][a]
|
||||
选题：[lujun9972][b]
|
||||
译者：[译者ID](https://github.com/译者ID)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
||||
[a]: https://opensource.com/users/jrepka
|
||||
[b]: https://github.com/lujun9972
|
||||
[1]: https://opensource.com/sites/default/files/styles/image-full-size/public/lead-images/collab-team-pair-programming-code-keyboard.png?itok=kBeRTFL1 (Pair programming)
|
||||
[2]: https://kubernetes.io/
|
||||
[3]: https://twitter.com/ChrisShort
|
||||
[4]: https://kubernetes.io/docs/concepts/architecture/nodes/
|
||||
[5]: https://kubernetes.io/docs/concepts/workloads/pods/pod/
|
||||
[6]: https://kubernetes.io/docs/reference/kubectl/kubectl/
|
||||
[7]: https://opensource.com/article/18/12/kubectl-definitive-pronunciation-guide
|
||||
[8]: https://opensource.com/resources/what-docker
|
||||
[9]: https://enterprisersproject.com/article/2019/2/kubernetes-job-interview-questions-how-prepare
|
||||
@ -0,0 +1,68 @@
|
||||
[#]: collector: (lujun9972)
|
||||
[#]: translator: ( )
|
||||
[#]: reviewer: ( )
|
||||
[#]: publisher: ( )
|
||||
[#]: url: ( )
|
||||
[#]: subject: (10 resources to boost your Git skills)
|
||||
[#]: via: (https://opensource.com/article/19/12/git-resources)
|
||||
[#]: author: (Joshua Allen Holm https://opensource.com/users/holmja)
|
||||
|
||||
10 resources to boost your Git skills
|
||||
======
|
||||
Wrap up the year with a review of the best in Git. Here are the top 10
|
||||
articles about surprising ways you can use Git in the new year.
|
||||
![open source button on keyboard][1]
|
||||
|
||||
As we near the end of 2019, it is time to look back at the top 10 articles we published about Git this year.
|
||||
|
||||
These articles range from use cases and tutorials to some very interesting, if somewhat unconventional, ways to use Git. All of these articles can help you improve your Git skills, but if you really need a Git 101 introduction, be sure to check out our _[Getting started with Git: Terminology 101][2]_ article and download our [Git cheat sheet][3].
|
||||
|
||||
1. _[How GNOME uses Git][4]_ by Molly de Blanc looks at the GNOME project’s adoption of a self-hosted GitLab instance as the GNOME project’s centralized location for contributing to GNOME. De Blanc works in a non-coding position, so her article also explores how the switch to GitLab benefits contributors whose primary role is not writing code.
|
||||
|
||||
2. Ahmad Awais’ _[Emoji-Log: A new way to write Git commit messages][5]_ explains how to use Emoji-Log, "a straightforward, open source Git commit log standard," to write better, more user-friendly, Git commit messages. The article contains an overview of the theory behind Emoji-Log and configuration examples that can be added to **.bashrc, .zshrc, or .gitconfig** to quickly start using Emoji-Log.
|
||||
|
||||
3. In _[Manage your daily schedule with Git][6]_, Seth Kenlon explains how to use Git to manage your calendar. By combining Org mode, Git, and a few other tools, Kenlon describes how to create a Git-based calendar workflow that can be synced across devices.
|
||||
|
||||
4. [_Use Git as the backend for chat_][7] by Seth Kenlon explores another unconventional way to use Git. In this article, he explores GIC, which is a chat client written in Node.js with Git functioning as the backend database. GIC is proof of concept, not something intended for production use, but it provides an interesting example of a really unique way to use Git.
|
||||
|
||||
5. Alan Formy-Duval’s _[A practical learning exercise for Git][8]_ is a chronicle of his effort to improve his Git skills. He shares his experience for others to benefit from what he learned, and Git novices will gain a lot from this excellent overview of Git’s core functionality.
|
||||
|
||||
6. _[How writers can get work done better with Git][9]_ by Seth Kenlon looks at how writers can benefit from a Git-based workflow. The article explains how to use Git and Atom to write using Markdown. By following the examples in this article, writers can easily add a complex revision control system to their writing workflow.
|
||||
|
||||
7. In _[How to use Magit to manage Git projects][10]_, Sachin Patil explains how to use Emacs’ Magit extension to manage Git repositories. The article provides clear examples of how to perform a selection of key Git tasks inside Emacs. The examples are supported by screenshots illustrating the various tasks.
|
||||
|
||||
8. _[Move your dotfiles to version control][11]_ by Matthew Broberg shows how to use Git to store the dotfiles in your home directory. Storing your dotfiles in a Git repository makes it easier to share your system configuration between computers and, if you so choose, share your configurations with others. The article does come with a warning about what not to share because sharing the wrong dotfiles can expose others.
|
||||
|
||||
9. Austin Dewey’s _[4 secrets management tools for Git encryption][12]_ compares Git-crypt, BlackBox, SOPS, and Transcrypt in this article examining tools for storing secrets in Git. The article covers four major areas: encryption types supported, the goals of each project, the projects’ workflows and differences, and other features.
|
||||
|
||||
10. _[Run a server with Git][13]_ by Seth Kenlon explains how Gitolite can be used to manage a Git server. Gitolite is "a backend application managing the fiddly bits" involved in using Git to manage a Git server. The article demonstrates how to install, configure, and use Gitolite, with clear examples detailing each step the process.
|
||||
|
||||
|
||||
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://opensource.com/article/19/12/git-resources
|
||||
|
||||
作者：[Joshua Allen Holm][a]
|
||||
选题：[lujun9972][b]
|
||||
译者：[译者ID](https://github.com/译者ID)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
||||
[a]: https://opensource.com/users/holmja
|
||||
[b]: https://github.com/lujun9972
|
||||
[1]: https://opensource.com/sites/default/files/styles/image-full-size/public/lead-images/button_push_open_keyboard_file_organize.png?itok=KlAsk1gx (open source button on keyboard)
|
||||
[2]: https://opensource.com/article/19/2/git-terminology
|
||||
[3]: https://opensource.com/downloads/cheat-sheet-git
|
||||
[4]: https://opensource.com/article/19/10/how-gnome-uses-git
|
||||
[5]: https://opensource.com/article/19/2/emoji-log-git-commit-messages
|
||||
[6]: https://opensource.com/article/19/4/calendar-git
|
||||
[7]: https://opensource.com/article/19/4/git-based-chat
|
||||
[8]: https://opensource.com/article/19/5/practical-learning-exercise-git
|
||||
[9]: https://opensource.com/article/19/4/write-git
|
||||
[10]: https://opensource.com/article/19/1/how-use-magit
|
||||
[11]: https://opensource.com/article/19/3/move-your-dotfiles-version-control
|
||||
[12]: https://opensource.com/article/19/2/secrets-management-tools-git
|
||||
[13]: https://opensource.com/article/19/4/server-administration-git
|
||||
@ -0,0 +1,71 @@
|
||||
[#]: collector: (lujun9972)
|
||||
[#]: translator: ( )
|
||||
[#]: reviewer: ( )
|
||||
[#]: publisher: ( )
|
||||
[#]: url: ( )
|
||||
[#]: subject: (The importance of consistency in your Python code)
|
||||
[#]: via: (https://opensource.com/article/19/12/zen-python-consistency)
|
||||
[#]: author: (Moshe Zadka https://opensource.com/users/moshez)
|
||||
|
||||
The importance of consistency in your Python code
|
||||
======
|
||||
This is part of a special series about the Zen of Python focusing on the
|
||||
12th, 13th, and 14th principles: the roles of ambiguity and obviousness.
|
||||
![Two animated computers waving one missing an arm][1]
|
||||
|
||||
The principle of least surprise is [a guideline][2] when designing user interfaces. It says that when the user performs an action, the program should do whatever would surprise the user the least. This is for the same reason kids love reading the same book over and over again: there is nothing more comforting to people than the ability to predict and have those predictions come true.
|
||||
|
||||
A critical insight in the development of the [ABC language][3], Python's inspiration, was that programming languages are user interfaces and need to be designed with the same tools that UI designers use. Thankfully, since then, more languages have adopted the concepts of affordance and ergonomics from UI design, even if they apply them less strictly.
|
||||
|
||||
This brings us to the next three principles in the [Zen of Python][4].
|
||||
|
||||
### In the face of ambiguity, refuse the temptation to guess.
|
||||
|
||||
What should the result of **1 + "1"** be? Both **"11"** and **2** would be valid guesses. This expression is _ambiguous_: there is no single thing it can do that would not be a surprise to at least some people.
|
||||
|
||||
Some languages choose to guess. In JavaScript, the result is **"11"**. In Perl, the result is **2**. In C, naturally, the result is the empty string. In the face of ambiguity, JavaScript, Perl, and C all guess.
|
||||
|
||||
In Python, this raises a **TypeError**: an error that is not silent. It is atypical to catch **TypeError**: it will usually terminate the program or at least the current task (for example, in most web frameworks, it will terminate the handling of the current request).
|
||||
|
||||
Python refuses to guess what **1 + "1"** means. The programmer is forced to write code with clear intention: either **1 + int("1")**, which would be **2**; or **str(1) + "1"**, which would be **"11"**; or **"1"[1:]**, which would be an empty string. By refusing to guess, Python makes programs more predictable.
|
||||
|
||||
### There should be one—and preferably only one—obvious way to do it.
|
||||
|
||||
Prediction also goes the other way. Given a task, can you predict the code that will be written to achieve it? It is impossible, of course, to predict perfectly. Programming, after all, is a creative task.
|
||||
|
||||
However, there is no reason to intentionally provide multiple, redundant ways to achieve the same thing. There is a sense in which some solutions are "better" or "more Pythonic."
|
||||
|
||||
Part of the appreciation for the Pythonic aesthetic is that it is OK to have healthy debates about which solution is better. It is even OK to disagree and keep programming. It is even OK to agree to disagree for the sake of harmony. But beneath it all, there has to be a feeling that, eventually, the right solution will come to light. There must be the hope that eventually we can live in true harmony by agreeing on the best way to achieve a goal.
|
||||
|
||||
### Although that way may not be obvious at first (unless you're Dutch).
|
||||
|
||||
This is an important caveat: It is often _not_ obvious, at first, what is the best way to achieve a task. Ideas are evolving. _Python_ is evolving. The best way to read a file block-by-block is, probably, to wait until Python 3.8 and use the [walrus operator][5].
|
||||
|
||||
This common task, reading a file block-by-block, did not have a "single best way to do it" for almost _30 years_ of Python's existence.
|
||||
|
||||
When I started using Python in 1998 with Python 1.5.2, there was no single best way to read a file line-by-line. For many years, the best way to know if a dictionary had a key was to use **.haskey**, until the **in** operator became the best way.
|
||||
|
||||
It is only by appreciating that sometimes, finding the one (and only one) way of achieving a goal can take 30 years of trying out alternatives that Python can keep aiming to find those ways. This view of history, where 30 years is an acceptable time for something to take, often feels foreign to people in the United States, when the country has existed for just over 200 years.
|
||||
|
||||
The Dutch, whether it's Python creator [Guido van Rossum][6] or famous computer scientist [Edsger W. Dijkstra][7], have a different worldview according to this part of the Zen of Python. A certain European appreciation for time is essential to appreciate it.
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://opensource.com/article/19/12/zen-python-consistency
|
||||
|
||||
作者：[Moshe Zadka][a]
|
||||
选题：[lujun9972][b]
|
||||
译者：[译者ID](https://github.com/译者ID)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
||||
[a]: https://opensource.com/users/moshez
|
||||
[b]: https://github.com/lujun9972
|
||||
[1]: https://opensource.com/sites/default/files/styles/image-full-size/public/lead-images/rh_003499_01_other11x_cc.png?itok=I_kCDYj0 (Two animated computers waving one missing an arm)
|
||||
[2]: https://www.uxpassion.com/blog/the-principle-of-least-surprise/
|
||||
[3]: https://en.wikipedia.org/wiki/ABC_(programming_language)
|
||||
[4]: https://www.python.org/dev/peps/pep-0020/
|
||||
[5]: https://www.python.org/dev/peps/pep-0572/#abstract
|
||||
[6]: https://en.wikipedia.org/wiki/Guido_van_Rossum
|
||||
[7]: http://en.wikipedia.org/wiki/Edsger_W._Dijkstra
|
||||
@ -0,0 +1,57 @@
|
||||
[#]: collector: (lujun9972)
|
||||
[#]: translator: ( )
|
||||
[#]: reviewer: ( )
|
||||
[#]: publisher: ( )
|
||||
[#]: url: ( )
|
||||
[#]: subject: (Top CI/CD resources to set you up for success)
|
||||
[#]: via: (https://opensource.com/article/19/12/cicd-resources)
|
||||
[#]: author: (Jessica Cherry https://opensource.com/users/jrepka)
|
||||
|
||||
Top CI/CD resources to set you up for success
|
||||
======
|
||||
Continuous integration and continuous deployment were key topics in 2019
|
||||
as organizations look to achieve seamless, flexible, and scalable
|
||||
deployments.
|
||||
![Plumbing tubes in many directions][1]
|
||||
|
||||
This has been a fantastic year for continuous integration/continuous deployment (CI/CD) and the world of DevOps. Opensource.com authors shared how they're moving toward agile and scrum as they focus on seamless, flexible, and scalable deployments. Here are some of the big themes in the CI/CD articles we published this year.
|
||||
|
||||
### Learning and improving your CI/CD skills
|
||||
|
||||
Some of our favorite articles focus on hands-on CI/CD experience and cover a lot of ground as they do. The place to start is always with [Jenkins][2] pipelines, and Bryant Son's [_Building CI/CD pipelines with Jenkins_][3] will give you enough experience to get started building your first pipelines. Daniel Oh's [_Automate user acceptance testing with your DevOps pipeline_][4] provides great information on acceptance testing, including various CI/CD applications you can use for testing in its own right. And my article on [_Security scanning your DevOps pipeline_][5] is a very short, to the point tutorial on how to set up security in a pipeline using the Jenkins platform.
|
||||
|
||||
### Delivery workflow
|
||||
|
||||
While learning how to use and improve your skills with CI/CD, the workflow matters, especially when it comes to pipelines, as Jithin Emmanuel shares in [_Screwdriver: A scalable build platform for continuous delivery_][6]. Emily Burns explains having the flexibility to build exactly what you need with your CI/CD workflow in [_Why Spinnaker matters to CI/CD_][7]. And Willy-Peter Schaub extols the idea of creating a unified pipeline for everything to build consistently in [_One CI/CD pipeline per product to rule them all_][8]. These articles will give you a good sense of what happens after you onboard team members to the workflow process.
|
||||
|
||||
### How CI/CD affects organizations
|
||||
|
||||
2019 was also the year of recognizing CI/CD's business impact and how it affects day-to-day operations. Agnieszka Gancarczyk shares the results of Red Hat's [_Small Scale Scrum vs. Large Scale Scrum_][9] survey, including respondents' differing opinions on scrums, the agile movement, and the impact on teams. Will Kelly covers [_How continuous deployment impacts the entire organization_][10], including the importance of open communication, and Daniel Oh emphasizes the importance of metrics and observability in [_3 types of metric dashboards for DevOps teams_][11]. Last, but far from least, Ann Marie Fred's great article [_Don't test in production? Test in production!_][12] details why it's important for you to test in production—before your customers do.
|
||||
|
||||
We are thankful to the many contributing authors who shared their insights with Opensource.com readers in 2019, and I look forward to learning more from them about the evolution of CI/CD in 2020.
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://opensource.com/article/19/12/cicd-resources
|
||||
|
||||
作者：[Jessica Cherry][a]
|
||||
选题：[lujun9972][b]
|
||||
译者：[译者ID](https://github.com/译者ID)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
||||
[a]: https://opensource.com/users/jrepka
|
||||
[b]: https://github.com/lujun9972
|
||||
[1]: https://opensource.com/sites/default/files/styles/image-full-size/public/lead-images/plumbing_pipes_tutorial_how_behind_scenes.png?itok=F2Z8OJV1 (Plumbing tubes in many directions)
|
||||
[2]: https://jenkins.io/
|
||||
[3]: https://opensource.com/article/19/9/intro-building-cicd-pipelines-jenkins
|
||||
[4]: https://opensource.com/article/19/4/devops-pipeline-acceptance-testing
|
||||
[5]: https://opensource.com/article/19/7/security-scanning-your-devops-pipeline
|
||||
[6]: https://opensource.com/article/19/3/screwdriver-cicd
|
||||
[7]: https://opensource.com/article/19/8/why-spinnaker-matters-cicd
|
||||
[8]: https://opensource.com/article/19/7/cicd-pipeline-rule-them-all
|
||||
[9]: https://opensource.com/article/19/3/small-scale-scrum-vs-large-scale-scrum
|
||||
[10]: https://opensource.com/article/19/7/organizational-impact-continuous-deployment
|
||||
[11]: https://opensource.com/article/19/7/dashboards-devops-teams
|
||||
[12]: https://opensource.com/article/19/5/dont-test-production
|
||||
@ -0,0 +1,88 @@
|
||||
[#]: collector: (lujun9972)
|
||||
[#]: translator: (Morisun029)
|
||||
[#]: reviewer: ( )
|
||||
[#]: publisher: ( )
|
||||
[#]: url: ( )
|
||||
[#]: subject: (5 interview questions every Kubernetes job candidate should know)
|
||||
[#]: via: (https://opensource.com/article/19/12/kubernetes-interview-questions)
|
||||
[#]: author: (Jessica Repka https://opensource.com/users/jrepka)
|
||||
|
||||
每个 Kubernetes 应聘者应该知道的5个面试题
|
||||
======
|
||||
如果你要面试Kubernetes相关的应聘者，这里给出了要提问的问题以及这些问题的重要性。
|
||||
![Pair programming][1]
|
||||
|
||||
面试对面试官及候选人来说都很不容易。最近，我发现面试 Kubernetes 相关工作的候选人似乎尤其困难。为什么呢？一方面，很难找到可以回答他们问题的人。而且，不管回答者回答的怎样，都很难确定他们是否有正确的经验。
|
||||
|
||||
跳过这个问题，让我们来看看面试[Kubernetes][2]求职者时应该提问的一些问题。
|
||||
|
||||
### Kubernetes 是什么？
|
||||
|
||||
我发现这个问题是面试中最好的问题之一。我经常听到有人说“我用Kubernetes工作”，但是当我问道“Kubernetes 是什么时，从来都没有得到过一个满意答案。
|
||||
|
||||
我最喜欢克里斯•肖特[Chris Short][3]给出的答案：“Kubernetes 就是带有一些 YAML 文件的 API 。”
|
||||
|
||||
虽然他的回答没有错，但我会给你更详细的解释。 Kubernetes 是一个便携式容器编排工具，用于自动执行管理，监控，扩展和部署容器化应用程序。
|
||||
|
||||
我认为“用于部署容器化应用程序的编排工具”这个回答可能与你期望的答案差不多了。能回答出这个，我觉得已经很不错了。尽管许多人相信 Kubernetes 可以增加很多，但总的来说，它提供了许多API来增加其核心功能：容器编排。
|
||||
|
||||
我认为，这是你在面试中可以提问的最好的问题之一，因为它至少证明了候选人是否知道 Kubernetes 是什么。
|
||||
|
||||
### Kubernetes 的 node(节点)和 Pod 有什么区别?
|
||||
|
||||
该问题揭示了候选人对 Kubernetes 复杂性的初步了解。它将对话转换为体系结构概述，并可能导向许多有趣的后续细节问题。我已经听到了无数次关于该问题的错误解释了。
|
||||
|
||||
[node][4] 是工作计算机。该计算机可以是虚拟机（VM）或物理计算机，具体取决于你是在虚拟机监控程序上运行还是在裸机上运行。该节点包含用于运行容器的服务，包括 kubelet，kube-proxy 和容器运行时。
|
||||
|
||||
[pod][5] pod 包括（1）一个或多个具有共享网络（3）和存储（4）的容器（2）以及有关如何运行一起部署的容器的规范。这四个细节都很重要。更进一步，申请人应从技术层面解释，pod 是Kubernetes 可以创建和管理的最小可部署单元，而不是容器。
|
||||
|
||||
对于这个问题，我听到的最好的简答是：“node 是计算机，而 pod 是容器中的东西。” 区别很重要。 Kubernetes 管理员的大部分工作是知道什么时间要部署什么，而节点可能非常非常昂贵，具体取决于它们的运行位置。我不希望有人一遍又一遍地部署节点，他们需要做的就是部署一堆Pod。
|
||||
|
||||
### kubectl 是什么？ （你怎么发音？）
|
||||
|
||||
这个问题是我的优先级中较高的问题之一，但可能与你和你的团队无关。在我的团队中，我们不会使用图形化界面来管理Kubernetes环境，我们使用命令行操作。
|
||||
|
||||
那么什么是[kubectl][6]？它是 Kubernetes 的命令行界面。你可以从该界面获取并设置任何内容，从收集日志和事件到编辑部署环境和机密文件。随机提问候选人关于如何使用此工具对测试候选人对 kubectl 的熟悉度是很有帮助的。
|
||||
|
||||
你是怎么读的？好吧，你随便吧（对此有很大的分歧），但是我很高兴向你介绍我朋友[Waldo][7]的精彩视频演示。
|
||||
|
||||
### 名称空间是什么？
|
||||
|
||||
在多次面试中，我都没有得到关于这个问题的答案。我不确定在其他环境中使用的名称空间是否会在我所在的团队经常使用。我在这里给出一个简短的答案：名称空间是Pod中的虚拟集群。这种抽象可以使你将多个虚拟群集保留在各种环境中以此来进行隔离。
|
||||
|
||||
### 容器是什么?
|
||||
了解 Pod 中正在部署的内容总是有帮助的，因为如果都不知道其中部署的是什么，何谈部署？容器是打包代码及其所有依赖项的软件的标准单元。我收到了两个可以接收的答案，其中包括：a）精简的操作系统映像，以及b）在受限的 OS 环境中运行的应用程序。如果你可以命名使用[Docker][8]以外的其他容器的编排软件（例如你最喜欢的公共云的容器服务），则可以得到加分。
|
||||
|
||||
### 其他问题
|
||||
如果你想知道为什么我没有在此问题列表中添加更多问题，那么我可以给出一个简单的答案：我所列出的这些问题是在面试候选人时应了解的最基本的问题。接下来的问题应该是基于具体的团队、环境及组织。如果你想知道为什么我没有在此问题列表中添加更多问题，那么我可以给出一个简单的答案：我所列出的这些问题是在面试候选人时应了解的最基本的问题。接下来的问题应该是基于具体的团队、环境及组织。
|
||||
|
||||
**[阅读更多：如何准备 Kubernetes 相关的面试？]][9]**
|
||||
|
||||
没有两个环境是完全相同的。这也适用于面试中。我在每次面试中都会混合提问。 我也有一个测试面试者的小环境。我经常发现回答问题是最容易的部分，而你所做的工作才是对你的真正的考验。
|
||||
|
||||
我给面试官的最后一点建议是：如果你遇到一个很有潜力但没有经验的候选人时，请给他们一个证明自己的机会。如果当初没有人看到我的潜力，没有给我机会的话，我不会拥有今天的知识和经验。
|
||||
|
||||
还有哪些重要的问题？请留言告诉我们。
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://opensource.com/article/19/12/kubernetes-interview-questions
|
||||
|
||||
作者：[Jessica Repka][a]
|
||||
选题：[lujun9972][b]
|
||||
译者：[Morisun029](https://github.com/译者ID)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
||||
[a]: https://opensource.com/users/jrepka
|
||||
[b]: https://github.com/lujun9972
|
||||
[1]: https://opensource.com/sites/default/files/styles/image-full-size/public/lead-images/collab-team-pair-programming-code-keyboard.png?itok=kBeRTFL1 (Pair programming)
|
||||
[2]: https://kubernetes.io/
|
||||
[3]: https://twitter.com/ChrisShort
|
||||
[4]: https://kubernetes.io/docs/concepts/architecture/nodes/
|
||||
[5]: https://kubernetes.io/docs/concepts/workloads/pods/pod/
|
||||
[6]: https://kubernetes.io/docs/reference/kubectl/kubectl/
|
||||
[7]: https://opensource.com/article/18/12/kubectl-definitive-pronunciation-guide
|
||||
[8]: https://opensource.com/resources/what-docker
|
||||
[9]: https://enterprisersproject.com/article/2019/2/kubernetes-job-interview-questions-how-prepare
|
||||
@ -1,218 +0,0 @@
|
||||
[#]: collector: (lujun9972)
|
||||
[#]: translator: (geekpi)
|
||||
[#]: reviewer: ( )
|
||||
[#]: publisher: ( )
|
||||
[#]: url: ( )
|
||||
[#]: subject: (Build a retro Apple desktop with the Linux MLVWM)
|
||||
[#]: via: (https://opensource.com/article/19/12/linux-mlvwm-desktop)
|
||||
[#]: author: (Seth Kenlon https://opensource.com/users/seth)
|
||||
|
||||
使用 Linux MLVWM 打造复古苹果桌面
|
||||
======
|
||||
本文是 24 天 Linux 桌面特别系列的一部分。如果老式的苹果电脑用开源 POSIX 构建如何？你可以通过构建类 Macintosh 虚拟窗口管理器来实现。
|
||||
![Person typing on a 1980's computer][1]
|
||||
|
||||
想象一下进入另外一个历史，Apple II GS 和 MacOS 7 是基于开源 [POSIX][2] 构建的，它使用了与现代 Linux 相同的所有约定，例如纯文本配置文件和模块化系统设计。这样的操作系统将为其用户带来什么？你可以使用[类 Macintosh 虚拟窗口管理器（MLVWM）][3]来回答这些问题（甚至更多！）。
|
||||
|
||||
![MLVWM running on Slackware 14.2][4]
|
||||
|
||||
### 安装 MLVWM
|
||||
|
||||
MLVWM 安装并不容易，并且可能不在发行版的软件仓库中。如果你有时间理解翻译不佳的 README 文件，编辑一些配置文件，收集并调整一些旧的 **.xpm**图像，编辑一两个 Xorg 选项，那么你就可以体验 MLVWM。否则，这是一个新奇的窗口管理器，其最新版本可以追溯到 2000 年。
|
||||
|
||||
|
||||
要编译 MLVWM，你必须安装 **imake**，它提供 **xmkmf** 命令。你可以从发行版的软件仓库中安装 imake，也可以直接从 [Freedesktop.org][5] 获得。假设你已经有 **xmkmf**命令，请进入包含 MLVWM 源码的目录，然后运行以下命令进行构建：
|
||||
|
||||
|
||||
```
|
||||
$ xmkmf -a
|
||||
$ make
|
||||
```
|
||||
|
||||
构建后，编译后的 **mlvwm** 二进制文件位于 **mlvwm** 目录中。将其移动到[你的 PATH ][6]的任何位置：
|
||||
|
||||
|
||||
```
|
||||
`$ mv mlvwm/mlvwm /usr/local/bin/`
|
||||
```
|
||||
|
||||
#### 编辑配置文件
|
||||
|
||||
现在已经安装 MLVWM，但是如果不调整几个配置文件并仔细排列所需的图像文件，它将无法正确启动。示例配置文件位于你下载的源代码的 **sample_rc** 目录中。将文件 **Mlvwm-Netscape** 和 **Mlvwm-Xterm** 复制到你的主目录：
|
||||
|
||||
|
||||
```
|
||||
`$ cp sample_rc/Mlvwm-{Netscape,Xterm} $HOME`
|
||||
```
|
||||
|
||||
将 **Mlvwmrc** 移动到 **$HOME/.mlvwmrc**（是的，即使示例文件的名称看似是大写字母，但你也必须使用小写的 “m”）：
|
||||
|
||||
|
||||
```
|
||||
`$ cp sample_rc/Mlvwmrc $HOME/.mlvwmrc`
|
||||
```
|
||||
|
||||
打开 **.mlwmrc** 并找到第 54-55 行，它们定义了 MLVWM 在菜单和 UI 中使用的像素图的路径（“IconPath”）：
|
||||
|
||||
|
||||
```
|
||||
# Set icon search path. It needs before "Style".
|
||||
IconPath /usr/local/include/X11/pixmaps:/home2/tak/bin/pixmap
|
||||
```
|
||||
|
||||
调整路径以匹配你填充图像的路径（我建议使用 **$HOME/.local/share/pixmaps**）。MLVWM 不提供像素图，因此需要你提供构建桌面所需图标。
|
||||
|
||||
即使你有位于系统其他位置的像素图（例如 **/usr/share/pixmaps**)），也要这样做，因为你需要调整像素图的大小，你可能也不想在系统范围内执行此操作。
|
||||
|
||||
|
||||
```
|
||||
# Set icon search path. It needs before "Style".
|
||||
IconPath /home/seth/.local/share/pixmaps
|
||||
```
|
||||
|
||||
#### 选择像素图
|
||||
|
||||
你已将 **.local/share/pixmaps** 目录定义为像素图源路径，但是该目录和图像均不存在。创建目录：
|
||||
|
||||
|
||||
```
|
||||
`$ mkdir -p $HOME/.local/share/pixmaps`
|
||||
```
|
||||
|
||||
现在，配置文件将图像分配给菜单项和 UI 元素，但是系统中不存在这些图像。要解决此问题，请通读配置文件并找到每个 **.xpm** 图像。对于配置中列出的每个图像，将具有相同文件名的图像（或更改配置文件中的文件名）添加到你的 IconPath 目录。
|
||||
|
||||
**.mlvwmrc** 文件的注释很好，因此你可以大致了解要编辑的内容。无论如何，这只是第一步。你可以随时回来更改桌面外观。
|
||||
|
||||
这有些例子
|
||||
|
||||
此代码块设置屏幕左上角的图标：
|
||||
|
||||
```
|
||||
# Register the menu
|
||||
Menu Apple, Icon label1.xpm, Stick
|
||||
```
|
||||
|
||||
**label1.xpm** 图像实际上在源代码的 **pixmap**目录中，但我更喜欢使用来自 **/usr/share/pixmaps** 的 **Penguin.xpm**（在 Slackware 上）。无论使用什么，都必须将自定义像素图放在 **~/.local/share/pixmaps** 中，并在配置中更改像素图的名称，或者重命名像素图以匹配配置文件中当前的名称。
|
||||
|
||||
此代码块定义了左侧菜单中列出的应用：
|
||||
|
||||
|
||||
```
|
||||
"About this Workstation..." NonSelect, Gray, Action About
|
||||
"" NonSelect
|
||||
"Terminal" Icon mini-display.xpm, Action Exec "kterm" exec kterm -ls
|
||||
"Editor" Action Exec "mule" exec mule, Icon mini-edit.xpm
|
||||
"calculator" Action Exec "xcal" exec xcalc, Icon mini-calc.xpm
|
||||
END
|
||||
```
|
||||
|
||||
通过遵循与配置文件中相同的语法，你可以自定义像素图并将自己的应用添加到菜单中（例如，我将 **mule** 更改为 **emacs**）。 这是你在 MLVWM GUI 中打开应用的入口，因此请列出你要快速访问的所有内容。你可能还希望包括指向 **/usr/share/applications** 文件夹的快捷方式。
|
||||
|
||||
|
||||
```
|
||||
`"Applications" Icon Penguin.xpm, Action Exec "thunar /usr/share/applications" exec thunar /usr/share/applications`
|
||||
```
|
||||
|
||||
完成编辑配置文件并将自己的图像添加到 IconPath 目录后，必须将所有像素图的大小都调整为大约 16x16 像素。（MLVWM 的默认设置不一致，因此存在变化空间。）你可以使用 ImageMagick 进行批量操作：
|
||||
|
||||
|
||||
```
|
||||
`$ for i in ~/.local/share/mlvwm-pixmaps/*xpm ; do convert -resize '16x16^' $i; done`
|
||||
```
|
||||
|
||||
### 启动 MLVWM
|
||||
|
||||
最简单的运行 MLVWM 的方式是让 Xorg 完成大部分工作。首先，你必须创建一个 **$HOME/.xinitrc** 文件。我从 Slackware 复制了这个，它也是从 Xorg 来的：
|
||||
|
||||
|
||||
```
|
||||
#!/bin/sh
|
||||
# $XConsortium: xinitrc.cpp,v 1.4 91/08/22 11:41:34 rws Exp $
|
||||
|
||||
userresources=$HOME/.Xresources
|
||||
usermodmap=$HOME/.Xmodmap
|
||||
sysresources=/etc/X11/xinit/.Xresources
|
||||
sysmodmap=/etc/X11/xinit/.Xmodmap
|
||||
|
||||
# merge in defaults and keymaps
|
||||
|
||||
if [ -f $sysresources ]; then
|
||||
xrdb -merge $sysresources
|
||||
fi
|
||||
|
||||
if [ -f $sysmodmap ]; then
|
||||
xmodmap $sysmodmap
|
||||
fi
|
||||
|
||||
if [ -f $userresources ]; then
|
||||
xrdb -merge $userresources
|
||||
fi
|
||||
|
||||
if [ -f $usermodmap ]; then
|
||||
xmodmap $usermodmap
|
||||
fi
|
||||
|
||||
# Start the window manager:
|
||||
if [ -z "$DESKTOP_SESSION" -a -x /usr/bin/ck-launch-session ]; then
|
||||
exec ck-launch-session /usr/local/bin/mlvwm
|
||||
else
|
||||
exec /usr/local/bin/mlvwm
|
||||
fi
|
||||
```
|
||||
|
||||
根据此文件，**startx** 命令的默认操作是启动 MLVWM。但是，你的发行版可能对于图形服务器启动（或被终止重新启动）时会发生的情况有其他做法，因此此文件可能对你没有什么帮助。在许多发行版上，你可以添加 **.desktop** 文件到 **/usr/share/xsessions** 中，以将其列在 GDM 或 KDM 菜单中，因此创建名为 **mlvwm.desktop** 的文件并输入：
|
||||
|
||||
|
||||
```
|
||||
[Desktop Entry]
|
||||
Name=Mlvwm
|
||||
Comment=Macintosh-like virtual window manager
|
||||
Exec=/usr/local/bin/mlvwm
|
||||
TryExec=ck-launch-session /usr/local/bin/mlvwm
|
||||
Type=Application
|
||||
```
|
||||
|
||||
从桌面会话注销并重新登录到 MLVWM。默认情况下，会话管理器（KDM、GDM 或 LightDM，具体取决于你的设置）将继续登录到以前的桌面，因此在登录之前必须覆盖它。
|
||||
|
||||
对于 GDM：
|
||||
|
||||
![][7]
|
||||
|
||||
对于 SDDM：
|
||||
|
||||
![][8]
|
||||
|
||||
#### 强制启动
|
||||
|
||||
如果 MLVWM 无法启动，请尝试安装 XDM，这是一个轻量级会话管理器，它不会查询 **/usr/share/xsessions** 的内容，而是执行经过身份验证用户的所有 **.xinitrc** 操作。
|
||||
|
||||
![MLVWM][9]
|
||||
|
||||
### 打造自己的复古苹果
|
||||
|
||||
MLVWM 桌面未经打磨、不完美、准确且充满乐趣。你看到的许多菜单项都是未实现的，但你可以使它们变得活跃且有意义。
|
||||
|
||||
这是一次让你时光倒流，改变历史，让老式苹果系列电脑成为开源堡垒的机会。成为一名修正主义者，设计你自己的复古苹果桌面，最重要的是，它有乐趣。
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://opensource.com/article/19/12/linux-mlvwm-desktop
|
||||
|
||||
作者：[Seth Kenlon][a]
|
||||
选题：[lujun9972][b]
|
||||
译者：[geekpi](https://github.com/geekpi)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
||||
[a]: https://opensource.com/users/seth
|
||||
[b]: https://github.com/lujun9972
|
||||
[1]: https://opensource.com/sites/default/files/styles/image-full-size/public/lead-images/1980s-computer-yearbook.png?itok=eGOYEKK- (Person typing on a 1980's computer)
|
||||
[2]: https://opensource.com/article/19/7/what-posix-richard-stallman-explains
|
||||
[3]: http://www2u.biglobe.ne.jp/~y-miyata/mlvwm.html
|
||||
[4]: https://opensource.com/sites/default/files/uploads/advent-mlvwm-file.jpg (MLVWM running on Slackware 14.2)
|
||||
[5]: http://cgit.freedesktop.org/xorg/util/imake
|
||||
[6]: https://opensource.com/article/17/6/set-path-linux
|
||||
[7]: https://opensource.com/sites/default/files/advent-gdm_2.jpg
|
||||
[8]: https://opensource.com/sites/default/files/advent-kdm_1.jpg
|
||||
[9]: https://opensource.com/sites/default/files/uploads/advent-mlvwm-chess.jpg (MLVWM)
|
||||
Loading…
Reference in New Issue
Block a user