if you like them and are interested in what they are about.

I watch lots of game and movie trailers - or ads - and love it.

I didn't know about either of those things. Thanks.

I'm busy being happy that Yosemite has finally made it easy to see which programs are still running. I have no idea how people ever though this was easier.

Thanks.

The pain was pretty difficult for a while but for the moment I'm pretty comfortable. Hopefully it will stay that way until after I can get the surgery.

Appreciate it.

I think everything will be fine. And at the moment the pain is really limited. So all things considered, it could be tons worse.

A Fedora community member releases periodic respins of Fedora stable releases; they're not official releases and they don't go through QA but FWIW I'd trust the guy if I needed a respun image in a pinch. http://jbwillia.wordpress.com/ is his site, you can find the spins at https://alt.fedoraproject.org/... .

One of the definitions I found was:

One who makes great sacrifices or suffers much in order to further a belief, cause, or principle.

I am sure that fits. While SpaceShip II is mainly intended for a non-exploration purpose, the program has resulted in some significant advances in rocketry and White Knight II has significant non-tourism use. These pilots have been involved in other space efforts, I remember the one who was injured from the Rotary Rocket test flights. There are lots of safer ways for these folks to make as much money as a test pilot is paid. They do what they do to advance our progress in aeronautics and space.

well, ultimately the init system launches *everything* if you take a broad enough view of things, but that doesn't mean the init system is somehow responsible for your desktop environment's display configuration.

I mean, if you're really determined to, you can 'configure' things by modifying their init scripts, sure, but it's usually not the right way to do it. X has a perfectly good configuration system already. So does GNOME. If you want to change the DPI at one or other of those levels, go configure it through their configuration systems. That's how it's supposed to work.

That's far too reductionist. For a start, there are many sysv-compatible init implementations that do parallel boot; upstart does it, Mandriva's pinit does it. There's a whole subset of LSB that exists exclusively to provide a way for sysv initscripts to represent dependencies *precisely in order to enable parallel init* - see https://wiki.debian.org/LSBIni... for a good write-up of that.

Secondly, insofar as systemd is intended to improve boot speeds, it wasn't actually just about implementing simple parallelization of sysv-style services using dependencies. If you read http://0pointer.de/blog/projec... it talks a lot about parallelization but it's actually talking about making *more* parallelization possible, not just *implementing* parallelization: the big idea Lennart had back then was the idea that you don't actually have to completely start up a service in order to start up another service that 'requires' it, if you can create the socket it listens on before it's ready, then queue up any requests and pass them on to the service once it's actually done starting up. Lennart was clearly really excited about this idea at the time, but if you look at systemd these days, it's a really pretty small corner of all the things it does.

All the way through the first part of that first post, Lennart is really talking about making more parallelization possible, he's not simply talking about implementing inter-service dependencies.

These days systemd does an awful lot more, and it really isn't just about making boot faster any more. Even in the very first post, once you get past the first half, it starts talking about improved capabilities. I find startup speed the least interesting thing about systemd, really, I'm much more interested in the improved capabilities for units and especially in the improved logging journald provides.

"Since RedHat's obviously the largest major proponent"

For the record, there's absolutely nothing 'obvious' about that. People tend to assume that since Lennart was @redhat.com when he wrote systemd it's 'obviously' a Red Hat project, but it really isn't, and never was. It's a Lennart project: he came up with the idea and he wrote it. Red Hat didn't ask for it, didn't actually have any idea it was coming.

The very first instance of all these battles that get fought every six weeks in some distro or on /. or on Phoronix happened in Fedora, when Lennart first proposed switching to systemd. Around the same time / a bit later, all the same battles happened within Red Hat. Just as with every other distro, systemd's proponents brought the idea and argued for it. systemd wasn't planned from the top down by 'Red Hat authorities' as 'our new init system', Lennart came up with it on his own, and convinced the plurality of significant folks/bodies within Fedora and RHEL that it was a good idea.

Um. What? Display DPI is nothing the system init daemon cares about and never *has* been.

It can be set at the X level or at the desktop environment level. Some desktops respect X's setting, some ignore it.

In GNOME you can set both text scaling and full display scaling (the new thing used for hi-dpi screens) in GNOME Tweak Tool. Text scaling is in Fonts, it's the 'Scaling Factor' - if you think about things in DPI terms, just consider the 'scaling factor' to be a multiple of 96, e.g. if you want to set 110 DPI, set it to 1.14.

If you mean GNOME's decided your display is hidpi and starting scaling *everything*, that's the 'Window scaling' setting on the Windows tab, set it to 1 (which is no scaling).

Again, none of this has the slightest thing to do with init.

Martyrs? Who killed them for their beliefs?

Go away, troll. They certainly died while pursuing something intensely important that they were willing to risk their lives for. The fact that you weren't around to pull the trigger makes them no less martyrs.