https://boards.4channel.org/g/thread/84936528 interesting read tho

О Anonymous 12/27/21(Mon)02:47:16 №.84939384 >>84939400 >>84941760 >>84943288
>>8493923:
Anonymous 12/27/21(Mon)02:31:02 No.84939235 >>84939346 >>84939384
О Anonymous 12/27/21(Mon)00:08:02 No.84937584 >>84939235 >>84939414
О 12/26/21(Sun)22:45:36 No.84936621 >>84936636 >>84937170 >>84937584 >>84941678 >>84944244
>>84936591
systemd-homed which makes home owned nobody:nobody but translates it into your uid/gid so you can transfer it between users/computers?? i
forgot i dont really care about what systemd does
Basically systemd-homed plus an LDAP server plus a block storage cluster to store the encrypted home containers lets you have "roaming profiles" better than
Windows ever managed. It's a super useful feature for corporate networks but worth jack all for home users. Only worry if it becomes mandatory for laptops.
Interesting, tell me more
So the big problem with mounting /home on a network is that it all has to be ONE server if it's NFS or Samba. a massive single point of failure. This is true even in Windows shops where
the kludgy workaround is to split people on to smaller LDAP/AD groups with different centralized servers. The servers have to all the file permission metadata handling, which is a major
cause of network file slowness.
With systemd-homed the encryption is per user and each user is represented as one loopback mount image file, which removes a fuckload of limitations. You can use a clustered block level file
storage solution like Ceph, or an iSCSI connection to a proprietary SAN, and just treat them like disk images, including keeping rollback copies. If you use Ceph, the only centralized
services you need are DNS, LDAP, and DHCP, which can be a cheapass Windows domain controller or a Linux based equivalent (like LTSP with PXE).