概览

项目网站 docs.freebsd.org/en
翻译许可证 BSD 2-Clause "Simplified" License
翻译进程
  • 可以直接翻译。
  • 可以提出翻译建议。
  • 只允许指定的用户贡献。
  • 该翻译使用双语文件。
文件掩码 documentation/content/*/articles/linux-emulation/_index.po
翻译文件 下载 documentation/content/zh_TW/articles/linux-emulation/_index.po
最后更改 2022年1月9日 16:25
最后作者 Allan Sun

字符串统计数据

字符串百分比 托管的字符串数 字数百分比 托管的单词数 字符百分比 托管的字符数
总数 396 12240 77383
已翻译数 1% 7 1% 9 1% 65
需要编辑 0% 0 0% 0 0% 0
只读 0% 0 0% 0 0% 0
未通过的检查数 0% 0 0% 0 0% 0
带有建议的字符串数 0% 0 0% 0 0% 0
未翻译的字符串数 98% 389 99% 12231 99% 77318
过去 12 个月 上一年

过去 12 个月内的活动

0 个更改 0 个更改 0 个更改 0 个更改 0 个更改 0 个更改 3 个更改 0 个更改 0 个更改 0 个更改 0 个更改 0 个更改 0 个更改 0 个更改 0 个更改 0 个更改 0 个更改 0 个更改 0 个更改 0 个更改 0 个更改 0 个更改 0 个更改 0 个更改
十月 十一月 十二月 一月 二月 三月 四月 五月 六月 七月 八月 九月

快速数字

12240
托管的单词数
396
托管的字符串数
1%
已翻译
0
贡献者
及之前 30 天

过去 30 天的趋势

—
托管的单词数
+100%
—
托管的字符串数
+100%
—
已翻译
+1%
—
贡献者
—
用户头像 无

要翻译的新字符串

Documentation / articles/linux-emulation/_index — 中文（繁体） (zh_TW)

翻译中出现了 1 条要翻译的新字符串。 1 年前
用户头像 无

资源更新

Documentation / articles/linux-emulation/_index — 中文（繁体） (zh_TW)

文件 documentation/content/zh_TW/articles/linux-emulation/_index.po 已更改。 1 年前
用户头像 无

更新了仓库中的字符串

Documentation / articles/linux-emulation/_index — 中文（繁体） (zh_TW)

Common UNIX(R) API defines a syscall as a way to issue commands from a user space process to the kernel. The most common implementation is either by using an interrupt or specialized instruction (think of `SYSENTER`/`SYSCALL` instructions for ia32). Syscalls are defined by a number. For example in FreeBSD, the syscall number 85 is the man:swapon[2] syscall and the syscall number 132 is man:mkfifo[2]. Some syscalls need parameters, which are passed from the user-space to the kernel-space in various ways (implementation dependent). Syscalls are synchronous.
 
1 年前
用户头像 无

要翻译的新字符串

Documentation / articles/linux-emulation/_index — 中文（繁体） (zh_TW)

翻译中出现了 6 条要翻译的新字符串。 2 年前
用户头像 无

资源更新

Documentation / articles/linux-emulation/_index — 中文（繁体） (zh_TW)

文件 documentation/content/zh_TW/articles/linux-emulation/_index.po 已更改。 2 年前
用户头像 无

更新了仓库中的字符串

Documentation / articles/linux-emulation/_index — 中文（繁体） (zh_TW)

Many UNIX(R) derivates implement the man:ptrace[2] syscall to allow various tracking and debugging features. This facility enables the tracing process to obtain various information about the traced process, like register dumps, any memory from the process address space, etc. and also to trace the process like in stepping an instruction or between system entries (syscalls and traps). man:ptrace[2] also lets you set various information in the traced process (registers etc.). man:ptrace[2] is a UNIX(R)-wide standard implemented in most UNIX(R)es around the world.
 
2 年前
用户头像 无

更新了仓库中的字符串

Documentation / articles/linux-emulation/_index — 中文（繁体） (zh_TW)

The Linux(R) emulation layer is not complete, as some syscalls are not implemented properly and some are not implemented at all. The emulation layer employs a facility to mark unimplemented syscalls with the `DUMMY` macro. These dummy definitions reside in [.filename]#linux_dummy.c# in a form of `DUMMY(syscall);`, which is then translated to various syscall auxiliary files and the implementation consists of printing a message saying that this syscall is not implemented. The `UNIMPL` prototype is not used because we want to be able to identify the name of the syscall that was called to know what syscalls are more important to implement.
 
2 年前
用户头像 无

更新了仓库中的字符串

Documentation / articles/linux-emulation/_index — 中文（繁体） (zh_TW)

`sched_bind` is an API used to bind a thread to a particular CPU for all the time it executes the code, until a `sched_unbind` function call does not unbind it. This feature has a key role in situations where you cannot trust the current state of CPUs (for example, at very early stages of boot), as you want to avoid your thread to migrate on inactive CPUs. Since `sched_bind` and `sched_unbind` manipulate internal scheduler structures, they need to be enclosed in `sched_lock` acquisition/releasing when used.
 
2 年前
用户头像 无

更新了仓库中的字符串

Documentation / articles/linux-emulation/_index — 中文（繁体） (zh_TW)

The FreeBSD kernel has been made preemptive basically to deal with interrupt threads. In fact, to avoid high interrupt latency, time-sharing priority threads can be preempted by interrupt threads (in this way, they do not need to wait to be scheduled as the normal path previews). Preemption, however, introduces new racing points that need to be handled, as well. Often, to deal with preemption, the simplest thing to do is to completely disable it. A critical section defines a piece of code (borderlined by the pair of functions man:critical_enter[9] and man:critical_exit[9], where preemption is guaranteed to not happen (until the protected code is fully executed). This can often replace a lock effectively but should be used carefully to not lose the whole advantage that preemption brings.
 
2 年前
用户头像 无

更新了仓库中的字符串

Documentation / articles/linux-emulation/_index — 中文（繁体） (zh_TW)

Scheduling barriers are intended to be used to drive scheduling of threading. They consist mainly of three different stubs:
 
2 年前
浏览翻译的所有变化