mtbc | (Reply)

From:

I will at least maintain some familiarity through, for instance, running a more conventional Debian installation on Dawn's laptop in an environment that suits her better: for example, she's using XFCE4, and I found that installing policykit-1 gave her login screen the option to shut down the computer (back in the day, I used some setuid xmessage thing for this with xdm), and that installing gvfs made it possible to plug in her cellphone to get the photographs from it, but I never actually found the things on the system that gave me the hint that those were the solutions to those problems, and how cgroups and whatnot fit into everything else I am losing track of. Whereas, with previous issues I've been better at at least hacking around them, for instance I can shut apt-get up by forging/tweaking package metadata and I can stop udev doing things by messing with (generally removing) its rules (I've not yet looked at vdev). It's possible that I'm just missing the big conceptual-but-detailed overview of this new ecosystem of things, together with some kind of wireshark-for-dbus and whatnot so I can better see what's actually going on, but unfortunately my local Debian developers here respond to my questions more in a my god, yes, I don't know either these days, it's horrifying, let me tell you about these other things that seem wrong lately kind of way, so you might be doing rather better than I for local knowledge that can help all this to make sense. Whereas, OpenBSD's simply easier to make sense of from the manpages and the shell scripts, configuration files and log files. But I bet it doesn't do various things that I'm not asking for but many Linux users are. Init-system-wise we do use systemd on our Ubuntu docker images at work so I try to keep an eye on those to at least get used to them. I'm glad it's still working well for you though and I will keep on using Debian in some places so as not to lose touch, maybe my understanding of it all will start to increase enough again.