Assignment of Network Administration
Assignment of Network Administration
1.
How
happens, what tasks are handled by the hardware and what tasks are handled by
the OS?
1. Interrupt Generation: When an event occurs that triggers an interrupt, the device generates an
electrical signal that is sent to the CPU.
2. Interrupt Request: The CPU receives the interrupt request and pauses its current task.
3. Interrupt Vector Table: The CPU uses the interrupt request to look up an entry in the interrupt
vector table. This table contains the memory address of the interrupt service routine (ISR) that
should be executed to handle the interrupt.
1. Interrupt Service Routine (ISR): The OS provides the ISR that will be executed to handle the
interrupt. This routine may be part of the OS kernel or a device driver.
2. Interrupt Handling: The ISR performs the necessary actions to handle the interrupt, such as
reading or writing data to a device, updating system state, or scheduling a task.
3. Privileged Instructions
Privileged instructions are those that can potentially modify or compromise the system's
security or stability. Here's why the following instructions should be privileged:
a) Set value of timer: Modifying the timer can affect system timing and scheduling.
d) Turn off interrupts: Disabling interrupts can prevent the system from responding to
critical events.
e) Switch from user to monitor (kernel) mode: This transition grants access to
privileged instructions and system resources.
Instructions like b) Read the clock and c) Set memory content to zero can be non-privileged
as they do not directly affect system security or stability.
Another approach is to use a specific memory location or register to store syscall requests. The
kernel can periodically check this location and handle any pending requests.
Interactive user interfaces: Providing a graphical environment for users to interact with
the system
Network connectivity: Supporting communication with other computers and devices.
applications such as web browsers and mail programs. Argue both pro and
The question of whether applications like web browsers and mail programs should be
considered part of the OS is a complex one.
1. Flexibility: If applications are bundled with the OS, it can limit flexibility. Users may not be able
to easily install or remove applications based on their specific needs.
2. Innovation: Keeping applications separate from the OS can foster innovation. Independent
developers can create and distribute applications without relying on the OS vendor's approval.