User:Lahwaacz/Style violations

From ArchWiki
Jump to: navigation, search
Note: How to generate the reports:
  • Sync latest revisions with clone.py: python clone.py --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:*"

sudo

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

Prompt inside Template:ic

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

  • 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]].}}
  • AMD_Catalyst: * Ensure that you are loading the correct agp modules for your AGP chipset before you load the {{ic|fglrx}} kernel module. To determine which agp modules you will need, run {{ic|# hwdetect --show-agp}}. Then open your {{ic|/etc/modules-load.d/fglrx.conf}} and add the agp module on a line '''before''' the {{ic|fglrx}} line.
  • 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: {{ic|# dd if=/path/of/tryingToResuePatrition of=/path/to/backUp.iso}}
  • Cgit: ** {{ic|# usermod -aG gitolite http}}
  • Cgit: **{{ic|# chmod g+rX /var/lib/gitolite}}
  • Cgit: **{{ic|# chmod -R g+rX /var/lib/gitolite/repositories}}
  • Change_root: {{Note|If trying to access an [[Disk_encryption|encrypted]] filesystem, do not forget to first unlock its container (e.g. with {{ic|# cryptsetup open /dev/sdX# ''name''}} for [[Disk_encryption#Block_device_encryption|dm-crypt/LUKS]]-based encryption), then mount the device using its previously supplied device-mapper ''name'' (under the form {{ic|# mount /dev/mapper/''name'' /mnt/arch/...}}). More info: [[Dm-crypt/Device_encryption#Unlocking.2FMapping LUKS partitions with the device mapper|Unlocking/Mapping LUKS partitions with the device mapper]].}}
  • Change_username: *Also do not forget to edit accordingly the configuration files in {{ic|/etc}} that relies on your absolute path (i.e. Samba, CUPS, so on). A nice way to learn what files you need to update involves using the grep command this way: {{ic|# grep -r {old_user} *}}
  • 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_a_Public_Key_Infrastructure_Using_the_easy-rsa_Scripts: {{ic|# openvpn --genkey --secret /root/easy-rsa/keys/ta.key}} (This is no typo -- the command generates a ta.key file)
  • 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
  • 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: {{ic|# pwrstat -status}}
  • 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}}.}}
  • Dovecot: * Copy the configuration file from the sample file: {{ic|# cp /etc/ssl/dovecot-openssl.cnf{.sample,} }}.
  • Dovecot: Run {{ic|mv /etc/ssl/certs/dovecot.pem /etc/ca-certificates/trust-source/anchors/dovecot.crt}} and then {{ic|# trust extract-compat}} whenever you have
  • Drupal: # Start the Postfix service: {{ic|# systemctl start postfix}}.
  • 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}}
  • 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.
  • Hyper-V: # After the rest of the installation, install {{Pkg|grub}}: {{ic|# pacman -S grub}}.
  • Hyper-V: # Run {{ic|grub-mkconfig}}: {{ic|# grub-mkconfig -o /boot/grub/grub.cfg}}.
  • Installing_Arch_Linux_on_a_USB_key: * It is highly recommended to review the [[SSD#Tips_for_minimizing_disk_reads.2Fwrites|tips for minimizing disk reads/writes]] on the [[SSD]] wiki article prior to selecting a filesystem. To sum up, [http://fenidik.blogspot.com/2010/03/ext4-disable-journal.html ext4 without a journal] should be fine, which can be created with {{ic|# mkfs.ext4 -O "^has_journal" /dev/sdXX}}. 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.
  • 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.
  • KDE: # To update from a previous KDE installation, run: {{ic|# pacman -Syu}} or {{ic|# pacman -S kde-unstable/kde}}
  • Kodi: {{Tip|If using {{AUR|kodi-standalone-service}}, the default for the profile is /var/lib/kodi/.kodi and be sure to chown the newly created file to the kodi user and group, i.e. {{ic|# chown -R kodi:kodi /var/lib/kodi}}}}
  • 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.
  • Linux-pf: * If you notice disk-related performance problems or occasional hiccups, it might be an I/O scheduler issue. Try a different one than the linux-pf default (BFQ) by echoing to {{ic|/sys/block/sda/queue/scheduler}} ''cfq'', ''noop'' or ''deadline'': {{ic|# echo noop >| /sys/block/sda/queue/scheduler}}. Note, the aforementioned command only sets the I/O scheduler for the 1st hard drive and additional ''echoes'' will be needed if you have more. If the situation improves, then append "''elevator''='''''cfq'''''" (or '''''noop''''' or '''''deadline''''') to the linux-pf command line in {{ic|/boot/grub/menu.lst}}, to make the change permanent.
  • Logitech_Unifying_Receiver: Solaar is also available from the AUR: {{AUR|solaar}}. At installation the Solaar package is creating the group plugdev. After installation add you user to the plugdev group ({{ic|# gpasswd -a $USER plugdev}}) to use Solaar as non-root user.
  • 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 PE 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: {{ic|# lvconvert --merge /dev/vg0/snap01}}
  • 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: 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
  • Nginx: {{ic|# rm /run/fcgiwrap.sock}}
  • Official_repositories: # Perform a {{ic|# pacman -Syyuu}} to "rollback" your updates from these repositories.
  • OpenVPN: Run {{ic|# openvpn /etc/openvpn/server.conf}} on the server, and {{ic|# openvpn /etc/openvpn/client.conf}} on the client. You should see something similar to this:
  • Pacman_tips: * Issue the following command to install from the backup list: {{ic|# pacman -S $(< pkglist.txt)}}
  • PeerGuardian_Linux: For further information, please refer to the {{ic|# Whitelist IPs #}} section of {{ic|/usr/lib/pgl/pglcmd.defaults}}.
  • PHP: For {{Pkg|imagemagick}} run {{ic|# pecl install imagick}}. The ''pecl'' binary is included in the {{Pkg|php-pear}} package. Then add
  • Powertop: # Use PowerTOP to produce a report on parameters: {{ic|# powertop <nowiki>--html=powerreport.html</nowiki>}}
  • Prelink: {{ic|# chmod 755 /etc/cron.daily/prelink}}
  • Prelink: {{ic|# chmod 755 /etc/profile.d/kde-is-prelinked.sh}}
  • Prey: The installer should enable automatically the [[systemd]] service '''prey-agent''' to start Prey at boot. You can check if it's loaded and running with {{ic|# systemctl <nowiki>|</nowiki> grep prey-agent}}
  • Prosody: {{Ic|# systemctl start prosody}}
  • Prosody: {{Ic|# systemctl enable prosody}}
  • Prosody: {{Ic|# prosodyctl adduser <JID>}}
  • 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|# rake generate_session_store}}.}}
  • Reflector: Then {{ic|# systemctl start reflector}} will update your mirrorlist.
  • Ruby: * Gems are updated along with the rest of your system. As a result, you never need to run {{ic|gem update}}: {{ic|# pacman -Syu}} suffices.
  • 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.}}
  • SABnzbd: * reload systemd with {{ic|# systemctl --system daemon-reload}}
  • SABnzbd: * reload systemd with {{ic|# systemctl --system daemon-reload}}
  • Samsung_N150: To enable hotkeys to change backlight, wireless, and system performance settings, it is necessary to give regular users certain permissions via the [[sudo]] command. Run {{ic|# visudo}} and add the following to the Cmnd alias specifications:
  • 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.}}
  • Simple_stateful_firewall: {{Tip|For self-testing the rules after setup, the actual blacklist happening 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}}}}
  • Steam/Wine: * If you still have trouble starting games, use {{ic|# mount --bind /path/to/SteamApps ~/.local/share/Steam/SteamApps -ouser=your-user-name }}, this is the only thing that worked with {{ic|TF2}} for one Arch user.
  • Systemd-nspawn: You need to set up the container .network manually after pacstrapping and {{ic|# systemctl enable [[systemd-networkd]]}} (your dhcp client) with systemd-nspawn's -n switch to ensure a virtual Ethernet link is setup. Don't forget to populate your container's {{ic|/etc/resolv.conf}} with your DNS server IPs.
  • Tor: {{ic|# machinectl login tor-exit}} login to the container, see [[Systemd-nspawn#machinectl command]].
  • 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 succesfully 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.
  • Transmission: To load the new configuration run {{ic|# sysctl --system}} and then reload Transmission.
  • 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.