So my operating system repeatedly asks for my approval to proceed with a critical patch.
This has happened many times over my lifelong adventures with various Operating Systems, which range from flings with Microsoft Windows to serious relationships with MacOS and Red Hat Enterprise Linux.
Patching of these operating systems are never that straight forward, regardless of what the manual or online documentation tells you.
The fact is, patching can fail and to varying degrees of mayhem.
So whenever patching fails for Macbooks and WinTel machines that I occasionally commandeer, the system could be stuck in a loop, attempting to bootup and failing eventually.
The same phenomenon occurred on the notebook computer, that is powered by the more popular variant of Linux. known as Red Hat Enteprise Linux, that I now call my workstation. A critical patch failed and it resulted in the emergency shell prompt to appear upon startup.
Despite my best efforts to proceed with a manual intervention of the workstation startup, it just does not proceed.
After much investigation and research on Google, it seems the patching process is attempting to proceed upon system reboot. However, Red Hat Enteprise Linux set the filesystem of the partitions on my notebook computer to read-only, as a safety precaution, upon patching failure.
In order to resume patching, the filesystem on my notebook computer has to be set to read-write. And that was what I did, to complete my patch process and resume normal business operations.
