[volunteers] January 7th talk about systemd?

[Rick Moen]

Akkana wrote:

> I've also recently left the bay area and moved to New Mexico

Yeah, I thought that was what I remembered (he says, through an
antihistimine haze).  FWIW, a quick check on your Web pages still suggests
you're a San Jose person, so at your leisure you might want to update that.

> I know Alison has been working on a systemd talk, while I'm way
> behind the curve on systemd myself.


Just for your inoformation, Debian sid's packaging of systemd is a very
conservative one:  Although it builds and installs all of the many
components provided by upstream systemd, it _uses_ only these three daemons:
he systemd core init, udevd, and logind.

(This is per a debian-project posting by Russell Stuart:
https://lists.debian.org/debian-project/2014/11/msg00072.html)

systemd daemons provided in the Debian package but UNUSED according to
Stuart are consoled, hostnamed, journald, localed, machined, networkd,
resolved, shutdownd, timedated, and timesyncd.   This follows Debian's
customary pattern of conservative implementation, thereby, e.g., avoiding
rushing to implement journald's controversy-wreathed binary logfiles.

As Stuart points out, many critics have gone off half-cocked based (in part)
on not understanding this difference.  

tl;dr:  The systemd implementation on your Debian sid system is a somewhat
different proposition from what you would get by default on, say, Fedora or
OpenSUSE, and it is best to be careful to not overgeneralise, or to at least
ask for starters '_Whose packaging_ of systemd?'