written修复工具文章列表:

• 1、C++｜输入流对象cin、>>提取和处理无效文本输入
• 2、译 Yarn 官方介绍：一款新的 JavaScript 包管理器
• 3、九年级英语被动语态用法详解及易错点
• 4、高考英语｜巧解词义猜测题，英语阅读理解满分必备！
• 5、Linux从12c non-CDB升级到18.0.0 non-CDB手动

译 Yarn 官方介绍：一款新的 JavaScript 包管理器

译者前言

这两天被 Yarn 刷屏了？对于新工具，范范地道听途说或浅尝辄止，不如静下心来听听作者的心路历程。我读了多篇文章，感觉说得最清楚的还是 Facebook 发表的这篇官方介绍，于是翻译出来分享给大家。

在谈论 Yarn 时，有人在谈论前端圈的 “造轮子” 风气，有人在谈论 Facebook 工程师的 PR 能力，有人在谈论网络速度……但读完这篇文章之后，我看到的是前端工程、是开发体验、是思维方式。相信不论是一线工程师还是架构师，都会从 Facebook 团队的思考中找到启发。

In the JavaScript community, engineers share hundreds of thousands of pieces of code so we can avoid rewriting basic components, libraries, or frameworks of our own. Each piece of code may in turn depend on other pieces of code, and these dependencies are managed by package managers. The most popular JavaScript package manager is the npm client, which provides access to more than 300,000 packages in the npm registry. More than 5 million engineers use the npm registry, which sees up to 5 billion downloads every month.

在 JavaScript 社区里，开发者们共享出了成千上万的代码，这令我们不必自己从头开始编写最基础的组件、类库或框架。这些代码之间通常层层依赖，而这些依赖关系正是由包管理器来管理的。当前最流行的 JavaScript 包管理器是 npm 客户端，通过它，我们可以获取 npm 仓库中的 30 多万个包。超过 500 万名开发者在使用 npm 仓库，每个月产生 50 多亿次下载。

We've used the npm client successfully at Facebook for years, but as the size of our codebase and the number of engineers grew, we ran into problems with consistency, security, and performance. After trying to solve for each issue as it came up, we set out to build a new solution to help us manage our dependencies more reliably. The product of that work is called Yarn — a fast, reliable, and secure alternative npm client.

在 Facebook，我们已经成功地使用 npm 客户端多年了，但随着代码体积的不断增长和团队规模的不断壮大，我们在一致性、安全性和性能方面遇到了问题。我们曾尝试逐一解决这些问题，但最终，我们决定自己打造一套全新的解决方案，以一种更加可靠的方式来管理依赖。我们的工作成果叫作 Yarn——作为 npm 客户端的替代器，它更加快速、可靠、安全。

We're pleased to announce the open source release of Yarn, a collaboration with Exponent, Google, and Tilde. With Yarn, engineers still have access to the npm registry, but can install packages more quickly and manage dependencies consistently across machines or in secure offline environments. Yarn enables engineers to move faster and with confidence when using shared code so they can focus on what matters — building new products and features.

今天，我们很荣幸地宣布，Yarn 以开源的方式发布，它是由 Exponent、 Google、Tilde 与我们合作完成的。在使用 Yarn 时，开发者们还像以前一样从 npm 仓库那里获取资源，但安装速度更快，不同的机器的安装结果完全一致，甚至还可以在安全的离线环境中使用。Yarn 令开发者可以更加迅捷和从容地享受前人栽种的果实，进而集中精力打造自己的产品——这才是更加重要的事情。

The evolution of JavaScript package management at Facebook

JS 包管理方案在 Facebook 的演变

In the days before package managers, it was commonplace for JavaScript engineers to rely on a small number of dependencies stored directly in their projects or served by a CDN. The first major JavaScript package manager, npm, was built shortly after Node.js was introduced, and it quickly became one of the most popular package managers in the world. Thousands of new open source projects were created and engineers shared more code than ever before.

在包管理器出现之前，JavaScript 开发者平时所用的依赖并不多，这些依赖通常会直接存放在项目中，或通过 CDN 引入。npm 是第一个正式的 JavaScript 包管理器，在 Node.js 诞生后不久它就建立起来了，随后迅速成为全世界最流行的包管理器。从此，开源项目如雨后春笋般涌现，盛况空前。

Many of our projects at Facebook, like React, depend on code in the npm registry. However, as we scaled internally, we faced problems with consistency when installing dependencies across different machines and users, the amount of time it took to pull dependencies in, and had some security concerns with the way the npm client executes code from some of those dependencies automatically. We attempted to build solutions around these issues, but they often raised new issues themselves.

Facebook 的很多项目，比如 React，就依赖了 npm 仓库中的代码。但是，随着内部规模的扩张，我们遇到了很多问题：不同机器或不同人所得到的安装结果并不一致，安装依赖所花费的时间也无法忽视；由于 npm 客户端在安装依赖包时会自动执行其中的脚本，安全性也令我们顾虑重重。我们不断尝试针对这些问题建立解决方案，但这些解决方案往往又不断引发新的问题。

Attempts at scaling the npm client

关于理顺 npm 客户端的一系列尝试

Initially, following the prescribed best practices, we only checked in package.json and asked engineers to manually run npm install. This worked well enough for engineers, but broke down in our continuous integration environments, which need to be sandboxed and cut off from the internet for security and reliability reasons.

最开始，我们遵循官方推荐的最佳实践，只把 package.json 文件提交到代码库，然后要求工程师们手动运行 npm install 来安装依赖。这种方法对工程师来说运作良好，但在我们的持续集成（CI）环境下就不灵了，因为 CI 环境需要运行在沙箱中，基于安全性和可靠性的考虑，它需要切断与互联网的连接。

The next solution we implemented was to check all of node_modules into the repository. While this worked, it made some simple operations quite difficult. For example, updating a minor version of babelgenerated an 800,000-line commit that was difficult to land and triggered lint rules for invalid utf8 byte sequences, windows line endings, non png-crushed images, and more. Merging changes to node_modules would often take engineers an entire day. Our source control team also pointed out that our checked-in node_modules folder was responsible for a tremendous amount of metadata. The React Native package.json currently lists just 68 dependencies, but after running npm install the node_modules directory contains 121,358 files.

