Systemd's new feature: systemd-homed. Your thoughts ?
Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I am yet to play with ubuntu 20.04 which bundles this with systemd 245 (I will, in a week or so and add to the conversation), but if any of you have been using this, I would be very much interested in your opinion about it, specially in regards with -
a. Enterprise application - This does not play well with users logging in over ssh or so the links claim. (at the time of writing)
b. /home mounted on a NFS location: It is possible to set up /home on a nfs server (or NAS box) and then use autofs to mount it when it is reqd(when the user logs in). What happens in those cases ?
c. Users managed by AD/LDAP etc - AD keeps the record of UID/GID anyway, so what's the point of keeping that again in .identity ?
d. Anything else you think about it.
Distribution: debian, lfs, whatever else i need in qemu
Posts: 268
Rep:
hate systemd and everything about it. causes so many troubles and does things on it's own under the hood requiring extensive knowledge to fix. screw it and people who advocated it and accepted it to debian, redhat, centos, ubuntu.
Distribution: Mainly Devuan, antiX, & Void, with Tiny Core, Fatdog, & BSD thrown in.
Posts: 5,509
Rep:
Dislike systemd also, (I always look for distros that don't use it), &, from what I've read, too much software is being written with hooks into it for my liking.
Distribution: openSUSE, Raspbian, Slackware. Previous: MacOS, Red Hat, Coherent, Consensys SVR4.2, Tru64, Solaris
Posts: 2,813
Rep:
Quote:
Originally Posted by rkelsen
This is a solution to a problem nobody has...
This pretty much nails it.
Sure, I've had a laptop that had multiple users defined on it: myself, a 'postgres' account for a local database owner/dba (also me while I'm wearing my Pg dba hat), an http account owning a local Apache instance for hosting HTML-based documentation, etc. I suspect, though, that that is not the use case that ol' Lennart is thinking about and which I'm not sure I "get" the purpose of on a laptop. I'll need to see an example of how and why this is a good thing to even be doing. My personal take is that it smells like something Windows-inspired.
Whatever its intended purpose, I haven't seen it yet. My sole Tumbleweed-based system is running "245" but I haven't noticed it in the system services utility part of YaST and haven't seen anything "homed"-related anywhere. (To be honest, I'm not looking real hard for it.) Maybe the OpenSUSE folks are watching out for us. :^D
There are two large, fundamental problems with this:
Quote:
Originally Posted by https://www.howtogeek.com/673018/systemd-will-change-how-your-linux-home-directory-works/
"As we mentioned previously, a person’s home directory is decrypted whenever he or she logs in. But if someone is remotely accessing the computer over SSH, the SSH keys in the home directory can’t be referenced because the home directory is still encrypted until that person logs in. Of course, one needs the SSH keys to authenticate against before he or she can log in."
Whoever designed this "feature" clearly doesn't use ssh. I have boxes everywhere running Linux. I use OpenVPN with ssh to administer them with my laptop. They all do different jobs and exist in geographic locations which are up to 30 miles apart. I can't live without remote ssh access to those machines. It is just not practical to spend the day driving between sites.
The second problem:
Quote:
Originally Posted by https://www.howtogeek.com/673018/systemd-will-change-how-your-linux-home-directory-works/
"Let’s say someone transports his home directory to a new machine. If the UID is already being used on the new machine by someone else, he’ll be assigned a new UID automatically. Of course, all his files will have to have their ownership reassigned to the new UID.
Currently, this is being handled by a recursive, automatic application of the chown -R command. This will probably be handled differently in the future when a more elegant scheme is developed. This heavy-handed approach doesn’t take into account the daemons and processes that run as other users."
Well that certainly seems like very poor design choice. That's being polite. I can't say what I wanted to say because I'd get banned from here.
I'm sorry, but I fail to see any practical use for this "feature" outside of a closed university-style computer lab. It certainly has very little appeal in the business world, IME. You can call me a hater all you like... I just want to get stuff done.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.