mirror of
https://github.com/tiyn/wiki.git
synced 2026-05-01 15:41:35 +02:00
Compare commits
10 Commits
58f836b4d4
...
master
| Author | SHA1 | Date | |
|---|---|---|---|
| f990fa6557 | |||
| 456c436e09 | |||
| f2c8027c4d | |||
| 603cecf8c4 | |||
| ede99678ea | |||
| e2e2310b81 | |||
| d3483b952a | |||
| b624010967 | |||
| f8243dc08f | |||
| 7874c37998 |
@@ -16,7 +16,7 @@ These are [Linuxservers Sonarr image](/wiki/docker/linuxserver_-_sonarr.md),
|
||||
### Initial Configuration
|
||||
|
||||
For the initial configuration navigate to `System` and `Status`.
|
||||
Afterward, check if there are any messages.
|
||||
Afterward check if there are any messages.
|
||||
There are probably a few steps that need to be taken to complete the setup.
|
||||
Set the `Download Clients` under `Settings`.
|
||||
For this an instance of a [BitTorrent Client](/wiki/bittorrent.md#clients) can be used.
|
||||
|
||||
@@ -11,7 +11,7 @@ A free and open-source alternative to it is [F-Droid](/wiki/android/f-droid.md)
|
||||
open-source software.
|
||||
|
||||
A list of open-source software options is also available on Alberto Mosconis
|
||||
[Github](/wiki/git_%28general%29.md#server-with-web-interface) repository
|
||||
[Github](/wiki/git_%28general%29.md#server) repository
|
||||
[foss apps](https://github.com/albertomosconi/foss-apps/tree/main).
|
||||
|
||||
Additionally, open-source apps can be installed from source using
|
||||
|
||||
@@ -19,7 +19,7 @@ Gadgetbridge.
|
||||
### Configuration of Devices
|
||||
|
||||
Devices can be added to Gadgetbridge by clicking on the `+` in the main screen.
|
||||
Afterward, the device can simply be paired.
|
||||
Afterward the device can simply be paired.
|
||||
|
||||
A special pairing procedure is needed for Amazfit or Xiaomi devices.
|
||||
The following describes the steps that need to be done.
|
||||
@@ -34,10 +34,10 @@ The following describes the steps that need to be done.
|
||||
phone.
|
||||
- Inside the Gadgetbridge app click on the `+`, find the device and enter the auth key by long
|
||||
pressing on the devices name.
|
||||
Afterward, navigate back to the scanning list.
|
||||
Afterward navigate back to the scanning list.
|
||||
- Pair the device by clicking on the device name.
|
||||
|
||||
Afterward, the device will be paired and connected.
|
||||
Afterward the device will be paired and connected.
|
||||
|
||||
### Add Weather Function
|
||||
|
||||
@@ -49,7 +49,7 @@ An example for this is the [Breezy Weather app](https://github.com/breezy-weathe
|
||||
which is available on the F-Droid store.
|
||||
Install and configure it to your needs.
|
||||
Then check the Gadgetbridge option insdie the Breezy Weather app.
|
||||
Afterward, the weather function will be working.
|
||||
Afterward the weather function will be working.
|
||||
|
||||
In the past an application named
|
||||
[Weather Notification](https://f-droid.org/en/packages/ru.gelin.android.weather.notification/)
|
||||
|
||||
@@ -39,7 +39,7 @@ This guide assumes the default Anki client is used.
|
||||
To change this select `Browse` and then navigate to the `Note Type` the deck to add backwards cards
|
||||
uses.
|
||||
Right click the note type and select `Cards`.
|
||||
Afterward, the cards for backwards learning can be added by `Options` and `Add Card Types...`.
|
||||
Afterward the cards for backwards learning can be added by `Options` and `Add Card Types...`.
|
||||
You can confirm the fields have been setup correctly by clicking through the card types and
|
||||
verifying it.
|
||||
|
||||
|
||||
@@ -18,7 +18,7 @@ converted to BetterDiscord.
|
||||
betterdiscordctl install
|
||||
```
|
||||
|
||||
Afterward, BetterDiscord can be kept up to date with the following command.
|
||||
Afterward BetterDiscord can be kept up to date with the following command.
|
||||
|
||||
```sh
|
||||
betterdiscordctl self-upgrade
|
||||
|
||||
@@ -53,7 +53,7 @@ Then press `Recalculate all author sort values` for the change to take effect.
|
||||
titles.
|
||||
Setting `title_series_sorting = 'strictly_alphabetic'` will use the standard
|
||||
title and wont make articles of titles suffixes.
|
||||
Afterward, select all books, right-click and select `Edit metadata in bulk`
|
||||
Afterward select all books, right-click and select `Edit metadata in bulk`
|
||||
under `Edit metadata`.
|
||||
Then check the box `update title sort` and press `Ok` to update all sort titles.
|
||||
|
||||
@@ -80,13 +80,13 @@ After a while calibre should recognize the device which will be apparent by the
|
||||
additional buttons on the top menu like the `Send to device`- and the `Device`-Button.
|
||||
First make sure only the formats you want will be transfered.
|
||||
This can be done by selecting `Device`, `File formats` and checking the formats as needed.
|
||||
Afterward, select the books and press `Send to device` to start the process of transfering the
|
||||
Afterward select the books and press `Send to device` to start the process of transfering the
|
||||
devices.
|
||||
Alternatively only specific formats of the books can be send to the device by selecting
|
||||
`Send specific format to` and `Main memory` under the `Send to device` menu.
|
||||
If there are books that contain series metadata make sure to disconnect the e-reader once and
|
||||
reconnect it.
|
||||
Afterward, select `Update cached metadata on device` under `Device` to update the metadata
|
||||
Afterward select `Update cached metadata on device` under `Device` to update the metadata
|
||||
including the series.
|
||||
Finally, disconnect the device.
|
||||
|
||||
@@ -98,7 +98,7 @@ It is recommended to convert `.mobi` and `.epub` files to a `.kepub` file before
|
||||
[transfering it to a Kobo device](#transfer-books-to-a-device).
|
||||
For this the Plugin `KePub Output` by Joel Goguen [can be added](#adding-a-plugin) can be
|
||||
installed.
|
||||
Afterward, books can be converted the normal way, but now the output format `.kepub` is available.
|
||||
Afterward books can be converted the normal way, but now the output format `.kepub` is available.
|
||||
Additionally, the `Kobo Touch Extended` plugin is recommended to use since it makes sending books
|
||||
to Kobo e-readers easier.
|
||||
Finally, `KePub Metadata Reader` and `KePub Metadata Reader` make it possible to read and write
|
||||
|
||||
@@ -9,7 +9,7 @@ Change the settings according to your needs.
|
||||
Create the volume for the configuration files by running the command `docker volume create
|
||||
gameyfin_config`.
|
||||
Make sure to run the following command on the config volume `chown -R 1000:root gameyfin_config`.
|
||||
Afterward, run `./rebuild.sh`.
|
||||
Afterward run `./rebuild.sh`.
|
||||
|
||||
### Environment-variables
|
||||
|
||||
|
||||
@@ -80,7 +80,7 @@ For this set the server type by using the `-e TYPE=<type>` flag.
|
||||
Most notably this value could be `FABRIC` or `FORGE`.
|
||||
After this the mods (as `.jar` files) can be placed in the `mods` directory of the
|
||||
[Docker](/wiki/docker.md) volume.
|
||||
Afterward, run the [`rebuild.sh`](#rebuildsh) to restart the server with loaded mods.
|
||||
Afterward run the [`rebuild.sh`](#rebuildsh) to restart the server with loaded mods.
|
||||
|
||||
#### Installing Datapacks
|
||||
|
||||
|
||||
143
wiki/docker/kohakuhub_-_kohakuhub.md
Normal file
143
wiki/docker/kohakuhub_-_kohakuhub.md
Normal file
@@ -0,0 +1,143 @@
|
||||
# kohakuhub - kohakuhub
|
||||
|
||||
This is a [Docker](/wiki/docker.md) container for a
|
||||
[KohakuHub](https://github.com/KohakuBlueleaf/KohakuHub) server.
|
||||
The Server consists of multiple Docker containers.
|
||||
These are containers for the KohakuHub API and - depending on configuration - MinIO, LakeFS,
|
||||
[Postgres](/wiki/docker/postgres.md)
|
||||
|
||||
## Set-up
|
||||
|
||||
Create the files `rebuild.sh` and `docker-compose.yml` at the same place.
|
||||
The file `docker-compose.yml` is usually created automatically.
|
||||
For this first download the [repository](https://github.com/KohakuBlueleaf/KohakuHub).
|
||||
Then run the following command to generate the `docker-compose.yml` file.
|
||||
|
||||
```sh
|
||||
python scripts/generate_docker_compose.py
|
||||
```
|
||||
|
||||
Alternatively the example file `docker-compose.example.yml` file can be copied.
|
||||
An additional example can be found in the [corresponding section](#docker-composeyml).
|
||||
Change the settings according to your needs and run `./rebuild.sh` afterwards.
|
||||
|
||||
To publish the page on a domain the nginx container usually called `hub-ui` has to be published -
|
||||
for example using a reverse proxy like
|
||||
[traefik](/wiki/traefik.md#reverse-proxies-for-docker-service).
|
||||
|
||||
### Environment Variables
|
||||
|
||||
Set the following environment-variables in the `environment:` section of the
|
||||
docker-compose file.
|
||||
There are many other environment variables, which are automatically generated and not listed here.
|
||||
|
||||
| Name | Usage | Default |
|
||||
| ----------------------------------------- | ------------------------------------ | ------- |
|
||||
| `KOHAKU_HUB_INVITATION_ONLY` | Will disable public registration | false |
|
||||
|
||||
### Volumes
|
||||
|
||||
There are some volumes, which are automatically generated and not listed here.
|
||||
|
||||
### Ports
|
||||
|
||||
There are no ports, which are exposed by default.
|
||||
|
||||
### rebuild.sh
|
||||
|
||||
```sh
|
||||
#!/bin/sh
|
||||
docker-compose down
|
||||
docker-compose up -d
|
||||
```
|
||||
|
||||
### docker-compose.yml
|
||||
|
||||
```yml
|
||||
services:
|
||||
hub-ui:
|
||||
image: nginx:alpine
|
||||
restart: always
|
||||
volumes:
|
||||
- ./src/kohaku-hub-ui/dist:/usr/share/nginx/html
|
||||
- ./src/kohaku-hub-admin/dist:/usr/share/nginx/html-admin
|
||||
- ./docker/nginx/default.conf:/etc/nginx/conf.d/default.conf
|
||||
depends_on:
|
||||
- hub-api
|
||||
|
||||
hub-api:
|
||||
build: .
|
||||
restart: always
|
||||
depends_on:
|
||||
- postgres
|
||||
- lakefs
|
||||
- minio
|
||||
environment:
|
||||
- KOHAKU_HUB_INVITATION_ONLY=true
|
||||
- KOHAKU_HUB_BASE_URL=https://hub.sub.domain.tld
|
||||
- KOHAKU_HUB_S3_PUBLIC_ENDPOINT=https://s3.sub.domain.tld
|
||||
- KOHAKU_HUB_SESSION_SECRET=CHANGE_ME_SESSION_SECRET
|
||||
- KOHAKU_HUB_ADMIN_SECRET_TOKEN=CHANGE_ME_ADMIN_TOKEN
|
||||
- KOHAKU_HUB_DATABASE_KEY=CHANGE_ME_DATABASE_KEY
|
||||
- KOHAKU_HUB_DB_BACKEND=postgres
|
||||
- KOHAKU_HUB_DATABASE_URL=postgresql://user:password@postgres:5432/database
|
||||
- KOHAKU_HUB_S3_ENDPOINT=http://minio:9000
|
||||
- KOHAKU_HUB_S3_ACCESS_KEY=CHANGE_ME_S3_ACCESS_KEY
|
||||
- KOHAKU_HUB_S3_SECRET_KEY=CHANGE_ME_S3_SECRET_KEY
|
||||
- KOHAKU_HUB_S3_BUCKET=example-bucket
|
||||
- KOHAKU_HUB_S3_REGION=us-east-1
|
||||
- KOHAKU_HUB_LAKEFS_ENDPOINT=http://lakefs:28000
|
||||
- KOHAKU_HUB_LAKEFS_REPO_NAMESPACE=example
|
||||
- KOHAKU_HUB_SITE_NAME=ExampleHub
|
||||
- KOHAKU_HUB_AUTO_MIGRATE=true
|
||||
volumes:
|
||||
- ./hub-meta/hub-api:/hub-api-creds
|
||||
|
||||
minio:
|
||||
image: quay.io/minio/minio:latest
|
||||
command: server /data --console-address ":29000"
|
||||
restart: unless-stopped
|
||||
environment:
|
||||
- MINIO_ROOT_USER=CHANGE_ME_MINIO_USER
|
||||
- MINIO_ROOT_PASSWORD=CHANGE_ME_MINIO_PASSWORD
|
||||
volumes:
|
||||
- ./hub-storage/minio-data:/data
|
||||
- ./hub-meta/minio-data:/root/.minio
|
||||
|
||||
lakefs:
|
||||
build:
|
||||
context: ./docker/lakefs
|
||||
entrypoint: ["/bin/sh", "/scripts/lakefs-entrypoint.sh"]
|
||||
command: ["run"]
|
||||
restart: unless-stopped
|
||||
depends_on:
|
||||
- minio
|
||||
- postgres
|
||||
environment:
|
||||
- LAKEFS_DATABASE_TYPE=postgres
|
||||
- LAKEFS_DATABASE_POSTGRES_CONNECTION_STRING=postgres://user:password@postgres:5432/lakefs?sslmode=disable
|
||||
- LAKEFS_BLOCKSTORE_TYPE=s3
|
||||
- LAKEFS_BLOCKSTORE_S3_ENDPOINT=http://minio:9000
|
||||
- LAKEFS_BLOCKSTORE_S3_BUCKET=example-bucket
|
||||
- LAKEFS_BLOCKSTORE_S3_FORCE_PATH_STYLE=true
|
||||
- LAKEFS_BLOCKSTORE_S3_CREDENTIALS_ACCESS_KEY_ID=CHANGE_ME_S3_ACCESS_KEY
|
||||
- LAKEFS_BLOCKSTORE_S3_CREDENTIALS_SECRET_ACCESS_KEY=CHANGE_ME_S3_SECRET_KEY
|
||||
- LAKEFS_BLOCKSTORE_S3_REGION=us-east-1
|
||||
- LAKEFS_AUTH_ENCRYPT_SECRET_KEY=CHANGE_ME_LAKEFS_SECRET
|
||||
- LAKEFS_LISTEN_ADDRESS=0.0.0.0:28000
|
||||
volumes:
|
||||
- ./hub-meta/lakefs-data:/var/lakefs/data
|
||||
- ./hub-meta/lakefs-cache:/lakefs/data/cache
|
||||
- ./docker/lakefs/lakefs-entrypoint.sh:/scripts/lakefs-entrypoint.sh:ro
|
||||
- ./docker/lakefs/init-databases.sh:/scripts/init-databases.sh:ro
|
||||
|
||||
postgres:
|
||||
image: postgres:15
|
||||
restart: always
|
||||
environment:
|
||||
- POSTGRES_USER=user
|
||||
- POSTGRES_PASSWORD=password
|
||||
- POSTGRES_DB=database
|
||||
volumes:
|
||||
- ./hub-meta/postgres-data:/var/lib/postgresql/data
|
||||
```
|
||||
@@ -20,7 +20,7 @@ docker run -v openvpn:/etc/openvpn --rm kylemanna/openvpn ovpn_genconfig -u udp:
|
||||
docker run -v openvpn:/etc/openvpn --rm -it kylemanna/openvpn ovpn_initpki
|
||||
```
|
||||
|
||||
Afterward, run `./rebuild.sh`.
|
||||
Afterward run `./rebuild.sh`.
|
||||
|
||||
### Volumes
|
||||
|
||||
|
||||
@@ -35,7 +35,7 @@ And finally generate the DCIM keys and rebuild once again.
|
||||
Finally, if a reverse proxy is used check the
|
||||
[traefik entry](/wiki/docker/traefik.md#setup-mailserver) or the [nginx entry](/wiki/nginx.md).
|
||||
|
||||
Afterward, you're ready to go by once again running the `rebuild.sh` file.
|
||||
Afterward you're ready to go by once again running the `rebuild.sh` file.
|
||||
|
||||
If setting up this mailserver with [Traefik](/wiki/traefik.md) as a reverse proxy some additional
|
||||
steps should be taken.
|
||||
|
||||
@@ -9,7 +9,7 @@ The official container and documentation was made by
|
||||
|
||||
Create the file `rebuild.sh`.
|
||||
Change the settings according to your needs and run `./rebuild.sh` afterward.
|
||||
Afterward, you need to create a user.
|
||||
Afterward you need to create a user.
|
||||
This can be done by running the following line with changed credentials:
|
||||
|
||||
```sh
|
||||
|
||||
@@ -29,7 +29,7 @@ For the Gnome Keyring install the [packages](/wiki/linux/package_manager.md) `li
|
||||
`gnome-keyring`.
|
||||
The name may differ slightly depending on the [package manager](/wiki/linux/package_manager.md)
|
||||
used.
|
||||
Afterward, make sure to run the service and enable it if not already done.
|
||||
Afterward make sure to run the service and enable it if not already done.
|
||||
An example for this is shown in the following command
|
||||
|
||||
```sh
|
||||
|
||||
@@ -45,7 +45,7 @@ First set up Syncthing as described in the
|
||||
If a system with only user access - like the [Steam Deck](/wiki/game/steam_deck.md) - is used the
|
||||
[user space configuration](/wiki/syncthing.md#user-space-configuration-for-linux)
|
||||
is recommended.
|
||||
Afterward, move the game saves to the directory set up by Syncthing and create
|
||||
Afterward move the game saves to the directory set up by Syncthing and create
|
||||
[symbolic links](/wiki/linux/shell.md#symbolic-links-using-ln) to link them back to the original
|
||||
place.
|
||||
|
||||
|
||||
@@ -25,7 +25,7 @@ Some installations require the swapping of discs during the installation.
|
||||
An easy way around this is to mount the [ISO image](/wiki/linux/iso_image.md#mounting) and copy
|
||||
them into another directory.
|
||||
This way the files from two discs can be put in one folder.
|
||||
Afterward, follow the installation as usual.
|
||||
Afterward follow the installation as usual.
|
||||
|
||||
If a setup executable is available select `Install a Windows game from media`.
|
||||
Then select the setup executable from the mounted path.
|
||||
@@ -87,7 +87,7 @@ the [documentation of Lutris](https://github.com/lutris/docs/blob/master/Perform
|
||||
It is important to install both the 64-bit and the 32-bit version to ensure full functionality.
|
||||
Check the package manager of your distribution for packages with the names `gamemode` and
|
||||
`lib32-gamemode` or similar names or install it manually via git.
|
||||
Afterward, check in Lutris `Preferences` if `Enable Feral GameMode` is checked under the
|
||||
Afterward check in Lutris `Preferences` if `Enable Feral GameMode` is checked under the
|
||||
`Global options` tab.
|
||||
|
||||
Another way to increase the performance is to increase the
|
||||
@@ -118,7 +118,7 @@ For disabling networking for a command the program
|
||||
In Lutris after the installation of firejail right-click the game to disable networking on.
|
||||
Select `Configure` and navigate to `System Options`.
|
||||
Enable `Advanced` and insert `firejail --net=none --noprofile` into the `command prefix` field.
|
||||
Afterward, all networking of the selected game is disabled.
|
||||
Afterward all networking of the selected game is disabled.
|
||||
|
||||
### Adding and Removing Runners and Sources
|
||||
|
||||
|
||||
@@ -32,7 +32,7 @@ appended to the command used for starting the emulator needed for it.
|
||||
This should be made in quotation marks as it could contain characters that need
|
||||
to be escaped.
|
||||
|
||||
Afterward, the icons and banners of it can be set using
|
||||
Afterward the icons and banners of it can be set using
|
||||
[SteamGridDB](/wiki/game/steam.md#setting-icons-and-banners-for-games).
|
||||
|
||||
### Plugin Manager Decky
|
||||
@@ -42,7 +42,7 @@ Some of these options can be accessed by installing
|
||||
[the plugin manager Decky](https://github.com/SteamDeckHomebrew/decky-loader).
|
||||
To install it download the setup file from the
|
||||
[GitHub page](https://github.com/SteamDeckHomebrew/decky-loader) and run it.
|
||||
Afterward, the plugin manager will be available after pressing the `...` button on the Deck and
|
||||
Afterward the plugin manager will be available after pressing the `...` button on the Deck and
|
||||
navigating to the bottom of the menu.
|
||||
There plugins can be installed and removed aswell as managed.
|
||||
|
||||
|
||||
@@ -16,36 +16,41 @@ has a [separate article](/wiki/linux/git_%28package%29.md).
|
||||
### Server
|
||||
|
||||
The server hosts the data that is needed for the versioning.
|
||||
A distinction can be made between
|
||||
[GUI-less servers](#server-without-graphical-interface) and
|
||||
[servers with a web-GUI](#server-with-web-interface).
|
||||
There are many different [server](#server) which also have
|
||||
[distinct applications](#distinct-git-server-apps) other than the normal [client](#client).
|
||||
|
||||
#### Server with web interface
|
||||
#### Server
|
||||
|
||||
Web interfaces for git are quite useful for easily showing code to other people.
|
||||
Additionally, it is easy to collaborate together.
|
||||
|
||||
- [Gitea](gitea.md) is an open-source and selfhosted git instance which can be dockerized.
|
||||
- [Gitea](gitea.md) is an open-source and self-hosted git instance which can be
|
||||
[dockerized](/wiki/docker/gitea_-_gitea.md).
|
||||
It has a graphical user interface.
|
||||
- [GitHub](https://github.com) is a popular git server.
|
||||
It is not selfhosted and owned by microsoft ([cli-tool](https://github.com/github/hub)).
|
||||
It is not self-hosted and owned by Microsoft.
|
||||
It has a graphical user interface.
|
||||
- [GitLab](https://gitlab.com) is a self-hostable git instance which also has a default version
|
||||
available via their website.
|
||||
|
||||
#### Git Apps
|
||||
|
||||
Depending on the [specific server](#server-with-web-interface) used there are many different apps
|
||||
that can be used.
|
||||
|
||||
- For [GitHub](https://github.com) there is app with the same name for
|
||||
[Android](/wiki/android.md) devices and iOS devices.
|
||||
- For [Gitea](/wiki/gitea.md) and Forgejo there is an app called [GitNex](https://gitnex.com) which
|
||||
is available for [Android](/wiki/android.md) devices.
|
||||
- For [GitLab](https://gitlab.com) there is an app called [LabNex](https://labnex.app) which is
|
||||
available for [Android](/wiki/android.md) devices.
|
||||
|
||||
#### Server without graphical interface
|
||||
|
||||
If you don't need a bloated web-interface a more basic approach is more than enough.
|
||||
|
||||
It has a graphical user interface.
|
||||
- [git-server-docker](/wiki/docker/jkarlos_-_git-server-docker.md) is a pretty
|
||||
basic docker-container for git.
|
||||
It does not have a graphical user interface.
|
||||
|
||||
If a solution for storing datasets or AI models is needed [KohakuHub](/wiki/kohakuhub.md) is
|
||||
available and uses similar techniques of storage and versioning although it is not a Git server.
|
||||
|
||||
#### Distinct Git Server Apps
|
||||
|
||||
Depending on the [specific server](#server) used there are many different apps
|
||||
that can be used.
|
||||
The normal git [clients](#client) can be used for all of them.
|
||||
|
||||
- [GitHub](https://github.com) features various apps with the same name for
|
||||
[Android](/wiki/android.md) and iOS devices.
|
||||
- [hub](https://github.com/github/hub) is an official command-line tool for
|
||||
[GitHub](https://github.com).
|
||||
- [GitNex](https://gitnex.com) is an app for [Android](/wiki/android.md) devices which can access
|
||||
[Gitea](/wiki/gitea.md) and Forgejo instances.
|
||||
- [LabNex](https://labnex.app) is an app for [Android](/wiki/android.md) devices which can access
|
||||
[GitLab](https://gitlab.com) instances.
|
||||
|
||||
@@ -14,7 +14,7 @@ command is called `gpclient` which can sometimes lead to confusion.
|
||||
|
||||
The usage of the GlobalProtect client is pretty simple.
|
||||
After starting the program the portal address has to be added and is followed by a login.
|
||||
Afterward, the client will connect.
|
||||
Afterward the client will connect.
|
||||
|
||||
The standard command to connect to a [VPN](/wiki/vpn.md) server is the following where
|
||||
`<vpn-server>` is the domain of the server (for example `vpn.abc.de`).
|
||||
|
||||
@@ -9,7 +9,7 @@ An example for a system that uses it is
|
||||
Depending on the system and the type of access various things may have to be setup.
|
||||
For Ubuntu systems like the [Raspberry Pi](/wiki/linux/raspberry_pi.md) these are often named
|
||||
`hailort-pcie-driver` and `hailort`.
|
||||
When using the [Python prorgamming language](/wiki/programming_language/python.md) refer to the
|
||||
When using the [Python programming language](/wiki/programming_language/python.md) refer to the
|
||||
[Hailo section](/wiki/programming_language/python.md#hailo).
|
||||
|
||||
## Usage
|
||||
@@ -26,11 +26,11 @@ This section assumes the neural network is using
|
||||
|
||||
To convert TensorFlow models first the Hailo 8 Software Suite needs to be downloaded.
|
||||
This can be done from the [official website](https://hailo.ai/developer-zone/software-downloads/)
|
||||
altough an account is needed for it.
|
||||
although, an account is needed for it.
|
||||
|
||||
After downloading, extracting and then navigating into the folder a heavily customized
|
||||
[Docker](/wiki/docker.md) container can be started by running the following command.
|
||||
However it is recommended to slightly modify this file.
|
||||
However, it is recommended to slightly modify this file.
|
||||
Add a volume that contains the TensorFlow model, that is to be converted, to the environment
|
||||
variable `DOCKER_ARGS` which is set in the file `hailo_ai_sw_suite_docker_run.sh`.
|
||||
|
||||
@@ -41,11 +41,11 @@ variable `DOCKER_ARGS` which is set in the file `hailo_ai_sw_suite_docker_run.sh
|
||||
Using the tools which come in this container a `.tf` or `.tflite` model can be converted to the
|
||||
`.hef` format.
|
||||
At the current time only models using `float32` or `float16` are supported.
|
||||
`int8` and `int32` are not supported.
|
||||
Mixed precision models are not supported aswell.
|
||||
`int8` and `int32` are not supported.
|
||||
Mixed precision models are not supported as well.
|
||||
|
||||
For this to work run the following commands inside the Docker container.
|
||||
The first command takes the path to the tensorflow model (`<path-to-tf-model>`) and will output a
|
||||
The first command takes the path to the TensorFlow model (`<path-to-tf-model>`) and will output a
|
||||
`.har` model.
|
||||
The second command is optional but recommended and takes the path to this `.har` model
|
||||
(`<path-to-har-model`) and returns an optimized `.har` model.
|
||||
@@ -68,7 +68,7 @@ the input format.
|
||||
hailo optimize --calib-set-path <data-set> <path-to-har-model>
|
||||
```
|
||||
|
||||
Note that the user in the Docker container usually uses anothr UID and GID.
|
||||
Note that the user in the Docker container usually uses another UID and GID.
|
||||
To make the volume and files accessible inside the container the IDs of the files in the volume
|
||||
should be changed accordingly - for example as shown in the following example.
|
||||
`<volume-path>` is the path that points to the volume
|
||||
@@ -79,7 +79,7 @@ and `<gid>` the GID of the Docker user - which can be found using `id -g` (for e
|
||||
chown -R <uid>:<gid> <volume-path>
|
||||
```
|
||||
|
||||
After the models have been converted it can be reversed using the systems user UID and GID.
|
||||
After the models have been converted it can be reversed using the user UID and GID of the system.
|
||||
|
||||
The converted models can than be run using the Python programming language as described in the
|
||||
[Python article](/wiki/programming_language/python.md#hailo).
|
||||
|
||||
14
wiki/hierarchical_data_format.md
Normal file
14
wiki/hierarchical_data_format.md
Normal file
@@ -0,0 +1,14 @@
|
||||
# Hierarchical Data Format
|
||||
|
||||
Hierarchical Data Format - or in short HDF - is a file format to organize data in a hierarchical
|
||||
way.
|
||||
|
||||
## Viewer
|
||||
|
||||
There are various possible viewers for `.hdf` files.
|
||||
The following list contains some of them.
|
||||
|
||||
- [HDFView](https://github.com/HDFGroup/hdfview) is a graphical viewer for `.hdf` files.
|
||||
It also features the ability to plot data.
|
||||
- [ViTables](https://github.com/uvemas/ViTables) is a graphical viewer for `.hdf` files.
|
||||
Contrary to other viewers it does not feature plotting data and is relatively simple.
|
||||
@@ -28,7 +28,7 @@ To convert handwriting to a vector graphic an image of the writing should first
|
||||
Inkscape.
|
||||
First the levels of black and white can be changed by using `Extensions > Raster > Levels` and
|
||||
changing the values for white and black points.
|
||||
Afterward, the bitmap should be traced.
|
||||
Afterward the bitmap should be traced.
|
||||
For this select `Path > Trace Bitmap` and change the values in the Detection mode
|
||||
`Brightness cutoff` until it matches your expectations.
|
||||
After this the image has been converted to a bitmap, but most of the times it is not smooth and has
|
||||
|
||||
@@ -26,6 +26,6 @@ Paste this in the \*ARR application under
|
||||
`Settings`, `Indexers`, `Add`, `Torznab` and `Custom` in the `URL` field.
|
||||
Also copy and paste the Jackett API key into the corresponding field in the
|
||||
\*ARR application.
|
||||
Afterward, check and configure the correct category IDs via the `Categories` option.
|
||||
Afterward check and configure the correct category IDs via the `Categories` option.
|
||||
The list of supported categories can be found in the Jackett indexer
|
||||
configuration (the wrench in the corresponding index list entry).
|
||||
|
||||
@@ -35,7 +35,7 @@ In the [TVHeadend entry](/wiki/tvheadend.md) a guide to run an instance is given
|
||||
In the admin dashboard install the
|
||||
[TVHeadend plugin](https://jellyfin.org/docs/general/server/plugins/tvheadend/)
|
||||
and restart the server.
|
||||
Afterward, create a user with a username in TVHeadend under
|
||||
Afterward create a user with a username in TVHeadend under
|
||||
`Go to Configuration > Users > Access Entries > Add`.
|
||||
Check the `Change Parameters`
|
||||
`Rights`, `Channel number range`, `Channel tags`, `DVR configurations`,
|
||||
@@ -49,7 +49,7 @@ Select `Basic`, `Advanced` and `HTSP` under `Streaming` and `Basic`, `HTSP` and
|
||||
Save the user.
|
||||
Create a password via `Configuration > Users > Passwords > Add`.
|
||||
Check `Enabled`, select the according `Username` and fill in the `Password`.
|
||||
Afterward, save.
|
||||
Afterward save.
|
||||
|
||||
Now in Jellyfin under `Go to Dashboard > Plugins > TVHeadend > Settings` set
|
||||
the `TVHeadend Hostname or IP Address`, the `HTTP Port` and `HTSP Port`, the
|
||||
@@ -57,7 +57,7 @@ the `TVHeadend Hostname or IP Address`, the `HTTP Port` and `HTSP Port`, the
|
||||
|
||||
Finally, run `Refresh Guide Data` under `Dashboard > Live TV > Live TV` to load
|
||||
the guide data for the next 7 days aswell as to refresh the TV channels.
|
||||
Afterward, the channels [mapped in TVHeadend](/wiki/tvheadend.md#adding-channels)
|
||||
Afterward the channels [mapped in TVHeadend](/wiki/tvheadend.md#adding-channels)
|
||||
should appear in the `Live TV` Library.
|
||||
|
||||
### Client
|
||||
|
||||
11
wiki/kohakuhub.md
Normal file
11
wiki/kohakuhub.md
Normal file
@@ -0,0 +1,11 @@
|
||||
# KohakuHub
|
||||
|
||||
[KohakuHub](https://hub.kohaku-lab.org/) is a self-hostable platform for AI models and datasets for
|
||||
AI models.
|
||||
It can be used as an alternative to the very popular service called
|
||||
[HuggingFace](https://huggingface.co/).
|
||||
|
||||
## Setup
|
||||
|
||||
The software can be setup via [Docker](/wiki/docker.md) with the
|
||||
[kohakuhub image](/wiki/docker/kohakuhub_-_kohakuhub.md).
|
||||
@@ -31,4 +31,4 @@ When first starting LibreOffice may appear not to start.
|
||||
This is because problems with hardware acceleration can occur on some systems.
|
||||
It can starting the software in safe mode, navigate to the `Settings` by the `Tools` tab.
|
||||
Then select `LibreOffice` and `View` and remove the check in `Use hardware acceleration`.
|
||||
Afterward, LibreOffice can be closed and reopened without selecting the safe mode.
|
||||
Afterward LibreOffice can be closed and reopened without selecting the safe mode.
|
||||
|
||||
@@ -1,35 +1,30 @@
|
||||
# Arch Linux
|
||||
|
||||
[Arch Linux](https://archlinux.org/) is a rolling-release, general-purpose
|
||||
[Linux](/wiki/linux.md)
|
||||
[Arch Linux](https://archlinux.org/) is a rolling-release, general-purpose [Linux](/wiki/linux.md)
|
||||
distribution.
|
||||
The package manager of Arch Linux is generally
|
||||
[Pacman and various possible AUR ones](/wiki/linux/package_manager/pacman_and_aur.md).
|
||||
|
||||
## Package Manager and AUR
|
||||
|
||||
Arch Linux uses the
|
||||
[pacman](/wiki/linux/package_manager/pacman_and_aur.md) package
|
||||
manager.
|
||||
Arch Linux uses the [pacman](/wiki/linux/package_manager/pacman_and_aur.md) package manager.
|
||||
An additional repository for user made software exists.
|
||||
It is called Arch User Repository (AUR).
|
||||
The Arch User Repositories (AUR) features community-made packages that can be
|
||||
installed with different
|
||||
[package manager for that purpose](/wiki/linux/package_manager/pacman_and_aur.md).
|
||||
The Arch User Repositories (AUR) features community-made packages that can be installed with
|
||||
different [package manager for that purpose](/wiki/linux/package_manager/pacman_and_aur.md).
|
||||
|
||||
## Installation
|
||||
|
||||
The installation of a basic Arch Linux system is described in the
|
||||
[installation entry](/wiki/linux/arch-linux/installation.md).
|
||||
The entry features a guide to install a system with a X server setup aswell as
|
||||
programs for the most used tasks on a system.
|
||||
The entry features a guide to install a system with a X server setup as well as programs for the
|
||||
most used tasks on a system.
|
||||
|
||||
### Create Installation Medium
|
||||
|
||||
For the installation usage of a simple USB key is advised.
|
||||
This has to be flashed with the Arch ISO.
|
||||
The ISO file can be found on the
|
||||
[official website](https://www.archlinux.org/download/).
|
||||
The ISO file can be found on the [official website](https://www.archlinux.org/download/).
|
||||
The iso can be written on an USB-stick using the command
|
||||
`dd bs=4M if=<path to ISO> of=/dev/sdx conv=fsync oflag=direct status=progress`.
|
||||
`<path to ISO>` points the command to the location of the ISO file.
|
||||
@@ -39,21 +34,21 @@ Alternatively a [Ventoy stick can be created](/wiki/ventoy.md) which can contain
|
||||
|
||||
## Usage
|
||||
|
||||
The following section describes various ways to use and improve the usage of
|
||||
the Arch Linux operating system.
|
||||
The following section describes various ways to use and improve the usage of the Arch Linux
|
||||
operating system.
|
||||
|
||||
### Recommended Practices
|
||||
|
||||
The following articles describe steps to undertake to harden the system security
|
||||
or setups and installation that are recommended for Arch Linux.
|
||||
The following articles describe steps to undertake to harden the system security or setups and
|
||||
installation that are recommended for Arch Linux.
|
||||
|
||||
#### Enable Microcode Updates
|
||||
|
||||
The microcode of Intel and AMD CPUs can be automatically updated by installing
|
||||
the `amd-ucode` or `intel-ucode` package depending on your CPU.
|
||||
The microcode of Intel and AMD CPUs can be automatically updated by installing the `amd-ucode` or
|
||||
`intel-ucode` package depending on your CPU.
|
||||
Not all processors are supported, especially old ones can lead to problems.
|
||||
It has to be confirmed that the processor is supported, if this is not the case
|
||||
is possible for the next steps to break the functionality of the bootloader.
|
||||
It has to be confirmed that the processor is supported, if this is not the case is possible for
|
||||
the next steps to break the functionality of the bootloader.
|
||||
|
||||
The following part assumes the system is installed with
|
||||
[UEFI bootloader](/wiki/linux/arch-linux/installation.md#10-install-and-configure-uefi-bootloader)
|
||||
@@ -78,23 +73,23 @@ To access the files of the system an Arch Linux boot stick has to be created as
|
||||
[a previous section](#create-installation-medium).
|
||||
After booting into it set your keymap layout using the `loadkeys` setup similar to
|
||||
[the installation preparation](/wiki/linux/arch-linux/installation.md#1-preparation).
|
||||
Afterward, [mount](/wiki/linux/disk-management.md#mounting) the partition that contains the root
|
||||
Afterward [mount](/wiki/linux/disk-management.md#mounting) the partition that contains the root
|
||||
file system to the `/mnt` directory.
|
||||
It is possible that LUKS encrypted file systems need to be
|
||||
[opened](/wiki/linux/dm-crypt.md#openclose-an-encrypted-volume) and then mounted using the
|
||||
`/dev/mapper` symbolic link.
|
||||
On some systems there are home or boot file system that have to be mounted on `/mnt/boot` or
|
||||
`/mnt/home` after mounting the root file system.
|
||||
Afterward, use `arch-chroot /mnt` to get into the not bootable system.
|
||||
Afterward use `arch-chroot /mnt` to get into the not bootable system.
|
||||
Now the command line of the system can be accessed for troubleshooting.
|
||||
After troubleshooting `exit` the system and [unmount](/wiki/linux/disk-management.md#mounting) all previously
|
||||
mounted file systems and try to boot back into the system.
|
||||
After troubleshooting `exit` the system and [unmount](/wiki/linux/disk-management.md#mounting) all
|
||||
previously mounted file systems and try to boot back into the system.
|
||||
|
||||
If the system broke during an update then the easiest way to fix it, is by running the same update
|
||||
command again.
|
||||
The used command can be found in `/var/log/pacman.log`.
|
||||
Make sure to run exactly this command.
|
||||
Afterward, try to reboot into the system.
|
||||
Afterward try to reboot into the system.
|
||||
|
||||
Another common source for not bootable systems is
|
||||
[the initial ramdisk](#problems-with-the-initial-ramdisk).
|
||||
@@ -112,11 +107,11 @@ To fix this generate the initial ramdisk manually as described in
|
||||
There is a known problem described in the Arch Linux forums by
|
||||
[TheRealNubby](https://bbs.archlinux.org/viewtopic.php?id=300292) where the system goes into a
|
||||
perceived freeze after the boot process.
|
||||
This problem seems to be most prevalent on systems that use an [Nvidia](/wiki/nvidia.md) GPU
|
||||
since its only known occurences were found on Nvidia GTX 1080 GPUs.
|
||||
This problem seems to be most prevalent on systems that use an [Nvidia](/wiki/nvidia.md) GPU since
|
||||
its only known occurences were found on Nvidia GTX 1080 GPUs.
|
||||
The boot screen will not show any errors and when
|
||||
[troubleshooting using a installation medium](#troubleshooting-setup-for-not-bootable-systems)
|
||||
logs like [the ones of SystemD](/wiki/linux/systemd.md#retrieving-the-systemd-logs) will look
|
||||
logs like [the ones of systemd](/wiki/linux/systemd.md#retrieving-the-systemd-logs) will look
|
||||
normal and won't show any errors.
|
||||
|
||||
In this case there is the possibility that logging into Arch Linux blindly will work.
|
||||
|
||||
@@ -1,7 +1,7 @@
|
||||
# Arch installation with LUKS encryption and LVM
|
||||
|
||||
This guide is based upon a
|
||||
[german arch wiki article](https://wiki.archlinux.de/title/Installation_mit_UEFI_und_Verschl%C3%BCsselung).
|
||||
[German arch wiki article](https://wiki.archlinux.de/title/Installation_mit_UEFI_und_Verschl%C3%BCsselung).
|
||||
For encryption [dm-crypt](/wiki/linux/dm-crypt.md) is used.
|
||||
Inside the encrypted partition a logical volume will be created with
|
||||
[LVM](/wiki/linux/lvm.md).
|
||||
@@ -25,9 +25,9 @@ Ahead of the installation an Arch boot-stick has to be created as described in
|
||||
After that the USB can be plugged in the system on which Arch should be installed.
|
||||
Boot the target system and select `Boot Arch Linux (x86_64)`.
|
||||
|
||||
If you need to set the keyboard layout to anything other than english you can
|
||||
If you need to set the keyboard layout to anything other than English you can
|
||||
temporarily do so by using the `loadkeys` command.
|
||||
This has to be followed by your country id (for example a german keyboard layout
|
||||
This has to be followed by your country id (for example a German keyboard layout
|
||||
would be `de`,`de-latin1` or `de-latin1-nodeadkeys`).
|
||||
|
||||
## 2. Formatting of the target drive
|
||||
@@ -87,7 +87,7 @@ For this guide this partition is assumed to be `/dev/sda2`.
|
||||
```sh
|
||||
cryptsetup -c aes-xts-plain -s 512 -y -v luksFormat /dev/sda2
|
||||
```
|
||||
Afterward, confirm with `YES`.
|
||||
Afterward confirm with `YES`.
|
||||
Now you can assign a passphrase.
|
||||
The passphrase has to be entered at boot to decrypt the system.
|
||||
Recovering of this passphrase is **not** possible.
|
||||
@@ -125,7 +125,7 @@ Now the created filesystems will be mounted for the installation.
|
||||
Now you need a working internet connection.
|
||||
If a wireless internet connection is needed start `iwctl`, scan (`station wlan0 scan`) and connect
|
||||
to the router (`station wlan0 connect <router ssid>`).
|
||||
Afterward, the internet connection will be established.
|
||||
Afterward the internet connection will be established.
|
||||
Exit `iwctl`.
|
||||
|
||||
- `pacstrap /mnt base base-devel dosfstools gptfdisk lvm2 linux linux-firmware vim networkmanager ntp`
|
||||
@@ -137,7 +137,7 @@ Exit `iwctl`.
|
||||
## 7. Set Region and Language
|
||||
|
||||
- `echo LANG=en\_US.UTF-8 > /etc/locale.conf` - Assign system Language to be
|
||||
english (you can use other languages, look into the `/etc/locale.gen` for a list of all available languages)
|
||||
English (you can use other languages, look into the `/etc/locale.gen` for a list of all available languages)
|
||||
- `vim /etc/locale.gen` - Assigning system language by uncomment the lines
|
||||
depending on your needs.
|
||||
In this example:
|
||||
@@ -151,7 +151,7 @@ en_US.UTF-8 UTF-8
|
||||
- `ln -sf /usr/share/zoneinfo/Europe/Berlin /etc/localtime` - set your timezone
|
||||
(select the first file accordingly to your location)
|
||||
- `ntpdate -q 0.de.pool.ntp.org` - sync the time and date with
|
||||
[NTP](/wiki/linux/ntp.md) (note that a german time server is used and
|
||||
[NTP](/wiki/linux/ntp.md) (note that a German time server is used and
|
||||
depending on the needs a adjustments should be made)
|
||||
|
||||
## 8. Configure and create kernel-image
|
||||
@@ -254,8 +254,8 @@ partition, take a look at the according section in
|
||||
[the dm-crypt article](/wiki/linux/dm-crypt.md).
|
||||
|
||||
After installing [xorg windows system](/wiki/linux/x_window_system.md) the language of it will be
|
||||
english by default.
|
||||
To change it - in this example to german - run the following command.
|
||||
English by default.
|
||||
To change it - in this example to German - run the following command.
|
||||
|
||||
```sh
|
||||
localectl --no-convert set-x11-keymap de pc105 deadgraveacute
|
||||
|
||||
@@ -9,7 +9,7 @@ This entry features the BlueZ package and all software that is based on it.
|
||||
On most [Linux](/wiki/linux.md) distributions BlueZ can be installed with the `bluez` package.
|
||||
Additionally, the `bluez-utils` package needs to be installed.
|
||||
To load the kernel module `modprobe btusb` needs to be run.
|
||||
Afterward, the
|
||||
Afterward the
|
||||
[service](/wiki/linux/systemd.md#startstopenabledisable-a-service) can be
|
||||
started and enabled by running the following commands.
|
||||
|
||||
@@ -73,6 +73,6 @@ For this run the following command where `<bluetooth-adapter>` is the name of th
|
||||
rfkill unblock <bluetooth-adapter>
|
||||
```
|
||||
|
||||
Afterward, the adapter will probably be recognized again but a restart of service
|
||||
Afterward the adapter will probably be recognized again but a restart of service
|
||||
`bluetooth.service` eventually has to be restarted as described in the
|
||||
[systemd entry](/wiki/linux/systemd.md#startstopenabledisable-a-service-and-retrieve-its-logs).
|
||||
|
||||
@@ -30,7 +30,7 @@ For this reason the following command has to be run first.
|
||||
apt-mark hold docker-ce docker-ce-cli containerd.io
|
||||
```
|
||||
|
||||
Afterward, the packages of the current major release version have to be
|
||||
Afterward the packages of the current major release version have to be
|
||||
[upgrading](/wiki/linux/package_manager/apt.md#updating-upgrading) using APTs `full-upgrade`
|
||||
option.
|
||||
Then a reboot is recommended.
|
||||
|
||||
@@ -133,7 +133,7 @@ In the following it is assumed that the partition to enlarge is `/dev/sda2`
|
||||
the partition)
|
||||
- `quit` parted
|
||||
|
||||
Afterward, the file system needs to be resized as described in the
|
||||
Afterward the file system needs to be resized as described in the
|
||||
[corresponding section](#growing-a-file-system).
|
||||
|
||||
### Growing a File System
|
||||
@@ -154,7 +154,7 @@ This can be done using the command `sudo e2fsck -f <path to partition>`.
|
||||
`<path to partition>` directs to the volume whose file system should be shrinked - for example
|
||||
`/dev/sda1`.
|
||||
It has to be the same for the next step as well.
|
||||
Afterward, the file system can be shrunken with the command
|
||||
Afterward the file system can be shrunken with the command
|
||||
`sudo resize2fs <path to partition> <new size of the file system>`.
|
||||
`<new size of the file system>` is the size that the file system will be shrunken to in the usual
|
||||
notation (for example `12G`).
|
||||
|
||||
@@ -38,7 +38,7 @@ Alternatively a recovery key can be used.
|
||||
sudo dislocker /dev/sdc1 -p<recovery password> -- /mnt/bitlocker
|
||||
```
|
||||
|
||||
Afterward, the `dislocker-file` can be mounted to the `/mnt/windows` directory or another mount
|
||||
Afterward the `dislocker-file` can be mounted to the `/mnt/windows` directory or another mount
|
||||
point as described in the [NTFS entry](/wiki/linux/ntfs.md#manual-mounting).
|
||||
|
||||
### Automatic Mounting at Boot
|
||||
|
||||
@@ -26,4 +26,4 @@ chmod +x ~/.xinitrc
|
||||
ln -s ~/.xsession ~/.xinitrc
|
||||
```
|
||||
|
||||
Afterward, the session will start like the `xinitrc`
|
||||
Afterward the session will start like the `xinitrc`
|
||||
|
||||
@@ -89,7 +89,7 @@ cryptsetup luksOpen <path to LUKS volume> crypt-volume --key-file=<key file loca
|
||||
|
||||
`<path to LUKS device>` is the encrypted device (for example `/dev/sda2`).
|
||||
|
||||
Afterward, it can be closed by running `cryptsetup close /dev/mapper/crypt0`.
|
||||
Afterward it can be closed by running `cryptsetup close /dev/mapper/crypt0`.
|
||||
|
||||
### Creating/Add a USB Decryption Key
|
||||
|
||||
|
||||
@@ -33,9 +33,9 @@ easyeffects --gapplication-service
|
||||
```
|
||||
|
||||
The two former commands will only work if called on each startup.
|
||||
The easiest way to do this is by using [SystemD](/wiki/linux/systemd.md).
|
||||
The easiest way to do this is by using [systemd](/wiki/linux/systemd.md).
|
||||
The following will work analogously to the path explained in
|
||||
[the corresponding section of the SystemD entry](/wiki/linux/systemd.md#run-command-on-boot).
|
||||
[the corresponding section of the systemd entry](/wiki/linux/systemd.md#run-command-on-boot).
|
||||
|
||||
Run the following command to edit the configuration file for the newly created EasyEffect service.
|
||||
|
||||
@@ -43,7 +43,7 @@ Run the following command to edit the configuration file for the newly created E
|
||||
systemctl --user edit --force -full easyeffects.service
|
||||
```
|
||||
|
||||
Afterward, set the contents of this file to the following.
|
||||
Afterward set the contents of this file to the following.
|
||||
Due to EasyEffect working together with [Pipewire and Wireplumber](/wiki/linux/pipewire.md) some
|
||||
precautions have to be taken to start it before these two.
|
||||
|
||||
@@ -88,8 +88,8 @@ By default, EasyEffects processes all input and output streams.
|
||||
This includes [loopback devices](/wiki/linux/pipewire.md#virtual-devices) with which it may lead to
|
||||
some problems - for example
|
||||
[problems with virtual devices](/wiki/linux/pipewire.md#problems-with-input-an-output-of-loopback-devices).
|
||||
It can be disabled and re-enabled in the `Preferences` under `Audio` by deselecting or selecting the
|
||||
switches for `Process all output streams` and `Process all input streams`.
|
||||
It can be disabled and re-enabled in the `Preferences` under `Audio` by deselecting or selecting
|
||||
the switches for `Process all output streams` and `Process all input streams`.
|
||||
|
||||
#### Recommended Presets
|
||||
|
||||
@@ -97,4 +97,4 @@ The following is a list of presets that have been tested and only need slight co
|
||||
adjust them to the specific system.
|
||||
|
||||
- [tiyns voice input preset](https://github.com/tiyn/dotfiles/blob/master/.config/easyeffects/input/voice.json)
|
||||
is a list of different effects to achieve an enhanced quality of microphone sound for speach.
|
||||
is a list of different effects to achieve an enhanced quality of microphone sound for speech.
|
||||
|
||||
@@ -59,7 +59,7 @@ An explanation of this was given by
|
||||
[aergistal on Stack Overflow](https://stackoverflow.com/questions/29082422/ffmpeg-video-compression-specific-file-size).
|
||||
This can easily be done with the calculation `bitrate = target size / duration`
|
||||
in Bits/Second.
|
||||
Afterward, the encoding can be done by using Two-Pass Encoding as explained in
|
||||
Afterward the encoding can be done by using Two-Pass Encoding as explained in
|
||||
[a previous section](#two-pass-encoding).
|
||||
Note that the bitrate for videos is split amongst a bitrate for video and a
|
||||
bitrate for audio.
|
||||
|
||||
@@ -76,7 +76,7 @@ fontforge arial.ttf
|
||||
|
||||
A font can be added to the local users fonts using a `.ttf` file.
|
||||
The file has to be copied into the local fonts directory `~/.local/share/fonts`.
|
||||
Afterward, the [cache should be reloaded](#reload-the-cache).
|
||||
Afterward the [cache should be reloaded](#reload-the-cache).
|
||||
Finally, the font can be [found](#list-or-find-font-family).
|
||||
|
||||
### Reload the Cache
|
||||
|
||||
@@ -19,7 +19,7 @@ First the devices updatable by fwupd can be checked.
|
||||
fwupdmgr get-devices
|
||||
```
|
||||
|
||||
Afterward, the latest metadata can be downloaded by the following command.
|
||||
Afterward the latest metadata can be downloaded by the following command.
|
||||
|
||||
```sh
|
||||
fwupdmgr refresh
|
||||
|
||||
@@ -107,7 +107,7 @@ The following sections assumes using a [Linux-based system](/wiki/linux.md) usin
|
||||
For this a
|
||||
[SSH certificate has to be created](/wiki/linux/openssh.md#generate-new-keys) and
|
||||
[added to the authentication agent](/wiki/linux/openssh.md#adding-keys-to-authentication-agent).
|
||||
Afterward, it the public SSH key to be added to the git server.
|
||||
Afterward it the public SSH key to be added to the git server.
|
||||
For GitHub there is
|
||||
[a guide on that topic](https://docs.github.com/en/get-started/getting-started-with-git/why-is-git-always-asking-for-my-password).
|
||||
|
||||
@@ -144,7 +144,7 @@ A more or less complete overview of the options was performed in an
|
||||
[delta](https://github.com/dandavison/delta) first needs to be installed.
|
||||
Most [package managers](/wiki/linux/package_manager.md) package it in the package `git-delta`.
|
||||
|
||||
Afterward, it needs to be enabled.
|
||||
Afterward it needs to be enabled.
|
||||
To do this globally add the following lines to the configuration file of git, which can be found in
|
||||
`~/.gitconfig`.
|
||||
Depending on the system settings and preferences the dark-mode (`dark`) and the side-by-side view
|
||||
@@ -170,7 +170,7 @@ Depending on the system settings and preferences the dark-mode (`dark`) and the
|
||||
`git diff` look.
|
||||
It can be installed via most [package managers](/wiki/linux/package_manager.md) using the
|
||||
`diff-so-fancy` package.
|
||||
Afterward, the following lines need to be run to complete the configuration.
|
||||
Afterward the following lines need to be run to complete the configuration.
|
||||
|
||||
```sh
|
||||
# switch to diff-so-fancy
|
||||
|
||||
@@ -61,7 +61,7 @@ gpg --import-ownertrust ownertrust.txt
|
||||
|
||||
Again the first command can be run individually to import single public keys that are not owned.
|
||||
|
||||
Afterward, the following commands can be run to set the ultimate trust level to the key pair.
|
||||
Afterward the following commands can be run to set the ultimate trust level to the key pair.
|
||||
Caution is advised.
|
||||
|
||||
```sh
|
||||
@@ -125,9 +125,9 @@ e-mail to.
|
||||
gpg --edit-key <key-id>
|
||||
```
|
||||
|
||||
Afterward, a console will open.
|
||||
Afterward a console will open.
|
||||
Using `adduid` another user can be added by following the on-screen instructions.
|
||||
Afterward, `save` will save the progress and exit from the console.
|
||||
Afterward `save` will save the progress and exit from the console.
|
||||
|
||||
To delete an existing user and e-mail also open the edit-console.
|
||||
Then list the existing users using the command `uid` and select the user id of the key to delete
|
||||
|
||||
@@ -25,7 +25,7 @@ command.
|
||||
upower -e
|
||||
```
|
||||
|
||||
Afterward, different values like the state, voltage, percentage and much other can be displayed.
|
||||
Afterward different values like the state, voltage, percentage and much other can be displayed.
|
||||
Additionally, it will show the original capacity (`energy-full-design`) and the current capacity
|
||||
(`energy-full`), which can be used to determine the health of the battery.
|
||||
The following is an example command where `<battery-name>` is the name of the batter returned from
|
||||
|
||||
@@ -8,4 +8,4 @@ The init process is given to a init system that manages various services.
|
||||
|
||||
The following is a list of available init services.
|
||||
|
||||
- [SystemD](/wiki/linux/systemd.md) is most common among linux systems.
|
||||
- [systemd](/wiki/linux/systemd.md) is most common among linux systems.
|
||||
|
||||
@@ -6,11 +6,11 @@ It is available for both [X](/wiki/linux/x_window_system.md) and Wayland.
|
||||
|
||||
## Setup
|
||||
|
||||
On most linux distributions LightDM can be installed with the `lemurs` package.
|
||||
On most [Linux](/wiki/linux.md) distributions LightDM can be installed with the `lemurs` package.
|
||||
|
||||
This setup needs an `xsession`.
|
||||
An alternative to this is using `xinitrc` as an `xsession`.
|
||||
The process of this is desribed in the
|
||||
This setup needs a `xsession`.
|
||||
An alternative to this is using `xinitrc` as a `xsession`.
|
||||
The process of this is described in the
|
||||
[display manager entry](/wiki/linux/display_managers.md#use-xinitrc-as-xsession).
|
||||
Make sure to have a working `xsession` or `xinitrc`.
|
||||
If you are not sure about it, use the tests provided in the penultimate step.
|
||||
@@ -22,7 +22,7 @@ This can be done by using one or both of the following commands.
|
||||
systemctl start lemurs.service
|
||||
```
|
||||
|
||||
Finally, the [SystemD](/wiki/linux/systemd.md) lightdm service needs to be enabled and reboot the
|
||||
Finally, the [systemd](/wiki/linux/systemd.md) `lightdm` service needs to be enabled and reboot the
|
||||
system.
|
||||
|
||||
```sh
|
||||
|
||||
@@ -2,11 +2,11 @@
|
||||
|
||||
[LightDM](https://github.com/canonical/lightdm/) is a lightweight GUI
|
||||
[display manager](/wiki/linux/display_managers.md).
|
||||
It is available for both [X](/wiki/linux/x_window_system.md) and Wayland.
|
||||
It is available for both [X](/wiki/linux/x_window_system.md) and [Wayland](/wiki/linux/wayland.md).
|
||||
|
||||
## Setup
|
||||
|
||||
On most linux distributions LightDM can be installed with the `lightdm` package.
|
||||
On most [Linux](/wiki/linux.md) distributions LightDM can be installed with the `lightdm` package.
|
||||
Additionally, `lightdm-gtk-greeter` and `xorg-server-xephyr` are recommended.
|
||||
This setup will work with [LightDM-GTK-Greeter](#lightdm-gtk-greeter) which is the default greeter.
|
||||
If another greeter is to be chosen `lightdm-gtk-greeter` does not have to be installed, but an
|
||||
@@ -15,9 +15,9 @@ For a guide on how to set the greeter navigate to the [greeter section](#greeter
|
||||
This section will also discuss various other greeters like the
|
||||
[LightDM-Mini-Greeter](#lightdm-mini-greeter).
|
||||
|
||||
This setup needs an `xsession`.
|
||||
An alternative to this is using `xinitrc` as an `xsession`.
|
||||
The process of this is desribed in the
|
||||
A system with [the X window system](/wiki/linux/x_window_system.md) setup needs a `xsession`.
|
||||
An alternative to this is using `xinitrc` as a `xsession`.
|
||||
The process of this is described in the
|
||||
[display manager entry](/wiki/linux/display_managers.md#use-xinitrc-as-xsession).
|
||||
Make sure to have a working `xsession` or `xinitrc`.
|
||||
If you are not sure about it, use the tests provided in the penultimate step.
|
||||
@@ -26,9 +26,26 @@ Then edit the config file `~/.dmrc` and edit the file to the following contents.
|
||||
|
||||
```txt
|
||||
[Desktop]
|
||||
Session=xinitrc
|
||||
Session=default
|
||||
```
|
||||
|
||||
Then create a symbolic link for a default session.
|
||||
|
||||
```sh
|
||||
ln -s /usr/share/xsessions/xinitrc.desktop /usr/share/xsessions/default.desktop
|
||||
```
|
||||
|
||||
For a [Wayland](/wiki/linux/wayland.md) do the same for your compositor and replace `<session>`
|
||||
with it.
|
||||
For example in case the system is set up with [the DWL compositor](/wiki/linux/suckless.md)
|
||||
`<session>` has to be removed with `dwl.desktop` and for Sway it will be `sway.desktop`.
|
||||
Check which session is created by your compositor.
|
||||
|
||||
```sh
|
||||
ln -s /usr/share/wayland-sessions/<session> /usr/share/wayland-sessions/default.desktop
|
||||
```
|
||||
|
||||
|
||||
Before finishing the setup the functionality should be tested.
|
||||
This can be done by using one or both of the following commands.
|
||||
|
||||
@@ -37,7 +54,7 @@ lightdm --test-mode --debug
|
||||
systemctl start lightdm.service
|
||||
```
|
||||
|
||||
Finally, the [SystemD](/wiki/linux/systemd.md) lightdm service needs to be enabled and reboot the
|
||||
Finally, the [systemd](/wiki/linux/systemd.md) `lightdm` service needs to be enabled and reboot the
|
||||
system.
|
||||
|
||||
```sh
|
||||
@@ -48,7 +65,7 @@ reboot
|
||||
## Greeters
|
||||
|
||||
LightDM features the option to choose between many different greeters.
|
||||
This section focusses on various greeters.
|
||||
This section focuses on various greeters.
|
||||
|
||||
The greeter can be set with the option `greeter-session` under the section `[Seat:*]` in the file
|
||||
`/etc/lightdm/lightdm.conf`.
|
||||
@@ -67,7 +84,7 @@ If no `greeter-session` is set the default will fall back to the
|
||||
|
||||
The [LightDM-GTK-Greeter](https://github.com/Xubuntu/lightdm-gtk-greeter) is the default greeter
|
||||
for LightDM.
|
||||
This is the default [greeter](#greeters) of [GTK](/wiki/linux/gtk.md) but others may be chosen.
|
||||
This is the default [greeter](#greeters) of [GTK](/wiki/linux/gtk.md), but others may be chosen.
|
||||
|
||||
### LightDM-Mini-Greeter
|
||||
|
||||
@@ -79,8 +96,7 @@ For the LightDM-Mini-Greeter to work correctly some settings have to be set in t
|
||||
The following lines show an example of this file.
|
||||
The most important changes have been done to set the `user` under `[greeter]`
|
||||
and `background-image` under `[greeter-theme]`.
|
||||
The background image path can vary, but lightdm has to be able to access the
|
||||
image.
|
||||
The background image path can vary, but LightDM has to be able to access the image.
|
||||
|
||||
```txt
|
||||
# LightDM Mini Greeter Configuration
|
||||
@@ -179,5 +195,5 @@ This section will focus on errors and the fixing of errors of LightDM.
|
||||
|
||||
### Bypass LightDM on Error
|
||||
|
||||
If it comes to problems that deny the login it can be useful to switch to another tty.
|
||||
If it comes to problems that deny the login it can be useful to switch to another TTY.
|
||||
This can be done by hitting the key combination `CTRL+ALT+F2`.
|
||||
|
||||
@@ -95,7 +95,7 @@ If the volume to shrink is the root volume it has to be done offline.
|
||||
For that a simple installation stick is enough.
|
||||
[The Arch Linux entry](/wiki/linux/arch-linux.md#installation-medium) describes the creation of
|
||||
such a boot stick.
|
||||
Afterward, the operating system has to be booted from the just created stick or a comparable
|
||||
Afterward the operating system has to be booted from the just created stick or a comparable
|
||||
device.
|
||||
For non-root volumes this extra step can be skipped.
|
||||
|
||||
@@ -146,7 +146,7 @@ sudo pvmove <path to physical volume>
|
||||
|
||||
`<path to physical volume>` is the physical volume that will get emptied and later removed from the
|
||||
logical volume.
|
||||
Afterward, the physical volume is emptied and can be removed from the logical volume by running the
|
||||
Afterward the physical volume is emptied and can be removed from the logical volume by running the
|
||||
following command.
|
||||
|
||||
```sh
|
||||
@@ -159,6 +159,6 @@ After this command the physical volume is no longer a part of it.
|
||||
If no longer used the empty physical volume can then be removed as described in the
|
||||
[according section](#remove-physical-volume).
|
||||
|
||||
Afterward, the file system can be matched to the logical volume so it takes up the full new size.
|
||||
Afterward the file system can be matched to the logical volume so it takes up the full new size.
|
||||
This is explained in the
|
||||
:wq[entry about disk management](/wiki/linux/disk-management.md#growing-a-file-system).
|
||||
|
||||
@@ -17,7 +17,7 @@ This can be done by using one or both of the following commands.
|
||||
systemctl start ly.service
|
||||
```
|
||||
|
||||
Finally, the [SystemD](/wiki/linux/systemd.md) Ly service needs to be enabled and reboot the
|
||||
Finally, the [systemd](/wiki/linux/systemd.md) Ly service needs to be enabled and reboot the
|
||||
system.
|
||||
|
||||
```sh
|
||||
|
||||
@@ -24,7 +24,7 @@ Desktop and gaming systems will benefit the most.
|
||||
|
||||
To setup the zen kernel do the following. Firstly install the packages `linux-zen` and
|
||||
`linux-zen-header`.
|
||||
Afterward, open the file `boot/loader/entries/arch.conf` and change the following lines.
|
||||
Afterward open the file `boot/loader/entries/arch.conf` and change the following lines.
|
||||
|
||||
```txt
|
||||
linux /vmlinuz-linux
|
||||
@@ -40,7 +40,7 @@ initrd /initramfs-linux-zen.img
|
||||
|
||||
If you want to switch the backup to Zen too, the backup file in `boot/loader/entries/` has to be
|
||||
changed too.
|
||||
Afterward, the system should be rebooted for the change to take effect.
|
||||
Afterward the system should be rebooted for the change to take effect.
|
||||
|
||||
## Usage
|
||||
|
||||
@@ -62,7 +62,7 @@ PRESETS=('default' 'fallback')
|
||||
Notice that the options are separated only by a space.
|
||||
To just build a fallback image remove `'default'` or vice versa.
|
||||
|
||||
Afterward, the initial ramdisk has to be [rebuild](#manually-generate-initial-ramdisk).
|
||||
Afterward the initial ramdisk has to be [rebuild](#manually-generate-initial-ramdisk).
|
||||
|
||||
### Manually Generate Initial Ramdisk
|
||||
|
||||
|
||||
@@ -32,5 +32,5 @@ network:
|
||||
version: 2
|
||||
```
|
||||
|
||||
Afterward, netplan has to be restarted by running `sudo netplan apply`.
|
||||
Afterward netplan has to be restarted by running `sudo netplan apply`.
|
||||
The addresses then are assigned to the system.
|
||||
|
||||
@@ -24,7 +24,7 @@ This plugin can be installed with the `networkmanager-openvpn` package.
|
||||
|
||||
OpenVPNs `.ovpn` files can then be imported by running
|
||||
`nmcli connection import type openvpn file <openvpn-file>`.
|
||||
Afterward, they can be modified accordingly.
|
||||
Afterward they can be modified accordingly.
|
||||
|
||||
### Prioritize Connections
|
||||
|
||||
@@ -36,13 +36,13 @@ priority, `1` being the next highest and so on.
|
||||
|
||||
## Troubleshooting
|
||||
|
||||
This section focusses on the troubleshooting of situations where the system does not connect
|
||||
This section focuses on the troubleshooting of situations where the system does not connect
|
||||
correctly.
|
||||
|
||||
### Restarting and Reenabling Wi-Fi
|
||||
|
||||
A useful chain of commands is the following.
|
||||
It will restart the [SystemD](/wiki/linux/systemd.md) service and enable the Wi-Fi device.
|
||||
It will restart the [systemd](/wiki/linux/systemd.md) service and enable the Wi-Fi device.
|
||||
|
||||
```sh
|
||||
systemctl restart NetworkManager
|
||||
|
||||
@@ -19,7 +19,7 @@ For one time synchronization of the time and date the `ntpdate` command can be
|
||||
used.
|
||||
The following command is an example for a one time sync.
|
||||
Note that the server has to be changed for different time zones.
|
||||
In this case a german time server is used.
|
||||
In this case a German time-server is used.
|
||||
|
||||
```sh
|
||||
ntpdate ptbtime1.ptb.de
|
||||
|
||||
@@ -37,7 +37,7 @@ and select either `Force Composition Timeline` or
|
||||
|
||||
On some operating systems like [Arch Linux](/wiki/linux/arch-linux.md) the newer versions of
|
||||
drivers are not compatible with Pascal GPUs anymore as explained in
|
||||
[the german Arch forum](https://www.archlinux.de/news/35689-Nvidia-Treiber-ab-Version-590-stellen-den-Support-fuer-Pascal-GPUs-ein).
|
||||
[the German Arch forum](https://www.archlinux.de/news/35689-Nvidia-Treiber-ab-Version-590-stellen-den-Support-fuer-Pascal-GPUs-ein).
|
||||
This is due to the drop of support for these cards from Nvidias site.
|
||||
If Pascal-GPUs are still used some minor changes need to be performed and some packets need to be
|
||||
replaced.
|
||||
|
||||
@@ -114,7 +114,7 @@ Make sure to restart the SSH daemon afterward by running the following command.
|
||||
service sshd restart
|
||||
```
|
||||
|
||||
Afterward, X-forwarding should be enabled on the server.
|
||||
Afterward X-forwarding should be enabled on the server.
|
||||
For full functionality install the `x11-apps` package as well.
|
||||
|
||||
#### Enabling X-Forwarding on a Client
|
||||
@@ -166,7 +166,7 @@ the process.
|
||||
ps aux | grep "ssh -f -N -L <local port>"
|
||||
```
|
||||
|
||||
Afterward, it can be killed by running the following command where `<process-id>` is the ID of the
|
||||
Afterward it can be killed by running the following command where `<process-id>` is the ID of the
|
||||
process found with the previous command.
|
||||
|
||||
```sh
|
||||
|
||||
@@ -17,7 +17,7 @@ command.
|
||||
apt update
|
||||
```
|
||||
|
||||
Afterward, there are two possible update types without changing the major release version.
|
||||
Afterward there are two possible update types without changing the major release version.
|
||||
|
||||
The following command - `upgrade` - updates the packages only if no new or previously removed dependencies are
|
||||
needed.
|
||||
|
||||
@@ -53,7 +53,7 @@ This works like the following assuming the package `v4l2loopback-dmks` needs to
|
||||
sudo downgrade v4l2loopback-dmks
|
||||
```
|
||||
|
||||
Afterward, the target version can be selected and the downgrading process will conclude.
|
||||
Afterward the target version can be selected and the downgrading process will conclude.
|
||||
After the downgrade of a package you will get asked if you want to
|
||||
[ignore future updates](#ignoring-packages).
|
||||
|
||||
@@ -67,7 +67,7 @@ Using the `makepkg` command it can be installed like the following command shows
|
||||
makepkg -sirc
|
||||
```
|
||||
|
||||
Afterward, it is installed on the system and can be further managed (especially uninstalled) by the
|
||||
Afterward it is installed on the system and can be further managed (especially uninstalled) by the
|
||||
Pacman package manager.
|
||||
|
||||
### Installing an AUR Program with a Specific Version
|
||||
@@ -77,7 +77,7 @@ For this navigate to the AUR page of the program to install.
|
||||
On the right-hand side click on `View Changes` and select the version you want to install in the
|
||||
commit list.
|
||||
Next to `download` a `.tar.gz` file can be downloaded which includes a `PKGBUILD` file.
|
||||
Afterward, it needs to be [uncompressed](/wiki/linux/tar.md#uncompressing-a-tar-archive).
|
||||
Afterward it needs to be [uncompressed](/wiki/linux/tar.md#uncompressing-a-tar-archive).
|
||||
|
||||
### Clear Cache
|
||||
|
||||
@@ -209,7 +209,7 @@ AbortOnFail
|
||||
|
||||
The following hook will use [reflector](https://xyne.dev/projects/reflector/) to update the pacman
|
||||
mirrorlist.
|
||||
It will use german mirrors (`-c de`), will list the fastest 15 mirrors (`-n 15`) and only do so if
|
||||
It will use German mirrors (`-c de`), will list the fastest 15 mirrors (`-n 15`) and only do so if
|
||||
the mirror was online in the last 24 hours (`-a 24`).
|
||||
It was found in a
|
||||
[reddit post by IBNash](https://www.reddit.com/r/archlinux/comments/dsnu81/hear_ye_archers_share_your_pacman_hooks/)
|
||||
|
||||
@@ -58,7 +58,7 @@ papis add https://arxiv.org/abs/1712.03134
|
||||
```
|
||||
|
||||
To remove an entry the following command can be run.
|
||||
Afterward, the entry that should be removed can be easily selected via the terminal user interface.
|
||||
Afterward the entry that should be removed can be easily selected via the terminal user interface.
|
||||
|
||||
```sh
|
||||
papis rm
|
||||
@@ -112,13 +112,13 @@ inside the folder `tmp-db`.
|
||||
papis bibtex read mylib.bib import -a -o tmp-db
|
||||
```
|
||||
|
||||
Afterward, the contents of the temporary database should be checked to be correctly imported.
|
||||
Afterward the contents of the temporary database should be checked to be correctly imported.
|
||||
|
||||
```sh
|
||||
papis -l tmp-db edit
|
||||
```
|
||||
|
||||
Afterward, the contents of the temporary library should be moved to the actualy directory where
|
||||
Afterward the contents of the temporary library should be moved to the actualy directory where
|
||||
papis stores its entries.
|
||||
The path for that can be found in the [config file](#configuration).
|
||||
|
||||
|
||||
@@ -8,7 +8,7 @@ It can change the native resolution early in the boot process and display splash
|
||||
|
||||
On most linux distributions LightDM can be installed with the `plymouth` package.
|
||||
|
||||
Afterward, the kernel options need to be changed.
|
||||
Afterward the kernel options need to be changed.
|
||||
On [Arch Linux](/wiki/linux/arch-linux.md) systems this can be done by editing the file located at
|
||||
`/boot/loader/entries/arch.conf`.
|
||||
In the options line append `quiet` if you want to use the quiet-mode and `splash` if you want to
|
||||
|
||||
@@ -125,7 +125,7 @@ For example if you want to the disk 100 by 100G (100GibiByte):
|
||||
qm resize 100 ide0 +100G
|
||||
```
|
||||
|
||||
Afterward, the partition of the VM needs to be enlarged.
|
||||
Afterward the partition of the VM needs to be enlarged.
|
||||
For that
|
||||
[the disk management article](/wiki/linux/disk-management.md#grow-non-lvm-partition)
|
||||
can be used for non-LVM paritions.
|
||||
|
||||
@@ -16,7 +16,7 @@ qt5ct is officially archived and qt6ct is the recommended program to use and wil
|
||||
discussed in this article.
|
||||
These programs can sometimes be found as [package](/wiki/linux/package_manager.md) of the same
|
||||
name.
|
||||
Afterward, `qt6ct` can be run to get a graphical user interface to set the theme and icons of Qt
|
||||
Afterward `qt6ct` can be run to get a graphical user interface to set the theme and icons of Qt
|
||||
applications.
|
||||
This will create or edit a configuration file located at `~/.config/qt6ct/qt6ct.conf`.
|
||||
To make this config apply for all Qt applications the following line needs to be inserted into the
|
||||
@@ -26,7 +26,7 @@ To make this config apply for all Qt applications the following line needs to be
|
||||
export QT_QPA_PLATFORMTHEME="qt6ct"
|
||||
```
|
||||
|
||||
Afterward, `qt6ct` can be used to enable the dark mode or change other configurations.
|
||||
Afterward `qt6ct` can be used to enable the dark mode or change other configurations.
|
||||
|
||||
#### Achieving a System-Wide Uniform Look
|
||||
|
||||
@@ -56,5 +56,5 @@ When updating the system it is possible that the theme will not work correctly a
|
||||
Often the error `The libqt6ct.so plugin is compiled against incompatible Qt version` is responsible
|
||||
for this.
|
||||
To fix it most of the time it is enough to recompile the `qt6ct` package.
|
||||
Afterward, a reboot might be needed for the theme to be displayed correctly again.
|
||||
Afterward a reboot might be needed for the theme to be displayed correctly again.
|
||||
|
||||
|
||||
@@ -161,7 +161,7 @@ yay -S dash
|
||||
sudo ln -sfT /bin/dash /bin/sh
|
||||
```
|
||||
|
||||
Afterward, create the file `/usr/share/libalpm/hooks/bash-update.hook` and fill
|
||||
Afterward create the file `/usr/share/libalpm/hooks/bash-update.hook` and fill
|
||||
it with the following text.
|
||||
|
||||
```txt
|
||||
|
||||
@@ -58,7 +58,7 @@ On Ubuntu systems the repository first has to be added by running the following
|
||||
add-apt-repository -y ppa:flacon
|
||||
```
|
||||
|
||||
Afterward, `flacon` can be installed like a normal package.
|
||||
Afterward `flacon` can be installed like a normal package.
|
||||
|
||||
## Troubleshooting
|
||||
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
# SystemD
|
||||
# systemd
|
||||
|
||||
SystemD is an [init system](/wiki/linux/init.md) for Linux systems.
|
||||
systemd is an [init system](/wiki/linux/init.md) for Linux systems.
|
||||
It is used for service configuration and startup.
|
||||
|
||||
## Usage
|
||||
@@ -54,9 +54,9 @@ Logs of the last start of the service can be found by running `systemctl status
|
||||
|
||||
Additionally, the `--user` flag can be set to start the service only for the current user.
|
||||
|
||||
### Retrieving the SystemD Logs
|
||||
### Retrieving the systemd Logs
|
||||
|
||||
SystemD logs can easily be found using the `journalctl` command.
|
||||
systemd logs can easily be found using the `journalctl` command.
|
||||
One of the most notable usages of the command is for checking the logs of the previous boot.
|
||||
This can be achieved by running the following command.
|
||||
|
||||
@@ -108,7 +108,7 @@ HandleLidSwitchExternalPower=ignore
|
||||
HandleLidSwitchDocked=ignore
|
||||
```
|
||||
|
||||
Afterward, the logind service has to be restarted
|
||||
Afterward the logind service has to be restarted
|
||||
[as described on a later section](#startstopenabledisable-a-service-and-retrieve-its-logs).
|
||||
|
||||
```sh
|
||||
@@ -117,7 +117,7 @@ sudo systemctl restart systemd-logind
|
||||
|
||||
## Troubleshooting
|
||||
|
||||
This section focusses on errors that correspond to the SystemD software.
|
||||
This section focusses on errors that correspond to the systemd software.
|
||||
|
||||
### Timed Out Waiting for Device `/dev/tpmrm0`
|
||||
|
||||
|
||||
@@ -9,21 +9,19 @@ optimizing battery life.
|
||||
TLP can be installed on most distributions by installing the `tlp` package.
|
||||
Additionally, the installation of `tlp-rdw` is recommended, which is used to get better control over
|
||||
radio devices.
|
||||
Afterward, the TLP [service](/wiki/linux/systemd.md#startstopenabledisable-a-service) needs to be
|
||||
Afterward the TLP [service](/wiki/linux/systemd.md#startstopenabledisable-a-service) needs to be
|
||||
started and enabled.
|
||||
In contrast to other
|
||||
[SystemD services](/wiki/linux/systemd.md#startstopenabledisable-a-service) this
|
||||
can be done by running `sudo tlp start` and running `systemctl enable tlp.service`.
|
||||
In contrast to other [systemd services](/wiki/linux/systemd.md#startstopenabledisable-a-service)
|
||||
this can be done by running `sudo tlp start` and running `systemctl enable tlp.service`.
|
||||
|
||||
## Configure Battery Charge Thresholds
|
||||
|
||||
There are two battery charge thresholds.
|
||||
The first is `START_CHARGE_THRESH` this threshold contains the battery charge
|
||||
level below which charging will begin.
|
||||
The first is `START_CHARGE_THRESH` this threshold contains the battery charge level below which
|
||||
charging will begin.
|
||||
`STOP_CHARGE_TRESH` is the second threshold.
|
||||
It describes up to which level the battery will be charged.
|
||||
Battery charge thresholds are used to limit the charging of the battery to
|
||||
extend the battery life.
|
||||
Battery charge thresholds are used to limit the charging of the battery to extend the battery life.
|
||||
|
||||
Thresholds can be set in the file `/etc/tlp.conf`.
|
||||
Search and edit the following lines according to your needs.
|
||||
@@ -33,4 +31,4 @@ START_CHARGE_THRESH_BAT0=75
|
||||
STOP_CHARGE_THRESH_BAT0=80
|
||||
```
|
||||
|
||||
This can also be achieved by using [tp-battery-mode](/wiki/linux/battery_saving.md#programs)
|
||||
This can also be achieved by using [tp-battery-mode](/wiki/linux/battery_saving.md#programs).
|
||||
|
||||
@@ -32,8 +32,7 @@ v4l2loopback can be manually started by running the following command.
|
||||
modprobe v4l2loopback card_label='V4L2 Loopback' video_nr=7 exclusive_caps=1
|
||||
```
|
||||
|
||||
`video_nr=7` states the device path to use with v4l2loopback - in this case
|
||||
`/dev/video7`.
|
||||
`video_nr=7` states the device path to use with v4l2loopback - in this case `/dev/video7`.
|
||||
This can be changed according to the needs.
|
||||
It is important that the device is not already in use by another application.
|
||||
|
||||
@@ -46,8 +45,8 @@ modprobe v4l2loopback card_label='OBS Virtual Camera','IP Webcam' video_nr=7,8 e
|
||||
|
||||
### Create Permanent V4L2 Devices
|
||||
|
||||
For an automatic start at boot via [SystemD](/wiki/linux/systemd.md) a service can be created - as
|
||||
described in [the SystemD entry](/wiki/linux/systemd.md#run-command-on-boot).
|
||||
For an automatic start at boot via [systemd](/wiki/linux/systemd.md) a service can be created - as
|
||||
described in [the systemd entry](/wiki/linux/systemd.md#run-command-on-boot).
|
||||
For v4l2loopback create the file `/etc/systemd/system/v4l2loopback.service` containing the
|
||||
following lines.
|
||||
|
||||
@@ -69,7 +68,7 @@ Note the line starting with `ExecStart=/bin/` is the same line described in the
|
||||
[above section](#create-temporary-v4l2-devices).
|
||||
Make sure to change it if needed.
|
||||
|
||||
Afterward, enable the service to start at every boot process aswell as running it by using the
|
||||
Afterward enable the service to start at every boot process aswell as running it by using the
|
||||
following command:
|
||||
|
||||
```sh
|
||||
|
||||
@@ -37,7 +37,7 @@ The tracking of the time can be stopped by running the following command.
|
||||
watson stop
|
||||
```
|
||||
|
||||
Afterward, the summary of the tracked time can be displayed by running the following command.
|
||||
Afterward the summary of the tracked time can be displayed by running the following command.
|
||||
|
||||
```sh
|
||||
watson report
|
||||
|
||||
@@ -26,12 +26,12 @@ correctly.
|
||||
### Restarting WPA Supplicant
|
||||
|
||||
Most of the problems regarding WPA Supplicant can be fixed by restarting the
|
||||
[SystemD](/wiki/linux/systemd.md) service with the following command.
|
||||
[systemd](/wiki/linux/systemd.md) service with the following command.
|
||||
|
||||
```sh
|
||||
systemctl restart wpa_supplicant
|
||||
```
|
||||
|
||||
Afterward, if the error still persists - it may be useful to reenable the Wi-Fi device as explained
|
||||
Afterward if the error still persists - it may be useful to reenable the Wi-Fi device as explained
|
||||
in the
|
||||
[section of the NetworkManager entry](/wiki/linux/networkmanager.md#restarting-and-reenabling-wi-fi).
|
||||
|
||||
@@ -1,8 +1,8 @@
|
||||
# X Window System
|
||||
|
||||
X Window System - also called X and X11 according to the current version - is a protocoll for
|
||||
handling the display of the most unix-like operating systems.
|
||||
[Xorg](https://www.x.org/wiki/) is the most used implementation of the X protocoll.
|
||||
X Window System - also called X and X11 according to the current version - is a protocol for
|
||||
handling the display of the most Unix-like operating systems.
|
||||
[X.Org](https://www.x.org/wiki/) is the most used implementation of the X protocol.
|
||||
It is maintained by the [X.Org Foundation](https://x.org/wiki/).
|
||||
|
||||
## Usage
|
||||
@@ -26,7 +26,7 @@ The screen can be run by simply running the following command.
|
||||
slock
|
||||
```
|
||||
|
||||
By default this will not be run automatically when the computer goes into sleep.
|
||||
By default, this will not be run automatically when the computer goes into sleep.
|
||||
This can be changed by installing and using `xss-lock` like the following example shows.
|
||||
|
||||
```sh
|
||||
@@ -43,7 +43,7 @@ For this navigate to the [corresponding section](#turning-off-the-screen).
|
||||
|
||||
Windows can be killed with the utility `xkill`.
|
||||
Depending on the [distribution](/wiki/linux.md#distributions) used it maybe has to be installed.
|
||||
It often is bundled in a package named `xorg-xkill`.
|
||||
It is often bundled in a package named `xorg-xkill`.
|
||||
By running `xkill` the mouse cursor will turn into an x.
|
||||
With the mouse the window to close can then be selected.
|
||||
|
||||
@@ -87,7 +87,7 @@ EndSection
|
||||
|
||||
This section describes the handling of keyboards by X.
|
||||
|
||||
##### Change Keyboardlayout
|
||||
##### Change Keyboard Layout
|
||||
|
||||
To temporarily change the layout of the keyboard just run `setxkbmap <your preferred layout>`.
|
||||
For a permanent change run `localectl set-x11-keymap <your preferred layout>`.
|
||||
@@ -107,7 +107,7 @@ layouts.
|
||||
|
||||
In many languages there are ligatures (for example `œ`) and diacritics (for example `ç`).
|
||||
An easy way to write them is by using the compose button.
|
||||
Using the compose button these special symbols can be composed from their parts.
|
||||
Using the compose button these special symbols can be composed of their parts.
|
||||
The `ç` can be written by chaining compose with `,` and `c`.
|
||||
The `œ` can be written by chaining compose with `o` and `e`.
|
||||
There are many other diacritics and ligatures that can be written this way.
|
||||
@@ -115,8 +115,8 @@ There are many other diacritics and ligatures that can be written this way.
|
||||
To temporarily set up a compose key the following command can be used.
|
||||
It will set the given key `<compose>` (for example the right control key with `rctrl`) to act as
|
||||
the compose key when tapped.
|
||||
`<layout>` specifies the layout of the keymap (for example german with `de`).
|
||||
If it is omitted the english `en` layout will be set.
|
||||
`<layout>` specifies the layout of the keymap (for example German with `de`).
|
||||
If it is omitted the English `en` layout will be set.
|
||||
|
||||
```sh
|
||||
setxkbmap -layout <layout> -option compose:<compose>
|
||||
@@ -158,7 +158,7 @@ EndSection
|
||||
```
|
||||
|
||||
Another option to do this is by using the command `xset`.
|
||||
An example for this are the follwing commands which will enable the screensaver to act upon 10
|
||||
An example for this are the following commands which will enable the screensaver to act upon 10
|
||||
minutes of inactivity.
|
||||
|
||||
```sh
|
||||
@@ -166,7 +166,7 @@ xset s on
|
||||
xset s 600
|
||||
```
|
||||
|
||||
For more informations on this visit the
|
||||
For more information on this visit the
|
||||
[Arch wiki](https://wiki.archlinux.org/title/Session_lock#DPMS).
|
||||
|
||||
##### Adjust DPI and UI Scale
|
||||
@@ -180,8 +180,8 @@ The DPI number should be adjusted as needed.
|
||||
Xft.dpi: 100
|
||||
```
|
||||
|
||||
Afterward, `~/.config/xorg/xpcspec` needs to be sourced in the `~/.xinitrc` file.
|
||||
For this to work the following line needs to be added into the `~/.xinitrc` file .
|
||||
Afterward `~/.config/xorg/xpcspec` needs to be sourced in the `~/.xinitrc` file.
|
||||
For this to work the following line needs to be added into the `~/.xinitrc` file.
|
||||
|
||||
```sh
|
||||
[ -f "$HOME/.config/xorg/xpcspec" ] && xrdb -merge "$HOME/.config/xorg/xpcspec"
|
||||
@@ -205,7 +205,7 @@ As written by
|
||||
there are two ways to change this property.
|
||||
If the change is only needed temporarily
|
||||
`xinput set-prop <id> "libinput Middle Emulation Enabled" <flag>` can be run.
|
||||
`<id>` is the identifier of the mouse and <flag> is `0` for disabling and `1` for enabling the
|
||||
`<id>` is the identifier of the mouse and `<flag>` is `0` for disabling and `1` for enabling the
|
||||
middle mouse button.
|
||||
For permanent change of the property a change or addition to
|
||||
`/etc/X11/xorg.conf.d/40-libinput.conf` can be made.
|
||||
@@ -241,7 +241,7 @@ For that search for the package `xdg-desktop-portal` or a similar named one usin
|
||||
[package manager](/wiki/linux/package_manager.md).
|
||||
If it is installed check if it starts up correctly by using the command
|
||||
`systemctl --user status xdg-desktop-portal` as described in the
|
||||
[SystemD entry](/wiki/linux/systemd.md#startstopenabledisable-a-service-and-retrieve-its-logs).
|
||||
[systemd entry](/wiki/linux/systemd.md#startstopenabledisable-a-service-and-retrieve-its-logs).
|
||||
|
||||
A possible error is `cannot open display` as it was described and fixed by rockzombie2 and V1del in
|
||||
an [Arch Linux](/wiki/linux/arch-linux.md)
|
||||
@@ -253,7 +253,7 @@ systemctl --user import-environment DISPLAY XAUTHORITY
|
||||
systemctl --user restart xdg-desktop-portal
|
||||
```
|
||||
|
||||
If that works make sure the Xorg configs are sourced for users aswell.
|
||||
If that works make sure the X configs are sourced for users as well.
|
||||
It is possible that the following code block is missing in the local `.xinitrc`.
|
||||
This would create similar errors to the ones experienced.
|
||||
|
||||
|
||||
@@ -29,7 +29,7 @@ love <game-directory>
|
||||
|
||||
For building the game, the game directory has to be compressed first, then compiled and finally the
|
||||
permissions has to be changed to make the compiled file runnable.
|
||||
Afterward, the game can be compiled using the following command, where `<game-directory>` is the
|
||||
Afterward the game can be compiled using the following command, where `<game-directory>` is the
|
||||
path to the game directory and `<game-name>` is the name the compiled file should be called.
|
||||
|
||||
```sh
|
||||
@@ -38,7 +38,7 @@ cat /usr/bin/love <game-name>.love > <game-name>
|
||||
chmod a+x <game-name>
|
||||
```
|
||||
|
||||
Afterward, the compiled file can simply be run using the usual [Shell](/wiki/linux/shell.md)
|
||||
Afterward the compiled file can simply be run using the usual [Shell](/wiki/linux/shell.md)
|
||||
command.
|
||||
|
||||
```sh
|
||||
|
||||
@@ -427,4 +427,4 @@ Finally, add the following lines in the `service` section to your `docker-compos
|
||||
- "5349:5349"
|
||||
```
|
||||
|
||||
Afterward, if not done already restart the Matrix server and all its services.
|
||||
Afterward if not done already restart the Matrix server and all its services.
|
||||
|
||||
@@ -23,7 +23,7 @@ Under preferences set the following URL under `Additional boards manager URLs`.
|
||||
|
||||
`https://raw.githubusercontent.com/espressif/arduino-esp32/gh-pages/package_esp32_index.json`
|
||||
|
||||
Afterward, install the board manager `esp32`.
|
||||
Afterward install the board manager `esp32`.
|
||||
|
||||
### Flash Firmware on the ESP32
|
||||
|
||||
@@ -52,7 +52,7 @@ If it is not in programming mode it will show up as port but will encounter `Wri
|
||||
when trying to flash programs or firmware onto it.
|
||||
To put the ESP32 in the programming mode press and hold the Boot-Button (usually labeled `B`).
|
||||
Then press and release the Reset-Button (usually labeled `R`).
|
||||
Afterward, release the Boot-Button.
|
||||
Afterward release the Boot-Button.
|
||||
The board now should be in programming mode and it should be possible to upload and flash programs
|
||||
or firmware onto it.
|
||||
This section is based on a Reddit
|
||||
|
||||
@@ -31,7 +31,7 @@ make
|
||||
cp mpv_thumbnail_script_client_osc.lua mpv_thumbnail_script_server.lua ~/.config/mpv/scripts
|
||||
```
|
||||
|
||||
Afterward, create the file `~/.config/mpv/script-opts/mpv_thumbnail_script.conf` with the following
|
||||
Afterward create the file `~/.config/mpv/script-opts/mpv_thumbnail_script.conf` with the following
|
||||
text.
|
||||
|
||||
```txt
|
||||
|
||||
@@ -52,7 +52,7 @@ nativefier --name Mastodon \
|
||||
--single-instance https://mastodon.technology
|
||||
```
|
||||
|
||||
Afterward, if a [Linux](/wiki/linux.md)-based system is used the created app can be added to the
|
||||
Afterward if a [Linux](/wiki/linux.md)-based system is used the created app can be added to the
|
||||
path.
|
||||
An example for this is the following command which
|
||||
[links](/wiki/linux/shell.md#symbolic-links-using-ln) the applicatoin to a specifically created
|
||||
|
||||
@@ -5,7 +5,7 @@ NextCloud is a free and open source client-server cloud-service.
|
||||
## Setup
|
||||
|
||||
The software can be setup via [Docker](/wiki/docker.md) with the
|
||||
[nextcloud image](/wiki/docker/nextcloud.md).
|
||||
[NextCloud image](/wiki/docker/nextcloud.md).
|
||||
|
||||
When using NextCloud with a specific nginx configuration you have to append
|
||||
`'overwriteprotocol' => 'https',` to your `config/config.html`.
|
||||
@@ -21,8 +21,65 @@ You can access ownCloud via WebDAV with the link
|
||||
|
||||
### Nesting Nextcloud Data of Multiple Servers
|
||||
|
||||
By default it is not possible for one servers files to be saved to the folder structure that is
|
||||
By default, it is not possible for one server files to be saved to the folder structure that is
|
||||
used for another server or to nest data from two or more servers within each other.
|
||||
This however can be conveniently avoided by using symbolic links
|
||||
(for example [symbolic links](/wiki/linux/shell.md#symbolic-links-using-ln) in
|
||||
[Linux](/wiki/linux.md)), which are not by default synchronized to NextCloud.
|
||||
|
||||
## Troubleshooting
|
||||
|
||||
This section will focus on errors and the fixing of errors of NextCloud.
|
||||
|
||||
### `Error occurred while downloading files` on Android Clients
|
||||
|
||||
When using [Android](/wiki/android.md) clients for NextCloud the error `Error occurred while
|
||||
downloading files` can occur.
|
||||
This error can especially show up when a file or a directory contains a colon (`:`).
|
||||
[Android](/wiki/android.md) might display them correctly but has problems with downloading and
|
||||
displaying them which seems to be a problem with file handling and the conversion of file names.
|
||||
Most notably this error is not reproducible with the [Linux](/wiki/linux.md) or
|
||||
[Windows](/wiki/windows.md) or the web interface.
|
||||
Simply renaming files and folders to not include colons fixes the problems most of the time.
|
||||
|
||||
### Problem Uploading Files on Android Clients
|
||||
|
||||
When using an [Android](/wiki/android.md) client problems may occur regarding uploading files.
|
||||
Most of the time no error messages are given, but the error can be caused by a colon (`:`) and be
|
||||
similar to the [previous section](#error-occurred-while-downloading-files-on-android-clients).
|
||||
Simply renaming files and folders to not include colons fixes the problems most of the time.
|
||||
|
||||
### Stuck with `Synchronizing files in local folder`
|
||||
|
||||
When the NextCloud client is stuck with in an idle loop that is characterized by a status like
|
||||
`Synchronizing files in local folder` and/or `Syncing file 0 of <file-number>` where `<file-number>`
|
||||
is an arbitrarily large number of files.
|
||||
When checking the logging file in `~/.local/share/Nextcloudoud_sync.log` there won't be any obvious
|
||||
error messages.
|
||||
In fact there will only be a sync running without it finishing - unless interrupted manually.
|
||||
|
||||
However, this problem can easily be fixed with the following steps.
|
||||
First the NextCloud instance which is stuck needs to be stopped.
|
||||
|
||||
```sh
|
||||
nextcloud --quit
|
||||
```
|
||||
|
||||
Afterward some files have to be removed.
|
||||
Firstly delete the cache at `~/.local/share/Nextcloud`.
|
||||
|
||||
```sh
|
||||
rm -rf ~/.local/share/Nextcloud/*
|
||||
```
|
||||
|
||||
And secondly remove the synchronization files in the NextCloud folder.
|
||||
`<nextcloud-folder>` is the placeholder for that.
|
||||
|
||||
```sh
|
||||
rm -rf <nextcloud-folder>/.sync_*
|
||||
```
|
||||
|
||||
Finally, restart NextCloud and the system should not be stuck anymore.
|
||||
Please note that after this steps a complete re-check of all files will be due.
|
||||
This however does not mean that all files will be downloaded or uploaded again.
|
||||
They will just be checked and only if the local version differs will they be synchronized.
|
||||
|
||||
@@ -22,7 +22,7 @@ camera.
|
||||
First of all [V4L2](/wiki/linux/v4l2.md) needs to be set up.
|
||||
This guide assumes it is set up according to the section in the
|
||||
[V4L2 entry](/wiki/linux/v4l2.md#v4l2loopback).
|
||||
Afterward, the virtual camera can be started.
|
||||
Afterward the virtual camera can be started.
|
||||
|
||||
### Background Removal
|
||||
|
||||
@@ -35,7 +35,7 @@ Made by royshil [the GitHub page](https://github.com/royshil/obs-backgroundremov
|
||||
various possibilities to install the background removal for OBS on different systems.
|
||||
On Linux systems background removal is often contained in a package named `obs-backgroundremoval`
|
||||
or similarly.
|
||||
Afterward, the background removal can be added as a filter on a input source.
|
||||
Afterward the background removal can be added as a filter on a input source.
|
||||
|
||||
## Troubleshooting
|
||||
|
||||
|
||||
@@ -32,7 +32,7 @@ list available networks.
|
||||
ollama list
|
||||
```
|
||||
|
||||
Afterward, a model can be selected and pulled by using the following command. `<model>` is the name
|
||||
Afterward a model can be selected and pulled by using the following command. `<model>` is the name
|
||||
of the model obtained in the previous step (for example `deepseek-r1`).
|
||||
|
||||
```sh
|
||||
|
||||
@@ -31,7 +31,7 @@ be run afterward to change the current database.
|
||||
\c <database>
|
||||
```
|
||||
|
||||
Afterward, the following command can be used to show all tables in the database.
|
||||
Afterward the following command can be used to show all tables in the database.
|
||||
|
||||
```sh
|
||||
\dt
|
||||
|
||||
@@ -49,7 +49,7 @@ aswell.
|
||||
sudo apt install tk-dev tcl-dev
|
||||
```
|
||||
|
||||
Afterward, the python source code can be downloaded.
|
||||
Afterward the python source code can be downloaded.
|
||||
|
||||
```sh
|
||||
wget https://www.python.org/ftp/python/3.9.1/Python-3.9.1.tgz
|
||||
@@ -57,7 +57,7 @@ tar -xf Python-3.9.1.tgz
|
||||
cd Python-3.9.1
|
||||
```
|
||||
|
||||
Afterward, if OpenSSL should be enabled for Python uncomment all the corresponding lines in
|
||||
Afterward if OpenSSL should be enabled for Python uncomment all the corresponding lines in
|
||||
`Modules/Setup`.
|
||||
This part of the guide is taken from a
|
||||
[StackOverflow post by Ironman](https://stackoverflow.com/questions/58309485/modulenotfounderror-no-module-named-ssl).
|
||||
@@ -70,7 +70,7 @@ make
|
||||
sudo make altinstall
|
||||
```
|
||||
|
||||
Afterward, you can check if the Pyhton version is installed using the following command.
|
||||
Afterward you can check if the Pyhton version is installed using the following command.
|
||||
|
||||
```sh
|
||||
python3.9 --version
|
||||
|
||||
@@ -21,13 +21,13 @@ various [package managers](/wiki/linux/package_manager/pacman_and_aur.md).
|
||||
For Carbon Boogie has to be installed too.
|
||||
This is best done by installing a .NET SDK which is often packaged in a package called `dotnet-sdk`
|
||||
or a similar named one.
|
||||
Afterward, boogie can be installed using the following command.
|
||||
Afterward boogie can be installed using the following command.
|
||||
|
||||
```sh
|
||||
dotnet tool install -g boogie
|
||||
```
|
||||
|
||||
Afterward, the building of Silicon and/or Carbon can follow.
|
||||
Afterward the building of Silicon and/or Carbon can follow.
|
||||
|
||||
The easiest way to build one or both verifiers locally is creating a `.jar` file via
|
||||
[Docker](/wiki/docker.md) using the
|
||||
@@ -50,14 +50,14 @@ cd /mnt/carbon
|
||||
sbt assembly
|
||||
```
|
||||
|
||||
Afterward, leave the Docker container.
|
||||
Afterward leave the Docker container.
|
||||
It is no longer needed.
|
||||
|
||||
The `.jar` files are now available in `<path-to-carbon>/target/scala-<version>/carbon.jar` or
|
||||
`<path-to-silicon>/target/scala-2.13/silicon.jar` and are ready to be used outside the docker
|
||||
container from the host machine.
|
||||
|
||||
Afterward, Carbon and/or Silicon are ready to be [used](#usage).
|
||||
Afterward Carbon and/or Silicon are ready to be [used](#usage).
|
||||
|
||||
## Usage
|
||||
|
||||
|
||||
@@ -16,5 +16,5 @@ Alternatively most [Linux systems](/wiki/linux/package_manager.md) feature a pac
|
||||
|
||||
Connect the phone which is to be controlled with the computer via USB.
|
||||
Make sure USB debugging is enabled in the phones setting.
|
||||
Afterward, start up scrcpy.
|
||||
Afterward start up scrcpy.
|
||||
It is possible that debugging has to be confirmed on the phone again after starting the application.
|
||||
|
||||
@@ -53,7 +53,7 @@ Sound packs can be found on the
|
||||
[myTeamSpeak website](https://www.myteamspeak.com/?search=&type=SOUNDPACK).
|
||||
They are often available as a `.ts3_soundpack` file.
|
||||
This file is similar to a `.zip` archive and can be unpacked the same way.
|
||||
Afterward, the folder containing the audio files (`.wav` files) needs to be inserted into the sound
|
||||
Afterward the folder containing the audio files (`.wav` files) needs to be inserted into the sound
|
||||
folder of TeamSpeak.
|
||||
For TeamSpeak3 on [Linux](/wiki/linux.md) systems this folder can be found at
|
||||
`/opt/teamspeak3/sound`.
|
||||
|
||||
@@ -26,5 +26,5 @@ Most of the times this can be fixed easily as explained in a
|
||||
[Reddit post by orestaras](https://www.reddit.com/r/firefox/comments/1hipkzh/ublock_origin_no_longer_works_on_youtube).
|
||||
Open the dashboard in the extension menu.
|
||||
Under the tab `Filter List`, extend `Built-in` and uncheck `uBlock filters - Quick fixes`.
|
||||
Afterward, reload the page containing the YouTube video and it should load normally and without
|
||||
Afterward reload the page containing the YouTube video and it should load normally and without
|
||||
advertisements.
|
||||
|
||||
@@ -46,5 +46,5 @@ When the message `Error: Verification failed: (0x1A) Security Violation` is show
|
||||
Ventoy stick it can easily be fixed.
|
||||
For this press `OK`, then press any key to perform MOK management.
|
||||
Select `Enroll key from disk`, `VTOYEFI` and `ENROLL_THIS_KEY_IN_MOKMANAGER.cer`.
|
||||
Afterward, select `Continue`, `Yes` and finally reboot by selecting `Reboot`.
|
||||
Afterward select `Continue`, `Yes` and finally reboot by selecting `Reboot`.
|
||||
After performing these steps the Ventoy key should work as usual.
|
||||
|
||||
@@ -34,7 +34,7 @@ This can be done by running the following command.
|
||||
wsl.exe -l -o
|
||||
```
|
||||
|
||||
Afterward, install the distribution.
|
||||
Afterward install the distribution.
|
||||
`<Distribution Name>` is the name of the distribution obtained in the previous stepa.
|
||||
|
||||
```powershell
|
||||
@@ -54,7 +54,7 @@ For example Ubuntu file system images can be found
|
||||
wsl --import <Distribution Name> <Install Location> <Install TarFile>
|
||||
```
|
||||
|
||||
Afterward, the default distribution may have to be set.
|
||||
Afterward the default distribution may have to be set.
|
||||
Once again `<DistributionName>` is the name of the distribution to make the new default.
|
||||
|
||||
```powershell
|
||||
|
||||
@@ -30,7 +30,7 @@ Wireguard clients connect to servers by using a `.conf` file.
|
||||
For mobile devices often times a QR-code can also be used.
|
||||
|
||||
In Linux based operating systems the `.conf` can be placed at the path `/etc/wireguard/wg0.conf`.
|
||||
Afterward, wireguard can be started and stopped by running the following commands.
|
||||
Afterward wireguard can be started and stopped by running the following commands.
|
||||
|
||||
```
|
||||
wg-quick up wg0
|
||||
|
||||
Reference in New Issue
Block a user