后来我们改变了对策，把所有 node_modules 签入代码库。这种方法也运行了一段时间，但它也让一些原本简单的操作变得困难起来。举例来说，更新 Babel 的一个次版本号会产生一次 “80 万行” 级别的提交动作，这种情况很难处理，而且会触发一系列无意义的 lint 操作（诸如检查 UTF-8 字节序列、Windows 换行符、未优化的 PNG 图片等等）。把 node_modules 的变更合并进来往往要花费工程师一整天的时间。我们的版本控制团队也指出我们提交的 node_modules 目录直接导致元数据体积的飙升。比如 React Native 项目的 package.json 只列出了 68 个依赖，但在跑过了 npm install 之后，node_modules 目录下会产生 121,358 个文件。

We made one final attempt to scale the npm client to work with the number of engineers at Facebook and the amount of code that we need to install. We decided to zip the entire node_modules folder and upload it to an internal CDN so that both engineers and our continuous integration systems could download and extract the files consistently. This enabled us to remove hundreds of thousands of files from source control, but made it so engineers needed internet access not just to pull new code, but also to build it.

为了让 npm 的这一套工作流适应 Facebook 的团队人数和代码量，我们动用了最后一招。我们决定把整个 node_modules 目录打成一个压缩包，上传到专用的 CDN 上，这样工程师和 CI 服务器都可以下载、解压并得到完全一致的结果了。这个方案一上，我们就可以从版本控制系统中清掉成千上万的文件了；但这同时也导致工程师不论是在拉取新代码时，还是在编写新代码时，都需要保持网络连接。

We also had to work around issues with npm's shrinkwrap feature, which we used to lock down dependency versions. Shrinkwrap files aren't generated by default and will fall out of sync if engineers forget to generate them, so we wrote a tool to verify that the contents of the shrinkwrap file matches what's in node_modules. These files are huge JSON blobs with unsorted keys, though, so changes to them would generate massive, difficult-to-review commits. To mitigate this, we needed to add an additional script to sort all the entries.

我们还不得不应付 npm 的 shrinkwrap 功能所带来的问题，因为我们使用 shrinkwrap 来锁定依赖版本。Shrinkwrap 文件并不是默认生成的，一旦工程师在提交代码前忘记生成这个文件，则这个文件跟代码就不同步了。为此我们还特意写了一个工具，用来校验 shrinkwrap 文件的内容跟 node_modules 的内容是否匹配。这个 shrinkwrap 文件是由一堆乱序字段所组成的巨型 JSON 数据，因此每次修改都会产生一次巨型的、无法 review 的提交。为了缓解这个问题，我们又需要写一个额外的脚本来把所有的字段排好序。

Finally, updating a single dependency with npm also updates many unrelated ones based on semantic versioning rules. This makes every change much larger than anticipated, and having to do things like committing node_modules or uploading it to a CDN made the process less than ideal for engineers.

这还没完呢。在 npm 中，更新一项单独的依赖其实还会按照 “语义化版本”（semantic versioning）的规则更新一堆无关的依赖。这使得每次代码变更都比预期的要多，而我们所能做的也就是上述这一系列的下策。

Building a new client

构建新的客户端

Rather than continue building infrastructure around the npm client, we decided to try looking at the problem more holistically. What if instead we attempted to build a new client that addressed the core issues we were experiencing? Sebastian McKenzie in our London office started hacking on this idea and we quickly became excited about its potential.

痛定思痛，我们决定不再围绕 npm 客户端来构建基础设施，而是从一个更高的高度来审视整件事情。如果我们针对当下的痛点来打造一款全新的客户端会怎么样？我们伦敦办事处的 Sebastian McKenzie 同学开始推进这个想法，很快我们就发现这条道路充满光明。

As we worked on this, we began speaking with engineers across the industry and found that they faced a similar set of problems and had attempted many of the same solutions, often focused on resolving a single issue at a time. It became obvious that by collaborating on the whole set of problems the community was facing, we could develop a solution that worked for everyone. With the help of engineers from Exponent, Google, and Tilde, we built out the Yarn client and tested and validated its performance on every major JS framework and for additional use cases outside of Facebook. Today, we're excited to share it with the community.

在推进这个计划的同时，我们也开始跟业内的工程师们广泛交谈。我们发现大家遇到的问题其实都差不多，也都尝试过差不多的解决方案，效果也差不多都是按下个葫芦浮起个瓢。接下来的事情就变得水到渠成了——我们集合社区的力量来解决共通的问题，产出一个适用于每个人的解决方案。由此我们收到了来自 Exponent、Google 和 Tilde 公司的工程师的帮助，共同开发出了 Yarn 客户端；为了确保它也适用于 Facebook 之外的使用场景，我们还在所有主流的 JS 框架身上验证了它的性能。今天，我们怀着激动的心情，将它推荐给整个社区。

Introducing Yarn

Yarn 介绍

Yarn is a new package manager that replaces the existing workflow for the npm client or other package managers while remaining compatible with the npm registry. It has the same feature set as existing workflows while operating faster, more securely, and more reliably.

Yarn 是一款新的包管理器，它将取代原有的基于 npm 客户端（或其它包管理器）的工作流，但同时又保留了与 npm 仓库的兼容性。它具备原有工作流的所有功能，但相比之下更加快速、安全、可靠。

The primary function of any package manager is to install some package — a piece of code that serves a particular purpose — from a global registry into an engineer's local environment. Each package may or may not depend on other packages. A typical project could have tens, hundreds, or even thousands of packages within its tree of dependencies.

所有包管理器的核心功能都是从一个通用仓库中获取包，然后安装到开发者的本地环境中。所谓 “包”，就是一套解决特定任务的代码。一个包可能依赖、也可能不依赖其它包。一个典型的项目可能会在它的依赖树中涉及数十、数百甚至数千个包。

