What's It?

Geek vocab.

kernel Heart, or core, of the Unix operating system. Called the traffic cop since it is responsible for managing all the elements that make up the system. Manages the interface between user programs and input/output system. Only portion of the Unix operating system which interacts with the hardware. Therefore, the only part of Unix which is modified for use by different computers.

interrupt Either a hardware- or software-generated signal that causes a temporary break in the normal flow, or context, of a running system. When an interrupt is detected, the kernel blocks off (and thus prevents) lower priority interrupts, saves the context of the process being run and services the interrupt. After servicing the interrupt, the kernel restores the process context and resumes execution. If the interrupt detects an error condition, e.g., a divide by zero, the kernel may simply abort the process and select another for execution. or use interpreter, which you already have; use any two that fit.

Copyright 1994 William H. Holt. Reprinted with permission from UNIX: An Open Systems Dictionary, by William H. Holt & Rockie J. Morgan, published by Resolution Business Press.

______________________

White Paper
Fabric-Based Computing Enables Optimized Hyperscale Data Centers

Today’s modular x86 servers are compute-centric, designed as a least common denominator to support a wide range of IT workloads. Those generic, virtualized IT workloads have much different resource optimization requirements than hyperscale and cloud applications. They have resulted in a “one size fits all” enterprise IT architecture that is not optimized for a specific set of IT workloads, and especially not emerging hyperscale workloads, such as web applications, big data, and object storage. In this report, you will learn how shifting the focus from traditional compute-centric IT architectures to an innovative disaggregated fabric-based architecture can optimize and scale your data center.

Learn More

Sponsored by AMD

White Paper
Red Hat White Paper: Using an Open Source Framework to Catch the Bad Guy

Built-in forensics, incident response, and security with Red Hat Enterprise Linux 6

Every security policy provides guidance and requirements for ensuring adequate protection of information and data, as well as high-level technical and administrative security requirements for a system in a given environment. Traditionally, providing security for a system focuses on the confidentiality of the information on it. However, protecting the data integrity and system and data availability is just as important. For example, when processing United States intelligence information, there are three attributes that require protection: confidentiality, integrity, and availability.

Learn more about catching the bad guy in this free white paper.

Learn More

Sponsored by DLT Solutions