This sounds like a homework problem to me.
Sorry, but I don't do homework for other people. If I do your work for you, I do the work, and you get the credit! You need to go back to the textbook and read the chapter so you can learn the materials properly. Otherwise, just copying somebody else's answers is plageurism and cheating, and you don't learn anything that way.
Study it for yourself, and good luck.
2006-09-15 04:41:17
·
answer #1
·
answered by no1home2day 7
·
1⤊
0⤋
Yeah, I could do a copy/paste of an explaination for all of that . . . but I won't. Nor will I write a novel for you explaining in detail what each of those are. You are asking me to do a school-type project and I'm not even going to get college credits for it. Sorry, do the research yourself or copy text-book answers off the internet, your choice . . . but there has to be a reason why you are looking for these answers - do yourself a favor and actually learn, youll be more valuable in the end.
2006-09-15 06:00:29
·
answer #2
·
answered by Nientech 3
·
1⤊
0⤋
This is a question or a Homework for you dear.We are here to solve the problem and give simple solutions to complected situation and not to discuss in details.Do your homework at Home not at Net.
2006-09-16 04:36:45
·
answer #3
·
answered by shri 6
·
0⤊
0⤋
Memory management is the act of managing computer memory. In its simpler forms, this involves providing ways to allocate portions of memory to programs at their request, and freeing it for reuse when no longer needed.
Virtual memory systems separate the memory addresses used by a process from actual physical addresses, allowing separation of processes and increasing the effectively available amount of RAM using disk swapping. The quality of the virtual memory manager can have a big impact on overall system performance.
Garbage collection is the automated allocation and deallocation of computer memory resources for a program. This is generally implemented at the programming language level and is in opposition to manual memory management, the explicit allocation and deallocation of computer memory resources.
In addition to standard memory management, DOS led to the development of programs known as memory managers. These move portions of the operating system outside their normal locations in order to increase the amount of memory available to other applications. Examples are EMM386, which was part of the standard installation in DOS's later versions, and QEMM. These allowed use of memory above the 640 kb barrier, where memory was normally reserved for ROMs, and high and upper memory.
===================================
Process management is the ensemble of activities of planning and monitoring the performance of a process, especially in the sense of business process, often confused with reengineering.
Process Management is the application of knowledge, skills, tools, techniques and systems to define, visualize, measure, control, report and improve processes with the goal to meet customer requirements profitably.
ISO 9000 mandates the process approach to managing an organization.
========================================
File Manager was a file manager program bundled with Microsoft Windows 3.0 and Windows 3.1x to replace the previous MS-DOS Executive interface. The program's interface showed a list of directories (later called folders) on the left side, and a list of the current directory's contents on the right side. File Manager allowed a user to create, rename, move, print, copy, search for, and delete files and directories, as well as to set permissions such as read-only or hidden and to associate file types with programs. Also available were tools to label and format disks and to connect and disconnect from a network drive.
The 16-bit program was simple and proved to have issues such as Y2K problems. [1] From Windows 95 onward, File Manager was superseded by Windows Explorer; however, the WINFILE.EXE program still existed in Windows 95 and Windows 98. It was removed in subsequent versions of Windows.
===========================================
LINUX
The protection mechanisms of current mainstream operating systems are inadequate to support confidentiality and integrity requirements for end systems. Mandatory access control (MAC) is needed to address such requirements, but the limitations of traditional MAC have inhibited its adoption into mainstream operating systems. The National Security Agency (NSA) worked with Secure Computing Corporation (SCC) to develop a flexible MAC architecture called Flask to overcome the limitations of traditional MAC. The NSA has implemented this architecture in the Linux operating system, producing a Security-Enhanced Linux (SELinux) prototype, to make the technology available to a wider community and to enable further research into secure operating systems. NAI Labs has developed an example security policy configuration to demonstrate the benefits of the architecture and to provide a foundation for others to use. This paper describes the security architecture, security mechanisms, application programming interface, security policy configuration, and performance of SELinux.
2006-09-15 05:04:55
·
answer #4
·
answered by Amit G 4
·
0⤊
1⤋
ah its one of those guess what the question is.. Answer is: 23.7 But only when its value is 44.
2016-03-17 21:35:27
·
answer #5
·
answered by ? 4
·
0⤊
0⤋