├── .gitignore ├── 2023-autumn-scheduling-1.md ├── 2023-autumn-scheduling-2.md ├── 2023os2train.jpg ├── LICENSE ├── QA.md ├── README.md ├── announce.md ├── excellent-students-2022summer.md ├── excellent-students-2023winter.md ├── graduate-students-2023winter.md ├── lab3-os5-passed.md ├── news.md ├── relatedinfo.md ├── scheduling-1.md ├── scheduling-2.md ├── stage2-passed.md └── stage3-sched.md /.gitignore: -------------------------------------------------------------------------------- 1 | **/.*/* 2 | !.github/* 3 | !.cargo/* 4 | 5 | **/target 6 | **/Cargo.lock 7 | /os*/src/link_app.S 8 | /os/last-* 9 | 10 | tools 11 | workplace/ 12 | -------------------------------------------------------------------------------- /2023-autumn-scheduling-1.md: -------------------------------------------------------------------------------- 1 | 2 | # 2023年秋季开源操作系统训练营：第一阶段 3 | 4 | - [新闻与纪要](./news.md) 5 | - [常见问题解答](./QA.md) 6 | - [Learning Resource](./relatedinfo.md) (训练营学习资源) 7 | - [第一阶段课程直播](https://os2edu.cn/course/123/) 8 | - [2023/10/09第一次课程ppt](https://cloud.tsinghua.edu.cn/d/51b02806997d459783e0/files/?p=%2FRust%E7%AC%AC%E4%B8%80%E6%AC%A1%E5%AD%A6%E4%B9%A0.pdf) 9 | - Online Ranking （训练营在线排行榜） 10 | - [第一阶段排行：Rust Lang](https://os2edu.cn/2023-autumn-rust-ranking/) 11 | - [rustlings Rust编程训练教室](https://classroom.github.com/a/gbr5Jk7V) 12 | 13 | 欢迎在校学生/工程师在2023年秋季参加清华大学、CSDN、阿图教育等共同举办的**2023年秋季开源操作系统训练营**活动（2023.10.08～2023.12.03）。训练营结束后，部分表现突出的同学将获得训练营优秀证书。鼓励同学继续以开源社区的方式参与到企业/科研院所的操作系统实习/实践/工作/学习等相关的活动。 14 | 15 | > 我们也在持续探索和改进开源操作系统训练营，即这个活动不仅仅局限在 2023.10.08～2023.12.03。我们希望建立的是一种长期持续发展的操作系统训练营模式，即各种学习资源都开源并整理集中在一起，导师/助教和学生/爱好者之间基于要做的实验或项目不定期/定期的进行交流。学生/爱好者完成了一定程度的学习和训练后，除了自身得到能力的提升外，还可获得相关证书和就业/学习等机会和相关推荐等，推动他在未来的进一步发展。 16 | 17 | ## 目标： 18 | 19 | **培养具有开源思想的合作者，搭建开源合作平台。** 20 | 21 | **探索把现代系统语言Rust和灵活开放的系统结构RISC-V带入到操作系统的架构与设计的创新中来，思考未来的操作系统应该是什么样。** 22 | 23 | ## 宗旨： 24 | 25 | **希望本活动的组织，能为操作系统爱好者提供一个活跃的开源社区环境，为对Rust、RISC-V和操作系统感兴趣的人士营造一个平等的学习与交流空间，吸引更多对操作系统感兴趣的人士参与。** 26 | 27 | ## 相关信息： 28 | 29 | - [参加2020--2022 OS训练营学生的blog](https://rcore-os.github.io/blog/)，鼓励参加2023 OS训练营的同学把自己在学习过程中的感悟/收获等写成blog，生成pr，并提交到 上，让更多人看到你的进步！ 30 | - **注意** 为及时了解和指导同学的学习和实践情况并推动学生相互帮助，本次活动要求学生把每周学习实践的过程记录（Markdown格式）放在github上自己的公开repo中。可参见[每日学习实践的具体例子](https://github.com/GCYYfun/DailySchedule)和[2020年OS训练营同学的每日学习情况汇总](https://github.com/rcore-os/rCore-Tutorial/issues/18 ) 。请参加实习的同学把记录每天的进展的git repo网址 更新到[2023年OS训练营同学的每日学习情况汇总](https://github.com/LearningOS/rust-based-os-comp2023/issues/1) 中。要求每位同学在自己的git repo中记录自己的每周进展，其他同学也可以参考学习。 31 | - **注意** 第一阶段学习中的技术问题，建议基于[OS训练营github discussion](https://github.com/LearningOS/rust-based-os-comp2023/discussion) 发出并讨论。 32 | 33 | 34 | # 2023秋冬季开源操作系统训练营第一阶段环境配置与学习资料 35 | 36 | 前提条件： 要求有基本数据结构，算法基础，相对了解或熟悉C语言等编程. 37 | 38 | 1. 自学基础知识：[阅读书籍/课程/视频等资源汇总](https://github.com/rcore-os/rCore/wiki/study-resource-of-system-programming-in-RUST) 39 | 40 | - 推荐：[Rust语言圣经(Rust教程 Rust Course和配套练习)](https://course.rs/) 41 | - 推荐：[半小时快速了解Rust](https://fasterthanli.me/articles/a-half-hour-to-learn-rust) 42 | - 推荐：[Rust速查表（cheatsheet）](https://cheats.rs/) 该项目不仅提供了基础的语法速查，还有执行顺序详解和编写时需要关注的注意事项。项目还包含了示例代码（EX）、书籍（BK）、标准（STD）等相关资料的扩展。 43 | - 推荐：[清华计算机系大一学生2022暑期课程：Rust程序设计训练（有课程视频）](https://lab.cs.tsinghua.edu.cn/rust/) 44 | 45 | 2. 自学编程 46 | 47 | - [2023秋季OS训练营--rustling训练](https://classroom.github.com/a/gbr5Jk7V)（采用Github Classroom模式的Rustling小练习，点击上述链接，形成自己的练习用repo） 48 | 49 | - 要求：**必须完成** 。完成所有练习后，执行 ``git add; git commit -m"update"; git push`` 命令，把更新提交到GithubClassroom的CI进行自动评测。要求小练习全部通过GithubClassroom的CI自动评测。 50 | 51 | - [学习系列视频：Rust中文社群线上学习室--通过 Rustlings 学 Rust](https://space.bilibili.com/24917186/video) 52 | **提示：基于github classroom的开发方式** 53 | 基于github classroom，可方便建立开发用的git repository，并可基于github的 codespace（在线版ubuntu +vscode）在线开发使用。整个开发环境仅仅需要一个网络浏览器。 54 | 55 | > codespace 不是必须的。如果是本地的ubuntu中建立开发环境，可在shell中执行 `make ubuntu_local_setenv` 来自动安装配置开发环境（执行需要 `sudo` root 权限，仅需要执行一次）。 56 | 57 | 1. 在网络浏览器中用自己的 github id 登录 github.com。 58 | 59 | 2. 接收 [Rust-lang Lab Test based on Rustlings 的github classroom在线邀请](https://classroom.github.com/a/gbr5Jk7V) ，根据提示一路选择OK即可。 60 | 61 | 3. 完成第二步后，你的rustings实验练习 的 github repository 会被自动建立好，点击此github repository的链接，就可看到你要完成的实验了。 62 | 63 | 4. 在你的第一个实验练习的网页的中上部可以看到一个醒目的 `code` 绿色按钮，点击后，可以进一步看到 `codespace` 标签和醒目的 `create codesapce on main` 绿色按钮。请点击这个绿色按钮，就可以进入到在线的ubuntu +vscode环境中 64 | 65 | 5. 再按照下面的环境安装提示在vscode的 `console` 中安装配置开发环境：rustc等工具。 66 | 67 | 6. 然后就可以基于在线vscode进行测试 (执行命令 `rustlings watch` ），编辑代码的循环实验过程了。 68 | 69 | 7. 如果使用本地的环境进行rustlings的练习，请按照接下来的步骤进行：首先需要安装一个Linux的环境，对于windows的用户，推荐使用wsl2，也可以使用vmware等虚拟机进行安装。如果在这一步存在问题，请联系助教。 70 | 71 | 8. 创建ssh key。在linux环境下，使用` ssh-keygen -t rsa -b 4096 -C "你的邮箱" `命令，创建ssh key，下面的选项全部直接敲回车即可。 72 | 随后使用` cat ~/.ssh/id_rsa.pub` 命令查看生成的公钥，并完整的复制下来。 73 | 在github仓库界面点击自己的头像，选择`settings`。进入到设置页面后，点击左侧的`SSH and GPG keys`选项。点击`New SSH key`选项，并将复制下来的内容粘贴上去，添加该ssh key的描述。随后点击`Add SSH key`，并一路点击确认即可。 74 | 75 | 9. 在本地安装rust。进入linux环境下，参考rcore 教程 http://rcore-os.cn/rCore-Tutorial-Book-v3/ 中， 第零章操作系统概述，实验环境配置的内容，找到Rust 开发环境配置的章节，相应配置即可，你可以同时将后续需要的环境也配置好。 76 | 77 | 10. clone实验仓库到本地。在前面点击链接生成的仓库中，同样点击醒目的 `code` 绿色按钮，选择`local`下的`ssh`选项，复制下面的链接。随后回到本地linux环境下，使用`git clone 复制的链接`的方式，将目标仓库clone到本地。随后，使用`ls`命令查看自己clone下来的文件夹，再使用`cd`命令进入到该文件夹下，使用`cargo install --force --path .`安装rustlings。 78 | 79 | 11. 练习rustlings。使用vscode等编辑器，进入clone下来的目录下的`exercises`文件夹，依次完成对应的练习。使用`rustlings run 练习名称`去运行对应练习，也可以使用`rustlings hint 练习名称`查看题解。 80 | 81 | 12. 提交。当做完部分或所有练习之后，执行 ``git add; git commit -m "update"; git push`` 命令，把更新提交到GithubClassroom的CI进行自动评测。你可以在github仓库页面的actions页面，看到你的CI提交结果，或者 http://os2edu.cn/2023-autumn-rust-ranking 上面查看自己的评分。 82 | 83 | 13. 上述步骤有任何问题都可以找助教。 84 | 85 | - （Option）[32 Rust Quizes](https://dtolnay.github.io/rust-quiz/1) 86 | 87 | - 要求：小练习全部通过。（**非必须完成**） 88 | 89 | - （Option）[exercisms.io 快速练习(88+道题目的中文详细描述)](http://llever.com/exercism-rust-zh/index.html) 90 | 91 | - 要求：大部分练习会做或能读懂。（**非必须完成**） 92 | - [exercism.io官方站点](https://exercism.io/) 93 | 94 | #### step 1 自学risc-v系统结构（大约2~7天） 95 | 96 | 前提条件：要求有基本计算机组成原理，计算机系统结构基础。 97 | 98 | 阅读《计算机组成与设计（RISC-V版）》第一、二章，可以在整体结构上对 RISC-V 体系建立基本认知。再进行后面的学习比较有效果。 99 | 100 | #### 自学材料和练习要求: 101 | 102 | 1. 阅读书籍和在线课程 103 | 104 | - 自学[PPT for RISC-V特权指令级架构](https://content.riscv.org/wp-content/uploads/2018/05/riscv-privileged-BCN.v7-2.pdf) 105 | - 自学[RISC-V手册：一本开源指令集的指南](http://riscvbook.com/chinese/RISC-V-Reader-Chinese-v2p1.pdf) 重点是第10章 106 | - （Option）自学[RISC-V特权指令级规范](https://riscv.org/technical/specifications/) 重点是与OS相关的特权硬件访问的规范内容（Privileged Spec） 107 | - （Option）自学[RISC-V汇编手册](https://github.com/riscv-non-isa/riscv-asm-manual/blob/master/riscv-asm.md) 108 | - （Option）[计算机组成与设计：RISC-V 教材](https://item.jd.com/12887758.html) 这是完整的课程教材，不要求全部看完，请根据自己的需求选择。 109 | - （Option）[计算机组成与设计：RISC-V 浙大在线课程](http://www.icourse163.org/course/ZJU-1452997167) 这是完整的一门课，不要求全部看完，请根据自己的需求选择。 110 | 111 | 2. 其他参考学习信息 112 | 113 | - （Option）[Berkeley CS61C: Great Ideas in Computer Architecture (Machine Structures)](http://www-inst.eecs.berkeley.edu/~cs61c/sp18/) 114 | 115 | > Option的含义是：如果有足够的时间建议看看，否则在后续要用到时或需要查询进一步信息时再查阅这些内容。 116 | 117 | 3. 通过要求 118 | 119 | - 掌握RUST编程，理解RISC-V与OS相关的硬件特性（中断，异常，系统调用，寄存器，特权级，MMU...）。 120 | 121 | One More Thing：当你看到这，感觉第一阶段还没开始，还在想下一步要干啥时，我们的建议是：**Just Do It NOW!** 122 | -------------------------------------------------------------------------------- /2023-autumn-scheduling-2.md: -------------------------------------------------------------------------------- 1 | 2 | # 2023年秋冬季开源操作系统训练营：第二阶段 3 | 4 | - [新闻与纪要](./news.md) 5 | - [常见问题解答](./QA.md) 6 | - [Learning Resource](./relatedinfo.md) (训练营学习资源) 7 | - Online Ranking （训练营在线排行榜） 8 | - [rCore Tutorial ClassRoom排名页面]( https://os2edu.cn/2023-autumn-os-ranking/) 9 | - Classroom 10 | - [rCore Tutorial ClassRoom邀请链接](https://classroom.github.com/a/QCd3t3jG) 11 | 12 | 13 | ## 相关信息： 14 | 15 | - [参加2020--2022 OS训练营学生的blog](https://rcore-os.github.io/blog/)，鼓励参加2023 OS训练营的同学把自己在学习过程中的感悟/收获等写成blog，生成pr，并提交到 上，让更多人看到你的进步！ 16 | - **注意** 为及时了解和指导同学的学习和实践情况并推动学生相互帮助，本次活动要求学生把每周学习实践的过程记录（Markdown格式）放在github上自己的公开repo中。可参见[每日学习实践的具体例子](https://github.com/GCYYfun/DailySchedule)和[2020年OS训练营同学的每日学习情况汇总](https://github.com/rcore-os/rCore-Tutorial/issues/18 ) 。请参加实习的同学把记录每天的进展的git repo网址 更新到[2023年OS训练营同学的每日学习情况汇总](https://github.com/LearningOS/rust-based-os-comp2023/issues/1) 中。要求每位同学在自己的git repo中记录自己的每周进展，其他同学也可以参考学习。 17 | - **注意** 第二阶段学习中的技术问题，建议基于[OS训练营github discussion](https://github.com/LearningOS/rust-based-os-comp2023/discussion) 发出并讨论。 18 | 19 | 20 | ## 第二阶段活动安排 21 | 22 | ### 总体学习要求和成绩考核方式 23 | 24 | - 在[学习实践过程记录表](https://github.com/LearningOS/rust-based-os-comp2022/issues/1)上登记自己每日/周学习记录情况的repo网址，并在这个repo上记录每日/周学习记录情况 (成绩分数：20%) 25 | - [学习记录的标杆1](https://github.com/LearningOS/record)，浙江大学本科生徐文浩的2020开源操作系统训练营的过程记录，是大家学习的榜样，供大家学习参考。 26 | - [学习记录的标杆2](https://kiprey.github.io/tags/uCore/)：湖南大学本科生肖政杭的自学ucore for x86的过程记录，是大家学习的榜样，供大家学习参考。 27 | 28 | - 在[OS训练营github discussions](https://github.com/LearningOS/rust-based-os-comp2023/discussions) 上的提问和回答问题情况，在[第二阶段OS学习项目](https://github.com/LearningOS/rust-based-os-comp2023/) 、 [rCore Tutorial v3的详细实验指导内容](https://rcore-os.github.io/rCore-Tutorial-Book-v3/) 上的Pull Request提交情况（代码改进、文档改进、文档错误等） (成绩分数：30%) 29 | 30 | - step 0 [第二阶段OS学习的5个实验](https://github.com/LearningOS/rust-based-os-comp2023#kernel-labs)的完成情况和总结报告 (成绩分数：70%) 31 | - [第二阶段总结报告的参考：杨攀同学的2021年开源操作系统训练营第一阶段总结报告](https://rcore-os.github.io/blog/2021/07/29/rcore-summary-yangpan/) 32 | 33 | ### 第二阶段的训练步骤 34 | 35 | 基于Rust语言进行操作系统内核实验--based on qemu （两周时间） 36 | 37 | 前提条件：要求有操作系统的基础，基本理解RISC-V与OS相关的硬件特性 38 | 39 | 40 | #### 课程参考 41 | - [课程幻灯片](https://www.yuque.com/docs/share/4c39608f-3051-4445-96ca-f3c018cb96c7) 42 | - 参考书 43 | - [Operating Systems: Three Easy Pieces](https://pages.cs.wisc.edu/~remzi/OSTEP/) 44 | - [深入了解计算机系统](https://hansimov.gitbook.io/csapp/) 45 | - [RISC-V Reader中文版](http://riscvbook.com/chinese/RISC-V-Reader-Chinese-v2p1.pdf) 46 | 47 | #### 课程实践：rCore Tutorial Book v3 48 | - [课程实践参考书](https://learningos.github.io/rCore-Tutorial-Book-v3/) 49 | - [课程实践代码仓库](https://github.com/rcore-os/rCore-Tutorial-v3) 50 | - [课程实践代码的API文档](https://github.com/rcore-os/rCore-Tutorial-v3#os-api-docs) 51 | 52 | 53 | #### 基于Rust语言的rCore Tutorial实验指导 54 | - [实验文档](https://learningos.github.io/rCore-Tutorial-Guide-2023A/) 55 | - [API文档](https://github.com/LearningOS/rCore-Tutorial-Guide-2023A/#os-api-docs-of-rcore-tutorial-code-2022s) 56 | - [实验代码](https://github.com/LearningOS/rCore-Tutorial-Code-2023A) 57 | - [测试用例](https://github.com/LearningOS/rCore-Tutorial-Test-2023A) 58 | 59 | 60 | #### [rCore实验讲解视频](https://www.yuque.com/docs/share/1b5b9260-8a80-4427-a612-78ec72b37e5f) 61 | 62 | #### 建立基于ClassRoom实验的具体步骤 63 | 64 | **基于Rust语言的rCore Tutorial** 65 | - [rCore Tutorial ClassRoom邀请链接](https://classroom.github.com/a/QCd3t3jG)：点击后按提示可以建立自己的rCore Tutorial实验专用仓库 66 | - [rCore Tutorial ClassRoom排名页面]( https://os2edu.cn/2023-autumn-os-ranking/)：可以查看自己的rCore Tutorial实验的排名情况 67 | 68 | 69 | 请根据各个实验的具体实验要求在自己的仓库中完成5个实验。请在每完成一个实验（完成编码和实验报告文档）后，请通过执行 `git push` 命令来更新自己的实验专用 repos，来通过基于GitHub Classroom的CI测试。 70 | 71 | One More Thing：当你看到这，感觉第二阶段还没开始，还在想下一步要干啥时，我们的建议是：**Just Do It NOW!** 72 | -------------------------------------------------------------------------------- /2023os2train.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/LearningOS/rust-based-os-comp2023/519b3b915682fb6d12c9ab1ec1ac311b6b8382f7/2023os2train.jpg -------------------------------------------------------------------------------- /LICENSE: -------------------------------------------------------------------------------- 1 | GNU GENERAL PUBLIC LICENSE 2 | Version 3, 29 June 2007 3 | 4 | Copyright (C) 2007 Free Software Foundation, Inc. 5 | Everyone is permitted to copy and distribute verbatim copies 6 | of this license document, but changing it is not allowed. 7 | 8 | Preamble 9 | 10 | The GNU General Public License is a free, copyleft license for 11 | software and other kinds of works. 12 | 13 | The licenses for most software and other practical works are designed 14 | to take away your freedom to share and change the works. By contrast, 15 | the GNU General Public License is intended to guarantee your freedom to 16 | share and change all versions of a program--to make sure it remains free 17 | software for all its users. We, the Free Software Foundation, use the 18 | GNU General Public License for most of our software; it applies also to 19 | any other work released this way by its authors. You can apply it to 20 | your programs, too. 21 | 22 | When we speak of free software, we are referring to freedom, not 23 | price. Our General Public Licenses are designed to make sure that you 24 | have the freedom to distribute copies of free software (and charge for 25 | them if you wish), that you receive source code or can get it if you 26 | want it, that you can change the software or use pieces of it in new 27 | free programs, and that you know you can do these things. 28 | 29 | To protect your rights, we need to prevent others from denying you 30 | these rights or asking you to surrender the rights. Therefore, you have 31 | certain responsibilities if you distribute copies of the software, or if 32 | you modify it: responsibilities to respect the freedom of others. 33 | 34 | For example, if you distribute copies of such a program, whether 35 | gratis or for a fee, you must pass on to the recipients the same 36 | freedoms that you received. You must make sure that they, too, receive 37 | or can get the source code. And you must show them these terms so they 38 | know their rights. 39 | 40 | Developers that use the GNU GPL protect your rights with two steps: 41 | (1) assert copyright on the software, and (2) offer you this License 42 | giving you legal permission to copy, distribute and/or modify it. 43 | 44 | For the developers' and authors' protection, the GPL clearly explains 45 | that there is no warranty for this free software. For both users' and 46 | authors' sake, the GPL requires that modified versions be marked as 47 | changed, so that their problems will not be attributed erroneously to 48 | authors of previous versions. 49 | 50 | Some devices are designed to deny users access to install or run 51 | modified versions of the software inside them, although the manufacturer 52 | can do so. This is fundamentally incompatible with the aim of 53 | protecting users' freedom to change the software. The systematic 54 | pattern of such abuse occurs in the area of products for individuals to 55 | use, which is precisely where it is most unacceptable. Therefore, we 56 | have designed this version of the GPL to prohibit the practice for those 57 | products. If such problems arise substantially in other domains, we 58 | stand ready to extend this provision to those domains in future versions 59 | of the GPL, as needed to protect the freedom of users. 60 | 61 | Finally, every program is threatened constantly by software patents. 62 | States should not allow patents to restrict development and use of 63 | software on general-purpose computers, but in those that do, we wish to 64 | avoid the special danger that patents applied to a free program could 65 | make it effectively proprietary. To prevent this, the GPL assures that 66 | patents cannot be used to render the program non-free. 67 | 68 | The precise terms and conditions for copying, distribution and 69 | modification follow. 70 | 71 | TERMS AND CONDITIONS 72 | 73 | 0. Definitions. 74 | 75 | "This License" refers to version 3 of the GNU General Public License. 76 | 77 | "Copyright" also means copyright-like laws that apply to other kinds of 78 | works, such as semiconductor masks. 79 | 80 | "The Program" refers to any copyrightable work licensed under this 81 | License. Each licensee is addressed as "you". "Licensees" and 82 | "recipients" may be individuals or organizations. 83 | 84 | To "modify" a work means to copy from or adapt all or part of the work 85 | in a fashion requiring copyright permission, other than the making of an 86 | exact copy. The resulting work is called a "modified version" of the 87 | earlier work or a work "based on" the earlier work. 88 | 89 | A "covered work" means either the unmodified Program or a work based 90 | on the Program. 91 | 92 | To "propagate" a work means to do anything with it that, without 93 | permission, would make you directly or secondarily liable for 94 | infringement under applicable copyright law, except executing it on a 95 | computer or modifying a private copy. Propagation includes copying, 96 | distribution (with or without modification), making available to the 97 | public, and in some countries other activities as well. 98 | 99 | To "convey" a work means any kind of propagation that enables other 100 | parties to make or receive copies. Mere interaction with a user through 101 | a computer network, with no transfer of a copy, is not conveying. 102 | 103 | An interactive user interface displays "Appropriate Legal Notices" 104 | to the extent that it includes a convenient and prominently visible 105 | feature that (1) displays an appropriate copyright notice, and (2) 106 | tells the user that there is no warranty for the work (except to the 107 | extent that warranties are provided), that licensees may convey the 108 | work under this License, and how to view a copy of this License. If 109 | the interface presents a list of user commands or options, such as a 110 | menu, a prominent item in the list meets this criterion. 111 | 112 | 1. Source Code. 113 | 114 | The "source code" for a work means the preferred form of the work 115 | for making modifications to it. "Object code" means any non-source 116 | form of a work. 117 | 118 | A "Standard Interface" means an interface that either is an official 119 | standard defined by a recognized standards body, or, in the case of 120 | interfaces specified for a particular programming language, one that 121 | is widely used among developers working in that language. 122 | 123 | The "System Libraries" of an executable work include anything, other 124 | than the work as a whole, that (a) is included in the normal form of 125 | packaging a Major Component, but which is not part of that Major 126 | Component, and (b) serves only to enable use of the work with that 127 | Major Component, or to implement a Standard Interface for which an 128 | implementation is available to the public in source code form. A 129 | "Major Component", in this context, means a major essential component 130 | (kernel, window system, and so on) of the specific operating system 131 | (if any) on which the executable work runs, or a compiler used to 132 | produce the work, or an object code interpreter used to run it. 133 | 134 | The "Corresponding Source" for a work in object code form means all 135 | the source code needed to generate, install, and (for an executable 136 | work) run the object code and to modify the work, including scripts to 137 | control those activities. However, it does not include the work's 138 | System Libraries, or general-purpose tools or generally available free 139 | programs which are used unmodified in performing those activities but 140 | which are not part of the work. For example, Corresponding Source 141 | includes interface definition files associated with source files for 142 | the work, and the source code for shared libraries and dynamically 143 | linked subprograms that the work is specifically designed to require, 144 | such as by intimate data communication or control flow between those 145 | subprograms and other parts of the work. 146 | 147 | The Corresponding Source need not include anything that users 148 | can regenerate automatically from other parts of the Corresponding 149 | Source. 150 | 151 | The Corresponding Source for a work in source code form is that 152 | same work. 153 | 154 | 2. Basic Permissions. 155 | 156 | All rights granted under this License are granted for the term of 157 | copyright on the Program, and are irrevocable provided the stated 158 | conditions are met. This License explicitly affirms your unlimited 159 | permission to run the unmodified Program. The output from running a 160 | covered work is covered by this License only if the output, given its 161 | content, constitutes a covered work. This License acknowledges your 162 | rights of fair use or other equivalent, as provided by copyright law. 163 | 164 | You may make, run and propagate covered works that you do not 165 | convey, without conditions so long as your license otherwise remains 166 | in force. You may convey covered works to others for the sole purpose 167 | of having them make modifications exclusively for you, or provide you 168 | with facilities for running those works, provided that you comply with 169 | the terms of this License in conveying all material for which you do 170 | not control copyright. Those thus making or running the covered works 171 | for you must do so exclusively on your behalf, under your direction 172 | and control, on terms that prohibit them from making any copies of 173 | your copyrighted material outside their relationship with you. 174 | 175 | Conveying under any other circumstances is permitted solely under 176 | the conditions stated below. Sublicensing is not allowed; section 10 177 | makes it unnecessary. 178 | 179 | 3. Protecting Users' Legal Rights From Anti-Circumvention Law. 180 | 181 | No covered work shall be deemed part of an effective technological 182 | measure under any applicable law fulfilling obligations under article 183 | 11 of the WIPO copyright treaty adopted on 20 December 1996, or 184 | similar laws prohibiting or restricting circumvention of such 185 | measures. 186 | 187 | When you convey a covered work, you waive any legal power to forbid 188 | circumvention of technological measures to the extent such circumvention 189 | is effected by exercising rights under this License with respect to 190 | the covered work, and you disclaim any intention to limit operation or 191 | modification of the work as a means of enforcing, against the work's 192 | users, your or third parties' legal rights to forbid circumvention of 193 | technological measures. 194 | 195 | 4. Conveying Verbatim Copies. 196 | 197 | You may convey verbatim copies of the Program's source code as you 198 | receive it, in any medium, provided that you conspicuously and 199 | appropriately publish on each copy an appropriate copyright notice; 200 | keep intact all notices stating that this License and any 201 | non-permissive terms added in accord with section 7 apply to the code; 202 | keep intact all notices of the absence of any warranty; and give all 203 | recipients a copy of this License along with the Program. 204 | 205 | You may charge any price or no price for each copy that you convey, 206 | and you may offer support or warranty protection for a fee. 207 | 208 | 5. Conveying Modified Source Versions. 209 | 210 | You may convey a work based on the Program, or the modifications to 211 | produce it from the Program, in the form of source code under the 212 | terms of section 4, provided that you also meet all of these conditions: 213 | 214 | a) The work must carry prominent notices stating that you modified 215 | it, and giving a relevant date. 216 | 217 | b) The work must carry prominent notices stating that it is 218 | released under this License and any conditions added under section 219 | 7. This requirement modifies the requirement in section 4 to 220 | "keep intact all notices". 221 | 222 | c) You must license the entire work, as a whole, under this 223 | License to anyone who comes into possession of a copy. This 224 | License will therefore apply, along with any applicable section 7 225 | additional terms, to the whole of the work, and all its parts, 226 | regardless of how they are packaged. This License gives no 227 | permission to license the work in any other way, but it does not 228 | invalidate such permission if you have separately received it. 229 | 230 | d) If the work has interactive user interfaces, each must display 231 | Appropriate Legal Notices; however, if the Program has interactive 232 | interfaces that do not display Appropriate Legal Notices, your 233 | work need not make them do so. 234 | 235 | A compilation of a covered work with other separate and independent 236 | works, which are not by their nature extensions of the covered work, 237 | and which are not combined with it such as to form a larger program, 238 | in or on a volume of a storage or distribution medium, is called an 239 | "aggregate" if the compilation and its resulting copyright are not 240 | used to limit the access or legal rights of the compilation's users 241 | beyond what the individual works permit. Inclusion of a covered work 242 | in an aggregate does not cause this License to apply to the other 243 | parts of the aggregate. 244 | 245 | 6. Conveying Non-Source Forms. 246 | 247 | You may convey a covered work in object code form under the terms 248 | of sections 4 and 5, provided that you also convey the 249 | machine-readable Corresponding Source under the terms of this License, 250 | in one of these ways: 251 | 252 | a) Convey the object code in, or embodied in, a physical product 253 | (including a physical distribution medium), accompanied by the 254 | Corresponding Source fixed on a durable physical medium 255 | customarily used for software interchange. 256 | 257 | b) Convey the object code in, or embodied in, a physical product 258 | (including a physical distribution medium), accompanied by a 259 | written offer, valid for at least three years and valid for as 260 | long as you offer spare parts or customer support for that product 261 | model, to give anyone who possesses the object code either (1) a 262 | copy of the Corresponding Source for all the software in the 263 | product that is covered by this License, on a durable physical 264 | medium customarily used for software interchange, for a price no 265 | more than your reasonable cost of physically performing this 266 | conveying of source, or (2) access to copy the 267 | Corresponding Source from a network server at no charge. 268 | 269 | c) Convey individual copies of the object code with a copy of the 270 | written offer to provide the Corresponding Source. This 271 | alternative is allowed only occasionally and noncommercially, and 272 | only if you received the object code with such an offer, in accord 273 | with subsection 6b. 274 | 275 | d) Convey the object code by offering access from a designated 276 | place (gratis or for a charge), and offer equivalent access to the 277 | Corresponding Source in the same way through the same place at no 278 | further charge. You need not require recipients to copy the 279 | Corresponding Source along with the object code. If the place to 280 | copy the object code is a network server, the Corresponding Source 281 | may be on a different server (operated by you or a third party) 282 | that supports equivalent copying facilities, provided you maintain 283 | clear directions next to the object code saying where to find the 284 | Corresponding Source. Regardless of what server hosts the 285 | Corresponding Source, you remain obligated to ensure that it is 286 | available for as long as needed to satisfy these requirements. 287 | 288 | e) Convey the object code using peer-to-peer transmission, provided 289 | you inform other peers where the object code and Corresponding 290 | Source of the work are being offered to the general public at no 291 | charge under subsection 6d. 292 | 293 | A separable portion of the object code, whose source code is excluded 294 | from the Corresponding Source as a System Library, need not be 295 | included in conveying the object code work. 296 | 297 | A "User Product" is either (1) a "consumer product", which means any 298 | tangible personal property which is normally used for personal, family, 299 | or household purposes, or (2) anything designed or sold for incorporation 300 | into a dwelling. In determining whether a product is a consumer product, 301 | doubtful cases shall be resolved in favor of coverage. For a particular 302 | product received by a particular user, "normally used" refers to a 303 | typical or common use of that class of product, regardless of the status 304 | of the particular user or of the way in which the particular user 305 | actually uses, or expects or is expected to use, the product. A product 306 | is a consumer product regardless of whether the product has substantial 307 | commercial, industrial or non-consumer uses, unless such uses represent 308 | the only significant mode of use of the product. 309 | 310 | "Installation Information" for a User Product means any methods, 311 | procedures, authorization keys, or other information required to install 312 | and execute modified versions of a covered work in that User Product from 313 | a modified version of its Corresponding Source. The information must 314 | suffice to ensure that the continued functioning of the modified object 315 | code is in no case prevented or interfered with solely because 316 | modification has been made. 317 | 318 | If you convey an object code work under this section in, or with, or 319 | specifically for use in, a User Product, and the conveying occurs as 320 | part of a transaction in which the right of possession and use of the 321 | User Product is transferred to the recipient in perpetuity or for a 322 | fixed term (regardless of how the transaction is characterized), the 323 | Corresponding Source conveyed under this section must be accompanied 324 | by the Installation Information. But this requirement does not apply 325 | if neither you nor any third party retains the ability to install 326 | modified object code on the User Product (for example, the work has 327 | been installed in ROM). 328 | 329 | The requirement to provide Installation Information does not include a 330 | requirement to continue to provide support service, warranty, or updates 331 | for a work that has been modified or installed by the recipient, or for 332 | the User Product in which it has been modified or installed. Access to a 333 | network may be denied when the modification itself materially and 334 | adversely affects the operation of the network or violates the rules and 335 | protocols for communication across the network. 336 | 337 | Corresponding Source conveyed, and Installation Information provided, 338 | in accord with this section must be in a format that is publicly 339 | documented (and with an implementation available to the public in 340 | source code form), and must require no special password or key for 341 | unpacking, reading or copying. 342 | 343 | 7. Additional Terms. 344 | 345 | "Additional permissions" are terms that supplement the terms of this 346 | License by making exceptions from one or more of its conditions. 347 | Additional permissions that are applicable to the entire Program shall 348 | be treated as though they were included in this License, to the extent 349 | that they are valid under applicable law. If additional permissions 350 | apply only to part of the Program, that part may be used separately 351 | under those permissions, but the entire Program remains governed by 352 | this License without regard to the additional permissions. 353 | 354 | When you convey a copy of a covered work, you may at your option 355 | remove any additional permissions from that copy, or from any part of 356 | it. (Additional permissions may be written to require their own 357 | removal in certain cases when you modify the work.) You may place 358 | additional permissions on material, added by you to a covered work, 359 | for which you have or can give appropriate copyright permission. 360 | 361 | Notwithstanding any other provision of this License, for material you 362 | add to a covered work, you may (if authorized by the copyright holders of 363 | that material) supplement the terms of this License with terms: 364 | 365 | a) Disclaiming warranty or limiting liability differently from the 366 | terms of sections 15 and 16 of this License; or 367 | 368 | b) Requiring preservation of specified reasonable legal notices or 369 | author attributions in that material or in the Appropriate Legal 370 | Notices displayed by works containing it; or 371 | 372 | c) Prohibiting misrepresentation of the origin of that material, or 373 | requiring that modified versions of such material be marked in 374 | reasonable ways as different from the original version; or 375 | 376 | d) Limiting the use for publicity purposes of names of licensors or 377 | authors of the material; or 378 | 379 | e) Declining to grant rights under trademark law for use of some 380 | trade names, trademarks, or service marks; or 381 | 382 | f) Requiring indemnification of licensors and authors of that 383 | material by anyone who conveys the material (or modified versions of 384 | it) with contractual assumptions of liability to the recipient, for 385 | any liability that these contractual assumptions directly impose on 386 | those licensors and authors. 387 | 388 | All other non-permissive additional terms are considered "further 389 | restrictions" within the meaning of section 10. If the Program as you 390 | received it, or any part of it, contains a notice stating that it is 391 | governed by this License along with a term that is a further 392 | restriction, you may remove that term. If a license document contains 393 | a further restriction but permits relicensing or conveying under this 394 | License, you may add to a covered work material governed by the terms 395 | of that license document, provided that the further restriction does 396 | not survive such relicensing or conveying. 397 | 398 | If you add terms to a covered work in accord with this section, you 399 | must place, in the relevant source files, a statement of the 400 | additional terms that apply to those files, or a notice indicating 401 | where to find the applicable terms. 402 | 403 | Additional terms, permissive or non-permissive, may be stated in the 404 | form of a separately written license, or stated as exceptions; 405 | the above requirements apply either way. 406 | 407 | 8. Termination. 408 | 409 | You may not propagate or modify a covered work except as expressly 410 | provided under this License. Any attempt otherwise to propagate or 411 | modify it is void, and will automatically terminate your rights under 412 | this License (including any patent licenses granted under the third 413 | paragraph of section 11). 414 | 415 | However, if you cease all violation of this License, then your 416 | license from a particular copyright holder is reinstated (a) 417 | provisionally, unless and until the copyright holder explicitly and 418 | finally terminates your license, and (b) permanently, if the copyright 419 | holder fails to notify you of the violation by some reasonable means 420 | prior to 60 days after the cessation. 421 | 422 | Moreover, your license from a particular copyright holder is 423 | reinstated permanently if the copyright holder notifies you of the 424 | violation by some reasonable means, this is the first time you have 425 | received notice of violation of this License (for any work) from that 426 | copyright holder, and you cure the violation prior to 30 days after 427 | your receipt of the notice. 428 | 429 | Termination of your rights under this section does not terminate the 430 | licenses of parties who have received copies or rights from you under 431 | this License. If your rights have been terminated and not permanently 432 | reinstated, you do not qualify to receive new licenses for the same 433 | material under section 10. 434 | 435 | 9. Acceptance Not Required for Having Copies. 436 | 437 | You are not required to accept this License in order to receive or 438 | run a copy of the Program. Ancillary propagation of a covered work 439 | occurring solely as a consequence of using peer-to-peer transmission 440 | to receive a copy likewise does not require acceptance. However, 441 | nothing other than this License grants you permission to propagate or 442 | modify any covered work. These actions infringe copyright if you do 443 | not accept this License. Therefore, by modifying or propagating a 444 | covered work, you indicate your acceptance of this License to do so. 445 | 446 | 10. Automatic Licensing of Downstream Recipients. 447 | 448 | Each time you convey a covered work, the recipient automatically 449 | receives a license from the original licensors, to run, modify and 450 | propagate that work, subject to this License. You are not responsible 451 | for enforcing compliance by third parties with this License. 452 | 453 | An "entity transaction" is a transaction transferring control of an 454 | organization, or substantially all assets of one, or subdividing an 455 | organization, or merging organizations. If propagation of a covered 456 | work results from an entity transaction, each party to that 457 | transaction who receives a copy of the work also receives whatever 458 | licenses to the work the party's predecessor in interest had or could 459 | give under the previous paragraph, plus a right to possession of the 460 | Corresponding Source of the work from the predecessor in interest, if 461 | the predecessor has it or can get it with reasonable efforts. 462 | 463 | You may not impose any further restrictions on the exercise of the 464 | rights granted or affirmed under this License. For example, you may 465 | not impose a license fee, royalty, or other charge for exercise of 466 | rights granted under this License, and you may not initiate litigation 467 | (including a cross-claim or counterclaim in a lawsuit) alleging that 468 | any patent claim is infringed by making, using, selling, offering for 469 | sale, or importing the Program or any portion of it. 470 | 471 | 11. Patents. 472 | 473 | A "contributor" is a copyright holder who authorizes use under this 474 | License of the Program or a work on which the Program is based. The 475 | work thus licensed is called the contributor's "contributor version". 476 | 477 | A contributor's "essential patent claims" are all patent claims 478 | owned or controlled by the contributor, whether already acquired or 479 | hereafter acquired, that would be infringed by some manner, permitted 480 | by this License, of making, using, or selling its contributor version, 481 | but do not include claims that would be infringed only as a 482 | consequence of further modification of the contributor version. For 483 | purposes of this definition, "control" includes the right to grant 484 | patent sublicenses in a manner consistent with the requirements of 485 | this License. 486 | 487 | Each contributor grants you a non-exclusive, worldwide, royalty-free 488 | patent license under the contributor's essential patent claims, to 489 | make, use, sell, offer for sale, import and otherwise run, modify and 490 | propagate the contents of its contributor version. 491 | 492 | In the following three paragraphs, a "patent license" is any express 493 | agreement or commitment, however denominated, not to enforce a patent 494 | (such as an express permission to practice a patent or covenant not to 495 | sue for patent infringement). To "grant" such a patent license to a 496 | party means to make such an agreement or commitment not to enforce a 497 | patent against the party. 498 | 499 | If you convey a covered work, knowingly relying on a patent license, 500 | and the Corresponding Source of the work is not available for anyone 501 | to copy, free of charge and under the terms of this License, through a 502 | publicly available network server or other readily accessible means, 503 | then you must either (1) cause the Corresponding Source to be so 504 | available, or (2) arrange to deprive yourself of the benefit of the 505 | patent license for this particular work, or (3) arrange, in a manner 506 | consistent with the requirements of this License, to extend the patent 507 | license to downstream recipients. "Knowingly relying" means you have 508 | actual knowledge that, but for the patent license, your conveying the 509 | covered work in a country, or your recipient's use of the covered work 510 | in a country, would infringe one or more identifiable patents in that 511 | country that you have reason to believe are valid. 512 | 513 | If, pursuant to or in connection with a single transaction or 514 | arrangement, you convey, or propagate by procuring conveyance of, a 515 | covered work, and grant a patent license to some of the parties 516 | receiving the covered work authorizing them to use, propagate, modify 517 | or convey a specific copy of the covered work, then the patent license 518 | you grant is automatically extended to all recipients of the covered 519 | work and works based on it. 520 | 521 | A patent license is "discriminatory" if it does not include within 522 | the scope of its coverage, prohibits the exercise of, or is 523 | conditioned on the non-exercise of one or more of the rights that are 524 | specifically granted under this License. You may not convey a covered 525 | work if you are a party to an arrangement with a third party that is 526 | in the business of distributing software, under which you make payment 527 | to the third party based on the extent of your activity of conveying 528 | the work, and under which the third party grants, to any of the 529 | parties who would receive the covered work from you, a discriminatory 530 | patent license (a) in connection with copies of the covered work 531 | conveyed by you (or copies made from those copies), or (b) primarily 532 | for and in connection with specific products or compilations that 533 | contain the covered work, unless you entered into that arrangement, 534 | or that patent license was granted, prior to 28 March 2007. 535 | 536 | Nothing in this License shall be construed as excluding or limiting 537 | any implied license or other defenses to infringement that may 538 | otherwise be available to you under applicable patent law. 539 | 540 | 12. No Surrender of Others' Freedom. 541 | 542 | If conditions are imposed on you (whether by court order, agreement or 543 | otherwise) that contradict the conditions of this License, they do not 544 | excuse you from the conditions of this License. If you cannot convey a 545 | covered work so as to satisfy simultaneously your obligations under this 546 | License and any other pertinent obligations, then as a consequence you may 547 | not convey it at all. For example, if you agree to terms that obligate you 548 | to collect a royalty for further conveying from those to whom you convey 549 | the Program, the only way you could satisfy both those terms and this 550 | License would be to refrain entirely from conveying the Program. 551 | 552 | 13. Use with the GNU Affero General Public License. 553 | 554 | Notwithstanding any other provision of this License, you have 555 | permission to link or combine any covered work with a work licensed 556 | under version 3 of the GNU Affero General Public License into a single 557 | combined work, and to convey the resulting work. The terms of this 558 | License will continue to apply to the part which is the covered work, 559 | but the special requirements of the GNU Affero General Public License, 560 | section 13, concerning interaction through a network will apply to the 561 | combination as such. 562 | 563 | 14. Revised Versions of this License. 564 | 565 | The Free Software Foundation may publish revised and/or new versions of 566 | the GNU General Public License from time to time. Such new versions will 567 | be similar in spirit to the present version, but may differ in detail to 568 | address new problems or concerns. 569 | 570 | Each version is given a distinguishing version number. If the 571 | Program specifies that a certain numbered version of the GNU General 572 | Public License "or any later version" applies to it, you have the 573 | option of following the terms and conditions either of that numbered 574 | version or of any later version published by the Free Software 575 | Foundation. If the Program does not specify a version number of the 576 | GNU General Public License, you may choose any version ever published 577 | by the Free Software Foundation. 578 | 579 | If the Program specifies that a proxy can decide which future 580 | versions of the GNU General Public License can be used, that proxy's 581 | public statement of acceptance of a version permanently authorizes you 582 | to choose that version for the Program. 583 | 584 | Later license versions may give you additional or different 585 | permissions. However, no additional obligations are imposed on any 586 | author or copyright holder as a result of your choosing to follow a 587 | later version. 588 | 589 | 15. Disclaimer of Warranty. 590 | 591 | THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY 592 | APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT 593 | HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY 594 | OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, 595 | THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR 596 | PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM 597 | IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF 598 | ALL NECESSARY SERVICING, REPAIR OR CORRECTION. 599 | 600 | 16. Limitation of Liability. 601 | 602 | IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING 603 | WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS 604 | THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY 605 | GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE 606 | USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF 607 | DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD 608 | PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), 609 | EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF 610 | SUCH DAMAGES. 611 | 612 | 17. Interpretation of Sections 15 and 16. 613 | 614 | If the disclaimer of warranty and limitation of liability provided 615 | above cannot be given local legal effect according to their terms, 616 | reviewing courts shall apply local law that most closely approximates 617 | an absolute waiver of all civil liability in connection with the 618 | Program, unless a warranty or assumption of liability accompanies a 619 | copy of the Program in return for a fee. 620 | 621 | END OF TERMS AND CONDITIONS 622 | 623 | How to Apply These Terms to Your New Programs 624 | 625 | If you develop a new program, and you want it to be of the greatest 626 | possible use to the public, the best way to achieve this is to make it 627 | free software which everyone can redistribute and change under these terms. 628 | 629 | To do so, attach the following notices to the program. It is safest 630 | to attach them to the start of each source file to most effectively 631 | state the exclusion of warranty; and each file should have at least 632 | the "copyright" line and a pointer to where the full notice is found. 633 | 634 | 635 | Copyright (C) 636 | 637 | This program is free software: you can redistribute it and/or modify 638 | it under the terms of the GNU General Public License as published by 639 | the Free Software Foundation, either version 3 of the License, or 640 | (at your option) any later version. 641 | 642 | This program is distributed in the hope that it will be useful, 643 | but WITHOUT ANY WARRANTY; without even the implied warranty of 644 | MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the 645 | GNU General Public License for more details. 646 | 647 | You should have received a copy of the GNU General Public License 648 | along with this program. If not, see . 649 | 650 | Also add information on how to contact you by electronic and paper mail. 651 | 652 | If the program does terminal interaction, make it output a short 653 | notice like this when it starts in an interactive mode: 654 | 655 | Copyright (C) 656 | This program comes with ABSOLUTELY NO WARRANTY; for details type `show w'. 657 | This is free software, and you are welcome to redistribute it 658 | under certain conditions; type `show c' for details. 659 | 660 | The hypothetical commands `show w' and `show c' should show the appropriate 661 | parts of the General Public License. Of course, your program's commands 662 | might be different; for a GUI interface, you would use an "about box". 663 | 664 | You should also get your employer (if you work as a programmer) or school, 665 | if any, to sign a "copyright disclaimer" for the program, if necessary. 666 | For more information on this, and how to apply and follow the GNU GPL, see 667 | . 668 | 669 | The GNU General Public License does not permit incorporating your program 670 | into proprietary programs. If your program is a subroutine library, you 671 | may consider it more useful to permit linking proprietary applications with 672 | the library. If this is what you want to do, use the GNU Lesser General 673 | Public License instead of this License. But first, please read 674 | . 675 | -------------------------------------------------------------------------------- /QA.md: -------------------------------------------------------------------------------- 1 | # 常见问题解答 2 | 3 | ## Q0：GitHub classroom 是啥？如何使用？ 4 | 5 | ### A： 6 | 7 | - [B 站的 GitHub Classroom 视频介绍](https://www.bilibili.com/video/BV12L41147r7?spm_id_from=333.337.search-card.all.click&vd_source=8e19ee6e49f598fda8c17e306d8b3726) 8 | - [Youtube 的 GitHub Classroom 视频介绍](https://www.youtube.com/playlist?list=PLIRjfNq867bewk3ZGV6Z7a16YDNRCpK3u) 9 | - [GitHub 文档：使用 GitHub Classroom 教学](https://docs.github.com/cn/education/manage-coursework-with-github-classroom/get-started-with-github-classroom) 10 | 11 | ## Q1：已经在 classroom 中建立了自己的仓库（例如“LearningOS/lab0-0-setup-env-run-os1-chyyuu2022”），但是源仓库“LearningOS/rust-based-os-comp2022”更新了，如何处理？ 12 | 13 | ### A： 14 | 15 | **方法一：** 16 | 17 | 重新点击加入课程的链接，在页面下方会有一行字“We've configured the repository associated with this assignment (update)”，“update”是一个链接，点击 update 就可以把自己的仓库更新到与最新状态的 repository template 一致。 18 | 19 | **方法二：** 20 | 21 | 在自己构建的仓库根目录下执行以下命令： 22 | 23 | ```bash 24 | git remote add upstream "https://github.com/LearningOS/rust-based-os-comp2022.git" 25 | git fetch upstream 26 | git checkout -b foo 27 | git branch -D main 28 | git checkout -t upstream/main 29 | git reset --hard origin/main 30 | git push -f 31 | ``` 32 | 33 | **方法三：** 34 | 35 | 向管理员“助教许善朴”申请删除已生成仓库，再点击 链接重新创建仓库。 36 | 37 | ## Q2：在 classroom 中建立了自己的仓库中，进行提交 `git push` 后，触发 CI 后，出现 Annotations 错误“The job was not stared because recent account payments have failed or your spending limit needs to be increased. Please check the 'Billing & plans' section in your settings”，无法完成自动 CI 功能，比如 `Autograding` 等。 38 | 39 | ### A： 40 | 41 | **方法一：** 42 | 43 | 这是由于对用户的私有仓库进行 CI 相关的 GitHub Action 是需要付费的。用户可通过给自己的 github 账户充值来解决。https://docs.github.com/cn/billing/managing-billing-for-github-actions/about-billing-for-github-actions 给出了具体信息。 44 | 45 | **方法二：** 46 | 47 | 对用户的公开仓库进行 CI GitHub Action 是不需要付费的。在项目的 `Settings` -> `Change visibility` 将项目改成 Public, 重新触发 Action。 48 | 目前设置了让用户具有修改自己的项目从 private --> public 的能力。 49 | 如果用户还是发现自己的权限不够，或看不到 `Settings` 这个选项，可以通过联系助教帮助来解决。 50 | 51 | ## Q3：我刚开始准备学习 Rust，是 Rust 新手，我应该如何入门？ 52 | 53 | ### A： 54 | 55 | - [Rust 大佬给初学者的学习建议](https://github.com/rustlang-cn/Rustt/blob/main/Articles/%5B2022-04-02%5D%20Rust%20%E5%A4%A7%E4%BD%AC%E7%BB%99%E5%88%9D%E5%AD%A6%E8%80%85%E7%9A%84%E5%AD%A6%E4%B9%A0%E5%BB%BA%E8%AE%AE.md) 56 | - [张汉东：学习 Rust 你需要一个认知框架](https://zhuanlan.zhihu.com/p/494001676) 57 | - [Rust 语言圣经（Rust Course）](https://course.rs/) 58 | - [Rust 速查表（cheatsheet）](https://cheats.rs/) 该项目不仅提供了基础的语法速查，还有执行顺序详解和编写时需要关注的注意事项。项目还包含了示例代码（EX）、书籍（BK）、标准（STD）等相关资料的扩展。 59 | 60 | ## Q4：我不熟悉 GitHub 和 Git，有啥快速入门的资源吗？ 61 | 62 | ### A： 63 | 64 | - [包括：从 0 开始学习 GitHub 系列 1-7](https://jtxiao.com/main/categories/%E5%B7%A5%E5%85%B7/) 65 | - [超级简单的 Git 入门](https://backlog.com/git-tutorial/cn/) 66 | - [git - 简明指南](https://rogerdudler.github.io/git-guide/index.zh.html) 67 | - [中文 git-tips](https://github.com/521xueweihan/git-tips) 68 | - [GitHub 官方制作的 Git 速查表](https://education.github.com/git-cheat-sheet-education.pdf) 69 | 70 | ## Q5：我不熟悉 Linux 的各种命令，有啥快速入门的资源吗？ 71 | 72 | ### A： 73 | 74 | - [中文 Linux 命令（linux-command）搜索引擎](https://wangchujiang.com/linux-command/)：随用随搜 Linux 命令，而且还支持中文搜索 75 | - [新版 Linux 命令百科全书》（英文）](https://github.com/tldr-pages/tldr) 76 | 77 | ## Q6：我碰到一些命令/应用（比如 vim, curl）、操作（比如 vscode）或语言用法（比如 Makefile）等不知到哪里能快速查找，怎么办？ 78 | 79 | ### A： 80 | 81 | - [Rico's cheatsheets](https://devhints.io/) 开源、全面的速查表网站，涵盖了前端、后端、运维、IDE 多个方面，而且界面友好简洁支持在线查看 82 | - [所有与命令行相关的 cheatsheet](http://cheat.sh/)：号称「你唯一需要的命令行相关速查表」 83 | 84 | ## Q7：我可以正常 `make run`，但使用 `make test` 命令后，构件过程报了许多错（`asm!` not found in scope），Autograding 也无法通过，怎么办？ 85 | 86 | ### A： 87 | 88 | 这是由于内置的 `ci-user/riscv` 代码有错误，在 Autograding 时远程的 `riscv` 依赖被替换，导致编译失败。 89 | 90 | **方法一：** 91 | 92 | 替换内置的 riscv 至正常版本，直接删除本地 `ci-user/riscv` 文件夹，替换为 [ Yakkhini / rust-based-os-comp2022](https://github.com/Yakkhini/rust-based-os-comp2022/tree/main/ci-user) 同位置的修复版本 `/riscv`。 93 | 94 | **方法二：** 95 | 96 | 删除 `ci-user/overwrite.py` 21 行以下部分的依赖替换脚本。 97 | 98 | **方法三：** 99 | 100 | 替换你实验文件夹中 `Cargo.toml` 的 riscv 依赖网址为 `https://GitHub.com/rcore-os/riscv`（修改了网址的大小写）或 `https://gitee.com/rcore-os/riscv`（改为 Gitee 源），使脚本中的替换匹配失效。 101 | 102 | **方法四：** 103 | 104 | 如果你能看到这个 QA，说明相关 Pull request 已被 merge，可以按 QA1 中方法更新仓库。 105 | 106 | ## Q8：在用vscode的esbonio （for Sphinx：rst-->html,...）和rust-analyzer插件时，不能正常工作。请问如何配置？ 107 | 108 | ### A： 109 | 110 | **esbonio error：找不到 conf.py 文件** 111 | 112 | **解决方法** 113 | 114 | 在 .vscode/settings.json中添加如下内容： 115 | 116 | "esbonio.sphinx.confDir": "${workspaceFolder}/guide/source" 117 | 118 | **rust-analyzer插件无法正常解析源代码中的相关定义** 119 | 120 | 比如 os/main.rs中，有如下代码： 121 | 122 | #[cfg(feature = "board_k210")] 123 | #[path = "boards/k210.rs"] 124 | mod board; 125 | #[cfg(not(any(feature = "board_k210")))] 126 | #[path = "boards/qemu.rs"] 127 | mod board; 128 | 129 | 这使得 mod board 可能是 k210.rs中的代码，也可能是qemu.rs中的代码，取决于编译时的参数，即 os/Makefile 中的： 130 | 131 | @cargo build --release --features "board_$(BOARD)" 132 | 133 | rust-analyzer会报错：unresolved import `crate::drivers::chardev::UART` 等错误 134 | 135 | **解决方法** 136 | 137 | 在 .vscode/settings.json中添加如下内容： 138 | 139 | // Prevent "can't find crate for `test`" error on no_std 140 | // Ref: https://github.com/rust-lang/vscode-rust/issues/729 141 | // For vscode-rust plugin users: 142 | "rust.target": "riscv64gc-unknown-none-elf", 143 | "rust.all_targets": false, 144 | // For Rust Analyzer plugin users: 145 | "rust-analyzer.cargo.target": "riscv64gc-unknown-none-elf", 146 | "rust-analyzer.checkOnSave.allTargets": false, 147 | "rust-analyzer.cargo.features": [ 148 | "board_qemu" 149 | ] 150 | 151 | **rust-analyzer插件无法正常解析repo中多个不同projects中的代码** 152 | 153 | **解决方法** 154 | 155 | 以本repo为例，在 .vscode/settings.json中添加如下内容： 156 | 157 | "rust-analyzer.linkedProjects": [ 158 | "guide-code/ch1-3mini-rt-usrland/Cargo.toml", 159 | "os1-ref/Cargo.toml", 160 | "os2-ref/Cargo.toml", 161 | "os3-ref/Cargo.toml", 162 | "os4-ref/Cargo.toml", 163 | "os5-ref/Cargo.toml", 164 | "os6-ref/Cargo.toml", 165 | "os7-ref/Cargo.toml", 166 | "os8-ref/Cargo.toml", 167 | "easy-fs/Cargo.toml", 168 | "easy-fs-fuse/Cargo.toml", 169 | "user/Cargo.toml", 170 | ] 171 | 172 | 如果还有新的projects想要rust-analyzer分析，参考上面的例子，把projects对应路径加入即可。 173 | 174 | **rust-analyzer插件无法正常解析rustlings repo中不同源码** 175 | 176 | **解决方法** 177 | 178 | 访问 安装并允许rustlings-fix工具，它会生成一个配置文件 rust-project.json ，然后就可以看了 179 | 180 | # Install rustlings-fix from cargo 181 | cargo install rustlings-fix 182 | 183 | # Change directory into wherever rustlings is cloned 184 | cd ~/src/rustlings 185 | 186 | # Run the binary 187 | rustlings-fix 188 | 189 | ## Q9：在用vscode中能否像一般应用一样，源码级调试rcore-tutorial-v3？如果可以，如何做？ 190 | 191 | **方法一：（适合vscode 一般用户）** 192 | 193 | 请看 [VSCode 可视化调试支持](https://learningos.github.io/rust-based-os-comp2022/0setup-devel-env.html#vscode)。 194 | 感谢 @myrfy 米明恒的贡献！ 195 | 196 | **方法二：（适合vscode熟手）** 197 | 198 | 目前 @chenzhiy2001 已经有了一个初步的实现方案， 请访问 [coredebugger安装与使用](https://github.com/chenzhiy2001/code-debug#%E5%AE%89%E8%A3%85%E4%B8%8E%E4%BD%BF%E7%94%A8) 了解具体操作过程。@chyyuu 试用后，觉得很不错！ 199 | 200 | 感谢 @chenzhiy2001 陈志扬的贡献！ 201 | 202 | 提示： 203 | 204 | 1. 目前项目在开发中，还没有设计得对用户特别友好，建议新手慎用。 205 | 2. 因为opt-level被设置成0，rCore Tutorial v3在qemu中会比较慢（在耗时的for循环等情况下，要有耐心等待） 206 | 207 | **方法三：（适合Linux 命令行熟手）** 208 | 209 | 请看 [GDB 调试支持](https://learningos.github.io/rust-based-os-comp2022/0setup-devel-env.html#gdb) 210 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | # Open-Source OS Training Comp 2023 2 | 3 | Welcome to Open-Source OS Training Comp 2023（欢迎加入2023 年开源操作系统训练营） 4 | 5 | ## 重要信息 6 | - [**第一阶段训练安排**](./2023-autumn-scheduling-1.md) 7 | - 2023.10.08：2023 年秋冬季开源操作系统训练营正式启动。 8 | - 2023.09.30：[2023秋冬季OS训练营培训课表安排](https://docs.qq.com/sheet/DUHZ3anNKUW53TXdL?tab=000001) 。 9 | 10 | ## 以往信息 11 | - 2023.04.01：2023 年春夏季开源操作系统训练营正式启动。 12 | - 2023.03.23：请参加的同学填写[训练营报名登记表](http://chyyyuuu.mikecrm.com/2zxG8dp)，并加入[相关微信群](./2023os2train.jpg)。 13 | - 2023.03.19: 2023 年春夏季开源操作系统训练营启动&报名交流会，会议时间：2023/03/25 11:00-12:00 ，#腾讯会议号：231-190-126 会议密码：0325。请报名的同学参加。 14 | - [**第一阶段训练安排**](./scheduling-1.md) 15 | - [**第二阶段训练安排**](./scheduling-2.md) 16 | - [**(可选)竞赛级训练安排**](https://github.com/LearningOS/oscomp-kernel-training) 17 | - [**News**](./news.md)（2023 年开源操作系统训练营的新闻和纪要） 18 | - [**QA**](./QA.md)（常见问题解答） 19 | - **Online Ranking**（训练营在线排行榜） 20 | - [第一阶段排行榜：Rust Language Porgramming](https://learningos.github.io/rust-rustlings-ranking/) 21 | - [Rust Language Porgramming ClassRoom邀请链接](https://classroom.github.com/a/H1iQ2GNX) 22 | - 第二阶段排行榜：OS Kernel Design&Implementation 23 | - [基于C语言的uCore Tutorial ClassRoom排行榜]( https://learningos.github.io/2023S-OS-uCore-Classroom-Rank-list/) 24 | - [uCore Tutorial ClassRoom邀请链接](https://classroom.github.com/a/5vRW-e_W) 25 | - [基于Rust语言的rCore Tutorial ClassRoom排行榜]( https://learningos.github.io/2023S-OS-rCore-Classroom-Rank-list/) 26 | - [rCore Tutorial ClassRoom邀请链接](https://classroom.github.com/a/AFBsVzHi) 27 | - [**Learning Resource**](./relatedinfo.md)（训练营学习资源） 28 | 29 | 30 | ## 31 | 32 | ## 历史 33 | - [open-source os training comp 2022](https://github.com/LearningOS/rust-based-os-comp2023/tree/comp2022) 34 | - [open-source os training comp 2021](https://github.com/rcore-os/rCore/wiki/os-tutorial-summer-of-code-2021) 35 | - [open-source os training comp 2020](https://github.com/rcore-os/rCore/wiki/os-tutorial-summer-of-code-2020) 36 | 37 | ## 开源社区负责人 38 | - 李明 微信id：limingth 39 | 40 | ## 助教 41 | - 朱 懿 微信id：ZhiyuanSue 42 | - 闭浩扬 微信id：scpointer 43 | 44 | ## 技术指导委员会 45 | 46 | - 陈向群 47 | - 吴庆波 48 | - 潘爱民 49 | - 张汉东 50 | - 赵霞 51 | - 曹东刚 52 | - 李栋 53 | - 向勇 54 | - 陈渝 55 | - 李国良 56 | - 任炬 57 | 58 | ## 支持与合作单位 59 | 60 | - [rcore-os 开源社区](https://github.com/rcore-os) 61 | - [木兰开源社区](https://portal.mulanos.cn) 62 | - CCF开源发展委员会 63 | - CCF系统软件专业技术委员会 64 | - 清华大学 65 | - 北京工商大学 66 | - 国防科技大学 67 | - CSDN 68 | - 阿图教育 69 | - 鹏城实验室 70 | - 启元实验室 71 | - 中关村实验室 72 | - 之江实验室 73 | - 阿里云 74 | - 华为 75 | - 智谱 ai 76 | - 101 计划操作系统课程虚拟教研室 77 | - [上海大学开源社区](https://github.com/shuosc/) 78 | -------------------------------------------------------------------------------- /announce.md: -------------------------------------------------------------------------------- 1 | ## 公告（Announce） 2 | 3 | - 2023.02.05 2022秋冬季开源操作系统训练营顺利结束 4 | - 2022.11.05 微信群助教名单 5 | 6 | "2022秋冬季开源OS训练营-泛在OS" 微信群助教是@助教-唐洪雨 @刘逸珑 @陈文杰 @李明 @陈渝 如果大家有问题，请在群里咨询助教 7 | 8 | - 2022.11.05 推荐学习顺序&如何加入训练营OS微信群 9 | 10 | 训练营目前安排的学习步骤是，先学rust，再学riscv，然后是os基本实验，最后是比赛级的os训练。目前大家都在最开始阶段的群。我们会建议一个训练营OS群，用于觉得自己已经完成了rust和riscv学习和训练的同学用于讨论OS相关内容。建议还在学习rust和riscv的同学先不必加入新群。如要加入，请联系本群助教。 11 | 12 | - 2022.11.05 unikernel相关的一些论文列表 13 | 14 | https://github.com/chyyuu/aos_course_info/blob/master/unikernel-related.md unikernel相关的一些论文列表，感兴趣的同学可以看看。操作系统很难有全新的理念，unikernel是早期 exokernel （MIT在上世纪90年代提出）在云计算场景下的进一步发展的产物。我们觉得这种思路还可进一步进化，用于当前的AIoT领域，比如工业机器人，智能驾驶等。 15 | 16 | - 2022.11.05 删除报名表 17 | 18 | 根据学员的反馈，考虑到大家的信息安全和隐私， https://github.com/LearningOS/rust-based-os-comp2022/issues/101 的报名作用也已经完成。如果没有收到进一步的异议，用于训练营前期报名的issues https://github.com/LearningOS/rust-based-os-comp2022/issues/101 将在今天下午被删除。 19 | -------------------------------------------------------------------------------- /excellent-students-2022summer.md: -------------------------------------------------------------------------------- 1 | ## 2022年夏季训练营 2 | ### 通过训练营的锻炼并获得训练营证书的优秀学员名单 3 | 4 | 1. 黃建榮 5 | 2. 杨金博 6 | 3. 唐洪雨 7 | 4. 朱懿 8 | 5. 陈林峰 9 | 6. 米明恒 10 | 7. 陈思宇 11 | -------------------------------------------------------------------------------- /excellent-students-2023winter.md: -------------------------------------------------------------------------------- 1 | ## 2023年秋冬季训练营 2 | ### 通过训练营的锻炼并获得训练营证书的优秀学员名单（共28人） 3 | 4 | - 项目1: 郝淼 陈正宁 邱沛中 5 | - 项目2: 尹健徽 许炜冬 王政 周海鹏 6 | - 项目3: 劲强 江昊 周睿 童浩轩 林晨 翟红号 7 | - 项目4: 邱沛中 李国玮 蒋秋吉 刘金成 8 | - 项目5: 袁晖翔 宋宇阳 范天奇 余智超 杜清林 叶可天 许慎林 姚宏伟 9 | - 项目6: 杨凯豪 杨杰 10 | - Dora : 胡友豪 11 | -------------------------------------------------------------------------------- /graduate-students-2023winter.md: -------------------------------------------------------------------------------- 1 | ## 2023年秋冬季训练营 2 | ### 通过训练营的锻炼并获得训练营证书的结业学员名单（共40人） 3 | 4 | - 项目1: 邝劲强 叶可禾 王格格 杜清林 曾榆高 苏爽 刘逸珑 郝逸飞 陈德 袁晖翔 庄广 王英吉 蒋文卓 范天奇 黄文禹 刘哲潭 5 | - 项目2: 肖炯 曾榆高 黄立刚 陈正宁 王振宇 郑好 郭涵宇 王烨文 6 | - 项目3: 杨凯 叶钧喆 李一鸣 金烜宇 尚林玮 袁国栋 王伟 王柱 7 | - 项目4: 徐子信 许世豪 8 | - 项目5: 童浩轩 彭宇科 蒋秋吉 林晨旭 9 | - 项目6: 王传义 王明一 10 | -------------------------------------------------------------------------------- /lab3-os5-passed.md: -------------------------------------------------------------------------------- 1 | | github_username | student_repository_url | 2 | | ---------------- | ------------------------------------------------------- | 3 | | jackyliu16 | https://github.com/LearningOS/lab3-os5-jackyliu16 | 4 | | CL-a11y | https://github.com/LearningOS/lab3-os5-CL-a11y | 5 | | Zfl990109 | https://github.com/LearningOS/lab3-os5-Zfl990109 | 6 | | pickanameforlove | https://github.com/LearningOS/lab3-os5-pickanameforlove | 7 | | Andre-HJR | https://github.com/LearningOS/lab3-os5-Andre-HJR | 8 | | TXuian | https://github.com/LearningOS/lab3-os5-TXuian | 9 | | aucker | https://github.com/LearningOS/lab3-os5-aucker | 10 | | myrfy001 | https://github.com/LearningOS/lab3-os5-myrfy001 | 11 | | wanderya | https://github.com/LearningOS/lab3-os5-wanderya | 12 | | zhaiqiming | https://github.com/LearningOS/lab3-os5-zhaiqiming | 13 | | Yakkhini | https://github.com/LearningOS/lab3-os5-Yakkhini | 14 | | linyihai | https://github.com/LearningOS/lab3-os5-linyihai | 15 | | Godones | https://github.com/LearningOS/lab3-os5-Godones | 16 | | wanghun315 | https://github.com/LearningOS/lab3-os5-wanghun315 | 17 | | werifu | https://github.com/LearningOS/lab3-os5-werifu | 18 | | xy-plus | https://github.com/LearningOS/lab3-os5-xy-plus | 19 | | fengF3ng | https://github.com/LearningOS/lab3-os5-fengF3ng | 20 | | Trojanking123 | https://github.com/LearningOS/lab3-os5-Trojanking123 | 21 | | thy1037 | https://github.com/LearningOS/lab3-os5-thy1037 | 22 | | ZhiyuanSue | https://github.com/LearningOS/lab3-os5-ZhiyuanSue | 23 | | xuwuu | https://github.com/LearningOS/lab3-os5-xuwuu | 24 | | Shl1015CS | https://github.com/LearningOS/lab3-os5-Shl1015CS | 25 | | traversalnat | https://github.com/LearningOS/lab3-os5-traversalnat | 26 | | nkbai | https://github.com/LearningOS/lab3-os5-nkbai | 27 | | Ameima | https://github.com/LearningOS/lab3-os5-Ameima | 28 | | 00yk | https://github.com/LearningOS/lab3-os5-00yk | 29 | | Wonderland23333 | https://github.com/LearningOS/lab3-os5-Wonderland23333 | 30 | | Every365 | https://github.com/LearningOS/lab3-os5-Every365 | 31 | | whfuyn | https://github.com/LearningOS/lab3-os5-whfuyn | 32 | | YXLZJ | https://github.com/LearningOS/lab3-os5-YXLZJ | 33 | | yfblock | https://github.com/LearningOS/lab3-os5-yfblock | 34 | | drysaltery | https://github.com/LearningOS/lab3-os5-drysaltery | 35 | | alexfanqi | https://github.com/LearningOS/lab3-os5-alexfanqi | -------------------------------------------------------------------------------- /news.md: -------------------------------------------------------------------------------- 1 | # 2023 年开源操作系统训练营的新闻与活动纪要 2 | - 2023.04.01：2023 年春夏季开源操作系统训练营正式启动。 3 | - 2023.03.23：请参加的同学填写[训练营报名登记表](http://chyyyuuu.mikecrm.com/2zxG8dp)，并加入[相关微信群](./2023os2train.jpg)。 4 | - 2023.03.19: 2023 年春夏季开源操作系统训练营启动&报名交流会，会议时间：2023/03/25 11:00-12:00 ，#腾讯会议号：231-190-126 会议密码：0325。请报名的同学参加。 5 | 6 | # 以往开源操作系统训练营的新闻与活动纪要 7 | - 2023.02.05：[组件化操作系统设计与实现的相关题目](https://github.com/chyyuu/thoughts/blob/main/task-list.md)，欢迎感兴趣的朋友联系我们。 8 | - 2023.02.05：[2022 秋冬季训练营总结会&组件化操作系统设计与实现技术交流会-part2](https://meeting.tencent.com/v2/cloud-record/share?id=b2bd335e-c3fb-4169-8558-7621c71dfb75&from=3&is-single=true) 9 | - 2023.02.02：[组件化操作系统设计与实现技术交流会-part1](https://meeting.tencent.com/v2/cloud-record/share?id=af9f763c-a862-4dd4-9552-7061b1355b0d&from=3) 10 | - 2023.02.01：2022 秋冬季训练营第二阶段学习结束，[通过第二阶段的学员名单和项目列表](stage2-passed.md)。 11 | - 2022.11.04：到目前为止，参与训练营的学员在 https://github.com/LearningOS 上创建了**2000 多个 public/private gitclassroom repos**。 12 | - 2022.11.01：2022 秋冬季训练营启动交流会，会议时间：2022/11/01 20:00-21:00 ，#腾讯会议号：838-197-763。请报名的同学参加。[视频回放](https://meeting.tencent.com/v2/cloud-record/share?id=00e0e809-1e03-4f41-8e6a-4e71c0ca1342&from=3) 13 | - 2022.10.16：2022 秋冬季训练营开始招生(报名时间段 2022.10.16 ~ 2022.10.30)，请在[报名登记处](https://github.com/LearningOS/rust-based-os-comp2022/issues/101) 填写相关个人信息，并加入[相关微信群](./wechat1016.png)。（如加不了微信群，请写“OS训练营”联系助教许善朴 微信号id： bitmeet520 帮助加入。另外，如果你有时间，其实不用等待报名结束，现在就可以开始基于[第一阶段](./scheduling.md)安排进行自学&自我训练--这就是训练营的主要内容） 14 | - 2022.10.01：2022 秋冬季训练营筹备中，正在准备 2022 年开源操作系统训练营的第一/二阶段安排：[**Stage1 SCHEDULING**](./scheduling.md) & [**Stage2 SCHEDULING**](https://github.com/LearningOS/oscomp-kernel-training)。 15 | - 2022.09.28：[oscomp-kernel-training Github Class Room](https://github.com/LearningOS/oscomp-kernel-training)上线，基于全国大学生操作系统比赛内核挑战赛内容，提供编写支持 Linux App 的操作系统在线训练，在[学习资源](./relatedinfo.md)中增加清华大学计算机系暑期Rust编程课的信息。 16 | - 2022.09.10：祝贺[完成暑期训练营的学员](./excellent-students-2022summer.md)完成最终技术报告，并将获得训练营证书。到目前为止，参与训练营的学员创建了**1000 多个 public/private gitclassroom repos**。 17 | - 2022.08.07：形成三个微信群：训练营异步操作系统、训练营操作系统探索、训练营rcore/zcore，建立部分classroom， 进行有针对性的讨论，开展相关项目。 18 | - 2022.08.06：目前接触并创建rCore Tutorial OS Classroom突破400人次。下午两点交流各位同学的第二阶段项目分组，大致确定要做的事情。 19 | - 2022.08.05：从08.01~08.05，每晚8:30一个zCore技术报告，共完成5个zCore系列报告。 20 | - 2022.08.01：训练营第二阶段开始，中午12点前公布进入[第二阶段人员名单](./lab3-os5-passed.md)，晚上19:30召开“训练营第一阶段总结&第二阶段启动会”，晚上20:30开始技术报告。 21 | - 2022.07.30：[训练营第一阶段结束的调查问卷](https://www.wjx.cn/vm/w8a5pG0.aspx)发布；第二阶段技术交流报告日程安排发布 22 | - 2022.07.15: [训练营在线排行榜](https://os2edu.cn/grading/)发布 23 | - 2022.07.05：晚上 20:30， 基于腾讯会议召开"开源操作系统学习训练营开幕式" 24 | - 2022.07.04：大约 150 人在线报名，微信群目前 120 人左右，162 人在 开始并建立了“lab0-0-setup-env-run-os1”作业的 repos 25 | - 2022.06.28：在微信部分群中发布“欢迎加入 2022 年开源操作系统训练营”的信息，感谢[Rust 语言中文社区](https://rustcc.cn/)、CSDN 和张汉东老师等的进一步宣传 26 | - 2022.06.27：完成夏令营日程内容、建立报名通道，初步建立训练营开发环境 27 | - 2022.06.26：完成基于 github classroom 等资源的训练营开发环境原型系统验证 28 | - 2022.06.22：开始尝试基于 github classroom 等资源 29 | - 2022.06.18：确定本次训练营的大致活动内容，确定支持与合作单位、指导委员会、助教等 30 | - 2022.06.01：训练营准备开始启动 31 | -------------------------------------------------------------------------------- /relatedinfo.md: -------------------------------------------------------------------------------- 1 | # 注意事项 2 | [**Stage1 SCHEDULING**](./scheduling-1.md) & [**Stage2 SCHEDULING**](./scheduling-2.md)是开源操作系统训练营的第一/二阶段安排，可根据阶段安排中的信息和下面列出的资源信息进行自学和自我联系。 3 | 4 | 5 | ## 2022夏季Rust程序设计训练课资源（easy） 6 | 7 | - [清华计算机系大一学生2022暑期课程：Rust程序设计训练](https://lab.cs.tsinghua.edu.cn/rust/) 8 | - [Rust相关书籍/课程/视频等资源汇总](https://github.com/rcore-os/rCore/wiki/study-resource-of-system-programming-in-RUST) 9 | 10 | ## RISC-V 计算机硬件相关资源（normal） 11 | - [RISC-V相关课程资源](https://github.com/rcore-os/rCore/wiki/os-tutorial-summer-of-code-2021#step-1-%E8%87%AA%E5%AD%A6risc-v%E7%B3%BB%E7%BB%9F%E7%BB%93%E6%9E%84%E5%A4%A7%E7%BA%A67%E5%A4%A9) 12 | 13 | ## 2022春季OS课资源（normal） 14 | 15 | ### 课程Slides 16 | 17 | - [清华计算机系大三学生2022春季OS课程Slides](https://learningos.github.io/os-lectures/) 18 | 19 | ### 课程参考书 20 | 21 | - [Operating Systems: Three Easy Pieces](https://pages.cs.wisc.edu/~remzi/OSTEP/) 22 | - [rCore Tutorial Book v3](https://rcore-os.github.io/rCore-Tutorial-Book-v3/) 23 | 24 | ### 课程视频 25 | 26 | - [20220221第一次课视频](https://meeting.tencent.com/v2/cloud-record/share?id=5fcc9ef3-cb43-48f6-9d33-f75f640e8c38&from=3) 27 | - [20220228第二次课视频](https://meeting.tencent.com/v2/cloud-record/share?id=0c2a73ec-238a-453b-8f0f-aaadaeb55eca&from=3) 28 | - [20220307第三次课视频](https://meeting.tencent.com/v2/cloud-record/share?id=c21406cf-96f9-4df6-8cab-af4dbd798769&from=3) 29 | - [20220314第四次课视频](https://meeting.tencent.com/v2/cloud-record/share?id=5dae93b5-6f9d-40b9-86c3-f2c13670ecaf&from=3) 30 | - [20220321第五次课视频](https://meeting.tencent.com/v2/cloud-record/share?id=4e9dc00e-1c95-47b8-bd18-6a24fe2e3450&from=3) 31 | - [20220328第六次课视频](https://meeting.tencent.com/v2/cloud-record/share?id=a48d439c-c161-4a0a-bf75-70024d408526&from=3) 32 | - [20220418第八次课视频](https://meeting.tencent.com/v2/cloud-record/share?id=92b88816-805b-44f0-af5c-227654d5c5bd&from=3) 33 | - [20220425第九次课视频](https://meeting.tencent.com/v2/cloud-record/share?id=622c85a7-6549-4e1d-9ff1-6fb908107791&from=3) 34 | - [20220509第十次课视频](https://meeting.tencent.com/v2/cloud-record/share?id=26487a19-875a-457f-8a89-d0a3ca785915&from=3) 35 | - [20220516第11次课视频](https://meeting.tencent.com/v2/cloud-record/share?id=e45a7ab1-325a-44f1-904d-1bb661daa0dd&from=3) 36 | - [20220523第12次课视频](https://meeting.tencent.com/v2/cloud-record/share?id=5c2c8e4b-f9a0-4228-bb4d-b83c648057a0&from=3) 37 | - [20220530第13次课视频](https://meeting.tencent.com/v2/cloud-record/share?id=34309e7e-3835-4d3f-a056-eceec5598f66&from=3) 38 | 39 | > 缺第七次课，各次课的密码是8位数字中的后4位数字 40 | 41 | ## 2022春季Advanced OS课相关资源（hard） 42 | 43 | - [清华计算机系研究生2021春季Advanced OS课程视频/slides](https://www.xuetangx.com/course/thu080917777/3234209) 44 | - [论文阅读列表](https://github.com/chyyuu/aos_course_info/blob/master/readinglist.md) 45 | - [OS比赛相关的一些硬件/OS实例/教程](https://github.com/oscomp/os-competition-info/blob/main/ref-info.md) 46 | - [Rust based OS/Hypervisor/VMM/Firmwire](https://github.com/chyyuu/aos_course_info/blob/master/oslist.md) 47 | 48 | ## 2022春季OS课实验框架讲解 49 | 50 | - [20220001 rcore-tutorial-v3 ch1&ch2](https://cloud.tsinghua.edu.cn/f/254e6cc6921849e29e8c/) 51 | - [20220002 rcore-tutorial-v3 ch3](https://cloud.tsinghua.edu.cn/f/17a7c9d9b57f4838ae5f/) 52 | - [20220003 rcore-tutorial-v3 ch4](https://cloud.tsinghua.edu.cn/f/d44189eff077452e99a5/) 53 | - [20220004 rcore-tutorial-v3 ch5](https://cloud.tsinghua.edu.cn/f/e2a8b8b54037484fac73/) 54 | - [20220005 rcore-tutorial-v3 ch6](https://cloud.tsinghua.edu.cn/f/a5d5ece6e5b849a3ae8a/) 55 | - [20220006 rcore-tutorial-v3 ch8](https://cloud.tsinghua.edu.cn/f/b6b94ccebe084b31aa6b/) 56 | - [20220007 rcore-tutorial-v3 ch9](https://cloud.tsinghua.edu.cn/f/1c9706422ad54cad997c/) 57 | 58 | > 密码是 `xushanpu123` 59 | 60 | ## 2022春季OS课实验框架OS API DOC 61 | 62 | > 下面各章 ``[345678]`` 的源码与 本repo中的 ``os[345678]-ref/src`` 目录下的源码是相同的。 63 | 64 | ### OS API docs of rCore Tutorial Code 2022S 65 | 66 | - [OS API docs of ch3](https://learningos.github.io/rCore-Tutorial-Code-2022S/ch3/os/index.html) 67 | - [OS API docs of ch4](https://learningos.github.io/rCore-Tutorial-Code-2022S/ch4/os/index.html) 68 | - [OS API docs of ch5](https://learningos.github.io/rCore-Tutorial-Code-2022S/ch5/os/index.html) 69 | - [OS API docs of ch6](https://learningos.github.io/rCore-Tutorial-Code-2022S/ch6/os/index.html) 70 | - [easyFS API doc in ch6]( https://learningos.github.io/rCore-Tutorial-Code-2022S/ch6/easy_fs/index.html) 71 | - [OS API docs of ch7](https://learningos.github.io/rCore-Tutorial-Code-2022S/ch8/os/index.html) 72 | - [OS API docs of ch8](https://learningos.github.io/rCore-Tutorial-Code-2022S/ch8/os/index.html) 73 | 74 | ## 训练营rcore tutorial和rustlings视频讲解 75 | 76 | - [rustlings & OS lab0-0 搭建环境和初始开发过程](https://www.bilibili.com/video/BV1fY4y1n7up?share_source=copy_web) 77 | - [rustlings:rust所有权和借用相关](https://www.bilibili.com/video/BV1ze4y1R7C9?share_source=copy_web) 78 | - [chapter1&chapter2实践的框架和代码分析讲解](https://cloud.tsinghua.edu.cn/f/254e6cc6921849e29e8c/) 79 | - [chapter3(lab1)实践的框架和代码分析讲解](https://cloud.tsinghua.edu.cn/f/17a7c9d9b57f4838ae5f/) 80 | - [chapter4(lab2)的代码分析和编程练习讲解](https://cloud.tsinghua.edu.cn/f/d44189eff077452e99a5/) 81 | - [chapter5(lab3)进程管理的代码解析和编程练习讲解](https://cloud.tsinghua.edu.cn/f/e2a8b8b54037484fac73/) 82 | - [chapter6(lab4)文件系统的代码解析和练习讲解视频](https://cloud.tsinghua.edu.cn/f/a5d5ece6e5b849a3ae8a/) 83 | - [chapter8(lab5)同步互斥的代码解析和练习讲解视频](https://cloud.tsinghua.edu.cn/f/b6b94ccebe084b31aa6b/) 84 | - [chapter9（第二阶段训练）内核中断/外设管理的代码解析讲解视频](https://cloud.tsinghua.edu.cn/f/1c9706422ad54cad997c/) 85 | 86 | ## “秋冬季开源操作系统训练营”过程相关内容 87 | - 2022.11.01：[20221101：秋冬季训练营启动交流会视频回放](https://meeting.tencent.com/v2/cloud-record/share?id=00e0e809-1e03-4f41-8e6a-4e71c0ca1342&from=3) 88 | - 2023.02.05：[2022 秋冬季训练营总结会&组件化操作系统设计与实现技术交流会-part2](https://meeting.tencent.com/v2/cloud-record/share?id=b2bd335e-c3fb-4169-8558-7621c71dfb75&from=3&is-single=true) 89 | - 2023.02.02：[组件化操作系统设计与实现技术交流会-part1](https://meeting.tencent.com/v2/cloud-record/share?id=af9f763c-a862-4dd4-9552-7061b1355b0d&from=3) 90 | 91 | ## "夏季开源操作系统学习训练营开幕式" 相关slides 92 | 93 | - [20220705：2022年夏季开源操作系统学习训练营：日程安排：向勇](https://github.com/LearningOS/resrouce-on-rust-based-os-comp2022/blob/main/20220705-%E5%90%91%E5%8B%87-%E5%BC%80%E5%B9%95%E5%BC%8F%E4%B8%8A%E7%9A%84%E4%BB%8B%E7%BB%8D-v4.pdf) 94 | - [20220705：2022年夏季开源操作系统学习训练营：Rust学习与领域应用：张汉东](https://github.com/LearningOS/resrouce-on-rust-based-os-comp2022/blob/main/20220705-%E5%BC%A0%E6%B1%89%E4%B8%9C-Rust%E5%AD%A6%E4%B9%A0%E4%B8%8E%E9%A2%86%E5%9F%9F%E5%BA%94%E7%94%A8.pptx) 95 | 96 | > 如访问上述网址碰到问题，请联系助教了解访问方式。 97 | -------------------------------------------------------------------------------- /scheduling-1.md: -------------------------------------------------------------------------------- 1 | 2 | # 2023年春夏季开源操作系统训练营：第一阶段 3 | 4 | - [新闻与纪要](./news.md) 5 | - [常见问题解答](./QA.md) 6 | - [Learning Resource](./relatedinfo.md) (训练营学习资源) 7 | - Online Ranking （训练营在线排行榜） 8 | - [第一阶段排行：Rust Lang](https://learningos.github.io/rust-rustlings-ranking/) 9 | - [rustlings Rust编程训练教室](https://classroom.github.com/a/H1iQ2GNX) 10 | 11 | 欢迎在校学生/工程师在2023年春夏季参加清华大学、CSDN、阿图教育等共同举办的**2023年春夏季开源操作系统训练营**活动（2022.04.01～2023.08.01），本次活动分为两个阶段： 12 | 13 | - 第一阶段：（2023.04.01～2023.05.01）线上自学Rust编程和OS基础，并进行[Rust语言编程自学](https://github.com/LearningOS/rust-based-os-comp2023/blob/main/scheduling-1.md#step-0-%E8%87%AA%E5%AD%A6rust%E7%BC%96%E7%A8%8B%E5%A4%A7%E7%BA%A6714%E5%A4%A9)、[Rust语言编程实验](https://github.com/LearningOS/rustlings-template)、[RISC-V处理器学习](https://github.com/LearningOS/rust-based-os-comp2023/blob/main/scheduling-1.md#step-1-%E8%87%AA%E5%AD%A6risc-v%E7%B3%BB%E7%BB%9F%E7%BB%93%E6%9E%84%E5%A4%A7%E7%BA%A627%E5%A4%A9) **注意：如第二阶段选择基于C语言的uCore Tutorial做OS Kernel实验，可跳过Rust语言编程自学和实验。** 14 | - 第二阶段：（2023.05.01～2023.07.01）OS内核学习与实验 15 | - [C-based uCore Tutorial Kernel学习&实验](https://github.com/LearningOS/uCore-Tutorial-Guide-2023S) 16 | - [Rust-based rCore Tutorial Kernel学习&实验](https://github.com/LearningOS/rCore-Tutorial-Guide-2023S) 17 | - 可选：（完成第二阶段后～2023.08.20）OS竞赛级实战模拟训练：[OS Kernel supporting Linux Apps实验](https://github.com/LearningOS/oscomp-kernel-training) ,主要是**用Rust语言设计实现支持Linux APP的OS Kernel**，大约要支持<100个左右的Linux Syscalls，能通过上百个动静态链接的Linux App测试用例。 18 | - 可选：（完成第二阶段后～2023.08.20）[组件化操作系统设计与实现](https://github.com/rcore-os/arceos)，设计实现可灵活组合的内核模块，可灵活定制的内核框架，以及基于组合态OS的用户态应用程序。 19 | - 可选：（完成第二阶段后～2023.08.20）[可定制的hypervisor](https://github.com/LearningOS/RVM-Tutorial)，设计实现可在裸机或Linux中运行的Hypervisor，支持x86/ARM/RISC-V等多种硬件平台。 20 | - 可选：（完成第二阶段后～2023.08.20）如果有其它有趣的想法或愿意参加更有挑战的训练（比如实现支持Rust协程的OS，支持unikernel&微库形态的OS等），欢迎提出，联系LearningOS开源社区负责人李明老师（微信id：limingth）和助教。 21 | 22 | 23 | 如有兴趣参加，请在2023年04月01日前请在填写[训练营报名登记表](http://chyyyuuu.mikecrm.com/2zxG8dp)填写相关个人信息，并加入[相关微信群](./2023os2train.jpg)。获得邀请后，将开始参与本次训练营活动。完成本次活动第一阶段（2023.04.01～2023.05.01）的同学如果通过review，将可在2023.05.01～2023.07.01，开展第二阶段[OS Kernel supporting Linux Apps实验](https://github.com/LearningOS/oscomp-kernel-training)。训练营结束后，部分表现突出的同学将获得训练营优秀证书。鼓励同学继续以开源社区的方式参与到企业/科研院所的操作系统实习/实践/工作/学习等相关的活动。 24 | 25 | > 我们也在持续探索和改进开源操作系统训练营，即这个活动不仅仅局限在 2022.11.01～2023.02.01。我们希望建立的是一种长期持续发展的操作系统训练营模式，即各种学习资源都开源并整理集中在一起，导师/助教和学生/爱好者之间基于要做的实验或项目不定期/定期的进行交流。学生/爱好者完成了一定程度的学习和训练后，除了自身得到能力的提升外，还可获得相关证书和就业/学习等机会和相关推荐等，推动他在未来的进一步发展。 26 | 27 | ## 目标： 28 | 29 | **培养具有开源思想的合作者，搭建开源合作平台。** 30 | 31 | **探索把现代系统语言Rust和灵活开放的系统结构RISC-V带入到操作系统的架构与设计的创新中来，思考未来的操作系统应该是什么样。** 32 | 33 | ## 宗旨： 34 | 35 | **希望本活动的组织，能为操作系统爱好者提供一个活跃的开源社区环境，为对Rust、RISC-V和操作系统感兴趣的人士营造一个平等的学习与交流空间，吸引更多对操作系统感兴趣的人士参与。** 36 | 37 | ## 相关信息： 38 | 39 | - [参加2020--2022 OS训练营学生的blog](https://rcore-os.github.io/blog/)，鼓励参加2023 OS训练营的同学把自己在学习过程中的感悟/收获等写成blog，生成pr，并提交到 上，让更多人看到你的进步！ 40 | - **注意** 为及时了解和指导同学的学习和实践情况并推动学生相互帮助，本次活动要求学生把每周学习实践的过程记录（Markdown格式）放在github上自己的公开repo中。可参见[每日学习实践的具体例子](https://github.com/GCYYfun/DailySchedule)和[2020年OS训练营同学的每日学习情况汇总](https://github.com/rcore-os/rCore-Tutorial/issues/18 ) 。请参加实习的同学把记录每天的进展的git repo网址 更新到[2023年OS训练营同学的每日学习情况汇总](https://github.com/LearningOS/rust-based-os-comp2023/issues/1) 中。要求每位同学在自己的git repo中记录自己的每周进展，其他同学也可以参考学习。 41 | - **注意** 第一阶段学习中的技术问题，建议基于[OS训练营github discussion](https://github.com/LearningOS/rust-based-os-comp2023/discussion) 发出并讨论。 42 | 43 | 44 | ## 第一阶段活动安排 45 | 46 | ### 总体学习要求和成绩考核方式 47 | 48 | - 在[学习实践过程记录表](https://github.com/LearningOS/rust-based-os-comp2023/discussions/170)上登记自己每日/周学习记录情况的repo网址，并在这个repo上记录每日/周学习记录情况 (成绩分数：20%) 49 | - [学习记录的标杆1](https://github.com/LearningOS/record)，浙江大学本科生徐文浩的2020开源操作系统训练营的过程记录，是大家学习的榜样，供大家学习参考。 50 | - [学习记录的标杆2](https://kiprey.github.io/tags/uCore/)：湖南大学本科生肖政杭的自学ucore for x86的过程记录，是大家学习的榜样，供大家学习参考。 51 | 52 | - 在[第一阶段学习的讨论](https://github.com/LearningOS/rust-based-os-comp2023/discussions/)上的提问和回答问题情况 (成绩分数：30%) 53 | - 要求的[Rust-lang Lab Test based on Rustlings（采用Github Classroom模式的Rustling小练习）](https://classroom.github.com/a/H1iQ2GNX) 的完成情况 (成绩分数：70%) 54 | 55 | 56 | #### step 0 自学rust编程（大约7~14天） 57 | 58 | 前提条件： 要求有基本数据结构，算法基础，相对了解或熟悉C语言等编程. 59 | 60 | 1. 自学基础知识：[阅读书籍/课程/视频等资源汇总](https://github.com/rcore-os/rCore/wiki/study-resource-of-system-programming-in-RUST) 61 | 62 | - 推荐：[Rust语言圣经(Rust教程 Rust Course和配套练习)](https://course.rs/) 63 | - 推荐：[半小时快速了解Rust](https://fasterthanli.me/articles/a-half-hour-to-learn-rust) 64 | - 推荐：[Rust速查表（cheatsheet）](https://cheats.rs/) 该项目不仅提供了基础的语法速查，还有执行顺序详解和编写时需要关注的注意事项。项目还包含了示例代码（EX）、书籍（BK）、标准（STD）等相关资料的扩展。 65 | - 推荐：[清华计算机系大一学生2022暑期课程：Rust程序设计训练（有课程视频）](https://lab.cs.tsinghua.edu.cn/rust/) 66 | 67 | 2. 自学编程 68 | 69 | - [2023春夏季OS训练营--rustling训练](https://classroom.github.com/a/H1iQ2GNX)（采用Github Classroom模式的Rustling小练习，点击上述链接，形成自己的练习用repo） 70 | - 要求：**必须完成** 。完成所有练习后，执行 ``git add; git commit -m"update"; git push`` 命令，把更新提交到GithubClassroom的CI进行自动评测。要求小练习全部通过GithubClassroom的CI自动评测。 71 | - [学习系列视频：Rust中文社群线上学习室--通过 Rustlings 学 Rust](https://space.bilibili.com/24917186/video) 72 | 73 | **提示：基于github classroom的开发方式** 74 | 75 | 基于github classroom，可方便建立开发用的git repository，并可基于github的 codespace（在线版ubuntu +vscode）在线开发使用。整个开发环境仅仅需要一个网络浏览器。 76 | 77 | > codespace 不是必须的。如果是本地的ubuntu中建立开发环境，可在shell中执行 `make ubuntu_local_setenv` 来自动安装配置开发环境（执行需要 `sudo` root 权限，仅需要执行一次）。 78 | 79 | 1. 在网络浏览器中用自己的 github id 登录 github.com。 80 | 2. 接收 [Rust-lang Lab Test based on Rustlings 的github classroom在线邀请](https://classroom.github.com/a/H1iQ2GNX) ，根据提示一路选择OK即可。 81 | 3. 完成第二步后，你的rustings实验练习 的 github repository 会被自动建立好，点击此github repository的链接，就可看到你要完成的实验了。 82 | 4. 在你的第一个实验练习的网页的中上部可以看到一个醒目的 `code` 绿色按钮，点击后，可以进一步看到 `codespace` 标签和醒目的 `create codesapce on edu` 绿色按钮。请点击这个绿色按钮，就可以进入到在线的ubuntu +vscode环境中 83 | 5. 再按照下面的环境安装提示在vscode的 `console` 中安装配置开发环境：rustc等工具。 84 | 6. 然后就可以基于在线vscode进行测试 (执行命令 `rustlings watch` ），编辑代码的循环实验过程了。 85 | 7. 如果使用本地的环境进行rustlings的练习，请按照接下来的步骤进行：首先需要安装一个Linux的环境，对于windows的用户，推荐使用wsl2，也可以使用vmware等虚拟机进行安装。如果在这一步存在问题，请联系助教。 86 | 87 | 8. 创建ssh key。在linux环境下，使用` ssh-keygen -t rsa -b 4096 -C "你的邮箱" `命令，创建ssh key，下面的选项全部直接敲回车即可。 88 | 随后使用` cat ~/.ssh/id_rsa.pub` 命令查看生成的公钥，并完整的复制下来。 89 | 在github仓库界面点击自己的头像，选择`settings`。进入到设置页面后，点击左侧的`SSH and GPG keys`选项。点击`New SSH key`选项，并将复制下来的内容粘贴上去，添加该ssh key的描述。随后点击`Add SSH key`，并一路点击确认即可。 90 | 91 | 9. 在本地安装rust。进入linux环境下，参考rcore 教程 http://rcore-os.cn/rCore-Tutorial-Book-v3/ 中， 第零章操作系统概述，实验环境配置的内容，找到Rust 开发环境配置的章节，相应配置即可，你可以同时将后续需要的环境也配置好。 92 | 93 | 10. clone实验仓库到本地。在前面点击链接生成的仓库中，同样点击醒目的 `code` 绿色按钮，选择`local`下的`ssh`选项，复制下面的链接。随后回到本地linux环境下，使用`git clone 复制的链接`的方式，将目标仓库clone到本地。随后，使用`ls`命令查看自己clone下来的文件夹，再使用`cd`命令进入到该文件夹下，使用`cargo install --force --path .`安装rustlings。 94 | 95 | 11. 练习rustlings。使用vscode等编辑器，进入clone下来的目录下的`exercises`文件夹，依次完成对应的练习。使用`rustlings run 练习名称`去运行对应练习，也可以使用`rustlings hint 练习名称`查看题解。 96 | 97 | 12. 提交。当做完部分或所有练习之后，执行 ``git add; git commit -m "update"; git push`` 命令，把更新提交到GithubClassroom的CI进行自动评测。你可以在github仓库页面的actions页面，看到你的CI提交结果，或者 https://learningos.github.io/rust-rustlings-ranking/ 上面查看自己的评分。 98 | 99 | 13. 上述步骤有任何问题都可以找助教。 100 | 101 | - （Option）[32 Rust Quizes](https://dtolnay.github.io/rust-quiz/1) 102 | - 要求：小练习全部通过。（**非必须完成**） 103 | - （Option）[exercisms.io 快速练习(88+道题目的中文详细描述)](http://llever.com/exercism-rust-zh/index.html) 104 | - 要求：大部分练习会做或能读懂。（**非必须完成**） 105 | - [exercism.io官方站点](https://exercism.io/) 106 | 107 | #### step 1 自学risc-v系统结构（大约2~7天） 108 | 109 | 前提条件：要求有基本计算机组成原理，计算机系统结构基础。 110 | 111 | 阅读《计算机组成与设计（RISC-V版）》第一、二章，可以在整体结构上对 RISC-V 体系建立基本认知。再进行后面的学习比较有效果。 112 | 113 | #### 自学材料和练习要求: 114 | 115 | 1. 阅读书籍和在线课程 116 | 117 | - 自学[PPT for RISC-V特权指令级架构](https://content.riscv.org/wp-content/uploads/2018/05/riscv-privileged-BCN.v7-2.pdf) 118 | - 自学[RISC-V手册：一本开源指令集的指南](http://riscvbook.com/chinese/RISC-V-Reader-Chinese-v2p1.pdf) 重点是第10章 119 | - （Option）自学[RISC-V特权指令级规范](https://riscv.org/technical/specifications/) 重点是与OS相关的特权硬件访问的规范内容（Privileged Spec） 120 | - （Option）自学[RISC-V汇编手册](https://github.com/riscv-non-isa/riscv-asm-manual/blob/master/riscv-asm.md) 121 | - （Option）[计算机组成与设计：RISC-V 教材](https://item.jd.com/12887758.html) 这是完整的课程教材，不要求全部看完，请根据自己的需求选择。 122 | - （Option）[计算机组成与设计：RISC-V 浙大在线课程](http://www.icourse163.org/course/ZJU-1452997167) 这是完整的一门课，不要求全部看完，请根据自己的需求选择。 123 | 124 | 2. 其他参考学习信息 125 | 126 | - （Option）[Berkeley CS61C: Great Ideas in Computer Architecture (Machine Structures)](http://www-inst.eecs.berkeley.edu/~cs61c/sp18/) 127 | 128 | > Option的含义是：如果有足够的时间建议看看，否则在后续要用到时或需要查询进一步信息时再查阅这些内容。 129 | 130 | 3. 通过要求 131 | 132 | - 掌握RUST编程，理解RISC-V与OS相关的硬件特性（中断，异常，系统调用，寄存器，特权级，MMU...）。 133 | 134 | One More Thing：当你看到这，感觉第一阶段还没开始，还在想下一步要干啥时，我们的建议是：**Just Do It NOW!** 135 | -------------------------------------------------------------------------------- /scheduling-2.md: -------------------------------------------------------------------------------- 1 | 2 | # 2023年春夏季开源操作系统训练营：第二阶段 3 | 4 | - [新闻与纪要](./news.md) 5 | - [常见问题解答](./QA.md) 6 | - [Learning Resource](./relatedinfo.md) (训练营学习资源) 7 | - Online Ranking （训练营在线排行榜） 8 | - [uCore Tutorial ClassRoom排名页面]( https://learningos.github.io/2023S-OS-uCore-Classroom-Rank-list/) 9 | - [rCore Tutorial ClassRoom排名页面]( https://learningos.github.io/2023S-OS-rCore-Classroom-Rank-list/) 10 | - Classroom 11 | - [uCore Tutorial ClassRoom邀请链接](https://classroom.github.com/a/5vRW-e_W) 12 | - [rCore Tutorial ClassRoom邀请链接](https://classroom.github.com/a/AFBsVzHi) 13 | 14 | - 第二阶段：（2023.05.01～2023.07.01）线上自学OS基础知识，并进行OS实验 15 | - [C-based uCore Tutorial Kernel学习&实验](https://github.com/LearningOS/uCore-Tutorial-Guide-2023S) 16 | - [Rust-based rCore Tutorial Kernel学习&实验](https://github.com/LearningOS/rCore-Tutorial-Guide-2023S) 17 | 18 | 19 | ## 相关信息： 20 | 21 | - [参加2020--2022 OS训练营学生的blog](https://rcore-os.github.io/blog/)，鼓励参加2023 OS训练营的同学把自己在学习过程中的感悟/收获等写成blog，生成pr，并提交到 上，让更多人看到你的进步！ 22 | - **注意** 为及时了解和指导同学的学习和实践情况并推动学生相互帮助，本次活动要求学生把每周学习实践的过程记录（Markdown格式）放在github上自己的公开repo中。可参见[每日学习实践的具体例子](https://github.com/GCYYfun/DailySchedule)和[2020年OS训练营同学的每日学习情况汇总](https://github.com/rcore-os/rCore-Tutorial/issues/18 ) 。请参加实习的同学把记录每天的进展的git repo网址 更新到[2023年OS训练营同学的每日学习情况汇总](https://github.com/LearningOS/rust-based-os-comp2023/issues/1) 中。要求每位同学在自己的git repo中记录自己的每周进展，其他同学也可以参考学习。 23 | - **注意** 第二阶段学习中的技术问题，建议基于[OS训练营github discussion](https://github.com/LearningOS/rust-based-os-comp2023/discussion) 发出并讨论。 24 | 25 | 26 | ## 第二阶段活动安排 27 | 28 | ### 总体学习要求和成绩考核方式 29 | 30 | - 在[学习实践过程记录表](https://github.com/LearningOS/rust-based-os-comp2022/issues/1)上登记自己每日/周学习记录情况的repo网址，并在这个repo上记录每日/周学习记录情况 (成绩分数：20%) 31 | - [学习记录的标杆1](https://github.com/LearningOS/record)，浙江大学本科生徐文浩的2020开源操作系统训练营的过程记录，是大家学习的榜样，供大家学习参考。 32 | - [学习记录的标杆2](https://kiprey.github.io/tags/uCore/)：湖南大学本科生肖政杭的自学ucore for x86的过程记录，是大家学习的榜样，供大家学习参考。 33 | 34 | - 在[OS训练营github discussion](https://github.com/LearningOS/rust-based-os-comp2023/discussion) 上的提问和回答问题情况，在[第二阶段OS学习项目](https://github.com/LearningOS/rust-based-os-comp2023/) 、 [rCore Tutorial v3的详细实验指导内容](https://rcore-os.github.io/rCore-Tutorial-Book-v3/) 上的Pull Request提交情况（代码改进、文档改进、文档错误等） (成绩分数：30%) 35 | 36 | - step 0 [第一阶段OS学习的5个实验](https://github.com/LearningOS/rust-based-os-comp2023#kernel-labs)的完成情况和总结报告 (成绩分数：70%) 37 | - [第一阶段总结报告的参考：杨攀同学的2021年开源操作系统训练营第一阶段总结报告](https://rcore-os.github.io/blog/2021/07/29/rcore-summary-yangpan/) 38 | 39 | ### 第二阶段的训练步骤 40 | 41 | 基于C语言或Rust语言进行操作系统内核实验--based on qemu （大约30~60天） 42 | 43 | 前提条件：要求有操作系统的基础，基本理解RISC-V与OS相关的硬件特性 44 | 45 | 46 | #### 课程参考 47 | - [课程幻灯片](https://www.yuque.com/docs/share/4c39608f-3051-4445-96ca-f3c018cb96c7) 48 | - 参考书 49 | - [Operating Systems: Three Easy Pieces](https://pages.cs.wisc.edu/~remzi/OSTEP/) 50 | - [深入了解计算机系统](https://hansimov.gitbook.io/csapp/) 51 | - [RISC-V Reader中文版](http://riscvbook.com/chinese/RISC-V-Reader-Chinese-v2p1.pdf) 52 | 53 | #### 课程实践：rCore Tutorial Book v3 54 | - [课程实践参考书](https://learningos.github.io/rCore-Tutorial-Book-v3/) 55 | - [课程实践代码仓库](https://github.com/rcore-os/rCore-Tutorial-v3) 56 | - [课程实践代码的API文档](https://github.com/rcore-os/rCore-Tutorial-v3#os-api-docs) 57 | 58 | 59 | #### 基于C语言的uCore Tutorial实验指导 60 | 61 | - [实验代码](https://github.com/LearningOS/uCore-Tutorial-Code-2023S/) 62 | - [实验文档](https://learningos.github.io/uCore-Tutorial-Guide-2023S/) 63 | - [测试用例](https://github.com/LearningOS/uCore-Tutorial-Test-2023S) 64 | 65 | 66 | #### 基于Rust语言的rCore Tutorial实验指导 67 | - [实验文档](https://learningos.github.io/rCore-Tutorial-Guide-2023S/) 68 | - [API文档](https://github.com/LearningOS/rCore-Tutorial-Guide-2023S/#os-api-docs-of-rcore-tutorial-code-2022s) 69 | - [实验代码](https://github.com/LearningOS/rCore-Tutorial-Code-2023S) 70 | - [测试用例](https://github.com/LearningOS/rCore-Tutorial-Test-2023S) 71 | 72 | 73 | #### [uCore和rCore实验讲解视频](https://www.yuque.com/docs/share/1b5b9260-8a80-4427-a612-78ec72b37e5f) 74 | 75 | #### 建立基于ClassRoom实验的具体步骤 76 | **基于C语言的uCore Tutorial** 77 | - [uCore Tutorial ClassRoom邀请链接](https://classroom.github.com/a/5vRW-e_W)：点击后按提示可以建立自己的uCore Tutorial实验专用仓库 78 | - [uCore Tutorial ClassRoom排名页面]( https://learningos.github.io/2023S-OS-uCore-Classroom-Rank-list/)：可以查看自己的uCore Tutorial实验的排名情况 79 | 80 | **基于Rust语言的rCore Tutorial** 81 | - [rCore Tutorial ClassRoom邀请链接](https://classroom.github.com/a/AFBsVzHi)：点击后按提示可以建立自己的rCore Tutorial实验专用仓库 82 | - [rCore Tutorial ClassRoom排名页面]( https://learningos.github.io/2023S-OS-rCore-Classroom-Rank-list/)：可以查看自己的rCore Tutorial实验的排名情况 83 | 84 | 85 | 请根据各个实验的具体实验要求在自己的仓库中完成5个实验。请在每完成一个实验（完成编码和实验报告文档）后，请通过执行 `git push` 命令来更新自己的实验专用 repos，来通过基于GitHub Classroom的CI测试。 86 | 87 | One More Thing：当你看到这，感觉第二阶段还没开始，还在想下一步要干啥时，我们的建议是：**Just Do It NOW!** 88 | -------------------------------------------------------------------------------- /stage2-passed.md: -------------------------------------------------------------------------------- 1 | ## 2022秋冬季开源操作系统训练营第二阶段通过学员名单 2 | - 张艺枫 叶自立 郭睆 黄培源 3 | 4 | ## 第二阶段通过项目列表 5 | - https://github.com/LearningOS/oscomp-kernel-training-DarkAngelEX 6 | - https://github.com/LearningOS/oscomp-kernel-training-fg-sn2003 7 | - https://github.com/LearningOS/oscomp-kernel-training-npucore 8 | -------------------------------------------------------------------------------- /stage3-sched.md: -------------------------------------------------------------------------------- 1 | # 2022年开源操作系统训练营：第二阶段 2 | 3 | ## 相关信息 4 | 5 | - **注意：** 为及时了解和指导同学的学习和实践情况并推动学生相互帮助，本次活动要求学生把每日学习实践的过程记录在自己在github的公开repo上。可参考： 6 | - [徐文浩的2020开源操作系统训练营的过程记录](https://github.com/LearningOS/record) 7 | - [2021开源操作系统训练营第二阶段总结列表](https://rcore-os.github.io/blog/categories/report/) 8 | - [2020开源操作系统训练营第二阶段总结：K210组RustSBI开发总结 -- 洛佳](https://rcore-os.github.io/blog/2020/09/06/os-report-final-luojia65/) 9 | - [2020开源操作系统训练营第二阶段总结：zCore Summer of Code 2020 报告 -- 车春池](https://rcore-os.github.io/blog/2020/09/02/zcore_report_chechunchi/) 10 | - [2020开源操作系统训练营第二阶段总结：移植rCore-Tutorial 到k210 -- 徐文浩](https://rcore-os.github.io/blog/2020/08/30/report-k210/) 11 | - [2020开源操作系统训练营第二阶段总结：rCore 到 zCore 功能迁移组报告 -- 郑昱笙、李宇](https://rcore-os.github.io/blog/2020/08/30/report-of-rCore-to-zCore/) 12 | - [陈兴的每日学习实践的过程记录](https://github.com/GCYYfun/DailySchedule) 13 | 14 | ## 日程：第一周：OS相关技术讲解与学习（7天） 15 | 16 | - 题目：[CoreDebugger：支持Rust语言的源代码级内核调试工具，报告人：陈志扬，时间 2022.07.31 9:00(周日上午)](https://www.bilibili.com/video/BV1aY4y1P71W/?spm_id_from=333.999.0.0&vd_source=e4d77f526a0a13adbbe36506bd75e2e8) 17 | - 题目：[zCore结构和核心组件，报告人：张译仁，时间：2022.08.01 20:30(周一晚上)](https://www.bilibili.com/video/BV1LN4y1j7ce/?spm_id_from=333.999.0.0) 18 | - 题目：[操作系统多核启动，报告人：杨德睿，时间：2022.08.02 20:30(周二晚上)](https://www.bilibili.com/video/BV1d14y147L1/?spm_id_from=333.999.0.0) 19 | - 题目：[实现zCore syscall，报告人：董峰，时间：2022.08.03 20:30(周三晚上)](https://www.bilibili.com/video/BV1xN4y1V7uL/?spm_id_from=333.999.0.0) 20 | - 题目：[zCore网络框架，报告人：萧络元，时间：2022.08.03 20:30(周四晚上)](https://www.bilibili.com/video/BV1ia411V7eA/?spm_id_from=333.999.0.0) 21 | - 题目：[zCore单元测试框架，报告人：石振兴，时间：2022.08.05 20:30(周五晚上)](https://www.bilibili.com/video/BV1gP411j78D/?spm_id_from=333.999.0.0) 22 | 23 | ## 日程：第二~第四周：操作系统研究与探索项目 (34天) 24 | 25 | 目前设置了多个项目，学生可选择参加下面的项目，指导老师制定以周为单位的项目研究计划。 26 | 27 | **注意：参加操作系统研究与探索项目的前提先完成第一阶段的实验要求（写了总结报告，完成了lab0~lab5的实验），为此，晚了一些时间是可以的** 28 | 29 | #### 模块化的 rCore-Tutorial-v3 30 | 31 | 1. 项目标题：模块化的 rCore-Tutorial-v3 32 | 2. [模块化的 rCore-Tutorial-v3: GitHub Classroom](https://classroom.github.com/a/Oc792plB) 33 | 3. 项目描述：rCore-Tutorial-v3 是一套简洁，易于上手的教程，但是目前代码将不同章节用分支隔离的组织形式导致前一章实验的成果很难迁移到后一章，且若要修改某一章的实现，就需要手动同步到后续所有章节。我们希望能发挥 Rust 语言 workspace/crates/traits 的先进设计理念，重构并形成模块化rCore-Tutorial，将学习时对仓库的操作变为以下形式： 34 | 35 | | 操作 | 使用 git 分支 | 使用 crate 36 | | ------------ | ------------------- | --------------- 37 | | 学习另一个章节 | 切换分支 | 修改 workspace（即切换相关 crates） 38 | | 做课后实验 | 切换到 lab 分支写代码 | 封装一个 crate 加入 workspace 39 | 40 | 这样操作系统将以模块化/Traits的形式呈现给同学，同学按照模块化/Traits实现的方法来完成实验。实验的内容也可随之灵活调整。 41 | 42 | 4. 项目难度：中（适合完成了lab1-5，熟悉 Rust workspace/crates/traits 的同学） 43 | 5. 项目社区导师：杨德睿 github id:YdrMaster weichat id: ydrdwx ； 许善朴 github id: xushanpu123 weichat id: bitmeet520 44 | 6. 项目产出要求： 45 | 46 | 项目应该将现有的 rCore-Tutorial-v3 变得模块化。形式包括： 47 | - 章节模块化：所有章节不再被 git 分支隔离开，而是只有逻辑上的隔离关系，后一章节能够以依赖库的形式继承前一章节的成果 48 | - 实现模块化：能在所有章节中复用的代码形成单独的 crate 甚至 package，crates之间在调用方面有层次依赖关系, crates的粒度尽量小。 49 | - 系统调用接口模块化：系统调用的分发封装到一个 crate。使得添加系统调用的模式不是为某个 match 增加分支，而是实现一个分发库要求的 trait 并将实例传递给分发库 50 | 51 | 7. 相关的开源软件仓库列表： 52 | - （OS的目标不同，但在OS的设计上有部分内容与此相近） 53 | 54 | Theseus is a modern OS written from scratch in Rust that explores 𝐢𝐧𝐭𝐫𝐚𝐥𝐢𝐧𝐠𝐮𝐚𝐥 𝐝𝐞𝐬𝐢𝐠𝐧, novel OS structure, and state management. It strives to close the semantic gap between compiler and hardware to maximally leverage the power of language safety, and thus shift OS responsibilities like resource management into the compiler. 55 | 56 | ### rCore-Tutorial-v3 进一步进阶/扩展 57 | 58 | 1. 项目标题：rCore-Tutorial-v3 进一步扩展 59 | 2. [rCore-Tutorial-v3 进一步扩展 rCore-Tutorial-v3: GitHub Classroom](https://classroom.github.com/a/bAc-5319) 60 | 3. 项目描述：rCore-Tutorial-v3 的一个重要目标是以简洁的设计实现对应到操作系统的核心知识点上，所以还有很多可以扩展的地方。我们希望通过设计一个一个相对独立的实验，来展现操作系统的核心设计思想，在操作系统实现与操作系统原理之间建立桥梁。学生自己设计实现新OS功能后，其系统能力也随之提高。简言之：做多，错多，收获多 61 | 4. 项目难度：低/中 （适合完成了lab1-5，且希望能够一小步一小步地继续提升自己OS编程能力/系统能力的同学） 62 | 5. 项目社区导师：陈渝 github id: chyyuu weichat id: chyyuu 63 | 6. 项目社区导师：吴一凡 github id: wyfcyx weichat id: yifanwu1998 64 | 7. 项目社区导师：许善朴 github id: xushanpu123 weichat id: bitmeet520 65 | 8. 项目社区导师：杨德睿 github id:YdrMaster weichat id: ydrdwx 66 | 9. 项目社区导师：陈乐 github id: yuoo655 weichat id: Endagorion_ 67 | 10. 项目产出要求： 68 | 69 | - 补充完善 rCore-Tutorial-v3 70 | 71 | 11. 项目技术要求： 72 | 73 | - 具备一定的 Rust 语言基础，能看懂并模仿现有代码即可 74 | - 熟悉操作系统原理与简易实现 75 | - 具有基础英文阅读和写作能力 76 | 77 | 12. 相关的开源软件仓库列表： 78 | 79 | - 80 | - 81 | 82 | 13. 一个月可行的进阶步骤（当然也是一种挑战） 83 | - 选择1：内核支持中断响应 --> 内核支持 读取设备树，支持virtio外设，支持串口外设 （rcore tutorial v3的ch9已经完成） --> 内核支持多核结构 --> 内核支持Linux syscall（即支持Linux应用） 84 | - 选择2：内核支持中断响应 --> 内核支持 读取设备树，支持virtio外设，支持串口外设 --> 图形界面支持 （rcore tutorial v3的ch9已经完成） --> 改进图形界面支持 85 | - 选择3：内核支持中断响应 --> 内核支持 读取设备树，支持virtio外设，支持串口外设 （rcore tutorial v3的ch9已经完成） --> 实现对TUI界面的支持（即可以在字符界面实现窗口界面和各种基于TUI界面的游戏） 86 | 87 | 选择2/3的OS参考 88 | 89 | - [带TUI界面的Lateral OS](https://github.com/carterisonline/lateral) 90 | - [有snake/2048图形界面游戏的SnakeOS](https://github.com/trusch/snakeos) 91 | 92 | ### 操作系统课程的有趣大实验 93 | 94 | 1. 项目标题：操作系统课程的有趣大实验 95 | 2. 项目描述：操作系统课程的大实验的重要目标基于学生兴趣来开展各种操作系统技术的探索，拓展学生的视野，培养未来操作系统人才。 96 | 3. 项目难度：中/高 （适合完成了lab1-5，并希望能够较快进入更实际一些的OS能力训练或做OS方向研究的同学） 97 | 4. 项目社区导师：向勇 github id: xyongcn weichat id: xyongcn 98 | 5. 项目产出要求： 99 | - 各种大实验的设计与实现 100 | 101 | 6. 项目技术要求： 102 | - 具备一定的 Rust 语言基础，能看懂并模仿现有代码即可 103 | - 熟悉操作系统原理与简易实现 104 | - 具有基础英文阅读和写作能力 105 | 106 | 7. 2022春季OS课相关大实验的开源软件仓库列表(鼓励进一步改进和扩展)： 107 | 108 | - [类似ebpf的rcore trace](https://github.com/latte-c/rvjit) 109 | - [硬件级用户态中断模拟与系统软件支持](https://github.com/OS-F-4/usr-intr) 110 | - [支持异步协程的zCore](https://github.com/orgs/OSLab-zCore/) 111 | - [用rust重新实现FreeRTOS](https://github.com/LDYang694/RFREERTOS) 112 | - [用rust重新实现Linux的KVM](https://github.com/KaitoD/linux) 113 | - [基于x86_64的rCore-Tutorial-v3](https://github.com/rcore-os/rCore-Tutorial-v3-x86_64) 114 | - [基于AARCH64的rCore-Tutorial-v3](https://github.com/rcore-os/rCore-Tutorial-v3-arm64) 115 | - rCore-Tutorial-v3/zCore直接支持Rust std标准库：已完成的本科毕设，有初步结果 116 | 117 | ### 异步操作系统 118 | 119 | 1. 项目标题：异步操作系统设计和完善 120 | 2. 项目描述：在RISC-V平台上设计并实现一个基于Rust语言的异步操作系统。最终目标是，利用Rust语言和开源工具链的特征，在操作系统内核中实现细粒度的并发安全、模块化和可定制特征；利用Rust语言的异步机制，优化操作系统内核的并发性能；向应用程序提供的异步系统调用接口，优化操作系统的系统调用访问性能；结合LLVM中Rust语言编译器的异步支持技术，完善操作系统的进程、线程和协程概念，统一进程、线程和协程的调度机制；利用RISC-V平台的用户态中断技术，优化操作系统的信号和进程通信性能；开发原型系统，设计用户态测试用例库和操作系统动态分析跟踪工具，对异步操作系统的特征进行定量性的评估。 121 | 3. 项目难度：中/高 （适合完成了lab1-5，并希望能够较快进入更实际一些的OS能力训练或做OS方向研究的同学） 122 | 4. 项目社区导师：向勇 github id: xyongcn weichat id: xyongcn 123 | 5. 项目产出要求： 124 | - 参与正在进行的异步操作系统开发项目，提供力所能及改进和完善； 125 | - 针对异步操作系统中还没有开工的模块，提供初始的参考实现； 126 | 6. 项目技术要求： 127 | - 具备一定的 Rust 语言基础，能看懂并模仿现有代码即可 128 | - 熟悉操作系统原理与简易实现 129 | - 具有基础英文阅读和写作能力 130 | 131 | 7. 已有相关工作： 132 | 133 | - [异步操作系统设计](https://github.com/async-kernel/documents/blob/main/design/design.md) 134 | - 用户态中断扩展 135 | - 尤予阳，[软硬协同的用户态中断](https://gallium70.github.io/rv-n-ext-impl/intro.html)：RISC-V的用户态中断规范建议； 136 | - [软硬协同的用户态中断机制研究](https://github.com/Gallium70/final-project/blob/master/论文.pdf)：本科毕设论文； 137 | - 王之栋、项晨东、孙迅，[基于Intel x86用户态中断的高效进程间通信](https://github.com/OS-F-4/usr-intr/blob/main/ppt/2022-6-11.pptx)：Intel用户态中断的QEMU支持、基于用户态中断的异步系统调用实现 138 | - 内核模块的异步通信框架： 139 | - 吴一凡，[Async-modules extension of zCore](https://github.com/wyfcyx/zCore/tree/async-modules)：异步模块间的通信框架实现； 140 | - 用户态的异步支持库： 141 | - 车春池，[基于Rust的io-uring实现](https://github.com/SKTT1Ryze/Graduation2022/releases/download/v0.1.0/thesis.pdf)：Rust和C++的异步支持库，本科毕设论文； 142 | - 异步操作系统调度 143 | - 车春池、蒋周奇：共享调度器 #如何运行 144 | - 刘松铭、于子淳：[zCore多核异步调度器](https://github.com/OSLab-zCore/OSLab-Docs) 145 | - 王文智：[线程与协程的统一调度](https://github.com/AmoyCherry/UnifieldScheduler/blob/02f3d17cafd6b3ca4091df6a47798f67a44e7788/%E5%BC%82%E6%AD%A5OS%E8%AE%BE%E8%AE%A1%E6%96%87%E6%A1%A3.md) 146 | 147 | ### zCore 的文档与单元测试完善 148 | 149 | 1. 项目标题：zCore 的文档与单元测试完善 150 | 2. [zCore 的文档与单元测试完善](https://github.com/LearningOS/zCore)（注：由于有Github LFS，不能设置为classroom） 151 | 3. 项目描述：zCore 是用 Rust 实现的支持协程/异步等新机制的操作系统，目前zCore的实现已经初步支持 x86_64/RISC-V 64/AArch64。然而，随着后期开发进程的加快，大量代码缺少文档描述，并且没有实现单元测试，只能在 QEMU 中运行用户程序以检验代码正确性。本项目的目标是完善 zCore 的文档及单元测试，使其成为一个高质量的 Rust 社区项目。 152 | 4. 项目难度：低 （适合完成了lab1-5，并希望在OS领域找到一份测试/研发工作，或提升软件工程能力的同学） 153 | 5. 项目社区导师：石振兴 github id: shzhxh weichat id: szx-bj 154 | 6. 项目社区导师：董峰 github id: workerwork weichat id: Mr_dong-feng 155 | 7. 项目产出要求： 156 | - 补充完善 zCore 各模块的代码文档。 157 | 158 | 目标是通过 `#![deny(missing_docs)]` 编译，并且能够让开发者通过阅读文档，快速理解 zCore 的代码结构和各部分功能。 159 | - 参考 Fuchsia 官方文档及测试代码，为 zCore 中的内核对象补充单元测试。 160 | 161 | 目标让 `zircon-object` 模块的测试覆盖率提高到 90% 以上。 162 | - （可选）在 CI 中支持运行集成测试。 163 | 目标是最大化整体的测试覆盖率。 164 | - （可选）在zCore中添加zircon/linux的syscall。 165 | 目标：完善添加zCore内核功能，让zCore通过更多的zircon tests(基于zircon的coretest)或Linux tests（基于musl libc的libc test）或相关应用 166 | 167 | 8. 项目技术要求： 168 | - 具备一定的 Rust 语言基础，能看懂并模仿现有代码即可 169 | - 熟悉操作系统原理与简易实现 170 | - 具有基础英文阅读和写作能力 171 | 9. 相关的开源软件仓库列表： 172 | - （zCore 仓库） 173 | - （zCore 代码文档） 174 | - （Zircon 官方文档） 175 | 176 | ### zCore 的星光/SiFive/树莓派等开发板和外设支持 177 | 178 | 1. 项目标题：zCore 的星光/SiFive开发板支持 179 | 2. [zCore 的星光/SiFive开发板支持:项目模板](https://github.com/LearningOS/zCore)（注：由于有Github LFS，不能设置为classroom） 180 | 3. 项目描述：zCore 是用 Rust 实现的支持协程/异步等新机制的操作系统，目前zCore的实现已经初步支持 x86_64/RISC-V 64/AArch64。zCore需要继续完善相关驱动和系统调用。 181 | 4. 项目难度：中（适合完成了lab1-5，并希望在系统类企业找到一份OS底层研发工作，或提升软件工程能力的同学） 182 | 5. 项目社区导师：肖络元 github id: shzhxh weichat id: xiaoxiaoluckyard 183 | 6. 项目社区导师：杨德睿 github id:YdrMaster weichat id: ydrdwx 184 | 7. 项目产出要求： 185 | - 能够在某开发板上比较稳定地运行 zCore 186 | - （可选）能够在 Linux 系统上运行 zCore libos 187 | 这个相对比较简单，因为基于 Linux host OS，不会涉及太多指令级别的改动。可以作为入门练手。 188 | 189 | 8. 项目技术要求： 190 | - 熟悉 Rust 语言 191 | - 熟悉 RISC-V64 指令集，或做过其它平台的底层移植工作 192 | - 熟悉K210的开发经验 193 | 9. 相关的开源软件仓库列表： 194 | - （zCore 仓库） 195 | - （rCore 仓库，支持RISC-V） 196 | - 197 | - 198 | 199 | ### rCore 到 zCore 的功能迁移 200 | 201 | 1. 项目标题：rCore 到 zCore 的功能迁移 202 | 2. [rCore 到 zCore 的功能迁移:项目模板](https://github.com/LearningOS/zCore)（注：由于有Github LFS，不能设置为classroom） 203 | 3. 项目描述：rCore 是用 Rust 语言实现的兼容 Linux 内核。它支持四种指令集，能够运行比较丰富的应用程序。但是随着时间的积累，rCore 的代码越堆越多，很多内部实现缺乏推敲，需要优化和重构。后来我们从头开始实现了 zCore 项目，采用了更加清晰的分层结构，同时复用 Zircon 微内核的内核对象实现了 Linux 内核的部分功能（如内存管理和进程管理）。目前 zCore 中的 linux 模块已经能够运行基础的 Busybox 等小程序，但仍有大量原本 rCore 支持的功能没有实现。本项目希望将 rCore 的功能迁移到 zCore 当中，并借此机会进行重构。其中一些代码可以直接搬过来，剩下的可能需要调整适配（例如涉及到 async），还有一些可以直接基于 Zircon 内核对象进行实现（例如 epoll）。 204 | 4. 项目难度：中（适合完成了lab1-5，并希望在系统类企业找到一份OS底层研发工作，或提升软件工程能力的同学） 205 | 5. 项目社区导师：董峰 github id: workerwork weichat id: Mr_dong-feng 206 | 6. 项目社区导师：陈乐 github id: yuoo655 weichat id: Endagorion_ 207 | 7. 项目产出要求： 208 | - 能够在 zCore 上运行 rCore 支持的 Linux 程序：GCC，Nginx，Rustc 等 209 | - 对新迁移过来的代码，要求补充代码文档和必要的单元测试 210 | 8. 项目技术要求： 211 | - 熟悉 Rust 语言 212 | - 熟悉 Linux 系统调用 213 | 9. 相关的开源软件仓库列表： 214 | - （zCore 仓库） 215 | - （rCore 仓库） 216 | 217 | ### 改进 RVM 虚拟机 218 | 219 | 1. 项目标题：改进 RVM 虚拟机 220 | 2. 项目描述：RVM 是在 rCore 中实现的一个简易 Hypervisor。目前只支持 x86_64，利用 VT-x 硬件虚拟化技术，已经能够在 rCore 上运行 uCore（C 语言版本的 x86 教学操作系统）。我们希望继续完善 RVM，使其能够支持运行完整的 Linux 系统。此外，还希望将 RVM 从 rCore 中分离出来，作为独立项目。未来不但能够接入 rCore、zCore，还能作为 Linux 内核模块运行。 221 | 3. 项目难度：高 （适合完成了lab1-5，并希望能够较快进入更实际一些的OS能力训练或做OS方向研究的同学） 222 | 4. 项目社区导师：贾越凯 223 | 5. 导师联系方式：github id: equation314 weichat id: equation314 224 | 6. 项目产出要求： 225 | - 将 RVM 从 rCore 中分离出来作为独立项目。 226 | - 能够在 rCore RVM 上运行完整的 Linux 系统。 227 | - （可选）能够把 RVM 作为一个 Linux module，在 Linux 启动后以 kernel module 的形式加载运行，然后把自己设定成 host 态，把 Linux 设定成 guest 态。 228 | 229 | 这个有参考，即基于 C 语言实现的 Jailhouse 和 Blue Pill 230 | - （可选）支持 ARM64 的硬件虚拟化，能够在树莓派上运行虚拟机。 231 | 7. 项目技术要求： 232 | - 熟悉 Rust 语言 233 | - 熟悉虚拟化技术 234 | - 熟悉 x86_64 指令集，理解 VMX 的原理和基于 VMX 的开发 235 | 8. 相关的开源软件仓库列表： 236 | - （rCore 仓库） 237 | - （正在开发中的包含 RVM 的 rCore 仓库） 238 | - （树莓派上的 Rust OS 教程） 239 | - （基于 Linux module 的 Hypervisor） 240 | 241 | ### 面向 Rust-based OS的vscode 动态调试工具 242 | 243 | 1. 项目标题：面向 Rust-based OS的vscode 动态调试工具 244 | 2. 项目描述：方便的源代码级调试工具，对监测程序运行状态和理解程序的逻辑十分重要；高效的Rust语言跟踪能力，是Rust操作系统内核开发的必要工具，对基于Rust的操作系统教学和实验很有帮助。然而现有RISC-V、Rust实验环境搭建成本高，上手难度大，不利于学习与开发工作。本项目拟实现一种基于网页访问的在线实验系统，提供方便、高效的手段实现在QEMU和RISC-V开发板上的Rust教学操作系统的源代码调试。 245 | 3. 项目难度：中（适合完成了lab1-5，熟悉typescript, 了解vscode plugin，并希望能够较快进入更实际一些的OS能力训练或做OS方向研究的同学） 246 | 4. 项目社区导师： 247 | 陈志扬：github id: chenzhiy2001 weichat id: untilthedayibecome 248 | 吴竞邦：github id: wujingbang weichat id: wujingb33 249 | 250 | 5. . 项目产出要求： 251 | - 能够在vscode上动态调试Rust-based OS && APP in OS(比如rcore，zcore等) 252 | - 形成vscode插件 253 | - 提供使用说明和设计实现文档 254 | 6. 项目技术要求： 255 | - 熟悉 vscode 插件开发 256 | - 了解 VS Code的 Debug Adapter 协议 257 | - 了解QEMU 中的 gdbserver 与 gdb之间的通信协议 258 | - 熟悉 typescript开发 259 | 7. 相关的开源软件仓库列表： 260 | - 261 | 262 | > 欢迎进入第二阶段的同学提出自己感兴趣的题目，并尽快联系助教或老师进行立项。 263 | --------------------------------------------------------------------------------