These dependencies are versioned and installed based on semantic versioning (semver). Semver defines a versioning scheme that reflects the types of changes in each new version, whether a change breaks an API, adds a new feature, or fixes a bug. However, semver relies on package developers not making mistakes — breaking changes or new bugs may find their way into installed dependencies if the dependencies are not locked down.

这些依赖包都是有版本的，它们按照 “语义化版本”（semver）的规则被安装进来。Semver 定义了一套版本描述规范，用于表明每个版本的变更类型：是 API 行为出现了向后不兼容的破坏性变更、是增加了一个新功能、还是修复了一个 bug。但是，semver 是否奏效，取决于包的开发者是否遵守规则。在理想情况下，即使依赖包没有锁定版本，包的不同类型的变更版本都会在 semver 的约定下以不同的方式被正确地安装进来。

Architecture

架构设计

In the Node ecosystem, dependencies get placed within a node_modules directory in your project. However, this file structure can differ from the actual dependency tree as duplicate dependencies are merged together. The npm client installs dependencies into the node_modules directory non-deterministically. This means that based on the order dependencies are installed, the structure of a node_modules directory could be different from one person to another. These differences can cause “works on my machine” bugs that take a long time to hunt down.

在 Node 的生态系统中，依赖会被安装到你的项目中的 node_modules 目录中。不过，其内部的文件结构和实际的依赖关系树并不完全对应，因为安装过程存在重复依赖的合并机制。npm 客户端在把依赖安装到 node_modules 目录时存在不确定性。这种 “不确定性” 是指，由于安装依赖的顺序不同，你得到的 node_modules 目录的内部结构可能跟别人不一样。这种差异可能会导致 “我电脑上是好的” 之类的 bug，而这类 bug 往往是极难定位的。

Yarn resolves these issues around versioning and non-determinism by using lockfiles and an install algorithm that is deterministic and reliable. These lockfiles lock the installed dependencies to a specific version, and ensure that every install results in the exact same file structure in node_modules across all machines. The written lockfile uses a concise format with ordered keys to ensure that changes are minimal and review is simple.

Yarn 解决上述版本问题和不确性问题的方案是引入 lockfile（锁定文件），并启用了一套新的安装算法，以此达到一致、可靠的结果。这个 lockfile 会把所有已安装的依赖锁定在一个固定的版本上，确保每次安装所产生的 node_modules 目录的文件结构在不同机器上总是一致的。这个 lockfile 采用一种简明的格式来书写，其字段是有序的，以确保每次更新都是最小化的、易于 reivew 的。

The install process is broken down into three steps:

整个安装过程被分解为以下三个步骤：

Resolution: Yarn starts resolving dependencies by making requests to the registry and recursively looking up each dependency.

Fetching: Next, Yarn looks in a global cache directory to see if the package needed has already been downloaded. If it hasn't, Yarn fetches the tarball for the package and places it in the global cache so it can work offline and won't need to download dependencies more than once. Dependencies can also be placed in source control as tarballs for full offline installs.

Linking: Finally, Yarn links everything together by copying all the files needed from the global cache into the local node_modules directory.

解析：Yarn 首先开始解析依赖关系。它向包仓库发出请求，并递归地查询各层依赖。

获取：接下来，Yarn 会在一个全局的缓存目录中查找当前所需的包是不是已经下载过了。如果还没有，Yarn 会把这个包的 tarball 拉下来，并把它存放在全局缓存中，这样它下次就可以离线安装了，无需重复下载。依赖包也可以以 tarball 的形式存放到版本控制系统中，以实现完全的离线安装。

链接：最后，Yarn 会把所需的所有文件从缓存中复制到本地的 node_modules 目录中，这样所有东西就链接为一个整体了。

By breaking these steps down cleanly and having deterministic results, Yarn is able to parallelize operations, which maximizes resource utilization and makes the install process faster. On some Facebook projects, Yarn reduced the install process by an order of magnitude, from several minutes to just seconds. Yarn also uses a mutex to ensure that multiple running CLI instances don't collide and pollute each other.

由于我们把安装过程清晰地拆解开来，消灭了安装结果的不确定性，Yarn 天生具备并行操作的能力。这种并行能力可以最大化资源的利用率，提升安装速度。在 Facebook 的某些项目中，Yarn 可以带来一个数量级的性能提升，安装耗时从几分钟缩短到几秒。Yarn 内建互斥特性，以确保同时运行多个 CLI 实例也不会相互冲突、相互污染。

Throughout this entire process, Yarn imposes strict guarantees around package installation. You have control over which lifecycle scripts are executed for which packages. Package checksums are also stored in the lockfile to ensure that you get the same package every single time.

在整个安装过程中，Yarn 还提供了严格的安全保障。你可以精确控制某个包的某个生命周期脚本是否运行。包的校验信息（checksum）也会保存在 lockfile 中，确保你每次安装得到的都是同一个包。

Features

其它特性

In addition to making installs much faster and more reliable, Yarn has additional features to further simplify the dependency management workflow.

除了让包的安装变得更加快速和可靠以外，Yarn 还提供了如下特性，进一步简化了依赖管理的工作流。

Compatibility with both the npm and bower workflows and supports mixing registries.

Ability to restrict licenses of installed modules and a means for outputting license information.

Exposes a stable public JS API with logging abstracted for consumption via build tools.

Readable, minimal, pretty CLI output.

同时兼容 npm 和 Bower 工作流，支持混用多种仓库类型。

可以限制依赖包的授权类型，并且可以输出依赖包的授权信息。

暴露一个稳定的 JS API，提供抽象化的日志信息以便与其它构建工具集成。

提供可读的、最小化的、美观的 CLI 输出信息。

Yarn in production

应用到生产环境

At Facebook we're already using Yarn in production, and it's been working really well for us. It powers the dependency and package management for many of our JavaScript projects. With each migration we've enabled engineers to build offline and helped speed up their workflow. You can see how install times for Yarn and npm compare on React Native under different conditions, which you can find here.

