8,560
edits
Difference between revisions of "Manjaro:A Different Kind of Beast/zh-cn"
Manjaro:A Different Kind of Beast/zh-cn (view source)
Revision as of 06:44, 27 August 2023
, 1 year agoUpdating to match new version of source page
(Updating to match new version of source page) Tags: Mobile web edit Mobile edit |
(Updating to match new version of source page) Tags: Mobile web edit Mobile edit |
||
| Line 32: | Line 32: | ||
When a Manjaro ISO is released it contains the latest Long Time (LTS) as defined by upstream kernel project. This practise makes it possible to install Manjaro and keep it running using the LTS kernel - if not for ever - then for a very long time. | When a Manjaro ISO is released it contains the latest Long Time (LTS) as defined by upstream kernel project. This practise makes it possible to install Manjaro and keep it running using the LTS kernel - if not for ever - then for a very long time. | ||
The latest and | The latest and greatest hardware may have poor or non existing support using the LTS kernel. Such hardware will require you to use what is referenced as the '''stable''' kernel. | ||
The stable kernel goes End Of Life (EOL) when the next mainline becomes stable which happens roughly every 2 months. If you are using the '''stable''' kernel - not LTS - you will have to ensure you are syncing the next stable kernel. | The stable kernel goes End Of Life (EOL) when the next mainline becomes stable which happens roughly every 2 months. If you are using the '''stable''' kernel - not LTS - you will have to ensure you are syncing the next stable kernel. | ||
| Line 38: | Line 38: | ||
'''A stable kernel on Manjaro is never synced to the next stable kernel like you may be used to with an Arch Linux install'''. | '''A stable kernel on Manjaro is never synced to the next stable kernel like you may be used to with an Arch Linux install'''. | ||
If you neglect | If you neglect you are running an EOL kernel you will get various driver issues - most prominently Nvidia drivers - when the EOL kernel is removed from the repo. Such issues is not a Manjaro fault but a fault of the system admin who neglected proper system maintenance. | ||
}} | }} | ||
| Line 46: | Line 46: | ||
为了确保持续的稳定性和可靠性，Manjaro 使用自己的专用软件存储库。除了社区维护的 Arch 用户存储库 (AUR)，Manjaro 系统不访问官方的 Arch 存储库。 | 为了确保持续的稳定性和可靠性，Manjaro 使用自己的专用软件存储库。除了社区维护的 Arch 用户存储库 (AUR)，Manjaro 系统不访问官方的 Arch 存储库。 | ||
<div class="mw-translate-fuzzy"> | |||
===Manjaro 软件包仓库=== | ===Manjaro 软件包仓库=== | ||
====稳定分支（Stable）==== | ====稳定分支（Stable）==== | ||
| Line 55: | Line 56: | ||
====没有 Arch 激进（bleeding edge）==== | ====没有 Arch 激进（bleeding edge）==== | ||
适应这个测试过程的结果是 Manjaro 永远不会像 Arch 那样激进。一个软件可能会在几天、几周甚至几个月后发布到稳定的存储库；但是，希望访问最新版本的用户仍然可以通过切换到'''测试'''或'''不稳定'''分支来访问。这样做将证明您知识渊博并且是 Manjaro Linux 高级用户。 | 适应这个测试过程的结果是 Manjaro 永远不会像 Arch 那样激进。一个软件可能会在几天、几周甚至几个月后发布到稳定的存储库；但是，希望访问最新版本的用户仍然可以通过切换到'''测试'''或'''不稳定'''分支来访问。这样做将证明您知识渊博并且是 Manjaro Linux 高级用户。 | ||
</div> | |||
|}} | |}} | ||