Analysis of the Windows 7 Operating System For Microsoft to abandon its traditional approaches of defining memory management through a multi-threaded and often pre-emptive memory management design, the recognition of how critical it was from a design standpoint to stay in parity with UNIX and Linux is seen in the Windows 7 design (Spring, 2008). The concept of a kernel is predicated on recompilation of key system attributes during each run-time, in effect re-configuring and customizing the system with each boot-up sequence (Phillips, 1996)
Featuring as its graphical user interface the X-Window system (or X11) that provides rich input capability for networked computers, Linux can run multiple X window systems at once. As per its command-line interface, it has one that is equally powerful to that of Windows with its line being able to recover the system if the graphic subsystem fails (Horowitz, 2007 )
The downside is that disk fragmentation occurs as a result resulting in slower processing. Windows default file system also causes files to become fragmented, degrading the performance of the system significantly over time (Lettice, 2011)
Microsoft made significant improvements in their operating system design when they transitioned from MS-DOS to the Microsoft Windows platform. For the first time applications could share all the same system calls and APIs across all version of the operating system, cutting development time down by months (Bradley, 2009)
Finally the levels of security inherent in the Microsoft Windows operating system continue to be problematic (Bradley, 2009). The Linux and UNIX operating systems are comparable in terms of kernel and memory architectures (MacKinnon, 1999)(Predd, Cass, 2005)
The concept of tenancy and topology being dependent on each other, where the topology determines the functionality of the operating systems is completely wrong. The latest development in Web Services, where ubiquity through software-based service that tracks the state or status of any application connected to it, makes topology irrelevant (Malatras, Asgari, Bauge, Irons, 2008)
The fallacy of network latency being zero or nearly in real-time is also false as many factors go into the latency calculations for any transaction or query online. Distributed operating systems also initially assumed that due to their topology they would be inherently secure (Mullender, 1996)
In fact nothing could be further from the truth, as Service oriented Architectures have proven that multi-system integration is crucial for the development of an effective network platform and environment (Malatras, Asgari, Bauge, Irons, 2008). This fallacy of network homogeneity is also seen in how diverse and potentially conflicting the data sets are in Web Services platforms today, specifically on the Android platform (Pocatilu, 2010)
Microsoft designed Windows Services for UNIX to support 300 different UNIX commands including KornShell, C Shell and the common commands of awk and text editor vi for example. The high degree of modularity of the Microsoft Server system architecture is easily customizable yet also presents security risks as well (Hartley, 2008)
Comparing Kernels and Application Programmer Interface (API) The design of each operating systems' kernel is significantly different, varying on how each support I/O management, memory management, scheduling, power and thread management. One of the most significant differences between the kernels of these operating systems is how each define and use subsystems for completing application development while supporting deployment, delivering a high level of reliability at the system level (Janssens, Annot, van de Goor, 1986)
One of the most significant differences between the UNIX and Windows operating system architectures is that the former recompiles the system-level kernel at runtime. Database developers have favored the UNIX platform as a development environment as a result of this feature, as it makes the task of troubleshooting application development much more accurate and efficient (Son, Lee, Jeon, Chung, Lee, Lee, 2011)
The intent of this analysis is to evaluate the UNIX and Windows operating system architectures on the basis of differences in their kernel architectures, application programmer interfaces (API), security, approaches to process management. Both operating systems can support shell scripting, with this approach to process management and exception handling being more prevalent on the UNIX platform (Takeuchi, Nakayama, 2006)
The Microsoft hybrid kernel approach is also deliverable designed to allow for greater support of faster and more secured integration to 3rd party platforms through a wide variety of network protocols including TCP/IP. DHCP, XML and TELNET sessions as defined in UNIX shell scripts (Vellalacheruvu, Kumar, 2011)
Another variation in kernel architectural design that directly affects how customizable both operating systems are is the design philosophy with regard to monolithic vs. hybrid kernels (Zhou, Goscinski, 1997)
). The section will also cover more details on distributed systems (Dasgupta, 1997, p
Some examples of network operating systems are Microsoft Windows Server, Windows NT, Novell Netware, and Artisoft's LANtastic. (Hissom, 2006) Microsoft Windows Server 2003, Linux, UNIX, Microsoft Windows Server 2008, BSD and Mac OS X are also network operating systems (Sen, 2016)
They have remote access feature, affording users network access via the Internet. (Kabachinski, 2010, p
Network Operating Systems operate on servers, offering them the capacity of managing information, groups, users, applications, networking functions, security, etc. Network operating systems' key role is enabling sharing of printers and files among several computers within a given network (normally a LAN (local area network) or private network) (Sen, 2016, p
Moreover, lack of effective control and security systems may lead to breaking in or attack across the different application in the systems. (Anderson, 2008)
However, the encrypted data can only be read by an authorized individual having the decrypted key. (Beuchelt, 2013)