On 07/27/2014 11:14 AM, Paul Flint wrote: > Dear Tony, > > I worry that I will never get out of the "etc/init.d/blah" habit... > On the other hand, how much like a registry do we need in our lives? > I wonder why systemd can't have a shell capability?
To answer the specific question, I don't see why you can't use it along with the shell, have it trigger a shell script in the right circumstance, no? Anyway, I'm more of a programming language fan, than a Unix fan, so from my point of view, taking shell programming as sacred just leads to stuff like autotools (shutter). The problem I was most recently solving had to do with devices, audio not working consistently on the family desktop (also similar issues with suspend on my laptop). This was my first real dive into systemd. My problem turned out to be that startx was not quite up to speed with systemd; systemd itself was doing the right thing. When I finally figured out the problem, I was pretty excited to see device permissions working correctly for the first time in 20 years or so of Linux. It is so cool to switch through virtual consoles (X, text, other) and see that the access control lists of various devices are switching appropriately. This is a big deal for a family of five, and not something you can do with groups (consolekit sort of worked, sometimes). Now I dream of ssh-agent working both at the console and in X. What is good for system init is good for user init. Down with distribution specific shell spaghetti code controlling everything. Here is to hoping that systemd is as clean and well designed as it seems at first glance so I don't have to eat my words. BTW is it just me or does systemd sound like something from a PKD novel? -- Anthony Carrico
signature.asc
Description: OpenPGP digital signature