在 Facebook，我们已经将 Yarn 用于生产环境了，而且它跑得也确实不错。我们的很多 JavaScript 项目都是由它来完成依赖安装和包管理的。每当一个项目完成迁移后，工程师们都会获得离线工作的能力，进而加快工作流。我们提供了一个页面（https://yarnpkg.com/en/compare），用来展示不同条件下 Yarn 和 npm 在安装耗时方面的对比。

Getting started

如何上手

The easiest way to get started is to run:

最简单的上手方式就是运行以下命令：

npm install -g yarnyarn

The yarn CLI replaces npm in your development workflow, either with a matching command or a new, similar command:

新的 yarn CLI 将会在你的开发工作流中替代 npm。在各种场景下，Yarn 要么提供了一个对等的命令，要么提供了一个功能相似的新命令：

npm install → yarn

With no arguments, the yarn command will read your package.json, fetch packages from the npm registry, and populate your node_modules folder. It is equivalent to running npm install.

在不加任何参数的情况下，yarn 命令将会读取你的 package.json 文件，从 npm 仓库拉取包，然后存放到你的 node_modules 目录中。其效果等同于直接运行 npm install。

npm install --save <name> → yarn add <name>

We removed the “invisible dependency” behavior of npm install <name> and split the command. Running yarn add <name> is equivalent to running npm install --save <name>.

我们去掉了 npm install <name> 命令产生 “隐形依赖” 的行为，只保留了显式安装行为。运行 yarn add <name> 将等同于运行 npm install --save <name>。

Future

未来

Many of us came together to build Yarn to solve common problems, and we knew that we wanted Yarn to be a true community project that everyone can use. Yarn is now available on GitHub and we're ready for the Node community to do what it does best: Use Yarn, share ideas, write documentation, support each other, and help build a great community to care for it. We believe that Yarn is already off to a great start, and it can be even better with your help.

我们这一群人走到一起构建了 Yarn，目的在于解决社区共通的问题；我们的愿景也很明确，希望 Yarn 成为一个真正的社区项目，人人均可从中受益。Yarn 已经在 GitHub 开源，我们也已经准备好迎接来自 Node 社区的帮助：开始使用、交换想法、编写文档、互相扶持，共同建立一个强大的社区来推动它的发展。我们相信 Yarn 已经迈出了坚实的第一步，而且你的参与会让它变得更好！

希望本文能帮助到您！

点赞 转发，让更多的人也能看到这篇内容（收藏不点赞，都是耍流氓-_-）

关注 ｛我｝，享受文章首发体验！

每周重点攻克一个前端技术难点。更多精彩前端内容私信 我 回复“教程”

原文链接：https://github.com/cssmagic/blog/issues/67

九年级英语被动语态用法详解及易错点

一、 主动语态和被动语态的概念

1）He opened the door. 他开了门。

主动句，主语是动作的执行者/发出者

2）The door was opened by him. 门被开了。

被动句，主语是动作的承受者

汉语中表示被动的词：被…/ 由…/ 受…/ 给…

英语中表被动用：be 过去分词构成

二、 被动语态的结构及用法

1）被动语态的几种句型

肯定句：主语 be 及物动词的过去分词 （by）

eg: My phone was made in China.

否定句：主语 be not 过去分词 （by）

eg: My phone wasn’t made in China.

一般疑问句：Be 主语 过去分词 （by）？

eg: Was your phone made in China?

特殊疑问句：特殊疑问词 be 主语 过去分词 （by）?

eg: Where was your phone made?

2）不同时态中的被动语态

3） 被动语态的用法

当不知道或没有必要指出动作的执行者时，常用被动语态，这时往往不用by短语。The front window in the classroom was broken yesterday.

昨天，教室的前窗被打破了。(不知谁打破的)

They have been poorly paid.

他们的工资太低。(没必要指出工资是谁付的)

突出或强调动作的承受者，如果需要说出动作的执行者，用by短语。

These books are written especially for children.

这些书是专门为孩子们写的。(强调的是“这些书”)

三、主动语态变被动语态

1）一般情况下主动语态变被动语态

主动句：He closed the door.

变被动句：The door was closed by him.

口诀：宾变主，主变宾，谓变be done, 时不变，数格必须随被变。

2）主动语态中若有双宾语

Vivian gave me a book. 双宾语（me是间宾， book是直宾）

-I was given a book by Vivian. 间接宾语提前

-A book was given to me by Vivian. 直接宾语提前时，要在间接宾语前加介词

动词make/buy/get用for; 动词give/send/lend/take用to

3) “感使动词” (feel, hear, listen to, let, have, make, see, watch, notice, look at)真奇怪，主动结构“to”走开，被动结构又请来，十个动词要记牢，不会被它再难倒。

We saw him play football on the playground.

我们看见他在操场上打篮球。

变被动：He was seen to play football on the playground.

他被我们看到在操场上打篮球。

四、主动形式表被动意义

1) 系动词没有被动语态，如feel, sound, taste, look, become, fall, get, grow, keep, remain, seem, smell, stay, turn等等

Your idea sounds good.

你的注意听起来蛮好的。

You look beautiful.

你看起来美美的。

2) 在need, require, want, be worth , deserve等词的后面，动名词用主动形式表示被动意义

The TV needs repairing. 电视需要修理。

= The TV needs to be repaired.

3) 一般说来，不及物动词或不及物动词短语不能使用被动语态，常见的有：appear, die, disappear, end（vi. 结束）, fail, happen, last, lie, sit, spread, stand, break out, come true, fall asleep, keep silence, lose heart, take place，occur等。

A car accident happened in the street.

一场车祸发生在街上。

Great changes have taken place in my hometown.

我的故乡发生了巨变。

4) 在某些形容词后面，当不定式表达的情况与它前面的名词或代词构成逻辑上的动宾关系时，用主动式表示被动意义。

She has an important meeting to attend.

她有一个重要的会议要参加。

