docs: bring the wiki up to 2.0.0 — install and run, on every platform
The wiki still described a one-platform product installed a way that no longer
exists. Home called UniData "in progress" and did not mention UniVerse at all;
the walkthrough installed 1.3.1 by hand and configured a UniObjects/UniRPC
server, which the CLI stopped using in #45; nothing documented install.sh,
GIT.SETUP, mvgitd, or the command set.
New:
Installing-on-UniData prerequisites, install.sh, per-account setup,
upgrading, and how the CLI actually reaches records
Installing-on-UniVerse the same, plus why mvgitd exists and what it does not
need (no service, no administration)
Installing-on-MVX release package and the submodule/standalone builds
Command-reference all 24 commands with their flags, generated from the
dispatch table in BP/GIT rather than transcribed
Updated:
Home platform matrix, both surfaces, demo account, 2.0.0
Account-git-structure dictionaries across platforms -- the SM/association
remap, I-type canonicalisation, @ID, furniture and
the trailing newline; and that both surfaces now
project through one implementation (#108)
udt-demo install section replaced by a pointer to the guide;
the UniObjects environment variables are called out
as no longer used rather than silently deleted, since
people have them in their shell profiles
UniData-troubleshooting a banner marking the UniRPC entries as not applying
to 2.0.0, naming the four that still do
_Sidebar grouped nav
The obsolete UniRPC appendix is kept and labelled, not removed: it is still
correct for anyone using UniRPC for other reasons.
docs: troubleshooting entry for udt locale rejection (C.UTF-8 / POSIX)
udt validates $LANG/$LC_ALL against an allow-list of locale names: en_US.UTF-8
and C start; C.UTF-8 and POSIX are rejected with 'does not belong to current
language group'. C.UTF-8 is the default in minimal/sudo/cron/systemd/ssh
contexts, so udt can fail there even when the login shell is en_US.UTF-8.
Give the table + the LANG fix, and note udt-git's spawned udt inherits it.
docs: troubleshooting entry for libgit2 ownership check on shared UniData accounts
UniData accounts are almost always shared directories owned by the DBA /
install user, while udt-git runs as the invoking user, so libgit2's
CVE-2022-24765 owner check (GIT_EOWNER) fires as the normal case. Document
it as expected, with the safe.directory allow-list (per-account, blanket,
and host-wide), and note the non-fatal CallC verb-catalog line.
docs: udt-git EL8 release targets libgit2 1.7 (EPEL libgit2_1.7), no source build
The official EL8 build links libgit2.so.1.7 so end users install the
runtime with 'dnf install epel-release && dnf install libgit2_1.7' — a
parallel-installable EPEL package, no compiler. Flip the demo prereq
and the troubleshooting libgit2 section from the 1.9 from-source path to
this; keep the build-your-own path (min libgit2 1.0, -l:libgit2.so.1.7)
and note preflight prints the exact soname a given binary needs.
docs: pin the libgit2 version requirement (build min 1.0, runtime 1.9.x soname) + note EPEL libgit2_1.7 as an alternate source
UniData troubleshooting: correct the 81014 story (root-only unirpcservices; udtsetup does configure udcs) + add fresh/cloud PAM + password gotchas
Add UniData troubleshooting page (81014 udcs/unirpcservices, libunidata.so, session errors)