Edward's CS Journey

Persistence as it applies to operating systems and a CS Online Student Persistence in operating systems ensures that data is saved and managed even after a process is completed. It ensures that the operating system can save the data from a process when it writes to a file so it can be restored or resumed at a later time. The data will still exist after the process that created it has ended. Mechanisms such as file systems are used to save and manage data after a process is done. The contents of file systems are stored in non-volatile memory, such as a Hard Drive Disk or Solid State Drive, so that data is saved even in the event of power loss, reboots, or crashes. It is important that an operating system reinforces persistence so that data can be used in different applications, devices, and programs after a process finishes.  In a way, we, as CS students, should follow the path of persistence. In our studies, we will encounter blockades and obstacles and need to find strategies and tech

Persistence  This week, we learned about persistence in operating systems. Persistence involves managing data and devices so that their state is maintained even if a system loses power intentionally or unintentionally. When interacting with I/O devices, the OS can communicate with them by using I/O instructions or memory-mapped I/O. When dealing with different interfaces, we can build an abstract file system on top of a block interface. This will help with managing the data from the device.  To make storage persistent, we can use Hard Drive Disks or Solid State Disks. In most cases, Hard Drive Disks are used for storage persistence. We can manage and organize data on either of these storage by using two key abstractions: files and directories. A file is a linear array of bytes that are stored persistently. It usually consists of a human-readable file and has an OS-level identifier called an inode number. A directory consists of subdirectories and files with inode numbers.  File operati