How levichu51/sistemasoperativos-practicas-23-24 works
• P1 – Filesystem and shell history management (using p3.c and lista_hist.c/h)
• P2 – Memory management (using p2_functions.c and lista_mem.c/h)
• P3 – Process management (using p3_functions.c and lista_procesos.c/h)
Main components
a. Central Shell: This is the user interface where commands are interpreted.
b. Filesystem/History Module (P1): Handles file system-related operations and command history.
c. Memory Management Module (P2): Manages aspects related to memory handling and its supporting linked list operations.
d. Process Management Module (P3): Deals with process control, management of processes via linked lists, etc.
e. Build/Compilation Infrastructure: Represent the MakeFile which is used to compile and link all modules.
Relationships and interactions
• The Shell is the primary interface and dispatches commands to the appropriate module.
• For operations like listing history or file management, the Shell calls functions provided by the P1 module (implemented in p3.c and supported by lista_hist.c/h).
• When memory management is needed (e.g., allocation and memory state queries), the Shell interacts with the P2 module (using p2_functions.c and lista_mem.c/h).
• For process control or execution, the Shell utilizes the P3 module (via p3_functions.c and lista_procesos.c/h).
• The MakeFile (or Makefile) integrates the compilation process, tying all of these components together.
Architectural patterns and design principles
• Modularity: Each practice (P1, P2, P3) is separated into its own component, fostering separation of concerns.
• Layered Interaction: The Shell acts as a high-level controller that invokes the underlying modules based on user commands.
• Loose Coupling: While each module performs distinct operations, they are exposed via well-defined header files (e.g., p1.h, p2_functions.h, p3_functions.h), which minimizes interdependencies.
Relevant technologies and languages
• C Programming Language: The core language for implementing the Shell and its modules.
• Make: Utilized as a build tool to compile and link these modules conveniently.
• Standard libraries and possibly OS-level APIs for file, memory, and process management are implicit.