五、易错点总结（常考点）

1）在时间、条件状语从句中，要用一般现在时的被动语态表示将来时的被动语态。

If l am given enough time, I will do it better.

给我足够的时间，我会做得更好。

2）固定结构中的介词或副词在被动结构中不可省去。

Such a bad habit should be got rid of.

这样的坏习惯应该改掉。（of 不可以省去的）

3）有些动词如write, read, sell，wash, open等当强调动作执行情况时, 有被动语态; 当用作不及物动词来说明主语本身所具有的特征时,无被动语态。

The computers were sold out, because they sell well.

电脑被卖光了，因为它们卖得好。

The cloth washes easily.

这布很好洗。

4）在“too…to…”结构和形容词 enough to do结构中,通常用主动形式表示被动意义。

The problem is too difficult to work out.

5）常见的被动语态的句型搭配

据说..... It is said that ...

据报导.. It is reported that ...

据推测..... It is supposed that ...

希望.... It is hoped that ...

众所周知..... It is well known that ...

普遍认为..... It is generally considered that ...

有人建议..... It is suggested that

六、【被动语态专项训练】

1. A red sky in the morning _______ to be a sign of bad weather.

A. says B. is saying C. is said D. is being said

2. The book _______ for anyone who wants to learn more about the Internet.

A. is intended B. has intended

C. is intending D. will intend

3. Blood is the medium in which oxygen _______ to all parts of the body.

A. is carried B. has carried

C. is carrying D. will carry

4. If the package _______ well, we assume the contents are also wonderful.

A. is wrapped B. has wrapped

C. is wrapping D. will wrap

5. Both hydrogen and oxygen are elements, but water, which _______ when they combine, is not.

A. is formed B. has formed

C. is forming D. will form

6. The swimmer hung on to the rope and _______ to safety.

A. is pulled B. has pulled

C. was pulled D. was pulling

7. Einstein _______ the Nobel Prize for his contribution to Quantum Theory.

A. is awarded B. has awarded C. was awarded D. was awarding

8. They ought to have arrived at lunchtime but the flight _______.

A. is delayed B. has delayed

C. was delayed D. was delaying

9. The crunch came when she _______ to choose between her marriage and her career.

A. is forced B. has forced C. was forced D. was forcing

10. I _______ to wait four hours before I was examined by a doctor.

A. made B. has made

C. was made D. was making

11. Anyone seen carrying boxes, bags, or whatever, _______ by the police.

A. stopped B. has stopped

C. was stopped D. was stopping

12. I can’t turn a blind eye when someone _______.

A. has robbed B. was robbed

C. was robbing D. is being robbed

13. The dealer will provide you with a courtesy car while your vehicle_______.

A. has repaired B. was repaired

C. is being repaired D. was been repaired

14. The Olympic torch is carried by runners to the place where the games _______.

A. has held B. was held C. are being held D. were been held

15. He apologized to the people who _______.

A. affected B. has affected

C. have been affected

D. had been affected

16. No decision ______ until next year, so you’ll just have to wait and see.

A. have made B. are made

C. will make D. will be made

17. Candidates who are successful in the written test ______ for an interview.

A. have invited B. have been invited

C. will invite D. will be invited

18. There is every chance that more jobs ______ later this year.

A. will lose B. will be lost

C. have lost D. have been lost

19. There’s still a ray of hope that the missing child ______ alive.

A. was found B. have found C. will find D. will be found

20. Full details of the election results ______ in a special edition of tomorrow’s newspaper.

A. will publish B. will be published

C. have published D. have been published

21. No-one knows how many people ______ since the war began.

A. have killed B. have been killed C. killed D. were killed

22. She has written two novels, both of which ______ into television series.

A. have made B. have been made C. had made D. had been made

23. Due to the recent high cost of borrowing, many companies ______ to close.

A. had forced B. had been forced C. have forced D. have been forced

24. Once the goods ______ for they will be delivered at your convenience.

A. have paid B. have been paid

C. will pay D. will been paid

25. At least fifty four people ______ and a further fifty are missing.

A. have killed B. have been killed

C. will kill D. will be killed

高考英语｜巧解词义猜测题，英语阅读理解满分必备！

猜测词义是应用英语的重要能力，这种题型也是高中英语的必考题型。因此，掌握一定的猜词技巧，对突破高中阶段阅读理解、提高我们的英语语言能力有非常重要的意义。

考查“不明身份”的代词指代

代词指代题要求考生依据语境的逻辑关系，判断画线的人称代词或指示代词在文章中指代的对象，包括考查it(指动物、无生命的事物、特定的事件或人)，they/them(指代人、物、事件的复数名词)，he/she等人称代词的指代意义，以及指示代词this，that，these，those等在文章中的指代意义，以考查考生对文章中叙述的特定的人、物、事件的再认能力。

解答代词指代题时，我们要认真阅读画线词所在句和前后邻近句的内容，分析人称转换和动作变换的详细过程，理清其来龙去脉和前后的因果关系，从而准确推断其指代的对象。

In an effort to prevent language loss, scholars from a number of organizations — UNESCO and National Geographic among them — have for many years been documenting dying languages and the cultures they reflect.

Mark Turin, a scientist at the Macmillan Center, Yale University, who specializes in the languages and oral traditions of the Himalayas, is following in that__tradition. His recently published book, A Grammar of Thangmi with an Ethnolinguistic Introduction to the Speakersand Their Culture, grows out of his experience living, working, and raising a family in a village in Nepal.

33．What does “that tradition” in Paragraph 3 refer to?

A. Having full records of the languages.

B. Writing books on language teaching.

C. Telling stories about language users.

D. Living with the native speakers.

【分析】　A　根据画线词上一段的内容可知，有很多学者一直致力于对快要绝迹的语言和文化的记录工作。再结合画线词所在句可知，耶鲁大学的Mark Turin也在做这件事，即记录语言，防止语言的消失。

考查“熟词生义”的单词词义

