mirror of
https://github.com/tiyn/wiki.git
synced 2025-04-19 22:17:45 +02:00
Compare commits
No commits in common. "53846829358b87425049dcef9c9848f5c55e6a8a" and "c674f61876eb8fb583bdfcaa6895ebeca42b21ab" have entirely different histories.
5384682935
...
c674f61876
@ -7,14 +7,7 @@ The Arch User Repositories (AUR) features community-made packages that can be
|
|||||||
installed with different
|
installed with different
|
||||||
[package manager that inlcude access to the AUR](/wiki/linux/arch-linux/package_manager.md).
|
[package manager that inlcude access to the AUR](/wiki/linux/arch-linux/package_manager.md).
|
||||||
|
|
||||||
## Installation
|
## Installation Medium
|
||||||
|
|
||||||
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.
|
|
||||||
|
|
||||||
### ISO Medium
|
|
||||||
|
|
||||||
For the installation usage of a simple USB key is advised.
|
For the installation usage of a simple USB key is advised.
|
||||||
This has to be flashed with the Arch ISO.
|
This has to be flashed with the Arch ISO.
|
||||||
@ -24,20 +17,11 @@ 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`.
|
`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
|
`<path to ISO>` points the command to the location of the ISO file
|
||||||
|
|
||||||
## Recommended Practices
|
|
||||||
|
|
||||||
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
|
## Enable Microcode Updates
|
||||||
|
|
||||||
The microcode of Intel and AMD CPUs can be automatically updated by installing
|
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 `amd-ucode` or `intel-ucode` package depending on your CPU.
|
||||||
Not all processors are supported, especially old ones can lead to problems.
|
The following description assumes the system is installed with
|
||||||
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)
|
[UEFI bootloader](/wiki/linux/arch-linux/installation.md#10-install-and-configure-uefi-bootloader)
|
||||||
similar to the [recommended guide](/wiki/linux/arch-linux/installation.md).
|
similar to the [recommended guide](/wiki/linux/arch-linux/installation.md).
|
||||||
The microcode updates can then be enabled by adding the following line into
|
The microcode updates can then be enabled by adding the following line into
|
||||||
|
@ -209,9 +209,6 @@ this will install a bunch of useful base software including
|
|||||||
[a graphical environment](../x_window_system.md) and
|
[a graphical environment](../x_window_system.md) and
|
||||||
[a window manager](../suckless.md#programs).
|
[a window manager](../suckless.md#programs).
|
||||||
You can go on to other guides aswell.
|
You can go on to other guides aswell.
|
||||||
Especially the
|
|
||||||
[Recommended practices](/wiki/linux/arch-linux/arch-linux.md#recommended-practices)
|
|
||||||
should be checked for further setups.
|
|
||||||
|
|
||||||
Additionally if you have a NVidia Graphics Cards you should read
|
Additionally if you have a NVidia Graphics Cards you should read
|
||||||
[the NVidia article](../nvidia.md) too.
|
[the NVidia article](../nvidia.md) too.
|
||||||
|
@ -2,6 +2,7 @@
|
|||||||
|
|
||||||
DM-Crypt can create and manage encrypted devices.
|
DM-Crypt can create and manage encrypted devices.
|
||||||
|
|
||||||
|
|
||||||
## Usage
|
## Usage
|
||||||
|
|
||||||
### Creating an Encrypted Devices
|
### Creating an Encrypted Devices
|
||||||
|
@ -8,8 +8,8 @@ Easyeffects uses [Pipewire](./pipewire.md) as
|
|||||||
|
|
||||||
## Setup
|
## Setup
|
||||||
|
|
||||||
Easyeffects can be installed on most distributions by installing the
|
Easyeffects can be installed in most distributions by installing the
|
||||||
`easyeffects` package.
|
`easyeffects` plugin.
|
||||||
An installation via [Flatpak](./flatpak.md) is also possible.
|
An installation via [Flatpak](./flatpak.md) is also possible.
|
||||||
|
|
||||||
## Usage
|
## Usage
|
||||||
|
@ -2,10 +2,8 @@
|
|||||||
|
|
||||||
This article describes the `flac` package on linux.
|
This article describes the `flac` package on linux.
|
||||||
For the audio codec see the [flac entry](../flac_(codec).md)
|
For the audio codec see the [flac entry](../flac_(codec).md)
|
||||||
|
|
||||||
`flac` is a package to work with the [flac codec](../flac_(codec).md).
|
`flac` is a package to work with the [flac codec](../flac_(codec).md).
|
||||||
|
|
||||||
## Setup
|
|
||||||
|
|
||||||
On most distributions it is bundled together with the command line tagging
|
On most distributions it is bundled together with the command line tagging
|
||||||
software `metaflac` and other auxiliary tools in the `flac` package.
|
software `metaflac` and other auxiliary tools in the `flac` package.
|
||||||
Another possible tagging software is [MusicBrainz Picard](../picard.md)
|
Another possible tagging software is [MusicBrainz Picard](../picard.md)
|
||||||
|
@ -1,39 +0,0 @@
|
|||||||
# fwupd
|
|
||||||
|
|
||||||
[fwupd](https://fwupd.org/) is a daemon for managing and installing firmware
|
|
||||||
updates on Linux based operating systems.
|
|
||||||
It is mainly used for UEFI firmware and supported devices.
|
|
||||||
|
|
||||||
## Setup
|
|
||||||
|
|
||||||
fwupd can be installed on most distributions by installing the
|
|
||||||
`fwupd` package.
|
|
||||||
|
|
||||||
## Usage
|
|
||||||
|
|
||||||
The following commands describe the basic usage of an update process using
|
|
||||||
fwupd.
|
|
||||||
|
|
||||||
First the devices updatable by fwupd can be checked.
|
|
||||||
|
|
||||||
```sh
|
|
||||||
fwupdmgr get-devices
|
|
||||||
```
|
|
||||||
|
|
||||||
Afterwards the latest metadata can be downloaded by the following command.
|
|
||||||
|
|
||||||
```sh
|
|
||||||
fwupdmgr refresh
|
|
||||||
```
|
|
||||||
|
|
||||||
The updates can the be listed.
|
|
||||||
|
|
||||||
```sh
|
|
||||||
fwupdmgr get-updates
|
|
||||||
```
|
|
||||||
|
|
||||||
Finally the updates can be installed.
|
|
||||||
|
|
||||||
```sh
|
|
||||||
fwupdmgr update
|
|
||||||
```
|
|
@ -10,7 +10,7 @@ They provide motherboard chips, network interface controllers, flash memory,
|
|||||||
Intel graphics is the name for various intel made integrated graphics
|
Intel graphics is the name for various intel made integrated graphics
|
||||||
processors.
|
processors.
|
||||||
|
|
||||||
### Configuration
|
### Usage
|
||||||
|
|
||||||
#### Screen Tearing
|
#### Screen Tearing
|
||||||
|
|
||||||
|
@ -3,7 +3,7 @@
|
|||||||
Processor vendors release stability and security updates to the processor
|
Processor vendors release stability and security updates to the processor
|
||||||
microcode.
|
microcode.
|
||||||
|
|
||||||
## Setup
|
## Installation
|
||||||
|
|
||||||
Most Linux based operating systems feature packages depending on the processor
|
Most Linux based operating systems feature packages depending on the processor
|
||||||
manufacturer (on Arch Linux for example `intel-ucode` and `amd-ucode`).
|
manufacturer (on Arch Linux for example `intel-ucode` and `amd-ucode`).
|
||||||
|
@ -3,7 +3,7 @@
|
|||||||
NetworkManager - short NM - is a program to automatically detect and connect to
|
NetworkManager - short NM - is a program to automatically detect and connect to
|
||||||
networks by providing options for various configuration.
|
networks by providing options for various configuration.
|
||||||
|
|
||||||
## Setup
|
## Installation
|
||||||
|
|
||||||
NetworkManager can be installed with the `networkmanager` package on most linux
|
NetworkManager can be installed with the `networkmanager` package on most linux
|
||||||
distributions which provides daemon aswell as `nmcli` a command line interface
|
distributions which provides daemon aswell as `nmcli` a command line interface
|
||||||
|
@ -2,7 +2,7 @@
|
|||||||
|
|
||||||
NVidia is a vendor for graphics cards.
|
NVidia is a vendor for graphics cards.
|
||||||
|
|
||||||
## Setup
|
## Setup NVidia GPU
|
||||||
|
|
||||||
For NVidia GPUs to work install the `nvidia` and the `nvidia-utils` package.
|
For NVidia GPUs to work install the `nvidia` and the `nvidia-utils` package.
|
||||||
If you want to easily configure the monitors as described in a later section of
|
If you want to easily configure the monitors as described in a later section of
|
||||||
|
@ -4,6 +4,9 @@
|
|||||||
|
|
||||||
## Setup
|
## Setup
|
||||||
|
|
||||||
|
|
||||||
|
### Arch-Linux
|
||||||
|
|
||||||
Sc-im can be installed via [github](https://github.com/andmarti1424/sc-im).
|
Sc-im can be installed via [github](https://github.com/andmarti1424/sc-im).
|
||||||
Some distributions also feature the `sc-im` package.
|
Some distributions also feature the `sc-im` package.
|
||||||
|
|
||||||
|
@ -3,7 +3,7 @@
|
|||||||
A shell is a command-line interpreter that provides a command-line interface to
|
A shell is a command-line interpreter that provides a command-line interface to
|
||||||
interact with the many unix-like system.
|
interact with the many unix-like system.
|
||||||
|
|
||||||
## Change the standard shell
|
## Change /bin/sh
|
||||||
|
|
||||||
The Shell in some distributions is made up by a POSIX compliant mode of bash.
|
The Shell in some distributions is made up by a POSIX compliant mode of bash.
|
||||||
Problem with that is the speed.
|
Problem with that is the speed.
|
||||||
@ -15,27 +15,3 @@ dash.
|
|||||||
- `sudo ln -sfT /bin/dash /bin/sh` - link /bin/sh to dash
|
- `sudo ln -sfT /bin/dash /bin/sh` - link /bin/sh to dash
|
||||||
- `sudo vim /usr/share/libalpm/hooks/bash-update.hook` - setup a hook to avoid
|
- `sudo vim /usr/share/libalpm/hooks/bash-update.hook` - setup a hook to avoid
|
||||||
bash resetting the symlink
|
bash resetting the symlink
|
||||||
|
|
||||||
## Disown a Command
|
|
||||||
|
|
||||||
This section is based on a guide by
|
|
||||||
[baeldung](https://www.baeldung.com/linux/detach-process-from-terminal).
|
|
||||||
Disowning a command removes it from the current shell.
|
|
||||||
Commands that are detached from a shell will not terminate upon its closure.
|
|
||||||
A command can be disowned simply by appending `& disown` at the end of it.
|
|
||||||
It will then provide the PID of the command that got disowned.
|
|
||||||
|
|
||||||
## Silencing a Command
|
|
||||||
|
|
||||||
This section is based on a guide by
|
|
||||||
[baeldung](https://www.baeldung.com/linux/silencing-bash-output).
|
|
||||||
If the output of a command is unwanted it can be silenced.
|
|
||||||
There are two parts that can be silenced independently.
|
|
||||||
Non-error outputs (stdout) can be silenced by appending `1> /dev/null` to the
|
|
||||||
command.
|
|
||||||
Due to the `1` being ommitable `> /dev/null` has the same effect.
|
|
||||||
Error outputs (stderr) can be silenced by appending `2> /dev/null`.
|
|
||||||
The complete output of both stderr and stdout can be silenced by appending
|
|
||||||
`> /dev/null 2>&1` to the command.
|
|
||||||
A shortened version of it not possible on all shells is `&> /dev/null`.
|
|
||||||
|
|
||||||
|
12
wiki/obs.md
12
wiki/obs.md
@ -2,8 +2,6 @@
|
|||||||
|
|
||||||
[Open Broadcaster Software](https://obsproject.com) - short OBS - is a free
|
[Open Broadcaster Software](https://obsproject.com) - short OBS - is a free
|
||||||
and open source software for video recording and live streaming.
|
and open source software for video recording and live streaming.
|
||||||
Additionally see the
|
|
||||||
[the webcams entry](/wiki/linux/webcams.md#configure-the-webcam) if on Linux.
|
|
||||||
|
|
||||||
## Plugins
|
## Plugins
|
||||||
|
|
||||||
@ -21,10 +19,12 @@ camera.
|
|||||||
First of all [V4L2](./linux/v4l2.md) needs to be set up.
|
First of all [V4L2](./linux/v4l2.md) needs to be set up.
|
||||||
This guide assumes it is set up according to the section in the
|
This guide assumes it is set up according to the section in the
|
||||||
[V4L2 entry](./linux/v4l2.md#v4l2loopback).
|
[V4L2 entry](./linux/v4l2.md#v4l2loopback).
|
||||||
Make sure to
|
Make sure to start and/or enable it.
|
||||||
[start the service](/wiki/linux/systemd.md#startstopenabledisable-a-service) by
|
Additionally `obs-v4l2sink` needs to be installed.
|
||||||
running `systemctl start v4l2loopback.service` or enable it to start after each
|
Under `Tools/v4l2sink` select the device path set up in V4L2.
|
||||||
boot with `systemctl enable v4l2loopback.service`.
|
Select the same video format as set for your camera.
|
||||||
|
For Linux see [the webcams entry](/wiki/linux/webcams.md#configure-the-webcam)
|
||||||
|
to configure the video format.
|
||||||
Afterwards the virtual camera can be started.
|
Afterwards the virtual camera can be started.
|
||||||
|
|
||||||
### Background Removal
|
### Background Removal
|
||||||
|
Loading…
x
Reference in New Issue
Block a user