News for hackers. Stuff that matters.
Re:Systemd-homed merged as a fundamental change to Linux hom... by erik_seaberg on Friday January 31, 2020 @05:08PM (#22206387)
I seem to recall this is incompatible with cronjobs, which puts it pretty far to the the game console end of the tool spectrum.
Re:Systemd-homed merged as a fundamental change to Linux hom... by tyingq on Friday January 31, 2020 @05:12PM (#22206428)
Pretty sure it also breaks ssh logins. This needs more discussion before blessing it. Systemd has bled far, far, beyond an init replacement.
Re:Systemd-homed merged as a fundamental change to Linux hom... by throw0101a on Friday January 31, 2020 @05:49PM (#22206747)
> Systemd has bled far, far, beyond an init replacement.

This has been my main objection to it: feature creep (with tight coupling between 'components').

Re:Systemd-homed merged as a fundamental change to Linux hom... by pnako on Saturday February 01, 2020 @06:40PM (#22214044)
Don't worry about SSH, just wait for the systemd replacement for SSH.
Re:Systemd-homed merged as a fundamental change to Linux hom... by PlutoIsAPlanet on Saturday February 01, 2020 @06:24AM (#22209965)
You can store SSH keys in the user records.

systemd was never just an init replacement, it's a project that includes an init replacement.

Re:Systemd-homed merged as a fundamental change to Linux hom... by gnfurlong on Sunday February 02, 2020 @02:04PM (#22218648)
Systemd-homed isn't inventing the idea of encrypted home partitions and fundamentally, what you're saying is that cron is incompatible with encrypted home partitions (or any other auto mounted home partition, ex: network mounted). The same is true for the concerns about ssh.

If you listened to the original talk from Lennart, you're really just giving examples of one of his major points. Because /etc/passwd wasnt flexible enough to accomodate arbitrary user properties, user configuration has organically spread out over time into all these "side car" configuration files. Some are scattered around /etc so not easily portable while others are in the user's home directory and suffer from exactly the scenario you've mentioned. One of the goals of systemd-homed is to add a portable, extensible format for a user record external to the home directory which would mean that systemd-homed rather than causing, could actually lead to a solution for the issue you've highlighted.

Re:Systemd-homed merged as a fundamental change to Linux hom... by markandrewj on Friday January 31, 2020 @06:00PM (#22206843)
I'm not sure if your comment is accurate or not, but systemd timers have existed for a while now, and provide some flexibility cron doesn't.
Re:Systemd-homed merged as a fundamental change to Linux hom... by superkuh on Friday January 31, 2020 @06:07PM (#22206907)
They had better provide flexibility for all the complexity and tedium they introduce. It takes creating two new config files of about 10 lines each and a long system command to set up the simplest possible systemd timer.
Re:Systemd-homed merged as a fundamental change to Linux hom... by mbreedlove on Friday January 31, 2020 @06:45PM (#22207177)
Yep, I wanted to create a systemd timer to run my nightly backups.

I was pretty shocked that I needed to have three files. My backup script, a systemd service to call the backup script, and a systemd timer to call my systemd service that calls my backup script.

It took A LOT of fiddling and reading the Arch wiki before I had everything working as I wanted it to.

Re:Systemd-homed merged as a fundamental change to Linux hom... by markandrewj on Friday January 31, 2020 @07:27PM (#22207460)
I have also set up timers in Arch, and it wasn't that bad...
Re:Systemd-homed merged as a fundamental change to Linux hom... by catalogia on Saturday February 01, 2020 @11:32PM (#22215147)
Really? How did you do it then?
Re:Systemd-homed merged as a fundamental change to Linux hom... by markandrewj on Sunday February 02, 2020 @01:24PM (#22218406)
https://wiki.archlinux.org/index.php/Systemd/Timers

You can also find more documentation on the official systemd website, or Gentoo, CoreOS, and RedHat's website.

As an example: https://wiki.gentoo.org/wiki/Systemd#Timer_services

Re:Systemd-homed merged as a fundamental change to Linux hom... by catalogia on Sunday February 02, 2020 @06:56PM (#22220346)
I'm confused, unless I'm missing something, both of those pages seem to describe exactly the process mbreedlove described:

    1) create systemd service to call your script
    2) create a systemd timer to call that service
What did you do differently?
Re:Systemd-homed merged as a fundamental change to Linux hom... by markandrewj on Sunday February 02, 2020 @07:01PM (#22220377)
I didn't say I did anything different, I said it wasn't that difficult.
Re:Systemd-homed merged as a fundamental change to Linux hom... by gerdesj on Friday January 31, 2020 @05:48PM (#22206737)
Please elaborate because that sounds odd to me. How on earth can a home directory manager mess with another daemon? I use winbind's associated PAM NSS module to run up a home dir as needed for my AD joined Linux machines. cron still works.

I don't do games consoles, only business systems.

Re:Systemd-homed merged as a fundamental change to Linux hom... by mondoshawan on Friday January 31, 2020 @06:19PM (#22206995)
Easy: crontabs are in /var/spool/cron/..., not /home, and user editable. If the user's homedir isn't mounted because they logged off and cleared their security tokens, any crontab they write that uses their homedir will break.
Re:Systemd-homed merged as a fundamental change to Linux hom... by pmlnr on Saturday February 01, 2020 @01:10AM (#22209027)
The same way pulseaudio stops playing when the screen locks. Most annyoing behaviour I've ever had.
Re:Systemd-homed merged as a fundamental change to Linux hom... by renox on Saturday February 01, 2020 @04:59PM (#22213539)
That's a reasonable default behaviour, can you change it though?