英语单词的含义丰富、搭配灵活，一些熟词在不同的语境或不同的搭配中有不同的含义，而这些含义与其本义有时没有密切的联系，这就需要我们结合语境来推断其含义；有时这些单词的新义既体现了其基本含义，又有迁移与拓展。在解答此类词义猜测题时就要求我们将单词的本义和语境有机地结合起来，综合考虑，然后准确推断其在特定语境中的含义。

My husband rushed to their home to find a kind family holding all his papers and documents. Their young daughter had gone to the trash can and found a pile of unfamiliar papers...At last they had seen a half－written letter in the pile in which my husband had given his new telephone number to a friend.

That family not only restored the important documents to us that day but also restored our faith and trust in people. We still remember their kindness and often send a warm wish their way.

23．What does the underlined word “restored” in the last paragraph mean?

A. Showed. B. Sent out.

C. Delivered. D. Gave back.

【分析】　D　restore的含义是“恢复，使复原，修复”，但在本文的语境中，根据上文中的“found”、画线词后面的内容及故事情节的发展可知，此处指作者的丈夫找回了丢失的重要文件，因此give back“归还，还给”，符合语境。

考查“深奥难懂”的单词词义

这种类型是最常见的词义猜测题的命题方式，考查考生猜测文章中某个生词或短语的含义，或考查该词能被哪个单词或短语代替。此时我们可以借助下面这些方法来答题：(关键字:阳光学校,阳光教育集团,石家庄阳光学校,邯郸阳光学校,保定阳光学校,太原阳光学校)

1．“拆猜”并用解决问题

阅读中常常会遇到一些由熟悉的单词派生或合成的新词。此时可以用“拆猜”的方式，先把该词的各种词缀或前后两个合成部分拆开，再结合我们掌握的构词法知识，根据中心词的含义和词缀的含义猜测其意思。

Passenger pigeons (旅鸽) once flew over much of the United States in unbelievable numbers...described flocks (群) so large that they darkened the sky for hours.

It was calculated that when its population reached its highest point, there were more than 3 billion passenger pigeons...making it perhaps the most abundant bird in the world... was seen near Cincinnati.

Sadly, the abundance of passenger pigeons may have been their undoing. Where the birds were most abundant, people believed there was an ever lasting supply and killed them by the thousands.

25．The underlined word “undoing” probably refers to the pigeons'______．

A. escape B. ruin C. liberation D. evolution

【分析】　B　画线词undoing可分解为否定前缀un－和doing。画线词前面叙述了旅鸽数量很多，画线词后提到大量的旅鸽被杀害，结合否定前缀un－和选项看，该词的含义与ruin“毁灭”相近。

2．利用同义词、近义词猜词

在单词所出现的上下文中，有时会出现与之同义或近义的词语或结构，这时考生可从熟悉的词语中推测其含义。

3．利用反义词猜词

对比是描述、说明事物的常用方式。在对比中，对比的事物有可能是相反的，因此可以根据反义关系推测其含义。

4．利用上下文语境猜词

考生可以利用上下文提供的情景和线索，进行合乎逻辑的综合分析进而推测词义。

5．利用定义或解释猜词

释义是对单词以定语(从句)、表语甚至用逗号、破折号等标点符号引出并加以解释说明的方式。有些文章，特别是科研报告类的文章，通常会给一些关键词下定义，考生可以利用定义来猜测这些词的意思。

6．利用例证猜词

为了进行说明或证实，文章中经常会举例，用来列举说明前面较难理解的词，这些例子可帮助考生猜测单词词义。举例时，常常会用一些表列举的词，如：such as, like, for example, for instance等。

7．利用复述或同等关系猜词

为了强调某个观点或把某事叙述得更明白，作者有时会运用不同语句来复述同一概念，这时考生可以利用这些重复叙述的语句和表达形式的变化来猜测词义。虽然复述不如定义那样严谨、详细，但是提供的信息足以使考生猜出单词词义。只要我们找出其中一个或几个词或短语，便可确定同等关系中单词的词性、作用和大概的意思。

8．利用词义搭配、关联猜词

任何一个单词在句子中总是与其他词相关联的，考生可以通过这些前后的关联来猜测单词的词义。

9．利用语义转折猜词

有时作者为了增强表达效果，在文章中会用一些表示转折意思的连词、副词或短语，如：though, although, but, yet, instead, however, while, rather than等，考生可以根据转折的语境猜测词义。

考查句意理解

考查句意理解的试题一般因为句式复杂、意义含蓄而出现在长难句中。对于这种试题，考生应该认真阅读原文，特别是画线句子的上下文，准确理解作者的观点，尤其是对特定的人、物、事件的褒贬观点，以准确推断语句的含义。

Sampal's story began in 2011, when she was accidentally caught by fishermen in the waters off South Korea. However, instead of letting her go, the men sold her to an aquarium. Here, she was placed in a small pool where she spent her days performing tricks for visitors.

Sampal_was_not destined_to_spend_her_life_in_captivity. Shocked by the conditions she was living in, South Korean animal advocates began to help her get free.

32．What does the underlined sentence in Paragraph 3 probably mean?

A. Sampal didn't like spending her life in a pool.

B. Sampal would have to lose her freedom.

C. Sampal's life was brought back to normal.

D. Sampal would certainly be helped by people.

【分析】　D　前面谈到Sampal被捕捉之后的命运，画线句子后说到韩国动物保护者开始展开营救工作，因此选D项，她肯定会得到人们的帮助。(关键字:阳光学校,阳光教育集团,石家庄阳光学校,邯郸阳光学校,保定阳光学校,太原阳光学校)

最后提醒考生，掌握了一定的单词猜测技巧后，也不要去“死抠”个别词，除了人名、地名等一些专有名词不必去细究之外，那些一时难以断定其意思却又不妨碍理解或答题的单词，大可不必理会。

Linux从12c non-CDB升级到18.0.0 non-CDB手动

其他相关文章

Redhat 7.x 从11.2.0.4升级到18.0.0(DBUA)

从11.2.0.4升级到18.0.0 non-CDB(手动)

