Compare commits
202 Commits
| Author | SHA1 | Date | |
|---|---|---|---|
| efb68e1d94 | |||
| 5bc7d20547 | |||
| 311f86d55c | |||
| 0d4a550731 | |||
| f1c1786936 | |||
| e179118e1c | |||
| 44d07ab728 | |||
| 63ac1a54be | |||
| e39fd30704 | |||
| d67b9beac9 | |||
| 990966b5b4 | |||
| 76e377278f | |||
| c44548a55a | |||
| ce716eff61 | |||
| 851a41de88 | |||
| 4d62a23039 | |||
| bba463cb49 | |||
| 72a6b7f212 | |||
| 4151fb20d7 | |||
| 8d9fe19c89 | |||
| 29a77b8ba7 | |||
| ca40794a49 | |||
| f84ed4bdc9 | |||
| f9d2bbdb25 | |||
| 3957464189 | |||
| 96217f6179 | |||
| 83b12c65fd | |||
| c95c1ffd70 | |||
| b2ecf5f144 | |||
| 855153c10e | |||
| 77d7631e37 | |||
| bef08ba148 | |||
| 07a1a9372f | |||
| 1dc3d59bc4 | |||
| d0e71c8f5a | |||
| 2327247a29 | |||
| c0981002a6 | |||
| 6627f3105a | |||
| 52ea187067 | |||
| 10165b31ba | |||
| f481cbeaca | |||
| ff5f2e41c7 | |||
| 637ebdc2ba | |||
| 1b8fe35939 | |||
| ce3a6c3321 | |||
| 10d167b543 | |||
| 2020f5b1a6 | |||
| c913639121 | |||
| fb989f6291 | |||
| 8e32449d47 | |||
| 97cc3cfbbd | |||
| df0063ef02 | |||
| 41ca0a41b9 | |||
| 056119551c | |||
| 5071a60b34 | |||
| 4e16119846 | |||
| 81ea8a4e54 | |||
| f975d1dc00 | |||
| e90885986f | |||
| 7b21fb9159 | |||
| b753e49df3 | |||
| edbb9286e5 | |||
| 1b15019f03 | |||
| f9d976de41 | |||
| cdaa36e279 | |||
| e2e1a2896c | |||
| 0a8674c530 | |||
| 7a4e6c6d1c | |||
| 410768be7e | |||
| 389887026e | |||
| 0aa9fad0ec | |||
| 96b4c58aa7 | |||
| d539c6feff | |||
| 6e3e1d9135 | |||
| f8207916a3 | |||
| c98dfdad9c | |||
| 912bb57255 | |||
| 8ca656b901 | |||
| 112ec79c56 | |||
| 9264ae8b73 | |||
| dbf84a7bb9 | |||
| a39c15e550 | |||
| 74fd2fab55 | |||
| c9134c7283 | |||
| 2258c90604 | |||
| 3ec50a2cf8 | |||
| dd6d5aeed2 | |||
| d4cb55239f | |||
| 7f61f94836 | |||
| 5a66e0effe | |||
| 69f7314da2 | |||
| b3dc735a6c | |||
| a1c4bf38dc | |||
| 0351271a7e | |||
| 63cd737447 | |||
| 23bbd6ba73 | |||
| c99e596c79 | |||
| 5eebaea1f6 | |||
| d5dcf8a7a0 | |||
| 32e1b94030 | |||
| d744224c8e | |||
| 4df2dfdc15 | |||
| 58cba207fa | |||
| 9095e06aad | |||
| 992a703fbe | |||
| fab1ad6f85 | |||
| b3ca8be1a5 | |||
| 7e74e7b8ca | |||
| 20af82abd8 | |||
| 1b24b3629f | |||
| 211e5c1bdd | |||
| 718e480d71 | |||
| 46a25b42e7 | |||
| 9b13de39be | |||
| 72cca8f019 | |||
| 2102b71d83 | |||
| 0fcb703eeb | |||
| deb72b741c | |||
| 1688e2241a | |||
| a1822e21e8 | |||
| 3fa6558b07 | |||
| c811324028 | |||
| 1bc2804b1b | |||
| a3f72d407a | |||
| 59c745abfd | |||
| 2387065e74 | |||
| 73e5ba9f6f | |||
| 265469c584 | |||
| 3bbc77a187 | |||
| 6e7c909fef | |||
| b2e82fe887 | |||
| eb5c874627 | |||
| cace98df58 | |||
| 29d9bd2233 | |||
| 7030b996e9 | |||
| 0df6c38203 | |||
| fbfe5f43c6 | |||
| d4529b126b | |||
| 2f0a056995 | |||
| 8c588b9ac2 | |||
| 36c8cf81da | |||
| 6cc03629a3 | |||
| a4b24d7f86 | |||
| d671e584aa | |||
| fc972821c1 | |||
| 7861c356db | |||
| 4707f1d3e4 | |||
| 1f82cf1dab | |||
| 6cd5f65b17 | |||
| d0de8ee64a | |||
| 1806ec04dd | |||
| 8cf25310af | |||
| fa708972f4 | |||
| da2334e3ab | |||
| 8c0ad119e7 | |||
| c04bbed8cb | |||
| c1c4e6793f | |||
| 87930e2f2b | |||
| f3ffba44a1 | |||
| 0fa7d2bc64 | |||
| 5549a0a186 | |||
| 2ec68b4ab1 | |||
| 22e1af3d7e | |||
| a2de1ee7ba | |||
| 5a041baa1c | |||
| 6ac6b4812b | |||
| 565560ee7b | |||
| 699c4e60a9 | |||
| 03943a1774 | |||
| 21ae1da040 | |||
| cd0ec7217c | |||
| 72762f1399 | |||
| bc8907acb0 | |||
| ee38997188 | |||
| 973cd6a98b | |||
| d865735824 | |||
| d42d3ab438 | |||
| 69ec80848d | |||
| d2717ac3eb | |||
| 49efe4f7bc | |||
| 79daa13b75 | |||
| f226df0738 | |||
| e5678ec3e5 | |||
| f73fe76cbb | |||
| 02c4daa41c | |||
| 040a1b41ce | |||
| 3537e7e8a6 | |||
| 580b2166ec | |||
| a19948e235 | |||
| 17e70abdf2 | |||
| bb874bec89 | |||
| a20dee18a7 | |||
| 6902e5319b | |||
| 6d763205d2 | |||
| 8b19b4b151 | |||
| 1873b3f69e | |||
| ca25cc647d | |||
| cf59c3486e | |||
| cc56d56ee9 | |||
| 10d1185f9e | |||
| 6041602913 | |||
| a7005f8f34 |
@@ -0,0 +1,23 @@
|
||||
name: Check
|
||||
|
||||
on: [pull_request]
|
||||
|
||||
|
||||
jobs:
|
||||
build:
|
||||
|
||||
runs-on: ubuntu-latest
|
||||
|
||||
steps:
|
||||
- uses: actions/checkout@v1
|
||||
- name: Install dependencies
|
||||
run: |
|
||||
export PATH="$HOME/.local/bin:$PATH"
|
||||
sudo apt-get install -y python3-setuptools
|
||||
pip3 install --user -r requirements.txt
|
||||
- name: Build the docs
|
||||
run: |
|
||||
export PATH="$HOME/.local/bin:$PATH"
|
||||
make py
|
||||
make htmlall
|
||||
|
||||
@@ -0,0 +1,13 @@
|
||||
name: Greetings
|
||||
|
||||
on: [pull_request, issues]
|
||||
|
||||
jobs:
|
||||
greeting:
|
||||
runs-on: ubuntu-latest
|
||||
steps:
|
||||
- uses: actions/first-interaction@v1
|
||||
with:
|
||||
repo-token: ${{ secrets.GITHUB_TOKEN }}
|
||||
issue-message: 'Welcome to Clear Linux* OS Docs. Thanks for submitting your first issue.'
|
||||
pr-message: 'Welcome to Clear Linux* OS Docs. Thanks for submitting your first PR.'
|
||||
@@ -0,0 +1,39 @@
|
||||
name: CI
|
||||
|
||||
on:
|
||||
push:
|
||||
branches:
|
||||
- master
|
||||
|
||||
jobs:
|
||||
build:
|
||||
|
||||
runs-on: ubuntu-latest
|
||||
|
||||
steps:
|
||||
- uses: actions/checkout@v1
|
||||
- name: Install dependencies
|
||||
run: |
|
||||
export PATH="$HOME/.local/bin:$PATH"
|
||||
sudo apt-get install -y python3-setuptools
|
||||
pip3 install --user -r requirements.txt
|
||||
- name: Build the docs
|
||||
run: |
|
||||
export PATH="$HOME/.local/bin:$PATH"
|
||||
make py
|
||||
make htmlall
|
||||
- name: Pre-deploy
|
||||
run: |
|
||||
wget https://github.com/clearlinux/clear-linux-documentation-zh-CN/releases/latest/download/clearlinux-docs-zh-CN.tar.gz
|
||||
mkdir source/_build/html/zh_CN
|
||||
tar xvzf clearlinux-docs-zh-CN.tar.gz -C source/_build/html/zh_CN
|
||||
mv source/_build/html $HOME/output
|
||||
- name: Deploy the docs
|
||||
run: |
|
||||
cd $HOME/output
|
||||
git init
|
||||
git config --global user.name "${GITHUB_ACTOR}"
|
||||
git config --global user.email "${GITHUB_ACTOR}@github.com"
|
||||
git add .
|
||||
git commit -m "latest html output"
|
||||
git push -f https://${GITHUB_ACTOR}:${{secrets.ACCESS_TOKEN}}@github.com/clearlinux/clear-linux-documentation.git HEAD:developmentHTML
|
||||
@@ -0,0 +1,43 @@
|
||||
name: Publish
|
||||
|
||||
on:
|
||||
push:
|
||||
branches:
|
||||
- publish
|
||||
|
||||
jobs:
|
||||
build:
|
||||
|
||||
runs-on: ubuntu-latest
|
||||
|
||||
steps:
|
||||
- uses: actions/checkout@v1
|
||||
- name: Install dependencies
|
||||
run: |
|
||||
export PATH="$HOME/.local/bin:$PATH"
|
||||
sudo apt-get install -y python3-setuptools
|
||||
pip3 install --user -r requirements.txt
|
||||
- name: Build the docs
|
||||
run: |
|
||||
export PATH="$HOME/.local/bin:$PATH"
|
||||
make py
|
||||
make htmlall
|
||||
- name: Pre-deploy
|
||||
run: |
|
||||
wget https://github.com/clearlinux/clear-linux-documentation-zh-CN/releases/latest/download/clearlinux-docs-zh-CN.tar.gz
|
||||
mkdir source/_build/html/zh_CN
|
||||
tar xvzf clearlinux-docs-zh-CN.tar.gz -C source/_build/html/zh_CN
|
||||
mv source/_build/html $HOME/output
|
||||
- name: Deploy the docs
|
||||
run: |
|
||||
cd $HOME/output
|
||||
git init
|
||||
git config --global user.name "${GITHUB_ACTOR}"
|
||||
git config --global user.email "${GITHUB_ACTOR}@github.com"
|
||||
git add .
|
||||
git commit -m "latest html output"
|
||||
git push -f https://${GITHUB_ACTOR}:${{secrets.ACCESS_TOKEN}}@github.com/clearlinux/clear-linux-documentation.git HEAD:latestHTML
|
||||
- name: Publish the docs
|
||||
run: |
|
||||
wget ${{secrets.PUBLISH_URL}}
|
||||
cat clearlinux-latest
|
||||
@@ -14,3 +14,6 @@ source/_build
|
||||
# ignore artifacts generated by running make py
|
||||
cloned_repo
|
||||
bundles.html.txt
|
||||
|
||||
# ignore the venv, used for running make py
|
||||
venv
|
||||
|
||||
@@ -1,37 +0,0 @@
|
||||
language: python
|
||||
|
||||
python:
|
||||
- "3.6"
|
||||
|
||||
# command to install dependencies
|
||||
install:
|
||||
- pip3 install -q -r requirements.txt
|
||||
- pip3 install -q -r source/_scripts/_python/requirements.txt
|
||||
|
||||
# command to run tests
|
||||
script:
|
||||
- make py
|
||||
- make htmlall
|
||||
|
||||
before_deploy:
|
||||
- make linkcheck
|
||||
|
||||
deploy:
|
||||
- provider: pages
|
||||
skip_cleanup: true
|
||||
github_token: $GITHUB_TOKEN
|
||||
target-branch: latestHTML
|
||||
on:
|
||||
branch: master
|
||||
local_dir: source/_build/html/
|
||||
- provider: pages
|
||||
skip_cleanup: true
|
||||
github_token: $GITHUB_TOKEN
|
||||
target-branch: developmentHTML
|
||||
on:
|
||||
branch: development
|
||||
local_dir: source/_build/html/
|
||||
|
||||
after_deploy:
|
||||
- wget $PUBLISH_URL
|
||||
- cat clearlinux-latest
|
||||
@@ -1,5 +1,8 @@
|
||||
# Makefile for Sphinx documentation
|
||||
#
|
||||
|
||||
SHELL := /bin/bash
|
||||
|
||||
PY_VERSION ?= 3.6
|
||||
|
||||
all:
|
||||
make -C source html
|
||||
@@ -28,4 +31,9 @@ help:
|
||||
|
||||
clean:
|
||||
make -C source clean
|
||||
rm -rf venv
|
||||
|
||||
venv:
|
||||
virtualenv venv;\
|
||||
source venv/bin/activate; \
|
||||
pip3 install -r requirements.txt;
|
||||
|
||||
@@ -10,38 +10,46 @@ documentation locally for development and testing.
|
||||
Please make yourself familiar with our `contribution guidelines`_ before
|
||||
submitting a contribution.
|
||||
|
||||
Requirements
|
||||
************
|
||||
|
||||
Make sure you have Python and Sphinx installed. We use Python 3 and
|
||||
Sphinx 1.7.5
|
||||
|
||||
The Sphinx documentation provides `instructions for installing Sphinx`_ on various
|
||||
platforms.
|
||||
|
||||
Clone the documentation repository
|
||||
**********************************
|
||||
|
||||
Once Sphinx is installed, clone the documentation repository to your
|
||||
local machine.
|
||||
Clone the documentation repository to your local machine.
|
||||
|
||||
.. code-block:: console
|
||||
.. code-block:: bash
|
||||
|
||||
$ git clone https://github.com/clearlinux/clear-linux-documentation
|
||||
git clone https://github.com/clearlinux/clear-linux-documentation
|
||||
|
||||
Requirements
|
||||
************
|
||||
|
||||
Make sure you have Python 3 installed to start.
|
||||
|
||||
The Sphinx documentation provides `instructions for installing Sphinx`_
|
||||
on various platforms.
|
||||
|
||||
Use pip3 to install additional Python dependencies listed in the
|
||||
requirements.txt file found in the repository:
|
||||
|
||||
.. code-block:: bash
|
||||
|
||||
pip3 install -r requirements.txt
|
||||
|
||||
Run the build
|
||||
*************
|
||||
|
||||
We build our documentation using Sphinx. In the source directory of your
|
||||
local clear-linux-documentation repository, build the documentation by running
|
||||
**make html**:
|
||||
local clear-linux-documentation repository, preview changes to the
|
||||
documentation by building the docs in the default language (English) by
|
||||
running ``make html``:
|
||||
|
||||
.. code-block:: bash
|
||||
|
||||
make html
|
||||
|
||||
.. code-block:: console
|
||||
|
||||
$ make html
|
||||
>
|
||||
sphinx-build -b html -d _build/doctrees . _build/html
|
||||
Running Sphinx v1.7.5
|
||||
Running Sphinx v1.8.0
|
||||
making output directory...
|
||||
.
|
||||
.
|
||||
@@ -52,23 +60,125 @@ local clear-linux-documentation repository, build the documentation by running
|
||||
|
||||
Build finished. The HTML pages are in _build/html.
|
||||
|
||||
Open one of the HTML pages in a web browser to view the rendered
|
||||
documentation.
|
||||
Open one of the HTML pages found in ``source/_build/html`` in a web browser
|
||||
to view the rendered documentation.
|
||||
|
||||
If you want to build the documentation exactly as seen on the website, use
|
||||
``make py`` followed by ``make htmlall``. This builds some
|
||||
external dependencies and all supported languages.
|
||||
|
||||
Use virtualenv
|
||||
**************
|
||||
|
||||
To develop documentation in a ``virtualenv``, use the ``venv`` target.
|
||||
The Clear Linux OS documentation make target ``venv`` provides a
|
||||
simple development environment that ensures that you have the
|
||||
latest packages and that you manage Python versions separately. Use of the
|
||||
``virtualenv`` requires **Python 3.6** or higher. For Windows examples below, use Powershell as an Administrator.
|
||||
|
||||
The **virtual environment** uses the same version of Python that was used to **create the virtual environment**.
|
||||
|
||||
Verify ``pip`` is installed. A file path to pip should appear.
|
||||
|
||||
On Clear Linux OS and macOS\*:
|
||||
|
||||
.. code-block:: bash
|
||||
|
||||
which pip
|
||||
|
||||
On Windows\* 10 OS:
|
||||
|
||||
.. code-block:: bash
|
||||
|
||||
pip --version
|
||||
|
||||
If ``pip`` is not installed, install it.
|
||||
|
||||
On Clear Linux OS and macOS:
|
||||
|
||||
.. code-block:: bash
|
||||
|
||||
python3 -m pip install --user --upgrade pip
|
||||
|
||||
On Windows 10 OS:
|
||||
|
||||
.. code-block:: bash
|
||||
|
||||
py -m pip install --upgrade pip
|
||||
|
||||
.. note::
|
||||
|
||||
This assumes Python was already added to your Windows path.
|
||||
|
||||
Install virtualenv
|
||||
==================
|
||||
|
||||
Install ``virtualenv``.
|
||||
|
||||
On Clear Linux OS and macOS\*:
|
||||
|
||||
.. code-block:: bash
|
||||
|
||||
python3 -m pip install --user virtualenv
|
||||
|
||||
On Windows 10 OS:
|
||||
|
||||
.. code-block:: bash
|
||||
|
||||
py -m pip install --user virtualenv
|
||||
|
||||
Create the ``virtualenv`` and install the required packages:
|
||||
|
||||
.. code-block:: bash
|
||||
|
||||
make venv
|
||||
|
||||
Activate the ``venv``.
|
||||
|
||||
.. code-block:: bash
|
||||
|
||||
source venv/bin/activate
|
||||
|
||||
Follow `Run the build`_ section to start developing documentation.
|
||||
|
||||
Remove the ``venv`` when finished developing.
|
||||
|
||||
.. code-block:: bash
|
||||
|
||||
deactivate
|
||||
|
||||
Additional help
|
||||
***************
|
||||
|
||||
Cleaning up
|
||||
===========
|
||||
|
||||
When testing changes in the documentation, make sure to remove the previous
|
||||
build before building again by running **make clean**:
|
||||
build before building again by running ``make clean``:
|
||||
|
||||
.. code-block:: console
|
||||
.. code-block:: bash
|
||||
|
||||
$ make clean
|
||||
>
|
||||
rm -rf _build/*
|
||||
make clean
|
||||
|
||||
This will completely remove the previous build output.
|
||||
This will completely remove the previous build output, including artifacts
|
||||
from the `make venv` target when done outside an active venv.
|
||||
|
||||
.. _Clear Linux\* OS documentation: https://clearlinux.org/documentation
|
||||
Convenience script
|
||||
==================
|
||||
|
||||
This bash script (Linux only) includes both ``make clean`` and
|
||||
``make html``. It also starts a simple Python web server that
|
||||
displays a preview of the site at http://localhost:8000 on your local machine.
|
||||
|
||||
.. code-block:: bash
|
||||
|
||||
./checkwork.sh
|
||||
|
||||
To stop the web server simply use ``ctrl-c``.
|
||||
|
||||
.. _Clear Linux\* OS documentation: https://docs.01.org/clearlinux/
|
||||
.. _Sphinx: http://sphinx-doc.org/
|
||||
.. _reStructuredText: http://www.sphinx-doc.org/en/master/usage/restructuredtext/basics.html
|
||||
.. _contribution guidelines: https://clearlinux.org/documentation/clear-linux/reference/collaboration
|
||||
.. _contribution guidelines: https://docs.01.org/clearlinux/latest/collaboration/collaboration.html
|
||||
.. _instructions for installing Sphinx: https://www.sphinx-doc.org/en/master/usage/installation.html
|
||||
|
||||
|
||||
@@ -0,0 +1,54 @@
|
||||
language: python
|
||||
|
||||
python:
|
||||
- "3.6"
|
||||
|
||||
# command to install dependencies
|
||||
install:
|
||||
- pip3 install -q -r requirements.txt
|
||||
|
||||
# command to run tests
|
||||
script:
|
||||
- make py
|
||||
- make htmlall
|
||||
|
||||
before_deploy:
|
||||
- make linkcheck
|
||||
# only deploy the latest tagged release of Simplified Chinese docs
|
||||
- wget https://github.com/clearlinux/clear-linux-documentation-zh-CN/releases/latest/download/clearlinux-docs-zh-CN.tar.gz
|
||||
- mkdir source/_build/html/zh_CN
|
||||
- tar xvzf clearlinux-docs-zh-CN.tar.gz -C source/_build/html/zh_CN
|
||||
|
||||
deploy:
|
||||
- provider: pages
|
||||
skip_cleanup: true
|
||||
github_token: $GITHUB_TOKEN
|
||||
target-branch: latestHTML
|
||||
on:
|
||||
branch: publish
|
||||
local_dir: source/_build/html/
|
||||
- provider: pages
|
||||
skip_cleanup: true
|
||||
github_token: $GITHUB_TOKEN
|
||||
target-branch: developmentHTML
|
||||
on:
|
||||
branch: master
|
||||
local_dir: source/_build/html/
|
||||
- provider: pages
|
||||
skip_cleanup: true
|
||||
github_token: $GITHUB_TOKEN
|
||||
target-branch: developmentHTML
|
||||
on:
|
||||
branch: development
|
||||
local_dir: source/_build/html/
|
||||
- provider: releases
|
||||
skip_cleanup: true
|
||||
api_key: $GITHUB_TOKEN
|
||||
file: clearlinux-docs-zh-CN.tar.gz
|
||||
on:
|
||||
tags: true
|
||||
|
||||
|
||||
after_deploy:
|
||||
- wget $PUBLISH_URL
|
||||
- cat clearlinux-latest
|
||||
@@ -3,4 +3,7 @@ sphinx==1.8
|
||||
docutils==0.14
|
||||
sphinx_rtd_theme
|
||||
sphinx-intl==2.0.0
|
||||
sphinx-sitemap==1.0.2
|
||||
sphinx-sitemap==1.0.2
|
||||
Jinja2==2.10.1
|
||||
GitPython==3.0.8
|
||||
sphinx-tabs
|
||||
|
||||
@@ -12,26 +12,43 @@ Below is a list of commonly asked questions with answers sourced from the
|
||||
General
|
||||
*******
|
||||
|
||||
Why did you make another distro?
|
||||
================================
|
||||
What is |CL|?
|
||||
=============
|
||||
|
||||
|CL| is an open source, rolling release Linux distribution optimized for
|
||||
performance and security. See `the about page <https://clearlinux.org/about>`_
|
||||
for more information.
|
||||
|
||||
|
|
||||
|
||||
Why another Linux distribution?
|
||||
===============================
|
||||
|
||||
The |CL| team felt that performance was left on the table with Linux software.
|
||||
|CL| takes a holistic approach to improving performance across the stack. We
|
||||
|CL| takes a holistic approach to improve performance across the stack. We
|
||||
also wanted to take more modern approaches with OS updates and tooling.
|
||||
|
||||
|
|
||||
|
||||
Can other distros copy |CL| improvements?
|
||||
=========================================
|
||||
Is it a derivative of another Linux distribution?
|
||||
=================================================
|
||||
|
||||
No. |CL| is a new Linux distribution. It is not a fork and does not have a
|
||||
parent Linux distribution.
|
||||
|
||||
|
|
||||
|
||||
Can others copy improvements from |CL|?
|
||||
=======================================
|
||||
|
||||
Yes, we absolutely love open source reuse and upstreaming improvements.
|
||||
|
||||
|
|
||||
|
||||
How often do you update?
|
||||
========================
|
||||
How often does it update?
|
||||
=========================
|
||||
|
||||
The |CL| team puts out multiple releases a week, often releasing 2 or more
|
||||
The |CL| team puts out multiple releases a week, often releasing two or more
|
||||
times a day. This rolling release approach allows |CL| to remain agile to
|
||||
upstream changes and security patches.
|
||||
|
||||
@@ -43,15 +60,16 @@ Is telemetry required?
|
||||
The telemetry solution provided by |CL| is entirely optional and customizable.
|
||||
It is disabled by default. If you do choose to enable telemetry, the data
|
||||
helps the |CL| team proactively identify and resolve bugs. See the
|
||||
:ref:`telem-guide` guide for more information.
|
||||
:ref:`telemetry <telem-guide>` guide for more information.
|
||||
|
||||
|
|
||||
|
||||
What is the default firewall?
|
||||
=============================
|
||||
|
||||
|CL| packages :command:`iptables` as a bundle, however, there are no default
|
||||
firewall rules. All network traffic is allowed by default.
|
||||
|CL| packages :command:`iptables` and :command:`firewalld` as optional
|
||||
bundles, however, there are no default firewall rules. All network traffic is
|
||||
allowed by default.
|
||||
|
||||
|
|
||||
|
||||
@@ -60,21 +78,35 @@ Where are the files that I usually see under /etc like fstab?
|
||||
|
||||
|CL| has a stateless design that maintains a separation between system files
|
||||
and user files. Default values are stored under :file:`/usr/share/defaults/`.
|
||||
Files under :file:`/etc/` are not created unless you create one.
|
||||
|CL| starts with a mostly empty :file:`/etc` directory to store user-defined
|
||||
configurations. See the :ref:`stateless <stateless>` page for more information.
|
||||
|
||||
See `this blog post
|
||||
<https://clearlinux.org/news-blogs/where-etcfstab-clear-linux>`_ for an
|
||||
example explaining how this is accomplished with :file:`/etc/fstab/`
|
||||
specifically.
|
||||
|
||||
A blog post explaining how this is accomplished with :file:`/etc/fstab/`
|
||||
specifically is available here:
|
||||
https://clearlinux.org/news-blogs/where-etcfstab-clear-linux
|
||||
|
||||
|
|
||||
|
||||
Software packages
|
||||
*****************
|
||||
Does it use the Intel Compiler (icc)?
|
||||
=====================================
|
||||
|
||||
No. |CL| uses open source compilers: :command:`gcc` and :command:`clang`. |CL|
|
||||
does not compile any packages with :command:`icc`.
|
||||
|
||||
For a more detailed explanation, see `this discussion on the community forum
|
||||
<https://community.clearlinux.org/t/does-clear-linux-os-use-the-intel-compiler-icc-tl-nope/>`_.
|
||||
|
||||
|
|
||||
|
||||
Software
|
||||
********
|
||||
|
||||
How is software installed and updated?
|
||||
======================================
|
||||
|
||||
|CL| provides software in the form of :ref:`bundles-guide` and
|
||||
|CL| provides software in the form of :ref:`bundles <bundles-guide>` and
|
||||
updates software with :ref:`swupd <swupd-guide>`.
|
||||
|
||||
:ref:`Flatpak\* <flatpak-tutorial>` is an application virtualization solution
|
||||
@@ -86,15 +118,29 @@ bundles whenever possible.
|
||||
|
||||
|
|
||||
|
||||
Does |CL| use RPMs like other distros?
|
||||
======================================
|
||||
Does it use RPMs or DEBs packages like other distros?
|
||||
=====================================================
|
||||
|
||||
|CL| provides software in the form of :ref:`bundles-guide`. The RPM
|
||||
format is used as an intermediary step for packaging and determining software
|
||||
dependencies at OS build time.
|
||||
No. |CL| provides software to systems in the form of :ref:`bundles-guide`.
|
||||
Under the hood, |CL| developers use the RPM format as an intermediary step for
|
||||
packaging and determining software dependencies at OS build time.
|
||||
|
||||
Individual RPMs and DEBs can sometimes be manually extracted and installed on
|
||||
a |CL| system with the right tools, but that is not the intended use case.
|
||||
|
||||
|
|
||||
|
||||
Why does it have a different approach to software management?
|
||||
=============================================================
|
||||
|
||||
The |CL| team wants software *installation* and *updates* to be as efficient
|
||||
and error free as possible. |CL| packages software differently and uses a
|
||||
novel updater to solve some of the classic problems with how the software
|
||||
packages are on Linux.
|
||||
|
||||
For a more detailed explanation, see `this discussion on our community forum
|
||||
<https://community.clearlinux.org/t/why-does-clearlinux-use-swupd-and-not-apt-deb-rpm/>`_.
|
||||
|
||||
Individual RPMs can sometimes be manually installed on a |CL| system with the
|
||||
right tools, but that is not the intended use case.
|
||||
|
||||
|
|
||||
|
||||
@@ -127,8 +173,9 @@ Is Google\* Chrome\* available?
|
||||
The Google Chrome web browser is not distributed as a bundle in |CL| due to
|
||||
copyright and licensing complexities.
|
||||
|
||||
A discussion on manually installing and maintaining Google Chrome can be found
|
||||
on GitHub: https://github.com/clearlinux/distribution/issues/422
|
||||
A `discussion on manually installing and maintaining Google Chrome
|
||||
<https://github.com/clearlinux/distribution/issues/422>`_ can be found on
|
||||
GitHub.
|
||||
|
||||
|
|
||||
|
||||
@@ -137,13 +184,15 @@ Is Microsoft\* Visual Studio Code\* available?
|
||||
|
||||
Yes. Find the CLI command for installing `VS Code`_ and other Flatpak apps in
|
||||
the `software store`_. Installing Flatpak apps is also covered in our
|
||||
:ref:`tutorial <flatpak-tutorial>`.
|
||||
:ref:`tutorial <flatpak-tutorial>`.
|
||||
|
||||
The |CL| team is working on a natively packaged version of Visual Studio Code
|
||||
for future release.
|
||||
|
||||
Join a community forum discussion about manually installing and maintaining
|
||||
Visual Studio Code: https://community.clearlinux.org/t/need-native-support-for-vs-code-through-swupd/
|
||||
Join a community `forum discussion about manually installing and maintaining
|
||||
Visual Studio Code
|
||||
<https://community.clearlinux.org/t/need-native-support-for-vs-code-through-swupd/>`_.
|
||||
|
||||
|
||||
.. _VS Code: https://clearlinux.org/software?search_api_fulltext=vscode
|
||||
|
||||
@@ -159,13 +208,12 @@ various media encoding/decoding, streaming, and playback.
|
||||
complexities (See https://www.ffmpeg.org/legal.html and
|
||||
http://blog.pkh.me/p/13-the-ffmpeg-libav-situation.html).
|
||||
|
||||
Read more in the |CL| repository, including discussion of an alternative
|
||||
hardware-based solution:
|
||||
https://github.com/clearlinux/distribution/issues/429.
|
||||
|
||||
While |CL| cannot distribute FFmpeg, a manual solution to build and install
|
||||
FFmpeg under :file:`/usr/local` has been shared on the community forums:
|
||||
https://community.clearlinux.org/t/how-to-h264-etc-support-for-firefox-including-ffmpeg-install.
|
||||
While |CL| cannot distribute FFmpeg, solutions for manually building and
|
||||
installing FFmpeg have been shared by users `on GitHub
|
||||
<https://github.com/clearlinux/distribution/issues/429>`_ and `the community
|
||||
forums
|
||||
<https://community.clearlinux.org/t/how-to-h264-etc-support-for-firefox-including-ffmpeg-install>`_.
|
||||
|
||||
|
|
||||
|
||||
@@ -176,8 +224,8 @@ ZFS is not available with |CL| because of copyright and licensing
|
||||
complexities. BTRFS is an alternative filesystem that is available in |CL|
|
||||
natively.
|
||||
|
||||
A user on GitHub notes that the ZFS kernel module can be compiled, built, and
|
||||
installed manually: https://github.com/clearlinux/distribution/issues/631
|
||||
A user on GitHub notes that the `ZFS kernel module can be compiled, built, and
|
||||
installed manually <https://github.com/clearlinux/distribution/issues/631>`_.
|
||||
|
||||
|
|
||||
|
||||
|
||||
@@ -53,10 +53,11 @@ help:
|
||||
|
||||
clean:
|
||||
rm -rf $(BUILDDIR)/*
|
||||
rm -rf reference/bundles/*.txt
|
||||
|
||||
htmlall:
|
||||
htmlall:
|
||||
$(SPHINXBUILD) -b html $(ERROROPTS) $(ALLSPHINXOPTS) $(BUILDDIR)/html
|
||||
$(SPHINXBUILD) -b html $(ERROROPTS) -D language='zh_CN' $(ALLSPHINXOPTS) $(BUILDDIR)/html/zh_CN
|
||||
$(SPHINXBUILD) -b html $(ERROROPTS) -D language='zh_CN' $(ALLSPHINXOPTS) $(BUILDDIR)/zh_CN
|
||||
|
||||
htmlde:
|
||||
$(SPHINXBUILD) -b html -D language='de' $(ALLSPHINXOPTS) $(BUILDDIR)/html/de
|
||||
|
||||
|
Before Width: | Height: | Size: 196 KiB |
|
Before Width: | Height: | Size: 84 KiB After Width: | Height: | Size: 75 KiB |
|
Before Width: | Height: | Size: 75 KiB After Width: | Height: | Size: 15 KiB |
|
Before Width: | Height: | Size: 15 KiB After Width: | Height: | Size: 34 KiB |
|
Before Width: | Height: | Size: 34 KiB After Width: | Height: | Size: 59 KiB |
|
Before Width: | Height: | Size: 36 KiB After Width: | Height: | Size: 45 KiB |
|
Before Width: | Height: | Size: 45 KiB After Width: | Height: | Size: 46 KiB |
|
Before Width: | Height: | Size: 46 KiB After Width: | Height: | Size: 58 KiB |
|
Before Width: | Height: | Size: 44 KiB After Width: | Height: | Size: 42 KiB |
|
Before Width: | Height: | Size: 53 KiB After Width: | Height: | Size: 77 KiB |
|
Before Width: | Height: | Size: 94 KiB After Width: | Height: | Size: 80 KiB |
|
Before Width: | Height: | Size: 105 KiB After Width: | Height: | Size: 89 KiB |
|
Before Width: | Height: | Size: 16 KiB After Width: | Height: | Size: 80 KiB |
|
Before Width: | Height: | Size: 39 KiB After Width: | Height: | Size: 44 KiB |
|
Before Width: | Height: | Size: 74 KiB After Width: | Height: | Size: 53 KiB |
|
Before Width: | Height: | Size: 74 KiB After Width: | Height: | Size: 94 KiB |
|
Before Width: | Height: | Size: 77 KiB After Width: | Height: | Size: 105 KiB |
|
After Width: | Height: | Size: 16 KiB |
|
After Width: | Height: | Size: 39 KiB |
|
After Width: | Height: | Size: 74 KiB |
|
After Width: | Height: | Size: 74 KiB |
|
After Width: | Height: | Size: 77 KiB |
|
Before Width: | Height: | Size: 64 KiB After Width: | Height: | Size: 70 KiB |
|
Before Width: | Height: | Size: 31 KiB After Width: | Height: | Size: 74 KiB |
|
Before Width: | Height: | Size: 78 KiB After Width: | Height: | Size: 37 KiB |
|
Before Width: | Height: | Size: 80 KiB After Width: | Height: | Size: 45 KiB |
|
Before Width: | Height: | Size: 81 KiB After Width: | Height: | Size: 48 KiB |
|
Before Width: | Height: | Size: 46 KiB After Width: | Height: | Size: 43 KiB |
|
Before Width: | Height: | Size: 46 KiB After Width: | Height: | Size: 57 KiB |
|
Before Width: | Height: | Size: 37 KiB After Width: | Height: | Size: 69 KiB |
|
Before Width: | Height: | Size: 88 KiB After Width: | Height: | Size: 60 KiB |
|
Before Width: | Height: | Size: 43 KiB After Width: | Height: | Size: 64 KiB |
|
Before Width: | Height: | Size: 35 KiB After Width: | Height: | Size: 36 KiB |
|
Before Width: | Height: | Size: 26 KiB After Width: | Height: | Size: 46 KiB |
|
Before Width: | Height: | Size: 93 KiB After Width: | Height: | Size: 39 KiB |
|
Before Width: | Height: | Size: 195 KiB After Width: | Height: | Size: 49 KiB |
|
Before Width: | Height: | Size: 56 KiB After Width: | Height: | Size: 91 KiB |
|
Before Width: | Height: | Size: 42 KiB After Width: | Height: | Size: 43 KiB |
|
Before Width: | Height: | Size: 54 KiB After Width: | Height: | Size: 35 KiB |
|
After Width: | Height: | Size: 56 KiB |
|
Before Width: | Height: | Size: 54 KiB After Width: | Height: | Size: 26 KiB |
|
Before Width: | Height: | Size: 69 KiB After Width: | Height: | Size: 93 KiB |
|
Before Width: | Height: | Size: 85 KiB After Width: | Height: | Size: 195 KiB |
|
Before Width: | Height: | Size: 41 KiB After Width: | Height: | Size: 30 KiB |
|
Before Width: | Height: | Size: 30 KiB After Width: | Height: | Size: 69 KiB |
|
Before Width: | Height: | Size: 94 KiB After Width: | Height: | Size: 85 KiB |
|
Before Width: | Height: | Size: 80 KiB After Width: | Height: | Size: 47 KiB |
|
Before Width: | Height: | Size: 40 KiB After Width: | Height: | Size: 94 KiB |
|
After Width: | Height: | Size: 80 KiB |
|
After Width: | Height: | Size: 40 KiB |
|
After Width: | Height: | Size: 78 KiB |
|
After Width: | Height: | Size: 18 KiB |
|
After Width: | Height: | Size: 71 KiB |
|
After Width: | Height: | Size: 31 KiB |
|
After Width: | Height: | Size: 31 KiB |
|
After Width: | Height: | Size: 27 KiB |
|
After Width: | Height: | Size: 26 KiB |
|
After Width: | Height: | Size: 69 KiB |
|
After Width: | Height: | Size: 95 KiB |
|
After Width: | Height: | Size: 212 KiB |
|
After Width: | Height: | Size: 104 KiB |
|
After Width: | Height: | Size: 237 KiB |
|
After Width: | Height: | Size: 59 KiB |
|
After Width: | Height: | Size: 330 KiB |
|
After Width: | Height: | Size: 163 KiB |
|
After Width: | Height: | Size: 211 KiB |
|
After Width: | Height: | Size: 90 KiB |
|
After Width: | Height: | Size: 228 KiB |
|
After Width: | Height: | Size: 72 KiB |
|
After Width: | Height: | Size: 266 KiB |
|
After Width: | Height: | Size: 128 KiB |
|
After Width: | Height: | Size: 232 KiB |
|
After Width: | Height: | Size: 72 KiB |
|
After Width: | Height: | Size: 248 KiB |
|
After Width: | Height: | Size: 68 KiB |
|
After Width: | Height: | Size: 293 KiB |
|
After Width: | Height: | Size: 157 KiB |
|
After Width: | Height: | Size: 276 KiB |
|
After Width: | Height: | Size: 147 KiB |
|
After Width: | Height: | Size: 231 KiB |
|
After Width: | Height: | Size: 71 KiB |
|
After Width: | Height: | Size: 302 KiB |
|
After Width: | Height: | Size: 249 KiB |
|
After Width: | Height: | Size: 248 KiB |
@@ -0,0 +1,18 @@
|
||||
1) Capture screenshot
|
||||
2) Open in GIMP 2.10
|
||||
3) Select the area of interest
|
||||
4) Copy the selection; take note of X, Y dimensions of the selection
|
||||
5) "File" > "New"
|
||||
- Add 100 extra pixels to X for the "Width"
|
||||
- Add 100 extra pixels to Y for the "Height"
|
||||
- Set "Fill with" to "Transparency"
|
||||
6) Switch from the "Selection" tool to the "Move" tool and move the
|
||||
the top-left corner of the image to 2 squares down and 2 squares across
|
||||
7) Right-click the image and select "Layer" > "Anchor Layer"
|
||||
8) "Filters" > "Decor" > "Light and Shadow" > "Drop Shadow"
|
||||
- X = 20.0
|
||||
- Y = 20.0
|
||||
- Radius = 20.0
|
||||
- Opacity = 0.2
|
||||
|
||||
|
||||
|
Before Width: | Height: | Size: 39 KiB After Width: | Height: | Size: 62 KiB |
|
Before Width: | Height: | Size: 67 KiB After Width: | Height: | Size: 61 KiB |