15 Sep
2020
15 Sep
'20
6:49 p.m.
On 2020-09-15 13:39:42 Dr. Nikolaus Klepp wrote:
Anno domini 20:09:27 Tue, 15 Sep 2020 +0200 (CEST)
Felmon Davis via tde-users scripsit:
Which raises the question: why would a user wander with his home on a stick
from computer to computer? For "security"? His/Her home an be stolen, lost,
corrupted ... for what? To "ease" backup? Definitly not. That was why NFS
was invented. DJs with floppies in their hands preceded NFS. I thought that
times were dead for good.
1984 that was. What a magical number, so full of inspiration.
If you have only "libsystemd0" it's ok, if you have systemd as init .. you
remeber "svchost" from windows?
homed looks to me like another cure in search of a disease, much like the
semantic search "improvements" added in various desktops that made them
mostly unresponsive.
As Victor Borge said of his uncle the inventor, "He discovered the cure for
which there was no disease. Unfortunately, he later caught the cure and
died." :-)
Leslie
On Tue, 15 Sep 2020, Dr. Nikolaus Klepp wrote:
(I need more popcorn .. and a spellchecker)
Anno domini 18:08:23 Tue, 15 Sep 2020 +0200
(CEST)
Felmon Davis scripsit:
[...]
many of the reasons you cite go beyond my technical knowledge but I'll
venture comments on a couple: 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?
There are hords of resons. 1)
security relies on trust into the computer you plug your home in.
Well, that's a bad plan to begin with. System is compromised, sor
your home is now compromised, too. And becaus of the ease to do, you
compromomise all systems you go to that day and the next day ...
I guess it depends on the intended use-case. if I want to transfer
'home' to another one of my computers, there is no problem or rather,
I already had a problem if the computer I'm transferring to is
compromised. and as someone pointed out further down-thread
(sorry, I can't find
the msg!) this may be suitable to a business environment.
Yes, I can vividly imagine some suits not carring their Notebooks around
but USB flashdives .. no, won't happen. Companies have servers - there is a
reason why these bethelemoths are named that way. Campus/university? Nop,
neither that. Everybody has his/her notebook ... oh, maybe it is intended
to use a home on the phone and plug that thing as USB flashdrive .. no,
won't happen either, we had that problem on the list earlier.
2) TRhis
problem was solved when? 40 years ago? When was it,
NFS+yellowpages was introduced?
I have no idea. will have to look this up. sometime.
You can. But then you have to fix systemd-homed before (remember that JSON
file), 'cause sooner or later some genus will find out about "user
groups",
and will start to "fix" that, too. And each run of "chown ..." will
change
the entire home directory, so your flashdrive will like it.
3) It does not address at all the problems of
different hardware and
different OS. You can share your home on any *nix system you like -
if you are a bit coutious - without systemd-homed. You cannot any
more when you use systemd-homed.
I don't follow. even rsync-ing to another computer may involve some
fix-ups as Kate expressly indicated. you are saying once installed by
'systemd-homed' I cannot fix configuration files in 'home'? 4) WTF
encrypted JSON? This is soooo systemd. Remember the "benefits"
of binary logfiles? 5) "systemd-homed" looks more like
"systemd-owned"
than anything else.
Nik
I don't use systemd or at least didn't until it cropped up in my
install of MX and 4QOS but I think that's minimalistic. anyway, I'm not advocating systemd, just
wondering what's so terrible
about systemd-homed.
It solves a problem that does not exist since 1984. It solves it in a way
that it breaks onlmost anything but the most simple usecase - and there
it's not needed in the first place.
it sounds like what's terrible about
systend-homed is that it's
systemd!
Knowinf the origin of a software often gives a strong hint on what to
expect. And yes, comming from systemd is alost the same nogo as comming
from gnome.
Nik
> f.