• 0 Posts
  • 21 Comments
Joined 1 year ago
cake
Cake day: August 3rd, 2023

help-circle








  • tslnox@reddthat.comtoLinux@lemmy.mlSystemD is still too raw
    link
    fedilink
    arrow-up
    2
    arrow-down
    1
    ·
    10 months ago

    I’m a long time Gentoo user. No systemd ever. When my old computer started failing and my Gentoo started falling apart (mostly because I made multiple mistakes when trying out testing versions of Plasma 5 and also due to me not updating for a long time and then getting into a long list of blockers) I installed OpenSUSE (Tumbleweed… Once you go rolling release, you can’t go back. :-D).

    In just a few weeks, no idea why or how, it started having a weird problem. When shutting down, every time, it got stuck on some error (waiting for session something, I believe, but I don’t remember really) and it was waiting 1.5min until it continued. No explanation of what exactly it’s waiting for, no way to say “continue now without waiting”… No amount of googling got me anywhere near to finding out what the problem was.

    Later I also ran into a problem where I was changing something about hard drives, I changed the fstab too, but for some reason systemd was getting stuck on trying to mount the drives that weren’t in the fstab anymore. Later I found out that it was my fault, I had a line that mounted the drive, and a few lines later I had some mount bind line operating on that first mount or something, but I still think the normal init system would just spit out that it can’t mount that and go on.


  • /usr/local/sbin/adduser.local

    One line in there and you can make it add a new line with appropriate /home/userX/.cache tmpfs line to fstab.

    Or, maybe a cleaner way, you might make a init/systemd service that, when booting, would run something like

    for each dir in /home do
    mount dir/.tmp -type tmpfs
    done

    I’m not at the computer now and I’m lazy to Google it, so this above is just a pseudo code and probably won’t run.