User:Lahwaacz/Style violations

From ArchWiki
Jump to navigation Jump to search
Note: How to generate the reports:
  • Sync latest revisions with python --output-directory ArchWikiPages/ --clean
  • Run the grep commands in ArchWikiPages/en/ to exclude the path from the match prefix.
  • Append | awk -F '.mediawiki:' '{ gsub(/nowiki>/, "nowiki\\&gt;", $2); printf "* [[%s]]: {{ic|<nowiki>%s</nowiki>}}\n", $1, $2 }' | vim - to a grep command to generate a report.

Package management

Generated with grep -P "(pacman|yaourt) -S [[:alnum:]]" **/*.mediawiki --exclude="Help:*" --exclude "DeveloperWiki:*" --exclude "Talk:*"


Generated with grep -P "(#|\\$) sudo [[:alnum:]]" **/*.mediawiki --exclude="Help:*" --exclude "DeveloperWiki:*" --exclude "Talk:*"

Prompt inside Template:ic

Generated with grep -Pi "{{ic\|[ ]*(\$|#) [[:alnum:]]" **/*.mediawiki --exclude="Help:*" --exclude "DeveloperWiki:*" --exclude "Talk:*"

  • AMD_Catalyst: {{Note|To adhere to the new config location use {{ic|# aticonfig [...] --output}} to adapt the {{ic|Device}} section to {{ic|/etc/X11/xorg.conf.d/20-radeon.conf}}. The drawback is that many {{ic|aticonfig}} options rely on an {{ic|xorg.conf}}, and will be unavailable.}}
  • AMD_Catalyst: # Build your package and install; run {{ic|makepkg -i}} or {{ic|makepkg}} followed by {{ic|# pacman -U pkgname.pkg.tar.gz}}
  • AMD_Catalyst: {{ic|Catalyst-generator}} is not able to remove all those {{ic|<nowiki>catalyst-{kernver}</nowiki>}} packages automatically while being removed because there can not be more than one instance of pacman running. If you forget to run {{ic|# catalyst_build_module remove_all}} before using {{ic|# pacman -R catalyst-generator}} catalyst-generator will tell you which {{ic|<nowiki>catalyst-{kernver}</nowiki>}} packages you will have to remove manually after removing catalyst-generator itself.
  • AMD_Catalyst: *You may need to use {{ic|# pacman -Rdd}} to remove {{AUR|catalyst-utils}} (and/or {{AUR|lib32-catalyst-utils}}) because that package contains ''gl'' related files and many of your installed packages depend on them. These dependencies will be satisfied again when you install {{Pkg|xf86-video-ati}}.
  • AMD_Catalyst: {{Note|You should remove unofficial repositories from your {{ic|/etc/pacman.conf}} and run {{ic|# pacman -Syu}}, because those repositories include out-dated Xorg packages to allow use of {{ic|catalyst}} and the {{Pkg|xf86-video-ati}} package needs up-to-date Xorg packages from the [[Official repositories]].}}
  • Android: * if you need to install extra SDK plugins not found in the AUR, you must change the file ownership of /opt/android-sdk first. You can do this with {{ic|# chgrp -R users /opt/android-sdk ; chmod -R 0775 /opt/android-sdk}} (see [[File Permissions]] for more details).
  • ASUS_A6km: There should also be an '''irda0''' entry when running the {{ic|# ip a}} command.
  • Bcache: 4. Register the cache device against your backing device. To find its ''cache set UUID'', run {{ic|# bcache-super-show /dev/sdy2 | grep cset.uuid}} and then add it to the bcache device initially. Udev rules will take care of this on reboot and will only need to be done once.
  • Bluetooth_headset: Just do a {{ic|# systemctl restart bluetooth}} to apply it.
  • Btrfs: You can also run the scrub by [[starting]] {{ic|btrfs-scrub@.service}} (with the same encoded path). The advantage of this over {{ic|# btrfs scrub}} is that the results of the scrub will be logged in the [[systemd journal]].
  • Cgit: ** {{ic|# usermod -aG gitolite http}}
  • Cgit: **{{ic|# chmod g+rX /var/lib/gitolite}}
  • Cgit: **{{ic|# chmod -R g+rX /var/lib/gitolite/repositories}}
  • CPU_frequency_scaling: * Even P State behavior mentioned above can be influenced with {{ic|/sys/devices/system/cpu/intel_pstate}}, e.g. Intel Turbo Boost can be deactivated with {{ic|# echo 1 > /sys/devices/system/cpu/intel_pstate/no_turbo}} for keeping CPU-Temperatures low.
  • Create_root_filesystem_snapshots_with_LVM: {{Note|You should test the {{ic|# lvcreate}} command in the running system until it works as desired.
  • Create_root_filesystem_snapshots_with_LVM: Remove the test snapshots with {{ic|# lvremove}}. The snapshots taken from a running system are not as consistent as snapshots taken in single user mode or during startup.}}
  • Create_root_filesystem_snapshots_with_LVM: Enable the new service with {{ic|# systemctl enable mk-lvm-snapshots.service}}.
  • Create_root_filesystem_snapshots_with_LVM: After restarting the system with this grub entry {{ic|# lvs}} should show up the newly created snapshot.
  • Create_root_filesystem_snapshots_with_LVM: {{ic|# journalctl -u mk-lvm-snapshots.service}}.}}
  • Create_root_filesystem_snapshots_with_LVM: If you want to permantly stick to the updates just drop the snapshot with {{ic|# lvremove}}. If you want to revert to the snapshotted
  • Create_root_filesystem_snapshots_with_LVM: state issue a {{ic|# lvconvert --merge}} for the snapshot. During the next restart of the system (use the default target) the snapshot
  • CyberPower_UPS: Then run {{ic|# pwrstat -status}}. You should get something like this:
  • Disk_quota: *The command {{ic|# setquota}} may be used as an alternative of {{ic|# edquota}} [].}}
  • Disk_quota: Quotas are configured using {{ic|# edquota}} that will be opened in the default configured text editor:
  • Dm-crypt/Encrypting_a_non-root_file_system: {{Note|If it gives you the error {{ic|/dev/loop0: No such file or directory}}, you need to first load the kernel module with {{ic|modprobe loop}}. These days (Kernel 3.2) loop devices are created on demand. Ask for a new loop device with {{ic|# losetup -f}}.}}
  • Docker: To see current storage driver, run {{ic|# docker info {{!}} head}}, modern docker installation should already use {{ic|overlay2}} by default.
  • Dovecot: * Copy the example configuration: {{ic|# cp /usr/share/doc/dovecot/dovecot-openssl.cnf /etc/ssl/dovecot-openssl.cnf}}.
  • Dovecot: Run {{ic|cp /etc/ssl/certs/dovecot.pem /etc/ca-certificates/trust-source/anchors/dovecot.crt}} and then {{ic|# trust extract-compat}} whenever you have
  • DSDT: 1.) Extract ACPI tables (as root): {{ic|# cat /sys/firmware/acpi/tables/DSDT > dsdt.dat}}
  • DSDT: To check if you are really using your own DSDT read your table again {{ic|# cat /sys/firmware/acpi/tables/DSDT > dsdt.dat}}
  • Etckeeper: # Permit execution of file for ''root'' ({{ic|# chmod u+x /etc/cron.daily/''script_name''}}).
  • General_troubleshooting: : {{Note|At this point, the root filesystem will be mounted '''read-only'''. Execute {{ic|# mount -o remount,rw /}} to make changes.}}
  • General_troubleshooting: * As a last resort, boot with the '''Arch Linux Installation CD''' and mount the root filesystem on {{ic|/mnt}} then execute {{ic|# arch-chroot /mnt}}.
  • General_troubleshooting: # Mount your root {{ic|/}} filesystem on {{ic|/mnt}} and your {{ic|/boot}} filesystem on {{ic|/mnt/boot}} and chroot into the broken system by executing {{ic|# arch-chroot /mnt}}.
  • General_troubleshooting: # Rebuild the dynamic linker run-time bindings file {{ic|/etc/}} by executing {{ic|# ldconfig}}.
  • General_troubleshooting: # Rebuild the [[Initramfs]] by executing {{ic|# mkinitcpio -p linux}}.
  • GPD_Pocket: {{ic|# pacman -Syu --noconfirm gpd-pocket-support}}
  • HAproxy: Enable {{ic|haproxy.service}} [[Systemd#Using_units|using systemd]]. HAProxy's configuration can be reloaded live using {{ic|# systemctl reload haproxy.service}}.
  • Hylafax: * After installation please run {{ic|# faxsetup}}. Answer the questions and modify to your needs.
  • Hylafax: * Run {{ic|# faxaddmodem}}. It asks you for the device, leave out the {{ic|/dev}} prefix; only enter eg. modem, ttyS0 or such things.
  • Installing_Arch_Linux_on_a_USB_key: * Before creating the initial RAM disk {{ic|# mkinitcpio -p linux}}, in {{ic|/etc/mkinitcpio.conf}} add the {{ic|block}} hook to the hooks array right after udev. This is necessary for appropriate module loading in early userspace.
  • Installing_Arch_Linux_on_a_USB_key: * It is highly recommended to review the [[Improving_performance#Reduce_disk_reads.2Fwrites|reduce disk reads/writes]] wiki article prior to selecting a filesystem. To sum up, [ ext4 without a journal] should be fine, which can be created with {{ic|# mkfs.ext4 -O "^has_journal" /dev/sdXX}}. The obvious drawback of using a filesystem with journaling disabled is data loss as a result of an ungraceful dismount. Recognize that flash has a limited number of writes, and a journaling file system will take some of these as the journal is updated. For this same reason, it is best to forget the swap partition. Note that this does not affect installing onto a USB hard drive.
  • Kodi: * '''LIRC_button''' is the name as defined in {{ic|lircd.conf}}. If lircd.conf was autogenerated using {{ic|# irrecord}}, these are the names selected for the buttons. Refer back to [[LIRC]] for more information.
  • Let’s_Encrypt: {{Expansion|Explain what the Nginx ({{ic|# certbot --nginx}}) and Apache plugins actually do and how they modify the webserver configuration. So far this section targets only the [[#Webroot]] and [[#Manual]] ways.}}
  • LVM: Before moving free extents to the end of the volume, one must run {{ic|# pvdisplay -v -m}} to see physical segments. In the below example, there is one physical volume on {{ic|/dev/sdd1}}, one volume group {{ic|vg1}} and one logical volume {{ic|backup}}.
  • LVM: * the {{ic|--alloc anywhere}} option is used as we move PEs inside the same partition. In case of different partitions, the command would look something like this: {{ic|# pvmove /dev/sdb1:1000-1999 /dev/sdc1:0-999}}
  • LVM: Once all your free physical segments are on the last physical extent, run {{ic|# vgdisplay}} and see your free PE.
  • LVM: Fix: assuming you already tried to activate the volume group with {{ic|# vgchange -ay ''vg''}}, and are receiving the Input/output errors:
  • Map_scancodes_to_keycodes: {{Tip|You can obtain the identificator for the device you want to setup a custom ''hwdb'' rule for by using {{ic|# evemu-describe}}. This utility provided by the {{pkg|evemu}} package.}}
  • Map_scancodes_to_keycodes: On each upgrade of [[Systemd]], the installation script rebuilds {{ic|hwdb.bin}} by running {{ic|# udevadm hwdb --update}} so we do not need to care about it.
  • Map_scancodes_to_keycodes: Be aware that with {{ic|udevadm}} only added or changed key mapping are loaded so if we delete a mapping from the config file, rebuild {{ic|hwdb.bin}} and run {{ic|# udevadm trigger}} then the deleted mapping still kept by the kernel, at least until a reboot.
  • Microcode: * {{ic|# modprobe cpuid}}
  • Migrate_installation_to_new_hardware: ***"{{Ic|# grep -Ri 'hostname' /etc}}" should give some hints on the files to be updated
  • Official_repositories: # Perform a {{ic|# pacman -Syuu}} to "rollback" your updates from these repositories.
  • Openbox: Setting the root window's background color can be disabled by editing the Openbox startup script found in {{ic|/usr/lib/openbox/openbox-autostart}}. Simply comment out (or delete) the block starting with {{ic|# Set a background color}}.
  • OpenVPN: Run {{ic|# openvpn /etc/openvpn/server/server.conf}} on the server, and {{ic|# openvpn /etc/openvpn/client/client.conf}} on the client. Example output should be similar to the following:
  • Pacman/Package_signing: If you are still having issues, make sure the following file exists {{ic|/root/.gnupg/dirmngr_ldapservers.conf}} and that you can successfully run {{ic|# dirmngr}}. Create an empty file if it doesn't and run {{ic|# dirmngr}} again.
  • PeerGuardian_Linux: For further information, please refer to the {{ic|# Whitelist IPs #}} section of {{ic|/usr/lib/pgl/pglcmd.defaults}}.
  • Powertop: # Use powertop to produce a report on parameters: {{ic|# powertop <nowiki>--html=powerreport.html</nowiki>}}
  • PPTP_server: Allow GRE packets (protocol 47) in {{ic|/etc/ufw/before.rules}}, find the line with: {{ic|# drop INVALID packets}} and add rule:
  • Pure-FTPd: The server can be started using {{ic|# systemctl start pure-ftpd}}.
  • Pure-FTPd: To start the server automatically, use {{ic|# systemctl enable pure-ftpd}}.
  • Pure-FTPd: {{ic|# echo "/bin/false" >> /etc/shells}}
  • Readline: Now type a line and press {{ic|Alt}}+{{ic|W}}. Readline will act as though {{ic|Ctrl+E}} (end-of-line) had been pressed, appended with '{{Ic| # macro}}'.
  • Redmine: {{Note|For Redmine prior to 2.x this step is done by executing {{ic|# bundle exec rake generate_session_store}}.}}
  • Ruby: Then install required gem {{ic|# pacman -S ruby-$gemname}}.
  • Ruby_on_Rails: {{Note|If you get an error like {{ic|Errno::ENOENT: No such file or directory (...) An error occurred while installing x, and Bundler cannot continue.}}, you might have to configure [[Ruby#Bundler|Bundler]] so that it installs gems per-user and not system-wide. Alternatively, run {{ic|# rails new testapp_name}} once as root. If it has completed successfully, delete {{ic|testapp_name/}} and run {{ic|$ rails new testapp_name}} again as a regular user.}}
  • Samba: * disabling shell - {{ic|# usermod --shell /usr/bin/nologin --lock username}}
  • SANE/Scanner-specific_problems: If your device is connected on the network, use {{ic|# hp-setup <printer ip>}} instead.
  • Secure_Shell: {{Tip|When using socket activation neither {{ic|sshd.socket}} nor the daemon's regular {{ic|sshd.service}} allow to monitor connection attempts in the log, but executing {{ic|# journalctl /usr/bin/sshd}} does.}}
  • Secure_Shell: # Use {{ic|# journalctl -xe}} for possible (error) messages.
  • Simple_stateful_firewall: {{Tip|For self-testing the rules after setup, the actual blacklisting can slow the test, making it difficult to fine-tune parameters. One can watch the incoming attempts via {{ic|cat /proc/net/xt_recent/sshbf}}. To unblock the own IP during testing, root is needed {{ic|# echo / > /proc/net/xt_recent/sshbf}}}}
  • Smokeping: Verify that your config is fine via {{ic|# nginx -t}} and reload the configuration via {{ic|# nginx -s reload}}.
  • Solid_State_Drives/NVMe: To test if NVME Power Management is working, install {{AUR|nvme-cli}} if running an older kernel, and run {{ic|# nvme get-feature -f 0x0c -H /dev/nvme[0-9]}}.
  • Solid_State_Drives/NVMe: If ASPT is enabled but no non-zero states appear in the table, the latencies might be too high for any states to be enabled by default. The output of {{ic|# nvme id-ctrl /dev/nvme[0-9]}} should show the available non-operational power states of the NVME controller. If the total latency of any state (enlat + xlat) is greater than 25000 (25ms) then to enable it you must pass a value at least that high to the {{ic|default_ps_max_latency_us}} option for the {{ic|nvme_core}} module in the boot parameters. This should enable ASPT and make the table in {{ic|# nvme get-feature}} show the entries.
  • Systemd-nspawn: {{Note|The package {{Pkg|linux-firmware}} required by {{Pkg|linux}}, which is included in the {{Grp|base}} group and isn't necessary to run the container, causes some issues to {{ic|systemd-tmpfiles-setup.service}} during the booting process with {{ic|systemd-nspawn}}. It's possible to install the {{Grp|base}} group but excluding the {{Pkg|linux}} package and its dependencies when building the container with {{ic|# pacstrap -i -c -d ~/MyContainer base --ignore linux [additional pkgs/groups]}}. The {{ic|--ignore}} flag will be simply passed to {{Pkg|pacman}}. See {{Bug|46591}} for more information.}}
  • TigerVNC: {{Note|In order to keep the vncserver alive when the user logs out (physically or via ssh), one must enable the linger option for loginctl like this: {{ic|# loginctl enable-linger username}} Failure to do so will result in the vncserver getting killed when the user logs off the machine.}}
  • Tor: {{ic|# machinectl login tor-exit}} login to the container, see [[Systemd-nspawn#machinectl]].
  • Tor: {{ic|# mv /srv/container/tor-exit/etc/securetty /srv/container/tor-exit/etc/securetty.bak}} if you get the error described in [[Systemd-nspawn#Troubleshooting]].
  • Tor: Check if the {{ic|nofile}} (filedescriptor) limit is successfully raised with {{ic|# sudo -u tor 'ulimit -Hn'}} or {{ic|# sudo -u tor bash}} and {{ic|# ulimit -Hn}}.
  • Tor: {{ic|ExitPolicy reject XXX.XXX.XXX.XXX/XX:*}} should reflect your public IP and netmask, which can be obtained with the command {{ic|# ip addr}}, so exit connections cannot connect to the host or neighboring machines public IP and circumvent firewalls.
  • Udev: {{Note|By default, the USB host controllers are all enabled by default for wakeup. The status can be checked using {{ic|# cat /proc/acpi/wakeup}}.}}
  • Volnoti: Open {{ic|~./xbindkeysrc}} in a text editor and add these lines before the string {{ic|# End of xbindkeys configuration}}:
  • XScreenSaver: You can configure xscreensaver to write to a log file by creating the logfile {{ic|# touch /var/log/xscreensaver.log}} and then specifying its X resource ''logFile''.
  • ZFS: Use {{ic| # parted --list}} to see a list of all available drives. It is not necessary nor recommended to partition the drives before creating the zfs filesystem.
  • ZFS: If the command is successful, there will be no output. Using the {{ic|$ mount}} command will show that the pool is mounted. Using {{ic|# zpool status}} will show that the pool has been created.
  • ZFS: and enable a service instance for each encrypted volume: {{ic|# systemctl enable zfs-key@dataset}}.