mirror of
https://github.com/Dichgrem/Blog.git
synced 2025-07-31 00:59:31 -04:00
fix:remove-public-history
This commit is contained in:
Dich
130
public/404.html
Normal file
130
public/404.html
Normal file
@ -0,0 +1,130 @@
|
||||
<!DOCTYPE html>
|
||||
<html lang="en">
|
||||
|
||||
<head>
|
||||
<title>
|
||||
404 | Dich'blog
|
||||
</title>
|
||||
|
||||
<meta http-equiv="content-type" content="text/html; charset=utf-8">
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1">
|
||||
<meta name="robots" content="noodp"/>
|
||||
|
||||
<link rel="stylesheet" href="https://blog.dich.bid/style.css">
|
||||
<link rel="stylesheet" href="https://blog.dich.bid/color/blue.css">
|
||||
|
||||
<link rel="stylesheet" href="https://blog.dich.bid/color/background_dark.css">
|
||||
|
||||
<link rel="stylesheet" href="https://blog.dich.bid/font-hack-subset.css">
|
||||
|
||||
|
||||
<meta name="description" content="Page not found">
|
||||
|
||||
<meta property="og:description" content="Page not found">
|
||||
<meta property="og:title" content="Dich'blog">
|
||||
<meta property="og:type" content="website">
|
||||
<meta property="og:url" content="https://blog.dich.bid">
|
||||
|
||||
<meta name="twitter:card" content="summary_large_image">
|
||||
<meta name="twitter:description" content="Page not found">
|
||||
<meta name="twitter:title" content="Dich'blog">
|
||||
<meta property="twitter:domain" content="blog.dich.bid">
|
||||
<meta property="twitter:url" content="https://blog.dich.bid">
|
||||
|
||||
<link rel="alternate" type="application/atom+xml" title="Dich'blog Atom Feed" href="https://blog.dich.bid/atom.xml" />
|
||||
|
||||
|
||||
<link rel="icon" type="image/png" href=/dich.webp />
|
||||
|
||||
<!-- ✅ Added center alignment styles -->
|
||||
<style>
|
||||
.footer {
|
||||
text-align: center;
|
||||
padding: 1rem 0;
|
||||
}
|
||||
|
||||
.footer__inner {
|
||||
display: flex;
|
||||
justify-content: center;
|
||||
flex-direction: column;
|
||||
align-items: center;
|
||||
}
|
||||
|
||||
.copyright {
|
||||
text-align: center;
|
||||
}
|
||||
</style>
|
||||
</head>
|
||||
|
||||
<body class="">
|
||||
<div class="container">
|
||||
|
||||
<header class="header">
|
||||
<div class="header__inner">
|
||||
<div class="header__logo">
|
||||
|
||||
<a href="https://blog.dich.bid" style="text-decoration: none;">
|
||||
<div class="logo">
|
||||
|
||||
Dich'blog
|
||||
|
||||
</div>
|
||||
</a>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
|
||||
<nav class="menu">
|
||||
<ul class="menu__inner">
|
||||
<li><a href="https://blog.dich.bid">blog</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/archive">archive</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/tags">tags</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/weekly">weekly</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/search">search</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/about">about me</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/links">links</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/atom.xml">rss</a></li>
|
||||
|
||||
<li><a href="https://github.com/Dichgrem" target="_blank" rel="noopener noreferrer">github</a></li>
|
||||
</ul>
|
||||
</nav>
|
||||
|
||||
|
||||
</header>
|
||||
|
||||
|
||||
<div class="content">
|
||||
|
||||
<div class="post">
|
||||
<h1 class="post-title">Lost?</h1>
|
||||
<p>This page does not exist.</p>
|
||||
</div>
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
<footer class="footer">
|
||||
<div class="footer__inner">
|
||||
<div class="copyright">
|
||||
<span>©
|
||||
2025
|
||||
Dichgrem</span>
|
||||
<span class="copyright-theme">
|
||||
<span class="copyright-theme-sep"> :: CC BY-SA 4.0 :: A friend comes from distant lands</span>
|
||||
</a>
|
||||
</span>
|
||||
</div>
|
||||
</div>
|
||||
</footer>
|
||||
|
||||
</div>
|
||||
</body>
|
||||
</html>
|
||||
|
||||
221
public/about-2024/index.html
Normal file
221
public/about-2024/index.html
Normal file
@ -0,0 +1,221 @@
|
||||
<!DOCTYPE html>
|
||||
<html lang="en">
|
||||
|
||||
<head>
|
||||
<title>Dich'blog</title>
|
||||
|
||||
<meta http-equiv="content-type" content="text/html; charset=utf-8">
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1">
|
||||
<meta name="robots" content="noodp"/>
|
||||
|
||||
<link rel="stylesheet" href="https://blog.dich.bid/style.css">
|
||||
<link rel="stylesheet" href="https://blog.dich.bid/color/blue.css">
|
||||
|
||||
<link rel="stylesheet" href="https://blog.dich.bid/color/background_dark.css">
|
||||
|
||||
<link rel="stylesheet" href="https://blog.dich.bid/font-hack-subset.css">
|
||||
|
||||
<meta name="description" content="">
|
||||
|
||||
<meta property="og:description" content="">
|
||||
<meta property="og:title" content="Dich'blog">
|
||||
<meta property="og:type" content="article">
|
||||
<meta property="og:url" content="https://blog.dich.bid/about-2024/">
|
||||
|
||||
<meta name="twitter:card" content="summary_large_image">
|
||||
<meta name="twitter:description" content="">
|
||||
<meta name="twitter:title" content="Dich'blog">
|
||||
<meta property="twitter:domain" content="blog.dich.bid">
|
||||
<meta property="twitter:url" content="https://blog.dich.bid/about-2024/">
|
||||
|
||||
<link rel="alternate" type="application/atom+xml" title="Dich'blog Atom Feed" href="https://blog.dich.bid/atom.xml" />
|
||||
|
||||
|
||||
<link rel="icon" type="image/png" href=/dich.webp />
|
||||
|
||||
<!-- ✅ Added center alignment styles -->
|
||||
<style>
|
||||
.footer {
|
||||
text-align: center;
|
||||
padding: 1rem 0;
|
||||
}
|
||||
|
||||
.footer__inner {
|
||||
display: flex;
|
||||
justify-content: center;
|
||||
flex-direction: column;
|
||||
align-items: center;
|
||||
}
|
||||
|
||||
.copyright {
|
||||
text-align: center;
|
||||
}
|
||||
</style>
|
||||
</head>
|
||||
|
||||
<body class="">
|
||||
<div class="container">
|
||||
|
||||
<header class="header">
|
||||
<div class="header__inner">
|
||||
<div class="header__logo">
|
||||
|
||||
<a href="https://blog.dich.bid" style="text-decoration: none;">
|
||||
<div class="logo">
|
||||
|
||||
Dich'blog
|
||||
|
||||
</div>
|
||||
</a>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
|
||||
<nav class="menu">
|
||||
<ul class="menu__inner">
|
||||
<li><a href="https://blog.dich.bid">blog</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/archive">archive</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/tags">tags</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/weekly">weekly</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/search">search</a></li>
|
||||
|
||||
<li class="active"><a href="https://blog.dich.bid/about">about me</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/links">links</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/atom.xml">rss</a></li>
|
||||
|
||||
<li><a href="https://github.com/Dichgrem" target="_blank" rel="noopener noreferrer">github</a></li>
|
||||
</ul>
|
||||
</nav>
|
||||
|
||||
|
||||
|
||||
</header>
|
||||
|
||||
|
||||
<div class="content">
|
||||
|
||||
<div class="post">
|
||||
|
||||
<h1 class="post-title"><a href="https://blog.dich.bid/about-2024/">乱七八糟:2024年度总结</a></h1>
|
||||
<div class="post-meta-inline">
|
||||
|
||||
<span class="post-date">
|
||||
2025-01-04
|
||||
</span>
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
<span class="post-tags-inline">
|
||||
:: tags:
|
||||
<a class="post-tag" href="https://blog.dich.bid/tags/luan-qi-ba-zao/">#乱七八糟</a></span>
|
||||
|
||||
|
||||
<div class="post-content">
|
||||
<p>前言 又是新的一年，时间流速感觉越来越快了。</p>
|
||||
<span id="continue-reading"></span><h2 id="da-shi-ji">大事记</h2>
|
||||
<ul>
|
||||
<li>六月份暑假将家里大翻新，包括水晶头，吊灯，门锁，水龙头等等；</li>
|
||||
<li>买了新柜子，房间更有序了；</li>
|
||||
<li>和朋友们聚餐；</li>
|
||||
<li>采用Mesh进行家庭组网；</li>
|
||||
<li>安装了一盏太阳能路灯，院子里更明亮了；</li>
|
||||
<li>和父母看电影；</li>
|
||||
<li>将博客迁移到新平台，用上亚马逊CDN；</li>
|
||||
<li>更换域名，不再续费 .ink;</li>
|
||||
<li>使用国家补贴更换电脑，换掉了故障百出的机械革命；</li>
|
||||
<li>办理校园网套餐并注销掉旧的电话卡；</li>
|
||||
<li>买了一台AX3000路由器并刷成openwrt，绕过校园网检测；</li>
|
||||
<li>开了azure虚拟机并研究；</li>
|
||||
<li>卖掉了chromebook；</li>
|
||||
<li>配置了Qemu虚拟机；</li>
|
||||
<li>给父母加装了流量包；</li>
|
||||
<li>更换了鼠标，并买了显示器和沙发椅；</li>
|
||||
<li>家里更换新热水器；</li>
|
||||
<li>修理亲戚家的网络问题；</li>
|
||||
<li>在学校和家里两处配备常用药箱；</li>
|
||||
<li>将所有设备更换为typec接口；</li>
|
||||
<li>整理并精简了RSS订阅源；</li>
|
||||
<li>重构了书签结构，增加用途分类；</li>
|
||||
<li>用上了Android 15，并使用多种开源软件；</li>
|
||||
<li>研究不同的root方案并完美隐藏环境；</li>
|
||||
<li>自制养生茶，咖啡和燕麦粥；</li>
|
||||
<li>养成跑步习惯；</li>
|
||||
<li>使用Deepl api进行翻译学习；</li>
|
||||
<li>看Netflix并研究浏览器环境检测；</li>
|
||||
<li>搭建Syncthing同步服务器实现三端同步；</li>
|
||||
<li>定时备份重要数据；</li>
|
||||
<li>学习英语纪录片，每天背单词；</li>
|
||||
</ul>
|
||||
<h2 id="cheng-chang-yu-fan-si">成长与反思</h2>
|
||||
<ul>
|
||||
<li>谋定而后动，不要冲动消费；</li>
|
||||
<li>实践出真知，不要轻易下定论；</li>
|
||||
<li>适合自己的才是最好的；</li>
|
||||
<li>锻炼自身，早点睡觉，饮食规律是最好的养生；</li>
|
||||
</ul>
|
||||
<h2 id="xin-de-yi-nian-de-mu-biao">新的一年的目标</h2>
|
||||
<ul>
|
||||
<li>在各大SRC平台挖点漏洞；</li>
|
||||
<li>封装一个完美的windows系统用于对外使用；</li>
|
||||
<li>研究并总结各大代理技术；</li>
|
||||
<li>重构家庭数据中心；</li>
|
||||
<li>学习一门新的语言并熟悉一种业务；</li>
|
||||
<li>控制体重并研究低成本健身；</li>
|
||||
</ul>
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
<div class="pagination">
|
||||
<div class="pagination__title">
|
||||
<span class="pagination__title-h">Thanks for reading! Read other posts?</span>
|
||||
<hr />
|
||||
</div>
|
||||
<div class="pagination__buttons">
|
||||
<span class="button previous">
|
||||
<a href="https://blog.dich.bid/about-vim/">
|
||||
<span class="button__icon">←</span>
|
||||
<span class="button__text">乱七八糟:Vim编辑器速查</span>
|
||||
</a>
|
||||
</span>
|
||||
|
||||
|
||||
<span class="button next">
|
||||
<a href="https://blog.dich.bid/network-zuwang/">
|
||||
<span class="button__text">Network的艺术:家庭组网方案与设备选购</span>
|
||||
<span class="button__icon">→</span>
|
||||
</a>
|
||||
</span>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
</div>
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
<footer class="footer">
|
||||
<div class="footer__inner">
|
||||
<div class="copyright">
|
||||
<span>©
|
||||
2025
|
||||
Dichgrem</span>
|
||||
<span class="copyright-theme">
|
||||
<span class="copyright-theme-sep"> :: CC BY-SA 4.0 :: A friend comes from distant lands</span>
|
||||
</a>
|
||||
</span>
|
||||
</div>
|
||||
</div>
|
||||
</footer>
|
||||
|
||||
</div>
|
||||
</body>
|
||||
</html>
|
||||
|
||||
270
public/about-accurate-pronunciation/index.html
Normal file
270
public/about-accurate-pronunciation/index.html
Normal file
@ -0,0 +1,270 @@
|
||||
<!DOCTYPE html>
|
||||
<html lang="en">
|
||||
|
||||
<head>
|
||||
<title>Dich'blog</title>
|
||||
|
||||
<meta http-equiv="content-type" content="text/html; charset=utf-8">
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1">
|
||||
<meta name="robots" content="noodp"/>
|
||||
|
||||
<link rel="stylesheet" href="https://blog.dich.bid/style.css">
|
||||
<link rel="stylesheet" href="https://blog.dich.bid/color/blue.css">
|
||||
|
||||
<link rel="stylesheet" href="https://blog.dich.bid/color/background_dark.css">
|
||||
|
||||
<link rel="stylesheet" href="https://blog.dich.bid/font-hack-subset.css">
|
||||
|
||||
<meta name="description" content="">
|
||||
|
||||
<meta property="og:description" content="">
|
||||
<meta property="og:title" content="Dich'blog">
|
||||
<meta property="og:type" content="article">
|
||||
<meta property="og:url" content="https://blog.dich.bid/about-accurate-pronunciation/">
|
||||
|
||||
<meta name="twitter:card" content="summary_large_image">
|
||||
<meta name="twitter:description" content="">
|
||||
<meta name="twitter:title" content="Dich'blog">
|
||||
<meta property="twitter:domain" content="blog.dich.bid">
|
||||
<meta property="twitter:url" content="https://blog.dich.bid/about-accurate-pronunciation/">
|
||||
|
||||
<link rel="alternate" type="application/atom+xml" title="Dich'blog Atom Feed" href="https://blog.dich.bid/atom.xml" />
|
||||
|
||||
|
||||
<link rel="icon" type="image/png" href=/dich.webp />
|
||||
|
||||
<!-- ✅ Added center alignment styles -->
|
||||
<style>
|
||||
.footer {
|
||||
text-align: center;
|
||||
padding: 1rem 0;
|
||||
}
|
||||
|
||||
.footer__inner {
|
||||
display: flex;
|
||||
justify-content: center;
|
||||
flex-direction: column;
|
||||
align-items: center;
|
||||
}
|
||||
|
||||
.copyright {
|
||||
text-align: center;
|
||||
}
|
||||
</style>
|
||||
</head>
|
||||
|
||||
<body class="">
|
||||
<div class="container">
|
||||
|
||||
<header class="header">
|
||||
<div class="header__inner">
|
||||
<div class="header__logo">
|
||||
|
||||
<a href="https://blog.dich.bid" style="text-decoration: none;">
|
||||
<div class="logo">
|
||||
|
||||
Dich'blog
|
||||
|
||||
</div>
|
||||
</a>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
|
||||
<nav class="menu">
|
||||
<ul class="menu__inner">
|
||||
<li><a href="https://blog.dich.bid">blog</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/archive">archive</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/tags">tags</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/weekly">weekly</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/search">search</a></li>
|
||||
|
||||
<li class="active"><a href="https://blog.dich.bid/about">about me</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/links">links</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/atom.xml">rss</a></li>
|
||||
|
||||
<li><a href="https://github.com/Dichgrem" target="_blank" rel="noopener noreferrer">github</a></li>
|
||||
</ul>
|
||||
</nav>
|
||||
|
||||
|
||||
|
||||
</header>
|
||||
|
||||
|
||||
<div class="content">
|
||||
|
||||
<div class="post">
|
||||
|
||||
<h1 class="post-title"><a href="https://blog.dich.bid/about-accurate-pronunciation/">乱七八糟:常见发音错误术语集合</a></h1>
|
||||
<div class="post-meta-inline">
|
||||
|
||||
<span class="post-date">
|
||||
2023-08-25
|
||||
</span>
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
<span class="post-tags-inline">
|
||||
:: tags:
|
||||
<a class="post-tag" href="https://blog.dich.bid/tags/luan-qi-ba-zao/">#乱七八糟</a></span>
|
||||
|
||||
|
||||
<div class="post-content">
|
||||
<p>前言 中文和英语发音习惯不同，容易引起误解。本文旨在帮助您准确发音常见的科技术语，欢迎随时补充。</p>
|
||||
<span id="continue-reading"></span>
|
||||
<p><strong>常见发音错误指南：公司/产品名</strong></p>
|
||||
<ul>
|
||||
<li>
|
||||
<p>Youtube: 正确念法是 "You-tube" [tju:b]，而不是 "优吐毙"，应该是 "优tiu啵"。</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>Skype: 应该念为 [ˈskaɪp]，而不是 "死盖屁"，应该是 "死盖破"。</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>Adobe: 正确的发音是 [əˈdəʊbi]，不是 "阿斗伯"，而是 "阿兜笔"。</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>C#: 应该念为 "C Sharp"，即"C煞破"。</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>GNU: 正确的发音是 [(g)nuː]， 即"哥怒"。</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>GUI: 应该念为 [ˈɡui]，即"故意"。</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>JAVA: 正确的发音是 [ˈdʒɑːvə]，而不是 "夹蛙"，应该是 "扎蛙"。</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>AJAX: 应该念为 [ˈeɪdʒæks]，而不是 "阿贾克斯"，应该是 "诶(ei) 贾克斯"。</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>Ubuntu: 正确的发音是 [uˈbuntuː]，而不是 "友邦兔"，应该是 "巫不恩兔"。</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>Debian: 应该念为 [ˈdɛbiən]，即"得(dei)变"。</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>Linux: 正确的发音有两种，[ˈlɪnəks] 或 [ˈlɪnʊks]，"丽娜克斯" 或 "李扭克斯"都可以。</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>LaTeX: 正确的发音是 [ˈleɪtɛk] 或 [ˈleɪtɛx] 或 [ˈlɑːtɛx] 或 [ˈlɑːtɛk]，即"雷泰克" 或 "拉泰克"。</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>GNOME: 念法可以是 [ɡˈnoʊm] 或 [noʊm]，即"格弄姆" 或 "弄姆"。</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>App: 应该念为 [ˈæp]，即 "阿破"。</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>null: 正确的发音是 [nʌl]，即"闹"。</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>jpg: 应该念为 [ˈdʒeɪpɛɡ]，而不是 "勾屁记"，应该是 "zhei派个"。</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>WiFi: 正确的发音是 [ˈwaɪfaɪ]，即"歪fai"。</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>mobile: 念法可以是 [moˈbil] 或 [ˈmoˌbil] 或 [ˈməubail]，即"膜拜哦" 或 "牟bou"。</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>integer: 正确的发音是 [ˈɪntɪdʒə]，而不是 "阴太阁儿"，应该是 "音剃摺儿"。</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>cache: 应该念为 [kæʃ]，而不是 "卡尺"，即"喀什"。</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>@: 应该念为 "at"。</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>Tumblr: 应该念为 "Tumbler"，而不是 "贪不勒"。</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>nginx: 正确的发音是 "Engine X"，应该是 "恩静 爱克斯"。</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>Apache: 应该念为 [əˈpætʃiː]，即"阿趴气"。</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>Lucene: 正确的发音是 [ˈluːsin]，即"鲁信"。</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>MySQL: 应该念为 [maɪ ˌɛskjuːˈɛl] 或 [maɪ ˈsiːkwəl]，可以是 "买S奎儿" 或 "买 吸扣"。</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>Exposé: 念法可以是 [ɛksˈpəʊzeɪ]，重音在Z上。</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>RFID: 官方念法是四个字母分开读 "R F I D"。</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>JSON: 应该念为 "jason"，即"zhei森"。</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>Processing: 重音在 "Pro" 上。</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>avatar: 正确的发音是 [ˌævə'tɑr]，即"艾瓦塌儿"。</p>
|
||||
</li>
|
||||
</ul>
|
||||
<h2 id="hou-ji">后记</h2>
|
||||
<p>虽然许多的词汇常常被错误发音，但在中国遵守拼音原则是入乡随俗的一种表现，且往往并没有所谓的官方读法，不必太过于纠结100%纯正的读法。</p>
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
<div class="pagination">
|
||||
<div class="pagination__title">
|
||||
<span class="pagination__title-h">Thanks for reading! Read other posts?</span>
|
||||
<hr />
|
||||
</div>
|
||||
<div class="pagination__buttons">
|
||||
<span class="button previous">
|
||||
<a href="https://blog.dich.bid/about-calling-cards/">
|
||||
<span class="button__icon">←</span>
|
||||
<span class="button__text">乱七八糟:流量卡购买与套路</span>
|
||||
</a>
|
||||
</span>
|
||||
|
||||
|
||||
<span class="button next">
|
||||
<a href="https://blog.dich.bid/about-mechrev-keyboard/">
|
||||
<span class="button__text">乱七八糟:机械革命键盘失灵拯救记</span>
|
||||
<span class="button__icon">→</span>
|
||||
</a>
|
||||
</span>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
</div>
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
<footer class="footer">
|
||||
<div class="footer__inner">
|
||||
<div class="copyright">
|
||||
<span>©
|
||||
2025
|
||||
Dichgrem</span>
|
||||
<span class="copyright-theme">
|
||||
<span class="copyright-theme-sep"> :: CC BY-SA 4.0 :: A friend comes from distant lands</span>
|
||||
</a>
|
||||
</span>
|
||||
</div>
|
||||
</div>
|
||||
</footer>
|
||||
|
||||
</div>
|
||||
</body>
|
||||
</html>
|
||||
|
||||
253
public/about-aria2/index.html
Normal file
253
public/about-aria2/index.html
Normal file
@ -0,0 +1,253 @@
|
||||
<!DOCTYPE html>
|
||||
<html lang="en">
|
||||
|
||||
<head>
|
||||
<title>Dich'blog</title>
|
||||
|
||||
<meta http-equiv="content-type" content="text/html; charset=utf-8">
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1">
|
||||
<meta name="robots" content="noodp"/>
|
||||
|
||||
<link rel="stylesheet" href="https://blog.dich.bid/style.css">
|
||||
<link rel="stylesheet" href="https://blog.dich.bid/color/blue.css">
|
||||
|
||||
<link rel="stylesheet" href="https://blog.dich.bid/color/background_dark.css">
|
||||
|
||||
<link rel="stylesheet" href="https://blog.dich.bid/font-hack-subset.css">
|
||||
|
||||
<meta name="description" content="">
|
||||
|
||||
<meta property="og:description" content="">
|
||||
<meta property="og:title" content="Dich'blog">
|
||||
<meta property="og:type" content="article">
|
||||
<meta property="og:url" content="https://blog.dich.bid/about-aria2/">
|
||||
|
||||
<meta name="twitter:card" content="summary_large_image">
|
||||
<meta name="twitter:description" content="">
|
||||
<meta name="twitter:title" content="Dich'blog">
|
||||
<meta property="twitter:domain" content="blog.dich.bid">
|
||||
<meta property="twitter:url" content="https://blog.dich.bid/about-aria2/">
|
||||
|
||||
<link rel="alternate" type="application/atom+xml" title="Dich'blog Atom Feed" href="https://blog.dich.bid/atom.xml" />
|
||||
|
||||
|
||||
<link rel="icon" type="image/png" href=/dich.webp />
|
||||
|
||||
<!-- ✅ Added center alignment styles -->
|
||||
<style>
|
||||
.footer {
|
||||
text-align: center;
|
||||
padding: 1rem 0;
|
||||
}
|
||||
|
||||
.footer__inner {
|
||||
display: flex;
|
||||
justify-content: center;
|
||||
flex-direction: column;
|
||||
align-items: center;
|
||||
}
|
||||
|
||||
.copyright {
|
||||
text-align: center;
|
||||
}
|
||||
</style>
|
||||
</head>
|
||||
|
||||
<body class="">
|
||||
<div class="container">
|
||||
|
||||
<header class="header">
|
||||
<div class="header__inner">
|
||||
<div class="header__logo">
|
||||
|
||||
<a href="https://blog.dich.bid" style="text-decoration: none;">
|
||||
<div class="logo">
|
||||
|
||||
Dich'blog
|
||||
|
||||
</div>
|
||||
</a>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
|
||||
<nav class="menu">
|
||||
<ul class="menu__inner">
|
||||
<li><a href="https://blog.dich.bid">blog</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/archive">archive</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/tags">tags</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/weekly">weekly</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/search">search</a></li>
|
||||
|
||||
<li class="active"><a href="https://blog.dich.bid/about">about me</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/links">links</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/atom.xml">rss</a></li>
|
||||
|
||||
<li><a href="https://github.com/Dichgrem" target="_blank" rel="noopener noreferrer">github</a></li>
|
||||
</ul>
|
||||
</nav>
|
||||
|
||||
|
||||
|
||||
</header>
|
||||
|
||||
|
||||
<div class="content">
|
||||
|
||||
<div class="post">
|
||||
|
||||
<h1 class="post-title"><a href="https://blog.dich.bid/about-aria2/">乱七八糟:Aria2各平台使用指南</a></h1>
|
||||
<div class="post-meta-inline">
|
||||
|
||||
<span class="post-date">
|
||||
2025-04-15
|
||||
</span>
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
<span class="post-tags-inline">
|
||||
:: tags:
|
||||
<a class="post-tag" href="https://blog.dich.bid/tags/luan-qi-ba-zao/">#乱七八糟</a></span>
|
||||
|
||||
|
||||
<div class="post-content">
|
||||
<p>前言 Aria2是一款开源、跨平台的命令行界面下载管理器，常常被各种下载器软件使用。</p>
|
||||
<span id="continue-reading"></span><h2 id="jie-shao">介绍</h2>
|
||||
<p><a href="https://github.com/aria2/aria2">Aria2</a>是一款开源、跨平台的命令行界面下载管理器，支持的下载协议有：<code>HTTP、HTTPS、FTP、Bittorrent 和 Metalink</code>。它以高效、轻量和灵活著称，适用于需要批量下载、自动化任务或远程控制的用户。</p>
|
||||
<p>Aria2 有以下几个特点：</p>
|
||||
<ul>
|
||||
<li><code>多连接下载</code>：可以从多个来源/协议下载文件并尝试利用您的最大下载带宽，真正加快您的下载体验；</li>
|
||||
<li><code>轻量</code>：不需要太多内存和 CPU 时间；</li>
|
||||
<li><code>全功能的 BitTorrent 客户端</code>：BitTorrent 客户端的所有功能都可用,，如 DHT、PEX、加密、Magnet URI、网络播种、选择性下载、本地对等发现和 UDP 跟踪器；</li>
|
||||
<li><code>支持Metalink</code>：支持 Metalink 下载描述格式。 在下载中使用 Metalink 数据块的校验和自动验证下载的数据部分；</li>
|
||||
<li><code>远程控制</code>：支持 RPC 接口来控制 aria2 进程。 支持的接口是 JSON-RPC（通过 HTTP 和 WebSocket）和 XML-RPC。</li>
|
||||
</ul>
|
||||
<p>Aria2 原生使用命令行工具进行操作，为了更方便控制我们可以使用其他开源的面板配合本体，如<a href="https://github.com/mayswind/AriaNg">AriaNg</a>或者<a href="https://github.com/ziahamza/webui-aria2">webui-aria2</a>。</p>
|
||||
<h2 id="windows">Windows</h2>
|
||||
<p>首先下载<a href="https://github.com/aria2/aria2/releases/tag/release-1.37.0">aria2-1.37.0-win-64bit-build1.zip</a>，将下载好的文件解压并放到你喜欢的目录下，设置系统环境变量，类似<code>D:\DATA\Data\AriaNg-1.3.10-AllInOne</code>,随后即可在 CMD 中使用 Aria2 。</p>
|
||||
<p>随后可以安装 AriaNg 前端，AriaNg 使用纯 html & javascript 开发, 所以其不需要任何编译器或运行环境.</p>
|
||||
<p><img src="https://raw.githubusercontent.com/mayswind/AriaNg-WebSite/master/screenshots/desktop.png" alt="ariang-1" /></p>
|
||||
<p>AriaNg 现在提供三种版本, <code>标准版、单文件版和 AriaNg Native. </code>标准版适合在 Web 服务器中部署, 提供资源缓存和按需加载的功能. 单文件版适合本地使用, 您下载后只要在浏览器中打开唯一的 html 文件即可. AriaNg Native 同样适合本地使用, 并且不需要使用浏览器.这里<code>建议使用单文件版或者Native版。</code></p>
|
||||
<p><a href="https://github.com/mayswind/AriaNg/releases">单文件版(AllinOne)</a>
|
||||
<a href="https://github.com/mayswind/AriaNg-Native/releases/tag/1.3.10">Native版</a></p>
|
||||
<h2 id="arch-linux">Arch linux</h2>
|
||||
<p>首先安装aria2本体:</p>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>paru -S aria2
|
||||
</span></code></pre>
|
||||
<p>随后创建配置文件</p>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>nano /home/<you-username>/.config/aria2/aria2.conf
|
||||
</span></code></pre>
|
||||
<p>内容为</p>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>enable-rpc=true
|
||||
</span><span>rpc-listen-all=true
|
||||
</span><span>rpc-allow-origin-all=true
|
||||
</span><span>rpc-listen-port=6800
|
||||
</span><span>continue=true
|
||||
</span><span>dir=/home/<you-username>/Downloads
|
||||
</span><span>input-file=/home/<you-username>/.config/aria2/aria2.session
|
||||
</span><span>save-session=/home/<you-username>/.config/aria2/aria2.session
|
||||
</span><span>save-session-interval=60
|
||||
</span></code></pre>
|
||||
<p>保存退出；随后创建守护进程以便开机自启动：</p>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>nano ~/.config/systemd/user/aria2.service
|
||||
</span></code></pre>
|
||||
<p>写入：</p>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>[Unit]
|
||||
</span><span>Description=Aria2 Daemon
|
||||
</span><span>After=network.target
|
||||
</span><span>
|
||||
</span><span>[Service]
|
||||
</span><span>ExecStart=/usr/bin/aria2c --conf-path=/home/<you-username>/.config/aria2/aria2.conf
|
||||
</span><span>Restart=on-failure
|
||||
</span><span>
|
||||
</span><span>[Install]
|
||||
</span><span>WantedBy=default.target
|
||||
</span></code></pre>
|
||||
<p>在更新配置文件和服务文件后，执行以下命令以重启服务：</p>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>systemctl --user daemon-reload
|
||||
</span><span>systemctl --user enable aria2.service
|
||||
</span><span>systemctl --user start aria2.service
|
||||
</span></code></pre>
|
||||
<p>使用以下命令检查服务状态：</p>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>systemctl --user status aria2.service
|
||||
</span></code></pre>
|
||||
<h2 id="liu-lan-qi-cha-jian">浏览器插件</h2>
|
||||
<p>如果你想让其直接接管浏览器下载,可以使用以下几种浏览器插件：</p>
|
||||
<p><strong>Chrome 浏览器</strong></p>
|
||||
<ul>
|
||||
<li><a href="https://github.com/alexhua/Aria2-Explorer">Aria2 Explorer</a>是一款功能强大的扩展，能够自动拦截浏览器的下载任务，并通过 JSON-RPC 接口将其导出到 Aria2 进行下载。 </li>
|
||||
<li><a href="https://github.com/alexhua/Aria2-for-chrome">Aria2 for Chrome</a></li>
|
||||
</ul>
|
||||
<p><strong>Firefox 浏览器</strong></p>
|
||||
<ul>
|
||||
<li><a href="https://github.com/Cudiph/IA2DM">Integrated Aria2 Download Manager</a> 是一款 Firefox 扩展，能够拦截下载任务，并将其转发到 Aria2。</li>
|
||||
</ul>
|
||||
<p><strong>通用版</strong></p>
|
||||
<ul>
|
||||
<li><a href="https://github.com/giantpinkrobots/varia">varia</a></li>
|
||||
</ul>
|
||||
<p>🔗</p>
|
||||
<p><strong>附带 aria2 的服务端应用</strong></p>
|
||||
<ul>
|
||||
<li><a href="https://github.com/openwrt/packages/tree/master/net/ariang">AriaNg for Openwrt</a></li>
|
||||
<li><a href="https://github.com/wahyd4/aria2-ariang-docker">aria2-ariang-docker</a></li>
|
||||
</ul>
|
||||
<hr />
|
||||
<p><strong>Done.</strong></p>
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
<div class="pagination">
|
||||
<div class="pagination__title">
|
||||
<span class="pagination__title-h">Thanks for reading! Read other posts?</span>
|
||||
<hr />
|
||||
</div>
|
||||
<div class="pagination__buttons">
|
||||
<span class="button previous">
|
||||
<a href="https://blog.dich.bid/about-markdown/">
|
||||
<span class="button__icon">←</span>
|
||||
<span class="button__text">乱七八糟:Markdown使用快速教程</span>
|
||||
</a>
|
||||
</span>
|
||||
|
||||
|
||||
<span class="button next">
|
||||
<a href="https://blog.dich.bid/about-lazyvim/">
|
||||
<span class="button__text">乱七八糟:lazyvim快速上手</span>
|
||||
<span class="button__icon">→</span>
|
||||
</a>
|
||||
</span>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
</div>
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
<footer class="footer">
|
||||
<div class="footer__inner">
|
||||
<div class="copyright">
|
||||
<span>©
|
||||
2025
|
||||
Dichgrem</span>
|
||||
<span class="copyright-theme">
|
||||
<span class="copyright-theme-sep"> :: CC BY-SA 4.0 :: A friend comes from distant lands</span>
|
||||
</a>
|
||||
</span>
|
||||
</div>
|
||||
</div>
|
||||
</footer>
|
||||
|
||||
</div>
|
||||
</body>
|
||||
</html>
|
||||
|
||||
655
public/about-baci/index.html
Normal file
655
public/about-baci/index.html
Normal file
@ -0,0 +1,655 @@
|
||||
<!DOCTYPE html>
|
||||
<html lang="en">
|
||||
|
||||
<head>
|
||||
<title>Dich'blog</title>
|
||||
|
||||
<meta http-equiv="content-type" content="text/html; charset=utf-8">
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1">
|
||||
<meta name="robots" content="noodp"/>
|
||||
|
||||
<link rel="stylesheet" href="https://blog.dich.bid/style.css">
|
||||
<link rel="stylesheet" href="https://blog.dich.bid/color/blue.css">
|
||||
|
||||
<link rel="stylesheet" href="https://blog.dich.bid/color/background_dark.css">
|
||||
|
||||
<link rel="stylesheet" href="https://blog.dich.bid/font-hack-subset.css">
|
||||
|
||||
<meta name="description" content="">
|
||||
|
||||
<meta property="og:description" content="">
|
||||
<meta property="og:title" content="Dich'blog">
|
||||
<meta property="og:type" content="article">
|
||||
<meta property="og:url" content="https://blog.dich.bid/about-baci/">
|
||||
|
||||
<meta name="twitter:card" content="summary_large_image">
|
||||
<meta name="twitter:description" content="">
|
||||
<meta name="twitter:title" content="Dich'blog">
|
||||
<meta property="twitter:domain" content="blog.dich.bid">
|
||||
<meta property="twitter:url" content="https://blog.dich.bid/about-baci/">
|
||||
|
||||
<link rel="alternate" type="application/atom+xml" title="Dich'blog Atom Feed" href="https://blog.dich.bid/atom.xml" />
|
||||
|
||||
|
||||
<link rel="icon" type="image/png" href=/dich.webp />
|
||||
|
||||
<!-- ✅ Added center alignment styles -->
|
||||
<style>
|
||||
.footer {
|
||||
text-align: center;
|
||||
padding: 1rem 0;
|
||||
}
|
||||
|
||||
.footer__inner {
|
||||
display: flex;
|
||||
justify-content: center;
|
||||
flex-direction: column;
|
||||
align-items: center;
|
||||
}
|
||||
|
||||
.copyright {
|
||||
text-align: center;
|
||||
}
|
||||
</style>
|
||||
</head>
|
||||
|
||||
<body class="">
|
||||
<div class="container">
|
||||
|
||||
<header class="header">
|
||||
<div class="header__inner">
|
||||
<div class="header__logo">
|
||||
|
||||
<a href="https://blog.dich.bid" style="text-decoration: none;">
|
||||
<div class="logo">
|
||||
|
||||
Dich'blog
|
||||
|
||||
</div>
|
||||
</a>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
|
||||
<nav class="menu">
|
||||
<ul class="menu__inner">
|
||||
<li><a href="https://blog.dich.bid">blog</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/archive">archive</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/tags">tags</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/weekly">weekly</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/search">search</a></li>
|
||||
|
||||
<li class="active"><a href="https://blog.dich.bid/about">about me</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/links">links</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/atom.xml">rss</a></li>
|
||||
|
||||
<li><a href="https://github.com/Dichgrem" target="_blank" rel="noopener noreferrer">github</a></li>
|
||||
</ul>
|
||||
</nav>
|
||||
|
||||
|
||||
|
||||
</header>
|
||||
|
||||
|
||||
<div class="content">
|
||||
|
||||
<div class="post">
|
||||
|
||||
<h1 class="post-title"><a href="https://blog.dich.bid/about-baci/">乱七八糟:Baci实验笔记</a></h1>
|
||||
<div class="post-meta-inline">
|
||||
|
||||
<span class="post-date">
|
||||
2025-04-23
|
||||
</span>
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
<span class="post-tags-inline">
|
||||
:: tags:
|
||||
<a class="post-tag" href="https://blog.dich.bid/tags/luan-qi-ba-zao/">#乱七八糟</a></span>
|
||||
|
||||
|
||||
<div class="post-content">
|
||||
<p>前言 BACI是一个简化的并发程序模拟器，这里对其语法与运行环境进行说明。</p>
|
||||
<span id="continue-reading"></span>
|
||||
<p>BACI（<code>Ben-Ari Concurrent Interpreter</code>）由计算机科学家 M. Ben-Ari 开发，是一个用于教学目的的并发程序模拟器，提供了一个简化的编程环境，使学习者能够编写、编译和执行并发程序，从而深入<code>理解进程同步、互斥、信号量</code>等核心概念。</p>
|
||||
<h1 id="guan-fang-zhi-nan">官方指南</h1>
|
||||
<p><code>BACI C−− User’s Guide</code>：详细介绍了 C−− 编译器（bacc）与 PCODE 解释器（bainterp）的使用方法、语法说明及示例程序。该指南<code>包含编译命令、信号量、监视器等并发原语</code>介绍。 这里对官方文档进行了汉化：</p>
|
||||
<blockquote>
|
||||
<p>作者：Bill Bynum/Tracy Camp 威廉玛丽学院/科罗拉多矿业学院 2002年11月5日</p>
|
||||
</blockquote>
|
||||
<h2 id="mu-lu">目录</h2>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>1. 引言
|
||||
</span><span>2. C-- 编译器语法
|
||||
</span><span>3. 并发结构
|
||||
</span><span> 3.1 cobegin 块
|
||||
</span><span> 3.2 信号量
|
||||
</span><span> 3.2.1 初始化信号量
|
||||
</span><span> 3.2.2 p (或 wait) 和 v (或 signal) 函数
|
||||
</span><span> 3.2.3 信号量使用示例
|
||||
</span><span> 3.3 管程
|
||||
</span><span> 3.3.1 条件变量
|
||||
</span><span> 3.3.2 waitc 和 signalc 函数
|
||||
</span><span> 3.3.3 立即恢复要求
|
||||
</span><span> 3.3.4 管程示例
|
||||
</span><span> 3.4 其他并发结构
|
||||
</span><span> 3.4.1 atomic 关键字
|
||||
</span><span> 3.4.2 void suspend( void );
|
||||
</span><span> 3.4.3 void revive( int process_number );
|
||||
</span><span> 3.4.4 int which_proc( void );
|
||||
</span><span> 3.4.5 int random( int range );
|
||||
</span><span>4. 内置字符串处理函数
|
||||
</span><span> 4.1 void stringCopy(string dest, string src);
|
||||
</span><span> 4.2 void stringConcat(string dest, string src);
|
||||
</span><span> 4.3 int stringCompare(string x, string y);
|
||||
</span><span> 4.4 int stringLength(string x);
|
||||
</span><span> 4.5 int sscanf(string x, rawstring fmt,...);
|
||||
</span><span> 4.6 void sprintf(string x, rawstring fmt,...);
|
||||
</span><span>5. 使用 BACI C-- 编译器和 PCODE 解释器
|
||||
</span><span>6. 示例程序和输出
|
||||
</span></code></pre>
|
||||
<h2 id="1-yin-yan">1. 引言</h2>
|
||||
<p>本文档旨在简要描述 C-- BACI 编译器和并发 PCODE 解释器程序，并说明如何使用它们。C-- 编译器首先将用户程序编译成一种称为 PCODE 的中间目标代码，然后由解释器执行。C-- 编译器支持二进制和计数信号量以及 Hoare 管程。解释器模拟并发进程执行。</p>
|
||||
<p>BACI 系统程序：</p>
|
||||
<table><thead><tr><th>程序</th><th>功能</th><th>相关文档</th></tr></thead><tbody>
|
||||
<tr><td>bacc</td><td>BACI C-- 到 PCODE 编译器</td><td>本指南 (cmimi.ps)</td></tr>
|
||||
<tr><td>bapas</td><td>BACI Pascal 到 PCODE 编译器</td><td>guidepas.ps</td></tr>
|
||||
<tr><td>bainterp</td><td>命令行 PCODE 解释器</td><td>cmimi.ps, guidepas.ps, disasm.ps</td></tr>
|
||||
<tr><td>bagui</td><td>PCODE 解释器的图形用户界面（仅限 UNIX 系统）</td><td>guiguide.ps</td></tr>
|
||||
<tr><td>badis</td><td>PCODE 反编译器</td><td>disasm.ps</td></tr>
|
||||
<tr><td>baar</td><td>PCODE 归档程序</td><td>sepcomp.ps</td></tr>
|
||||
<tr><td>bald</td><td>PCODE 链接器</td><td>sepcomp.ps</td></tr>
|
||||
</tbody></table>
|
||||
<p>Pascal 版本的编译器和解释器最初是 M. Ben-Ari 编写的程序中的过程，基于 Niklaus Wirth 的原始 Pascal 编译器。程序源代码作为附录包含在 Ben-Ari 的著作《并发编程原理》中。BACI 编译器和解释器的原始版本就是从该源代码创建的。最终，Pascal 编译器和解释器被分成两个独立的程序，并开发了 C-- 编译器，用于将用 C++ 的受限子集编写的源程序编译成可由解释器执行的 PCODE。</p>
|
||||
<p>下面将解释 C-- 编译器的语法。本指南仅适用于 C-- 编译器，不适用于 BACI 并发 Pascal 编译器。对 Pascal 编译器感兴趣的用户应参考其用户指南（见文件 guidepas.ps）。</p>
|
||||
<h2 id="2-c-bian-yi-qi-yu-fa">2. C-- 编译器语法</h2>
|
||||
<ol>
|
||||
<li>
|
||||
<p>如同 C++，注释可以用 '/<em>' 和 '</em>/' 或 '//' 来界定。</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>除了标准输入和输出外没有其他文件：cout、cin 和 endl 在 C-- BACI 中的行为与标准 C++ 一致。主程序必须具有以下形式之一：</p>
|
||||
<pre data-lang="c" style="background-color:#151515;color:#e8e8d3;" class="language-c "><code class="language-c" data-lang="c"><span style="color:#8fbfdc;">int </span><span style="color:#fad07a;">main</span><span>()
|
||||
</span><span style="color:#8fbfdc;">void </span><span style="color:#fad07a;">main</span><span>()
|
||||
</span><span style="color:#ffb964;">main</span><span>()
|
||||
</span></code></pre>
|
||||
</li>
|
||||
<li>
|
||||
<p>C-- BACI 中唯一可用的简单 C/C++ 类型是 int 和 char。还有其他与并发控制相关的类型，将在下面讨论。</p>
|
||||
<p>所有变量必须在它们出现的代码块开头声明。特别是，for 循环的索引变量不能在循环头中声明，而必须在包含该 for 循环的块的开头声明。</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>支持 string 类型。声明字符串时，必须指定字符串的长度。以下声明定义了一个长度为 20 的字符串：</p>
|
||||
<pre data-lang="c" style="background-color:#151515;color:#e8e8d3;" class="language-c "><code class="language-c" data-lang="c"><span>string[</span><span style="color:#cf6a4c;">20</span><span>] string_name;
|
||||
</span></code></pre>
|
||||
<p>长度说明符应该是字符串应具有的字符数，不应包括终止字节的空间。编译器负责为终止字节保留空间。长度说明符必须是字面常量或程序常量。</p>
|
||||
<p>在函数声明中，string 关键字用于声明 string 类型的参数：</p>
|
||||
<pre data-lang="c" style="background-color:#151515;color:#e8e8d3;" class="language-c "><code class="language-c" data-lang="c"><span style="color:#8fbfdc;">void </span><span style="color:#fad07a;">proc</span><span>(string </span><span style="color:#ffb964;">formal_parm</span><span>)
|
||||
</span></code></pre>
|
||||
<p>此声明断言 formal_parm 的类型为 string[n]，其中 n 为某个正值。string 类型的参数是通过引用传递的。不执行字符串溢出检查。</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>支持任何有效类型的数组。数组声明遵循通常的 C 语法：</p>
|
||||
<pre data-lang="c" style="background-color:#151515;color:#e8e8d3;" class="language-c "><code class="language-c" data-lang="c"><span>element_type arrayname[index1][index2][index3]...[indexN];
|
||||
</span></code></pre>
|
||||
</li>
|
||||
<li>
|
||||
<p>C-- BACI 支持关键字 typedef。例如，要使变量名 length 成为 int 的同义词：</p>
|
||||
<pre data-lang="c" style="background-color:#151515;color:#e8e8d3;" class="language-c "><code class="language-c" data-lang="c"><span style="color:#8fbfdc;">typedef int </span><span style="color:#ffb964;">length</span><span>;
|
||||
</span></code></pre>
|
||||
</li>
|
||||
<li>
|
||||
<p>支持简单类型的常量 (const)：</p>
|
||||
<pre data-lang="c" style="background-color:#151515;color:#e8e8d3;" class="language-c "><code class="language-c" data-lang="c"><span style="color:#8fbfdc;">const int</span><span> m = </span><span style="color:#cf6a4c;">5</span><span>;
|
||||
</span></code></pre>
|
||||
</li>
|
||||
<li>
|
||||
<p>在声明 int 和 char 类型的变量时，支持初始化器。初始化器的值必须是字面量或程序常量：</p>
|
||||
<pre data-lang="c" style="background-color:#151515;color:#e8e8d3;" class="language-c "><code class="language-c" data-lang="c"><span style="color:#8fbfdc;">const int</span><span> m = </span><span style="color:#cf6a4c;">5</span><span>;
|
||||
</span><span style="color:#8fbfdc;">int</span><span> j = m;
|
||||
</span><span style="color:#8fbfdc;">int</span><span> k = </span><span style="color:#cf6a4c;">3</span><span>;
|
||||
</span><span style="color:#8fbfdc;">char</span><span> c = </span><span style="color:#556633;">'</span><span style="color:#99ad6a;">a</span><span style="color:#556633;">'</span><span>;
|
||||
</span></code></pre>
|
||||
</li>
|
||||
<li>
|
||||
<p>支持过程和函数。适用标准作用域规则。支持递归。参数声明为传值或传引用：</p>
|
||||
<pre data-lang="c" style="background-color:#151515;color:#e8e8d3;" class="language-c "><code class="language-c" data-lang="c"><span style="color:#8fbfdc;">int </span><span style="color:#fad07a;">afunc</span><span>(</span><span style="color:#8fbfdc;">int </span><span style="color:#ffb964;">a</span><span>, </span><span style="color:#888888;">/* 传值 */
|
||||
</span><span> </span><span style="color:#8fbfdc;">int</span><span>& </span><span style="color:#ffb964;">b</span><span>) </span><span style="color:#888888;">/* 传引用 */
|
||||
</span></code></pre>
|
||||
<p>每个程序必须有一个 int 或 void 类型的 main() 函数，并且该函数必须是源文件中的最后一个函数。执行从 main() 的调用开始。</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>可执行语句包括 if-else、switch/case、for、while、do-while、break 和 continue。这些语句的语法与标准 C/C++ 相同。代码的括号也是标准的，即 { ... }。</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>支持标准 C/C++ 文件包含：</p>
|
||||
<pre data-lang="c" style="background-color:#151515;color:#e8e8d3;" class="language-c "><code class="language-c" data-lang="c"><span style="color:#8fbfdc;">#include </span><span style="color:#556633;"><</span><span style="color:#99ad6a;"> ... </span><span style="color:#556633;">>
|
||||
</span><span style="color:#8fbfdc;">#include </span><span style="color:#556633;">"</span><span style="color:#99ad6a;"> ... </span><span style="color:#556633;">"
|
||||
</span></code></pre>
|
||||
<p>两种包含语句风格具有相同的语义，因为没有"系统"包含目录。</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>支持用于定义外部变量的 extern 关键字。外部变量可以是任何有效的 C-- 类型。外部变量不能使用初始化器。extern 关键字只能出现在全局（"外部"）级别。典型示例：</p>
|
||||
<pre data-lang="c" style="background-color:#151515;color:#e8e8d3;" class="language-c "><code class="language-c" data-lang="c"><span style="color:#8fbfdc;">extern int</span><span> i;
|
||||
</span><span style="color:#8fbfdc;">extern char</span><span> a[</span><span style="color:#cf6a4c;">20</span><span>];
|
||||
</span><span style="color:#8fbfdc;">extern</span><span> string[</span><span style="color:#cf6a4c;">30</span><span>] b;
|
||||
</span><span style="color:#888888;">// 不允许初始化器 ----> extern int i = 30;
|
||||
</span><span style="color:#888888;">// (如果有初始化，必须在 i 定义的地方进行)
|
||||
</span><span style="color:#8fbfdc;">extern int </span><span style="color:#fad07a;">func</span><span>(</span><span style="color:#8fbfdc;">int </span><span style="color:#ffb964;">k</span><span>);
|
||||
</span><span style="color:#8fbfdc;">extern</span><span> monitor monSemaphore { </span><span style="color:#888888;">// 见第 3 节。这里只需给出
|
||||
</span><span> </span><span style="color:#8fbfdc;">void </span><span style="color:#ffb964;">monP</span><span>(); </span><span style="color:#888888;">// 管程的外部可见细节
|
||||
</span><span> </span><span style="color:#8fbfdc;">void </span><span style="color:#ffb964;">monV</span><span>();
|
||||
</span><span>}
|
||||
</span></code></pre>
|
||||
<p>使用 bacc 编译包含外部引用的源文件时，必须使用 -c 选项。有关使用外部变量的更多信息，请参阅 BACI 系统分离编译指南。</p>
|
||||
</li>
|
||||
</ol>
|
||||
<h2 id="3-bing-fa-jie-gou">3. 并发结构</h2>
|
||||
<h3 id="3-1-cobegin-kuai">3.1 cobegin 块</h3>
|
||||
<p>C-- 进程是一个 void 函数。在 BACI 系统中，"并发进程"一词与"并发线程"一词同义。要并发运行的进程列表封装在一个 cobegin 块中。这种块不能嵌套，必须出现在主程序中。</p>
|
||||
<pre data-lang="c" style="background-color:#151515;color:#e8e8d3;" class="language-c "><code class="language-c" data-lang="c"><span>cobegin {
|
||||
</span><span> </span><span style="color:#ffb964;">proc1</span><span>(...); </span><span style="color:#ffb964;">proc2</span><span>(...); ... ; </span><span style="color:#ffb964;">procN</span><span>(...);
|
||||
</span><span>}
|
||||
</span></code></pre>
|
||||
<p>列出的过程中的 PCODE 语句由解释器以任意的"随机"顺序交错执行，因此，包含 cobegin 块的同一程序的多次执行将表现为非确定性的。主程序被挂起，直到 cobegin 块中的所有进程终止，此时主程序在块结尾后的语句处恢复执行。</p>
|
||||
<h3 id="3-2-xin-hao-liang">3.2 信号量</h3>
|
||||
<p>解释器有一个预先声明的 semaphore 类型。也就是说，C-- 中的信号量是一个非负整数变量（见下面的定义），只能以受限方式访问。二进制信号量，即只取值 0 和 1 的信号量，由 semaphore 类型的 binarysem 子类型支持。在编译和执行过程中，编译器和解释器强制限制 binarysem 变量只能取值 0 或 1，而 semaphore 类型只能是非负的。</p>
|
||||
<h4 id="3-2-1-chu-shi-hua-xin-hao-liang">3.2.1 初始化信号量</h4>
|
||||
<p>只有在定义信号量变量时才允许对其赋值。例如，以下任一声明都是有效的：</p>
|
||||
<pre data-lang="c" style="background-color:#151515;color:#e8e8d3;" class="language-c "><code class="language-c" data-lang="c"><span>semaphore s = </span><span style="color:#cf6a4c;">17</span><span>;
|
||||
</span><span>binarysem b = </span><span style="color:#cf6a4c;">0</span><span>;
|
||||
</span></code></pre>
|
||||
<p>内置过程：</p>
|
||||
<pre data-lang="c" style="background-color:#151515;color:#e8e8d3;" class="language-c "><code class="language-c" data-lang="c"><span style="color:#ffb964;">initialsem</span><span>(semaphore, integer_expression);
|
||||
</span></code></pre>
|
||||
<p>是在运行时初始化任一类型信号量的唯一可用方法。在调用中，integer_expression 可以是计算结果为整数且对信号量类型有效的任何表达式（semaphore 类型为非负，binarysem 类型为 0 或 1）。例如，以下两个 initialsem 调用显示了初始化上述两个信号量的另一种方式：</p>
|
||||
<pre data-lang="c" style="background-color:#151515;color:#e8e8d3;" class="language-c "><code class="language-c" data-lang="c"><span style="color:#ffb964;">initialsem</span><span>(s, </span><span style="color:#cf6a4c;">17</span><span>);
|
||||
</span><span style="color:#ffb964;">initialsem</span><span>(b, </span><span style="color:#cf6a4c;">0</span><span>);
|
||||
</span></code></pre>
|
||||
<h4 id="3-2-2-p-huo-wait-he-v-huo-signal-han-shu">3.2.2 p (或 wait) 和 v (或 signal) 函数</h4>
|
||||
<p>p 函数（或同义的 wait）和 v 函数（或同义的 signal）由并发执行的进程用于同步它们的操作。这些函数为用户提供了更改信号量值的唯一方式。</p>
|
||||
<p>这两个函数的原型如下：</p>
|
||||
<pre data-lang="c" style="background-color:#151515;color:#e8e8d3;" class="language-c "><code class="language-c" data-lang="c"><span style="color:#8fbfdc;">void </span><span style="color:#fad07a;">p</span><span>(semaphore& </span><span style="color:#ffb964;">s</span><span>);
|
||||
</span></code></pre>
|
||||
<p>或等效地：</p>
|
||||
<pre data-lang="c" style="background-color:#151515;color:#e8e8d3;" class="language-c "><code class="language-c" data-lang="c"><span style="color:#8fbfdc;">void </span><span style="color:#fad07a;">wait</span><span>(semaphore& </span><span style="color:#ffb964;">s</span><span>);
|
||||
</span></code></pre>
|
||||
<p>以及：</p>
|
||||
<pre data-lang="c" style="background-color:#151515;color:#e8e8d3;" class="language-c "><code class="language-c" data-lang="c"><span style="color:#8fbfdc;">void </span><span style="color:#fad07a;">v</span><span>(semaphore& </span><span style="color:#ffb964;">s</span><span>);
|
||||
</span></code></pre>
|
||||
<p>或等效地：</p>
|
||||
<pre data-lang="c" style="background-color:#151515;color:#e8e8d3;" class="language-c "><code class="language-c" data-lang="c"><span style="color:#8fbfdc;">void </span><span style="color:#fad07a;">signal</span><span>(semaphore& </span><span style="color:#ffb964;">s</span><span>);
|
||||
</span></code></pre>
|
||||
<p>每个函数的信号量参数显示为引用参数，因为函数会修改信号量的值。</p>
|
||||
<p>p 和 v 函数调用的语义如下：</p>
|
||||
<p>p(sem);</p>
|
||||
<ul>
|
||||
<li>如果 sem > 0，则将 sem 减 1 并返回，允许 p 的调用者继续。</li>
|
||||
<li>如果 sem = 0，则使 p 的调用者休眠。这些操作是原子的，即它们是不可中断的，从开始到结束执行。</li>
|
||||
</ul>
|
||||
<p>v(sem);</p>
|
||||
<ul>
|
||||
<li>如果 sem = 0 且一个或多个进程正在 sem 上休眠，则唤醒其中一个进程。如果没有进程在 sem 上等待，则将 sem 加一。在任何情况下，v 的调用者都被允许继续。这些操作是原子的，即它们是不可中断的，从开始到结束执行。</li>
|
||||
<li>v 的某些实现要求按 FIFO 顺序唤醒等待信号量的进程（队列信号量），但 BACI 符合 Dijkstra 的原始提议，在信号到达时随机选择要重新唤醒的进程。</li>
|
||||
</ul>
|
||||
<h4 id="3-2-3-xin-hao-liang-shi-yong-shi-li">3.2.3 信号量使用示例</h4>
|
||||
<p>为帮助解释信号量的使用，我们提供以下简短示例：</p>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>BACI System: C-- to PCODE Compiler, 09:24 2 May 2002
|
||||
</span><span>Source file: semexample.cm Sun Apr 28 20:40:12 2002
|
||||
</span><span>line pc
|
||||
</span><span>1 0 // C-- 信号量使用示例
|
||||
</span><span>2 0
|
||||
</span><span>3 0 semaphore count; // 一个"通用"信号量
|
||||
</span><span>4 0 binarysem output; // 一个二进制（0 或 1）信号量，用于解除输出混乱
|
||||
</span><span>5 0
|
||||
</span><span>6 0 void increment()
|
||||
</span><span>7 0 {
|
||||
</span><span>8 0 p(output); // 获取对标准输出的独占访问权
|
||||
</span><span>9 2 cout << "before v(count) value of count is " << count << endl;
|
||||
</span><span>10 6 v(output);
|
||||
</span><span>11 8 v(count); // 增加信号量
|
||||
</span><span>12 10 } // increment
|
||||
</span><span>13 11
|
||||
</span><span>14 11 void decrement()
|
||||
</span><span>15 11 {
|
||||
</span><span>16 11 p(output); // 获取对标准输出的独占访问权
|
||||
</span><span>17 13 cout << "before p(count) value of count is " << count << endl;
|
||||
</span><span>18 17 v(output);
|
||||
</span><span>19 19 p(count); // 减少信号量（或停止 -- 见手册文本）
|
||||
</span><span>20 21 } // decrement
|
||||
</span><span>21 22
|
||||
</span><span>22 22 main()
|
||||
</span><span>23 23 {
|
||||
</span><span>24 23 initialsem(count,0);
|
||||
</span><span>25 26 initialsem(output,1);
|
||||
</span><span>26 29 cobegin {
|
||||
</span><span>27 30 decrement(); increment();
|
||||
</span><span>28 36 }
|
||||
</span><span>29 37 } // main
|
||||
</span></code></pre>
|
||||
<p>该程序使用两个信号量。一个信号量 count 属于 semaphore 类型，这向 BACI 系统表明该信号量将被允许具有任何非负值。两个并发过程 increment 和 decrement 通过 count 信号量相互"发送信号"。另一个信号量 output 属于 binarysem 类型，这向 BACI 系统表明该信号量应始终具有值 0 或 1；任何其他值都会导致运行时异常。该信号量用于防止两个并发执行的过程 increment 和 decrement 的输出混合在一起。</p>
|
||||
<p>我们使用以下命令生成上述编译器列表：</p>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>prompt% bacc semexample
|
||||
</span><span>Pcode and tables are stored in semexample.pco
|
||||
</span><span>Compilation listing is stored in semexample.lst
|
||||
</span></code></pre>
|
||||
<p>然后可以使用 BACI PCODE 解释器执行 semexample.pco 文件：</p>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>prompt% bainterp semexample
|
||||
</span><span>Source file: semexample.cm Sun Apr 28 20:40:12 2002
|
||||
</span><span>Executing PCODE ...
|
||||
</span><span>before v(count) value of count is 0
|
||||
</span><span>before p(count) value of count is 1
|
||||
</span></code></pre>
|
||||
<p>这是程序可能产生的三种可能输出之一。另外两种可能的程序输出是：</p>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>prompt% bainterp semexample
|
||||
</span><span>Source file: semexample.cm Sun Apr 28 20:40:12 2002
|
||||
</span><span>Executing PCODE ...
|
||||
</span><span>before p(count) value of count is 0
|
||||
</span><span>before v(count) value of count is 0
|
||||
</span></code></pre>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>prompt% bainterp semexample
|
||||
</span><span>Source file: semexample.cm Sun Apr 28 20:40:12 2002
|
||||
</span><span>Executing PCODE ...
|
||||
</span><span>before v(count) value of count is 0
|
||||
</span><span>before p(count) value of count is 0
|
||||
</span></code></pre>
|
||||
<p>有兴趣的读者可能会发现，提供这三种程序输出生成方式的解释，并证明这三种输出是唯一可能的输出，是很有指导意义的。</p>
|
||||
<h3 id="3-3-guan-cheng">3.3 管程</h3>
|
||||
<p>支持 Hoare 提出的管程概念，但有一些限制。管程是一个 C-- 块，类似于由过程或函数定义的块，但具有一些额外的属性。管程块中的所有函数都是可见的（即可从块外部调用的入口过程），但管程变量在块外部不可访问，并且只能由管程函数访问。</p>
|
||||
<p>在 C-- 中，管程只能在最外层、全局级别声明。管程不能嵌套。管程可以选择在最后一个块中有一个 init{} 块，用于初始化管程变量的值。这段代码在主程序启动时运行。</p>
|
||||
<p>管程块的只有一个过程或函数可以在任何时候执行。这一特性使得可以使用管程来实现互斥。使用管程控制并发是有优势的，因为所有控制并发的代码都位于管程中，而不是像使用信号量那样广泛分布在调用者中。</p>
|
||||
<p>管程的过程和函数使用三种结构来控制并发：条件变量、waitc（等待条件）和 signalc（表示条件）。</p>
|
||||
<h4 id="3-3-1-tiao-jian-bian-liang">3.3.1 条件变量</h4>
|
||||
<p>条件变量只能在管程中定义，因此只能由管程的进程访问。条件变量实际上从不"有"值；它是等待的地方或信号的东西。管程进程可以通过 waitc 和 signalc 调用等待条件成立或表示给定条件现在成立。</p>
|
||||
<h4 id="3-3-2-waitc-he-signalc-han-shu">3.3.2 waitc 和 signalc 函数</h4>
|
||||
<p>waitc 和 signalc 调用具有以下语法和语义：</p>
|
||||
<pre data-lang="c" style="background-color:#151515;color:#e8e8d3;" class="language-c "><code class="language-c" data-lang="c"><span style="color:#8fbfdc;">void </span><span style="color:#fad07a;">waitc</span><span>(condition </span><span style="color:#ffb964;">cond</span><span>, </span><span style="color:#8fbfdc;">int </span><span style="color:#ffb964;">prio</span><span>);
|
||||
</span></code></pre>
|
||||
<p>管程进程（因此，也是调用管程进程的外部进程）被阻塞并被分配优先级 prio 以便被重新唤醒（见下面的 signalc）。请注意，这种阻塞操作允许另一个管程进程执行，如果有的话。</p>
|
||||
<pre data-lang="c" style="background-color:#151515;color:#e8e8d3;" class="language-c "><code class="language-c" data-lang="c"><span style="color:#8fbfdc;">void </span><span style="color:#fad07a;">waitc</span><span>(condition </span><span style="color:#ffb964;">cond</span><span>);
|
||||
</span></code></pre>
|
||||
<p>此调用具有与上面的 waitc 调用相同的语义，但等待被分配默认优先级 10。</p>
|
||||
<pre data-lang="c" style="background-color:#151515;color:#e8e8d3;" class="language-c "><code class="language-c" data-lang="c"><span style="color:#8fbfdc;">void </span><span style="color:#fad07a;">signalc</span><span>(condition </span><span style="color:#ffb964;">cond</span><span>);
|
||||
</span></code></pre>
|
||||
<p>唤醒在 cond 上等待的、具有最小（最高）优先级的某个进程；否则，不执行任何操作。请注意，这与信号量 v 或 signal 完全不同，因为如果没有人等待，signalc 是一个空操作，而 v(sem) 在没有人等待时会增加 sem，从而在将来的 p(sem) 发生时"记住"该操作。</p>
|
||||
<p>优先级方案可用于实现重新唤醒等待者的 FIFO 规则。如果每个管程进程都增加与当前分配给条件的优先级相关联的管程变量，那么对该条件的连续 signalc 将按照 FIFO 顺序唤醒休眠进程。</p>
|
||||
<p>C-- 编译器提供了一个 int 函数 empty(cond)，如果条件 cond 的队列中没有进程等待，则返回 1，否则返回 0。</p>
|
||||
<h4 id="3-3-3-li-ji-hui-fu-yao-qiu">3.3.3 立即恢复要求</h4>
|
||||
<p>这是指刚刚被发送信号的条件上等待的进程应该优先于新调用管程进程（那些想要"从顶部"进入的进程）重新进入管程的要求。该要求基于这样的假设：刚刚被发送信号的条件比新进入管程的情况具有更"紧急"的业务要执行。立即恢复要求在 BACI 中通过挂起条件的发送者并随机选择一个具有适当优先级的条件等待者来运行来实现。因此，signalc 条件的管程过程通常将其作为最后一条指令。</p>
|
||||
<p>当被 signalc 重新唤醒的进程离开管程时，在发出 signalc 调用后被挂起的在管程中执行的进程被允许优先于尝试"从顶部"进入管程的进程恢复在管程中的执行。</p>
|
||||
<h4 id="3-3-4-guan-cheng-shi-li">3.3.4 管程示例</h4>
|
||||
<p>以下通过管程实现通用信号量的示例说明了管程语法：</p>
|
||||
<pre data-lang="c" style="background-color:#151515;color:#e8e8d3;" class="language-c "><code class="language-c" data-lang="c"><span>monitor monSemaphore {
|
||||
</span><span> </span><span style="color:#8fbfdc;">int</span><span> semvalue;
|
||||
</span><span> condition notbusy;
|
||||
</span><span> </span><span style="color:#8fbfdc;">void </span><span style="color:#ffb964;">monP</span><span>()
|
||||
</span><span> {
|
||||
</span><span> </span><span style="color:#8fbfdc;">if </span><span>(!semvalue)
|
||||
</span><span> </span><span style="color:#ffb964;">waitc</span><span>(notbusy);
|
||||
</span><span> </span><span style="color:#8fbfdc;">else
|
||||
</span><span> semvalue--;
|
||||
</span><span> }
|
||||
</span><span> </span><span style="color:#8fbfdc;">void </span><span style="color:#ffb964;">monV</span><span>()
|
||||
</span><span> {
|
||||
</span><span> </span><span style="color:#8fbfdc;">if </span><span>(</span><span style="color:#ffb964;">empty</span><span>(notbusy))
|
||||
</span><span> semvalue++;
|
||||
</span><span> </span><span style="color:#8fbfdc;">else
|
||||
</span><span> </span><span style="color:#ffb964;">signalc</span><span>(notbusy);
|
||||
</span><span> }
|
||||
</span><span> init{ semvalue = </span><span style="color:#cf6a4c;">1</span><span>; }
|
||||
</span><span>} </span><span style="color:#888888;">// monSemaphore 管程结束
|
||||
</span></code></pre>
|
||||
<h3 id="3-4-qi-ta-bing-fa-jie-gou">3.4 其他并发结构</h3>
|
||||
<p>BACI C-- 提供了几个低级并发结构，可用于创建新的并发控制原语：这些函数可用于创建"公平"（FIFO）队列信号量。实现这一点的代码超出了本用户指南的范围。</p>
|
||||
<h4 id="3-4-1-atomic-guan-jian-zi">3.4.1 atomic 关键字</h4>
|
||||
<p>如果一个函数被定义为 atomic，那么该函数是不可抢占的。解释器不会用上下文切换中断一个原子函数。这为用户提供了定义新原语的方法。以下程序说明了如何定义 test_and_set 原语并使用它来强制互斥：</p>
|
||||
<pre data-lang="c" style="background-color:#151515;color:#e8e8d3;" class="language-c "><code class="language-c" data-lang="c"><span>atomic </span><span style="color:#8fbfdc;">int </span><span style="color:#fad07a;">test_and_set</span><span>(</span><span style="color:#8fbfdc;">int</span><span>& </span><span style="color:#ffb964;">target</span><span>) {
|
||||
</span><span> </span><span style="color:#8fbfdc;">int</span><span> u;
|
||||
</span><span> u = target;
|
||||
</span><span> target = </span><span style="color:#cf6a4c;">1</span><span>;
|
||||
</span><span> </span><span style="color:#8fbfdc;">return</span><span> u;
|
||||
</span><span>}
|
||||
</span><span>
|
||||
</span><span style="color:#8fbfdc;">int</span><span> lock = </span><span style="color:#cf6a4c;">0</span><span>;
|
||||
</span><span>
|
||||
</span><span style="color:#8fbfdc;">void </span><span style="color:#fad07a;">proc</span><span>(</span><span style="color:#8fbfdc;">int </span><span style="color:#ffb964;">id</span><span>) {
|
||||
</span><span> </span><span style="color:#8fbfdc;">int</span><span> i = </span><span style="color:#cf6a4c;">0</span><span>;
|
||||
</span><span> </span><span style="color:#8fbfdc;">while</span><span>(i < </span><span style="color:#cf6a4c;">10</span><span>) {
|
||||
</span><span> </span><span style="color:#8fbfdc;">while </span><span>(</span><span style="color:#ffb964;">test_and_set</span><span>(lock)) </span><span style="color:#888888;">/* wait */ </span><span>;
|
||||
</span><span> cout << id;
|
||||
</span><span> lock = </span><span style="color:#cf6a4c;">0</span><span>;
|
||||
</span><span> i++;
|
||||
</span><span> }
|
||||
</span><span>}
|
||||
</span><span>
|
||||
</span><span style="color:#ffb964;">main</span><span>() {
|
||||
</span><span> cobegin { </span><span style="color:#ffb964;">proc</span><span>(</span><span style="color:#cf6a4c;">1</span><span>); </span><span style="color:#ffb964;">proc</span><span>(</span><span style="color:#cf6a4c;">2</span><span>); </span><span style="color:#ffb964;">proc</span><span>(</span><span style="color:#cf6a4c;">3</span><span>); }
|
||||
</span><span>}
|
||||
</span></code></pre>
|
||||
<h4 id="3-4-2-void-suspend-void">3.4.2 void suspend(void);</h4>
|
||||
<p>suspend 函数使调用线程休眠。</p>
|
||||
<h4 id="3-4-3-void-revive-int-process-number">3.4.3 void revive(int process_number);</h4>
|
||||
<p>revive 函数重新激活给定编号的进程。</p>
|
||||
<h4 id="3-4-4-int-which-proc-void">3.4.4 int which_proc(void);</h4>
|
||||
<p>which_proc 函数返回当前线程的进程编号。</p>
|
||||
<h4 id="3-4-5-int-random-int-range">3.4.5 int random(int range);</h4>
|
||||
<p>random 函数返回一个在 0 到 range - 1（包含）之间"随机选择"的整数。它使用与解释器使用的不同的随机数生成器流；也就是说，random() 调用不会影响解释器执行。</p>
|
||||
<h2 id="4-nei-zhi-zi-fu-chuan-chu-li-han-shu">4. 内置字符串处理函数</h2>
|
||||
<h3 id="4-1-void-stringcopy-string-dest-string-src">4.1 void stringCopy(string dest, string src);</h3>
|
||||
<p>stringCopy 函数将 src 字符串复制到 dest 字符串中。不执行字符串溢出检查。例如：</p>
|
||||
<pre data-lang="c" style="background-color:#151515;color:#e8e8d3;" class="language-c "><code class="language-c" data-lang="c"><span>string[</span><span style="color:#cf6a4c;">20</span><span>] x;
|
||||
</span><span>...
|
||||
</span><span style="color:#ffb964;">stringCopy</span><span>(x,</span><span style="color:#556633;">"</span><span style="color:#99ad6a;">Hello, world!</span><span style="color:#556633;">"</span><span>);
|
||||
</span><span style="color:#ffb964;">stringCopy</span><span>(x,</span><span style="color:#556633;">""</span><span>);
|
||||
</span></code></pre>
|
||||
<p>将把字符串 x 初始化为一个众所周知的值。第二个 stringCopy 将字符串 x 重置为零长度字符串。</p>
|
||||
<h3 id="4-2-void-stringconcat-string-dest-string-src">4.2 void stringConcat(string dest, string src);</h3>
|
||||
<p>stringConcat 函数将 src 字符串连接到 dest 的末尾。不执行字符串溢出检查。</p>
|
||||
<h3 id="4-3-int-stringcompare-string-x-string-y">4.3 int stringCompare(string x, string y);</h3>
|
||||
<p>stringCompare 函数与 C 字符串库中的 strcmp 函数具有相同的语义：如果字符串 x 按字典顺序在字符串 y 之后，则返回正数；如果字符串相等，则返回零；如果字符串 x 按字典顺序在字符串 y 之前，则返回负数。</p>
|
||||
<h3 id="4-4-int-stringlength-string-x">4.4 int stringLength(string x);</h3>
|
||||
<p>stringLength 函数返回字符串 x 的长度，不包括终止字节。</p>
|
||||
<h3 id="4-5-int-sscanf-string-x-rawstring-fmt">4.5 int sscanf(string x, rawstring fmt,...);</h3>
|
||||
<p>与"真正的" sscanf 一样，sscanf 函数根据格式字符串 fmt 扫描字符串 x，将扫描到的值存储到参数列表中提供的变量中，并返回扫描到的项目数。仅支持真正的 sscanf 的 %d、%x 和 %s 格式说明符。还支持 BACI 独有的附加格式说明符 %q（带引号的字符串）。对于此说明符，所有由一对双引号（"）分隔的字符都将被扫描到相应的字符串变量中。当在格式字符串中遇到 %q 说明符时，如果要扫描的字符串中的下一个非空白字符不是双引号，则 %q 扫描失败，并且字符串的扫描终止。</p>
|
||||
<p>格式字符串后面出现的变量是引用变量（即，不需要 & 符号）。</p>
|
||||
<p>在以下示例中，sscanf 调用返回的 i 值将为 4，存储在变量 j 中的值将为 202，存储在字符串 x 中的字符串值将为 alongstring，存储在变量 k 中的值将为 0x3c03，存储在字符串 y 中的字符串将为 a long string。</p>
|
||||
<pre data-lang="c" style="background-color:#151515;color:#e8e8d3;" class="language-c "><code class="language-c" data-lang="c"><span>string[</span><span style="color:#cf6a4c;">50</span><span>] x,y;
|
||||
</span><span style="color:#8fbfdc;">int</span><span> i,j,k;
|
||||
</span><span style="color:#ffb964;">stringCopy</span><span>(x,</span><span style="color:#556633;">"</span><span style="color:#99ad6a;">202 alongstring 3c03 \"a long string\"</span><span style="color:#556633;">"</span><span>);
|
||||
</span><span>i = sscanf(x,</span><span style="color:#556633;">"</span><span style="color:#7697d6;">%d %s %x</span><span style="color:#99ad6a;"> %q</span><span style="color:#556633;">"</span><span>,j,x,k,y);
|
||||
</span></code></pre>
|
||||
<h3 id="4-6-void-sprintf-string-x-rawstring-fmt">4.6 void sprintf(string x, rawstring fmt,...);</h3>
|
||||
<p>与 C 库中的"真正的" sprintf 函数一样，sprintf 函数使用格式字符串 fmt 和格式字符串后面的变量创建存储在变量 x 中的字符串。</p>
|
||||
<p>支持 %d、%o、%x、%X、%c 和 %s 格式说明符，其全部功能与真正的 sprintf 相同。此外，%q 格式说明符将在输出字符串中插入带双引号的字符串。%q 格式说明符等同于 "%s" 说明符。</p>
|
||||
<p>例如，在以下代码片段中：</p>
|
||||
<pre data-lang="c" style="background-color:#151515;color:#e8e8d3;" class="language-c "><code class="language-c" data-lang="c"><span>string[</span><span style="color:#cf6a4c;">80</span><span>] x;
|
||||
</span><span>string[</span><span style="color:#cf6a4c;">15</span><span>] y,z;
|
||||
</span><span style="color:#ffb964;">stringCopy</span><span>(y,</span><span style="color:#556633;">"</span><span style="color:#99ad6a;">alongstring</span><span style="color:#556633;">"</span><span>);
|
||||
</span><span style="color:#ffb964;">stringCopy</span><span>(z,</span><span style="color:#556633;">"</span><span style="color:#99ad6a;">a long string</span><span style="color:#556633;">"</span><span>);
|
||||
</span><span style="color:#ffb964;">sprintf</span><span>(x,</span><span style="color:#556633;">"</span><span style="color:#99ad6a;">.</span><span style="color:#7697d6;">%12d</span><span style="color:#99ad6a;">. .</span><span style="color:#7697d6;">%-20s</span><span style="color:#99ad6a;">. .%q. .</span><span style="color:#7697d6;">%08X</span><span style="color:#99ad6a;">.</span><span style="color:#556633;">"</span><span>,</span><span style="color:#cf6a4c;">202</span><span>,y,z,</span><span style="color:#cf6a4c;">0x3c03</span><span>);
|
||||
</span></code></pre>
|
||||
<p>字符串 x 变为：</p>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>. 202. .alongstring . ."a long string". .00003C03.
|
||||
</span></code></pre>
|
||||
<h2 id="5-shi-yong-baci-c-bian-yi-qi-he-pcode-jie-shi-qi">5. 使用 BACI C-- 编译器和 PCODE 解释器</h2>
|
||||
<p>使用 BACI 系统执行程序有两个步骤。</p>
|
||||
<ol>
|
||||
<li>
|
||||
<p>编译 ".cm" 文件以获取 ".pco" 文件。</p>
|
||||
<p>用法：bacc [可选标志] 源文件名</p>
|
||||
<p>可选标志：</p>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>-h 显示此帮助
|
||||
</span><span>-c 创建一个 .pob 目标文件以便后续链接
|
||||
</span></code></pre>
|
||||
<p>源文件名是必需的。如果缺少，您将被提示输入。如果您不提供，将附加文件后缀 ".cm"。</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>解释 ".pco" 文件以执行程序</p>
|
||||
<p>用法：baininterp [可选标志] pcode文件名</p>
|
||||
<p>可选标志：</p>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>-d 进入调试器，单步执行，设置断点
|
||||
</span><span>-e 在进入每个进程时显示活动记录 (AR)
|
||||
</span><span>-x 在退出每个进程时显示 AR
|
||||
</span><span>-t 宣布进程终止
|
||||
</span><span>-h 显示此帮助
|
||||
</span><span>-p 显示正在执行的 PCODE 指令
|
||||
</span></code></pre>
|
||||
<p>PCODE 文件名是必需的。如果缺少，您将被提示输入。文件后缀 ".pco" 将附加到您给出的文件名。</p>
|
||||
</li>
|
||||
</ol>
|
||||
<p>每次用 bainterp 执行 .pco 文件时，不必重新编译源文件。有一个 shell 脚本 baccint，它将为您调用编译器，然后调用解释器。它会将您给它的选项（见上文）传递给解释器。</p>
|
||||
<h2 id="6-shi-li-cheng-xu-he-shu-chu">6. 示例程序和输出</h2>
|
||||
<p>以下列表由 C-- BACI 编译器生成。行号右侧的数字是开始该行的指令的 PCODE 偏移量。BACI 编译器从文件 "incremen.cm" 创建此列表。该列表被放置在文件 "incremen.lst" 中。还创建了一个 "incremen.pco" 文件；此文件由解释器使用。</p>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>BACI System: C-- to PCODE Compiler, 09:24 2 May 2002
|
||||
</span><span>Source file: incremen.cm Wed Oct 22 21:18:02 1997
|
||||
</span><span>line pc
|
||||
</span><span>1 0 const int m = 5;
|
||||
</span><span>2 0 int n;
|
||||
</span><span>3 0
|
||||
</span><span>4 0 void incr(char id)
|
||||
</span><span>5 0 {
|
||||
</span><span>6 0 int i;
|
||||
</span><span>7 0
|
||||
</span><span>8 0 for(i = 1; i <= m; i = i + 1)
|
||||
</span><span>9 14 {
|
||||
</span><span>10 14 n = n + 1;
|
||||
</span><span>11 19 cout << id << " n =" << n << " i =";
|
||||
</span><span>12 25 cout << i << " " << id << endl;
|
||||
</span><span>13 31 }
|
||||
</span><span>14 32 }
|
||||
</span><span>15 33
|
||||
</span><span>16 33 main()
|
||||
</span><span>17 34 {
|
||||
</span><span>18 34 n = 0;
|
||||
</span><span>19 37 cobegin
|
||||
</span><span>20 38 {
|
||||
</span><span>21 38 incr( 'A'); incr( 'B' ); incr('C');
|
||||
</span><span>22 50 }
|
||||
</span><span>23 51 cout << "The sum is " << n << endl;
|
||||
</span><span>24 55 }
|
||||
</span></code></pre>
|
||||
<p>以下列表由 BACI 解释器生成。解释器执行编译到文件 "incremen.pco" 中的程序。</p>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>Source file: incremen.cm Wed Oct 22 21:18:02 1997
|
||||
</span><span>Executing PCODE ...
|
||||
</span><span>C n =1 i =A n =1 C2 i =
|
||||
</span><span>1 A
|
||||
</span><span>C n =4 i =2 C
|
||||
</span><span>B n =A n =5 i =24 A
|
||||
</span><span>i =1 B
|
||||
</span><span>AC n = n =6 i =3 C6 i =3
|
||||
</span><span>A
|
||||
</span><span>C n =7 i =4 C
|
||||
</span><span>B n =9 i =2 BA n =8
|
||||
</span><span>i =4 A
|
||||
</span><span>C n =8 i =5 A n =9C
|
||||
</span><span>i =5 A
|
||||
</span><span>B n =10 i =3 B
|
||||
</span><span>B n =11 i =4 B
|
||||
</span><span>B n =12 i =5 B
|
||||
</span><span>The sum is 12
|
||||
</span></code></pre>
|
||||
<h1 id="linuxhuan-jing-yun-xing-baci">linux环境运行baci</h1>
|
||||
<ul>
|
||||
<li>首先安装jdk和dos2unix</li>
|
||||
</ul>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>apt install jdk-openjdk dos2unix
|
||||
</span></code></pre>
|
||||
<ul>
|
||||
<li>使用dos2unix转换格式</li>
|
||||
</ul>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>dos2unix ~/Git/java/baci/scripts/baci
|
||||
</span></code></pre>
|
||||
<ul>
|
||||
<li>编写baci脚本</li>
|
||||
</ul>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>#!/usr/bin/env bash
|
||||
</span><span># 定位到项目根目录（包含 javabaci 子目录的目录）
|
||||
</span><span>BASEDIR="$(cd "$(dirname "${BASH_SOURCE[0]}")/.." && pwd)"
|
||||
</span><span>
|
||||
</span><span># 将 javabaci/bin（默认包类）和项目根目录（javabaci 包根）加入 classpath
|
||||
</span><span>CLASSPATH="$BASEDIR/javabaci/bin:$BASEDIR"
|
||||
</span><span>
|
||||
</span><span># 将所有参数原样传递给 java 运行
|
||||
</span><span>exec java -cp "$CLASSPATH" "$@"
|
||||
</span></code></pre>
|
||||
<ul>
|
||||
<li>给baci授予可执行权限</li>
|
||||
</ul>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>chmod +x ~/Git/java/baci/scripts/baci
|
||||
</span></code></pre>
|
||||
<ul>
|
||||
<li>添加系统环境变量</li>
|
||||
</ul>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>fish_add_path ~/Git/java/baci/scripts
|
||||
</span></code></pre>
|
||||
<ul>
|
||||
<li>查看baci是否存在</li>
|
||||
</ul>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>which baci
|
||||
</span></code></pre>
|
||||
<ul>
|
||||
<li>现在即可编译运行</li>
|
||||
</ul>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>baci bacc ex3_1.cm
|
||||
</span><span>baci bainterp ex3_1
|
||||
</span></code></pre>
|
||||
<hr />
|
||||
<p><strong>Done.</strong></p>
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
<div class="pagination">
|
||||
<div class="pagination__title">
|
||||
<span class="pagination__title-h">Thanks for reading! Read other posts?</span>
|
||||
<hr />
|
||||
</div>
|
||||
<div class="pagination__buttons">
|
||||
<span class="button previous">
|
||||
<a href="https://blog.dich.bid/about-lazyvim/">
|
||||
<span class="button__icon">←</span>
|
||||
<span class="button__text">乱七八糟:lazyvim快速上手</span>
|
||||
</a>
|
||||
</span>
|
||||
|
||||
|
||||
<span class="button next">
|
||||
<a href="https://blog.dich.bid/about-gpg/">
|
||||
<span class="button__text">乱七八糟:GPG使用小记</span>
|
||||
<span class="button__icon">→</span>
|
||||
</a>
|
||||
</span>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
</div>
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
<footer class="footer">
|
||||
<div class="footer__inner">
|
||||
<div class="copyright">
|
||||
<span>©
|
||||
2025
|
||||
Dichgrem</span>
|
||||
<span class="copyright-theme">
|
||||
<span class="copyright-theme-sep"> :: CC BY-SA 4.0 :: A friend comes from distant lands</span>
|
||||
</a>
|
||||
</span>
|
||||
</div>
|
||||
</div>
|
||||
</footer>
|
||||
|
||||
</div>
|
||||
</body>
|
||||
</html>
|
||||
|
||||
319
public/about-blog/index.html
Normal file
319
public/about-blog/index.html
Normal file
@ -0,0 +1,319 @@
|
||||
<!DOCTYPE html>
|
||||
<html lang="en">
|
||||
|
||||
<head>
|
||||
<title>Dich'blog</title>
|
||||
|
||||
<meta http-equiv="content-type" content="text/html; charset=utf-8">
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1">
|
||||
<meta name="robots" content="noodp"/>
|
||||
|
||||
<link rel="stylesheet" href="https://blog.dich.bid/style.css">
|
||||
<link rel="stylesheet" href="https://blog.dich.bid/color/blue.css">
|
||||
|
||||
<link rel="stylesheet" href="https://blog.dich.bid/color/background_dark.css">
|
||||
|
||||
<link rel="stylesheet" href="https://blog.dich.bid/font-hack-subset.css">
|
||||
|
||||
<meta name="description" content="">
|
||||
|
||||
<meta property="og:description" content="">
|
||||
<meta property="og:title" content="Dich'blog">
|
||||
<meta property="og:type" content="article">
|
||||
<meta property="og:url" content="https://blog.dich.bid/about-blog/">
|
||||
|
||||
<meta name="twitter:card" content="summary_large_image">
|
||||
<meta name="twitter:description" content="">
|
||||
<meta name="twitter:title" content="Dich'blog">
|
||||
<meta property="twitter:domain" content="blog.dich.bid">
|
||||
<meta property="twitter:url" content="https://blog.dich.bid/about-blog/">
|
||||
|
||||
<link rel="alternate" type="application/atom+xml" title="Dich'blog Atom Feed" href="https://blog.dich.bid/atom.xml" />
|
||||
|
||||
|
||||
<link rel="icon" type="image/png" href=/dich.webp />
|
||||
|
||||
<!-- ✅ Added center alignment styles -->
|
||||
<style>
|
||||
.footer {
|
||||
text-align: center;
|
||||
padding: 1rem 0;
|
||||
}
|
||||
|
||||
.footer__inner {
|
||||
display: flex;
|
||||
justify-content: center;
|
||||
flex-direction: column;
|
||||
align-items: center;
|
||||
}
|
||||
|
||||
.copyright {
|
||||
text-align: center;
|
||||
}
|
||||
</style>
|
||||
</head>
|
||||
|
||||
<body class="">
|
||||
<div class="container">
|
||||
|
||||
<header class="header">
|
||||
<div class="header__inner">
|
||||
<div class="header__logo">
|
||||
|
||||
<a href="https://blog.dich.bid" style="text-decoration: none;">
|
||||
<div class="logo">
|
||||
|
||||
Dich'blog
|
||||
|
||||
</div>
|
||||
</a>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
|
||||
<nav class="menu">
|
||||
<ul class="menu__inner">
|
||||
<li><a href="https://blog.dich.bid">blog</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/archive">archive</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/tags">tags</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/weekly">weekly</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/search">search</a></li>
|
||||
|
||||
<li class="active"><a href="https://blog.dich.bid/about">about me</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/links">links</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/atom.xml">rss</a></li>
|
||||
|
||||
<li><a href="https://github.com/Dichgrem" target="_blank" rel="noopener noreferrer">github</a></li>
|
||||
</ul>
|
||||
</nav>
|
||||
|
||||
|
||||
|
||||
</header>
|
||||
|
||||
|
||||
<div class="content">
|
||||
|
||||
<div class="post">
|
||||
|
||||
<h1 class="post-title"><a href="https://blog.dich.bid/about-blog/">乱七八糟:个人博客搭建</a></h1>
|
||||
<div class="post-meta-inline">
|
||||
|
||||
<span class="post-date">
|
||||
2023-10-12
|
||||
</span>
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
<span class="post-tags-inline">
|
||||
:: tags:
|
||||
<a class="post-tag" href="https://blog.dich.bid/tags/luan-qi-ba-zao/">#乱七八糟</a></span>
|
||||
|
||||
|
||||
<div class="post-content">
|
||||
<p>前言 个人博客的搭建具有许多的方案可以选择，本文介绍如何快速部署一个博客，并将其发布到公网。</p>
|
||||
<span id="continue-reading"></span><h2 id="qian-qing-hui-gu">前情回顾</h2>
|
||||
<p>在互联网冲浪的过程中，我们常常看到许多独立站点，他们往往是个人博客，有各种各样的主题样式；这些站点见证了互联网的发展历史。从最初的手工编写HTML页面，到后来的内容管理系统（CMS）如WordPress的兴起，再到如今流行的静态网站生成器（SSG），如Hugo，Hexo，Zola等等。</p>
|
||||
<p>个人博客的定义是什么？私以为是<code>域名+站点+原创内容</code>三要素组成。当然，最重要的原创内容往往被忽视...</p>
|
||||
<ul>
|
||||
<li>域名可以在<a href="https://www.dynadot.com/">Dynadot</a>等平台购买，也可以申请如<code>eu.org</code>或<code>us.kg</code>等免费域名，目的是为了好记；</li>
|
||||
<li>站点可以在自己的服务器上使用动态的<code>WordPress</code>或者<code>Halo</code>来一键创建，也可以使用<code>静态框架</code>部署在PAAS平台上；</li>
|
||||
</ul>
|
||||
<p>因此，整体成本应该是非常低的。</p>
|
||||
<h2 id="shi-yong-halokuai-su-da-jian-bo-ke">使用Halo快速搭建博客</h2>
|
||||
<ul>
|
||||
<li>首先你需要有一台自己的云服务器，建议在1核1G以上配置，并安装Debian系统；</li>
|
||||
<li>随后我们安装1panel，执行以下命令一键安装：</li>
|
||||
</ul>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>curl -sSL https://resource.fit2cloud.com/1panel/package/quick_start.sh -o quick_start.sh && sudo bash quick_start.sh
|
||||
</span></code></pre>
|
||||
<blockquote>
|
||||
<p>1panel依赖于docker，如果实现没有安装docker，脚本会帮你安装。</p>
|
||||
</blockquote>
|
||||
<ul>
|
||||
<li>
|
||||
<p>安装过程中选择好端口，随后即可使用<code>http:<ip>:<port>:<安全入口></code>进入登录界面，并使用默认随机生成的密码进入面板。</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>进入之后我们可以看到里面有应用商店，在其中安装<code>OpenResty</code>与<code>Halo</code>与<code>mysql</code>，安装完毕后打开外部访问地址<code>http://ip:8090</code>，即可进入halo的后台，在其中写入文章并发布。</p>
|
||||
</li>
|
||||
</ul>
|
||||
<p>但我们不能使用不安全的HTTP以及IP来访问博客；因此，我们需要一个域名指向我们的博客，例如本文的<code>blog.dich.bid</code>;可以在在<a href="https://www.dynadot.com/">Dynadot</a>等平台购买域名，并托管到<a href="https://askai.glarity.app/zh-CN/search/%E5%A6%82%E4%BD%95%E5%B0%86Dynadot%E6%B3%A8%E5%86%8C%E7%9A%84%E5%9F%9F%E5%90%8D%E8%BD%AC%E7%A7%BB%E5%88%B0Cloudflare">Cloudflare</a>。</p>
|
||||
<ul>
|
||||
<li>
|
||||
<p>随后可以在1panel的<code>网站</code>中创建一个反向代理，代理地址即为http://ip:8090，主域名为刚刚注册的域名前加blog或其他，如<code>blog.xxx.com</code></p>
|
||||
</li>
|
||||
<li>
|
||||
<p>创建完成后我们还需要配置TLS证书，在网站-HTTPS中添加证书，可以选择<a href="https://bkssl.com/ssl/selfsign">自签名证书</a>正式或者通过Acme申请免费的<code>Let's Encrypt</code>证书。</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>配置完成后在Cloudflare的DNS解析界面创建一个A记录，将你的<code>blog.xxx.com解析到你的服务器的IP</code>；</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>大功告成！现在你应该可以通过HTTPS域名访问自己的博客！</p>
|
||||
</li>
|
||||
</ul>
|
||||
<h2 id="shi-yong-hugokuang-jia-gou-jian-bo-ke">使用Hugo框架构建博客</h2>
|
||||
<p>首先明确你需要的架构，一般有两种选择：</p>
|
||||
<ul>
|
||||
<li>使用现有的架构,包括Hugo,Hexo，Zola,Astro等等；</li>
|
||||
<li>或者从头写一个框架，需要HTML/CSS/JS等知识；</li>
|
||||
</ul>
|
||||
<blockquote>
|
||||
<p>可以在<a href="https://jamstackthemes.dev/">这个网站</a>上面查看常见的框架与主题的显示效果</p>
|
||||
</blockquote>
|
||||
<ol>
|
||||
<li><strong>安装Hugo</strong>:选择好你的框架与主题后（这里以hugo为例子），随后安装hugo以及对应的依赖：</li>
|
||||
</ol>
|
||||
<ul>
|
||||
<li><strong>Windows</strong></li>
|
||||
</ul>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span># 打开以管理员模式运行的PowerShell,输入命令安装 Hugo Extended：
|
||||
</span><span>winget install Hugo.Hugo.Extended
|
||||
</span></code></pre>
|
||||
<ul>
|
||||
<li><strong>Arch linux</strong></li>
|
||||
</ul>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>paru -S hugo
|
||||
</span></code></pre>
|
||||
<ul>
|
||||
<li><strong>检查版本</strong></li>
|
||||
</ul>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>hugo version
|
||||
</span></code></pre>
|
||||
<ol start="2">
|
||||
<li><strong>创建新的 Hugo 站点</strong>：选择一个文件夹打开命令行，执行：</li>
|
||||
</ol>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>hugo new site myblog
|
||||
</span></code></pre>
|
||||
<p>该命令会在<code>myblog</code>文件夹下生成hugo的基础目录。</p>
|
||||
<ol start="3">
|
||||
<li><strong>安装主题</strong>，这里以<a href="https://jamstackthemes.dev/theme/hugo-blog-awesome/">hugo-blog-awesome</a>主题为例：</li>
|
||||
</ol>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>cd myblog
|
||||
</span><span>git clone https://github.com/hugo-sid/hugo-blog-awesome.git themes/hugo-blog-awesome
|
||||
</span></code></pre>
|
||||
<p>并在<code>hugo.toml</code>顶层添加：</p>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>theme = "hugo-blog-awesome"
|
||||
</span></code></pre>
|
||||
<p>这样 Hugo 在构建时会从 themes/ 目录加载主题文件。后续可使用<code>git pull</code>获取主题更新。</p>
|
||||
<blockquote>
|
||||
<p>你也可以直接用theme中的文件夹替换掉项目根目录下的同名文件夹，并再次修改。</p>
|
||||
</blockquote>
|
||||
<ol start="4">
|
||||
<li><strong>写入文章</strong>：使用 Hugo 提供的命令创建新文章：</li>
|
||||
</ol>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>hugo new posts/hello-world.md
|
||||
</span></code></pre>
|
||||
<p>该命令会在<code>content/posts/</code>下生成 Markdown 文件，打开后修改<code>title、date、tags</code>等前缀然后撰写 Markdown 正文, Markdown 编辑器参考<a href="https://blog.dich.bid/about-markdown/">前文</a>。</p>
|
||||
<blockquote>
|
||||
<p>注意md文章头部和正文之间得使用<code><!-- more --></code>隔断</p>
|
||||
</blockquote>
|
||||
<ol start="5">
|
||||
<li><strong>本地测试</strong>：在项目根目录运行：</li>
|
||||
</ol>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>hugo server -D
|
||||
</span></code></pre>
|
||||
<p>然后在浏览器访问<code>http://localhost:1313</code>即可实时预览并查看更新效果。</p>
|
||||
<ol start="6">
|
||||
<li>
|
||||
<p><strong>上传到GitHub</strong>：新建一个Github仓库，用Git连接并将Hugo项目的文件夹push上去；</p>
|
||||
</li>
|
||||
<li>
|
||||
<p><strong>使用PAAS平台部署</strong>：随后使用<a href="https://vercel.com">Vercel</a>/<a href="https://www.netlify.com/">Netlify</a>等平台读取GitHub仓库并部署Hugo博客项目，并设置指向自己的域名，即<code>设置一条CNAME记录</code>。部署的时候可以让<code>平台command运行部署</code>也可以<code>本地build之后直接上传public文件夹</code>并在平台中指定。</p>
|
||||
</li>
|
||||
</ol>
|
||||
<blockquote>
|
||||
<p>当然，也可以使用GitHub Pages部署，详见<a href="https://docs.github.com/zh/pages/quickstart?library=true">官方文档</a></p>
|
||||
</blockquote>
|
||||
<h3 id="ke-xuan-ding-zhi-xiang">可选定制项</h3>
|
||||
<p><strong>你想要的显示效果?</strong></p>
|
||||
<ul>
|
||||
<li>风格，包括命令行风格，极简风格，MD3风格等等;</li>
|
||||
<li>布局，是响应式还是传统布局？</li>
|
||||
</ul>
|
||||
<p><strong>你需要那些功能?</strong></p>
|
||||
<ul>
|
||||
<li>黑暗/白天模式切换;</li>
|
||||
<li>高斯模糊？动态取色？</li>
|
||||
<li>PPT般的动效？</li>
|
||||
<li>访问人数和运行天数统计？</li>
|
||||
<li>Tag分类和时间排序？</li>
|
||||
<li>搜索功能和RSS？</li>
|
||||
</ul>
|
||||
<p><strong>需要处理哪些外部依赖?</strong></p>
|
||||
<ul>
|
||||
<li>域名和paas平台？</li>
|
||||
<li>图床还是直接嵌入图片？</li>
|
||||
<li>是否需要自动编译？</li>
|
||||
<li>是否需要多平台发布？</li>
|
||||
<li>是否需要加密特定文章？</li>
|
||||
</ul>
|
||||
<p><strong>以上的功能和需求是否对SEO和界面相应时间造成影响？</strong></p>
|
||||
<h2 id="link">🔗</h2>
|
||||
<ul>
|
||||
<li><a href="https://gohugo.io/documentation/">Hugo官方文档</a></li>
|
||||
<li><a href="https://www.getzola.org/documentation/getting-started/overview/">zola官方文档</a></li>
|
||||
<li><a href="https://github.com/pawroman/zola-theme-terminimal">zoal-terminimal主题</a></li>
|
||||
<li><a href="https://github.com/aaranxu/chinese-copywriting-guidelines">中文排版指南</a></li>
|
||||
<li><a href="https://atpx.com/blog/improving-online-reading-experience/">如何提高用户网页阅读体验</a></li>
|
||||
</ul>
|
||||
<hr />
|
||||
<p><strong>Done.</strong></p>
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
<div class="pagination">
|
||||
<div class="pagination__title">
|
||||
<span class="pagination__title-h">Thanks for reading! Read other posts?</span>
|
||||
<hr />
|
||||
</div>
|
||||
<div class="pagination__buttons">
|
||||
<span class="button previous">
|
||||
<a href="https://blog.dich.bid/about-mechrev-keyboard/">
|
||||
<span class="button__icon">←</span>
|
||||
<span class="button__text">乱七八糟:机械革命键盘失灵拯救记</span>
|
||||
</a>
|
||||
</span>
|
||||
|
||||
|
||||
<span class="button next">
|
||||
<a href="https://blog.dich.bid/about-junk-cleanup/">
|
||||
<span class="button__text">乱七八糟:垃圾清理的艺术</span>
|
||||
<span class="button__icon">→</span>
|
||||
</a>
|
||||
</span>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
</div>
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
<footer class="footer">
|
||||
<div class="footer__inner">
|
||||
<div class="copyright">
|
||||
<span>©
|
||||
2025
|
||||
Dichgrem</span>
|
||||
<span class="copyright-theme">
|
||||
<span class="copyright-theme-sep"> :: CC BY-SA 4.0 :: A friend comes from distant lands</span>
|
||||
</a>
|
||||
</span>
|
||||
</div>
|
||||
</div>
|
||||
</footer>
|
||||
|
||||
</div>
|
||||
</body>
|
||||
</html>
|
||||
|
||||
224
public/about-calling-cards/index.html
Normal file
224
public/about-calling-cards/index.html
Normal file
@ -0,0 +1,224 @@
|
||||
<!DOCTYPE html>
|
||||
<html lang="en">
|
||||
|
||||
<head>
|
||||
<title>Dich'blog</title>
|
||||
|
||||
<meta http-equiv="content-type" content="text/html; charset=utf-8">
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1">
|
||||
<meta name="robots" content="noodp"/>
|
||||
|
||||
<link rel="stylesheet" href="https://blog.dich.bid/style.css">
|
||||
<link rel="stylesheet" href="https://blog.dich.bid/color/blue.css">
|
||||
|
||||
<link rel="stylesheet" href="https://blog.dich.bid/color/background_dark.css">
|
||||
|
||||
<link rel="stylesheet" href="https://blog.dich.bid/font-hack-subset.css">
|
||||
|
||||
<meta name="description" content="">
|
||||
|
||||
<meta property="og:description" content="">
|
||||
<meta property="og:title" content="Dich'blog">
|
||||
<meta property="og:type" content="article">
|
||||
<meta property="og:url" content="https://blog.dich.bid/about-calling-cards/">
|
||||
|
||||
<meta name="twitter:card" content="summary_large_image">
|
||||
<meta name="twitter:description" content="">
|
||||
<meta name="twitter:title" content="Dich'blog">
|
||||
<meta property="twitter:domain" content="blog.dich.bid">
|
||||
<meta property="twitter:url" content="https://blog.dich.bid/about-calling-cards/">
|
||||
|
||||
<link rel="alternate" type="application/atom+xml" title="Dich'blog Atom Feed" href="https://blog.dich.bid/atom.xml" />
|
||||
|
||||
|
||||
<link rel="icon" type="image/png" href=/dich.webp />
|
||||
|
||||
<!-- ✅ Added center alignment styles -->
|
||||
<style>
|
||||
.footer {
|
||||
text-align: center;
|
||||
padding: 1rem 0;
|
||||
}
|
||||
|
||||
.footer__inner {
|
||||
display: flex;
|
||||
justify-content: center;
|
||||
flex-direction: column;
|
||||
align-items: center;
|
||||
}
|
||||
|
||||
.copyright {
|
||||
text-align: center;
|
||||
}
|
||||
</style>
|
||||
</head>
|
||||
|
||||
<body class="">
|
||||
<div class="container">
|
||||
|
||||
<header class="header">
|
||||
<div class="header__inner">
|
||||
<div class="header__logo">
|
||||
|
||||
<a href="https://blog.dich.bid" style="text-decoration: none;">
|
||||
<div class="logo">
|
||||
|
||||
Dich'blog
|
||||
|
||||
</div>
|
||||
</a>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
|
||||
<nav class="menu">
|
||||
<ul class="menu__inner">
|
||||
<li><a href="https://blog.dich.bid">blog</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/archive">archive</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/tags">tags</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/weekly">weekly</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/search">search</a></li>
|
||||
|
||||
<li class="active"><a href="https://blog.dich.bid/about">about me</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/links">links</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/atom.xml">rss</a></li>
|
||||
|
||||
<li><a href="https://github.com/Dichgrem" target="_blank" rel="noopener noreferrer">github</a></li>
|
||||
</ul>
|
||||
</nav>
|
||||
|
||||
|
||||
|
||||
</header>
|
||||
|
||||
|
||||
<div class="content">
|
||||
|
||||
<div class="post">
|
||||
|
||||
<h1 class="post-title"><a href="https://blog.dich.bid/about-calling-cards/">乱七八糟:流量卡购买与套路</a></h1>
|
||||
<div class="post-meta-inline">
|
||||
|
||||
<span class="post-date">
|
||||
2023-08-24
|
||||
</span>
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
<span class="post-tags-inline">
|
||||
:: tags:
|
||||
<a class="post-tag" href="https://blog.dich.bid/tags/luan-qi-ba-zao/">#乱七八糟</a></span>
|
||||
|
||||
|
||||
<div class="post-content">
|
||||
<p>前言 由于临近升学，校园网不尽人意，因此许多小伙伴有了买一张流量卡的计划。本文以三大运营商为例，说明常见流量卡的套路与选择。</p>
|
||||
<span id="continue-reading"></span>
|
||||
<p>2019 年 6 月 6 日，工信部发布 4 张 5G 牌照，标志 5G 商用的开始，中国进入 5G 时代。回想过去数年，4G 降速、5G 提费的新闻屡见不鲜，而 5G 网络的落地应用，似乎离普通人依然遥远。对于普通人而言，昂贵的5G套餐资费依然没有流量卡香；那什么是流量卡呢？</p>
|
||||
<h2 id="yi-shen-me-shi-liu-liang-qia">一.什么是流量卡</h2>
|
||||
<p>流量卡<code>本质上还是一张 SIM 卡，往往具有大流量、低月租的特征</code>。互联网上有非常多不同运营商的「优惠套餐」，实则是不同卡商取名包装后的产物，卡商往往可以通过激活后赚取高额佣金获利,比如每年大学新生开学，校园里总有「运营商营业厅」摆摊甚至上门推销所谓「校园卡」，不少声称「超大流量」「长期套餐」，更有甚者，会搬出「校园网」来给涉世未深的大一小白们制造焦虑。</p>
|
||||
<p>事实上，不管是「校园卡」还是网上卡商们大力吆喝的优惠流量卡，本质上<code>都属于个人使用的电话卡</code>。例如电信的优惠套餐，大都通过「电信星卡」套餐，再由当地运营商叠加优惠包（赠费或叠加流量包）包装而成。</p>
|
||||
<h2 id="er-wei-shen-me-xu-yao-liu-liang-qia">二.为什么需要流量卡</h2>
|
||||
<p>普通卡大多有着长合约和固定归属地，不能轻易更换套餐，且套餐月租费用较高，<code>特别是在5G推行时期，4G的资费不减反升，且速度有所下降</code>。而流量卡动则100G往上，月租在50左右，且可以随时退卡。</p>
|
||||
<h2 id="san-liu-liang-qia-ji-ben-yuan-li">三.流量卡基本原理</h2>
|
||||
<p>由于三大运营商处于<code>半国企状态（自负盈亏）</code>，因此在长期亏损下不得不整一些牛马活采用一些策略，比如冗长的条款和隐藏极深的优惠套餐等等。而由于不同地区的经济发展状况不同，<code>部分中西部地区的地区分公司业绩不佳</code>，为了在短期内达到要求往往会和一些地区分销商进行合作，将本地区的电话卡改为优惠的套餐，从而吸引客户。注意：<code>99%所谓的月租19、29等流量卡都是要先缴一笔较多的钱，进而每月返还一点点，实现长期上的低月租</code>，运营商是要短期变现的！</p>
|
||||
<p>那么，是不是我们就没有优惠了呢？其实相对于5元1G、40元10G的资费而言还是非常划算的。</p>
|
||||
<h2 id="si-fen-qing-liu-liang-qia-he-wu-lian-qia">四.分清流量卡和物联卡</h2>
|
||||
<p>部分小伙伴反映被物联卡坑了！这里我们一定要注意，诸如某宝某猫上面的9999G超级流量卡，usb接口的随身WiFi等等不出意外都是物联卡。</p>
|
||||
<p>什么是物联卡？<code>物联网设备往往只需要网络接入而不需要电话短信功能，也就不需要电话号码</code>。为了防止滥用，同时降低成本，运营商往往会给这些设备制作「物联网卡」，也就是只具备上网功能的电话卡。为了便于物联网设备公司管理，运营商还会授权这些代理公司组建「流量池」，对池中每一张卡进行限速、流控等管理。</p>
|
||||
<p>市面上绝大多数「随身 WiFi」自带的流量卡套餐，正是来自运营商授权公司的「自组流量池」。绝大多数物联卡商家，为了控制成本，会采取各种措施进行限制，而由于这一行业往往处于缺乏有效监管的灰色地带，这些限制大都不会被商家明确写出。</p>
|
||||
<p>最常见的套路是<strong>虚标流量</strong>。由于这类物联网卡并没有手机号码，也就无法使用运营商官方渠道查询流量使用情况。商家自建流量管理后台，也就有了对数据做手脚的可乘之机。有些商家会将使用的流量按 1.5 倍甚至更高倍率计费，因此，你也许会发现自己的流量不那么「经用」。</p>
|
||||
<p>另一个套路是<strong>流控</strong>，包括流量封顶和限速。网上销量相当高的某随身 WiFi 商家，电商平台可以看到不少次月开始卡慢、每日设置流量封顶的差评。比如，广告上打着「月享 1500G」，实际上也许每天限制使用 50G，达量往往会限速甚至封卡。</p>
|
||||
<p>在市面上，流量池批发流量的价格大约是 0.1 元 / G，如果你看到了显著低于这个价格的流量，可能需要多斟酌一下是否可靠。</p>
|
||||
<p>当然，也有正规厂商提供可信的流量池或与运营商直接合作的物联网卡，限制会少不少，不过难以买到。</p>
|
||||
<h2 id="wu-gou-mai-liu-liang-qia-xu-yao-zhu-yi-de-shi-xiang">五.购买流量卡需要注意的事项</h2>
|
||||
<ul>
|
||||
<li><strong>靓号</strong></li>
|
||||
</ul>
|
||||
<p><code>大部分流量卡是不能选号的</code>，因为这类具有优惠套餐的卡大多来自不同地区的前任买家，因此靓号数有限，总不能既有好的号码又有优惠套餐；而这就带来第二个问题：</p>
|
||||
<ul>
|
||||
<li><strong>号码绑定</strong></li>
|
||||
</ul>
|
||||
<p>作为信息时代的重要识别符，电话卡和身份证几乎同样重要，在前任主人信息意识不强的情况下，其<code>大部分社交媒体、生活服务和各种网站的帐号都会遗留下来，这就需要我们去一一解绑</code>；作者曾经买了一张宁夏的流量卡，结果通过验证和社工成功进入了前主人的微信和淘宝帐号，当然现在已经注销了；部分平台不支持注销的，只能继续使用前号；<code>甚至有概率被前号主的债务人打电话催债</code>；因此我们一定要小心谨慎；</p>
|
||||
<ul>
|
||||
<li><strong>归属地</strong></li>
|
||||
</ul>
|
||||
<p>由于前面所讲的原因，<code>流量卡的归属地大部分是随机的</code>，比如青海，宁夏等等；这样一来当别人打电话时会看到地址为中国宁夏之类，可能会误以为是诈骗电话；当然这样也有不被看到地址的好处，所谓各有优点。</p>
|
||||
<ul>
|
||||
<li><strong>信号</strong></li>
|
||||
</ul>
|
||||
<p><code>SIM卡本身对信号没有影响，除非氧化严重难以识别</code>；真正影响体验的不只是手机基带，还有你所在地区中三大<code>运营商的基站分布</code>；因此，购买之前可以先查看一下你所在地区哪个运营商信号最好，从而对症下药。</p>
|
||||
<ul>
|
||||
<li><strong>副卡</strong></li>
|
||||
</ul>
|
||||
<p>有些小伙伴在买完流量卡后打算作为主力卡使用，那这样原先的卡套餐就没必要了，可以办理8元保号套餐，让号码可以继续使用。</p>
|
||||
<ul>
|
||||
<li><strong>流量</strong></li>
|
||||
</ul>
|
||||
<p>不少校园套餐，使用了<code>定向流量</code>（或区域流量），即仅可在指定APP使用或指定省（市）内使用，而非全国流量/通用流量。而宣传的额外流量往往以流量包形式给出，此流量包不同活动获得方式也不同；办完卡后进入营业厅的APP，流量可能不会马上出现，这是因为系统的延迟以及运营商的计时方式，<code>有些卡需要在月初才能有全部的流量</code>，后几天按百分比计算，下个月就正常了。</p>
|
||||
<ul>
|
||||
<li><strong>激活</strong></li>
|
||||
</ul>
|
||||
<p>注意要<code>实名购卡</code>，且收获地址要足够详细，会有专门的快递小哥和你线下激活，预充值，注意接收电话！</p>
|
||||
<ul>
|
||||
<li><strong>注销</strong></li>
|
||||
</ul>
|
||||
<p><code>每个运营商最多办5张电话卡</code>，因此一个人一辈子最多只能从三大运营商办理一共15张卡，因此注销需谨慎；流量卡大部分可以线上异地注销，但也要仔细看清楚条款。</p>
|
||||
<hr />
|
||||
<p><strong>Done.</strong></p>
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
<div class="pagination">
|
||||
<div class="pagination__title">
|
||||
<span class="pagination__title-h">Thanks for reading! Read other posts?</span>
|
||||
<hr />
|
||||
</div>
|
||||
<div class="pagination__buttons">
|
||||
<span class="button previous">
|
||||
<a href="https://blog.dich.bid/awesome-arch-linux/">
|
||||
<span class="button__icon">←</span>
|
||||
<span class="button__text">综合工程:Arch-linux 安装与配置</span>
|
||||
</a>
|
||||
</span>
|
||||
|
||||
|
||||
<span class="button next">
|
||||
<a href="https://blog.dich.bid/about-accurate-pronunciation/">
|
||||
<span class="button__text">乱七八糟:常见发音错误术语集合</span>
|
||||
<span class="button__icon">→</span>
|
||||
</a>
|
||||
</span>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
</div>
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
<footer class="footer">
|
||||
<div class="footer__inner">
|
||||
<div class="copyright">
|
||||
<span>©
|
||||
2025
|
||||
Dichgrem</span>
|
||||
<span class="copyright-theme">
|
||||
<span class="copyright-theme-sep"> :: CC BY-SA 4.0 :: A friend comes from distant lands</span>
|
||||
</a>
|
||||
</span>
|
||||
</div>
|
||||
</div>
|
||||
</footer>
|
||||
|
||||
</div>
|
||||
</body>
|
||||
</html>
|
||||
|
||||
367
public/about-cslearning/index.html
Normal file
367
public/about-cslearning/index.html
Normal file
@ -0,0 +1,367 @@
|
||||
<!DOCTYPE html>
|
||||
<html lang="en">
|
||||
|
||||
<head>
|
||||
<title>Dich'blog</title>
|
||||
|
||||
<meta http-equiv="content-type" content="text/html; charset=utf-8">
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1">
|
||||
<meta name="robots" content="noodp"/>
|
||||
|
||||
<link rel="stylesheet" href="https://blog.dich.bid/style.css">
|
||||
<link rel="stylesheet" href="https://blog.dich.bid/color/blue.css">
|
||||
|
||||
<link rel="stylesheet" href="https://blog.dich.bid/color/background_dark.css">
|
||||
|
||||
<link rel="stylesheet" href="https://blog.dich.bid/font-hack-subset.css">
|
||||
|
||||
<meta name="description" content="">
|
||||
|
||||
<meta property="og:description" content="">
|
||||
<meta property="og:title" content="Dich'blog">
|
||||
<meta property="og:type" content="article">
|
||||
<meta property="og:url" content="https://blog.dich.bid/about-cslearning/">
|
||||
|
||||
<meta name="twitter:card" content="summary_large_image">
|
||||
<meta name="twitter:description" content="">
|
||||
<meta name="twitter:title" content="Dich'blog">
|
||||
<meta property="twitter:domain" content="blog.dich.bid">
|
||||
<meta property="twitter:url" content="https://blog.dich.bid/about-cslearning/">
|
||||
|
||||
<link rel="alternate" type="application/atom+xml" title="Dich'blog Atom Feed" href="https://blog.dich.bid/atom.xml" />
|
||||
|
||||
|
||||
<link rel="icon" type="image/png" href=/dich.webp />
|
||||
|
||||
<!-- ✅ Added center alignment styles -->
|
||||
<style>
|
||||
.footer {
|
||||
text-align: center;
|
||||
padding: 1rem 0;
|
||||
}
|
||||
|
||||
.footer__inner {
|
||||
display: flex;
|
||||
justify-content: center;
|
||||
flex-direction: column;
|
||||
align-items: center;
|
||||
}
|
||||
|
||||
.copyright {
|
||||
text-align: center;
|
||||
}
|
||||
</style>
|
||||
</head>
|
||||
|
||||
<body class="">
|
||||
<div class="container">
|
||||
|
||||
<header class="header">
|
||||
<div class="header__inner">
|
||||
<div class="header__logo">
|
||||
|
||||
<a href="https://blog.dich.bid" style="text-decoration: none;">
|
||||
<div class="logo">
|
||||
|
||||
Dich'blog
|
||||
|
||||
</div>
|
||||
</a>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
|
||||
<nav class="menu">
|
||||
<ul class="menu__inner">
|
||||
<li><a href="https://blog.dich.bid">blog</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/archive">archive</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/tags">tags</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/weekly">weekly</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/search">search</a></li>
|
||||
|
||||
<li class="active"><a href="https://blog.dich.bid/about">about me</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/links">links</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/atom.xml">rss</a></li>
|
||||
|
||||
<li><a href="https://github.com/Dichgrem" target="_blank" rel="noopener noreferrer">github</a></li>
|
||||
</ul>
|
||||
</nav>
|
||||
|
||||
|
||||
|
||||
</header>
|
||||
|
||||
|
||||
<div class="content">
|
||||
|
||||
<div class="post">
|
||||
|
||||
<h1 class="post-title"><a href="https://blog.dich.bid/about-cslearning/">乱七八糟:计算机科学优质视频</a></h1>
|
||||
<div class="post-meta-inline">
|
||||
|
||||
<span class="post-date">
|
||||
2024-05-31
|
||||
</span>
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
<span class="post-tags-inline">
|
||||
:: tags:
|
||||
<a class="post-tag" href="https://blog.dich.bid/tags/luan-qi-ba-zao/">#乱七八糟</a></span>
|
||||
|
||||
|
||||
<div class="post-content">
|
||||
<p>前言 CSdiy珠玉在前,为CS教育做出了极大贡献.这里分享一些优质的CS学习相关视频.</p>
|
||||
<span id="continue-reading"></span><h2 id="ji-suan-ji-zu-jian-fa-zhan-li-shi">计算机组件发展历史</h2>
|
||||
<ul>
|
||||
<li><a href="https://www.bilibili.com/video/BV1ME421A78n/">CPU发展史</a></li>
|
||||
<li><a href="https://www.bilibili.com/video/BV1gb421h7C4/">BIOS发展史</a></li>
|
||||
<li><a href="https://www.bilibili.com/video/BV1H5m6YkE9c/">存储器发展史</a></li>
|
||||
<li><a href="https://www.bilibili.com/video/BV1h2w5eREfD/">显示器发展史</a></li>
|
||||
<li><a href="https://www.bilibili.com/video/BV1ru411M7Hc/">计算机发展史</a></li>
|
||||
<li><a href="https://www.bilibili.com/video/BV1Zc411D7sG/">操作系统发展史</a></li>
|
||||
</ul>
|
||||
<h2 id="ji-suan-ji-zu-jian-yuan-li">计算机组件原理</h2>
|
||||
<ul>
|
||||
<li><a href="https://www.bilibili.com/video/BV1BG4y137mG/">【装机教程】全网最好的装机教程，没有之一</a></li>
|
||||
<li><a href="https://www.bilibili.com/video/BV1xQ4y1b7JS/">从零开始认识主板</a></li>
|
||||
<li><a href="https://www.bilibili.com/video/BV1xE421j7Uv/">从零开始认识显卡</a></li>
|
||||
<li><a href="https://www.bilibili.com/video/BV1Ab411d7zn/">如何合理科学的选择电源功率的大小？</a></li>
|
||||
<li><a href="https://www.bilibili.com/video/BV1Wz411B7Tf/">OLED与LCD屏幕工作原理与优劣科普</a></li>
|
||||
<li><a href="https://www.bilibili.com/video/BV1Me4y1k72b/">LCD OLED QLED mini-LED等显示技术的区别</a></li>
|
||||
<li><a href="https://www.bilibili.com/video/BV1kk4y167rk/">显示器的色域和色准是什么东西？</a></li>
|
||||
<li><a href="https://www.bilibili.com/video/BV1FK4y1x7bk/">Gsync Freesync 垂直同步工作原理科普</a></li>
|
||||
<li><a href="https://www.bilibili.com/video/BV1Ca4y1W73e/">电脑散热器工作原理科普</a></li>
|
||||
<li><a href="https://www.bilibili.com/video/BV1Qv411t7ZL/">硬盘的SATA M.2 NGFF NVME是什么意思，详解硬盘的总线协议与接口</a></li>
|
||||
<li><a href="https://www.bilibili.com/video/BV19T4y1R71r/">键鼠是怎么工作的？8K回报率有意义吗？</a></li>
|
||||
<li><a href="https://www.bilibili.com/video/BV1ca411t7qf/">音响耳机麦克风这些设备是怎么工作的？</a></li>
|
||||
<li><a href="https://www.bilibili.com/video/BV1G94y1g7Up">如何选择存储卡？SD、TF和CFe卡有哪些区别？</a></li>
|
||||
</ul>
|
||||
<h2 id="ji-suan-ji-bo-wu-zhi">计算机博物志</h2>
|
||||
<ul>
|
||||
<li><a href="https://www.bilibili.com/video/BV1qW4y1L7tN/">DES的生与死</a></li>
|
||||
<li><a href="https://www.bilibili.com/video/BV1S541127qR/">MD5为何不再安全</a></li>
|
||||
<li><a href="https://www.bilibili.com/video/BV1DS4y1R7hM/">战争密码（上集）如何复刻一台恩格玛机</a></li>
|
||||
<li><a href="https://www.bilibili.com/video/BV1M34y1o7ca/">战争密码（中集）蝴蝶的翅膀</a></li>
|
||||
<li><a href="https://www.bilibili.com/video/BV1PL4y1H77Z/">战争密码（下集）炸弹机</a></li>
|
||||
<li><a href="https://www.bilibili.com/video/BV1y5411D7a6/">被遗忘的科学天才：沃尔特·皮茨</a></li>
|
||||
<li><a href="https://www.bilibili.com/video/BV11R4y1b7zc/">最后的黑客：理查德·马修·斯托曼</a></li>
|
||||
</ul>
|
||||
<h2 id="ji-suan-ji-ti-xi-jie-gou">计算机体系结构</h2>
|
||||
<ul>
|
||||
<li><a href="https://www.bilibili.com/video/BV1Ct42177Y6/?spm_id_from=333.999.0.0&vd_source=cc4bfbaa0f8c6c363ff9afecce036d91">普林斯顿大学-计算机科学:算法、理论和机器(GPT 翻译)</a></li>
|
||||
<li><a href="https://www.bilibili.com/video/BV1bx421D7Xd/?spm_id_from=333.999.0.0&vd_source=cc4bfbaa0f8c6c363ff9afecce036d91">计算机体系结构（ 2024 年春）</a></li>
|
||||
<li><a href="https://www.bilibili.com/video/BV1VF4m1u7xi/?spm_id_from=333.999.0.0&vd_source=cc4bfbaa0f8c6c363ff9afecce036d91">台湾科技大学:计算机组成 2023-刘一宇</a></li>
|
||||
<li><a href="https://www.bilibili.com/video/BV1ZW4y1w7M6/?spm_id_from=333.999.0.0&vd_source=cc4bfbaa0f8c6c363ff9afecce036d91">国科大:计算机体系结构胡伟武、汪文祥</a></li>
|
||||
<li><a href="https://www.bilibili.com/video/BV1aC4y1X7VF/?spm_id_from=333.999.0.0&vd_source=cc4bfbaa0f8c6c363ff9afecce036d91">CMU15213/15513-2023Spring:深入理解计算机系统(英)</a></li>
|
||||
<li><a href="https://www.bilibili.com/video/BV1964y1j7gk/?spm_id_from=333.999.0.0&vd_source=cc4bfbaa0f8c6c363ff9afecce036d91">UCBerkeley-CS61C:计算机体系结构(GPT 翻译)</a></li>
|
||||
<li><a href="https://www.bilibili.com/video/BV1ua4y1a72K/?spm_id_from=333.999.0.0&vd_source=cc4bfbaa0f8c6c363ff9afecce036d91">Stanford-CS107:计算机组织与系统</a></li>
|
||||
<li><a href="https://www.bilibili.com/video/BV1Zp421y7Ex/?spm_id_from=333.999.0.0&vd_source=cc4bfbaa0f8c6c363ff9afecce036d91">耶路撒冷希伯来大学:从零开始构建现代计算机(GPT 翻译)</a></li>
|
||||
<li><a href="https://space.bilibili.com/91181150/channel/seriesdetail?sid=3700435&ctype=0">威廉玛丽学院:计算机体系结构建模与仿真(英)</a></li>
|
||||
</ul>
|
||||
<h2 id="cao-zuo-xi-tong-ji-suan-ji-zu-cheng">操作系统 /计算机组成</h2>
|
||||
<ul>
|
||||
<li><a href="https://space.bilibili.com/491131440/channel/collectiondetail?sid=146887">操作系统实现</a></li>
|
||||
<li><a href="https://space.bilibili.com/18777618/channel/collectiondetail?sid=801384">操作系统速成-2022 秋冬朋辈辅学录播</a></li>
|
||||
<li><a href="https://space.bilibili.com/354767108/channel/collectiondetail?sid=373847">CSAPP-深入理解计算机系统-讲解</a></li>
|
||||
<li><a href="https://space.bilibili.com/2107852263/channel/collectiondetail?sid=690279">“一生一芯”</a></li>
|
||||
<li><a href="https://space.bilibili.com/28086502/channel/collectiondetail?sid=674585">MIT6.828/6.S081 操作系统课程教程</a></li>
|
||||
<li><a href="https://space.bilibili.com/12995787/channel/collectiondetail?sid=196337">从零开始自制操作系统</a></li>
|
||||
<li><a href="https://space.bilibili.com/202224425/channel/collectiondetail?sid=1116786">2023 南京大学 “操作系统：设计与实现” (蒋炎岩)</a></li>
|
||||
<li><a href="https://space.bilibili.com/40333442/channel/collectiondetail?sid=444904&ctype=0">厦门大学-操作系统原理（ 2022 春）</a></li>
|
||||
<li><a href="https://www.bilibili.com/video/BV1B341117Ez?p=6">现代操作系统：原理与实现（上海交通大学）</a></li>
|
||||
<li><a href="https://www.bilibili.com/video/BV1wv4y1S7xm/">操作系统原理:清华大学陈渝教授</a></li>
|
||||
<li><a href="https://space.bilibili.com/4564101/channel/series">深入理解计算机系统---个人讲解</a></li>
|
||||
<li><a href="https://www.bilibili.com/video/BV1RK4y1R7Kf/">深入理解计算机系统-CSAPP 重点导读</a></li>
|
||||
<li><a href="https://www.bilibili.com/video/BV1hf4y1P7qW/">Dr.Dng 陪跑 CSAPP: bigONE 《深入理解计算机系统》</a></li>
|
||||
<li><a href="https://space.bilibili.com/31359187/channel/seriesdetail?sid=2310084">CS162 操作系统-精译(更新中)</a></li>
|
||||
<li><a href="https://www.bilibili.com/video/BV1nb411K7DT/">台湾清华大学 - 操作系统 Operating Systems - 黄能富教授</a></li>
|
||||
<li><a href="https://www.bilibili.com/video/BV1i2421K7P1?p=2&vd_source=cc4bfbaa0f8c6c363ff9afecce036d91">CS537:操作系统导论 Spring2018(英)</a></li>
|
||||
<li><a href="https://www.bilibili.com/video/BV1iy421q74x/?spm_id_from=333.999.0.0&vd_source=cc4bfbaa0f8c6c363ff9afecce036d91">中山大学:操作系统原理-2024</a></li>
|
||||
<li><a href="https://www.bilibili.com/video/BV1a7411w7tC/?spm_id_from=333.999.0.0&vd_source=cc4bfbaa0f8c6c363ff9afecce036d91">2020 年春季:南京大学计算机系统基础 PA 在线课-汪亮</a></li>
|
||||
<li><a href="https://www.bilibili.com/video/BV1pK4y1C7es/?spm_id_from=333.999.0.0&vd_source=cc4bfbaa0f8c6c363ff9afecce036d91">教你写一个简单的 CPU</a></li>
|
||||
<li><a href="https://www.bilibili.com/video/BV1194y157ku/?spm_id_from=333.999.0.0&vd_source=cc4bfbaa0f8c6c363ff9afecce036d91">台湾大学:信号与系统-李琳山</a></li>
|
||||
<li><a href="https://www.bilibili.com/video/BV1mW421A7Wi/?spm_id_from=333.999.0.0&vd_source=cc4bfbaa0f8c6c363ff9afecce036d91">信号与系统漫谈</a></li>
|
||||
<li><a href="https://www.bilibili.com/video/BV1iA4m137ML/?spm_id_from=333.999.0.0&vd_source=cc4bfbaa0f8c6c363ff9afecce036d91">嵌入式系统-南开大学李庆诚教授-2024 春</a></li>
|
||||
</ul>
|
||||
<h2 id="bian-yi-xiang-guan-ruan-jian-fen-xi">编译相关 /软件分析</h2>
|
||||
<ul>
|
||||
<li><a href="https://space.bilibili.com/2919428/channel/collectiondetail?sid=342930&ctype=0">南京大学《软件分析》课程 2020</a></li>
|
||||
<li><a href="https://space.bilibili.com/296494084/channel/collectiondetail?sid=571708">手写一个 RISC-V 编译器！初学者友好的实战课程</a></li>
|
||||
<li><a href="https://space.bilibili.com/479141149/channel/collectiondetail?sid=837891">南京大学软件学院编译原理课程</a></li>
|
||||
<li><a href="https://www.bilibili.com/video/BV1FA4m1P7kn/?spm_id_from=333.999.0.0&vd_source=cc4bfbaa0f8c6c363ff9afecce036d91">湖南大学:2024 计科拔尖班《编译原理》</a></li>
|
||||
<li><a href="https://www.bilibili.com/video/BV1WC4y1k768/?spm_id_from=333.999.0.0&vd_source=cc4bfbaa0f8c6c363ff9afecce036d91">KAISTCS420:编译器设计 2020Spring(机翻)</a></li>
|
||||
</ul>
|
||||
<h2 id="shu-ju-jie-gou-suan-fa-xiang-guan">数据结构 /算法相关</h2>
|
||||
<ul>
|
||||
<li><a href="https://space.bilibili.com/33807373/channel/collectiondetail?sid=442054&ctype=0">东北大学：2021 ～ 2022 春季学期算法设计与分析</a></li>
|
||||
<li><a href="https://space.bilibili.com/474662253/channel/collectiondetail?sid=1114093">南京大学《 2023 算法设计与分析》- 黄宇</a></li>
|
||||
<li><a href="https://space.bilibili.com/390606417/channel/collectiondetail?sid=1120423">南京大学《 2023 算法设计与分析》- 徐经纬</a></li>
|
||||
<li><a href="https://www.bilibili.com/video/BV1nJ411V7bd/">数据结构与算法基础（青岛大学-王卓）</a></li>
|
||||
<li><a href="https://space.bilibili.com/26340287/channel/collectiondetail?sid=5221">跟懒猫老师快乐学数据结构</a></li>
|
||||
<li><a href="https://www.bilibili.com/video/BV12V4y1Z78b/?spm_id_from=333.999.0.0&vd_source=cc4bfbaa0f8c6c363ff9afecce036d91">香港科技大学:高级算法 & Advanced Algorithms</a></li>
|
||||
</ul>
|
||||
<h2 id="ji-suan-ji-wang-luo">计算机网络</h2>
|
||||
<ul>
|
||||
<li><a href="https://space.bilibili.com/327247876/channel/collectiondetail?sid=60187">计算机网络-通熟易懂讲解每个知识要点</a></li>
|
||||
<li><a href="https://www.bilibili.com/video/BV1JV411t7ow/">中科大郑烇、杨坚全套-计算机网络（自顶向下方法)</a></li>
|
||||
<li><a href="https://www.bilibili.com/video/BV1c4411d7jb/">计算机网络微课堂</a></li>
|
||||
</ul>
|
||||
<h2 id="cheng-xu-yu-yan-bian-cheng-yu-yan">程序语言 /编程语言</h2>
|
||||
<ul>
|
||||
<li><a href="https://space.bilibili.com/283614758/channel/collectiondetail?sid=514109">计算机程序的构造与解释（ SICP, Python 版）</a></li>
|
||||
<li><a href="https://www.bilibili.com/video/BV1xE411N74T/">计算机语言 x86 汇编语言：从实模式到保护模式（操作系统引导课）</a></li>
|
||||
<li><a href="https://space.bilibili.com/1453436642/video">程序语言理论与实现</a></li>
|
||||
<li><a href="https://www.bilibili.com/video/BV1Xx41117tr/">CS 公开课:计算机程序的构造和解释（ SICP ）</a></li>
|
||||
<li><a href="https://www.bilibili.com/video/BV1v64y1Q78o?p=34">精译</a><a href="https://www.bilibili.com/video/BV1v64y1Q78o?p=34">-UC Berkeley 公开课-CS61A [计算机程序的构造和解释] (Spring 2021)</a></li>
|
||||
<li><a href="https://www.bilibili.com/video/BV1hb4y1A71J?p=4&vd_source=cc4bfbaa0f8c6c363ff9afecce036d91">计算机程序的构造和解释 (SICP) Python 版 教程（录制持续更新中）</a></li>
|
||||
</ul>
|
||||
<h2 id="ruan-jian-gong-cheng">软件工程</h2>
|
||||
<ul>
|
||||
<li><a href="https://space.bilibili.com/507030405/channel/seriesdetail?sid=1878983&ctype=0">南京大学-2023 软件工程与计算 I</a></li>
|
||||
<li><a href="https://www.bilibili.com/video/BV15y421h7j7/?spm_id_from=333.999.0.0&vd_source=cc4bfbaa0f8c6c363ff9afecce036d91">2024 Rust 现代实用教程</a></li>
|
||||
</ul>
|
||||
<h2 id="shu-ju-ku">数据库</h2>
|
||||
<ul>
|
||||
<li><a href="https://space.bilibili.com/87476569/channel/collectiondetail?sid=695667">数据库系统（ DBMS ）</a></li>
|
||||
<li><a href="https://space.bilibili.com/31359187/channel/seriesdetail?sid=2310086">CMU15-445-精译(更新中)</a></li>
|
||||
<li><a href="https://www.bilibili.com/video/BV15u4y1Q71R/?spm_id_from=333.999.0.0&vd_source=cc4bfbaa0f8c6c363ff9afecce036d91">清华大学计算机系:数据库管理系统-李国良</a></li>
|
||||
<li><a href="https://space.bilibili.com/23722270/channel/collectiondetail?sid=89600&spm_id_from=333.788.0.0">中文讲解版-CMU15-445:数据库内核</a></li>
|
||||
</ul>
|
||||
<h2 id="bing-xing-cheng-xu-she-ji">并行程序设计</h2>
|
||||
<ul>
|
||||
<li><a href="https://www.bilibili.com/video/BV1XM4y1S7wy?p=5">并行程序设计 谭光明</a></li>
|
||||
<li><a href="https://space.bilibili.com/263032155/channel/collectiondetail?sid=53025">高性能并行编程与优化</a></li>
|
||||
<li><a href="https://www.bilibili.com/video/BV1Yt411W7td/">新竹清华大学：并行计算与并行编程课程</a></li>
|
||||
</ul>
|
||||
<h2 id="mi-ma-xue">密码学</h2>
|
||||
<ul>
|
||||
<li><a href="https://space.bilibili.com/445312136/channel/collectiondetail?sid=988395&spm_id_from=333.788.0.0">分布式密码学:Dora Dōjō x THUBA</a></li>
|
||||
<li><a href="https://www.bilibili.com/video/BV1WL411d7Zi/?spm_id_from=333.999.0.0&vd_source=cc4bfbaa0f8c6c363ff9afecce036d91">新火公开课-密码学基础系列课程</a></li>
|
||||
<li><a href="https://www.bilibili.com/video/BV1Ht411w7Re/?spm_id_from=333.999.0.0&vd_source=cc4bfbaa0f8c6c363ff9afecce036d91">Stanford:密码学(有翻译)</a></li>
|
||||
</ul>
|
||||
<h2 id="gong-ju">工具</h2>
|
||||
<ul>
|
||||
<li><a href="https://space.bilibili.com/171431343/channel/collectiondetail?sid=1213483">浙江大学：「实用技能拾遗」 2023 春夏朋辈辅学</a></li>
|
||||
<li><a href="https://space.bilibili.com/443605967/channel/collectiondetail?sid=266172">Obsidian 公开课</a></li>
|
||||
</ul>
|
||||
<h2 id="qi-ta">其他</h2>
|
||||
<ul>
|
||||
<li>
|
||||
<p><a href="https://www.bilibili.com/video/BV1xa4y1g7sZ/?spm_id_from=333.999.0.0&vd_source=cc4bfbaa0f8c6c363ff9afecce036d91">自制双语字幕-计算机教育缺失的一课(2020)</a></p>
|
||||
</li>
|
||||
<li>
|
||||
<p><a href="https://www.bilibili.com/video/BV1SF4m1u7SU?p=27&vd_source=cc4bfbaa0f8c6c363ff9afecce036d91">CMU15-440:分布式系统(英)</a></p>
|
||||
</li>
|
||||
<li>
|
||||
<p><a href="https://www.bilibili.com/video/BV1Hz4y1c7EZ/?spm_id_from=333.999.0.0&vd_source=cc4bfbaa0f8c6c363ff9afecce036d91">数字电路(对应的 MIT 数电)-UP 主讲解</a></p>
|
||||
</li>
|
||||
<li>
|
||||
<p><a href="https://www.bilibili.com/video/BV1Vt411X7JF/?spm_id_from=333.999.0.0&vd_source=cc4bfbaa0f8c6c363ff9afecce036d91">北京大学肖臻老师《区块链技术与应用》公开课</a></p>
|
||||
</li>
|
||||
<li>
|
||||
<p><a href="https://space.bilibili.com/494117284/channel/series">《智能计算系统-从深度学习到大模型》</a></p>
|
||||
</li>
|
||||
</ul>
|
||||
<h2 id="shu-xue-xiang-guan">数学相关</h2>
|
||||
<ul>
|
||||
<li><a href="https://www.bilibili.com/video/BV1jR4y1M78W/?spm_id_from=333.999.0.0&vd_source=cc4bfbaa0f8c6c363ff9afecce036d91">北大丘维声教授清华高等代数课程 1080P 高清修复版</a></li>
|
||||
<li><a href="https://www.bilibili.com/video/BV1Nr4y1U7qC/?spm_id_from=333.999.0.0&vd_source=cc4bfbaa0f8c6c363ff9afecce036d91">中国科学技术大学-数学分析(B1)-程艺老师</a></li>
|
||||
<li><a href="https://www.bilibili.com/video/BV1T5411P7wi/?spm_id_from=333.999.0.0&vd_source=cc4bfbaa0f8c6c363ff9afecce036d91">北京大学公开课:数学分析（上下全 112 讲无级数部分）</a></li>
|
||||
<li><a href="https://www.bilibili.com/video/BV1bi4y1K7vn/?spm_id_from=333.999.0.0&vd_source=cc4bfbaa0f8c6c363ff9afecce036d91">复变函数(复分析) [中英双字] 已完结</a></li>
|
||||
<li><a href="https://www.bilibili.com/video/BV1sX4y1Y7jH/?spm_id_from=333.999.0.0&vd_source=cc4bfbaa0f8c6c363ff9afecce036d91">数学分析陈纪修无障碍重制版</a></li>
|
||||
<li><a href="https://www.bilibili.com/video/BV1fK411K7MA/?spm_id_from=333.999.0.0&vd_source=cc4bfbaa0f8c6c363ff9afecce036d91">2020 齐震宇老师微積分 02 班</a></li>
|
||||
<li><a href="https://www.bilibili.com/video/BV1mJ411r7ZB/?spm_id_from=333.999.0.0&vd_source=cc4bfbaa0f8c6c363ff9afecce036d91">高等代数学-复旦大学-谢启鸿-高清</a></li>
|
||||
<li><a href="https://www.bilibili.com/video/BV1d7411v7zu/?spm_id_from=333.999.0.0&vd_source=cc4bfbaa0f8c6c363ff9afecce036d91">离散数学-东北大学</a></li>
|
||||
<li><a href="https://space.bilibili.com/610062295/channel/seriesdetail?sid=2558242&ctype=0">统计学-个人 UP 主</a></li>
|
||||
</ul>
|
||||
<h2 id="zhe-xue-xiang-guan">哲学相关</h2>
|
||||
<ul>
|
||||
<li><a href="https://www.bilibili.com/video/BV1y64y1r7Mt/?spm_id_from=333.337.search-card.all.click&vd_source=cc4bfbaa0f8c6c363ff9afecce036d91">中国人民大学:西方哲学史-张志伟</a></li>
|
||||
<li><a href="https://www.bilibili.com/video/BV1hp4y1p7ye/?spm_id_from=333.999.0.0&vd_source=cc4bfbaa0f8c6c363ff9afecce036d91">赵林、邓晓芒-西方哲学史(旧版)</a></li>
|
||||
<li><a href="https://www.bilibili.com/video/BV19u4y1s7ug/?spm_id_from=333.999.0.0&vd_source=cc4bfbaa0f8c6c363ff9afecce036d91">台湾大学:逻辑学-傅皓政</a></li>
|
||||
<li><a href="https://www.bilibili.com/video/BV1tt411h7TT/?spm_id_from=333.999.0.0&vd_source=cc4bfbaa0f8c6c363ff9afecce036d91">康德专题研究-邓晓芒</a></li>
|
||||
<li><a href="https://www.bilibili.com/video/BV1P54y1G7EW/?spm_id_from=333.999.0.0&vd_source=cc4bfbaa0f8c6c363ff9afecce036d91">劳动关系学院:美学原理-2021 年春-杨宁</a></li>
|
||||
<li><a href="https://www.bilibili.com/video/BV1aZ4y167bp/?spm_id_from=333.999.0.0&vd_source=cc4bfbaa0f8c6c363ff9afecce036d91">符号学入门</a></li>
|
||||
</ul>
|
||||
<h2 id="ren-wen-yi-shu-jian-zhu-dian-ying-she-hui-xue">人文/艺术/建筑/电影/社会学</h2>
|
||||
<ul>
|
||||
<li><a href="https://www.bilibili.com/video/BV1D7411D7h4/?spm_id_from=333.999.0.0&vd_source=cc4bfbaa0f8c6c363ff9afecce036d91"> MIT全球建筑史（ 4.605 A Global History of Architecture ）（英文）</a></li>
|
||||
<li><a href="https://www.bilibili.com/video/BV1FL4y1e7nt/?spm_id_from=333.999.0.0&vd_source=cc4bfbaa0f8c6c363ff9afecce036d91">现代社会理论基础-中英字幕</a></li>
|
||||
<li><a href="https://www.bilibili.com/video/BV1Ti42117sw/?spm_id_from=333.999.0.0&vd_source=cc4bfbaa0f8c6c363ff9afecce036d91">中英双字-艺术史速成课</a></li>
|
||||
<li><a href="https://space.bilibili.com/477533700/channel/collectiondetail?sid=1737877&spm_id_from=333.788.0.0">贡布里希《艺术的故事》视频解说版</a></li>
|
||||
<li><a href="https://space.bilibili.com/386246830/channel/collectiondetail?sid=1837138&spm_id_from=333.788.0.0">摄影指导公开课-VFS/北电毕业生</a></li>
|
||||
<li><a href="https://space.bilibili.com/386246830/channel/collectiondetail?sid=1871554">导演公开课-北电/VFS 毕业生</a></li>
|
||||
<li><a href="https://www.bilibili.com/video/BV1EG4y187wq/?spm_id_from=333.999.0.0&vd_source=cc4bfbaa0f8c6c363ff9afecce036d91">劳动关系学院:文学理论-2021 年秋-杨宁</a></li>
|
||||
<li><a href="https://www.bilibili.com/video/BV1sR4y1W77y/?spm_id_from=333.999.0.0&vd_source=cc4bfbaa0f8c6c363ff9afecce036d91">劳动关系学院:西方文论-2021 年秋-杨宁</a></li>
|
||||
<li><a href="https://www.bilibili.com/video/BV1as411M7DG/?spm_id_from=333.999.0.0">周传基讲电影</a></li>
|
||||
</ul>
|
||||
<h2 id="zong-he">综合</h2>
|
||||
<ul>
|
||||
<li><a href="https://space.bilibili.com/479038960/channel/collectiondetail?sid=997541">精读 c++primer</a></li>
|
||||
<li><a href="https://space.bilibili.com/1268065381/channel/collectiondetail?sid=1163347">计算机图形学游戏方向-2023 年春季第 2 次迭代-谭剑</a></li>
|
||||
<li><a href="https://space.bilibili.com/1356949475/channel/collectiondetail?sid=1211802">Linux 文件系统九讲-陈硕</a></li>
|
||||
<li><a href="https://space.bilibili.com/30933812/channel/collectiondetail?sid=240551">DDIA 读书逐章分享</a></li>
|
||||
<li><a href="https://www.bilibili.com/video/BV1aE411o7qd/">机器学习-白板推导系列</a></li>
|
||||
<li><a href="https://space.bilibili.com/395471891/channel/collectiondetail?sid=1213523">陈明-南京大学 23 春-面向对象编程基础</a></li>
|
||||
<li><a href="https://www.bilibili.com/video/BV1Xy4y1b7SK/">每个程序员都应该知道的内存知识 (带你走读 Ulrich Drepper 的经典论文)</a></li>
|
||||
</ul>
|
||||
<h2 id="hou-ji">后记</h2>
|
||||
<p>待续...</p>
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
<div class="pagination">
|
||||
<div class="pagination__title">
|
||||
<span class="pagination__title-h">Thanks for reading! Read other posts?</span>
|
||||
<hr />
|
||||
</div>
|
||||
<div class="pagination__buttons">
|
||||
<span class="button previous">
|
||||
<a href="https://blog.dich.bid/windows-conda-python/">
|
||||
<span class="button__icon">←</span>
|
||||
<span class="button__text">乱七八糟:Windows-Jupyter开发Python</span>
|
||||
</a>
|
||||
</span>
|
||||
|
||||
|
||||
<span class="button next">
|
||||
<a href="https://blog.dich.bid/about-runer-1/">
|
||||
<span class="button__text">乱七八糟:跑步笔记(一)</span>
|
||||
<span class="button__icon">→</span>
|
||||
</a>
|
||||
</span>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
</div>
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
<footer class="footer">
|
||||
<div class="footer__inner">
|
||||
<div class="copyright">
|
||||
<span>©
|
||||
2025
|
||||
Dichgrem</span>
|
||||
<span class="copyright-theme">
|
||||
<span class="copyright-theme-sep"> :: CC BY-SA 4.0 :: A friend comes from distant lands</span>
|
||||
</a>
|
||||
</span>
|
||||
</div>
|
||||
</div>
|
||||
</footer>
|
||||
|
||||
</div>
|
||||
</body>
|
||||
</html>
|
||||
|
||||
530
public/about-frp/index.html
Normal file
530
public/about-frp/index.html
Normal file
@ -0,0 +1,530 @@
|
||||
<!DOCTYPE html>
|
||||
<html lang="en">
|
||||
|
||||
<head>
|
||||
<title>Dich'blog</title>
|
||||
|
||||
<meta http-equiv="content-type" content="text/html; charset=utf-8">
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1">
|
||||
<meta name="robots" content="noodp"/>
|
||||
|
||||
<link rel="stylesheet" href="https://blog.dich.bid/style.css">
|
||||
<link rel="stylesheet" href="https://blog.dich.bid/color/blue.css">
|
||||
|
||||
<link rel="stylesheet" href="https://blog.dich.bid/color/background_dark.css">
|
||||
|
||||
<link rel="stylesheet" href="https://blog.dich.bid/font-hack-subset.css">
|
||||
|
||||
<meta name="description" content="">
|
||||
|
||||
<meta property="og:description" content="">
|
||||
<meta property="og:title" content="Dich'blog">
|
||||
<meta property="og:type" content="article">
|
||||
<meta property="og:url" content="https://blog.dich.bid/about-frp/">
|
||||
|
||||
<meta name="twitter:card" content="summary_large_image">
|
||||
<meta name="twitter:description" content="">
|
||||
<meta name="twitter:title" content="Dich'blog">
|
||||
<meta property="twitter:domain" content="blog.dich.bid">
|
||||
<meta property="twitter:url" content="https://blog.dich.bid/about-frp/">
|
||||
|
||||
<link rel="alternate" type="application/atom+xml" title="Dich'blog Atom Feed" href="https://blog.dich.bid/atom.xml" />
|
||||
|
||||
|
||||
<link rel="icon" type="image/png" href=/dich.webp />
|
||||
|
||||
<!-- ✅ Added center alignment styles -->
|
||||
<style>
|
||||
.footer {
|
||||
text-align: center;
|
||||
padding: 1rem 0;
|
||||
}
|
||||
|
||||
.footer__inner {
|
||||
display: flex;
|
||||
justify-content: center;
|
||||
flex-direction: column;
|
||||
align-items: center;
|
||||
}
|
||||
|
||||
.copyright {
|
||||
text-align: center;
|
||||
}
|
||||
</style>
|
||||
</head>
|
||||
|
||||
<body class="">
|
||||
<div class="container">
|
||||
|
||||
<header class="header">
|
||||
<div class="header__inner">
|
||||
<div class="header__logo">
|
||||
|
||||
<a href="https://blog.dich.bid" style="text-decoration: none;">
|
||||
<div class="logo">
|
||||
|
||||
Dich'blog
|
||||
|
||||
</div>
|
||||
</a>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
|
||||
<nav class="menu">
|
||||
<ul class="menu__inner">
|
||||
<li><a href="https://blog.dich.bid">blog</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/archive">archive</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/tags">tags</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/weekly">weekly</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/search">search</a></li>
|
||||
|
||||
<li class="active"><a href="https://blog.dich.bid/about">about me</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/links">links</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/atom.xml">rss</a></li>
|
||||
|
||||
<li><a href="https://github.com/Dichgrem" target="_blank" rel="noopener noreferrer">github</a></li>
|
||||
</ul>
|
||||
</nav>
|
||||
|
||||
|
||||
|
||||
</header>
|
||||
|
||||
|
||||
<div class="content">
|
||||
|
||||
<div class="post">
|
||||
|
||||
<h1 class="post-title"><a href="https://blog.dich.bid/about-frp/">乱七八糟:FRP使用指南</a></h1>
|
||||
<div class="post-meta-inline">
|
||||
|
||||
<span class="post-date">
|
||||
2025-03-01
|
||||
</span>
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
<span class="post-tags-inline">
|
||||
:: tags:
|
||||
<a class="post-tag" href="https://blog.dich.bid/tags/luan-qi-ba-zao/">#乱七八糟</a></span>
|
||||
|
||||
|
||||
<div class="post-content">
|
||||
<p>前言 FRP (Fast Reverse Proxy) 是一个用Go语言开发的高性能反向代理应用，可以帮助您轻松地进行内网穿透，对外提供服务.</p>
|
||||
<span id="continue-reading"></span><h2 id="jian-jie">简介</h2>
|
||||
<p>FRP (Fast Reverse Proxy) 主要功能包括：</p>
|
||||
<ul>
|
||||
<li>支持TCP、UDP、HTTP、HTTPS等多种协议</li>
|
||||
<li>支持Web服务、远程桌面、SSH、游戏服务器等多种应用场景</li>
|
||||
<li>提供加密和压缩功能，保证数据安全性</li>
|
||||
<li>支持多个客户端连接服务端，适用于复杂网络环境</li>
|
||||
</ul>
|
||||
<p>FRP分为客户端(frpc)和服务端(frps)两部分：</p>
|
||||
<ul>
|
||||
<li><strong>服务端(frps)</strong>: 部署在有公网IP的服务器上</li>
|
||||
<li><strong>客户端(frpc)</strong>: 部署在内网机器上，负责将内网服务映射到公网</li>
|
||||
</ul>
|
||||
<h2 id="an-zhuang">安装</h2>
|
||||
<h3 id="fu-wu-duan-an-zhuang">服务端安装</h3>
|
||||
<p>服务端需要部署在具有公网IP的服务器上。</p>
|
||||
<ol>
|
||||
<li>下载最新版本的FRP发行包：</li>
|
||||
</ol>
|
||||
<pre data-lang="bash" style="background-color:#151515;color:#e8e8d3;" class="language-bash "><code class="language-bash" data-lang="bash"><span style="color:#ffb964;">wget</span><span> https://github.com/fatedier/frp/releases/download/v0.51.3/frp_0.51.3_linux_amd64.tar.gz
|
||||
</span></code></pre>
|
||||
<ol start="2">
|
||||
<li>解压文件：</li>
|
||||
</ol>
|
||||
<pre data-lang="bash" style="background-color:#151515;color:#e8e8d3;" class="language-bash "><code class="language-bash" data-lang="bash"><span style="color:#ffb964;">tar -xzvf</span><span> frp_0.51.3_linux_amd64.tar.gz
|
||||
</span><span>cd frp_0.51.3_linux_amd64
|
||||
</span></code></pre>
|
||||
<ol start="3">
|
||||
<li>现在您可以看到以下文件：
|
||||
<ul>
|
||||
<li>frps: 服务端可执行文件</li>
|
||||
<li>frps.ini: 服务端配置文件</li>
|
||||
<li>frpc: 客户端可执行文件</li>
|
||||
<li>frpc.ini: 客户端配置文件</li>
|
||||
</ul>
|
||||
</li>
|
||||
</ol>
|
||||
<h3 id="ke-hu-duan-an-zhuang">客户端安装</h3>
|
||||
<p>客户端需要安装在您的内网设备上，例如需要提供服务的电脑、服务器或IoT设备上。</p>
|
||||
<ul>
|
||||
<li>Linux/macOS</li>
|
||||
</ul>
|
||||
<p>与服务端安装步骤相同，只需使用frpc程序和frpc.ini配置文件。</p>
|
||||
<ul>
|
||||
<li>Windows</li>
|
||||
</ul>
|
||||
<p>同样下载Windows版本，解压后使用frpc.exe和frpc.ini。</p>
|
||||
<h2 id="pei-zhi">配置</h2>
|
||||
<h3 id="fu-wu-duan-pei-zhi">服务端配置</h3>
|
||||
<p>服务端配置文件为frps.ini，基本配置如下：</p>
|
||||
<pre data-lang="ini" style="background-color:#151515;color:#e8e8d3;" class="language-ini "><code class="language-ini" data-lang="ini"><span style="color:#8fbfdc;">[common]
|
||||
</span><span style="color:#888888;"># 服务端监听端口，用于与客户端建立连接
|
||||
</span><span style="color:#ffb964;">bind_port </span><span>= </span><span style="color:#cf6a4c;">7000
|
||||
</span><span>
|
||||
</span><span style="color:#888888;"># 用于身份验证的token
|
||||
</span><span style="color:#ffb964;">token </span><span>= yourSecureToken
|
||||
</span><span>
|
||||
</span><span style="color:#888888;"># 后台管理页面端口（可选）
|
||||
</span><span style="color:#ffb964;">dashboard_port </span><span>= </span><span style="color:#cf6a4c;">7500
|
||||
</span><span style="color:#ffb964;">dashboard_user </span><span>= admin
|
||||
</span><span style="color:#ffb964;">dashboard_pwd </span><span>= admin
|
||||
</span><span>
|
||||
</span><span style="color:#888888;"># 日志配置
|
||||
</span><span style="color:#ffb964;">log_file </span><span>= /var/log/frps.log
|
||||
</span><span style="color:#ffb964;">log_level </span><span>= info
|
||||
</span><span style="color:#ffb964;">log_max_days </span><span>= </span><span style="color:#cf6a4c;">3
|
||||
</span></code></pre>
|
||||
<h3 id="ke-hu-duan-pei-zhi">客户端配置</h3>
|
||||
<p>客户端配置文件为frpc.ini，基本配置如下：</p>
|
||||
<pre data-lang="ini" style="background-color:#151515;color:#e8e8d3;" class="language-ini "><code class="language-ini" data-lang="ini"><span style="color:#8fbfdc;">[common]
|
||||
</span><span style="color:#888888;"># 服务端的IP地址或域名
|
||||
</span><span style="color:#ffb964;">server_addr </span><span>= x.x.x.x
|
||||
</span><span style="color:#888888;"># 服务端的端口
|
||||
</span><span style="color:#ffb964;">server_port </span><span>= </span><span style="color:#cf6a4c;">7000
|
||||
</span><span style="color:#888888;"># 认证token，需要与服务端匹配
|
||||
</span><span style="color:#ffb964;">token </span><span>= yourSecureToken
|
||||
</span><span>
|
||||
</span><span style="color:#888888;"># 示例：SSH服务代理
|
||||
</span><span style="color:#8fbfdc;">[ssh]
|
||||
</span><span style="color:#ffb964;">type </span><span>= tcp
|
||||
</span><span style="color:#ffb964;">local_ip </span><span>= </span><span style="color:#7697d6;">127.0.0.1
|
||||
</span><span style="color:#ffb964;">local_port </span><span>= </span><span style="color:#cf6a4c;">22
|
||||
</span><span style="color:#ffb964;">remote_port </span><span>= </span><span style="color:#cf6a4c;">6000
|
||||
</span><span>
|
||||
</span><span style="color:#888888;"># 示例：HTTP服务代理
|
||||
</span><span style="color:#8fbfdc;">[web]
|
||||
</span><span style="color:#ffb964;">type </span><span>= http
|
||||
</span><span style="color:#ffb964;">local_ip </span><span>= </span><span style="color:#7697d6;">127.0.0.1
|
||||
</span><span style="color:#ffb964;">local_port </span><span>= </span><span style="color:#cf6a4c;">80
|
||||
</span><span style="color:#ffb964;">custom_domains </span><span>= www.yourdomain.com
|
||||
</span></code></pre>
|
||||
<h3 id="chang-yong-pei-zhi-shi-li">常用配置示例</h3>
|
||||
<h4 id="1-dai-li-sshfu-wu">1. 代理SSH服务</h4>
|
||||
<pre data-lang="ini" style="background-color:#151515;color:#e8e8d3;" class="language-ini "><code class="language-ini" data-lang="ini"><span style="color:#888888;"># frpc.ini
|
||||
</span><span style="color:#8fbfdc;">[common]
|
||||
</span><span style="color:#ffb964;">server_addr </span><span>= x.x.x.x
|
||||
</span><span style="color:#ffb964;">server_port </span><span>= </span><span style="color:#cf6a4c;">7000
|
||||
</span><span style="color:#ffb964;">token </span><span>= yourSecureToken
|
||||
</span><span>
|
||||
</span><span style="color:#8fbfdc;">[ssh]
|
||||
</span><span style="color:#ffb964;">type </span><span>= tcp
|
||||
</span><span style="color:#ffb964;">local_ip </span><span>= </span><span style="color:#7697d6;">127.0.0.1
|
||||
</span><span style="color:#ffb964;">local_port </span><span>= </span><span style="color:#cf6a4c;">22
|
||||
</span><span style="color:#ffb964;">remote_port </span><span>= </span><span style="color:#cf6a4c;">6000
|
||||
</span></code></pre>
|
||||
<p>使用方法：<code>ssh -p 6000 username@服务端IP</code></p>
|
||||
<h4 id="2-dai-li-httpwang-zhan">2. 代理HTTP网站</h4>
|
||||
<pre data-lang="ini" style="background-color:#151515;color:#e8e8d3;" class="language-ini "><code class="language-ini" data-lang="ini"><span style="color:#888888;"># frpc.ini
|
||||
</span><span style="color:#8fbfdc;">[common]
|
||||
</span><span style="color:#ffb964;">server_addr </span><span>= x.x.x.x
|
||||
</span><span style="color:#ffb964;">server_port </span><span>= </span><span style="color:#cf6a4c;">7000
|
||||
</span><span style="color:#ffb964;">token </span><span>= yourSecureToken
|
||||
</span><span>
|
||||
</span><span style="color:#8fbfdc;">[web]
|
||||
</span><span style="color:#ffb964;">type </span><span>= http
|
||||
</span><span style="color:#ffb964;">local_ip </span><span>= </span><span style="color:#7697d6;">127.0.0.1
|
||||
</span><span style="color:#ffb964;">local_port </span><span>= </span><span style="color:#cf6a4c;">80
|
||||
</span><span style="color:#ffb964;">custom_domains </span><span>= www.yourdomain.com
|
||||
</span></code></pre>
|
||||
<p>在服务端需要将域名解析到服务端IP。</p>
|
||||
<h4 id="3-dai-li-httpswang-zhan">3. 代理HTTPS网站</h4>
|
||||
<pre data-lang="ini" style="background-color:#151515;color:#e8e8d3;" class="language-ini "><code class="language-ini" data-lang="ini"><span style="color:#888888;"># frpc.ini
|
||||
</span><span style="color:#8fbfdc;">[common]
|
||||
</span><span style="color:#ffb964;">server_addr </span><span>= x.x.x.x
|
||||
</span><span style="color:#ffb964;">server_port </span><span>= </span><span style="color:#cf6a4c;">7000
|
||||
</span><span style="color:#ffb964;">token </span><span>= yourSecureToken
|
||||
</span><span>
|
||||
</span><span style="color:#8fbfdc;">[web-https]
|
||||
</span><span style="color:#ffb964;">type </span><span>= https
|
||||
</span><span style="color:#ffb964;">local_ip </span><span>= </span><span style="color:#7697d6;">127.0.0.1
|
||||
</span><span style="color:#ffb964;">local_port </span><span>= </span><span style="color:#cf6a4c;">443
|
||||
</span><span style="color:#ffb964;">custom_domains </span><span>= www.yourdomain.com
|
||||
</span></code></pre>
|
||||
<h4 id="4-dai-li-yuan-cheng-zhuo-mian-rdp">4. 代理远程桌面(RDP)</h4>
|
||||
<pre data-lang="ini" style="background-color:#151515;color:#e8e8d3;" class="language-ini "><code class="language-ini" data-lang="ini"><span style="color:#888888;"># frpc.ini
|
||||
</span><span style="color:#8fbfdc;">[common]
|
||||
</span><span style="color:#ffb964;">server_addr </span><span>= x.x.x.x
|
||||
</span><span style="color:#ffb964;">server_port </span><span>= </span><span style="color:#cf6a4c;">7000
|
||||
</span><span style="color:#ffb964;">token </span><span>= yourSecureToken
|
||||
</span><span>
|
||||
</span><span style="color:#8fbfdc;">[rdp]
|
||||
</span><span style="color:#ffb964;">type </span><span>= tcp
|
||||
</span><span style="color:#ffb964;">local_ip </span><span>= </span><span style="color:#7697d6;">127.0.0.1
|
||||
</span><span style="color:#ffb964;">local_port </span><span>= </span><span style="color:#cf6a4c;">3389
|
||||
</span><span style="color:#ffb964;">remote_port </span><span>= </span><span style="color:#cf6a4c;">7001
|
||||
</span></code></pre>
|
||||
<h2 id="qi-dong-yu-yun-xing">启动与运行</h2>
|
||||
<h3 id="fu-wu-duan-qi-dong">服务端启动</h3>
|
||||
<h4 id="linux-macos">Linux/macOS</h4>
|
||||
<pre data-lang="bash" style="background-color:#151515;color:#e8e8d3;" class="language-bash "><code class="language-bash" data-lang="bash"><span style="color:#ffb964;">./frps -c</span><span> frps.ini
|
||||
</span></code></pre>
|
||||
<p>后台运行：</p>
|
||||
<pre data-lang="bash" style="background-color:#151515;color:#e8e8d3;" class="language-bash "><code class="language-bash" data-lang="bash"><span style="color:#ffb964;">nohup</span><span> ./frps</span><span style="color:#ffb964;"> -c</span><span> frps.ini &
|
||||
</span></code></pre>
|
||||
<h4 id="windows">Windows</h4>
|
||||
<p>双击frps.exe或在命令行运行：</p>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>frps.exe -c frps.ini
|
||||
</span></code></pre>
|
||||
<h3 id="ke-hu-duan-qi-dong">客户端启动</h3>
|
||||
<h4 id="linux-macos-1">Linux/macOS</h4>
|
||||
<pre data-lang="bash" style="background-color:#151515;color:#e8e8d3;" class="language-bash "><code class="language-bash" data-lang="bash"><span style="color:#ffb964;">./frpc -c</span><span> frpc.ini
|
||||
</span></code></pre>
|
||||
<p>后台运行：</p>
|
||||
<pre data-lang="bash" style="background-color:#151515;color:#e8e8d3;" class="language-bash "><code class="language-bash" data-lang="bash"><span style="color:#ffb964;">nohup</span><span> ./frpc</span><span style="color:#ffb964;"> -c</span><span> frpc.ini &
|
||||
</span></code></pre>
|
||||
<h4 id="windows-1">Windows</h4>
|
||||
<p>双击frpc.exe或在命令行运行：</p>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>frpc.exe -c frpc.ini
|
||||
</span></code></pre>
|
||||
<h3 id="she-zhi-wei-xi-tong-fu-wu">设置为系统服务</h3>
|
||||
<h4 id="linux-systemd">Linux (Systemd)</h4>
|
||||
<ol>
|
||||
<li>创建服务文件 <code>/etc/systemd/system/frps.service</code> (服务端) 或 <code>/etc/systemd/system/frpc.service</code> (客户端)</li>
|
||||
</ol>
|
||||
<p><strong>服务端示例 (frps.service):</strong></p>
|
||||
<pre data-lang="ini" style="background-color:#151515;color:#e8e8d3;" class="language-ini "><code class="language-ini" data-lang="ini"><span style="color:#8fbfdc;">[Unit]
|
||||
</span><span style="color:#ffb964;">Description</span><span>=Frp Server Service
|
||||
</span><span style="color:#ffb964;">After</span><span>=network.target
|
||||
</span><span>
|
||||
</span><span style="color:#8fbfdc;">[Service]
|
||||
</span><span style="color:#ffb964;">Type</span><span>=simple
|
||||
</span><span style="color:#ffb964;">ExecStart</span><span>=/usr/bin/frps -c /etc/frps/frps.ini
|
||||
</span><span style="color:#ffb964;">Restart</span><span>=always
|
||||
</span><span style="color:#ffb964;">RestartSec</span><span>=</span><span style="color:#cf6a4c;">5s
|
||||
</span><span>
|
||||
</span><span style="color:#8fbfdc;">[Install]
|
||||
</span><span style="color:#ffb964;">WantedBy</span><span>=multi-user.target
|
||||
</span></code></pre>
|
||||
<p><strong>客户端示例 (frpc.service):</strong></p>
|
||||
<pre data-lang="ini" style="background-color:#151515;color:#e8e8d3;" class="language-ini "><code class="language-ini" data-lang="ini"><span style="color:#8fbfdc;">[Unit]
|
||||
</span><span style="color:#ffb964;">Description</span><span>=Frp Client Service
|
||||
</span><span style="color:#ffb964;">After</span><span>=network.target
|
||||
</span><span>
|
||||
</span><span style="color:#8fbfdc;">[Service]
|
||||
</span><span style="color:#ffb964;">Type</span><span>=simple
|
||||
</span><span style="color:#ffb964;">ExecStart</span><span>=/usr/bin/frpc -c /etc/frpc/frpc.ini
|
||||
</span><span style="color:#ffb964;">Restart</span><span>=always
|
||||
</span><span style="color:#ffb964;">RestartSec</span><span>=</span><span style="color:#cf6a4c;">5s
|
||||
</span><span>
|
||||
</span><span style="color:#8fbfdc;">[Install]
|
||||
</span><span style="color:#ffb964;">WantedBy</span><span>=multi-user.target
|
||||
</span></code></pre>
|
||||
<ol start="2">
|
||||
<li>启用并启动服务:</li>
|
||||
</ol>
|
||||
<pre data-lang="bash" style="background-color:#151515;color:#e8e8d3;" class="language-bash "><code class="language-bash" data-lang="bash"><span style="color:#888888;"># 服务端
|
||||
</span><span style="color:#ffb964;">sudo</span><span> systemctl enable frps
|
||||
</span><span style="color:#ffb964;">sudo</span><span> systemctl start frps
|
||||
</span><span>
|
||||
</span><span style="color:#888888;"># 客户端
|
||||
</span><span style="color:#ffb964;">sudo</span><span> systemctl enable frpc
|
||||
</span><span style="color:#ffb964;">sudo</span><span> systemctl start frpc
|
||||
</span></code></pre>
|
||||
<ol start="3">
|
||||
<li>查看服务状态:</li>
|
||||
</ol>
|
||||
<pre data-lang="bash" style="background-color:#151515;color:#e8e8d3;" class="language-bash "><code class="language-bash" data-lang="bash"><span style="color:#ffb964;">sudo</span><span> systemctl status frps
|
||||
</span><span style="color:#888888;"># 或
|
||||
</span><span style="color:#ffb964;">sudo</span><span> systemctl status frpc
|
||||
</span></code></pre>
|
||||
<h4 id="windows-2">Windows</h4>
|
||||
<ol>
|
||||
<li>使用NSSM (Non-Sucking Service Manager) 创建服务:
|
||||
<ul>
|
||||
<li>下载NSSM: http://nssm.cc/download</li>
|
||||
<li>安装服务:<pre style="background-color:#151515;color:#e8e8d3;"><code><span>nssm.exe install frpc C:\path\to\frpc.exe -c C:\path\to\frpc.ini
|
||||
</span></code></pre>
|
||||
</li>
|
||||
<li>启动服务:<pre style="background-color:#151515;color:#e8e8d3;"><code><span>nssm.exe start frpc
|
||||
</span></code></pre>
|
||||
</li>
|
||||
</ul>
|
||||
</li>
|
||||
</ol>
|
||||
<h2 id="jin-jie-gong-neng">进阶功能</h2>
|
||||
<h3 id="httpszhi-chi">HTTPS支持</h3>
|
||||
<p>要支持HTTPS服务，需要在服务端添加配置：</p>
|
||||
<pre data-lang="ini" style="background-color:#151515;color:#e8e8d3;" class="language-ini "><code class="language-ini" data-lang="ini"><span style="color:#888888;"># frps.ini
|
||||
</span><span style="color:#8fbfdc;">[common]
|
||||
</span><span style="color:#ffb964;">bind_port </span><span>= </span><span style="color:#cf6a4c;">7000
|
||||
</span><span style="color:#ffb964;">vhost_https_port </span><span>= </span><span style="color:#cf6a4c;">443
|
||||
</span></code></pre>
|
||||
<p>客户端配置：</p>
|
||||
<pre data-lang="ini" style="background-color:#151515;color:#e8e8d3;" class="language-ini "><code class="language-ini" data-lang="ini"><span style="color:#888888;"># frpc.ini
|
||||
</span><span style="color:#8fbfdc;">[web]
|
||||
</span><span style="color:#ffb964;">type </span><span>= https
|
||||
</span><span style="color:#ffb964;">local_ip </span><span>= </span><span style="color:#7697d6;">127.0.0.1
|
||||
</span><span style="color:#ffb964;">local_port </span><span>= </span><span style="color:#cf6a4c;">443
|
||||
</span><span style="color:#ffb964;">custom_domains </span><span>= www.yourdomain.com
|
||||
</span></code></pre>
|
||||
<h3 id="duo-lu-fu-yong">多路复用</h3>
|
||||
<p>使用多路复用可以减少连接数，提高性能：</p>
|
||||
<pre data-lang="ini" style="background-color:#151515;color:#e8e8d3;" class="language-ini "><code class="language-ini" data-lang="ini"><span style="color:#888888;"># frpc.ini
|
||||
</span><span style="color:#8fbfdc;">[common]
|
||||
</span><span style="color:#ffb964;">server_addr </span><span>= x.x.x.x
|
||||
</span><span style="color:#ffb964;">server_port </span><span>= </span><span style="color:#cf6a4c;">7000
|
||||
</span><span style="color:#ffb964;">token </span><span>= yourSecureToken
|
||||
</span><span style="color:#888888;"># 启用多路复用
|
||||
</span><span style="color:#ffb964;">tls_enable </span><span>= true
|
||||
</span><span style="color:#ffb964;">pool_count </span><span>= </span><span style="color:#cf6a4c;">5
|
||||
</span></code></pre>
|
||||
<h3 id="jia-mi-yu-ya-suo">加密与压缩</h3>
|
||||
<p>增加数据传输的安全性：</p>
|
||||
<pre data-lang="ini" style="background-color:#151515;color:#e8e8d3;" class="language-ini "><code class="language-ini" data-lang="ini"><span style="color:#888888;"># frpc.ini
|
||||
</span><span style="color:#8fbfdc;">[common]
|
||||
</span><span style="color:#ffb964;">server_addr </span><span>= x.x.x.x
|
||||
</span><span style="color:#ffb964;">server_port </span><span>= </span><span style="color:#cf6a4c;">7000
|
||||
</span><span style="color:#ffb964;">token </span><span>= yourSecureToken
|
||||
</span><span style="color:#888888;"># 启用加密和压缩
|
||||
</span><span style="color:#ffb964;">use_encryption </span><span>= true
|
||||
</span><span style="color:#ffb964;">use_compression </span><span>= true
|
||||
</span></code></pre>
|
||||
<h3 id="fu-zai-jun-heng">负载均衡</h3>
|
||||
<p>通过配置多个后端服务实现负载均衡：</p>
|
||||
<pre data-lang="ini" style="background-color:#151515;color:#e8e8d3;" class="language-ini "><code class="language-ini" data-lang="ini"><span style="color:#888888;"># frpc.ini
|
||||
</span><span style="color:#8fbfdc;">[web]
|
||||
</span><span style="color:#ffb964;">type </span><span>= tcp
|
||||
</span><span style="color:#ffb964;">local_ip </span><span>= </span><span style="color:#7697d6;">127.0.0.1
|
||||
</span><span style="color:#ffb964;">local_port </span><span>= </span><span style="color:#cf6a4c;">80
|
||||
</span><span style="color:#ffb964;">remote_port </span><span>= </span><span style="color:#cf6a4c;">8080
|
||||
</span><span style="color:#ffb964;">group </span><span>= web
|
||||
</span><span style="color:#ffb964;">group_key </span><span>= </span><span style="color:#cf6a4c;">123456
|
||||
</span><span>
|
||||
</span><span style="color:#8fbfdc;">[web2]
|
||||
</span><span style="color:#ffb964;">type </span><span>= tcp
|
||||
</span><span style="color:#ffb964;">local_ip </span><span>= </span><span style="color:#7697d6;">127.0.0.1
|
||||
</span><span style="color:#ffb964;">local_port </span><span>= </span><span style="color:#cf6a4c;">8081
|
||||
</span><span style="color:#ffb964;">remote_port </span><span>= </span><span style="color:#cf6a4c;">8080
|
||||
</span><span style="color:#ffb964;">group </span><span>= web
|
||||
</span><span style="color:#ffb964;">group_key </span><span>= </span><span style="color:#cf6a4c;">123456
|
||||
</span></code></pre>
|
||||
<h3 id="fang-wen-kong-zhi">访问控制</h3>
|
||||
<p>限制客户端连接数量和带宽：</p>
|
||||
<pre data-lang="ini" style="background-color:#151515;color:#e8e8d3;" class="language-ini "><code class="language-ini" data-lang="ini"><span style="color:#888888;"># frps.ini
|
||||
</span><span style="color:#8fbfdc;">[common]
|
||||
</span><span style="color:#ffb964;">bind_port </span><span>= </span><span style="color:#cf6a4c;">7000
|
||||
</span><span style="color:#ffb964;">token </span><span>= yourSecureToken
|
||||
</span><span style="color:#ffb964;">max_pool_count </span><span>= </span><span style="color:#cf6a4c;">50
|
||||
</span><span style="color:#ffb964;">max_ports_per_client </span><span>= </span><span style="color:#cf6a4c;">10
|
||||
</span></code></pre>
|
||||
<h2 id="chang-jian-wen-ti-pai-cha">常见问题排查</h2>
|
||||
<h3 id="1-lian-jie-bei-ju-jue">1. 连接被拒绝</h3>
|
||||
<p><strong>问题</strong>: 客户端报错 "dial tcp x.x.x.x:7000: connect: connection refused"</p>
|
||||
<p><strong>解决方案</strong>:</p>
|
||||
<ul>
|
||||
<li>检查服务端IP和端口是否正确</li>
|
||||
<li>确认服务端frps是否正在运行</li>
|
||||
<li>检查防火墙是否允许7000端口通信</li>
|
||||
</ul>
|
||||
<h3 id="2-ren-zheng-shi-bai">2. 认证失败</h3>
|
||||
<p><strong>问题</strong>: 客户端日志显示 "login to server failed: authentication failed"</p>
|
||||
<p><strong>解决方案</strong>:</p>
|
||||
<ul>
|
||||
<li>确认客户端和服务端的token设置一致</li>
|
||||
<li>检查服务端日志是否有更多错误信息</li>
|
||||
</ul>
|
||||
<h3 id="3-duan-kou-yi-bei-zhan-yong">3. 端口已被占用</h3>
|
||||
<p><strong>问题</strong>: 服务端启动失败，提示 "bind: address already in use"</p>
|
||||
<p><strong>解决方案</strong>:</p>
|
||||
<ul>
|
||||
<li>更改配置中的端口</li>
|
||||
<li>终止占用该端口的其他应用</li>
|
||||
<li>使用 <code>netstat -tunlp | grep 端口号</code> 查看占用该端口的进程</li>
|
||||
</ul>
|
||||
<h3 id="4-wu-fa-fang-wen-dai-li-fu-wu">4. 无法访问代理服务</h3>
|
||||
<p><strong>问题</strong>: 代理设置正确，但无法访问服务</p>
|
||||
<p><strong>解决方案</strong>:</p>
|
||||
<ul>
|
||||
<li>检查本地服务是否正常运行</li>
|
||||
<li>确认local_ip和local_port设置正确</li>
|
||||
<li>使用 <code>curl localhost:本地端口</code> 测试本地服务</li>
|
||||
<li>检查服务端防火墙是否开放了remote_port</li>
|
||||
</ul>
|
||||
<h3 id="5-dai-li-lian-jie-bu-wen-ding">5. 代理连接不稳定</h3>
|
||||
<p><strong>问题</strong>: 连接经常断开</p>
|
||||
<p><strong>解决方案</strong>:</p>
|
||||
<ul>
|
||||
<li>增加心跳包频率，在[common]部分添加:<pre style="background-color:#151515;color:#e8e8d3;"><code><span>heartbeat_interval = 30
|
||||
</span><span>heartbeat_timeout = 90
|
||||
</span></code></pre>
|
||||
</li>
|
||||
<li>启用多路复用和连接池</li>
|
||||
</ul>
|
||||
<h3 id="6-yu-ming-jie-xi-shi-bai">6. 域名解析失败</h3>
|
||||
<p><strong>问题</strong>: 使用custom_domains配置，但无法通过域名访问</p>
|
||||
<p><strong>解决方案</strong>:</p>
|
||||
<ul>
|
||||
<li>确保域名已正确解析到服务端IP</li>
|
||||
<li>检查frps.ini中是否配置了http/https的监听端口</li>
|
||||
<li>使用 <code>dig</code> 或 <code>nslookup</code> 命令验证域名解析</li>
|
||||
</ul>
|
||||
<p>🔗</p>
|
||||
<ul>
|
||||
<li><a href="https://gofrp.org/docs/">FRP官方文档</a></li>
|
||||
<li><a href="https://github.com/fatedier/frp">FRP GitHub仓库</a></li>
|
||||
<li><a href="https://github.com/fatedier/frp/issues">FRP常见问题解答</a></li>
|
||||
</ul>
|
||||
<hr />
|
||||
<p><strong>Done.</strong></p>
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
<div class="pagination">
|
||||
<div class="pagination__title">
|
||||
<span class="pagination__title-h">Thanks for reading! Read other posts?</span>
|
||||
<hr />
|
||||
</div>
|
||||
<div class="pagination__buttons">
|
||||
<span class="button previous">
|
||||
<a href="https://blog.dich.bid/about-ventoy/">
|
||||
<span class="button__icon">←</span>
|
||||
<span class="button__text">乱七八糟:Ventoy战斗盘部署</span>
|
||||
</a>
|
||||
</span>
|
||||
|
||||
|
||||
<span class="button next">
|
||||
<a href="https://blog.dich.bid/about-gfs/">
|
||||
<span class="button__text">乱七八糟:GFS项目考量笔记</span>
|
||||
<span class="button__icon">→</span>
|
||||
</a>
|
||||
</span>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
</div>
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
<footer class="footer">
|
||||
<div class="footer__inner">
|
||||
<div class="copyright">
|
||||
<span>©
|
||||
2025
|
||||
Dichgrem</span>
|
||||
<span class="copyright-theme">
|
||||
<span class="copyright-theme-sep"> :: CC BY-SA 4.0 :: A friend comes from distant lands</span>
|
||||
</a>
|
||||
</span>
|
||||
</div>
|
||||
</div>
|
||||
</footer>
|
||||
|
||||
</div>
|
||||
</body>
|
||||
</html>
|
||||
|
||||
228
public/about-gfs/index.html
Normal file
228
public/about-gfs/index.html
Normal file
@ -0,0 +1,228 @@
|
||||
<!DOCTYPE html>
|
||||
<html lang="en">
|
||||
|
||||
<head>
|
||||
<title>Dich'blog</title>
|
||||
|
||||
<meta http-equiv="content-type" content="text/html; charset=utf-8">
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1">
|
||||
<meta name="robots" content="noodp"/>
|
||||
|
||||
<link rel="stylesheet" href="https://blog.dich.bid/style.css">
|
||||
<link rel="stylesheet" href="https://blog.dich.bid/color/blue.css">
|
||||
|
||||
<link rel="stylesheet" href="https://blog.dich.bid/color/background_dark.css">
|
||||
|
||||
<link rel="stylesheet" href="https://blog.dich.bid/font-hack-subset.css">
|
||||
|
||||
<meta name="description" content="">
|
||||
|
||||
<meta property="og:description" content="">
|
||||
<meta property="og:title" content="Dich'blog">
|
||||
<meta property="og:type" content="article">
|
||||
<meta property="og:url" content="https://blog.dich.bid/about-gfs/">
|
||||
|
||||
<meta name="twitter:card" content="summary_large_image">
|
||||
<meta name="twitter:description" content="">
|
||||
<meta name="twitter:title" content="Dich'blog">
|
||||
<meta property="twitter:domain" content="blog.dich.bid">
|
||||
<meta property="twitter:url" content="https://blog.dich.bid/about-gfs/">
|
||||
|
||||
<link rel="alternate" type="application/atom+xml" title="Dich'blog Atom Feed" href="https://blog.dich.bid/atom.xml" />
|
||||
|
||||
|
||||
<link rel="icon" type="image/png" href=/dich.webp />
|
||||
|
||||
<!-- ✅ Added center alignment styles -->
|
||||
<style>
|
||||
.footer {
|
||||
text-align: center;
|
||||
padding: 1rem 0;
|
||||
}
|
||||
|
||||
.footer__inner {
|
||||
display: flex;
|
||||
justify-content: center;
|
||||
flex-direction: column;
|
||||
align-items: center;
|
||||
}
|
||||
|
||||
.copyright {
|
||||
text-align: center;
|
||||
}
|
||||
</style>
|
||||
</head>
|
||||
|
||||
<body class="">
|
||||
<div class="container">
|
||||
|
||||
<header class="header">
|
||||
<div class="header__inner">
|
||||
<div class="header__logo">
|
||||
|
||||
<a href="https://blog.dich.bid" style="text-decoration: none;">
|
||||
<div class="logo">
|
||||
|
||||
Dich'blog
|
||||
|
||||
</div>
|
||||
</a>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
|
||||
<nav class="menu">
|
||||
<ul class="menu__inner">
|
||||
<li><a href="https://blog.dich.bid">blog</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/archive">archive</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/tags">tags</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/weekly">weekly</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/search">search</a></li>
|
||||
|
||||
<li class="active"><a href="https://blog.dich.bid/about">about me</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/links">links</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/atom.xml">rss</a></li>
|
||||
|
||||
<li><a href="https://github.com/Dichgrem" target="_blank" rel="noopener noreferrer">github</a></li>
|
||||
</ul>
|
||||
</nav>
|
||||
|
||||
|
||||
|
||||
</header>
|
||||
|
||||
|
||||
<div class="content">
|
||||
|
||||
<div class="post">
|
||||
|
||||
<h1 class="post-title"><a href="https://blog.dich.bid/about-gfs/">乱七八糟:GFS项目考量笔记</a></h1>
|
||||
<div class="post-meta-inline">
|
||||
|
||||
<span class="post-date">
|
||||
2025-03-18
|
||||
</span>
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
<span class="post-tags-inline">
|
||||
:: tags:
|
||||
<a class="post-tag" href="https://blog.dich.bid/tags/luan-qi-ba-zao/">#乱七八糟</a></span>
|
||||
|
||||
|
||||
<div class="post-content">
|
||||
<p>前言 最近nekoray项目归档,考量新的singbox前端时发现这个项目不错,不过在Arch linux中运行有一些小问题,这里做个总结。</p>
|
||||
<span id="continue-reading"></span><h2 id="an-zhuang-zui-xin-ban">安装最新版:</h2>
|
||||
<p>安装gui-for-singbox的时候发现仓库的1.9.2版本release被作者删除,无法安装,于是：</p>
|
||||
<ul>
|
||||
<li>在AUR仓库中下载<strong>aur-gui-for-singbox.tar.gz</strong>,解压进入aur-gui-for-singbox目录;</li>
|
||||
<li><strong>更改.SRCINFO文件</strong>,使其版本号为最新;</li>
|
||||
<li><strong>使用makepkg -si构建并安装</strong>这个包,缺少的png图片可以直接下载并放进目录;</li>
|
||||
<li>如果有错误<strong>刷新密钥环</strong>（sudo pacman-key --refresh-keys）;</li>
|
||||
</ul>
|
||||
<h2 id="wu-fa-da-kai-wu-fa-shi-yong-tunmo-shi">无法打开/无法使用TUN模式:</h2>
|
||||
<ul>
|
||||
<li>安装成功,进入<code>/opt/gui-for-singbox</code>,运行<code>sudo chown -R your_username:your_group /opt/gui-for-singbox</code>,使其可以被非root用户启动;</li>
|
||||
<li>执行<code>sudo setcap cap_net_bind_service,cap_net_admin,cap_dac_override=+ep /opt/gui-for-singbox/your_executable</code>命令,并在设置-内核中点击盾牌-钥匙图标,使Tun模式可以有特权运行。</li>
|
||||
</ul>
|
||||
<h2 id="mian-mi-ma-yun-xing-tunmo-shi">免密码运行TUN模式:</h2>
|
||||
<ul>
|
||||
<li>检查 polkit 服务是否正在运行</li>
|
||||
</ul>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>systemctl status polkit
|
||||
</span></code></pre>
|
||||
<ul>
|
||||
<li>若返回状态为除 active (running) 之外的结果,运行</li>
|
||||
</ul>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>sudo systemctl enable --now polkit
|
||||
</span></code></pre>
|
||||
<ul>
|
||||
<li>创建 polkit 策略</li>
|
||||
</ul>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>sudo vi /etc/polkit-1/rules.d/99-nopassword.rules
|
||||
</span></code></pre>
|
||||
<ul>
|
||||
<li>添加以下内容并保存退出</li>
|
||||
</ul>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>polkit.addRule(function (action, subject) {
|
||||
</span><span> if (
|
||||
</span><span> (action.id == "org.freedesktop.resolve1.set-domains" ||
|
||||
</span><span> action.id == "org.freedesktop.resolve1.set-default-route" ||
|
||||
</span><span> action.id == "org.freedesktop.resolve1.set-dns-servers") &&
|
||||
</span><span> subject.local &&
|
||||
</span><span> subject.active &&
|
||||
</span><span> subject.isInGroup("wheel")
|
||||
</span><span> ) {
|
||||
</span><span> return polkit.Result.YES;
|
||||
</span><span> }
|
||||
</span><span>});
|
||||
</span></code></pre>
|
||||
<ul>
|
||||
<li>将当前用户添加至 wheel 组中,注意Debian 与衍生系统需要先创建 wheel 组,然后运行：</li>
|
||||
</ul>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>sudo usermod -G wheel 当前用户
|
||||
</span></code></pre>
|
||||
<ul>
|
||||
<li>重新加载 polkit 使更改生效</li>
|
||||
</ul>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>sudo systemctl restart polkit
|
||||
</span></code></pre>
|
||||
<hr />
|
||||
<p><strong>Done.</strong></p>
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
<div class="pagination">
|
||||
<div class="pagination__title">
|
||||
<span class="pagination__title-h">Thanks for reading! Read other posts?</span>
|
||||
<hr />
|
||||
</div>
|
||||
<div class="pagination__buttons">
|
||||
<span class="button previous">
|
||||
<a href="https://blog.dich.bid/about-frp/">
|
||||
<span class="button__icon">←</span>
|
||||
<span class="button__text">乱七八糟:FRP使用指南</span>
|
||||
</a>
|
||||
</span>
|
||||
|
||||
|
||||
<span class="button next">
|
||||
<a href="https://blog.dich.bid/about-markdown/">
|
||||
<span class="button__text">乱七八糟:Markdown使用快速教程</span>
|
||||
<span class="button__icon">→</span>
|
||||
</a>
|
||||
</span>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
</div>
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
<footer class="footer">
|
||||
<div class="footer__inner">
|
||||
<div class="copyright">
|
||||
<span>©
|
||||
2025
|
||||
Dichgrem</span>
|
||||
<span class="copyright-theme">
|
||||
<span class="copyright-theme-sep"> :: CC BY-SA 4.0 :: A friend comes from distant lands</span>
|
||||
</a>
|
||||
</span>
|
||||
</div>
|
||||
</div>
|
||||
</footer>
|
||||
|
||||
</div>
|
||||
</body>
|
||||
</html>
|
||||
|
||||
661
public/about-git/index.html
Normal file
661
public/about-git/index.html
Normal file
@ -0,0 +1,661 @@
|
||||
<!DOCTYPE html>
|
||||
<html lang="en">
|
||||
|
||||
<head>
|
||||
<title>Dich'blog</title>
|
||||
|
||||
<meta http-equiv="content-type" content="text/html; charset=utf-8">
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1">
|
||||
<meta name="robots" content="noodp"/>
|
||||
|
||||
<link rel="stylesheet" href="https://blog.dich.bid/style.css">
|
||||
<link rel="stylesheet" href="https://blog.dich.bid/color/blue.css">
|
||||
|
||||
<link rel="stylesheet" href="https://blog.dich.bid/color/background_dark.css">
|
||||
|
||||
<link rel="stylesheet" href="https://blog.dich.bid/font-hack-subset.css">
|
||||
|
||||
<meta name="description" content="">
|
||||
|
||||
<meta property="og:description" content="">
|
||||
<meta property="og:title" content="Dich'blog">
|
||||
<meta property="og:type" content="article">
|
||||
<meta property="og:url" content="https://blog.dich.bid/about-git/">
|
||||
|
||||
<meta name="twitter:card" content="summary_large_image">
|
||||
<meta name="twitter:description" content="">
|
||||
<meta name="twitter:title" content="Dich'blog">
|
||||
<meta property="twitter:domain" content="blog.dich.bid">
|
||||
<meta property="twitter:url" content="https://blog.dich.bid/about-git/">
|
||||
|
||||
<link rel="alternate" type="application/atom+xml" title="Dich'blog Atom Feed" href="https://blog.dich.bid/atom.xml" />
|
||||
|
||||
|
||||
<link rel="icon" type="image/png" href=/dich.webp />
|
||||
|
||||
<!-- ✅ Added center alignment styles -->
|
||||
<style>
|
||||
.footer {
|
||||
text-align: center;
|
||||
padding: 1rem 0;
|
||||
}
|
||||
|
||||
.footer__inner {
|
||||
display: flex;
|
||||
justify-content: center;
|
||||
flex-direction: column;
|
||||
align-items: center;
|
||||
}
|
||||
|
||||
.copyright {
|
||||
text-align: center;
|
||||
}
|
||||
</style>
|
||||
</head>
|
||||
|
||||
<body class="">
|
||||
<div class="container">
|
||||
|
||||
<header class="header">
|
||||
<div class="header__inner">
|
||||
<div class="header__logo">
|
||||
|
||||
<a href="https://blog.dich.bid" style="text-decoration: none;">
|
||||
<div class="logo">
|
||||
|
||||
Dich'blog
|
||||
|
||||
</div>
|
||||
</a>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
|
||||
<nav class="menu">
|
||||
<ul class="menu__inner">
|
||||
<li><a href="https://blog.dich.bid">blog</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/archive">archive</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/tags">tags</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/weekly">weekly</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/search">search</a></li>
|
||||
|
||||
<li class="active"><a href="https://blog.dich.bid/about">about me</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/links">links</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/atom.xml">rss</a></li>
|
||||
|
||||
<li><a href="https://github.com/Dichgrem" target="_blank" rel="noopener noreferrer">github</a></li>
|
||||
</ul>
|
||||
</nav>
|
||||
|
||||
|
||||
|
||||
</header>
|
||||
|
||||
|
||||
<div class="content">
|
||||
|
||||
<div class="post">
|
||||
|
||||
<h1 class="post-title"><a href="https://blog.dich.bid/about-git/">乱七八糟:Git使用简明手册</a></h1>
|
||||
<div class="post-meta-inline">
|
||||
|
||||
<span class="post-date">
|
||||
2023-12-15
|
||||
</span>
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
<span class="post-tags-inline">
|
||||
:: tags:
|
||||
<a class="post-tag" href="https://blog.dich.bid/tags/luan-qi-ba-zao/">#乱七八糟</a></span>
|
||||
|
||||
|
||||
<div class="post-content">
|
||||
<p>前言 Git，作为现代软件开发中不可或缺的版本控制工具，常常让初学者感到困惑。本文旨在介绍 Git 的全流程安装和基本使用，希望能够帮助新手更轻松地理解和掌握 Git 的基本概念和操作。</p>
|
||||
<span id="continue-reading"></span><h2 id="an-zhuang-git">安装git</h2>
|
||||
<ul>
|
||||
<li>
|
||||
<p>Windows：<a href="https://git-scm.com/download/">Git-download</a></p>
|
||||
</li>
|
||||
<li>
|
||||
<p>Archlinux：<code>sudo pacman -S git</code></p>
|
||||
</li>
|
||||
</ul>
|
||||
<h2 id="yuan-li">原理</h2>
|
||||
<p>一个Git仓库的目录里面包括<code>工作目录</code>（即我们要追踪的代码）以及<code>.git</code>目录（Git 在这里存储自己的数据）。Git 维护了三棵“树”:第一个是你的 <code>工作目录</code>，它持有实际文件；第二个是 <code>暂存区（Index）</code>，它像个缓存区域，临时保存你的改动；最后是 <code>HEAD</code>，它指向你最后一次提交的结果。</p>
|
||||
<p><img src="http://marklodato.github.io/visual-git-guide/basic-usage.svg.png" alt="git-tree" /></p>
|
||||
<h2 id="chuang-jian-xin-cang-ku">创建新仓库</h2>
|
||||
<p>首先我们需要得到一个Git仓库，一般有两种方法：</p>
|
||||
<ul>
|
||||
<li>在本地初始化之后连接到远程；</li>
|
||||
<li>在远程创建后”下载“到本地。</li>
|
||||
</ul>
|
||||
<p><strong>方法一</strong>
|
||||
创建新文件夹，在你的项目目录中运行以下命令：</p>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>git init --initial-branch=main
|
||||
</span></code></pre>
|
||||
<p>这里设置默认仓库主分支名称为 main,避免因为 main/master 名称不同导致的推送问题。</p>
|
||||
<blockquote>
|
||||
<p>Git目前默认的主分支为 master，和 github 默认分支 main 不同，这使得默认配置下 git 往往连接失败。除了创建的时候设定外还可以通过以下方法改变默认分支。</p>
|
||||
</blockquote>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>git config --global init.defaultBranch main //将默认分支修改成main
|
||||
</span></code></pre>
|
||||
<p><strong>方法二</strong></p>
|
||||
<p>克隆远端服务器上的仓库：</p>
|
||||
<ul>
|
||||
<li>HTTPS方法：<code>git clone https://github.com/Dichgrem/script.git</code></li>
|
||||
<li>或者使用SSH方法：<code>git clone git@github.com:Dichgrem/script.git</code></li>
|
||||
</ul>
|
||||
<blockquote>
|
||||
<p>建议使用SSH方法，如果你使用HTTPS方法，则提交代码时需要手动输入用户名/密码，使用SSH方法则只需要在<code>~/.ssh/config</code>中配置即可。</p>
|
||||
</blockquote>
|
||||
<h2 id="pei-zhi">配置</h2>
|
||||
<p>Git的设置文件为.gitconfig，它可以在用户主目录下（全局配置），也可以在项目目录下（项目配置）。</p>
|
||||
<ul>
|
||||
<li>显示当前的Git配置</li>
|
||||
</ul>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>git config --list
|
||||
</span></code></pre>
|
||||
<ul>
|
||||
<li>编辑Git配置文件</li>
|
||||
</ul>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>git config -e [--global]
|
||||
</span></code></pre>
|
||||
<ul>
|
||||
<li>设置提交代码时的用户信息</li>
|
||||
</ul>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>git config [--global] user.name "[name]"
|
||||
</span><span>git config [--global] user.email "[email address]"
|
||||
</span></code></pre>
|
||||
<ul>
|
||||
<li>设置大小写敏感（windows不区分大小写的解决办法）</li>
|
||||
</ul>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>git config core.ignorecase false
|
||||
</span></code></pre>
|
||||
<h2 id="lian-jie-yuan-cheng-cang-ku">连接远程仓库</h2>
|
||||
<p>连接到远程仓库并推送需要证明你有权写入仓库。早期Github可以使用密码认证，现在则使用密钥认证。</p>
|
||||
<ul>
|
||||
<li>生成密钥：</li>
|
||||
</ul>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>ssh-keygen -t rsa -b 4096 -C "your_email@example.com"
|
||||
</span></code></pre>
|
||||
<ul>
|
||||
<li>
|
||||
<p>生成的文件位于<code>~/.ssh/config</code>路径下，带.pub后缀的文件为公钥，不带.pub后缀的为私钥，使用<code>cat ~/.ssh/id_rsa.pub</code>将公钥添加到github/gitee的设置-SSH中。</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>随后使用 <code>ssh-add</code> 命令将生成的密钥添加到 SSH 代理中。</p>
|
||||
</li>
|
||||
</ul>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>ssh-add ~/.ssh/github_key
|
||||
</span><span>ssh-add ~/.ssh/gitee_key
|
||||
</span></code></pre>
|
||||
<ul>
|
||||
<li>在 <code>~/.ssh/config</code> 文件中配置不同的主机别名以及相应的密钥文件。编辑该文件并添加内容，例如：</li>
|
||||
</ul>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span># GitHub repository 1
|
||||
</span><span>
|
||||
</span><span>Host github1
|
||||
</span><span>
|
||||
</span><span> HostName github.com
|
||||
</span><span>
|
||||
</span><span> User git
|
||||
</span><span>
|
||||
</span><span> IdentityFile ~/.ssh/github_key
|
||||
</span><span>
|
||||
</span><span># GitHub repository 2
|
||||
</span><span>
|
||||
</span><span>Host github2
|
||||
</span><span>
|
||||
</span><span> HostName gitee.com
|
||||
</span><span>
|
||||
</span><span> User git
|
||||
</span><span>
|
||||
</span><span> IdentityFile ~/.ssh/gitee_key
|
||||
</span></code></pre>
|
||||
<ul>
|
||||
<li>连接到github：</li>
|
||||
</ul>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>ssh -T git@github.com
|
||||
</span></code></pre>
|
||||
<ul>
|
||||
<li>添加远程仓库：</li>
|
||||
</ul>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>git remote add origin <remote_repository_url>
|
||||
</span><span>
|
||||
</span><span># 例如：git remote add origin git@github.com:Dichgrem/dichos.git
|
||||
</span></code></pre>
|
||||
<blockquote>
|
||||
<p>如果你运行<code>git remote -v</code>发现URL为HTTP格式则可以用下面的命令改为Git格式：</p>
|
||||
</blockquote>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span># 例如：git remote set-url origin git@github.com:Dichgrem/dichos.git
|
||||
</span></code></pre>
|
||||
<h2 id="chuang-jian-fen-zhi">创建分支</h2>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>git branch main
|
||||
</span></code></pre>
|
||||
<p>这将创建一个名为 main 的分支。</p>
|
||||
<ul>
|
||||
<li>删除分支</li>
|
||||
</ul>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>git branch -d master
|
||||
</span></code></pre>
|
||||
<ul>
|
||||
<li>使用大写强制删除</li>
|
||||
</ul>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>git branch -D master
|
||||
</span></code></pre>
|
||||
<h2 id="tian-jia-he-ti-jiao">添加和提交</h2>
|
||||
<p>你可以提出更改（把它们添加到暂存区），使用如下命令：</p>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>git add <filename>
|
||||
</span><span>git add *
|
||||
</span></code></pre>
|
||||
<p>这是 git 基本工作流程的第一步；使用如下命令以实际提交改动：</p>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>git commit -m "代码提交信息"
|
||||
</span><span># 例如：git commit -m "Initial commit"
|
||||
</span></code></pre>
|
||||
<p>现在，你的改动已经提交到了 <strong>HEAD</strong>，但是还没到你的远端仓库。</p>
|
||||
<ul>
|
||||
<li>添加指定文件到暂存区</li>
|
||||
</ul>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>git add [file1] [file2] ...
|
||||
</span></code></pre>
|
||||
<ul>
|
||||
<li>添加指定目录到暂存区，包括子目录</li>
|
||||
</ul>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>git add [dir]
|
||||
</span></code></pre>
|
||||
<ul>
|
||||
<li>添加当前目录的所有文件到暂存区</li>
|
||||
</ul>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>git add .
|
||||
</span></code></pre>
|
||||
<p>添加每个变化前，都会要求确认</p>
|
||||
<ul>
|
||||
<li>对于同一个文件的多处变化，可以实现分次提交</li>
|
||||
</ul>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>git add -p
|
||||
</span></code></pre>
|
||||
<ul>
|
||||
<li>删除工作区文件，并且将这次删除放入暂存区</li>
|
||||
</ul>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>git rm [file1] [file2] ...
|
||||
</span></code></pre>
|
||||
<ul>
|
||||
<li>停止追踪指定文件，但该文件会保留在工作区</li>
|
||||
</ul>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>git rm --cached [file]
|
||||
</span></code></pre>
|
||||
<ul>
|
||||
<li>改名文件，并且将这个改名放入暂存区</li>
|
||||
</ul>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>git mv [file-original] [file-renamed]
|
||||
</span></code></pre>
|
||||
<h2 id="tui-song-gai-dong">推送改动</h2>
|
||||
<p>你的改动现在已经在本地仓库的 <strong>HEAD</strong> 中了。执行如下命令以将这些改动提交到远端仓库：</p>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>git push origin main
|
||||
</span></code></pre>
|
||||
<p>可以把 <strong>main</strong> 换成你想要推送的任何分支,如<strong>master</strong>或者<strong>test</strong></p>
|
||||
<p>如果你的远程仓库是最新的，可以使用以下命令更新本地仓库：</p>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>git pull
|
||||
</span></code></pre>
|
||||
<h2 id="he-bing-fen-zhi">合并分支</h2>
|
||||
<p>分支是用来将特性开发绝缘开来的。比如你在本地的test分支新增了一个功能，想要合并到主分支中。</p>
|
||||
<p>创建一个叫做“test”的分支，并切换过去：</p>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>git checkout -b test
|
||||
</span></code></pre>
|
||||
<p>新增某些功能后切换回主分支：</p>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>git checkout master
|
||||
</span></code></pre>
|
||||
<p>在主分支上执行合并操作，将 test 分支的改动合并到主分支：</p>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>git merge test
|
||||
</span></code></pre>
|
||||
<p>推送完成后可以把新建的分支删掉：</p>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>git branch -d test
|
||||
</span></code></pre>
|
||||
<h3 id="fen-zhi-chang-yong-cao-zuo">分支常用操作</h3>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>- 列出所有本地分支
|
||||
</span><span>git branch
|
||||
</span><span>
|
||||
</span><span>- 列出所有远程分支
|
||||
</span><span>git branch -r
|
||||
</span><span>
|
||||
</span><span>- 列出所有本地分支和远程分支
|
||||
</span><span>git branch -a
|
||||
</span><span>
|
||||
</span><span>- 列出所有本地分支，并展示没有分支最后一次提交的信息
|
||||
</span><span>git branch -v
|
||||
</span><span>
|
||||
</span><span>- 列出所有本地分支，并展示没有分支最后一次提交的信息和远程分支的追踪情况
|
||||
</span><span>git branch -vv
|
||||
</span><span>
|
||||
</span><span>- 列出所有已经合并到当前分支的分支
|
||||
</span><span>git branch --merged
|
||||
</span><span>
|
||||
</span><span>- 列出所有还没有合并到当前分支的分支
|
||||
</span><span>git branch --no-merged
|
||||
</span><span>
|
||||
</span><span>- 新建一个分支，但依然停留在当前分支
|
||||
</span><span>git branch [branch-name]
|
||||
</span><span>
|
||||
</span><span>- 新建一个分支，并切换到该分支
|
||||
</span><span>git checkout -b [branch]
|
||||
</span><span>
|
||||
</span><span>- 新建一个与远程分支同名的分支，并切换到该分支
|
||||
</span><span>git checkout --track [branch-name]
|
||||
</span><span>
|
||||
</span><span>- 新建一个分支，指向指定commit
|
||||
</span><span>git branch [branch] [commit]
|
||||
</span><span>
|
||||
</span><span>- 新建一个分支，与指定的远程分支建立追踪关系
|
||||
</span><span>git branch --track [branch] [remote-branch]
|
||||
</span><span>
|
||||
</span><span>- 切换到指定分支，并更新工作区
|
||||
</span><span>git checkout [branch-name]
|
||||
</span><span>
|
||||
</span><span>- 切换到上一个分支
|
||||
</span><span>git checkout -
|
||||
</span><span>
|
||||
</span><span>- 建立追踪关系，在现有分支与指定的远程分支之间
|
||||
</span><span>git branch --set-upstream-to=[remote-branch]
|
||||
</span><span>git branch --set-upstream [branch] [remote-branch] - 已被弃用
|
||||
</span><span>
|
||||
</span><span>- 合并指定分支到当前分支
|
||||
</span><span>git merge [branch]
|
||||
</span><span>
|
||||
</span><span>- 中断此次合并（你可能不想处理冲突）
|
||||
</span><span>git merge --abort
|
||||
</span><span>
|
||||
</span><span>- 选择一个commit，合并进当前分支
|
||||
</span><span>git cherry-pick [commit]
|
||||
</span><span>
|
||||
</span><span>- 删除分支
|
||||
</span><span>git branch -d [branch-name]
|
||||
</span><span>
|
||||
</span><span>#新增远程分支 远程分支需先在本地创建,再进行推送
|
||||
</span><span>git push origin [branch-name]
|
||||
</span><span>
|
||||
</span><span>- 删除远程分支
|
||||
</span><span>git push origin --delete [branch-name]
|
||||
</span><span>git branch -dr [remote/branch]
|
||||
</span></code></pre>
|
||||
<h2 id="biao-qian">标签</h2>
|
||||
<p>Git 的 tag 功能主要用于<code>给仓库历史中的某个特定提交打上“标签”</code>，通常用于标记版本发布点（例如 v1.0、v2.0 等），以<code>便于后续的版本定位、回溯和发布管理</code>。</p>
|
||||
<h3 id="biao-qian-lei-xing">标签类型</h3>
|
||||
<p>Git 提供两种类型的标签：</p>
|
||||
<ul>
|
||||
<li>
|
||||
<p>附注标签（Annotated Tag）会创建成一个完整的 Git 对象，存储打标签者的名字、邮箱、日期和标签说明，还可采用 GPG 进行签名。推荐用于正式发布，因为包含更多元数据和安全信息。</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>轻量标签（Lightweight Tag）实际上只是对某个提交的引用，不保存额外信息，类似一个固定的分支。适用于临时标记或非正式用途。</p>
|
||||
</li>
|
||||
</ul>
|
||||
<h3 id="chuang-jian-biao-qian">创建标签</h3>
|
||||
<ul>
|
||||
<li>创建附注标签</li>
|
||||
</ul>
|
||||
<p>使用 -a 参数表示“annotated”，并用 -m 提供标签说明。例如，给当前提交创建一个名为 v1.0 的附注标签：</p>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>git tag -a v1.0 -m "发布版本 v1.0"
|
||||
</span></code></pre>
|
||||
<p>这会在 Git 数据库中生成一个完整的标签对象，可通过 git show v1.0 查看标签信息和对应的提交详情。</p>
|
||||
<p>如果需要给旧提交贴标签，可以在命令末尾指定提交的 SHA 值（部分 SHA 也可）：</p>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>git tag -a v1.0 <commit-sha> -m "发布版本 v1.0"
|
||||
</span></code></pre>
|
||||
<ul>
|
||||
<li>创建轻量标签</li>
|
||||
</ul>
|
||||
<p>直接指定标签名即可，不加任何参数：</p>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>git tag v1.0-light
|
||||
</span></code></pre>
|
||||
<p>轻量标签仅仅是一个提交引用，因此查看时不会显示附加信息。</p>
|
||||
<h3 id="lie-chu-biao-qian">列出标签</h3>
|
||||
<ul>
|
||||
<li>列出所有标签</li>
|
||||
</ul>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>git tag
|
||||
</span></code></pre>
|
||||
<ul>
|
||||
<li>还可以使用通配符过滤：</li>
|
||||
</ul>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>git tag -l "v1.*"
|
||||
</span></code></pre>
|
||||
<p>这样便于管理和筛选大量标签。</p>
|
||||
<ul>
|
||||
<li>查看标签详细信息</li>
|
||||
</ul>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>git show v1.0
|
||||
</span></code></pre>
|
||||
<p>这会显示标签对象的元数据以及对应的提交记录。</p>
|
||||
<h3 id="tui-song-biao-qian">推送标签</h3>
|
||||
<p><code>默认情况下，git push 不会将本地标签推送到远程仓库。推送标签有两种方式：</code></p>
|
||||
<ul>
|
||||
<li>推送单个标签</li>
|
||||
</ul>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>git push origin v1.0
|
||||
</span></code></pre>
|
||||
<ul>
|
||||
<li>一次性推送所有标签</li>
|
||||
</ul>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>git push origin --tags
|
||||
</span></code></pre>
|
||||
<h3 id="shan-chu-biao-qian">删除标签</h3>
|
||||
<ul>
|
||||
<li>删除本地标签</li>
|
||||
</ul>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>git tag -d v1.0
|
||||
</span></code></pre>
|
||||
<ul>
|
||||
<li>删除远程标签</li>
|
||||
</ul>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>git push origin --delete v1.0
|
||||
</span></code></pre>
|
||||
<h2 id="ri-zhi">日志</h2>
|
||||
<p>如果你想了解本地仓库的历史记录，最简单的命令就是使用:</p>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>git log
|
||||
</span></code></pre>
|
||||
<ul>
|
||||
<li>只看某一个人的提交记录:</li>
|
||||
</ul>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>git log --author=bob
|
||||
</span></code></pre>
|
||||
<ul>
|
||||
<li>一个压缩后的每一条提交记录只占一行的输出:</li>
|
||||
</ul>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>git log --pretty=oneline
|
||||
</span></code></pre>
|
||||
<ul>
|
||||
<li>看看哪些文件改变了:</li>
|
||||
</ul>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>git log --name-status
|
||||
</span></code></pre>
|
||||
<h2 id="shan-chu-qian-yi-ge-ti-jiao-ji-lu">删除前一个提交记录</h2>
|
||||
<p>有时候手滑或者不想使用一个commit说明，可以用以下命令撤销上一个 commit：</p>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>git reset --soft HEAD~1
|
||||
</span></code></pre>
|
||||
<p>这个命令会撤销上一个 commit，但保留文件修改（代码仍然在工作区）。适用于 想要重新提交（amend）或调整 commit 的情况。</p>
|
||||
<p>如果你想彻底删除更改（不保留代码修改），可以使用：</p>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>git reset --hard HEAD~1
|
||||
</span></code></pre>
|
||||
<blockquote>
|
||||
<p>注意：--hard 会清除未提交的更改，无法恢复。</p>
|
||||
</blockquote>
|
||||
<h2 id="git-mu-lu-zhong-zhu-yao-wen-jian-he-zi-mu-lu-de-jie-gou-ji-qi-zuo-yong"><code>.git</code> 目录中主要文件和子目录的结构及其作用</h2>
|
||||
<h3 id="file-folder-git-mu-lu-jie-gou-gai-lan">📁 <code>.git</code> 目录结构概览</h3>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>.git/
|
||||
</span><span>├── HEAD
|
||||
</span><span>├── config
|
||||
</span><span>├── description
|
||||
</span><span>├── hooks/
|
||||
</span><span>├── index
|
||||
</span><span>├── info/
|
||||
</span><span>│ └── exclude
|
||||
</span><span>├── logs/
|
||||
</span><span>│ ├── HEAD
|
||||
</span><span>│ └── refs/
|
||||
</span><span>├── objects/
|
||||
</span><span>│ ├── info/
|
||||
</span><span>│ └── pack/
|
||||
</span><span>├── refs/
|
||||
</span><span>│ ├── heads/
|
||||
</span><span>│ ├── remotes/
|
||||
</span><span>│ └── tags/
|
||||
</span></code></pre>
|
||||
<h3 id="dividers-he-xin-wen-jian-he-mu-lu-shuo-ming">🗂️ 核心文件和目录说明</h3>
|
||||
<ul>
|
||||
<li>
|
||||
<p><strong>HEAD</strong>：指向当前检出的分支或提交。例如，<code>ref: refs/heads/main</code> 表示当前位于 <code>main</code> 分支。</p>
|
||||
</li>
|
||||
<li>
|
||||
<p><strong>config</strong>：仓库级别的配置文件，包含用户名、邮箱、远程仓库等信息.</p>
|
||||
</li>
|
||||
<li>
|
||||
<p><strong>description</strong>：用于描述仓库，仅供 GitWeb 等工具使用。</p>
|
||||
</li>
|
||||
<li>
|
||||
<p><strong>hooks/</strong>：存放 Git 钩子脚本的目录，可用于在特定操作前后执行自定义脚本，如 <code>pre-commit</code>、<code>post-merge</code> 等.</p>
|
||||
</li>
|
||||
<li>
|
||||
<p><strong>index</strong>：暂存区（staging area）的索引文件，记录了即将提交的文件信息。</p>
|
||||
</li>
|
||||
<li>
|
||||
<p><strong>info/</strong>：包含辅助信息，如 <code>exclude</code> 文件用于定义仓库级别的忽略规则。</p>
|
||||
</li>
|
||||
<li>
|
||||
<p><strong>logs/</strong>：记录了引用（如分支、标签）的更新历史，有助于追踪操作记录。</p>
|
||||
</li>
|
||||
<li>
|
||||
<p><strong>objects/</strong>：存储 Git 的所有对象，包括：</p>
|
||||
<ul>
|
||||
<li><strong>blob</strong>：文件内容。</li>
|
||||
<li><strong>tree</strong>：目录结构。</li>
|
||||
<li><strong>commit</strong>：提交对象，记录提交信息和指向的树对象。</li>
|
||||
<li><strong>tag</strong>：标签对象。
|
||||
这些对象以 SHA-1 哈希命名，前两位作为子目录，其余作为文件名。</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><strong>refs/</strong>：存储所有引用，包括：</p>
|
||||
<ul>
|
||||
<li><strong>heads/</strong>：本地分支。</li>
|
||||
<li><strong>remotes/</strong>：远程分支。</li>
|
||||
<li><strong>tags/</strong>：标签。</li>
|
||||
</ul>
|
||||
</li>
|
||||
</ul>
|
||||
<h2 id="commitgui-fan">Commit规范</h2>
|
||||
<h3 id="ti-jiao-xin-xi-de-ji-ben-ge-shi">提交信息的基本格式</h3>
|
||||
<ul>
|
||||
<li>Header（头部）
|
||||
格式：</li>
|
||||
</ul>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span><type>[可选的 scope]: <简短描述>
|
||||
</span></code></pre>
|
||||
<p>type 表示提交类型，如：feat（新功能）、fix（修复bug）等。
|
||||
scope 是可选的，用于指出变更影响的模块或范围。
|
||||
简短描述 用于概述本次提交的核心内容，通常使用祈使语气。</p>
|
||||
<ul>
|
||||
<li>
|
||||
<p>Body（正文）
|
||||
用于详细说明变更的动机、方法以及可能的影响，建议每行不超过 72 个字符。</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>Footer（脚注）
|
||||
可选部分，用来引用相关 issue、任务或说明破坏性变更（例如：BREAKING CHANGE: ...）。例如：</p>
|
||||
</li>
|
||||
</ul>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>Fixes #123
|
||||
</span></code></pre>
|
||||
<p>这可以在提交后自动关闭相关问题。</p>
|
||||
<h3 id="chang-jian-de-commit-lei-xing">常见的 Commit 类型</h3>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>- feat：新功能的添加
|
||||
</span><span> 示例：feat(user): 添加用户注册功能
|
||||
</span><span>
|
||||
</span><span>- fix：修复 Bug
|
||||
</span><span> 示例：fix(parser): 修复解析错误导致程序崩溃
|
||||
</span><span>
|
||||
</span><span>- docs：文档相关的修改
|
||||
</span><span> 示例：docs(readme): 更新使用说明
|
||||
</span><span>
|
||||
</span><span>- style：代码格式、排版等不影响代码逻辑的调整
|
||||
</span><span> 示例：style: 优化代码缩进和空格
|
||||
</span><span>
|
||||
</span><span>- refactor：代码重构，不涉及新功能或 Bug 修复
|
||||
</span><span> 示例：refactor: 优化数据处理逻辑
|
||||
</span><span>
|
||||
</span><span>- perf：性能优化
|
||||
</span><span> 示例：perf: 提升数据查询速度
|
||||
</span><span>
|
||||
</span><span>- test：添加或修改测试代码
|
||||
</span><span> 示例：test: 补充用户登录单元测试
|
||||
</span><span>
|
||||
</span><span>- build：构建相关的变更，如依赖管理、构建脚本等
|
||||
</span><span> 示例：build: 更新 webpack 配置
|
||||
</span><span>
|
||||
</span><span>- ci：持续集成相关的修改
|
||||
</span><span> 示例：ci: 调整 GitHub Actions 配置
|
||||
</span><span>
|
||||
</span><span>- chore：其他杂项维护，不涉及源代码或测试文件的修改
|
||||
</span><span> 示例：chore: 更新项目依赖
|
||||
</span><span>
|
||||
</span><span>- revert：回滚到上一个版本的提交
|
||||
</span><span> 示例：revert: 撤销上次提交
|
||||
</span></code></pre>
|
||||
<hr />
|
||||
<p><strong>Done.</strong></p>
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
<div class="pagination">
|
||||
<div class="pagination__title">
|
||||
<span class="pagination__title-h">Thanks for reading! Read other posts?</span>
|
||||
<hr />
|
||||
</div>
|
||||
<div class="pagination__buttons">
|
||||
<span class="button previous">
|
||||
<a href="https://blog.dich.bid/about-junk-cleanup/">
|
||||
<span class="button__icon">←</span>
|
||||
<span class="button__text">乱七八糟:垃圾清理的艺术</span>
|
||||
</a>
|
||||
</span>
|
||||
|
||||
|
||||
<span class="button next">
|
||||
<a href="https://blog.dich.bid/network-download-1/">
|
||||
<span class="button__text">Network的艺术:下载技术的历史</span>
|
||||
<span class="button__icon">→</span>
|
||||
</a>
|
||||
</span>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
</div>
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
<footer class="footer">
|
||||
<div class="footer__inner">
|
||||
<div class="copyright">
|
||||
<span>©
|
||||
2025
|
||||
Dichgrem</span>
|
||||
<span class="copyright-theme">
|
||||
<span class="copyright-theme-sep"> :: CC BY-SA 4.0 :: A friend comes from distant lands</span>
|
||||
</a>
|
||||
</span>
|
||||
</div>
|
||||
</div>
|
||||
</footer>
|
||||
|
||||
</div>
|
||||
</body>
|
||||
</html>
|
||||
|
||||
281
public/about-gpg/index.html
Normal file
281
public/about-gpg/index.html
Normal file
@ -0,0 +1,281 @@
|
||||
<!DOCTYPE html>
|
||||
<html lang="en">
|
||||
|
||||
<head>
|
||||
<title>Dich'blog</title>
|
||||
|
||||
<meta http-equiv="content-type" content="text/html; charset=utf-8">
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1">
|
||||
<meta name="robots" content="noodp"/>
|
||||
|
||||
<link rel="stylesheet" href="https://blog.dich.bid/style.css">
|
||||
<link rel="stylesheet" href="https://blog.dich.bid/color/blue.css">
|
||||
|
||||
<link rel="stylesheet" href="https://blog.dich.bid/color/background_dark.css">
|
||||
|
||||
<link rel="stylesheet" href="https://blog.dich.bid/font-hack-subset.css">
|
||||
|
||||
<meta name="description" content="">
|
||||
|
||||
<meta property="og:description" content="">
|
||||
<meta property="og:title" content="Dich'blog">
|
||||
<meta property="og:type" content="article">
|
||||
<meta property="og:url" content="https://blog.dich.bid/about-gpg/">
|
||||
|
||||
<meta name="twitter:card" content="summary_large_image">
|
||||
<meta name="twitter:description" content="">
|
||||
<meta name="twitter:title" content="Dich'blog">
|
||||
<meta property="twitter:domain" content="blog.dich.bid">
|
||||
<meta property="twitter:url" content="https://blog.dich.bid/about-gpg/">
|
||||
|
||||
<link rel="alternate" type="application/atom+xml" title="Dich'blog Atom Feed" href="https://blog.dich.bid/atom.xml" />
|
||||
|
||||
|
||||
<link rel="icon" type="image/png" href=/dich.webp />
|
||||
|
||||
<!-- ✅ Added center alignment styles -->
|
||||
<style>
|
||||
.footer {
|
||||
text-align: center;
|
||||
padding: 1rem 0;
|
||||
}
|
||||
|
||||
.footer__inner {
|
||||
display: flex;
|
||||
justify-content: center;
|
||||
flex-direction: column;
|
||||
align-items: center;
|
||||
}
|
||||
|
||||
.copyright {
|
||||
text-align: center;
|
||||
}
|
||||
</style>
|
||||
</head>
|
||||
|
||||
<body class="">
|
||||
<div class="container">
|
||||
|
||||
<header class="header">
|
||||
<div class="header__inner">
|
||||
<div class="header__logo">
|
||||
|
||||
<a href="https://blog.dich.bid" style="text-decoration: none;">
|
||||
<div class="logo">
|
||||
|
||||
Dich'blog
|
||||
|
||||
</div>
|
||||
</a>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
|
||||
<nav class="menu">
|
||||
<ul class="menu__inner">
|
||||
<li><a href="https://blog.dich.bid">blog</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/archive">archive</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/tags">tags</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/weekly">weekly</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/search">search</a></li>
|
||||
|
||||
<li class="active"><a href="https://blog.dich.bid/about">about me</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/links">links</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/atom.xml">rss</a></li>
|
||||
|
||||
<li><a href="https://github.com/Dichgrem" target="_blank" rel="noopener noreferrer">github</a></li>
|
||||
</ul>
|
||||
</nav>
|
||||
|
||||
|
||||
|
||||
</header>
|
||||
|
||||
|
||||
<div class="content">
|
||||
|
||||
<div class="post">
|
||||
|
||||
<h1 class="post-title"><a href="https://blog.dich.bid/about-gpg/">乱七八糟:GPG使用小记</a></h1>
|
||||
<div class="post-meta-inline">
|
||||
|
||||
<span class="post-date">
|
||||
2025-06-17
|
||||
</span>
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
<span class="post-tags-inline">
|
||||
:: tags:
|
||||
<a class="post-tag" href="https://blog.dich.bid/tags/luan-qi-ba-zao/">#乱七八糟</a></span>
|
||||
|
||||
|
||||
<div class="post-content">
|
||||
<p>前言 PGP/GPG 的核心功能——公钥加密、数字签名、信任管理广泛用于各个行业，本文简单说明了其使用方法。</p>
|
||||
<span id="continue-reading"></span><h2 id="shen-me-shi-pgp-yu-gpg">什么是 PGP 与 GPG</h2>
|
||||
<ul>
|
||||
<li>
|
||||
<p><strong>PGP（Pretty Good Privacy）</strong></p>
|
||||
<ul>
|
||||
<li>由 Phil Zimmermann 于 1991 年发布，是第一个面向个人用户的大众化加密软件。</li>
|
||||
<li>采用公钥加密体系，用于对邮件和文件进行加密、签名与验证。</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><strong>GPG（GNU Privacy Guard，又称 GnuPG）</strong></p>
|
||||
<ul>
|
||||
<li>项目发起于 1997 年，由 Free Software Foundation 推动，是 GPL 许可的自由软件实现。</li>
|
||||
<li>完全兼容 OpenPGP 标准（RFC 4880），可无缝替代 PGP 软件。</li>
|
||||
</ul>
|
||||
</li>
|
||||
</ul>
|
||||
<h2 id="li-shi-yan-ge">历史沿革</h2>
|
||||
<table><thead><tr><th>时间</th><th>事件</th></tr></thead><tbody>
|
||||
<tr><td>1991 年</td><td>Phil Zimmermann 发布 PGP 1.0，标志个人加密进入大众市场</td></tr>
|
||||
<tr><td>1994 年</td><td>PGP 因出口管制遭到美国政府调查，后续改版加密算法合规化</td></tr>
|
||||
<tr><td>1997 年</td><td>GNU 推出 GnuPG，目标创建一个开源、自由的 OpenPGP 实现</td></tr>
|
||||
<tr><td>2001 年</td><td>OpenPGP 正式成为 IETF 标准（RFC 2440）</td></tr>
|
||||
<tr><td>2006 年</td><td>GnuPG 2.0 发布，引入多子系统（gpg-agent、dirmngr 等）</td></tr>
|
||||
<tr><td>2014 年</td><td>OpenPGP 更新为 RFC 4880bis，GnuPG 不断改进对新算法的支持</td></tr>
|
||||
</tbody></table>
|
||||
<h2 id="he-xin-zuo-yong">核心作用</h2>
|
||||
<table><thead><tr><th>应用领域</th><th>描述</th></tr></thead><tbody>
|
||||
<tr><td><strong>1. 电子邮件加密与签名</strong></td><td>- <strong>PGP/MIME</strong>：通过邮件客户端（如 Thunderbird + Enigmail）对正文和附件加密，并用私钥签名。<br>- <strong>PGP inline</strong>：将加密/签名内容以纯文本形式嵌入邮件，兼容性更强。</td></tr>
|
||||
<tr><td><strong>2. 文件与目录的加密签名</strong></td><td>- <strong>单文件加密/解密</strong>：<br><code>gpg --encrypt --recipient Alice file.txt</code><br><code>gpg --decrypt file.txt.gpg</code><br>- <strong>归档目录加密</strong>：使用 <code>tar</code> 打包后再加密。<br>- <strong>签名校验</strong>：<br><code>gpg --detach-sign --armor release.tar.gz</code><br><code>gpg --verify release.tar.gz.asc release.tar.gz</code></td></tr>
|
||||
<tr><td><strong>3. 软件包与系统镜像签名</strong></td><td>- Linux 包管理签名：APT、pacman-key 等验证来源可信性。<br>- 容器镜像签名：结合 TUF/Notary 使用 GPG 保护 Docker 镜像完整性。</td></tr>
|
||||
<tr><td><strong>4. SSH 公钥管理与登录</strong></td><td>- 将 GPG 子密钥作为 SSH 密钥使用：<br><code>echo "enable-ssh-support" >> ~/.gnupg/gpg-agent.conf</code><br><code>gpgconf --reload gpg-agent</code><br><code>ssh-add -L</code><br>- 好处：私钥集中管理、PIN保护、跨平台一致。</td></tr>
|
||||
<tr><td><strong>5. 自动化脚本与 CI/CD 环境</strong></td><td>- 用 GPG 自动签名构建产物，供用户验证。<br>- 将签名集成进发布脚本（如 <code>release.sh</code>），自动生成 <code>.sig</code> 并上传。</td></tr>
|
||||
<tr><td><strong>6. 文档与 PDF 数字签名</strong></td><td>- 利用 <code>gpgsm</code> 或 <code>OpenPGP.js</code> 对 PDF、Office 文档签名，保障法律或审计合规性。</td></tr>
|
||||
<tr><td><strong>7. 密码管理与“密码库”</strong></td><td>- <strong>pass</strong>：每个密码为一个 GPG 加密文件，支持 Git 同步和版本控制。<br>- <strong>git-crypt</strong>：自动加密 Git 仓库中的敏感文件，仅授权者可解密。</td></tr>
|
||||
<tr><td><strong>8. 安全聊天与即时通讯</strong></td><td>- 将 OTR 会话密钥托管在 GPG 中（如 <code>mcabber</code> + OTR），实现端到端加密。</td></tr>
|
||||
<tr><td><strong>9. 时间戳与不可篡改日志</strong></td><td>- 结合 GPG 签名与时间戳协议（如 RFC 3161）验证文件/日志未被篡改。</td></tr>
|
||||
<tr><td><strong>10. 去中心化信任与身份管理</strong></td><td>- 使用 Web of Trust 模型构建可信身份网络，用于开源社区签名、Key Signing Party、LDAP 交换等。</td></tr>
|
||||
</tbody></table>
|
||||
<h2 id="an-zhuang-gnupg">安装 GnuPG</h2>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>paru -S gnupg
|
||||
</span></code></pre>
|
||||
<h2 id="sheng-cheng-gong-yao-yu-si-yao">生成公钥与私钥</h2>
|
||||
<p>使用如下命令：</p>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>gpg --full-generate-key
|
||||
</span></code></pre>
|
||||
<p>生成流程：</p>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>gpg (GnuPG) 2.4.7; Copyright (C) 2024 g10 Code GmbH
|
||||
</span><span>This is free software: you are free to change and redistribute it.
|
||||
</span><span>There is NO WARRANTY, to the extent permitted by law.
|
||||
</span><span>
|
||||
</span><span>Please select what kind of key you want:
|
||||
</span><span> (1) RSA and RSA
|
||||
</span><span> (2) DSA and Elgamal
|
||||
</span><span> (3) DSA (sign only)
|
||||
</span><span> (4) RSA (sign only)
|
||||
</span><span> (9) ECC (sign and encrypt) *default*
|
||||
</span><span> (10) ECC (sign only)
|
||||
</span><span> (14) Existing key from card
|
||||
</span><span>Your selection? 9 ## 默认选择ECC算法
|
||||
</span><span>Please select which elliptic curve you want:
|
||||
</span><span> (1) Curve 25519 *default*
|
||||
</span><span> (4) NIST P-384
|
||||
</span><span> (6) Brainpool P-256
|
||||
</span><span>Your selection? 1 ## 默认选择标准椭圆曲线
|
||||
</span><span>Please specify how long the key should be valid.
|
||||
</span><span> 0 = key does not expire
|
||||
</span><span> <n> = key expires in n days
|
||||
</span><span> <n>w = key expires in n weeks
|
||||
</span><span> <n>m = key expires in n months
|
||||
</span><span> <n>y = key expires in n years
|
||||
</span><span>Key is valid for? (0) 1y ## 默认有效期为一年
|
||||
</span><span>Key expires at 2026年06月17日 星期三 13时06分27秒 CST
|
||||
</span><span>Is this correct? (y/N) y
|
||||
</span><span>
|
||||
</span><span>GnuPG needs to construct a user ID to identify your key.
|
||||
</span><span>
|
||||
</span><span>## 输入名字与邮箱,comment可省略
|
||||
</span><span>
|
||||
</span><span>Real name: xxx
|
||||
</span><span>Email address: xxx@gmail.com
|
||||
</span><span>Comment:
|
||||
</span><span>You selected this USER-ID:
|
||||
</span><span> "xxx <xxx@gmail.com>"
|
||||
</span><span>
|
||||
</span><span>Change (N)ame, (C)omment, (E)mail or (O)kay/(Q)uit?
|
||||
</span><span>Change (N)ame, (C)omment, (E)mail or (O)kay/(Q)uit? O
|
||||
</span><span>We need to generate a lot of random bytes. It is a good idea to perform
|
||||
</span><span>some other action (type on the keyboard, move the mouse, utilize the
|
||||
</span><span>disks) during the prime generation; this gives the random number
|
||||
</span><span>generator a better chance to gain enough entropy.
|
||||
</span><span>We need to generate a lot of random bytes. It is a good idea to perform
|
||||
</span><span>some other action (type on the keyboard, move the mouse, utilize the
|
||||
</span><span>disks) during the prime generation; this gives the random number
|
||||
</span><span>generator a better chance to gain enough entropy.
|
||||
</span></code></pre>
|
||||
<h2 id="lie-chu-mi-yao">列出密钥</h2>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>gpg --list-secret-keys --keyid-format long
|
||||
</span></code></pre>
|
||||
<p>其中<code>sec ed25519/xxxxxxxxx 2025-06-17 [SC] [expires: 2026-06-17]</code>的xxxxxxxxx即为公钥ID。</p>
|
||||
<h2 id="fa-bu-gong-yao">发布公钥</h2>
|
||||
<p>例如上传你的 key：</p>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>gpg --send-keys <你的Long‑Key‑ID>
|
||||
</span></code></pre>
|
||||
<p>默认为你的 gpg.conf 中配置的 keyserver，也可以显式指定：</p>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>gpg --keyserver hkps://keys.openpgp.org --send-keys <Key‑ID>
|
||||
</span></code></pre>
|
||||
<p>也可以使用如下命令导出公钥为可读 ASCII 格式，类似ssh-keys，随后即可发布在个人博客上等等。</p>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>gpg --armor --export <Key‑ID> > mypubkey.asc
|
||||
</span></code></pre>
|
||||
<h2 id="che-xiao-gong-yao">撤销公钥</h2>
|
||||
<p>如果怀疑密钥被泄露或被中间人替换，立即发布“撤销证书”（revocation certificate）并上传到 keyserver。</p>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>gpg --gen-revoke <KeyID> > revoke.asc
|
||||
</span></code></pre>
|
||||
<p>上传撤销证书后，所有人都能知道该公钥已不再可信。</p>
|
||||
<hr />
|
||||
<p><strong>Done.</strong></p>
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
<div class="pagination">
|
||||
<div class="pagination__title">
|
||||
<span class="pagination__title-h">Thanks for reading! Read other posts?</span>
|
||||
<hr />
|
||||
</div>
|
||||
<div class="pagination__buttons">
|
||||
<span class="button previous">
|
||||
<a href="https://blog.dich.bid/about-baci/">
|
||||
<span class="button__icon">←</span>
|
||||
<span class="button__text">乱七八糟:Baci实验笔记</span>
|
||||
</a>
|
||||
</span>
|
||||
|
||||
</div>
|
||||
</div>
|
||||
|
||||
</div>
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
<footer class="footer">
|
||||
<div class="footer__inner">
|
||||
<div class="copyright">
|
||||
<span>©
|
||||
2025
|
||||
Dichgrem</span>
|
||||
<span class="copyright-theme">
|
||||
<span class="copyright-theme-sep"> :: CC BY-SA 4.0 :: A friend comes from distant lands</span>
|
||||
</a>
|
||||
</span>
|
||||
</div>
|
||||
</div>
|
||||
</footer>
|
||||
|
||||
</div>
|
||||
</body>
|
||||
</html>
|
||||
|
||||
311
public/about-junk-cleanup/index.html
Normal file
311
public/about-junk-cleanup/index.html
Normal file
@ -0,0 +1,311 @@
|
||||
<!DOCTYPE html>
|
||||
<html lang="en">
|
||||
|
||||
<head>
|
||||
<title>Dich'blog</title>
|
||||
|
||||
<meta http-equiv="content-type" content="text/html; charset=utf-8">
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1">
|
||||
<meta name="robots" content="noodp"/>
|
||||
|
||||
<link rel="stylesheet" href="https://blog.dich.bid/style.css">
|
||||
<link rel="stylesheet" href="https://blog.dich.bid/color/blue.css">
|
||||
|
||||
<link rel="stylesheet" href="https://blog.dich.bid/color/background_dark.css">
|
||||
|
||||
<link rel="stylesheet" href="https://blog.dich.bid/font-hack-subset.css">
|
||||
|
||||
<meta name="description" content="">
|
||||
|
||||
<meta property="og:description" content="">
|
||||
<meta property="og:title" content="Dich'blog">
|
||||
<meta property="og:type" content="article">
|
||||
<meta property="og:url" content="https://blog.dich.bid/about-junk-cleanup/">
|
||||
|
||||
<meta name="twitter:card" content="summary_large_image">
|
||||
<meta name="twitter:description" content="">
|
||||
<meta name="twitter:title" content="Dich'blog">
|
||||
<meta property="twitter:domain" content="blog.dich.bid">
|
||||
<meta property="twitter:url" content="https://blog.dich.bid/about-junk-cleanup/">
|
||||
|
||||
<link rel="alternate" type="application/atom+xml" title="Dich'blog Atom Feed" href="https://blog.dich.bid/atom.xml" />
|
||||
|
||||
|
||||
<link rel="icon" type="image/png" href=/dich.webp />
|
||||
|
||||
<!-- ✅ Added center alignment styles -->
|
||||
<style>
|
||||
.footer {
|
||||
text-align: center;
|
||||
padding: 1rem 0;
|
||||
}
|
||||
|
||||
.footer__inner {
|
||||
display: flex;
|
||||
justify-content: center;
|
||||
flex-direction: column;
|
||||
align-items: center;
|
||||
}
|
||||
|
||||
.copyright {
|
||||
text-align: center;
|
||||
}
|
||||
</style>
|
||||
</head>
|
||||
|
||||
<body class="">
|
||||
<div class="container">
|
||||
|
||||
<header class="header">
|
||||
<div class="header__inner">
|
||||
<div class="header__logo">
|
||||
|
||||
<a href="https://blog.dich.bid" style="text-decoration: none;">
|
||||
<div class="logo">
|
||||
|
||||
Dich'blog
|
||||
|
||||
</div>
|
||||
</a>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
|
||||
<nav class="menu">
|
||||
<ul class="menu__inner">
|
||||
<li><a href="https://blog.dich.bid">blog</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/archive">archive</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/tags">tags</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/weekly">weekly</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/search">search</a></li>
|
||||
|
||||
<li class="active"><a href="https://blog.dich.bid/about">about me</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/links">links</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/atom.xml">rss</a></li>
|
||||
|
||||
<li><a href="https://github.com/Dichgrem" target="_blank" rel="noopener noreferrer">github</a></li>
|
||||
</ul>
|
||||
</nav>
|
||||
|
||||
|
||||
|
||||
</header>
|
||||
|
||||
|
||||
<div class="content">
|
||||
|
||||
<div class="post">
|
||||
|
||||
<h1 class="post-title"><a href="https://blog.dich.bid/about-junk-cleanup/">乱七八糟:垃圾清理的艺术</a></h1>
|
||||
<div class="post-meta-inline">
|
||||
|
||||
<span class="post-date">
|
||||
2023-11-19
|
||||
</span>
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
<span class="post-tags-inline">
|
||||
:: tags:
|
||||
<a class="post-tag" href="https://blog.dich.bid/tags/luan-qi-ba-zao/">#乱七八糟</a></span>
|
||||
|
||||
|
||||
<div class="post-content">
|
||||
<p>前言 在从前的机械硬盘时代，由于硬盘空间小，且没有时常清理垃圾文件，常常导致硬盘空间严重不足；特别是在以 Windows 平台为代表的 C/D盘 体系下。那么，我们常说的垃圾清理，释放硬盘空间，到底是在清理什么？哪些文件可以被清理？</p>
|
||||
<span id="continue-reading"></span><h2 id="la-ji-qing-li">垃圾清理</h2>
|
||||
<p>通常指的是清理计算机硬盘上的<code>不必要或临时</code>文件，以释放硬盘空间。这些文件包括：</p>
|
||||
<ol>
|
||||
<li><strong>临时文件：</strong> 程序在运行时会生成临时文件，以帮助它们完成任务。这些文件在任务完成后不再需要，占据了硬盘空间,却没有被回收。</li>
|
||||
<li><strong>缓存文件：</strong> 许多程序比如浏览器，会在本地存储缓存数据，以加快后续访问速度。但是，这些缓存文件可能会占据大量空间，尤其是在长时间不清理的情况下，这里点名国产的微信和QQ。</li>
|
||||
</ol>
|
||||
<blockquote>
|
||||
<p>注意,清理缓存文件可能意味着加载速度变慢或需要重新下载，耗费流量，视情况而清理。</p>
|
||||
</blockquote>
|
||||
<ol start="3">
|
||||
<li><strong>日志文件：</strong> 许多应用程序会生成日志文件来记录其活动和错误。这些日志文件可能会积累并占用大量空间，尤其是在长时间不清理的情况下。</li>
|
||||
</ol>
|
||||
<blockquote>
|
||||
<p>特别是C盘上的log文件，因为它们记录了系统和应用程序的运行情况，可能会变得相当庞大。因此，定期清理C盘中的log文件是维护系统性能和释放磁盘空间的重要步骤之一。</p>
|
||||
</blockquote>
|
||||
<ul>
|
||||
<li><strong>备份文件：</strong> 如果您的系统或软件定期创建备份或快照，旧版本备份可能会占用大量空间。您可以定期清理旧版本备份以释放空间。</li>
|
||||
<li><strong>大型文件：</strong> 有些应用程序可能会生成大型临时数据文件，如媒体编辑软件的临时视频或音频文件。这些文件在任务完成后可能会被遗留，占据大量空间。</li>
|
||||
</ul>
|
||||
<blockquote>
|
||||
<p>例如PS加载的工作文件，放C盘的话会占用大量空间。</p>
|
||||
</blockquote>
|
||||
<ol start="4">
|
||||
<li><strong>卸载残余：</strong> 在卸载应用程序时，有时候可能会留下一些残余文件，如配置文件、注册表项等，这些文件可能会继续占用硬盘空间，并且在一定程度上影响系统的性能。定期清理这些卸载残余是维护系统健康的一部分。</li>
|
||||
</ol>
|
||||
<blockquote>
|
||||
<p>还记得删除牛马软件时的挽留选项吗？里面往往藏着“保存个人配置”。</p>
|
||||
</blockquote>
|
||||
<ol start="5">
|
||||
<li><strong>重复文件：</strong> 在计算机系统中，有时候可能会出现重复的文件，这些文件可能是因为用户错误地复制或下载了多个副本，也可能是由于应用程序或系统错误导致文件重复。这些重复文件不仅占用了宝贵的存储空间，而且也增加了文件管理的复杂性。</li>
|
||||
</ol>
|
||||
<blockquote>
|
||||
<p>这里再次点名微信，同样一个文件能保存好几次，且不给出具体的存放路径，怪不得动辄十几个G,尾大不掉，真的离谱！</p>
|
||||
</blockquote>
|
||||
<ol start="6">
|
||||
<li><strong>回收站文件：</strong> 删除文件时，它们通常不会立即从硬盘上删除，而是移动到回收站。清空回收站可以释放这些被删除文件所占据的空间。</li>
|
||||
</ol>
|
||||
<blockquote>
|
||||
<p>注意，尽管清空回收站会立即释放硬盘空间，但实际上删除的文件并不会立即被擦除，而是被标记为可以被覆写的空间。在某些情况下，专业的数据恢复软件可能仍然可以找回部分被删除的文件。因此，如果希望永久删除文件而不被恢复，需要使用专门的文件删除工具,来覆盖文件内容以确保无法恢复。</p>
|
||||
</blockquote>
|
||||
<ol start="7">
|
||||
<li><strong>下载文件夹：</strong> 下载文件夹可能会积累大量临时文件、安装程序、文档和媒体文件。定期清理下载文件夹可以帮助释放硬盘空间。</li>
|
||||
<li><strong>不再使用的程序：</strong> 有时候，安装的一些程序你已经不再使用或需要它们。卸载这些程序可以释放相关的硬盘空间。</li>
|
||||
<li><strong>浏览器插件与扩展：</strong> 未使用的浏览器插件和扩展可能会占用不必要的资源和空间。删除不再需要的插件和扩展可以帮助优化浏览器性能并释放空间。</li>
|
||||
<li><strong>安装程序和更新文件：</strong> 在安装程序或更新软件时，临时安装文件可能会留在系统中。这些文件通常可以安全删除，因为安装程序已经完成。</li>
|
||||
</ol>
|
||||
<blockquote>
|
||||
<p>例如安卓上的安装包（APK文件）和下载安装后的EXE文件。</p>
|
||||
</blockquote>
|
||||
<p>需要注意的是，往往有许多牛马软件安装目录和文件目录不规范，或者是在安装时没有设定好，会产生大量垃圾文件；这时就需要垃圾清理工具或者手动遍历文件夹（注意隐藏文件夹）。</p>
|
||||
<h2 id="la-ji-qing-li-ruan-jian">垃圾清理软件</h2>
|
||||
<h3 id="windows-ping-tai">Windows 平台：</h3>
|
||||
<ol>
|
||||
<li><strong><a href="https://diskanalyzer.com/">WizTree</a>：</strong> WizTree是一款功能强大清理垃圾文件/在Windows上找到大文件以释放磁盘空间的首选程序...超级易于使用，快速闪电.</li>
|
||||
<li><strong>Disk Cleanup（磁盘清理）：</strong> Windows 自带的磁盘清理工具，可以帮助您清理不必要的系统文件，包括临时文件、回收站等。</li>
|
||||
<li><strong><a href="https://github.com/bleachbit/bleachbit">BleachBit</a>：</strong> BleachBit 是一款开源的系统清理工具，可以帮助您清理系统中的临时文件、缓存、浏览器历史等。</li>
|
||||
</ol>
|
||||
<h3 id="macos-ping-tai">macOS 平台：</h3>
|
||||
<ol>
|
||||
<li><strong>CleanMyMac X：</strong> CleanMyMac X 是一款功能强大的系统优化工具，可以帮助您清理系统中的垃圾文件、优化性能，并提供了其他的实用工具。</li>
|
||||
<li><strong>Onyx：</strong> Onyx 是一款免费的 macOS 系统维护和优化工具，可以帮助您清理系统缓存、日志文件、临时文件等。</li>
|
||||
<li><strong>AppCleaner：</strong> AppCleaner 是一款简单易用的应用程序卸载工具，可以帮助您彻底清理 macOS 系统中的应用程序及其相关文件。</li>
|
||||
</ol>
|
||||
<h3 id="linux-ping-tai">Linux 平台：</h3>
|
||||
<ol>
|
||||
<li><strong>BleachBit：</strong> BleachBit 不仅适用于 Windows，也提供了 Linux 版本，可以帮助您清理系统中的临时文件、缓存、浏览器历史等。</li>
|
||||
<li><strong>Stacer：</strong> Stacer 是一款开源的系统优化和监控工具，提供了垃圾清理、系统管理、系统监控等功能，适用于多种 Linux 发行版。</li>
|
||||
<li><strong>Sweeper（KDE 扫除者）：</strong> Sweeper 是 KDE 桌面环境的一部分，提供了简单易用的垃圾清理功能，可以帮助您清理系统中的临时文件、缓存等。</li>
|
||||
</ol>
|
||||
<h2 id="arch-linux-qing-li">Arch linux 清理</h2>
|
||||
<ol>
|
||||
<li>
|
||||
<p><strong>缓存清理</strong>:</p>
|
||||
<ul>
|
||||
<li><code>sudo pacman -Sc</code>: 清理包缓存，删除已安装的但不再需要的软件包。</li>
|
||||
<li><code>sudo pacman -Scc</code>: 进一步清理所有包文件，包括已下载的包。</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><strong>系统日志</strong>:</p>
|
||||
<ul>
|
||||
<li><code>/var/log</code> 目录下包含系统日志文件。你可以删除较旧的日志文件，或者使用日志轮换工具，如 <code>logrotate</code>。</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><strong>临时文件</strong>:</p>
|
||||
<ul>
|
||||
<li><code>/tmp</code> 目录下包含临时文件。你可以通过 <code>sudo rm -rf /tmp/*</code> 清理它们。</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><strong>缓存文件</strong>:</p>
|
||||
<ul>
|
||||
<li>一些应用程序会在 <code>~/.cache</code> 目录下存储缓存文件。你可以检查该目录并删除不再需要的文件。</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><strong>AUR 缓存</strong>:</p>
|
||||
<ul>
|
||||
<li>AUR 辅助工具（如 <code>yay</code>）会在 <code>~/.cache/yay</code> 目录下存储构建和下载的软件包。你可以清理这些文件。</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><strong>旧内核</strong>:</p>
|
||||
<ul>
|
||||
<li>如果你安装了多个内核版本，你可以删除不再需要的旧内核。首先使用 <code>uname -r</code> 查看当前内核版本，然后使用 <code>sudo pacman -Rns linux-older-kernel</code> 删除不需要的版本。</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><strong>不再使用的配置文件</strong>:</p>
|
||||
<ul>
|
||||
<li>检查家目录下的隐藏文件，如 <code>~/.config</code>，并删除不再需要的配置文件。</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><strong>Docker日志文件</strong>:<br />
|
||||
使用 <code>docker ps -a</code> 命令查找你感兴趣的容器的 ID。</p>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>docker ps -a
|
||||
</span></code></pre>
|
||||
<p>进入容器的日志目录，路径类似于 <code>/var/lib/docker/containers/<container-id>/</code>。</p>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>cd /var/lib/docker/containers/<container-id>/
|
||||
</span></code></pre>
|
||||
<p>使用命令清理或删除日志文件。你可以删除所有日志文件，或者只删除特定的日志文件。</p>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span># 删除所有日志文件
|
||||
</span><span>rm *.log
|
||||
</span><span>
|
||||
</span><span># 删除特定日志文件（例如 stdout 和 stderr）
|
||||
</span><span>rm *-json.log
|
||||
</span></code></pre>
|
||||
</li>
|
||||
</ol>
|
||||
<h2 id="arch-linux-an-zhuang-bei-fen"><strong>Arch Linux 安装备份</strong></h2>
|
||||
<p>你可以定期备份 Arch Linux 安装的软件列表，以便在需要时轻松还原。</p>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>pacman -Qqe > package-list.txt
|
||||
</span></code></pre>
|
||||
<p>这将列出所有已安装的软件包，并将其保存到文件 <code>package-list.txt</code> 中。在还原系统时，你可以使用以下命令：</p>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>sudo pacman -S --needed - < package-list.txt
|
||||
</span></code></pre>
|
||||
<h2 id="hou-ji">后记</h2>
|
||||
<p>垃圾文件的产生总是无可避免，这是因为随着使用时间的流逝，系统的熵值也在增大；生命以负熵为食，同样的为系统清理垃圾也是逆熵的一部分。在你的生命中会有许多电子设备，但它们往往只有你一任主人，请善待它们！</p>
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
<div class="pagination">
|
||||
<div class="pagination__title">
|
||||
<span class="pagination__title-h">Thanks for reading! Read other posts?</span>
|
||||
<hr />
|
||||
</div>
|
||||
<div class="pagination__buttons">
|
||||
<span class="button previous">
|
||||
<a href="https://blog.dich.bid/about-blog/">
|
||||
<span class="button__icon">←</span>
|
||||
<span class="button__text">乱七八糟:个人博客搭建</span>
|
||||
</a>
|
||||
</span>
|
||||
|
||||
|
||||
<span class="button next">
|
||||
<a href="https://blog.dich.bid/about-git/">
|
||||
<span class="button__text">乱七八糟:Git使用简明手册</span>
|
||||
<span class="button__icon">→</span>
|
||||
</a>
|
||||
</span>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
</div>
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
<footer class="footer">
|
||||
<div class="footer__inner">
|
||||
<div class="copyright">
|
||||
<span>©
|
||||
2025
|
||||
Dichgrem</span>
|
||||
<span class="copyright-theme">
|
||||
<span class="copyright-theme-sep"> :: CC BY-SA 4.0 :: A friend comes from distant lands</span>
|
||||
</a>
|
||||
</span>
|
||||
</div>
|
||||
</div>
|
||||
</footer>
|
||||
|
||||
</div>
|
||||
</body>
|
||||
</html>
|
||||
|
||||
488
public/about-lazyvim/index.html
Normal file
488
public/about-lazyvim/index.html
Normal file
@ -0,0 +1,488 @@
|
||||
<!DOCTYPE html>
|
||||
<html lang="en">
|
||||
|
||||
<head>
|
||||
<title>Dich'blog</title>
|
||||
|
||||
<meta http-equiv="content-type" content="text/html; charset=utf-8">
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1">
|
||||
<meta name="robots" content="noodp"/>
|
||||
|
||||
<link rel="stylesheet" href="https://blog.dich.bid/style.css">
|
||||
<link rel="stylesheet" href="https://blog.dich.bid/color/blue.css">
|
||||
|
||||
<link rel="stylesheet" href="https://blog.dich.bid/color/background_dark.css">
|
||||
|
||||
<link rel="stylesheet" href="https://blog.dich.bid/font-hack-subset.css">
|
||||
|
||||
<meta name="description" content="">
|
||||
|
||||
<meta property="og:description" content="">
|
||||
<meta property="og:title" content="Dich'blog">
|
||||
<meta property="og:type" content="article">
|
||||
<meta property="og:url" content="https://blog.dich.bid/about-lazyvim/">
|
||||
|
||||
<meta name="twitter:card" content="summary_large_image">
|
||||
<meta name="twitter:description" content="">
|
||||
<meta name="twitter:title" content="Dich'blog">
|
||||
<meta property="twitter:domain" content="blog.dich.bid">
|
||||
<meta property="twitter:url" content="https://blog.dich.bid/about-lazyvim/">
|
||||
|
||||
<link rel="alternate" type="application/atom+xml" title="Dich'blog Atom Feed" href="https://blog.dich.bid/atom.xml" />
|
||||
|
||||
|
||||
<link rel="icon" type="image/png" href=/dich.webp />
|
||||
|
||||
<!-- ✅ Added center alignment styles -->
|
||||
<style>
|
||||
.footer {
|
||||
text-align: center;
|
||||
padding: 1rem 0;
|
||||
}
|
||||
|
||||
.footer__inner {
|
||||
display: flex;
|
||||
justify-content: center;
|
||||
flex-direction: column;
|
||||
align-items: center;
|
||||
}
|
||||
|
||||
.copyright {
|
||||
text-align: center;
|
||||
}
|
||||
</style>
|
||||
</head>
|
||||
|
||||
<body class="">
|
||||
<div class="container">
|
||||
|
||||
<header class="header">
|
||||
<div class="header__inner">
|
||||
<div class="header__logo">
|
||||
|
||||
<a href="https://blog.dich.bid" style="text-decoration: none;">
|
||||
<div class="logo">
|
||||
|
||||
Dich'blog
|
||||
|
||||
</div>
|
||||
</a>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
|
||||
<nav class="menu">
|
||||
<ul class="menu__inner">
|
||||
<li><a href="https://blog.dich.bid">blog</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/archive">archive</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/tags">tags</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/weekly">weekly</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/search">search</a></li>
|
||||
|
||||
<li class="active"><a href="https://blog.dich.bid/about">about me</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/links">links</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/atom.xml">rss</a></li>
|
||||
|
||||
<li><a href="https://github.com/Dichgrem" target="_blank" rel="noopener noreferrer">github</a></li>
|
||||
</ul>
|
||||
</nav>
|
||||
|
||||
|
||||
|
||||
</header>
|
||||
|
||||
|
||||
<div class="content">
|
||||
|
||||
<div class="post">
|
||||
|
||||
<h1 class="post-title"><a href="https://blog.dich.bid/about-lazyvim/">乱七八糟:lazyvim快速上手</a></h1>
|
||||
<div class="post-meta-inline">
|
||||
|
||||
<span class="post-date">
|
||||
2025-04-20
|
||||
</span>
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
<span class="post-tags-inline">
|
||||
:: tags:
|
||||
<a class="post-tag" href="https://blog.dich.bid/tags/luan-qi-ba-zao/">#乱七八糟</a></span>
|
||||
|
||||
|
||||
<div class="post-content">
|
||||
<p>前言 LazyVim 是一个基于 Neovim 的现代化配置框架，易于定制和扩展，这里对其介绍并说明使用方法。</p>
|
||||
<span id="continue-reading"></span><h2 id="lazy">Lazy!</h2>
|
||||
<blockquote>
|
||||
<p>LazyVim 是一个基于 Neovim 的现代化配置框架，旨在简化 Neovim 的配置过程。它通过集成的 lazy.nvim 插件管理器，提供了一种易于定制和扩展配置的方式，结合了从头开始配置的灵活性和预配置设置的便利性 。</p>
|
||||
</blockquote>
|
||||
<blockquote>
|
||||
<p>LazyVim 是在Neovim的基础上进行配置，Neovim又继承了vim的操作模式，对vim不熟悉的同学可以看<a href="https://vimsheet.com/">这里</a>。</p>
|
||||
</blockquote>
|
||||
<h2 id="an-zhuang">安装</h2>
|
||||
<p>首先安装neovim,在arch linux上是：</p>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>paru -S neovim
|
||||
</span></code></pre>
|
||||
<p>在Ubuntu上是</p>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>sudo add-apt-repository ppa:neovim-ppa/unstable
|
||||
</span><span>sudo apt update
|
||||
</span><span>sudo apt install -y \ neovim git curl unzip build-essential ripgrep fd-find
|
||||
</span></code></pre>
|
||||
<p>备份现有配置：</p>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>mv ~/.config/nvim ~/.config/nvim.bak
|
||||
</span><span>mv ~/.local/share/nvim ~/.local/share/nvim.bak
|
||||
</span></code></pre>
|
||||
<p>克隆 LazyVim Starter 模板：</p>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>git clone https://github.com/LazyVim/starter ~/.config/nvim
|
||||
</span></code></pre>
|
||||
<p>启动 Neovim：</p>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>nvim
|
||||
</span></code></pre>
|
||||
<p>首次启动时，LazyVim 会自动安装并配置所需的插件。</p>
|
||||
<h2 id="jie-gou">结构</h2>
|
||||
<p>LazyVim 的配置目录通常位于<code>~/.config/nvim/</code>中：</p>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>~/.config/nvim
|
||||
</span><span>❯ tree
|
||||
</span><span>.
|
||||
</span><span>├── init.lua
|
||||
</span><span>├── lazy-lock.json
|
||||
</span><span>├── lazyvim.json
|
||||
</span><span>├── LICENSE
|
||||
</span><span>├── lua
|
||||
</span><span>│ ├── config
|
||||
</span><span>│ │ ├── autocmds.lua
|
||||
</span><span>│ │ ├── keymaps.lua
|
||||
</span><span>│ │ ├── lazy.lua
|
||||
</span><span>│ │ └── options.lua
|
||||
</span><span>│ └── plugins
|
||||
</span><span>│ ├── example.lua
|
||||
</span><span>│ └── mp.lua
|
||||
</span><span>├── README.md
|
||||
</span><span>└── stylua.toml
|
||||
</span><span>
|
||||
</span><span>4 directories, 12 files
|
||||
</span></code></pre>
|
||||
<p>另外在<code>~/.local/share/nvim/lazy/LazyVim/lua/lazyvim/plugins/</code>目录下看到的文件结构，是 LazyVim 为其核心插件和扩展插件提供的模块化配置体系。这些配置文件并不直接出现在<code>~/.config/nvim/lua/plugins/</code>目录中，是因为 LazyVim 采用了模块化和懒加载的设计理念，将核心插件和配置封装在其自身的代码库中。</p>
|
||||
<h3 id="ge-wen-jian-he-mu-lu-de-zuo-yong">各文件和目录的作用</h3>
|
||||
<ul>
|
||||
<li>
|
||||
<p><strong><code>init.lua</code></strong>：主配置文件，负责加载 <code>lua/config/lazy.lua</code>，从而引导整个 LazyVim 的初始化过程。</p>
|
||||
</li>
|
||||
<li>
|
||||
<p><strong><code>lazy-lock.json</code></strong>：由 <code>lazy.nvim</code> 插件管理器生成的锁定文件，记录了已安装插件的精确版本，确保插件的一致性。</p>
|
||||
</li>
|
||||
<li>
|
||||
<p><strong><code>lazyvim.json</code></strong>：用于记录通过 <code>:LazyExtras</code> 命令启用的额外功能（Extras），便于在不同设备间同步配置。</p>
|
||||
</li>
|
||||
<li>
|
||||
<p><strong><code>LICENSE</code></strong> 和 <strong><code>README.md</code></strong>：分别为许可协议和项目说明文档。</p>
|
||||
</li>
|
||||
<li>
|
||||
<p><strong><code>stylua.toml</code></strong>：<code>stylua</code> 的配置文件，用于格式化 Lua 代码。</p>
|
||||
</li>
|
||||
<li>
|
||||
<p><strong><code>lua/config/</code></strong>：包含 Neovim 的基础配置文件，如自动命令（<code>autocmds.lua</code>）、快捷键（<code>keymaps.lua</code>）、插件管理（<code>lazy.lua</code>）和编辑器选项（<code>options.lua</code>）。这些文件会被 LazyVim 自动加载，无需手动引入。</p>
|
||||
</li>
|
||||
<li>
|
||||
<p><strong><code>lua/plugins/</code></strong>：用于添加或修改插件配置的目录。您可以在此目录中添加新的 Lua 文件，以引入其他插件或更改现有插件的设置。
|
||||
</p>
|
||||
</li>
|
||||
</ul>
|
||||
<h2 id="lazyvimzi-dai-pei-zhi">Lazyvim自带配置</h2>
|
||||
<p>在 LazyVim 中，插件被分类为已加载（Loaded）和未加载（Not Loaded）。</p>
|
||||
<h3 id="white-check-mark-yi-jia-zai-de-cha-jian-loaded">✅ 已加载的插件（Loaded）</h3>
|
||||
<ul>
|
||||
<li>
|
||||
<p><strong>blink.cmp</strong>：一个高性能、开箱即用的自动补全引擎，旨在替代 <code>nvim-cmp</code>，提供更快的性能和更少的配置需求。</p>
|
||||
</li>
|
||||
<li>
|
||||
<p><strong>bufferline.nvim</strong>：用于在顶部显示缓冲区列表的插件，提供类似于浏览器标签页的界面。</p>
|
||||
</li>
|
||||
<li>
|
||||
<p><strong>friendly-snippets</strong>：一个包含多种语言代码片段的集合，可与多个片段引擎（如 <code>luasnip</code>）配合使用。</p>
|
||||
</li>
|
||||
<li>
|
||||
<p><strong>gitsigns.nvim</strong>：在编辑器中显示 Git 更改标记（如添加、修改、删除）的插件，增强版本控制的可视化。</p>
|
||||
</li>
|
||||
<li>
|
||||
<p><strong>lazy.nvim</strong>：LazyVim 的插件管理器，支持懒加载和依赖管理，提升启动速度和性能。</p>
|
||||
</li>
|
||||
<li>
|
||||
<p><strong>lualine.nvim</strong>：一个高度可定制的状态栏插件，支持多种主题和组件。</p>
|
||||
</li>
|
||||
<li>
|
||||
<p><strong>mason-lspconfig.nvim</strong> & <strong>mason.nvim</strong>：用于自动安装和配置 LSP（语言服务器协议）服务器的插件组合，简化开发环境的设置。</p>
|
||||
</li>
|
||||
<li>
|
||||
<p><strong>mini.ai</strong>、<strong>mini.pairs</strong>：<code>mini.nvim</code> 插件集合的一部分，分别用于增强文本对象操作和自动括号配对功能。</p>
|
||||
</li>
|
||||
<li>
|
||||
<p><strong>noice.nvim</strong>：改进 Neovim 消息和命令行界面的插件，提供更丰富的 UI 体验。</p>
|
||||
</li>
|
||||
<li>
|
||||
<p><strong>nui.nvim</strong>：一个用于构建 Neovim 用户界面的 Lua 库，被多个插件作为依赖使用。</p>
|
||||
</li>
|
||||
<li>
|
||||
<p><strong>nvim-lint</strong>：一个异步代码检查器，支持多种语言的语法和风格检查。</p>
|
||||
</li>
|
||||
<li>
|
||||
<p><strong>nvim-lspconfig</strong>：提供预配置的 LSP 客户端设置，简化语言服务器的集成。</p>
|
||||
</li>
|
||||
<li>
|
||||
<p><strong>nvim-treesitter</strong>、<strong>nvim-treesitter-textobjects</strong>、<strong>nvim-ts-autotag</strong>：基于 Tree-sitter 的语法高亮和代码结构分析插件，增强代码编辑体验。</p>
|
||||
</li>
|
||||
<li>
|
||||
<p><strong>persistence.nvim</strong>：自动保存和恢复会话的插件，方便在不同项目之间切换。</p>
|
||||
</li>
|
||||
<li>
|
||||
<p><strong>snacks.nvim</strong>：提供快速导航和编辑功能的插件，提升编辑效率。</p>
|
||||
</li>
|
||||
<li>
|
||||
<p><strong>todo-comments.nvim</strong>：高亮和管理代码中的 TODO、FIXME 等注释的插件，方便任务跟踪。</p>
|
||||
</li>
|
||||
<li>
|
||||
<p><strong>tokyonight.nvim</strong>：一个流行的 Neovim 主题，提供多种配色方案。</p>
|
||||
</li>
|
||||
<li>
|
||||
<p><strong>trouble.nvim</strong>：一个用于显示诊断信息（如 LSP 错误、警告）的插件，提供统一的界面。</p>
|
||||
</li>
|
||||
<li>
|
||||
<p><strong>ts-comments.nvim</strong>：基于 Tree-sitter 的注释插件，支持多语言的智能注释功能。</p>
|
||||
</li>
|
||||
<li>
|
||||
<p><strong>which-key.nvim</strong>：在按下快捷键时弹出可用键位提示的插件，帮助记忆和发现快捷键。</p>
|
||||
</li>
|
||||
</ul>
|
||||
<h3 id="x-wei-jia-zai-de-cha-jian-not-loaded">❌ 未加载的插件（Not Loaded）</h3>
|
||||
<ul>
|
||||
<li>
|
||||
<p><strong>catppuccin</strong>：一个柔和的 Neovim 主题，提供多种风格的配色方案。</p>
|
||||
</li>
|
||||
<li>
|
||||
<p><strong>conform.nvim</strong>：一个用于代码格式化的插件，支持多种语言的格式化工具。</p>
|
||||
</li>
|
||||
<li>
|
||||
<p><strong>grug-far.nvim</strong>：一个快速的全局查找和替换插件，提供直观的界面和操作。</p>
|
||||
</li>
|
||||
<li>
|
||||
<p><strong>lazydev.nvim</strong>：用于 LazyVim 插件开发的辅助工具，简化开发流程。</p>
|
||||
</li>
|
||||
<li>
|
||||
<p><strong>markdown-preview.nvim</strong>：在浏览器中实时预览 Markdown 文件的插件，提升写作体验。</p>
|
||||
</li>
|
||||
<li>
|
||||
<p><strong>plenary.nvim</strong>：一个 Lua 函数库，提供多种实用功能，被许多插件作为依赖使用。</p>
|
||||
</li>
|
||||
</ul>
|
||||
<h2 id="zi-ding-yi-pei-zhi">自定义配置</h2>
|
||||
<ul>
|
||||
<li>
|
||||
<p><strong>添加插件</strong>：在 lua/plugins/ 目录下创建一个新的 Lua 文件，返回插件的配置表。</p>
|
||||
</li>
|
||||
<li>
|
||||
<p><strong>修改快捷键</strong>：编辑 lua/config/keymaps.lua 文件，添加或修改快捷键映射。</p>
|
||||
</li>
|
||||
<li>
|
||||
<p><strong>调整选项</strong>：编辑 lua/config/options.lua 文件，设置 Neovim 的行为选项。</p>
|
||||
</li>
|
||||
</ul>
|
||||
<h2 id="chang-yong-kuai-jie-jian">常用快捷键</h2>
|
||||
<p>LazyVim 默认使用<code><space> 作为 <leader></code>，\ 作为<code><localleader></code>，并通过 which-key.nvim 插件动态展示所有以<code><space></code>开头的可用映射，极大降低了记忆成本。</p>
|
||||
<ul>
|
||||
<li><strong>导航与窗口管理</strong></li>
|
||||
</ul>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>- 在窗口间切换：Ctrl +h / Ctrl +j / Ctrl +k / Ctrl +l
|
||||
</span><span>- 调整当前窗口尺寸：Ctrl + ↑ / Ctrl + ↓ / Ctrl + ← / Ctrl + →
|
||||
</span></code></pre>
|
||||
<ul>
|
||||
<li><strong>缓冲区切换与管理</strong></li>
|
||||
</ul>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>- 切换到上一个/下一个缓冲区：Shift +h / Shift +l
|
||||
</span><span>- 切换“另一个”缓冲区：Space + b + b
|
||||
</span><span>- 关闭当前缓冲区：Space + b + d
|
||||
</span><span>- 只保留当前缓冲区：Space + b + o
|
||||
</span></code></pre>
|
||||
<ul>
|
||||
<li><strong>文件与搜索</strong></li>
|
||||
</ul>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>- 新建文件：Space + f + n
|
||||
</span><span>- 打开文件（普通命令）：输入 :e <文件名> 回车
|
||||
</span><span>- 在项目根目录查找文件：Space + Space
|
||||
</span><span>- 在项目根目录查找文件（另一路径）：Space + f + f
|
||||
</span><span>- 在当前工作目录查找文件：Space + f + F
|
||||
</span><span>- 查找 Git 管理的文件：Space + f + g
|
||||
</span><span>- 列出最近打开的文件：Space + f + r
|
||||
</span><span>- 列出所有缓冲区：Space + ,
|
||||
</span><span>- 全局全文搜索：Space + /
|
||||
</span></code></pre>
|
||||
<ul>
|
||||
<li><strong>分割与终端</strong></li>
|
||||
</ul>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>- 向下分割：Space + -
|
||||
</span><span>- 向右分割：Space + |
|
||||
</span><span>- 关闭当前窗口：Space + w + d
|
||||
</span><span>- 窗口最大化/恢复：Space + w + m 或 Space + u + Z
|
||||
</span><span>- 打开根目录终端：Space + f + t
|
||||
</span><span>- 打开当前目录终端：Space + f + T
|
||||
</span><span>- 切换（隐藏/显示）终端：Ctrl + /
|
||||
</span></code></pre>
|
||||
<ul>
|
||||
<li><strong>LSP 相关</strong></li>
|
||||
</ul>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>- 跳转到定义：g + d
|
||||
</span><span>- 查找引用：g + r
|
||||
</span><span>- 跳转到实现：g + I
|
||||
</span><span>- 跳转到声明：g + D
|
||||
</span><span>- 查看文档悬停：K
|
||||
</span><span>- 插入模式签名帮助：Ctrl + k
|
||||
</span><span>- 代码操作：Space + c + a
|
||||
</span><span>- 重命名：Space + c + r
|
||||
</span><span>- 运行 CodeLens：Space + c + c
|
||||
</span><span>- 显示行诊断：Space + c + d
|
||||
</span></code></pre>
|
||||
<ul>
|
||||
<li><strong>Git 操作</strong></li>
|
||||
</ul>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>- 查看状态：Space + g + s
|
||||
</span><span>- 查看差异：Space + g + d
|
||||
</span><span>- 查看行级 Blame：Space + g + b
|
||||
</span><span>- 在浏览器打开当前文件：Space + g + B
|
||||
</span><span>- Git Stash（snacks.nvim）：Space + g + S
|
||||
</span></code></pre>
|
||||
<ul>
|
||||
<li><strong>诊断与快速修复</strong></li>
|
||||
</ul>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>- 打开 Location List：Space + x + l
|
||||
</span><span>- 打开 Quickfix List：Space + x + q
|
||||
</span><span>- 在 Quickfix 跳转：[ q / ] q
|
||||
</span></code></pre>
|
||||
<h2 id="tian-jia-cha-jian">添加插件</h2>
|
||||
<ul>
|
||||
<li><strong>Markdown预览</strong></li>
|
||||
</ul>
|
||||
<p>在<code>~/config/nvim/lua/plugins/</code>下新建一个mp.lua，写入如下配置：</p>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>return {
|
||||
</span><span> {
|
||||
</span><span> "iamcco/markdown-preview.nvim",
|
||||
</span><span> cmd = { "MarkdownPreviewToggle", "MarkdownPreview", "MarkdownPreviewStop" },
|
||||
</span><span> ft = { "markdown" },
|
||||
</span><span> build = ':call mkdp#util#install()'
|
||||
</span><span> }
|
||||
</span><span>}
|
||||
</span></code></pre>
|
||||
<p>随后即可在 Neovim 中打开一个 Markdown 文件，执行以下命令启动预览：</p>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>:MarkdownPreview
|
||||
</span></code></pre>
|
||||
<h2 id="tips">tips</h2>
|
||||
<ul>
|
||||
<li>lazyvim中的行号是非自然序的，这是为了方便光标移动而设置的：你可以在正常模式中通过10k快速移动光标到10行前，10j，10h，10l同理。</li>
|
||||
<li>lazyvim的字体是和终端相同的，不同单独设置；</li>
|
||||
<li>lazyvim中在侧边栏选择文件按d删除,按y复制,按p粘贴,按a创建,按r重命名；</li>
|
||||
<li>gcc:注释当前行；</li>
|
||||
<li>g+ctrl+g:显示信息；</li>
|
||||
<li>alt+h：显示隐藏文件；</li>
|
||||
<li>space+c+f:将当前代码格式化；</li>
|
||||
<li>设置文件编码<code>:set fileencoding?</code></li>
|
||||
<li>设置换行符<code>:set fileformat=unix</code></li>
|
||||
<li>LSP快捷操作：</li>
|
||||
</ul>
|
||||
<table><thead><tr><th>快捷键</th><th>功能</th></tr></thead><tbody>
|
||||
<tr><td><code>gd</code></td><td>跳转到定义（Go to Definition）</td></tr>
|
||||
<tr><td><code>gr</code></td><td>查找引用（Go to References）</td></tr>
|
||||
<tr><td><code>K</code></td><td>显示悬浮文档（Hover）</td></tr>
|
||||
<tr><td><code><leader>rn</code></td><td>重命名（Rename）</td></tr>
|
||||
<tr><td><code><leader>ca</code></td><td>Code Action（修复）</td></tr>
|
||||
<tr><td><code>gl</code></td><td>显示诊断信息（Diagnostic）</td></tr>
|
||||
<tr><td><code>[d</code> / <code>]d</code></td><td>上/下一个诊断问题</td></tr>
|
||||
</tbody></table>
|
||||
<h2 id="edit">Edit!</h2>
|
||||
<blockquote>
|
||||
<p>编辑器的基本素养</p>
|
||||
</blockquote>
|
||||
<p><code>文件操作</code></p>
|
||||
<ul>
|
||||
<li>创建文件/文件夹</li>
|
||||
<li>打开/关闭/切换文件</li>
|
||||
<li>复制/粘贴</li>
|
||||
<li>写入/保存/退出</li>
|
||||
<li>搜索替换</li>
|
||||
</ul>
|
||||
<p><code>字符处理</code></p>
|
||||
<ul>
|
||||
<li>LF/CRLF处理</li>
|
||||
<li>零宽字符处理</li>
|
||||
<li>GBK/UTF-8处理</li>
|
||||
</ul>
|
||||
<p><code>终端</code></p>
|
||||
<ul>
|
||||
<li>打开终端/复用终端</li>
|
||||
</ul>
|
||||
<p><code>其他功能</code></p>
|
||||
<ul>
|
||||
<li>LSP</li>
|
||||
<li>代码调试</li>
|
||||
<li>工作区切换</li>
|
||||
<li>Git支持</li>
|
||||
<li>主题与显示效果</li>
|
||||
</ul>
|
||||
<p>🔗</p>
|
||||
<p><a href="https://yelog.org/2024/08/02/write-markdown-in-neovim-experience-and-tips/">用 neovim 写 markdown 是一种什么样的体验</a></p>
|
||||
<hr />
|
||||
<p><strong>Done.</strong></p>
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
<div class="pagination">
|
||||
<div class="pagination__title">
|
||||
<span class="pagination__title-h">Thanks for reading! Read other posts?</span>
|
||||
<hr />
|
||||
</div>
|
||||
<div class="pagination__buttons">
|
||||
<span class="button previous">
|
||||
<a href="https://blog.dich.bid/about-aria2/">
|
||||
<span class="button__icon">←</span>
|
||||
<span class="button__text">乱七八糟:Aria2各平台使用指南</span>
|
||||
</a>
|
||||
</span>
|
||||
|
||||
|
||||
<span class="button next">
|
||||
<a href="https://blog.dich.bid/about-baci/">
|
||||
<span class="button__text">乱七八糟:Baci实验笔记</span>
|
||||
<span class="button__icon">→</span>
|
||||
</a>
|
||||
</span>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
</div>
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
<footer class="footer">
|
||||
<div class="footer__inner">
|
||||
<div class="copyright">
|
||||
<span>©
|
||||
2025
|
||||
Dichgrem</span>
|
||||
<span class="copyright-theme">
|
||||
<span class="copyright-theme-sep"> :: CC BY-SA 4.0 :: A friend comes from distant lands</span>
|
||||
</a>
|
||||
</span>
|
||||
</div>
|
||||
</div>
|
||||
</footer>
|
||||
|
||||
</div>
|
||||
</body>
|
||||
</html>
|
||||
|
||||
402
public/about-markdown/index.html
Normal file
402
public/about-markdown/index.html
Normal file
@ -0,0 +1,402 @@
|
||||
<!DOCTYPE html>
|
||||
<html lang="en">
|
||||
|
||||
<head>
|
||||
<title>Dich'blog</title>
|
||||
|
||||
<meta http-equiv="content-type" content="text/html; charset=utf-8">
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1">
|
||||
<meta name="robots" content="noodp"/>
|
||||
|
||||
<link rel="stylesheet" href="https://blog.dich.bid/style.css">
|
||||
<link rel="stylesheet" href="https://blog.dich.bid/color/blue.css">
|
||||
|
||||
<link rel="stylesheet" href="https://blog.dich.bid/color/background_dark.css">
|
||||
|
||||
<link rel="stylesheet" href="https://blog.dich.bid/font-hack-subset.css">
|
||||
|
||||
<meta name="description" content="">
|
||||
|
||||
<meta property="og:description" content="">
|
||||
<meta property="og:title" content="Dich'blog">
|
||||
<meta property="og:type" content="article">
|
||||
<meta property="og:url" content="https://blog.dich.bid/about-markdown/">
|
||||
|
||||
<meta name="twitter:card" content="summary_large_image">
|
||||
<meta name="twitter:description" content="">
|
||||
<meta name="twitter:title" content="Dich'blog">
|
||||
<meta property="twitter:domain" content="blog.dich.bid">
|
||||
<meta property="twitter:url" content="https://blog.dich.bid/about-markdown/">
|
||||
|
||||
<link rel="alternate" type="application/atom+xml" title="Dich'blog Atom Feed" href="https://blog.dich.bid/atom.xml" />
|
||||
|
||||
|
||||
<link rel="icon" type="image/png" href=/dich.webp />
|
||||
|
||||
<!-- ✅ Added center alignment styles -->
|
||||
<style>
|
||||
.footer {
|
||||
text-align: center;
|
||||
padding: 1rem 0;
|
||||
}
|
||||
|
||||
.footer__inner {
|
||||
display: flex;
|
||||
justify-content: center;
|
||||
flex-direction: column;
|
||||
align-items: center;
|
||||
}
|
||||
|
||||
.copyright {
|
||||
text-align: center;
|
||||
}
|
||||
</style>
|
||||
</head>
|
||||
|
||||
<body class="">
|
||||
<div class="container">
|
||||
|
||||
<header class="header">
|
||||
<div class="header__inner">
|
||||
<div class="header__logo">
|
||||
|
||||
<a href="https://blog.dich.bid" style="text-decoration: none;">
|
||||
<div class="logo">
|
||||
|
||||
Dich'blog
|
||||
|
||||
</div>
|
||||
</a>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
|
||||
<nav class="menu">
|
||||
<ul class="menu__inner">
|
||||
<li><a href="https://blog.dich.bid">blog</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/archive">archive</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/tags">tags</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/weekly">weekly</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/search">search</a></li>
|
||||
|
||||
<li class="active"><a href="https://blog.dich.bid/about">about me</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/links">links</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/atom.xml">rss</a></li>
|
||||
|
||||
<li><a href="https://github.com/Dichgrem" target="_blank" rel="noopener noreferrer">github</a></li>
|
||||
</ul>
|
||||
</nav>
|
||||
|
||||
|
||||
|
||||
</header>
|
||||
|
||||
|
||||
<div class="content">
|
||||
|
||||
<div class="post">
|
||||
|
||||
<h1 class="post-title"><a href="https://blog.dich.bid/about-markdown/">乱七八糟:Markdown使用快速教程</a></h1>
|
||||
<div class="post-meta-inline">
|
||||
|
||||
<span class="post-date">
|
||||
2025-04-08
|
||||
</span>
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
<span class="post-tags-inline">
|
||||
:: tags:
|
||||
<a class="post-tag" href="https://blog.dich.bid/tags/luan-qi-ba-zao/">#乱七八糟</a></span>
|
||||
|
||||
|
||||
<div class="post-content">
|
||||
<p>前言 本文为 Markdown 教程，内容涵盖 Markdown 的历史、作用、基本语法和显示效果，可以在github将本文的源码拷贝供大家参考和学习。</p>
|
||||
<span id="continue-reading"></span><h1 id="markdown-jiao-cheng">Markdown 教程</h1>
|
||||
<h2 id="ling-chang-yong-de-markdownbian-ji-qi">零.常用的markdown编辑器</h2>
|
||||
<ul>
|
||||
<li>VSCode的<code>Markdown Preview Enhanced</code>插件；</li>
|
||||
<li>跨平台的<a href="https://obsidian.md/download">obsdian</a>或者<a href="https://github.com/1943time/inkdown">inkdown</a>，<a href="https://github.com/laurent22/joplin">joplin</a>或<a href="https://github.com/Zettlr/Zettlr">zettlr</a></li>
|
||||
</ul>
|
||||
<h2 id="yi-markdown-jian-jie">一、Markdown 简介</h2>
|
||||
<h3 id="1-1-shen-me-shi-markdown">1.1 什么是 Markdown？</h3>
|
||||
<p>Markdown 是一种轻量级标记语言，最初由约翰·格鲁伯（John Gruber）在 2004 年创建，其设计目标在于简洁易读，同时能够快速转换为 HTML。Markdown 被广泛用于撰写文档、博客、论坛帖子以及 README 文档，其直观的语法和高度可读性受到开发者和写作者的一致好评。</p>
|
||||
<h3 id="1-2-markdown-de-li-shi-he-zuo-yong">1.2 Markdown 的历史和作用</h3>
|
||||
<ul>
|
||||
<li>
|
||||
<p><strong>历史沿革：</strong><br />
|
||||
2004 年左右，随着互联网内容量的增加以及对纯文本格式的需求不断上升，人们开始寻找一种既能保留纯文本的可读性，又能方便地生成格式化内容（如 HTML）的解决方案。Markdown 应运而生。经过十多年的发展，Markdown 已衍生出多个方言（例如 GitHub Flavored Markdown、CommonMark 等），并被各种编辑器、静态博客生成器（如 Zola、Jekyll、Hugo 等）以及内容管理系统所支持。</p>
|
||||
</li>
|
||||
<li>
|
||||
<p><strong>主要作用：</strong></p>
|
||||
<ul>
|
||||
<li><strong>快速排版：</strong> Markdown 语法简单，使用自然语言符号来表示标题、列表、链接、图片等格式。</li>
|
||||
<li><strong>跨平台兼容：</strong> 由于基于纯文本格式，Markdown 文件可以在任何文本编辑器中打开和编辑，而且可以很容易地转换成 HTML、PDF 等格式。</li>
|
||||
<li><strong>降低学习成本：</strong> 与复杂的 HTML 标记相比，Markdown 的语法简单易懂，非常适合非程序员使用。</li>
|
||||
<li><strong>促进内容创作：</strong> 许多博客平台和文档系统都采用 Markdown 作为主要写作格式，降低了内容创作和协作的门槛。</li>
|
||||
</ul>
|
||||
</li>
|
||||
</ul>
|
||||
<hr />
|
||||
<h2 id="er-markdown-ji-ben-yu-fa">二、Markdown 基本语法</h2>
|
||||
<p>下面详细介绍 Markdown 常用的语法，并演示其在渲染后显示的效果。</p>
|
||||
<h3 id="2-1-biao-ti">2.1 标题</h3>
|
||||
<p>使用井号 <code>#</code> 来表示标题，井号的数量表示标题级别（1~6级）。</p>
|
||||
<pre data-lang="markdown" style="background-color:#151515;color:#e8e8d3;" class="language-markdown "><code class="language-markdown" data-lang="markdown"><span># </span><span style="color:#ffb964;">这是一级标题
|
||||
</span><span>## </span><span style="color:#ffb964;">这是二级标题
|
||||
</span><span>### </span><span style="color:#ffb964;">这是三级标题
|
||||
</span><span>#### </span><span style="color:#ffb964;">这是四级标题
|
||||
</span><span>##### </span><span style="color:#ffb964;">这是五级标题
|
||||
</span><span>###### </span><span style="color:#ffb964;">这是六级标题
|
||||
</span></code></pre>
|
||||
<p><strong>渲染效果：</strong></p>
|
||||
<h1 id="zhe-shi-yi-ji-biao-ti">这是一级标题</h1>
|
||||
<h2 id="zhe-shi-er-ji-biao-ti">这是二级标题</h2>
|
||||
<h3 id="zhe-shi-san-ji-biao-ti">这是三级标题</h3>
|
||||
<h4 id="zhe-shi-si-ji-biao-ti">这是四级标题</h4>
|
||||
<h5 id="zhe-shi-wu-ji-biao-ti">这是五级标题</h5>
|
||||
<h6 id="zhe-shi-liu-ji-biao-ti">这是六级标题</h6>
|
||||
<hr />
|
||||
<h3 id="2-2-qiang-diao-wen-ben">2.2 强调文本</h3>
|
||||
<ul>
|
||||
<li><em>斜体</em>：在文字两侧加上一个星号 <code>*</code> 或下划线 <code>_</code>。</li>
|
||||
<li><strong>加粗</strong>：在文字两侧加上两个星号 <code>**</code> 或下划线 <code>__</code>。</li>
|
||||
<li><em><strong>斜体加粗</strong></em>：在文字两侧加上三个星号 <code>***</code>。</li>
|
||||
</ul>
|
||||
<pre data-lang="markdown" style="background-color:#151515;color:#e8e8d3;" class="language-markdown "><code class="language-markdown" data-lang="markdown"><span>*这是斜体*
|
||||
</span><span>_这也是斜体_
|
||||
</span><span>
|
||||
</span><span>**这是加粗**
|
||||
</span><span>__这也是加粗__
|
||||
</span><span>
|
||||
</span><span>***这是斜体加粗***
|
||||
</span></code></pre>
|
||||
<p><strong>渲染效果：</strong></p>
|
||||
<p><em>这是斜体</em><br />
|
||||
<em>这也是斜体</em></p>
|
||||
<p><strong>这是加粗</strong><br />
|
||||
<strong>这也是加粗</strong></p>
|
||||
<p><em><strong>这是斜体加粗</strong></em></p>
|
||||
<hr />
|
||||
<h3 id="2-3-lie-biao">2.3 列表</h3>
|
||||
<h4 id="wu-xu-lie-biao">无序列表</h4>
|
||||
<p>使用 <code>-</code>、<code>*</code> 或 <code>+</code> 表示无序列表项。</p>
|
||||
<pre data-lang="markdown" style="background-color:#151515;color:#e8e8d3;" class="language-markdown "><code class="language-markdown" data-lang="markdown"><span>- 项目 1
|
||||
</span><span>- 项目 2
|
||||
</span><span> - 子项目 2.1
|
||||
</span><span> - 子项目 2.2
|
||||
</span><span>- 项目 3
|
||||
</span></code></pre>
|
||||
<p><strong>渲染效果：</strong></p>
|
||||
<ul>
|
||||
<li>项目 1</li>
|
||||
<li>项目 2
|
||||
<ul>
|
||||
<li>子项目 2.1</li>
|
||||
<li>子项目 2.2</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>项目 3</li>
|
||||
</ul>
|
||||
<h4 id="you-xu-lie-biao">有序列表</h4>
|
||||
<p>使用数字后面跟点号来表示有序列表：</p>
|
||||
<pre data-lang="markdown" style="background-color:#151515;color:#e8e8d3;" class="language-markdown "><code class="language-markdown" data-lang="markdown"><span>1. 第一项
|
||||
</span><span>2. 第二项
|
||||
</span><span>3. 第三项
|
||||
</span></code></pre>
|
||||
<p><strong>渲染效果：</strong></p>
|
||||
<ol>
|
||||
<li>第一项</li>
|
||||
<li>第二项</li>
|
||||
<li>第三项</li>
|
||||
</ol>
|
||||
<hr />
|
||||
<h3 id="2-4-lian-jie-yu-tu-pian">2.4 链接与图片</h3>
|
||||
<h4 id="lian-jie">链接</h4>
|
||||
<p>格式：<a href="https://blog.dich.bid/about-markdown/URL" title="可选标题">链接文字</a>。</p>
|
||||
<pre data-lang="markdown" style="background-color:#151515;color:#e8e8d3;" class="language-markdown "><code class="language-markdown" data-lang="markdown"><span>[GitHub](https://github.com </span><span style="color:#556633;">"</span><span style="color:#99ad6a;">GitHub 官网</span><span style="color:#556633;">"</span><span>)
|
||||
</span></code></pre>
|
||||
<p><strong>渲染效果：</strong><br />
|
||||
<a href="https://github.com" title="GitHub 官网">GitHub</a></p>
|
||||
<h4 id="tu-pian">图片</h4>
|
||||
<p>格式：<code></code>。</p>
|
||||
<pre data-lang="markdown" style="background-color:#151515;color:#e8e8d3;" class="language-markdown "><code class="language-markdown" data-lang="markdown"><span>![Markdown Logo](https://upload.wikimedia.org/wikipedia/commons/4/48/Markdown-mark.svg </span><span style="color:#556633;">"</span><span style="color:#99ad6a;">Markdown</span><span style="color:#556633;">"</span><span>)
|
||||
</span></code></pre>
|
||||
<p><strong>渲染效果：</strong></p>
|
||||
<p><img src="https://upload.wikimedia.org/wikipedia/commons/4/48/Markdown-mark.svg" alt="Markdown Logo" /></p>
|
||||
<hr />
|
||||
<h3 id="2-5-dai-ma">2.5 代码</h3>
|
||||
<h4 id="xing-nei-dai-ma">行内代码</h4>
|
||||
<p>使用反引号 <code>`</code> 来表示行内代码。</p>
|
||||
<pre data-lang="markdown" style="background-color:#151515;color:#e8e8d3;" class="language-markdown "><code class="language-markdown" data-lang="markdown"><span>使用 `printf()` 函数输出内容。
|
||||
</span></code></pre>
|
||||
<p><strong>渲染效果：</strong><br />
|
||||
使用 <code>printf()</code> 函数输出内容。</p>
|
||||
<h4 id="dai-ma-kuai">代码块</h4>
|
||||
<p>代码块使用三个反引号（```）包裹，也可以指定语言以便进行语法高亮。</p>
|
||||
<pre data-lang="markdown" style="background-color:#151515;color:#e8e8d3;" class="language-markdown "><code class="language-markdown" data-lang="markdown"><span>```</span><span style="color:#7697d6;">python
|
||||
</span><span style="color:#8fbfdc;">def </span><span style="color:#fad07a;">hello</span><span>():
|
||||
</span><span> </span><span style="color:#ffb964;">print</span><span>(</span><span style="color:#556633;">"</span><span style="color:#99ad6a;">Hello, World!</span><span style="color:#556633;">"</span><span>)
|
||||
</span><span>```
|
||||
</span></code></pre>
|
||||
<blockquote>
|
||||
<p>注意：上述代码块中第一行的三个反引号后面紧跟着语言名称（如 <code>python</code>），结束时用相同的三个反引号结束。</p>
|
||||
</blockquote>
|
||||
<p><strong>渲染效果（依赖编辑器或平台的语法高亮支持）：</strong></p>
|
||||
<pre data-lang="python" style="background-color:#151515;color:#e8e8d3;" class="language-python "><code class="language-python" data-lang="python"><span style="color:#8fbfdc;">def </span><span style="color:#fad07a;">hello</span><span>():
|
||||
</span><span> </span><span style="color:#ffb964;">print</span><span>(</span><span style="color:#556633;">"</span><span style="color:#99ad6a;">Hello, World!</span><span style="color:#556633;">"</span><span>)
|
||||
</span></code></pre>
|
||||
<hr />
|
||||
<h3 id="2-6-yin-yong-kuai">2.6 引用块</h3>
|
||||
<p>使用 <code>></code> 来表示引用（Blockquote）。</p>
|
||||
<pre data-lang="markdown" style="background-color:#151515;color:#e8e8d3;" class="language-markdown "><code class="language-markdown" data-lang="markdown"><span>> 这是引用的内容，可以用于引用名言或文章片段。
|
||||
</span><span>>
|
||||
</span><span>> 多行引用时，每行前面都加上 `>`。
|
||||
</span></code></pre>
|
||||
<p><strong>渲染效果：</strong></p>
|
||||
<blockquote>
|
||||
<p>这是引用的内容，可以用于引用名言或文章片段。</p>
|
||||
<p>多行引用时，每行前面都加上 <code>></code>。</p>
|
||||
</blockquote>
|
||||
<hr />
|
||||
<h3 id="2-7-fen-ge-xian">2.7 分割线</h3>
|
||||
<p>使用三个或更多的横线 <code>---</code>、星号 <code>***</code> 或下划线 <code>___</code> 来产生水平分割线。</p>
|
||||
<pre data-lang="markdown" style="background-color:#151515;color:#e8e8d3;" class="language-markdown "><code class="language-markdown" data-lang="markdown"><span>---
|
||||
</span><span>或者
|
||||
</span><span>***
|
||||
</span><span>或者
|
||||
</span><span>___
|
||||
</span></code></pre>
|
||||
<p><strong>渲染效果：</strong></p>
|
||||
<hr />
|
||||
<p>或者</p>
|
||||
<hr />
|
||||
<p>或者</p>
|
||||
<hr />
|
||||
<hr />
|
||||
<h3 id="2-8-biao-ge">2.8 表格</h3>
|
||||
<p>Markdown 表格可以使用管道符 <code>|</code> 和短横线 <code>-</code> 来创建。</p>
|
||||
<pre data-lang="markdown" style="background-color:#151515;color:#e8e8d3;" class="language-markdown "><code class="language-markdown" data-lang="markdown"><span>| 表头1 | 表头2 | 表头3 |
|
||||
</span><span>| :--- | :---: | ---: |
|
||||
</span><span>| 左对齐 | 居中对齐 | 右对齐 |
|
||||
</span><span>| 单元格内容 | 更多内容 | 数据 |
|
||||
</span></code></pre>
|
||||
<p><strong>渲染效果：</strong></p>
|
||||
<table><thead><tr><th style="text-align: left">表头1</th><th style="text-align: center">表头2</th><th style="text-align: right">表头3</th></tr></thead><tbody>
|
||||
<tr><td style="text-align: left">左对齐</td><td style="text-align: center">居中对齐</td><td style="text-align: right">右对齐</td></tr>
|
||||
<tr><td style="text-align: left">单元格内容</td><td style="text-align: center">更多内容</td><td style="text-align: right">数据</td></tr>
|
||||
</tbody></table>
|
||||
<blockquote>
|
||||
<p><strong>注：</strong><br />
|
||||
“:---” 表示左对齐；<br />
|
||||
“:---:” 表示居中对齐；<br />
|
||||
“---:” 表示右对齐。</p>
|
||||
</blockquote>
|
||||
<hr />
|
||||
<h2 id="san-markdown-gao-ji-yu-fa-yu-kuo-zhan">三、Markdown 高级语法与扩展</h2>
|
||||
<p>不同平台可能支持额外的 Markdown 扩展语法，下面列举一些常见的扩展功能：</p>
|
||||
<h3 id="3-1-jiao-zhu">3.1 脚注</h3>
|
||||
<p>某些 Markdown 方言支持脚注。脚注格式如下：</p>
|
||||
<pre data-lang="markdown" style="background-color:#151515;color:#e8e8d3;" class="language-markdown "><code class="language-markdown" data-lang="markdown"><span>这是一个带脚注的句子.[^1]
|
||||
</span><span>
|
||||
</span><span>[</span><span style="color:#ffb964;">^1</span><span>]: 这是脚注的内容。
|
||||
</span></code></pre>
|
||||
<p><strong>渲染效果：</strong></p>
|
||||
<p>这是一个带脚注的句子.<sup class="footnote-reference"><a href="#1">1</a></sup></p>
|
||||
<div class="footnote-definition" id="1"><sup class="footnote-definition-label">1</sup>
|
||||
<p>这是脚注的内容。</p>
|
||||
</div>
|
||||
<h3 id="3-2-ren-wu-lie-biao">3.2 任务列表</h3>
|
||||
<p>GitHub Flavored Markdown（GFM）支持任务列表，可以用于表示待办事项。</p>
|
||||
<pre data-lang="markdown" style="background-color:#151515;color:#e8e8d3;" class="language-markdown "><code class="language-markdown" data-lang="markdown"><span>- [x] 完成 Markdown 教程
|
||||
</span><span>- [ ] 阅读更多文章
|
||||
</span><span>- [ ] 分享教程
|
||||
</span></code></pre>
|
||||
<p><strong>渲染效果：</strong></p>
|
||||
<ul>
|
||||
<li><input disabled="" type="checkbox" checked=""/>
|
||||
完成 Markdown 教程</li>
|
||||
<li><input disabled="" type="checkbox"/>
|
||||
阅读更多文章</li>
|
||||
<li><input disabled="" type="checkbox"/>
|
||||
分享教程</li>
|
||||
</ul>
|
||||
<hr />
|
||||
<h2 id="si-markdown-shi-yong-zhu-yi-shi-xiang">四、Markdown 使用注意事项</h2>
|
||||
<ol>
|
||||
<li>
|
||||
<p><strong>空行与段落：</strong><br />
|
||||
Markdown 使用一个或多个空行来分隔不同的段落。如果要换行但不创建新段落，在行尾添加两个或更多空格后回车即可。</p>
|
||||
</li>
|
||||
<li>
|
||||
<p><strong>转义字符：</strong><br />
|
||||
如果想要显示 Markdown 特殊符号而不被解析，比如 <code>*</code>、<code>#</code>、<code>\</code> 等，可以在前面加上反斜杠 <code>\</code>。</p>
|
||||
<pre data-lang="markdown" style="background-color:#151515;color:#e8e8d3;" class="language-markdown "><code class="language-markdown" data-lang="markdown"><span>\*这不是斜体，而是普通的星号\*
|
||||
</span></code></pre>
|
||||
<p><strong>渲染效果：</strong><br />
|
||||
*这不是斜体，而是普通的星号*</p>
|
||||
</li>
|
||||
<li>
|
||||
<p><strong>原始文本展示：</strong><br />
|
||||
为了展示 Markdown 源码而不被渲染，请使用代码块（反引号包围）或适用平台支持的原始文本标签（例如 <code>{% raw %}</code> 与 <code>{% endraw %}</code>）。</p>
|
||||
</li>
|
||||
</ol>
|
||||
<hr />
|
||||
<p><strong>Done.</strong></p>
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
<div class="pagination">
|
||||
<div class="pagination__title">
|
||||
<span class="pagination__title-h">Thanks for reading! Read other posts?</span>
|
||||
<hr />
|
||||
</div>
|
||||
<div class="pagination__buttons">
|
||||
<span class="button previous">
|
||||
<a href="https://blog.dich.bid/about-gfs/">
|
||||
<span class="button__icon">←</span>
|
||||
<span class="button__text">乱七八糟:GFS项目考量笔记</span>
|
||||
</a>
|
||||
</span>
|
||||
|
||||
|
||||
<span class="button next">
|
||||
<a href="https://blog.dich.bid/about-aria2/">
|
||||
<span class="button__text">乱七八糟:Aria2各平台使用指南</span>
|
||||
<span class="button__icon">→</span>
|
||||
</a>
|
||||
</span>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
</div>
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
<footer class="footer">
|
||||
<div class="footer__inner">
|
||||
<div class="copyright">
|
||||
<span>©
|
||||
2025
|
||||
Dichgrem</span>
|
||||
<span class="copyright-theme">
|
||||
<span class="copyright-theme-sep"> :: CC BY-SA 4.0 :: A friend comes from distant lands</span>
|
||||
</a>
|
||||
</span>
|
||||
</div>
|
||||
</div>
|
||||
</footer>
|
||||
|
||||
</div>
|
||||
</body>
|
||||
</html>
|
||||
|
||||
330
public/about-mechrev-keyboard/index.html
Normal file
330
public/about-mechrev-keyboard/index.html
Normal file
@ -0,0 +1,330 @@
|
||||
<!DOCTYPE html>
|
||||
<html lang="en">
|
||||
|
||||
<head>
|
||||
<title>Dich'blog</title>
|
||||
|
||||
<meta http-equiv="content-type" content="text/html; charset=utf-8">
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1">
|
||||
<meta name="robots" content="noodp"/>
|
||||
|
||||
<link rel="stylesheet" href="https://blog.dich.bid/style.css">
|
||||
<link rel="stylesheet" href="https://blog.dich.bid/color/blue.css">
|
||||
|
||||
<link rel="stylesheet" href="https://blog.dich.bid/color/background_dark.css">
|
||||
|
||||
<link rel="stylesheet" href="https://blog.dich.bid/font-hack-subset.css">
|
||||
|
||||
<meta name="description" content="">
|
||||
|
||||
<meta property="og:description" content="">
|
||||
<meta property="og:title" content="Dich'blog">
|
||||
<meta property="og:type" content="article">
|
||||
<meta property="og:url" content="https://blog.dich.bid/about-mechrev-keyboard/">
|
||||
|
||||
<meta name="twitter:card" content="summary_large_image">
|
||||
<meta name="twitter:description" content="">
|
||||
<meta name="twitter:title" content="Dich'blog">
|
||||
<meta property="twitter:domain" content="blog.dich.bid">
|
||||
<meta property="twitter:url" content="https://blog.dich.bid/about-mechrev-keyboard/">
|
||||
|
||||
<link rel="alternate" type="application/atom+xml" title="Dich'blog Atom Feed" href="https://blog.dich.bid/atom.xml" />
|
||||
|
||||
|
||||
<link rel="icon" type="image/png" href=/dich.webp />
|
||||
|
||||
<!-- ✅ Added center alignment styles -->
|
||||
<style>
|
||||
.footer {
|
||||
text-align: center;
|
||||
padding: 1rem 0;
|
||||
}
|
||||
|
||||
.footer__inner {
|
||||
display: flex;
|
||||
justify-content: center;
|
||||
flex-direction: column;
|
||||
align-items: center;
|
||||
}
|
||||
|
||||
.copyright {
|
||||
text-align: center;
|
||||
}
|
||||
</style>
|
||||
</head>
|
||||
|
||||
<body class="">
|
||||
<div class="container">
|
||||
|
||||
<header class="header">
|
||||
<div class="header__inner">
|
||||
<div class="header__logo">
|
||||
|
||||
<a href="https://blog.dich.bid" style="text-decoration: none;">
|
||||
<div class="logo">
|
||||
|
||||
Dich'blog
|
||||
|
||||
</div>
|
||||
</a>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
|
||||
<nav class="menu">
|
||||
<ul class="menu__inner">
|
||||
<li><a href="https://blog.dich.bid">blog</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/archive">archive</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/tags">tags</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/weekly">weekly</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/search">search</a></li>
|
||||
|
||||
<li class="active"><a href="https://blog.dich.bid/about">about me</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/links">links</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/atom.xml">rss</a></li>
|
||||
|
||||
<li><a href="https://github.com/Dichgrem" target="_blank" rel="noopener noreferrer">github</a></li>
|
||||
</ul>
|
||||
</nav>
|
||||
|
||||
|
||||
|
||||
</header>
|
||||
|
||||
|
||||
<div class="content">
|
||||
|
||||
<div class="post">
|
||||
|
||||
<h1 class="post-title"><a href="https://blog.dich.bid/about-mechrev-keyboard/">乱七八糟:机械革命键盘失灵拯救记</a></h1>
|
||||
<div class="post-meta-inline">
|
||||
|
||||
<span class="post-date">
|
||||
2023-09-04
|
||||
</span>
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
<span class="post-tags-inline">
|
||||
:: tags:
|
||||
<a class="post-tag" href="https://blog.dich.bid/tags/luan-qi-ba-zao/">#乱七八糟</a></span>
|
||||
|
||||
|
||||
<div class="post-content">
|
||||
<p>前言 机械革命作为一款极高性价比的笔记本，其优惠的力度和问题不断的故障让玩家们爱恨交织；作者在其上安装 Linux 时遇到了键盘失灵的问题，为了避免更多人踩坑，故写本文。</p>
|
||||
<span id="continue-reading"></span><h2 id="yi-gu-zhang-qing-kuang">一.故障情况</h2>
|
||||
<p>作者在一台锐龙平台的笔记本上安装 Debian 时，先在虚拟机中尝试安装，没有发现异常；随后在实体机安装时发现 liveCD 中键盘不可用，无法设置密码和主机名，在连接外接键盘后安装完成，却发现Fn快捷键仍然可用。</p>
|
||||
<h2 id="er-ju-ti-si-lu">二.具体思路</h2>
|
||||
<p>根据机革一贯的“特性”，作者猜测是因为 BIOS 或者 ACPI 出现了故障，随后在翻阅论坛时发现是由于锐龙笔记本键盘中断描述与其他键盘不同：其为边缘敏 感、低电平有效的；而蛟龙16K机器键盘实际是边缘敏感、高电平有效（Edge ActiveHigh）。结合 linux 的特性，读取到边缘敏感、低电平有效的中断时，会认为 BIOS 有Bug，会直接当成边缘敏感、高电平有效进行处理。因此，键盘就没有了响应。</p>
|
||||
<h2 id="san-jie-jue-fang-fa">三.解决方法</h2>
|
||||
<p>既然是高低电平表述的错误，那么我们只需建立DSDT 表副本，将其修改，然后让它优先启动，从而让键盘配置正常；另外还存在 BIOS 修复，内核编译的方法，比较复杂，这里不做说明。</p>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>首先建立一个DSDT文件夹：
|
||||
</span><span>sudo su
|
||||
</span><span>mkdir -p /home/dsdt
|
||||
</span><span>
|
||||
</span><span>随后将系统的DSDT表读取到里面，并安装acpica-tools：
|
||||
</span><span>cat /sys/firmware/acpi/tables/DSDT > dsdt.dat
|
||||
</span><span>apt install acpica-tools
|
||||
</span><span>iasl -d dsdt.dat
|
||||
</span><span>
|
||||
</span><span>进入vim编辑DSDT表，没有vim的先安装一个：
|
||||
</span><span>apt install vim
|
||||
</span><span>vim dsdt.dsl
|
||||
</span><span>
|
||||
</span><span>搜索并替换 Device(PS2K) 下面的
|
||||
</span><span>IRQ (Edge, ActiveLow, Shared, )
|
||||
</span><span>为
|
||||
</span><span>IRQ (Edge, ActiveHigh, Shared, )
|
||||
</span><span>
|
||||
</span><span>vim搜索的方法为在命令模式下按下“/”，键入搜索字符并回车即可，按“n”跳转到下一处，“N”跳转到前一处，按: wq保存：
|
||||
</span><span>
|
||||
</span><span>随后搜索DefinitionBlock，将其步进值增加一（十六进制），即更改
|
||||
</span><span>DefinitionBlock ("", "DSDT", 2, "ALASKA", "A M I", 0x01072009)
|
||||
</span><span>为
|
||||
</span><span>DefinitionBlock ("", "DSDT", 2, "ALASKA", "A M I", 0x0107200A)
|
||||
</span><span>
|
||||
</span><span>关闭DSDT，并设置其优先启动
|
||||
</span><span>iasl dsdt.dsl
|
||||
</span><span>mkdir -p kernel/firmware/acpi
|
||||
</span><span>cp dsdt.aml kernel/firmware/acpi/
|
||||
</span><span>find kernel | cpio -H newc --create > acpi_override
|
||||
</span><span>cp acpi_override /boot/acpi_override
|
||||
</span><span>echo "GRUB_EARLY_INITRD_LINUX_CUSTOM=\"acpi_override\"" >>/etc/default/grub
|
||||
</span><span>
|
||||
</span><span>更新并重启：
|
||||
</span><span>
|
||||
</span><span>sudo grub-mkconfig -o /boot/grub/grub.cfg
|
||||
</span><span>sudo grub-install /dev/sdX
|
||||
</span><span>sudo grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=grub
|
||||
</span><span>
|
||||
</span><span>update-grub2
|
||||
</span><span>reboot
|
||||
</span></code></pre>
|
||||
<p>不出意外，重启后键盘即可使用，若系统不同将 apt 替换即可。</p>
|
||||
<h2 id="si-qi-ta-wen-ti">四.其他问题</h2>
|
||||
<p>对于Redmi 或 Lenovo刚发布的AMD R7 6800H机型：</p>
|
||||
<ul>
|
||||
<li>WIFI没有驱动 - （螃蟹卡 8852be）。</li>
|
||||
<li>蓝牙没有驱动 - (螃蟹卡 8852be)。</li>
|
||||
<li>开启窗口特效后，kwin_x11进程CPU占用飙升。</li>
|
||||
<li>电源管理，无论怎么调，笔记本都发热很严重。</li>
|
||||
</ul>
|
||||
<h3 id="xiu-fu-wifiqu-dong">修复wifi驱动</h3>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span># 内核小于5.18的
|
||||
</span><span>git clone https://github.com/HRex39/rtl8852be.git
|
||||
</span><span># 内核大于等于5.18的
|
||||
</span><span>git clone https://github.com/HRex39/rtl8852be.git -b dev
|
||||
</span><span>
|
||||
</span><span>cd rtl8852be
|
||||
</span><span>make -j8
|
||||
</span><span>sudo make install
|
||||
</span><span>sudo modprobe 8852be
|
||||
</span></code></pre>
|
||||
<h3 id="xiu-fu-lan-ya-qu-dong">修复蓝牙驱动</h3>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span># 内核=5.15
|
||||
</span><span>git clone https://github.com/HRex39/rtl8852be_bt.git -b 5.15
|
||||
</span><span># 内核=5.18
|
||||
</span><span>git clone https://github.com/HRex39/rtl8852be_bt.git -b 5.18
|
||||
</span><span>
|
||||
</span><span>cd rtl8852be_bt
|
||||
</span><span>make -j8
|
||||
</span><span>sudo make install
|
||||
</span></code></pre>
|
||||
<h3 id="xiu-fu-kwin-x11xian-qia-wei-qu-dong">修复kwin_x11显卡未驱动</h3>
|
||||
<p>首先去amd官网下载最新的linux-amd驱动：</p>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>https://www.amd.com/zh-hans/support/linux-drivers // 22.20 for Ubuntu 20.04.5 HWE
|
||||
</span></code></pre>
|
||||
<p>修改Deepin为ubuntu</p>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>sudo vim /etc/os-release // ID=Deepin => ID=ubuntu
|
||||
</span><span>
|
||||
</span><span>sudo apt install ./amdgpu-install_22.20.50200-1_all.deb
|
||||
</span><span>
|
||||
</span><span>sudo vim /etc/apt/sources.list.d/amdgpu.list // focal => bionic
|
||||
</span><span>
|
||||
</span><span>sudo apt update
|
||||
</span><span>
|
||||
</span><span>sudo amdgpu-install --no-dkms
|
||||
</span><span>
|
||||
</span><span>sudo apt install inxi clinfo
|
||||
</span></code></pre>
|
||||
<p>安装成功以后，用inxi查看下：</p>
|
||||
<p><code>inxi -G</code></p>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>Graphics: Device-1: AMD Rembrandt driver: amdgpu v: kernel
|
||||
</span><span> Display: x11 server: X.Org 1.20.11 driver: amdgpu,ati unloaded: fbdev,modesetting,vesa
|
||||
</span><span> resolution: 1920x1080~60Hz
|
||||
</span><span> OpenGL: renderer: AMD YELLOW_CARP (LLVM 14.0.1 DRM 3.42 5.15.34-amd64-desktop)
|
||||
</span><span> v: 4.6 Mesa 22.1.0-devel
|
||||
</span></code></pre>
|
||||
<p>最后还原最初的修改：</p>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>sudo vim /etc/os-release // ID=ubuntu => ID=Deepin
|
||||
</span><span>sudo apt purge amdgpu-install
|
||||
</span></code></pre>
|
||||
<p>看下效果图：</p>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>➜ ~ glxinfo -B
|
||||
</span><span>name of display: :0
|
||||
</span><span>display: :0 screen: 0
|
||||
</span><span>direct rendering: Yes
|
||||
</span><span>Extended renderer info (GLX_MESA_query_renderer):
|
||||
</span><span> Vendor: AMD (0x1002)
|
||||
</span><span> Device: AMD YELLOW_CARP (LLVM 14.0.1, DRM 3.42, 5.15.34-amd64-desktop) (0x1681)
|
||||
</span><span> Version: 22.1.0
|
||||
</span><span> Accelerated: yes
|
||||
</span><span> Video memory: 2048MB
|
||||
</span><span> Unified memory: no
|
||||
</span><span> Preferred profile: core (0x1)
|
||||
</span><span> Max core profile version: 4.6
|
||||
</span><span> Max compat profile version: 4.6
|
||||
</span><span> Max GLES1 profile version: 1.1
|
||||
</span><span> Max GLES[23] profile version: 3.2
|
||||
</span><span>Memory info (GL_ATI_meminfo):
|
||||
</span><span> VBO free memory - total: 1388 MB, largest block: 1388 MB
|
||||
</span><span> VBO free aux. memory - total: 3047 MB, largest block: 3047 MB
|
||||
</span><span> Texture free memory - total: 1388 MB, largest block: 1388 MB
|
||||
</span><span> Texture free aux. memory - total: 3047 MB, largest block: 3047 MB
|
||||
</span><span> Renderbuffer free memory - total: 1388 MB, largest block: 1388 MB
|
||||
</span><span> Renderbuffer free aux. memory - total: 3047 MB, largest block: 3047 MB
|
||||
</span><span>Memory info (GL_NVX_gpu_memory_info):
|
||||
</span><span> Dedicated video memory: 2048 MB
|
||||
</span><span> Total available memory: 5120 MB
|
||||
</span><span> Currently available dedicated video memory: 1388 MB
|
||||
</span><span>OpenGL vendor string: AMD
|
||||
</span><span>OpenGL renderer string: AMD YELLOW_CARP (LLVM 14.0.1, DRM 3.42, 5.15.34-amd64-desktop)
|
||||
</span><span>OpenGL core profile version string: 4.6 (Core Profile) Mesa 22.1.0-devel
|
||||
</span><span>OpenGL core profile shading language version string: 4.60
|
||||
</span><span>OpenGL core profile context flags: (none)
|
||||
</span><span>OpenGL core profile profile mask: core profile
|
||||
</span><span>
|
||||
</span><span>OpenGL version string: 4.6 (Compatibility Profile) Mesa 22.1.0-devel
|
||||
</span><span>OpenGL shading language version string: 4.60
|
||||
</span><span>OpenGL context flags: (none)
|
||||
</span><span>OpenGL profile mask: compatibility profile
|
||||
</span><span>
|
||||
</span><span>OpenGL ES profile version string: OpenGL ES 3.2 Mesa 22.1.0-devel
|
||||
</span><span>OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20
|
||||
</span></code></pre>
|
||||
<h3 id="shou-dong-guan-li-dian-yuan-bi-mian-cpuguo-du-shi-yong-er-fa-re">手动管理电源，避免CPU过度使用而发热</h3>
|
||||
<p>安装下面的三方电源管理工具 <code>Boost Changer</code>，选择 <code>Performance</code>策略即可</p>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>wget https://github.com/nbebaw/boostchanger/releases/download/v4.4.0/boostchanger_4.4.0_amd64.deb
|
||||
</span></code></pre>
|
||||
<h2 id="can-kao">参考</h2>
|
||||
<p><a href="https://zhuanlan.zhihu.com/p/530643928">https://zhuanlan.zhihu.com/p/530643928</a></p>
|
||||
<p><a href="https://github.com/HRex39/rtl8852be">https://github.com/HRex39/rtl8852be</a></p>
|
||||
<p><a href="https://github.com/HRex39/rtl8852be_bt">https://github.com/HRex39/rtl8852be_bt</a></p>
|
||||
<p><a href="https://bbs.deepin.org/post/241607">https://bbs.deepin.org/post/241607</a></p>
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
<div class="pagination">
|
||||
<div class="pagination__title">
|
||||
<span class="pagination__title-h">Thanks for reading! Read other posts?</span>
|
||||
<hr />
|
||||
</div>
|
||||
<div class="pagination__buttons">
|
||||
<span class="button previous">
|
||||
<a href="https://blog.dich.bid/about-accurate-pronunciation/">
|
||||
<span class="button__icon">←</span>
|
||||
<span class="button__text">乱七八糟:常见发音错误术语集合</span>
|
||||
</a>
|
||||
</span>
|
||||
|
||||
|
||||
<span class="button next">
|
||||
<a href="https://blog.dich.bid/about-blog/">
|
||||
<span class="button__text">乱七八糟:个人博客搭建</span>
|
||||
<span class="button__icon">→</span>
|
||||
</a>
|
||||
</span>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
</div>
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
<footer class="footer">
|
||||
<div class="footer__inner">
|
||||
<div class="copyright">
|
||||
<span>©
|
||||
2025
|
||||
Dichgrem</span>
|
||||
<span class="copyright-theme">
|
||||
<span class="copyright-theme-sep"> :: CC BY-SA 4.0 :: A friend comes from distant lands</span>
|
||||
</a>
|
||||
</span>
|
||||
</div>
|
||||
</div>
|
||||
</footer>
|
||||
|
||||
</div>
|
||||
</body>
|
||||
</html>
|
||||
|
||||
299
public/about-opensource/index.html
Normal file
299
public/about-opensource/index.html
Normal file
@ -0,0 +1,299 @@
|
||||
<!DOCTYPE html>
|
||||
<html lang="en">
|
||||
|
||||
<head>
|
||||
<title>Dich'blog</title>
|
||||
|
||||
<meta http-equiv="content-type" content="text/html; charset=utf-8">
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1">
|
||||
<meta name="robots" content="noodp"/>
|
||||
|
||||
<link rel="stylesheet" href="https://blog.dich.bid/style.css">
|
||||
<link rel="stylesheet" href="https://blog.dich.bid/color/blue.css">
|
||||
|
||||
<link rel="stylesheet" href="https://blog.dich.bid/color/background_dark.css">
|
||||
|
||||
<link rel="stylesheet" href="https://blog.dich.bid/font-hack-subset.css">
|
||||
|
||||
<meta name="description" content="">
|
||||
|
||||
<meta property="og:description" content="">
|
||||
<meta property="og:title" content="Dich'blog">
|
||||
<meta property="og:type" content="article">
|
||||
<meta property="og:url" content="https://blog.dich.bid/about-opensource/">
|
||||
|
||||
<meta name="twitter:card" content="summary_large_image">
|
||||
<meta name="twitter:description" content="">
|
||||
<meta name="twitter:title" content="Dich'blog">
|
||||
<meta property="twitter:domain" content="blog.dich.bid">
|
||||
<meta property="twitter:url" content="https://blog.dich.bid/about-opensource/">
|
||||
|
||||
<link rel="alternate" type="application/atom+xml" title="Dich'blog Atom Feed" href="https://blog.dich.bid/atom.xml" />
|
||||
|
||||
|
||||
<link rel="icon" type="image/png" href=/dich.webp />
|
||||
|
||||
<!-- ✅ Added center alignment styles -->
|
||||
<style>
|
||||
.footer {
|
||||
text-align: center;
|
||||
padding: 1rem 0;
|
||||
}
|
||||
|
||||
.footer__inner {
|
||||
display: flex;
|
||||
justify-content: center;
|
||||
flex-direction: column;
|
||||
align-items: center;
|
||||
}
|
||||
|
||||
.copyright {
|
||||
text-align: center;
|
||||
}
|
||||
</style>
|
||||
</head>
|
||||
|
||||
<body class="">
|
||||
<div class="container">
|
||||
|
||||
<header class="header">
|
||||
<div class="header__inner">
|
||||
<div class="header__logo">
|
||||
|
||||
<a href="https://blog.dich.bid" style="text-decoration: none;">
|
||||
<div class="logo">
|
||||
|
||||
Dich'blog
|
||||
|
||||
</div>
|
||||
</a>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
|
||||
<nav class="menu">
|
||||
<ul class="menu__inner">
|
||||
<li><a href="https://blog.dich.bid">blog</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/archive">archive</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/tags">tags</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/weekly">weekly</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/search">search</a></li>
|
||||
|
||||
<li class="active"><a href="https://blog.dich.bid/about">about me</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/links">links</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/atom.xml">rss</a></li>
|
||||
|
||||
<li><a href="https://github.com/Dichgrem" target="_blank" rel="noopener noreferrer">github</a></li>
|
||||
</ul>
|
||||
</nav>
|
||||
|
||||
|
||||
|
||||
</header>
|
||||
|
||||
|
||||
<div class="content">
|
||||
|
||||
<div class="post">
|
||||
|
||||
<h1 class="post-title"><a href="https://blog.dich.bid/about-opensource/">乱七八糟:开源软件与协议</a></h1>
|
||||
<div class="post-meta-inline">
|
||||
|
||||
<span class="post-date">
|
||||
2024-03-03
|
||||
</span>
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
<span class="post-tags-inline">
|
||||
:: tags:
|
||||
<a class="post-tag" href="https://blog.dich.bid/tags/luan-qi-ba-zao/">#乱七八糟</a></span>
|
||||
|
||||
|
||||
<div class="post-content">
|
||||
<p>前言 本文旨在介绍开源以及开源许可证，这些许可证规定了使用、修改和分发开源软件的条件。通过了解不同类型的开源许可证及其特点，读者将能够更好地理解在开发和使用开源软件时的法律和道德责任。</p>
|
||||
<span id="continue-reading"></span><h2 id="kai-yuan-de-gai-nian">开源的概念</h2>
|
||||
<p>「开源」一词对应英文 Open Source，最初起源于软件开发领域，因此也称为「开放源代码」，对应的软件则称为开源软件（Open Source Software，简称 OSS）。除了我们熟知的开源软件以外，开源的表现形式还有很多，例如开源硬件（Open Source Hardware）、开放设计（Open Design）、开放文档（Open Document）等等。开源的目的是分享共享、加速创新，可以说开源已经成为一种超越软件生产界限的运动和工作方式。</p>
|
||||
<p>对于很多刚踏入软件这个行业的小伙伴来说，「开源」是个比较陌生的概念。但是随着经手项目逐渐增多，会发现很多项目，尤其是一些大型项目，经常会引用到别人一些优秀的开源代码，而这些优秀的开源代码通常都会在最开始简单地附上一段关于授权的声明或在项目根目录下提供完整的授权声明文件，比如：「The project is licensed under the Apache 2 license.」，诸如此类便是「开源许可证」。</p>
|
||||
<p>开源不等于免费，开源也不等于没有约束</p>
|
||||
<h3 id="kai-yuan-de-hao-chu"><strong>开源的好处</strong></h3>
|
||||
<ol>
|
||||
<li>
|
||||
<p>透明度和安全性
|
||||
开源软件的代码是公开的，任何人都可以检查和改进它。这使得潜在的安全漏洞更容易被发现和修复，提升了软件的安全性。</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>促进创新
|
||||
开源允许开发者自由研究和修改代码，推动技术进步。例如，Linux、Python、TensorFlow 等开源项目极大地促进了计算机科学和人工智能的发展。</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>降低成本
|
||||
企业和个人可以免费使用开源软件，而不需要支付高昂的许可证费用。例如，使用 Linux 服务器代替 Windows Server 可以减少 IT 成本。</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>快速迭代和社区支持
|
||||
开源项目通常由全球开发者社区维护和改进，Bug 修复和新功能开发的速度比封闭源代码的软件更快。例如，开源浏览器 Firefox 就依赖社区贡献不断改进。</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>避免供应商锁定
|
||||
开源软件允许用户自由选择和修改代码，而不是被某个公司的专有软件绑定，避免了供应商锁定的问题。例如，MySQL 和 PostgreSQL 等开源数据库是很多企业的首选，避免依赖单一厂商。</p>
|
||||
</li>
|
||||
</ol>
|
||||
<h2 id="kai-yuan-ruan-jian">开源软件</h2>
|
||||
<p>开源软件，顾名思义是指能够免费且不受限制地使用、再开发、再发布的软件。但在狭义上，只有符合开放源代码促进会（Open Source Initiative）定义的软件才能被称为开源软件。这个定义提出了十个特征，必须全部符合才能认定为开源软件。</p>
|
||||
<p>这些特征包括：</p>
|
||||
<ul>
|
||||
<li>可自由再分发。</li>
|
||||
<li>提供源代码。</li>
|
||||
<li>允许衍生作品。</li>
|
||||
<li>不得过度限制原始代码的修改。</li>
|
||||
<li>不得歧视特定人、群体或用途。</li>
|
||||
<li>必须「技术中立」等。</li>
|
||||
</ul>
|
||||
<p>根据这些标准，一些看似自由使用的软件可能不符合开源软件的定义。例如，Elasticsearch原本使用Apache 2.0授权，是真正的开源软件。但面对云服务提供商如AWS等将其用于营利目的却不回馈改进的情况，Elasticsearch在2021年1月选择了SSPL（Server Side Public License，服务器端公共许可证）和Elastic License两种许可证并行；SSPL要求如果将程序的功能或修改后的版本作为服务提供给第三方，则必须免费公开提供服务源代码，这违背了开源软件的定义。另一方面，Elastic License要求不能向第三方提供主机或托管服务，也违反了开源软件的定义，因此也不算严格意义上的「开源」。</p>
|
||||
<h2 id="kai-yuan-xu-ke-zheng">开源许可证</h2>
|
||||
<p>开源许可证是软件许可证的一种特殊形式，用于规定开源软件的使用、修改、分享等相关事宜。它是一种格式合同，涉及版权、专利、商标等权利义务，自动生效。</p>
|
||||
<p>在美国，一些法院认为软件许可证是合同（contract），一些法院则认为是许可（license）。两者的区别在于，许可在传统上是由地产或物主作出的，目的在于允许他人使用自己的地块或物品。因此，它是单方向的，不构成完整的合同，而是作为合同的一个要素，用来和他人交换的条件。由于合同和许可之分在法律上有着重要的意义，它们的违约救济和版权侵权救济等方面有着不同的规定。</p>
|
||||
<p>与美国不同，大陆法系国家如中国普遍认为开源软件许可证构成合同，但这种合同是事先规定好的标准化格式合同，并且自动生效。</p>
|
||||
<p>开源许可证的种类繁多，据不完全统计，广义上的开源许可证超过200种，其中OSI批准的许可证有96个。这些许可证的内容各不相同，有些条款非常有意思，例如，啤酒软件许可证（Beerware License）规定，用户与作者聚会时可以请作者喝一杯啤酒；Jason Hunter 许可证规定，如果将该许可证下的代码用于商业目的，那么项目开发团队的所有成员都必须拥有 Jason Hunter 撰写的《Java Servlet编程》最新版。</p>
|
||||
<h2 id="chang-jian-kai-yuan-xu-ke-zheng">常见开源许可证</h2>
|
||||
<p>世界上的开源许可证（Open Source License）大概有上百种，而常见的开源协议大致有GPL、BSD、MIT、Mozilla、Apache和LGPL等。
|
||||
<img src="https://www.ruanyifeng.com/blogimg/asset/201105/free_software_licenses.png" alt="alt text" /></p>
|
||||
<blockquote>
|
||||
<p><a href="https://choosealicense.com/">Choose an open source license</a></p>
|
||||
</blockquote>
|
||||
<h2 id="apache-license">Apache License</h2>
|
||||
<p>Apache License（Apache许可证），是Apache软件基金会发布的一个自由软件许可证。</p>
|
||||
<p>Apache Licence 是著名的非盈利开源组织 Apache 采用的协议。该协议和BSD类似，同样鼓励代码共享和最终原作者的著作权，同样允许源代码修改和再发布。但是也需要遵循以下条件：</p>
|
||||
<ul>
|
||||
<li>需要给代码的用户一份 Apache Licence。</li>
|
||||
<li>如果修改了代码，需要再被修改的文件中说明。</li>
|
||||
<li>在衍生的代码中（修改和有源代码衍生的代码中）需要带有原来代码中的协议，商标，专利声明和其他原来作者规定需要包含的说明。</li>
|
||||
<li>如果再发布的产品中包含一个 Notice 文件，则在Notice文件中需要带有 Apache Licence。你可以在 Notice 中增加自己的许可，但是不可以表现为对 Apache Licence 构成更改。</li>
|
||||
</ul>
|
||||
<p>Apache Licence 也是对商业应用友好的许可。使用者也可以再需要的时候修改代码来满足并作为开源或商业产品发布/销售。</p>
|
||||
<p>使用这个协议的好处是:</p>
|
||||
<ul>
|
||||
<li>永久权利 一旦被授权，永久拥有。</li>
|
||||
<li>全球范围的权利 在一个国家获得授权，适用于所有国家。假如你在美国，许可是从印度授权的，也没有问题。</li>
|
||||
<li>授权免费 无版税， 前期、后期均无任何费用。</li>
|
||||
<li>授权无排他性 任何人都可以获得授权</li>
|
||||
<li>授权不可撤消 一旦获得授权，没有任何人可以取消。比如，你基于该产品代码开发了衍生产品，你不用担心会在某一天被禁止使用该代码</li>
|
||||
</ul>
|
||||
<h2 id="bsd">BSD</h2>
|
||||
<p>BSD 是"Berkeley Software Distribution"的缩写，意思是"伯克利软件发行版"。</p>
|
||||
<p>BSD开源协议：是一个给于使用者很大自由的协议。可以自由的使用，修改源代码，也可以将修改后的代码作为开源或者专有软件再发布。 当你发布使用了BSD协议的代码，或则以BSD协议代码为基础做二次开发自己的产品时，需要满足三个条件：</p>
|
||||
<ul>
|
||||
<li>
|
||||
<p>如果再发布的产品中包含源代码，则在源代码中必须带有原来代码中的BSD协议。</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>如果再发布的只是二进制类库/软件，则需要在类库/软件的文档和版权声明中包含原来代码中的BSD协议。</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>不可以用开源代码的作者/机构名字和原来产品的名字做市场推广。</p>
|
||||
</li>
|
||||
</ul>
|
||||
<p>BSD代码鼓励代码共享，但需要尊重代码作者的著作权。BSD由于允许使用者修改和重新发布代码，也允许使用或在BSD代码上开发商业软件发布和销售，因此是对商业集成很友好的协议。而很多的公司企业在选用开源产品的时候都首选BSD协议，因为可以完全控制这些第三方的代码，在必要的时候可以修改或者二次开发。</p>
|
||||
<h2 id="gpl">GPL</h2>
|
||||
<p>GPL （GNU General Public License） ：GNU通用公共许可协议。</p>
|
||||
<p>Linux 采用了 GPL。</p>
|
||||
<p>GPL 协议和 BSD, Apache Licence 等鼓励代码重用的许可很不一样。GPL 的出发点是代码的开源/免费使用和引用/修改/衍生代码的开源/免费使用，但不允许修改后和衍生的代码做为闭源的商业软件发布和销售。这也就是为什么我们能用免费的各种 linux，包括商业公司的 linux 和 linux 上各种各样的由个人，组织，以及商业软件公司开发的免费软件了。</p>
|
||||
<h2 id="lgpl">LGPL</h2>
|
||||
<p>LGPL是GPL的一个为主要为类库使用设计的开源协议。和 GPL 要求任何使用/修改/衍生之GPL类库的的软件必须采用GPL协议不同。LGPL允许商业软件通过类库引用(link)方式使用LGPL类库而不需要开源商业软件的代码。这使得采用 LGPL 协议的开源代码可以被商业软件作为类库引用并发布和销售。</p>
|
||||
<p>但是如果修改 LGPL 协议的代码或者衍生，则所有修改的代码，涉及修改部分的额外代码和衍生的代码都必须采用 LGPL 协议。因此LGPL协议的开源代码很适合作为第三方类库被商业软件引用，但不适合希望以 LGPL 协议代码为基础，通过修改和衍生的方式做二次开发的商业软件采用。</p>
|
||||
<p>GPL/LGPL都保障原作者的知识产权，避免有人利用开源代码复制并开发类似的产品。</p>
|
||||
<h2 id="mit">MIT</h2>
|
||||
<p>MIT是和BSD一样宽范的许可协议,源自麻省理工学院（Massachusetts Institute of Technology, MIT），又称X11协议。作者只想保留版权,而无任何其他了限制。MIT与BSD 类似，但是比 BSD 协议更加宽松，是目前最少限制的协议。这个协议唯一的条件就是在修改后的代码或者发行包包含原作者的许可信息。适用商业软件。使用MIT的软件项目有：jquery、Node.js。</p>
|
||||
<p>MIT与BSD类似，但是比BSD协议更加宽松，是目前最少限制的协议。这个协议唯一的条件就是在修改后的代码或者发行包包含原作者的许可信息。适用商业软件。使用MIT的软件项目有：jquery、Node.js。</p>
|
||||
<h2 id="mpl-mozilla-public-license-1-1">MPL (Mozilla Public License 1.1)</h2>
|
||||
<p>MPL 协议允许免费重发布、免费修改，但要求修改后的代码版权归软件的发起者 。这种授权维护了商业软件的利益，它要求基于这种软件的修改无偿贡献版权给该软件。这样，围绕该软件的所有代码的版权都集中在发起开发人的手中。但MPL是允许修改，无偿使用得。MPL 软件对链接没有要求。</p>
|
||||
<h2 id="epl-eclipse-public-license-1-0">EPL (Eclipse Public License 1.0)</h2>
|
||||
<p>EPL允许 Recipients 任意使用、复制、分发、传播、展示、修改以及改后闭源的二次商业发布。</p>
|
||||
<p>使用EPL协议，需要遵守以下规则：</p>
|
||||
<p>当一个 Contributors 将源码的整体或部分再次开源发布的时候,必须继续遵循EPL开源协议来发布,而不能改用其他协议发布.除非你得到了原"源码"Owner 的授权；</p>
|
||||
<p>EPL协议下,你可以将源码不做任何修改来商业发布.但如果你要发布修改后的源码,或者当你再发布的是 Object Code 的时候,你必须声明它的 Source Code 是可以获取的,而且要告知获取方法；</p>
|
||||
<p>当你需要将EPL下的源码作为一部分跟其他私有的源码混和着成为一个 Project 发布的时候,你可以将整个 Project/Product 以私人的协议发布,但要声明哪一部分代码是EPL下的,而且声明那部分代码继续遵循EPL；</p>
|
||||
<p>4.独立的模块(Separate Module),不需要开源。</p>
|
||||
<h2 id="creative-commons-zhi-shi-gong-xiang-xie-yi">Creative Commons 知识共享协议</h2>
|
||||
<p>Creative Commons (CC) 许可协议并不能说是真正的开源协议，它们大多是被使用于设计类的工程上。 CC 协议种类繁多，每一种都授权特定的权利。 一个 CC 许可协议具有四个基本部分，这几个部分可以单独起作用，也可以组合起来。下面是这几部分的简介：</p>
|
||||
<ul>
|
||||
<li>
|
||||
<p>署名 作品上必须附有作品的归属。如此之后，作品可以被修改，分发，复制和其它用途。</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>相同方式共享 作品可以被修改、分发或其它操作，但所有的衍生品都要置于CC许可协议下。</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>非商业用途 作品可以被修改、分发等等，但不能用于商业目的。但语言上对什么是"商业"的说明十分含糊不清 (没有提供精确的定义)，所以你可以在你的工程里对其进行说明。例如，有些人简单的解释"非商业"为不能出售这个作品。而另外一些人认为你甚至不能在有广告的网站上使用它们。 还有些人认为"商业"仅仅指你用它获取利益。</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>禁止衍生作品</p>
|
||||
</li>
|
||||
</ul>
|
||||
<p>CC 许可协议的这些条款可以自由组合使用。大多数的比较严格的CC协议会声明 "署名权，非商业用途，禁止衍生"条款，这意味着你可以自由的分享这个作品，但你不能改变它和对其收费，而且必须声明作品的归属。这个许可协议非常的有用，它可以让你的作品传播出去，但又可以对作品的使用保留部分或完全的控制。最少限制的CC协议类型当属 "署名"协议，这意味着只要人们能维护你的名誉，他们对你的作品怎么使用都行。</p>
|
||||
<p>CC 许可协议更多的是在设计类工程中使用，而不是开发类，但没有人或妨碍你将之使用与后者。只是你必须要清楚各部分条款能覆盖到的和不能覆盖到的权利。</p>
|
||||
<h2 id="can-kao">参考</h2>
|
||||
<ul>
|
||||
<li><a href="https://opensource.guide/zh-hans/">开源软件指南</a></li>
|
||||
<li><a href="https://www.tldrlegal.com/browse">Browse Software Licenses and Summaries</a></li>
|
||||
<li><a href="https://opensource.org/license">开源协议检索</a></li>
|
||||
<li><a href="https://oschina.gitee.io/opensource-guide/">开源指北</a></li>
|
||||
</ul>
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
<div class="pagination">
|
||||
<div class="pagination__title">
|
||||
<span class="pagination__title-h">Thanks for reading! Read other posts?</span>
|
||||
<hr />
|
||||
</div>
|
||||
<div class="pagination__buttons">
|
||||
<span class="button previous">
|
||||
<a href="https://blog.dich.bid/network-how-email-works-3/">
|
||||
<span class="button__icon">←</span>
|
||||
<span class="button__text">电子邮件是如何工作的:自建域名邮箱</span>
|
||||
</a>
|
||||
</span>
|
||||
|
||||
|
||||
<span class="button next">
|
||||
<a href="https://blog.dich.bid/about-rss-read/">
|
||||
<span class="button__text">搭建个人信息流:RSS阅读指南</span>
|
||||
<span class="button__icon">→</span>
|
||||
</a>
|
||||
</span>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
</div>
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
<footer class="footer">
|
||||
<div class="footer__inner">
|
||||
<div class="copyright">
|
||||
<span>©
|
||||
2025
|
||||
Dichgrem</span>
|
||||
<span class="copyright-theme">
|
||||
<span class="copyright-theme-sep"> :: CC BY-SA 4.0 :: A friend comes from distant lands</span>
|
||||
</a>
|
||||
</span>
|
||||
</div>
|
||||
</div>
|
||||
</footer>
|
||||
|
||||
</div>
|
||||
</body>
|
||||
</html>
|
||||
|
||||
210
public/about-podcast-use/index.html
Normal file
210
public/about-podcast-use/index.html
Normal file
@ -0,0 +1,210 @@
|
||||
<!DOCTYPE html>
|
||||
<html lang="en">
|
||||
|
||||
<head>
|
||||
<title>Dich'blog</title>
|
||||
|
||||
<meta http-equiv="content-type" content="text/html; charset=utf-8">
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1">
|
||||
<meta name="robots" content="noodp"/>
|
||||
|
||||
<link rel="stylesheet" href="https://blog.dich.bid/style.css">
|
||||
<link rel="stylesheet" href="https://blog.dich.bid/color/blue.css">
|
||||
|
||||
<link rel="stylesheet" href="https://blog.dich.bid/color/background_dark.css">
|
||||
|
||||
<link rel="stylesheet" href="https://blog.dich.bid/font-hack-subset.css">
|
||||
|
||||
<meta name="description" content="">
|
||||
|
||||
<meta property="og:description" content="">
|
||||
<meta property="og:title" content="Dich'blog">
|
||||
<meta property="og:type" content="article">
|
||||
<meta property="og:url" content="https://blog.dich.bid/about-podcast-use/">
|
||||
|
||||
<meta name="twitter:card" content="summary_large_image">
|
||||
<meta name="twitter:description" content="">
|
||||
<meta name="twitter:title" content="Dich'blog">
|
||||
<meta property="twitter:domain" content="blog.dich.bid">
|
||||
<meta property="twitter:url" content="https://blog.dich.bid/about-podcast-use/">
|
||||
|
||||
<link rel="alternate" type="application/atom+xml" title="Dich'blog Atom Feed" href="https://blog.dich.bid/atom.xml" />
|
||||
|
||||
|
||||
<link rel="icon" type="image/png" href=/dich.webp />
|
||||
|
||||
<!-- ✅ Added center alignment styles -->
|
||||
<style>
|
||||
.footer {
|
||||
text-align: center;
|
||||
padding: 1rem 0;
|
||||
}
|
||||
|
||||
.footer__inner {
|
||||
display: flex;
|
||||
justify-content: center;
|
||||
flex-direction: column;
|
||||
align-items: center;
|
||||
}
|
||||
|
||||
.copyright {
|
||||
text-align: center;
|
||||
}
|
||||
</style>
|
||||
</head>
|
||||
|
||||
<body class="">
|
||||
<div class="container">
|
||||
|
||||
<header class="header">
|
||||
<div class="header__inner">
|
||||
<div class="header__logo">
|
||||
|
||||
<a href="https://blog.dich.bid" style="text-decoration: none;">
|
||||
<div class="logo">
|
||||
|
||||
Dich'blog
|
||||
|
||||
</div>
|
||||
</a>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
|
||||
<nav class="menu">
|
||||
<ul class="menu__inner">
|
||||
<li><a href="https://blog.dich.bid">blog</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/archive">archive</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/tags">tags</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/weekly">weekly</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/search">search</a></li>
|
||||
|
||||
<li class="active"><a href="https://blog.dich.bid/about">about me</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/links">links</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/atom.xml">rss</a></li>
|
||||
|
||||
<li><a href="https://github.com/Dichgrem" target="_blank" rel="noopener noreferrer">github</a></li>
|
||||
</ul>
|
||||
</nav>
|
||||
|
||||
|
||||
|
||||
</header>
|
||||
|
||||
|
||||
<div class="content">
|
||||
|
||||
<div class="post">
|
||||
|
||||
<h1 class="post-title"><a href="https://blog.dich.bid/about-podcast-use/">搭建个人信息流:播客收听指北</a></h1>
|
||||
<div class="post-meta-inline">
|
||||
|
||||
<span class="post-date">
|
||||
2024-03-06
|
||||
</span>
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
<span class="post-tags-inline">
|
||||
:: tags:
|
||||
<a class="post-tag" href="https://blog.dich.bid/tags/luan-qi-ba-zao/">#乱七八糟</a></span>
|
||||
|
||||
|
||||
<div class="post-content">
|
||||
<p>前言 讲起播客，许多人第一反应是喜马拉雅，但其实播客的订阅和收听有许多种方式。本文带你了解订阅播客的各种方式，并告诉你市面上有哪些不错的播客客户端可供选择。</p>
|
||||
<span id="continue-reading"></span><h2 id="yi-shen-me-shi-bo-ke">一.什么是播客</h2>
|
||||
<p>播客是一种通过互联网传播音频或视频文件的媒体形式。这个词汇是由“广播”（broadcasting）和“iPod”（一种流行的便携式媒体播放器）两个词组合而成的。播客通常是由个人、组织或公司制作，并通过互联网上的订阅服务分享给观众。</p>
|
||||
<ul>
|
||||
<li>
|
||||
<p>定期更新： 播客通常以系列形式发布，每一集都是一个独立的音频或视频文件。制作者会定期发布新的内容，让观众订阅后能够定期收听或观看。</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>订阅：观众可以通过订阅播客来自动获取最新的内容。这意味着一旦订阅了某个播客，新的内容就会自动下载到用户的设备上，方便随时收听或观看。</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>多样的内容： 播客内容非常多样化，涵盖了几乎所有可能的主题，包括新闻、科技、文化、教育、娱乐等。从个人讲述生活故事到专业领域的讨论，播客的形式和内容都非常灵活。</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>低门槛制作：制作播客相对来说不需要太多的专业设备和技能，因此许多个人或小团队可以轻松开始制作自己的播客。</p>
|
||||
</li>
|
||||
</ul>
|
||||
<p>播客的流行得益于它提供了一种轻松、灵活、个性化的信息传递方式，让人们可以方便地在各种主题上深入了解或娱乐。</p>
|
||||
<h2 id="er-ru-he-ting-bo-ke">二.如何听播客</h2>
|
||||
<p>要收听播客，首先得确定自己所用的平台和客户端，一般有以下几种：</p>
|
||||
<ul>
|
||||
<li>
|
||||
<p>使用播客应用： 最常见的方式是使用专门的播客应用程序，这些应用可以在智能手机、平板电脑或计算机上安装。一些常见的播客应用包括 Apple Podcasts（苹果播客）、Spotify、Google Podcasts（谷歌播客）、Pocket Casts等。这些应用通常允许你搜索、订阅和播放播客。像喜马拉雅以及各大云音乐等非泛用型播客客户端，这类软件的特点是收听方便，种类繁多，但一般不开源，也没有 RSS 链接。</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>在网页上收听： 许多播客也提供在其官方网站上在线收听的选项。你可以在制作者的网站上找到相应的播客链接，然后直接在浏览器中收听，或者使用浏览器插件。</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>通过流媒体服务： 一些流媒体服务，如 Spotify、Apple Music 等，也提供了播客的功能。你可以在这些服务中搜索并订阅你感兴趣的播客。</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>通过RSS订阅： 几乎每个独立播客的主播都会反复强调「请使用节目 RSS 链接在 泛用型播客客户端 里订阅节目」，一定程度上有无 RSS 订阅链接是作为独立播客的判断标准。使用 RSS 链接订阅播客其实非常简单——得到节目的 RSS 订阅链接后，将之粘贴到你的播客客户端内（通常是节目的搜索栏或地址栏）即可。大多数播客应用都支持这种方式。注意，例如喜马拉雅、荔枝等平台是没有原生RSS链接的，因此，对第三方服务生成的 RSS 链接要注意鉴别。有些服务提供者会在不告知主播和听众的前提下，私自在节目中间插入广告，非常影响节目收听体验，在使用时请注意甄别。</p>
|
||||
</li>
|
||||
</ul>
|
||||
<h2 id="san-chang-jian-ke-hu-duan-you-que-dian">三.常见客户端优缺点</h2>
|
||||
<p><code>我个人推荐使用开源的 AntennaPod 。</code></p>
|
||||
<h2 id="si-bo-ke-zi-yuan">四.播客资源</h2>
|
||||
<p><a href="https://tianxianzi.me/2023/12/11/selected_podcast/">天仙子的播客年度总结：播客选录</a></p>
|
||||
<p><a href="https://xyzrank.com/#/">中文播客榜</a></p>
|
||||
<p><a href="https://www.listennotes.com/">Podcast search</a></p>
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
<div class="pagination">
|
||||
<div class="pagination__title">
|
||||
<span class="pagination__title-h">Thanks for reading! Read other posts?</span>
|
||||
<hr />
|
||||
</div>
|
||||
<div class="pagination__buttons">
|
||||
<span class="button previous">
|
||||
<a href="https://blog.dich.bid/about-rss-read/">
|
||||
<span class="button__icon">←</span>
|
||||
<span class="button__text">搭建个人信息流:RSS阅读指南</span>
|
||||
</a>
|
||||
</span>
|
||||
|
||||
|
||||
<span class="button next">
|
||||
<a href="https://blog.dich.bid/about-shortcut-key/">
|
||||
<span class="button__text">乱七八糟:常用实用快捷键</span>
|
||||
<span class="button__icon">→</span>
|
||||
</a>
|
||||
</span>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
</div>
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
<footer class="footer">
|
||||
<div class="footer__inner">
|
||||
<div class="copyright">
|
||||
<span>©
|
||||
2025
|
||||
Dichgrem</span>
|
||||
<span class="copyright-theme">
|
||||
<span class="copyright-theme-sep"> :: CC BY-SA 4.0 :: A friend comes from distant lands</span>
|
||||
</a>
|
||||
</span>
|
||||
</div>
|
||||
</div>
|
||||
</footer>
|
||||
|
||||
</div>
|
||||
</body>
|
||||
</html>
|
||||
|
||||
379
public/about-rss-read/index.html
Normal file
379
public/about-rss-read/index.html
Normal file
@ -0,0 +1,379 @@
|
||||
<!DOCTYPE html>
|
||||
<html lang="en">
|
||||
|
||||
<head>
|
||||
<title>Dich'blog</title>
|
||||
|
||||
<meta http-equiv="content-type" content="text/html; charset=utf-8">
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1">
|
||||
<meta name="robots" content="noodp"/>
|
||||
|
||||
<link rel="stylesheet" href="https://blog.dich.bid/style.css">
|
||||
<link rel="stylesheet" href="https://blog.dich.bid/color/blue.css">
|
||||
|
||||
<link rel="stylesheet" href="https://blog.dich.bid/color/background_dark.css">
|
||||
|
||||
<link rel="stylesheet" href="https://blog.dich.bid/font-hack-subset.css">
|
||||
|
||||
<meta name="description" content="">
|
||||
|
||||
<meta property="og:description" content="">
|
||||
<meta property="og:title" content="Dich'blog">
|
||||
<meta property="og:type" content="article">
|
||||
<meta property="og:url" content="https://blog.dich.bid/about-rss-read/">
|
||||
|
||||
<meta name="twitter:card" content="summary_large_image">
|
||||
<meta name="twitter:description" content="">
|
||||
<meta name="twitter:title" content="Dich'blog">
|
||||
<meta property="twitter:domain" content="blog.dich.bid">
|
||||
<meta property="twitter:url" content="https://blog.dich.bid/about-rss-read/">
|
||||
|
||||
<link rel="alternate" type="application/atom+xml" title="Dich'blog Atom Feed" href="https://blog.dich.bid/atom.xml" />
|
||||
|
||||
|
||||
<link rel="icon" type="image/png" href=/dich.webp />
|
||||
|
||||
<!-- ✅ Added center alignment styles -->
|
||||
<style>
|
||||
.footer {
|
||||
text-align: center;
|
||||
padding: 1rem 0;
|
||||
}
|
||||
|
||||
.footer__inner {
|
||||
display: flex;
|
||||
justify-content: center;
|
||||
flex-direction: column;
|
||||
align-items: center;
|
||||
}
|
||||
|
||||
.copyright {
|
||||
text-align: center;
|
||||
}
|
||||
</style>
|
||||
</head>
|
||||
|
||||
<body class="">
|
||||
<div class="container">
|
||||
|
||||
<header class="header">
|
||||
<div class="header__inner">
|
||||
<div class="header__logo">
|
||||
|
||||
<a href="https://blog.dich.bid" style="text-decoration: none;">
|
||||
<div class="logo">
|
||||
|
||||
Dich'blog
|
||||
|
||||
</div>
|
||||
</a>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
|
||||
<nav class="menu">
|
||||
<ul class="menu__inner">
|
||||
<li><a href="https://blog.dich.bid">blog</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/archive">archive</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/tags">tags</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/weekly">weekly</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/search">search</a></li>
|
||||
|
||||
<li class="active"><a href="https://blog.dich.bid/about">about me</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/links">links</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/atom.xml">rss</a></li>
|
||||
|
||||
<li><a href="https://github.com/Dichgrem" target="_blank" rel="noopener noreferrer">github</a></li>
|
||||
</ul>
|
||||
</nav>
|
||||
|
||||
|
||||
|
||||
</header>
|
||||
|
||||
|
||||
<div class="content">
|
||||
|
||||
<div class="post">
|
||||
|
||||
<h1 class="post-title"><a href="https://blog.dich.bid/about-rss-read/">搭建个人信息流:RSS阅读指南</a></h1>
|
||||
<div class="post-meta-inline">
|
||||
|
||||
<span class="post-date">
|
||||
2024-03-05
|
||||
</span>
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
<span class="post-tags-inline">
|
||||
:: tags:
|
||||
<a class="post-tag" href="https://blog.dich.bid/tags/luan-qi-ba-zao/">#乱七八糟</a></span>
|
||||
|
||||
|
||||
<div class="post-content">
|
||||
<p>前言 RSS 提供了一种数据格式，以 XML（可扩展标记语言）的形式组织信息，包括文章标题、摘要、链接和发布日期等。这些信息形成了所谓的“订阅源”（Feed），用户可以使用RSS阅读器（Feed Reader）来订阅这些源。</p>
|
||||
<span id="continue-reading"></span><h2 id="yi-shen-me-shi-rss">一.什么是RSS</h2>
|
||||
<p>如果你使用过类似红板报，轻芒杂志,摸鱼 kiki,今日热榜等 APP，应该对 RSS 并不陌生。</p>
|
||||
<p>RSS（Really Simple Syndication）是一种用于发布经常更新的内容的标准，通常用于博客、新闻网站和其他线上发布的信息。RSS 允许用户订阅这些站点的内容，以便在内容有更新时，用户能够获得及时的通知。</p>
|
||||
<p>基本上，RSS 提供了一种数据格式，以 XML（可扩展标记语言）的形式组织信息，包括文章标题、摘要、链接和发布日期等。这些信息形成了所谓的“订阅源”（Feed），用户可以使用 RSS 阅读器（Feed Reader）来订阅这些源。</p>
|
||||
<p>RSS 的主要优势包括：</p>
|
||||
<ul>
|
||||
<li>
|
||||
<p>即时通知：用户订阅了 RSS 源后，当源中的内容有更新时，用户将立即收到通知，而无需手动检查网站。</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>集中管理：使用 RSS 阅读器，用户可以集中管理多个网站的更新，而无需逐个访问这些站点。</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>隐私保护：RSS 订阅不需要提供个人信息，用户只需关注感兴趣的内容，而无需注册账户。</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>定制内容：用户可以选择订阅感兴趣的主题或网站，定制他们的信息流。</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>减少信息过载：通过只关注真正感兴趣的内容，用户可以减少信息过载，集中注意力在最关键的信息上。</p>
|
||||
</li>
|
||||
</ul>
|
||||
<p>如果我们想更高效地获取信息，不在多个应用间来回切换，另一方面拒绝算法给我们推荐的内容，那么建议用回原始的 RSS。</p>
|
||||
<p>虽然 RSS 曾经非常流行，但随着社交媒体和其他信息传递方式的兴起，逐渐成为时代的眼泪。然而，RSS 仍然是一种有效的信息分发和获取方式，许多网站和博客仍提供 RSS 源。题主曾经计划使用 Kindle 作为专门的RSS阅读器，后来由于过于昂贵而作罢。</p>
|
||||
<h2 id="er-ru-he-jin-xing-rssyue-du">二.如何进行RSS阅读</h2>
|
||||
<p>基本上有以下几步：</p>
|
||||
<ul>
|
||||
<li>
|
||||
<p>寻找 RSS 订阅源</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>确定 RSS 客户端</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>自建 RSS 服务端（可选）</p>
|
||||
</li>
|
||||
</ul>
|
||||
<p><strong>寻找RSS订阅源</strong></p>
|
||||
<p>要知道一个网站是否支持 RSS 订阅，最直接的方法就是看网站的底部或侧边栏是否有 RSS 图标。一般来说，图标所指向的地址就是该网站的订阅链接，可以直接点击 跳转到 RSS 客户端内进行订阅，也可以复制粘贴按钮中的地址到自己在用的 RSS 服务中订阅这些网站中的内容。</p>
|
||||
<p>在浏览器中推荐使用 RSS Hub radar 插件，可以自动找到可用的RSS源并提示。</p>
|
||||
<p>有时候网站不会直接给出订阅源，这时候你也可以尝试在网站域名后面加上 /feed 或 /rss 或许可以碰巧猜中，比如少数派的 RSS 订阅链接就是 https://sspai.com/feed。当然，你也可以直接通过搜索引擎通过 网站名 + RSS 的关键字进行搜索，往往都能找到支持网站的 RSS 链接。</p>
|
||||
<p>MoreRSS，这个网站提供中、英文的RSS源，并且显示源的订阅量，对于一些受欢迎的英文 RSS，还提供了中文翻译。但此网站还在建设中，收录量不大、功能也不完善，可以关注其更新。</p>
|
||||
<p>有一些中文博客聚合网站，收录了多则1000+少则几百的中文博客（PS.经查世界上现存的大熊猫数量约2600只），知名的有十年之约、博友圈、BlogFinder 、积薪、川流 等，不一一列举了。</p>
|
||||
<p>Feedsearch，如果在网站的首页看不到 RSS 信息，可以使用这个 RSS 源搜索服务，实测准确度很高，我用它找出来很多隐藏的 RSS 源，如果这个网站搜不到，那可能是网站确实没有提供 RSS。</p>
|
||||
<p>RSSAnything ，如果 RSSHub 也没有找到需要的 RSS，可以尝试使用这个网站生成 RSS，这是我试过的效果最好的，但要看运气，有的时候效果很好，有的时候达不到期望值。</p>
|
||||
<p>有一些针对具体的社会化媒体生成 RSS 的服务，但或者收费，或者稳定性欠佳失效，或者收费且稳定性欠佳失效（我就订阅了一个微信公众号的 RSS 服务，没用多久就失效了还不退款），想了下，就不在这里列举了，感兴趣可以直接在https://morerss.com/tools_zh.html查找。</p>
|
||||
<blockquote>
|
||||
<p>英文RSS源翻译<br />
|
||||
可以把外语信息源翻译为中文的，这里推荐的服务器是 RSS-Translator，功能强大但需要一定的能力。MoreRSS 基于 RSS-Translator 的服务，翻译了一批优质的外语信息源，可以直接订阅。</p>
|
||||
</blockquote>
|
||||
<p>当然，我们也可以直接导入现有的订阅源，一般为 OPML 文件，如 RSS Source;或者调用第三方的 RSS 服务，如 anyfeeder，等等。</p>
|
||||
<p>这里介绍一个 RSS 神器，由 DIygod 发起的RSShub项目：</p>
|
||||
<p>RSSHub 是一个开源项目，旨在为用户提供一个集中化、可定制的RSS（Really Simple Syndication）源的生成器。该项目的目标是通过从各种网站和平台获取信息，将其聚合到用户自定义的RSS源中，从而使用户能够方便地订阅他们关心的内容。</p>
|
||||
<ul>
|
||||
<li>
|
||||
<p>开源性质： RSSHub 是一个开源项目，其源代码可以在 GitHub 上找到。这意味着任何人都可以查看、使用、修改和贡献代码。</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>支持的站点： RSSHub 支持从各种网站和平台提取数据，包括但不限于新闻网站、社交媒体、博客、视频分享平台等。用户可以根据自己的需求选择要订阅的站点。</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>自定义生成： 用户可以通过指定参数和规则来定制他们的 RSS 源，以便获取特定主题或关键字的更新。这使得用户能够灵活地定制他们的订阅流。</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>社区参与： RSSHub 是一个社区驱动的项目，有很多开发者和贡献者参与其中。社区可以通过 GitHub 进行讨论、报告问题和提交代码。</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>部署方式： RSSHub 可以自行部署，用户可以在自己的服务器上搭建RSSHub实例，以便更好地控制和定制生成的RSS源。</p>
|
||||
</li>
|
||||
</ul>
|
||||
<p><strong>确定RSS客户端</strong></p>
|
||||
<p>RSS客户端非常丰富，包括 Android 端，IOS 端，Windows 端，linux 端，浏览器插件，甚至 Vscode 插件（用来摸鱼）等等。这里推荐一些阅读器，当然，也可以选择类似 Feedly 的服务商。</p>
|
||||
<ul>
|
||||
<li>
|
||||
<p>Android：News，在Fdorid里可下载，中文名为“新闻”，界面简洁，功能全面，支持本地或连接自建服务端。</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>IOS：Inoreader， 其提供了方便的阅读体验，支持离线阅读、标签和快速搜索。</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>Windows：Fluent Reader,在github上开源，界面优雅，支持本地或连接自建服务端。</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>linux：Fluent Reader或Newsboat， 是 Newsbeuter 的一个分支，一款文本控制台 RSS/Atom 订阅阅读器。</p>
|
||||
</li>
|
||||
</ul>
|
||||
<p><strong>自建RSS服务端</strong></p>
|
||||
<p>开源的RSS服务端软件可以用来搭建个人的RSS阅读服务：</p>
|
||||
<ul>
|
||||
<li>
|
||||
<p>FreshRSS: FreshRSS 是一款简单易用的自建 RSS 服务端软件。它提供了丰富的功能，包括标签、筛选器、阅读统计等，并支持多用户。</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>Miniflux: Miniflux 是一个轻量级的 RSS/Atom 阅读器服务，支持自建。它采用 Go 语言编写，具有快速响应和简洁的用户界面。</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>Tiny Tiny RSS (tt-rss): Tiny Tiny RSS 是一款功能丰富的自建RSS服务端软件，提供了类似于 Google Reader 的界面，并支持标签、过滤器、插件等。</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>Selfoss: Selfoss 是一款支持多种数据源（包括RSS）的自建聚合器。它的界面简洁，支持标签、过滤器和插件，同时也提供了跨平台的客户端。</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>Miniflux 2: 不要与上面提到的 Miniflux 混淆，Miniflux 2 是 Miniflux 的一个全新版本，同样支持自建 RSS 服务。</p>
|
||||
</li>
|
||||
</ul>
|
||||
<p>这里以MiniFlux为例，其优势在与：</p>
|
||||
<ul>
|
||||
<li>
|
||||
<p>程序设计极简，不处理任何订阅之外的事情。</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>程序无外部依赖，运行性能高。</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>支持自动抓取并缓存图片，加速浏览。</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>有限支持自动将摘要替换为全文进行抓取。</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>支持多账号登录，支持 Fever API ，允许客户端从外部登录。</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>支持集成 PinBoard 、Instapaper、 Pocket、Wallabag、Nunux Keeper 等服务。</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>提供 Open API、书签快速订阅脚本。</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>维护者和社区相对活跃，更新频率高。</p>
|
||||
</li>
|
||||
</ul>
|
||||
<p><strong>步骤：</strong></p>
|
||||
<p>1.安装docker 和docker-compose（略）</p>
|
||||
<p>2.Docker 安装 miniflux：</p>
|
||||
<p>（1）创建并进入你想安装 Miniflux 的文件夹：</p>
|
||||
<p><code>mkdir ~/miniflux</code> # 在根目录创建名为miniflux的文件夹</p>
|
||||
<p><code>cd ~/miniflux</code> # 进入miniflux文件夹</p>
|
||||
<p>（2）创建docker-compose.yml文件：</p>
|
||||
<p><code>nano docker-compose.yml</code> # 使用nano编辑器创建，会自动打开文件以写入内容</p>
|
||||
<p>（3）在文件中写入以下内容并保存：</p>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>version: '3.4'
|
||||
</span><span>
|
||||
</span><span>services:
|
||||
</span><span>
|
||||
</span><span> miniflux:
|
||||
</span><span>
|
||||
</span><span> image: miniflux/miniflux:latest
|
||||
</span><span>
|
||||
</span><span> ports:
|
||||
</span><span>
|
||||
</span><span> - "127.0.0.1:8080:8080" #调整一：增加localhost ip 并改port为8080
|
||||
</span><span>
|
||||
</span><span> depends_on:
|
||||
</span><span>
|
||||
</span><span> - db
|
||||
</span><span>
|
||||
</span><span> environment:
|
||||
</span><span>
|
||||
</span><span> - DATABASE_URL=postgres://miniflux:secret@db/miniflux?sslmode=disable
|
||||
</span><span>
|
||||
</span><span> - RUN_MIGRATIONS=1
|
||||
</span><span>
|
||||
</span><span> - CREATE_ADMIN=1
|
||||
</span><span>
|
||||
</span><span> - ADMIN_USERNAME=admin # 登录Miniflux的用户名，可自定义
|
||||
</span><span>
|
||||
</span><span> - ADMIN_PASSWORD=password # 登录Miniflux的密码，可自定义，至少6位
|
||||
</span><span>
|
||||
</span><span> - "BASE_URL=https://enter.your.url" # 调整二：输入想用来访问Miniflux的域名
|
||||
</span><span>
|
||||
</span><span> healthcheck:
|
||||
</span><span>
|
||||
</span><span> test: ["CMD", "/usr/bin/miniflux", "-healthcheck", "auto"]
|
||||
</span><span>
|
||||
</span><span> db:
|
||||
</span><span>
|
||||
</span><span> image: postgres:latest
|
||||
</span><span>
|
||||
</span><span> environment:
|
||||
</span><span>
|
||||
</span><span> - POSTGRES_USER=miniflux
|
||||
</span><span>
|
||||
</span><span> - POSTGRES_PASSWORD=secret
|
||||
</span><span>
|
||||
</span><span> volumes:
|
||||
</span><span>
|
||||
</span><span> - miniflux-db:/var/lib/postgresql/data
|
||||
</span><span>
|
||||
</span><span> healthcheck:
|
||||
</span><span>
|
||||
</span><span> test: ["CMD", "pg_isready", "-U", "miniflux"]
|
||||
</span><span>
|
||||
</span><span> interval: 10s
|
||||
</span><span>
|
||||
</span><span> start_period: 30s
|
||||
</span><span>
|
||||
</span><span>volumes:
|
||||
</span><span>
|
||||
</span><span> miniflux-db:
|
||||
</span></code></pre>
|
||||
<p>该 docker-compose.yml 文档内容基于 Miniflux 官方文档 ，并在细节上进行了调整。调整有两处：一是将 port 改为127.0.0.1:8080:8080，主要目的是错开常用port 80，并调整 localhost 为127.0.0.1来跟 nginx 的设置一致（如不调整， miniflux 将使用0.0.0.0，无法顺利运行 nginx ）；二是在 miniflux 的environment 中加入新的 configuration BASE_URL，请将内容换为你想用来访问 Miniflux 的域名。</p>
|
||||
<p>//如何用 nano 保存文件：可以使用 ctrl+X，在退出编辑时，选择Y来保存所有更改，再敲一次回车便可以回到命令行。//</p>
|
||||
<p>（4）运行以下代码进行安装：</p>
|
||||
<p><code>docker-compose up -d</code></p>
|
||||
<p>在浏览器中访问服务器ip:端口号（如http://123.45.67.890:8080），如显示登录界面，即代表安装成功。域名解析和反代步骤略。</p>
|
||||
<h2 id="hou-ji">后记</h2>
|
||||
<p><a href="https://morerss.com/tools_zh.html">RSS源</a></p>
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
<div class="pagination">
|
||||
<div class="pagination__title">
|
||||
<span class="pagination__title-h">Thanks for reading! Read other posts?</span>
|
||||
<hr />
|
||||
</div>
|
||||
<div class="pagination__buttons">
|
||||
<span class="button previous">
|
||||
<a href="https://blog.dich.bid/about-opensource/">
|
||||
<span class="button__icon">←</span>
|
||||
<span class="button__text">乱七八糟:开源软件与协议</span>
|
||||
</a>
|
||||
</span>
|
||||
|
||||
|
||||
<span class="button next">
|
||||
<a href="https://blog.dich.bid/about-podcast-use/">
|
||||
<span class="button__text">搭建个人信息流:播客收听指北</span>
|
||||
<span class="button__icon">→</span>
|
||||
</a>
|
||||
</span>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
</div>
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
<footer class="footer">
|
||||
<div class="footer__inner">
|
||||
<div class="copyright">
|
||||
<span>©
|
||||
2025
|
||||
Dichgrem</span>
|
||||
<span class="copyright-theme">
|
||||
<span class="copyright-theme-sep"> :: CC BY-SA 4.0 :: A friend comes from distant lands</span>
|
||||
</a>
|
||||
</span>
|
||||
</div>
|
||||
</div>
|
||||
</footer>
|
||||
|
||||
</div>
|
||||
</body>
|
||||
</html>
|
||||
|
||||
257
public/about-runer-1/index.html
Normal file
257
public/about-runer-1/index.html
Normal file
@ -0,0 +1,257 @@
|
||||
<!DOCTYPE html>
|
||||
<html lang="en">
|
||||
|
||||
<head>
|
||||
<title>Dich'blog</title>
|
||||
|
||||
<meta http-equiv="content-type" content="text/html; charset=utf-8">
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1">
|
||||
<meta name="robots" content="noodp"/>
|
||||
|
||||
<link rel="stylesheet" href="https://blog.dich.bid/style.css">
|
||||
<link rel="stylesheet" href="https://blog.dich.bid/color/blue.css">
|
||||
|
||||
<link rel="stylesheet" href="https://blog.dich.bid/color/background_dark.css">
|
||||
|
||||
<link rel="stylesheet" href="https://blog.dich.bid/font-hack-subset.css">
|
||||
|
||||
<meta name="description" content="">
|
||||
|
||||
<meta property="og:description" content="">
|
||||
<meta property="og:title" content="Dich'blog">
|
||||
<meta property="og:type" content="article">
|
||||
<meta property="og:url" content="https://blog.dich.bid/about-runer-1/">
|
||||
|
||||
<meta name="twitter:card" content="summary_large_image">
|
||||
<meta name="twitter:description" content="">
|
||||
<meta name="twitter:title" content="Dich'blog">
|
||||
<meta property="twitter:domain" content="blog.dich.bid">
|
||||
<meta property="twitter:url" content="https://blog.dich.bid/about-runer-1/">
|
||||
|
||||
<link rel="alternate" type="application/atom+xml" title="Dich'blog Atom Feed" href="https://blog.dich.bid/atom.xml" />
|
||||
|
||||
|
||||
<link rel="icon" type="image/png" href=/dich.webp />
|
||||
|
||||
<!-- ✅ Added center alignment styles -->
|
||||
<style>
|
||||
.footer {
|
||||
text-align: center;
|
||||
padding: 1rem 0;
|
||||
}
|
||||
|
||||
.footer__inner {
|
||||
display: flex;
|
||||
justify-content: center;
|
||||
flex-direction: column;
|
||||
align-items: center;
|
||||
}
|
||||
|
||||
.copyright {
|
||||
text-align: center;
|
||||
}
|
||||
</style>
|
||||
</head>
|
||||
|
||||
<body class="">
|
||||
<div class="container">
|
||||
|
||||
<header class="header">
|
||||
<div class="header__inner">
|
||||
<div class="header__logo">
|
||||
|
||||
<a href="https://blog.dich.bid" style="text-decoration: none;">
|
||||
<div class="logo">
|
||||
|
||||
Dich'blog
|
||||
|
||||
</div>
|
||||
</a>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
|
||||
<nav class="menu">
|
||||
<ul class="menu__inner">
|
||||
<li><a href="https://blog.dich.bid">blog</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/archive">archive</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/tags">tags</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/weekly">weekly</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/search">search</a></li>
|
||||
|
||||
<li class="active"><a href="https://blog.dich.bid/about">about me</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/links">links</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/atom.xml">rss</a></li>
|
||||
|
||||
<li><a href="https://github.com/Dichgrem" target="_blank" rel="noopener noreferrer">github</a></li>
|
||||
</ul>
|
||||
</nav>
|
||||
|
||||
|
||||
|
||||
</header>
|
||||
|
||||
|
||||
<div class="content">
|
||||
|
||||
<div class="post">
|
||||
|
||||
<h1 class="post-title"><a href="https://blog.dich.bid/about-runer-1/">乱七八糟:跑步笔记(一)</a></h1>
|
||||
<div class="post-meta-inline">
|
||||
|
||||
<span class="post-date">
|
||||
2024-06-08
|
||||
</span>
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
<span class="post-tags-inline">
|
||||
:: tags:
|
||||
<a class="post-tag" href="https://blog.dich.bid/tags/luan-qi-ba-zao/">#乱七八糟</a></span>
|
||||
|
||||
|
||||
<div class="post-content">
|
||||
<p>前言 最近读得<<亮哥跑经>>一书,遂迷上跑步;奈何体重偏高,略微有些吃力.以下是一些笔记:</p>
|
||||
<span id="continue-reading"></span>
|
||||
<blockquote>
|
||||
<p>为啥有人跑两步就喘？</p>
|
||||
</blockquote>
|
||||
<ul>
|
||||
<li>运动基础薄弱</li>
|
||||
</ul>
|
||||
<p>再慢的跑步，它也比快走的强度要大。跑步虽然很简单，但它并不是低强度的运动。</p>
|
||||
<ul>
|
||||
<li>呼吸方法错误</li>
|
||||
</ul>
|
||||
<p>跑步时需要更多的氧气,如果呼和吸的量不均等，吐气比吸的要多，身体没有充分地进行气体交换，就会气喘吁吁。</p>
|
||||
<ul>
|
||||
<li>呼吸肌能力较弱</li>
|
||||
</ul>
|
||||
<p>大基数体重的人，腹部往往很胖，身体的呼吸系统较弱。内脏脂肪多，呼吸肌就像吹大的气球一样，被撑薄了，相应的，它收缩和扩张的能力就会下降，所以大体重的人跑步更容易喘。而且除了容易喘之外，他们跑步也更容易岔气。</p>
|
||||
<blockquote>
|
||||
<p>正确的呼吸方法是什么?</p>
|
||||
</blockquote>
|
||||
<ul>
|
||||
<li>
|
||||
<p>建议初学者采用两步一吸两步一呼的方式。</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>等跑了一段时间，心肺功能和整体体能加强之后，可以改为三步一吸三步一呼。</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>需要注意的是，最好口鼻同时呼吸,才能使充足氧气吸入</p>
|
||||
</li>
|
||||
</ul>
|
||||
<blockquote>
|
||||
<p>冬天跑步注意事项</p>
|
||||
</blockquote>
|
||||
<ul>
|
||||
<li>
|
||||
<p>冬天户外跑时，因为天气比较冷，为了防止冷空气进入我们的身体，可以带一个薄薄的口罩。</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>不要秋天的时候都没跑，到冬天最冷的时候突然出去跑步了。也不要顶风跑，这样你的呼吸系统是受不了的。</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>冬天跑步的时候，可以用舌尖顶住上牙膛，过滤加温一下冷空气，免得空气直灌入身体，造成肠胃不适。</p>
|
||||
</li>
|
||||
</ul>
|
||||
<blockquote>
|
||||
<p>为什么会岔气？</p>
|
||||
</blockquote>
|
||||
<ul>
|
||||
<li>
|
||||
<p>岔气，简单来说，就是呼吸肌痉挛（抽筋）了。</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>当呼吸肌的能力不足以支撑你的身体这样强度运动时，就会通过痉挛的方式告诉你，你需要停下来或者减慢速度。</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>平时可以配合做一些腰腹部的核心训练，比如说卷腹、平板支撑等，多练习腹部呼吸法，这样在加强核心力量的同时，也加强了呼吸肌的能力。</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>跑步之前，要做好充分的热身，不要上来就加速跑，逐渐平缓地提升呼吸节奏，你得让呼吸肌有适应的过程。</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>如果跑步时出现了岔气情况，可以放慢跑步速度；严重的话，可以停下来调整呼吸，并且身体向相反方向伸展，右侧岔气的话，那就向上伸直右侧手臂，并向左侧伸展 15～30 秒.</p>
|
||||
</li>
|
||||
</ul>
|
||||
<blockquote>
|
||||
<p>跑步前期很难坚持，怎么办？</p>
|
||||
</blockquote>
|
||||
<ul>
|
||||
<li>
|
||||
<p>刚开始跑，心肺体能都还跟不上，那可能跑起来不太有成就感，没有正反馈，也不好坚持。因此,需要制定合理的跑步计划(时间/距离)</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>从跑够 10 分钟开始的。之后每周的运动强度可以比前一周提高 5%。</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>无论是跑步还是健身，训练时长最好控制在 1 个小时之内，因为 1 个小时的运动会让我们身心都得到满足.</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>在前期跑步的时候，不要跑上坡路，上坡路非常累.</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>另外可以通过听音乐、给跑步赋予意义和仪式感、装备奖励等方式，帮助自己度过刚开始跑时的枯燥期。</p>
|
||||
</li>
|
||||
</ul>
|
||||
<hr />
|
||||
<p><strong>Done</strong></p>
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
<div class="pagination">
|
||||
<div class="pagination__title">
|
||||
<span class="pagination__title-h">Thanks for reading! Read other posts?</span>
|
||||
<hr />
|
||||
</div>
|
||||
<div class="pagination__buttons">
|
||||
<span class="button previous">
|
||||
<a href="https://blog.dich.bid/about-cslearning/">
|
||||
<span class="button__icon">←</span>
|
||||
<span class="button__text">乱七八糟:计算机科学优质视频</span>
|
||||
</a>
|
||||
</span>
|
||||
|
||||
|
||||
<span class="button next">
|
||||
<a href="https://blog.dich.bid/about-runer-2/">
|
||||
<span class="button__text">乱七八糟:跑步笔记(二)</span>
|
||||
<span class="button__icon">→</span>
|
||||
</a>
|
||||
</span>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
</div>
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
<footer class="footer">
|
||||
<div class="footer__inner">
|
||||
<div class="copyright">
|
||||
<span>©
|
||||
2025
|
||||
Dichgrem</span>
|
||||
<span class="copyright-theme">
|
||||
<span class="copyright-theme-sep"> :: CC BY-SA 4.0 :: A friend comes from distant lands</span>
|
||||
</a>
|
||||
</span>
|
||||
</div>
|
||||
</div>
|
||||
</footer>
|
||||
|
||||
</div>
|
||||
</body>
|
||||
</html>
|
||||
|
||||
250
public/about-runer-2/index.html
Normal file
250
public/about-runer-2/index.html
Normal file
@ -0,0 +1,250 @@
|
||||
<!DOCTYPE html>
|
||||
<html lang="en">
|
||||
|
||||
<head>
|
||||
<title>Dich'blog</title>
|
||||
|
||||
<meta http-equiv="content-type" content="text/html; charset=utf-8">
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1">
|
||||
<meta name="robots" content="noodp"/>
|
||||
|
||||
<link rel="stylesheet" href="https://blog.dich.bid/style.css">
|
||||
<link rel="stylesheet" href="https://blog.dich.bid/color/blue.css">
|
||||
|
||||
<link rel="stylesheet" href="https://blog.dich.bid/color/background_dark.css">
|
||||
|
||||
<link rel="stylesheet" href="https://blog.dich.bid/font-hack-subset.css">
|
||||
|
||||
<meta name="description" content="">
|
||||
|
||||
<meta property="og:description" content="">
|
||||
<meta property="og:title" content="Dich'blog">
|
||||
<meta property="og:type" content="article">
|
||||
<meta property="og:url" content="https://blog.dich.bid/about-runer-2/">
|
||||
|
||||
<meta name="twitter:card" content="summary_large_image">
|
||||
<meta name="twitter:description" content="">
|
||||
<meta name="twitter:title" content="Dich'blog">
|
||||
<meta property="twitter:domain" content="blog.dich.bid">
|
||||
<meta property="twitter:url" content="https://blog.dich.bid/about-runer-2/">
|
||||
|
||||
<link rel="alternate" type="application/atom+xml" title="Dich'blog Atom Feed" href="https://blog.dich.bid/atom.xml" />
|
||||
|
||||
|
||||
<link rel="icon" type="image/png" href=/dich.webp />
|
||||
|
||||
<!-- ✅ Added center alignment styles -->
|
||||
<style>
|
||||
.footer {
|
||||
text-align: center;
|
||||
padding: 1rem 0;
|
||||
}
|
||||
|
||||
.footer__inner {
|
||||
display: flex;
|
||||
justify-content: center;
|
||||
flex-direction: column;
|
||||
align-items: center;
|
||||
}
|
||||
|
||||
.copyright {
|
||||
text-align: center;
|
||||
}
|
||||
</style>
|
||||
</head>
|
||||
|
||||
<body class="">
|
||||
<div class="container">
|
||||
|
||||
<header class="header">
|
||||
<div class="header__inner">
|
||||
<div class="header__logo">
|
||||
|
||||
<a href="https://blog.dich.bid" style="text-decoration: none;">
|
||||
<div class="logo">
|
||||
|
||||
Dich'blog
|
||||
|
||||
</div>
|
||||
</a>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
|
||||
<nav class="menu">
|
||||
<ul class="menu__inner">
|
||||
<li><a href="https://blog.dich.bid">blog</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/archive">archive</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/tags">tags</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/weekly">weekly</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/search">search</a></li>
|
||||
|
||||
<li class="active"><a href="https://blog.dich.bid/about">about me</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/links">links</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/atom.xml">rss</a></li>
|
||||
|
||||
<li><a href="https://github.com/Dichgrem" target="_blank" rel="noopener noreferrer">github</a></li>
|
||||
</ul>
|
||||
</nav>
|
||||
|
||||
|
||||
|
||||
</header>
|
||||
|
||||
|
||||
<div class="content">
|
||||
|
||||
<div class="post">
|
||||
|
||||
<h1 class="post-title"><a href="https://blog.dich.bid/about-runer-2/">乱七八糟:跑步笔记(二)</a></h1>
|
||||
<div class="post-meta-inline">
|
||||
|
||||
<span class="post-date">
|
||||
2024-06-11
|
||||
</span>
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
<span class="post-tags-inline">
|
||||
:: tags:
|
||||
<a class="post-tag" href="https://blog.dich.bid/tags/luan-qi-ba-zao/">#乱七八糟</a></span>
|
||||
|
||||
|
||||
<div class="post-content">
|
||||
<p>前言 最近读得<<亮哥跑经>>一书,遂迷上跑步;奈何体重偏高,略微有些吃力.以下是一些笔记:</p>
|
||||
<span id="continue-reading"></span><h2 id="guan-yu-pao-zi">关于跑姿:</h2>
|
||||
<blockquote>
|
||||
<p>摆臂</p>
|
||||
</blockquote>
|
||||
<ul>
|
||||
<li>
|
||||
<p>摆臂的主要目的，是对抗腿的阻力，来保持我们的身体平衡，让身体向正前方笔直前行。</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>摆臂和步频是紧密相关的。所以你看那些短跑运动员，他们上肢力量也很发达，因为他们短跑时速度很快，步频很大，如果没有相应的摆臂，他们身体会不平衡.</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>正确的摆臂应该是什么样的呢？既然我们是向前跑，那么摆臂也应该是垂直向前的，而不是在胸口前左右交叉的，因为你左右摆臂的时候，等于给身体一个左右旋转的力，实际上这消耗了多余的能量，对于腰腹肌肉及腰椎压力也比较大，跑的也不快也不长久。</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>正确的摆臂应该是肩膀放松状态下，以肩关节为轴的，大臂和小臂成 90 度角，大臂带动小臂前后垂直摆动。 抬起时，大拇指不要超过眉毛，回来时，大拇指不要越过躯干。</p>
|
||||
</li>
|
||||
</ul>
|
||||
<blockquote>
|
||||
<p>常见的错误摆臂方式</p>
|
||||
</blockquote>
|
||||
<ul>
|
||||
<li>
|
||||
<p>双臂在身前交叉，我称之为“戳鼻孔跑”。当你的双臂不是垂直向前用力，而是左右旋转的时候，身体会消耗多余能量。</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>只摆小臂，不摆大臂。跑步时把大臂夹得特别紧，而且摆臂是以肘关节为轴了，这是不对的。</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>不摆手臂，摆动躯干。完全只是靠摆动躯干的方式在维持平衡，这样会造成能量过度损失，而且对腰椎压力也比较大。</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>摆臂高度不对，比如说摆臂过大，或是一面高一面低。摆臂过大是短跑的摆臂方式，长跑的摆臂，向前手指不超过眉梢、向后不超过躯干。</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>摆臂一面高一面低，一般我们戴臂包、手中握手机或水瓶等容易出现这个问题。摆臂是帮我们平衡的，如果你的左右摆臂高度不一样，那跑姿一定是变形的，也就是说身体左右受力是不均匀的，这时很容易导致身体的一侧肌肉紧张，出现像跑步膝等身体损伤.</p>
|
||||
</li>
|
||||
</ul>
|
||||
<blockquote>
|
||||
<p>摆腿</p>
|
||||
</blockquote>
|
||||
<ul>
|
||||
<li>
|
||||
<p>看一个人摆腿对不对，就看他是用髋关节跑还是膝关节跑。</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>正确的长跑姿势，应该是核心收紧，臀大肌和大腿后侧肌肉发力，以髋关节为轴，带动膝关节和踝关节向前跑动，小腿只是辅助性肌肉，它发力不多。所以长跑运动员基本上臀部都是很翘的，而小腿纤细。</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>如果一直屈髋“坐着跑”，跑步时就会经常出现重心不稳的情况，而且地面给你带来的冲击力，你不能很好地将它传导到臀部，也就是说，这些冲击力都消耗在了膝关节这里。这样的话，一是你很难跑得长久，二是容易把小腿跑粗，三是全身的压力都集中在膝关节，容易带来一些慢性损伤。</p>
|
||||
</li>
|
||||
</ul>
|
||||
<blockquote>
|
||||
<p>着地</p>
|
||||
</blockquote>
|
||||
<ul>
|
||||
<li>
|
||||
<p>跑步的着地方式主要有三种：前脚掌、中脚掌和后脚掌。如果我们是长跑的话，主要采用的是后脚跟着地和中足着地的方式。</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>前脚掌着地会帮助我们跑步提速，但是大众跑者跑长跑，不是比谁跑的快，而是看谁跑得更健康、更安全、更节能。</p>
|
||||
</li>
|
||||
</ul>
|
||||
<blockquote>
|
||||
<p>前倾跑 & 低头族</p>
|
||||
</blockquote>
|
||||
<ul>
|
||||
<li>
|
||||
<p>跑步时腰疼或者下背部疼痛，其实这主要和你跑步时身体前倾了有关。因为当你身体前倾时，你的屈髋肌群，也就是胯骨部位会过度紧张，你的下背部肌肉会被反向拉长，它的压力就会增加。这就好比你背个书包去跑步，背部肌肉很容易疲劳的。</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>而且当你身体前倾的时候，你的髋关节不能很好的帮你做功，身体容易左右扭动，时间长了也容易引起腰部肌肉酸疼。</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>还有的人是低头跑，如果有这个情况，可以在跑步之前做一些颈部伸展；跑步时，不要探头，稍微收下巴，眼睛可以平视前方 50 米左右地方，这样就可以很好地解决这个问题了。</p>
|
||||
</li>
|
||||
</ul>
|
||||
<hr />
|
||||
<p><strong>Done</strong></p>
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
<div class="pagination">
|
||||
<div class="pagination__title">
|
||||
<span class="pagination__title-h">Thanks for reading! Read other posts?</span>
|
||||
<hr />
|
||||
</div>
|
||||
<div class="pagination__buttons">
|
||||
<span class="button previous">
|
||||
<a href="https://blog.dich.bid/about-runer-1/">
|
||||
<span class="button__icon">←</span>
|
||||
<span class="button__text">乱七八糟:跑步笔记(一)</span>
|
||||
</a>
|
||||
</span>
|
||||
|
||||
|
||||
<span class="button next">
|
||||
<a href="https://blog.dich.bid/about-server-set/">
|
||||
<span class="button__text">乱七八糟:服务器初始化与安全设置</span>
|
||||
<span class="button__icon">→</span>
|
||||
</a>
|
||||
</span>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
</div>
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
<footer class="footer">
|
||||
<div class="footer__inner">
|
||||
<div class="copyright">
|
||||
<span>©
|
||||
2025
|
||||
Dichgrem</span>
|
||||
<span class="copyright-theme">
|
||||
<span class="copyright-theme-sep"> :: CC BY-SA 4.0 :: A friend comes from distant lands</span>
|
||||
</a>
|
||||
</span>
|
||||
</div>
|
||||
</div>
|
||||
</footer>
|
||||
|
||||
</div>
|
||||
</body>
|
||||
</html>
|
||||
|
||||
545
public/about-server-set/index.html
Normal file
545
public/about-server-set/index.html
Normal file
@ -0,0 +1,545 @@
|
||||
<!DOCTYPE html>
|
||||
<html lang="en">
|
||||
|
||||
<head>
|
||||
<title>Dich'blog</title>
|
||||
|
||||
<meta http-equiv="content-type" content="text/html; charset=utf-8">
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1">
|
||||
<meta name="robots" content="noodp"/>
|
||||
|
||||
<link rel="stylesheet" href="https://blog.dich.bid/style.css">
|
||||
<link rel="stylesheet" href="https://blog.dich.bid/color/blue.css">
|
||||
|
||||
<link rel="stylesheet" href="https://blog.dich.bid/color/background_dark.css">
|
||||
|
||||
<link rel="stylesheet" href="https://blog.dich.bid/font-hack-subset.css">
|
||||
|
||||
<meta name="description" content="">
|
||||
|
||||
<meta property="og:description" content="">
|
||||
<meta property="og:title" content="Dich'blog">
|
||||
<meta property="og:type" content="article">
|
||||
<meta property="og:url" content="https://blog.dich.bid/about-server-set/">
|
||||
|
||||
<meta name="twitter:card" content="summary_large_image">
|
||||
<meta name="twitter:description" content="">
|
||||
<meta name="twitter:title" content="Dich'blog">
|
||||
<meta property="twitter:domain" content="blog.dich.bid">
|
||||
<meta property="twitter:url" content="https://blog.dich.bid/about-server-set/">
|
||||
|
||||
<link rel="alternate" type="application/atom+xml" title="Dich'blog Atom Feed" href="https://blog.dich.bid/atom.xml" />
|
||||
|
||||
|
||||
<link rel="icon" type="image/png" href=/dich.webp />
|
||||
|
||||
<!-- ✅ Added center alignment styles -->
|
||||
<style>
|
||||
.footer {
|
||||
text-align: center;
|
||||
padding: 1rem 0;
|
||||
}
|
||||
|
||||
.footer__inner {
|
||||
display: flex;
|
||||
justify-content: center;
|
||||
flex-direction: column;
|
||||
align-items: center;
|
||||
}
|
||||
|
||||
.copyright {
|
||||
text-align: center;
|
||||
}
|
||||
</style>
|
||||
</head>
|
||||
|
||||
<body class="">
|
||||
<div class="container">
|
||||
|
||||
<header class="header">
|
||||
<div class="header__inner">
|
||||
<div class="header__logo">
|
||||
|
||||
<a href="https://blog.dich.bid" style="text-decoration: none;">
|
||||
<div class="logo">
|
||||
|
||||
Dich'blog
|
||||
|
||||
</div>
|
||||
</a>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
|
||||
<nav class="menu">
|
||||
<ul class="menu__inner">
|
||||
<li><a href="https://blog.dich.bid">blog</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/archive">archive</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/tags">tags</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/weekly">weekly</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/search">search</a></li>
|
||||
|
||||
<li class="active"><a href="https://blog.dich.bid/about">about me</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/links">links</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/atom.xml">rss</a></li>
|
||||
|
||||
<li><a href="https://github.com/Dichgrem" target="_blank" rel="noopener noreferrer">github</a></li>
|
||||
</ul>
|
||||
</nav>
|
||||
|
||||
|
||||
|
||||
</header>
|
||||
|
||||
|
||||
<div class="content">
|
||||
|
||||
<div class="post">
|
||||
|
||||
<h1 class="post-title"><a href="https://blog.dich.bid/about-server-set/">乱七八糟:服务器初始化与安全设置</a></h1>
|
||||
<div class="post-meta-inline">
|
||||
|
||||
<span class="post-date">
|
||||
2024-06-12
|
||||
</span>
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
<span class="post-tags-inline">
|
||||
:: tags:
|
||||
<a class="post-tag" href="https://blog.dich.bid/tags/luan-qi-ba-zao/">#乱七八糟</a></span>
|
||||
|
||||
|
||||
<div class="post-content">
|
||||
<p>前言 本文记录服务器常用操作步骤。</p>
|
||||
<span id="continue-reading"></span><h2 id="doamin">Doamin</h2>
|
||||
<p>建站不一定需要服务器、域名和备案。尤其不要买腾讯云，不要买CN域名；备案过程要填很多个人信息，且一周没有解析网站，备案就会自动注销。</p>
|
||||
<ul>
|
||||
<li>
|
||||
<p><strong>cn 域名没有隐私保护（whois protection）</strong>。国内域名注册商说的隐私保护根本是自欺欺人，在它们隐私保护就是在自己的查询服务隐藏注册人信息。但在别的地方是能查到的，在<a href="https://whois.cnnic.cn/">中国互联网络信息中心</a>可以查到每个 cn 域名注册人的姓名和邮箱。</p>
|
||||
</li>
|
||||
<li>
|
||||
<p><strong>注册 cn 域名必须使用真实身份信息</strong>。要是你想用假信息注册来保护隐私，那就太天真了。审核的时候不会通过的。真的不想用自己的信息注册的话，要么以公司名义注册，但公司的法定代表人还是能查到的。要么叫别人注册域名之后给你用，可谁愿意冒这种风险呢。</p>
|
||||
</li>
|
||||
<li>
|
||||
<p><strong>cn 域名无法删除</strong>。如果你觉得 cn 域名暴露了你的隐私，那对不起，这是不能注销的<a href="https://cyrusyip.org/zh-cn/post/2021/05/25/damn-cn-domain/#fn:3">3</a>。你只能修改邮箱地址，然后等到它过期。或者转让给别人，不过感觉把别人推到火坑里不太好啊。</p>
|
||||
</li>
|
||||
<li>
|
||||
<p><strong>cn 域名有被停用的风险</strong>。2008 年，有人以跳水奥运冠军吴敏霞拼音注册了 wuminxia.cn，<a href="https://www.cnbeta.com/articles/tech/62209.htm">结果被中国互联网络信息中心（CNNIC）回收了域名</a>，并转交给国家体育总局。此域名在 2021 年 2 月 28 日被优视科技<a href="https://whois.cnnic.cn/WhoisServlet?queryType=Domain&domain=wuminxia.cn">注册</a>，呵呵。2009 年，牛博网被域名注册商万网停止解析。</p>
|
||||
</li>
|
||||
</ul>
|
||||
<h2 id="vps">VPS</h2>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span># 更新系统
|
||||
</span><span>apt update && apt upgrade -y
|
||||
</span><span>apt install wget curl vim sudo neofetch
|
||||
</span><span># 添加普通用户并赋予sudo
|
||||
</span><span>adduser xxx
|
||||
</span><span>sudo usermod -aG sudo xxx
|
||||
</span></code></pre>
|
||||
<h2 id="bbr">BBR</h2>
|
||||
<ul>
|
||||
<li>查询系统所支持的拥塞控制算法</li>
|
||||
</ul>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>sysctl net.ipv4.tcp_available_congestion_control
|
||||
</span></code></pre>
|
||||
<ul>
|
||||
<li>查询正在使用中的拥塞控制算法（Linux 绝大部分系统默认为 Cubic 算法）</li>
|
||||
</ul>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>sysctl net.ipv4.tcp_congestion_control
|
||||
</span></code></pre>
|
||||
<ul>
|
||||
<li>指定拥塞控制算法为 bbr</li>
|
||||
</ul>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>echo net.ipv4.tcp_congestion_control=bbr >> /etc/sysctl.conf && sysctl -p
|
||||
</span></code></pre>
|
||||
<h2 id="safe">Safe</h2>
|
||||
<blockquote>
|
||||
<p>使用密码登录：更换SSH端口+安装UFW+安装Fail2ban
|
||||
使用密钥登录：不用额外操作</p>
|
||||
</blockquote>
|
||||
<h3 id="geng-huan-sshduan-kou">更换SSH端口</h3>
|
||||
<p>使用root账户或已经有sudo权限的用户登录到系统。</p>
|
||||
<p>打开SSH配置文件<code>sshd_config</code>，可以使用文本编辑器如nano或vi。以下是使用nano编辑器的示例：</p>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>sudo vim /etc/ssh/sshd_config
|
||||
</span></code></pre>
|
||||
<p>在配置文件中找到以下行：</p>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>Port 22
|
||||
</span></code></pre>
|
||||
<p>这是SSH默认的端口号，你可以将其更改为你想要的任何未被占用的端口号。例如，将端口更改为2222：</p>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>Port 2222
|
||||
</span></code></pre>
|
||||
<p>保存并关闭文本编辑器。重新启动SSH服务，以应用更改：</p>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>sudo service ssh restart
|
||||
</span></code></pre>
|
||||
<p>或者，如果你的系统使用systemd，可以使用以下命令：</p>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>sudo systemctl restart ssh
|
||||
</span></code></pre>
|
||||
<h3 id="an-zhuang-ufw">安装 UFW</h3>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>sudo apt install ufw
|
||||
</span></code></pre>
|
||||
<p><strong>如果你在远程位置连接你的服务器，在启用 UFW 防火墙之前，你必须显式允许进来的 SSH 连接。否则，你将永远都无法连接到机器上。</strong></p>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>sudo ufw allow 22/tcp
|
||||
</span></code></pre>
|
||||
<blockquote>
|
||||
<p>如果 SSH 运行在非标准端口，你需要将上述命令中的 22 端口替换为对应的 SSH 端口。</p>
|
||||
</blockquote>
|
||||
<p><strong>启动 UFW</strong></p>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>sudo ufw enable
|
||||
</span></code></pre>
|
||||
<h3 id="an-zhuang-fail2ban">安装 Fail2ban</h3>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>sudo apt-get install fail2ban
|
||||
</span></code></pre>
|
||||
<p><strong>2、Debian 12 及以上的版本需要手动安装 rsyslog</strong></p>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>sudo apt-get install rsyslog
|
||||
</span></code></pre>
|
||||
<p><strong>3、启动 Fail2ban 服务</strong></p>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>sudo systemctl start fail2ban
|
||||
</span></code></pre>
|
||||
<p><strong>4、开机自启动</strong></p>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>sudo systemctl enable fail2ban
|
||||
</span></code></pre>
|
||||
<p><strong>5、查看 Fail2ban 服务状态。</strong></p>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>sudo systemctl status fail2ban
|
||||
</span></code></pre>
|
||||
<h3 id="gai-wei-mi-yao-deng-lu">改为密钥登录</h3>
|
||||
<ul>
|
||||
<li>执行以下命令生成.pub后缀的公钥和无后缀的密钥：</li>
|
||||
</ul>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>ssh-keygen
|
||||
</span></code></pre>
|
||||
<p>注意不同密钥对名称不能相同；同时可以为这两个文件用密码加密；</p>
|
||||
<ul>
|
||||
<li>
|
||||
<p>随后将.pub后缀的公钥中的内容写入服务器的<code>~/.ssh/authorized_keys</code>中；</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>使用以下命令编译服务器的SSH配置：</p>
|
||||
</li>
|
||||
</ul>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>vim /etc/ssh/sshd_config
|
||||
</span></code></pre>
|
||||
<p>将其中的该行改为<code>PasswordAuthentication no</code>，保存退出；随后使用</p>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>sudo systemctl restart sshd
|
||||
</span></code></pre>
|
||||
<p>重启SSH即可禁用密码登录；</p>
|
||||
<ul>
|
||||
<li>
|
||||
<p>将<strong>PermitRootLogin</strong>一栏改为<strong>PermitRootLogin prohibit-password</strong>，即可实现仅root用户密钥登录；</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>使用以下命令查看输出，</p>
|
||||
</li>
|
||||
</ul>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>sudo cat /etc/ssh/sshd_config | grep -E 'PasswordAuthentication|PubkeyAuthentication'
|
||||
</span></code></pre>
|
||||
<p>如有<strong>PasswordAuthentication no → 禁用密码登录</strong>以及<strong>PubkeyAuthentication yes → 允许密钥登录</strong>则成功。</p>
|
||||
<blockquote>
|
||||
<p>注意<strong>authorized_keys</strong>的权限为600，如果不是则需要改正：<code>chmod 600 ~/.ssh/authorized_keys</code></p>
|
||||
</blockquote>
|
||||
<h2 id="docker">Docker</h2>
|
||||
<h3 id="jiao-ben-an-zhuang">脚本安装</h3>
|
||||
<p>Docker 官方提供了一个安装脚本，可以自动选择适当版本，并规避仓库问题：</p>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>curl -fsSL https://get.docker.com -o get-docker.sh
|
||||
</span><span>sudo sh get-docker.sh
|
||||
</span></code></pre>
|
||||
<p>这个脚本会为你的系统自动选择合适的安装方式。</p>
|
||||
<h3 id="xie-zai-docker">卸载 Docker</h3>
|
||||
<p>要删除所有 Docker 容器和 Docker 本身，可以按照以下步骤操作：</p>
|
||||
<ol>
|
||||
<li>首先停止所有正在运行的容器：</li>
|
||||
</ol>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>docker stop $(docker ps -aq)
|
||||
</span></code></pre>
|
||||
<ol start="2">
|
||||
<li>删除所有容器</li>
|
||||
</ol>
|
||||
<p>删除所有容器（包括停止的容器）：</p>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>docker rm $(docker ps -aq)
|
||||
</span></code></pre>
|
||||
<ol start="3">
|
||||
<li>删除所有镜像</li>
|
||||
</ol>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>docker rmi $(docker images -q)
|
||||
</span></code></pre>
|
||||
<ol start="4">
|
||||
<li>删除所有网络</li>
|
||||
</ol>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>docker network prune -f
|
||||
</span></code></pre>
|
||||
<ol start="5">
|
||||
<li>删除所有未使用的卷</li>
|
||||
</ol>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>docker volume prune -f
|
||||
</span></code></pre>
|
||||
<ol start="6">
|
||||
<li>卸载 Docker</li>
|
||||
</ol>
|
||||
<p>最后，如果您希望完全删除 Docker 本身，可以执行以下命令:</p>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>sudo apt-get purge docker-ce docker-ce-cli containerd.io
|
||||
</span><span>sudo apt-get autoremove --purge
|
||||
</span><span>sudo rm -rf /var/lib/docker
|
||||
</span><span>sudo rm -rf /etc/docker
|
||||
</span></code></pre>
|
||||
<p>这些命令会卸载 Docker 软件并删除 Docker 数据目录。</p>
|
||||
<h3 id="docker-chang-yong-ming-ling">Docker 常用命令</h3>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>docker-compose up -d #在后台启动容器
|
||||
</span><span>docker-compose ps #查看正在运行的容器
|
||||
</span><span>docker-compose down #停止并移除所有运行中的容器
|
||||
</span><span>docker-compose stop #停止容器，但保留数据和卷
|
||||
</span><span>docker pull <镜像名称>:latest #拉取最新镜像
|
||||
</span><span>docker-compose build #更新镜像后重新构建
|
||||
</span><span>docker-compose logs #查看日志
|
||||
</span><span>docker image prune -a #删除所有未被容器使用的镜像
|
||||
</span></code></pre>
|
||||
<h2 id="chang-yong-huan-jing">常用环境</h2>
|
||||
<ul>
|
||||
<li>ALL</li>
|
||||
</ul>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>apt install curl wget gpg vim nano sudo neofetch openssh-server
|
||||
</span></code></pre>
|
||||
<ul>
|
||||
<li>C/C++</li>
|
||||
</ul>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>sudo apt install build-essential gdb cmake clangd clang-format libstdc++-dev
|
||||
</span></code></pre>
|
||||
<ul>
|
||||
<li>Miniconda</li>
|
||||
</ul>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>wget https://repo.anaconda.com/miniconda/Miniconda3-latest-Linux-x86_64.sh
|
||||
</span><span>bash Miniconda3-latest-Linux-x86_64.sh
|
||||
</span></code></pre>
|
||||
<ul>
|
||||
<li>UV</li>
|
||||
</ul>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>curl -LsSf https://astral.sh/uv/install.sh | sh
|
||||
</span></code></pre>
|
||||
<ul>
|
||||
<li>Docker</li>
|
||||
</ul>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>curl -fsSL https://get.docker.com -o get-docker.sh
|
||||
</span><span>sudo sh get-docker.sh
|
||||
</span></code></pre>
|
||||
<ul>
|
||||
<li>OpenCV</li>
|
||||
</ul>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>sudo apt install tree libx11-dev libgtk-3-dev freeglut3-dev libopencv-dev libdlib-dev
|
||||
</span></code></pre>
|
||||
<ul>
|
||||
<li>Vmware</li>
|
||||
</ul>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>sudo apt install open-vm-tools
|
||||
</span><span>sudo apt install open-vm-tools-desktop
|
||||
</span></code></pre>
|
||||
<blockquote>
|
||||
<p>Vscode无法连接：需要删除本地存储的错误密钥，powershell：</p>
|
||||
</blockquote>
|
||||
<pre data-lang="powershell" style="background-color:#151515;color:#e8e8d3;" class="language-powershell "><code class="language-powershell" data-lang="powershell"><span>(Get-Content </span><span style="color:#556633;">"</span><span style="color:#ffb964;">$env:USERPROFILE</span><span style="color:#99ad6a;">\.ssh\known_hosts</span><span style="color:#556633;">"</span><span>) |
|
||||
</span><span>Where-Object { $_ -notmatch </span><span style="color:#556633;">'</span><span style="color:#99ad6a;"><你的IP></span><span style="color:#556633;">' </span><span>} |
|
||||
</span><span>Set-Content </span><span style="color:#556633;">"</span><span style="color:#ffb964;">$env:USERPROFILE</span><span style="color:#99ad6a;">\.ssh\known_hosts</span><span style="color:#556633;">"
|
||||
</span></code></pre>
|
||||
<h2 id="1panel">1panel</h2>
|
||||
<p>执行如下命令一键安装 1Panel:</p>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>curl -sSL https://resource.fit2cloud.com/1panel/package/quick_start.sh -o quick_start.sh && sudo bash quick_start.sh
|
||||
</span></code></pre>
|
||||
<h3 id="jin-yong-ipv6">禁用 IPv6</h3>
|
||||
<p>手动 禁用 VPS 的 IPv6 命令:</p>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>sysctl -w net.ipv6.conf.all.disable_ipv6=1
|
||||
</span><span>sysctl -w net.ipv6.conf.default.disable_ipv6=1
|
||||
</span></code></pre>
|
||||
<p>如果想重启系统也生效， 执行：</p>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>echo 'net.ipv6.conf.all.disable_ipv6=1' >> /etc/sysctl.conf
|
||||
</span><span>echo 'net.ipv6.conf.default.disable_ipv6=1' >> /etc/sysctl.conf
|
||||
</span></code></pre>
|
||||
<p>手动 启用 VPS 的 IPv6 命令:</p>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>sysctl -w net.ipv6.conf.all.disable_ipv6=0
|
||||
</span><span>sysctl -w net.ipv6.conf.default.disable_ipv6=0
|
||||
</span></code></pre>
|
||||
<p>重新载入 sysctl 配置</p>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>sysctl --system # reload sysctl
|
||||
</span></code></pre>
|
||||
<p>如果重载, 还无效果, 可能要 reboot 重启下.
|
||||
查看 VPS 的 IPv6 信息</p>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>ip -6 addr show scope global
|
||||
</span><span>
|
||||
</span><span>或者 curl ipv6.ip.sb
|
||||
</span></code></pre>
|
||||
<h2 id="ipzheng-shu-shen-qing-bu-shu">IP证书申请部署</h2>
|
||||
<ul>
|
||||
<li>
|
||||
<p>在 <a href="https://zerossl.com/">ZeroSSL</a> 中申请一个90天的证书；</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>然后在VPS上输入以下命令：</p>
|
||||
</li>
|
||||
</ul>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>mkdir -p ./.well-known/pki-validation
|
||||
</span></code></pre>
|
||||
<ul>
|
||||
<li>
|
||||
<p>随后在ZeroSSL中将所给出的类似<strong>B992F08CB46748D02E4C553A4038BC.txt</strong>复制；</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>将从ZeroSSL下载得到的文件打开，复制里面的东西形成以下的格式:<code>将pki-validation/之后EOF之前的内容</code>替换为你自己的。</p>
|
||||
</li>
|
||||
</ul>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>cat << EOF | sudo tee ./.well-known/pki-validation/B992F08CB46748D02E4C553A4038BC.txt
|
||||
</span><span>254563C20918258D661E7D43D6A43A2A258857E191977DD5F740FBB9ABD25279
|
||||
</span><span>comodoca.com
|
||||
</span><span>ca5792984e3f0a1
|
||||
</span><span>EOF
|
||||
</span></code></pre>
|
||||
<p>随后在VPS上运行该命令。</p>
|
||||
<ul>
|
||||
<li>开启一个临时HTTP服务器：</li>
|
||||
</ul>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>python3 -m http.server 80
|
||||
</span></code></pre>
|
||||
<ul>
|
||||
<li>随后即可在ZeroSSL中验证证书并开启SSL。</li>
|
||||
</ul>
|
||||
<h2 id="wang-ji-mi-ma-zen-me-ban">忘记密码怎么办</h2>
|
||||
<p>通过恢复模式 (Recovery Mode) 修改用户权限：</p>
|
||||
<ul>
|
||||
<li>
|
||||
<p>重启计算机，按住 Shift 键进入 GRUB 菜单（或者按 Esc 键）。</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>在 GRUB 菜单中，选择<code>Advanced options for Ubuntu</code>然后选择带有<code>recovery mode</code>的内核版本。</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>进入恢复模式后，选择<code>root – Drop to root shell prompt</code>进入 root shell（不需要密码）。</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>挂载文件系统为可写模式：</p>
|
||||
</li>
|
||||
</ul>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>mount -o remount,rw /
|
||||
</span></code></pre>
|
||||
<ul>
|
||||
<li>将用户添加到 sudo 组：</li>
|
||||
</ul>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>usermod -aG sudo 用户名
|
||||
</span></code></pre>
|
||||
<ul>
|
||||
<li>重启计算机：</li>
|
||||
</ul>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>reboot
|
||||
</span></code></pre>
|
||||
<h2 id="geng-huan-nei-he">更换内核</h2>
|
||||
<p>以Xanmod为例：</p>
|
||||
<ol>
|
||||
<li>添加 XanMod 仓库密钥和源</li>
|
||||
</ol>
|
||||
<pre data-lang="bash" style="background-color:#151515;color:#e8e8d3;" class="language-bash "><code class="language-bash" data-lang="bash"><span>echo </span><span style="color:#556633;">'</span><span style="color:#99ad6a;">deb [signed-by=/usr/share/keyrings/xanmod.gpg] http://deb.xanmod.org releases main</span><span style="color:#556633;">' </span><span>| </span><span style="color:#ffb964;">sudo</span><span> tee /etc/apt/sources.list.d/xanmod.list
|
||||
</span><span style="color:#ffb964;">curl -fsSL</span><span> https://dl.xanmod.org/gpg.key | </span><span style="color:#ffb964;">gpg --dearmor </span><span>| </span><span style="color:#ffb964;">sudo</span><span> tee /usr/share/keyrings/xanmod.gpg > /dev/null
|
||||
</span></code></pre>
|
||||
<ol start="2">
|
||||
<li>更新软件包列表</li>
|
||||
</ol>
|
||||
<pre data-lang="bash" style="background-color:#151515;color:#e8e8d3;" class="language-bash "><code class="language-bash" data-lang="bash"><span style="color:#ffb964;">sudo</span><span> apt update
|
||||
</span></code></pre>
|
||||
<ol start="3">
|
||||
<li>搜索可用内核</li>
|
||||
</ol>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>apt search xanmod
|
||||
</span><span>sudo apt install linux-image-6.8.6-x64v3-xanmod1 linux-headers-6.8.6-x64v3-xanmod1
|
||||
</span></code></pre>
|
||||
<h3 id="chang-jian-xanmod-nei-he-hou-zhui-han-yi-dui-bi">常见 XanMod 内核后缀含义对比</h3>
|
||||
<table><thead><tr><th>后缀示例</th><th>含义简述</th><th>适合用途</th></tr></thead><tbody>
|
||||
<tr><td><code>xanmod1</code>, <code>xanmod2</code>, …</td><td>主线 XanMod 版本编号（带通用优化）</td><td>桌面、通用、游戏</td></tr>
|
||||
<tr><td><code>x64v3-xanmod1</code></td><td>针对 <strong>x86_64-v3 架构优化</strong>（AVX2 以上指令集）</td><td>高性能桌面、较新 CPU（2011+）</td></tr>
|
||||
<tr><td><code>rt-xanmod1</code></td><td><strong>实时（RT）内核</strong>，用于极低延迟任务</td><td>音频制作、工业控制</td></tr>
|
||||
<tr><td><code>lts-xanmod1</code></td><td><strong>长期支持版本</strong>（LTS）</td><td>服务器、稳定性优先</td></tr>
|
||||
<tr><td><code>edge-xanmod1</code></td><td>更前沿、不稳定的测试版本</td><td>喜欢尝鲜的高级用户</td></tr>
|
||||
<tr><td><code>x64v2-xanmod1</code>, <code>x64v4-…</code></td><td>针对特定 <strong>微架构（CPU 指令集）</strong> 的优化版本</td><td>有特定硬件支持的系统</td></tr>
|
||||
</tbody></table>
|
||||
<p>你可以用以下命令检测你的 CPU 是否支持 <code>x64v3</code>：</p>
|
||||
<pre data-lang="bash" style="background-color:#151515;color:#e8e8d3;" class="language-bash "><code class="language-bash" data-lang="bash"><span style="color:#ffb964;">lscpu </span><span>| </span><span style="color:#ffb964;">grep</span><span> avx2
|
||||
</span></code></pre>
|
||||
<p>如果输出中有 <code>avx2</code>，就可以用 <code>x64v3</code> 版本。</p>
|
||||
<ol start="4">
|
||||
<li>更新 GRUB 并重启</li>
|
||||
</ol>
|
||||
<pre data-lang="bash" style="background-color:#151515;color:#e8e8d3;" class="language-bash "><code class="language-bash" data-lang="bash"><span style="color:#ffb964;">sudo</span><span> update-grub
|
||||
</span><span style="color:#ffb964;">sudo</span><span> reboot
|
||||
</span><span style="color:#ffb964;">uname -r
|
||||
</span></code></pre>
|
||||
<ol start="5">
|
||||
<li>移除旧内核（可选）</li>
|
||||
</ol>
|
||||
<p>查看已安装内核：</p>
|
||||
<pre data-lang="bash" style="background-color:#151515;color:#e8e8d3;" class="language-bash "><code class="language-bash" data-lang="bash"><span style="color:#ffb964;">dpkg --list </span><span>| </span><span style="color:#ffb964;">grep</span><span> linux-image
|
||||
</span></code></pre>
|
||||
<p>移除旧的：</p>
|
||||
<pre data-lang="bash" style="background-color:#151515;color:#e8e8d3;" class="language-bash "><code class="language-bash" data-lang="bash"><span style="color:#ffb964;">sudo</span><span> apt remove linux-image-5.10.0-26-amd64
|
||||
</span></code></pre>
|
||||
<hr />
|
||||
<ol start="6">
|
||||
<li>自动选择 XanMod 为默认（可选）</li>
|
||||
</ol>
|
||||
<p>如果你想默认引导到 XanMod 内核：</p>
|
||||
<p>编辑 <code>/etc/default/grub</code>：</p>
|
||||
<pre data-lang="bash" style="background-color:#151515;color:#e8e8d3;" class="language-bash "><code class="language-bash" data-lang="bash"><span style="color:#ffb964;">GRUB_DEFAULT</span><span>=</span><span style="color:#556633;">"</span><span style="color:#99ad6a;">Advanced options for Debian>Debian, with Linux 6.8.6-x64v3-xanmod1</span><span style="color:#556633;">"
|
||||
</span></code></pre>
|
||||
<p>然后：</p>
|
||||
<pre data-lang="bash" style="background-color:#151515;color:#e8e8d3;" class="language-bash "><code class="language-bash" data-lang="bash"><span style="color:#ffb964;">sudo</span><span> update-grub
|
||||
</span></code></pre>
|
||||
<hr />
|
||||
<p><strong>Done.</strong></p>
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
<div class="pagination">
|
||||
<div class="pagination__title">
|
||||
<span class="pagination__title-h">Thanks for reading! Read other posts?</span>
|
||||
<hr />
|
||||
</div>
|
||||
<div class="pagination__buttons">
|
||||
<span class="button previous">
|
||||
<a href="https://blog.dich.bid/about-runer-2/">
|
||||
<span class="button__icon">←</span>
|
||||
<span class="button__text">乱七八糟:跑步笔记(二)</span>
|
||||
</a>
|
||||
</span>
|
||||
|
||||
|
||||
<span class="button next">
|
||||
<a href="https://blog.dich.bid/network-nginx/">
|
||||
<span class="button__text">Network的艺术:Docker建站与反向代理</span>
|
||||
<span class="button__icon">→</span>
|
||||
</a>
|
||||
</span>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
</div>
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
<footer class="footer">
|
||||
<div class="footer__inner">
|
||||
<div class="copyright">
|
||||
<span>©
|
||||
2025
|
||||
Dichgrem</span>
|
||||
<span class="copyright-theme">
|
||||
<span class="copyright-theme-sep"> :: CC BY-SA 4.0 :: A friend comes from distant lands</span>
|
||||
</a>
|
||||
</span>
|
||||
</div>
|
||||
</div>
|
||||
</footer>
|
||||
|
||||
</div>
|
||||
</body>
|
||||
</html>
|
||||
|
||||
422
public/about-shortcut-key/index.html
Normal file
422
public/about-shortcut-key/index.html
Normal file
@ -0,0 +1,422 @@
|
||||
<!DOCTYPE html>
|
||||
<html lang="en">
|
||||
|
||||
<head>
|
||||
<title>Dich'blog</title>
|
||||
|
||||
<meta http-equiv="content-type" content="text/html; charset=utf-8">
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1">
|
||||
<meta name="robots" content="noodp"/>
|
||||
|
||||
<link rel="stylesheet" href="https://blog.dich.bid/style.css">
|
||||
<link rel="stylesheet" href="https://blog.dich.bid/color/blue.css">
|
||||
|
||||
<link rel="stylesheet" href="https://blog.dich.bid/color/background_dark.css">
|
||||
|
||||
<link rel="stylesheet" href="https://blog.dich.bid/font-hack-subset.css">
|
||||
|
||||
<meta name="description" content="">
|
||||
|
||||
<meta property="og:description" content="">
|
||||
<meta property="og:title" content="Dich'blog">
|
||||
<meta property="og:type" content="article">
|
||||
<meta property="og:url" content="https://blog.dich.bid/about-shortcut-key/">
|
||||
|
||||
<meta name="twitter:card" content="summary_large_image">
|
||||
<meta name="twitter:description" content="">
|
||||
<meta name="twitter:title" content="Dich'blog">
|
||||
<meta property="twitter:domain" content="blog.dich.bid">
|
||||
<meta property="twitter:url" content="https://blog.dich.bid/about-shortcut-key/">
|
||||
|
||||
<link rel="alternate" type="application/atom+xml" title="Dich'blog Atom Feed" href="https://blog.dich.bid/atom.xml" />
|
||||
|
||||
|
||||
<link rel="icon" type="image/png" href=/dich.webp />
|
||||
|
||||
<!-- ✅ Added center alignment styles -->
|
||||
<style>
|
||||
.footer {
|
||||
text-align: center;
|
||||
padding: 1rem 0;
|
||||
}
|
||||
|
||||
.footer__inner {
|
||||
display: flex;
|
||||
justify-content: center;
|
||||
flex-direction: column;
|
||||
align-items: center;
|
||||
}
|
||||
|
||||
.copyright {
|
||||
text-align: center;
|
||||
}
|
||||
</style>
|
||||
</head>
|
||||
|
||||
<body class="">
|
||||
<div class="container">
|
||||
|
||||
<header class="header">
|
||||
<div class="header__inner">
|
||||
<div class="header__logo">
|
||||
|
||||
<a href="https://blog.dich.bid" style="text-decoration: none;">
|
||||
<div class="logo">
|
||||
|
||||
Dich'blog
|
||||
|
||||
</div>
|
||||
</a>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
|
||||
<nav class="menu">
|
||||
<ul class="menu__inner">
|
||||
<li><a href="https://blog.dich.bid">blog</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/archive">archive</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/tags">tags</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/weekly">weekly</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/search">search</a></li>
|
||||
|
||||
<li class="active"><a href="https://blog.dich.bid/about">about me</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/links">links</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/atom.xml">rss</a></li>
|
||||
|
||||
<li><a href="https://github.com/Dichgrem" target="_blank" rel="noopener noreferrer">github</a></li>
|
||||
</ul>
|
||||
</nav>
|
||||
|
||||
|
||||
|
||||
</header>
|
||||
|
||||
|
||||
<div class="content">
|
||||
|
||||
<div class="post">
|
||||
|
||||
<h1 class="post-title"><a href="https://blog.dich.bid/about-shortcut-key/">乱七八糟:常用实用快捷键</a></h1>
|
||||
<div class="post-meta-inline">
|
||||
|
||||
<span class="post-date">
|
||||
2024-05-23
|
||||
</span>
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
<span class="post-tags-inline">
|
||||
:: tags:
|
||||
<a class="post-tag" href="https://blog.dich.bid/tags/luan-qi-ba-zao/">#乱七八糟</a></span>
|
||||
|
||||
|
||||
<div class="post-content">
|
||||
<p>前言 在日常使用浏览器时，掌握一些快捷键和技巧可以节省大量时间，提高工作和学习效率。通过学习和实践，能够更加轻松地应对各种网页浏览场景，让浏览器成为工作和学习的得力助手。</p>
|
||||
<span id="continue-reading"></span><h2 id="liu-lan-qi-kuai-jie-jian">浏览器快捷键</h2>
|
||||
<h3 id="chang-yong">常用</h3>
|
||||
<table><thead><tr><th>快捷键</th><th>描述</th></tr></thead><tbody>
|
||||
<tr><td>Ctrl + A</td><td>全选</td></tr>
|
||||
<tr><td>Ctrl + C</td><td>复制</td></tr>
|
||||
<tr><td>Ctrl + X</td><td>剪切</td></tr>
|
||||
<tr><td>Ctrl + V</td><td>粘贴</td></tr>
|
||||
<tr><td>Ctrl + F</td><td>查找</td></tr>
|
||||
<tr><td>Ctrl + Q</td><td>退出</td></tr>
|
||||
<tr><td>Ctrl + T</td><td>新建标签页</td></tr>
|
||||
<tr><td>Ctrl + W</td><td>关闭标签页</td></tr>
|
||||
<tr><td>Ctrl + N</td><td>新建窗口</td></tr>
|
||||
<tr><td>Ctrl + Shift + P</td><td>新建隐私浏览窗口</td></tr>
|
||||
</tbody></table>
|
||||
<h3 id="li-shi">历史</h3>
|
||||
<table><thead><tr><th>快捷键</th><th>描述</th></tr></thead><tbody>
|
||||
<tr><td>Ctrl + H</td><td>历史侧栏</td></tr>
|
||||
<tr><td>Ctrl + Shift + H</td><td>我的足迹窗口（历史）</td></tr>
|
||||
<tr><td>Ctrl + Shift + Del</td><td>清除最近历史记录</td></tr>
|
||||
</tbody></table>
|
||||
<h3 id="shu-qian">书签</h3>
|
||||
<table><thead><tr><th>快捷键</th><th>描述</th></tr></thead><tbody>
|
||||
<tr><td>Ctrl + D</td><td>将此页加为书签</td></tr>
|
||||
<tr><td>Ctrl + I</td><td>页面信息</td></tr>
|
||||
<tr><td>Ctrl + Shift + O</td><td>显示全部书签（我的足迹窗口）</td></tr>
|
||||
<tr><td>Ctrl + B / Ctrl + Shift + B</td><td>书签侧栏 / 顶栏</td></tr>
|
||||
</tbody></table>
|
||||
<h3 id="xia-zai-yu-cha-jian">下载与插件</h3>
|
||||
<table><thead><tr><th>快捷键</th><th>描述</th></tr></thead><tbody>
|
||||
<tr><td>Ctrl + Shift + Y</td><td>下载</td></tr>
|
||||
<tr><td>Ctrl + Shift + A</td><td>附加组件 / 插件</td></tr>
|
||||
</tbody></table>
|
||||
<h3 id="kong-zhi-tai-yu-kai-fa">控制台与开发</h3>
|
||||
<table><thead><tr><th>快捷键</th><th>描述</th></tr></thead><tbody>
|
||||
<tr><td>Ctrl + Shift + K</td><td>Web 控制台</td></tr>
|
||||
<tr><td>Ctrl + Shift + C</td><td>查看器</td></tr>
|
||||
<tr><td>Shift + F7</td><td>样式编辑器</td></tr>
|
||||
<tr><td>Shift + F5</td><td>分析器</td></tr>
|
||||
<tr><td>Ctrl + Shift + E</td><td>网络</td></tr>
|
||||
<tr><td>Ctrl + U</td><td>页面源码</td></tr>
|
||||
<tr><td>Ctrl + Shift + J</td><td>浏览器控制台</td></tr>
|
||||
</tbody></table>
|
||||
<h3 id="biao-qian-ye-yu-jie-mian">标签页与界面</h3>
|
||||
<table><thead><tr><th>快捷键</th><th>描述</th></tr></thead><tbody>
|
||||
<tr><td>Ctrl + S</td><td>界面保存</td></tr>
|
||||
<tr><td>Ctrl + +</td><td>放大</td></tr>
|
||||
<tr><td>Ctrl + -</td><td>缩小</td></tr>
|
||||
<tr><td>Ctrl + 0</td><td>重置缩放</td></tr>
|
||||
<tr><td>Ctrl + K / J</td><td>搜索</td></tr>
|
||||
<tr><td>Ctrl + Home / End</td><td>到文件头 / 尾</td></tr>
|
||||
<tr><td>Ctrl + Page Up</td><td>切换到左边标签页</td></tr>
|
||||
<tr><td>Ctrl + Page Down</td><td>切换到右边标签页</td></tr>
|
||||
<tr><td>Ctrl + Shift + Page Up</td><td>当前标签页左移</td></tr>
|
||||
<tr><td>Ctrl + Shift + Page Down</td><td>当前标签页右移</td></tr>
|
||||
</tbody></table>
|
||||
<h3 id="qi-ta-cao-zuo">其他操作</h3>
|
||||
<table><thead><tr><th>快捷键</th><th>描述</th></tr></thead><tbody>
|
||||
<tr><td>Alt + Space</td><td>KDE 搜索栏</td></tr>
|
||||
<tr><td>Alt + → / ←</td><td>前进 / 后退</td></tr>
|
||||
<tr><td>Alt + 数字键</td><td>选择标签页（1–8）</td></tr>
|
||||
<tr><td>Alt + M</td><td>静音</td></tr>
|
||||
<tr><td>End</td><td>到达页尾</td></tr>
|
||||
<tr><td>Home</td><td>到达页首</td></tr>
|
||||
<tr><td>F6</td><td>地址栏</td></tr>
|
||||
</tbody></table>
|
||||
<h2 id="vs-code-kuai-jie-jian">VS Code 快捷键</h2>
|
||||
<h3 id="jie-mian-gai-lan">界面概览</h3>
|
||||
<table><thead><tr><th>快捷键</th><th>描述</th></tr></thead><tbody>
|
||||
<tr><td><code>cmd + shift + e</code></td><td>文件资源管理器</td></tr>
|
||||
<tr><td><code>cmd + shift + f</code></td><td>跨文件搜索</td></tr>
|
||||
<tr><td><code>ctrl + shift + g</code></td><td>源代码管理</td></tr>
|
||||
<tr><td><code>cmd + shift + d</code></td><td>启动和调试</td></tr>
|
||||
<tr><td><code>cmd + shift + x</code></td><td>扩展管理</td></tr>
|
||||
<tr><td><code>cmd + shift + p</code></td><td>查找并运行所有命令</td></tr>
|
||||
<tr><td><code>cmd + j</code></td><td>打开、关闭面板</td></tr>
|
||||
</tbody></table>
|
||||
<h3 id="ming-ling-xing-de-shi-yong">命令行的使用</h3>
|
||||
<table><thead><tr><th>命令</th><th>描述</th></tr></thead><tbody>
|
||||
<tr><td><code>code $path</code></td><td>新窗口中打开文件或文件夹</td></tr>
|
||||
<tr><td><code>code -r $path</code></td><td>窗口复用打开文件</td></tr>
|
||||
<tr><td><code>code -r -g $file:lineno</code></td><td>打开文件并跳转到指定行</td></tr>
|
||||
<tr><td><code>code -r -d $file1 $file2</code></td><td>比较两个文件</td></tr>
|
||||
<tr><td><code>ls code -</code></td><td>查看可用命令</td></tr>
|
||||
</tbody></table>
|
||||
<h3 id="guang-biao-yi-dong">光标移动</h3>
|
||||
<table><thead><tr><th>快捷键</th><th>描述</th></tr></thead><tbody>
|
||||
<tr><td><code>option + 左/右方向键</code></td><td>按单词移动光标</td></tr>
|
||||
<tr><td><code>cmd + 左/右方向键</code></td><td>移动到行首/行尾</td></tr>
|
||||
<tr><td><code>cmd + shift + \</code></td><td>在花括号之间跳转</td></tr>
|
||||
<tr><td><code>cmd + 上/下方向键</code></td><td>移动到文档首/尾</td></tr>
|
||||
</tbody></table>
|
||||
<h3 id="wen-ben-xuan-ze">文本选择</h3>
|
||||
<ul>
|
||||
<li>使用 <code>shift + 光标移动</code> 进行文本选择。</li>
|
||||
</ul>
|
||||
<h3 id="shan-chu-cao-zuo">删除操作</h3>
|
||||
<table><thead><tr><th>快捷键</th><th>描述</th></tr></thead><tbody>
|
||||
<tr><td><code>cmd + fn + del</code></td><td>删除到行尾</td></tr>
|
||||
<tr><td><code>cmd + del</code></td><td>删除到行首</td></tr>
|
||||
<tr><td><code>option + del</code></td><td>向前删除单词</td></tr>
|
||||
<tr><td><code>option + fn + del</code></td><td>向后删除单词</td></tr>
|
||||
</tbody></table>
|
||||
<h3 id="dai-ma-xing-bian-ji">代码行编辑</h3>
|
||||
<table><thead><tr><th>快捷键</th><th>描述</th></tr></thead><tbody>
|
||||
<tr><td><code>cmd + shift + k</code></td><td>删除行</td></tr>
|
||||
<tr><td><code>cmd + x</code></td><td>剪切行</td></tr>
|
||||
<tr><td><code>cmd + enter</code></td><td>在当前行下方插入新行</td></tr>
|
||||
<tr><td><code>cmd + shift + enter</code></td><td>在当前行上方插入新行</td></tr>
|
||||
<tr><td><code>option + 上/下方向键</code></td><td>移动当前行</td></tr>
|
||||
<tr><td><code>option + shift + 上/下方向键</code></td><td>复制当前行</td></tr>
|
||||
<tr><td><code>cmd + /</code></td><td>注释/取消注释当前行</td></tr>
|
||||
<tr><td><code>option + shift + a</code></td><td>注释/取消注释代码块</td></tr>
|
||||
<tr><td><code>option + shift + f</code></td><td>格式化代码</td></tr>
|
||||
<tr><td><code>cmd + k cmd + f</code></td><td>格式化选中代码</td></tr>
|
||||
<tr><td><code>ctrl + t</code></td><td>调换光标前后字符</td></tr>
|
||||
<tr><td><code>cmd + shift + p</code> + <code>transform to up/low case</code></td><td>转换大小写</td></tr>
|
||||
<tr><td><code>ctrl + j</code></td><td>合并代码行</td></tr>
|
||||
<tr><td><code>cmd + u</code></td><td>撤销光标移动</td></tr>
|
||||
</tbody></table>
|
||||
<h3 id="chuang-jian-duo-ge-guang-biao">创建多个光标</h3>
|
||||
<ul>
|
||||
<li>使用鼠标：<code>option + 鼠标左键</code></li>
|
||||
<li>使用键盘：</li>
|
||||
</ul>
|
||||
<table><thead><tr><th>快捷键</th><th>描述</th></tr></thead><tbody>
|
||||
<tr><td><code>cmd + option + 上/下方向键</code></td><td>创建多个光标</td></tr>
|
||||
<tr><td><code>cmd + d</code></td><td>选中相同单词并创建多个光标</td></tr>
|
||||
<tr><td><code>option + shift + i</code></td><td>在选中的多行后创建光标</td></tr>
|
||||
</tbody></table>
|
||||
<h3 id="wen-jian-tiao-zhuan">文件跳转</h3>
|
||||
<table><thead><tr><th>快捷键</th><th>描述</th></tr></thead><tbody>
|
||||
<tr><td><code>ctrl + tab</code></td><td>文件标签之间跳转</td></tr>
|
||||
<tr><td><code>cmd + p</code></td><td>打开文件列表</td></tr>
|
||||
</tbody></table>
|
||||
<h3 id="xing-tiao-zhuan">行跳转</h3>
|
||||
<table><thead><tr><th>快捷键</th><th>描述</th></tr></thead><tbody>
|
||||
<tr><td><code>ctrl + g</code></td><td>跳转到指定行</td></tr>
|
||||
</tbody></table>
|
||||
<h3 id="fu-hao-tiao-zhuan">符号跳转</h3>
|
||||
<table><thead><tr><th>快捷键</th><th>描述</th></tr></thead><tbody>
|
||||
<tr><td><code>cmd + shift + o</code></td><td>当前文件所有符号列表</td></tr>
|
||||
<tr><td><code>@:</code></td><td>符号分类排列</td></tr>
|
||||
<tr><td><code>cmd + t</code></td><td>在多个文件中进行符号跳转</td></tr>
|
||||
<tr><td><code>cmd + F12</code></td><td>跳转到函数的实现位置</td></tr>
|
||||
<tr><td><code>shift + F12</code></td><td>查看函数引用列表</td></tr>
|
||||
<tr><td><code>ctrl + -</code></td><td>跳回上一次光标所在位置</td></tr>
|
||||
<tr><td><code>ctrl + shift + -</code></td><td>跳回下一次光标所在位置</td></tr>
|
||||
</tbody></table>
|
||||
<h3 id="dai-ma-zi-dong-bu-quan">代码自动补全</h3>
|
||||
<table><thead><tr><th>快捷键</th><th>描述</th></tr></thead><tbody>
|
||||
<tr><td><code>ctrl + space</code></td><td>调出建议列表</td></tr>
|
||||
<tr><td><code>cmd + shift + space</code></td><td>调出参数预览窗口</td></tr>
|
||||
<tr><td><code>cmd + .</code></td><td>快速修复建议列表</td></tr>
|
||||
<tr><td><code>F2</code></td><td>函数名重构</td></tr>
|
||||
</tbody></table>
|
||||
<h3 id="dai-ma-zhe-die">代码折叠</h3>
|
||||
<table><thead><tr><th>快捷键</th><th>描述</th></tr></thead><tbody>
|
||||
<tr><td><code>cmd + option + [</code></td><td>最内层折叠</td></tr>
|
||||
<tr><td><code>cmd + option + ]</code></td><td>最内层展开</td></tr>
|
||||
<tr><td><code>cmd + k cmd + 0</code></td><td>全部折叠</td></tr>
|
||||
<tr><td><code>cmd + k cmd + j</code></td><td>全部展开</td></tr>
|
||||
</tbody></table>
|
||||
<h3 id="sou-suo">搜索</h3>
|
||||
<table><thead><tr><th>快捷键</th><th>描述</th></tr></thead><tbody>
|
||||
<tr><td><code>cmd + f</code></td><td>搜索</td></tr>
|
||||
<tr><td><code>cmd + g</code></td><td>搜索并跳转</td></tr>
|
||||
<tr><td><code>cmd + option + f</code></td><td>查找替换</td></tr>
|
||||
<tr><td><code>cmd + shift + f</code></td><td>多文件搜索</td></tr>
|
||||
</tbody></table>
|
||||
<h3 id="bian-ji-qi-cao-zuo">编辑器操作</h3>
|
||||
<table><thead><tr><th>快捷键</th><th>描述</th></tr></thead><tbody>
|
||||
<tr><td><code>cmd + \</code></td><td>拆分编辑器</td></tr>
|
||||
<tr><td><code>option + cmd + 左/右方向键</code></td><td>编辑器间切换</td></tr>
|
||||
<tr><td><code>cmd + 数字键</code></td><td>在拆分的编辑器窗口跳转</td></tr>
|
||||
<tr><td><code>cmd + /</code></td><td>缩放整个工作区</td></tr>
|
||||
<tr><td><code>cmd + shift + p</code> + <code>reset zoom</code></td><td>重置缩放</td></tr>
|
||||
</tbody></table>
|
||||
<h3 id="zhuan-zhu-mo-shi">专注模式</h3>
|
||||
<table><thead><tr><th>快捷键</th><th>描述</th></tr></thead><tbody>
|
||||
<tr><td><code>cmd + b</code></td><td>打开或关闭侧边栏</td></tr>
|
||||
<tr><td><code>cmd + j</code></td><td>打开或关闭面板</td></tr>
|
||||
<tr><td><code>cmd + shift + p</code> + <code>Toggle Zen Mode</code></td><td>切换禅模式</td></tr>
|
||||
<tr><td><code>cmd + shift + p</code> + <code>Toggle Centered Layout</code></td><td>切换居中布局</td></tr>
|
||||
</tbody></table>
|
||||
<h3 id="ming-ling-mian-ban">命令面板</h3>
|
||||
<table><thead><tr><th>快捷键</th><th>描述</th></tr></thead><tbody>
|
||||
<tr><td><code>cmd + shift + p</code></td><td>打开命令面板</td></tr>
|
||||
</tbody></table>
|
||||
<p>命令面板的前缀符号功能：</p>
|
||||
<ul>
|
||||
<li><code>?</code>：列出所有可用功能</li>
|
||||
<li><code>></code>：显示所有命令</li>
|
||||
<li><code>@</code>：显示并跳转文件中的符号</li>
|
||||
<li><code>@:</code>：按类别归类符号</li>
|
||||
<li><code>#</code>：显示并跳转工作区中的符号</li>
|
||||
<li><code>:</code>：跳转到当前文件中的某一行</li>
|
||||
<li><code>edt</code>：显示所有已打开的文件</li>
|
||||
<li><code>edt active</code>：显示当前活动组中的文件</li>
|
||||
<li><code>ext</code>：插件管理</li>
|
||||
<li><code>ext install</code>：搜索和安装插件</li>
|
||||
<li><code>task</code>：任务管理</li>
|
||||
<li><code>debug</code>：调试功能</li>
|
||||
<li><code>term</code>：创建和管理终端实例</li>
|
||||
<li><code>view</code>：打开各个 UI 组件</li>
|
||||
</ul>
|
||||
<h3 id="chuang-kou-guan-li">窗口管理</h3>
|
||||
<table><thead><tr><th>快捷键</th><th>描述</th></tr></thead><tbody>
|
||||
<tr><td><code>ctrl + w</code></td><td>关闭当前窗口</td></tr>
|
||||
<tr><td><code>ctrl + r</code></td><td>切换文件夹</td></tr>
|
||||
<tr><td><code>ctrl + r</code> + <code>cmd + enter</code></td><td>新建窗口打开文件夹</td></tr>
|
||||
</tbody></table>
|
||||
<h3 id="ji-cheng-zhong-duan">集成终端</h3>
|
||||
<table><thead><tr><th>快捷键</th><th>描述</th></tr></thead><tbody>
|
||||
<tr><td>`ctrl + ``</td><td>切换集成终端</td></tr>
|
||||
<tr><td>`ctrl + shift + ``</td><td>新建集成终端</td></tr>
|
||||
<tr><td><code>cmd + shift + p</code> + <code>Run Active File In Active Terminal</code></td><td>在终端中运行当前文件</td></tr>
|
||||
<tr><td><code>cmd + shift + p</code> + <code>Run Selected Text In Active Terminal</code></td><td>在终端中运行选中文本</td></tr>
|
||||
</tbody></table>
|
||||
<h3 id="ren-wu-guan-li">任务管理</h3>
|
||||
<table><thead><tr><th>快捷键</th><th>描述</th></tr></thead><tbody>
|
||||
<tr><td><code>cmd + shift + p</code> + <code>run task</code></td><td>自动检测可运行的任务</td></tr>
|
||||
<tr><td><code>cmd + shift + p</code> + <code>Configure Task</code></td><td>配置任务</td></tr>
|
||||
<tr><td><code>cmd + shift + b</code></td><td>运行默认的生成任务</td></tr>
|
||||
</tbody></table>
|
||||
<h3 id="shu-biao-cao-zuo">鼠标操作</h3>
|
||||
<ul>
|
||||
<li>
|
||||
<p><strong>文本选择</strong>：</p>
|
||||
<ul>
|
||||
<li>双击：选中单词</li>
|
||||
<li>三击：选中一行</li>
|
||||
<li>四击：选中整个文档</li>
|
||||
<li>单击行号：选中整行</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><strong>文本编辑</strong>：</p>
|
||||
<ul>
|
||||
<li>拖动选中文本：移动文本</li>
|
||||
<li>拖动时按住 <code>option</code>：复制文本</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><strong>函数提示</strong>：</p>
|
||||
<ul>
|
||||
<li>在悬停窗口上按下 <code>cmd</code>：提示函数的实现</li>
|
||||
</ul>
|
||||
</li>
|
||||
</ul>
|
||||
<hr />
|
||||
<p><strong>Done.</strong></p>
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
<div class="pagination">
|
||||
<div class="pagination__title">
|
||||
<span class="pagination__title-h">Thanks for reading! Read other posts?</span>
|
||||
<hr />
|
||||
</div>
|
||||
<div class="pagination__buttons">
|
||||
<span class="button previous">
|
||||
<a href="https://blog.dich.bid/about-podcast-use/">
|
||||
<span class="button__icon">←</span>
|
||||
<span class="button__text">搭建个人信息流:播客收听指北</span>
|
||||
</a>
|
||||
</span>
|
||||
|
||||
|
||||
<span class="button next">
|
||||
<a href="https://blog.dich.bid/windows-some-setting/">
|
||||
<span class="button__text">乱七八糟:Windows常用操作</span>
|
||||
<span class="button__icon">→</span>
|
||||
</a>
|
||||
</span>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
</div>
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
<footer class="footer">
|
||||
<div class="footer__inner">
|
||||
<div class="copyright">
|
||||
<span>©
|
||||
2025
|
||||
Dichgrem</span>
|
||||
<span class="copyright-theme">
|
||||
<span class="copyright-theme-sep"> :: CC BY-SA 4.0 :: A friend comes from distant lands</span>
|
||||
</a>
|
||||
</span>
|
||||
</div>
|
||||
</div>
|
||||
</footer>
|
||||
|
||||
</div>
|
||||
</body>
|
||||
</html>
|
||||
|
||||
262
public/about-ventoy/index.html
Normal file
262
public/about-ventoy/index.html
Normal file
@ -0,0 +1,262 @@
|
||||
<!DOCTYPE html>
|
||||
<html lang="en">
|
||||
|
||||
<head>
|
||||
<title>Dich'blog</title>
|
||||
|
||||
<meta http-equiv="content-type" content="text/html; charset=utf-8">
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1">
|
||||
<meta name="robots" content="noodp"/>
|
||||
|
||||
<link rel="stylesheet" href="https://blog.dich.bid/style.css">
|
||||
<link rel="stylesheet" href="https://blog.dich.bid/color/blue.css">
|
||||
|
||||
<link rel="stylesheet" href="https://blog.dich.bid/color/background_dark.css">
|
||||
|
||||
<link rel="stylesheet" href="https://blog.dich.bid/font-hack-subset.css">
|
||||
|
||||
<meta name="description" content="">
|
||||
|
||||
<meta property="og:description" content="">
|
||||
<meta property="og:title" content="Dich'blog">
|
||||
<meta property="og:type" content="article">
|
||||
<meta property="og:url" content="https://blog.dich.bid/about-ventoy/">
|
||||
|
||||
<meta name="twitter:card" content="summary_large_image">
|
||||
<meta name="twitter:description" content="">
|
||||
<meta name="twitter:title" content="Dich'blog">
|
||||
<meta property="twitter:domain" content="blog.dich.bid">
|
||||
<meta property="twitter:url" content="https://blog.dich.bid/about-ventoy/">
|
||||
|
||||
<link rel="alternate" type="application/atom+xml" title="Dich'blog Atom Feed" href="https://blog.dich.bid/atom.xml" />
|
||||
|
||||
|
||||
<link rel="icon" type="image/png" href=/dich.webp />
|
||||
|
||||
<!-- ✅ Added center alignment styles -->
|
||||
<style>
|
||||
.footer {
|
||||
text-align: center;
|
||||
padding: 1rem 0;
|
||||
}
|
||||
|
||||
.footer__inner {
|
||||
display: flex;
|
||||
justify-content: center;
|
||||
flex-direction: column;
|
||||
align-items: center;
|
||||
}
|
||||
|
||||
.copyright {
|
||||
text-align: center;
|
||||
}
|
||||
</style>
|
||||
</head>
|
||||
|
||||
<body class="">
|
||||
<div class="container">
|
||||
|
||||
<header class="header">
|
||||
<div class="header__inner">
|
||||
<div class="header__logo">
|
||||
|
||||
<a href="https://blog.dich.bid" style="text-decoration: none;">
|
||||
<div class="logo">
|
||||
|
||||
Dich'blog
|
||||
|
||||
</div>
|
||||
</a>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
|
||||
<nav class="menu">
|
||||
<ul class="menu__inner">
|
||||
<li><a href="https://blog.dich.bid">blog</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/archive">archive</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/tags">tags</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/weekly">weekly</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/search">search</a></li>
|
||||
|
||||
<li class="active"><a href="https://blog.dich.bid/about">about me</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/links">links</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/atom.xml">rss</a></li>
|
||||
|
||||
<li><a href="https://github.com/Dichgrem" target="_blank" rel="noopener noreferrer">github</a></li>
|
||||
</ul>
|
||||
</nav>
|
||||
|
||||
|
||||
|
||||
</header>
|
||||
|
||||
|
||||
<div class="content">
|
||||
|
||||
<div class="post">
|
||||
|
||||
<h1 class="post-title"><a href="https://blog.dich.bid/about-ventoy/">乱七八糟:Ventoy战斗盘部署</a></h1>
|
||||
<div class="post-meta-inline">
|
||||
|
||||
<span class="post-date">
|
||||
2025-02-14
|
||||
</span>
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
<span class="post-tags-inline">
|
||||
:: tags:
|
||||
<a class="post-tag" href="https://blog.dich.bid/tags/luan-qi-ba-zao/">#乱七八糟</a></span>
|
||||
|
||||
|
||||
<div class="post-content">
|
||||
<p>前言 Ventoy 是一款开源免费的多系统启动盘制作工具，这里说明其主要功能的制作流程。</p>
|
||||
<span id="continue-reading"></span><h3 id="jie-shao">介绍</h3>
|
||||
<p>Ventoy 是一款开源免费的多系统启动盘制作工具，旨在简化操作系统的安装过程。与传统的启动盘制作方法不同，Ventoy 允许用户将多个操作系统的镜像文件<code>如 ISO、WIM、IMG、VHD(x)、EFI 等</code>直接复制到 U 盘，无需反复格式化或使用专门的工具写入镜像。</p>
|
||||
<p><img src="https://www.ventoy.net/static/img/screen/screen_uefi_cn.png?v=4" alt="ventoy" /></p>
|
||||
<h2 id="mu-biao">目标</h2>
|
||||
<blockquote>
|
||||
<p>PE启动盘 / ISO系统安装盘 / Win-to-go / Linux-to-go / 文件存储 五功能合一</p>
|
||||
</blockquote>
|
||||
<h2 id="zhi-zuo-liu-cheng">制作流程</h2>
|
||||
<ul>
|
||||
<li>首先<code>在官网下载</code><a href="https://www.ventoy.net/cn/download.html">Ventoy</a></li>
|
||||
<li>随后在<code>language</code>中改为中文显示，可以看到左上角有<code>配置选项</code></li>
|
||||
<li>将分区类型设置为<code>GPT</code>，开启安全启动支持；</li>
|
||||
<li>将<code>分区格式</code>设置为NTFS；</li>
|
||||
<li>随后在<code>分区设置</code>中进行分区，选择在<code>磁盘后保留一段空间</code>，这里的空间将不被分区，即为空闲空间，可以当作普通的文件存储盘；</li>
|
||||
<li>Ventoy分区则会使用<code>U盘总容量-保留空间-ventoy保留分区</code>的空间新建一个盘，这里可以放<code>ISO、WIM、IMG、VHD(x)、EFI</code>等等</li>
|
||||
<li>随后<code>选择磁盘</code>并开始安装；</li>
|
||||
<li>制作完成后即可使用 <code>BIOS Legacy</code>模式 或 <code>UEFI</code> 模式启动。</li>
|
||||
</ul>
|
||||
<h2 id="wen-jian-cun-chu-pan">文件存储盘</h2>
|
||||
<p>使用<code>DiskGenius</code>或其他磁盘工具，可以看到刚刚制作的磁盘有两个分区：ventoy保留分区(有文件)和Ventoy分区(无文件)以及一个空闲空间。</p>
|
||||
<p>将空闲空间<code>格式化并新建磁盘</code>，随后会出现一个新的可用盘，<code>可以用这个盘进行存储</code>。</p>
|
||||
<h2 id="peqi-dong-pan-zhi-zuo">PE启动盘制作</h2>
|
||||
<p>将PE的ISO文件放入Ventoy分区即可。常用PE:</p>
|
||||
<ul>
|
||||
<li><a href="https://www.wepe.com.cn/download.html">微PE</a></li>
|
||||
<li><a href="https://github.com/VirtualHotBar/HotPEToolBox">HotPE</a></li>
|
||||
</ul>
|
||||
<h2 id="isoxi-tong-an-zhuang-pan">ISO系统安装盘</h2>
|
||||
<p>将要安装的系统的ISO镜像放入Ventoy分区即可。常用系统:</p>
|
||||
<ul>
|
||||
<li><a href="https://ubuntu.com/download">Ubuntu</a></li>
|
||||
<li><a href="https://cdimage.debian.org/debian-cd/">Debian-DVD</a></li>
|
||||
<li><a href="https://massgrave.dev/genuine-installation-media">Windows</a></li>
|
||||
</ul>
|
||||
<h2 id="win-to-go">Win-to-go</h2>
|
||||
<p>Ventoy 使用名为ventoy_vhdboot插件来支持直接启动 VHD(x) 文件(Win7以上).支持 Legacy BIOS 和 UEFI 模式。<code>支持固定大小以及动态扩展类型</code>的 VHD/VHDX 格式。</p>
|
||||
<p>从下面任意一个链接中下载<code>ventoy_vhdboot.img</code>文件即可（几个链接中的文件都是一样的）。</p>
|
||||
<ul>
|
||||
<li><a href="https://github.com/ventoy/vhdiso/releases">Github</a></li>
|
||||
<li><a href="https://ventoy.lanzoub.com/b01dlxuaj">蓝奏云/密码7my4</a></li>
|
||||
</ul>
|
||||
<p>把下载后的文件放在U盘第1个分区（就是放ISO文件的分区）的 ventoy 目录下（默认没有这个目录，<code>需手动创建，注意大小写</code>），即 /ventoy/ventoy_vhdboot.img 就可以了。</p>
|
||||
<p>随后将vhd或vhdx后缀的Windows虚拟机镜像放入其中即可出现在启动栏。</p>
|
||||
<blockquote>
|
||||
<p>可以使用<a href="https://www.virtualbox.org/">Virtualbox</a>创建Windows虚拟机并将镜像复制到ventoy中。</p>
|
||||
</blockquote>
|
||||
<h2 id="linux-to-go">Linux-to-go</h2>
|
||||
<p>Ventoy 使用<code>plugin_vtoyboot</code>插件来支持在物理机上直接启动安装了 Linux系统的 vdisk 文件 （vhd/vdi/raw 等）。这种模式的优点有：</p>
|
||||
<ul>
|
||||
<li>系统是在真实物理机上运行，并不是在虚拟机里运行，<code>没有性能损失</code>。</li>
|
||||
<li>同一个 vhd/vdi 文件<code>既可以在 Legacy BIOS 模式下启动，也可以在 UEFI 模式</code>下启动。</li>
|
||||
<li>Linux系统<code>无需独占一个磁盘或者分区</code>，相当于把一个完整的Linux系统放在一个文件里。 比如，你的主系统是 C 盘里的 Windows 系统，你可以在D盘里放一些</li>
|
||||
<li>Deepin、UOS、Ubuntu、Arch 等系统的 VHD 文件，想启动哪个选哪个，不用了就把对应的 VHD 文件删除即可。</li>
|
||||
</ul>
|
||||
<p>支持的 vdisk 格式:</p>
|
||||
<ul>
|
||||
<li><code>固定大小的 vhd</code> （注意只能是vhd, 不支持vhdx）</li>
|
||||
<li><code>固定大小的 vdi</code></li>
|
||||
<li><code>Raw Disk 镜像</code>格式</li>
|
||||
</ul>
|
||||
<h3 id="an-zhuang-linux-xi-tong-dao-vdisk">安装 Linux 系统到 vdisk</h3>
|
||||
<p>VirtualBox中创建固定大小的 vhd/vdi，注意<code>只支持静态大小的，不支持动态扩展类型的</code>。然后把支持的 Linux 系统安装到 vhd/vdi 中即可。</p>
|
||||
<p>注意：</p>
|
||||
<ul>
|
||||
<li><code>虚拟硬盘必须是全新创建的</code>，不能使用之前用过的。</li>
|
||||
<li>新版本的 VirtualBox 在创建虚拟机时不要选择操作系统ISO文件，等创建完虚拟机之后再添加ISO文件进行安装。</li>
|
||||
<li>安装系统时，VirtualBox <code>必须设置为 UEFI 模式</code>！</li>
|
||||
<li>注意，系统安装完之后<code>不能对虚拟机创建快照</code>，否则会导致 vdi/vhd 无法识别。</li>
|
||||
</ul>
|
||||
<p>有一些系统安装完之后还需要再额外安装一个 grub 的包才可以，否则最终的 vhd/vdi 文件只能在 UEFI 模式下启动，无法在 Legacy BIOS 模式下启动。对于这种，在前面表格最后的 "备注" 一栏有说明，没有特殊说明的就不需要。详见<a href="https://www.ventoy.net/cn/plugin_vtoyboot.html">Linux vDisk 文件启动插件</a></p>
|
||||
<h3 id="zai-xi-tong-xia-zhi-xing-vtoyboot-jiao-ben">在系统下执行 vtoyboot 脚本</h3>
|
||||
<ul>
|
||||
<li>
|
||||
<p>安装完成并启动到 Linux 系统中之后，执行 vtoyboot 脚本。这一步是为了在系统中做一些处理，以支持Ventoy启动。</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>vtoyboot 是配套 Ventoy 开发的一个项目，单独发布。从 https://github.com/ventoy/vtoyboot/releases 下载压缩包即可。</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>下载到 Linux 系统中，解压，然后以root权限执行里面的脚本 sudo bash vtoyboot.sh 脚本执行完之后，使用 poweroff 命令关机。</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>注意 vtoyboot 会经常更新以支持更多的 Linux 版本以及修复 BUG，所以请使用最新版本。</p>
|
||||
</li>
|
||||
</ul>
|
||||
<blockquote>
|
||||
<p>如果是对内核、驱动进行了升级、或者类似于通过 dnf update 命令进行了系统的大升级之后， 建议再重新执行一次 vtoyboot 脚本，防止下次重启之后vDisk文件无法启动。</p>
|
||||
</blockquote>
|
||||
<p>随后拷贝到U盘，改后缀名为 .vtoy 然后用 Ventoy 启动即可。</p>
|
||||
<hr />
|
||||
<p><strong>Done.</strong></p>
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
<div class="pagination">
|
||||
<div class="pagination__title">
|
||||
<span class="pagination__title-h">Thanks for reading! Read other posts?</span>
|
||||
<hr />
|
||||
</div>
|
||||
<div class="pagination__buttons">
|
||||
<span class="button previous">
|
||||
<a href="https://blog.dich.bid/network-zuwang/">
|
||||
<span class="button__icon">←</span>
|
||||
<span class="button__text">Network的艺术:家庭组网方案与设备选购</span>
|
||||
</a>
|
||||
</span>
|
||||
|
||||
|
||||
<span class="button next">
|
||||
<a href="https://blog.dich.bid/about-frp/">
|
||||
<span class="button__text">乱七八糟:FRP使用指南</span>
|
||||
<span class="button__icon">→</span>
|
||||
</a>
|
||||
</span>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
</div>
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
<footer class="footer">
|
||||
<div class="footer__inner">
|
||||
<div class="copyright">
|
||||
<span>©
|
||||
2025
|
||||
Dichgrem</span>
|
||||
<span class="copyright-theme">
|
||||
<span class="copyright-theme-sep"> :: CC BY-SA 4.0 :: A friend comes from distant lands</span>
|
||||
</a>
|
||||
</span>
|
||||
</div>
|
||||
</div>
|
||||
</footer>
|
||||
|
||||
</div>
|
||||
</body>
|
||||
</html>
|
||||
|
||||
323
public/about-vim/index.html
Normal file
323
public/about-vim/index.html
Normal file
@ -0,0 +1,323 @@
|
||||
<!DOCTYPE html>
|
||||
<html lang="en">
|
||||
|
||||
<head>
|
||||
<title>Dich'blog</title>
|
||||
|
||||
<meta http-equiv="content-type" content="text/html; charset=utf-8">
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1">
|
||||
<meta name="robots" content="noodp"/>
|
||||
|
||||
<link rel="stylesheet" href="https://blog.dich.bid/style.css">
|
||||
<link rel="stylesheet" href="https://blog.dich.bid/color/blue.css">
|
||||
|
||||
<link rel="stylesheet" href="https://blog.dich.bid/color/background_dark.css">
|
||||
|
||||
<link rel="stylesheet" href="https://blog.dich.bid/font-hack-subset.css">
|
||||
|
||||
<meta name="description" content="">
|
||||
|
||||
<meta property="og:description" content="">
|
||||
<meta property="og:title" content="Dich'blog">
|
||||
<meta property="og:type" content="article">
|
||||
<meta property="og:url" content="https://blog.dich.bid/about-vim/">
|
||||
|
||||
<meta name="twitter:card" content="summary_large_image">
|
||||
<meta name="twitter:description" content="">
|
||||
<meta name="twitter:title" content="Dich'blog">
|
||||
<meta property="twitter:domain" content="blog.dich.bid">
|
||||
<meta property="twitter:url" content="https://blog.dich.bid/about-vim/">
|
||||
|
||||
<link rel="alternate" type="application/atom+xml" title="Dich'blog Atom Feed" href="https://blog.dich.bid/atom.xml" />
|
||||
|
||||
|
||||
<link rel="icon" type="image/png" href=/dich.webp />
|
||||
|
||||
<!-- ✅ Added center alignment styles -->
|
||||
<style>
|
||||
.footer {
|
||||
text-align: center;
|
||||
padding: 1rem 0;
|
||||
}
|
||||
|
||||
.footer__inner {
|
||||
display: flex;
|
||||
justify-content: center;
|
||||
flex-direction: column;
|
||||
align-items: center;
|
||||
}
|
||||
|
||||
.copyright {
|
||||
text-align: center;
|
||||
}
|
||||
</style>
|
||||
</head>
|
||||
|
||||
<body class="">
|
||||
<div class="container">
|
||||
|
||||
<header class="header">
|
||||
<div class="header__inner">
|
||||
<div class="header__logo">
|
||||
|
||||
<a href="https://blog.dich.bid" style="text-decoration: none;">
|
||||
<div class="logo">
|
||||
|
||||
Dich'blog
|
||||
|
||||
</div>
|
||||
</a>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
|
||||
<nav class="menu">
|
||||
<ul class="menu__inner">
|
||||
<li><a href="https://blog.dich.bid">blog</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/archive">archive</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/tags">tags</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/weekly">weekly</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/search">search</a></li>
|
||||
|
||||
<li class="active"><a href="https://blog.dich.bid/about">about me</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/links">links</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/atom.xml">rss</a></li>
|
||||
|
||||
<li><a href="https://github.com/Dichgrem" target="_blank" rel="noopener noreferrer">github</a></li>
|
||||
</ul>
|
||||
</nav>
|
||||
|
||||
|
||||
|
||||
</header>
|
||||
|
||||
|
||||
<div class="content">
|
||||
|
||||
<div class="post">
|
||||
|
||||
<h1 class="post-title"><a href="https://blog.dich.bid/about-vim/">乱七八糟:Vim编辑器速查</a></h1>
|
||||
<div class="post-meta-inline">
|
||||
|
||||
<span class="post-date">
|
||||
2024-08-15
|
||||
</span>
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
<span class="post-tags-inline">
|
||||
:: tags:
|
||||
<a class="post-tag" href="https://blog.dich.bid/tags/luan-qi-ba-zao/">#乱七八糟</a></span>
|
||||
|
||||
|
||||
<div class="post-content">
|
||||
<p>前言 Vim 是从早期的 vi 编辑器发展而来的增强版，其名称代表“Vi IMproved”。由荷兰程序员 Bram Moolenaar 于 1991 年首次发布。Vim 是开源软件，支持多种操作系统，包括 Unix、Linux、Windows 和 macOS 等。</p>
|
||||
<span id="continue-reading"></span>
|
||||
<hr />
|
||||
<h2 id="yi-fen-you-xiu-de-vim-su-cha-biao">一份优秀的 Vim 速查表</h2>
|
||||
<blockquote>
|
||||
<p>翻译自<code>https://vimsheet.com/</code></p>
|
||||
</blockquote>
|
||||
<p>我整理了一份我每天使用的 Vim 基本命令列表，并提供了一些配置建议，使 Vim 更加实用。因为没有配置的 Vim 使用起来会比较痛苦。</p>
|
||||
<h2 id="ji-chu-ming-ling">基础命令</h2>
|
||||
<h3 id="guang-biao-yi-dong-pu-tong-mo-shi-ke-shi-mo-shi">光标移动（普通模式/可视模式）</h3>
|
||||
<ul>
|
||||
<li><code>h</code> <code>j</code> <code>k</code> <code>l</code>：左、下、上、右移动</li>
|
||||
<li><code>w</code> / <code>b</code>：下一个/上一个单词</li>
|
||||
<li><code>W</code> / <code>B</code>：下一个/上一个以空格分隔的单词</li>
|
||||
<li><code>e</code> / <code>ge</code>：下一个/上一个单词的结尾</li>
|
||||
<li><code>0</code> / <code>$</code>：行首/行尾</li>
|
||||
<li><code>^</code>：行首第一个非空白字符（等同于 <code>0w</code>）</li>
|
||||
</ul>
|
||||
<h3 id="bian-ji-wen-ben">编辑文本</h3>
|
||||
<ul>
|
||||
<li><code>i</code> / <code>a</code>：在光标处/之后进入插入模式</li>
|
||||
<li><code>I</code> / <code>A</code>：在行首/行尾进入插入模式</li>
|
||||
<li><code>o</code> / <code>O</code>：在当前行下方/上方插入空行</li>
|
||||
<li><code>Esc</code> 或 <code>Ctrl+[</code>：退出插入模式</li>
|
||||
<li><code>d</code>：删除</li>
|
||||
<li><code>dd</code>：删除整行</li>
|
||||
<li><code>c</code>：删除并进入插入模式</li>
|
||||
<li><code>cc</code>：删除整行并进入插入模式</li>
|
||||
</ul>
|
||||
<h3 id="cao-zuo-fu">操作符</h3>
|
||||
<ul>
|
||||
<li>操作符也适用于可视模式</li>
|
||||
<li><code>d</code>：从光标处删除到移动目标</li>
|
||||
<li><code>c</code>：从光标处删除到移动目标，并进入插入模式</li>
|
||||
<li><code>y</code>：从光标处复制到移动目标</li>
|
||||
<li><code>></code>：缩进一级</li>
|
||||
<li><code><</code>：取消缩进一级</li>
|
||||
<li>操作符可与移动命令组合使用，例如：<code>d$</code> 删除从光标到行尾的内容</li>
|
||||
</ul>
|
||||
<h3 id="biao-ji-wen-ben-ke-shi-mo-shi">标记文本（可视模式）</h3>
|
||||
<ul>
|
||||
<li><code>v</code>：进入可视模式</li>
|
||||
<li><code>V</code>：进入行可视模式</li>
|
||||
<li><code>Ctrl+v</code>：进入块可视模式</li>
|
||||
<li><code>Esc</code> 或 <code>Ctrl+[</code>：退出可视模式</li>
|
||||
</ul>
|
||||
<h3 id="jian-tie-ban-cao-zuo">剪贴板操作</h3>
|
||||
<ul>
|
||||
<li><code>yy</code>：复制整行</li>
|
||||
<li><code>p</code>：在光标后粘贴</li>
|
||||
<li><code>P</code>：在光标前粘贴</li>
|
||||
<li><code>dd</code>：剪切整行</li>
|
||||
<li><code>x</code>：删除当前字符</li>
|
||||
<li><code>X</code>：删除前一个字符</li>
|
||||
<li>默认情况下，<code>d</code> / <code>c</code> 会将删除的内容复制到剪贴板</li>
|
||||
</ul>
|
||||
<h3 id="tui-chu">退出</h3>
|
||||
<ul>
|
||||
<li><code>:w</code>：保存文件但不退出</li>
|
||||
<li><code>:wq</code>：保存并退出</li>
|
||||
<li><code>:q</code>：退出（如果有修改会失败）</li>
|
||||
<li><code>:q!</code>：强制退出并放弃修改</li>
|
||||
</ul>
|
||||
<h3 id="sou-suo-ti-huan">搜索/替换</h3>
|
||||
<ul>
|
||||
<li><code>/pattern</code>：搜索 pattern</li>
|
||||
<li><code>?pattern</code>：向上搜索 pattern</li>
|
||||
<li><code>n</code>：重复上一次搜索（同方向）</li>
|
||||
<li><code>N</code>：重复上一次搜索（反方向）</li>
|
||||
<li><code>:%s/old/new/g</code>：全文件替换 old 为 new</li>
|
||||
<li><code>:%s/old/new/gc</code>：全文件替换 old 为 new，并逐个确认</li>
|
||||
</ul>
|
||||
<h3 id="chang-gui-ming-ling">常规命令</h3>
|
||||
<ul>
|
||||
<li><code>u</code>：撤销</li>
|
||||
<li><code>Ctrl+r</code>：重做</li>
|
||||
</ul>
|
||||
<h2 id="gao-ji-ming-ling">高级命令</h2>
|
||||
<h3 id="guang-biao-yi-dong">光标移动</h3>
|
||||
<ul>
|
||||
<li><code>Ctrl+d</code>：向下移动半页</li>
|
||||
<li><code>Ctrl+u</code>：向上移动半页</li>
|
||||
<li><code>}</code>：跳转到下一个段落（空行）</li>
|
||||
<li><code>{</code>：跳转到上一个段落（空行）</li>
|
||||
<li><code>gg</code>：跳转到文件顶部</li>
|
||||
<li><code>G</code>：跳转到文件底部</li>
|
||||
<li><code>:[num]</code>：跳转到指定行号</li>
|
||||
<li><code>Ctrl+e</code> / <code>Ctrl+y</code>：向下/向上滚动一行</li>
|
||||
</ul>
|
||||
<h3 id="zi-fu-sou-suo">字符搜索</h3>
|
||||
<ul>
|
||||
<li><code>f [char]</code>：向前移动到指定字符</li>
|
||||
<li><code>F [char]</code>：向后移动到指定字符</li>
|
||||
<li><code>t [char]</code>：向前移动到指定字符之前</li>
|
||||
<li><code>T [char]</code>：向后移动到指定字符之前</li>
|
||||
<li><code>;</code> / <code>,</code>：重复上一次字符搜索（正向/反向）</li>
|
||||
</ul>
|
||||
<h3 id="bian-ji-wen-ben-1">编辑文本</h3>
|
||||
<ul>
|
||||
<li><code>J</code>：将下一行合并到当前行</li>
|
||||
<li><code>r [char]</code>：用指定字符替换当前字符（不进入插入模式）</li>
|
||||
</ul>
|
||||
<h3 id="ke-shi-mo-shi">可视模式</h3>
|
||||
<ul>
|
||||
<li><code>O</code>：移动到块的另一个角</li>
|
||||
<li><code>o</code>：移动到标记区域的另一端</li>
|
||||
</ul>
|
||||
<h3 id="wen-jian-biao-qian">文件标签</h3>
|
||||
<ul>
|
||||
<li><code>:e filename</code>：编辑文件</li>
|
||||
<li><code>:tabe</code>：打开新标签页</li>
|
||||
<li><code>gt</code>：切换到下一个标签页</li>
|
||||
<li><code>gT</code>：切换到上一个标签页</li>
|
||||
<li><code>:vsp</code>：垂直分割窗口</li>
|
||||
<li><code>Ctrl+ws</code>：水平分割窗口</li>
|
||||
<li><code>Ctrl+wv</code>：垂直分割窗口</li>
|
||||
<li><code>Ctrl+ww</code>：在窗口间切换</li>
|
||||
<li><code>Ctrl+wq</code>：关闭当前窗口</li>
|
||||
</ul>
|
||||
<h3 id="biao-ji">标记</h3>
|
||||
<ul>
|
||||
<li>标记允许你跳转到代码中的指定位置</li>
|
||||
<li><code>m{a-z}</code>：在光标位置设置标记 {a-z}</li>
|
||||
<li>大写标记 {A-Z} 是全局标记，可跨文件使用</li>
|
||||
<li><code>'{a-z}</code>：跳转到设置标记的行首</li>
|
||||
<li><code>''</code>：返回上一个跳转位置</li>
|
||||
</ul>
|
||||
<h3 id="wen-ben-dui-xiang">文本对象</h3>
|
||||
<ul>
|
||||
<li>例如：<code>def (arg1, arg2, arg3)</code>，光标在括号内</li>
|
||||
<li><code>di(</code>：删除括号内的内容，即“删除最近括号内的内容”</li>
|
||||
<li>如果没有文本对象，你需要使用 <code>T(dt)</code> 来实现相同的功能</li>
|
||||
</ul>
|
||||
<h3 id="chang-gui-ming-ling-1">常规命令</h3>
|
||||
<ul>
|
||||
<li><code>.</code>：重复上一次命令</li>
|
||||
<li>在插入模式下，<code>Ctrl+r 0</code>：插入最近复制的文本</li>
|
||||
<li><code>gv</code>：重新选择上一次选中的文本块</li>
|
||||
<li><code>%</code>：在匹配的 <code>()</code> 或 <code>{}</code> 之间跳转</li>
|
||||
</ul>
|
||||
<hr />
|
||||
<p>如果你希望将此速查表保存为 PDF 或打印出来，可以使用 Markdown 编辑器（如 Typora）或在线工具（如 Dillinger）进行导出。</p>
|
||||
<p>此外，Vim 的默认配置可能不够友好，建议你参考以下资源进行配置优化：</p>
|
||||
<ul>
|
||||
<li><a href="https://github.com/tpope/vim-sensible">vim-sensible</a>：提供一套合理的默认配置</li>
|
||||
<li><a href="https://github.com/tpope/vim-pathogen">vim-pathogen</a>：插件管理工具</li>
|
||||
<li><a href="https://github.com/rking/ag.vim">ag.vim</a>：快速全局搜索插件</li>
|
||||
<li><a href="https://github.com/ctrlpvim/ctrlp.vim">ctrlp.vim</a>：文件和缓冲区快速切换插件</li>
|
||||
<li><a href="https://github.com/preservim/nerdcommenter">nerdcommenter</a>：代码注释插件</li>
|
||||
</ul>
|
||||
<p>这些插件可以显著提升 Vim 的功能，使其更接近一个完整的 IDE。</p>
|
||||
<hr />
|
||||
<p><strong>Done.</strong></p>
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
<div class="pagination">
|
||||
<div class="pagination__title">
|
||||
<span class="pagination__title-h">Thanks for reading! Read other posts?</span>
|
||||
<hr />
|
||||
</div>
|
||||
<div class="pagination__buttons">
|
||||
<span class="button previous">
|
||||
<a href="https://blog.dich.bid/network-nginx/">
|
||||
<span class="button__icon">←</span>
|
||||
<span class="button__text">Network的艺术:Docker建站与反向代理</span>
|
||||
</a>
|
||||
</span>
|
||||
|
||||
|
||||
<span class="button next">
|
||||
<a href="https://blog.dich.bid/about-2024/">
|
||||
<span class="button__text">乱七八糟:2024年度总结</span>
|
||||
<span class="button__icon">→</span>
|
||||
</a>
|
||||
</span>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
</div>
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
<footer class="footer">
|
||||
<div class="footer__inner">
|
||||
<div class="copyright">
|
||||
<span>©
|
||||
2025
|
||||
Dichgrem</span>
|
||||
<span class="copyright-theme">
|
||||
<span class="copyright-theme-sep"> :: CC BY-SA 4.0 :: A friend comes from distant lands</span>
|
||||
</a>
|
||||
</span>
|
||||
</div>
|
||||
</div>
|
||||
</footer>
|
||||
|
||||
</div>
|
||||
</body>
|
||||
</html>
|
||||
|
||||
209
public/about/index.html
Normal file
209
public/about/index.html
Normal file
@ -0,0 +1,209 @@
|
||||
<!DOCTYPE html>
|
||||
<html lang="en">
|
||||
|
||||
<head>
|
||||
<title>Dich'blog</title>
|
||||
|
||||
<meta http-equiv="content-type" content="text/html; charset=utf-8">
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1">
|
||||
<meta name="robots" content="noodp"/>
|
||||
|
||||
<link rel="stylesheet" href="https://blog.dich.bid/style.css">
|
||||
<link rel="stylesheet" href="https://blog.dich.bid/color/blue.css">
|
||||
|
||||
<link rel="stylesheet" href="https://blog.dich.bid/color/background_dark.css">
|
||||
|
||||
<link rel="stylesheet" href="https://blog.dich.bid/font-hack-subset.css">
|
||||
|
||||
<meta name="description" content="">
|
||||
|
||||
<meta property="og:description" content="">
|
||||
<meta property="og:title" content="Dich'blog">
|
||||
<meta property="og:type" content="article">
|
||||
<meta property="og:url" content="https://blog.dich.bid/about/">
|
||||
|
||||
<meta name="twitter:card" content="summary_large_image">
|
||||
<meta name="twitter:description" content="">
|
||||
<meta name="twitter:title" content="Dich'blog">
|
||||
<meta property="twitter:domain" content="blog.dich.bid">
|
||||
<meta property="twitter:url" content="https://blog.dich.bid/about/">
|
||||
|
||||
<link rel="alternate" type="application/atom+xml" title="Dich'blog Atom Feed" href="https://blog.dich.bid/atom.xml" />
|
||||
|
||||
|
||||
<link rel="icon" type="image/png" href=/dich.webp />
|
||||
|
||||
<!-- ✅ Added center alignment styles -->
|
||||
<style>
|
||||
.footer {
|
||||
text-align: center;
|
||||
padding: 1rem 0;
|
||||
}
|
||||
|
||||
.footer__inner {
|
||||
display: flex;
|
||||
justify-content: center;
|
||||
flex-direction: column;
|
||||
align-items: center;
|
||||
}
|
||||
|
||||
.copyright {
|
||||
text-align: center;
|
||||
}
|
||||
</style>
|
||||
</head>
|
||||
|
||||
<body class="">
|
||||
<div class="container">
|
||||
|
||||
<header class="header">
|
||||
<div class="header__inner">
|
||||
<div class="header__logo">
|
||||
|
||||
<a href="https://blog.dich.bid" style="text-decoration: none;">
|
||||
<div class="logo">
|
||||
|
||||
Dich'blog
|
||||
|
||||
</div>
|
||||
</a>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
|
||||
<nav class="menu">
|
||||
<ul class="menu__inner">
|
||||
<li><a href="https://blog.dich.bid">blog</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/archive">archive</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/tags">tags</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/weekly">weekly</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/search">search</a></li>
|
||||
|
||||
<li class="active"><a href="https://blog.dich.bid/about">about me</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/links">links</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/atom.xml">rss</a></li>
|
||||
|
||||
<li><a href="https://github.com/Dichgrem" target="_blank" rel="noopener noreferrer">github</a></li>
|
||||
</ul>
|
||||
</nav>
|
||||
|
||||
|
||||
|
||||
</header>
|
||||
|
||||
|
||||
<div class="content">
|
||||
|
||||
<div class="post">
|
||||
|
||||
<h1 class="post-title"><a href="https://blog.dich.bid/about/">About Me</a></h1>
|
||||
<div class="post-meta-inline">
|
||||
|
||||
<span class="post-date"></span>
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
|
||||
<div class="post-content">
|
||||
<h2 id="welcome-to-dich-blog">Welcome to dich' Blog!</h2>
|
||||
<p>用电子罗盘，转赛博核桃，勘电磁风水，寻网络龙脉</p>
|
||||
<blockquote>
|
||||
<p>一个人应该能够给孩子换尿布、计划一次侵略行动、杀猪、驾驶飞船、设计建筑物、写诗、做会计账目、砌墙、接合断骨、照顾临终的人、执行命令、下达命令、与人合作、独立行动、解方程式、分析一个新问题、施肥、编程、做一餐美味的饭、高效地战斗、勇敢地死去。专业化是为昆虫准备的。 ——<em>罗伯特·海因莱恩</em></p>
|
||||
</blockquote>
|
||||
<p>有事请联系 admin@dich.bid</p>
|
||||
<p>GPG公钥:</p>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>-----BEGIN PGP PUBLIC KEY BLOCK-----
|
||||
</span><span>
|
||||
</span><span>mDMEaFD4ERYJKwYBBAHaRw8BAQdAWahrrdkEPyUXuYxI72vuu10wdzoUflXwgoOP
|
||||
</span><span>W5BDNwy0F2RpY2ggPGJyY2VmeUBnbWFpbC5jb20+iJYEExYKAD4WIQQLzPfdBMio
|
||||
</span><span>WbXLx6aN3u4/oWJWBAUCaFD4EQIbAwUJAeEzgAULCQgHAgYVCgkICwIEFgIDAQIe
|
||||
</span><span>AQIXgAAKCRCN3u4/oWJWBJyIAP9pDBde2tEdppRHn+Qk8tYIsdJHmEdbSiWBRGgq
|
||||
</span><span>oEtqZwD/SlTXOKC8XFBHhXfDQe6HKKfcmOHzI7tCAbEvYzXNPwW4OARoUPgREgor
|
||||
</span><span>BgEEAZdVAQUBAQdAtId5jz2fnDkGUz2b4Y7wqI4yDAgeJgKlmEdxMMVEjgcDAQgH
|
||||
</span><span>iH4EGBYKACYWIQQLzPfdBMioWbXLx6aN3u4/oWJWBAUCaFD4EQIbDAUJAeEzgAAK
|
||||
</span><span>CRCN3u4/oWJWBPrHAQCtfO5kC5XEEcJUCM7hKjC1OMzqE2qlBS3te2rZT3KH0wD/
|
||||
</span><span>dr+m3w+D4q5y5uy1sny6BW6QjjdrQP+ZWUjA3na0jgqZAg0EWpElGwEQAMkauPYV
|
||||
</span><span>lZPeaWC0AUxQJ7EPFVBcuAEnYZ9eXoPvlo74DIuqODCmaj90uBfyhkKcFj4c63WZ
|
||||
</span><span>9eFL5JpJxz7BuIMjLbaaVI1eFE9EvBXW0cUeu86WNu8Jbtn5CxtfyokqtYXmP6AP
|
||||
</span><span>hj1p8hdic//hRXs3eLeeNe1YZRW6i8cLM1WCkbWjzKvg91JX4hKXDPExwgGwoqDi
|
||||
</span><span>ZqrvkyQ4kY0oddzwoQ9Lb1U4oXWzE4g34o46hUaLgNW1iZ/zYJNT3EUb74bAzxvE
|
||||
</span><span>nwsVrueNsS8wuYOWckD2WKt7KjHJxg4uo+MjSUdPf5+qgN68+n91qKstSz3lZq25
|
||||
</span><span>1q5HUL2jnyeCTMBl8BY9O/+qdDrm2dXNaPSfRCk0jPKxcyi0YydhrEgzDX9wW2Ha
|
||||
</span><span>dDyGIUwSKxvwdzjE/quE+d3WUWv51oTrYZmHm9YhXki37AFqCcz+7qECvNTvyvih
|
||||
</span><span>tQ86x+TUwZmlWwusPoZJNEOOi/9Popvd+ys7uBiCKae7wAAtlrdMXLBwOLMpis+z
|
||||
</span><span>HkfHN41ZpjwnbPSq7hM7NwhHTBA+8TxNTgu4piZadHf2Qvw0ofme5+ipkcueufdf
|
||||
</span><span>ocj9rXGZ7D3cxVgCK2c7QpUV+gVcY29hqNAiY7Eh+ldgxHt/o6vTiauYjPpjlyh4
|
||||
</span><span>31TEv8kQapqcgtC6JL6LKeZiyqb7+5YTt7rbABEBAAG0REZyYW5jaXMgQmFueWlr
|
||||
</span><span>d2EgKEEga2V5IGZvciBzaWduaW5nIHBhY2thZ2VzKSA8YmFueWlrd2FmYkBnbWFp
|
||||
</span><span>bC5jb20+iQI3BBMBCAAhBQJakSUbAhsDBQsJCAcDBRUKCQgLBRYCAwEAAh4BAheA
|
||||
</span><span>AAoJEBbi4azG9RJCoasQAMkL3AcIinDXec8/9Tg4MFMKd0/owT9arC0K8UP7yu2S
|
||||
</span><span>/H+G+uYm8lsnjCv2Nlsll8fo2P+QuIsIg4ec7qb6Ng/ZAXvKwILMHsULLcYY1Jv5
|
||||
</span><span>n5k5+DnItUehUSSKTn1haOvL0+3u48PzcCmVHVMsECnW6sUuUnVPE+gtuvwChKWV
|
||||
</span><span>92jLfWkk+jl7FxxCv0b20COCX0MRtIO1Im7oqSgTLQLzKQiK2NxsNmciMBmWhzZm
|
||||
</span><span>X/64eZeidS3VRYmWd0rUdFCXwTDgXeHOwYmlI9la7hmqi1k5i2ILFW2XE4m5+Jtv
|
||||
</span><span>5VIIa1rSB6iOVpsIKb0wFwJhye8ak2ZCQfRLL3Fhwt8M+qri0V9X6EJpa7U6uMUL
|
||||
</span><span>qWl3N6Tt7DMbTFAFfxeykRSzEENGWF3PcyC/KGakuQGhsNJcUInXUhjKKHyUPRpo
|
||||
</span><span>udV14RZoSzLEBepjowUCulRGJ6VIcDpmmCMKmlOBMiErtqyBeLJZ3L6DGgW059bW
|
||||
</span><span>FxPZeyauoO86mZ3eA2WRrm7B1jb/1gCg8IneqOIVp9Vt5yLmfZ5ZrM5m3L/Id7Zs
|
||||
</span><span>dAU0ATYv2YIh3tZWfgG7SKIlv7eBj7Ytwl4ELLHRgyE0mewZen5qxcACxCax6rJw
|
||||
</span><span>aM+jgmnSlyWpt1JuQJBNIdV6UCi3G7fkfQBAmFftF1ZgYTx9/6fiB2bvr3DQkn57
|
||||
</span><span>uQINBFqRJRsBEACt+JgM+FRqK5EDUZEhP0huTAzMdZITBjtDbCNs2UakAVJS8l4C
|
||||
</span><span>P9pulv+E01yAj+ecw++Ke/tKeeUOjzezGihRhpwAstPiquNodkE9MLftkyu9lkIN
|
||||
</span><span>Xvzt6t6fLdIJzE+kB0x8gMphSq0Wp7qjWxDXCyr0SMYD8wLttYIjFogG5YRsQ/j6
|
||||
</span><span>PV+hRexZ+P8l2UoWvtbxDCbNrDLUMEYjK6CZjtXn8qNLzPFSOVNjqZpIm9/BlWZZ
|
||||
</span><span>0WbtpSmzdVL23aGt968RueqcRdqy9+lvw7U8tOUOmjP9zKRN0IADdw0WphYEBfWa
|
||||
</span><span>hxeKmJk+nFR6g3TPQ86xdL3VZsPtqSdVO6O5CdqcVFVyoaebsTZlw/Qz1/6Sy3gJ
|
||||
</span><span>83IezA8kJItk6ZRMiHNVM5+x/z8feFVjnDz+DG3px09vZ/YOi4GF1d0G/dnCf2DF
|
||||
</span><span>l4dH6+Va34KfCwYjnkFPtd8Wj4M8H62UMJrCg81eEcGtlFtKBtkHv8VMRl6I/cYH
|
||||
</span><span>p1uq3eNCy5G7IrIlYyG1zc6xuDun0PZChnkwNWjylfdk0XFGTtASC9WjIjIBD364
|
||||
</span><span>ns/p4j7gJYx5RZspCfytPzjpUtP0N5wEMLoz3KbQsbxAuDxkijV7s1xVrApxk2xG
|
||||
</span><span>rdMeWM5KpbAwlos9yDlb4YYbUrOR+CPBYPTbrQ55wcePV4gOnEmoyrdkYwARAQAB
|
||||
</span><span>iQIfBBgBCAAJBQJakSUbAhsMAAoJEBbi4azG9RJCaEsQAJJB2BXMks73ETSdvIPn
|
||||
</span><span>R9eRFIpXmaYnGOBQnvz+lSlQ+etcjmXbWw8YxKohdeIfuydV1Fug/I/WmlzDDH8B
|
||||
</span><span>1R26Vs0Czr2P64iNJVIhrdjvfPK5fdJXKwSchiJ1SEWahsXXXyQXqOZwMkGMxxFd
|
||||
</span><span>diH4OVsY5q9cM21gXup4WBezFPMtaUvu35QKbwgKntgdJJv/JSc8rWHZQS8p/820
|
||||
</span><span>v8UWxxxbgprbtTvmwMakr70u4FtORWic1UTJ9sCsD4Yw6CbvLyMV8z5vAQhi+lND
|
||||
</span><span>qIzRXEXTfYnZaQ6ddCuTMGF2K1+CyS7/7FA0YwxrjhlxE0XwOgvpvJS/tmK0fB4J
|
||||
</span><span>IvDXgCW/ym2xvGVwLTNu/apeon0Skli4sokl2yVnUMRKGCz7ApjhrNo1kikHKGJw
|
||||
</span><span>8jv6tCTIyJtGobmTaIZGg2N3Owd7QhoBbR80LIFFaAlWgFv2XnLes8wF1xVNmjMI
|
||||
</span><span>jsKO+itYmntg/GPep6hOcFnU/JrsSiVTvmHlpTHqK7q1cZTDV/G5W739m4z00hgw
|
||||
</span><span>zXHD2OOP/LPGEtQWOg+g8g3+KNQzLHZqQO5UScTG2fL99FaXNDv3BZt4e4liGD01
|
||||
</span><span>5oRRZTFV4YPmXVB1x23FhkRQN2Jnt76x9t8QcwKcXWBUOUZg9uJUkIgipxxPEPSC
|
||||
</span><span>NS+riEdhXHgqG76f+wRnkDOK
|
||||
</span><span>=2r/G
|
||||
</span><span>-----END PGP PUBLIC KEY BLOCK-----
|
||||
</span></code></pre>
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
</div>
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
<footer class="footer">
|
||||
<div class="footer__inner">
|
||||
<div class="copyright">
|
||||
<span>©
|
||||
2025
|
||||
Dichgrem</span>
|
||||
<span class="copyright-theme">
|
||||
<span class="copyright-theme-sep"> :: CC BY-SA 4.0 :: A friend comes from distant lands</span>
|
||||
</a>
|
||||
</span>
|
||||
</div>
|
||||
</div>
|
||||
</footer>
|
||||
|
||||
</div>
|
||||
</body>
|
||||
</html>
|
||||
|
||||
659
public/archive/index.html
Normal file
659
public/archive/index.html
Normal file
@ -0,0 +1,659 @@
|
||||
<!DOCTYPE html>
|
||||
<html lang="en">
|
||||
|
||||
<head>
|
||||
<title>Dich'blog</title>
|
||||
|
||||
<meta http-equiv="content-type" content="text/html; charset=utf-8">
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1">
|
||||
<meta name="robots" content="noodp"/>
|
||||
|
||||
<link rel="stylesheet" href="https://blog.dich.bid/style.css">
|
||||
<link rel="stylesheet" href="https://blog.dich.bid/color/blue.css">
|
||||
|
||||
<link rel="stylesheet" href="https://blog.dich.bid/color/background_dark.css">
|
||||
|
||||
<link rel="stylesheet" href="https://blog.dich.bid/font-hack-subset.css">
|
||||
|
||||
<meta name="description" content="">
|
||||
|
||||
<meta property="og:description" content="">
|
||||
<meta property="og:title" content="Dich'blog">
|
||||
<meta property="og:type" content="article">
|
||||
<meta property="og:url" content="https://blog.dich.bid/archive/">
|
||||
|
||||
<meta name="twitter:card" content="summary_large_image">
|
||||
<meta name="twitter:description" content="">
|
||||
<meta name="twitter:title" content="Dich'blog">
|
||||
<meta property="twitter:domain" content="blog.dich.bid">
|
||||
<meta property="twitter:url" content="https://blog.dich.bid/archive/">
|
||||
|
||||
<link rel="alternate" type="application/atom+xml" title="Dich'blog Atom Feed" href="https://blog.dich.bid/atom.xml" />
|
||||
|
||||
|
||||
<link rel="icon" type="image/png" href=/dich.webp />
|
||||
|
||||
<!-- ✅ Added center alignment styles -->
|
||||
<style>
|
||||
.footer {
|
||||
text-align: center;
|
||||
padding: 1rem 0;
|
||||
}
|
||||
|
||||
.footer__inner {
|
||||
display: flex;
|
||||
justify-content: center;
|
||||
flex-direction: column;
|
||||
align-items: center;
|
||||
}
|
||||
|
||||
.copyright {
|
||||
text-align: center;
|
||||
}
|
||||
</style>
|
||||
</head>
|
||||
|
||||
<body class="">
|
||||
<div class="container">
|
||||
|
||||
<header class="header">
|
||||
<div class="header__inner">
|
||||
<div class="header__logo">
|
||||
|
||||
<a href="https://blog.dich.bid" style="text-decoration: none;">
|
||||
<div class="logo">
|
||||
|
||||
Dich'blog
|
||||
|
||||
</div>
|
||||
</a>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
|
||||
<nav class="menu">
|
||||
<ul class="menu__inner">
|
||||
<li><a href="https://blog.dich.bid">blog</a></li>
|
||||
|
||||
<li class="active"><a href="https://blog.dich.bid/archive">archive</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/tags">tags</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/weekly">weekly</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/search">search</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/about">about me</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/links">links</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/atom.xml">rss</a></li>
|
||||
|
||||
<li><a href="https://github.com/Dichgrem" target="_blank" rel="noopener noreferrer">github</a></li>
|
||||
</ul>
|
||||
</nav>
|
||||
|
||||
|
||||
|
||||
</header>
|
||||
|
||||
|
||||
<div class="content">
|
||||
|
||||
<div class="post">
|
||||
<h1 class="post-title">Archive</h1>
|
||||
|
||||
|
||||
|
||||
|
||||
<ul><li class="post-list">
|
||||
<a href="https://blog.dich.bid/about-gpg/">
|
||||
<span class="post-date">2025-06-17</span>
|
||||
:: <span class="post-list-title">乱七八糟:GPG使用小记</span></a>
|
||||
|
||||
<span class="post-tags-inline">
|
||||
::
|
||||
<a class="post-tag" href="https://blog.dich.bid/tags/luan-qi-ba-zao/">#乱七八糟</a></span>
|
||||
|
||||
</li>
|
||||
<li class="post-list">
|
||||
<a href="https://blog.dich.bid/about-baci/">
|
||||
<span class="post-date">2025-04-23</span>
|
||||
:: <span class="post-list-title">乱七八糟:Baci实验笔记</span></a>
|
||||
|
||||
<span class="post-tags-inline">
|
||||
::
|
||||
<a class="post-tag" href="https://blog.dich.bid/tags/luan-qi-ba-zao/">#乱七八糟</a></span>
|
||||
|
||||
</li>
|
||||
<li class="post-list">
|
||||
<a href="https://blog.dich.bid/about-lazyvim/">
|
||||
<span class="post-date">2025-04-20</span>
|
||||
:: <span class="post-list-title">乱七八糟:lazyvim快速上手</span></a>
|
||||
|
||||
<span class="post-tags-inline">
|
||||
::
|
||||
<a class="post-tag" href="https://blog.dich.bid/tags/luan-qi-ba-zao/">#乱七八糟</a></span>
|
||||
|
||||
</li>
|
||||
<li class="post-list">
|
||||
<a href="https://blog.dich.bid/about-aria2/">
|
||||
<span class="post-date">2025-04-15</span>
|
||||
:: <span class="post-list-title">乱七八糟:Aria2各平台使用指南</span></a>
|
||||
|
||||
<span class="post-tags-inline">
|
||||
::
|
||||
<a class="post-tag" href="https://blog.dich.bid/tags/luan-qi-ba-zao/">#乱七八糟</a></span>
|
||||
|
||||
</li>
|
||||
<li class="post-list">
|
||||
<a href="https://blog.dich.bid/about-markdown/">
|
||||
<span class="post-date">2025-04-08</span>
|
||||
:: <span class="post-list-title">乱七八糟:Markdown使用快速教程</span></a>
|
||||
|
||||
<span class="post-tags-inline">
|
||||
::
|
||||
<a class="post-tag" href="https://blog.dich.bid/tags/luan-qi-ba-zao/">#乱七八糟</a></span>
|
||||
|
||||
</li>
|
||||
<li class="post-list">
|
||||
<a href="https://blog.dich.bid/about-gfs/">
|
||||
<span class="post-date">2025-03-18</span>
|
||||
:: <span class="post-list-title">乱七八糟:GFS项目考量笔记</span></a>
|
||||
|
||||
<span class="post-tags-inline">
|
||||
::
|
||||
<a class="post-tag" href="https://blog.dich.bid/tags/luan-qi-ba-zao/">#乱七八糟</a></span>
|
||||
|
||||
</li>
|
||||
<li class="post-list">
|
||||
<a href="https://blog.dich.bid/about-frp/">
|
||||
<span class="post-date">2025-03-01</span>
|
||||
:: <span class="post-list-title">乱七八糟:FRP使用指南</span></a>
|
||||
|
||||
<span class="post-tags-inline">
|
||||
::
|
||||
<a class="post-tag" href="https://blog.dich.bid/tags/luan-qi-ba-zao/">#乱七八糟</a></span>
|
||||
|
||||
</li>
|
||||
<li class="post-list">
|
||||
<a href="https://blog.dich.bid/about-ventoy/">
|
||||
<span class="post-date">2025-02-14</span>
|
||||
:: <span class="post-list-title">乱七八糟:Ventoy战斗盘部署</span></a>
|
||||
|
||||
<span class="post-tags-inline">
|
||||
::
|
||||
<a class="post-tag" href="https://blog.dich.bid/tags/luan-qi-ba-zao/">#乱七八糟</a></span>
|
||||
|
||||
</li>
|
||||
<li class="post-list">
|
||||
<a href="https://blog.dich.bid/network-zuwang/">
|
||||
<span class="post-date">2025-01-21</span>
|
||||
:: <span class="post-list-title">Network的艺术:家庭组网方案与设备选购</span></a>
|
||||
|
||||
<span class="post-tags-inline">
|
||||
::
|
||||
<a class="post-tag" href="https://blog.dich.bid/tags/wang-luo-yi-shu/">#网络艺术</a></span>
|
||||
|
||||
</li>
|
||||
<li class="post-list">
|
||||
<a href="https://blog.dich.bid/about-2024/">
|
||||
<span class="post-date">2025-01-04</span>
|
||||
:: <span class="post-list-title">乱七八糟:2024年度总结</span></a>
|
||||
|
||||
<span class="post-tags-inline">
|
||||
::
|
||||
<a class="post-tag" href="https://blog.dich.bid/tags/luan-qi-ba-zao/">#乱七八糟</a></span>
|
||||
|
||||
</li>
|
||||
<li class="post-list">
|
||||
<a href="https://blog.dich.bid/about-vim/">
|
||||
<span class="post-date">2024-08-15</span>
|
||||
:: <span class="post-list-title">乱七八糟:Vim编辑器速查</span></a>
|
||||
|
||||
<span class="post-tags-inline">
|
||||
::
|
||||
<a class="post-tag" href="https://blog.dich.bid/tags/luan-qi-ba-zao/">#乱七八糟</a></span>
|
||||
|
||||
</li>
|
||||
<li class="post-list">
|
||||
<a href="https://blog.dich.bid/network-nginx/">
|
||||
<span class="post-date">2024-07-14</span>
|
||||
:: <span class="post-list-title">Network的艺术:Docker建站与反向代理</span></a>
|
||||
|
||||
<span class="post-tags-inline">
|
||||
::
|
||||
<a class="post-tag" href="https://blog.dich.bid/tags/wang-luo-yi-shu/">#网络艺术</a></span>
|
||||
|
||||
</li>
|
||||
<li class="post-list">
|
||||
<a href="https://blog.dich.bid/about-server-set/">
|
||||
<span class="post-date">2024-06-12</span>
|
||||
:: <span class="post-list-title">乱七八糟:服务器初始化与安全设置</span></a>
|
||||
|
||||
<span class="post-tags-inline">
|
||||
::
|
||||
<a class="post-tag" href="https://blog.dich.bid/tags/luan-qi-ba-zao/">#乱七八糟</a></span>
|
||||
|
||||
</li>
|
||||
<li class="post-list">
|
||||
<a href="https://blog.dich.bid/about-runer-2/">
|
||||
<span class="post-date">2024-06-11</span>
|
||||
:: <span class="post-list-title">乱七八糟:跑步笔记(二)</span></a>
|
||||
|
||||
<span class="post-tags-inline">
|
||||
::
|
||||
<a class="post-tag" href="https://blog.dich.bid/tags/luan-qi-ba-zao/">#乱七八糟</a></span>
|
||||
|
||||
</li>
|
||||
<li class="post-list">
|
||||
<a href="https://blog.dich.bid/about-runer-1/">
|
||||
<span class="post-date">2024-06-08</span>
|
||||
:: <span class="post-list-title">乱七八糟:跑步笔记(一)</span></a>
|
||||
|
||||
<span class="post-tags-inline">
|
||||
::
|
||||
<a class="post-tag" href="https://blog.dich.bid/tags/luan-qi-ba-zao/">#乱七八糟</a></span>
|
||||
|
||||
</li>
|
||||
<li class="post-list">
|
||||
<a href="https://blog.dich.bid/about-cslearning/">
|
||||
<span class="post-date">2024-05-31</span>
|
||||
:: <span class="post-list-title">乱七八糟:计算机科学优质视频</span></a>
|
||||
|
||||
<span class="post-tags-inline">
|
||||
::
|
||||
<a class="post-tag" href="https://blog.dich.bid/tags/luan-qi-ba-zao/">#乱七八糟</a></span>
|
||||
|
||||
</li>
|
||||
<li class="post-list">
|
||||
<a href="https://blog.dich.bid/windows-conda-python/">
|
||||
<span class="post-date">2024-05-31</span>
|
||||
:: <span class="post-list-title">乱七八糟:Windows-Jupyter开发Python</span></a>
|
||||
|
||||
<span class="post-tags-inline">
|
||||
::
|
||||
<a class="post-tag" href="https://blog.dich.bid/tags/windows/">#Windows</a>,
|
||||
<a class="post-tag" href="https://blog.dich.bid/tags/luan-qi-ba-zao/">#乱七八糟</a></span>
|
||||
|
||||
</li>
|
||||
<li class="post-list">
|
||||
<a href="https://blog.dich.bid/windows-vscode-gcc/">
|
||||
<span class="post-date">2024-05-30</span>
|
||||
:: <span class="post-list-title">乱七八糟:Windows-VScode开发C/C++</span></a>
|
||||
|
||||
<span class="post-tags-inline">
|
||||
::
|
||||
<a class="post-tag" href="https://blog.dich.bid/tags/windows/">#Windows</a>,
|
||||
<a class="post-tag" href="https://blog.dich.bid/tags/luan-qi-ba-zao/">#乱七八糟</a></span>
|
||||
|
||||
</li>
|
||||
<li class="post-list">
|
||||
<a href="https://blog.dich.bid/windows-iso/">
|
||||
<span class="post-date">2024-05-29</span>
|
||||
:: <span class="post-list-title">乱七八糟:Windows封装与全自动安装</span></a>
|
||||
|
||||
<span class="post-tags-inline">
|
||||
::
|
||||
<a class="post-tag" href="https://blog.dich.bid/tags/windows/">#Windows</a>,
|
||||
<a class="post-tag" href="https://blog.dich.bid/tags/luan-qi-ba-zao/">#乱七八糟</a></span>
|
||||
|
||||
</li>
|
||||
<li class="post-list">
|
||||
<a href="https://blog.dich.bid/windows-all/">
|
||||
<span class="post-date">2024-05-26</span>
|
||||
:: <span class="post-list-title">乱七八糟:Windows安装与环境配置</span></a>
|
||||
|
||||
<span class="post-tags-inline">
|
||||
::
|
||||
<a class="post-tag" href="https://blog.dich.bid/tags/windows/">#Windows</a>,
|
||||
<a class="post-tag" href="https://blog.dich.bid/tags/luan-qi-ba-zao/">#乱七八糟</a></span>
|
||||
|
||||
</li>
|
||||
<li class="post-list">
|
||||
<a href="https://blog.dich.bid/windows-activation/">
|
||||
<span class="post-date">2024-05-25</span>
|
||||
:: <span class="post-list-title">乱七八糟:Windows激活那些事</span></a>
|
||||
|
||||
<span class="post-tags-inline">
|
||||
::
|
||||
<a class="post-tag" href="https://blog.dich.bid/tags/windows/">#Windows</a>,
|
||||
<a class="post-tag" href="https://blog.dich.bid/tags/luan-qi-ba-zao/">#乱七八糟</a></span>
|
||||
|
||||
</li>
|
||||
<li class="post-list">
|
||||
<a href="https://blog.dich.bid/windows-some-setting/">
|
||||
<span class="post-date">2024-05-24</span>
|
||||
:: <span class="post-list-title">乱七八糟:Windows常用操作</span></a>
|
||||
|
||||
<span class="post-tags-inline">
|
||||
::
|
||||
<a class="post-tag" href="https://blog.dich.bid/tags/windows/">#Windows</a>,
|
||||
<a class="post-tag" href="https://blog.dich.bid/tags/luan-qi-ba-zao/">#乱七八糟</a></span>
|
||||
|
||||
</li>
|
||||
<li class="post-list">
|
||||
<a href="https://blog.dich.bid/about-shortcut-key/">
|
||||
<span class="post-date">2024-05-23</span>
|
||||
:: <span class="post-list-title">乱七八糟:常用实用快捷键</span></a>
|
||||
|
||||
<span class="post-tags-inline">
|
||||
::
|
||||
<a class="post-tag" href="https://blog.dich.bid/tags/luan-qi-ba-zao/">#乱七八糟</a></span>
|
||||
|
||||
</li>
|
||||
<li class="post-list">
|
||||
<a href="https://blog.dich.bid/about-podcast-use/">
|
||||
<span class="post-date">2024-03-06</span>
|
||||
:: <span class="post-list-title">搭建个人信息流:播客收听指北</span></a>
|
||||
|
||||
<span class="post-tags-inline">
|
||||
::
|
||||
<a class="post-tag" href="https://blog.dich.bid/tags/luan-qi-ba-zao/">#乱七八糟</a></span>
|
||||
|
||||
</li>
|
||||
<li class="post-list">
|
||||
<a href="https://blog.dich.bid/about-rss-read/">
|
||||
<span class="post-date">2024-03-05</span>
|
||||
:: <span class="post-list-title">搭建个人信息流:RSS阅读指南</span></a>
|
||||
|
||||
<span class="post-tags-inline">
|
||||
::
|
||||
<a class="post-tag" href="https://blog.dich.bid/tags/luan-qi-ba-zao/">#乱七八糟</a></span>
|
||||
|
||||
</li>
|
||||
<li class="post-list">
|
||||
<a href="https://blog.dich.bid/about-opensource/">
|
||||
<span class="post-date">2024-03-03</span>
|
||||
:: <span class="post-list-title">乱七八糟:开源软件与协议</span></a>
|
||||
|
||||
<span class="post-tags-inline">
|
||||
::
|
||||
<a class="post-tag" href="https://blog.dich.bid/tags/luan-qi-ba-zao/">#乱七八糟</a></span>
|
||||
|
||||
</li>
|
||||
<li class="post-list">
|
||||
<a href="https://blog.dich.bid/network-how-email-works-3/">
|
||||
<span class="post-date">2024-02-22</span>
|
||||
:: <span class="post-list-title">电子邮件是如何工作的:自建域名邮箱</span></a>
|
||||
|
||||
<span class="post-tags-inline">
|
||||
::
|
||||
<a class="post-tag" href="https://blog.dich.bid/tags/wang-luo-yi-shu/">#网络艺术</a></span>
|
||||
|
||||
</li>
|
||||
<li class="post-list">
|
||||
<a href="https://blog.dich.bid/network-how-email-works-2/">
|
||||
<span class="post-date">2024-02-21</span>
|
||||
:: <span class="post-list-title">电子邮件是如何工作的:POP3/IMAP/SMTP</span></a>
|
||||
|
||||
<span class="post-tags-inline">
|
||||
::
|
||||
<a class="post-tag" href="https://blog.dich.bid/tags/wang-luo-yi-shu/">#网络艺术</a></span>
|
||||
|
||||
</li>
|
||||
<li class="post-list">
|
||||
<a href="https://blog.dich.bid/network-how-email-works-1/">
|
||||
<span class="post-date">2024-02-20</span>
|
||||
:: <span class="post-list-title">电子邮件是如何工作的:SPF/DKIM/DMARC</span></a>
|
||||
|
||||
<span class="post-tags-inline">
|
||||
::
|
||||
<a class="post-tag" href="https://blog.dich.bid/tags/wang-luo-yi-shu/">#网络艺术</a></span>
|
||||
|
||||
</li>
|
||||
<li class="post-list">
|
||||
<a href="https://blog.dich.bid/network-cdn/">
|
||||
<span class="post-date">2024-02-16</span>
|
||||
:: <span class="post-list-title">Network的艺术:CDN技术与应用</span></a>
|
||||
|
||||
<span class="post-tags-inline">
|
||||
::
|
||||
<a class="post-tag" href="https://blog.dich.bid/tags/wang-luo-yi-shu/">#网络艺术</a></span>
|
||||
|
||||
</li>
|
||||
<li class="post-list">
|
||||
<a href="https://blog.dich.bid/network-ssl/">
|
||||
<span class="post-date">2024-02-15</span>
|
||||
:: <span class="post-list-title">Network的艺术:SSL/TLS证书</span></a>
|
||||
|
||||
<span class="post-tags-inline">
|
||||
::
|
||||
<a class="post-tag" href="https://blog.dich.bid/tags/wang-luo-yi-shu/">#网络艺术</a></span>
|
||||
|
||||
</li>
|
||||
<li class="post-list">
|
||||
<a href="https://blog.dich.bid/network-isps/">
|
||||
<span class="post-date">2024-02-10</span>
|
||||
:: <span class="post-list-title">Network的艺术:国内至国际骨干ISP线路整理</span></a>
|
||||
|
||||
<span class="post-tags-inline">
|
||||
::
|
||||
<a class="post-tag" href="https://blog.dich.bid/tags/wang-luo-yi-shu/">#网络艺术</a></span>
|
||||
|
||||
</li>
|
||||
<li class="post-list">
|
||||
<a href="https://blog.dich.bid/network-download-1/">
|
||||
<span class="post-date">2024-02-09</span>
|
||||
:: <span class="post-list-title">Network的艺术:下载技术的历史</span></a>
|
||||
|
||||
<span class="post-tags-inline">
|
||||
::
|
||||
<a class="post-tag" href="https://blog.dich.bid/tags/wang-luo-yi-shu/">#网络艺术</a></span>
|
||||
|
||||
</li>
|
||||
<li class="post-list">
|
||||
<a href="https://blog.dich.bid/about-git/">
|
||||
<span class="post-date">2023-12-15</span>
|
||||
:: <span class="post-list-title">乱七八糟:Git使用简明手册</span></a>
|
||||
|
||||
<span class="post-tags-inline">
|
||||
::
|
||||
<a class="post-tag" href="https://blog.dich.bid/tags/luan-qi-ba-zao/">#乱七八糟</a></span>
|
||||
|
||||
</li>
|
||||
<li class="post-list">
|
||||
<a href="https://blog.dich.bid/about-junk-cleanup/">
|
||||
<span class="post-date">2023-11-19</span>
|
||||
:: <span class="post-list-title">乱七八糟:垃圾清理的艺术</span></a>
|
||||
|
||||
<span class="post-tags-inline">
|
||||
::
|
||||
<a class="post-tag" href="https://blog.dich.bid/tags/luan-qi-ba-zao/">#乱七八糟</a></span>
|
||||
|
||||
</li>
|
||||
<li class="post-list">
|
||||
<a href="https://blog.dich.bid/about-blog/">
|
||||
<span class="post-date">2023-10-12</span>
|
||||
:: <span class="post-list-title">乱七八糟:个人博客搭建</span></a>
|
||||
|
||||
<span class="post-tags-inline">
|
||||
::
|
||||
<a class="post-tag" href="https://blog.dich.bid/tags/luan-qi-ba-zao/">#乱七八糟</a></span>
|
||||
|
||||
</li>
|
||||
<li class="post-list">
|
||||
<a href="https://blog.dich.bid/about-mechrev-keyboard/">
|
||||
<span class="post-date">2023-09-04</span>
|
||||
:: <span class="post-list-title">乱七八糟:机械革命键盘失灵拯救记</span></a>
|
||||
|
||||
<span class="post-tags-inline">
|
||||
::
|
||||
<a class="post-tag" href="https://blog.dich.bid/tags/luan-qi-ba-zao/">#乱七八糟</a></span>
|
||||
|
||||
</li>
|
||||
<li class="post-list">
|
||||
<a href="https://blog.dich.bid/about-accurate-pronunciation/">
|
||||
<span class="post-date">2023-08-25</span>
|
||||
:: <span class="post-list-title">乱七八糟:常见发音错误术语集合</span></a>
|
||||
|
||||
<span class="post-tags-inline">
|
||||
::
|
||||
<a class="post-tag" href="https://blog.dich.bid/tags/luan-qi-ba-zao/">#乱七八糟</a></span>
|
||||
|
||||
</li>
|
||||
<li class="post-list">
|
||||
<a href="https://blog.dich.bid/about-calling-cards/">
|
||||
<span class="post-date">2023-08-24</span>
|
||||
:: <span class="post-list-title">乱七八糟:流量卡购买与套路</span></a>
|
||||
|
||||
<span class="post-tags-inline">
|
||||
::
|
||||
<a class="post-tag" href="https://blog.dich.bid/tags/luan-qi-ba-zao/">#乱七八糟</a></span>
|
||||
|
||||
</li>
|
||||
<li class="post-list">
|
||||
<a href="https://blog.dich.bid/awesome-arch-linux/">
|
||||
<span class="post-date">2023-08-16</span>
|
||||
:: <span class="post-list-title">综合工程:Arch-linux 安装与配置</span></a>
|
||||
|
||||
<span class="post-tags-inline">
|
||||
::
|
||||
<a class="post-tag" href="https://blog.dich.bid/tags/zong-he-gong-cheng/">#综合工程</a></span>
|
||||
|
||||
</li>
|
||||
<li class="post-list">
|
||||
<a href="https://blog.dich.bid/awesome-android-tv/">
|
||||
<span class="post-date">2023-08-14</span>
|
||||
:: <span class="post-list-title">综合工程:Android-TV 折腾小记</span></a>
|
||||
|
||||
<span class="post-tags-inline">
|
||||
::
|
||||
<a class="post-tag" href="https://blog.dich.bid/tags/zong-he-gong-cheng/">#综合工程</a></span>
|
||||
|
||||
</li>
|
||||
<li class="post-list">
|
||||
<a href="https://blog.dich.bid/awesome-android-root/">
|
||||
<span class="post-date">2023-08-13</span>
|
||||
:: <span class="post-list-title">综合工程:安卓刷机与root教程</span></a>
|
||||
|
||||
<span class="post-tags-inline">
|
||||
::
|
||||
<a class="post-tag" href="https://blog.dich.bid/tags/zong-he-gong-cheng/">#综合工程</a></span>
|
||||
|
||||
</li>
|
||||
<li class="post-list">
|
||||
<a href="https://blog.dich.bid/awesome-openwrt/">
|
||||
<span class="post-date">2023-08-12</span>
|
||||
:: <span class="post-list-title">综合工程:OpenWrt路由部署与软件编译</span></a>
|
||||
|
||||
<span class="post-tags-inline">
|
||||
::
|
||||
<a class="post-tag" href="https://blog.dich.bid/tags/zong-he-gong-cheng/">#综合工程</a></span>
|
||||
|
||||
</li>
|
||||
<li class="post-list">
|
||||
<a href="https://blog.dich.bid/awesome-pve-mcsm/">
|
||||
<span class="post-date">2023-08-11</span>
|
||||
:: <span class="post-list-title">综合工程:PVE安装与MC服务器搭建</span></a>
|
||||
|
||||
<span class="post-tags-inline">
|
||||
::
|
||||
<a class="post-tag" href="https://blog.dich.bid/tags/zong-he-gong-cheng/">#综合工程</a></span>
|
||||
|
||||
</li>
|
||||
<li class="post-list">
|
||||
<a href="https://blog.dich.bid/awesome-vm-android/">
|
||||
<span class="post-date">2023-08-10</span>
|
||||
:: <span class="post-list-title">综合工程:linux搭建安卓虚拟机</span></a>
|
||||
|
||||
<span class="post-tags-inline">
|
||||
::
|
||||
<a class="post-tag" href="https://blog.dich.bid/tags/zong-he-gong-cheng/">#综合工程</a></span>
|
||||
|
||||
</li>
|
||||
<li class="post-list">
|
||||
<a href="https://blog.dich.bid/learn-linux-for-pc-7/">
|
||||
<span class="post-date">2023-08-01</span>
|
||||
:: <span class="post-list-title">Linux之旅(七):系统与终端字体设置</span></a>
|
||||
|
||||
<span class="post-tags-inline">
|
||||
::
|
||||
<a class="post-tag" href="https://blog.dich.bid/tags/linux/">#Linux</a></span>
|
||||
|
||||
</li>
|
||||
<li class="post-list">
|
||||
<a href="https://blog.dich.bid/learn-linux-for-pc-6/">
|
||||
<span class="post-date">2023-07-25</span>
|
||||
:: <span class="post-list-title">Linux之旅(六):常用命令与性能分析</span></a>
|
||||
|
||||
<span class="post-tags-inline">
|
||||
::
|
||||
<a class="post-tag" href="https://blog.dich.bid/tags/linux/">#Linux</a></span>
|
||||
|
||||
</li>
|
||||
<li class="post-list">
|
||||
<a href="https://blog.dich.bid/learn-linux-for-pc-5/">
|
||||
<span class="post-date">2023-07-24</span>
|
||||
:: <span class="post-list-title">Linux之旅(五):BIOS-UEFI-MBR-GPT-GRUB</span></a>
|
||||
|
||||
<span class="post-tags-inline">
|
||||
::
|
||||
<a class="post-tag" href="https://blog.dich.bid/tags/linux/">#Linux</a></span>
|
||||
|
||||
</li>
|
||||
<li class="post-list">
|
||||
<a href="https://blog.dich.bid/learn-linux-for-pc-4/">
|
||||
<span class="post-date">2023-07-23</span>
|
||||
:: <span class="post-list-title">Linux之旅(四):Terminal，Console and Shell</span></a>
|
||||
|
||||
<span class="post-tags-inline">
|
||||
::
|
||||
<a class="post-tag" href="https://blog.dich.bid/tags/linux/">#Linux</a></span>
|
||||
|
||||
</li>
|
||||
<li class="post-list">
|
||||
<a href="https://blog.dich.bid/learn-linux-for-pc-3/">
|
||||
<span class="post-date">2023-07-22</span>
|
||||
:: <span class="post-list-title">Linux之旅(三):内核/shell/包管理/文件系统/桌面环境</span></a>
|
||||
|
||||
<span class="post-tags-inline">
|
||||
::
|
||||
<a class="post-tag" href="https://blog.dich.bid/tags/linux/">#Linux</a></span>
|
||||
|
||||
</li>
|
||||
<li class="post-list">
|
||||
<a href="https://blog.dich.bid/learn-linux-for-pc-2/">
|
||||
<span class="post-date">2023-07-21</span>
|
||||
:: <span class="post-list-title">Linux之旅(二):FHS与目录结构</span></a>
|
||||
|
||||
<span class="post-tags-inline">
|
||||
::
|
||||
<a class="post-tag" href="https://blog.dich.bid/tags/linux/">#Linux</a></span>
|
||||
|
||||
</li>
|
||||
<li class="post-list">
|
||||
<a href="https://blog.dich.bid/learn-linux-for-pc-1/">
|
||||
<span class="post-date">2023-07-20</span>
|
||||
:: <span class="post-list-title">Linux之旅(一):构成与发行版</span></a>
|
||||
|
||||
<span class="post-tags-inline">
|
||||
::
|
||||
<a class="post-tag" href="https://blog.dich.bid/tags/linux/">#Linux</a></span>
|
||||
|
||||
</li>
|
||||
</ul>
|
||||
|
||||
</div>
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
<footer class="footer">
|
||||
<div class="footer__inner">
|
||||
<div class="copyright">
|
||||
<span>©
|
||||
2025
|
||||
Dichgrem</span>
|
||||
<span class="copyright-theme">
|
||||
<span class="copyright-theme-sep"> :: CC BY-SA 4.0 :: A friend comes from distant lands</span>
|
||||
</a>
|
||||
</span>
|
||||
</div>
|
||||
</div>
|
||||
</footer>
|
||||
|
||||
</div>
|
||||
</body>
|
||||
</html>
|
||||
|
||||
1398
public/atom.xml
Normal file
1398
public/atom.xml
Normal file
File diff suppressed because it is too large
Load Diff
405
public/awesome-android-root/index.html
Normal file
405
public/awesome-android-root/index.html
Normal file
@ -0,0 +1,405 @@
|
||||
<!DOCTYPE html>
|
||||
<html lang="en">
|
||||
|
||||
<head>
|
||||
<title>Dich'blog</title>
|
||||
|
||||
<meta http-equiv="content-type" content="text/html; charset=utf-8">
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1">
|
||||
<meta name="robots" content="noodp"/>
|
||||
|
||||
<link rel="stylesheet" href="https://blog.dich.bid/style.css">
|
||||
<link rel="stylesheet" href="https://blog.dich.bid/color/blue.css">
|
||||
|
||||
<link rel="stylesheet" href="https://blog.dich.bid/color/background_dark.css">
|
||||
|
||||
<link rel="stylesheet" href="https://blog.dich.bid/font-hack-subset.css">
|
||||
|
||||
<meta name="description" content="">
|
||||
|
||||
<meta property="og:description" content="">
|
||||
<meta property="og:title" content="Dich'blog">
|
||||
<meta property="og:type" content="article">
|
||||
<meta property="og:url" content="https://blog.dich.bid/awesome-android-root/">
|
||||
|
||||
<meta name="twitter:card" content="summary_large_image">
|
||||
<meta name="twitter:description" content="">
|
||||
<meta name="twitter:title" content="Dich'blog">
|
||||
<meta property="twitter:domain" content="blog.dich.bid">
|
||||
<meta property="twitter:url" content="https://blog.dich.bid/awesome-android-root/">
|
||||
|
||||
<link rel="alternate" type="application/atom+xml" title="Dich'blog Atom Feed" href="https://blog.dich.bid/atom.xml" />
|
||||
|
||||
|
||||
<link rel="icon" type="image/png" href=/dich.webp />
|
||||
|
||||
<!-- ✅ Added center alignment styles -->
|
||||
<style>
|
||||
.footer {
|
||||
text-align: center;
|
||||
padding: 1rem 0;
|
||||
}
|
||||
|
||||
.footer__inner {
|
||||
display: flex;
|
||||
justify-content: center;
|
||||
flex-direction: column;
|
||||
align-items: center;
|
||||
}
|
||||
|
||||
.copyright {
|
||||
text-align: center;
|
||||
}
|
||||
</style>
|
||||
</head>
|
||||
|
||||
<body class="">
|
||||
<div class="container">
|
||||
|
||||
<header class="header">
|
||||
<div class="header__inner">
|
||||
<div class="header__logo">
|
||||
|
||||
<a href="https://blog.dich.bid" style="text-decoration: none;">
|
||||
<div class="logo">
|
||||
|
||||
Dich'blog
|
||||
|
||||
</div>
|
||||
</a>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
|
||||
|
||||
<nav class="menu">
|
||||
<ul class="menu__inner">
|
||||
<li class="active"><a href="https://blog.dich.bid">blog</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/archive">archive</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/tags">tags</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/weekly">weekly</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/search">search</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/about">about me</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/links">links</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/atom.xml">rss</a></li>
|
||||
|
||||
<li><a href="https://github.com/Dichgrem" target="_blank" rel="noopener noreferrer">github</a></li>
|
||||
</ul>
|
||||
</nav>
|
||||
|
||||
|
||||
|
||||
</header>
|
||||
|
||||
|
||||
<div class="content">
|
||||
|
||||
<div class="post">
|
||||
|
||||
<h1 class="post-title"><a href="https://blog.dich.bid/awesome-android-root/">综合工程:安卓刷机与root教程</a></h1>
|
||||
<div class="post-meta-inline">
|
||||
|
||||
<span class="post-date">
|
||||
2023-08-13
|
||||
</span>
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
<span class="post-tags-inline">
|
||||
:: tags:
|
||||
<a class="post-tag" href="https://blog.dich.bid/tags/zong-he-gong-cheng/">#综合工程</a></span>
|
||||
|
||||
|
||||
<div class="post-content">
|
||||
<p>前言 自安卓系统诞生以来，root 一直是玩机的必备过程。时至今日，在安卓定制系统日益完善的情况下，能 root 的机型越来越少，本文以小米手机为例，介绍 root 的具体方法。</p>
|
||||
<span id="continue-reading"></span><h2 id="yi-shen-me-shi-root"><strong>一.什么是root</strong></h2>
|
||||
<p>这涉及安卓的权限系统。Andoird 系统是基于 Linux 内核的，Linux中的root用户为超级用户，<code>root 权限则为系统的最高权限</code>，与 Windows 的 system 权限相当（比 administer 还高）。日常使用中我们可以发现一般软件权限需要经过用户同意，即每次安装前出现的各种请求弹窗。我们看似可以做到许多事情，但有些地方比如安卓的根目录没有root就无法查看。</p>
|
||||
<p>所谓 Root 也就是使手机获得超级管理员的权限，但是出于种种原因，厂商默认不提供超级管理员的权限，因此，<code>root的本质就是一个提权的过程</code>。</p>
|
||||
<h2 id="er-wei-shen-me-yao-root"><strong>二.为什么要root</strong></h2>
|
||||
<ol>
|
||||
<li>
|
||||
<p>国内定制的安卓系统充满着云控，反诈以及各种广告，预装软件，这种系统实在为极客们所不容；而当我们具备了 root 权限后，就可以实现许多功能，例如屏蔽广告，虚拟定位，安装 Google 框架和软件，满血运行CPU，删除系统自带软件等等。</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>某种意义上不能root的手机相当于只有使用权而无所有权，不能完全控制自己的数据。</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>我可以不要但你厂商不能不给。</p>
|
||||
</li>
|
||||
</ol>
|
||||
<blockquote>
|
||||
<p>云控：一般指为了计划性报废而特地远程操控使用户的手机变的卡顿，加快换机；也有另一层含义：在UP主测试手机时调整设置使其跑分虚高而用户到手的手机分数远不如测试的时候的情况。</p>
|
||||
</blockquote>
|
||||
<blockquote>
|
||||
<p>反诈：一般指厂商与网络安全部门合作的后门或漏洞，可以监控用户行为，例如某
|
||||
“其他”品牌手机系统的webview级别的网址拦截；</p>
|
||||
</blockquote>
|
||||
<blockquote>
|
||||
<p>广告：一般指系统自带的弹窗广告，自带系统应用中的广告和“负一屏”中的广告。</p>
|
||||
</blockquote>
|
||||
<h2 id="san-na-xie-ji-xing-ke-yi-root"><strong>三.哪些机型可以root</strong></h2>
|
||||
<p>在 2023 年的今天，能 root 的机型还是比较少。<a href="https://github.com/KHwang9883/MobileModels/blob/master/misc/bootloader-kernel-source.md">各品牌手机root情况汇总</a></p>
|
||||
<table><thead><tr><th>品牌 / 机型</th><th>BL 解锁情况</th><th>等待时长</th><th>支持回锁</th><th>Root/越狱 能力</th></tr></thead><tbody>
|
||||
<tr><td>OnePlus</td><td>✅ 支持</td><td>秒解</td><td>✅ 支持</td><td>✅ 容易 root</td></tr>
|
||||
<tr><td>Google (Pixel)</td><td>✅ 支持</td><td>秒解</td><td>✅ 支持</td><td>✅ 容易 root</td></tr>
|
||||
<tr><td>Nothing Phone</td><td>ℹ️ 社区支持</td><td>—</td><td>—</td><td>✅ 社区方法多</td></tr>
|
||||
<tr><td>Motorola</td><td>✅ 支持</td><td>官方发解锁码</td><td>⚠️ 部分</td><td>✅ 社区方法多</td></tr>
|
||||
<tr><td>Xiaomi/Redmi/POCO</td><td>⚠️ 支持</td><td>~7–14 天</td><td>⏹ 部分</td><td>✅ 可 root（需等待）</td></tr>
|
||||
<tr><td>Lenovo</td><td>✅ 支持</td><td>秒解</td><td>⚠️ 部分</td><td>✅ 容易 root</td></tr>
|
||||
<tr><td>Sony</td><td>⚠️ 支持</td><td>—</td><td>⚠️ 部分</td><td>✅ 海外版易 root</td></tr>
|
||||
<tr><td>OPPO / Realme</td><td>⚠️ 支持</td><td>—</td><td>—</td><td>❌ 部分型号难 root</td></tr>
|
||||
<tr><td>Vivo / iQOO</td><td>⚠️ 支持</td><td>—</td><td>—</td><td>❌ 部分型号难 root</td></tr>
|
||||
<tr><td>Huawei</td><td>❌ 不支持</td><td>—</td><td>—</td><td>❌ 基本不可 root</td></tr>
|
||||
<tr><td>Honor</td><td>❌ 不支持</td><td>—</td><td>—</td><td>⚠️ 少数型号有社区支持</td></tr>
|
||||
<tr><td>ASUS</td><td>❌ 不支持</td><td>—</td><td>❌</td><td>❌ 不可 root</td></tr>
|
||||
<tr><td>Black Shark</td><td>❌ 不支持</td><td>—</td><td>—</td><td>❌ 不可 root</td></tr>
|
||||
<tr><td>LG</td><td>❌ 不支持</td><td>—</td><td>✅ 支持</td><td>⚠️ 旧机型可能可 root</td></tr>
|
||||
<tr><td>Meizu</td><td>❌ 不支持</td><td>—</td><td>—</td><td>⚠️ 部分机型有 root 方法</td></tr>
|
||||
<tr><td>Samsung</td><td>⚠️ 支持</td><td>—</td><td>—</td><td>❌ 解锁后 Knox 熔断，Pay 功能被禁用</td></tr>
|
||||
<tr><td>Apple iPhone</td><td>❌ 不支持</td><td>—</td><td>—</td><td>✅ iPhone 10 前可越狱</td></tr>
|
||||
</tbody></table>
|
||||
<p><code>刷机有风险，root 需谨慎</code>！刷机前要了解相应的厂商，考虑保修和变砖的问题！</p>
|
||||
<h2 id="si-que-ding-ni-yao-shua-de-xi-tong"><strong>四.确定你要刷的系统</strong></h2>
|
||||
<p>可以选择<code>官方原版，官改版，海外版和类原生版</code>。官方原版镜像一般用来救砖;官改版在一些方面例如性能更为强大;海外版本如EEA（欧盟版）为符合法规对隐私保护更好且广告更少；而类原生版是在AOSP的基础上进行简单修改，最为纯净原生。</p>
|
||||
<p>需要注意这些rom的搜索往往使用的海外名，得先搜索你所对应机型的海外名称/代号。</p>
|
||||
<ul>
|
||||
<li>
|
||||
<p><a href="https://mi.fiime.cn/Android">Android原生项目大全</a></p>
|
||||
</li>
|
||||
<li>
|
||||
<p><a href="https://miuiver.com/">小米各机型 MIUI 历史版本分类索引</a></p>
|
||||
</li>
|
||||
</ul>
|
||||
<blockquote>
|
||||
<p>需要注意的是刷类原生系统较之其他系统可能会有如下问题；如果你只需要root，推荐使用原厂系统。</p>
|
||||
</blockquote>
|
||||
<ul>
|
||||
<li>解锁BL之后Tee假死，无法使用指纹付款；</li>
|
||||
<li>由于原厂相机驱动不开源，相机变的模糊；</li>
|
||||
<li>部分机型无法快充；</li>
|
||||
<li>12306无法使用前置人脸识别；</li>
|
||||
<li>5G可能无法使用；</li>
|
||||
</ul>
|
||||
<h2 id="wu-ru-he-root"><strong>五.如何root</strong></h2>
|
||||
<p>首先我们要了解安卓系统的分区和启动。安卓的分区包括:</p>
|
||||
<ul>
|
||||
<li>
|
||||
<p><code>recovery 分区</code>，类似PC端的PE环境，手机上的恢复出厂设置即为从 recovery 恢复；</p>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>cache 分区</code>，保存系统最常访问的数据和应用程序。 擦除这个分区，不会影响个人数据，只是删除了这个分区中已经保存的缓存内容；</p>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>boot 分区</code>，类似PC端的MBR分区，用来引导系统启动，擦除后手机会卡在开机 logo 的界面；</p>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>system 分区</code>，包括操作系统与软件，vendor 定制文件与库文件等等，擦除后会卡在开机的动画界面；</p>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>data 分区</code>，存放用户数据和系统设置，擦除后不影响系统的运行。</p>
|
||||
</li>
|
||||
</ul>
|
||||
<blockquote>
|
||||
<p>除了以上5大分区外，手机启动阶段还存在名为 bootloader 的程序，通常位于设备的专用引导区域（如boot ROM或firmware分区的一部分），与 PC 端的 BIOS 类似，被称为 fastboot 模式，厂商一般会将其锁定，要刷机的话必须解开它。</p>
|
||||
</blockquote>
|
||||
<blockquote>
|
||||
<p>早些年间，存在大量一键 root，kingroot 之类的软件，可以直接刷写 root 包，获得 root 权限，但成功率不高，且有植入木马之嫌。</p>
|
||||
</blockquote>
|
||||
<p>因此，现在<strong>主流的刷机步骤</strong>为</p>
|
||||
<ul>
|
||||
<li>
|
||||
<p><code>备份手机数据</code>,即备份Data分区(可使用Neobackup或系统自带),字库/基带/官方固件,桌面样式截图以及该机器的官方原厂包；</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>打开机器上的<code>允许USB调试</code>;</p>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>解开 bootloader</code>，俗称解BL锁. <a href="https://telegra.ph/BL%E9%94%81%E7%9A%84%E5%8E%9F%E7%90%86%E6%98%AF%E4%BB%80%E4%B9%88-05-29">BL锁原理参考</a></p>
|
||||
</li>
|
||||
<li>
|
||||
<p>下载要刷的第三方系统包和原厂系统包并提取以上两个包中的 boot.img 和 recovery.img 文件;</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>将机器与PC等设备连接,并<code>进入 bootloader</code>;</p>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>刷入第三方 recovery</code>，比如大名鼎鼎的 TWRP,或者对应新系统的recovery.img；</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>进入 recovery 模式，清空原系统数据并刷入新系统Zip包,随后重启,即可进入新系统。</p>
|
||||
</li>
|
||||
</ul>
|
||||
<p><strong>主流的root步骤</strong>:</p>
|
||||
<ul>
|
||||
<li>Magisk:在recovery中<code>刷入 Magisk </code>(面具)zip包，随后重启进入桌面,安装 Magisk(apk),在其中选择直接安装；</li>
|
||||
<li>Apatch:安装apk软件并修补提取出来的boot.img,随后在fastboot模式中<code>fastboot flash boot apatch_patched-boot.img</code>，重启即可。</li>
|
||||
<li>KernelSU:修补init_boot.img或者刷入GKI内核修补，若官方无支持需要自行编译GKI内核。</li>
|
||||
</ul>
|
||||
<p><strong>常用root方案</strong></p>
|
||||
<ul>
|
||||
<li><a href="https://jesse205.github.io/MagiskChineseDocument/">Magisk</a></li>
|
||||
<li><a href="https://jesse205.github.io/MagiskChineseDocument/delta/main.html">Kitsune Mask</a></li>
|
||||
<li><a href="https://kernelsu.org/zh_CN/">KernelSU</a></li>
|
||||
<li><a href="https://rifsxd.github.io/KernelSU-Next/zh/index.html">KernelSU Next</a></li>
|
||||
<li><a href="https://apatch.dev/zh_CN/">APatch</a></li>
|
||||
</ul>
|
||||
<h2 id="liu-ju-ti-cao-zuo-liu-cheng"><strong>六.具体操作流程</strong></h2>
|
||||
<blockquote>
|
||||
<p>前置知识：ADB与Fastboot命令的使用</p>
|
||||
</blockquote>
|
||||
<p><strong>adb 命令</strong></p>
|
||||
<table><thead><tr><th>命令</th><th>说明</th></tr></thead><tbody>
|
||||
<tr><td><code>adb devices</code></td><td>列出 adb 设备</td></tr>
|
||||
<tr><td><code>adb reboot</code></td><td>重启设备</td></tr>
|
||||
<tr><td><code>adb reboot bootloader</code></td><td>重启到 fastboot 模式</td></tr>
|
||||
<tr><td><code>adb reboot recovery</code></td><td>重启到 recovery 模式</td></tr>
|
||||
<tr><td><code>adb reboot edl</code></td><td>重启到 edl 模式</td></tr>
|
||||
<tr><td><code>adb sideload <要刷写的文件路径></code></td><td>刷写模块，如 Magisk</td></tr>
|
||||
</tbody></table>
|
||||
<p><strong>fastboot 命令</strong></p>
|
||||
<table><thead><tr><th>命令</th><th>说明</th></tr></thead><tbody>
|
||||
<tr><td><code>fastboot devices</code></td><td>列出 fastboot 设备</td></tr>
|
||||
<tr><td><code>fastboot reboot</code></td><td>重启设备</td></tr>
|
||||
<tr><td><code>fastboot reboot-bootloader</code></td><td>重启到 fastboot 模式</td></tr>
|
||||
<tr><td><code>fastboot flash <分区名称> <镜像文件名></code></td><td>刷写分区</td></tr>
|
||||
<tr><td><code>fastboot oem reboot-<模式名称></code></td><td>重启到相应模式</td></tr>
|
||||
<tr><td><code>fastboot oem device-info</code></td><td>查看解锁状态</td></tr>
|
||||
</tbody></table>
|
||||
<blockquote>
|
||||
<p>以 Poco F2 这款手机为例，</p>
|
||||
</blockquote>
|
||||
<ol>
|
||||
<li>
|
||||
<p>首先我们进入手机设置界面，进入“我的设备”，在“全部参数”中找到“ MIUI 版本”，连续点击后开启开发者模式，随后在“更多设置”中开启 USB 调试， USB安装 功能。</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>然后我们进入<a href="https://www.miui.com/unlock/download.html">小米官网</a> ，下载官方解锁工具，需要登陆小米账号并等待7天，随后即可解锁。</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>解锁完成后在<a href="https://mifirm.net/downloadtwrp/148">MiFirm网</a> 中下载对应的 TWRP 版本。</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>随后用数据线连接手机，用其中的一键刷写刷入 TWRP；随后下载你要刷的系统的 rom 包，下载时注意一并下载 boot.img 文件，作为 Magisk 的修补用。然后下载 <a href="https://magisk.me/zip/">Magisk</a> 包，与 rom 一起存入TF卡或者U盘中。</p>
|
||||
</li>
|
||||
</ol>
|
||||
<blockquote>
|
||||
<p>注意，由于本机型为新型<a href="https://www.jianshu.com/p/b2726b304801"><strong>AB分区</strong></a>因此如果刷机失败，需要下载原厂包用以恢复AB分区，否则无法启动和安装rom。</p>
|
||||
</blockquote>
|
||||
<ol start="5">
|
||||
<li>
|
||||
<p>进入 recovery 模式，首先我们<code>清除Data、Cache两个分区</code>，俗称“双清”，随后在高级清除选项中<code>清除 Data、Cache、Dalvik Cache 和 System 分区</code>，俗称“四清”。</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>清除完成后即可开始刷机。将 TF 卡或者U盘插入手机，在“安装”中选择 rom 包，右滑确认刷机；随后如法炮制，刷入 magisk.zip 包，不然会卡在开机 logo 界面，俗称“卡米”。</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>刷完之后重启，则会进入安装界面。<strong>注意：如果刷的是海外版的包，千万不能联网安装，否则会失败且变为国内版。</strong></p>
|
||||
</li>
|
||||
<li>
|
||||
<p>此刻我们将下载好的 boot.img 文件复制到手机上，打开 Magisk 软件，在其中选择修补一个文件，选中 boot.img，修复完成后可以看到超级用户一栏可以使用了，说明 root 完成。</p>
|
||||
</li>
|
||||
</ol>
|
||||
<blockquote>
|
||||
<p>以一加（oneplus）为例：</p>
|
||||
</blockquote>
|
||||
<ol>
|
||||
<li>
|
||||
<p>打开开发者模式并开启USB调试，连接到提前装好ADB/Fastboot驱动的电脑；</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>随后进入fastboot模式（adb reboot bootloader），执行<code>fastboot oem unlock</code>或者<code>fastboot flashing unlock</code>，查看<code>fastboot oem device-info</code>，若为<code>Device unlocked: true</code>表示已成功解锁。</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>随后刷入新系统的recovery.img,使用命令<code>fastboot flash recovery xxx.img</code>；四清操作可以用<code>fastboot erase data / fastboot erase cache / fastboot erase system / fastboot erase metadata</code> 代替。</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>随后进入新系统的recovery，使用命令<code>fastboot reboot recovery</code>，在其中<code>adb sideload xxx.zip</code>,即为刷入新系统的全量包。</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>随后 <code>adb reboot</code> 即可进入新系统。</p>
|
||||
</li>
|
||||
</ol>
|
||||
<blockquote>
|
||||
<p>如果你不想安装TWRP也可以直接安装要刷的系统的recovery，一般放在系统zip包的中，如果没有则需要手动解包payload.bin，可以安装payload-dumper-go并在解压出来的系统文件夹中使用<code>payload-dumper-go payload.bin</code>，随后会将所有.img后缀的文件放在文件夹中。</p>
|
||||
</blockquote>
|
||||
<h2 id="ba-roothou-de-mo-kuai-an-zhuang"><strong>八.Root后的模块安装</strong></h2>
|
||||
<p>在 Root 管理器中安装 Zygisk-Lsposed 模块,即可使用 Lsposed，在 Lsposed 中可以安装 HMA, Amarok ，QAuxiliary 模块，并配合 MMRL 等软件等等。</p>
|
||||
<blockquote>
|
||||
<p>免 Root 的平替方法,目前这一套流程也很成熟了:利用 ADB 权限的 Shizuku;利用 Device Owner 权限的 Dhizuku等等。</p>
|
||||
</blockquote>
|
||||
<blockquote>
|
||||
<p>常用模块</p>
|
||||
</blockquote>
|
||||
<ul>
|
||||
<li><a href="https://github.com/mywalkb/LSPosed_mod">LSPosed</a></li>
|
||||
<li><a href="https://github.com/MhmRdd/NoHello">NoHello</a></li>
|
||||
<li><a href="https://github.com/thelordalex/WAHideBootloader">WAHideBootloader</a></li>
|
||||
<li><a href="https://github.com/Dr-TSNG/ZygiskNext">ZygiskNext</a></li>
|
||||
<li><a href="https://github.com/snake-4/Zygisk-Assistant">Zygisk-Assistant</a></li>
|
||||
</ul>
|
||||
<h2 id="can-kao"><strong>参考</strong></h2>
|
||||
<ul>
|
||||
<li><a href="https://download.lineageos.org/devices/lmi/builds">lineageos镜像</a></li>
|
||||
<li><a href="https://wiki.lineageos.org/devices/lmi/install/variant1/">lineageos教程</a></li>
|
||||
<li><a href="https://wiki.lineageos.org/devices/lmi/variant2/">机型介绍</a></li>
|
||||
<li><a href="https://xdaforums.com/t/no-sound-issue-can-u-help.4479225/">XDA-没有声音的问题解决</a></li>
|
||||
<li><a href="https://xdaforums.com/t/kernel-overclocked-no-gravity-2023-08-28-protonclang.4531497/">XDA-更换内核</a></li>
|
||||
</ul>
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
<div class="pagination">
|
||||
<div class="pagination__title">
|
||||
<span class="pagination__title-h">Thanks for reading! Read other posts?</span>
|
||||
<hr />
|
||||
</div>
|
||||
<div class="pagination__buttons">
|
||||
<span class="button previous">
|
||||
<a href="https://blog.dich.bid/awesome-openwrt/">
|
||||
<span class="button__icon">←</span>
|
||||
<span class="button__text">综合工程:OpenWrt路由部署与软件编译</span>
|
||||
</a>
|
||||
</span>
|
||||
|
||||
|
||||
<span class="button next">
|
||||
<a href="https://blog.dich.bid/awesome-android-tv/">
|
||||
<span class="button__text">综合工程:Android-TV 折腾小记</span>
|
||||
<span class="button__icon">→</span>
|
||||
</a>
|
||||
</span>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
</div>
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
<footer class="footer">
|
||||
<div class="footer__inner">
|
||||
<div class="copyright">
|
||||
<span>©
|
||||
2025
|
||||
Dichgrem</span>
|
||||
<span class="copyright-theme">
|
||||
<span class="copyright-theme-sep"> :: CC BY-SA 4.0 :: A friend comes from distant lands</span>
|
||||
</a>
|
||||
</span>
|
||||
</div>
|
||||
</div>
|
||||
</footer>
|
||||
|
||||
</div>
|
||||
</body>
|
||||
</html>
|
||||
|
||||
316
public/awesome-android-tv/index.html
Normal file
316
public/awesome-android-tv/index.html
Normal file
@ -0,0 +1,316 @@
|
||||
<!DOCTYPE html>
|
||||
<html lang="en">
|
||||
|
||||
<head>
|
||||
<title>Dich'blog</title>
|
||||
|
||||
<meta http-equiv="content-type" content="text/html; charset=utf-8">
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1">
|
||||
<meta name="robots" content="noodp"/>
|
||||
|
||||
<link rel="stylesheet" href="https://blog.dich.bid/style.css">
|
||||
<link rel="stylesheet" href="https://blog.dich.bid/color/blue.css">
|
||||
|
||||
<link rel="stylesheet" href="https://blog.dich.bid/color/background_dark.css">
|
||||
|
||||
<link rel="stylesheet" href="https://blog.dich.bid/font-hack-subset.css">
|
||||
|
||||
<meta name="description" content="">
|
||||
|
||||
<meta property="og:description" content="">
|
||||
<meta property="og:title" content="Dich'blog">
|
||||
<meta property="og:type" content="article">
|
||||
<meta property="og:url" content="https://blog.dich.bid/awesome-android-tv/">
|
||||
|
||||
<meta name="twitter:card" content="summary_large_image">
|
||||
<meta name="twitter:description" content="">
|
||||
<meta name="twitter:title" content="Dich'blog">
|
||||
<meta property="twitter:domain" content="blog.dich.bid">
|
||||
<meta property="twitter:url" content="https://blog.dich.bid/awesome-android-tv/">
|
||||
|
||||
<link rel="alternate" type="application/atom+xml" title="Dich'blog Atom Feed" href="https://blog.dich.bid/atom.xml" />
|
||||
|
||||
|
||||
<link rel="icon" type="image/png" href=/dich.webp />
|
||||
|
||||
<!-- ✅ Added center alignment styles -->
|
||||
<style>
|
||||
.footer {
|
||||
text-align: center;
|
||||
padding: 1rem 0;
|
||||
}
|
||||
|
||||
.footer__inner {
|
||||
display: flex;
|
||||
justify-content: center;
|
||||
flex-direction: column;
|
||||
align-items: center;
|
||||
}
|
||||
|
||||
.copyright {
|
||||
text-align: center;
|
||||
}
|
||||
</style>
|
||||
</head>
|
||||
|
||||
<body class="">
|
||||
<div class="container">
|
||||
|
||||
<header class="header">
|
||||
<div class="header__inner">
|
||||
<div class="header__logo">
|
||||
|
||||
<a href="https://blog.dich.bid" style="text-decoration: none;">
|
||||
<div class="logo">
|
||||
|
||||
Dich'blog
|
||||
|
||||
</div>
|
||||
</a>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
|
||||
|
||||
<nav class="menu">
|
||||
<ul class="menu__inner">
|
||||
<li class="active"><a href="https://blog.dich.bid">blog</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/archive">archive</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/tags">tags</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/weekly">weekly</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/search">search</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/about">about me</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/links">links</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/atom.xml">rss</a></li>
|
||||
|
||||
<li><a href="https://github.com/Dichgrem" target="_blank" rel="noopener noreferrer">github</a></li>
|
||||
</ul>
|
||||
</nav>
|
||||
|
||||
|
||||
|
||||
</header>
|
||||
|
||||
|
||||
<div class="content">
|
||||
|
||||
<div class="post">
|
||||
|
||||
<h1 class="post-title"><a href="https://blog.dich.bid/awesome-android-tv/">综合工程:Android-TV 折腾小记</a></h1>
|
||||
<div class="post-meta-inline">
|
||||
|
||||
<span class="post-date">
|
||||
2023-08-14
|
||||
</span>
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
<span class="post-tags-inline">
|
||||
:: tags:
|
||||
<a class="post-tag" href="https://blog.dich.bid/tags/zong-he-gong-cheng/">#综合工程</a></span>
|
||||
|
||||
|
||||
<div class="post-content">
|
||||
<p>前言 由于 AppleTV 的高昂的售价和普通电视盒子广告的泛滥，一台开源、多功能的原生安卓电视盒子逐渐成为智能家居的必备神器。出于对 IPTV、YouTube 和家庭影院等需求，以及对一面赏心悦目电视墙的期待，这里分享 Android TV （以下简称ATV）安装的一些要点。</p>
|
||||
<span id="continue-reading"></span><h2 id="ling-yao-shi-xian-de-mu-biao">零.要实现的目标</h2>
|
||||
<ul>
|
||||
<li>实现自己的设备(X86/Arm)上安装TV系统；</li>
|
||||
<li>实现<strong>无开机广告和内置广告</strong>；</li>
|
||||
<li>实现<strong>海报墙效果</strong>（矩形磁帖），或自定义安卓桌面启动器；</li>
|
||||
<li>实现<strong>影视番剧观看</strong>，基于TVbox/Kodi/Kazumi；</li>
|
||||
<li>实现<strong>国内流媒体观看</strong>，包括Bilibili，爱优腾等等；</li>
|
||||
<li>实现<strong>国外流媒体观看</strong>，包括Netflix，YouTube，Disney+，Spotify等等；</li>
|
||||
<li>实现<strong>家庭影院</strong>，Emby类软件自动刮削；</li>
|
||||
<li>实现<strong>IPTV</strong>观看，采用自抓取源或者公共源；</li>
|
||||
<li>实现<strong>复古游戏</strong>游玩，包括GBA/FC等等，基于RetroArch/PPSSPP/Emuelec,可以连接手柄；</li>
|
||||
<li>实现<strong>游戏主机串流</strong>，包括PS/Xbox/Switch等等；</li>
|
||||
</ul>
|
||||
<h2 id="yi-xuan-ze-he-gua-de-ping-tai">一.选择合适的平台</h2>
|
||||
<p>X86还是Arm？两者之间各有优点，截止到今天各种Arm电视盒子已经非常成熟，价格便宜，也可以使用运营商的电视盒子进行刷机，性能并不会太弱；而X86平台往往价格偏贵，且解码性能和功能适配没有和电视生态联系紧密，因此建议首选Arm平台。</p>
|
||||
<h2 id="er-xuan-ze-he-gua-de-xi-tong">二.选择合适的系统</h2>
|
||||
<p>无论是运营商自带的电视盒子还是各种所谓的“无广告”电视盒子，往往都基于以下两种系统，且不要迷信所谓的“无广告”电视盒子，它们往往配置低下，性价比不高且还是有内置付费项目，甚至有一些根本没有做到去广告。</p>
|
||||
<table><thead><tr><th>特性</th><th><strong>Android-x86</strong></th><th><strong>Android TV</strong></th></tr></thead><tbody>
|
||||
<tr><td><strong>目标用户</strong></td><td>面向 PC 用户，将 Android 运行在 x86/x86_64 设备上。</td><td>面向电视和机顶盒用户，优化用于遥控器或语音操作。</td></tr>
|
||||
<tr><td><strong>适配设备</strong></td><td>传统 PC、笔记本、平板电脑等 x86 架构设备。</td><td>智能电视、电视盒子等 ARM 或特定芯片架构设备。</td></tr>
|
||||
<tr><td><strong>界面设计</strong></td><td>和标准 Android 类似，为触摸屏和鼠标键盘优化。</td><td>专为大屏设计，使用 Leanback UI，适配遥控器操作。</td></tr>
|
||||
<tr><td><strong>Google 服务</strong></td><td>默认不包含 Google 服务，需要用户手动安装。</td><td>官方版本内置 Google 服务（例如 Play Store、Assistant）。</td></tr>
|
||||
<tr><td><strong>开机启动器</strong></td><td>使用标准 Android 桌面启动器（Launcher3）。</td><td>使用电视优化的启动器（Leanback Launcher）。</td></tr>
|
||||
<tr><td><strong>架构支持</strong></td><td>专注于 <strong>x86/x86_64</strong>，但支持 ARM 仿真（通过 Houdini）。</td><td>主要支持 <strong>ARM/ARM64</strong> 架构，有限支持 x86。</td></tr>
|
||||
<tr><td><strong>硬件支持</strong></td><td>需要额外优化，部分硬件（如 GPU 驱动）可能无法正常工作。</td><td>深度集成硬件，默认支持电视硬件（如 HDMI CEC、音频输出）。</td></tr>
|
||||
<tr><td><strong>应用市场</strong></td><td>默认不内置 Google Play，需要手动安装 Aurora Store 等替代方案。</td><td>默认集成 Google Play 商店，提供大屏优化的应用程序。</td></tr>
|
||||
<tr><td><strong>遥控器支持</strong></td><td>不适配遥控器，主要使用鼠标键盘操作。</td><td>专为遥控器优化，支持按键导航和语音输入。</td></tr>
|
||||
<tr><td><strong>开源贡献</strong></td><td>由社区维护，支持各种自定义和实验功能。</td><td>由 Google 官方主导，OEM 厂商提供硬件优化支持。</td></tr>
|
||||
</tbody></table>
|
||||
<hr />
|
||||
<blockquote>
|
||||
<p>Android-x86 的安装类似windows，需要命令行界面配置；Android TV安装类似 Android手机，通过刷分区或TWRP卡刷安装。</p>
|
||||
</blockquote>
|
||||
<blockquote>
|
||||
<p>Tosathony 制作的 Android TV x86 是一个由社区成员制作的定制化 Android TV 版本,针对 Android TV 的大屏界面 和 遥控器操作 进行特别优化,但某些硬件（如 Wi-Fi、GPU、音频设备等）的驱动可能不兼容或需要额外的配置。</p>
|
||||
</blockquote>
|
||||
<p><strong>刷 Tosathony Android TV X86 准备工作</strong>：</p>
|
||||
<ul>
|
||||
<li>
|
||||
<p>1.<a href="https://pan.baidu.com/s/17eDDrf4WzWVmrc9hLw-c_w?pwd=a728">Tosathony 制作的 Android TV x86 9.0</a></p>
|
||||
</li>
|
||||
<li>
|
||||
<p>2.<a href="https://www.423down.com/10080.html">Rufus 写盘工具</a></p>
|
||||
</li>
|
||||
<li>
|
||||
<p>3.<a href="https://android-tv-remote-control.en.softonic.com/android">Android tv Remote 手机遥控器软件：</a></p>
|
||||
</li>
|
||||
<li>
|
||||
<p>4.<a href="https://androidmtk.com/tiny-adb-and-fastboot-tool#installer">Tiny ADB 软件</a></p>
|
||||
</li>
|
||||
</ul>
|
||||
<p><strong>一些可安装的软件</strong>：</p>
|
||||
<ul>
|
||||
<li>
|
||||
<p><a href="http://www.kodiplayer.cn/">kodi</a></p>
|
||||
</li>
|
||||
<li>
|
||||
<p><a href="https://www.dangbei.com/apps/">当贝市场</a></p>
|
||||
</li>
|
||||
<li>
|
||||
<p><a href="https://www.fenxm.com/104.html">哔哩哔哩TV版</a></p>
|
||||
</li>
|
||||
<li>
|
||||
<p><a href="https://www.fenxm.com/592.html">ATV Launcher</a></p>
|
||||
</li>
|
||||
</ul>
|
||||
<h2 id="yi-xie-pan-biosqi-dong">一、写盘，BIOS启动</h2>
|
||||
<ul>
|
||||
<li>
|
||||
<p>使用 Rufus 将下载好的 ATV 镜像写入U盘。</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>将U盘插到目标主机上，并设置 BIOS-boot 优先启动，不同设备进入 BIOS 的按键不同，大部分是F2或者DEL；</p>
|
||||
</li>
|
||||
</ul>
|
||||
<h2 id="er-kai-shi-an-zhuang">二、开始安装</h2>
|
||||
<ul>
|
||||
<li>
|
||||
<p>boot 成功后选择自动安装；</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>经过跑码后进入若干个选项，一路 yes 过去，文件系统选 ext4;随后运行 ATV ，并拔出U盘；</p>
|
||||
</li>
|
||||
</ul>
|
||||
<h2 id="san-jin-ru-googlejie-mian">三、进入Google界面</h2>
|
||||
<p>由于国内网络环境问题，导致一些界面无法进入，可使用如下方法或全局科学。</p>
|
||||
<p>1.如果卡在 Google的logo 界面或者动画比较缓慢，或者重启后无法进入 ATV 界面，需要在<code>BIOS-Advanced-OS selection</code>中将其设置为Windows 8.X或者Android。</p>
|
||||
<p>2.然后可以看到 PayPal 界面，这里使用可以 <code>Ctrl+Alt+F1</code> 进入命令行界面，随后输入</p>
|
||||
<p><code>pm disable com.tosanthony.tv.networkprovider #注意空格</code></p>
|
||||
<p>回车执行，随后按<code>Ctrl+Alt+F7或F8</code>回到图形界面。</p>
|
||||
<p>3.下一步，我们可以看到自动更新界面，这里我们需要禁用它：</p>
|
||||
<p>同样<code>Ctrl+Alt+F1</code> 进入命令行界面，随后输入</p>
|
||||
<p><code>pm disable com.google.android.tungsten.setupwraith #注意空格</code></p>
|
||||
<p>回车执行，随后按<code>Ctrl+Alt+F7或F8</code>回到图形界面。</p>
|
||||
<p>4.此时会进入一个 WiFi 界面，如果你是使用网线直连就没有问题，或者用键盘连接家里的WiFi，作者因为工控机没有WiFi模块在这里卡了半天。</p>
|
||||
<p>5.随后进入了 AndroidTV 的桌面。</p>
|
||||
<h2 id="si-an-zhuang-ruan-jian-bing-she-zhi-zhuo-mian-qi-dong">四、安装软件并设置桌面启动</h2>
|
||||
<p>1.首先我们在设置中找到“设置”>“设备首选项”>“关于”，然后在“构建”上点击几次以解锁“开发人员”选项，随后开启USB调试开关。</p>
|
||||
<p>2.随后在设置 > 设备首选项 > 关于 > 状态中找到并记下IP 地址，然后用Tiny ADB连接上去，这里使用命令<code>adb connect <IP 地址> </code>，随后在ATV端授权连接；</p>
|
||||
<p>3.接着使用命令adb install <path to android app.apk>将要安装的软件包上传，也可以将文件拖到命令提示符窗口上以复制其路径，回车确认。</p>
|
||||
<p><strong>一些 ADB 常用命令</strong>：</p>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>adb reboot #将重启 Android 设备。
|
||||
</span><span>
|
||||
</span><span>adb reboot recovery #将设备重新启动到恢复模式。
|
||||
</span><span>
|
||||
</span><span>adb push <local> <remote> #将文件从您的 PC 复制到您的 Android 设备。
|
||||
</span><span>
|
||||
</span><span>adb shell wm density <dpi> #改变显示器的像素密度。
|
||||
</span><span>
|
||||
</span><span>adb kill server #切断 PC 和 Android TV 之间的连接。
|
||||
</span></code></pre>
|
||||
<p>4.如果存在一些软件无法安装，可开启ARM兼容层，具体方法为在 <code>dl.android-x86.org/houdini/9_y/houdini.sfs</code> 中下载得到<code>houdini.sfs</code>，把文件名改成<code>houdini9_y.sfs</code>，随后拷贝进U盘，进入命令行界面，输入 <code>ls</code> 找到 storage 目录，输入 <code>cd storage</code> 进入你的U盘，输入 <code>ls</code> ，查看你拷贝的 <code>houdini9_y.sfs</code> 文件，并复制到该目录下。</p>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>cp houdini9_y.sfs /system/etc
|
||||
</span><span>
|
||||
</span><span>enable_nativebridge
|
||||
</span><span>
|
||||
</span><span>reboot
|
||||
</span></code></pre>
|
||||
<p>5.安装一些软件包后我们发现需要代替掉ATV自带的桌面，从而形成海报墙的效果，这和 linux 的桌面环境切换有异曲同工之处。注意：替换前需要已经安装完成其他桌面！！！！（比如 ATV Launcher ）我们使用以下命令禁用 google 默认的桌面。随后重启，即可看到ATV的海报墙。</p>
|
||||
<p><code>pm disable-user --user 0 com.google.android.tvlauncher </code></p>
|
||||
<p>恢复原有桌面：</p>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>C:\Users\root>adb shell
|
||||
</span><span>generic_x86:/ $ su
|
||||
</span><span>generic_x86:/ # pm enable --user 0 com.google.android.tvlauncher
|
||||
</span><span>Package com.google.android.tvlauncher new state: enabled
|
||||
</span></code></pre>
|
||||
<h2 id="hou-ji">后记</h2>
|
||||
<ul>
|
||||
<li>
|
||||
<p><a href="https://github.com/googlesamples/leanback-showcase">Android TV google 官方 TV 库</a></p>
|
||||
</li>
|
||||
<li>
|
||||
<p><a href="https://github.com/boxmate/tvframe">智能电视，电视盒子开发 SDK</a></p>
|
||||
</li>
|
||||
<li>
|
||||
<p><a href="https://github.com/EZJasonBoy/FocusChangeAnimation">选中框切换动画，适用于电视</a></p>
|
||||
</li>
|
||||
<li>
|
||||
<p><a href="https://github.com/FrozenFreeFall/Android-tv-widget">Android tv，盒子，投影仪 控件</a></p>
|
||||
</li>
|
||||
<li>
|
||||
<p><a href="https://github.com/genius158/TVProjectUtils">TV 项目常用工具(焦点问题，适配问题等.)</a></p>
|
||||
</li>
|
||||
</ul>
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
<div class="pagination">
|
||||
<div class="pagination__title">
|
||||
<span class="pagination__title-h">Thanks for reading! Read other posts?</span>
|
||||
<hr />
|
||||
</div>
|
||||
<div class="pagination__buttons">
|
||||
<span class="button previous">
|
||||
<a href="https://blog.dich.bid/awesome-android-root/">
|
||||
<span class="button__icon">←</span>
|
||||
<span class="button__text">综合工程:安卓刷机与root教程</span>
|
||||
</a>
|
||||
</span>
|
||||
|
||||
|
||||
<span class="button next">
|
||||
<a href="https://blog.dich.bid/awesome-arch-linux/">
|
||||
<span class="button__text">综合工程:Arch-linux 安装与配置</span>
|
||||
<span class="button__icon">→</span>
|
||||
</a>
|
||||
</span>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
</div>
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
<footer class="footer">
|
||||
<div class="footer__inner">
|
||||
<div class="copyright">
|
||||
<span>©
|
||||
2025
|
||||
Dichgrem</span>
|
||||
<span class="copyright-theme">
|
||||
<span class="copyright-theme-sep"> :: CC BY-SA 4.0 :: A friend comes from distant lands</span>
|
||||
</a>
|
||||
</span>
|
||||
</div>
|
||||
</div>
|
||||
</footer>
|
||||
|
||||
</div>
|
||||
</body>
|
||||
</html>
|
||||
|
||||
447
public/awesome-arch-linux/index.html
Normal file
447
public/awesome-arch-linux/index.html
Normal file
@ -0,0 +1,447 @@
|
||||
<!DOCTYPE html>
|
||||
<html lang="en">
|
||||
|
||||
<head>
|
||||
<title>Dich'blog</title>
|
||||
|
||||
<meta http-equiv="content-type" content="text/html; charset=utf-8">
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1">
|
||||
<meta name="robots" content="noodp"/>
|
||||
|
||||
<link rel="stylesheet" href="https://blog.dich.bid/style.css">
|
||||
<link rel="stylesheet" href="https://blog.dich.bid/color/blue.css">
|
||||
|
||||
<link rel="stylesheet" href="https://blog.dich.bid/color/background_dark.css">
|
||||
|
||||
<link rel="stylesheet" href="https://blog.dich.bid/font-hack-subset.css">
|
||||
|
||||
<meta name="description" content="">
|
||||
|
||||
<meta property="og:description" content="">
|
||||
<meta property="og:title" content="Dich'blog">
|
||||
<meta property="og:type" content="article">
|
||||
<meta property="og:url" content="https://blog.dich.bid/awesome-arch-linux/">
|
||||
|
||||
<meta name="twitter:card" content="summary_large_image">
|
||||
<meta name="twitter:description" content="">
|
||||
<meta name="twitter:title" content="Dich'blog">
|
||||
<meta property="twitter:domain" content="blog.dich.bid">
|
||||
<meta property="twitter:url" content="https://blog.dich.bid/awesome-arch-linux/">
|
||||
|
||||
<link rel="alternate" type="application/atom+xml" title="Dich'blog Atom Feed" href="https://blog.dich.bid/atom.xml" />
|
||||
|
||||
|
||||
<link rel="icon" type="image/png" href=/dich.webp />
|
||||
|
||||
<!-- ✅ Added center alignment styles -->
|
||||
<style>
|
||||
.footer {
|
||||
text-align: center;
|
||||
padding: 1rem 0;
|
||||
}
|
||||
|
||||
.footer__inner {
|
||||
display: flex;
|
||||
justify-content: center;
|
||||
flex-direction: column;
|
||||
align-items: center;
|
||||
}
|
||||
|
||||
.copyright {
|
||||
text-align: center;
|
||||
}
|
||||
</style>
|
||||
</head>
|
||||
|
||||
<body class="">
|
||||
<div class="container">
|
||||
|
||||
<header class="header">
|
||||
<div class="header__inner">
|
||||
<div class="header__logo">
|
||||
|
||||
<a href="https://blog.dich.bid" style="text-decoration: none;">
|
||||
<div class="logo">
|
||||
|
||||
Dich'blog
|
||||
|
||||
</div>
|
||||
</a>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
|
||||
|
||||
<nav class="menu">
|
||||
<ul class="menu__inner">
|
||||
<li class="active"><a href="https://blog.dich.bid">blog</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/archive">archive</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/tags">tags</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/weekly">weekly</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/search">search</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/about">about me</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/links">links</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/atom.xml">rss</a></li>
|
||||
|
||||
<li><a href="https://github.com/Dichgrem" target="_blank" rel="noopener noreferrer">github</a></li>
|
||||
</ul>
|
||||
</nav>
|
||||
|
||||
|
||||
|
||||
</header>
|
||||
|
||||
|
||||
<div class="content">
|
||||
|
||||
<div class="post">
|
||||
|
||||
<h1 class="post-title"><a href="https://blog.dich.bid/awesome-arch-linux/">综合工程:Arch-linux 安装与配置</a></h1>
|
||||
<div class="post-meta-inline">
|
||||
|
||||
<span class="post-date">
|
||||
2023-08-16
|
||||
</span>
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
<span class="post-tags-inline">
|
||||
:: tags:
|
||||
<a class="post-tag" href="https://blog.dich.bid/tags/zong-he-gong-cheng/">#综合工程</a></span>
|
||||
|
||||
|
||||
<div class="post-content">
|
||||
<p>前言 Arch linux是一个轻量、灵活、滚动更新的 Linux 发行版，衍生了诸多优秀的桌面端linux。其官方Wiki更是被称为技术界的“武林秘籍”；这里介绍其安装与使用。</p>
|
||||
<span id="continue-reading"></span><h2 id="an-zhuang">安装</h2>
|
||||
<p>一般而言有以下几种安装方法：</p>
|
||||
<ul>
|
||||
<li>原版 Arch linux 的命令行安装；</li>
|
||||
<li>原版 Arch linux 的脚本安装；</li>
|
||||
<li>第三方发行版的图形界面安装。</li>
|
||||
</ul>
|
||||
<p>前两种方法较为繁琐，这里说明第三种方法：常见的Arch发行版有Garuda，Cachyos以及EndeavourOS等等。</p>
|
||||
<ul>
|
||||
<li><a href="https://cachyos.org/download/">Cachyos下载</a></li>
|
||||
<li><a href="https://garudalinux.org/editions">Garuda下载</a></li>
|
||||
<li><a href="https://endeavouros.com/">EndeavourOS下载</a></li>
|
||||
</ul>
|
||||
<p>安装方法同ubuntu一样，是基于Calamares的图形化界面安装。一般步骤为<code>选择语言（American English）--选择键盘/时区（默认/shanghai）--选择分区（xfs抹除全盘，可选全盘加密）--选择桌面环境（Gnome或KDE）--确认安装。</code></p>
|
||||
<h2 id="an-zhuang-ruan-jian">安装软件</h2>
|
||||
<p>随后安装常用开源软件：</p>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span># gui
|
||||
</span><span>
|
||||
</span><span>paru -S alacritty zellij qemu-full virt-manager wireshark-qt floorp-bin foliate materialgram-bin legcord-bin keepassxc onlyoffice-bin kazumi-bin vlc krita qtscrcpy localsend-bin strawberry oculante obs-studio
|
||||
</span><span>
|
||||
</span><span># tui
|
||||
</span><span>
|
||||
</span><span>paru -S neovim yazi lazygit btop
|
||||
</span><span>
|
||||
</span><span># cli
|
||||
</span><span>
|
||||
</span><span>paru -S nexttrace-bin android-tools syncthing aria2 zola fastfetch onefetch starship atuin bat fzf eza tree
|
||||
</span><span>
|
||||
</span><span># other
|
||||
</span><span>
|
||||
</span><span>paru -S ttf-jetbrains-mono-nerd fcitx5-chinese-addons fcitx5-skin-material fcitx5-im fcitx5-rime npm pnpm just go wl-clipboard
|
||||
</span></code></pre>
|
||||
<p>安装完毕后我们开始配置输入法与字体：</p>
|
||||
<p>输入法我们采用雾凇拼音，即前面我们安装的fcitx5系列软件包的一个输入方案，这里我们使用<a href="https://github.com/Mark24Code/rime-auto-deploy">自动部署脚本</a>：</p>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span># step1: 克隆/下载 latest 最新的稳定版到本地
|
||||
</span><span>git clone --depth=1 https://github.com/Mark24Code/rime-auto-deploy.git --branch latest
|
||||
</span><span># step2: 进入项目目录
|
||||
</span><span>cd rime-auto-deploy
|
||||
</span><span># step3: 执行部署脚本
|
||||
</span><span>./installer.rb
|
||||
</span></code></pre>
|
||||
<p>选择部署fcitx5即可，随后在设置的Input Method中Add Input Method ，选择Rime，随后默认按Ctrl+Space即可切换中文。</p>
|
||||
<p>字体的配置在<a href="https://blog.dich.bid/learn-linux-for-pc-7/">Linux之旅(七):系统与终端字体设置</a>这一期说过，这里不再赘述。缺少的字体可以通过paru下载或者到<a href="https://www.miao3.cn/">喵闪字库</a>下载ttf并安装。</p>
|
||||
<h2 id="tu-xing-mei-hua">图形美化</h2>
|
||||
<p>安装完毕后可以看到KDE的界面较为简陋，这里给出笔者的美化配置：</p>
|
||||
<ul>
|
||||
<li>在设置中找到Colors&Themes，分别设置为：</li>
|
||||
</ul>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>- Color：Breeze Dark
|
||||
</span><span>- Application Style：Breeze
|
||||
</span><span>- Plasma Style：Sweet
|
||||
</span><span>- Window Decorations：Edna
|
||||
</span><span>- Icons：BeautySolar
|
||||
</span><span>- Cursors：Afterglow Cursors
|
||||
</span><span>- Splash Screen：None
|
||||
</span></code></pre>
|
||||
<ul>
|
||||
<li>
|
||||
<p>随后设置壁纸，这里给出了笔者收藏的<a href="https://github.com/Dichgrem/wallpaper.git">壁纸</a>。</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>设置完成后将Dock栏的Status全部隐藏，删除间隔与空隙，删除时间，更改Memu图标，随后固定常用软件到其上。</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>随后在Dock栏下新建一个空白栏，结构为数字时钟加两个空白，字体为JetBrains Mono，24小时ISO格式。最终效果如下：</p>
|
||||
</li>
|
||||
</ul>
|
||||
<p><img src="/images/desktop.png" alt="desktop" /></p>
|
||||
<h2 id="qian-yi-shu-ju">迁移数据</h2>
|
||||
<p>将需要的数据迁移到Home目录下，对笔者来说是用来同步的Data文件夹以及Git工作文件夹。随后Add to Places将其固定到侧边栏，开启隐藏文件可见，将View mode改为Detail。最终效果如下：</p>
|
||||
<p><img src="/images/file.png" alt="file" /></p>
|
||||
<h2 id="she-zhi-ruan-jian">设置软件</h2>
|
||||
<ul>
|
||||
<li>配置fastfetch显示效果</li>
|
||||
</ul>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>创建配置目录：mkdir -p ~/.config/fastfetch
|
||||
</span><span>创建配置文件：touch ~/.config/fastfetch/config.jsonc
|
||||
</span><span>编辑该文件以添加你的自定义选项
|
||||
</span></code></pre>
|
||||
<ul>
|
||||
<li>
|
||||
<p>设置GFS：参考<a href="https://blog.dich.bid/about-gfs/">乱七八糟:GFS项目考量笔记 </a>。</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>设置Keepassxc/Vscodium/Electerm：导入备份好的配置文件。</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>设置Matrix/Telegram：登录并在另一台设备上验证。</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>设置浏览器：导入书签备份文件（有图标）；定制工具栏，下载扩展插件，包括：</p>
|
||||
</li>
|
||||
</ul>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>Dark Reader（暗黑模式）
|
||||
</span><span>kiss-translator（翻译工具）
|
||||
</span><span>uBlock Origin（广告拦截）
|
||||
</span><span>ClearURLs（去跟踪链接）
|
||||
</span><span>KeePassXC-Browser（链接Keepass）
|
||||
</span><span>BookmarkHub（书签同步）
|
||||
</span><span>BewlyBewly（B站美化）
|
||||
</span><span>V2EX Polish（V站美化）
|
||||
</span></code></pre>
|
||||
<h2 id="shuang-xi-tong-tian-jia-windowsyin-dao">双系统添加Windows引导</h2>
|
||||
<p>如果Grub引导菜单中没有windows选项，可以通过以下方法添加：</p>
|
||||
<ul>
|
||||
<li>安装 os-prober：首先确保系统中安装了 os-prober，这是一个用于检测其他操作系统的工具。</li>
|
||||
</ul>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>sudo pacman -S os-prober
|
||||
</span><span>sudo os-prober
|
||||
</span></code></pre>
|
||||
<ul>
|
||||
<li>打开 /etc/default/grub 文件进行编辑：</li>
|
||||
</ul>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>sudo nano /etc/default/grub
|
||||
</span><span># 确保 GRUB_DISABLE_OS_PROBER 设置为 false
|
||||
</span></code></pre>
|
||||
<ul>
|
||||
<li>保存文件并退出编辑器后，运行以下命令更新 GRUB 配置：</li>
|
||||
</ul>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>sudo grub-mkconfig -o /boot/grub/grub.cfg
|
||||
</span></code></pre>
|
||||
<p>或者<code>手动添加</code>：</p>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>nano /etc/grub.d/40_custom
|
||||
</span></code></pre>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>#!/bin/sh
|
||||
</span><span>exec tail -n +3 $0
|
||||
</span><span># This file provides an easy way to add custom menu entries. Simply type the
|
||||
</span><span># menu entries you want to add after this comment. Be careful not to change
|
||||
</span><span># the 'exec tail' line above.
|
||||
</span><span>menuentry "Windows 11 (Manual)" {
|
||||
</span><span> insmod part_gpt
|
||||
</span><span> insmod fat
|
||||
</span><span> insmod chain
|
||||
</span><span> set root='hd0,gpt1'
|
||||
</span><span> chainloader /EFI/Microsoft/Boot/bootmgfw.efi
|
||||
</span><span>}
|
||||
</span></code></pre>
|
||||
<h2 id="archzhong-an-zhuang-qemuxu-ni-ji">Arch中安装QEMU虚拟机</h2>
|
||||
<p>前面我们已经安装了Qemu高性能虚拟机平台和virt-manager用来管理虚拟机的图形界面，随后配置virt-manager并安装Ubuntu-server：</p>
|
||||
<p>如果virt-manager报错无法找到Qemu，则：</p>
|
||||
<ul>
|
||||
<li>如果 libvirtd 服务未运行，virt-manager 将无法连接到虚拟化环境。</li>
|
||||
</ul>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>sudo systemctl start libvirtd
|
||||
</span><span>sudo systemctl enable libvirtd
|
||||
</span></code></pre>
|
||||
<ul>
|
||||
<li>用户权限问题：将当前用户添加到 libvirt 组，以获得必要的权限。</li>
|
||||
</ul>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>sudo usermod -aG libvirt $(whoami)
|
||||
</span></code></pre>
|
||||
<ul>
|
||||
<li>虚拟网络未激活：virt-manager 可能无法连接到默认的虚拟网络。</li>
|
||||
</ul>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>sudo virsh net-start default
|
||||
</span></code></pre>
|
||||
<p>默认网络在系统启动时自动启动，可以执行：</p>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>sudo virsh net-autostart default
|
||||
</span></code></pre>
|
||||
<ul>
|
||||
<li>配置文件权限问题：配置文件的权限设置可能导致访问问题。</li>
|
||||
</ul>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>sudo chown $(whoami):libvirt /var/run/libvirt/libvirt-sock
|
||||
</span></code></pre>
|
||||
<p>随后安装虚拟机，流程大概为<code>选择镜像和系统类型--设置CPU/内存--设置空间大小--编辑配置项--开启UEFI引导和3D加速</code>.</p>
|
||||
<p><strong>开启3D加速：</strong></p>
|
||||
<ul>
|
||||
<li>NIC：</li>
|
||||
</ul>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span><graphics type="spice">
|
||||
</span><span> <listen type="none"/>
|
||||
</span><span> <image compression="off"/>
|
||||
</span><span> <gl enable="yes" rendernode="/dev/dri/by-path/pci-0000:05:00.0-render"/>
|
||||
</span><span></graphics>
|
||||
</span><span>
|
||||
</span></code></pre>
|
||||
<ul>
|
||||
<li>video virtio：</li>
|
||||
</ul>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span><video>
|
||||
</span><span> <model type="virtio" heads="1" primary="yes">
|
||||
</span><span> <acceleration accel3d="yes"/>
|
||||
</span><span> </model>
|
||||
</span><span> <alias name="video0"/>
|
||||
</span><span> <address type="pci" domain="0x0000" bus="0x00" slot="0x01" function="0x0"/>
|
||||
</span><span></video>
|
||||
</span></code></pre>
|
||||
<p>安装完成后即可使用electerm进行SSH连接，如果无法连接，可以将Tun模式开启的"strict_route"关闭。</p>
|
||||
<h2 id="geng-gai-qi-dong-nei-he-shun-xu">更改启动内核顺序</h2>
|
||||
<p>如果安装了多个linux内核，可以使用以下方法调整启动顺序：</p>
|
||||
<ul>
|
||||
<li>使用以下命令查看内核名称：</li>
|
||||
</ul>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>ls /boot/vmlinuz*
|
||||
</span></code></pre>
|
||||
<ul>
|
||||
<li>在 /etc/default/grub 中添加或修改如下行：</li>
|
||||
</ul>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>GRUB_TOP_LEVEL="/boot/vmlinuz-linux-cachyos"
|
||||
</span></code></pre>
|
||||
<p>需要注意，这种方法会关闭 GRUB 的“记住上次启动项”的功能。</p>
|
||||
<ul>
|
||||
<li>修改完 /etc/default/grub 后，记得重新生成 GRUB 配置文件：</li>
|
||||
</ul>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>sudo grub-mkconfig -o /boot/grub/grub.cfg
|
||||
</span></code></pre>
|
||||
<p><strong>图形界面更改方法：</strong></p>
|
||||
<p>可以使用grub-customizer来修改Grub，这里以ubuntu为例子：</p>
|
||||
<ul>
|
||||
<li>添加PPA源并更新软件列表：</li>
|
||||
</ul>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>sudo add-apt-repository ppa:danielrichter2007/grub-customizer
|
||||
</span><span>sudo apt update
|
||||
</span></code></pre>
|
||||
<ul>
|
||||
<li>安装GRUB Customizer：</li>
|
||||
</ul>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>sudo apt install grub-customizer
|
||||
</span></code></pre>
|
||||
<p>随后在grub-customizer中将要默认启动的选项放在首位即可。</p>
|
||||
<h2 id="kai-ji-zi-qi-dong">开机自启动</h2>
|
||||
<p><strong>设置Syncthing开机自启动</strong></p>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>sudo systemctl enable --now syncthing@<username>.service
|
||||
</span></code></pre>
|
||||
<h2 id="kai-qi-bbr">开启BBR</h2>
|
||||
<ul>
|
||||
<li>确保你的内核版本 >= 4.9：</li>
|
||||
</ul>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>uname -r
|
||||
</span></code></pre>
|
||||
<ul>
|
||||
<li>启用 BBR</li>
|
||||
</ul>
|
||||
<p>你只需要设置两个 sysctl 参数即可：</p>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>sudo sysctl -w net.core.default_qdisc=fq
|
||||
</span><span>sudo sysctl -w net.ipv4.tcp_congestion_control=bbr
|
||||
</span></code></pre>
|
||||
<p>要让它们永久生效，把它们写入配置文件：</p>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>sudo nano /etc/sysctl.d/99-bbr.conf
|
||||
</span></code></pre>
|
||||
<p>加入以下内容：</p>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>net.core.default_qdisc = fq
|
||||
</span><span>net.ipv4.tcp_congestion_control = bbr
|
||||
</span></code></pre>
|
||||
<p>然后重新加载配置：</p>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>sudo sysctl --system
|
||||
</span></code></pre>
|
||||
<ul>
|
||||
<li>验证 BBR 是否启用</li>
|
||||
</ul>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>sysctl net.ipv4.tcp_congestion_control
|
||||
</span></code></pre>
|
||||
<p>应该输出：</p>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>net.ipv4.tcp_congestion_control = bbr
|
||||
</span></code></pre>
|
||||
<h2 id="zai-arch-linuxshang-an-zhuang-docker">在Arch Linux上安装Docker</h2>
|
||||
<p>一般推荐在qemu虚拟机中安装，这里仅做示例：</p>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>sudo pacman -S docker
|
||||
</span></code></pre>
|
||||
<p>安装完成后，需要启动Docker服务，并设置为开机自启：</p>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>sudo systemctl start docker
|
||||
</span><span>sudo systemctl enable docker
|
||||
</span></code></pre>
|
||||
<p>运行以下命令来验证Docker是否正常工作：</p>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>sudo docker run hello-world
|
||||
</span></code></pre>
|
||||
<p>默认情况下，只有root用户才能运行Docker命令。为了避免每次运行Docker命令时都需要使用sudo，可以将当前用户添加到docker组：</p>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>sudo usermod -aG docker $USER
|
||||
</span></code></pre>
|
||||
<p>之后，需要注销并重新登录，或者重启系统以使更改生效。</p>
|
||||
<p>安装Docker Compose：</p>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>sudo pacman -S docker-compose
|
||||
</span></code></pre>
|
||||
<hr />
|
||||
<p><strong>Done.</strong></p>
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
<div class="pagination">
|
||||
<div class="pagination__title">
|
||||
<span class="pagination__title-h">Thanks for reading! Read other posts?</span>
|
||||
<hr />
|
||||
</div>
|
||||
<div class="pagination__buttons">
|
||||
<span class="button previous">
|
||||
<a href="https://blog.dich.bid/awesome-android-tv/">
|
||||
<span class="button__icon">←</span>
|
||||
<span class="button__text">综合工程:Android-TV 折腾小记</span>
|
||||
</a>
|
||||
</span>
|
||||
|
||||
|
||||
<span class="button next">
|
||||
<a href="https://blog.dich.bid/about-calling-cards/">
|
||||
<span class="button__text">乱七八糟:流量卡购买与套路</span>
|
||||
<span class="button__icon">→</span>
|
||||
</a>
|
||||
</span>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
</div>
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
<footer class="footer">
|
||||
<div class="footer__inner">
|
||||
<div class="copyright">
|
||||
<span>©
|
||||
2025
|
||||
Dichgrem</span>
|
||||
<span class="copyright-theme">
|
||||
<span class="copyright-theme-sep"> :: CC BY-SA 4.0 :: A friend comes from distant lands</span>
|
||||
</a>
|
||||
</span>
|
||||
</div>
|
||||
</div>
|
||||
</footer>
|
||||
|
||||
</div>
|
||||
</body>
|
||||
</html>
|
||||
|
||||
717
public/awesome-openwrt/index.html
Normal file
717
public/awesome-openwrt/index.html
Normal file
@ -0,0 +1,717 @@
|
||||
<!DOCTYPE html>
|
||||
<html lang="en">
|
||||
|
||||
<head>
|
||||
<title>Dich'blog</title>
|
||||
|
||||
<meta http-equiv="content-type" content="text/html; charset=utf-8">
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1">
|
||||
<meta name="robots" content="noodp"/>
|
||||
|
||||
<link rel="stylesheet" href="https://blog.dich.bid/style.css">
|
||||
<link rel="stylesheet" href="https://blog.dich.bid/color/blue.css">
|
||||
|
||||
<link rel="stylesheet" href="https://blog.dich.bid/color/background_dark.css">
|
||||
|
||||
<link rel="stylesheet" href="https://blog.dich.bid/font-hack-subset.css">
|
||||
|
||||
<meta name="description" content="">
|
||||
|
||||
<meta property="og:description" content="">
|
||||
<meta property="og:title" content="Dich'blog">
|
||||
<meta property="og:type" content="article">
|
||||
<meta property="og:url" content="https://blog.dich.bid/awesome-openwrt/">
|
||||
|
||||
<meta name="twitter:card" content="summary_large_image">
|
||||
<meta name="twitter:description" content="">
|
||||
<meta name="twitter:title" content="Dich'blog">
|
||||
<meta property="twitter:domain" content="blog.dich.bid">
|
||||
<meta property="twitter:url" content="https://blog.dich.bid/awesome-openwrt/">
|
||||
|
||||
<link rel="alternate" type="application/atom+xml" title="Dich'blog Atom Feed" href="https://blog.dich.bid/atom.xml" />
|
||||
|
||||
|
||||
<link rel="icon" type="image/png" href=/dich.webp />
|
||||
|
||||
<!-- ✅ Added center alignment styles -->
|
||||
<style>
|
||||
.footer {
|
||||
text-align: center;
|
||||
padding: 1rem 0;
|
||||
}
|
||||
|
||||
.footer__inner {
|
||||
display: flex;
|
||||
justify-content: center;
|
||||
flex-direction: column;
|
||||
align-items: center;
|
||||
}
|
||||
|
||||
.copyright {
|
||||
text-align: center;
|
||||
}
|
||||
</style>
|
||||
</head>
|
||||
|
||||
<body class="">
|
||||
<div class="container">
|
||||
|
||||
<header class="header">
|
||||
<div class="header__inner">
|
||||
<div class="header__logo">
|
||||
|
||||
<a href="https://blog.dich.bid" style="text-decoration: none;">
|
||||
<div class="logo">
|
||||
|
||||
Dich'blog
|
||||
|
||||
</div>
|
||||
</a>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
|
||||
|
||||
<nav class="menu">
|
||||
<ul class="menu__inner">
|
||||
<li class="active"><a href="https://blog.dich.bid">blog</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/archive">archive</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/tags">tags</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/weekly">weekly</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/search">search</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/about">about me</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/links">links</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/atom.xml">rss</a></li>
|
||||
|
||||
<li><a href="https://github.com/Dichgrem" target="_blank" rel="noopener noreferrer">github</a></li>
|
||||
</ul>
|
||||
</nav>
|
||||
|
||||
|
||||
|
||||
</header>
|
||||
|
||||
|
||||
<div class="content">
|
||||
|
||||
<div class="post">
|
||||
|
||||
<h1 class="post-title"><a href="https://blog.dich.bid/awesome-openwrt/">综合工程:OpenWrt路由部署与软件编译</a></h1>
|
||||
<div class="post-meta-inline">
|
||||
|
||||
<span class="post-date">
|
||||
2023-08-12
|
||||
</span>
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
<span class="post-tags-inline">
|
||||
:: tags:
|
||||
<a class="post-tag" href="https://blog.dich.bid/tags/zong-he-gong-cheng/">#综合工程</a></span>
|
||||
|
||||
|
||||
<div class="post-content">
|
||||
<p>前言 openwrt 是一个自由的、兼容性好的嵌入式 linux 发行版。作为软路由玩家必备的一款神器，可以实现诸如去广告，多拨和科学上网等多种功能。本文介绍openwrt在各种平台上的部署流程。</p>
|
||||
<span id="continue-reading"></span><h2 id="yao-shi-xian-de-mu-biao"><strong>要实现的目标</strong></h2>
|
||||
<ul>
|
||||
<li>1.IPv6 分配到每个设备；</li>
|
||||
<li>2.NAT类型为NAT1（全锥形）；</li>
|
||||
<li>3.可控的流量记录与IP控制/QOS；</li>
|
||||
<li>4.可靠的硬件加速；</li>
|
||||
<li>5.多线多播/宽带提速；</li>
|
||||
<li>6.PPPoE拨号，替代一部分光猫功能；</li>
|
||||
<li>7.智能DNS配置与去广告；</li>
|
||||
<li>8.VPN配置回家；</li>
|
||||
<li>9.实现透明代理。</li>
|
||||
</ul>
|
||||
<blockquote>
|
||||
<p>剩余专业路由功能可以由ROS替代，服务则跑在NAS系统上，避免ALL in Boom！</p>
|
||||
</blockquote>
|
||||
<h2 id="da-zhi-si-lu">大致思路</h2>
|
||||
<ul>
|
||||
<li>使用高性能的X86主机管理拨号和 DHCP 内网的工作，其他无线路由器桥接做AP，Mesh组网；</li>
|
||||
<li>使用绕过中国流量模式，国内流量不经过代理内核直接直连，加快国内网站访问。保持尽可能高的 NAT 等级；</li>
|
||||
<li>不使用旁路由，所有流量过主路由；由于第二点代理挂了也不影响国内正常上网；</li>
|
||||
<li>国内外域名分流查询，国内域名查运营商 DNS ，国外域名经代理查国外 DoH ，直接返回真实 IP；</li>
|
||||
<li>良好的国内 IPv6 支持，只对国内域名返回 IPv6 AAAA 结果，国外域名只用 IPv4；</li>
|
||||
<li>兼容 Adguard Home ，方便管理域名黑白名单；</li>
|
||||
<li>对能直连的国外服务能返回最优的节点，而不是绕路其他地方；</li>
|
||||
</ul>
|
||||
<h2 id="xuan-ze-he-gua-de-she-bei"><strong>选择合适的设备</strong></h2>
|
||||
<p>无论是传统的无线路由器还是小主机都有成为openwrt路由的潜力。截止到今天，已经有20多个品牌（小米，华硕，锐捷，华三等）30多种架构（x86,ipq,bcm,mtd等）支持刷入openwrt；你可以在这个<a href="https://mao.fan/select">网站</a>找到符合你预算和其他要求的，能刷机的路由器。
|
||||
传统家用无线路由器由于主频低，内存小，并不适合作为软路由；而 NAS-软路由一体式 又有 all in boom 的风险，因此推荐X86平台作为物理机。当然，也可以采用 armbian 平台或是开发板，例如网心云老母鸡、树莓派等设备。截至本文撰写时间，二手平台上的价格不太利好：一台J1900平台的售价往往在200左右，而专门的多网口工控机价格在200到1000不等，树莓派更是成为了理财产品，需要慎重选择。</p>
|
||||
<h2 id="xuan-ze-he-gua-de-xi-tong"><strong>选择合适的系统</strong></h2>
|
||||
<p>除了openwrt主线外，还可以选择：</p>
|
||||
<ul>
|
||||
<li>
|
||||
<p><a href="https://github.com/coolsnowwolf/lede">LEDE</a> 高质量，更新快速，具有新特性的openwrt分支。</p>
|
||||
</li>
|
||||
<li>
|
||||
<p><a href="https://github.com/istoreos">iStoreOS</a> iStoreOS是openwrt的一个分支，iStoreOS 提供了软件中心：iStore，以及较美观的界面和docker支持，对新手体验较好。</p>
|
||||
</li>
|
||||
<li>
|
||||
<p><a href="https://firmware-selector.immortalwrt.org/">ImmortalWrt</a> 是一个原版openwrt的分支，中文优化好，更新也勤快，内置镜像源可以直连下载&更新。</p>
|
||||
</li>
|
||||
</ul>
|
||||
<h2 id="ru-he-de-dao-yi-ge-openwrtxi-tong"><strong>如何得到一个openwrt系统</strong></h2>
|
||||
<ul>
|
||||
<li>可以在恩山论坛上使用他人编译好的现成的镜像，如"高大全","精品小包"等等，但存在一定风险；</li>
|
||||
<li>可以使用<a href="https://downloads.openwrt.org/">官方固件</a>下载得到一个最小化的系统，再一步步添加自己要用的包；注意需要根据你的uboot来选择，注意固件名称是否带了uboot_mod!</li>
|
||||
<li>可以使用<a href="https://firmware-selector.openwrt.org/">Openwrt 在线编译</a>或<a href="https://openwrt.ai/?target=x86%2F64&id=generic">Openwrt.ai</a>在线编译
|
||||
一个固件；</li>
|
||||
<li>可以使用GitHub action 云编译一个固件；</li>
|
||||
<li>可以在本地linux环境中进行编译。</li>
|
||||
</ul>
|
||||
<h2 id="x86ping-tai-an-zhuang-zhun-bei"><strong>X86平台安装准备：</strong></h2>
|
||||
<ul>
|
||||
<li>
|
||||
<p>一个U盘与一台双网口物理机</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>openwrt 的编译包，官方网站：<a href="https://firmware-selector.openwrt.org/?version=24.10.0-rc2&target=ipq40xx%2Fgeneric&id=glinet_gl-a1300">OpenWrt Firmware Selector</a></p>
|
||||
</li>
|
||||
<li>
|
||||
<p>或者用由 eSir 大佬编译的<a href="https://drive.google.com/drive/folders/1uRXg_krKHPrQneI3F2GNcSVRoCgkqESr">懒人包</a></p>
|
||||
</li>
|
||||
<li>
|
||||
<p>PE 启动盘，这里推荐<a href="https://github.com/VirtualHotBar/HotPEToolBox">HotPE</a></p>
|
||||
</li>
|
||||
<li>
|
||||
<p><a href="https://www.roadkil.net/program.php?ProgramID=12#google_vignette">img 写盘工具</a></p>
|
||||
</li>
|
||||
</ul>
|
||||
<h2 id="x86ping-tai-an-zhuang-liu-cheng"><strong>X86平台安装流程：</strong></h2>
|
||||
<p>1.进入PE环境：</p>
|
||||
<ul>
|
||||
<li>打开微PE，将其安装进U盘中，安装完成后将 img 工具和 openwrt 包一起放进去；</li>
|
||||
<li>将U盘插入目标主机，进入 BIOS-boot 设置U盘优先启动，各主板进入 BIOS 的按键不同，不确定的话建议都试一遍。</li>
|
||||
</ul>
|
||||
<p>2.格式化硬盘并写盘</p>
|
||||
<ul>
|
||||
<li>进入PE环境中，可以看到存在名为“分区助手”的软件，打开它并将目标主机硬盘格式化；注意不要分区！不要分区！不要设置文件系统！否则后续可能无法编译！点击左上角提交并执行</li>
|
||||
<li>打开img写盘工具，将openwrt包写入硬盘，注意不要写进U盘里。</li>
|
||||
</ul>
|
||||
<p>3.进入配置界面</p>
|
||||
<ul>
|
||||
<li>重启系统并快速拔出U盘，避免重新进入PE；这时系统开始运行了。注意Esir固件是不跑码的，无需担心。- 一个U盘与一台双网口物理机</li>
|
||||
<li>当看到 <code>please press Enter to activate this console</code>这个提示的时候系统就安装完毕了。可使用 passwd 命令设置密码。软路由将自动获取IP地址，随后我们在浏览器中打开该地址，即可看到 Lucl 界面。</li>
|
||||
</ul>
|
||||
<p>4.如果你使用官方固件，注意:</p>
|
||||
<ul>
|
||||
<li>硬盘空间有一部分没有被格式化，可以手动格式化为ext4并挂载。</li>
|
||||
<li>注意初始IP往往是192.168.1.1，如果和光猫冲突需要在网络-接口中更改。</li>
|
||||
<li>基本系统主题比较简陋，可以使用luci-theme-argon。</li>
|
||||
<li>刷错主题无法打开luci：通过 SSH 登录路由器，切换到另一个已知正常的主题（例如 Bootstrap）：
|
||||
<code>uci set luci.main.mediaurlbase='/luci-static/bootstrap' uci commit luci /etc/init.d/uhttpd restart</code>
|
||||
然后重新访问 Web 界面，查看是否恢复正常。</li>
|
||||
<li>一般要安装的包：</li>
|
||||
</ul>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>openssh-sftp-server
|
||||
</span><span>libpcap
|
||||
</span><span>luci-app-upnp
|
||||
</span><span>luci-app-ttyd
|
||||
</span><span>kmod-nft-xxx
|
||||
</span></code></pre>
|
||||
<h2 id="x86ping-tai-ben-di-bian-yi-wan-zheng-openwrt"><strong>X86平台本地编译完整openwrt</strong></h2>
|
||||
<ul>
|
||||
<li>
|
||||
<p><strong>系统版本：Debian 11 或者 Ubuntu LTS</strong></p>
|
||||
</li>
|
||||
<li>
|
||||
<p><strong>网络要求：科学上网环境，配置推荐 2H4G 以上</strong></p>
|
||||
</li>
|
||||
<li>
|
||||
<p><strong>编译依赖</strong></p>
|
||||
</li>
|
||||
</ul>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>sudo apt update
|
||||
</span><span>sudo apt install -y \
|
||||
</span><span> ack antlr3 asciidoc autoconf automake autopoint binutils bison build-essential \
|
||||
</span><span> bzip2 ccache clang cmake cpio curl device-tree-compiler diffutils diffstat findutils flex gawk \
|
||||
</span><span> gcc-multilib g++-multilib git gettext gperf grep haveged help2man intltool \
|
||||
</span><span> libelf-dev libfuse-dev libgmp3-dev libgl1-mesa-dev libgraphene-1.0-dev libglib2.0-dev \
|
||||
</span><span> libltdl-dev libmpc-dev libmpfr-dev libncurses-dev libpython3-dev libreadline-dev libssl-dev \
|
||||
</span><span> libtool lrzsz make mesa-common-dev msmtp ninja-build p7zip p7zip-full patch pkgconf \
|
||||
</span><span> perl python-is-python3 python3 python3-dev python3-distutils-extra python3-pip python3-pyelftools \
|
||||
</span><span> python3-setuptools qemu-utils rsync scons squashfs-tools subversion swig texinfo uglifyjs \
|
||||
</span><span> upx-ucl unzip vim wget gnu-which xmlto xxd zlib1g-dev genisoimage llvm llvm-runtime docutils-common \
|
||||
</span><span> ecj fastjar java-wrappers libeclipse-jdt-core-java libgnutls-dane0t64 \
|
||||
</span><span> libgnutls-openssl27t64 libgnutls28-dev libidn2-dev libp11-kit-dev libtasn1-6-dev libtasn1-doc \
|
||||
</span><span> libunbound8 libyaml-dev lld lld-18 nettle-dev python3-docutils python3-ply python3-roman re2c
|
||||
</span></code></pre>
|
||||
<ul>
|
||||
<li><strong>清理</strong></li>
|
||||
</ul>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>sudo apt autoremove --purge
|
||||
</span><span>sudo apt clean
|
||||
</span></code></pre>
|
||||
<ul>
|
||||
<li><strong>新建一个用户，用于编译固件(可选)</strong></li>
|
||||
</ul>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>useradd -m openwrt # 新建一个名为 openwrt 的用户
|
||||
</span></code></pre>
|
||||
<blockquote>
|
||||
<p>不可以使用Root用户进行编译！!!</p>
|
||||
</blockquote>
|
||||
<ul>
|
||||
<li><strong>修改用户默认的 Shell</strong></li>
|
||||
</ul>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>apt install -y sudo
|
||||
</span><span>usermod -s /bin/bash openwrt
|
||||
</span></code></pre>
|
||||
<ul>
|
||||
<li><strong>切换用户</strong></li>
|
||||
</ul>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>su openwrt
|
||||
</span><span>cd ~
|
||||
</span></code></pre>
|
||||
<ul>
|
||||
<li><strong>拉取源码，这里用的是 LEDE 分支源码：</strong></li>
|
||||
</ul>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>git clone https://github.com/coolsnowwolf/lede
|
||||
</span><span>cd lede
|
||||
</span></code></pre>
|
||||
<h3 id="mu-lu-shuo-ming">目录说明</h3>
|
||||
<ul>
|
||||
<li>
|
||||
<p>buildroot: OpenWrt 的核心目录，包含构建系统相关的文件。</p>
|
||||
<ul>
|
||||
<li><code>feeds.conf.default</code>：定义软件包源的配置文件。</li>
|
||||
<li><code>files/</code>：存放自定义文件，用于覆盖默认的 root 文件系统。</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p>target: 包含目标设备架构的配置和构建信息。</p>
|
||||
<ul>
|
||||
<li><code>linux/</code>：包含与 Linux 内核相关的代码和配置。</li>
|
||||
<li><code>generic/</code>：通用配置文件。</li>
|
||||
<li><code>platform/</code>：针对具体设备平台的特定配置。</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p>package: 包含所有 OpenWrt 的软件包。</p>
|
||||
<ul>
|
||||
<li><code>base/</code>：基本功能相关的软件包（如 BusyBox、opkg）。</li>
|
||||
<li><code>kernel/</code>：与内核相关的补丁或模块。</li>
|
||||
<li><code>network/</code>：网络工具和协议（如 DHCP、DNS）。</li>
|
||||
<li><code>utils/</code>：各种实用工具（如编解码器、文件工具）。</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p>config: 存放默认配置文件，例如 <code>Config.in</code>，用于定义菜单项。</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>scripts: 构建过程中使用的辅助脚本（如生成补丁、编译镜像）。</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>toolchain: 构建工具链所需的文件，如编译器、链接器。</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>tools: 一些构建系统依赖的额外工具（如 <code>autoconf</code>、<code>zlib</code>）。</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>include: 存放 Makefile 的通用模板和其他全局定义文件。</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>feeds: 包含通过 <code>feeds.conf</code> 配置的外部软件包源。</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>documentation: 包含与 OpenWrt 项目相关的文档，如构建指南和开发文档。</p>
|
||||
</li>
|
||||
<li>
|
||||
<p><strong>添加软件源,可自行添加软件源至 feeds.conf.default 文件，也可以直接git添加需要的软件到lede目录下：</strong></p>
|
||||
</li>
|
||||
</ul>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>vim feeds.conf.default
|
||||
</span></code></pre>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>常用源
|
||||
</span><span>src-git kenzo https://github.com/kenzok8/openwrt-packages
|
||||
</span><span>src-git small https://github.com/kenzok8/small
|
||||
</span><span>src-git haibo https://github.com/haiibo/openwrt-packages
|
||||
</span><span>src-git liuran001 https://github.com/liuran001/openwrt-packages
|
||||
</span></code></pre>
|
||||
<ul>
|
||||
<li><strong>单独添加</strong>（在更新并安装插件之前执行）例如：</li>
|
||||
</ul>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>git clone https://github.com/chenmozhijin/turboacc.git
|
||||
</span></code></pre>
|
||||
<ul>
|
||||
<li><strong>更新并安装插件</strong></li>
|
||||
</ul>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>./scripts/feeds clean
|
||||
</span><span>./scripts/feeds update -a
|
||||
</span><span>./scripts/feeds install -a
|
||||
</span></code></pre>
|
||||
<ul>
|
||||
<li><strong>自定义配置</strong></li>
|
||||
</ul>
|
||||
<p><strong>修改默认IP为 10.0.0.2</strong></p>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>sed -i 's/192.168.1.1/192.168.2.1/g' package/base-files/files/bin/config_generate
|
||||
</span></code></pre>
|
||||
<p><strong>修改默认主机名</strong></p>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>sed -i '/uci commit system/i\uci set system.@system[0].hostname='OpenWrt'' package/lean/default-settings/files/zzz-default-settings
|
||||
</span></code></pre>
|
||||
<p><strong>加入编译者信息</strong></p>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>sed -i "s/OpenWrt /smith build $(TZ=UTC-8 date "+%Y.%m.%d") @ OpenWrt /g" package/lean/default-settings/files/zzz-default-settings
|
||||
</span></code></pre>
|
||||
<p><strong>修改默认主题</strong></p>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>sed -i "s/luci-theme-bootstrap/luci-theme-argon/g" feeds/luci/collections/luci/Makefile
|
||||
</span></code></pre>
|
||||
<p>执行 <strong>make menuconfig</strong> 命令进入编译菜单。</p>
|
||||
<h3 id="bian-yi-pei-zhi-cai-dan-shuo-ming-bu-fen"><strong>编译配置菜单说明（部分）</strong></h3>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>Target System (Broadcom BCM27xx) # 选择处理器架构
|
||||
</span><span>└── Subtarget (BCM2711 boards (64 bit)) # 选择处理器
|
||||
</span><span> └── Target Profile (Raspberry Pi 4B/400/4CM (64bit)) # 预制配置文件
|
||||
</span><span> └── Target Images # 固件映像设置
|
||||
</span><span> └── ramdisk # 内存盘
|
||||
</span><span> ├── Compression # 压缩等级 (none 表示不压缩)
|
||||
</span><span> ├── Root filesystem archives # 根文件系统存档类型
|
||||
</span><span> │ ├── cpio.gz
|
||||
</span><span> │ └── tar.gz
|
||||
</span><span> ├── Root filesystem images # 根文件系统格式
|
||||
</span><span> │ ├── ext4 # 适用于大容量闪存
|
||||
</span><span> │ ├── squashfs # 适用于小容量闪存
|
||||
</span><span> │ └── Gzip images # Gzip 存档
|
||||
</span><span> └── Image Options
|
||||
</span><span> ├── Kernel partition size # 内核分区大小
|
||||
</span><span> ├── Root filesystem partition size # 跟文件系统分区大小
|
||||
</span><span> └── Make /var persistent # 持久化 /var
|
||||
</span><span>
|
||||
</span><span>Enable experimental features by default # 默认启用实验性功能
|
||||
</span><span>Global build settings # 全局编译设置
|
||||
</span><span>Advanced configuration options (for developers) # 高级选项（仅供开发者）
|
||||
</span><span>Build the OpenWrt Image Builder # 编译 OpenWrt 镜像编译器
|
||||
</span><span>Build the OpenWrt SDK # 编译 OpenWrt SDK
|
||||
</span><span>Package the OpenWrt-based Toolchain # 打包 OpenWrt 工具链
|
||||
</span><span>Image configuration # 镜像选项
|
||||
</span><span>
|
||||
</span><span>Base system # 基本组件
|
||||
</span><span>Administration # 管理员工具
|
||||
</span><span>Boot Loaders # 引导程序
|
||||
</span><span>Development # 开发者工具
|
||||
</span><span>Extra packages # 额外包
|
||||
</span><span>Firmware # 固件工具
|
||||
</span><span>Fonts # 字体
|
||||
</span><span>Kernel modules # 内核模块
|
||||
</span><span>Languages # 额外的语言 (Python3, PHP, NodeJS 等)
|
||||
</span><span>Libraries # 系统库
|
||||
</span><span>LuCI # LuCI 插件（一般只需修改应用和主题）
|
||||
</span><span>└── Collections
|
||||
</span><span>└── Modules
|
||||
</span><span>└── Applications
|
||||
</span><span>└── Themes
|
||||
</span><span>└── Protocols
|
||||
</span><span>└── Libraries
|
||||
</span><span>└── default-settings # 默认选项（自动配置语言包）
|
||||
</span><span>
|
||||
</span><span>Mail # 邮件
|
||||
</span><span>Multimedia # 多媒体
|
||||
</span><span>Network # 网络相关
|
||||
</span><span>Sound # 音频
|
||||
</span><span>Utilities # 各类实用软件（比如 VIM）
|
||||
</span><span>Xorg
|
||||
</span></code></pre>
|
||||
<h3 id="cai-dan-xuan-xiang-shuo-ming"><strong>菜单选项说明</strong></h3>
|
||||
<p><strong>选择 CPU 类型</strong></p>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>Target System (x86) --> # 软路由选择 x86，硬路由根据型号厂家自行选择
|
||||
</span><span>
|
||||
</span><span>Subtarget (x86_64) --> # CPU 子选项
|
||||
</span><span>
|
||||
</span><span>Target Profile (Generic x86/64) --> # 厂家具体型号
|
||||
</span></code></pre>
|
||||
<p><strong>设置镜像编译的格式（squashfs，ext4）</strong></p>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>Target Images --> # 默认 squashfs
|
||||
</span></code></pre>
|
||||
<p><strong>添加较多插件时，为了避免空间不足，建议修改下面两项默认大小（x86/64）</strong></p>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>Target Images --> (16) Kernel partition size (in MB) # 默认是16，建议修改为256
|
||||
</span></code></pre>
|
||||
<p><strong>开启 IPv6 支持</strong></p>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>Extra packages --> ipv6helper（选定这个后，下面几项会自动选择）
|
||||
</span></code></pre>
|
||||
<p><strong>开启适用于 VMware 的 VMware Tools</strong></p>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>Utilities --> open-vm-tools
|
||||
</span><span>
|
||||
</span><span>Utilities --> open-vm-tools-fuse
|
||||
</span></code></pre>
|
||||
<p><strong>选择插件</strong></p>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>LuCI --> Applications # 根据需要选择，* 代表编入固件，M 表示编译成模块或者IPK包，为空表示不编译
|
||||
</span></code></pre>
|
||||
<p><strong>选择主题</strong></p>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>LuCI --> Themes # 选择喜欢的主题，可以选多个
|
||||
</span></code></pre>
|
||||
<p>配置完成后使用编译菜单底部的 Save 保存，然后退出菜单 Exit，开始下载软件包</p>
|
||||
<ul>
|
||||
<li><strong>预下载编译所需的软件包</strong></li>
|
||||
</ul>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>make download -j8
|
||||
</span></code></pre>
|
||||
<ul>
|
||||
<li><strong>检查文件完整性</strong></li>
|
||||
</ul>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>find dl -size -1024c -exec ls -l {} \;
|
||||
</span></code></pre>
|
||||
<p>检查文件完整性命令可以列出下载不完整的文件，小于1k的文件属于下载不完整，如果存在则用下面的命令删除，然后重新下载编译所需的软件包，再次检查.确认所有文件完整可大大提高编译成功率，避免浪费时间</p>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>find dl -size -1024c -exec rm -f {} \;
|
||||
</span></code></pre>
|
||||
<p>最后编译固件，编译完成后输出路径是 <strong>bin/targets</strong>，默认密码是 <strong>password</strong>.</p>
|
||||
<ul>
|
||||
<li><strong>编译固件（-j 后面是线程数，首次编译推荐用单线程）</strong></li>
|
||||
</ul>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>make V=s -j1
|
||||
</span></code></pre>
|
||||
<ul>
|
||||
<li><strong>二次编译</strong></li>
|
||||
</ul>
|
||||
<p>拉取最新 OpenWrt 源码和更新 feeds 源中的软件包源码</p>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>cd lede
|
||||
</span><span>
|
||||
</span><span>git pull
|
||||
</span><span>
|
||||
</span><span>./scripts/feeds update -a
|
||||
</span><span>
|
||||
</span><span>./scripts/feeds install -a
|
||||
</span></code></pre>
|
||||
<p>清除旧的编译产物和目录（可选）</p>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>make clean
|
||||
</span></code></pre>
|
||||
<ul>
|
||||
<li>源码有大规模更新或者内核更新后执行，以保证编译质量;此操作会删除 /bin 和 /build_dir 目录中的文件</li>
|
||||
</ul>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>make dirclean
|
||||
</span></code></pre>
|
||||
<blockquote>
|
||||
<p>更换架构编译前必须执行</p>
|
||||
</blockquote>
|
||||
<blockquote>
|
||||
<p>此操作会删除 /bin 和 /build_dir 目录的中的文件（make clean），以及 /staging_dir、/toolchain、/tmp 和 /logs 中的文件</p>
|
||||
</blockquote>
|
||||
<p>同首次编译，多线程编译失败后自动进入单线程编译，失败则输出详细日志</p>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>make defconfig
|
||||
</span><span>
|
||||
</span><span>make download -j8
|
||||
</span><span>
|
||||
</span><span>find dl -size -1024c -exec ls -l {} \;
|
||||
</span><span>
|
||||
</span><span>make -j$(nproc) || make -j1 || make -j1 V=s
|
||||
</span></code></pre>
|
||||
<h3 id="ru-guo-xu-yao-zhong-xin-pei-zhi">如果需要重新配置</h3>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>rm -rf ./tmp && rm -rf .config # 清除临时文件和编译配置文件
|
||||
</span><span>
|
||||
</span><span>make menuconfig
|
||||
</span><span>
|
||||
</span><span>make download -j8
|
||||
</span><span>
|
||||
</span><span>find dl -size -1024c -exec ls -l {} \;
|
||||
</span><span>
|
||||
</span><span>make -j$(nproc) || make -j1 || make -j1 V=s
|
||||
</span></code></pre>
|
||||
<h2 id="armping-tai-an-zhuang-openwrt">Arm平台安装OpenWrt：</h2>
|
||||
<p>相比X86平台，arm架构的设备兼容性不高，不能随便找一个包就能安装。以下是一般步骤：</p>
|
||||
<ul>
|
||||
<li>
|
||||
<p>首先得知道你的设备的CPU，比如ipq40XX系列，然后在对应的<a href="https://archive.openwrt.org/releases/23.05.4/targets/">仓库</a>查看并下载包体。</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>当然也可以在<a href="https://firmware-selector.openwrt.org/">这里</a>直接下载相关型号对应的固件，其中 Sysupgrade 映像是用来更新现有运行 OpenWrt 的设备，使用 Factory 映像在首次刷机时刷入。</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>随后开启Telnet或者SSH或者TTL串口连接到路由器，将对应的Uboot刷入，如果没有适配的包就无法刷openwrt。</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>通过Uboot的网络界面刷入Factory包，随后就可以在后台（如192.168.1.1）进入openwrt的管理界面。</p>
|
||||
</li>
|
||||
</ul>
|
||||
<h2 id="zai-ubuntushang-dan-du-bian-yi-openwrtde-ipkbao">在ubuntu上单独编译openwrt的ipk包</h2>
|
||||
<p>这里以ubuntu环境为例，我们假设你有一台虚拟机或者WSL。</p>
|
||||
<blockquote>
|
||||
<p><code>注意编译不能使用Root用户！</code></p>
|
||||
</blockquote>
|
||||
<p><strong>随后安装编译依赖的各个包：</strong></p>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>sudo apt update
|
||||
</span><span>sudo apt install -y \
|
||||
</span><span> ack antlr3 asciidoc autoconf automake autopoint binutils bison build-essential \
|
||||
</span><span> bzip2 ccache clang cmake cpio curl device-tree-compiler diffutils diffstat findutils flex gawk \
|
||||
</span><span> gcc-multilib g++-multilib git gettext gperf grep haveged help2man intltool \
|
||||
</span><span> libelf-dev libfuse-dev libgmp3-dev libgl1-mesa-dev libgraphene-1.0-dev libglib2.0-dev \
|
||||
</span><span> libltdl-dev libmpc-dev libmpfr-dev libncurses-dev libpython3-dev libreadline-dev libssl-dev \
|
||||
</span><span> libtool lrzsz make mesa-common-dev msmtp ninja-build p7zip p7zip-full patch pkgconf \
|
||||
</span><span> perl python-is-python3 python3 python3-dev python3-distutils-extra python3-pip python3-pyelftools \
|
||||
</span><span> python3-setuptools qemu-utils rsync scons squashfs-tools subversion swig texinfo uglifyjs \
|
||||
</span><span> upx-ucl unzip vim wget gnu-which xmlto xxd zlib1g-dev genisoimage llvm llvm-runtime docutils-common \
|
||||
</span><span> ecj fastjar java-wrappers libeclipse-jdt-core-java libgnutls-dane0t64 \
|
||||
</span><span> libgnutls-openssl27t64 libgnutls28-dev libidn2-dev libp11-kit-dev libtasn1-6-dev libtasn1-doc \
|
||||
</span><span> libunbound8 libyaml-dev lld lld-18 nettle-dev python3-docutils python3-ply python3-roman re2c
|
||||
</span></code></pre>
|
||||
<p>随后下载我们<strong>刷入openwrt的对应的SDK包</strong>，如</p>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>git clone https://github.com/immortalwrt/immortalwrt.git
|
||||
</span></code></pre>
|
||||
<p><strong>下载和安装仓库信息</strong></p>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>./scripts/feeds update -a
|
||||
</span><span>./scripts/feeds install -a
|
||||
</span></code></pre>
|
||||
<p><strong>下载并选中我们需要编译的包,这里以inyn为例：</strong></p>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>git clone https://github.com/diredocks/openwrt-inyn.git ./package/inyn
|
||||
</span><span>make menuconfig
|
||||
</span></code></pre>
|
||||
<p>在 <code>menuconfig</code> 的命令行界面中，选中 <code>Network -> inyn</code> 将其首部调整为 <code><M></code> 表示按需编译，最后选中 <code>Save -> OK -> Exit</code> 保存配置信息，然后 <code>Exit</code> 退出配置。</p>
|
||||
<p><strong>编译 inyn 软件包</strong></p>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>make package/inyn/compile V=s
|
||||
</span><span>## 如果不行则需要先编译工具链，即为 make j=4 ，j为CPU核数
|
||||
</span></code></pre>
|
||||
<h2 id="github-actions-bian-yi-openwrt">Github Actions 编译OpenWrt</h2>
|
||||
<p>Github为我们提供了免费的E5主机用来编译。</p>
|
||||
<ul>
|
||||
<li>
|
||||
<p>首先Fork<a href="https://github.com/hugcabbage/shared-lede">这个仓库</a>，可以看到有许多现成的配置，在<strong>顶栏actions里面可以直接启动一个Workflow</strong>来编译。</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>大体架构是选择<strong>源码 -- 机型 -- 版本 -- 插件/主题 -- 配置（IP/密码/Hostname/编译者）</strong>，由一个config文件管理，这个文件在前面也提到过，可以在本地生成并上传；</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>想要什么插件可以直接git clone过来原仓库，如果你想要添加其他架构和设备，这里<strong>使用templet里面的init.toml来创建</strong>，按照类似的格式填好；</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>在actions里面运行produce，注意这需要<strong>GitHub Personal Access Token (PAT)</strong>；如果没有，必须先添加：</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>打开 GitHub，进入<a href="https://github.com/settings/tokens">GitHub Developer Settings</a>点击 “Generate new token (classic)”，<strong>勾选所需权限</strong>（最关键的是 repo 和 workflow）：✅ repo（所有子权限）✅ workflow✅ read:packages <strong>Token 过期时间</strong>：选择 “No expiration”（不过期），否则过期后需要重新生成。<strong>点击</strong> “Generate token”
|
||||
<strong>复制 Token</strong>（只显示一次，一定要保存好！）</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>然后添加 <strong>PRODUCE_DEVICE</strong> 到 <strong>GitHub Secrets</strong>，
|
||||
首先进入你的 GitHub 仓库，<code>依次进入：Settings（设置）- Secrets and variables-Actions-New repository secret 名称为PRODUCE_DEVICE</code>，值为粘贴刚刚复制的 GitHub Token，点击 “Add secret” 完成添加。</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>随后<code>在actions里面运行produce</code>，完成后即可出现新架构的编译按钮.</p>
|
||||
</li>
|
||||
</ul>
|
||||
<h2 id="chang-yong-ming-ling">常用命令:</h2>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span># 更新软件列表
|
||||
</span><span>opkg update
|
||||
</span><span>
|
||||
</span><span># 更新所有 LUCI 插件
|
||||
</span><span>opkg list-upgradable | grep luci- | cut -f 1 -d ' ' | xargs opkg upgrade
|
||||
</span><span>
|
||||
</span><span># 如果要更新所有软件，包括 OpenWRT 内核、固件等
|
||||
</span><span>opkg list-upgradable | cut -f 1 -d ' ' | xargs opkg upgrade
|
||||
</span></code></pre>
|
||||
<blockquote>
|
||||
<p>新版本的openwrt（24.10）已经改用APK包管理器。</p>
|
||||
</blockquote>
|
||||
<h2 id="chang-yong-ke-xue-cha-jian">常用科学插件</h2>
|
||||
<table><thead><tr><th>特性</th><th>HomeProxy</th><th>OpenClash</th><th>Passwall</th><th>ShellClash</th></tr></thead><tbody>
|
||||
<tr><td><strong>核心</strong></td><td>Sing-box、Xray</td><td>Clash</td><td>Xray、Sing-box</td><td>Clash、Xray、Sing-box</td></tr>
|
||||
<tr><td><strong>UI 管理</strong></td><td>✅（Web UI、桌面端 GUI）</td><td>✅（OpenClash Web UI）</td><td>✅（Luci Web UI）</td><td>❌（Shell 终端管理）</td></tr>
|
||||
<tr><td><strong>适用场景</strong></td><td>性能较好,但分流设置复杂</td><td>适用于clash系,机场首选</td><td>操作简单,分流完善,但对路由器性能要求较高</td><td>没有UI界面，性能最好，支持完善，可以通过clashapi安装UI</td></tr>
|
||||
</tbody></table>
|
||||
<h2 id="xiao-yuan-wang-duo-she-bei-fang-jian-ce">校园网多设备防检测</h2>
|
||||
<p><strong>常见检测方法</strong>：</p>
|
||||
<ul>
|
||||
<li>TTL检测法 解法：插件统一修复或使用桥接；使用kmod-iptables-ipot模块；</li>
|
||||
<li>User-Agent 解法：统一经过singbox代理或使用UA2F/UA3F；</li>
|
||||
<li>时间戳检测法 解法：统一NTP服务器；</li>
|
||||
</ul>
|
||||
<p><strong>高性能开销检测方法</strong>：</p>
|
||||
<ul>
|
||||
<li>IP-ID检测法 解法：UDP over TCP或rkp-IPid；</li>
|
||||
<li>Flash cookie 解法：内置防火墙组件；</li>
|
||||
<li>DPI检测法 深度包检测特征值 解法：代理协议；</li>
|
||||
</ul>
|
||||
<blockquote>
|
||||
<p>高性能开销的检测方法会浪费大量性能，一般很少有学校这么做。IP-ID和Flash检测法如今已经不多见。</p>
|
||||
</blockquote>
|
||||
<p><strong>TTL修复</strong>:</p>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>依赖包
|
||||
</span><span>opkg install kmod-nft-core kmod-nft-bridge kmod-nft-net kmod-nft-offload kmod-nft-nat
|
||||
</span><span>
|
||||
</span><span>首先检查 mangle 表是否存在
|
||||
</span><span>nft list tables
|
||||
</span><span>
|
||||
</span><span>创建 mangle 表（如果不存在）
|
||||
</span><span>nft add table ip mangle
|
||||
</span><span>
|
||||
</span><span>创建 POSTROUTING 链（如果不存在）
|
||||
</span><span>nft add chain ip mangle POSTROUTING { type nat hook postrouting priority 0 \; }
|
||||
</span><span>
|
||||
</span><span>
|
||||
</span><span>添加 TTL 规则
|
||||
</span><span>nft add rule ip mangle POSTROUTING ip ttl set 64
|
||||
</span><span>
|
||||
</span><span>检查规则是否生效
|
||||
</span><span>nft list table ip mangle
|
||||
</span></code></pre>
|
||||
<h2 id="openwrtgai-apmo-shi">Openwrt改AP模式</h2>
|
||||
<p>有时候我们使用X86做主路由，想让无线路由器只起到发射信号的作用，就可以将其改为AP模式，一般步骤为：</p>
|
||||
<ul>
|
||||
<li>更改lan地址，将lan口地址改到主路由下的一个IP;</li>
|
||||
<li>关闭DHCP服务；</li>
|
||||
<li>关闭WAN口；</li>
|
||||
<li>关闭防火墙的禁止转发规则，全部允许；</li>
|
||||
<li>将X86主路由的网线插到AP的任意一个LAN口。</li>
|
||||
</ul>
|
||||
<h2 id="link">🔗</h2>
|
||||
<ul>
|
||||
<li><a href="https://openwrt.org/zh/docs/start">Openwrt wiki</a></li>
|
||||
<li><a href="https://openwrt.ai/?target=ipq807x%2Fgeneric&id=xiaomi_ax3600">OpenWrt在线定制编译</a></li>
|
||||
<li><a href="https://www.cnblogs.com/tfel-ypoc/p/17226064.html">openwrt luci 页面无法访问 问题排查</a></li>
|
||||
<li><a href="https://post.smzdm.com/p/axz6369w/">超详细，多图，简单，OpenWRT 设置，IPV6配置</a></li>
|
||||
<li><a href="https://blog.csdn.net/weixin_44548582/article/details/121064734">保姆级-光猫改桥接-路由拨号-openwrt端口转发</a></li>
|
||||
</ul>
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
<div class="pagination">
|
||||
<div class="pagination__title">
|
||||
<span class="pagination__title-h">Thanks for reading! Read other posts?</span>
|
||||
<hr />
|
||||
</div>
|
||||
<div class="pagination__buttons">
|
||||
<span class="button previous">
|
||||
<a href="https://blog.dich.bid/awesome-pve-mcsm/">
|
||||
<span class="button__icon">←</span>
|
||||
<span class="button__text">综合工程:PVE安装与MC服务器搭建</span>
|
||||
</a>
|
||||
</span>
|
||||
|
||||
|
||||
<span class="button next">
|
||||
<a href="https://blog.dich.bid/awesome-android-root/">
|
||||
<span class="button__text">综合工程:安卓刷机与root教程</span>
|
||||
<span class="button__icon">→</span>
|
||||
</a>
|
||||
</span>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
</div>
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
<footer class="footer">
|
||||
<div class="footer__inner">
|
||||
<div class="copyright">
|
||||
<span>©
|
||||
2025
|
||||
Dichgrem</span>
|
||||
<span class="copyright-theme">
|
||||
<span class="copyright-theme-sep"> :: CC BY-SA 4.0 :: A friend comes from distant lands</span>
|
||||
</a>
|
||||
</span>
|
||||
</div>
|
||||
</div>
|
||||
</footer>
|
||||
|
||||
</div>
|
||||
</body>
|
||||
</html>
|
||||
|
||||
296
public/awesome-pve-mcsm/index.html
Normal file
296
public/awesome-pve-mcsm/index.html
Normal file
@ -0,0 +1,296 @@
|
||||
<!DOCTYPE html>
|
||||
<html lang="en">
|
||||
|
||||
<head>
|
||||
<title>Dich'blog</title>
|
||||
|
||||
<meta http-equiv="content-type" content="text/html; charset=utf-8">
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1">
|
||||
<meta name="robots" content="noodp"/>
|
||||
|
||||
<link rel="stylesheet" href="https://blog.dich.bid/style.css">
|
||||
<link rel="stylesheet" href="https://blog.dich.bid/color/blue.css">
|
||||
|
||||
<link rel="stylesheet" href="https://blog.dich.bid/color/background_dark.css">
|
||||
|
||||
<link rel="stylesheet" href="https://blog.dich.bid/font-hack-subset.css">
|
||||
|
||||
<meta name="description" content="">
|
||||
|
||||
<meta property="og:description" content="">
|
||||
<meta property="og:title" content="Dich'blog">
|
||||
<meta property="og:type" content="article">
|
||||
<meta property="og:url" content="https://blog.dich.bid/awesome-pve-mcsm/">
|
||||
|
||||
<meta name="twitter:card" content="summary_large_image">
|
||||
<meta name="twitter:description" content="">
|
||||
<meta name="twitter:title" content="Dich'blog">
|
||||
<meta property="twitter:domain" content="blog.dich.bid">
|
||||
<meta property="twitter:url" content="https://blog.dich.bid/awesome-pve-mcsm/">
|
||||
|
||||
<link rel="alternate" type="application/atom+xml" title="Dich'blog Atom Feed" href="https://blog.dich.bid/atom.xml" />
|
||||
|
||||
|
||||
<link rel="icon" type="image/png" href=/dich.webp />
|
||||
|
||||
<!-- ✅ Added center alignment styles -->
|
||||
<style>
|
||||
.footer {
|
||||
text-align: center;
|
||||
padding: 1rem 0;
|
||||
}
|
||||
|
||||
.footer__inner {
|
||||
display: flex;
|
||||
justify-content: center;
|
||||
flex-direction: column;
|
||||
align-items: center;
|
||||
}
|
||||
|
||||
.copyright {
|
||||
text-align: center;
|
||||
}
|
||||
</style>
|
||||
</head>
|
||||
|
||||
<body class="">
|
||||
<div class="container">
|
||||
|
||||
<header class="header">
|
||||
<div class="header__inner">
|
||||
<div class="header__logo">
|
||||
|
||||
<a href="https://blog.dich.bid" style="text-decoration: none;">
|
||||
<div class="logo">
|
||||
|
||||
Dich'blog
|
||||
|
||||
</div>
|
||||
</a>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
|
||||
|
||||
<nav class="menu">
|
||||
<ul class="menu__inner">
|
||||
<li class="active"><a href="https://blog.dich.bid">blog</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/archive">archive</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/tags">tags</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/weekly">weekly</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/search">search</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/about">about me</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/links">links</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/atom.xml">rss</a></li>
|
||||
|
||||
<li><a href="https://github.com/Dichgrem" target="_blank" rel="noopener noreferrer">github</a></li>
|
||||
</ul>
|
||||
</nav>
|
||||
|
||||
|
||||
|
||||
</header>
|
||||
|
||||
|
||||
<div class="content">
|
||||
|
||||
<div class="post">
|
||||
|
||||
<h1 class="post-title"><a href="https://blog.dich.bid/awesome-pve-mcsm/">综合工程:PVE安装与MC服务器搭建</a></h1>
|
||||
<div class="post-meta-inline">
|
||||
|
||||
<span class="post-date">
|
||||
2023-08-11
|
||||
</span>
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
<span class="post-tags-inline">
|
||||
:: tags:
|
||||
<a class="post-tag" href="https://blog.dich.bid/tags/zong-he-gong-cheng/">#综合工程</a></span>
|
||||
|
||||
|
||||
<div class="post-content">
|
||||
<p>前言 假期将至，不少家里有闲置设备的小伙伴想尝试开设一个我的世界（Minecraft）服务器，却不知从何下手。本文以 PVE-Debian-MCSM 为主线介绍其部署流程。</p>
|
||||
<span id="continue-reading"></span><h2 id="shen-me-shi-pve">什么是PVE？</h2>
|
||||
<p>PVE (全称 Proxmox Virtual Environment) 是一款开源免费的虚拟化环境平台，同时支持KVM 虚拟机和 LXC 容器。它基于 Debian 和 KVM 技术开发，可在一台 PC 或服务器上同时运行Linux、OpenWRT、Windows 等，实现计算、网络、存储一体化解决方案，即所谓的“all in one”。类似的平台还有ESXi、Unraid等。</p>
|
||||
<h2 id="shen-me-shi-mcsm">什么是MCSM？</h2>
|
||||
<p>MCSManager 面板（简称：MCSM 面板）是一款全中文，轻量级，开箱即用，多实例和支持 Docker 的 Minecraft 服务端管理面板。</p>
|
||||
<p>此软件在 Minecraft 和其他游戏社区内中已有一定的流行程度，它可以帮助你集中管理多个物理服务器，动态在任何主机上创建游戏服务端，并且提供安全可靠的多用户权限系统，可以很轻松的帮助你管理多个服务器。
|
||||
具体步骤：安装PVE并优化，开设虚拟机并安装Debian，安装mscm界面并开设实例，配置网络服务。</p>
|
||||
<h2 id="zhun-bei-gong-zuo">准备工作</h2>
|
||||
<ul>
|
||||
<li>
|
||||
<p>1.<a href="https://www.proxmox.com/en/downloads">PVE镜像，推荐使用7.4版本</a></p>
|
||||
</li>
|
||||
<li>
|
||||
<p>2.<a href="https://mirrors.tuna.tsinghua.edu.cn/debian/dists/">Debian镜像</a>（不建议使用DVD版，会出现奇怪的问题。）</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>3.<a href="https://www.423down.com/10080.html">我们的老伙计Rufus</a></p>
|
||||
</li>
|
||||
<li>
|
||||
<p>4.<a href="https://purpurmc.org/">Purpur1.19 服务端</a></p>
|
||||
</li>
|
||||
<li>
|
||||
<p>5.<a href="https://hmcl.huangyuhui.net/">MC启动器HMCL</a></p>
|
||||
</li>
|
||||
<li>
|
||||
<p>6.<a href="https://www.zerotier.com/download/">Zerotier客户端</a></p>
|
||||
</li>
|
||||
</ul>
|
||||
<h2 id="yi-an-zhuang-pvebing-you-hua">一.安装PVE并优化</h2>
|
||||
<p>1.将下载好的镜像用Rufus写入U盘。</p>
|
||||
<p>2.将U盘插到目标主机上面，进入BIOS-boot设置启动顺序。这里我使用二手浪潮服务器X99主板，矿龙电源以及一块128G的SSD固态。注意：大部分服务器主板有机箱入侵检测机制，需要在说明书中找到特定针脚并用导电帽盖上，否则无法开机。</p>
|
||||
<p>3.进入安装界面，选择install；
|
||||
随后跑码，进入如下界面，同意协议：
|
||||
设置硬盘与文件类型，可以选择ext4或者btrfs;
|
||||
选择国家与地区，这里需要手打出China；
|
||||
随后设置密码与邮件，邮件可以随便填：
|
||||
然后设置网络连接，这里插网线就有地址；设置主机名，并记下内网IP地址；
|
||||
检查无误后开始安装：
|
||||
安装完成后 reboot。</p>
|
||||
<p>4.浏览器打开 PVE 地址，进入系统后我们需要给PVE换源。</p>
|
||||
<h2 id="huan-yuan">换源</h2>
|
||||
<p><strong>禁用 Ceph 企业仓库:</strong></p>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>nano /etc/apt/sources.list.d/ceph.list
|
||||
</span></code></pre>
|
||||
<p>将文件内容注释掉或删除。</p>
|
||||
<p><strong>编辑仓库源文件：</strong></p>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>nano /etc/apt/sources.list.d/pve-enterprise.list
|
||||
</span></code></pre>
|
||||
<p>将文件内容注释掉或删除;</p>
|
||||
<p><strong>启用社区仓库:</strong></p>
|
||||
<p>确保社区仓库已启用。编辑社区仓库文件：</p>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>nano /etc/apt/sources.list.d/pve-no-subscription.list
|
||||
</span></code></pre>
|
||||
<p>确保文件内容如下：</p>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>deb http://download.proxmox.com/debian/pve bookworm pve-no-subscription
|
||||
</span></code></pre>
|
||||
<h2 id="er-xin-jian-xu-ni-ji-bing-an-zhuang-debian">二.新建虚拟机并安装Debian</h2>
|
||||
<p>1.找到 local-btrfs(pve),在其中的 ISO 中上传下载好的 Debian 镜像；</p>
|
||||
<p>2.随后创建虚拟机，选择 Debian 镜像并设置 CPU 核数与硬盘、内存大小；</p>
|
||||
<p>3.一路确认后开机进入命令行界面，即可开始Debian安装。我们选择graphical install：</p>
|
||||
<p>4.选择国家和语言，随后自动配置网络；</p>
|
||||
<p>5.设置主机名，跳过域名设置；设置 root 账户名和密码、普通用户账户名与密码；</p>
|
||||
<p>6.对磁盘进行分区，由于是虚拟机我们选择使用整个磁盘；</p>
|
||||
<p>7.安装基本系统，随后将进入包管理器和大组件安装；</p>
|
||||
<p>我们选择清华源，速度较快。注意：Debian 安装时默认开启安全源，这个源是国外的所以下载速度极慢，因此还需要修改配置文件。</p>
|
||||
<p>在安装步骤进入到选择安装的桌面环境和软件时, 键入 Ctrl+Alt+F2 可以看到从图形界面转到了tty命令终端, 键入 Enter
|
||||
这里修改软件源配置文件</p>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>nano /target/etc/apt/sources.list
|
||||
</span></code></pre>
|
||||
<p>修改debian-security源地址 <code>http://mirrors.ustc.edu.cn </code> 目测最快</p>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>deb http://mirrors.ustc.edu.cn/debian-security bullseye-security main
|
||||
</span></code></pre>
|
||||
<p>修改后 Ctrl+X 退出保存,然后退出终端重新进入界面继续安装，键入 Ctrl+Alt+F5。</p>
|
||||
<p>下载需要一些时间，此时可以饮口茶先，随后看到如下界面：</p>
|
||||
<p>由于是服务器所以不需要桌面环境：</p>
|
||||
<p>安装 grub 引导：</p>
|
||||
<p>随后安装完成，reboot后进入mscm的安装。</p>
|
||||
<h2 id="san-an-zhuang-mcsmbing-kai-she-shi-li">三.安装MCSM并开设实例</h2>
|
||||
<p><strong>1.开机进入tty1界面</strong></p>
|
||||
<p><strong>2.安装JAVA环境</strong>，不同版本的游戏的 Java 版本也不同。这里我们使用1.19版，需要安装 Java18。</p>
|
||||
<p>安装 wget 和 下载 Java18</p>
|
||||
<p><code>apt install wget && wget http://img.zeruns.tech/down/Java/OpenJDK18U-jre_x64_linux_hotspot_18.0.1_10.tar.gz</code></p>
|
||||
<p>创建安装目录</p>
|
||||
<p><code>mkdir /usr/local/java/</code></p>
|
||||
<p>解压当前目录下的 JDK 压缩文件</p>
|
||||
<p><code>tar -zxvf OpenJDK18U-jre_x64_linux_hotspot_18.0.1_10.tar.gz -C /usr/local/java/</code></p>
|
||||
<p>软链接程序到环境变量中</p>
|
||||
<p><code>ln -sf /usr/local/java/jdk-18.0.1+10-jre/bin/java /usr/bin/java</code></p>
|
||||
<p>测试是否安装正常，显示 <code>openjdk version "18.0.1" 2022-04-19</code> 则为正常</p>
|
||||
<p><code>java -version</code></p>
|
||||
<p><strong>3.端口开发</strong>，面板需要 23333和24444 端口，游戏服务器默认端口是 25565。</p>
|
||||
<p>在 PVE-防火墙中打开它们。如果还是不行，执行如下命令：</p>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>systemctl stop firewalld
|
||||
</span><span>
|
||||
</span><span>systemctl disable firewalld
|
||||
</span><span>
|
||||
</span><span>service iptables stop
|
||||
</span></code></pre>
|
||||
<p>从而关闭防火墙。</p>
|
||||
<p><strong>4.安装面板</strong>，这里使用一键安装命令（注意该脚本仅适用于 AMD64 架构）</p>
|
||||
<p><code>wget -qO- https://gitee.com/mcsmanager/script/raw/master/setup.sh | bash</code></p>
|
||||
<p>执行完成后，使用 <code>systemctl start mcsm-{web,daemon} </code>即可启动面板服务。使用 <code>systemctl enable mcsm-{daemon,web}.service </code>实现开机自启。</p>
|
||||
<p><strong>5.在浏览器中打开该地址</strong>加上23333端口后缀，即可看到面板，账户为root，密码为123456。</p>
|
||||
<p><strong>6.新建实例</strong>，上传 Purpur1.19 服务端,设置名称随后开启实例</p>
|
||||
<p><strong>7.随后我们可以在</strong> 配置文件中设置游戏的相关选项，如关闭正版验证等。</p>
|
||||
<p><strong>8.大功告成</strong>，此时打开 HMCL 启动器，即可加入游戏。</p>
|
||||
<h2 id="si-pei-zhi-lian-ji-wang-luo">四.配置联机网络</h2>
|
||||
<p>1.此时不要忘记需要和小伙伴们一起玩耍。如果你家里有公网固定 IPv4 或者 IPv6，直接输入联机即可；如果没有公网IP，此时就需要进行内网穿透或者DDNS。</p>
|
||||
<p>这里介绍一种名为 zerotier 的工具。</p>
|
||||
<p>2.首先在 https://www.zerotier.com/ 注册并创建一个私有网络；</p>
|
||||
<p>3.首先在虚拟机中安装 curl 命令支持</p>
|
||||
<p><code>apt-get install curl</code></p>
|
||||
<p>4.安装gnupg非对称信息加密系统，通讯所需必备软件</p>
|
||||
<p><code>apt-get install gnupg</code></p>
|
||||
<p>5.安装 ZeroTier</p>
|
||||
<p><code>curl -s https://install.zerotier.com/ | bash</code></p>
|
||||
<p>安装成功后提示如下：</p>
|
||||
<p><code>Success! You are ZeroTier address [ xxxxxxxxx ].</code></p>
|
||||
<p>方括号内地址为类似于MAC地址。</p>
|
||||
<p>6.设定开机自启动（分别执行如下命令）</p>
|
||||
<p><code>systemctl start zerotier-one.service</code></p>
|
||||
<p><code>systemctl enable zerotier-one.service</code></p>
|
||||
<p>7.加入自己的私有网络</p>
|
||||
<p><code>zerotier-cli join xxxxxxxxx</code></p>
|
||||
<p>8.大功告成!此时只要让小伙伴们下载 zerotier 客户端并加入相同的私有网络，即可一起快乐联机！</p>
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
<div class="pagination">
|
||||
<div class="pagination__title">
|
||||
<span class="pagination__title-h">Thanks for reading! Read other posts?</span>
|
||||
<hr />
|
||||
</div>
|
||||
<div class="pagination__buttons">
|
||||
<span class="button previous">
|
||||
<a href="https://blog.dich.bid/awesome-vm-android/">
|
||||
<span class="button__icon">←</span>
|
||||
<span class="button__text">综合工程:linux搭建安卓虚拟机</span>
|
||||
</a>
|
||||
</span>
|
||||
|
||||
|
||||
<span class="button next">
|
||||
<a href="https://blog.dich.bid/awesome-openwrt/">
|
||||
<span class="button__text">综合工程:OpenWrt路由部署与软件编译</span>
|
||||
<span class="button__icon">→</span>
|
||||
</a>
|
||||
</span>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
</div>
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
<footer class="footer">
|
||||
<div class="footer__inner">
|
||||
<div class="copyright">
|
||||
<span>©
|
||||
2025
|
||||
Dichgrem</span>
|
||||
<span class="copyright-theme">
|
||||
<span class="copyright-theme-sep"> :: CC BY-SA 4.0 :: A friend comes from distant lands</span>
|
||||
</a>
|
||||
</span>
|
||||
</div>
|
||||
</div>
|
||||
</footer>
|
||||
|
||||
</div>
|
||||
</body>
|
||||
</html>
|
||||
|
||||
457
public/awesome-vm-android/index.html
Normal file
457
public/awesome-vm-android/index.html
Normal file
@ -0,0 +1,457 @@
|
||||
<!DOCTYPE html>
|
||||
<html lang="en">
|
||||
|
||||
<head>
|
||||
<title>Dich'blog</title>
|
||||
|
||||
<meta http-equiv="content-type" content="text/html; charset=utf-8">
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1">
|
||||
<meta name="robots" content="noodp"/>
|
||||
|
||||
<link rel="stylesheet" href="https://blog.dich.bid/style.css">
|
||||
<link rel="stylesheet" href="https://blog.dich.bid/color/blue.css">
|
||||
|
||||
<link rel="stylesheet" href="https://blog.dich.bid/color/background_dark.css">
|
||||
|
||||
<link rel="stylesheet" href="https://blog.dich.bid/font-hack-subset.css">
|
||||
|
||||
<meta name="description" content="">
|
||||
|
||||
<meta property="og:description" content="">
|
||||
<meta property="og:title" content="Dich'blog">
|
||||
<meta property="og:type" content="article">
|
||||
<meta property="og:url" content="https://blog.dich.bid/awesome-vm-android/">
|
||||
|
||||
<meta name="twitter:card" content="summary_large_image">
|
||||
<meta name="twitter:description" content="">
|
||||
<meta name="twitter:title" content="Dich'blog">
|
||||
<meta property="twitter:domain" content="blog.dich.bid">
|
||||
<meta property="twitter:url" content="https://blog.dich.bid/awesome-vm-android/">
|
||||
|
||||
<link rel="alternate" type="application/atom+xml" title="Dich'blog Atom Feed" href="https://blog.dich.bid/atom.xml" />
|
||||
|
||||
|
||||
<link rel="icon" type="image/png" href=/dich.webp />
|
||||
|
||||
<!-- ✅ Added center alignment styles -->
|
||||
<style>
|
||||
.footer {
|
||||
text-align: center;
|
||||
padding: 1rem 0;
|
||||
}
|
||||
|
||||
.footer__inner {
|
||||
display: flex;
|
||||
justify-content: center;
|
||||
flex-direction: column;
|
||||
align-items: center;
|
||||
}
|
||||
|
||||
.copyright {
|
||||
text-align: center;
|
||||
}
|
||||
</style>
|
||||
</head>
|
||||
|
||||
<body class="">
|
||||
<div class="container">
|
||||
|
||||
<header class="header">
|
||||
<div class="header__inner">
|
||||
<div class="header__logo">
|
||||
|
||||
<a href="https://blog.dich.bid" style="text-decoration: none;">
|
||||
<div class="logo">
|
||||
|
||||
Dich'blog
|
||||
|
||||
</div>
|
||||
</a>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
|
||||
|
||||
<nav class="menu">
|
||||
<ul class="menu__inner">
|
||||
<li class="active"><a href="https://blog.dich.bid">blog</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/archive">archive</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/tags">tags</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/weekly">weekly</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/search">search</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/about">about me</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/links">links</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/atom.xml">rss</a></li>
|
||||
|
||||
<li><a href="https://github.com/Dichgrem" target="_blank" rel="noopener noreferrer">github</a></li>
|
||||
</ul>
|
||||
</nav>
|
||||
|
||||
|
||||
|
||||
</header>
|
||||
|
||||
|
||||
<div class="content">
|
||||
|
||||
<div class="post">
|
||||
|
||||
<h1 class="post-title"><a href="https://blog.dich.bid/awesome-vm-android/">综合工程:linux搭建安卓虚拟机</a></h1>
|
||||
<div class="post-meta-inline">
|
||||
|
||||
<span class="post-date">
|
||||
2023-08-10
|
||||
</span>
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
<span class="post-tags-inline">
|
||||
:: tags:
|
||||
<a class="post-tag" href="https://blog.dich.bid/tags/zong-he-gong-cheng/">#综合工程</a></span>
|
||||
|
||||
|
||||
<div class="post-content">
|
||||
<p>前言 linux搭建安卓虚拟机有Waydroid，QEMU和Docker三种方案，各有不同。</p>
|
||||
<span id="continue-reading"></span><h1 id="waydroid">Waydroid</h1>
|
||||
<p>Waydroid是Anbox配合Halium技术开发的LXC Android容器，可在GNU/Linux系统执行Android APP。以下是Waydroid的特色功能：</p>
|
||||
<ul>
|
||||
<li>开源</li>
|
||||
<li>支持x86与ARM架构</li>
|
||||
<li>与宿主机共用剪切板</li>
|
||||
<li>直接使用电脑显卡硬件加速</li>
|
||||
<li>內建GAPPS，可以使用Google Play</li>
|
||||
<li>支持Magisk</li>
|
||||
</ul>
|
||||
<blockquote>
|
||||
<p>Waydroid执行时的Android系统资料放在<code>~/.local/share/waydroid/data/</code>，系统映像档位于<code>/var/lib/waydroid</code>，APP图示位于<code>~/.local/share/applications/</code></p>
|
||||
</blockquote>
|
||||
<h2 id="an-zhuang-qian-zhun-bei">安装前准备</h2>
|
||||
<p>目前Waydroid只支持Intel和AMD的显卡，对于 NVIDIA 显卡（除 Tegra 系列外），Waydroid 不支持硬件加速，推荐使用软件渲染或QEMU方案。</p>
|
||||
<ul>
|
||||
<li>Waydroid必须使用Wayland，用此命令检查当前系统是否为Wayland：</li>
|
||||
</ul>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>echo $XDG_SESSION_TYPE
|
||||
</span></code></pre>
|
||||
<p>若显示X11代表不是Wayland。GNOME和KDE可在登入画面切换至Wayland工作阶段。</p>
|
||||
<ul>
|
||||
<li>Waydroid要求Linux核心支持binder核心模组，但Arch Linux预设的linux核心並无开启此选项，因此需要从AUR安装binder_linux-dkms补齐。</li>
|
||||
</ul>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>paru -S binder_linux-dkms
|
||||
</span></code></pre>
|
||||
<ul>
|
||||
<li>安装后载入binder核心模组</li>
|
||||
</ul>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>sudo modprobe binder-linux devices=binder,hwbinder,vndbinder
|
||||
</span></code></pre>
|
||||
<ul>
|
||||
<li>设定开机自动载入核心模组</li>
|
||||
</ul>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>echo "binder_linux" | sudo tee -a /etc/modules-load.d/binder_linux.conf
|
||||
</span><span>
|
||||
</span><span>echo "options binder_linux devices=binder,hwbinder,vndbinder" | sudo tee -a /etc/modprobe.d/binder_linux.conf
|
||||
</span></code></pre>
|
||||
<h2 id="an-zhuang-waydroid">安装Waydroid</h2>
|
||||
<ul>
|
||||
<li>安装以下软件包，让Linux与Waydroid共享剪切板</li>
|
||||
</ul>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>paru -S wl-clipboard xclip
|
||||
</span><span>paru -S python-pyclip
|
||||
</span></code></pre>
|
||||
<ul>
|
||||
<li>安装Waydroid</li>
|
||||
</ul>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>paru -S waydroid
|
||||
</span></code></pre>
|
||||
<ul>
|
||||
<li>初始化Waydroid，下载含有GAPPS的Android系统映像档</li>
|
||||
</ul>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>sudo waydroid init -s GAPPS -f
|
||||
</span></code></pre>
|
||||
<ul>
|
||||
<li>启动Waydroid容器服务</li>
|
||||
</ul>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>sudo systemctl start waydroid-container
|
||||
</span></code></pre>
|
||||
<h2 id="chang-yong-ming-ling">常用命令</h2>
|
||||
<ul>
|
||||
<li>开机自动启动</li>
|
||||
</ul>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>sudo systemctl enable waydroid-container
|
||||
</span></code></pre>
|
||||
<ul>
|
||||
<li>点选应用列表的「Waydroid」图示开启主画面，或者使用命令：</li>
|
||||
</ul>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>waydroid show-full-ui
|
||||
</span></code></pre>
|
||||
<ul>
|
||||
<li>若Waydroid无法连上网路，开放UFW防火墙：</li>
|
||||
</ul>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>sudo ufw allow 53
|
||||
</span><span>sudo ufw allow 67
|
||||
</span><span>sudo ufw default allow FORWARD
|
||||
</span><span>sudo ufw reload
|
||||
</span><span>sudo systemctl restart waydroid-container
|
||||
</span></code></pre>
|
||||
<ul>
|
||||
<li>重启Waydroid</li>
|
||||
</ul>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>sudo systemctl restart waydroid-container
|
||||
</span></code></pre>
|
||||
<ul>
|
||||
<li>启动/停止Waydroid容器服务</li>
|
||||
</ul>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>sudo systemctl start waydroid-container
|
||||
</span><span>sudo systemctl stop waydroid-container
|
||||
</span></code></pre>
|
||||
<ul>
|
||||
<li>用命令开启Waydroid主画面</li>
|
||||
</ul>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>waydroid show-full-ui
|
||||
</span></code></pre>
|
||||
<ul>
|
||||
<li>查看系统错误讯息</li>
|
||||
</ul>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>waydroid log
|
||||
</span><span>sudo waydroid logcat
|
||||
</span></code></pre>
|
||||
<ul>
|
||||
<li>强制屏幕旋转</li>
|
||||
</ul>
|
||||
<p>安装Rotation Control这类APP，即可强制调整Waydroid屏幕方向.</p>
|
||||
<ul>
|
||||
<li>模拟Wifi</li>
|
||||
</ul>
|
||||
<p>安装Package Manager，用於查看APP的软件包名称。</p>
|
||||
<p>部份APP会要求开启Wifi才能上网，那么就如它所愿，开启fake wifi：</p>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>waydroid prop set persist.waydroid.fake_wifi "软件包名称"
|
||||
</span></code></pre>
|
||||
<p>例如给Fate/Go游戏开启模拟Wifi：</p>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>waydroid prop set persist.waydroid.fake_wifi "com.aniplex.fategrandorder"
|
||||
</span></code></pre>
|
||||
<ul>
|
||||
<li>模拟触控功能</li>
|
||||
</ul>
|
||||
<p>安装Package Manager，用於查看APP的软件包名称。有些APP认不到鼠标点击，需要启用模拟触控(fake touch)：</p>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>waydroid prop set persist.waydroid.fake_touch "软件包名称"
|
||||
</span></code></pre>
|
||||
<p>例如给Fate/Go游戏开启模拟触控：</p>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>waydroid prop set persist.waydroid.fake_touch "com.aniplex.fategrandorder"
|
||||
</span></code></pre>
|
||||
<ul>
|
||||
<li>用命令安装APK</li>
|
||||
</ul>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>waydroid app install <APK档案路径>.apk
|
||||
</span></code></pre>
|
||||
<ul>
|
||||
<li>进入ADB Shell</li>
|
||||
</ul>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>sudo waydroid shell
|
||||
</span></code></pre>
|
||||
<ul>
|
||||
<li>开启多视窗模式</li>
|
||||
</ul>
|
||||
<p>Waydroid的多视窗模式，看起来像Linux的原生应用。启动后按F11改回来。</p>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>waydroid prop set persist.waydroid.multi_windows true
|
||||
</span><span>sudo systemctl restart waydroid-container
|
||||
</span></code></pre>
|
||||
<h2 id="jiang-waydroidzhu-ce-wei-googlezhuang-zhi">将Waydroid注册为Google装置</h2>
|
||||
<p>Waydroid第一次开机可能会收到<code>Device is not Play Protect certified</code>的通知，无法登入Google账号。</p>
|
||||
<p>用以下命令取得Waydroid的装置ID。该命令会印出一长串数字。</p>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>sudo waydroid shell
|
||||
</span><span>
|
||||
</span><span>ANDROID_RUNTIME_ROOT=/apex/com.android.runtime ANDROID_DATA=/data ANDROID_TZDATA_ROOT=/apex/com.android.tzdata ANDROID_I18N_ROOT=/apex/com.android.i18n sqlite3 /data/data/com.google.android.gsf/databases/gservices.db "select * from main where name = \"android_id\";"
|
||||
</span></code></pre>
|
||||
<p>开启装置注册页面，登入Google账号，输入装置ID注册，等个半小时应该就能登入Google账号了。如果还是不行就重新启动Waydroid容器服务：</p>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>sudo systemctl restart waydroid-container
|
||||
</span></code></pre>
|
||||
<p>现在可以安装APP了，Google Play和F-Droid会自动筛出適合x86架构的APP。</p>
|
||||
<h1 id="qemu-kvm">QEMU/KVM</h1>
|
||||
<h2 id="gai-shu">概述</h2>
|
||||
<p>Bliss OS 是基于 Android-x86 的开源系统，已更新至 Android 13，并内建 Google Play 商店，可直接运行 64 位 APK，无需额外转译器；在 Linux 上通过 QEMU/KVM + virglrenderer 实现 GPU 加速，使得在虚拟机中也能流畅体验手游。</p>
|
||||
<h2 id="wei-shen-me-xuan-ze-bliss-os">为什么选择 Bliss OS？</h2>
|
||||
<ul>
|
||||
<li><strong>版本更新快</strong>：Bliss OS 最新测试版基于 Android 13，而 Android-x86 官方仅更新至 Android 9。</li>
|
||||
<li><strong>更完善的 ARM 转译</strong>：采用 Google libndk，可兼容 64 位 ARM-v8a APK；相比仅支持 32 位 ARM-v7 的 liboudini，兼容性大幅提升。</li>
|
||||
<li><strong>丰富实用功能</strong>：预装强制旋转、按键映射、游戏模式、模拟触控点击、KernelSU（难以检测的 root 权限）和 Gearlock 恢复环境等增强工具，提升桌面化体验。</li>
|
||||
</ul>
|
||||
<h2 id="huan-jing-zhun-bei">环境准备</h2>
|
||||
<ul>
|
||||
<li><strong>硬件要求</strong>：CPU 要开启 <code>VT-x/AMD-V</code>，并加载 KVM 内核模块；Intel 10 代及更新集成 GPU 可用，AMD 同理；闭源 Nvidia 驱动下 virglrenderer 不稳定，不建议使用硬件加速。</li>
|
||||
<li><strong>软件安装</strong>：在宿主机上安装 QEMU (≥8.1.1)、Libvirt、Virt-Manager，并部署 virglrenderer (≥0.10.4) 以获得半虚拟化 3D 加速；Ubuntu 与 Arch 安装方法分别见官方文档。</li>
|
||||
<li><strong>性能调优</strong>：可参考 Red Hat 虚拟化性能调优指南，启用 IOMMU、调整 CPU 调度与内存缓存策略，以提升 KVM 性能。</li>
|
||||
</ul>
|
||||
<h2 id="an-zhuang-liu-cheng-yu-fen-qu">安装流程与分区</h2>
|
||||
<ol>
|
||||
<li>从官方站点下载带 GApps 的 Bliss OS 15.x ISO 镜像，并在 Virt-Manager 中新建虚拟机，选择 <code>Q35 芯片组、UEFI (OVMF)</code>。</li>
|
||||
<li>推荐分配 ≥8 GB RAM、4 核 CPU 及 ≥64 GB 虚拟硬盘，并勾选 OpenGL、VirtIO 显示卡 + 3D 加速。</li>
|
||||
<li>进入 Bliss OS 安装器，使用 GPT 分区表：
|
||||
<ul>
|
||||
<li>首分区 512 MB，类型 EFI (<code>ef00</code>)，挂载点 <code>/mnt/efi</code>；</li>
|
||||
<li>次分区 全盘剩余空间格式化为 Ext4，用于系统安装。</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>安装 GRUB、格式化分区后强制关机，移除 ISO 并重启，即可启动已启用 virglrenderer 加速的系统。</li>
|
||||
</ol>
|
||||
<h2 id="fen-bian-lu-diao-zheng">分辨率调整</h2>
|
||||
<ul>
|
||||
<li>启动时选择 “Debug QEMU/KVM VirGL” 进入 shell，通过 <code>blkid</code> 找到 EFI 分区（如 <code>/dev/sda1</code>），挂载后编辑 <code>/mnt/efi/boot/android.cfg</code>：
|
||||
<ul>
|
||||
<li>在 <code>linux $kd/kernel</code> 行末添加 <code>video=1920x1080</code>；</li>
|
||||
<li>修改 <code>set gfxmode=</code> 为相应分辨率，保存并重启即可生效。</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>如需更灵活调整，可在系统内安装 SecondScreen 等第三方工具强制改分辨率。</li>
|
||||
</ul>
|
||||
<h2 id="xi-tong-shi-yong-ji-qiao">系统使用技巧</h2>
|
||||
<ul>
|
||||
<li>默认启用 Boringdroid 桌面模式，底部常驻任务栏；可在设置里为特定应用强制全屏运行。</li>
|
||||
<li>强制旋转：内置 Set Orientation 或使用更佳的 OHMAE Ryosuke 工具；屏幕录制推荐宿主机通过 OBS 采集 VM 窗口。</li>
|
||||
<li>多窗口：开发者选项启用“自由形式窗口”；Root 需在 KernelSU 中对指定应用授权，Termux 可提供终端环境。</li>
|
||||
<li>ADB 调试：可通过无线 ADB 连接，并在 shell 中为 <code>com.android.shell</code> 授予 Root 权限。</li>
|
||||
</ul>
|
||||
<h2 id="shou-you-shi-ce">手游实测</h2>
|
||||
<ul>
|
||||
<li>优先安装原生 x86 版游戏，减少 ARM 转译开销；多游戏如《水果忍者》、《Temple Run 2》均能流畅运行。</li>
|
||||
<li>部分大型游戏（如《原神》）因 virglrenderer 不稳定在着色器编译时易崩溃；《幻塔》可正常进入并游玩。</li>
|
||||
<li>若触控事件不响应，可启用 “Force Mouse Click as touch” 强制映射鼠标点击，但会导致滚轮失效；开启“游戏模式”可屏蔽通知并悬浮截屏。</li>
|
||||
</ul>
|
||||
<h1 id="docker">Docker</h1>
|
||||
<h2 id="gai-shu-1">概述</h2>
|
||||
<p>ReDroid（Remote-Android）是一款开源的容器化 Android 解决方案，支持在 x86 主机通过 Docker、Podman 或 Kubernetes 启动多实例 Android 系统，并提供 GPU 加速与多架构（arm64/amd64）支持，适用于云端游戏、自动化测试、虚拟手机等场景。本文从环境准备、部署配置、日常使用及进阶定制等方面，逐步讲解如何在 Linux 主机上用 Docker 容器运行并优化 ReDroid，使其能够流畅运行 ARM 架构的手游。</p>
|
||||
<h2 id="shen-me-shi-redroid">什么是 ReDroid？</h2>
|
||||
<ul>
|
||||
<li><strong>项目简介</strong>：ReDroid 即 Remote-Android，是一个多架构、GPU 加速的“Android In Cloud”（AIC）方案，可在任何具备必要内核特性（如 binderfs）的 Linux 主机上部署 Android 容器。</li>
|
||||
<li><strong>版本支持</strong>：活跃维护 Android 11–15 多个版本的镜像，并提供丰富的文档与社区支持。</li>
|
||||
<li><strong>应用场景</strong>：适用于云游戏、自动化测试、连续集成中的 UI 测试、远程开发等多种场景。</li>
|
||||
</ul>
|
||||
<h2 id="huan-jing-yu-yi-lai">环境与依赖</h2>
|
||||
<ul>
|
||||
<li><strong>内核模块</strong>：宿主机需开启 <code>binderfs</code>、<code>ashmem</code> 等内核模块，部分发行版可能需安装 <code>redroid-modules</code>。</li>
|
||||
<li><strong>GPU 加速</strong>：推荐使用 Intel/AMD 集成 GPU，避免闭源 NVIDIA 驱动下的不稳定性；也可在云端 GPU 实例上部署。</li>
|
||||
<li><strong>软件需求</strong>：安装 Docker / Docker Compose（或 Podman）、ADB（Android Debug Bridge）和 Scrcpy，用于容器管理与远程调试、画面传输。</li>
|
||||
<li><strong>硬件配置</strong>：8 GB 及以上内存、四核及以上 CPU、至少 20 GB 存储；若运行高负载游戏，推荐更高配置并开启 GPU 硬件加速。</li>
|
||||
</ul>
|
||||
<h2 id="bu-shu-yu-pei-zhi">部署与配置</h2>
|
||||
<ol>
|
||||
<li><strong>创建目录与编写 Compose 文件</strong><pre data-lang="bash" style="background-color:#151515;color:#e8e8d3;" class="language-bash "><code class="language-bash" data-lang="bash"><span style="color:#ffb964;">mkdir ~</span><span>/redroid && cd </span><span style="color:#ffb964;">~</span><span>/redroid
|
||||
</span><span style="color:#ffb964;">vim</span><span> docker-compose.yml
|
||||
</span></code></pre>
|
||||
</li>
|
||||
<li><strong>示例 <code>docker-compose.yml</code></strong><pre data-lang="yaml" style="background-color:#151515;color:#e8e8d3;" class="language-yaml "><code class="language-yaml" data-lang="yaml"><span style="color:#ffb964;">version</span><span>: </span><span style="color:#556633;">'</span><span style="color:#99ad6a;">3.8</span><span style="color:#556633;">'
|
||||
</span><span style="color:#ffb964;">services</span><span>:
|
||||
</span><span> </span><span style="color:#ffb964;">redroid</span><span>:
|
||||
</span><span> </span><span style="color:#ffb964;">image</span><span>: </span><span style="color:#99ad6a;">redroid/redroid:11.0.0_gapps
|
||||
</span><span> </span><span style="color:#ffb964;">stdin_open</span><span>: true
|
||||
</span><span> </span><span style="color:#ffb964;">tty</span><span>: true
|
||||
</span><span> </span><span style="color:#ffb964;">privileged</span><span>: true
|
||||
</span><span> </span><span style="color:#ffb964;">ports</span><span>:
|
||||
</span><span> - </span><span style="color:#556633;">"</span><span style="color:#99ad6a;">127.0.0.1:5555:5555</span><span style="color:#556633;">"
|
||||
</span><span> </span><span style="color:#ffb964;">volumes</span><span>:
|
||||
</span><span> - </span><span style="color:#99ad6a;">./redroid-11-data:/data
|
||||
</span><span> </span><span style="color:#ffb964;">command</span><span>:
|
||||
</span><span> - </span><span style="color:#99ad6a;">androidboot.redroid_width=720
|
||||
</span><span> - </span><span style="color:#99ad6a;">androidboot.redroid_height=1280
|
||||
</span><span> - </span><span style="color:#99ad6a;">androidboot.redroid_dpi=320
|
||||
</span><span> - </span><span style="color:#99ad6a;">androidboot.redroid_fps=60
|
||||
</span><span> - </span><span style="color:#99ad6a;">androidboot.redroid_gpu_mode=host
|
||||
</span><span> - </span><span style="color:#99ad6a;">ro.product.cpu.abilist0=x86_64,arm64-v8a,x86,armeabi-v7a,armeabi
|
||||
</span><span> - </span><span style="color:#99ad6a;">ro.enable.native.bridge.exec=1
|
||||
</span><span> - </span><span style="color:#99ad6a;">ro.dalvik.vm.native.bridge=libndk_translation.so
|
||||
</span></code></pre>
|
||||
</li>
|
||||
<li><strong>启动容器</strong><pre data-lang="bash" style="background-color:#151515;color:#e8e8d3;" class="language-bash "><code class="language-bash" data-lang="bash"><span style="color:#ffb964;">sudo</span><span> docker compose up</span><span style="color:#ffb964;"> -d
|
||||
</span></code></pre>
|
||||
</li>
|
||||
</ol>
|
||||
<h2 id="ri-chang-shi-yong">日常使用</h2>
|
||||
<ul>
|
||||
<li><strong>ADB 连接与屏幕镜像</strong><pre data-lang="bash" style="background-color:#151515;color:#e8e8d3;" class="language-bash "><code class="language-bash" data-lang="bash"><span style="color:#ffb964;">adb</span><span> connect localhost:5555
|
||||
</span><span style="color:#ffb964;">scrcpy -s</span><span> localhost:5555</span><span style="color:#ffb964;"> --audio-codec</span><span>=aac
|
||||
</span></code></pre>
|
||||
</li>
|
||||
<li><strong>安装 APK</strong>：
|
||||
<ul>
|
||||
<li>使用 <code>adb install your_app.apk</code></li>
|
||||
<li>或在 Scrcpy 界面中拖拽 APK 文件进行安装</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><strong>停止与重启</strong>：<pre data-lang="bash" style="background-color:#151515;color:#e8e8d3;" class="language-bash "><code class="language-bash" data-lang="bash"><span style="color:#ffb964;">sudo</span><span> docker compose down
|
||||
</span><span style="color:#ffb964;">sudo</span><span> docker compose up</span><span style="color:#ffb964;"> -d
|
||||
</span></code></pre>
|
||||
</li>
|
||||
<li><strong>数据持久化</strong>：所有数据保存在 <code>~/redroid/redroid-11-data</code>，可备份或运行多实例。</li>
|
||||
</ul>
|
||||
<h2 id="gao-ji-cao-zuo-yu-an-quan-jian-yi">高级操作与安全建议</h2>
|
||||
<ul>
|
||||
<li><strong>Google Play 验证</strong>：首次登录 Play Store 需获取设备 ID 并在 Google 控制台注册后重启容器。</li>
|
||||
<li><strong>3D 加速检测</strong>：通过 AIDA64 等应用验证 GPU 加速是否生效。</li>
|
||||
<li><strong>网络安全</strong>：只绑定本地回环地址监听 ADB 端口；如需外网访问，务必配置防火墙规则，避免安全风险。</li>
|
||||
</ul>
|
||||
<h2 id="ding-zhi-jing-xiang-yu-gapps">定制镜像与 GApps</h2>
|
||||
<ul>
|
||||
<li><strong>安装 GApps</strong>：下载 OpenGApps x86_64 Android 11 Pico 包，将其中 APK 拷贝到自建镜像的 <code>system</code> 目录，再在容器内推送并授权。</li>
|
||||
<li><strong>自定义 libndk</strong>：从 Android Studio 模拟器提取 Google 官方 ARM 翻译库（libndk），在 Dockerfile 中加入到基于 <code>redroid:13.0.0-latest</code> 的自定义镜像，提升兼容性与性能。</li>
|
||||
</ul>
|
||||
<hr />
|
||||
<p>🔗</p>
|
||||
<p><a href="https://ivonblog.com/posts/install-bliss-os-on-msi-modern-15-a10/">如何在Linux安裝Bliss OS</a></p>
|
||||
<hr />
|
||||
<p><strong>Done.</strong></p>
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
<div class="pagination">
|
||||
<div class="pagination__title">
|
||||
<span class="pagination__title-h">Thanks for reading! Read other posts?</span>
|
||||
<hr />
|
||||
</div>
|
||||
<div class="pagination__buttons">
|
||||
<span class="button previous">
|
||||
<a href="https://blog.dich.bid/learn-linux-for-pc-7/">
|
||||
<span class="button__icon">←</span>
|
||||
<span class="button__text">Linux之旅(七):系统与终端字体设置</span>
|
||||
</a>
|
||||
</span>
|
||||
|
||||
|
||||
<span class="button next">
|
||||
<a href="https://blog.dich.bid/awesome-pve-mcsm/">
|
||||
<span class="button__text">综合工程:PVE安装与MC服务器搭建</span>
|
||||
<span class="button__icon">→</span>
|
||||
</a>
|
||||
</span>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
</div>
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
<footer class="footer">
|
||||
<div class="footer__inner">
|
||||
<div class="copyright">
|
||||
<span>©
|
||||
2025
|
||||
Dichgrem</span>
|
||||
<span class="copyright-theme">
|
||||
<span class="copyright-theme-sep"> :: CC BY-SA 4.0 :: A friend comes from distant lands</span>
|
||||
</a>
|
||||
</span>
|
||||
</div>
|
||||
</div>
|
||||
</footer>
|
||||
|
||||
</div>
|
||||
</body>
|
||||
</html>
|
||||
|
||||
1
public/buttons.css
Normal file
1
public/buttons.css
Normal file
@ -0,0 +1 @@
|
||||
.button-container{display:table;margin-left:auto;margin-right:auto}button,.button,a.button{position:relative;display:flex;align-items:center;justify-content:center;padding:8px 18px;margin-bottom:5px;text-align:center;border-radius:8px;border:1px solid rgba(0,0,0,0);appearance:none;cursor:pointer;outline:none;}button.outline,.button.outline,a.button.outline{background:rgba(0,0,0,0);box-shadow:none;padding:8px 18px}button.outline :hover,.button.outline :hover,a.button.outline :hover{transform:none;box-shadow:none}button.primary,.button.primary,a.button.primary{box-shadow:0 4px 6px rgba(50,50,93,.11),0 1px 3px rgba(0,0,0,.08)}button.primary:hover,.button.primary:hover,a.button.primary:hover{box-shadow:0 2px 6px rgba(50,50,93,.21),0 1px 3px rgba(0,0,0,.08)}button.link,.button.link,a.button.link{background:none;font-size:1rem}button.small,.button.small,a.button.small{font-size:.8rem}button.wide,.button.wide,a.button.wide{min-width:200px;padding:14px 24px}a.read-more,a.read-more:hover,a.read-more:active{display:inline-flex;background:none;box-shadow:none;padding:0;margin:20px 0;max-width:100%}.code-toolbar{margin-bottom:20px}.code-toolbar .toolbar-item a{position:relative;display:inline-flex;align-items:center;justify-content:center;padding:3px 8px;margin-bottom:5px;text-align:center;font-size:13px;font-weight:500;border-radius:8px;border:1px solid rgba(0,0,0,0);appearance:none;cursor:pointer;outline:none}
|
||||
1
public/color/background_auto.css
Normal file
1
public/color/background_auto.css
Normal file
@ -0,0 +1 @@
|
||||
@media (prefers-color-scheme: light){:root{--background: white;--color: #101010}}@media (prefers-color-scheme: dark){:root{--background: #101010;--color: #A9B7C6}}
|
||||
1
public/color/background_blue.css
Normal file
1
public/color/background_blue.css
Normal file
@ -0,0 +1 @@
|
||||
:root{--background: #1D212C}
|
||||
1
public/color/background_dark.css
Normal file
1
public/color/background_dark.css
Normal file
@ -0,0 +1 @@
|
||||
:root{--background: #101010;--color: #A9B7C6}
|
||||
1
public/color/background_green.css
Normal file
1
public/color/background_green.css
Normal file
@ -0,0 +1 @@
|
||||
:root{--background: #1F222A}
|
||||
1
public/color/background_light.css
Normal file
1
public/color/background_light.css
Normal file
@ -0,0 +1 @@
|
||||
:root{--background: #f0f0f0}
|
||||
1
public/color/background_orange.css
Normal file
1
public/color/background_orange.css
Normal file
@ -0,0 +1 @@
|
||||
:root{--background: #222129}
|
||||
1
public/color/background_pink.css
Normal file
1
public/color/background_pink.css
Normal file
@ -0,0 +1 @@
|
||||
:root{--background: #21202C}
|
||||
1
public/color/background_red.css
Normal file
1
public/color/background_red.css
Normal file
@ -0,0 +1 @@
|
||||
:root{--background: #221F29}
|
||||
1
public/color/blue-auto.css
Normal file
1
public/color/blue-auto.css
Normal file
@ -0,0 +1 @@
|
||||
@media (prefers-color-scheme: dark){:root{--accent: rgb(35,176,255);--accent-alpha-70: rgba(35,176,255,.7);--accent-alpha-20: rgba(35,176,255,.2);--background: #101010;--color: #f0f0f0;--border-color: rgba(255,240,224,.125)}:root div.logo{color:#000}}@media (prefers-color-scheme: light){:root{--accent: rgb(32,128,192);--accent-alpha-70: rgba(32,128,192,.7);--accent-alpha-20: rgba(32,128,192,.2);--background: white;--color: #201030;--border-color: rgba(0,0,16,.125)}:root div.logo{color:#fff}}
|
||||
1
public/color/blue-light.css
Normal file
1
public/color/blue-light.css
Normal file
@ -0,0 +1 @@
|
||||
:root{--accent: rgb(32,128,192);--accent-alpha-70: rgba(32,128,192,.7);--accent-alpha-20: rgba(32,128,192,.2);--background: white;--color: #1D212C;--border-color: rgba(0, 0, 0, .1)}:root div.logo{color:#fff}
|
||||
1
public/color/blue.css
Normal file
1
public/color/blue.css
Normal file
@ -0,0 +1 @@
|
||||
:root{--accent: rgb(35,176,255);--accent-alpha-70: rgba(35,176,255,.7);--accent-alpha-20: rgba(35,176,255,.2);--background: #1D212C;--color: white;--border-color: rgba(255, 255, 255, .1)}
|
||||
1
public/color/green-auto.css
Normal file
1
public/color/green-auto.css
Normal file
@ -0,0 +1 @@
|
||||
@media (prefers-color-scheme: dark){:root{--accent: rgb(120,226,160);--accent-alpha-70: rgba(120,226,160,.7);--accent-alpha-20: rgba(120,226,160,.2);--background: #101010;--color: #f0f0f0;--border-color: rgba(255,240,224,.125)}:root div.logo{color:#000}}@media (prefers-color-scheme: light){:root{--accent: rgb(24, 192, 128);--accent-alpha-70: rgba(24, 192, 128,.7);--accent-alpha-20: rgba(24, 192, 128,.2);--background: white;--color: #201030;--border-color: rgba(0,0,16,.125)}:root div.logo{color:#fff}}
|
||||
1
public/color/green-light.css
Normal file
1
public/color/green-light.css
Normal file
@ -0,0 +1 @@
|
||||
:root{--accent: rgb(24, 192, 128);--accent-alpha-70: rgba(24, 192, 128,.7);--accent-alpha-20: rgba(24, 192, 128,.2);--background: white;--color: #1D212C;--border-color: rgba(0, 0, 0, .1)}:root div.logo{color:#fff}
|
||||
1
public/color/green.css
Normal file
1
public/color/green.css
Normal file
@ -0,0 +1 @@
|
||||
:root{--accent: rgb(120,226,160);--accent-alpha-70: rgba(120,226,160,.7);--accent-alpha-20: rgba(120,226,160,.2);--background: #1F222A;--color: white;--border-color: rgba(255, 255, 255, .1)}
|
||||
1
public/color/orange-auto.css
Normal file
1
public/color/orange-auto.css
Normal file
@ -0,0 +1 @@
|
||||
@media (prefers-color-scheme: dark){:root{--accent: rgb(255,168,106);--accent-alpha-70: rgba(255,168,106,.7);--accent-alpha-20: rgba(255,168,106,.2);--background: #101010;--color: #f0f0f0;--border-color: rgba(255,240,224,.125)}:root div.logo{color:#000}}@media (prefers-color-scheme: light){:root{--accent: rgb(240,128,48);--accent-alpha-70: rgba(240,128,48,.7);--accent-alpha-20: rgba(240,128,48,.2);--background: white;--color: #201030;--border-color: rgba(0,0,16,.125)}:root div.logo{color:#fff}}
|
||||
1
public/color/orange-light.css
Normal file
1
public/color/orange-light.css
Normal file
@ -0,0 +1 @@
|
||||
:root{--accent: rgb(240,128,48);--accent-alpha-70: rgba(240,128,48,.7);--accent-alpha-20: rgba(240,128,48,.2);--background: white;--color: #1D212C;--border-color: rgba(0, 0, 0, .1)}:root div.logo{color:#fff}
|
||||
1
public/color/orange.css
Normal file
1
public/color/orange.css
Normal file
@ -0,0 +1 @@
|
||||
:root{--accent: rgb(255,168,106);--accent-alpha-70: rgba(255,168,106,.7);--accent-alpha-20: rgba(255,168,106,.2);--background: #222129;--color: white;--border-color: rgba(255, 255, 255, .1)}
|
||||
1
public/color/pink-auto.css
Normal file
1
public/color/pink-auto.css
Normal file
@ -0,0 +1 @@
|
||||
@media (prefers-color-scheme: dark){:root{--accent: rgb(224,64,192);--accent-alpha-70: rgba(224,64,192);--accent-alpha-20: rgba(224,64,192,.2);--background: #101010;--color: #f0f0f0;--border-color: rgba(255,240,224,.125)}:root div.logo{color:#000}}@media (prefers-color-scheme: light){:root{--accent: rgb(238,114,241);--accent-alpha-70: rgba(238,114,241,.7);--accent-alpha-20: rgba(238,114,241,.2);--background: white;--color: #201030;--border-color: rgba(0,0,16,.125)}:root div.logo{color:#fff}}
|
||||
1
public/color/pink-light.css
Normal file
1
public/color/pink-light.css
Normal file
@ -0,0 +1 @@
|
||||
:root{--accent: rgb(224,64,192);--accent-alpha-70: rgba(224,64,192);--accent-alpha-20: rgba(224,64,192,.2);--background: white;--color: #1D212C;--border-color: rgba(0, 0, 0, .1)}:root div.logo{color:#fff}
|
||||
1
public/color/pink.css
Normal file
1
public/color/pink.css
Normal file
@ -0,0 +1 @@
|
||||
:root{--accent: rgb(238,114,241);--accent-alpha-70: rgba(238,114,241,.7);--accent-alpha-20: rgba(238,114,241,.2);--background: #21202C;--color: white;--border-color: rgba(255, 255, 255, .1)}
|
||||
1
public/color/red-auto.css
Normal file
1
public/color/red-auto.css
Normal file
@ -0,0 +1 @@
|
||||
@media (prefers-color-scheme: dark){:root{--accent: rgb(255,98,102);--accent-alpha-70: rgba(255,98,102,.7);--accent-alpha-20: rgba(255,98,102,.2);--background: #101010;--color: #f0f0f0;--border-color: rgba(255,240,224,.125)}:root div.logo{color:#000}}@media (prefers-color-scheme: light){:root{--accent: rgb(240,48,64);--accent-alpha-70: rgba(240,48,64,.7);--accent-alpha-20: rgba(240,48,64,.2);--background: white;--color: #201030;--border-color: rgba(0,0,16,.125)}:root div.logo{color:#fff}}
|
||||
1
public/color/red-light.css
Normal file
1
public/color/red-light.css
Normal file
@ -0,0 +1 @@
|
||||
:root{--accent: rgb(240,48,64);--accent-alpha-70: rgba(240,48,64,.7);--accent-alpha-20: rgba(240,48,64,.2);--background: white;--color: #1D212C;--border-color: rgba(0, 0, 0, .1)}:root div.logo{color:#fff}
|
||||
1
public/color/red.css
Normal file
1
public/color/red.css
Normal file
@ -0,0 +1 @@
|
||||
:root{--accent: rgb(255,98,102);--accent-alpha-70: rgba(255,98,102,.7);--accent-alpha-20: rgba(255,98,102,.2);--background: #221F29;--color: white;--border-color: rgba(255, 255, 255, .1)}
|
||||
1
public/css/water.min.css
vendored
Normal file
1
public/css/water.min.css
vendored
Normal file
File diff suppressed because one or more lines are too long
BIN
public/dich.webp
Normal file
BIN
public/dich.webp
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 24 KiB |
4
public/font-hack-subset.css
Normal file
4
public/font-hack-subset.css
Normal file
@ -0,0 +1,4 @@
|
||||
/*!
|
||||
* Hack typeface https://github.com/source-foundry/Hack
|
||||
* License: https://github.com/source-foundry/Hack/blob/master/LICENSE.md
|
||||
*/@font-face{font-family:"Hack";src:url("fonts/hack-regular.woff2?sha=3114f1256") format("woff2"),url("fonts/hack-regular.woff?sha=3114f1256") format("woff");font-weight:400;font-style:normal}@font-face{font-family:"Hack";src:url("fonts/hack-bold-subset.woff2?sha=3114f1256") format("woff2"),url("fonts/hack-bold-subset.woff?sha=3114f1256") format("woff");font-weight:700;font-style:normal}@font-face{font-family:"Hack";src:url("fonts/hack-italic-subset.woff2?sha=3114f1256") format("woff2"),url("fonts/hack-italic-webfont.woff?sha=3114f1256") format("woff");font-weight:400;font-style:italic}@font-face{font-family:"Hack";src:url("fonts/hack-bolditalic-subset.woff2?sha=3114f1256") format("woff2"),url("fonts/hack-bolditalic-subset.woff?sha=3114f1256") format("woff");font-weight:700;font-style:italic}
|
||||
4
public/font-hack.css
Normal file
4
public/font-hack.css
Normal file
@ -0,0 +1,4 @@
|
||||
/*!
|
||||
* Hack typeface https://github.com/source-foundry/Hack
|
||||
* License: https://github.com/source-foundry/Hack/blob/master/LICENSE.md
|
||||
*/@font-face{font-family:"Hack";src:url("fonts/hack-regular.woff2?sha=3114f1256") format("woff2"),url("fonts/hack-regular.woff?sha=3114f1256") format("woff");font-weight:400;font-style:normal}@font-face{font-family:"Hack";src:url("fonts/hack-bold.woff2?sha=3114f1256") format("woff2"),url("fonts/hack-bold.woff?sha=3114f1256") format("woff");font-weight:700;font-style:normal}@font-face{font-family:"Hack";src:url("fonts/hack-italic.woff2?sha=3114f1256") format("woff2"),url("fonts/hack-italic.woff?sha=3114f1256") format("woff");font-weight:400;font-style:italic}@font-face{font-family:"Hack";src:url("fonts/hack-bolditalic.woff2?sha=3114f1256") format("woff2"),url("fonts/hack-bolditalic.woff?sha=3114f1256") format("woff");font-weight:700;font-style:italic}
|
||||
BIN
public/fonts/hack-bold-subset.woff
Normal file
BIN
public/fonts/hack-bold-subset.woff
Normal file
Binary file not shown.
BIN
public/fonts/hack-bold-subset.woff2
Normal file
BIN
public/fonts/hack-bold-subset.woff2
Normal file
Binary file not shown.
BIN
public/fonts/hack-bold.woff
Normal file
BIN
public/fonts/hack-bold.woff
Normal file
Binary file not shown.
BIN
public/fonts/hack-bold.woff2
Normal file
BIN
public/fonts/hack-bold.woff2
Normal file
Binary file not shown.
BIN
public/fonts/hack-bolditalic-subset.woff
Normal file
BIN
public/fonts/hack-bolditalic-subset.woff
Normal file
Binary file not shown.
BIN
public/fonts/hack-bolditalic-subset.woff2
Normal file
BIN
public/fonts/hack-bolditalic-subset.woff2
Normal file
Binary file not shown.
BIN
public/fonts/hack-bolditalic.woff
Normal file
BIN
public/fonts/hack-bolditalic.woff
Normal file
Binary file not shown.
BIN
public/fonts/hack-bolditalic.woff2
Normal file
BIN
public/fonts/hack-bolditalic.woff2
Normal file
Binary file not shown.
BIN
public/fonts/hack-italic-subset.woff
Normal file
BIN
public/fonts/hack-italic-subset.woff
Normal file
Binary file not shown.
BIN
public/fonts/hack-italic-subset.woff2
Normal file
BIN
public/fonts/hack-italic-subset.woff2
Normal file
Binary file not shown.
BIN
public/fonts/hack-italic.woff
Normal file
BIN
public/fonts/hack-italic.woff
Normal file
Binary file not shown.
BIN
public/fonts/hack-italic.woff2
Normal file
BIN
public/fonts/hack-italic.woff2
Normal file
Binary file not shown.
BIN
public/fonts/hack-regular-subset.woff
Normal file
BIN
public/fonts/hack-regular-subset.woff
Normal file
Binary file not shown.
BIN
public/fonts/hack-regular-subset.woff2
Normal file
BIN
public/fonts/hack-regular-subset.woff2
Normal file
Binary file not shown.
BIN
public/fonts/hack-regular.woff
Normal file
BIN
public/fonts/hack-regular.woff
Normal file
Binary file not shown.
BIN
public/fonts/hack-regular.woff2
Normal file
BIN
public/fonts/hack-regular.woff2
Normal file
Binary file not shown.
1
public/footer.css
Normal file
1
public/footer.css
Normal file
@ -0,0 +1 @@
|
||||
.footer{padding:40px 0;flex-grow:0;opacity:.5}.footer__inner{display:flex;align-items:center;justify-content:space-between;margin:0;width:760px;max-width:100%}@media (max-width: 899px){.footer__inner{flex-direction:column}}.footer a{color:inherit}.footer .copyright{display:flex;flex-direction:row;align-items:center;font-size:1rem;color:var(--light-color-secondary)}.footer .copyright--user{margin:auto;text-align:center}.footer .copyright>*:first-child:not(:only-child){margin-right:10px}@media (max-width: 899px){.footer .copyright>*:first-child:not(:only-child){border:none;padding:0;margin:0}}@media (max-width: 899px){.footer .copyright{flex-direction:column;margin-top:10px}}@media (max-width: 899px){.footer .copyright-theme-sep{display:none}}@media (max-width: 899px){.footer .copyright-theme{font-size:.75rem}}
|
||||
1
public/header.css
Normal file
1
public/header.css
Normal file
@ -0,0 +1 @@
|
||||
.header{display:flex;flex-direction:column;position:relative}.header__inner{display:flex;align-items:center;justify-content:space-between}.header__logo{display:flex;flex:1}.header__logo:after{content:"";background:repeating-linear-gradient(90deg, var(--accent), var(--accent) 2px, rgba(0,0,0,0) 0, rgba(0,0,0,0) 16px);display:block;width:100%;right:10px}.header__logo a{flex:0 0 auto;max-width:100%}.header .menu{margin:20px 0}.header .menu__inner{display:flex;flex-wrap:wrap;list-style:none;margin:0;padding:0}.header .menu__inner li.active{color:var(--accent-alpha-70)}.header .menu__inner li:not(:last-of-type){margin-right:20px;margin-bottom:10px;flex:0 0 auto}.header .menu__sub-inner{position:relative;list-style:none;padding:0;margin:0}.header .menu__sub-inner:not(:only-child){margin-left:20px}.header .menu__sub-inner-more{position:absolute;background:var(--background);box-shadow:var(--shadow);color:#fff;border:2px solid;margin:0;padding:10px;list-style:none;z-index:99;top:35px;left:0}.header .menu__sub-inner-more-trigger{color:var(--accent);user-select:none;cursor:pointer}.header .menu__sub-inner-more li{margin:0;padding:5px;white-space:nowrap}
|
||||
BIN
public/images/desktop.png
Normal file
BIN
public/images/desktop.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 2.1 MiB |
BIN
public/images/file.png
Normal file
BIN
public/images/file.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 206 KiB |
301
public/index.html
Normal file
301
public/index.html
Normal file
@ -0,0 +1,301 @@
|
||||
<!DOCTYPE html>
|
||||
<html lang="en">
|
||||
|
||||
<head>
|
||||
<title>Dich'blog</title>
|
||||
|
||||
<meta http-equiv="content-type" content="text/html; charset=utf-8">
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1">
|
||||
<meta name="robots" content="noodp"/>
|
||||
|
||||
<link rel="stylesheet" href="https://blog.dich.bid/style.css">
|
||||
<link rel="stylesheet" href="https://blog.dich.bid/color/blue.css">
|
||||
|
||||
<link rel="stylesheet" href="https://blog.dich.bid/color/background_dark.css">
|
||||
|
||||
<link rel="stylesheet" href="https://blog.dich.bid/font-hack-subset.css">
|
||||
|
||||
<meta name="description" content="用电子罗盘，转赛博核桃，勘电磁风水，寻网络龙脉">
|
||||
|
||||
<meta property="og:description" content="用电子罗盘，转赛博核桃，勘电磁风水，寻网络龙脉">
|
||||
<meta property="og:title" content="Dich'blog">
|
||||
<meta property="og:type" content="website">
|
||||
<meta property="og:url" content="https://blog.dich.bid/">
|
||||
|
||||
<meta name="twitter:card" content="summary_large_image">
|
||||
<meta name="twitter:description" content="用电子罗盘，转赛博核桃，勘电磁风水，寻网络龙脉">
|
||||
<meta name="twitter:title" content="Dich'blog">
|
||||
<meta property="twitter:domain" content="blog.dich.bid">
|
||||
<meta property="twitter:url" content="https://blog.dich.bid/">
|
||||
|
||||
<link rel="alternate" type="application/atom+xml" title="Dich'blog Atom Feed" href="https://blog.dich.bid/atom.xml" />
|
||||
|
||||
|
||||
<link rel="icon" type="image/png" href=/dich.webp />
|
||||
|
||||
<!-- ✅ Added center alignment styles -->
|
||||
<style>
|
||||
.footer {
|
||||
text-align: center;
|
||||
padding: 1rem 0;
|
||||
}
|
||||
|
||||
.footer__inner {
|
||||
display: flex;
|
||||
justify-content: center;
|
||||
flex-direction: column;
|
||||
align-items: center;
|
||||
}
|
||||
|
||||
.copyright {
|
||||
text-align: center;
|
||||
}
|
||||
</style>
|
||||
</head>
|
||||
|
||||
<body class="">
|
||||
<div class="container">
|
||||
|
||||
<header class="header">
|
||||
<div class="header__inner">
|
||||
<div class="header__logo">
|
||||
|
||||
<a href="https://blog.dich.bid" style="text-decoration: none;">
|
||||
<div class="logo">
|
||||
|
||||
Dich'blog
|
||||
|
||||
</div>
|
||||
</a>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
|
||||
|
||||
<nav class="menu">
|
||||
<ul class="menu__inner">
|
||||
<li class="active"><a href="https://blog.dich.bid">blog</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/archive">archive</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/tags">tags</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/weekly">weekly</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/search">search</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/about">about me</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/links">links</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/atom.xml">rss</a></li>
|
||||
|
||||
<li><a href="https://github.com/Dichgrem" target="_blank" rel="noopener noreferrer">github</a></li>
|
||||
</ul>
|
||||
</nav>
|
||||
|
||||
|
||||
|
||||
</header>
|
||||
|
||||
|
||||
<div class="content">
|
||||
|
||||
<div class="posts">
|
||||
<div class="post on-list">
|
||||
|
||||
<h1 class="post-title"><a href="https://blog.dich.bid/about-gpg/">乱七八糟:GPG使用小记</a></h1>
|
||||
<div class="post-meta-inline">
|
||||
|
||||
<span class="post-date">
|
||||
2025-06-17
|
||||
</span>
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
<span class="post-tags-inline">
|
||||
:: tags:
|
||||
<a class="post-tag" href="https://blog.dich.bid/tags/luan-qi-ba-zao/">#乱七八糟</a></span>
|
||||
|
||||
|
||||
|
||||
|
||||
<div class="post-content">
|
||||
<p>前言 PGP/GPG 的核心功能——公钥加密、数字签名、信任管理广泛用于各个行业，本文简单说明了其使用方法。</p>
|
||||
</div>
|
||||
<div>
|
||||
<!-- ︎ -- force text style - some devices render this as emoji -->
|
||||
<a class="read-more button" href="https://blog.dich.bid/about-gpg/">
|
||||
<span class="button__text">Read more</span>
|
||||
<span class="button__icon">↩︎</span>
|
||||
</a>
|
||||
</div>
|
||||
|
||||
|
||||
</div>
|
||||
|
||||
<div class="post on-list">
|
||||
|
||||
<h1 class="post-title"><a href="https://blog.dich.bid/about-baci/">乱七八糟:Baci实验笔记</a></h1>
|
||||
<div class="post-meta-inline">
|
||||
|
||||
<span class="post-date">
|
||||
2025-04-23
|
||||
</span>
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
<span class="post-tags-inline">
|
||||
:: tags:
|
||||
<a class="post-tag" href="https://blog.dich.bid/tags/luan-qi-ba-zao/">#乱七八糟</a></span>
|
||||
|
||||
|
||||
|
||||
|
||||
<div class="post-content">
|
||||
<p>前言 BACI是一个简化的并发程序模拟器，这里对其语法与运行环境进行说明。</p>
|
||||
</div>
|
||||
<div>
|
||||
<!-- ︎ -- force text style - some devices render this as emoji -->
|
||||
<a class="read-more button" href="https://blog.dich.bid/about-baci/">
|
||||
<span class="button__text">Read more</span>
|
||||
<span class="button__icon">↩︎</span>
|
||||
</a>
|
||||
</div>
|
||||
|
||||
|
||||
</div>
|
||||
|
||||
<div class="post on-list">
|
||||
|
||||
<h1 class="post-title"><a href="https://blog.dich.bid/about-lazyvim/">乱七八糟:lazyvim快速上手</a></h1>
|
||||
<div class="post-meta-inline">
|
||||
|
||||
<span class="post-date">
|
||||
2025-04-20
|
||||
</span>
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
<span class="post-tags-inline">
|
||||
:: tags:
|
||||
<a class="post-tag" href="https://blog.dich.bid/tags/luan-qi-ba-zao/">#乱七八糟</a></span>
|
||||
|
||||
|
||||
|
||||
|
||||
<div class="post-content">
|
||||
<p>前言 LazyVim 是一个基于 Neovim 的现代化配置框架，易于定制和扩展，这里对其介绍并说明使用方法。</p>
|
||||
</div>
|
||||
<div>
|
||||
<!-- ︎ -- force text style - some devices render this as emoji -->
|
||||
<a class="read-more button" href="https://blog.dich.bid/about-lazyvim/">
|
||||
<span class="button__text">Read more</span>
|
||||
<span class="button__icon">↩︎</span>
|
||||
</a>
|
||||
</div>
|
||||
|
||||
|
||||
</div>
|
||||
|
||||
<div class="post on-list">
|
||||
|
||||
<h1 class="post-title"><a href="https://blog.dich.bid/about-aria2/">乱七八糟:Aria2各平台使用指南</a></h1>
|
||||
<div class="post-meta-inline">
|
||||
|
||||
<span class="post-date">
|
||||
2025-04-15
|
||||
</span>
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
<span class="post-tags-inline">
|
||||
:: tags:
|
||||
<a class="post-tag" href="https://blog.dich.bid/tags/luan-qi-ba-zao/">#乱七八糟</a></span>
|
||||
|
||||
|
||||
|
||||
|
||||
<div class="post-content">
|
||||
<p>前言 Aria2是一款开源、跨平台的命令行界面下载管理器，常常被各种下载器软件使用。</p>
|
||||
</div>
|
||||
<div>
|
||||
<!-- ︎ -- force text style - some devices render this as emoji -->
|
||||
<a class="read-more button" href="https://blog.dich.bid/about-aria2/">
|
||||
<span class="button__text">Read more</span>
|
||||
<span class="button__icon">↩︎</span>
|
||||
</a>
|
||||
</div>
|
||||
|
||||
|
||||
</div>
|
||||
|
||||
<div class="post on-list">
|
||||
|
||||
<h1 class="post-title"><a href="https://blog.dich.bid/about-markdown/">乱七八糟:Markdown使用快速教程</a></h1>
|
||||
<div class="post-meta-inline">
|
||||
|
||||
<span class="post-date">
|
||||
2025-04-08
|
||||
</span>
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
<span class="post-tags-inline">
|
||||
:: tags:
|
||||
<a class="post-tag" href="https://blog.dich.bid/tags/luan-qi-ba-zao/">#乱七八糟</a></span>
|
||||
|
||||
|
||||
|
||||
|
||||
<div class="post-content">
|
||||
<p>前言 本文为 Markdown 教程，内容涵盖 Markdown 的历史、作用、基本语法和显示效果，可以在github将本文的源码拷贝供大家参考和学习。</p>
|
||||
</div>
|
||||
<div>
|
||||
<!-- ︎ -- force text style - some devices render this as emoji -->
|
||||
<a class="read-more button" href="https://blog.dich.bid/about-markdown/">
|
||||
<span class="button__text">Read more</span>
|
||||
<span class="button__icon">↩︎</span>
|
||||
</a>
|
||||
</div>
|
||||
|
||||
|
||||
</div>
|
||||
<div class="pagination">
|
||||
<div class="pagination__buttons">
|
||||
<span class="button next">
|
||||
<a href="https://blog.dich.bid/page/2/">
|
||||
<span class="button__text">Older posts</span>
|
||||
<span class="button__icon">→</span>
|
||||
</a>
|
||||
</span>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
<footer class="footer">
|
||||
<div class="footer__inner">
|
||||
<div class="copyright">
|
||||
<span>©
|
||||
2025
|
||||
Dichgrem</span>
|
||||
<span class="copyright-theme">
|
||||
<span class="copyright-theme-sep"> :: CC BY-SA 4.0 :: A friend comes from distant lands</span>
|
||||
</a>
|
||||
</span>
|
||||
</div>
|
||||
</div>
|
||||
</footer>
|
||||
|
||||
</div>
|
||||
</body>
|
||||
</html>
|
||||
|
||||
264
public/learn-linux-for-pc-1/index.html
Normal file
264
public/learn-linux-for-pc-1/index.html
Normal file
@ -0,0 +1,264 @@
|
||||
<!DOCTYPE html>
|
||||
<html lang="en">
|
||||
|
||||
<head>
|
||||
<title>Dich'blog</title>
|
||||
|
||||
<meta http-equiv="content-type" content="text/html; charset=utf-8">
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1">
|
||||
<meta name="robots" content="noodp"/>
|
||||
|
||||
<link rel="stylesheet" href="https://blog.dich.bid/style.css">
|
||||
<link rel="stylesheet" href="https://blog.dich.bid/color/blue.css">
|
||||
|
||||
<link rel="stylesheet" href="https://blog.dich.bid/color/background_dark.css">
|
||||
|
||||
<link rel="stylesheet" href="https://blog.dich.bid/font-hack-subset.css">
|
||||
|
||||
<meta name="description" content="">
|
||||
|
||||
<meta property="og:description" content="">
|
||||
<meta property="og:title" content="Dich'blog">
|
||||
<meta property="og:type" content="article">
|
||||
<meta property="og:url" content="https://blog.dich.bid/learn-linux-for-pc-1/">
|
||||
|
||||
<meta name="twitter:card" content="summary_large_image">
|
||||
<meta name="twitter:description" content="">
|
||||
<meta name="twitter:title" content="Dich'blog">
|
||||
<meta property="twitter:domain" content="blog.dich.bid">
|
||||
<meta property="twitter:url" content="https://blog.dich.bid/learn-linux-for-pc-1/">
|
||||
|
||||
<link rel="alternate" type="application/atom+xml" title="Dich'blog Atom Feed" href="https://blog.dich.bid/atom.xml" />
|
||||
|
||||
|
||||
<link rel="icon" type="image/png" href=/dich.webp />
|
||||
|
||||
<!-- ✅ Added center alignment styles -->
|
||||
<style>
|
||||
.footer {
|
||||
text-align: center;
|
||||
padding: 1rem 0;
|
||||
}
|
||||
|
||||
.footer__inner {
|
||||
display: flex;
|
||||
justify-content: center;
|
||||
flex-direction: column;
|
||||
align-items: center;
|
||||
}
|
||||
|
||||
.copyright {
|
||||
text-align: center;
|
||||
}
|
||||
</style>
|
||||
</head>
|
||||
|
||||
<body class="">
|
||||
<div class="container">
|
||||
|
||||
<header class="header">
|
||||
<div class="header__inner">
|
||||
<div class="header__logo">
|
||||
|
||||
<a href="https://blog.dich.bid" style="text-decoration: none;">
|
||||
<div class="logo">
|
||||
|
||||
Dich'blog
|
||||
|
||||
</div>
|
||||
</a>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
|
||||
|
||||
<nav class="menu">
|
||||
<ul class="menu__inner">
|
||||
<li class="active"><a href="https://blog.dich.bid">blog</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/archive">archive</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/tags">tags</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/weekly">weekly</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/search">search</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/about">about me</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/links">links</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/atom.xml">rss</a></li>
|
||||
|
||||
<li><a href="https://github.com/Dichgrem" target="_blank" rel="noopener noreferrer">github</a></li>
|
||||
</ul>
|
||||
</nav>
|
||||
|
||||
|
||||
|
||||
</header>
|
||||
|
||||
|
||||
<div class="content">
|
||||
|
||||
<div class="post">
|
||||
|
||||
<h1 class="post-title"><a href="https://blog.dich.bid/learn-linux-for-pc-1/">Linux之旅(一):构成与发行版</a></h1>
|
||||
<div class="post-meta-inline">
|
||||
|
||||
<span class="post-date">
|
||||
2023-07-20
|
||||
</span>
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
<span class="post-tags-inline">
|
||||
:: tags:
|
||||
<a class="post-tag" href="https://blog.dich.bid/tags/linux/">#Linux</a></span>
|
||||
|
||||
|
||||
<div class="post-content">
|
||||
<p>前言 Linux 作为一款强大、灵活且免费的操作系统，吸引了越来越多的用户。然而，对于初学者来说，Linux 可能显得有些陌生，甚至有些令人望而生畏。本文旨在为那些刚踏入 Linux 世界的新手提供一份指南，帮助他们更好地了解、使用这个令人着迷的操作系统。我们将探讨Linux的基本概念，解释为何选择Linux，深入剖析其主要构成要素以及不同的发行版之间的差异。</p>
|
||||
<span id="continue-reading"></span><h2 id="yi-shen-me-shi-linux">一.什么是Linux？</h2>
|
||||
<p>Linux 是一种开源的类 UNIX 操作系统内核。它由芬兰的 Linus Torvalds 于1991年开始开发，是一个自由、免费的操作系统。Linux 内核是操作系统的核心，负责管理硬件资源，并提供各种系统服务。与 Windows 和 macOS 等操作系统不同，Linux 的源代码对所有人开放，任何人都可以查看、修改和重新分发。这使得 Linux 具有极高的自由度和可定制性，用户可以根据自己的需求和偏好来定制操作系统。Linux 广泛应用于各种设备，包括个人计算机、服务器、手机、嵌入式系统等，是一个功能强大且灵活多样的操作系统。</p>
|
||||
<h2 id="er-wei-shen-me-yao-yong-linux">二.为什么要用Linux？</h2>
|
||||
<ol>
|
||||
<li>
|
||||
<p><strong>开源免费</strong>：Linux 是完全开源的，用户可以免费使用和修改源代码。</p>
|
||||
</li>
|
||||
<li>
|
||||
<p><strong>稳定性和安全性</strong>：Linux 系统以其稳定性和安全性而闻名，适合长时间运行的服务。</p>
|
||||
</li>
|
||||
<li>
|
||||
<p><strong>灵活性和可定制性</strong>：用户可以根据需要定制 Linux 系统。</p>
|
||||
</li>
|
||||
<li>
|
||||
<p><strong>广泛的软件支持</strong>：有大量的开源软件可供选择，满足不同需求。</p>
|
||||
</li>
|
||||
</ol>
|
||||
<blockquote>
|
||||
<p>Liunx可以用来玩游戏吗？
|
||||
实际上著名的 Steam Deck 的系统就是基于Arch linux 的。对于个人使用而言，现在有不少原生支持linux 的游戏；也可以使用Wine来运行Windows下的游戏。</p>
|
||||
</blockquote>
|
||||
<blockquote>
|
||||
<p>Linux上软件会不会太少？
|
||||
参见 <a href="https://blog.dich.ink/open-source-software">常用跨平台开源软件</a>一文，在社区的努力下如今软件生态已经非常丰富，你也可以使用如Flatpak等商店安装软件，或者直接使用Wine。如果有不得不在Windows下使用的软件，可以装双系统。</p>
|
||||
</blockquote>
|
||||
<h2 id="san-linuxde-zhu-yao-gou-cheng">三.Linux的主要构成</h2>
|
||||
<p>Linux操作系统主要由以下几个部分组成：</p>
|
||||
<ol>
|
||||
<li>
|
||||
<p><strong>内核</strong>：操作系统的核心，负责管理系统资源。如Zen内核，LTS内核等。</p>
|
||||
</li>
|
||||
<li>
|
||||
<p><strong>Shell</strong>：命令行界面，用户通过它与系统交互，如Bash,Zsh等。</p>
|
||||
</li>
|
||||
<li>
|
||||
<p><strong>图形用户界面（GUI）</strong>：提供图形化操作界面，如GNOME、KDE、XFCE等。</p>
|
||||
</li>
|
||||
<li>
|
||||
<p><strong>文件系统</strong>：如ext4、Btrfs等，用于组织和管理磁盘上的文件。</p>
|
||||
</li>
|
||||
<li>
|
||||
<p><strong>系统库</strong>：为应用程序提供运行时支持。</p>
|
||||
</li>
|
||||
<li>
|
||||
<p><strong>应用程序</strong>：用户可以直接使用的软件，如文本编辑器、网页浏览器等。其中也有著名的GNU工具，如Vim,GCC等。</p>
|
||||
</li>
|
||||
</ol>
|
||||
<h2 id="si-xuan-ze-linuxfa-xing-ban">四.选择Linux发行版</h2>
|
||||
<p>从上文可以发现，选择Linux发行版实际上是在选择 <strong>内核/包管理器/图形界面</strong> 等组件的排列组合。其中最主要的因素是包管理器。</p>
|
||||
<p>Linux有许多不同的发行版，但大致可以分为几个系：</p>
|
||||
<p><strong>Debian系：</strong>
|
||||
Debian：Debian以稳定性，安全性和轻量级著称，适合用于服务器和桌面环境。我们常说的Ubuntu就是基于Debian的发行版，注重用户友好性和易用性。它提供了多种桌面环境选择，以及许多现成的软件包。</p>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>APT（Advanced Package Tool）是Debian系发行版的主要包管理器。它使用命令行工具如apt-get、aptitude等来管理软件包。
|
||||
</span></code></pre>
|
||||
<p><strong>Red Hat系：</strong></p>
|
||||
<ul>
|
||||
<li>Red Hat Enterprise Linux（RHEL）：RHEL是一款商业发行版，专注于企业级应用和支持。它提供了长期支持和专业技术支持服务，适用于企业级服务器和工作站。</li>
|
||||
<li>CentOS：CentOS是基于RHEL源代码编译而成的免费发行版，与RHEL兼容并提供类似的功能和性能。它也提供了长期支持版本和稳定性较高的特点。</li>
|
||||
<li>Fedora：Fedora是由Red Hat支持的社区驱动的发行版，注重提供最新的软件特性和技术。它适用于开发者和技术爱好者，提供了稳定的发布周期和丰富的软件包。</li>
|
||||
</ul>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>YUM（Yellowdog Updater, Modified）是Red Hat系发行版的主要包管理器。最近的版本也开始采用DNF（Dandified YUM）。
|
||||
</span></code></pre>
|
||||
<p><strong>Arch系：</strong>
|
||||
Arch Linux：Arch Linux是一个简洁、轻量级且灵活的发行版，注重简洁性和滚动更新。它采用“滚动发布”的方式，用户可以通过自定义安装来构建自己的系统，适合有一定Linux经验的用户。</p>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>Pacman（Package Manager）是Arch Linux的主要包管理器。它使用简洁的命令来管理软件包，如pacman -S安装软件包、pacman -Syu更新系统等。
|
||||
</span></code></pre>
|
||||
<p><strong>Gentoo系：</strong>
|
||||
Gentoo：Gentoo是一个源码驱动的发行版，用户可以通过源代码自定义编译软件包以满足自己的需求。它注重性能和灵活性，适合高级用户和技术爱好者。</p>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>Portage是Gentoo的包管理器，它是一个源代码驱动的包管理器，允许用户从源代码构建和安装软件包。
|
||||
</span></code></pre>
|
||||
<p>除了以上列举的包管理器外，还有其他一些较为特殊的包管理器，如Slackware系的pkgtool、SUSE系的zypper等。</p>
|
||||
<p>对于个人使用而言，我个人建议新手使用Ubuntu,有比较易用的界面和完善的资料参考；如果你是一个系统极客，可以使用Arch linux 或者 NixOS。</p>
|
||||
<h2 id="wu-ge-ren-ri-chang-shi-yong-xu-yao-zhu-yi-shen-me">五.个人日常使用需要注意什么？</h2>
|
||||
<ol>
|
||||
<li>
|
||||
<p><strong>学习命令行</strong>：命令行是Linux的强大工具，学习基本命令可以提高效率。</p>
|
||||
</li>
|
||||
<li>
|
||||
<p><strong>选择合适的发行版</strong>：根据个人需求和技术水平选择适合的发行版。</p>
|
||||
</li>
|
||||
<li>
|
||||
<p><strong>系统备份</strong>：定期备份重要数据，以防意外丢失。</p>
|
||||
</li>
|
||||
<li>
|
||||
<p><strong>软件管理</strong>：了解如何安装、更新和卸载软件。</p>
|
||||
</li>
|
||||
<li>
|
||||
<p><strong>安全设置</strong>：设置强密码，定期更新系统以修复安全漏洞。</p>
|
||||
</li>
|
||||
<li>
|
||||
<p><strong>社区参与</strong>：Linux社区非常活跃，遇到问题可以寻求社区帮助。</p>
|
||||
</li>
|
||||
<li>
|
||||
<p><strong>硬件兼容性</strong>：检查你的硬件是否与选择的Linux发行版兼容。</p>
|
||||
</li>
|
||||
<li>
|
||||
<p><strong>驱动程序</strong>：确保你的硬件设备有可用的驱动程序，以避免兼容性问题。</p>
|
||||
</li>
|
||||
</ol>
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
<div class="pagination">
|
||||
<div class="pagination__title">
|
||||
<span class="pagination__title-h">Thanks for reading! Read other posts?</span>
|
||||
<hr />
|
||||
</div>
|
||||
<div class="pagination__buttons">
|
||||
|
||||
<span class="button next">
|
||||
<a href="https://blog.dich.bid/learn-linux-for-pc-2/">
|
||||
<span class="button__text">Linux之旅(二):FHS与目录结构</span>
|
||||
<span class="button__icon">→</span>
|
||||
</a>
|
||||
</span>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
</div>
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
<footer class="footer">
|
||||
<div class="footer__inner">
|
||||
<div class="copyright">
|
||||
<span>©
|
||||
2025
|
||||
Dichgrem</span>
|
||||
<span class="copyright-theme">
|
||||
<span class="copyright-theme-sep"> :: CC BY-SA 4.0 :: A friend comes from distant lands</span>
|
||||
</a>
|
||||
</span>
|
||||
</div>
|
||||
</div>
|
||||
</footer>
|
||||
|
||||
</div>
|
||||
</body>
|
||||
</html>
|
||||
|
||||
282
public/learn-linux-for-pc-2/index.html
Normal file
282
public/learn-linux-for-pc-2/index.html
Normal file
@ -0,0 +1,282 @@
|
||||
<!DOCTYPE html>
|
||||
<html lang="en">
|
||||
|
||||
<head>
|
||||
<title>Dich'blog</title>
|
||||
|
||||
<meta http-equiv="content-type" content="text/html; charset=utf-8">
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1">
|
||||
<meta name="robots" content="noodp"/>
|
||||
|
||||
<link rel="stylesheet" href="https://blog.dich.bid/style.css">
|
||||
<link rel="stylesheet" href="https://blog.dich.bid/color/blue.css">
|
||||
|
||||
<link rel="stylesheet" href="https://blog.dich.bid/color/background_dark.css">
|
||||
|
||||
<link rel="stylesheet" href="https://blog.dich.bid/font-hack-subset.css">
|
||||
|
||||
<meta name="description" content="">
|
||||
|
||||
<meta property="og:description" content="">
|
||||
<meta property="og:title" content="Dich'blog">
|
||||
<meta property="og:type" content="article">
|
||||
<meta property="og:url" content="https://blog.dich.bid/learn-linux-for-pc-2/">
|
||||
|
||||
<meta name="twitter:card" content="summary_large_image">
|
||||
<meta name="twitter:description" content="">
|
||||
<meta name="twitter:title" content="Dich'blog">
|
||||
<meta property="twitter:domain" content="blog.dich.bid">
|
||||
<meta property="twitter:url" content="https://blog.dich.bid/learn-linux-for-pc-2/">
|
||||
|
||||
<link rel="alternate" type="application/atom+xml" title="Dich'blog Atom Feed" href="https://blog.dich.bid/atom.xml" />
|
||||
|
||||
|
||||
<link rel="icon" type="image/png" href=/dich.webp />
|
||||
|
||||
<!-- ✅ Added center alignment styles -->
|
||||
<style>
|
||||
.footer {
|
||||
text-align: center;
|
||||
padding: 1rem 0;
|
||||
}
|
||||
|
||||
.footer__inner {
|
||||
display: flex;
|
||||
justify-content: center;
|
||||
flex-direction: column;
|
||||
align-items: center;
|
||||
}
|
||||
|
||||
.copyright {
|
||||
text-align: center;
|
||||
}
|
||||
</style>
|
||||
</head>
|
||||
|
||||
<body class="">
|
||||
<div class="container">
|
||||
|
||||
<header class="header">
|
||||
<div class="header__inner">
|
||||
<div class="header__logo">
|
||||
|
||||
<a href="https://blog.dich.bid" style="text-decoration: none;">
|
||||
<div class="logo">
|
||||
|
||||
Dich'blog
|
||||
|
||||
</div>
|
||||
</a>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
|
||||
|
||||
<nav class="menu">
|
||||
<ul class="menu__inner">
|
||||
<li class="active"><a href="https://blog.dich.bid">blog</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/archive">archive</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/tags">tags</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/weekly">weekly</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/search">search</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/about">about me</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/links">links</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/atom.xml">rss</a></li>
|
||||
|
||||
<li><a href="https://github.com/Dichgrem" target="_blank" rel="noopener noreferrer">github</a></li>
|
||||
</ul>
|
||||
</nav>
|
||||
|
||||
|
||||
|
||||
</header>
|
||||
|
||||
|
||||
<div class="content">
|
||||
|
||||
<div class="post">
|
||||
|
||||
<h1 class="post-title"><a href="https://blog.dich.bid/learn-linux-for-pc-2/">Linux之旅(二):FHS与目录结构</a></h1>
|
||||
<div class="post-meta-inline">
|
||||
|
||||
<span class="post-date">
|
||||
2023-07-21
|
||||
</span>
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
<span class="post-tags-inline">
|
||||
:: tags:
|
||||
<a class="post-tag" href="https://blog.dich.bid/tags/linux/">#Linux</a></span>
|
||||
|
||||
|
||||
<div class="post-content">
|
||||
<p>前言 在Linux世界中，Filesystem Hierarchy Standard（FHS）是一座引导我们进入系统核心的桥梁，它定义了Linux系统中目录结构的规范与作用，为我们提供了一张清晰的地图，指引我们轻松管理和理解系统。本文将深入探讨FHS规范与Linux系统目录结构，解释各个目录的用途与功能，帮助我们更好地理解和利用Linux系统。</p>
|
||||
<span id="continue-reading"></span><h2 id="yi-ren-shi-fhs">一.认识FHS</h2>
|
||||
<p>FHS是Filesystem Hierarchy Standard（文件系统层次结构标准）的缩写。它是一个定义了Linux系统中目录结构和各个目录作用的规范。FHS规定了Linux系统中各个目录的用途和预期内容，以便确保不同Linux发行版之间的兼容性，并使得用户能够更轻松地理解和管理系统。</p>
|
||||
<p>FHS规范最初由Linux基金会（Linux Foundation）和自由软件基金会（Free Software Foundation）共同发布，并经过多次修订和更新。该规范不仅对Linux系统本身有用，也适用于其他类UNIX操作系统。</p>
|
||||
<p>FHS规范定义了一些基本的目录，如/bin、/boot、/dev等，并规定了每个目录的作用和预期内容。这样做有助于系统管理员和开发人员更好地组织和管理文件系统，并使得用户能够更轻松地找到所需的文件和数据。</p>
|
||||
<h2 id="er-chang-jian-mu-lu-jie-gou">二.常见目录结构</h2>
|
||||
<p>在刚刚由Windows切换至Linux时，往往会对目录感到不解，不知道安装的软件放在哪个目录之下？</p>
|
||||
<p>以下是对Linux系统目录结构的详细说明：</p>
|
||||
<ul>
|
||||
<li><strong>/（根目录）</strong>：
|
||||
根目录是整个文件系统的起点，包含了系统中所有其他目录和文件。在Linux系统中，根目录被表示为/。</li>
|
||||
<li><strong>/bin（二进制文件）</strong>：
|
||||
/bin目录存放着一些最基本的系统命令，如ls、cp、mv等，这些命令通常被所有用户使用。</li>
|
||||
<li><strong>/boot（引导文件）</strong>：
|
||||
/boot目录存放着启动Linux系统所需的引导文件，如内核映像（vmlinuz）、引导加载程序（boot loader）配置文件（如GRUB配置文件）等。</li>
|
||||
<li><strong>/dev（设备文件）</strong>：
|
||||
/dev目录包含了系统中所有设备的特殊文件，如硬盘、键盘、鼠标等。在Linux中，一切皆文件，设备被抽象为文件，通过/dev目录中的特殊文件来表示。</li>
|
||||
<li><strong>/etc（配置文件）</strong>：
|
||||
/etc目录包含了系统的配置文件，如网络配置、用户账户信息、服务配置等。这些配置文件通常以纯文本的形式存在，可以由系统管理员进行编辑和修改。</li>
|
||||
<li><strong>/home（用户主目录）</strong>：
|
||||
/home目录是系统中所有普通用户的主目录所在地，每个用户通常都有一个对应的子目录，用于存放用户的个人文件和数据。</li>
|
||||
<li><strong>/lib（库文件）</strong>：
|
||||
/lib目录存放着系统所需的共享库文件，这些库文件包含了一些程序运行所需的函数和数据，为程序提供了基本的支持。</li>
|
||||
<li><strong>/mnt（挂载点）</strong>：
|
||||
/mnt目录用于挂载临时文件系统，如光盘、移动硬盘等。系统管理员可以将其他设备或文件系统挂载到/mnt目录下，以便访问其中的文件和数据。</li>
|
||||
<li><strong>/opt（可选软件包）</strong>：
|
||||
/opt目录用于存放一些可选的软件包和应用程序，这些软件包通常不属于Linux发行版的默认安装范围，但可以被用户自行安装和管理。</li>
|
||||
<li><strong>/proc（进程信息）</strong>：
|
||||
/proc目录是一个虚拟的文件系统，包含了系统运行时的各种进程信息和系统状态信息。用户可以通过读取/proc目录中的特殊文件来获取系统信息。</li>
|
||||
<li><strong>/sbin（系统命令）</strong>：
|
||||
/sbin目录存放着一些系统管理和维护命令，这些命令通常只能由超级用户（root）执行，用于系统的管理和维护。</li>
|
||||
<li><strong>/srv（服务数据）</strong>：
|
||||
/srv目录用于存放一些服务相关的数据文件，如Web服务器的网站数据、FTP服务器的文件等。每个服务通常都会有一个对应的子目录。</li>
|
||||
<li><strong>/tmp（临时文件）</strong>：
|
||||
/tmp目录用于存放临时文件和临时数据，这些文件通常在系统重启时会被删除。任何用户都可以在/tmp目录下创建临时文件。</li>
|
||||
<li><strong>/usr（用户程序）</strong>：
|
||||
/usr目录包含了系统中大部分用户可用的程序和文件，如用户应用程序、共享库文件、文档等。它通常是系统的二级目录，类似于Windows系统中的Program Files目录。</li>
|
||||
<li><strong>/var（可变数据）</strong>：
|
||||
/var目录用于存放系统运行时产生的可变数据，如日志文件、邮件、缓存文件等。这些数据通常会随着系统的运行而不断变化。</li>
|
||||
</ul>
|
||||
<blockquote>
|
||||
<p>注意：NixOS不符合FHS标准！</p>
|
||||
</blockquote>
|
||||
<h2 id="san-fen-qu-da-xiao">三.分区大小</h2>
|
||||
<p>对各个分区进行容量分配时，需要根据系统的实际需求和用途来进行规划。一般而言在安装引导时可以选择让程序自动分区。</p>
|
||||
<ul>
|
||||
<li><strong>根目录（/）</strong>：根目录是整个文件系统的起点，通常会分配较大的空间，以确保系统和应用程序有足够的空间运行。建议分配至少20GB的空间给根目录。</li>
|
||||
<li><strong>/home目录</strong>：/home目录用于存放用户的个人文件和数据，因此需要根据用户数量和存储需求来进行容量分配。一般情况下，建议为每个用户分配至少10GB的空间。</li>
|
||||
<li><strong>/var目录</strong>：/var目录用于存放系统运行时产生的可变数据，如日志文件、邮件、缓存文件等。根据系统的运行情况和日志文件的大小来进行容量分配，一般建议分配10-20GB的空间。</li>
|
||||
<li><strong>/tmp目录</strong>：/tmp目录用于存放临时文件和临时数据，通常不需要分配太大的空间。建议分配至少1-2GB的空间给/tmp目录。</li>
|
||||
<li><strong>/boot目录</strong>：/boot目录存放着启动Linux系统所需的引导文件，通常只需要分配几百MB的空间即可。</li>
|
||||
<li><strong>Swap分区</strong>：Swap分区是一种虚拟内存，用于暂时存放不常用的内存数据。当系统内存不足时，Linux会将一部分内存数据移动到Swap分区中，以避免内存耗尽导致系统崩溃。Swap分区的大小通常与系统内存大小有关，一般建议为系统内存的1.5-2倍。例如，如果系统内存为4GB，则建议设置Swap分区大小为6-8GB。</li>
|
||||
</ul>
|
||||
<blockquote>
|
||||
<p>这里特别讲讲Swap分区</p>
|
||||
</blockquote>
|
||||
<p>Swap分区可以通过以下几种方式实现：</p>
|
||||
<ul>
|
||||
<li>交换分区（Swap Partition）：创建一个独立的交换分区，通常是一个专门的分区，用于存放Swap数据。</li>
|
||||
<li>交换文件（Swap File）：创建一个专门的文件用于存放Swap数据，而不是创建独立的分区。这种方式更加灵活，可以根据需要动态调整Swap的大小。</li>
|
||||
<li>Swap大小：Swap的大小应该根据系统的内存大小和使用情况来确定，一般建议为系统内存的1.5-2倍。</li>
|
||||
<li>Swap分区/文件的位置：Swap分区/文件应该位于较快的存储介质上，以确保交换操作的效率。
|
||||
Swap的优先级：如果同时存在多个Swap分区/文件，可以通过设置优先级来指定系统使用的Swap空间。</li>
|
||||
</ul>
|
||||
<h2 id="si-jiang-home-mu-lu-xia-de-wen-jian-jia-gai-wei-ying-wen">四.将 <code>home</code> 目录下的文件夹改为英文</h2>
|
||||
<p>可以使用 <code>xdg-user-dirs-update</code> 工具来更新用户目录为英文版本。你可以按照以下步骤进行：</p>
|
||||
<ol>
|
||||
<li>
|
||||
<p><strong>编辑用户目录配置文件</strong>：
|
||||
打开或创建 <code>~/.config/user-dirs.dirs</code> 文件，用文本编辑器编辑它：</p>
|
||||
<pre data-lang="bash" style="background-color:#151515;color:#e8e8d3;" class="language-bash "><code class="language-bash" data-lang="bash"><span style="color:#ffb964;">nano ~</span><span>/.config/user-dirs.dirs
|
||||
</span></code></pre>
|
||||
</li>
|
||||
<li>
|
||||
<p><strong>将目录名称更改为英文</strong>：
|
||||
在该文件中，你可以看到类似以下的条目：</p>
|
||||
<pre data-lang="bash" style="background-color:#151515;color:#e8e8d3;" class="language-bash "><code class="language-bash" data-lang="bash"><span style="color:#ffb964;">XDG_DESKTOP_DIR</span><span>=</span><span style="color:#556633;">"</span><span style="color:#99ad6a;">$</span><span style="color:#ffb964;">HOME</span><span style="color:#99ad6a;">/桌面</span><span style="color:#556633;">"
|
||||
</span><span style="color:#ffb964;">XDG_DOWNLOAD_DIR</span><span>=</span><span style="color:#556633;">"</span><span style="color:#99ad6a;">$</span><span style="color:#ffb964;">HOME</span><span style="color:#99ad6a;">/下载</span><span style="color:#556633;">"
|
||||
</span><span style="color:#ffb964;">XDG_DOCUMENTS_DIR</span><span>=</span><span style="color:#556633;">"</span><span style="color:#99ad6a;">$</span><span style="color:#ffb964;">HOME</span><span style="color:#99ad6a;">/文档</span><span style="color:#556633;">"
|
||||
</span><span style="color:#ffb964;">XDG_MUSIC_DIR</span><span>=</span><span style="color:#556633;">"</span><span style="color:#99ad6a;">$</span><span style="color:#ffb964;">HOME</span><span style="color:#99ad6a;">/音乐</span><span style="color:#556633;">"
|
||||
</span><span style="color:#ffb964;">XDG_PICTURES_DIR</span><span>=</span><span style="color:#556633;">"</span><span style="color:#99ad6a;">$</span><span style="color:#ffb964;">HOME</span><span style="color:#99ad6a;">/图片</span><span style="color:#556633;">"
|
||||
</span><span style="color:#ffb964;">XDG_VIDEOS_DIR</span><span>=</span><span style="color:#556633;">"</span><span style="color:#99ad6a;">$</span><span style="color:#ffb964;">HOME</span><span style="color:#99ad6a;">/视频</span><span style="color:#556633;">"
|
||||
</span></code></pre>
|
||||
<p>将这些路径改为英文，例如：</p>
|
||||
<pre data-lang="bash" style="background-color:#151515;color:#e8e8d3;" class="language-bash "><code class="language-bash" data-lang="bash"><span style="color:#ffb964;">XDG_DESKTOP_DIR</span><span>=</span><span style="color:#556633;">"</span><span style="color:#99ad6a;">$</span><span style="color:#ffb964;">HOME</span><span style="color:#99ad6a;">/Desktop</span><span style="color:#556633;">"
|
||||
</span><span style="color:#ffb964;">XDG_DOWNLOAD_DIR</span><span>=</span><span style="color:#556633;">"</span><span style="color:#99ad6a;">$</span><span style="color:#ffb964;">HOME</span><span style="color:#99ad6a;">/Downloads</span><span style="color:#556633;">"
|
||||
</span><span style="color:#ffb964;">XDG_DOCUMENTS_DIR</span><span>=</span><span style="color:#556633;">"</span><span style="color:#99ad6a;">$</span><span style="color:#ffb964;">HOME</span><span style="color:#99ad6a;">/Documents</span><span style="color:#556633;">"
|
||||
</span><span style="color:#ffb964;">XDG_MUSIC_DIR</span><span>=</span><span style="color:#556633;">"</span><span style="color:#99ad6a;">$</span><span style="color:#ffb964;">HOME</span><span style="color:#99ad6a;">/Music</span><span style="color:#556633;">"
|
||||
</span><span style="color:#ffb964;">XDG_PICTURES_DIR</span><span>=</span><span style="color:#556633;">"</span><span style="color:#99ad6a;">$</span><span style="color:#ffb964;">HOME</span><span style="color:#99ad6a;">/Pictures</span><span style="color:#556633;">"
|
||||
</span><span style="color:#ffb964;">XDG_VIDEOS_DIR</span><span>=</span><span style="color:#556633;">"</span><span style="color:#99ad6a;">$</span><span style="color:#ffb964;">HOME</span><span style="color:#99ad6a;">/Videos</span><span style="color:#556633;">"
|
||||
</span></code></pre>
|
||||
</li>
|
||||
<li>
|
||||
<p><strong>重命名现有的文件夹</strong>：
|
||||
手动将 <code>home</code> 目录下的文件夹重命名为英文版本：</p>
|
||||
<pre data-lang="bash" style="background-color:#151515;color:#e8e8d3;" class="language-bash "><code class="language-bash" data-lang="bash"><span style="color:#ffb964;">mv ~</span><span>/桌面 </span><span style="color:#ffb964;">~</span><span>/Desktop
|
||||
</span><span style="color:#ffb964;">mv ~</span><span>/下载 </span><span style="color:#ffb964;">~</span><span>/Downloads
|
||||
</span><span style="color:#ffb964;">mv ~</span><span>/文档 </span><span style="color:#ffb964;">~</span><span>/Documents
|
||||
</span><span style="color:#ffb964;">mv ~</span><span>/音乐 </span><span style="color:#ffb964;">~</span><span>/Music
|
||||
</span><span style="color:#ffb964;">mv ~</span><span>/图片 </span><span style="color:#ffb964;">~</span><span>/Pictures
|
||||
</span><span style="color:#ffb964;">mv ~</span><span>/视频 </span><span style="color:#ffb964;">~</span><span>/Videos
|
||||
</span></code></pre>
|
||||
</li>
|
||||
<li>
|
||||
<p><strong>应用更改</strong>：
|
||||
完成以上操作后，运行以下命令应用新配置：</p>
|
||||
<pre data-lang="bash" style="background-color:#151515;color:#e8e8d3;" class="language-bash "><code class="language-bash" data-lang="bash"><span style="color:#ffb964;">xdg-user-dirs-update
|
||||
</span></code></pre>
|
||||
</li>
|
||||
</ol>
|
||||
<p>这样，<code>home</code> 目录下的文件夹就会改为英文，并且系统也会正确识别这些新的目录路径。</p>
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
<div class="pagination">
|
||||
<div class="pagination__title">
|
||||
<span class="pagination__title-h">Thanks for reading! Read other posts?</span>
|
||||
<hr />
|
||||
</div>
|
||||
<div class="pagination__buttons">
|
||||
<span class="button previous">
|
||||
<a href="https://blog.dich.bid/learn-linux-for-pc-1/">
|
||||
<span class="button__icon">←</span>
|
||||
<span class="button__text">Linux之旅(一):构成与发行版</span>
|
||||
</a>
|
||||
</span>
|
||||
|
||||
|
||||
<span class="button next">
|
||||
<a href="https://blog.dich.bid/learn-linux-for-pc-3/">
|
||||
<span class="button__text">Linux之旅(三):内核/shell/包管理/文件系统/桌面环境</span>
|
||||
<span class="button__icon">→</span>
|
||||
</a>
|
||||
</span>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
</div>
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
<footer class="footer">
|
||||
<div class="footer__inner">
|
||||
<div class="copyright">
|
||||
<span>©
|
||||
2025
|
||||
Dichgrem</span>
|
||||
<span class="copyright-theme">
|
||||
<span class="copyright-theme-sep"> :: CC BY-SA 4.0 :: A friend comes from distant lands</span>
|
||||
</a>
|
||||
</span>
|
||||
</div>
|
||||
</div>
|
||||
</footer>
|
||||
|
||||
</div>
|
||||
</body>
|
||||
</html>
|
||||
|
||||
358
public/learn-linux-for-pc-3/index.html
Normal file
358
public/learn-linux-for-pc-3/index.html
Normal file
@ -0,0 +1,358 @@
|
||||
<!DOCTYPE html>
|
||||
<html lang="en">
|
||||
|
||||
<head>
|
||||
<title>Dich'blog</title>
|
||||
|
||||
<meta http-equiv="content-type" content="text/html; charset=utf-8">
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1">
|
||||
<meta name="robots" content="noodp"/>
|
||||
|
||||
<link rel="stylesheet" href="https://blog.dich.bid/style.css">
|
||||
<link rel="stylesheet" href="https://blog.dich.bid/color/blue.css">
|
||||
|
||||
<link rel="stylesheet" href="https://blog.dich.bid/color/background_dark.css">
|
||||
|
||||
<link rel="stylesheet" href="https://blog.dich.bid/font-hack-subset.css">
|
||||
|
||||
<meta name="description" content="">
|
||||
|
||||
<meta property="og:description" content="">
|
||||
<meta property="og:title" content="Dich'blog">
|
||||
<meta property="og:type" content="article">
|
||||
<meta property="og:url" content="https://blog.dich.bid/learn-linux-for-pc-3/">
|
||||
|
||||
<meta name="twitter:card" content="summary_large_image">
|
||||
<meta name="twitter:description" content="">
|
||||
<meta name="twitter:title" content="Dich'blog">
|
||||
<meta property="twitter:domain" content="blog.dich.bid">
|
||||
<meta property="twitter:url" content="https://blog.dich.bid/learn-linux-for-pc-3/">
|
||||
|
||||
<link rel="alternate" type="application/atom+xml" title="Dich'blog Atom Feed" href="https://blog.dich.bid/atom.xml" />
|
||||
|
||||
|
||||
<link rel="icon" type="image/png" href=/dich.webp />
|
||||
|
||||
<!-- ✅ Added center alignment styles -->
|
||||
<style>
|
||||
.footer {
|
||||
text-align: center;
|
||||
padding: 1rem 0;
|
||||
}
|
||||
|
||||
.footer__inner {
|
||||
display: flex;
|
||||
justify-content: center;
|
||||
flex-direction: column;
|
||||
align-items: center;
|
||||
}
|
||||
|
||||
.copyright {
|
||||
text-align: center;
|
||||
}
|
||||
</style>
|
||||
</head>
|
||||
|
||||
<body class="">
|
||||
<div class="container">
|
||||
|
||||
<header class="header">
|
||||
<div class="header__inner">
|
||||
<div class="header__logo">
|
||||
|
||||
<a href="https://blog.dich.bid" style="text-decoration: none;">
|
||||
<div class="logo">
|
||||
|
||||
Dich'blog
|
||||
|
||||
</div>
|
||||
</a>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
|
||||
|
||||
<nav class="menu">
|
||||
<ul class="menu__inner">
|
||||
<li class="active"><a href="https://blog.dich.bid">blog</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/archive">archive</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/tags">tags</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/weekly">weekly</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/search">search</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/about">about me</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/links">links</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/atom.xml">rss</a></li>
|
||||
|
||||
<li><a href="https://github.com/Dichgrem" target="_blank" rel="noopener noreferrer">github</a></li>
|
||||
</ul>
|
||||
</nav>
|
||||
|
||||
|
||||
|
||||
</header>
|
||||
|
||||
|
||||
<div class="content">
|
||||
|
||||
<div class="post">
|
||||
|
||||
<h1 class="post-title"><a href="https://blog.dich.bid/learn-linux-for-pc-3/">Linux之旅(三):内核/shell/包管理/文件系统/桌面环境</a></h1>
|
||||
<div class="post-meta-inline">
|
||||
|
||||
<span class="post-date">
|
||||
2023-07-22
|
||||
</span>
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
<span class="post-tags-inline">
|
||||
:: tags:
|
||||
<a class="post-tag" href="https://blog.dich.bid/tags/linux/">#Linux</a></span>
|
||||
|
||||
|
||||
<div class="post-content">
|
||||
<p>前言 在Linux世界中，内核/shell/包管理/文件系统构成了Linux系统的核心，它们相互配合，共同构建了一个强大而稳定的操作环境。本文将深入探讨这些关键组成部分，解释它们的作用和原理，帮助读者更好地理解Linux系统的运作机制。</p>
|
||||
<span id="continue-reading"></span><h2 id="yi-linuxnei-he"><strong>一.Linux内核</strong></h2>
|
||||
<p>有许多不同的版本，每个版本都包含了一系列的功能改进、bug修复和性能优化。在Linux发行版中，通常会使用某个特定版本的Linux内核，或者在需要时进行升级。以下是一些常见的Linux内核及其主要特点：</p>
|
||||
<p><strong>Zen内核</strong>：</p>
|
||||
<ul>
|
||||
<li>Zen内核是Linux内核的一个变体，旨在提供更好的性能和响应性。它通常包含了一些特定的调度程序和调优参数，以提高系统的负载均衡和响应速度。Zen内核也可能包含一些来自其他内核变体的功能和补丁，以进一步优化性能。</li>
|
||||
</ul>
|
||||
<p><strong>LTS内核</strong>：</p>
|
||||
<ul>
|
||||
<li>LTS（Long-Term Support）内核是一种长期支持的内核版本，它会获得更长时间的更新和维护。LTS内核通常会选择一些相对稳定和经过充分测试的功能，并对其进行长期支持，以确保系统的稳定性和安全性。</li>
|
||||
</ul>
|
||||
<p><strong>Real-Time内核</strong>：</p>
|
||||
<ul>
|
||||
<li>Real-Time内核是一种专门针对实时应用场景进行优化的内核变体。它通常包含了一些实时调度算法和机制，以确保系统能够及时响应各种事件，并满足实时性要求。Real-Time内核适用于一些对实时性要求较高的应用，如工业控制、机器人控制等领域。</li>
|
||||
</ul>
|
||||
<p><strong>Hardened内核</strong>：</p>
|
||||
<ul>
|
||||
<li>Hardened内核是一种针对安全性进行优化的内核变体。它通常包含了一些安全增强功能和补丁，以提高系统的安全性和抵御攻击的能力。Hardened内核适用于一些对安全性要求较高的应用，如服务器、云计算等场景。</li>
|
||||
</ul>
|
||||
<p><strong>XanMod内核</strong>：</p>
|
||||
<ul>
|
||||
<li>XanMod内核是一个基于Linux内核的自定义内核，旨在提供更好的响应性和性能。它包含了一些针对桌面和工作站系统优化的功能和补丁，如MuQSS调度器、BFQ I/O调度器等，以提高系统的响应速度和性能稳定性。XanMod内核还支持一些实时性应用，如音视频处理等，适用于对系统响应速度要求较高的用户。</li>
|
||||
</ul>
|
||||
<p><strong>CachyOS内核</strong>：</p>
|
||||
<ul>
|
||||
<li>CachyOS内核是一个专门针对缓存优化的Linux内核变体。它包含了一些针对缓存系统优化的功能和调整，以提高系统的缓存性能和数据访问速度。CachyOS内核通常适用于需要高性能缓存的应用场景，如数据库服务器、Web服务器等。</li>
|
||||
</ul>
|
||||
<p>这些内核变体针对不同的需求和使用场景进行了优化，可以根据具体的应用需求来选择合适的内核版本。例如，如果您需要更好的性能和响应性，可以选择Zen内核；如果您需要长期支持和稳定性，可以选择LTS内核；如果您需要实时性能，可以选择Real-Time内核；如果您需要更高的安全性，可以选择Hardened内核。</p>
|
||||
<h2 id="er-linux-shell"><strong>二.Linux Shell</strong></h2>
|
||||
<p>在Linux系统中，有许多不同的Shell（命令行解释器），每种Shell都有自己的特点和用途。以下是一些常见的Linux Shell及其主要特点：</p>
|
||||
<p><strong>Bash（Bourne Again Shell）</strong>：</p>
|
||||
<ul>
|
||||
<li>Bash是Linux系统中最常用的Shell之一，也是默认的命令行解释器。它是Bourne Shell的增强版，提供了丰富的功能和扩展性，包括命令历史、命令补全、作业控制等。Bash具有良好的兼容性和易用性，适用于日常的系统管理和脚本编程。</li>
|
||||
</ul>
|
||||
<p><strong>Zsh（Z Shell）</strong>：</p>
|
||||
<ul>
|
||||
<li>Zsh是一种功能强大的Shell，提供了丰富的功能和扩展性，如更强大的命令补全、自动纠正拼写错误、主题和插件系统等。Zsh具有良好的可定制性和用户体验，适用于高级用户和程序员。</li>
|
||||
</ul>
|
||||
<p><strong>Fish（Friendly Interactive Shell）</strong>：</p>
|
||||
<ul>
|
||||
<li>Fish是一种用户友好的交互式Shell，提供了直观的命令提示和自动补全功能，以及丰富的语法高亮和命令提示信息。Fish具有良好的用户体验和易用性，适用于初学者和普通用户。</li>
|
||||
</ul>
|
||||
<p><strong>Dash（Debian Almquist Shell）</strong>：</p>
|
||||
<ul>
|
||||
<li>Dash是一种轻量级的Shell，专门设计用于系统启动过程和脚本执行。Dash具有较高的执行速度和较低的内存占用，适用于系统启动脚本和简单的脚本编程。</li>
|
||||
</ul>
|
||||
<p>Bash是最常用的Shell之一，具有良好的兼容性和功能性；Zsh提供了更多的高级特性和定制选项，适用于高级用户和程序员；Fish具有友好的交互式体验和直观的用户界面，适用于初学者和普通用户；Dash则是一个轻量级的Shell，专门用于系统启动过程和简单的脚本编程。用户可以根据自己的需求和偏好选择合适的Shell。</p>
|
||||
<h2 id="san-linuxbao-guan-li-qi"><strong>三.Linux包管理器</strong></h2>
|
||||
<p>在Linux系统中，有几种常见的包管理器，它们各自管理着不同的发行版，具有不同的特点和用途。以下是一些常见的Linux包管理器及其主要特点：</p>
|
||||
<p><strong>APT（Advanced Package Tool）</strong>：</p>
|
||||
<ul>
|
||||
<li>APT是Debian系（如Debian、Ubuntu）中最常用的包管理器之一。它使用基于命令行的工具，如<code>apt-get</code>、<code>apt-cache</code>等来安装、升级和删除软件包。APT还支持依赖关系的自动解决，使得软件包的安装和管理变得更加方便。</li>
|
||||
</ul>
|
||||
<p><strong>YUM（Yellowdog Updater, Modified）</strong>：</p>
|
||||
<ul>
|
||||
<li>YUM是Red Hat系（如CentOS、Fedora）中常用的包管理器之一。它使用基于命令行的工具，如<code>yum</code>来管理软件包。YUM具有良好的依赖关系解决能力和事务处理功能，使得系统升级和软件包管理变得更加简单和可靠。</li>
|
||||
</ul>
|
||||
<p><strong>DNF（Dandified YUM）</strong>：</p>
|
||||
<ul>
|
||||
<li>DNF是YUM的下一代版本，逐渐取代了YUM在Fedora和RHEL系列中的地位。DNF具有更快的包查询和事务处理能力，以及更友好的用户界面。它是未来主流的包管理器之一。</li>
|
||||
</ul>
|
||||
<p><strong>Pacman（Package Manager）</strong>：</p>
|
||||
<ul>
|
||||
<li>Pacman是Arch Linux中常用的包管理器，也被一些其他发行版如Manjaro采用。Pacman使用简洁的命令，如<code>pacman -S</code>安装软件包、<code>pacman -Syu</code>更新系统等来管理软件包。Pacman具有简单、直观的界面和快速的操作速度，适用于对系统有一定了解的用户。</li>
|
||||
</ul>
|
||||
<p><strong>zypper</strong>：</p>
|
||||
<ul>
|
||||
<li>zypper是openSUSE中常用的包管理器，它使用基于命令行的工具，如<code>zypper install</code>、<code>zypper update</code>等来管理软件包。zypper具有良好的依赖关系解决能力和事务处理功能，使得系统升级和软件包管理变得更加简单和可靠。</li>
|
||||
</ul>
|
||||
<p><strong>dpkg</strong>：</p>
|
||||
<ul>
|
||||
<li>dpkg是Debian系（如Debian、Ubuntu）中的低级别软件包管理工具，用于直接管理软件包的安装、升级和删除。它提供了一系列的命令，如<code>dpkg -i</code>安装软件包、<code>dpkg -r</code>删除软件包等。</li>
|
||||
</ul>
|
||||
<p><strong>RPM（RPM Package Manager）</strong>：</p>
|
||||
<ul>
|
||||
<li>RPM是Red Hat系（如CentOS、Fedora）中的低级别软件包管理工具，用于直接管理软件包的安装、升级和删除。它提供了一系列的命令，如<code>rpm -i</code>安装软件包、<code>rpm -e</code>删除软件包等。</li>
|
||||
</ul>
|
||||
<p><strong>Portage</strong>：</p>
|
||||
<ul>
|
||||
<li>Portage是Gentoo Linux中的包管理器，它使用源代码进行软件包的安装和管理。Portage具有高度定制化和灵活性，允许用户根据需要自定义软件包的编译参数和依赖关系。</li>
|
||||
</ul>
|
||||
<p><strong>Snap</strong>：</p>
|
||||
<ul>
|
||||
<li>Snap是一种跨发行版的软件包格式和包管理器，允许用户在不同的Linux发行版上安装和管理软件包。Snap具有自包含性和隔离性，使得软件包的安装和升级变得更加简单和安全。</li>
|
||||
</ul>
|
||||
<p><strong>Flatpak</strong>：</p>
|
||||
<ul>
|
||||
<li>Flatpak是另一种跨发行版的软件包格式和包管理器，类似于Snap，允许用户在不同的Linux发行版上安装和管理软件包。Flatpak提供了一种统一的应用分发和运行环境，使得软件包的安装和升级更加简单和可靠。</li>
|
||||
</ul>
|
||||
<h2 id="si-linuxwen-jian-xi-tong"><strong>四.Linux文件系统</strong></h2>
|
||||
<p>Linux系统支持多种文件系统，每种文件系统都有自己的特点和优势，适用于不同的应用场景和需求。以下是一些常见的Linux文件系统及其主要特点：</p>
|
||||
<p><strong>ext4</strong>：</p>
|
||||
<ul>
|
||||
<li>ext4是Linux系统中最常用的文件系统之一，它是ext文件系统的后续版本，提供了更好的性能和扩展性。ext4支持更大的文件和分区大小，更快的文件系统检查和恢复速度，以及更高的性能和稳定性。</li>
|
||||
</ul>
|
||||
<p><strong>Btrfs</strong>：</p>
|
||||
<ul>
|
||||
<li>Btrfs是一种先进的文件系统，具有许多先进的功能和特性，如快照、数据校验、数据压缩等。Btrfs支持在线扩展和收缩分区大小，以及动态添加和删除磁盘，适用于需要高级特性和灵活性的应用场景。此外，Btrfs对快照功能支持较好。</li>
|
||||
</ul>
|
||||
<blockquote>
|
||||
<p>快照功能是一种文件系统的特性，它允许用户在特定时间点对文件系统的状态进行快照或备份，并且可以在需要时一键恢复到该时间点的状态。
|
||||
快照允许用户轻松地创建文件系统的历史版本，并在需要时回滚到特定的版本；快照允许用户在文件系统中进行实验和测试，并在测试失败或不需要时轻松地回滚到初始状态，以避免对系统造成影响。在升级或安装过程中出现问题时快速恢复到原始状态</p>
|
||||
</blockquote>
|
||||
<p><strong>XFS</strong>：</p>
|
||||
<ul>
|
||||
<li>XFS是一种高性能的日志文件系统，适用于大型文件和高吞吐量的应用场景。XFS支持大容量的文件和分区，具有较低的碎片化和较高的并发性能，适用于大规模存储和数据分析等应用。</li>
|
||||
</ul>
|
||||
<p><strong>ZFS</strong>：</p>
|
||||
<ul>
|
||||
<li>ZFS是一种先进的文件系统，具有强大的数据管理和保护功能，如快照、数据校验、数据压缩等。ZFS支持软件RAID和存储池（pool），以及动态添加和删除磁盘，适用于数据中心和大规模存储等应用场景。</li>
|
||||
</ul>
|
||||
<p><strong>F2FS</strong>：</p>
|
||||
<ul>
|
||||
<li>F2FS是一种针对闪存存储设备进行优化的文件系统，具有高性能和高可靠性。F2FS支持闪存特性如块擦除计数（block erase count）和块生命周期管理（block lifetime management），适用于固态硬盘（SSD）和闪存卡等闪存设备。</li>
|
||||
</ul>
|
||||
<h2 id="wu-linuxzhuo-mian-huan-jing"><strong>五.Linux桌面环境</strong></h2>
|
||||
<p>Linux系统有多种不同的桌面环境，每种环境都有其独特的特点、风格和用户体验。以下是一些常见的Linux桌面环境及其主要特点：</p>
|
||||
<p><strong>GNOME</strong>：</p>
|
||||
<ul>
|
||||
<li>GNOME是一个功能强大、现代化的桌面环境，具有直观的用户界面和丰富的功能。它采用了扁平化的设计风格和简洁的用户界面，提供了丰富的应用程序和插件，适用于普通用户和开发人员。</li>
|
||||
</ul>
|
||||
<p><strong>KDE Plasma</strong>：</p>
|
||||
<ul>
|
||||
<li>KDE Plasma是一个灵活、可定制的桌面环境，提供了丰富的特性和选项，如桌面特效、窗口管理器、小部件等。它采用了现代化的设计风格和强大的桌面管理功能，适用于高级用户和技术爱好者。</li>
|
||||
</ul>
|
||||
<p><strong>XFCE</strong>：</p>
|
||||
<ul>
|
||||
<li>XFCE是一个轻量级、快速的桌面环境，具有简洁的用户界面和低资源消耗。它采用了传统的桌面布局和简约的设计风格，提供了基本的桌面管理功能和应用程序，适用于老旧计算机和资源有限的环境。</li>
|
||||
</ul>
|
||||
<p><strong>LXQt</strong>：</p>
|
||||
<ul>
|
||||
<li>LXQt是一个轻量级、快速的桌面环境，是LXDE和Razor-qt的合并项目。它采用了现代化的设计风格和简洁的用户界面，提供了丰富的特性和可定制选项，适用于资源有限的环境和嵌入式系统。</li>
|
||||
</ul>
|
||||
<p><strong>Cinnamon</strong>：</p>
|
||||
<ul>
|
||||
<li>Cinnamon是一个基于GNOME的桌面环境，具有类似于传统Windows桌面的用户界面和功能。它采用了传统的桌面布局和直观的用户体验，提供了丰富的特性和可定制选项，适用于对传统桌面风格有需求的用户。</li>
|
||||
</ul>
|
||||
<p>GNOME和KDE Plasma提供了丰富的特性和高度定制化选项，适用于高级用户和开发人员；XFCE和LXQt则提供了轻量级和快速的用户体验，适用于资源有限的环境；Cinnamon则提供了类似于传统Windows桌面的用户界面和功能，适用于对传统桌面风格有需求的用户。可以根据自己的需求和偏好选择合适的桌面环境。</p>
|
||||
<blockquote>
|
||||
<p>当然，也可以使用轻量级的窗口管理器。
|
||||
窗口管理器是Linux系统中控制窗口布局、管理窗口行为的关键组件。它们决定了窗口的外观和行为方式，以及如何管理和排列窗口。以下是一些常见的窗口管理器及其主要特点：</p>
|
||||
</blockquote>
|
||||
<p><strong>X Window Manager (XWM)</strong>：</p>
|
||||
<ul>
|
||||
<li>X Window Manager是最基本的窗口管理器，用于管理X Window系统中的窗口。它提供了最基本的窗口布局和管理功能，如窗口移动、调整大小、最小化等。XWM本身并不提供任何外观效果，但可以与其他工具配合使用来实现更丰富的窗口管理和外观特性。</li>
|
||||
</ul>
|
||||
<p><strong>Openbox</strong>：</p>
|
||||
<ul>
|
||||
<li>Openbox是一个轻量级的窗口管理器，具有简洁的用户界面和低资源消耗。它提供了丰富的自定义选项和扩展功能，如虚拟桌面、窗口装饰、键盘快捷键等。Openbox适用于资源有限的环境和对简洁风格有需求的用户。</li>
|
||||
</ul>
|
||||
<p><strong>i3</strong>：</p>
|
||||
<ul>
|
||||
<li>i3是一个动态平铺窗口管理器，采用了平铺式布局，将窗口按照一定规则自动排列在屏幕上。它提供了快速的窗口切换和管理功能，支持键盘操作和自动布局调整，适用于需要高效多任务处理的用户。</li>
|
||||
</ul>
|
||||
<p><strong>Awesome</strong>：</p>
|
||||
<ul>
|
||||
<li>Awesome是一个高度可定制的动态平铺窗口管理器，具有丰富的特性和扩展功能。它采用Lua脚本语言进行配置和定制，支持强大的自定义选项和扩展功能，适用于高级用户和技术爱好者。</li>
|
||||
</ul>
|
||||
<p><strong>KWin</strong>：</p>
|
||||
<ul>
|
||||
<li>KWin是KDE桌面环境中的默认窗口管理器，具有丰富的特性和功能。它提供了多种窗口布局和管理选项，支持虚拟桌面、窗口效果、窗口组织等功能，适用于需要丰富特性和高度定制化的用户。</li>
|
||||
</ul>
|
||||
<p>这些窗口管理器之间的主要异同在于窗口布局、外观效果、自定义选项和功能特性等方面。Openbox和i3提供了简洁的用户界面和低资源消耗，适用于资源有限的环境；Awesome和KWin则提供了丰富的特性和扩展功能，适用于高级用户和技术爱好者。用户可以根据自己的需求和偏好选择合适的窗口管理器。</p>
|
||||
<blockquote>
|
||||
<p>Wayland和X11
|
||||
Wayland和X11都是用于Linux系统的图形显示协议，它们负责管理图形用户界面（GUI）的显示和交互。下面是它们的简要介绍以及异同点：</p>
|
||||
</blockquote>
|
||||
<ul>
|
||||
<li>
|
||||
<p><strong>X11（X Window System）</strong>：
|
||||
X11是一个由MIT开发的图形显示协议，长期以来一直是Linux系统中最常用的图形显示系统。它采用客户端-服务器模型，图形应用程序（客户端）通过X服务器与显示设备（服务器）进行通信。X11提供了丰富的图形特性和功能，如窗口管理、窗口装饰、多任务处理等。</p>
|
||||
</li>
|
||||
<li>
|
||||
<p><strong>Wayland</strong>：
|
||||
Wayland是一个由Red Hat主导开发的新一代图形显示协议，旨在取代X11成为Linux系统的标准图形显示系统。Wayland采用了现代化的设计理念和架构，取消了X11中复杂的客户端-服务器模型，将图形显示功能直接集成到操作系统中。Wayland具有更低的延迟和更高的性能，支持更好的硬件加速和多触摸设备，以及更简洁的代码结构。</p>
|
||||
</li>
|
||||
</ul>
|
||||
<p><strong>异同点</strong>：</p>
|
||||
<ul>
|
||||
<li><strong>架构差异</strong>：X11采用了客户端-服务器模型，图形应用程序通过X服务器与显示设备进行通信；而Wayland取消了这种模型，将图形显示功能直接集成到操作系统中，减少了中间层的复杂性。</li>
|
||||
<li><strong>性能差异</strong>：Wayland具有更低的延迟和更高的性能，支持更好的硬件加速和多触摸设备，使得图形显示更加流畅和响应。</li>
|
||||
<li><strong>功能差异</strong>：X11提供了丰富的图形特性和功能，如窗口管理、窗口装饰、多任务处理等；Wayland在功能上相对较少，但提供了更简洁的代码结构和更好的性能。</li>
|
||||
<li><strong>兼容性差异</strong>：X11在Linux系统中被广泛使用，拥有大量的应用程序和工具的支持；而Wayland在兼容性方面仍在发展中，尚未完全取代X11成为Linux系统的标准图形显示系统。</li>
|
||||
</ul>
|
||||
<p>总的来说，Wayland是未来Linux系统中的趋势，具有更好的性能和更简洁的架构，但在兼容性和功能丰富度上仍有待改进。X11则是当前仍然广泛使用的图形显示系统，拥有丰富的生态和大量的应用程序支持。</p>
|
||||
<h2 id="liu-hou-ji"><strong>六.后记</strong></h2>
|
||||
<p>个人使用推荐Zen+Zsh+Pacman+Btrfs+Hyprland,并使用 paru xxx 来搜索软件包，使用paru -S xxx 安装软件。</p>
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
<div class="pagination">
|
||||
<div class="pagination__title">
|
||||
<span class="pagination__title-h">Thanks for reading! Read other posts?</span>
|
||||
<hr />
|
||||
</div>
|
||||
<div class="pagination__buttons">
|
||||
<span class="button previous">
|
||||
<a href="https://blog.dich.bid/learn-linux-for-pc-2/">
|
||||
<span class="button__icon">←</span>
|
||||
<span class="button__text">Linux之旅(二):FHS与目录结构</span>
|
||||
</a>
|
||||
</span>
|
||||
|
||||
|
||||
<span class="button next">
|
||||
<a href="https://blog.dich.bid/learn-linux-for-pc-4/">
|
||||
<span class="button__text">Linux之旅(四):Terminal，Console and Shell</span>
|
||||
<span class="button__icon">→</span>
|
||||
</a>
|
||||
</span>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
</div>
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
<footer class="footer">
|
||||
<div class="footer__inner">
|
||||
<div class="copyright">
|
||||
<span>©
|
||||
2025
|
||||
Dichgrem</span>
|
||||
<span class="copyright-theme">
|
||||
<span class="copyright-theme-sep"> :: CC BY-SA 4.0 :: A friend comes from distant lands</span>
|
||||
</a>
|
||||
</span>
|
||||
</div>
|
||||
</div>
|
||||
</footer>
|
||||
|
||||
</div>
|
||||
</body>
|
||||
</html>
|
||||
|
||||
191
public/learn-linux-for-pc-4/index.html
Normal file
191
public/learn-linux-for-pc-4/index.html
Normal file
@ -0,0 +1,191 @@
|
||||
<!DOCTYPE html>
|
||||
<html lang="en">
|
||||
|
||||
<head>
|
||||
<title>Dich'blog</title>
|
||||
|
||||
<meta http-equiv="content-type" content="text/html; charset=utf-8">
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1">
|
||||
<meta name="robots" content="noodp"/>
|
||||
|
||||
<link rel="stylesheet" href="https://blog.dich.bid/style.css">
|
||||
<link rel="stylesheet" href="https://blog.dich.bid/color/blue.css">
|
||||
|
||||
<link rel="stylesheet" href="https://blog.dich.bid/color/background_dark.css">
|
||||
|
||||
<link rel="stylesheet" href="https://blog.dich.bid/font-hack-subset.css">
|
||||
|
||||
<meta name="description" content="">
|
||||
|
||||
<meta property="og:description" content="">
|
||||
<meta property="og:title" content="Dich'blog">
|
||||
<meta property="og:type" content="article">
|
||||
<meta property="og:url" content="https://blog.dich.bid/learn-linux-for-pc-4/">
|
||||
|
||||
<meta name="twitter:card" content="summary_large_image">
|
||||
<meta name="twitter:description" content="">
|
||||
<meta name="twitter:title" content="Dich'blog">
|
||||
<meta property="twitter:domain" content="blog.dich.bid">
|
||||
<meta property="twitter:url" content="https://blog.dich.bid/learn-linux-for-pc-4/">
|
||||
|
||||
<link rel="alternate" type="application/atom+xml" title="Dich'blog Atom Feed" href="https://blog.dich.bid/atom.xml" />
|
||||
|
||||
|
||||
<link rel="icon" type="image/png" href=/dich.webp />
|
||||
|
||||
<!-- ✅ Added center alignment styles -->
|
||||
<style>
|
||||
.footer {
|
||||
text-align: center;
|
||||
padding: 1rem 0;
|
||||
}
|
||||
|
||||
.footer__inner {
|
||||
display: flex;
|
||||
justify-content: center;
|
||||
flex-direction: column;
|
||||
align-items: center;
|
||||
}
|
||||
|
||||
.copyright {
|
||||
text-align: center;
|
||||
}
|
||||
</style>
|
||||
</head>
|
||||
|
||||
<body class="">
|
||||
<div class="container">
|
||||
|
||||
<header class="header">
|
||||
<div class="header__inner">
|
||||
<div class="header__logo">
|
||||
|
||||
<a href="https://blog.dich.bid" style="text-decoration: none;">
|
||||
<div class="logo">
|
||||
|
||||
Dich'blog
|
||||
|
||||
</div>
|
||||
</a>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
|
||||
|
||||
<nav class="menu">
|
||||
<ul class="menu__inner">
|
||||
<li class="active"><a href="https://blog.dich.bid">blog</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/archive">archive</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/tags">tags</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/weekly">weekly</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/search">search</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/about">about me</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/links">links</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/atom.xml">rss</a></li>
|
||||
|
||||
<li><a href="https://github.com/Dichgrem" target="_blank" rel="noopener noreferrer">github</a></li>
|
||||
</ul>
|
||||
</nav>
|
||||
|
||||
|
||||
|
||||
</header>
|
||||
|
||||
|
||||
<div class="content">
|
||||
|
||||
<div class="post">
|
||||
|
||||
<h1 class="post-title"><a href="https://blog.dich.bid/learn-linux-for-pc-4/">Linux之旅(四):Terminal，Console and Shell</a></h1>
|
||||
<div class="post-meta-inline">
|
||||
|
||||
<span class="post-date">
|
||||
2023-07-23
|
||||
</span>
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
<span class="post-tags-inline">
|
||||
:: tags:
|
||||
<a class="post-tag" href="https://blog.dich.bid/tags/linux/">#Linux</a></span>
|
||||
|
||||
|
||||
<div class="post-content">
|
||||
<p>前言 在linux的学习过程中，我们常常遇到诸如 Terminal，Console，bash,zsh,shell,tty 等概念，这些概念常常被混淆，似乎都和命令行相关。本文从历史角度出发介绍它们的前世今生。</p>
|
||||
<span id="continue-reading"></span><h2 id="zhong-duan-he-kong-zhi-tai">终端和控制台</h2>
|
||||
<p>终端，英文叫做 terminal ,通常简称为 term；控制台，英文叫做 console。</p>
|
||||
<p>要明白这两者的关系，还得从最初的计算机说起。当时的计算机价格昂贵，一台计算机一般是由多个人同时使用的。在这种情况下一台计算机需要连接上许多套键盘和显示器来供多个人使用。在以前专门有这种可以连上一台电脑的设备，只有显示器和键盘，还有简单的处理电路，本身不具有处理计算机信息的能力，他是负责连接到一台正常的计算机上（通常是通过串口） ，然后登陆计算机，并对该计算机进行操作。当然，那时候的计算机操作系统都是多任务多用户的操作系统。这样一台只有显示器和键盘能够通过串口连接到计算机的设备就叫做终端。</p>
|
||||
<p>而控制台又是什么回事呢？其概念来自于管风琴的控制台。顾名思义，控制台就是一个直接控制设备的台面（一个面板，上面有很多控制按钮）。 在计算机里，把那套直接连接在电脑上的键盘和显示器就叫做控制台。</p>
|
||||
<p>终端是通过串口连接上的，不是计算机本身就有的设备，而控制台是计算机本身就有的设备，一个计算机只有一个控制台。计算机启动的时候，所有的信息都会显示到控制台上，而不会显示到终端上。也就是说，控制台是计算机的基本设备，而终端是附加设备。 当然，由于控制台也有终端一样的功能，控制台有时候也被模糊的统称为终端。</p>
|
||||
<p>以上是控制台和终端的历史遗留区别。现在由于计算机硬件越来越便宜，终端和控制台的概念也慢慢演化了。终端和控制台由硬件的概念，演化成了软件的概念。
|
||||
</p>
|
||||
<h2 id="nei-he-yu-wai-ke">内核与外壳</h2>
|
||||
<p>内核（ Kernel ）和外壳（ Shell ）是 linux 的两个主要部分。Kernel 是操作系统的核心，系统的文件管理、进程管理、内存管理、设备管理这些功能，都是由 Kernel 提供的。</p>
|
||||
<p>用户和操作系统内核交流需要一个工具，那么这个工具就是 Shell。</p>
|
||||
<p>什么是 Shell？在 Linux 中，最常见的 Shell 形式有命令行界面命令行界面和图形界面两种。并不是打开的那个终端窗口就是 Shell，如Alacritty、Gnome-Terminal、xterm 、kitty等程序，它们不是 Shell，而它们里面运行的 Bash、Zsh、fish 等命令行解释器程序，才是 Shell。</p>
|
||||
<p>那 Alacritty、Gnome-Terminal、xtermxterm 是什么？</p>
|
||||
<p>它们是终端模拟器。</p>
|
||||
<p>前面提到过，在远古时代，终端和控制台都是有实体的。控制台直接和计算机在一起，你可以通过控制台控制计算机。终端通过数据线和计算机连接，终端也提供一个键盘和一个屏幕，你可以通过键盘向计算机下达指令，然后通过屏幕观察输出。</p>
|
||||
<p>但是现在的计算机组成和以前不一样了，一般一台电脑都是自带键盘和屏幕，很少再外接终端设备。</p>
|
||||
<p>所以 Linux 提供了另外一个更高级的功能，那就是虚拟终端。那就是在一台电脑上，通过软件的模拟，好像有好几个终端连接在这台计算机上一样。</p>
|
||||
<p>现在说的终端，比如 linux 中的虚拟终端，都是软件的概念。虚拟终端称之为 tty，tty 是电传打字机电传打字机 Teletypewriter 的缩写，在带显示屏的视频终端出现之前，tty是最流行的终端设备。每一个 tty 都有一个编号，在/dev目录下有相应的设备文件。其中/dev/tty1到/dev/tty7可以通过 Ctrl+Alt+F1 到 Ctrl+Alt+F7 进行切换，也可以通过 chvt 命令进行切换，就好比是以前多人公用的计算机中的六个终端设备，这就是为什么这个叫“虚拟终端”的原因。</p>
|
||||
<h2 id="shi-dai-bian-qian">时代变迁</h2>
|
||||
<p>随着时间的推移，我们看到了从硬件到软件的转变，以及从多用户共享到个人使用的转变。这种变迁不仅影响了终端和控制台的概念，也塑造了我们对计算机的理解和期待。</p>
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
<div class="pagination">
|
||||
<div class="pagination__title">
|
||||
<span class="pagination__title-h">Thanks for reading! Read other posts?</span>
|
||||
<hr />
|
||||
</div>
|
||||
<div class="pagination__buttons">
|
||||
<span class="button previous">
|
||||
<a href="https://blog.dich.bid/learn-linux-for-pc-3/">
|
||||
<span class="button__icon">←</span>
|
||||
<span class="button__text">Linux之旅(三):内核/shell/包管理/文件系统/桌面环境</span>
|
||||
</a>
|
||||
</span>
|
||||
|
||||
|
||||
<span class="button next">
|
||||
<a href="https://blog.dich.bid/learn-linux-for-pc-5/">
|
||||
<span class="button__text">Linux之旅(五):BIOS-UEFI-MBR-GPT-GRUB</span>
|
||||
<span class="button__icon">→</span>
|
||||
</a>
|
||||
</span>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
</div>
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
<footer class="footer">
|
||||
<div class="footer__inner">
|
||||
<div class="copyright">
|
||||
<span>©
|
||||
2025
|
||||
Dichgrem</span>
|
||||
<span class="copyright-theme">
|
||||
<span class="copyright-theme-sep"> :: CC BY-SA 4.0 :: A friend comes from distant lands</span>
|
||||
</a>
|
||||
</span>
|
||||
</div>
|
||||
</div>
|
||||
</footer>
|
||||
|
||||
</div>
|
||||
</body>
|
||||
</html>
|
||||
|
||||
287
public/learn-linux-for-pc-5/index.html
Normal file
287
public/learn-linux-for-pc-5/index.html
Normal file
@ -0,0 +1,287 @@
|
||||
<!DOCTYPE html>
|
||||
<html lang="en">
|
||||
|
||||
<head>
|
||||
<title>Dich'blog</title>
|
||||
|
||||
<meta http-equiv="content-type" content="text/html; charset=utf-8">
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1">
|
||||
<meta name="robots" content="noodp"/>
|
||||
|
||||
<link rel="stylesheet" href="https://blog.dich.bid/style.css">
|
||||
<link rel="stylesheet" href="https://blog.dich.bid/color/blue.css">
|
||||
|
||||
<link rel="stylesheet" href="https://blog.dich.bid/color/background_dark.css">
|
||||
|
||||
<link rel="stylesheet" href="https://blog.dich.bid/font-hack-subset.css">
|
||||
|
||||
<meta name="description" content="">
|
||||
|
||||
<meta property="og:description" content="">
|
||||
<meta property="og:title" content="Dich'blog">
|
||||
<meta property="og:type" content="article">
|
||||
<meta property="og:url" content="https://blog.dich.bid/learn-linux-for-pc-5/">
|
||||
|
||||
<meta name="twitter:card" content="summary_large_image">
|
||||
<meta name="twitter:description" content="">
|
||||
<meta name="twitter:title" content="Dich'blog">
|
||||
<meta property="twitter:domain" content="blog.dich.bid">
|
||||
<meta property="twitter:url" content="https://blog.dich.bid/learn-linux-for-pc-5/">
|
||||
|
||||
<link rel="alternate" type="application/atom+xml" title="Dich'blog Atom Feed" href="https://blog.dich.bid/atom.xml" />
|
||||
|
||||
|
||||
<link rel="icon" type="image/png" href=/dich.webp />
|
||||
|
||||
<!-- ✅ Added center alignment styles -->
|
||||
<style>
|
||||
.footer {
|
||||
text-align: center;
|
||||
padding: 1rem 0;
|
||||
}
|
||||
|
||||
.footer__inner {
|
||||
display: flex;
|
||||
justify-content: center;
|
||||
flex-direction: column;
|
||||
align-items: center;
|
||||
}
|
||||
|
||||
.copyright {
|
||||
text-align: center;
|
||||
}
|
||||
</style>
|
||||
</head>
|
||||
|
||||
<body class="">
|
||||
<div class="container">
|
||||
|
||||
<header class="header">
|
||||
<div class="header__inner">
|
||||
<div class="header__logo">
|
||||
|
||||
<a href="https://blog.dich.bid" style="text-decoration: none;">
|
||||
<div class="logo">
|
||||
|
||||
Dich'blog
|
||||
|
||||
</div>
|
||||
</a>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
|
||||
|
||||
<nav class="menu">
|
||||
<ul class="menu__inner">
|
||||
<li class="active"><a href="https://blog.dich.bid">blog</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/archive">archive</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/tags">tags</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/weekly">weekly</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/search">search</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/about">about me</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/links">links</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/atom.xml">rss</a></li>
|
||||
|
||||
<li><a href="https://github.com/Dichgrem" target="_blank" rel="noopener noreferrer">github</a></li>
|
||||
</ul>
|
||||
</nav>
|
||||
|
||||
|
||||
|
||||
</header>
|
||||
|
||||
|
||||
<div class="content">
|
||||
|
||||
<div class="post">
|
||||
|
||||
<h1 class="post-title"><a href="https://blog.dich.bid/learn-linux-for-pc-5/">Linux之旅(五):BIOS-UEFI-MBR-GPT-GRUB</a></h1>
|
||||
<div class="post-meta-inline">
|
||||
|
||||
<span class="post-date">
|
||||
2023-07-24
|
||||
</span>
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
<span class="post-tags-inline">
|
||||
:: tags:
|
||||
<a class="post-tag" href="https://blog.dich.bid/tags/linux/">#Linux</a></span>
|
||||
|
||||
|
||||
<div class="post-content">
|
||||
<p>前言 在计算机领域，系统引导和磁盘分区是至关重要的。本文将介绍BIOS与UEFI，MBR与GPT，以及它们之间的异同点。此外，我们还会讨论与这些概念密切相关的引导加载程序——GRUB。</p>
|
||||
<span id="continue-reading"></span><h2 id="bios">BIOS</h2>
|
||||
<blockquote>
|
||||
<p><code>BIOS（Basic Input Output System）</code>，直译成中文名称就是"<code>基本输入输出系统</code>"。它是一组固化到主板中一个ROM芯片上的程序，它可以从CMOS中读写系统设置的具体信息。此程序保存着计算机最重要的基本输入输出程序、开机后的自检程序和系统自启动程序。简单来说，BIOS只认识设备，不认识分区、不认识文件。</p>
|
||||
</blockquote>
|
||||
<h2 id="uefi">UEFI</h2>
|
||||
<blockquote>
|
||||
<p>UEFI（统一可扩展固件接口）是一个公开的规范，定义了操作系统和平台固件之间的软件接口。UEFI 是传统 PC BIOS 的继承者，是取代传统BIOS的，相比传统BIOS来说，它更易实现，容错和纠错特性也更强。 它将引导数据存储在 .efi 文件中，而不是固件中。你经常会在新款的主板中找到 UEFI 启动模式。UEFI 启动模式包含一个特殊的 EFI 分区，用于存储 .efi 文件并用于引导过程和引导加载程序。</p>
|
||||
</blockquote>
|
||||
<blockquote>
|
||||
<p>UEFI使用GPT的分区引导方案，支持更大的硬盘。由于省去了BIOS自检的过程，所以启动速度更快。传统BIOS主要支持MBR引导，UEFI则是取代传统BIOS，它加入了对新硬件的支持，其中就有支持2TB以上硬盘。</p>
|
||||
</blockquote>
|
||||
<h2 id="mbr">MBR</h2>
|
||||
<blockquote>
|
||||
<p>全新硬盘在使用之前必须进行分区格式化，硬盘分区初始化的格式主要有两种，分别为<code>MBR</code>格式和<code>GPT</code>格式。MBR是传统的分区表类型，当一台电脑启动时，它会先启动主板上的BIOS系统，BIOS再从硬盘上读取MBR主引导记录，硬盘上的MBR运行后，就会启动操作系统，但最大的缺点则是不支持容量大于2T的硬盘。</p>
|
||||
</blockquote>
|
||||
<h2 id="gpt">GPT</h2>
|
||||
<blockquote>
|
||||
<p>而GPT是另一种更先进的磁盘系统分区方式，它的出现弥补了MBR这个缺点，最大支持<code>18EB</code>的硬盘，是基于<code>UEFI</code>使用的磁盘分区架构。目前所有Windows系统均支持<code>MBR</code>，而<code>GPT</code>只有<code>64</code>位系统才能支持。<code>BIOS只支持MBR引导系统，而GPT仅可用UEFI引导系统</code>。正因为这样，现在主板大多采用BIOS集成UEFI，或UEFI集成BIOS，以此达到同时兼容MBR和GPT引导系统的目的。</p>
|
||||
</blockquote>
|
||||
<h2 id="grub">GRUB</h2>
|
||||
<blockquote>
|
||||
<p>GRUB（GRand unified bootloader）,多操作系统启动程序。它允许用户可以在计算机内同时拥有多个操作系统，并在计算机启动时选择希望运行的操作系统。</p>
|
||||
<p>GRUB可用于选择操作系统分区上的不同内核，也可用于向这些内核传递启动参数。<code>它是一个多重操作系统启动管理器，用来引导不同系统</code>，如Windows、Linux。Linux常见的引导程序包括LILO、GRUB、GRUB2。</p>
|
||||
</blockquote>
|
||||
<h2 id="legacy">Legacy</h2>
|
||||
<blockquote>
|
||||
<p>如果你遇到过刚制作的U盘启动盘无法启动，或者新买的固态硬盘做好系统后无法启动，那么大概率的问题就出现在BIOS的引导模式的选择上，是UEFI还是Legacy。legacy启动模式是指BIOS 固件用来初始化硬件设备的引导过程，Legacy启动模式包含一系列已安装的设备，这些设备在引导过程中计算机执行 POST （开机自检）测试时会被初始化。传统引导将检查所有连接设备的主引导记录 (MBR)，通常位于磁盘的第一个扇区。<br />
|
||||
当它在设备中找不到引导加载程序时，Legacy会切换到列表中的下一个设备并不断重复此过程，直到找到引导加载程序，否则返回错误。</p>
|
||||
</blockquote>
|
||||
<h2 id="biao-ge">表格</h2>
|
||||
<h3 id="bios-uefi">BIOS/UEFI</h3>
|
||||
<table><thead><tr><th>BIOS</th><th>UEFI</th></tr></thead><tbody>
|
||||
<tr><td>用于初始化计算机硬件并引导操作系统</td><td>在计算机启动时运行</td></tr>
|
||||
<tr><td>具有较少功能和灵活性</td><td>具有更多功能和灵活性</td></tr>
|
||||
<tr><td></td><td>支持更大的硬盘容量、更快的启动速度、更好的安全性和更多的扩展性v</td></tr>
|
||||
<tr><td></td><td>通常具有图形用户界面（GUI）</td></tr>
|
||||
</tbody></table>
|
||||
<h3 id="mbr-gpt">MBR/GPT</h3>
|
||||
<table><thead><tr><th>MBR</th><th>GPT</th></tr></thead><tbody>
|
||||
<tr><td>用于分区磁盘并存储分区布局信息</td><td>用于分区磁盘并存储分区布局信息</td></tr>
|
||||
<tr><td>支持最多4个主分区或3个主分区加1个扩展分区</td><td>支持最多4个主分区或3个主分区加1个扩展分区支持最多4个主分区或3个主分区加1个扩展分区</td></tr>
|
||||
<tr><td></td><td>具有更好的数据完整性和可靠性，使用校验和检测数据损坏</td></tr>
|
||||
<tr><td></td><td>UEFI需要GPT格式的磁盘才能引导</td></tr>
|
||||
</tbody></table>
|
||||
<h3 id="uefi-legacy">UEFI/Legacy</h3>
|
||||
<table><thead><tr><th>UEFI 引导模式</th><th>Legacy引导模式</th></tr></thead><tbody>
|
||||
<tr><td>UEFI 提供了更好的用户界面</td><td>Legacy引导模式是传统的且非常基本的</td></tr>
|
||||
<tr><td>使用 GPT 分区方案</td><td>使用 MBR 分区方案</td></tr>
|
||||
<tr><td>UEFI 提供更快的启动时间</td><td>相比UEFI，它的速度较慢</td></tr>
|
||||
<tr><td>由于 UEFI 使用 GPT 分区方案，因此它可以支持多达 9 zB 的存储设备</td><td>Legacy使用的 MBR 分区方案仅支持最多 2 TB 存储设备</td></tr>
|
||||
<tr><td>UEFI 以 32 位和 64 位运行，支持鼠标和触摸板</td><td>Legacy在仅支持键盘，仅 16 位模式下运行</td></tr>
|
||||
<tr><td>它允许安全启动，防止加载未经授权的应用程序它还可能阻碍双启动，因为它将操作系统（OS）视为应用程序</td><td>它不提供允许加载未经授权的应用程序的安全启动方法，未限制双启动</td></tr>
|
||||
<tr><td>它具有更简单的更新过程</td><td>与UEFI相比，它更复杂</td></tr>
|
||||
</tbody></table>
|
||||
<h2 id="zu-he">组合</h2>
|
||||
<ul>
|
||||
<li>
|
||||
<p><strong>BIOS+MBR</strong>：</p>
|
||||
<p>这是最传统的，系统都会支持；唯一的缺点就是<code>不支持容量大于2T的硬盘</code>。</p>
|
||||
</li>
|
||||
<li>
|
||||
<p><strong>BIOS+GPT</strong>：</p>
|
||||
<p>BIOS是可以使用GPT分区表的硬盘来作为数据盘的，但不能引导系统；若电脑同时带有容量小于2T的硬盘和容量大于2T的硬盘，<code>小于2T的可以用MBR分区表安装系统，而大于2T的可以使用GPT分区表来存放资料</code>。但系统须使用64位系统。</p>
|
||||
</li>
|
||||
<li>
|
||||
<p><strong>UEFI+MBR</strong>：</p>
|
||||
<p>可以把UEFI设置成<code>Legacy模式</code>（传统模式）让其支持传统MBR启动，效果同<code>BIOS+MBR</code>；也可以建立FAT分区，放置UEFI启动文件来，可应用在U盘和移动硬盘上实现双模式启动。</p>
|
||||
</li>
|
||||
<li>
|
||||
<p><strong>UEFI+GPT</strong>：</p>
|
||||
<p>如果要把大于2T的硬盘作为系统盘来安装系统的话，就必须<code>UEFI+GPT</code>。而且系统须使用64位系统，否则无法引导。但系统又不是传统在PE下安装后就能直接使用的，引导还得经过处理才行。</p>
|
||||
</li>
|
||||
</ul>
|
||||
<h2 id="xi-tong-de-qi-dong-guo-cheng">系统的启动过程</h2>
|
||||
<p>从按下计算机的开机按钮到用户开始使用计算机，涉及了多个步骤和组件，让我们一起详细了解整个过程：</p>
|
||||
<p><strong>1. 电源启动</strong>：</p>
|
||||
<ul>
|
||||
<li>用户按下计算机的开机按钮，电源开始供电，计算机硬件开始初始化。电源将电流传递到主板上的BIOS/UEFI芯片。</li>
|
||||
</ul>
|
||||
<p><strong>2. BIOS/UEFI启动</strong>：</p>
|
||||
<ul>
|
||||
<li>BIOS/UEFI芯片接收到电源信号后，开始执行初始化过程。它首先进行自检（POST），检测主板、CPU、内存等硬件设备的工作状态，并在显示屏上输出相关信息。</li>
|
||||
<li>BIOS/UEFI根据配置的启动顺序（通常为硬盘、光盘、USB等）搜索启动设备，并加载位于启动设备上的引导加载程序。</li>
|
||||
</ul>
|
||||
<p><strong>3. 引导加载程序加载</strong>：</p>
|
||||
<ul>
|
||||
<li>引导加载程序（如GRUB）被加载到内存中，它负责后续的操作系统加载过程。GRUB通常会显示启动菜单，列出可用的操作系统选项。</li>
|
||||
<li>用户可以在GRUB菜单中选择要启动的操作系统，或者等待默认选项启动。</li>
|
||||
</ul>
|
||||
<p><strong>4. 操作系统加载</strong>：</p>
|
||||
<ul>
|
||||
<li>一旦选择了启动选项，引导加载程序会加载操作系统的内核和初始化RAM磁盘（initramfs/initrd）。</li>
|
||||
<li>内核加载完成后，操作系统开始启动初始化过程，包括加载系统服务、挂载文件系统、启动用户界面等。</li>
|
||||
</ul>
|
||||
<p><strong>5. 用户登录</strong>：</p>
|
||||
<ul>
|
||||
<li>操作系统初始化完成后，显示登录界面（如果配置了图形用户界面），用户输入用户名和密码登录系统。</li>
|
||||
<li>如果登录成功，操作系统加载用户的桌面环境或命令行界面，用户开始使用计算机。</li>
|
||||
</ul>
|
||||
<h2 id="ge-chong-yin-dao-jia-zai-cheng-xu">各种引导加载程序</h2>
|
||||
<table><thead><tr><th>特性</th><th>GRUB（GRand Unified Bootloader）</th><th>LILO（Linux Loader）</th><th>systemd-boot（前身为 gummiboot）</th><th>rEFInd（UEFI 引导管理器）</th></tr></thead><tbody>
|
||||
<tr><td><strong>支持的系统类型</strong></td><td>BIOS 和 UEFI</td><td>仅支持 BIOS 模式</td><td>仅支持 UEFI</td><td>仅支持 UEFI</td></tr>
|
||||
<tr><td><strong>多系统引导支持</strong></td><td>✅ 强大支持</td><td>❌ 不支持多系统引导</td><td>✅ 支持（需手动配置）</td><td>✅ 自动检测操作系统</td></tr>
|
||||
<tr><td><strong>图形界面支持</strong></td><td>✅ 支持（可自定义主题）</td><td>❌ 不支持</td><td>❌ 不支持</td><td>✅ 支持（可自定义主题）</td></tr>
|
||||
<tr><td><strong>配置方式</strong></td><td>配置文件（复杂）</td><td>配置文件（简单）</td><td>配置文件（简单）</td><td>配置文件（简单）</td></tr>
|
||||
<tr><td><strong>命令行支持</strong></td><td>✅ 支持（交互式命令行）</td><td>❌ 不支持</td><td>❌ 不支持</td><td>❌ 不支持</td></tr>
|
||||
<tr><td><strong>文件系统支持</strong></td><td>✅ 支持多种文件系统</td><td>✅ 支持 ext2/ext3/ext4 等</td><td>✅ 支持 ext4、FAT 等</td><td>✅ 支持 ext4、FAT 等</td></tr>
|
||||
<tr><td><strong>安全启动支持</strong></td><td>✅ 支持（需配置）</td><td>❌ 不支持</td><td>✅ 支持（需配置）</td><td>✅ 支持（需配置）</td></tr>
|
||||
<tr><td><strong>安装复杂度</strong></td><td>中等（需配置）</td><td>较低</td><td>较低</td><td>中等（需配置）</td></tr>
|
||||
<tr><td><strong>适用场景</strong></td><td>多系统引导、复杂配置</td><td>简单系统引导</td><td>简单系统引导</td><td>多系统引导、美观界面</td></tr>
|
||||
</tbody></table>
|
||||
<h2 id="hou-ji">后记</h2>
|
||||
<ul>
|
||||
<li><a href="https://segmentfault.com/a/1190000020850901">聊聊BIOS、UEFI、MBR、GPT、GRUB……</a></li>
|
||||
</ul>
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
<div class="pagination">
|
||||
<div class="pagination__title">
|
||||
<span class="pagination__title-h">Thanks for reading! Read other posts?</span>
|
||||
<hr />
|
||||
</div>
|
||||
<div class="pagination__buttons">
|
||||
<span class="button previous">
|
||||
<a href="https://blog.dich.bid/learn-linux-for-pc-4/">
|
||||
<span class="button__icon">←</span>
|
||||
<span class="button__text">Linux之旅(四):Terminal，Console and Shell</span>
|
||||
</a>
|
||||
</span>
|
||||
|
||||
|
||||
<span class="button next">
|
||||
<a href="https://blog.dich.bid/learn-linux-for-pc-6/">
|
||||
<span class="button__text">Linux之旅(六):常用命令与性能分析</span>
|
||||
<span class="button__icon">→</span>
|
||||
</a>
|
||||
</span>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
</div>
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
<footer class="footer">
|
||||
<div class="footer__inner">
|
||||
<div class="copyright">
|
||||
<span>©
|
||||
2025
|
||||
Dichgrem</span>
|
||||
<span class="copyright-theme">
|
||||
<span class="copyright-theme-sep"> :: CC BY-SA 4.0 :: A friend comes from distant lands</span>
|
||||
</a>
|
||||
</span>
|
||||
</div>
|
||||
</div>
|
||||
</footer>
|
||||
|
||||
</div>
|
||||
</body>
|
||||
</html>
|
||||
|
||||
353
public/learn-linux-for-pc-6/index.html
Normal file
353
public/learn-linux-for-pc-6/index.html
Normal file
@ -0,0 +1,353 @@
|
||||
<!DOCTYPE html>
|
||||
<html lang="en">
|
||||
|
||||
<head>
|
||||
<title>Dich'blog</title>
|
||||
|
||||
<meta http-equiv="content-type" content="text/html; charset=utf-8">
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1">
|
||||
<meta name="robots" content="noodp"/>
|
||||
|
||||
<link rel="stylesheet" href="https://blog.dich.bid/style.css">
|
||||
<link rel="stylesheet" href="https://blog.dich.bid/color/blue.css">
|
||||
|
||||
<link rel="stylesheet" href="https://blog.dich.bid/color/background_dark.css">
|
||||
|
||||
<link rel="stylesheet" href="https://blog.dich.bid/font-hack-subset.css">
|
||||
|
||||
<meta name="description" content="">
|
||||
|
||||
<meta property="og:description" content="">
|
||||
<meta property="og:title" content="Dich'blog">
|
||||
<meta property="og:type" content="article">
|
||||
<meta property="og:url" content="https://blog.dich.bid/learn-linux-for-pc-6/">
|
||||
|
||||
<meta name="twitter:card" content="summary_large_image">
|
||||
<meta name="twitter:description" content="">
|
||||
<meta name="twitter:title" content="Dich'blog">
|
||||
<meta property="twitter:domain" content="blog.dich.bid">
|
||||
<meta property="twitter:url" content="https://blog.dich.bid/learn-linux-for-pc-6/">
|
||||
|
||||
<link rel="alternate" type="application/atom+xml" title="Dich'blog Atom Feed" href="https://blog.dich.bid/atom.xml" />
|
||||
|
||||
|
||||
<link rel="icon" type="image/png" href=/dich.webp />
|
||||
|
||||
<!-- ✅ Added center alignment styles -->
|
||||
<style>
|
||||
.footer {
|
||||
text-align: center;
|
||||
padding: 1rem 0;
|
||||
}
|
||||
|
||||
.footer__inner {
|
||||
display: flex;
|
||||
justify-content: center;
|
||||
flex-direction: column;
|
||||
align-items: center;
|
||||
}
|
||||
|
||||
.copyright {
|
||||
text-align: center;
|
||||
}
|
||||
</style>
|
||||
</head>
|
||||
|
||||
<body class="">
|
||||
<div class="container">
|
||||
|
||||
<header class="header">
|
||||
<div class="header__inner">
|
||||
<div class="header__logo">
|
||||
|
||||
<a href="https://blog.dich.bid" style="text-decoration: none;">
|
||||
<div class="logo">
|
||||
|
||||
Dich'blog
|
||||
|
||||
</div>
|
||||
</a>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
|
||||
|
||||
<nav class="menu">
|
||||
<ul class="menu__inner">
|
||||
<li class="active"><a href="https://blog.dich.bid">blog</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/archive">archive</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/tags">tags</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/weekly">weekly</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/search">search</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/about">about me</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/links">links</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/atom.xml">rss</a></li>
|
||||
|
||||
<li><a href="https://github.com/Dichgrem" target="_blank" rel="noopener noreferrer">github</a></li>
|
||||
</ul>
|
||||
</nav>
|
||||
|
||||
|
||||
|
||||
</header>
|
||||
|
||||
|
||||
<div class="content">
|
||||
|
||||
<div class="post">
|
||||
|
||||
<h1 class="post-title"><a href="https://blog.dich.bid/learn-linux-for-pc-6/">Linux之旅(六):常用命令与性能分析</a></h1>
|
||||
<div class="post-meta-inline">
|
||||
|
||||
<span class="post-date">
|
||||
2023-07-25
|
||||
</span>
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
<span class="post-tags-inline">
|
||||
:: tags:
|
||||
<a class="post-tag" href="https://blog.dich.bid/tags/linux/">#Linux</a></span>
|
||||
|
||||
|
||||
<div class="post-content">
|
||||
<p>前言 在学习Linux操作系统时，熟悉常用命令和性能分析工具是至关重要的。让我们一起探索Linux的世界，提升技能，解锁无限可能！</p>
|
||||
<span id="continue-reading"></span>
|
||||
<blockquote>
|
||||
<p>翻译自https://medium.com/netflix-techblog/linux-performance-analysis-in-60-000-milliseconds-accc10403c55。</p>
|
||||
</blockquote>
|
||||
<h2 id="wen-ti-bei-jing"><strong>问题背景</strong></h2>
|
||||
<p>当登录到一台有性能问题的Linux服务器，第一分钟要检查什么？</p>
|
||||
<p>在Netflix，我们拥有庞大的EC2 Linux虚拟机云，我们有众多性能分析工具来监视和诊断这些Linux服务器的性能。这些工具包括Atlas（负责整个虚拟机云的监控）和Vector（负责按需对虚拟机实例进行性能分析）。这些工具可以帮助我们解决大多数问题，但有时我们需要登录到虚拟机实例，并运行一些标准的Linux性能工具。</p>
|
||||
<h2 id="qian-60miao-zhai-yao"><strong>前60秒：摘要</strong></h2>
|
||||
<p>在本文中，Netflix性能工程团队将使用您应该使用的标准Linux工具在命令行中向您展示一个性能诊断过程的前60秒。在60秒内，您可以通过运行以下十个命令来了解有关系统资源使用和运行进程的信息。最应该关注的是一些很容易理解的错误、饱和度指标和资源利用率等指标。饱和度是衡量资源负载超出其处理能力的指标，它可以通过观察请求队列的长度或等待时间反映出来。</p>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>uptime
|
||||
</span><span>dmesg | tail
|
||||
</span><span>vmstat 1
|
||||
</span><span>mpstat -P ALL 1
|
||||
</span><span>pidstat 1
|
||||
</span><span>iostat -xz 1
|
||||
</span><span>free -m
|
||||
</span><span>sar -n DEV 1
|
||||
</span><span>sar -n TCP,ETCP 1
|
||||
</span><span>top
|
||||
</span></code></pre>
|
||||
<p>其中的一些命令需要安装sysstat软件包。这些命令暴露出的指标将帮助您完成一些USE方法：一种查找性能瓶颈的方法。它们涉及检查所有资源（CPU、内存、磁盘等）的利用率，饱和度和错误指标。在诊断过程中还应该注意检查和排除某些资源的问题。因为通过排除某些资源的问题，可以缩小诊断的范围，并指民后续的诊断。</p>
|
||||
<h2 id="uptime"><strong>uptime</strong></h2>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>$ uptime
|
||||
</span><span>23:51:26 up 21:31, 1 user, load average: 30.02, 26.43, 19.02
|
||||
</span></code></pre>
|
||||
<p>这是快速查看平均负载的方法，该平均负载指标了要运行的任务（进程）的数量。在Linux系统上，这些数字包括要在CPU上运行的进程以及在不中断IO（通常是磁盘IO）中阻塞的进程。这里给出了资源负载高层次的概览，但是没有其它工具就很难正确理解，值得快速看一眼。</p>
|
||||
<p>这三个数字是指数衰减移动平均值，分别代表了1分钟、5分钟、15分钟的平均值。这三个数字使我们对负载如何随时间变化有了一定的了解。例如，如果您去诊断一个有问题的服务器，发现1分钟的值比15分钟的值低很多，那么您可能已经登录得太晚了，错过了问题。</p>
|
||||
<p>在上面的例子中，平均负载有所增加，因为1分钟的值30相对15分钟的值19来说大了一些。数字变大意味着很多种可能：有可能是CPU的需求变多了，使用3和4中提到的vmstat或mpstat命令将可以进一步确认问题。</p>
|
||||
<h2 id="dmesg-tail"><strong>dmesg|tail</strong></h2>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>$ dmesg | tail
|
||||
</span><span>[1880957.563150] perl invoked oom-killer: gfp_mask=0x280da, order=0, oom_score_adj=0
|
||||
</span><span>[...]
|
||||
</span><span>[1880957.563400] Out of memory: Kill process 18694 (perl) score 246 or sacrifice child
|
||||
</span><span>[1880957.563408] Killed process 18694 (perl) total-vm:1972392kB, anon-rss:1953348kB, file-rss:0kB
|
||||
</span><span>[2320864.954447] TCP: Possible SYN flooding on port 7001. Dropping request. Check SNMP counters.
|
||||
</span></code></pre>
|
||||
<p>该命令展示最近 10条系统消息。在这些系统消息中查找有可能引起性能问题的报错。上面的例子包括oom-killer和TCP丢弃了一个请求。</p>
|
||||
<p>不能忘记这个步骤，dmesg通常对诊断问题很有价值。</p>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>## **vmstat 1**
|
||||
</span><span>$ vmstat 1
|
||||
</span><span>procs ---------memory---------- ---swap-- -----io---- -system-- ------cpu-----
|
||||
</span><span> r b swpd free buff cache si so bi bo in cs us sy id wa st
|
||||
</span><span>34 0 0 200889792 73708 591828 0 0 0 5 6 10 96 1 3 0 0
|
||||
</span><span>32 0 0 200889920 73708 591860 0 0 0 592 13284 4282 98 1 1 0 0
|
||||
</span><span>32 0 0 200890112 73708 591860 0 0 0 0 9501 2154 99 1 0 0 0
|
||||
</span><span>32 0 0 200889568 73712 591856 0 0 0 48 11900 2459 99 0 0 0 0
|
||||
</span><span>32 0 0 200890208 73712 591860 0 0 0 0 15898 4840 98 1 1 0 0
|
||||
</span></code></pre>
|
||||
<p>vmstat是虚拟内存统计(Virtual Memory Stat)的缩写，vmstat(8)是一个通常可用的工具(最初是在之前的BSD时代创建的)，它每行打印一行服务器关键统计的概览。</p>
|
||||
<p>vmstat使用参数1运行，意味着每1秒打印打印一次概览。命令输出的第一行展示的是从启动开始的平均值，而不是最近一秒的平均值。因此跳过第一行，除非您想学习并记住哪一列是哪一列。</p>
|
||||
<p>要检查的列：</p>
|
||||
<p>r：在CPU上运行并等待回合的进程数。由于它不包含IO，因此它比指示CPU饱和的平均负载提供了更多的信息。一个大于CPU核数的r值就是饱和的。
|
||||
free：空闲的内存（单位的KB）。如果计数很大，说明服务器有足够的内存，free -m命令将对空闲内存的状态有更好的说明。
|
||||
si、so：交换置入和交换置出。如果这两个值是非空，说明物理内存用完了，现在在使用交换内存了。
|
||||
us、sy、id、wa、st：这些是CPU时间的分类，其是所有CPU的平均值。它们是用户时间、系统时间(内核)、空闲时间、等待IO和被偷窃时间（被其它宾客系统进行使用，或宾客系统隔离的驱动程序域Xen）
|
||||
通过将用户时间和系统时间这两个分类相加，即可判断CPU是否繁忙。一定的等待IO时间说明磁盘有可能是性能瓶颈。你可以认为等待IO时间是另一种形式的空闲时间，它提供了它是如何空闲的线索。</p>
|
||||
<p>IO处理需要占用CPU系统时间。一个较高的CPU系统时间（超过20%）可能会很有趣，有必要进一步研究：也许内核在很低效地处理IO。</p>
|
||||
<p>在上面的示例中，CPU时间基本全在用户时间，这说明应用程序本身在大量占用CPU时间。CPU的平均利用率也远远超过90%。这不一定是问题，可以使用r列来检查饱和度。</p>
|
||||
<h2 id="mpstat-p-all-1"><strong>mpstat -P ALL 1</strong></h2>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>$ mpstat -P ALL 1
|
||||
</span><span>Linux 3.13.0-49-generic (titanclusters-xxxxx) 07/14/2015 _x86_64_ (32 CPU)
|
||||
</span><span>07:38:49 PM CPU %usr %nice %sys %iowait %irq %soft %steal %guest %gnice %idle
|
||||
</span><span>07:38:50 PM all 98.47 0.00 0.75 0.00 0.00 0.00 0.00 0.00 0.00 0.78
|
||||
</span><span>07:38:50 PM 0 96.04 0.00 2.97 0.00 0.00 0.00 0.00 0.00 0.00 0.99
|
||||
</span><span>07:38:50 PM 1 97.00 0.00 1.00 0.00 0.00 0.00 0.00 0.00 0.00 2.00
|
||||
</span><span>07:38:50 PM 2 98.00 0.00 1.00 0.00 0.00 0.00 0.00 0.00 0.00 1.00
|
||||
</span><span>07:38:50 PM 3 96.97 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 3.03
|
||||
</span><span>[...]
|
||||
</span></code></pre>
|
||||
<p>此命令显示每个CPU的CPU时间明细，可用于检查不平衡的情况。单个热CPU说明是单线程应用程序在大量占用CPU时间。</p>
|
||||
<h2 id="pidstat-1"><strong>pidstat 1</strong></h2>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>$ pidstat 1
|
||||
</span><span>Linux 3.13.0-49-generic (titanclusters-xxxxx) 07/14/2015 _x86_64_ (32 CPU)
|
||||
</span><span>07:41:02 PM UID PID %usr %system %guest %CPU CPU Command
|
||||
</span><span>07:41:03 PM 0 9 0.00 0.94 0.00 0.94 1 rcuos/0
|
||||
</span><span>07:41:03 PM 0 4214 5.66 5.66 0.00 11.32 15 mesos-slave
|
||||
</span><span>07:41:03 PM 0 4354 0.94 0.94 0.00 1.89 8 java
|
||||
</span><span>07:41:03 PM 0 6521 1596.23 1.89 0.00 1598.11 27 java
|
||||
</span><span>07:41:03 PM 0 6564 1571.70 7.55 0.00 1579.25 28 java
|
||||
</span><span>07:41:03 PM 60004 60154 0.94 4.72 0.00 5.66 9 pidstat
|
||||
</span><span>07:41:03 PM UID PID %usr %system %guest %CPU CPU Command
|
||||
</span><span>07:41:04 PM 0 4214 6.00 2.00 0.00 8.00 15 mesos-slave
|
||||
</span><span>07:41:04 PM 0 6521 1590.00 1.00 0.00 1591.00 27 java
|
||||
</span><span>07:41:04 PM 0 6564 1573.00 10.00 0.00 1583.00 28 java
|
||||
</span><span>07:41:04 PM 108 6718 1.00 0.00 0.00 1.00 0 snmp-pass
|
||||
</span><span>07:41:04 PM 60004 60154 1.00 4.00 0.00 5.00 9 pidstat
|
||||
</span></code></pre>
|
||||
<p>pidstat有点像top的每个进程摘要，但是会滚动打印，而不是清屏再打印。这对于观察一段时间内的模式以及将所看到的内容（复制&粘贴）记录到调查记录中很有用。</p>
|
||||
<p>上面的示例显示两个Java进程要为消耗大量CPU负责。%CPU这一列是所有CPU核的总和，1591%说明Java进程差不多消耗了16个核的CPU。</p>
|
||||
<h2 id="iostat-xz-1"><strong>iostat -xz 1</strong></h2>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>$ iostat -xz 1
|
||||
</span><span>Linux 3.13.0-49-generic (titanclusters-xxxxx) 07/14/2015 _x86_64_ (32 CPU)
|
||||
</span><span>avg-cpu: %user %nice %system %iowait %steal %idle
|
||||
</span><span> 73.96 0.00 3.73 0.03 0.06 22.21
|
||||
</span><span>Device: rrqm/s wrqm/s r/s w/s rkB/s wkB/s avgrq-sz avgqu-sz await r_await w_await svctm %util
|
||||
</span><span>xvda 0.00 0.23 0.21 0.18 4.52 2.08 34.37 0.00 9.98 13.80 5.42 2.44 0.09
|
||||
</span><span>xvdb 0.01 0.00 1.02 8.94 127.97 598.53 145.79 0.00 0.43 1.78 0.28 0.25 0.25
|
||||
</span><span>xvdc 0.01 0.00 1.02 8.86 127.79 595.94 146.50 0.00 0.45 1.82 0.30 0.27 0.26
|
||||
</span><span>dm-0 0.00 0.00 0.69 2.32 10.47 31.69 28.01 0.01 3.23 0.71 3.98 0.13 0.04
|
||||
</span><span>dm-1 0.00 0.00 0.00 0.94 0.01 3.78 8.00 0.33 345.84 0.04 346.81 0.01 0.00
|
||||
</span><span>dm-2 0.00 0.00 0.09 0.07 1.35 0.36 22.50 0.00 2.55 0.23 5.62 1.78 0.03
|
||||
</span><span>[...]
|
||||
</span></code></pre>
|
||||
<p>这是了解块设备（磁盘），应用的工作负载和产生的性能影响的绝佳工具。重点关注下面的指标：</p>
|
||||
<ul>
|
||||
<li>r/s、w/s、 rkB/s、 wkB/s：这些是设备每秒交付的读取、写入、读取千字节和写入千字节。使用这些来表征块设备的工作负载。性能问题可能是由于向块设备施加了过多的工作负载。</li>
|
||||
<li>await：IO的平均时间，以毫秒为单位。这是应用程序所感受到的时间，它包括IO排队时间和IO服务时间。大于预期的平均时间可能表示块设备饱和或设备出现问题了。</li>
|
||||
<li>avgqu-sz：发给设备的平均请求数。值大于1可以表明已达到饱和状态（尽管设备通常可以并行处理请求，尤其是在多个后端磁盘所组成的前端虚拟设备的情况下）。</li>
|
||||
<li>%util：设备利用率。这是一个表征繁忙度的百分比，它表示设备每秒工作的时间。尽管它的值取决于设备，但值大于60%通常会导致性能不佳（也会通过await的值观察到）。接近100%的值通常表示饱和。</li>
|
||||
</ul>
|
||||
<p>如果存储设备是有许多后端磁盘组成的前端逻辑磁盘设备，则100%的利用率可能仅意味着100%的时间正在处理某些IO，但是后端磁盘可能远远没有饱和，并且可能还可以处理更多的工作。</p>
|
||||
<p>请记住，性能不佳的磁盘IO不一定是应用问题，通常可以使用许多技术以执行异步IO，以便使应用程序不会被阻塞住而产生直接产生IO延迟（例如，预读和缓冲写入技术）</p>
|
||||
<h2 id="free-m"><strong>free -m</strong></h2>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>$ free -m
|
||||
</span><span> total used free shared buffers cached
|
||||
</span><span>Mem: 245998 24545 221453 83 59 541
|
||||
</span><span>-/+ buffers/cache: 23944 222053
|
||||
</span><span>Swap: 0 0 0
|
||||
</span></code></pre>
|
||||
<p>右边两列：</p>
|
||||
<p>buffers：缓冲区高速缓存，用于块设备I / O
|
||||
cached：页面缓存，由文件系统使用
|
||||
我们只需要检查下它们的大小是否接近零。如果接近零的话，这可能导致较高的磁盘IO（可以使用iostat进行确认）和较差的性能。上面的示例看起来不错，每列都有较大的数据。</p>
|
||||
<p>-/+ buffers/cache为已用和空闲内存提供较少让人产生混乱的值。Linux将可用内存用于高速缓存，但是如果应用程序需要，它们可以快速被回收。因此应以某种方式将缓存的内存包括在free列中，这也就是这一行的所做的。甚至还有一个网站专门讨论了这种混乱。</p>
|
||||
<p>如果在Linux上使用ZFS，就像我们对某些服务所做的那么，因为ZFS具有自己的文件系统缓存，它们并不会反映在free -m的列中，因此这种场景下这种混乱还将存在。所以会看到似乎系统的可用内存不足，而实际上可根据需要从ZFS缓存中申请到内存。</p>
|
||||
<h2 id="sar-n-dev-1"><strong>sar -n DEV 1</strong></h2>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>$ sar -n DEV 1
|
||||
</span><span>Linux 3.13.0-49-generic (titanclusters-xxxxx) 07/14/2015 _x86_64_ (32 CPU)
|
||||
</span><span>12:16:48 AM IFACE rxpck/s txpck/s rxkB/s txkB/s rxcmp/s txcmp/s rxmcst/s %ifutil
|
||||
</span><span>12:16:49 AM eth0 18763.00 5032.00 20686.42 478.30 0.00 0.00 0.00 0.00
|
||||
</span><span>12:16:49 AM lo 14.00 14.00 1.36 1.36 0.00 0.00 0.00 0.00
|
||||
</span><span>12:16:49 AM docker0 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00
|
||||
</span><span>12:16:49 AM IFACE rxpck/s txpck/s rxkB/s txkB/s rxcmp/s txcmp/s rxmcst/s %ifutil
|
||||
</span><span>12:16:50 AM eth0 19763.00 5101.00 21999.10 482.56 0.00 0.00 0.00 0.00
|
||||
</span><span>12:16:50 AM lo 20.00 20.00 3.25 3.25 0.00 0.00 0.00 0.00
|
||||
</span><span>12:16:50 AM docker0 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00
|
||||
</span></code></pre>
|
||||
<p>此工具可以检查网络接口的吞吐量：rxkB/s和txkB/s，作为工作负载的度量，还可以检查是否已达到网络接口的限制。在上面的示例中，eth0接收速率达到22MB/s，即176Mbit/s（远低于1Gbit/s的网络接口限制，假设是千兆网卡）。</p>
|
||||
<p>此版本还具有%ifutil用来指示设备利用率（全双工双向），这也是我们使用的Brendan的nicstat工具测量出来的。就像nicstat一样，这个指标很难计算正确，而且在本例中好像不起作用（数据是0.00）。</p>
|
||||
<h2 id="sar-n-tcp-etcp-1"><strong>sar -n TCP,ETCP 1</strong></h2>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>$ sar -n TCP,ETCP 1
|
||||
</span><span>Linux 3.13.0-49-generic (titanclusters-xxxxx) 07/14/2015 _x86_64_ (32 CPU)
|
||||
</span><span>12:17:19 AM active/s passive/s iseg/s oseg/s
|
||||
</span><span>12:17:20 AM 1.00 0.00 10233.00 18846.00
|
||||
</span><span>12:17:19 AM atmptf/s estres/s retrans/s isegerr/s orsts/s
|
||||
</span><span>12:17:20 AM 0.00 0.00 0.00 0.00 0.00
|
||||
</span><span>12:17:20 AM active/s passive/s iseg/s oseg/s
|
||||
</span><span>12:17:21 AM 1.00 0.00 8359.00 6039.00
|
||||
</span><span>12:17:20 AM atmptf/s estres/s retrans/s isegerr/s orsts/s
|
||||
</span><span>12:17:21 AM 0.00 0.00 0.00 0.00 0.00
|
||||
</span></code></pre>
|
||||
<p>这是一些关键的TCP指标的摘要，包括：</p>
|
||||
<ul>
|
||||
<li>active / s：每秒本地启动的TCP连接数（例如，通过connect（））。</li>
|
||||
<li>passive/s：每秒远程启动的TCP连接数（例如，通过accept（））。</li>
|
||||
<li>retrans / s：每秒TCP重传的次数。
|
||||
主动和被动计数通常作为服务器TCP负载的粗略度量：新接受的连接数（被动）和新出站的连接数（主动）。将主动视为出站，将被动视为入站可能对理解这两个指标有些帮助，但这并不是严格意义上的（例如，考虑从localhost到localhost的连接）。</li>
|
||||
</ul>
|
||||
<p>重新传输是网络或服务器问题的迹象；它可能是不可靠的网络（例如，公共Internet），也可能是由于服务器过载并丢弃了数据包。上面的示例仅显示每秒一个新的TCP连接。</p>
|
||||
<h2 id="top"><strong>top</strong></h2>
|
||||
<p>$ top</p>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>top - 00:15:40 up 21:56, 1 user, load average: 31.09, 29.87, 29.92
|
||||
</span><span>Tasks: 871 total, 1 running, 868 sleeping, 0 stopped, 2 zombie
|
||||
</span><span>%Cpu(s): 96.8 us, 0.4 sy, 0.0 ni, 2.7 id, 0.1 wa, 0.0 hi, 0.0 si, 0.0 st
|
||||
</span><span>KiB Mem: 25190241+total, 24921688 used, 22698073+free, 60448 buffers
|
||||
</span><span>KiB Swap: 0 total, 0 used, 0 free. 554208 cached Mem
|
||||
</span><span> PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
|
||||
</span><span> 20248 root 20 0 0.227t 0.012t 18748 S 3090 5.2 29812:58 java
|
||||
</span><span> 4213 root 20 0 2722544 64640 44232 S 23.5 0.0 233:35.37 mesos-slave
|
||||
</span><span> 66128 titancl+ 20 0 24344 2332 1172 R 1.0 0.0 0:00.07 top
|
||||
</span><span> 5235 root 20 0 38.227g 547004 49996 S 0.7 0.2 2:02.74 java
|
||||
</span><span> 4299 root 20 0 20.015g 2.682g 16836 S 0.3 1.1 33:14.42 java
|
||||
</span><span> 1 root 20 0 33620 2920 1496 S 0.0 0.0 0:03.82 init
|
||||
</span><span> 2 root 20 0 0 0 0 S 0.0 0.0 0:00.02 kthreadd
|
||||
</span><span> 3 root 20 0 0 0 0 S 0.0 0.0 0:05.35 ksoftirqd/0
|
||||
</span><span> 5 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 kworker/0:0H
|
||||
</span><span> 6 root 20 0 0 0 0 S 0.0 0.0 0:06.94 kworker/u256:0
|
||||
</span><span> 8 root 20 0 0 0 0 S 0.0 0.0 2:38.05 rcu_sched
|
||||
</span></code></pre>
|
||||
<p>top命令包括我们之前检查的许多指标。运行它可以很方便地查看是否有任何东西与以前的命令有很大不同，这表明负载是可变的。</p>
|
||||
<p>top命令不太好的地方是，随着时间的推移很难看到指标变化的模式，这在提供滚动输出的vmstat和pidstat之类的工具中可能更清楚一点。如果您没有足够快地暂停输出（Ctrl-S暂停，Ctrl-Q继续），在屏幕输出被top命令清除后，间歇性问题的证据也可能被丢失了。</p>
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
<div class="pagination">
|
||||
<div class="pagination__title">
|
||||
<span class="pagination__title-h">Thanks for reading! Read other posts?</span>
|
||||
<hr />
|
||||
</div>
|
||||
<div class="pagination__buttons">
|
||||
<span class="button previous">
|
||||
<a href="https://blog.dich.bid/learn-linux-for-pc-5/">
|
||||
<span class="button__icon">←</span>
|
||||
<span class="button__text">Linux之旅(五):BIOS-UEFI-MBR-GPT-GRUB</span>
|
||||
</a>
|
||||
</span>
|
||||
|
||||
|
||||
<span class="button next">
|
||||
<a href="https://blog.dich.bid/learn-linux-for-pc-7/">
|
||||
<span class="button__text">Linux之旅(七):系统与终端字体设置</span>
|
||||
<span class="button__icon">→</span>
|
||||
</a>
|
||||
</span>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
</div>
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
<footer class="footer">
|
||||
<div class="footer__inner">
|
||||
<div class="copyright">
|
||||
<span>©
|
||||
2025
|
||||
Dichgrem</span>
|
||||
<span class="copyright-theme">
|
||||
<span class="copyright-theme-sep"> :: CC BY-SA 4.0 :: A friend comes from distant lands</span>
|
||||
</a>
|
||||
</span>
|
||||
</div>
|
||||
</div>
|
||||
</footer>
|
||||
|
||||
</div>
|
||||
</body>
|
||||
</html>
|
||||
|
||||
202
public/learn-linux-for-pc-7/index.html
Normal file
202
public/learn-linux-for-pc-7/index.html
Normal file
@ -0,0 +1,202 @@
|
||||
<!DOCTYPE html>
|
||||
<html lang="en">
|
||||
|
||||
<head>
|
||||
<title>Dich'blog</title>
|
||||
|
||||
<meta http-equiv="content-type" content="text/html; charset=utf-8">
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1">
|
||||
<meta name="robots" content="noodp"/>
|
||||
|
||||
<link rel="stylesheet" href="https://blog.dich.bid/style.css">
|
||||
<link rel="stylesheet" href="https://blog.dich.bid/color/blue.css">
|
||||
|
||||
<link rel="stylesheet" href="https://blog.dich.bid/color/background_dark.css">
|
||||
|
||||
<link rel="stylesheet" href="https://blog.dich.bid/font-hack-subset.css">
|
||||
|
||||
<meta name="description" content="">
|
||||
|
||||
<meta property="og:description" content="">
|
||||
<meta property="og:title" content="Dich'blog">
|
||||
<meta property="og:type" content="article">
|
||||
<meta property="og:url" content="https://blog.dich.bid/learn-linux-for-pc-7/">
|
||||
|
||||
<meta name="twitter:card" content="summary_large_image">
|
||||
<meta name="twitter:description" content="">
|
||||
<meta name="twitter:title" content="Dich'blog">
|
||||
<meta property="twitter:domain" content="blog.dich.bid">
|
||||
<meta property="twitter:url" content="https://blog.dich.bid/learn-linux-for-pc-7/">
|
||||
|
||||
<link rel="alternate" type="application/atom+xml" title="Dich'blog Atom Feed" href="https://blog.dich.bid/atom.xml" />
|
||||
|
||||
|
||||
<link rel="icon" type="image/png" href=/dich.webp />
|
||||
|
||||
<!-- ✅ Added center alignment styles -->
|
||||
<style>
|
||||
.footer {
|
||||
text-align: center;
|
||||
padding: 1rem 0;
|
||||
}
|
||||
|
||||
.footer__inner {
|
||||
display: flex;
|
||||
justify-content: center;
|
||||
flex-direction: column;
|
||||
align-items: center;
|
||||
}
|
||||
|
||||
.copyright {
|
||||
text-align: center;
|
||||
}
|
||||
</style>
|
||||
</head>
|
||||
|
||||
<body class="">
|
||||
<div class="container">
|
||||
|
||||
<header class="header">
|
||||
<div class="header__inner">
|
||||
<div class="header__logo">
|
||||
|
||||
<a href="https://blog.dich.bid" style="text-decoration: none;">
|
||||
<div class="logo">
|
||||
|
||||
Dich'blog
|
||||
|
||||
</div>
|
||||
</a>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
|
||||
|
||||
<nav class="menu">
|
||||
<ul class="menu__inner">
|
||||
<li class="active"><a href="https://blog.dich.bid">blog</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/archive">archive</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/tags">tags</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/weekly">weekly</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/search">search</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/about">about me</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/links">links</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/atom.xml">rss</a></li>
|
||||
|
||||
<li><a href="https://github.com/Dichgrem" target="_blank" rel="noopener noreferrer">github</a></li>
|
||||
</ul>
|
||||
</nav>
|
||||
|
||||
|
||||
|
||||
</header>
|
||||
|
||||
|
||||
<div class="content">
|
||||
|
||||
<div class="post">
|
||||
|
||||
<h1 class="post-title"><a href="https://blog.dich.bid/learn-linux-for-pc-7/">Linux之旅(七):系统与终端字体设置</a></h1>
|
||||
<div class="post-meta-inline">
|
||||
|
||||
<span class="post-date">
|
||||
2023-08-01
|
||||
</span>
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
<span class="post-tags-inline">
|
||||
:: tags:
|
||||
<a class="post-tag" href="https://blog.dich.bid/tags/linux/">#Linux</a></span>
|
||||
|
||||
|
||||
<div class="post-content">
|
||||
<p>前言 一个好看的字体会提高工作效率与审美.Linux 下的字体可以很漂亮,但需要一些设置.</p>
|
||||
<span id="continue-reading"></span>
|
||||
<p>随着 FreeType2 由于专利过期默认开启了高质量的 LCD 优化,以及一批高质量的开源字体的公布,Linux 上的中文字体渲染比过去好了太多.</p>
|
||||
<blockquote>
|
||||
<p>Windows 的字体渲染从技术上来说是相当先进的,问题是在中文字体的选择上实在是一坨...</p>
|
||||
</blockquote>
|
||||
<h2 id="xuan-ze-zi-ti">选择字体</h2>
|
||||
<p>近几年来出现了一大批自由字体（包括工作量极大的 CJK 字体）,使 Linux 下的字体选择一下子丰富了起来.如果愿意花一点时间的话,可以去<a href="https://wiki.archlinux.org/title/Fonts#Font_packages">ArchWiki</a> 上看看,里面涵盖了相当多的自由字体.</p>
|
||||
<h3 id="zhong-duan-zi-ti">终端字体</h3>
|
||||
<p><a href="https://github.com/subframe7536/maple-font?tab=readme-ov-file">Maple Mono</a>,这是一款字形整洁、拥有手写风格的斜体、细粒度配置、内置 Nerd-Font、中英文2:1等宽 的字体.我使用的:</p>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>MapleMono-Bold
|
||||
</span></code></pre>
|
||||
<h3 id="yue-du-qi-zi-ti">阅读器字体</h3>
|
||||
<p><a href="https://github.com/lxgw/LxgwWenKai">霞鹜文楷</a>,一款开源中文字体,基于 FONTWORKS 出品字体 Klee One 衍生.我使用的:</p>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>LXGW WenKai
|
||||
</span></code></pre>
|
||||
<h3 id="liu-lan-qi-zi-ti">浏览器字体</h3>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>拉丁字体
|
||||
</span><span>├── Inter -无衬线,类似于 Roboto 但更适合屏幕显示的字体
|
||||
</span><span>├── Noto Serif -衬线
|
||||
</span><span>└── Sarasa Term SC -等宽,拉丁文字符严格为半宽的字体,中英文混排时较协调
|
||||
</span><span>├── 如果不适应这种较瘦的字体风格, 则可以尝试使用:
|
||||
</span><span>│ ├── Adobe Source Pro
|
||||
</span><span>│ ├── Cascadia Code
|
||||
</span><span>│ └── Fira Code
|
||||
</span><span>中文字体
|
||||
</span><span>├── Noto Sans CJK SC （思源黑体）
|
||||
</span><span>└── Noto Serif CJK SC（思源宋体）
|
||||
</span></code></pre>
|
||||
<hr />
|
||||
<p><strong>Done.</strong></p>
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
<div class="pagination">
|
||||
<div class="pagination__title">
|
||||
<span class="pagination__title-h">Thanks for reading! Read other posts?</span>
|
||||
<hr />
|
||||
</div>
|
||||
<div class="pagination__buttons">
|
||||
<span class="button previous">
|
||||
<a href="https://blog.dich.bid/learn-linux-for-pc-6/">
|
||||
<span class="button__icon">←</span>
|
||||
<span class="button__text">Linux之旅(六):常用命令与性能分析</span>
|
||||
</a>
|
||||
</span>
|
||||
|
||||
|
||||
<span class="button next">
|
||||
<a href="https://blog.dich.bid/awesome-vm-android/">
|
||||
<span class="button__text">综合工程:linux搭建安卓虚拟机</span>
|
||||
<span class="button__icon">→</span>
|
||||
</a>
|
||||
</span>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
</div>
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
<footer class="footer">
|
||||
<div class="footer__inner">
|
||||
<div class="copyright">
|
||||
<span>©
|
||||
2025
|
||||
Dichgrem</span>
|
||||
<span class="copyright-theme">
|
||||
<span class="copyright-theme-sep"> :: CC BY-SA 4.0 :: A friend comes from distant lands</span>
|
||||
</a>
|
||||
</span>
|
||||
</div>
|
||||
</div>
|
||||
</footer>
|
||||
|
||||
</div>
|
||||
</body>
|
||||
</html>
|
||||
|
||||
242
public/links/index.html
Normal file
242
public/links/index.html
Normal file
@ -0,0 +1,242 @@
|
||||
<!DOCTYPE html>
|
||||
<html lang="en">
|
||||
|
||||
<head>
|
||||
<title>Dich'blog</title>
|
||||
|
||||
<meta http-equiv="content-type" content="text/html; charset=utf-8">
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1">
|
||||
<meta name="robots" content="noodp"/>
|
||||
|
||||
<link rel="stylesheet" href="https://blog.dich.bid/style.css">
|
||||
<link rel="stylesheet" href="https://blog.dich.bid/color/blue.css">
|
||||
|
||||
<link rel="stylesheet" href="https://blog.dich.bid/color/background_dark.css">
|
||||
|
||||
<link rel="stylesheet" href="https://blog.dich.bid/font-hack-subset.css">
|
||||
|
||||
<meta name="description" content="用电子罗盘，转赛博核桃，勘电磁风水，寻网络龙脉">
|
||||
|
||||
<meta property="og:description" content="用电子罗盘，转赛博核桃，勘电磁风水，寻网络龙脉">
|
||||
<meta property="og:title" content="Dich'blog">
|
||||
<meta property="og:type" content="website">
|
||||
<meta property="og:url" content="https://blog.dich.bid/links/">
|
||||
|
||||
<meta name="twitter:card" content="summary_large_image">
|
||||
<meta name="twitter:description" content="用电子罗盘，转赛博核桃，勘电磁风水，寻网络龙脉">
|
||||
<meta name="twitter:title" content="Dich'blog">
|
||||
<meta property="twitter:domain" content="blog.dich.bid">
|
||||
<meta property="twitter:url" content="https://blog.dich.bid/links/">
|
||||
|
||||
<link rel="alternate" type="application/atom+xml" title="Dich'blog Atom Feed" href="https://blog.dich.bid/atom.xml" />
|
||||
|
||||
|
||||
<link rel="icon" type="image/png" href=/dich.webp />
|
||||
|
||||
<!-- ✅ Added center alignment styles -->
|
||||
<style>
|
||||
.footer {
|
||||
text-align: center;
|
||||
padding: 1rem 0;
|
||||
}
|
||||
|
||||
.footer__inner {
|
||||
display: flex;
|
||||
justify-content: center;
|
||||
flex-direction: column;
|
||||
align-items: center;
|
||||
}
|
||||
|
||||
.copyright {
|
||||
text-align: center;
|
||||
}
|
||||
</style>
|
||||
</head>
|
||||
|
||||
<body class="">
|
||||
<div class="container">
|
||||
|
||||
<header class="header">
|
||||
<div class="header__inner">
|
||||
<div class="header__logo">
|
||||
|
||||
<a href="https://blog.dich.bid" style="text-decoration: none;">
|
||||
<div class="logo">
|
||||
|
||||
Dich'blog
|
||||
|
||||
</div>
|
||||
</a>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
|
||||
<nav class="menu">
|
||||
<ul class="menu__inner">
|
||||
<li><a href="https://blog.dich.bid">blog</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/archive">archive</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/tags">tags</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/weekly">weekly</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/search">search</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/about">about me</a></li>
|
||||
|
||||
<li class="active"><a href="https://blog.dich.bid/links">links</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/atom.xml">rss</a></li>
|
||||
|
||||
<li><a href="https://github.com/Dichgrem" target="_blank" rel="noopener noreferrer">github</a></li>
|
||||
</ul>
|
||||
</nav>
|
||||
|
||||
|
||||
|
||||
</header>
|
||||
|
||||
|
||||
<div class="content">
|
||||
|
||||
<div class="posts">
|
||||
<div class="post on-list">
|
||||
|
||||
<h1 class="post-title"><a href="https://blog.dich.bid/links/link-1/">Yon Zilch</a></h1>
|
||||
<div class="post-meta-inline">
|
||||
|
||||
<span class="post-date"></span>
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
|
||||
|
||||
<div class="post-content">
|
||||
<p><a href="https://blog.yon.im/">blog.yon.im/</a></p>
|
||||
|
||||
</div>
|
||||
|
||||
</div>
|
||||
|
||||
<div class="post on-list">
|
||||
|
||||
<h1 class="post-title"><a href="https://blog.dich.bid/links/link-2/">diredocks</a></h1>
|
||||
<div class="post-meta-inline">
|
||||
|
||||
<span class="post-date"></span>
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
|
||||
|
||||
<div class="post-content">
|
||||
<p><a href="https://blog.clickfling.top/">blog.clickfling.top</a></p>
|
||||
|
||||
</div>
|
||||
|
||||
</div>
|
||||
|
||||
<div class="post on-list">
|
||||
|
||||
<h1 class="post-title"><a href="https://blog.dich.bid/links/link-3/">Ice Year の位面</a></h1>
|
||||
<div class="post-meta-inline">
|
||||
|
||||
<span class="post-date"></span>
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
|
||||
|
||||
<div class="post-content">
|
||||
<p><a href="https://blog.iceyear.eu.org/">blog.iceyear.eu.org</a></p>
|
||||
|
||||
</div>
|
||||
|
||||
</div>
|
||||
|
||||
<div class="post on-list">
|
||||
|
||||
<h1 class="post-title"><a href="https://blog.dich.bid/links/link-4/">Purkit's Blog</a></h1>
|
||||
<div class="post-meta-inline">
|
||||
|
||||
<span class="post-date"></span>
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
|
||||
|
||||
<div class="post-content">
|
||||
<p><a href="https://www.fovir.fyi/">www.fovir.fyi</a></p>
|
||||
|
||||
</div>
|
||||
|
||||
</div>
|
||||
|
||||
<div class="post on-list">
|
||||
|
||||
<h1 class="post-title"><a href="https://blog.dich.bid/links/link-5/">Milvoid</a></h1>
|
||||
<div class="post-meta-inline">
|
||||
|
||||
<span class="post-date"></span>
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
|
||||
|
||||
<div class="post-content">
|
||||
<p><a href="https://milvoid.com/">milvoid.com/</a></p>
|
||||
|
||||
</div>
|
||||
|
||||
</div>
|
||||
|
||||
<div class="post on-list">
|
||||
|
||||
<h1 class="post-title"><a href="https://blog.dich.bid/links/link-6/">世纪大道 | 春风少年兄</a></h1>
|
||||
<div class="post-meta-inline">
|
||||
|
||||
<span class="post-date"></span>
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
|
||||
|
||||
<div class="post-content">
|
||||
<p><a href="https://blog.0pt.icu/">blog.0pt.icu</a></p>
|
||||
|
||||
</div>
|
||||
|
||||
</div>
|
||||
<div class="pagination">
|
||||
<div class="pagination__buttons"></div>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
<footer class="footer">
|
||||
<div class="footer__inner">
|
||||
<div class="copyright">
|
||||
<span>©
|
||||
2025
|
||||
Dichgrem</span>
|
||||
<span class="copyright-theme">
|
||||
<span class="copyright-theme-sep"> :: CC BY-SA 4.0 :: A friend comes from distant lands</span>
|
||||
</a>
|
||||
</span>
|
||||
</div>
|
||||
</div>
|
||||
</footer>
|
||||
|
||||
</div>
|
||||
</body>
|
||||
</html>
|
||||
|
||||
158
public/links/link-1/index.html
Normal file
158
public/links/link-1/index.html
Normal file
@ -0,0 +1,158 @@
|
||||
<!DOCTYPE html>
|
||||
<html lang="en">
|
||||
|
||||
<head>
|
||||
<title>Dich'blog</title>
|
||||
|
||||
<meta http-equiv="content-type" content="text/html; charset=utf-8">
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1">
|
||||
<meta name="robots" content="noodp"/>
|
||||
|
||||
<link rel="stylesheet" href="https://blog.dich.bid/style.css">
|
||||
<link rel="stylesheet" href="https://blog.dich.bid/color/blue.css">
|
||||
|
||||
<link rel="stylesheet" href="https://blog.dich.bid/color/background_dark.css">
|
||||
|
||||
<link rel="stylesheet" href="https://blog.dich.bid/font-hack-subset.css">
|
||||
|
||||
<meta name="description" content="">
|
||||
|
||||
<meta property="og:description" content="">
|
||||
<meta property="og:title" content="Dich'blog">
|
||||
<meta property="og:type" content="article">
|
||||
<meta property="og:url" content="https://blog.dich.bid/links/link-1/">
|
||||
|
||||
<meta name="twitter:card" content="summary_large_image">
|
||||
<meta name="twitter:description" content="">
|
||||
<meta name="twitter:title" content="Dich'blog">
|
||||
<meta property="twitter:domain" content="blog.dich.bid">
|
||||
<meta property="twitter:url" content="https://blog.dich.bid/links/link-1/">
|
||||
|
||||
<link rel="alternate" type="application/atom+xml" title="Dich'blog Atom Feed" href="https://blog.dich.bid/atom.xml" />
|
||||
|
||||
|
||||
<link rel="icon" type="image/png" href=/dich.webp />
|
||||
|
||||
<!-- ✅ Added center alignment styles -->
|
||||
<style>
|
||||
.footer {
|
||||
text-align: center;
|
||||
padding: 1rem 0;
|
||||
}
|
||||
|
||||
.footer__inner {
|
||||
display: flex;
|
||||
justify-content: center;
|
||||
flex-direction: column;
|
||||
align-items: center;
|
||||
}
|
||||
|
||||
.copyright {
|
||||
text-align: center;
|
||||
}
|
||||
</style>
|
||||
</head>
|
||||
|
||||
<body class="">
|
||||
<div class="container">
|
||||
|
||||
<header class="header">
|
||||
<div class="header__inner">
|
||||
<div class="header__logo">
|
||||
|
||||
<a href="https://blog.dich.bid" style="text-decoration: none;">
|
||||
<div class="logo">
|
||||
|
||||
Dich'blog
|
||||
|
||||
</div>
|
||||
</a>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
|
||||
<nav class="menu">
|
||||
<ul class="menu__inner">
|
||||
<li><a href="https://blog.dich.bid">blog</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/archive">archive</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/tags">tags</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/weekly">weekly</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/search">search</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/about">about me</a></li>
|
||||
|
||||
<li class="active"><a href="https://blog.dich.bid/links">links</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/atom.xml">rss</a></li>
|
||||
|
||||
<li><a href="https://github.com/Dichgrem" target="_blank" rel="noopener noreferrer">github</a></li>
|
||||
</ul>
|
||||
</nav>
|
||||
|
||||
|
||||
|
||||
</header>
|
||||
|
||||
|
||||
<div class="content">
|
||||
|
||||
<div class="post">
|
||||
|
||||
<h1 class="post-title"><a href="https://blog.dich.bid/links/link-1/">Yon Zilch</a></h1>
|
||||
<div class="post-meta-inline">
|
||||
|
||||
<span class="post-date"></span>
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
|
||||
<div class="post-content">
|
||||
<p><a href="https://blog.yon.im/">blog.yon.im/</a></p>
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
<div class="pagination">
|
||||
<div class="pagination__title">
|
||||
<span class="pagination__title-h">Thanks for reading! Read other posts?</span>
|
||||
<hr />
|
||||
</div>
|
||||
<div class="pagination__buttons">
|
||||
<span class="button previous">
|
||||
<a href="https://blog.dich.bid/links/link-2/">
|
||||
<span class="button__icon">←</span>
|
||||
<span class="button__text">diredocks</span>
|
||||
</a>
|
||||
</span>
|
||||
|
||||
</div>
|
||||
</div>
|
||||
|
||||
</div>
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
<footer class="footer">
|
||||
<div class="footer__inner">
|
||||
<div class="copyright">
|
||||
<span>©
|
||||
2025
|
||||
Dichgrem</span>
|
||||
<span class="copyright-theme">
|
||||
<span class="copyright-theme-sep"> :: CC BY-SA 4.0 :: A friend comes from distant lands</span>
|
||||
</a>
|
||||
</span>
|
||||
</div>
|
||||
</div>
|
||||
</footer>
|
||||
|
||||
</div>
|
||||
</body>
|
||||
</html>
|
||||
|
||||
165
public/links/link-2/index.html
Normal file
165
public/links/link-2/index.html
Normal file
@ -0,0 +1,165 @@
|
||||
<!DOCTYPE html>
|
||||
<html lang="en">
|
||||
|
||||
<head>
|
||||
<title>Dich'blog</title>
|
||||
|
||||
<meta http-equiv="content-type" content="text/html; charset=utf-8">
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1">
|
||||
<meta name="robots" content="noodp"/>
|
||||
|
||||
<link rel="stylesheet" href="https://blog.dich.bid/style.css">
|
||||
<link rel="stylesheet" href="https://blog.dich.bid/color/blue.css">
|
||||
|
||||
<link rel="stylesheet" href="https://blog.dich.bid/color/background_dark.css">
|
||||
|
||||
<link rel="stylesheet" href="https://blog.dich.bid/font-hack-subset.css">
|
||||
|
||||
<meta name="description" content="">
|
||||
|
||||
<meta property="og:description" content="">
|
||||
<meta property="og:title" content="Dich'blog">
|
||||
<meta property="og:type" content="article">
|
||||
<meta property="og:url" content="https://blog.dich.bid/links/link-2/">
|
||||
|
||||
<meta name="twitter:card" content="summary_large_image">
|
||||
<meta name="twitter:description" content="">
|
||||
<meta name="twitter:title" content="Dich'blog">
|
||||
<meta property="twitter:domain" content="blog.dich.bid">
|
||||
<meta property="twitter:url" content="https://blog.dich.bid/links/link-2/">
|
||||
|
||||
<link rel="alternate" type="application/atom+xml" title="Dich'blog Atom Feed" href="https://blog.dich.bid/atom.xml" />
|
||||
|
||||
|
||||
<link rel="icon" type="image/png" href=/dich.webp />
|
||||
|
||||
<!-- ✅ Added center alignment styles -->
|
||||
<style>
|
||||
.footer {
|
||||
text-align: center;
|
||||
padding: 1rem 0;
|
||||
}
|
||||
|
||||
.footer__inner {
|
||||
display: flex;
|
||||
justify-content: center;
|
||||
flex-direction: column;
|
||||
align-items: center;
|
||||
}
|
||||
|
||||
.copyright {
|
||||
text-align: center;
|
||||
}
|
||||
</style>
|
||||
</head>
|
||||
|
||||
<body class="">
|
||||
<div class="container">
|
||||
|
||||
<header class="header">
|
||||
<div class="header__inner">
|
||||
<div class="header__logo">
|
||||
|
||||
<a href="https://blog.dich.bid" style="text-decoration: none;">
|
||||
<div class="logo">
|
||||
|
||||
Dich'blog
|
||||
|
||||
</div>
|
||||
</a>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
|
||||
<nav class="menu">
|
||||
<ul class="menu__inner">
|
||||
<li><a href="https://blog.dich.bid">blog</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/archive">archive</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/tags">tags</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/weekly">weekly</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/search">search</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/about">about me</a></li>
|
||||
|
||||
<li class="active"><a href="https://blog.dich.bid/links">links</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/atom.xml">rss</a></li>
|
||||
|
||||
<li><a href="https://github.com/Dichgrem" target="_blank" rel="noopener noreferrer">github</a></li>
|
||||
</ul>
|
||||
</nav>
|
||||
|
||||
|
||||
|
||||
</header>
|
||||
|
||||
|
||||
<div class="content">
|
||||
|
||||
<div class="post">
|
||||
|
||||
<h1 class="post-title"><a href="https://blog.dich.bid/links/link-2/">diredocks</a></h1>
|
||||
<div class="post-meta-inline">
|
||||
|
||||
<span class="post-date"></span>
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
|
||||
<div class="post-content">
|
||||
<p><a href="https://blog.clickfling.top/">blog.clickfling.top</a></p>
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
<div class="pagination">
|
||||
<div class="pagination__title">
|
||||
<span class="pagination__title-h">Thanks for reading! Read other posts?</span>
|
||||
<hr />
|
||||
</div>
|
||||
<div class="pagination__buttons">
|
||||
<span class="button previous">
|
||||
<a href="https://blog.dich.bid/links/link-3/">
|
||||
<span class="button__icon">←</span>
|
||||
<span class="button__text">Ice Year の位面</span>
|
||||
</a>
|
||||
</span>
|
||||
|
||||
|
||||
<span class="button next">
|
||||
<a href="https://blog.dich.bid/links/link-1/">
|
||||
<span class="button__text">Yon Zilch</span>
|
||||
<span class="button__icon">→</span>
|
||||
</a>
|
||||
</span>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
</div>
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
<footer class="footer">
|
||||
<div class="footer__inner">
|
||||
<div class="copyright">
|
||||
<span>©
|
||||
2025
|
||||
Dichgrem</span>
|
||||
<span class="copyright-theme">
|
||||
<span class="copyright-theme-sep"> :: CC BY-SA 4.0 :: A friend comes from distant lands</span>
|
||||
</a>
|
||||
</span>
|
||||
</div>
|
||||
</div>
|
||||
</footer>
|
||||
|
||||
</div>
|
||||
</body>
|
||||
</html>
|
||||
|
||||
165
public/links/link-3/index.html
Normal file
165
public/links/link-3/index.html
Normal file
@ -0,0 +1,165 @@
|
||||
<!DOCTYPE html>
|
||||
<html lang="en">
|
||||
|
||||
<head>
|
||||
<title>Dich'blog</title>
|
||||
|
||||
<meta http-equiv="content-type" content="text/html; charset=utf-8">
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1">
|
||||
<meta name="robots" content="noodp"/>
|
||||
|
||||
<link rel="stylesheet" href="https://blog.dich.bid/style.css">
|
||||
<link rel="stylesheet" href="https://blog.dich.bid/color/blue.css">
|
||||
|
||||
<link rel="stylesheet" href="https://blog.dich.bid/color/background_dark.css">
|
||||
|
||||
<link rel="stylesheet" href="https://blog.dich.bid/font-hack-subset.css">
|
||||
|
||||
<meta name="description" content="">
|
||||
|
||||
<meta property="og:description" content="">
|
||||
<meta property="og:title" content="Dich'blog">
|
||||
<meta property="og:type" content="article">
|
||||
<meta property="og:url" content="https://blog.dich.bid/links/link-3/">
|
||||
|
||||
<meta name="twitter:card" content="summary_large_image">
|
||||
<meta name="twitter:description" content="">
|
||||
<meta name="twitter:title" content="Dich'blog">
|
||||
<meta property="twitter:domain" content="blog.dich.bid">
|
||||
<meta property="twitter:url" content="https://blog.dich.bid/links/link-3/">
|
||||
|
||||
<link rel="alternate" type="application/atom+xml" title="Dich'blog Atom Feed" href="https://blog.dich.bid/atom.xml" />
|
||||
|
||||
|
||||
<link rel="icon" type="image/png" href=/dich.webp />
|
||||
|
||||
<!-- ✅ Added center alignment styles -->
|
||||
<style>
|
||||
.footer {
|
||||
text-align: center;
|
||||
padding: 1rem 0;
|
||||
}
|
||||
|
||||
.footer__inner {
|
||||
display: flex;
|
||||
justify-content: center;
|
||||
flex-direction: column;
|
||||
align-items: center;
|
||||
}
|
||||
|
||||
.copyright {
|
||||
text-align: center;
|
||||
}
|
||||
</style>
|
||||
</head>
|
||||
|
||||
<body class="">
|
||||
<div class="container">
|
||||
|
||||
<header class="header">
|
||||
<div class="header__inner">
|
||||
<div class="header__logo">
|
||||
|
||||
<a href="https://blog.dich.bid" style="text-decoration: none;">
|
||||
<div class="logo">
|
||||
|
||||
Dich'blog
|
||||
|
||||
</div>
|
||||
</a>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
|
||||
<nav class="menu">
|
||||
<ul class="menu__inner">
|
||||
<li><a href="https://blog.dich.bid">blog</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/archive">archive</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/tags">tags</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/weekly">weekly</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/search">search</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/about">about me</a></li>
|
||||
|
||||
<li class="active"><a href="https://blog.dich.bid/links">links</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/atom.xml">rss</a></li>
|
||||
|
||||
<li><a href="https://github.com/Dichgrem" target="_blank" rel="noopener noreferrer">github</a></li>
|
||||
</ul>
|
||||
</nav>
|
||||
|
||||
|
||||
|
||||
</header>
|
||||
|
||||
|
||||
<div class="content">
|
||||
|
||||
<div class="post">
|
||||
|
||||
<h1 class="post-title"><a href="https://blog.dich.bid/links/link-3/">Ice Year の位面</a></h1>
|
||||
<div class="post-meta-inline">
|
||||
|
||||
<span class="post-date"></span>
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
|
||||
<div class="post-content">
|
||||
<p><a href="https://blog.iceyear.eu.org/">blog.iceyear.eu.org</a></p>
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
<div class="pagination">
|
||||
<div class="pagination__title">
|
||||
<span class="pagination__title-h">Thanks for reading! Read other posts?</span>
|
||||
<hr />
|
||||
</div>
|
||||
<div class="pagination__buttons">
|
||||
<span class="button previous">
|
||||
<a href="https://blog.dich.bid/links/link-4/">
|
||||
<span class="button__icon">←</span>
|
||||
<span class="button__text">Purkit's Blog</span>
|
||||
</a>
|
||||
</span>
|
||||
|
||||
|
||||
<span class="button next">
|
||||
<a href="https://blog.dich.bid/links/link-2/">
|
||||
<span class="button__text">diredocks</span>
|
||||
<span class="button__icon">→</span>
|
||||
</a>
|
||||
</span>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
</div>
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
<footer class="footer">
|
||||
<div class="footer__inner">
|
||||
<div class="copyright">
|
||||
<span>©
|
||||
2025
|
||||
Dichgrem</span>
|
||||
<span class="copyright-theme">
|
||||
<span class="copyright-theme-sep"> :: CC BY-SA 4.0 :: A friend comes from distant lands</span>
|
||||
</a>
|
||||
</span>
|
||||
</div>
|
||||
</div>
|
||||
</footer>
|
||||
|
||||
</div>
|
||||
</body>
|
||||
</html>
|
||||
|
||||
165
public/links/link-4/index.html
Normal file
165
public/links/link-4/index.html
Normal file
@ -0,0 +1,165 @@
|
||||
<!DOCTYPE html>
|
||||
<html lang="en">
|
||||
|
||||
<head>
|
||||
<title>Dich'blog</title>
|
||||
|
||||
<meta http-equiv="content-type" content="text/html; charset=utf-8">
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1">
|
||||
<meta name="robots" content="noodp"/>
|
||||
|
||||
<link rel="stylesheet" href="https://blog.dich.bid/style.css">
|
||||
<link rel="stylesheet" href="https://blog.dich.bid/color/blue.css">
|
||||
|
||||
<link rel="stylesheet" href="https://blog.dich.bid/color/background_dark.css">
|
||||
|
||||
<link rel="stylesheet" href="https://blog.dich.bid/font-hack-subset.css">
|
||||
|
||||
<meta name="description" content="">
|
||||
|
||||
<meta property="og:description" content="">
|
||||
<meta property="og:title" content="Dich'blog">
|
||||
<meta property="og:type" content="article">
|
||||
<meta property="og:url" content="https://blog.dich.bid/links/link-4/">
|
||||
|
||||
<meta name="twitter:card" content="summary_large_image">
|
||||
<meta name="twitter:description" content="">
|
||||
<meta name="twitter:title" content="Dich'blog">
|
||||
<meta property="twitter:domain" content="blog.dich.bid">
|
||||
<meta property="twitter:url" content="https://blog.dich.bid/links/link-4/">
|
||||
|
||||
<link rel="alternate" type="application/atom+xml" title="Dich'blog Atom Feed" href="https://blog.dich.bid/atom.xml" />
|
||||
|
||||
|
||||
<link rel="icon" type="image/png" href=/dich.webp />
|
||||
|
||||
<!-- ✅ Added center alignment styles -->
|
||||
<style>
|
||||
.footer {
|
||||
text-align: center;
|
||||
padding: 1rem 0;
|
||||
}
|
||||
|
||||
.footer__inner {
|
||||
display: flex;
|
||||
justify-content: center;
|
||||
flex-direction: column;
|
||||
align-items: center;
|
||||
}
|
||||
|
||||
.copyright {
|
||||
text-align: center;
|
||||
}
|
||||
</style>
|
||||
</head>
|
||||
|
||||
<body class="">
|
||||
<div class="container">
|
||||
|
||||
<header class="header">
|
||||
<div class="header__inner">
|
||||
<div class="header__logo">
|
||||
|
||||
<a href="https://blog.dich.bid" style="text-decoration: none;">
|
||||
<div class="logo">
|
||||
|
||||
Dich'blog
|
||||
|
||||
</div>
|
||||
</a>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
|
||||
<nav class="menu">
|
||||
<ul class="menu__inner">
|
||||
<li><a href="https://blog.dich.bid">blog</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/archive">archive</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/tags">tags</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/weekly">weekly</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/search">search</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/about">about me</a></li>
|
||||
|
||||
<li class="active"><a href="https://blog.dich.bid/links">links</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/atom.xml">rss</a></li>
|
||||
|
||||
<li><a href="https://github.com/Dichgrem" target="_blank" rel="noopener noreferrer">github</a></li>
|
||||
</ul>
|
||||
</nav>
|
||||
|
||||
|
||||
|
||||
</header>
|
||||
|
||||
|
||||
<div class="content">
|
||||
|
||||
<div class="post">
|
||||
|
||||
<h1 class="post-title"><a href="https://blog.dich.bid/links/link-4/">Purkit's Blog</a></h1>
|
||||
<div class="post-meta-inline">
|
||||
|
||||
<span class="post-date"></span>
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
|
||||
<div class="post-content">
|
||||
<p><a href="https://www.fovir.fyi/">www.fovir.fyi</a></p>
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
<div class="pagination">
|
||||
<div class="pagination__title">
|
||||
<span class="pagination__title-h">Thanks for reading! Read other posts?</span>
|
||||
<hr />
|
||||
</div>
|
||||
<div class="pagination__buttons">
|
||||
<span class="button previous">
|
||||
<a href="https://blog.dich.bid/links/link-5/">
|
||||
<span class="button__icon">←</span>
|
||||
<span class="button__text">Milvoid</span>
|
||||
</a>
|
||||
</span>
|
||||
|
||||
|
||||
<span class="button next">
|
||||
<a href="https://blog.dich.bid/links/link-3/">
|
||||
<span class="button__text">Ice Year の位面</span>
|
||||
<span class="button__icon">→</span>
|
||||
</a>
|
||||
</span>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
</div>
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
<footer class="footer">
|
||||
<div class="footer__inner">
|
||||
<div class="copyright">
|
||||
<span>©
|
||||
2025
|
||||
Dichgrem</span>
|
||||
<span class="copyright-theme">
|
||||
<span class="copyright-theme-sep"> :: CC BY-SA 4.0 :: A friend comes from distant lands</span>
|
||||
</a>
|
||||
</span>
|
||||
</div>
|
||||
</div>
|
||||
</footer>
|
||||
|
||||
</div>
|
||||
</body>
|
||||
</html>
|
||||
|
||||
165
public/links/link-5/index.html
Normal file
165
public/links/link-5/index.html
Normal file
@ -0,0 +1,165 @@
|
||||
<!DOCTYPE html>
|
||||
<html lang="en">
|
||||
|
||||
<head>
|
||||
<title>Dich'blog</title>
|
||||
|
||||
<meta http-equiv="content-type" content="text/html; charset=utf-8">
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1">
|
||||
<meta name="robots" content="noodp"/>
|
||||
|
||||
<link rel="stylesheet" href="https://blog.dich.bid/style.css">
|
||||
<link rel="stylesheet" href="https://blog.dich.bid/color/blue.css">
|
||||
|
||||
<link rel="stylesheet" href="https://blog.dich.bid/color/background_dark.css">
|
||||
|
||||
<link rel="stylesheet" href="https://blog.dich.bid/font-hack-subset.css">
|
||||
|
||||
<meta name="description" content="">
|
||||
|
||||
<meta property="og:description" content="">
|
||||
<meta property="og:title" content="Dich'blog">
|
||||
<meta property="og:type" content="article">
|
||||
<meta property="og:url" content="https://blog.dich.bid/links/link-5/">
|
||||
|
||||
<meta name="twitter:card" content="summary_large_image">
|
||||
<meta name="twitter:description" content="">
|
||||
<meta name="twitter:title" content="Dich'blog">
|
||||
<meta property="twitter:domain" content="blog.dich.bid">
|
||||
<meta property="twitter:url" content="https://blog.dich.bid/links/link-5/">
|
||||
|
||||
<link rel="alternate" type="application/atom+xml" title="Dich'blog Atom Feed" href="https://blog.dich.bid/atom.xml" />
|
||||
|
||||
|
||||
<link rel="icon" type="image/png" href=/dich.webp />
|
||||
|
||||
<!-- ✅ Added center alignment styles -->
|
||||
<style>
|
||||
.footer {
|
||||
text-align: center;
|
||||
padding: 1rem 0;
|
||||
}
|
||||
|
||||
.footer__inner {
|
||||
display: flex;
|
||||
justify-content: center;
|
||||
flex-direction: column;
|
||||
align-items: center;
|
||||
}
|
||||
|
||||
.copyright {
|
||||
text-align: center;
|
||||
}
|
||||
</style>
|
||||
</head>
|
||||
|
||||
<body class="">
|
||||
<div class="container">
|
||||
|
||||
<header class="header">
|
||||
<div class="header__inner">
|
||||
<div class="header__logo">
|
||||
|
||||
<a href="https://blog.dich.bid" style="text-decoration: none;">
|
||||
<div class="logo">
|
||||
|
||||
Dich'blog
|
||||
|
||||
</div>
|
||||
</a>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
|
||||
<nav class="menu">
|
||||
<ul class="menu__inner">
|
||||
<li><a href="https://blog.dich.bid">blog</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/archive">archive</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/tags">tags</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/weekly">weekly</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/search">search</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/about">about me</a></li>
|
||||
|
||||
<li class="active"><a href="https://blog.dich.bid/links">links</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/atom.xml">rss</a></li>
|
||||
|
||||
<li><a href="https://github.com/Dichgrem" target="_blank" rel="noopener noreferrer">github</a></li>
|
||||
</ul>
|
||||
</nav>
|
||||
|
||||
|
||||
|
||||
</header>
|
||||
|
||||
|
||||
<div class="content">
|
||||
|
||||
<div class="post">
|
||||
|
||||
<h1 class="post-title"><a href="https://blog.dich.bid/links/link-5/">Milvoid</a></h1>
|
||||
<div class="post-meta-inline">
|
||||
|
||||
<span class="post-date"></span>
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
|
||||
<div class="post-content">
|
||||
<p><a href="https://milvoid.com/">milvoid.com/</a></p>
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
<div class="pagination">
|
||||
<div class="pagination__title">
|
||||
<span class="pagination__title-h">Thanks for reading! Read other posts?</span>
|
||||
<hr />
|
||||
</div>
|
||||
<div class="pagination__buttons">
|
||||
<span class="button previous">
|
||||
<a href="https://blog.dich.bid/links/link-6/">
|
||||
<span class="button__icon">←</span>
|
||||
<span class="button__text">世纪大道 | 春风少年兄</span>
|
||||
</a>
|
||||
</span>
|
||||
|
||||
|
||||
<span class="button next">
|
||||
<a href="https://blog.dich.bid/links/link-4/">
|
||||
<span class="button__text">Purkit's Blog</span>
|
||||
<span class="button__icon">→</span>
|
||||
</a>
|
||||
</span>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
</div>
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
<footer class="footer">
|
||||
<div class="footer__inner">
|
||||
<div class="copyright">
|
||||
<span>©
|
||||
2025
|
||||
Dichgrem</span>
|
||||
<span class="copyright-theme">
|
||||
<span class="copyright-theme-sep"> :: CC BY-SA 4.0 :: A friend comes from distant lands</span>
|
||||
</a>
|
||||
</span>
|
||||
</div>
|
||||
</div>
|
||||
</footer>
|
||||
|
||||
</div>
|
||||
</body>
|
||||
</html>
|
||||
|
||||
158
public/links/link-6/index.html
Normal file
158
public/links/link-6/index.html
Normal file
@ -0,0 +1,158 @@
|
||||
<!DOCTYPE html>
|
||||
<html lang="en">
|
||||
|
||||
<head>
|
||||
<title>Dich'blog</title>
|
||||
|
||||
<meta http-equiv="content-type" content="text/html; charset=utf-8">
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1">
|
||||
<meta name="robots" content="noodp"/>
|
||||
|
||||
<link rel="stylesheet" href="https://blog.dich.bid/style.css">
|
||||
<link rel="stylesheet" href="https://blog.dich.bid/color/blue.css">
|
||||
|
||||
<link rel="stylesheet" href="https://blog.dich.bid/color/background_dark.css">
|
||||
|
||||
<link rel="stylesheet" href="https://blog.dich.bid/font-hack-subset.css">
|
||||
|
||||
<meta name="description" content="">
|
||||
|
||||
<meta property="og:description" content="">
|
||||
<meta property="og:title" content="Dich'blog">
|
||||
<meta property="og:type" content="article">
|
||||
<meta property="og:url" content="https://blog.dich.bid/links/link-6/">
|
||||
|
||||
<meta name="twitter:card" content="summary_large_image">
|
||||
<meta name="twitter:description" content="">
|
||||
<meta name="twitter:title" content="Dich'blog">
|
||||
<meta property="twitter:domain" content="blog.dich.bid">
|
||||
<meta property="twitter:url" content="https://blog.dich.bid/links/link-6/">
|
||||
|
||||
<link rel="alternate" type="application/atom+xml" title="Dich'blog Atom Feed" href="https://blog.dich.bid/atom.xml" />
|
||||
|
||||
|
||||
<link rel="icon" type="image/png" href=/dich.webp />
|
||||
|
||||
<!-- ✅ Added center alignment styles -->
|
||||
<style>
|
||||
.footer {
|
||||
text-align: center;
|
||||
padding: 1rem 0;
|
||||
}
|
||||
|
||||
.footer__inner {
|
||||
display: flex;
|
||||
justify-content: center;
|
||||
flex-direction: column;
|
||||
align-items: center;
|
||||
}
|
||||
|
||||
.copyright {
|
||||
text-align: center;
|
||||
}
|
||||
</style>
|
||||
</head>
|
||||
|
||||
<body class="">
|
||||
<div class="container">
|
||||
|
||||
<header class="header">
|
||||
<div class="header__inner">
|
||||
<div class="header__logo">
|
||||
|
||||
<a href="https://blog.dich.bid" style="text-decoration: none;">
|
||||
<div class="logo">
|
||||
|
||||
Dich'blog
|
||||
|
||||
</div>
|
||||
</a>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
|
||||
<nav class="menu">
|
||||
<ul class="menu__inner">
|
||||
<li><a href="https://blog.dich.bid">blog</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/archive">archive</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/tags">tags</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/weekly">weekly</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/search">search</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/about">about me</a></li>
|
||||
|
||||
<li class="active"><a href="https://blog.dich.bid/links">links</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/atom.xml">rss</a></li>
|
||||
|
||||
<li><a href="https://github.com/Dichgrem" target="_blank" rel="noopener noreferrer">github</a></li>
|
||||
</ul>
|
||||
</nav>
|
||||
|
||||
|
||||
|
||||
</header>
|
||||
|
||||
|
||||
<div class="content">
|
||||
|
||||
<div class="post">
|
||||
|
||||
<h1 class="post-title"><a href="https://blog.dich.bid/links/link-6/">世纪大道 | 春风少年兄</a></h1>
|
||||
<div class="post-meta-inline">
|
||||
|
||||
<span class="post-date"></span>
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
|
||||
<div class="post-content">
|
||||
<p><a href="https://blog.0pt.icu/">blog.0pt.icu</a></p>
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
<div class="pagination">
|
||||
<div class="pagination__title">
|
||||
<span class="pagination__title-h">Thanks for reading! Read other posts?</span>
|
||||
<hr />
|
||||
</div>
|
||||
<div class="pagination__buttons">
|
||||
|
||||
<span class="button next">
|
||||
<a href="https://blog.dich.bid/links/link-5/">
|
||||
<span class="button__text">Milvoid</span>
|
||||
<span class="button__icon">→</span>
|
||||
</a>
|
||||
</span>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
</div>
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
<footer class="footer">
|
||||
<div class="footer__inner">
|
||||
<div class="copyright">
|
||||
<span>©
|
||||
2025
|
||||
Dichgrem</span>
|
||||
<span class="copyright-theme">
|
||||
<span class="copyright-theme-sep"> :: CC BY-SA 4.0 :: A friend comes from distant lands</span>
|
||||
</a>
|
||||
</span>
|
||||
</div>
|
||||
</div>
|
||||
</footer>
|
||||
|
||||
</div>
|
||||
</body>
|
||||
</html>
|
||||
|
||||
1
public/logo.css
Normal file
1
public/logo.css
Normal file
@ -0,0 +1 @@
|
||||
.logo{display:flex;align-items:center;text-decoration:none;background:var(--accent);color:#000;padding:5px 10px}
|
||||
1
public/main.css
Normal file
1
public/main.css
Normal file
@ -0,0 +1 @@
|
||||
html{box-sizing:border-box}*,*:before,*:after{box-sizing:inherit}body{margin:0;padding:0;font-family:Hack,DejaVu Sans Mono,Monaco,Consolas,Ubuntu Mono,monospace;font-size:1rem;line-height:1.54;background-color:var(--background);color:var(--color);text-rendering:optimizeLegibility;-webkit-font-smoothing:antialiased;-webkit-overflow-scrolling:touch;-webkit-text-size-adjust:100%}@media (max-width: 683px){body{font-size:1rem}}h1,h2,h3,h4,h5,h6{display:flex;align-items:center;font-weight:bold;line-height:1.3}h1{font-size:1.4rem}h2{font-size:1.3rem}h3{font-size:1.2rem}h4,h5,h6{font-size:1.15rem}a{color:inherit}img{display:block;max-width:100%}img.left{margin-right:auto}img.center{margin-left:auto;margin-right:auto}img.right{margin-left:auto}p{margin-bottom:20px}figure{display:table;max-width:100%;margin:25px 0}figure.left,figure img{margin-right:auto}figure.center,figure img{margin-left:auto;margin-right:auto}figure.right,figure img{margin-left:auto}figure figcaption{font-size:14px;padding:5px 10px;margin-top:5px;background:var(--accent);color:var(--background)}figure figcaption.left{text-align:left}figure figcaption.center{text-align:center}figure figcaption.right{text-align:right}code{font-family:Hack,DejaVu Sans Mono,Monaco,Consolas,Ubuntu Mono,monospace;font-feature-settings:normal;background:var(--accent-alpha-20);padding:1px 6px;margin:0 2px;font-size:.95rem}pre{font-family:Hack,DejaVu Sans Mono,Monaco,Consolas,Ubuntu Mono,monospace;padding:20px;font-size:.95rem;overflow:auto;border-top:1px solid rgba(255,255,255,.1);border-bottom:1px solid rgba(255,255,255,.1)}@media (max-width: 683px){pre{white-space:pre-wrap;word-wrap:break-word}}pre code{padding:0;margin:0;background:none}blockquote{border-top:1px solid var(--accent);border-bottom:1px solid var(--accent);margin:40px 0;padding:25px}@media (max-width: 683px){blockquote{padding-right:0}}blockquote:before{content:"”";font-family:Georgia,serif;font-size:3.875rem;position:absolute;left:-40px;top:-20px}blockquote p:first-of-type{margin-top:0}blockquote p:last-of-type{margin-bottom:0}blockquote p{position:relative}blockquote p:before{content:">";display:block;position:absolute;left:-25px;color:var(--accent)}table{table-layout:fixed;border-collapse:collapse;width:100%;margin:40px 0}table,th,td{border:1px dashed var(--accent);padding:10px}th{color:var(--accent)}ul,ol{margin-left:30px;padding:0}ul li,ol li{position:relative}@media (max-width: 683px){ul,ol{margin-left:20px}}ol ol{list-style-type:lower-alpha}.container{display:flex;flex-direction:column;padding:40px;max-width:864px;min-height:100vh;margin:0 auto}@media (max-width: 683px){.container{padding:20px}}.content{display:flex}hr{width:100%;border:none;background:var(--border-color);height:1px}.hidden{display:none}
|
||||
395
public/network-cdn/index.html
Normal file
395
public/network-cdn/index.html
Normal file
@ -0,0 +1,395 @@
|
||||
<!DOCTYPE html>
|
||||
<html lang="en">
|
||||
|
||||
<head>
|
||||
<title>Dich'blog</title>
|
||||
|
||||
<meta http-equiv="content-type" content="text/html; charset=utf-8">
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1">
|
||||
<meta name="robots" content="noodp"/>
|
||||
|
||||
<link rel="stylesheet" href="https://blog.dich.bid/style.css">
|
||||
<link rel="stylesheet" href="https://blog.dich.bid/color/blue.css">
|
||||
|
||||
<link rel="stylesheet" href="https://blog.dich.bid/color/background_dark.css">
|
||||
|
||||
<link rel="stylesheet" href="https://blog.dich.bid/font-hack-subset.css">
|
||||
|
||||
<meta name="description" content="">
|
||||
|
||||
<meta property="og:description" content="">
|
||||
<meta property="og:title" content="Dich'blog">
|
||||
<meta property="og:type" content="article">
|
||||
<meta property="og:url" content="https://blog.dich.bid/network-cdn/">
|
||||
|
||||
<meta name="twitter:card" content="summary_large_image">
|
||||
<meta name="twitter:description" content="">
|
||||
<meta name="twitter:title" content="Dich'blog">
|
||||
<meta property="twitter:domain" content="blog.dich.bid">
|
||||
<meta property="twitter:url" content="https://blog.dich.bid/network-cdn/">
|
||||
|
||||
<link rel="alternate" type="application/atom+xml" title="Dich'blog Atom Feed" href="https://blog.dich.bid/atom.xml" />
|
||||
|
||||
|
||||
<link rel="icon" type="image/png" href=/dich.webp />
|
||||
|
||||
<!-- ✅ Added center alignment styles -->
|
||||
<style>
|
||||
.footer {
|
||||
text-align: center;
|
||||
padding: 1rem 0;
|
||||
}
|
||||
|
||||
.footer__inner {
|
||||
display: flex;
|
||||
justify-content: center;
|
||||
flex-direction: column;
|
||||
align-items: center;
|
||||
}
|
||||
|
||||
.copyright {
|
||||
text-align: center;
|
||||
}
|
||||
</style>
|
||||
</head>
|
||||
|
||||
<body class="">
|
||||
<div class="container">
|
||||
|
||||
<header class="header">
|
||||
<div class="header__inner">
|
||||
<div class="header__logo">
|
||||
|
||||
<a href="https://blog.dich.bid" style="text-decoration: none;">
|
||||
<div class="logo">
|
||||
|
||||
Dich'blog
|
||||
|
||||
</div>
|
||||
</a>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
|
||||
|
||||
<nav class="menu">
|
||||
<ul class="menu__inner">
|
||||
<li class="active"><a href="https://blog.dich.bid">blog</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/archive">archive</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/tags">tags</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/weekly">weekly</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/search">search</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/about">about me</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/links">links</a></li>
|
||||
|
||||
<li><a href="https://blog.dich.bid/atom.xml">rss</a></li>
|
||||
|
||||
<li><a href="https://github.com/Dichgrem" target="_blank" rel="noopener noreferrer">github</a></li>
|
||||
</ul>
|
||||
</nav>
|
||||
|
||||
|
||||
|
||||
</header>
|
||||
|
||||
|
||||
<div class="content">
|
||||
|
||||
<div class="post">
|
||||
|
||||
<h1 class="post-title"><a href="https://blog.dich.bid/network-cdn/">Network的艺术:CDN技术与应用</a></h1>
|
||||
<div class="post-meta-inline">
|
||||
|
||||
<span class="post-date">
|
||||
2024-02-16
|
||||
</span>
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
<span class="post-tags-inline">
|
||||
:: tags:
|
||||
<a class="post-tag" href="https://blog.dich.bid/tags/wang-luo-yi-shu/">#网络艺术</a></span>
|
||||
|
||||
|
||||
<div class="post-content">
|
||||
<p>前言 内容分发网络（CDN）是一组分布在不同地理位置的服务器网络,使用户能够就近获取内容，从而降低延迟并缓解源站压力.</p>
|
||||
<span id="continue-reading"></span><h2 id="shen-me-shi-cdn">什么是CDN？</h2>
|
||||
<p>内容分发网络（CDN）是一组分布在不同地理位置的服务器网络，旨在将网站或应用的静态资源（如HTML、图片、视频等）缓存到距离用户更近的节点，以缩短传输路径、降低带宽成本并提高访问速度.CDN通过“缓存”机制，在全球多个数据中心临时存储内容副本，用户发起请求时无需回源到主服务器，就能从最近的缓存节点获取数据，从而显著改善页面加载时间和整体用户体验.相比传统的单点源站访问，CDN在用户和源站之间增加了分层缓存，通过负载均衡技术和智能路由，将访问请求定向到最优节点，既减轻了源站压力，又提升了网络抗拥塞能力和可用性.</p>
|
||||
<p>在现代互联网中，内容分发网络（CDN）和域名系统（DNS）相互配合，共同提升了网页和多媒体内容的访问速度与可靠性.CDN通过在全球分布的缓存节点上存储静态资源，使用户能够就近获取内容，从而降低延迟并缓解源站压力.而DNS则负责将用户的域名请求导向适当的CDN节点，通过CNAME重定向、全局负载均衡（GSLB）、Anycast及EDNS扩展等技术，实现智能化的流量调度和最优路径选择.</p>
|
||||
<p><strong>CDN的核心功能与优势</strong></p>
|
||||
<ul>
|
||||
<li>
|
||||
<p>加速访问：将内容存储于距离用户更近的节点，减少传输延迟，常见于视频点播、大文件下载等场景.</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>减轻源站压力：缓存请求可直接由CDN节点响应，降低源站带宽和计算资源消耗，有助于应对突发流量和DDoS攻击.</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>高可用与弹性扩展：全球分布的节点架构，使内容分发具备冗余能力，单点故障不会影响整体服务，且可动态扩容以应对业务增长.</p>
|
||||
</li>
|
||||
</ul>
|
||||
<h2 id="cdnyu-dnsde-jie-he-fang-shi">CDN与DNS的结合方式</h2>
|
||||
<ol>
|
||||
<li><strong>通过CNAME实现权威DNS指向CDN</strong></li>
|
||||
</ol>
|
||||
<p>当用户在浏览器中输入域名发起请求时，首先触发本地DNS解析过程；如果该域名已开通CDN服务，其DNS解析记录通常配置为一条CNAME（别名）记录，指向CDN运营商提供的专用域名；本地DNS服务器再将解析权交给CDN的权威DNS服务器，从而实现对CDN网络的接入.</p>
|
||||
<p>CDN的权威DNS服务器根据用户请求的域名，返回一个“全局负载均衡设备”的IP地址，该IP并非最终缓存节点，而是GSLB层用于智能调度的入口地址；浏览器接收到该IP后，向GSLB层发起实际内容请求.</p>
|
||||
<ol start="2">
|
||||
<li><strong>全局负载均衡（GSLB）与智能DNS</strong></li>
|
||||
</ol>
|
||||
<p>GSLB（Global Server Load Balancing）是CDN架构中最核心的部分，负责根据多种因素（用户IP地理位置、节点健康状态、节点负载情况等）动态选择最优区域负载均衡节点或缓存服务器，向用户提供最低延迟和最佳性能的服务.</p>
|
||||
<p>这一过程通常也基于DNS解析完成：当GSLB层接到DNS查询请求时，智能DNS服务器会返回针对该用户最优的缓存节点IP，从而实现“DNS级”的流量调度和负载均衡.</p>
|
||||
<ol start="3">
|
||||
<li><strong>Anycast与EDNS扩展</strong></li>
|
||||
</ol>
|
||||
<p>Anycast路由：部分CDN运营商在全球部署相同IP的多个节点，利用BGP Anycast技术使得用户请求自动路由到网络拓扑上“最近”的节点，增强访问的网络路径效率与容灾能力.</p>
|
||||
<p>EDNS Client Subnet（EDNS-CS）：传统DNS仅看到发起查询的递归DNS服务器IP，难以准确判断终端用户位置；EDNS-CS协议在DNS请求中携带部分客户端IP前缀，使权威DNS能更细粒度地进行地理定位与节点选取，大幅提升了基于DNS的智能调度精度.</p>
|
||||
<h2 id="wei-shen-me-jia-liao-cdnzhi-hou-wang-zhan-de-zi-qian-ming-zheng-shu-ye-bei-xin-ren-liao">为什么加了CDN之后网站的自签名证书也被信任了？</h2>
|
||||
<blockquote>
|
||||
<p>在启用 CDN 后，终端用户看到的并不是您在源站（origin）上配置的自签名证书，而是 CDN 边缘节点（edge）所出示的、由受信任 CA 签发的“边缘证书”.也就是说，浏览器与 CDN 边缘之间的 TLS 握手完全独立于您源站和自签名证书的存在，源站的自签名证书仅用于 CDN 与源站之间的“后端”加密连接，不会暴露给最终用户浏览器.</p>
|
||||
</blockquote>
|
||||
<p><strong>CDN 模式下的 TLS 终止</strong></p>
|
||||
<ul>
|
||||
<li>
|
||||
<p><strong>DNS/CNAME 指向</strong>
|
||||
当您为域名启用 CDN 后，通常会在 DNS 中将该域名的 CNAME 记录指向 CDN 运营商提供的专用域名，本地递归 DNS 随后会将解析权交给 CDN 供应商的权威 DNS，实现请求切入 CDN 网络.</p>
|
||||
</li>
|
||||
<li>
|
||||
<p><strong>边缘节点出示证书</strong>
|
||||
用户发起 HTTPS 请求时，浏览器直接与就近的 CDN 边缘节点建立 TLS 连接，边缘节点会出示由受信任 CA（如 Let's Encrypt、DigiCert 等）签发的“边缘证书”，而非您源站的自签名证书.</p>
|
||||
</li>
|
||||
<li>
|
||||
<p><strong>源站连接加密</strong>
|
||||
在边缘节点接收并缓存用户流量后，CDN 再以 HTTPS（或 HTTP，根据配置）向源站发起请求.此时，您可以在源站使用自签名证书（或 Cloudflare Origin CA 自签名证书），仅保证 CDN 与源站之间的加密传输，且该证书对终端用户浏览器不可见.</p>
|
||||
</li>
|
||||
</ul>
|
||||
<h3 id="ssl-tls-jia-mi-mo-shi-dui-zi-qian-ming-zheng-shu-de-ying-xiang">SSL/TLS 加密模式对自签名证书的影响</h3>
|
||||
<p>以 Cloudflare 为例，常见的四种 SSL/TLS 模式对自签名证书的处理策略如下：</p>
|
||||
<ul>
|
||||
<li>
|
||||
<p><strong>Flexible</strong>：浏览器 ↔ CDN 边缘 使用 HTTPS；CDN 边缘 ↔ 源站 使用 HTTP，不接触证书验证.</p>
|
||||
</li>
|
||||
<li>
|
||||
<p><strong>Full</strong>：浏览器 ↔ CDN 边缘 使用 HTTPS；CDN 边缘 ↔ 源站 使用 HTTPS，但不验证源站证书的 CA 链和域名匹配，可使用自签名证书.
|
||||
Cloudflare Docs</p>
|
||||
</li>
|
||||
<li>
|
||||
<p><strong>Full (strict)</strong>：浏览器 ↔ CDN 边缘 使用 HTTPS；CDN 边缘 ↔ 源站 使用 HTTPS，严格验证源站证书是否由受信任 CA 签发且域名匹配，不支持自签名证书.
|
||||
Cloudflare Docs</p>
|
||||
</li>
|
||||
<li>
|
||||
<p><strong>Off</strong>：关闭 HTTPS，加密支持完全关闭.</p>
|
||||
</li>
|
||||
</ul>
|
||||
<p>若您选择 Full 或 Flexible 模式，即使源站使用自签名证书，CDN 也不会在边缘层对其进行验证，仍会正常转发和缓存内容；而用户浏览器只会看到 CDN 边缘提供的受信任证书，因此不会出现“不受信任”警告.</p>
|
||||
<blockquote>
|
||||
<p>为什么浏览器会信任? 浏览器内置了受信任的根证书列表，CDN 边缘出示的证书链会完整地链接到某个系统信任根，而您的自签名证书则不在此列表内，因而只有源站连接可被 CDN 信任，而非终端浏览器.CDN 则作为“可信中间人”，它信任自签名证书以加密与源站的通信，而浏览器仅信任 CDN 边缘的 CA 签发证书，二者互不干扰，有效隔离了自签名的风险.</p>
|
||||
</blockquote>
|
||||
<h3 id="ru-he-kai-qi-full-strict-mo-shi">如何开启Full (Strict)模式？</h3>
|
||||
<p>要在 Cloudflare 上启用 Full (Strict) 模式，以确保 CDN 与源站之间的通信既加密又验证证书的有效性，请按照以下步骤操作：</p>
|
||||
<p>✅ 步骤 1：确保源站配置了有效的 SSL/TLS 证书</p>
|
||||
<p>在启用 Full (Strict) 模式之前，您的源站必须安装一个有效且受信任的 SSL/TLS 证书.您可以选择以下方式之一：</p>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>使用公共 CA 颁发的证书：如 Let's Encrypt、DigiCert、GlobalSign 等.
|
||||
</span><span>
|
||||
</span><span>使用 Cloudflare Origin CA 证书：这是 Cloudflare 提供的免费证书，专为与其边缘节点通信设计.
|
||||
</span></code></pre>
|
||||
<p>确保证书未过期，且域名匹配正确.如果使用 Cloudflare Origin CA 证书，请在源站服务器上正确安装，并配置服务器（如 Nginx、Apache）以使用该证书.</p>
|
||||
<p>✅ 步骤 2：在 Cloudflare 仪表板中启用 Full (Strict) 模式</p>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>登录到您的 Cloudflare 仪表板.
|
||||
</span><span>
|
||||
</span><span>选择您要配置的站点.
|
||||
</span><span>
|
||||
</span><span>在左侧菜单中，点击 “SSL/TLS”.
|
||||
</span><span>
|
||||
</span><span>在 “概览（Overview）” 标签下，找到 “SSL/TLS 加密模式（SSL/TLS encryption mode）”.
|
||||
</span><span>
|
||||
</span><span>选择 “Full (Strict)” 模式.
|
||||
</span></code></pre>
|
||||
<p>更改后，Cloudflare 会立即应用此设置.建议等待几分钟，然后通过浏览器访问您的网站，确保一切正常运行.</p>
|
||||
<p>🔗 注意事项</p>
|
||||
<p>如果源站使用的是自签名证书或过期的证书，启用 Full (Strict) 模式后，Cloudflare 将无法建立连接，用户可能会看到 526 错误.</p>
|
||||
<p>确保源站服务器的时间设置正确，以避免因时间不一致导致的证书验证失败.</p>
|
||||
<h2 id="dnssecshi-shen-me">DNSSEC是什么？</h2>
|
||||
<p>DNSSEC（Domain Name System Security Extensions，域名系统安全扩展）是一组为 DNS 协议设计的安全机制，旨在通过数字签名验证 DNS 数据的真实性和完整性，防止域名解析过程中的数据篡改和伪造.</p>
|
||||
<ol>
|
||||
<li>DNSSEC 的工作原理</li>
|
||||
</ol>
|
||||
<p>DNSSEC 通过引入以下关键机制来增强 DNS 的安全性：</p>
|
||||
<ul>
|
||||
<li>
|
||||
<p>数字签名（RRSIG 记录）：每个 DNS 记录集（如 A、MX、CNAME 等）都会生成一个对应的数字签名，确保记录在传输过程中未被篡改.</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>公钥发布（DNSKEY 记录）：用于存储验证数字签名所需的公钥.这些公钥本身也通过上级域的签名进行验证，形成信任链.</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>委派签名者（DS 记录）：上级域使用 DS 记录存储下级域的 DNSKEY 记录的摘要，确保公钥的真实性.</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>不存在性证明（NSEC/NSEC3 记录）：用于明确指示某个 DNS 记录不存在，防止攻击者伪造不存在的记录.</p>
|
||||
</li>
|
||||
</ul>
|
||||
<p>通过这些机制，DNSSEC 建立了一条从根域开始的信任链，逐级验证每个域的 DNS 数据，确保其未被篡改且来源可信.</p>
|
||||
<ol start="2">
|
||||
<li>DNSSEC 的局限性</li>
|
||||
</ol>
|
||||
<ul>
|
||||
<li>
|
||||
<p>不加密数据内容：DNSSEC 仅对 DNS 数据进行签名验证，并不加密查询和响应内容，因此无法防止数据被监听.</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>部署复杂性：实施 DNSSEC 需要域名注册商、DNS 服务提供商和客户端解析器的共同支持，部署和维护相对复杂.</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>性能影响：由于引入了额外的签名验证过程，DNSSEC 可能会增加 DNS 查询的响应时间和系统资源消耗.</p>
|
||||
</li>
|
||||
</ul>
|
||||
<ol start="3">
|
||||
<li>DNSSEC 的优势</li>
|
||||
</ol>
|
||||
<ul>
|
||||
<li>
|
||||
<p>防止 DNS 欺骗和缓存投毒：通过验证 DNS 数据的真实性，DNSSEC 能有效防止攻击者伪造 DNS 响应，将用户引导至恶意网站.</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>增强互联网基础设施安全性：作为互联网信任体系的一部分，DNSSEC 为其他安全协议（如 DANE）提供基础支持.</p>
|
||||
</li>
|
||||
</ul>
|
||||
<h2 id="cdnde-wei-zhi-xuan-ze">CDN的位置选择</h2>
|
||||
<p>Netlify在考虑到CDN成本以及可用性的情况下选择了以下这些地区以保证全球大部分访客访问他们的服务都能有不错的连接性和访问速度。</p>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>欧洲中部（德国法兰克福）
|
||||
</span><span>南美（巴西圣保罗）
|
||||
</span><span>美东（美国弗吉尼亚）
|
||||
</span><span>美西（美国旧金山）
|
||||
</span><span>亚洲（新加坡）
|
||||
</span><span>大洋洲（澳大利亚悉尼）
|
||||
</span></code></pre>
|
||||
<p>那么Netlify为什么会选择把CDN节点放到这些地区呢？</p>
|
||||
<p>1.弗吉尼亚，美东的弗吉尼亚被誉为“全球数据中心之都"，美国政府对这个地区的网络投入非常大，使得弗吉尼亚的全球互联（美国本土、欧洲以及到南美洲）优秀。</p>
|
||||
<p>2.旧金山，面向亚太和美西的访客。需要注意的是美西对亚太的网络连接比较优秀，但是到南美不太理想，甚至还有丢包的情况。</p>
|
||||
<p>3.法兰克福，面向欧洲用户，德国法兰克福或者荷兰阿姆斯特丹都是不错的选择。</p>
|
||||
<p>4.新加坡，亚太地区数据中心的枢纽，到印度、日本、越南、香港、中国移动的联通性都不错。</p>
|
||||
<p>5.悉尼，土澳出了名的国际互联不太好，悉尼节点主要是服务本地和周边。</p>
|
||||
<p>6.圣保罗，南美市场。</p>
|
||||
<h2 id="chang-jian-cdnde-iplie-biao">常见CDN的IP列表</h2>
|
||||
<blockquote>
|
||||
<p>需要注意的是有些CDN的回源IP并不用作节点IP，比如Cloudflare的回源IP仅作回源IP使用，如果要获取Cloudflare的节点IP，可前往https://bgp.tools/as/13335#prefixes。而有些CDN的回源IP同时被用作CDN节点，比如BunnyCDN和Gcore CDN。</p>
|
||||
</blockquote>
|
||||
<p>Cloudflare</p>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span># https://www.cloudflare.com/ips-v4
|
||||
</span><span>103.21.244.0/22
|
||||
</span><span>103.22.200.0/22
|
||||
</span><span>103.31.4.0/22
|
||||
</span><span>104.16.0.0/13
|
||||
</span><span>104.24.0.0/14
|
||||
</span><span>108.162.192.0/18
|
||||
</span><span>131.0.72.0/22
|
||||
</span><span>141.101.64.0/18
|
||||
</span><span>162.158.0.0/15
|
||||
</span><span>172.64.0.0/13
|
||||
</span><span>173.245.48.0/20
|
||||
</span><span>188.114.96.0/20
|
||||
</span><span>190.93.240.0/20
|
||||
</span><span>197.234.240.0/22
|
||||
</span><span>198.41.128.0/17
|
||||
</span><span>
|
||||
</span><span># https://www.cloudflare.com/ips-v6
|
||||
</span><span>2400:cb00::/32
|
||||
</span><span>2405:8100::/32
|
||||
</span><span>2405:b500::/32
|
||||
</span><span>2606:4700::/32
|
||||
</span><span>2803:f800::/32
|
||||
</span><span>2a06:98c0::/29
|
||||
</span><span>2c0f:f248::/32
|
||||
</span></code></pre>
|
||||
<p>Gcore</p>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>https://api.gcore.com/cdn/public-ip-list
|
||||
</span></code></pre>
|
||||
<p>BunnyCDN</p>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>https://api.bunny.net/system/edgeserverlist
|
||||
</span><span>https://api.bunny.net/system/edgeserverlist/plain
|
||||
</span></code></pre>
|
||||
<p>Cloudfront</p>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>https://d7uri8nf7uskq.cloudfront.net/tools/list-cloudfront-ips
|
||||
</span><span>https://files.imunify360.com/static/whitelist/v2/cloudfront-cdn.txt
|
||||
</span></code></pre>
|
||||
<p>CDN77</p>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>https://files.imunify360.com/static/whitelist/v2/cdn77.txt
|
||||
</span></code></pre>
|
||||
<p>Fastly</p>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>https://api.fastly.com/public-ip-list
|
||||
</span></code></pre>
|
||||
<p>Keycdn</p>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>https://www.keycdn.com/shield-prefixes.json
|
||||
</span></code></pre>
|
||||
<p>quic.cloud</p>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>https://quic.cloud/ips
|
||||
</span></code></pre>
|
||||
<p>Google CDN</p>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>https://files.imunify360.com/static/whitelist/v2/google-cdn.txt
|
||||
</span></code></pre>
|
||||
<p>CacheFly</p>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>https://cachefly.cachefly.net/ips/cdn.txt
|
||||
</span></code></pre>
|
||||
<p>Akaima</p>
|
||||
<pre style="background-color:#151515;color:#e8e8d3;"><code><span>https://techdocs.akamai.com/origin-ip-acl/docs/update-your-origin-server
|
||||
</span></code></pre>
|
||||
<hr />
|
||||
<p><strong>Done.</strong></p>
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
<div class="pagination">
|
||||
<div class="pagination__title">
|
||||
<span class="pagination__title-h">Thanks for reading! Read other posts?</span>
|
||||
<hr />
|
||||
</div>
|
||||
<div class="pagination__buttons">
|
||||
<span class="button previous">
|
||||
<a href="https://blog.dich.bid/network-ssl/">
|
||||
<span class="button__icon">←</span>
|
||||
<span class="button__text">Network的艺术:SSL/TLS证书</span>
|
||||
</a>
|
||||
</span>
|
||||
|
||||
|
||||
<span class="button next">
|
||||
<a href="https://blog.dich.bid/network-how-email-works-1/">
|
||||
<span class="button__text">电子邮件是如何工作的:SPF/DKIM/DMARC</span>
|
||||
<span class="button__icon">→</span>
|
||||
</a>
|
||||
</span>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
</div>
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
<footer class="footer">
|
||||
<div class="footer__inner">
|
||||
<div class="copyright">
|
||||
<span>©
|
||||
2025
|
||||
Dichgrem</span>
|
||||
<span class="copyright-theme">
|
||||
<span class="copyright-theme-sep"> :: CC BY-SA 4.0 :: A friend comes from distant lands</span>
|
||||
</a>
|
||||
</span>
|
||||
</div>
|
||||
</div>
|
||||
</footer>
|
||||
|
||||
</div>
|
||||
</body>
|
||||
</html>
|
||||
|
||||
Some files were not shown because too many files have changed in this diff Show More
Reference in New Issue
Block a user