I can't tell what is going on here. Are those 5 logo-sized images supposed to be logo submissions for 2017? Or are they submissions from previous years? Also the animated gif is really hard to read

I can't tell what is going on here. Are those 5 logo-sized images supposed to be logo submissions for 2017? Or are they submissions from previous years? Also the animated gif is really hard to read

If Nikumubeki is the most polite, one has to wonder: what is he holding back?

Dead members should not be able to enter

Do you think he has sexually assaulted other memebers?

I hadn't previously had any experience with systemd (and it probably has nothing to do with my upgrade issue), but after dealing with it on centos7 it makes me want to gouge my own eyes out with a rusty spoon.

it's an annoying thread

It's bad but I'm slowly getting used to it.

I actually like systemd when I'm writing "init scripts". In quotes because I think they are more like configuration files. Very easy and quick to write, once you know how. I once read the old joke "systemd is a great operating system, it just lacks a good init system" and I actually think it's the other way around. If they would just pull everything out and leave in the init system it would be a huge improvement.

GuixSD uses the GNU Daemon Shepherd as its init system, which is developed in tandem with Guix and is written in Guile as well. It was previously known as "dmd", which stood for "Daemon managing Daemons" or "Daemons-managing Daemon", but changed names to avoid collision with another project.[SUP][10][/SUP]

Shepherd takes some inspiration from systemd, another recent init system, in supplying user space functionality asynchronously as services, which under Shepherd are generic functions and object data types that are exported for use by the Shepherd to extend the base operating system in some defined way. Core to the Shepherd model of user space initialisation is the concept of the extension, a form of composability where services are designed to be layered onto other services, augmenting them with more elaborate or specialised behaviours as desired.[SUP][11][/SUP] This expresses the instantiation-based dependency relationships found in many modern init systems,[SUP][12][/SUP] making the system modular, but also allows services to interact variadically with other services in arbitrary ways.

Shepherd also provides so-called virtual services which allow dynamic dispatch over a class of related service objects, such as all those which instantiate an MTA for the system.[SUP][13][/SUP] A system governed via the Shepherd daemon can represent its user space as a directed acyclic graph, with the "system-service" − responsible for early phases of boot and init − as its root, and all subsequently initialised services as extensions to system-service's functionality, either directly or over other services.[SUP][11][/SUP][SUP][14][/SUP]

Being both written and configured in Guile Scheme, GNU Shepherd is intended to be highly programmable by the system administrator, but it can also be used to manage per-user profiles of unprivileged daemons and services.[SUP][15][/SUP] Its services and configuration are stored uniformly as object-oriented Scheme code, and while a core set of services are provided with the basic Guix System Distribution,[SUP][16][/SUP] arbitrary new services can be flexibly declared, and through Guile's object system, GOOPS, existing services can be redefined at the user's discretion by asking the Shepherd to dynamically rewrite services in specified ways on instantiation.[SUP][17][/SUP][SUP][18][/SUP]

GNU Shepherd was originally designed to work with GNU Hurd, and was later adopted by GuixSD.[SUP][19][
[/SUP]

it makes me want to gouge my own eyes out with a rusty spoon.