Message: previous - next
Month: September 2020

[trinity-users] Re: systemd-homed - new thread

From: Michael via tde-users <ml-migration-agent@...>
Date: Tue, 15 Sep 2020 11:35:30 -0500
On Tuesday 15 September 2020 11:08:23 am Felmon Davis wrote:
> On Tue, 15 Sep 2020, William Morder via tde-users wrote:
> > Better not to give in to conspiracy-theory thinking here. I believe a
> > simpler proportion is at work.
> there may be truth in some of this but it seems a bit like
> thread-drift - perhaps retraction of apfelstr�del must be considered;
> how does this relate to systemd-homed?
> it seems systemd-homed brings precisely the benefit which Kate
> mentioned is lacking in our usual way of moving 'home'; she wrote:
> "I don't understand why this is even needed?! I can already move home
> directories without a problem. Been doing it for years. I just make
> sure to use the same user on the same distro, same etc. Works
> perfectly. Or I save key settings (konq bookmarks, FF bms, etc) it's
> so easy after that to just retheme to spec."
> I take it with systemd-homed one doesn't get trapped by shifting UIDs
> and such. they write (partial quotation),
> "Linux assigns UIDs in the order usernames are registered on a
> machine. you may get UID 1000 if you are the first user on a laptop
> and you could get 1001 on another laptop if you are the second user to
> be registered there. This poses a problem if you move a home directory
> container from machine A where you're UID 1000 to machine B where you
> are 1001. systemd-homed solves this by doing a chown -R on the entire
> home directory if there is a conflict. [...]"
> I once fell athwart of that! not to mention that 'home' gets encrypted.
> why isn't this a net bonus?

"All user-specific records are stored within a JSON formatted file called 
~/.identity which is cryptographically signed with a key out of the users 

.."out of the users control"...

Welcome to Big Brother?

Seriously, homed says my data is not mine.  Worse, if homed borks, then I've 
lost ALL my data.

This reply from the linked article, also seems to be relevent:

> systemd-homed solves this by doing a chown -R on the entire home directory 
if there is a conflict.


I'm supposed to trust you to know what my home directory permissions are 
supposed to be?

Are you fucking crazy?"

Background on this is that, especially in a developer's system, it's frequent 
to have files owned by different users and groups within your home.  homed is 
just going to overwrite all that.
tde-users mailing list -- users@...
To unsubscribe send an email to users-leave@...
Web mail archive available at