在 UNIX 中，一切皆文件 #4225
Merged
在 UNIX 中，一切皆文件 #4225
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Closed
|
@leviding 对了，这个并不属于iOS标签，我硬着头皮翻完了😰…… |
|
@pmwangyang 好的，再遇到这种情况，可以不硬着头皮翻译，可以申请不翻译或者换一个，及时沟通都可以的哈 |
|
校对认领 |
|
@yqian1991 好的呢 🍺 |
|
校对认领 |
|
@sisibeloved 妥妥哒 🍻 |
sisibeloved
reviewed
Jul 31, 2018
|
|
||
| The UNIX operating system crystallizes a couple of unifying ideas and concepts that shaped its design, user interface, culture and evolution. One of the most important of these is probably the mantra: “everything is a file”, widely regarded as one of the defining points of UNIX. | ||
| 为了有计划的发展架构设计、界面、文化和开发路线，UNIX系统明确了一系列统一的概念和创想。 |
| * A Modular User Mode File System for BSD | ||
| * “Self-Healing in Modern Operating Systems” by Michael W. Shapiro for a better understanding of Solaris contracts. | ||
| * 一本了不起的书 —— 《The Art of UNIX Programming》，Eric S. Raymond 著。 | ||
| * “The Elements of Operating-System Style” 和 “Problems in the Design of UNIX” 两章对本文有很大帮助。 |
There was a problem hiding this comment.
大部分修改了，有少部分比如“The Linux Information Project”并非图书或文章，我觉得还是方引号比较适合：「Linux 情报项目」。
| 3. For more details see this wikipedia entry | ||
| 4. This concept also eventually made its way back to UNIX in the for ofunionfs | ||
| 5. For example of current activity in this arena, check out unionfs, portalfs andobjfs for instance. | ||
| 1. 想知道更多关于 UNIX 操作系统的背景故事，请阅读维基百科[入口](https://zh.wikipedia.org/wiki/UNIX)（译者注：需科学上网）。 |
There was a problem hiding this comment.
角标的超链接无效，可以用<span id="note1"></span>包裹起来
| 4. This concept also eventually made its way back to UNIX in the for ofunionfs | ||
| 5. For example of current activity in this arena, check out unionfs, portalfs andobjfs for instance. | ||
| 1. 想知道更多关于 UNIX 操作系统的背景故事，请阅读维基百科[入口](https://zh.wikipedia.org/wiki/UNIX)（译者注：需科学上网）。 | ||
| 2. 文件描述符只是存取一个文件的抽象键，文件描述符通常是整型值并且管理啊难道一个打开的文件。 |
|
|
||
| This key design principle consists of providing a unified paradigm for accessing a wide range of input/output resources: documents, directories, hard-drives, CD-Roms, modems, keyboards, printers, monitors, terminals and even some inter-process and network communications. The trick is to provide a common abstraction for all of these resources, each of which the UNIX fathers called a “file”. Since every “file” is exposed through the same API1, you can use the same set of basic commands to read/write to a disk, keyboard, document or network device. | ||
| 最主要的设计原则是提供一个访问大范围输入/输出资源（包括文件、文件夹、硬盘、CD-ROM、调制解调器、键盘、打印机、显示器、终端机甚至跨进程和网络通讯）的统一的范例。窍门是提供一个所有这些资源的抽象对象，UNIX 之父把这个对象叫做「文件」。因为每个「文件」都暴露相同的 API<sup><a href="#note1">[1]</a></sup>，所以你可以用同一套命令来读写/操作磁盘、键盘、文件或网络设备。 |
There was a problem hiding this comment.
『因为每个「文件」都暴露相同的 API』 => 『因为所有「文件」都由同一个 API 暴露』
| * Wikipedia 上的 “UNIX File Types”。 | ||
| * 《Understanding UNIX Concepts》，USAIL (UNIX System Administration Independent Learning) 著。 | ||
| * 《文件系统层级标准》。 | ||
| * 《proc 文件系统》，Redhat 著。 |
There was a problem hiding this comment.
Redhat 是一家公司名，其实这边好几行引用的并不像一本书或一篇文章，而是出处的一个概括，我对此也了解不深，需要专业人士来指正。
『《proc 文件系统》，Redhat 著』 => 『Redhat 出品的 proc 文件系统』
There was a problem hiding this comment.
好的，这块粗心了没注意Redhat。
| 1. 想知道更多关于 UNIX 操作系统的背景故事，请阅读维基百科[入口](https://zh.wikipedia.org/wiki/UNIX)（译者注：需科学上网）。 | ||
| 2. 文件描述符只是存取一个文件的抽象键，文件描述符通常是整型值并且管理啊难道一个打开的文件。 | ||
| 3. 了解详情请查看维基百科（译者注：原文没有地址，自行搜索吧） | ||
| 4. 这个概念最终也在 forunionfs 中回归 UNIX |
There was a problem hiding this comment.
原意应为"in the form of unionfs"，可能为作者笔误
『这个概念最终也在 forunionfs 中回归 UNIX』 => 『这个概念最终以 unionfs 的形式在 UNIX 中实现』
|
|
||
| In spite of its limitations, most people acknowledge the power in the metaphor and its effect on the integration of the operating system. Ever since UNIX was first released, researchers kept trying to further this central concept. For instance, the Plan 9 operating system pioneered a fully integrated approach to system resources: A cornerstone of Plan 9 vision was the objective to represent not only devices and communication channels but _all_ system interfaces through the filesystem. For instance, Plan 9 designers noted that in UNIX, network devices cannot _completely_ be considered as regular files: They are accessed through sockets which have distinct opening semantics and which reside in a different name space (host and port for internet sockets). Plan 9 implementation demonstrated that you could successfully unify all local and remote devices in a global namespace. This concept eventually came back to UNIX in the form of portalfs. | ||
| 尽管它有它的限制，但很多人也承认这个比喻的威力，和它在集成操作系统上的效果。自从 UNIX 第一次发布以来，研究者们持续促进这一核观念。比如 Plan 9 操作系统倡导一个将系统资源完全集成的方法：Plan 9 愿景的基础就是这样的目标 —— 不仅仅设备和信道，而是将 **所有**系统接口通过文件系统代表。比如 Plan 9 的设计人员注意到在 UNIX 中，网络设备不能 **完全地**被视为合格的文件：它们通过套接字存取，而套接字有特有的打开语义并且属于一个不同的命名空间（因特网套接字的主机和端口）。Plan 9 实现并且证明了，你可以在一个全局命名空间里成功的统一所有本地和远程设备。这个观念最终通过 `portalfs` 的形式回归到 UNIX 中来。 |
There was a problem hiding this comment.
『研究者们持续促进这一核观念』 => 『研究者们持续推进这一中心思想』
|
|
||
| In spite of its limitations, most people acknowledge the power in the metaphor and its effect on the integration of the operating system. Ever since UNIX was first released, researchers kept trying to further this central concept. For instance, the Plan 9 operating system pioneered a fully integrated approach to system resources: A cornerstone of Plan 9 vision was the objective to represent not only devices and communication channels but _all_ system interfaces through the filesystem. For instance, Plan 9 designers noted that in UNIX, network devices cannot _completely_ be considered as regular files: They are accessed through sockets which have distinct opening semantics and which reside in a different name space (host and port for internet sockets). Plan 9 implementation demonstrated that you could successfully unify all local and remote devices in a global namespace. This concept eventually came back to UNIX in the form of portalfs. | ||
| 尽管它有它的限制，但很多人也承认这个比喻的威力，和它在集成操作系统上的效果。自从 UNIX 第一次发布以来，研究者们持续促进这一核观念。比如 Plan 9 操作系统倡导一个将系统资源完全集成的方法：Plan 9 愿景的基础就是这样的目标 —— 不仅仅设备和信道，而是将 **所有**系统接口通过文件系统代表。比如 Plan 9 的设计人员注意到在 UNIX 中，网络设备不能 **完全地**被视为合格的文件：它们通过套接字存取，而套接字有特有的打开语义并且属于一个不同的命名空间（因特网套接字的主机和端口）。Plan 9 实现并且证明了，你可以在一个全局命名空间里成功的统一所有本地和远程设备。这个观念最终通过 `portalfs` 的形式回归到 UNIX 中来。 |
There was a problem hiding this comment.
『这个观念最终通过 portalfs 的形式回归到 UNIX 中来』 => 『这个想法最终以 portalfs 的形式在 UNIX 中实现』
|
|
||
| In spite of its limitations, most people acknowledge the power in the metaphor and its effect on the integration of the operating system. Ever since UNIX was first released, researchers kept trying to further this central concept. For instance, the Plan 9 operating system pioneered a fully integrated approach to system resources: A cornerstone of Plan 9 vision was the objective to represent not only devices and communication channels but _all_ system interfaces through the filesystem. For instance, Plan 9 designers noted that in UNIX, network devices cannot _completely_ be considered as regular files: They are accessed through sockets which have distinct opening semantics and which reside in a different name space (host and port for internet sockets). Plan 9 implementation demonstrated that you could successfully unify all local and remote devices in a global namespace. This concept eventually came back to UNIX in the form of portalfs. | ||
| 尽管它有它的限制，但很多人也承认这个比喻的威力，和它在集成操作系统上的效果。自从 UNIX 第一次发布以来，研究者们持续促进这一核观念。比如 Plan 9 操作系统倡导一个将系统资源完全集成的方法：Plan 9 愿景的基础就是这样的目标 —— 不仅仅设备和信道，而是将 **所有**系统接口通过文件系统代表。比如 Plan 9 的设计人员注意到在 UNIX 中，网络设备不能 **完全地**被视为合格的文件：它们通过套接字存取，而套接字有特有的打开语义并且属于一个不同的命名空间（因特网套接字的主机和端口）。Plan 9 实现并且证明了，你可以在一个全局命名空间里成功的统一所有本地和远程设备。这个观念最终通过 `portalfs` 的形式回归到 UNIX 中来。 |
There was a problem hiding this comment.
『但很多人也承认这个比喻的威力，和它在集成操作系统上的效果』 => 『但很多人也承认这个比喻的影响力，和它在操作系统一体化上的效果』
|
@pmwangyang @leviding 校对完成。行文和遣词都比较流畅，主要的问题应该是受限于领域。伪操作系统国内的文章也很少提及，我也只能在能力范围内提出一些意见。 |
yqian1991
reviewed
Jul 31, 2018
|
|
||
| The UNIX operating system crystallizes a couple of unifying ideas and concepts that shaped its design, user interface, culture and evolution. One of the most important of these is probably the mantra: “everything is a file”, widely regarded as one of the defining points of UNIX. | ||
| 为了有计划的发展架构设计、界面、文化和开发路线，UNIX系统明确了一系列统一的概念和创想。 |
There was a problem hiding this comment.
最后一句， “One of the most important of these is probably the mantra ...” 好像没有翻译哦
| * In UNIX everything is a stream of bytes | ||
| * In UNIX the filesystem is used as a universal name space | ||
| * 在 UNIX 中，一切都是字节流 | ||
| * 在 UNIX 中，文件系统有通用的命名空间 |
There was a problem hiding this comment.
“文件系统有通用的命名空间”
=>
"文件系统被用做通用的命名空间"
|
|
||
| So what really constitutes a file in UNIX? A file is not much more than a plain collection of bytes that you can read and/or write. Once you have a reference to a file, called a file descriptor2, I/O access in UNIX is done using the same set of operations, the same API – whatever the type of the device and the underlying hardware. | ||
| 在 UNIX 中，文件是由什么组成的呢？文件其实和一系列可读写的字节没什么区别。如果你有一个文件的索引（我们称之为「文件描述<sup><a href="#note2">[2]</a></sup>」），那么 UNIX 的 I/O 通道就已经准备好了，他们有着同样的一套操作和 API —— 无论设备的类型如何、连接的硬件是什么。 |
|
|
||
| Historically, UNIX was the first operating system to abstract all I/O under such a unified concept and small set of primitives. At the time, most operating systems were providing a distinct API for each device or device family. Some early microcomputer operating systems even required you to use multiple user commands to copy files – each one dedicated to a specific floppy disk size! | ||
| 纵观历史，UNIX是第一个在这样一种统一概念和一套小基元下抽象所有 I/O 的系统。那时，大部分操作系统为每一种或一类设备提供不同的 API。一些早期的微型计算机操作系统甚至需要你使用多个命令去拷贝文件 —— 因为每个命令对应指定的磁盘大小！ |
There was a problem hiding this comment.
primitives, 在操作系统中翻译成 “原语” 比较好
|
|
||
| Historically, UNIX was the first operating system to abstract all I/O under such a unified concept and small set of primitives. At the time, most operating systems were providing a distinct API for each device or device family. Some early microcomputer operating systems even required you to use multiple user commands to copy files – each one dedicated to a specific floppy disk size! | ||
| 纵观历史，UNIX是第一个在这样一种统一概念和一套小基元下抽象所有 I/O 的系统。那时，大部分操作系统为每一种或一类设备提供不同的 API。一些早期的微型计算机操作系统甚至需要你使用多个命令去拷贝文件 —— 因为每个命令对应指定的磁盘大小！ |
|
|
||
| From the programmer and the user perspectives, UNIX exposes: | ||
| 对于大多数程序员和用户的层面，UNIX 向他们暴露了： |
There was a problem hiding this comment.
“对于大多数程序员和用户的层面” =>
“对于大多数程序员和用户来说”
| * Almost all other devices (e,g, Printers, Graphic Card) | ||
| * 网络通信 | ||
| * 可交互终端 | ||
| * 几乎其他所有设备（例如：打印机、图形卡） |
| 2. 文件描述符只是存取一个文件的抽象键，文件描述符通常是整型值并且管理啊难道一个打开的文件。 | ||
| 3. 了解详情请查看维基百科（译者注：原文没有地址，自行搜索吧） | ||
| 4. 这个概念最终也在 forunionfs 中回归 UNIX | ||
| 5. 例如，在这个领域的当前活动，请查看 unionfs、portalfs 和 objfs 获取实例。 |
There was a problem hiding this comment.
”例如，在这个领域的当前活动，请查看 unionfs、portalfs 和 objfs 获取实例。“ =>
“需要这个领域当前活动的一些例子，请查看 unionfs、portalfs 和 objfs 获取实例”
|
@pmwangyang @leviding 校对完成 |
yqian1991
reviewed
Jul 31, 2018
| * 硬盘中的文件 | ||
| * 文件夹 | ||
| * 链接 | ||
| * 大容量存储设备（例如：硬盘、CD-ROM、磁带、USB设备） |
|
|
||
| UNIX filesystem paths provide a consistent and global scheme to label resources, regardless of their nature. For instance you can reference a local directory with `/usr/local`, a file with `/home/joe/memo.pdf`, a CD-ROM with `/mnt/cdrom`, a directory on a network drive with `/usr`, a hard disk partition with `/dev/sda1`, a UNIX domain socket with `/tmp/mysql.sock`, a terminal with `/dev/tty0` or even a mouse with `/dev/mouse`. This global namespace is often viewed as a hierarchy of files and directories. However, as the previous examples illustrate, this is just a convenient abstraction, and a file path can reference just about anything: a filesystem, an device, a network share or a communication channel. | ||
| UNIX 的文件系统路径为标签资源提供了一致的全局方案，从而可以忽略他们的物理地址。举个几个例子，你可以使用 `/usr/local` 命令访问一个本地文件夹、`/home/joe/memo.pdf` 命令访问一个文件、`/mnt/cdrom` 命令访问 CD-ROM、`/usr` 命令访问网络驱动器上的一个文件夹，`/dev/sda1` 命令访问硬盘分区，`/tmp/mysql.sock` 命令访问 UNIX 域名套接字，`/dev/tty0` 命令访问终端，甚至使用 `/dev/mouse` 命令来访问鼠标。这些通用命名空间通常看起来像一个文件层级或文件夹，其实就像前面举的例子，这些只是一个方便的抽象概念，一个文件路径可以引用一切东西：一个文件系统、一个设备、一个网络共享或信道。 |
There was a problem hiding this comment.
”命令访问网络驱动器上的一个文件夹，“， 最后应该是 “、” =>
”命令访问网络驱动器上的一个文件夹、“
|
|
||
| The namespace is hierarchical and all resources can be referenced from the root directory (`/`). You can access multiple filesystems within the same namespace: you just “attach” a device or a filesystem (let’s say an external hard-drive) at a specific location in the namespace (say `/backups`). In UNIX jargon, this action is called _mounting_ a filesystem, and the namespace location where you attach the filesystem is called a _mount point_. You can reference all the resources of a mounted filesystem as a part of the global namespace by prefixing them with the mount point (say the file `/backups/myproject-Oct07.zip`) | ||
| 命名空间是分层的，所有的资源都可以从根文件夹访问到(`/`)。你可以使用同样的命名空间来进入多个文件系统：你只是在命名空间的指定的位置（比如 `/backups`）「连接」了一个设备或文件系统（比如外置硬盘）。用 UNIX 术语来说，这个操作叫做 **挂载**（_mounting_）一个文件系统，你连接文件系统的命名空间位置叫做 **挂载点**（_mount point_）。你可以通过给挂载的文件系统添加以挂载点命名的前缀，就像访问通用命名空间的一部分一样，来访问它的所有资源（比如 `/backups/myproject-Oct07.zip` 这个文件）。 |
There was a problem hiding this comment.
『你可以使用同样的命名空间来进入多个文件系统』 =>
『你可以使用同样的命名空间来访问多个文件系统』
|
|
||
| Despite the success of the “Everything is a File” metaphor, some people are somewhat skeptical on its universality. When every file is considered to be a stream of bytes, one consequence is the lack of standard support for meta-data: To process a file appropriately, each application must come up with its own way of figuring the file type, structure and sematics. Besides, for the meta-data to be preserved, _every_ tool that processes the stream must keep the meta-data unaltered (e.g. XMP information for a photograph). Therefore, while the fact that a UNIX file is just a big bag of bytes is extremely powerful for connecting programs based on a text interface, it seriously limits application composition when it comes to multimedia and binary formats. | ||
| 先不管「一切皆文件」这个比喻的成功与否，一些人或多或少怀疑它的普遍性。当每个文件都被视为字节流时，元数据的一个结论缺少标准支持：为了合适地处理一个文件，每个应用必须想办法计算文件类型、架构和语义。并且，为了保存元数据，**每个**处理数据流的工具必须保持元数据不变（比如照片中的 XMP 信息）。因此，尽管 UNIX 文件的一大堆字节的形态对于链接文字界面的程序极度高效，同时也严重限制了多媒体和二进制应用的组合。 |
There was a problem hiding this comment.
"先不管「一切皆文件」这个比喻的成功与否，"=>
尽管「一切皆文件」这个比喻很成功，但是...
|
|
||
| Despite the success of the “Everything is a File” metaphor, some people are somewhat skeptical on its universality. When every file is considered to be a stream of bytes, one consequence is the lack of standard support for meta-data: To process a file appropriately, each application must come up with its own way of figuring the file type, structure and sematics. Besides, for the meta-data to be preserved, _every_ tool that processes the stream must keep the meta-data unaltered (e.g. XMP information for a photograph). Therefore, while the fact that a UNIX file is just a big bag of bytes is extremely powerful for connecting programs based on a text interface, it seriously limits application composition when it comes to multimedia and binary formats. | ||
| 先不管「一切皆文件」这个比喻的成功与否，一些人或多或少怀疑它的普遍性。当每个文件都被视为字节流时，元数据的一个结论缺少标准支持：为了合适地处理一个文件，每个应用必须想办法计算文件类型、架构和语义。并且，为了保存元数据，**每个**处理数据流的工具必须保持元数据不变（比如照片中的 XMP 信息）。因此，尽管 UNIX 文件的一大堆字节的形态对于链接文字界面的程序极度高效，同时也严重限制了多媒体和二进制应用的组合。 |
There was a problem hiding this comment.
"元数据的一个结论缺少标准支持" =>
"产生的一个后果就是元数据缺少标准支持"
|
@pmwangyang 可以修改啦 |
|
@pmwangyang 修改一下吧 |
|
修改完成，两位校对辛苦了，都很专业且细致，衷心感谢！ |
leviding
approved these changes
Aug 3, 2018
|
@pmwangyang 已经 merge 啦~ 快快麻溜发布到掘金然后给我发下链接，方便及时添加积分哟。 掘金翻译计划有自己的知乎专栏，你也可以投稿哈，推荐使用一个好用的插件。 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
译文翻译完成，resolve #4207