Lets take a moment to remember Justin Beiber has purchased a ticket.

That's just it. No one here is AGAINST NEW TECH. They are against defaulting new tech on reference and enterprise software.

Systemd is half baked. Wake me when its cooled and ready to eat.

> Let the good people who develop your distro worry about these hard parts.

I needed RHEL7 in January. It sort of works in November. I work in devops and know better than anyone developers can not be trusted to sort the shit out for us.

I don't use automount because it is flakey. Admittedly this seems to be a solved problem on Ubuntu. But on RHEL7, you best be using automount or you are going to have a bad time. But with solutions like this, who needs problems? It will be the first of many RHEL6 it is.

Truespace is a very acessible 3D program. I loved the simplicity of its binary object tools. You might not make the most efficient model in TS, but its solid.

And when it fails it fails hard. I can't say I agree with your approach either. If you are concerned about how fast your server boots up after downtime you've already lost. A Server failure should not take down multiple critical systems. That's how you save real money.

>Because, you know, Zimbra can't use the postfix, apache httpd, amavis, tomcat or openldap that comes with RHEL

Part-time problems. I suggest you haven't looked closely enough at RHEL's capabilities (see channel subscriptions) or you should probably just go with something like Ubuntu or Fedora if you want/need bleeding edge. Though I did a check and I'm not sure what your issue with Zimbra on RHEL is anyway.

I'm in the exact same boat. RHEL7 GA stability has been atrocious. Most of my problems have been related in some way or another to systemd.

Congratulations you've decided that uptime matters more than your stability. Such wisdom!

> given that when the server is down, the phones are down, the security system's video recording is down, the internet access and internal networking is down, the environmental controls for the building are down, etc.

What?

> but if you're doing security updates, it boils down to having update everything sooner or later - might as well have it all on one machine.

Oh ok, you're trolling.

I am so old the teardrops are coming to my eyes.

Well technically it is.

Thank you, this is my every day as systemd's birth has been painful to say the least.

The assumption that I am free to choose what platform I support is bonkers. I am asking to choose the init system. I make multiplatform software. I need to support every distro, and it has fractured in to SysV and SysD. It will fracture again further in the future. Locking in is stupid stupid stupid and anti-UX

Why not indeed!

THe problem is this has been top down dictated. The correct way would have been to offer both, and let developers develop for BOTH. Not systemd primacy. Beg for secondary.

Great, so what happens when journald breaks>?