Re: Not LFS
So, it's an HLFS (sort of)?
I'll take a look at the binutils docs - thanks for the pointer.
What immediately springs to mind as a potential concern, however, is incompatibilities that arise due to upstream development that relies upon hardcoded values, offsets, etc. - drivers and firmware in particular.
Also, keeping up-to-date with all the CVEs for standard elements is probably fine if you're on the kernel devs' mailing list but what about all the external elements and apps - your in-box must take some serious management, no?
I'm of two minds vis a vis systemd: on the one hand I find its monolithic mission creep disturbing but, on the other, the 'nspawn' function allows me to pivot to a sort of second-stage initramfs that lets me to use lvm on dm-cypt without the usual limitation to the pool size - boot an encrypted system that then mounts an image containing a standard lvm schema that maps encrypted devices, so you can add as many additional encrypted devices as you like at runtime, save changes, shutdown and protect your lvm schema with encryption too! I haven't found a way to do this with a init so, despite my misgivings about eggs, baskets and single points of failure, it has a very big plus going for it as far as I'm concerned.
I haven't been paying much attention for the last two years for various reasons, so my last knowledge of Wayland was that it was still the future - no-one but Canonical was giving it sufficient development support for it to be anything more last time I looked and Ubuntu is not my distro of choice; not even as a base from which to spin. Iirc, however, it seemed a bit like systemd to me, insofar as you ended up with some hybridised frankenWM whereby apps controlled their own window management without reference to anything else, thus doing more than should be within their remit as apps - which struck me as a bit dubious security-wise and also to pose a potential danger of runaway threads using up resources like a logic bomb. I assume you're going to tell me I needn't fret but I'd be happier with a pointer to some good documentation on Wayland, if it's all the same to you ; )