从11.2.0.4升级到18.0.0 non-CDB(手动)

说明

本节通过手动执行脚本方式升级，因为使用DBUA升级方式过于简单，参考前面章节即可。过程也非常简单，首先安装新版本的数据库软件并创建数据库(CDB模式)，然后将non-CDB插入到CDB中。

1.1.1. 源库准备工作

1) 数据库版本

数据库版本是12.2.0.1，支持直接升级到18c.

SQL> select * from v$version where rownum=1;BANNER CON_ID----------------------------------------------------------------------------------------------------- ------------------ORACLE Database 12c Enterprise Edition Release 12.2.0.1.0 - 64bit Production 0

2) 是否是CDB

为non-CDB模式

SQL> select name,cdb from v$database;NAME CDB--------- --------CNDBA NO

3) 全库备份

升级前建议进行备份，以防万一。

rman "target / nocatalog"RUN{ALLOCATE CHANNEL chan_name TYPE DISK;BACKUP DATABASE FORMAT '<db_backup_directory>%U' TAG before_upgrade;BACKUP CURRENT CONTROLFILE TO '<controlfile_backup_directory>';}

4) 执行检查脚本

这里不再具体说明，请参考其他升级文章：从11.2.0.4升级到18.0.0 non-CDB(手动)。

5) 开启归档和闪回

查看是否开启闪回和归档

SQL> select log_mode,flashback_on from v$database;LOG_MODE FLASHBACK_ON------------ ------------------ARCHIVELOG YES

没有则手动开启归档和闪回。

shutdown immediate;startup mount;alter database archivelog;alter database flashback on;

6) (可选)如果是RAC，则修改CLUSTER_DATABASE为FALSE

ALTER SYSTEM SET CLUSTER_DATABASE=FALSE SCOPE=SPFILE;

7) 关闭数据库

shutdown immediate

1.1.2. 目标库准备工作

1) 安装18c数据库软件

具体步骤略，请参考：从11.2.0.4升级到18.0.0 non-CDB(手动)。

2) oratab文件是否指向新的Oracle_HOME

[oracle@cndba ~]$ tail -1 /etc/orataborcl:/u01/app/oracle/product/18.1.0/db_1:N

3) 将环境变量修改为新版本数据库的目录

例如：ORACLE_HOME，ORACLE_BAES，PATH等

[oracle@12cr1 ~]$ env|grep ORACLE_HOMEORACLE_HOME=/u01/app/oracle/product/18.1.0/db_1

4) 将源库的spfile拷贝目标库

cp /u01/app/oracle/product/12.2.0/db_1/dbs/spfilecndba.ora /u01/app/oracle/product/18.1.0/db_1/dbs/

5) 以UPGRADE方式打开数据库

SQL> startup upgrade;ORACLE instance started.Total System Global Area 1560280224 bytesFixed Size 8658080 bytesVariable Size 1006632960 bytesDatabase Buffers 536870912 bytesRedo Buffers 8118272 bytesDatabase mounted.Database opened.

1.1.3. 正式升级

1) 退出所有SQL*PLUS，执行升级脚本

[oracle@12cr1 ~]$ cd /u01/app/oracle/product/18.1.0/db_1/bin/[oracle@12cr1 bin]$ ./dbupgrade -n 4 -d /u01/app/oracle/product/18.1.0/db_1/RDBMS/admin/ -l /tmp/Argument list for [/u01/app/oracle/product/18.1.0/db_1/rdbms/admin/catctl.pl]Run in c = 0Do not run in C = 0Input Directory d = /u01/app/oracle/product/18.1.0/db_1/rdbms/admin/Echo OFF e = 1Simulate E = 0Forced cleanup F = 0Log Id i = 0Child Process I = 0Log Dir l = /tmp/Priority List Name L = 0Upgrade Mode active M = 0SQL Process Count n = 4SQL PDB Process Count N = 0Open Mode Normal o = 0Start Phase p = 0End Phase P = 0Reverse Order r = 0AutoUpgrade Resume R = 0Script s = 0Serial Run S = 0RO User Tablespaces T = 0Display Phases y = 0Debug catcon.pm z = 0Debug catctl.pl Z = 0catctl.pl VERSION: [18.0.0.0.0]STATUS: [Production]BUILD: [RDBMS_18.1CLOUD_LINUX.X64_180131.2]/u01/app/oracle/product/18.1.0/db_1/rdbms/admin/orahome = [/u01/app/oracle/product/18.1.0/db_1]/u01/app/oracle/product/18.1.0/db_1/bin/orabasehome = [/u01/app/oracle/product/18.1.0/db_1]catctlGetOrabase = [/u01/app/oracle/product/18.1.0/db_1]Analyzing file /u01/app/oracle/product/18.1.0/db_1/rdbms/admin/catupgrd.sqlLog File directory = [/tmp/]catcon::set_log_file_base_path: ALL catcon-related output will be written to [/tmp/catupgrd_catcon_30640.lst]catcon::set_log_file_base_path: catcon: See [/tmp/catupgrd*.log] files for output generated by scriptscatcon::set_log_file_base_path: catcon: See [/tmp/catupgrd_*.lst] files for spool files, if anyNumber of Cpus = 1Database Name = cndbaDataBase Version = 12.2.0.1.0Parallel SQL Process Count = 4Components in [cndba]Installed [APS CATALOG CATJAVA CATPROC CONTEXT DV JAVAVM OLS ORDIM OWM SDO XDB XML XOQ]Not Installed [APEX EM MGW ODM RAC WK]------------------------------------------------------Phases [0-108] Start Time:[2018_07_12 12:17:41]------------------------------------------------------*********** Executing Change Scripts ***********Serial Phase #:0 [cndba] Files:1略….Serial Phase #:104 [cndba] Files:1 Time: 16s**************** Summary report ****************Serial Phase #:105 [cndba] Files:1 Time: 2s*** End PDB Application Upgrade Post-Shutdown **Serial Phase #:106 [cndba] Files:1 Time: 0sSerial Phase #:107 [cndba] Files:1 Time: 0sSerial Phase #:108 [cndba] Files:1 Time: 24s------------------------------------------------------Phases [0-108] End Time:[2018_07_12 13:09:40]------------------------------------------------------Grand Total Time: 3120sLOG FILES: (/tmp//catupgrd*.log)Upgrade Summary Report Located in:/tmp//upg_Summary.logGrand Total Upgrade Time: [0d:0h:52m:0s]

