Difficulty: Medium
Correct Answer: 2GB
Explanation:
Introduction / Context:
Swap space extends virtual memory beyond physical RAM, enabling processes to run when RAM is fully utilized. Historical kernel versions imposed strict limits on the size of a single swap area. Administrators working with legacy systems must know these constraints to plan partitioning correctly.
Given Data / Assumptions:
Concept / Approach:
Linux kernels have evolved in their swap area limits. In the 2.2.x era, a single swap partition supported up to approximately 2GB. Systems could employ multiple swap areas (activated via swapon) to increase total swap beyond this per-area cap, but each individual area had its own limit.
Step-by-Step Solution:
Verification / Alternative check:
Consult man mkswap and historical kernel documentation for 2.2.x. Cross-reference with distribution release notes from that period, which typically confirm the 2GB per swap area limit and the ability to use several swap areas concurrently.
Why Other Options Are Wrong:
Common Pitfalls:
Confusing per-area limits with total swap limits; overlooking differences between swap partitions and swap files; failing to align swap size with RAM and workload needs on legacy systems. Modern kernels may have different limits, so always align guidance with the actual kernel version.
Final Answer:
2GB
Discussion & Comments