{{ tag.name }}
28 |-
29 | {% for page in tag.pages %}
30 |
- 31 | {{ page.title }} 32 | 33 | {% endfor %} 34 |
9 | {# Navigation #}
10 | AOSC {{ config.title }}
11 | contents with tag
12 | {{ term.name }}
13 |
14 | {# Buttons #}
15 |
20 |
16 | Also available in:
17 | zh_CN
18 |
19 | Pages with tag: {{ term.name }}
21 | 22 | {# Acutal pages #} 23 |-
24 | {% for page in term.pages %}
25 |
- 26 | {{ page.title }} 27 | 28 | {% endfor %} 29 |
10 | {# Navigation #}
11 | All tags in
12 | AOSC/{{ config.title }}
13 |
14 | {% endblock header %}
15 |
16 | {% block main %}
17 |
23 |
24 | {# Acutal tags #}
25 |
15 | {% if source.translations | length > 1 %}
16 | {{ trans(key="also_available_in", lang=lang) }}
17 | {% for t in source.translations %}
18 | {% if t.lang != lang %}
19 | {{ trans(key=t.lang, lang=lang) }}
20 | {% endif %}
21 | {% endfor %}
22 | {% endif %}
23 |
24 | {% endmacro language_select %}
25 |
26 |
--------------------------------------------------------------------------------
/content/aosc-os/_index.md:
--------------------------------------------------------------------------------
1 | +++
2 | title = "AOSC OS"
3 | description = "It just works™"
4 | insert_anchor_links = "right"
5 | +++
6 |
7 | AOSC OS is our main project at the community, a general-purposed Linux Distribution designed with simplicity, localisation, software compatibility, device sustainability, and gradual refinement in mind.
8 |
9 | - [Is AOSC OS Right for Me?](@/aosc-os/is-aosc-os-right-for-me.md)
10 | - [AOSC OS and AOSC OS/Retro Architecture Support Matrix](@/aosc-os/information/arch-support.md)
11 | - [Installation Guides](@/aosc-os/installation/_index.md)
12 |
13 | If you are wondering what to do with your ancient device, we got you covered! Checkout [AOSC OS/Retro](@/aosc-os/retro/intro.md) project, which aims to provide a modern Linux experience on some retro devices.
14 |
15 | Other useful resources:
16 |
17 | - [AOSC OS Security Advisories (AOSA)](@/aosc-os/aosa/_index.md) covers how AOSC handles security vulnerabilities and contains past security advisories.
18 | - [Information](@/aosc-os/information/_index.md) covers some design choices and system information.
19 |
--------------------------------------------------------------------------------
/content/community/crowdsourcing/aoscc-2023-funds.md:
--------------------------------------------------------------------------------
1 | +++
2 | title = "[COMPLETE] AOSCC 2023 Budgets"
3 | draft = false
4 | +++
5 |
6 | # Rationale
7 |
8 | After four long years, AOSCC 2023 is finally returning in-person. To procure souvenirs and lucky draw items, community contributors have or will spend private funds. This crowdsourcing campaign aims to reimburse these spendings.
9 |
10 | # Budget
11 |
12 | Private funds were spent on the following items (all items are in CNY):
13 |
14 | - Lucky Draw: IBM ThinkPad X41, laptops and parts - CNY 1,927
15 | - AOSCC 2023 Sticker Packs, two pages, totalling 200 copies - CNY 1,200
16 | - AOSCC 2023 Tote Bags, totalling 120 pieces - CNY 1,440
17 | - Free sourvenir T-Shirts for guest speakers - CNY 524
18 |
19 | Totals: CNY 5,091
20 |
21 | # Timeline
22 |
23 | All merchandises have been purchased and this campaign is used for reimbursement.
24 |
25 | # Participants
26 |
27 | - Jack Lee：IBM ThinkPad X41 procurement and refurbishment
28 | - Vincent Liang：AOSCC 2023 Sticker Pack printing
29 | - Mingcong Bai: Tote bags and shirts procurement
30 |
--------------------------------------------------------------------------------
/content/community/crowdsourcing/aoscc-2021-sticker-set.md:
--------------------------------------------------------------------------------
1 | +++
2 | title = "[COMPLETE] Printing the AOSCC 2021 Sticker Set"
3 | +++
4 |
5 | This is a proposal to crowdsource the necessary funds to print the AOSCC 2021 Sticker Set.
6 |
7 | # Rationale
8 |
9 | Per community tradition, we have created a new sticker set that includes community logos, memes, and mascots - a set of three pages.
10 |
11 | Due to material change (from paper to PVC to improve quality and durability) and supply chain issues, the price to print this year's community sticker set rised significantly. Stickers will be distributed free-of-cost by request, recipients will pay postage.
12 |
13 | # Budget
14 |
15 | + Sticker Set (CNY 1800)
16 | - Three pages (CNY 600/page)
17 |
18 | # Timeline
19 |
20 | - December 2021: Crowdsourcing.
21 | - End-of-Year 2021: Sticker printing and distribution.
22 |
23 | # Donation Methods
24 |
25 | - Contact Mingcong Bai (see below).
26 | - Via [GitHub Sponsors](https://github.com/sponsors/AOSC-Dev).
27 |
28 | # Contacts
29 |
30 | - Mingcong Bai 
18 |
19 | 如果你正在运行不支持 Microsoft Store 的 Windows Server 或长期服务 (LTSC) 桌面操作系统 SKU，或者你的公司网络策略和/或管理员不允许在你的环境中使用 Microsoft Store，你可以从 [GitHub Releases](https://github.com/AOSC-Dev/AOSCOSLauncher/releases/latest) 获取适用于你的体系结构的 AOSC OS on WSL。从压缩的文件夹提取全部文件，然后运行其中的 Install.ps1。
20 |
21 | # 配置 AOSC OS
22 |
23 | 请参阅[为新的 Linux 分发版创建用户帐户和密码](https://docs.microsoft.com/zh-cn/windows/wsl/user-support)，AOSC OS 也使用 apt 管理软件包。
24 |
--------------------------------------------------------------------------------
/content/community/aoscc/2019-hotel.md:
--------------------------------------------------------------------------------
1 | +++
2 | title = "AOSCC 2019: Hotel"
3 | description = ""
4 | date = 2020-05-04T03:35:04.386Z
5 | [taxonomies]
6 | tags = ["events"]
7 | +++
8 |
9 | # 如何提名
10 |
11 | 请在下方《提名列表》章节仿照第一个提案那样创建。
12 |
13 | 交通耗时包含公共交通、驾车两种方式的耗时，以 slash 隔开。均以高德地图为准，单位为分钟，隐含单位。
14 |
15 | # 提名列表
16 |
17 | | 名称 | 平均每晚价格 | 含早餐 | 前往会场交通耗时 | 前往合肥站交通耗时 | 前往合肥南站交通耗时 | 参考链接 | 提名者 |
18 | | --- | --- | --- | --- | --- | --- | --- | --- |
19 | | 合肥中心智选假日酒店 | 264 | True | 28 / 13 | 30 / 12 | 34 / 16 | [link](https://www.ihg.com.cn/holidayinnexpress/hotels/cn/zh/hefei/hfeex/hoteldetail) | @neruthes |
20 |
21 | # 提名结果
22 | 截至 2019 年 5 月 25 日 0:00（UTC+8），只出现了一个提名，所以自动成为钦定选项。
23 |
24 | # AOSCC-2019 合肥中心智选假日酒店入住指南
25 |
26 | 请 07/11、07/12 到达的入住人分别持 46168284、25456725 两个预订号到前台办理入住。
27 |
28 | 在前台办理入住时，前台应持签到确认表，请在自己那一项后方的 Checkbox 一栏打勾（✓）。
29 |
30 | 对酒店方面提供的接待说明如下:
31 |
32 | > 由于每位入住人到店时间均可能有所不同并且存在拼房，原则上前台应按照到店顺序安排入住人到尽可能集中的客房；例如，第 4 位入住人安排在第 2 间客房，第 5 位入住人安排在第 3 间客房；但是，如果双床房入住人列表中成对到店的入住人要求安排在同一间客房，并且在订单范围内仍有未分配的客房，前台应安排一间尚未分配的客房。在客房位置较为分散时，这个策略特别有意义。
33 |
34 | 请 07/11 到达的入住人特别注意，如果到达时间早于 18:00，那么 @Neruthes 可能还没到酒店。这种情况下，酒店前台会要求入住人在银行卡预授权、现金、支付宝、微信支付等支付手段中选择其中之一来支付一定的「押金」。这些「押金」将会在 @Neruthes 到酒店后全部返还，换成 @Neruthes 的信用卡的预授权。
35 |
--------------------------------------------------------------------------------
/content/_index.zh.md:
--------------------------------------------------------------------------------
1 | +++
2 | title = "AOSC Wiki"
3 | insert_anchor_links = "right"
4 | +++
5 |
6 | 欢迎来到安同开源社区（AOSC）维基！
7 |
8 | > 这里是面向用户与开发者的所有文档、信息和指南的汇总。请根据以下的章节和链接访问最常用的信息，并善用搜索功能。
9 |
10 | 如果您愿意帮助我们，欢迎您为我们的 [AOSC-Dev/wiki](https://github.com/AOSC-Dev/wiki) 储存库的 `master` 分支贡献提交。为了提高效率，在贡献前烦请阅读 [Meta](@/meta/_index.zh.md) 板块的 [维基维护指南](@/meta/wiki_maintenance_guide.zh.md)。
11 |
12 | {% section(name="AOSC OS") %}
13 | [AOSC OS 适合我吗？](/zh/aosc-os/is-aosc-os-right-for-me)
14 | 找到最适合您的（或者反之）
15 |
16 | [安装指南](/zh/aosc-os/installation/)
17 | 在您的机器上安装 AOSC OS
18 |
19 | [AOSC OS/Retro](/zh/aosc-os/retro/intro)
20 | 照顾您的旧式设备和低性能设备
21 |
22 | [应用程序](/zh/software/)
23 | 了解如何使用 AOSC OS 为您提供的各式应用
24 | {% end %}
25 |
26 |
27 | {% section(name="社区") %}
28 | [AOSC 人际关系准则（长期征求意见稿）](/zh/community/guidelines/)
29 | 心里装着别人才是真正的快乐
30 |
31 | [AOSC：我们的历史](/zh/community/history)
32 | 我们自 2011 年 11 月以来的历史
33 | {% end %}
34 |
35 |
36 | {% section(name="开发者") %}
37 | [为 AOSC OS 打包](/zh/developer/packaging/)
38 | 将您最喜欢的应用程序添加到 AOSC OS 软件仓库
39 |
40 | [自动化](/zh/developer/automation/)
41 | 正在推进中的 AOSC OS 自动化维护和质量保障工作
42 | {% end %}
43 |
44 | {% section(name="基础设施") %}
45 | [打包服务器](/developer/infrastructure/buildbots/)
46 | 为 AOSC OS 维护者准备的公用打包服务器
47 | {% end %}
48 |
--------------------------------------------------------------------------------
/content/community/history.md:
--------------------------------------------------------------------------------
1 | +++
2 | title = "AOSC: Our History"
3 | description = "A Brief History of the Anthon Open Source Community"
4 | date = 2020-05-04T03:35:15.633Z
5 | [taxonomies]
6 | tags = ["community"]
7 | +++
8 |
9 | AOSC was originally founded as Anthon.Dev (Anthon Dev. Team) by Mingcong Bai and his two classmates in late 2011. Following a year of mismanagement, the team was disbanded and refactored as the Anthon Open Source Community in late 2012.
10 |
11 | AOSC OS, the community's main project, was originally known as AnthonOS - an OpenSUSE derivative built with the now defunct SUSE Studio. The OS project was then remade as a Debian derivative focusing on a customised KDE 4 UI and CJK support.
12 |
13 | In 2014, with the help of Icenowy Zheng, developer of the Eastern Heart Linux distribution, the Anthon :Next project was established to rebuild the distribution from scratch. With the rebuild, AnthonOS was renamed as AOSC OS, and has become the general-purpose distribution as we know it today.
14 |
15 | In the following years, AOSC OS expanded its package repostory and scope of arcthitectural support. To this day, AOSC OS continues to diversify its software selection and device support, owing to our developer's dedication.
16 |
--------------------------------------------------------------------------------
/LICENSE:
--------------------------------------------------------------------------------
1 | MIT License
2 |
3 | Copyright (c) 2011-2020 Anthon Open Source Community
4 |
5 | For a list of contributors, see https://github.com/AOSC-Dev/wiki/graphs/contributors
6 |
7 | Permission is hereby granted, free of charge, to any person obtaining a copy
8 | of this software and associated documentation files (the "Software"), to deal
9 | in the Software without restriction, including without limitation the rights
10 | to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
11 | copies of the Software, and to permit persons to whom the Software is
12 | furnished to do so, subject to the following conditions:
13 |
14 | The above copyright notice and this permission notice shall be included in all
15 | copies or substantial portions of the Software.
16 |
17 | THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
18 | IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
19 | FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
20 | AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
21 | LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
22 | OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
23 | SOFTWARE.
24 |
--------------------------------------------------------------------------------
/content/community/crowdsourcing/loongson3-3b4000.zh.md:
--------------------------------------------------------------------------------
1 | +++
2 | title = "[众筹成功] 升级龙芯 3 移植用构建服务器"
3 | +++
4 |
5 | {% card(type="success") %}
6 | 众筹已完成，设备已转交至托管方。
7 | {% end %}
8 |
9 | 本文为众筹龙梦双路龙芯 3B4000 主板并组装服务器的计划。本服务器将辅佐当前的龙芯 3A4000 构建服务器 (Relay 23869)。
10 |
11 | # 导言
12 |
13 | 当前的 AOSC OS 龙芯 3 移植完全依靠一台 3A4000 构建服务器（龙梦 LX-1901）构建及测试软件包，但该服务器只有四个核心，其计算力远不足以进行日常的发行版维护。此外，因为这台服务器和 AMD64 及 AArch64 构建服务器的性能差异巨大，在构建软件包更新时也会造成计划上的困难。
14 |
15 | 本计划的主要目的是通过组装一台基于双路龙芯 3B4000 服务器提高龙芯 3 移植的计算力，因为双路 3B4000 服务器有八个核心，性能相对 3A4000 理论上可以翻倍。
16 |
17 | # 预算计划
18 |
19 | 计划从龙梦购买如下组件：
20 |
21 | + 龙梦 LX-2510 主板（11000 元）
22 | - 板载双路龙芯 3B4000 处理器。
23 | - 包含散热器。
24 | - **已筹资**，感谢 *MariaBombardier*，*weilinfox*，*LiangYongxiang*, *FlyGoat*, *HenryChen* 和几位匿名赞助者。
25 | + 2 × 16GB 内存（2 × 750 元）
26 | - 计划直接通过龙梦购买以确保兼容性
27 | - **已筹资**，感谢 *JeffBai*。
28 |
29 | （运费另计）
30 |
31 | 此外还需要如下组件，计划通过物品及资金募捐的形式收集：
32 |
33 | + 机箱
34 | - 需兼容 E-ATX 主板。
35 | + 电源
36 | - ATX 规范电源，约 500W 功率。
37 | - **已筹集**，感谢 *PegionFish*。
38 | + 存储
39 | - 优先考虑 NVMe 方案。
40 | - **已筹集**，感谢 *PegionFish*。
41 |
42 | # 日程计划
43 |
44 | - 2021 年 7 月：购置服务器及相关组件，简单测试并转交硬件维护者。
45 | - 2021 年 8 月：服务器上线并应用于发行版维护。
46 |
47 | # 参与者
48 |
49 | - Leo Shen {{ category }}
20 |-
21 | {% for subsection in section.subsections %}
22 | {% set section = get_section(path=subsection, metadata_only=true) %}
23 | {% if section.extra.software_category == category %}
24 |
- 25 | {{ section.title }} 26 | 27 | {% endif %} 28 | {% endfor %} 29 |
{{ type }}
18 |-
19 | {% for page in section.pages %}
20 | {% if page.extra.article_type == type %}
21 |
- 22 | {{ page.title }} 23 | 24 | {% endif %} 25 | {% endfor %} 26 |
18 |
19 | If you're running a Windows Server or Long-Term Servicing (LTSC) desktop OS SKU that doesn't support Microsoft Store, or your corporate network policies and/or admins to not permit Microsoft Store usage in your environment, you can get AOSC OS on WSL for your architecture from [GitHub Releases](https://github.com/AOSC-Dev/AOSCOSLauncher/releases/latest). Extract all files from the compressed folder, then run Install.ps1 in it.
20 |
21 | # Configure AOSC OS
22 |
23 | Please see [Create a user account and password for your new Linux distribution](https://docs.microsoft.com/en-us/windows/wsl/user-support), AOSC OS also uses apt to manage packages.
24 |
--------------------------------------------------------------------------------
/sass/_index.sass:
--------------------------------------------------------------------------------
1 | #grand-header
2 | display: flex
3 | align-item: center
4 | $grand-height: 3rem
5 | .logo
6 | height: $grand-height
7 | width: $grand-height
8 | .text
9 | font-size: $grand-height
10 | // Magic happens here
11 | display: inline
12 | position: relative
13 | bottom: 10%
14 | .slash
15 | position: relative
16 | bottom: 2%
17 | .logo-text
18 | //
19 | .description
20 | font-style: italic
21 | font-size: .5em
22 | @media screen and (max-width: $smallScreenWidth)
23 | $small-grand-height: 2.2rem
24 | .logo
25 | height: $small-grand-height
26 | width: $small-grand-height
27 | .text
28 | font-size: $small-grand-height
29 |
30 | .search-grand-header
31 | margin-top: .5rem
32 |
33 | .section
34 | margin: 1rem 0
35 | border-top: 2px solid grey
36 | padding-top: .3rem
37 | .marker
38 | position: absolute
39 | margin: 0
40 | padding-top: .3rem
41 | max-width: 9rem
42 |
43 | font-weight: 600
44 | font-size: 1.25em
45 | .content
46 | padding-left: 10rem
47 | padding-top: .4rem
48 | a
49 | display: block
50 | position: relative
51 | // Hack for Zola's Markdown renderer
52 | margin: 0
53 | left: -1rem
54 | p
55 | margin: 0 0 1rem 0
56 | padding-left: 1rem
57 | @media screen and (max-width: $smallScreenWidth)
58 | .marker
59 | position: relative
60 | max-width: 100%
61 | .content
62 | padding: .5rem 0
63 |
--------------------------------------------------------------------------------
/sass/_typography.sass:
--------------------------------------------------------------------------------
1 | body
2 | // Nerdy stuff
3 | text-rendering: optimizeLegibility
4 | font-feature-settings: 'liga' 1
5 | // Stupid Safari...
6 | text-size-adjust: none
7 |
8 | font-size: 1.1rem
9 | font-weight: 400
10 | line-height: 1.5
11 | hyphens: auto
12 |
13 | h1, h2, h3, h4, h5, h6
14 | font-family: $serifFonts
15 |
16 | h1
17 | font-size: 1.4em
18 |
19 | h2
20 | font-size: 1.25em
21 |
22 | h3
23 | font-size: 1.1em
24 |
25 | a
26 | transition-duration: .1s
27 | transition-property: background
28 | text-decoration: none
29 |
30 | // lists
31 | ul
32 | list-style-type: square
33 | li
34 | margin: .2rem 0
35 |
36 | blockquote
37 | margin: 0
38 | padding: .5rem 1.5rem
39 | border-left: 2px solid grey
40 | *
41 | margin: 0
42 |
43 | code
44 | font-family: $monospaceFonts
45 | font-size: .95em
46 |
47 | pre
48 | overflow-x: auto
49 | padding: 1rem
50 | line-height: 1.2
51 | code
52 | // So we can see non-colored text
53 | color: #c0c5ce
54 | background-color: transparent
55 |
56 | // Table formatting
57 | table
58 | display: block
59 | margin: .5rem 0
60 | max-width: 100%
61 | overflow-x: auto
62 | border-collapse: collapse
63 |
64 | th, td
65 | padding: .75rem
66 | min-width: 5em
67 | th
68 | border-width: 0 0 2px 0
69 | border-style: solid
70 | td
71 | border-width: 0 0 1px 0
72 | border-style: solid
73 |
74 | .footnote-definition
75 | .footnote-definition-label
76 | p
77 | display: inline
78 |
--------------------------------------------------------------------------------
/content/developer/minutes/20230819.md:
--------------------------------------------------------------------------------
1 | +++
2 | title = "Contributor Minutes on 2023-08-19"
3 | description = ""
4 | date = 2023-08-19
5 | [taxonomies]
6 | tags = ["minutes"]
7 | +++
8 |
9 | Agenda
10 | ======
11 |
12 | - [Omakase History/Undo Design](#omakase-history-undo-design)
13 | - [OpenSSL 3.1.1 Upgrade Testing](#openssl-3-1-1-upgrade-testing)
14 | - [Distro Review: Ubuntu 23.04](#distro-review-ubuntu-23-04)
15 | - [Distro Review: openKylin 1.0](#distro-review-openkylin-1-0)
16 |
17 | Omakase History/Undo Design
18 | ===========================
19 |
20 | - Limit history items to 10 per page for oma history.
21 | - Localize all command history (Removed X, Installed Y, Upgraded system).
22 | - Drop `oma redo`, as it is quite pointless.
23 | - `oma history` interface.
24 | - Show a list of history items (dialoguer), as you do with `oma history undo`.
25 | - Selecting an item will "replay" the confirmation interface.
26 | - Redraw the confirmation interface on terminal after hitting Q.
27 |
28 | OpenSSL 3.1.1 Upgrade Testing
29 | =============================
30 |
31 | - Upgraded successfully on three personal machines.
32 | - Failed from the 20220922 Desktop release, to investigate or announce as errata.
33 |
34 | Distro Review: Ubuntu 23.04
35 | ===========================
36 |
37 | See our [survey notes on Ubuntu](/developer/notes/distro-survey-2023#ubuntu).
38 |
39 | Distro Review: openKylin 1.0
40 | ============================
41 |
42 | See our [survey notes on openKylin](/developer/notes/distro-survey-2023#openkylin).
--------------------------------------------------------------------------------
/content/developer/packaging/acbs/install.zh.md:
--------------------------------------------------------------------------------
1 | +++
2 | title = "ACBS - 安装"
3 | +++
4 |
5 | 安装
6 | ====
7 |
8 | 开始
9 | ----
10 |
11 | ACBS 可以被部署到任何您认为合适的目录中，只需执行 `acbs-build.py` 即可开始安装。在此之前，您需要先安装下文提到的 [依赖项](@/developer/packaging/acbs/install.zh.md#yi-lai-xiang)。您可能还需要为 ACBS 创建一个配置文件，虽然这不是必须的，但我们强烈建议您这么做。
12 |
13 | 如果您在使用 AOSC OS，可以使用软件包管理器安装 ACBS：
14 |
15 | sudo apt install acbs
16 |
17 | 你也可以在 GitHub 取得 ACBS 的源码：
23 |
24 | 强制依赖项：
25 |
26 |
27 |
28 | - Python 3 (\>= 3.6)：程序运行的基石。
29 | - GNU File (libmagic)：文件类型侦测。
30 | - LibArchive (bsdtar)：压缩文件管理。
31 | - GNU Wget or Aria2：源码包获取。
32 | - [Autobuild3](https://github.com/AOSC-Dev/autobuild3)：软件包构建。
33 |
34 |
35 |
36 | 可选依赖项[1]：
37 |
38 |
39 |
40 | - libmagic：侦测文件类型的 Python 模组。
41 | - pycryptodome：检查校验和的 Python 模组。
42 | - pexpect: 模拟 PTY 会话并将输出记录到文件中的 Python 模组。
43 |
44 | 初始化配置
45 | --------
46 |
47 | ACBS 使用了类 INI 配置文件以定义需要使用到的树，配置文件储存在 `/etc/acbs/forest.conf`。
48 |
49 | 下面是一个最简单的配置示例：
50 |
51 | [default]
52 | location = /usr/lib/acbs/repo
53 |
54 | 您可以在配置文件中使用变量：
55 |
56 | [vars]
57 | base = /mnt
58 |
59 | [default]
60 | location = ${vars:base}/aosc-os-abbs
61 |
62 | 默认情况下，ACBS 会构建 `[default]` 所定义软件包树中的软件包。您可以通过使用 `-t
11 | {# Navigation #}
12 | {% for ancestor in page.ancestors %}
13 | {% set section = get_section(path=ancestor, metadata_only=true) %}
14 | {{ section.title }}
15 | {% if not loop.last %}
16 | /
17 | {% else %}
18 | /
19 | .
20 | {% endif %}
21 | {% endfor %}
22 |
23 | {{ macros::language_select(source=page, lang=page.lang) }}
24 |
25 |
26 | {{ page.title }}
27 |{{ page.description }}
28 | {% endblock header %} 29 | 30 | {% block main %} 31 | 42 |
45 | {{ page.content | safe }}
46 |
47 | {% else %}
48 | {{ page.content | safe }}
49 | {% endif %}
50 |
7 | {% set search_msg = trans(key="search_placeholder", lang=lang) %}
8 |
9 |
13 | {% endblock search %}
14 |
15 | {% block header %}
16 |
10 |
11 |
12 |
17 |
25 | {% endblock header %}
26 |
27 | {% block main %}
28 | {{ section.content | safe }}
29 |
30 |
51 | {% endblock main %}
52 |
--------------------------------------------------------------------------------
/content/_index.md:
--------------------------------------------------------------------------------
1 | +++
2 | title = "AOSC Wiki"
3 | insert_anchor_links = "right"
4 | +++
5 |
6 | Welcome to the AOSC Community Wiki!
7 |
8 | > This is where all documentations, information, and guides will gather for users and developers alike. Please refer to the sections and links below for frequently accessed information, and use the search function to locate your specific topics.
9 |
10 | If you would like to improve this Wiki, please take a look at our [Wiki Maintenance Guide](@/meta/wiki_maintenance_guide.md) in the [AOSC Wiki Meta](@/meta/_index.md) section. Then, you may contribute your articles and edits to the `master` branch of our [AOSC-Dev/wiki](https://github.com/AOSC-Dev/wiki) repository.
11 |
12 | {% section(name="AOSC OS") %}
13 | [Is AOSC OS Right for Me?](/aosc-os/is-aosc-os-right-for-me)
14 | Finding Your Best Fit (or Not)
15 |
16 | [Installation Guides](/aosc-os/installation/)
17 | Installing AOSC OS on Your Device
18 |
19 | [AOSC OS/Retro](/aosc-os/retro/intro)
20 | Enjoying AOSC OS on Your Retro Devices
21 |
22 | [Software](/software/)
23 | Find information about how to use software provided by AOSC OS
24 | {% end %}
25 |
26 |
27 | {% section(name="Community") %}
28 | [AOSC Inter-Personal Guidelines (Long Term RFC)](/community/guidelines/)
29 | A Guide of References for Your Happy Stay
30 |
31 | [AOSC: Our History](/community/history)
32 | Our History Since November 2011
33 | {% end %}
34 |
35 |
36 | {% section(name="Developer") %}
37 | [Packaging for AOSC OS](/developer/packaging/)
38 | Adding your favourite application to AOSC OS's main repository
39 |
40 | [Automation](/developer/automation/)
41 | On-going effort to automate AOSC OS maintenance and quality assurance
42 | {% end %}
43 |
44 | {% section(name="Infrastructure") %}
45 | [Buildbots](/developer/infrastructure/buildbots/)
46 | Public Build Servers for AOSC OS Maintainers
47 | {% end %}
48 |
--------------------------------------------------------------------------------
/content/community/aoscc/2020.zh.md:
--------------------------------------------------------------------------------
1 | +++
2 | title = "AOSCC 2020"
3 | description = "AOSCC 2020 参会信息及日程安排"
4 | date = 2020-05-05T14:44:16.388Z
5 | [taxonomies]
6 | tags = ["events"]
7 | +++
8 |
9 | # 参会信息
10 |
11 | - 地点：社区 Discord #general 语音频道（[传送门](https://discord.gg/VYPHgt9)）
12 | - 日期：2020 年 9 月 26 - 27 日 (UTC +8)
13 | - 议程大致内容：
14 | - 社区项目进度报告及后续开发流程讨论
15 | - 社区项目作坊及培训活动
16 |
17 | # 日程
18 |
19 | 由于新冠疫情及其他因素影响，本年度 AOSCC 将于线上举行。除参与方式与往年不同外，AOSCC 2020 议程也将被缩短及简化，从三天缩短至两天。其中，第一天（26 日）的议程将于 UTC +8 时间 10 时开始，并于当晚适时结束（见下）；第二天以作坊 (Workshop) 活动为主，于早 10 时开始至下午六时结束。社区 Discord #general 语音频道将作为虚拟“会场”，所有议程按下述顺序进行：
20 |
21 | - 日程一律使用 24 小时格式表示时间。
22 | - 形式：
23 | - ACT: Activity（活动）
24 | - DIS: Discussion（讨论）
25 | - LEC: Lecture（讲演）
26 |
27 | ## 第一天（9 月 26 日）
28 |
29 | | 讲者 | 主题 | 时间 | 形式 |
30 | |----------------|---------------------------------------------------------|---------------|------|
31 | | 白铭骢 | 年度总结；AOSC OS：质量保障、代码风格及 Retro 项目 | 10:00 - 11:00 | LEC |
32 | | ^ | 社区吉祥物“安安”介绍会及鸣谢 | 11:00 - 11:30 | LEC |
33 | | Staph | AOSCNet 计划及与现存 Relay 架构的比较 | 11:30 - 12:00 | LEC |
34 | | ~ | 午饭、午休及提问时间 | 12:00 - 14:00 | ACT |
35 | | 刘子兴 | Pakreq/Iter Editor、ACBS/Autobuild3 及 Ciel-rs | 14:00 - 15:00 | LEC |
36 | | AOSC OS 维护组 | 讨论：主题制 (Topic-based) 迭代周期可行性及执行计划讨论 | 15:00 - [^1] | DIS |
37 |
38 | [^1]: 本议程持续至讨论结束为止。
39 |
40 | ## 第二天（9 月 27 日）
41 |
42 | | 讲者 | 标题 | 时间 | 形式 |
43 | |----------------|-------------------------------------------------|---------------|------|
44 | | AOSC OS 维护组 | AOSC OS 软件包构建及维护作坊 | 10:00 - 18:00 | ACT |
45 |
46 | ## 自由活动/消磨时间
47 |
48 | 如有不感兴趣的话题或有其他讨论需要进行，请前往社区 Discord 其他语音/文字频道。
49 |
--------------------------------------------------------------------------------
/content/aosc-os/installation/_index.md:
--------------------------------------------------------------------------------
1 | +++
2 | title = "Installing AOSC OS"
3 | +++
4 |
5 | This page lists installation guides for AOSC OS and AOSC OS/Retro, as well
6 | as system requirements to help you decide whether AOSC OS or AOSC OS/Retro
7 | is suitable for your device.
8 |
9 | LiveKit Installation
10 | ====================
11 |
12 | For the majority of x86-, PowerPC-, OpenPOWER- and Loongson-based desktop
13 | devices, as well as some AArch64-based devices, AOSC OS and AOSC OS/Retro
14 | could be easily installed with LiveKit. For details on how to make use of
15 | LiveKit, please refer to the following page for details.
16 |
17 | - [Using LiveKit](@/aosc-os/installation/livekit.md)
18 |
19 | Windows Subsystem for Linux
20 | ===========================
21 |
22 | For details on how to install AOSC OS on WSL, please refer to the following
23 | page for details.
24 |
25 | - [Installation/WSL](@/aosc-os/installation/wsl.md)
26 |
27 | Raw System Images
28 | =================
29 |
30 | For ARM and RISC-V devices which do not make use of (U)EFI boot facilities,
31 | you would want to use device-specific raw system images. The downloads for
32 | which are listed in our
33 | [Alternative Downloads](https://aosc.io/downloads/alternative/) page.
34 |
35 | For instructions on how to write these images, please refer to the
36 | following page for details.
37 |
38 | - [Writing System Images](@/aosc-os/installation/rawimgs.md)
39 |
40 | Manual Installation
41 | ===================
42 |
43 | For uncommon, advanced, and LiveKit-incompatible installation procedures,
44 | please refer to our library of
45 | [manual installation guides](/aosc-os/installation/manual/) for details.
46 |
47 | System Requirements
48 | ===================
49 |
50 | For a list of system requirements for AOSC OS and AOSC OS/Retro, please
51 | refer to our library of [system requirements](/aosc-os/installation/sysreq/)
52 | for details.
53 |
--------------------------------------------------------------------------------
/content/developer/minutes/20231119.md:
--------------------------------------------------------------------------------
1 | +++
2 | title = "Contributor Minutes on 2023-11-19"
3 | description = ""
4 | date = 2023-11-19
5 | [taxonomies]
6 | tags = ["minutes"]
7 | +++
8 |
9 | Topics
10 | ======
11 |
12 | Today's meeting focuses on various project planning and updates.
13 |
14 | - [Omakase 1.2 Testing](#omakase-1-2-testing)
15 | - [Omakase: Rename to oma?](#omakase-rename-to-oma)
16 |
17 | Omakase 1.2 Testing
18 | ===================
19 |
20 | - `oma --ailurus` does not display the Easter Egg correctly on smaller screens (< 116col).
21 | - Originally, there should be a 80 - 116col mode.
22 | - Omakase should have returned an error when terminal width is < 80col.
23 | - `oma install --sysroot` only functions with absolute path.
24 | - When running `oma refresh`, falsely resolved DNS addresses (such as `repo.o`) provided by ISP may cause Omakase returns a huge amount of empty lines.
25 | - AT&T redirects to dnserrorassis.att.net and Omakase attempted to read from the last file name on that URL.
26 |
27 | ```
28 | Notes from cth451:
29 |
30 | oma prints out filename component from effective URLs (may be different from one used in sources list due to server side redirects) upon download failure.
31 |
32 | ISPs engaging in non standard behavior may redirect NXDOMAIN into URLs that are too long to print on the terminal
33 | ```
34 |
35 |
36 | - Consider reverting d0c7e3b4d78efa8c05bb91cfbef0d0f0284892d8, which seem to have broken the progress bar layout again.
37 | - Possible upstream bug: pkexec cancellation returns code 127 (should be 1?).
38 | - Record failed Omakase operations with `[Failed]` (or something similar).
39 | - `oma download` does not return permission error "DUE TO" while attempting to overwrite .deb files created by root.
40 | - Or for any file operations in general.
41 |
42 | Omakase: Rename to oma?
43 | =======================
44 |
45 | Tabled as a trivial topic.
46 |
--------------------------------------------------------------------------------
/content/developer/deploykit-quirks.zh.md:
--------------------------------------------------------------------------------
1 | +++
2 | title = "DeployKit 机型规避数据格式"
3 | description = ""
4 | +++
5 |
6 | # 格式说明
7 |
8 | 规避配置使用 TOML 格式编写，内容如下：
9 |
10 | ```toml
11 | [model]
12 | # 两种匹配方式：
13 | #
14 | # - dmi：使用 DMI 信息进行匹配，此处指的是 modalias - 机型别名，一般足够判定
15 | # 机型级别的规避
16 | # - path：使用系统路径特征，尤其是 sysfs 虚拟文件系统中的文件特征进行判断
17 | type = [dmi|path]
18 |
19 | # 下列 path_pattern/dmi_pattern 不可同时指定
20 |
21 | # 匹配某个路径是否存在（一般为 sysfs 下的虚拟文件），可使用通配符
22 | #
23 | # 下例匹配 LEFI 设备
24 | #
25 | # 如指定 type = path 则此项必填
26 | path_pattern = "/sys/firmware/lefi"
27 |
28 | # 匹配 DMI 信息，使用 /sys/class/dmi/id/modalias 内容，可使用通配符
29 | #
30 | # 例如 Loongson XA61200 的 modalias 内容为：
31 | #
32 | # dmi:bvnLoongson:bvrLoongson-UDK2018-V4.0.05756-prestable202405:bd05/23/24145323:svnLoongson:pnLoongson-3A6000-HV-7A2000-1w-V0.1-EVB:pvrToBeFilledByO.E.M:rvnToBeFilledByO.E.M:rnLoongson-3A6000-HV-7A2000-1w-EVB-V1.21:rvrToBeFilledByO.E.M:cvnLoongson:ct3:cvrToBeFilledByO.E.M:skuToBeFilledByO.E.M:
33 | #
34 | # 此处可匹配板型：
35 | #
36 | # dmi:*svnLoongson:*pnLoongson-3A6000-HV-7A2000-1w-V0.1-EVB:*
37 | #
38 | # 抑或具体的主板版本
39 | #
40 | # dmi:*svnLoongson:*rnLoongson-3A6000-HV-7A2000-1w-EVB-V1.21:*
41 | #
42 | # 如指定 type = dmi 则此项必填
43 | dmi_pattern = "dmi:*svnLoongson:*rnLoongson-3A6000-HV-7A2000-1w-EVB-V1.21:*"
44 |
45 | [quirk]
46 | # 执行规避命令，预期命令已设置有执行位（如命令为脚本则须正确定义 shebang）
47 | command = "/usr/share/deploykit-backend/quirks/loongson-xa61200/quirk.bash"
48 |
49 | # 跳过某个或多个步骤，用于处理已知无法完成的步骤（数组形式）
50 | #
51 | # 查阅 deploykit-backend: install/src/lib.rs 中的 enum InstallationStage 即可
52 | # 获取步骤列表
53 | #
54 | # 此项选填；下例为跳过 GRUB 安装及 SSH 密钥生成
55 | skip_stages = ["InstallGrub", "GenerateSshKey"]
56 | ```
57 |
58 | # 文件摆放
59 |
60 | 规避配置应放置在 `/usr/share/deploykit-backend/quirks` 路径下，并以单级子目录进行分类：
61 |
62 | ```
63 | - /usr/share/deploykit-backend/quirks
64 | - ./loongson-xa61200 # 机型
65 | - ./quirk.toml # 规避配置
66 | ```
--------------------------------------------------------------------------------
/content/developer/minutes/20240602.md:
--------------------------------------------------------------------------------
1 | +++
2 | title = "Contributor Minutes on 2024-06-02"
3 | description = ""
4 | date = 2024-06-02
5 | [taxonomies]
6 | tags = ["minutes"]
7 | +++
8 |
9 | 软件包信息站需求讨论
10 | ===
11 |
12 | 当前[软件包信息站](https://packages.aosc.io/)服务不稳定且原维护者已失联，故计划重新实现
13 |
14 | 今日例会讨论了关于重新实现时的特性及服务调整：
15 |
16 | - 需要排除的功能
17 | - 软件包质量监测页面
18 | - 面向开发者的功能，如 Topic 信息
19 | - 需要简化的功能
20 | - 将 Changelog 功能简化为 GitHub 历史页
21 | - Section 信息改为从 Packages 读取
22 | - 架构间软件包版本比较（只拉取最新的相对版本）
23 | - 服务调整
24 | - 将信息站服务直接部署在新的香港源服务器上
25 |
26 | p-vector-rs Acquire-by-Hash
27 | ===
28 |
29 | - 已审阅代码，但部分代码需要重新调整
30 | - 可考虑使用非官方（如柴天浩的）源进行初步测试，避免服务事故
31 |
32 | autopr 白名单调研
33 | ===
34 |
35 | - 初步确立如下白名单准入规则
36 | - 软件包足够简单
37 | - 软件包无版本管制（如 KDE 暂时不更新到 6）
38 | - 软件包非运行时性质（避免潜在重构需求）
39 | - 目前完成 `a` 与 `b` 开头软件包的登记，其余后续完成
40 |
41 | AOSCC 2024 工作组第二次例会
42 | ===
43 |
44 | 报名表
45 | ---
46 |
47 | - 开始制作 AOSCC 2024 登记表
48 | - 实名登记（共享给校方安保部门及联系人：Ciel 和白铭骢）
49 | - 法定姓名
50 | - 手机号（用于收取门禁短信）
51 | - 证件号（身份证或护照）
52 | - 联系方式
53 | - 各即时通讯平台联系方式，用作联系方式
54 | - 与会者名牌
55 | - 设计见 https://github.com/AOSC-Dev/aoscc/tree/master/2024/badges
56 | - 多种样式可选
57 | - 预先印刷
58 | - 空模板（供现场填写）
59 | - 匿名（无印）
60 | - 酒店团体优惠
61 | - 提供选项，与会者自行判断
62 | - 感兴趣者可选择单人或拼房
63 |
64 | 周边文创
65 | ---
66 |
67 | - 可使用新的安安同同贴图包
68 | - Kexy Biscuit 联系亚克力钥匙串提供商
69 | - 其余计划：贴纸、T 恤、编织袋、保温杯
70 |
71 | 讲者
72 | ---
73 |
74 | - 目前已邀请
75 | - 统信科技的李成刚，分享 deepin 系统维护（安排在信创场）
76 | - 龙芯中科的曾路，分享 LATX 工作（暂未确定是否能到会）
77 | - 计划邀请
78 | - 刘子兴，Canonical Foundations Team 工程师
79 | - 陈华才、孙海勇、史璞金等龙芯中科工程师
80 | - 孙子谦，红帽（中国）公司工程师
81 | - 高涵 (Revy)、王雪瑞 (xen0n) 等来自社区的专家
82 | - PLCT 一线工程师/实习生（通过 PLCT 社区伙伴群统一联系收集意向，吴伟表示可以报销职工差旅）
83 | - 此外：计划联系其他对社区较为友好的信创公司（如芯动科技）是否有一线职工希望来分享
84 |
85 | 下次例会
86 | ---
87 |
88 | 至 7 月 13 日前每周日晚 9 时同步工作进展
--------------------------------------------------------------------------------
/content/community/crowdsourcing/loongson-3c5000-server-parts.md:
--------------------------------------------------------------------------------
1 | +++
2 | title = "[COMPLETE] Loongson 3C5000 Server Parts"
3 | +++
4 |
5 | This crowdsourcing project aims to fund components and peripherals for a Loongson 3C5000 server build.
6 |
7 | # Rationale
8 |
9 | In December 2024, we received a generous donation of a Loongson 3C5000 motherboard, RAM, and heatsink from [Xinmudotmoe](http://t.me/xm_moe). However, it is still missing parts before it could be hosted and go online. We would like to source funds to complete the purchase of several key components (PSU, SSD, and adaptor), as well as a rackable chassis and rails.
10 |
11 | # Budget
12 |
13 | From [Xinmudotmoe](http://t.me/xm_moe):
14 |
15 | - Motherboard: 1 \* Loongson TC512A0 (Loongson 3C5000)
16 | - RAM: 2 \* 64GiB DDR4 3200
17 | - Heatsink: 1 \* Original 3U-spec heatsink and fan
18 |
19 | To source:
20 |
21 | | Part | Model | Qty | Price | Total |
22 | | --- | --- | :-: | :-: | :-: |
23 | | Power supply | [Super Flower Bronze King 450W](https://detail.tmall.com/item.htm?id=570585371610) | 1 | CNY ¥239 | CNY ¥239 |
24 | | Case | [3U Industrial Rackable Chassis](https://detail.tmall.com/item.htm?id=570585371610) | 1 | CNY ¥315 | CNY ¥315 |
25 | | Rails | [Generic 3U Rail](https://item.taobao.com/item.htm?id=54345568720) | 2 | CNY ¥90 | CNY ¥180 |
26 | | SSD | Intel 750 800GB U.2 (Second Hand) | 1 | CNY ¥240 | CNY ¥240 |
27 | | U.2 to PCIe Adaptor | [Jiayi U.2 to PCIe Adaptor](https://detail.tmall.com/item.htm?id=642746851242) | 1 | CNY ¥39 | CNY ¥39 |
28 | | Total | | 6 | | CNY ¥1113 |
29 |
30 | # Timeline
31 |
32 | - Late December, 2024: Parts purchase and shipment to Loongson (Wuhan), the hosting location.
33 | - Late December, 2024 to early January, 2025: Kaijian Ruan from Loongson builds and deploys the server.
34 |
35 | # Participants
36 |
37 | - Lain Yang
18 | 
19 |
24 |
19 |
20 | /{{ config.extra.logo_text }}
21 | {{ trans(key="description", lang=lang) }}
22 |
23 |
27 | {% set search_msg = trans(key="search_placeholder", lang=lang) %}
28 |
29 |
33 | {% endblock search %}
34 |
35 |
30 |
31 |
32 | ↑
46 |
47 |
48 |
49 |
54 |
55 |
56 |
57 |
58 |
--------------------------------------------------------------------------------
/templates/404.html:
--------------------------------------------------------------------------------
1 | {% import "macros.html" as macros %}
2 |
3 |
4 |
5 |
6 |
7 |
8 |
9 |
10 |
11 |
12 |
13 | {{ macros::head(title="404 Not Found", url="#", description="Page Not Found") }}
14 |
15 |
16 | {# For Netsurf #}
17 |
18 |
19 |
20 | 404
22 |Page Not Found
23 |
27 | Tomorrow, and tomorrow, and tomorrow,
28 | Creeps in this petty pace from day to day,
29 | To the last syllable of recorded time;
30 | And all our yesterdays have lighted fools
31 | The way to dusty death. Out, out, brief candle!
32 | Life's but a walking shadow, a poor player,
33 | That struts and frets his hour upon the stage,
34 | And then is heard no more. It is a tale
35 | Told by an idiot, full of sound and fury,
36 | Signifying nothing.
37 |
41 |
47 |
48 |
49 |
50 |
51 |
52 |
--------------------------------------------------------------------------------
/content/aosc-os/devices/raspberrypi/troubleshooting.zh.md:
--------------------------------------------------------------------------------
1 | +++
2 | title = "树莓派通用故障排除指南"
3 | description = "FAQs and troubleshooting guides for Raspberry Pi 4B"
4 | date = 2021-04-14T04:37:11.499Z
5 | [taxonomies]
6 | tags = ["sys-installation"]
7 |
8 | +++
9 |
10 | # 通用故障排除
11 |
12 | 本节内容将带你逐步排除树莓派的相关问题。
13 |
14 | ## HDMI 接口无输出
15 |
16 | - 移除连接到树莓派上的所有外设、存储，包括 SD 卡。然后将 MicroHDMI 线插入 Type-C 接口旁的 MicroHDMI 口。
17 | - 如果你能看到启动诊断屏幕，则说明树莓派启动正常，请进一步检查操作系统的安装。
18 | - 如果依旧无输出，则请[重新写入 EEPROM 固件](https://www.raspberrypi.org/documentation/hardware/raspberrypi/booteeprom.md)。
19 |
20 | ## 卡在启动诊断屏幕
21 |
22 | 检查你的系统介质是否已经插入，若介质存在，请确认 `start4.elf` 存在并完整。在另一台机器上挂载系统介质，重新安装 `rpi-firmware-boot` 软件包。
23 |
24 | ## 卡在彩虹屏幕
25 |
26 | 这意味着你的树莓派无法找到内核，或者内核损坏无法启动。请检查 `kernel8.img` 或指定的内核文件存在于启动分区的根目录中。内核必须为未压缩的 `Image`。
27 |
28 | 请同时检查 HDMI 接口是否接错。请保持 HDMI 连接在 Type-C 接口旁的 MiniHDMI 接口。第二个 HDMI 接口只有在系统启动之后才可用。
29 |
30 | ## 屏幕左上角有树莓派的标志，其余黑屏
31 |
32 | 如果没有光标闪动，说明内核已经崩溃了。
33 |
34 | 检查 `cmdline.txt`，删除其中的 `quiet` 参数，否则在启动时无法看到内核输出。
35 |
36 | 如果光标依旧在闪动，说明内核依旧在等待根文件系统出现。检查 `cmdline.txt`，确保 `root=` 参数指向了正确的根分区。
37 |
38 | ## 内核崩溃了 (panicked)
39 |
40 | 内核崩溃的原因有很多，具体请观察屏幕提示。以下是几个例子：
41 |
42 | - `VFS: Unable to mount root fs on unknown-block(0,0)`:
43 |
44 | 内核无法定位到根文件系统。检查 `cmdline.txt`，确保 `root=` 参数指向了正确的根分区，并且 `rootwait` 存在。
45 |
46 | - `Attempted to kill init!`
47 |
48 | 初始化程序意外结束。重新安装操作系统可能解决问题。如果你使用 initrd，尝试去掉 initrd 选项。
49 |
50 | ## 性能不佳
51 |
52 | 该问题不应该在 AOSC OS 中出现，因为 AOSC 的树莓派内核使用的是 `ondemand` 调度器。
53 |
54 | 如果你在使用树莓派官方分发的内核，请注意，该内核中 CPU 默认调度器为 `powersave`，它会一直保持你的树莓派运行在最低频率。
55 |
56 | 要设置 CPU 调度器，运行如下命令：
57 |
58 | ```
59 | sudo cpupower frequency-set -g governor
60 | ```
61 |
62 | `ondemand` 和 `conservative` 是很好的选择。如果你的散热足够好，考虑使用 `performance` 或者超频。
63 |
64 | 另请参阅
65 | ------
66 |
67 | - [树莓派文档](https://www.raspberrypi.org/documentation/)
68 | - [树莓派 GitHub](https://github.com/raspberrypi/)
69 | - [eLinux.org 社区文档](https://elinux.org/RPi_Hub)
70 | - [LibreELEC 源码](https://github.com/LibreELEC/LibreELEC.tv)
71 | - [Arch Linux ARM Wiki](https://archlinuxarm.org/wiki/Raspberry_Pi)
72 |
--------------------------------------------------------------------------------
/content/developer/minutes/20230729.md:
--------------------------------------------------------------------------------
1 | +++
2 | title = "Contributor Minutes on 2023-07-29"
3 | description = ""
4 | date = 2023-07-29
5 | [taxonomies]
6 | tags = ["minutes"]
7 | +++
8 |
9 | Agenda
10 | ======
11 |
12 | - [AOSC OS Core 11 Components and Scheduling](#aosc-os-core-11-components-and-scheduling)
13 | - [Outreach Workgroup for Bilibili, WeChat, etc.](#outreach-workgroup-for-bilibili-wechat-etc)
14 | - [Distro Review: openEuler Community Edition 22.03 LTS SP2](#distro-review-openeuler-community-edition-22-03-lts-sp2)
15 | - [Distro Review: RHEL Workstation 9.2](#distro-review-rhel-workstation-9-2)
16 |
17 | AOSC OS Core 11 Components and Scheduling
18 | =========================================
19 |
20 | - While updating GCC, keep a note that Binutils must be bumped.
21 | - RISC-V rebuilds after GCC 13 update.
22 | - Compiler tooling improvements results in faster binaries being generated.
23 | - Replacing system components step by step, instead of a full system rebuild?
24 | - This topic must not be merged before LLVM 16.
25 | - LLVM 15 will not build with GCC 13.
26 | - There are remaining GCC 12 changes, including D language enablement for POWER, which will aid GCC 13 bootstrapping.
27 |
28 | Outreach Workgroup for Bilibili, WeChat, etc.
29 | =============================================
30 |
31 | - Set e-mail for Bilibili, will need phone authentication.
32 | - Mingcong Bai is the current email and phone number owner.
33 | - To be decided: What to do when Mingcong Bai returns to the United States.
34 | - Opened an official WeChat account (ID: aosc_io), currently under audit.
35 | - Probably need a new Weibo account?
36 |
37 | Distro Review: openEuler Community Edition 22.03 LTS SP2
38 | ========================================================
39 |
40 | See our [survey notes on openEuler Community Edition](/developer/notes/distro-survey-2023#openeuler-community-edition).
41 |
42 | Distro Review: RHEL Workstation 9.2
43 | ===================================
44 |
45 | See our [survey notes on RHEL Workstation](/developer/notes/distro-survey-2023#rhel-workstation).
46 |
--------------------------------------------------------------------------------
/content/community/crowdsourcing/repo-cold-storage.md:
--------------------------------------------------------------------------------
1 | +++
2 | title = "[COMPLETE] Cold Storage HDD for Community Repository"
3 | +++
4 |
5 | This crowdsourcing project aims to fund the purchase of two hard disk drives to expand the community repository's cold storage.
6 |
7 | # Rationale
8 |
9 | As AOSC OS's software package and system release updates increase in both frequency and volume, the demand for cold storage and backup capacity has grown significantly in more recent times. We are currently running out of space for cold storage (~8TiB) and is in urgent need for more storage capacity. The cold storage contains mostly backups for old system releases and packages can help us record changes in packages and systems for regression testing.
10 |
11 | # Budget
12 |
13 | According to our investigation of the current market, the Western Digital Ultrastar DC HC570 (22TB) has excellent price to capacity ratio (for our price analysis, see [this table](https://kdocs.cn/l/ckvFzk5MYxqc)). We therefore plan to purchase two hard drives of this model to build a RAID1 array (this configuration should be fine for single-site application, as we plan to investigate potential backup solutions). The drives are to be purchased through JD's first-party seller, as the price premium is reasonable (accounting for exactly the 13% VAT) and the drives purchased through this channel has relatively good warranty coverage.
14 |
15 | Kexy Biscuit（柯晓宇）has offered to pay for the 13% VAT difference (we have therefore wrote this budget in accordance with the quote from the Taobao store "南京梵多电子科技", which is exactly JD's quote - 13% VAT). According to the current pricing (Feb. 5, 2025), the budget is as follows:
16 |
17 | - 2 * Western Digital Ultrastar DC HC570: 2 * 2729 = CNY ¥5458.
18 |
19 | # Timeline
20 |
21 | - Early February, 2024: Parts purchase and shipment to Loongson (Wuhan).
22 | - Early February, 2024: Drives to be hooked up to the hosting location's virtualised platform, going online for backups.
23 |
24 | # Participants
25 |
26 | - Kexy Biscuit（柯晓宇）42 | Return to Wiki Index 43 | · 44 | 返回维基主页 45 |
46 |