求翻译：　　有一些RTOS试图通过使用单内核架构来解决这个问题。在这种架构中，用户的应用程序在隔离的、受保护内存地址空间中运行。如果一个应用程序试图访问其地址空间之外的数据，内存管理单元（MMU）将通知操作系统，操作系统可能会采取保护措施，例如终止出错进程。由于这样的操作系统需要将大多数或所有驱动程序、文件系统和其它系统服务绑定到内核中，因此任何组件中的一个错误都可能带来灾难性的内核故障。采用微内核（mricokernel）架构可提供更精确的故障隔离，如QNX Neutrino等操作系统都基于微内核架构。微内核有两个明确的特征：（1）在操作系统内核中只实现了一个包含了基本OS服务的小内核（如信号量、定时器、任务调度等），包括驱动程序、文件系统、协议栈和用户应用程序在内的所有其它的组件在内核外部分离的、保护内存的进程中运行。有问题的系统服务不再作为孤立的故障点，而是在破坏其它服务或操作系统内核之前被终止并重启。（2）所有的组件能够通过消息传递进行通信，一个定义良好的通信机制保障了程序在保持彼此安全隔离的前提下进行数据交换。适当实现的消息传递也可以作为一个虚拟的“软件总线”，允许任何的软件组件，甚至是一个设备驱动程序被动态地加入或替换，对于必须提供连续服务的系统而言这是一项关键要求。是什么意思？

　　Some RTOS trying to solve this problem by using single-core architecture. In this schema, the user's applications run in isolation, protected memory address space. If an application attempts to access data outside of their address space, memory management unit (MMU) will notify the operating system, the operating system may take protective measures, for example an error terminates a process. Because of this operating system that most or all of the drivers, file system and other system services is bound to the kernel, so in any of the components of an error may cause a catastrophic kernel failure. Using micro-kernel (mricokernel) architecture provides more granular fault isolation, such as operating systems such as QNX Neutrino microkernel-based architecture. Micro-kernel has two clear features: (1) in the operating system kernel implements a contains only a small core of basic OS services (such as a semaphore, timer, task scheduling, etc), including drivers, protocol stacks, file systems, and all other components, user application isolation, protected memory outside of the kernel runs in the process. Problem of system services that are no longer as isolated points of failure, but prior to the destruction of other services, or the operating system kernel is terminated and restarted. (2) all of the components to communicate by message passing, a well defined communication mechanisms to protect the program on the premise of keeping each other safe isolation data exchange. Appropriate implementation of messaging can also be used as a virtual "software bus", allowing any software components, or even to join or replace a device driver is a dynamic, for the system must provide continuous service, this is a key requirement.