<output id="qn6qe"></output>

    1. <output id="qn6qe"><tt id="qn6qe"></tt></output>
    2. <strike id="qn6qe"></strike>

      亚洲 日本 欧洲 欧美 视频,日韩中文字幕有码av,一本一道av中文字幕无码,国产线播放免费人成视频播放,人妻少妇偷人无码视频,日夜啪啪一区二区三区,国产尤物精品自在拍视频首页,久热这里只有精品12

      MINIX 3 值得仔細研究 from Tanenbaum A., Bos H. Modern Operating Systems 5ed 2023

       

      10.1.6 MINIX

      One property that all modern UNIX systems have is that they are large and complicated, in a sense the antithesis of the original idea behind UNIX. Even if the source code were freely available, which it is not in most cases, it is out of the question that a single person could understand it all anymore. This situation led one of the authors of this book (AST) to write a new UNIX-like system that was small enough to understand, was available with all the source code, and could be used for educational purposes. That system consisted of 11,800 lines of C and 800 lines of assembly code. Released in 1987, it was functionally almost equivalent to Version 7 UNIX, the mainstay of most computer science departments during the PDP-11 era.

      MINIX was one of the first UNIX-like systems based on a microkernel design. The idea behind a microkernel is to provide minimal functionality in the kernel to make it reliable and efficient. Consequently, memory management and the file system were pushed out into user processes. The kernel handled message passing between the processes and little else. The kernel was 1600 lines of C and 800 lines of assembler. For technical reasons relating to the 8088 architecture, the I/O device drivers (2900 additional lines of C) were also in the kernel. The file system (5100 lines of C) and memory manager (2200 lines of C) ran as two separate user processes.

      Microkernels have the advantage over monolithic systems that they are easy to understand and maintain due to their highly modular structure. Also, moving code from the kernel to user mode makes them highly reliable because the crash of a user-mode process does less damage than the crash of a kernel-mode component. Their main disadvantage is a slightly lower performance due to the extra switches between user mode and kernel mode. However, performance is not everything: all modern UNIX systems run X Windows in user mode and simply accept the performance hit to get the greater modularity (in contrast to Windows, where even the GUI (Graphical User Interface) is in the kernel). Other microkernels of this era were Mach (Accetta et al., 1986) and Chorus (Rozier et al., 1988).

      Within a few months of its appearance, MINIX became a bit of a cult item, with its own USENET (now Google) newsgroup, comp.os.minix, and over 40,000 users. Numerous users contributed commands and other user programs, so MINIX quickly became a collective undertaking by large numbers of users over the Internet. It was a prototype of other collaborative efforts that came later. In 1997, Version 2.0 of MINIX was released and the base system, now including networking, had grown to 62,200 lines of code.

      Around 2004, the direction of MINIX development changed sharply. The focus shifted to building an extremely reliable and dependable system that could automatically repair its own faults and become self-healing, continuing to function correctly even in the face of repeated software bugs being triggered. Consequently, the modularization idea present in Version 1 was greatly expanded in MINIX 3.0. Nearly all the device drivers were moved to user space, with each driver running as a separate process. The size of the entire kernel abruptly dropped to under 4000 lines of code, something a single programmer could easily understand. Internal mechanisms were changed to enhance fault tolerance in numerous ways.

      In addition, over 650 popular UNIX programs were ported to MINIX 3.0, including the X Window System (sometimes just called X), various compilers (including gcc), text-processing software, networking software, Web browsers, and much more. Unlike previous versions, which were primarily educational in nature, starting with MINIX 3.0, the system was quite usable, with the focus moving toward high dependability. The ultimate goal is: No more reset buttons.

      A third edition of the book Operating Systems: Design and Implementation appeared, describing the new system, giving its source code in an appendix, and describing it in detail (Tanenbaum and Woodhull, 2006). The system continues to evolve and has an active user community. It has since been ported to the ARM processor, making it available for embedded systems. For more details and to get the current version for free, you can visit www.minix3.org.

       

       

      下載minix ISO:https://wiki.minix3.org/doku.php?id=www:download:start

       

      old versions of Minix: https://wiki.minix3.org/doku.php?id=www:download:previousversions

      這個系統值得仔細研究研究

       

      posted @ 2025-10-13 02:55  profesor  閱讀(10)  評論(0)    收藏  舉報
      主站蜘蛛池模板: 色噜噜一区二区三区| 久久久久久九九99精品| 欧美成人精品手机在线| 国产亚洲精品久久久久婷婷瑜伽 | 精品国产自在久久现线拍| 五月综合网亚洲乱妇久久| 亚洲av色一区二区三区| 肥大bbwbbw高潮抽搐| 精品人妻日韩中文字幕| 国产精品男女午夜福利片| 天天影视色香欲综合久久| 无遮挡高潮国产免费观看| 熟女激情乱亚洲国产一区| 亚洲成精品动漫久久精久| 亚洲AV高清一区二区三区尤物| 国产av精品一区二区三区| 久久精品国产亚洲av麻豆小说| 国产av丝袜旗袍无码网站| 国产99青青成人A在线| 激情影院内射美女| 国产av综合色高清自拍| 好紧好湿好黄的视频| 亚洲成人资源在线观看| 亚洲综合精品第一页| 精品国产福利一区二区在线| 日本高清一区免费中文视频| 色悠悠久久精品综合视频| 日韩精品 在线 国产 丝袜| 国产精品aⅴ免费视频| 亚洲av无码之国产精品网址蜜芽 | 国产一区二区三区麻豆视频 | 久章草在线毛片视频播放| 隆安县| av偷拍亚洲一区二区三区| 思思热在线视频精品| 国产无遮挡免费视频免费| 99久久亚洲综合精品成人| 亚洲自拍偷拍一区二区三区| 国产精品日韩精品日韩| 人人妻人人做人人爽夜欢视频| 人妻av无码系列一区二区三区|