Talk:X Keymap

From Just Solve the File Format Problem
Jump to: navigation, search

Possibly incorrect category as "System files"

This is specific to X server, which means the graphical side of possibly many Unix-like environments. Without these files, sure, the user has no way of possibly inputting anything from their physical keyboard, but only while using X server. Not all installations comes with a graphical environment, also not all users strictly uses X server. So I am not sure if this is placed the appropriate category.

Conversely on Linux,

  • Files in /boot, typically vmlinuz-linux, initramfs*.img, bootloader files (e.g. lilo, grub2, systemd-boot, etc...), as well EFI System Partition (ESP) for modern UEFI machines (these usually reside on a separate partition/volume, mounted as /boot/efi) would prevent a Linux installation from (successfully) booting, well before it could reach to the graphical environment.
  • Wayland is gaining widespread traction, as a replacement for soon-to-be obsolete X server. These files may not have any effect on installations that uses Wayland instead.
  • Risks like these could be minimized by means of mostly using:
    • Immutable OS such as (but are not limited to): Fedora Silverblue,
    • Immutable design e.g. NixOS - which makes deleting files harder unless you specify /nix directory,
    • Copy on Write filesystems, like btrfs when correctly setup to use snapshot

Anonymoususer852 (talk) 02:19, 10 August 2025 (UTC)

Personal tools
Namespaces

Variants
Actions
Navigation
Toolbox