At load time, the system loader then loads the bit-appropriate kernel extension.
在加载时，系统加载器加载相应位的内核扩展。
This function is called by the operating system loader for DLL assemblies.
DLL组件的作业系统载入器会呼叫这个函式。
Before any program can run, the operating system loader must load it into real memory.
在运行任何程序之前，操作系统装载器必须将它装载到实际内存中。
The operating system loader calls this method regardless of the entry point specified in the image file.
不论影像档中指定的进入点为何，作业系统载入器都会呼叫这个方法。
On a program's start, the system loader reads these instructions and loads the appropriate DLLs into the process 'address space.
程序启动时，程序会根据这些指令的说明把一些相关的dll加载进程序的内存空间中来。
During binary loading, the te sub system is called by the system loader, which calculates the hash using the SHA-256 hash algorithm.
在二进制加载期间，系统加载程序调用te子系统，并使用SHA- 256散列算法来计算散列值。
Here, we use reflection because we have loaded the application using a class loader that is not the system class loader.
这里，我们使用反射的原因是因为我们已经使用非系统类加载器加载了应用程序。
It USES the system class loader to achieve this.
它使用系统类装载程序来达到这个目的。
At this stage, the second-stage boot loader checks the system hardware, enumerates the attached hardware devices, mounts the root device, and then loads the necessary kernel modules.
在这个阶段中，第二阶段的引导加载程序会检测系统硬件、枚举系统链接的硬件设备、挂载根设备，然后加载必要的内核模块。
EFI includes its own boot loader, so you can boot from a GPT disk on an EFI-based system.
EFI包含自己的引导装载程序，因此您可以在一个基于EFI的系统上从一个GPT磁盘引导。
After POST, the loader from a ROM loads the boot sector, which then loads the operating system from the active partition.
在POST之后，ROM中的加载程序将载入引导扇区，该扇区随后将从活动分区中载入操作系统。
This is because B is not in the classpath of the system class loader or its parent or ancestor class loaders.
这是因为B不在系统类装入器或者它的双亲或祖先类装入器的类路径中。
While the simplest way to avoid class loader constraint violations is to only have one copy of a class in the system, it is sometimes necessary to have multiple versions.
虽然避免类装入器约束违反的最简单方法是在系统中只有类的一个副本，但有时拥有多个版本也是有必要的。
The FOCAL system is provided as a paper-tape image used in the binary loader format (see Listing 6).
FOCAL系统是作为用于二进制加载器格式的纸带图像而提供的(请单考清单6)。
The easiest way to resolve this problem is to ensure that there is only one copy of a class in the system — that is, that the class only appears in the classpath of one loader.
解决这个问题的最简单方法是确保在系统中只有类的一个副本——也就是说，类只出现在一个类装入器的类路径中。
Instead, it has a set of class loaders that are unrelated except that they have the same parent (usually the system class loader).
相反，它有一组类装入器，彼此互不相关，但是有共同的双亲(通常是系统类装入器)。
Because these are trusted system classes, the bootstrap loader skips much of the validation that gets done for normal (untrusted) classes.
因为这些是可信的系统类，所以引导程序装入器跳过了对常规(不可信)类所做的大量验证。
You can use GRUB or LILO to pass parameters to the kernel to control the way that your kernel starts the system once it has been loaded by the boot loader.
您可以使用GRUB或LILO来将参数传递到内核，控制内核被启动加载程序加载后启动系统的方式。
The LILO boot loader expanded the boot capabilities, but lacked any file system awareness.
LILO引导加载程序对引导能力进行了扩充，但是它却缺少文件系统的感知能力。
I like things that don't take up very much code, so Maypole currently uses a model class system based on Class::DBI::Loader.
我喜欢不用很多代码就能实现的东西，因此Mayple当前使用了一个基于Class::DBI::Loader 的模型类系统。
To lessen the risk of getting a bad configuration for the boot loader in RHEL 4 or 5, always create a boot partition (/boot) for your system.
为缓解在 RHEL4或5 中得到不良引导载入程序配置的风险，应总是为系统创建一个引导分区 (/boot)。
So whilst in a traditional application, classes from a logging library, a client and server JAR may be loaded by the same class loader, in an OSGi module system, each would be loaded by their own.
因此，尽管在传统应用中，来自logging类库、client和serverJAR中的类都是由同一个类加载器加载的，但在OSGi模块系统中，他们都是由自己的类加载器加载的。
If these classes are available in the classpath, the parent of the URLClassLoader instance, which is the system class loader, will load them.
如果这些类在类路径中可用，URLClassLoader实例的父加载器(即系统类加载器)将加载它们。
For a hard drive, the MBR loads a stage 1 boot loader, which is typically either the LILO or GRUB stage1 boot loader on a Linux system.
对于硬盘驱动器，mbr加载一个阶段1启动加载程序，该程序通常是Linux系统上的LILO或GRUB阶段1启动加载程序。
The problem with this approach is that the LogManager instance uses the system class loader to instantiate classes from the configuration file.
这种方法的问题是LogManager实例使用了系统类的装载程序从配置文件中对类进行实例化。
Stage 1 (MBR) boots a stage 1.5 boot loader that understands the particular file system containing the Linux kernel image.
阶段1 (MBR)引导了一个阶段1.5的引导加载程序，它可以理解包含Linux内核映像的特殊文件系统。
Download the binary images for the boot loader and root file system from the Angstrom BeagleBoard demo page. There files you need are.
为引导加载器和文件系统从angstromBeagleBoard页面下载二进制映像。
This class loader loads the core system classes from the boot classpath, which is normally the JAR files located in the jre/lib directory.
这个类装入器可以从启动的类路径装入核心系统类，通常是位于jre/lib目录的JAR文件。
This class loader loads the core system classes from the boot classpath, which is normally the JAR files located in the jre/lib directory.
这个类装入器可以从启动的类路径装入核心系统类，通常是位于jre/lib目录的JAR文件。
应用推荐