* Packages
… that took me more than one minute to find.
** spell-checking
- hunspell
- myspell-fr_FR
* HOWTO
** Disks
*** Auto-mount second disk under =$HOME/media=
#+begin_example
$ lsblk --fs
[…]
nvme0n1
└─nvme0n1p1 xfs                […UUID…]
$ sudo $edit /etc/fstab
[… add:
UUID=[…UUID…]   […$HOME…]/media         xfs     user,exec       0  0
…]
$ mkdir ~/media
$ mount ~/media
#+end_example
** Network
*** Open ports
#+begin_src sh
$ firewall-cmd --add-port=8000/tcp
$ firewall-cmd --add-service=mdns
#+end_src
To make permanent, either:
- run the command with =--permanent=, and restart ~firewalld~ for
  immediate application,
- run the command /a second time/ with =--permanent=,
- run ~firewall-cmd --runtime-to-permanent~.
** Software
*** Disable Akonadi
Takes up RAM, clutters htop; no use for it.
**** 🙅 via configuration? (symptom)
1. ~akonadictl stop~
2. set =StartServer=false= in =~/.config/akonadi/akonadiserverrc=.

Gave up at step 2: that file already existed, had some =[Sections]=,
and I was too lazy to look up where =StartServer= should go.
**** 🙅 via reading [[https://userbase.kde.org/Akonadi#Disabling_the_Akonadi_subsystem][the docs]]?
Insist on the /Digital Clock/ widget being a likely culprit, but the
/Calendar Events/ option (as it is spelled here) is unchecked.
**** 🙅 via uninstallation?
~zypper remove --clean-deps akonadi~ shows some collaterals (sqlite3).
**** 🙆 via configuration? (cause)
Kudos [[https://unix.stackexchange.com/questions/725548/kde-plasma-prevent-akonadi-stuff-from-being-launched-at-startup][MC68020]] for finding the culprit - kalendarac is the auto-started
service that loads Akonadi.  Suppress with =Hidden=True= in
=${XDG_CONFIG_HOME:-~/.config}/autostart/org.kde.kalendarac.desktop=.