The Dominant Operating: Microsoft Windows Platform – Lab Report Example
Lab Exercise and 2 Summaries and Lessons Learnt Lab Exercise The first lesson learnt from the first lab session was the possibility of more than two operating systems running adjacent to each other. Previously, one platform of operating system was the norm in most machines, and the dominant operating system had a Microsoft Windows platform.
A PXE menu is a vital tool utilized in a network of machines that equips the user with the ability to select the booting sequence of either the network or the local machine. The Image Management System, one of the choices in the PXE menu, is another significant tool that enables the user to load up hard disk images saved previously in an initial usage of the computer. These images are beneficial since they not only enable a user to save his or her work, but also be able to reload it in future using the PXE and IMS tools.
Both Linux Fedora and Windows XP operating systems require an equal measure of security before accessing their respective systems. However, each system could be configured to attain various levels of privileges by creating various accounts with the root in Linux being the equivalent of the administrator in the Windows XP operating system.
The Command Line is an application utilized in both Windows XP and Linux Fedora, named as command prompt and a terminal or shell respectively. These implement lines of instructions that load up various applications and save them (Simpson 976). However, both operating systems implement GUI, rather, Graphical User Interface, that is a simpler implementation of giving instruction to the systems comprising of images and icons.
Lab Exercise 2
Dual-booting is a technique enabled within a machine that could allow it to boot with more than two operating systems, in this case, Windows XP and Linux Fedora, but not in a simultaneous order. From the procedures in the second lab session, it was clear that Linux had a more superior boot loader, referred to as Grand Unified Bootloader (GRUB), than its alternate in windows platform. It is, therefore, advisable to ensure that Linux installation comes after Windows or any other alternate operating system given its superiority in booting other operating systems.
Saving is a significant activity after performing any procedure with the computer, regardless of how insignificant it is. This is so as to enable recovery of the same in case there is a mishap while performing other tasks on the host machine. In this procedure, there is an overemphasis on saving, given the delicacy of installing more than two operating systems on the machine for dual-booting capabilities.
Success in booting from the web server or any subsequent server requires the user to set its proxies in the correct format and give an accurate reference to each command. This ensures that the system loads from the correct directories. Any mistakes such as an unnecessary space or misspelling could result to failure in implementing the intended task.
While installing Linux or any other operating system whatsoever, it is vital to stick to the instructions; select the relevant and appropriate procedures that would satisfy the objective of each task. Failure to do this could lead to lack of the adequate functionalities initially intended on the operating system, a mistake that could prompt for a repeat of the cumbersome procedure of installation and a potential loss of data.
Installing Linux requires precise acquaintance of the partitions required (Petersen 254). Failure to name and allocate correct file system types and sizes could lead to either underperformance or overall failure of the entire booting system.
Changing either Linux or Windows configuration is possible especially using the command line interface of the respective operating system. Configurations help users modify the system according to their preferences.
Backing up is an essential procedure as learnt in the final step. Users make backups using external memory media that store data safely in case the machine fails in any way. If a machine fails without prior saving of the tasks that were being worked on, any efforts aimed at reviving it using the IMS will not succeed.
Petersen, Richard. Publisher: Fedora Core 7 & Red Hat Enterprise Linux: The Complete Reference. New York, NY: McGraw-Hill Osborne Media, 2007. Print.
Simpson, Alan. Alan Simpsons Windows XP Bible. 2nd ed. Malden, MA: Wiley, 2005. Print.