mirror of
https://github.com/tiyn/wiki.git
synced 2026-09-13 18:41:35 +02:00
Restructuring: Fixed links
This commit is contained in:
@@ -2,9 +2,9 @@
|
||||
|
||||
This guide is based upon a
|
||||
[german arch wiki article](https://wiki.archlinux.de/title/Installation_mit_UEFI_und_Verschl%C3%BCsselung).
|
||||
For encryption [dm-crypt](../dm-crypt.md) is used.
|
||||
For encryption [dm-crypt](/wiki/linux/dm-crypt.md) is used.
|
||||
Inside the encrypted partition a logical volume will be created with
|
||||
[LVM](../lvm.md).
|
||||
[LVM](/wiki/linux/lvm.md).
|
||||
|
||||
At the end of this guide a fully functional Arch Linux will be installed.
|
||||
|
||||
@@ -235,8 +235,8 @@ This can easily be done by using `nmtui`.
|
||||
Now you can follow the recommended larbs installation script of this wiki
|
||||
(`curl -LO larbs.sh https://raw.githubusercontent.com/tiyn/larbs/master/larbs.sh`)
|
||||
this will install a bunch of useful base software including
|
||||
[a graphical environment](../x_window_system.md) and
|
||||
[a window manager](../suckless.md#programs).
|
||||
[a graphical environment](/wiki/linux/x_window_system.md) and
|
||||
[a window manager](/wiki/linux/suckless.md).
|
||||
You can go on to other guides aswell.
|
||||
Especially the
|
||||
[Recommended practices](/wiki/linux/arch-linux.md#recommended-practices)
|
||||
@@ -247,11 +247,11 @@ This is discussed in
|
||||
[the package manager entry](/wiki/linux/package_manager/pacman_and_aur.md#error-during-updating-is-marginal-trust).
|
||||
|
||||
Additionally if you have a NVidia Graphics Cards you should read
|
||||
[the NVidia article](../nvidia.md) too.
|
||||
[the NVidia article](/wiki/linux/nvidia.md) too.
|
||||
|
||||
If you are interested in automatic decryption of the dm-crypt encrypted
|
||||
partition, take a look at the according section in
|
||||
[the dm-crypt article](../dm-crypt.md).
|
||||
[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.
|
||||
|
||||
@@ -9,9 +9,9 @@ For non-Linux specific audio software navigate to the corresponding
|
||||
A sound server is software that manages use and access of audio devices.
|
||||
The following is a list of available sound servers.
|
||||
|
||||
- [PulseAudio](./pulseaudio.md) is the go-to sound server program used for
|
||||
linux.
|
||||
- [Pipewire](./pipewire.md) is a modern graph based sound server.
|
||||
- [PulseAudio](/wiki/linux/pulseaudio.md) is the go-to sound server program used for
|
||||
linux.
|
||||
- [Pipewire](/wiki/linux/pipewire.md) is a modern graph based sound server.
|
||||
|
||||
## Noise cancellation
|
||||
|
||||
|
||||
@@ -1,7 +1,7 @@
|
||||
# Date
|
||||
|
||||
`date` is a program to show and edit the date and time of a system.
|
||||
To change the hardware clock look at the [according article](./hwclock.md)
|
||||
To change the hardware clock look at the [according article](/wiki/linux/hwclock.md)
|
||||
|
||||
## Display time and date
|
||||
|
||||
|
||||
@@ -1,12 +1,13 @@
|
||||
# Disk Management
|
||||
|
||||
This article focusses on non-LVM and non-MDADM storage including swap.
|
||||
For [LVM](lvm.md), [NTFS](./ntfs.md), [Samba](./samba.md), [MDADM](./mdadm.md) and [LUKS volumes](./dm-crypt.md) there
|
||||
are separate entries.
|
||||
This article focuses on non-LVM and non-MDADM storage including swap.
|
||||
For [LVM](/wiki/linux/lvm.md), [NTFS](/wiki/linux/ntfs.md), [Samba](/wiki/linux/samba.md),
|
||||
[MDADM](/wiki/linux/mdadm.md) and [LUKS volumes](/wiki/linux/dm-crypt.md) there are separate
|
||||
entries.
|
||||
|
||||
## Usage
|
||||
|
||||
This section focusses on various usages for disk management related topics.
|
||||
This section focuses on various usages for disk management related topics.
|
||||
|
||||
### Increasing Swap File Size
|
||||
|
||||
@@ -21,7 +22,7 @@ free -h
|
||||
|
||||
Then the swap file can be changed using the following commands.
|
||||
`<location>` is the location of the swap file (for example `/swap.img`).
|
||||
`<size>` describes the new size of the swap file (for example `16G`)
|
||||
`<size>` describes the new size of the swap file (for example `16G`).
|
||||
|
||||
```sh
|
||||
swapoff <location>
|
||||
@@ -31,7 +32,7 @@ mkswap <location>
|
||||
swapon <location>
|
||||
```
|
||||
|
||||
Finally the swap can be checked again to confirm that it is online and has the correct size
|
||||
Finally, the swap can be checked again to confirm that it is online and has the correct size.
|
||||
|
||||
```sh
|
||||
swapon --show
|
||||
@@ -57,11 +58,10 @@ cat /mnt/usb1/tmp | pv > /dev/zero
|
||||
|
||||
### Universally Unique identifier
|
||||
|
||||
Universally Unique identifier (UUID) are identifiers for informations on
|
||||
computer systems.
|
||||
Most notably they are used to identify file systems.
|
||||
This way the UUID of a file system can be used to identify and
|
||||
[mount it](#mounting) persistently and correctly.
|
||||
Universally Unique identifier (UUID) are identifiers for information on computer systems.
|
||||
Most notably they are used, to identify file systems.
|
||||
This way the UUID of a file system can be used to identify and [mount it](#mounting) persistently
|
||||
and correctly.
|
||||
|
||||
By listing the directory `/dev/disk/by-partuuid` all mappings of devices to a
|
||||
UUID are displayed.
|
||||
@@ -72,23 +72,27 @@ Mounting a file system makes the files of it accessible to the user.
|
||||
The command `mount` is used to manually and temporarily mount file systems.
|
||||
Automatic mounting is done by changing the file `/etc/fstab`.
|
||||
|
||||
The exact guide on how to mount specific file systems can be found in their
|
||||
respecitive wiki entries.
|
||||
The following describes the general basics of mounting temporarily and
|
||||
persistently.
|
||||
The exact guide on how to mount specific file systems can be found in their respective wiki
|
||||
entries.
|
||||
The following describes the general basics of mounting temporarily and persistently.
|
||||
|
||||
The basic mount command for temporarily accessing a file system is the
|
||||
following:
|
||||
`mount <path to partition> <path to mount point>`
|
||||
All partitions can be found at `/dev` and the standard mount point is `/mnt` and
|
||||
its subfolders.
|
||||
The basic mount command for temporarily accessing a file system is the following.
|
||||
|
||||
```sh
|
||||
mount <path to partition> <path to mount point>
|
||||
```
|
||||
|
||||
All partitions can be found at `/dev` and the standard mount point is `/mnt` and its subfolders.
|
||||
|
||||
For automatic mounting the following line has to be adapted and added to the file `/etc/fstab`.
|
||||
|
||||
```txt
|
||||
<specified partition> <path to mount point> <file system> <additional options> <dump flag> <fsck order>
|
||||
```
|
||||
|
||||
For automatic mounting the following line has to be adapted and added to the
|
||||
file `/etc/fstab`
|
||||
`<specified partition> <path to mount point> <file system> <additional options> <dump flag> <fsck order>`
|
||||
The partition can be specified by [UUID](#universally-unique-identifier).
|
||||
The file system varies and a file system specific guide on how to mount them
|
||||
can be found in their respective entries.
|
||||
The file system varies and a file system specific guide on how to mount them can be found in their
|
||||
respective entries.
|
||||
The dump flag signals if the file system should be dumped.
|
||||
The `fsck` order signals if a file system should be checked at boot.
|
||||
Boot partitions should be flagged with a `1` for this reason, otherwise `0`.
|
||||
@@ -113,33 +117,30 @@ In the following it is assumed that the disk is `/dev/sda`
|
||||
- create a primary partition (ext4 format) with `mkpart primary 2048s 100%`
|
||||
- `quit` parted
|
||||
|
||||
`<path to partition>` points to the partition that will be enlarged (for
|
||||
example `/dev/sda2`).
|
||||
`<path to partition>` points to the partition that will be enlarged (for example `/dev/sda2`).
|
||||
|
||||
### Grow non-LVM partition
|
||||
|
||||
ATTENTION: Please note that the partition to enlarge has to be the last one with
|
||||
the free space after it.
|
||||
Please note that the partition to enlarge has to be the last one with the free space after it.
|
||||
|
||||
In the following it is assumed that the partition to enlarge is `/dev/sda2`
|
||||
|
||||
- change the size of the partition with `parted /dev/sda`
|
||||
- inside of parted run `print free` and check where the free space after your
|
||||
partition ends
|
||||
- run `resizepart` and follow the instructions; End is the number you checked in
|
||||
the last step (alternatively you can insert `100%` as end, if you want to add all
|
||||
the available free space to the partition)
|
||||
partition ends
|
||||
- run `resizepart` and follow the instructions; End is the number you checked in the last step
|
||||
(alternatively you can insert `100%` as end, if you want to add all the available free space to
|
||||
the partition)
|
||||
- `quit` parted
|
||||
|
||||
Afterwards the file system need to be resized as described in a
|
||||
[later section](#growing-a-file-system).
|
||||
Afterward, the file system needs to be resized as described in the
|
||||
[corresponding section](#growing-a-file-system).
|
||||
|
||||
### Growing a File System
|
||||
|
||||
A file system can easily be resized if free space is available on the partition
|
||||
it is stored in.
|
||||
A file system can easily be resized if free space is available on the partition it is stored in.
|
||||
The free space has to be placed behind the partition.
|
||||
This can be done by running the following command:
|
||||
This can be done by running the following command.
|
||||
|
||||
```sh
|
||||
sudo resize2fs <path to partition>
|
||||
@@ -150,20 +151,20 @@ sudo resize2fs <path to partition>
|
||||
To shrink a file system the `resize2fs` command will be used aswell as `e2fsck`.
|
||||
First the file system needs to be checked for size aswell as data distribution.
|
||||
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 aswell.
|
||||
Afterwards the file system can be shrinked with the command
|
||||
`<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
|
||||
`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`).
|
||||
`<new size of the file system>` is the size that the file system will be shrunken to in the usual
|
||||
notation (for example `12G`).
|
||||
Especially for large file systems this might take a while.
|
||||
|
||||
### Clearing System Trash Bin
|
||||
|
||||
The system trash bin by default can be found at `~/.local/share/Trash`.
|
||||
The system moves deleted files there automatically.
|
||||
It can be deleted by hand, deleting all files from the subdirectories of the trash folder
|
||||
It can be deleted by hand, deleting all files from the subdirectories of the trash folder.
|
||||
Another option is to use the tool `trash-cli` with the command `trash-empty`.
|
||||
|
||||
### Removing Unused Files
|
||||
@@ -190,27 +191,24 @@ usermod -a -G disk $USER
|
||||
|
||||
## Error solving
|
||||
|
||||
This section addresses various problems that can occur and are related to
|
||||
disk-management.
|
||||
This section addresses various problems that can occur and are related to disk-management.
|
||||
|
||||
### `sudo: unable to open ... Read-only file system`
|
||||
|
||||
Ususally the filesystem will go into read-only mode whe the system is running
|
||||
and there is a consistency error.
|
||||
To fix it run:
|
||||
Ususally the filesystem will go into read-only mode whe the system is running and there is a
|
||||
consistency error.
|
||||
To fix it run the following command.
|
||||
|
||||
- `sudo fsck -Af -M` - check all filesystems
|
||||
If `fsck` gets stuck after its version banner:
|
||||
`fsck from util-linux 2.20.1`
|
||||
you may want to try using the ext4-specific fsck:
|
||||
- `sudo fsck -Af -M` - check all filesystems
|
||||
If `fsck` gets stuck after its version banner (for example `fsck from util-linux 2.20.1`) you
|
||||
may want to try using the ext4-specific fsck:
|
||||
- `fsck.ext4 -f /dev/sda1`
|
||||
|
||||
### `cannot access: Transport endpoint is not connected`
|
||||
|
||||
This error message can occur if a mounted directory is left mounted due to a
|
||||
crash of the filesystem but not accessible anymore.
|
||||
This error can be fixed and the directory made accessible again by running the
|
||||
following command.
|
||||
This error message can occur if a mounted directory is left mounted due to a crash of the
|
||||
file system but not accessible anymore.
|
||||
This error can be fixed and the directory made accessible again by running the following command.
|
||||
|
||||
```sh
|
||||
fusermount -u <path to mount point>
|
||||
|
||||
@@ -1,57 +1,59 @@
|
||||
# Dislocker
|
||||
|
||||
[Dislocker](https://github.com/Aorimn/dislocker) is a driver to read and write
|
||||
Bitlocker-ed volumes under Linux systems.
|
||||
[Dislocker](https://github.com/Aorimn/dislocker) is a driver to read and write Bitlocker encrypted
|
||||
volumes under Linux systems.
|
||||
|
||||
## Setup
|
||||
|
||||
On most of the Linux distributions Dislocker is bundled with the `dislocker`
|
||||
package.
|
||||
The installation of the `mbedtls2` package as an open-source TLS library can be
|
||||
of use.
|
||||
On most of the Linux distributions Dislocker is bundled with the `dislocker` package.
|
||||
The installation of the `mbedtls2` package as an open-source TLS library can be of use.
|
||||
|
||||
## Usage
|
||||
|
||||
### Manual Mounting of Bitlocker Partition
|
||||
|
||||
For the [mounting](/wiki/linux/disk-management.md#mounting) to work two directories
|
||||
are required.
|
||||
For the [mounting](/wiki/linux/disk-management.md#mounting) to work two directories are required.
|
||||
One to mount the `dislocker-file` (`/mnt/bitlocker`) and one to mount the
|
||||
[windows volume](/wiki/linux/ntfs.md#manual-mounting) (`/mnt/windows`).
|
||||
The device which holds the windows partition is assumed to be calles
|
||||
`/dev/sdc1`.
|
||||
The device which holds the windows partition is assumed to be calles `/dev/sdc1`.
|
||||
|
||||
The following command mounts the `dislocker` file to `/mnt/bitlocker`.
|
||||
Make sure to replace the password in the following command.
|
||||
There is no gap between the `-u` and the password:
|
||||
`sudo dislocker /dev/sdc1 -u<password> -- /mnt/bitlocker`.
|
||||
If the Bitlocker partition is set up using a `.BEK` file then the follwing
|
||||
command takes the path to the file in:
|
||||
`sudo dislocker /dev/sdb2 -f <path to bek-file> -- /mnt/bitlocker`
|
||||
Alternatively a recovery key can be used:
|
||||
`sudo dislocker /dev/sdc1 -p<recovery password> -- /mnt/bitlocker`.
|
||||
There is no gap between the `-u` and the password.
|
||||
|
||||
Afterwards 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).
|
||||
```sh
|
||||
sudo dislocker /dev/sdc1 -u<password> -- /mnt/bitlocker
|
||||
```
|
||||
|
||||
If the Bitlocker partition is set up using a `.BEK` file then the following
|
||||
command takes the path to the file in.
|
||||
|
||||
```sh
|
||||
sudo dislocker /dev/sdb2 -f <path to bek-file> -- /mnt/bitlocker
|
||||
```
|
||||
|
||||
Alternatively a recovery key can be used.
|
||||
|
||||
```sh
|
||||
sudo dislocker /dev/sdc1 -p<recovery password> -- /mnt/bitlocker
|
||||
```
|
||||
|
||||
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
|
||||
|
||||
Using [fstab](/wiki/linux/disk-management.md#mounting) the partition encrypted with
|
||||
Bitlocker can be automatically mounted.
|
||||
Using [fstab](/wiki/linux/disk-management.md#mounting) the partition encrypted with Bitlocker can
|
||||
be automatically mounted.
|
||||
The following lines have to be adapted and written into
|
||||
[`/etc/fstab`](/wiki/linux/disk-management.md#mounting).
|
||||
In this case the intermediary dislocker file `dislocker-file` is mounted to
|
||||
`/mnt/bitlocker`.
|
||||
In this case the intermediary dislocker file `dislocker-file` is mounted to `/mnt/bitlocker`.
|
||||
|
||||
```txt
|
||||
UUID=<partition uuid> /mnt/bitlocker fuse.dislocker bekfile=<path to bek-file>,nofail 0 0
|
||||
```
|
||||
|
||||
After that a line to mount the `dislocker-file` as a [NTFS](./ntfs.md) partition
|
||||
has to be added as described in
|
||||
[the NTFS entry](/wiki/linux/ntfs.md#automatic-mounting).
|
||||
In this case the specified partition to mount is
|
||||
`/mnt/bitlocker/dislocker-file`.
|
||||
The mount point can be chosen according to preference - for example
|
||||
`/mnt/windows`.
|
||||
After that a line to mount the `dislocker-file` as a [NTFS](/wiki/linux/ntfs.md) partition has to
|
||||
be added as described in [the NTFS entry](/wiki/linux/ntfs.md#automatic-mounting).
|
||||
In this case the specified partition to mount is `/mnt/bitlocker/dislocker-file`.
|
||||
The mount point can be chosen according to preference - for example `/mnt/windows`.
|
||||
|
||||
@@ -24,7 +24,7 @@ dd bs=512 count=4 if=/dev/random of=<path to destination>
|
||||
```
|
||||
|
||||
It is possible to increase the length to get a stronger key file.
|
||||
Alternatively strong LUKS keys can be created using [OpenSSL](./openssl.md)
|
||||
Alternatively strong LUKS keys can be created using [OpenSSL](/wiki/linux/openssl.md)
|
||||
using a bitlength of 4096:
|
||||
`openssl genrsa -out <path to destination> 4096`.
|
||||
The key file will then be saved to `<path to destination>`.
|
||||
@@ -50,7 +50,7 @@ Open the encrypted volume:
|
||||
Now resize the encrypted volume to all available space of the partition.
|
||||
If the encrypted volume should not be extended to the whole partition
|
||||
or the partition is too small for its intended purposes, make sure to resize the
|
||||
partition first accordingly (see [disk management](./disk-management.md)).
|
||||
partition first accordingly (see [disk management](/wiki/linux/disk-management.md)).
|
||||
`cryptsetup resize crypt-volume`
|
||||
|
||||
### Open/Close an Encrypted Volume
|
||||
@@ -73,7 +73,7 @@ Afterwards it can be closed by running `cryptsetup close /dev/mapper/crypt0`.
|
||||
### Creating/Add a USB Decryption Key
|
||||
|
||||
This guide assumes an Arch Linux System, as installed in
|
||||
[this wikis arch linux installation](./arch-linux/installation.md).
|
||||
[this wikis arch linux installation](/wiki/linux/arch-linux/installation.md).
|
||||
This section is based on entries from the
|
||||
[arch linux forum](https://forum.archlinux.de/d/28886-systementschluesselung-per-usb-stick).
|
||||
It uses a similar technique to the decryption of the encrypted volume via
|
||||
|
||||
@@ -1,21 +1,22 @@
|
||||
# Easyeffects
|
||||
# EasyEffects
|
||||
|
||||
[Easyeffects](https://github.com/wwmm/easyeffects) is a free and open-source GUI-software for
|
||||
[EasyEffects](https://github.com/wwmm/easyeffects) is a free and open-source GUI-software for
|
||||
applying sound effects and filters on input and output audio streams.
|
||||
Easyeffects uses [Pipewire](./pipewire.md) as [sound server](/wiki/linux/audio.md#sound-server).
|
||||
EasyEffects uses [Pipewire](/wiki/linux/pipewire.md) as
|
||||
[sound server](/wiki/linux/audio.md#sound-server).
|
||||
|
||||
## Setup
|
||||
|
||||
Easyeffects can be installed on most distributions by installing the `easyeffects` package.
|
||||
An installation via [Flatpak](./flatpak.md) is also possible.
|
||||
EasyEffects can be installed on most distributions by installing the `easyeffects` package.
|
||||
An installation via [Flatpak](/wiki/linux/flatpak.md) is also possible.
|
||||
|
||||
## Usage
|
||||
|
||||
Easyeffects can apply `Effects` to input and output sound.
|
||||
EasyEffects can apply `Effects` to input and output sound.
|
||||
|
||||
### Autostart
|
||||
|
||||
Easyeffects can be started in various ways.
|
||||
EasyEffects can be started in various ways.
|
||||
|
||||
The service can be started including the window with the following.
|
||||
It will have to be called each startup.
|
||||
@@ -62,11 +63,10 @@ WantedBy=graphical-session.target
|
||||
|
||||
### Noise cancellation
|
||||
|
||||
Setup
|
||||
Noise cancellation can be achieved by installing Easyeffects.
|
||||
Noise cancellation can be achieved by installing EasyEffects.
|
||||
Make sure to check the box `Process all Inputs` and `Process all Outputs` to route everything
|
||||
through `easyeffects`.
|
||||
Make log out of your system afterwards.
|
||||
Make log out of your system afterward.
|
||||
To enable noise cancellation navigate `Inputs` and click `Plugins`.
|
||||
After that click `Add Plugin` and select `Noise Reduction`.
|
||||
|
||||
|
||||
@@ -1,14 +1,14 @@
|
||||
# flac (Package)
|
||||
|
||||
This article describes the `flac` package on linux.
|
||||
For the audio codec see the [flac entry](../flac_(codec).md)
|
||||
`flac` is a package to work with the [flac codec](../flac_(codec).md).
|
||||
For the audio codec see the [flac entry](/wiki/flac_%28codec%29.md)
|
||||
`flac` is a package to work with the [flac codec](/wiki/flac_%28codec%29.md).
|
||||
|
||||
## Setup
|
||||
|
||||
On most distributions it is bundled together with the command line tagging
|
||||
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](/wiki/picard.md)
|
||||
|
||||
## Usage
|
||||
|
||||
@@ -38,6 +38,7 @@ According to a
|
||||
[Reddit comment by berdmayne](https://www.reddit.com/r/foobar2000/comments1m3634l/best_way_to_reduce_flac_file_size_without_losing)
|
||||
the compression rates of the different levels are the following.
|
||||
|
||||
|
||||
| Level | Saving to level 0 | Saving to previous level |
|
||||
| ---------------- | ------------------- | ------------------------ |
|
||||
| 0 (uncompressed) | 0.0% | |
|
||||
|
||||
@@ -9,17 +9,16 @@
|
||||
We will use `/dev/sdb` as our drive.
|
||||
Setup the disk for the physical volume with `sgdisk -N 1 /dev/sdb`.
|
||||
Then create the physical volume `pvcreate /dev/sdb`.
|
||||
The previous step can come to a halt when the device already contains an old
|
||||
partition table and will display the error `Device /dev/sdb excluded by a filter`.
|
||||
The previous step can come to a halt when the device already contains an old partition table and
|
||||
will display the error `Device /dev/sdb excluded by a filter`.
|
||||
This can be solved by removing the old partition table with `wipefs -a /dev/sdb`.
|
||||
And finally create the volume group `vgcreate vmdata /dev/sdb`.
|
||||
Then follow the guide in proxmox on how to connect a `vg` to proxmox.
|
||||
Then follow the guide in Proxmox on how to connect a `vg` to Proxmox.
|
||||
|
||||
### Add Physical Volume to Existing Volume Group
|
||||
|
||||
First format the disk so that it has one partition (we will assume its called
|
||||
`/dev/sdc1`).
|
||||
To add the partition to a group run:
|
||||
First format the disk so that it has one partition (we will assume it is called `/dev/sdc1`).
|
||||
To add the partition to a group run run the following command.
|
||||
|
||||
```sh
|
||||
pvcreate /dev/sdc1
|
||||
@@ -48,32 +47,31 @@ sudo pvremove <path to physical volume>
|
||||
To increase the size of a physical volume you have to have free free space
|
||||
in the partition containing the physical volume.
|
||||
A guide to change 'normal' partitions can be found in the
|
||||
[disk management article](./disk-management.md); if you have a volume that is
|
||||
encrypted with LUKS a guide is available in
|
||||
[the dm-crypt articel](./dm-crypt.md).
|
||||
[disk management article](/wiki/linux/disk-management.md); if you have a volume that is encrypted
|
||||
with LUKS a guide is available in [the dm-crypt articel](/wiki/linux/dm-crypt.md).
|
||||
|
||||
To resize the physical volume to the size of the containing volume run:
|
||||
`pvresize /dev/mapper/<name of physical volume>`
|
||||
|
||||
### Increase Size of a Logical Volume
|
||||
|
||||
To increase the size of the logical volume you have to have free space in the
|
||||
according volume group. You can check that by running: `vgdisplay`.
|
||||
If you don't have enough space you have to resize the physical volume as
|
||||
described in this article.
|
||||
Then run:
|
||||
To increase the size of the logical volume you have to have free space in the according volume
|
||||
group.
|
||||
You can check that by running: `vgdisplay`.
|
||||
If you don't have enough space you have to resize the physical volume as described in this article.
|
||||
Then run the following command.
|
||||
|
||||
```sh
|
||||
lvextend -L +<size (e.g. 40G)> /dev/<volume groupt>/<logical volume>
|
||||
```
|
||||
|
||||
If you want to allocate all the free space existing in a volume group run:
|
||||
If you want to allocate all the free space existing in a volume group run the following command.
|
||||
|
||||
```sh
|
||||
lvextend -l +100%FREE /dev/<volume group>/<logical volume>
|
||||
```
|
||||
|
||||
Now you need to extend the file system with:
|
||||
Now you need to extend the file system with the following command.
|
||||
|
||||
```sh
|
||||
resize2fs /dev/<volume group>/<logical volume>
|
||||
@@ -81,28 +79,25 @@ resize2fs /dev/<volume group>/<logical volume>
|
||||
|
||||
### Shrink Size of a Logical Volume
|
||||
|
||||
When trying to shrink a logical volume caution is advised as data can easily be
|
||||
destroyed by mistyping commands of paths.
|
||||
When trying to shrink a logical volume caution is advised as data can easily be destroyed by
|
||||
mistyping commands of paths.
|
||||
This section is based on a guide given by
|
||||
[telcoM](https://unix.stackexchange.com/questions/591389/how-to-remove-a-disk-from-an-lvm-partition).
|
||||
First of all the volumes have to be unmounted and not used by any programs or
|
||||
services other than the following commands.
|
||||
First of all the volumes have to be unmounted and not used by any programs or services other than
|
||||
the following commands.
|
||||
|
||||
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.
|
||||
Afterwards the operating system has to be booted from the just created stick or
|
||||
a comparable device.
|
||||
[The Arch Linux entry](/wiki/linux/arch-linux.md#installation-medium) describes the creation of
|
||||
such a boot stick.
|
||||
Afterwards 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.
|
||||
|
||||
The volume group needs to be activated by running the command
|
||||
`sudo vgchange -ay <volume group>`.
|
||||
`<volume group>` is the name of the volumegroup that features the logical volume
|
||||
to shrink.
|
||||
The volume group needs to be activated by running the command `sudo vgchange -ay <volume group>`.
|
||||
`<volume group>` is the name of the volumegroup that features the logical volume to shrink.
|
||||
Then the file system needs to be resized.
|
||||
For safety reasons make the file system exactly as big or smaller than the
|
||||
future logical volume.
|
||||
For safety reasons make the file system exactly as big or smaller than the future logical volume.
|
||||
The process of shrinking a file system is explained in the
|
||||
[disk management entry](/wiki/linux/disk-management.md#shrinking-a-file-system).
|
||||
The partition to shrink in this case is the logical volume.
|
||||
@@ -110,45 +105,44 @@ This is the only step that needs to be done offline for root volumes.
|
||||
Rebooting to the root volume at this moment is advised.
|
||||
|
||||
The next step will shrink the logical volume itself.
|
||||
This will be done by running the following command:
|
||||
This will be done by running the following command.
|
||||
|
||||
```sh
|
||||
sudo lvreduce -L <new size of logical volume> /dev/mapper/<volume group>-<logical volume>
|
||||
```
|
||||
|
||||
Again this statement has to be adapted accordingly.
|
||||
`new size of logical volume` describes the new size the logical volume will have
|
||||
after successful completion of the command.
|
||||
It is important for this to be exactly the same or larger than the size given
|
||||
into the resizing of the file system with `resize2fs`.
|
||||
`new size of logical volume` describes the new size the logical volume will have after successful
|
||||
completion of the command.
|
||||
It is important for this to be exactly the same or larger than the size given into the resizing of
|
||||
the file system with `resize2fs`.
|
||||
|
||||
### Remove Physical Volume from Volume Group
|
||||
|
||||
This section describes the removal of a physical volume from a logical volume.
|
||||
First the command `vgs <volume group>` has to be run.
|
||||
`<volume group>` is the name of the volume group belonging to the logical volume
|
||||
a physical volume should be removed from.
|
||||
It has to be ensured, that enough free space (`VFree`) on all physical volumes
|
||||
(except the ones to remove) is available to remove a physical volume from the
|
||||
volume group.
|
||||
There has to be equal or more free space than the size (`VSize`) of the physical
|
||||
volume that will be removed.
|
||||
`<volume group>` is the name of the volume group belonging to the logical volume a physical volume
|
||||
should be removed from.
|
||||
It has to be ensured, that enough free space (`VFree`) on all physical volumes (except the ones to
|
||||
remove) is available to remove a physical volume from the volume group.
|
||||
There has to be equal or more free space than the size (`VSize`) of the physical volume that will
|
||||
be removed.
|
||||
Otherwise an [earlier section](#shrink-size-of-a-logical-volume) explains how to
|
||||
shrink a logical volume.
|
||||
The logical volume has to be shrunk according to the described ration between
|
||||
`VFree` and `VSize`.
|
||||
|
||||
The following command will distribute the contents of a physical volume onto
|
||||
other physical volumes available:
|
||||
The following command will distribute the contents of a physical volume onto other physical volumes
|
||||
available.
|
||||
|
||||
```sh
|
||||
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.
|
||||
Afterwards the physical volume is emptied and can be removed from the logical
|
||||
volume by running the following command:
|
||||
`<path to physical volume>` is the physical volume that will get emptied and later removed from the
|
||||
logical volume.
|
||||
Afterwards the physical volume is emptied and can be removed from the logical volume by running the
|
||||
following command.
|
||||
|
||||
```sh
|
||||
sudo vgreduce <logical volume> <path to physical volume>
|
||||
@@ -157,10 +151,9 @@ sudo vgreduce <logical volume> <path to physical volume>
|
||||
`<logical volume>` is the name of the logical volume.
|
||||
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).
|
||||
If no longer used the empty physical volume can then be removed as described in the
|
||||
[according section](#remove-physical-volume).
|
||||
|
||||
Afterwards the file system can be matched to the logical volume so it takes up
|
||||
the full new size.
|
||||
Afterwards the file system can be matched to the logical volume so it takes up the full new size.
|
||||
This is explained in the
|
||||
[entry about disk management](/wiki/linux/disk-management.md#growing-a-file-system).
|
||||
:wq[entry about disk management](/wiki/linux/disk-management.md#growing-a-file-system).
|
||||
|
||||
@@ -1,6 +1,7 @@
|
||||
# NTFS
|
||||
|
||||
NTFS is the proprietary [file system](./disk-management.md) of Windows.
|
||||
NTFS is the proprietary [file system](/wiki/linux/disk-management.md) of
|
||||
[Windows](/wiki/windows.md).
|
||||
|
||||
## Setup
|
||||
|
||||
@@ -10,29 +11,31 @@ distributions - has to be installed.
|
||||
## Usage
|
||||
|
||||
When [mounting](/wiki/linux/disk-management.md#mounting) a
|
||||
[Bitlocker encrypted drive](./dislocker.md) there are additional steps that have
|
||||
to be taken to decrypt the device.
|
||||
[Bitlocker encrypted drive](/wiki/linux/dislocker.md) there are additional steps that have to be
|
||||
taken to decrypt the device.
|
||||
|
||||
### Manual Mounting
|
||||
|
||||
Partitions using NTFS can be mounted on Linux based operating systems by
|
||||
running the following command:
|
||||
`mount -t ntfs-3g -o loop <path to partition> <path to mount point>`.
|
||||
If the partition to mount is bootable or contains a windows system the
|
||||
hibernation and fast boot have to be disabled to mount the partition with write
|
||||
access.
|
||||
Partitions using NTFS can be mounted on Linux based operating systems by running the following
|
||||
command.
|
||||
|
||||
```sh
|
||||
mount -t ntfs-3g -o loop <path to partition> <path to mount point>
|
||||
```
|
||||
|
||||
If the partition to mount is bootable or contains a windows system the hibernation and fast boot
|
||||
have to be disabled to mount the partition with write access.
|
||||
|
||||
### Automatic Mounting
|
||||
|
||||
For the usage of NTFS file systems the `ntfs-3g` package - available on most
|
||||
distributions - has to be installed.
|
||||
To [automount partitions](/wiki/linux/disk-management.md#mounting) with NTFS
|
||||
the following line has to be adapted and added to `/etc/fstab`:
|
||||
For the usage of NTFS file systems the `ntfs-3g` package - available on most distributions - has to
|
||||
be installed.
|
||||
To [automount partitions](/wiki/linux/disk-management.md#mounting) with NTFS the following line has
|
||||
to be adapted and added to `/etc/fstab`.
|
||||
|
||||
```txt
|
||||
<specified partition> <path to mount point> ntfs-3g nofail,windows_names,big_writes 0 0
|
||||
```
|
||||
|
||||
If the partition to mount is bootable or contains a windows system the
|
||||
hibernation and fast boot have to be disabled to mount the partition with write
|
||||
access.
|
||||
If the partition to mount is bootable or contains a [Windows](/wiki/windows.md) system the
|
||||
hibernation and fast boot have to be disabled to mount the partition with write access.
|
||||
|
||||
@@ -23,7 +23,7 @@ Most configuration and changes require the use of `nvidia-settings`.
|
||||
|
||||
In `nvidia-setting` monitors can be dragged and dropped to your liking.
|
||||
After that you have to save the configuration to the
|
||||
[X window manager](./x_window_system.md) configuration file
|
||||
[X window manager](/wiki/linux/x_window_system.md) configuration file
|
||||
`/etc/X11/xorg.conf`.
|
||||
|
||||
### Avoid screen tearing
|
||||
|
||||
@@ -110,7 +110,7 @@ After that follow the instructions and fill in the fields to your liking.
|
||||
### Enlarging Disk of a VM
|
||||
|
||||
Make sure there is enough disk space available.
|
||||
For further information see [the disk management article](./disk-management.md)
|
||||
For further information see [the disk management article](/wiki/linux/disk-management.md)
|
||||
|
||||
SSH into Proxmox.
|
||||
Enlarge a disk by using:
|
||||
|
||||
@@ -1,20 +1,19 @@
|
||||
# RAR (package)
|
||||
|
||||
RAR is a package available for many Linux distributions that handles `.rar`
|
||||
archives of the [RAR algorithm](/wiki/rar_(algorithm).md).
|
||||
RAR is a package available for many Linux distributions that is handling `.rar` archives of the
|
||||
[RAR algorithm](/wiki/rar_%28algorithm%29.md).
|
||||
|
||||
## Setup
|
||||
|
||||
On most distributions the functionalities for creating a `.rar` archive is
|
||||
bundled in the `rar` package.
|
||||
On most distributions the functionalities for creating a `.rar` archive is bundled in the `rar`
|
||||
package.
|
||||
For extraction a separate package is used called `unrar`.
|
||||
|
||||
## Usage
|
||||
|
||||
### Extracting a `.rar` archive
|
||||
|
||||
A `.rar` archive can be extracted using the `unrar` package with the following
|
||||
command.
|
||||
A `.rar` archive can be extracted using the `unrar` package with the following command.
|
||||
|
||||
```sh
|
||||
unrar e <path to .rar file>
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
# Samba
|
||||
|
||||
[Samba](../samba.md) is the standard Windows interoperability suite for linux
|
||||
[Samba](/wiki/samba.md) is the standard Windows interoperability suite for linux
|
||||
and unix.
|
||||
|
||||
## Usage
|
||||
|
||||
@@ -12,7 +12,7 @@ shntool can be installed on most distributions by installing the `shntool` packa
|
||||
|
||||
### Splitting Audio Files According to a CUE File
|
||||
|
||||
An easy way to split audio files according to a [cue file](../cue_sheet.md) is
|
||||
An easy way to split audio files according to a [cue file](/wiki/cue_sheet.md) is
|
||||
using `shnsplit`.
|
||||
Alternatively the interface `cuebreakpoints` can be used which uses `shnsplit`.
|
||||
Note that some codecs require special setup.
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
# SystemD
|
||||
|
||||
SystemD is an [init system](./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
|
||||
@@ -32,9 +32,8 @@ ExecStart=/bin/bash /root/run.sh
|
||||
Type=simple
|
||||
```
|
||||
|
||||
For [Proxmox](./proxmox.md) you can add the following line under the `[Unit]`
|
||||
section to make sure the service is started after Proxmox has finished
|
||||
initializing.
|
||||
For [Proxmox](/wiki/linux/proxmox.md) you can add the following line under the `[Unit]` section to
|
||||
make sure the service is started after Proxmox has finished initializing.
|
||||
|
||||
```txt
|
||||
After=pve-guests.service
|
||||
@@ -46,8 +45,7 @@ A service that was created this way can then be started as explained in
|
||||
### Start/Stop/Enable/Disable a service and Retrieve its Logs
|
||||
|
||||
Services can be started by running `systemctl start <service-name>`.
|
||||
They respectively can be stopped by replacing the `start`
|
||||
keyword for `stop`.
|
||||
They respectively can be stopped by replacing the `start` keyword for `stop`.
|
||||
To start the service after boot it has to be enabled.
|
||||
This works accordingly with the keyword `enable`.
|
||||
The `disable` keyword stops the service from starting automatically.
|
||||
|
||||
@@ -1,7 +1,6 @@
|
||||
# V4L2
|
||||
|
||||
V4L2 is the second version of
|
||||
[Video4Linux](https://www.linuxtv.org/wiki/index.php/Main_Page).
|
||||
V4L2 is the second version of [Video4Linux](https://www.linuxtv.org/wiki/index.php/Main_Page).
|
||||
It functions as a driver for [webcams](/wiki/webcam.md) and [tv tuner cards](/wiki/video.md) and
|
||||
other devices.
|
||||
|
||||
@@ -10,17 +9,16 @@ other devices.
|
||||
The following section is based on a
|
||||
[gist by ioquatix](https://gist.github.com/ioquatix/18720c80a7f7eb997c19eef8afd6901e).
|
||||
|
||||
[v4l2loopback](https://github.com/umlaeute/v4l2loopback) is a utility to create
|
||||
a virtual video device.
|
||||
[v4l2loopback](https://github.com/umlaeute/v4l2loopback) is a utility to create a virtual video
|
||||
device.
|
||||
One use of it is in [OBS Virtual Camera](/wiki/obs.md#virtual-camera).
|
||||
|
||||
### Setup
|
||||
|
||||
To use v4l2loopback an according
|
||||
package needs to be installed.
|
||||
Some distributions have a package named `v4l2loopback-dkms` in the package
|
||||
manager, making the manual installation process unnecessary.
|
||||
Make sure that both `dkms` and `linux-headers` packages are installed aswell.
|
||||
To use v4l2loopback an according package needs to be installed.
|
||||
Some distributions have a package named `v4l2loopback-dkms` in the package manager, making the
|
||||
manual installation process unnecessary.
|
||||
Make sure that both `dkms` and `linux-headers` packages are installed as well.
|
||||
|
||||
### Usage
|
||||
|
||||
@@ -28,7 +26,7 @@ This section focusses on various use-cases for the v4l2loopback software.
|
||||
|
||||
### Create Temporary V4L2 Devices
|
||||
|
||||
v4l2loopback can be manually started by running:
|
||||
v4l2loopback can be manually started by running the following command.
|
||||
|
||||
```sh
|
||||
modprobe v4l2loopback card_label='V4L2 Loopback' video_nr=7 exclusive_caps=1
|
||||
@@ -48,10 +46,10 @@ 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](./systemd.md) a service can be
|
||||
created - as described in [the SystemD entry](./systemd.md#run-command-on-boot).
|
||||
For v4l2loopback create the file `/etc/systemd/system/v4l2loopback.service`
|
||||
containing the following lines:
|
||||
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.
|
||||
|
||||
```txt
|
||||
[Unit]
|
||||
@@ -81,7 +79,7 @@ sudo systemctl start v4l2loopback
|
||||
|
||||
## Troubleshooting
|
||||
|
||||
This section focusses on various errors that can appear in the v4l2loopback software.
|
||||
This section focuses on various errors that can appear in the v4l2loopback software.
|
||||
|
||||
### `Failed to start streaming on '/dev/video2' (Invalid argument)`
|
||||
|
||||
|
||||
@@ -12,12 +12,11 @@ It is used to set up [Wi-Fi](/wiki/linux/hardware_%28linux%29.md#wi-fi).
|
||||
This part assumes that your network interface is called `wlan0`
|
||||
(change it accordingly).
|
||||
|
||||
- First make sure that your [network interface is up](./ip.md).
|
||||
- First make sure that your [network interface is up](/wiki/linux/ip.md).
|
||||
- Save the authentication details to a file by running
|
||||
`wpa_passphrase <SSID> >> /etc/wpa_supplicant.conf`
|
||||
- Connect to the WLAN by running
|
||||
`wpa_supplicant -B -D wext -i wlan0 -c /etc/wpa_supplicant.conf`
|
||||
(`-B` is optional for running the process in the background)
|
||||
`wpa_passphrase <SSID> >> /etc/wpa_supplicant.conf`
|
||||
- Connect to the WLAN by running `wpa_supplicant -B -D wext -i wlan0 -c /etc/wpa_supplicant.conf`
|
||||
(`-B` is optional for running the process in the background)
|
||||
|
||||
## Troubleshooting
|
||||
|
||||
@@ -34,5 +33,5 @@ systemctl restart wpa_supplicant
|
||||
```
|
||||
|
||||
Afterwards - if the error still persists - it may be useful to reenable the Wi-Fi device as
|
||||
explained in the
|
||||
explained in the
|
||||
[section of the NetworkManager entry](/wiki/linux/networkmanager.md#restarting-and-reenabling-wi-fi).
|
||||
|
||||
@@ -1,9 +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 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.
|
||||
It is maintained by the [X.Org Foundation](https://x.org/wiki/).
|
||||
|
||||
## Usage
|
||||
@@ -51,16 +50,14 @@ With the mouse the window to close can then be selected.
|
||||
### Peripheral Devices
|
||||
|
||||
X also handles various options of peripheral devices.
|
||||
In the files of the directory `/etc/X11/xorg.conf.d` and the file
|
||||
`/etc/X11/xorg.conf` these settings can be found.
|
||||
In the files of the directory `/etc/X11/xorg.conf.d` and the file `/etc/X11/xorg.conf` these
|
||||
settings can be found.
|
||||
|
||||
The handling of input devices is achieved by xinput.
|
||||
For this the identifier of the device to show the options of is needed.
|
||||
By running `xinput list` a list of all devices with identifiers handled by
|
||||
xinput is printed.
|
||||
Properties and options of a peripheral device can then be shown by running
|
||||
`xinput list-props <id>` where `<id>` is the identifier of the
|
||||
device.
|
||||
By running `xinput list` a list of all devices with identifiers handled by xinput is printed.
|
||||
Properties and options of a peripheral device can then be shown by running `xinput list-props <id>`
|
||||
where `<id>` is the identifier of the device.
|
||||
|
||||
#### Touchpad
|
||||
|
||||
@@ -71,8 +68,7 @@ This section describes the handling of touchpads by X.
|
||||
To toggle the touchpad on or off
|
||||
[a simple script](https://github.com/tiyn/dotfiles/blob/master/.local/bin/tools/dwm/toggletouchpad)
|
||||
can be used that uses `synclient TouchpadOff=1` or `synclient TouchpadOff=0`.
|
||||
This requires `xf86-input-synaptics` which is a synaptics driver for
|
||||
notebook touchpads.
|
||||
This requires `xf86-input-synaptics` which is a synaptics driver for notebook touchpads.
|
||||
|
||||
##### Enable Tap to Click
|
||||
|
||||
@@ -93,8 +89,7 @@ This section describes the handling of keyboards by X.
|
||||
|
||||
##### Change Keyboardlayout
|
||||
|
||||
To temporarily change the layout of the keyboard just run
|
||||
`setxkbmap <your preferred 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>`.
|
||||
|
||||
If there are two main layouts are used then the following command can be used to switch between
|
||||
@@ -130,9 +125,9 @@ setxkbmap -layout <layout> -option compose:<compose>
|
||||
#### Display
|
||||
|
||||
This section describes the handling of displays by X.
|
||||
Additionally to the guides in this section that are independent of the used
|
||||
graphics unit special configuration for [Nvidia](/wiki/linux/nvidia.md)
|
||||
and [Intel](./intel.md) can be found in their respective entries in this wiki.
|
||||
Additionally to the guides in this section that are independent of the used graphics unit special
|
||||
configuration for [Nvidia](/wiki/linux/nvidia.md) and [Intel](/wiki/linux/intel.md) can be found in
|
||||
their respective entries in this wiki.
|
||||
|
||||
##### Turning Off the Screen
|
||||
|
||||
@@ -198,9 +193,8 @@ This section describes the handling of mouse by X.
|
||||
|
||||
##### Emulation of the Middle Mouse Button
|
||||
|
||||
If middle mouse button emulation is enabled the system will emulate a middle
|
||||
mouse button click when clicking both left and right mouse button
|
||||
simultaneously.
|
||||
If middle mouse button emulation is enabled the system will emulate a middle mouse button click
|
||||
when clicking both left and right mouse button simultaneously.
|
||||
The middle mouse button emulation can be activated or deactivated.
|
||||
First the current options have to be confirmed as explained in
|
||||
[the peripheral section](#peripheral-devices).
|
||||
@@ -211,14 +205,13 @@ 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 middle mouse button.
|
||||
`<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.
|
||||
If a section for the device is already present the line
|
||||
`Option "MiddleEmulation" "true"` should be added to it.
|
||||
Otherwise a catchall section for all types of mouses can be created like the
|
||||
following:
|
||||
If a section for the device is already present the line `Option "MiddleEmulation" "true"` should be
|
||||
added to it.
|
||||
Otherwise, a catchall section for all types of mouses can be created like the following.
|
||||
|
||||
```txt
|
||||
Section "InputClass"
|
||||
|
||||
Reference in New Issue
Block a user