2) 打开数据库，编译PL/SQL和java代码

SQL> startupORACLE instance started.Total System Global Area 1560280224 bytesFixed Size 8658080 bytesVariable Size 1006632960 bytesDatabase Buffers 536870912 bytesRedo Buffers 8118272 bytesDatabase mounted.Database opened.[oracle@12cr1 db_1]$ cd $ORACLE_HOME/rdbms/admin[oracle@12cr1 admin]$ $ORACLE_HOME/perl/bin/perl catcon.pl -n 1 -e -b utlrp -d '''.''' utlrp.sqlcatcon::set_log_file_base_path: ALL catcon-related output will be written to [/u01/app/oracle/product/18.1.0/db_1/rdbms/admin/utlrp_catcon_7595.lst]catcon::set_log_file_base_path: catcon: See [/u01/app/oracle/product/18.1.0/db_1/rdbms/admin/utlrp*.log] files for output generated by scriptscatcon::set_log_file_base_path: catcon: See [/u01/app/oracle/product/18.1.0/db_1/rdbms/admin/utlrp_*.lst] files for spool files, if anycatcon.pl: completed successfully[oracle@12cr1 admin]$

3) 执行修复脚本

对于没有修复成功的问题，需要手动进行处理，处理方法参考前一节。

SQL> @/u01/app/oracle/cfgtoollogs/cndba/preupgrade/postupgrade_fixups.sqlAuto-Generated by: Oracle Preupgrade ScriptVersion: 18.0.0.0.0 Build: 3Generated on: 2018-07-12 10:43:02For Source Database: CNDBASource Database Version: 12.2.0.1.0For Upgrade to Version: 18.0.0.0.0Preup PreupgradeAction Issue IsNumber Preupgrade Check Name Remedied Further DBA Action------ ------------------------ ---------- --------------------------------4. old_time_zones_exist YES None.5. post_dictionary YES None.6. post_fixed_objects NO Informational only.Further action is optional.The fixup scripts have been run and resolved what they can. However,there are still issues originally identified by the preupgrade thathave not been remedied and are still present in the database.Depending on the severity of the specific issue, and the nature ofthe issue itself, that could mean that your database upgrade is notfully complete. To resolve the outstanding issues, start by reviewingthe postupgrade_fixups.sql and searching it for the name ofthe failed CHECK NAME or Preupgrade Action Number listed above.There you will find the original corresponding diagnostic messagefrom the preupgrade which explains in more detail what still needsto be done.PL/SQL procedure successfully completed.Session altered.

4) 查看组件是否正常

执行脚本utlu122s.sql验证所有组件是否工作正常。

SQL> @$ORACLE_HOME/rdbms/admin/utlu122s.sqlOracle Database Release 18 Post-Upgrade Status Tool 07-12-2018 14:11:2Component Current Full Elapsed TimeName Status Version HH:MM:SSOracle Server VALID 18.1.0.0.0 00:30:14JServer JAVA Virtual Machine VALID 18.1.0.0.0 00:03:06Oracle XDK VALID 18.1.0.0.0 00:00:46Oracle Database Java Packages VALID 18.1.0.0.0 00:00:22OLAP Analytic Workspace VALID 18.1.0.0.0 00:00:45Oracle Label Security VALID 18.1.0.0.0 00:00:17Oracle Database Vault VALID 18.1.0.0.0 00:00:39Oracle Text VALID 18.1.0.0.0 00:01:04Oracle Workspace Manager VALID 18.1.0.0.0 00:00:54Oracle Real Application Clusters OPTION OFF 18.1.0.0.0 00:00:00Oracle XML Database VALID 18.1.0.0.0 00:01:58Oracle Multimedia VALID 18.1.0.0.0 00:02:19Spatial VALID 18.1.0.0.0 00:06:10Oracle OLAP API VALID 18.1.0.0.0 00:00:27Upgrade Datapatch 00:00:15Final Actions 00:00:31Post Upgrade 00:00:16Post Upgrade Datapatch 00:00:11Post Compile 00:10:29Total Upgrade Time: 01:00:47Database time zone version is 26. It is older than current release timezone version 31. Time zone upgrade is needed using the DBMS_DST package.Summary Report File = /tmp//upg_summary.log

可以看到都正常。

5) 查看无效对象

SQL> select owner,object_type,count(*) from dba_objects where status='INVALID' group by owner,object_type order by owner,object_type;no rows selected

6) 修改COMPATITLE参数

在所有测试完成后且结果都正常，那么就可以将COMPATITLE参数设置为18.0.0。

l 查看COMPATITLE

SQL> show parameter compatibleNAME TYPE VALUE------------------------------------ ----------- ------------------------------compatible string 12.2.0noncdb_compatible boolean FALSE

l 修改COMPATITLE

SQL> alter system set compatible='18.0.0' scope=spfile;System altered.

l 重启之前要删除所有的还原点

SQL> col name for a30SQL> select scn,GUARANTEE_FLASHBACK_DATABASE,NAME from v$restore_point;SCN GUA NAME------------ --------- ------------------------------1493536 YES GRP_15312104323351 row selected.SQL> drop restore point GRP_1531210432335;Restore point dropped.

l 重启数据库

SQL> shutdown immediateSQL> startup

l 再次查看COMPATITLE

COMPATITLE参数一旦修改了，就无法降级数据库到原来的版本了。

SQL> show parameter compatibleNAME TYPE VALUE------------------------------------ ----------- ------------------------------compatible string 18.0.0noncdb_compatible boolean FALSE